Jump to content

Orange Pi 5 Support


Efe Çetin

Recommended Posts

@Efe Çetinwill give it a try! :)

@Efe Çetin i have tried both: the cli version and the desktop version. Both works! The desktop start without problems and the nvme ssd works to boot from! Really nice! :) So it´s a good build!

 

I have also tried to enable 3d support as mentioned on the downloadpage fo the Orangepi5 https://www.armbian.com/orangepi-5/ And offcourse followed the instructions here: https://launchpad.net/~liujianfeng1994/+archive/ubuntu/rockchip-multimedia

But youtube in chromium wont play at all. Freeze complete on 4k resolution. Firefox runs a lot smoother but also on 1440 or 1080p. But i think i do something wrong because the RK3588s should be able to play on 8K resolution?

Edited by haajee
Link to comment
Share on other sites

@Avatar Ng@Nodon For the sake of completeness and for the benefit of others – the KingSpec M.2 2242 NVMe SSD comes in different variants:

  • NX series PCIe M-key
  • NT series SATA III (marketed as NGFF which really means M.2) B+M key
  • older NE series sold as PCIe with B+M key

From https://semiconductor.samsung.com/consumer-storage/support/faqs/nvmessd/

Quote

There are different types of M.2 slots. A “B-Key” enables SATA or PCIe NVMe™ SSDs using up to 2 PCIe lanes, while an “M-Key” enables NVMe™ SSDs with the use of up to 4 PCIe lanes.

 

B key is 6 narrow + the rest wide

M key is wide + 5 narrow

B+M key is 6 + wide + 5

Link to comment
Share on other sites

@haajee

I had also some difficulties to get video hw acceleration in Chromium and Kodi, but now it's all working, even hdr10 and hdr8 do work in Kodi (gbm) by renaming the dtb overlay files from rock 5b to rk3588-.....

What I did to make it work: (perhaps some of the latest steps were not necessary, I was clueless)

 

sudo add-apt-repository ppa:liujianfeng1994/panfork-mesa

sudo add-apt-repository ppa:liujianfeng1994/rockchip-multimedia

 

sudo nano /etc/rc.local

echo dec > /dev/video-dec0
chown root:video /dev/video-dec0
chmod 0660 /dev/video-dec0
echo enc > /dev/video-enc0
chown root:video /dev/video-enc0
chmod 0660 /dev/video-enc0

 

sudo nano /etc/udev/rules.d/11-rockchip-multimedia.rules

KERNEL=="mpp_service", MODE="0660", GROUP="video"
KERNEL=="rga", MODE="0660", GROUP="video"
KERNEL=="system-dma32", MODE="0666", GROUP="video"
KERNEL=="system-uncached-dma32", MODE="0666", GROUP="video" RUN+="/usr/bin/chmod a+rw /dev/dma_heap"


sudo ln -s /lib /usr/lib64

cd /usr/lib64/ && sudo ln -s aarch64-linux-gnu/libv4l2.so.0.0.0 libv4l2.so

sudo apt-get update && sudo apt dist-upgrade

sudo apt install chromium-browser=$(apt-cache show chromium-browser|grep Version|grep rkmpp|cut -d " " -f2) chromium-codecs-ffmpeg-extra=$(apt-cache show chromium-browser|grep Version|grep rkmpp|cut -d " " -f2) libv4l-rkmpp v4l-utils

 

sudo nano /etc/chromium-browser/default 

CHROMIUM_FLAGS="--use-gl=egl"

 

You might need to replace the existing one, not sure about that
wget https://github.com/JeffyCN/rockchip_mirrors/raw/libmali/firmware/g610/mali_csffw.bin

sudo mv mali_csffw.bin /lib/firmware/

 

For hw acceleration you need to use gbm or wayland. The easiest way I found was installing ubuntu-desktop.

sudo apt install ubuntu-desktop

Then add add the following line to /etc/gdm3/custom.conf

WaylandEnable=true

 

After that I had still no acceleration with videos in Chromium, then I tried some things, probably a lot of unnecessary stuff.

I'd installed almost all the ffmpeg related things from the added repository and mesa-vulkan-drivers primus-vk libgles2-mesa libd3dadapter9-mesa

As I said most likely not all necessary but this worked for me  

 

Now I can watch 4k videos on YouTube with Chromium with around 15% cpu load.

Kodi only displays video with GBM (run Kodi from Login screen after copying it to wayland)

sudo mv /usr/share/xsessions/kodi.desktop /usr/share/wayland-sessions/kodi-wayland.desktop

 

For HDR in Kodi under gbm I renamed in /boot/dtb/rockchip/overlay/ 

rock-5b-radxa-display-10hd.dtbo  --> rk3588-display-10hd.dtbo

rock-5b-radxa-display-8hd.dtbo  --> rk3588-display-8hd.dtbo

 

Now the HDR sign on my tv came up,

 

The only things I would really have working is audio passthrough in Kodi and cec, so if anyone knows what has to be done for that I would really like to know.

I've got multichannel audio working however, so I can live without it for a while.

 

I'm really glad how quick all these things are working by all the hard work of the developers, thank you

Link to comment
Share on other sites

Releases 130+ works now for me as well to boot from NVMe and without a SD card inserted. Below are my steps that I used.

 

Clear disk in case there are partitions already.

 

dd if=/dev/zero of=/dev/nvme0n1 bs=1M count=1
dd if=/dev/zero of=/dev/mtdblock0 bs=1M count=1

 

Create partitions, format them and set labels.
 

# create partitions
parted -s /dev/nvme0n1 mklabel gpt
parted -s /dev/nvme0n1 mkpart primary fat16 17m 285m
parted -s /dev/nvme0n1 name 1 '"bootfs"'
parted -s /dev/nvme0n1 set 1 bls_boot on
parted -s /dev/nvme0n1 mkpart primary ext4 285m 100%
parted -s /dev/nvme0n1 name 2 '" "'

# format partitions
mkfs.fat /dev/nvme0n1p1
mkfs.ext4 -F /dev/nvme0n1p2

# create labels
dosfslabel /dev/nvme0n1p1 armbi_boot
tune2fs -L armbi_root /dev/nvme0n1p2

 

Install the existing system onto the NVMe.

  • Select "Boot from MTD Flash, system on SATA, USB or NVMe"
  • Select the partition "/dev/nvme0n1p2" for rootfs and format as EXT4
  • Then it installs bootloader to SPI (mtdblock0)
  • Select "Exit" instead of "Power off"

Since the armbian-install command does not copy data to the dedicated /boot partition and also does not update all files, we prepare the bootfs manually.

 

mkdir /mnt/boot /mnt/root
mount /dev/nvme0n1p1 /mnt/boot
mount /dev/nvme0n1p2 /mnt/root
    
rsync -av /boot/* /mnt/boot/
rsync -av /boot/* /mnt/root/boot/

# The set command is "fish" shell syntax
set UUID (blkid -o export /dev/nvme0n1p2 | grep -E '(^UUID=)' | cut -d '=' -f 2)
sed -i "s#rootdev=UUID=[A-Fa-f0-9-]*#rootdev=UUID=$UUID#" /mnt/boot/armbianEnv.txt
sed -i "s#rootdev=UUID=[A-Fa-f0-9-]*#rootdev=UUID=$UUID#" /mnt/root/boot/armbianEnv.txt

# not needed, installer updated to the correct UUID already
#sed -i "s#UUID=[A-Fa-f0-9-]* / ext4#UUID=$UUID / ext4#" /mnt/root/etc/fstab
    
# Works without the next 2 steps.
# /dev/nvme0n1p1 is not mounted as /boot partition and the armbian-install installed all /boot files into the /boot folder on the rootfs partition
# Not sure which way is better. With or without /boot partition
set UUID (blkid -o export /dev/nvme0n1p1 | grep -E '(^UUID=)' | cut -d '=' -f 2)
echo "UUID=$UUID /boot vfat defaults 0 2" >> /mnt/root/etc/fstab
  • Power off
  • Remove SD card
  • Boot from NVMe

Output after NVMe boot.
 

root@orangepi5 ~# lsblk -f
NAME        FSTYPE FSVER LABEL      UUID                                 FSAVAIL FSUSE% MOUNTPOINTS
mtdblock0
zram0                                                                                   [SWAP]
zram1                                                                      28.2M    32% /var/log
nvme0n1
├─nvme0n1p1 vfat   FAT16 armbi_boot 9A27-3D56                             128.8M    50% /boot
└─nvme0n1p2 ext4   1.0   armbi_root 6df3fbd7-700a-4324-805e-b72a4c4d41ed    442G     0% /var/log.hdd
                                                                                            /
root@orangepi5 ~# uname -a
Linux orangepi5 5.10.110-rockchip-rk3588 #trunk.0133 SMP Thu Jan 5 03:03:13 UTC 2023 aarch64 aarch64 aarch64 GNU/Linux

 

Edited by Marco Schirrmeister
typo
Link to comment
Share on other sites

@royk I didn't try your method:

-- Modify rootdev in armbianEnv.txt is the same as your boot.cmd change and is preferred way to customize boot parameter.

-- I did try dd image directly to NVMe SSD and it worked. Now I have some data on rootfs of SSD, I prefer to use separate partition for testing, by selecting different one when running armbian-install.

Link to comment
Share on other sites

Hello everyone.

 

First of all, thanks for the support for orange pi 5. I'm just learning to use SBC with orange pi and armbian, and I really love it! So I buy the orange pi 5, thinking to use armbian as my main desktop.

 

I'm struggling for the past 4 days to get usb wifi working in Armbian jammy xcfe in the latest nightly build. My wifi is RTL8812AU. I tried to learn more (searching on github, and this forum) and it seems like I need to compile the driver.

 

But when I try to do it, the best I can get is error on missing scripts/module.lds. can anyone help on this one? Or where should I go to make this usb wifi working on armbian

 

P.s this functionality is working out of the box on the original Orange Pi image

Link to comment
Share on other sites

@zjd Only setting the bootenv didn't work for me, but ArmbianEnv.txt seems to be the better place to set that indeed.

For me it begun to boot after also change the line where it searches the boot UUID of the first partition of the sd-card/mmc.

After writing the image you didn't have to edit these lines?

Link to comment
Share on other sites

Thanks Marco for posting the tips for getting the GPU working. 

 

I was unable to get mpv, a newly compiled vlc or gst-launch to work with the GPU but the ffplay provided by liujianfeng1994 did work however it only can play up to 4k. At 8k, it chokes with a bunch of messages like 

Quote

[hevc_rkmpp @ 0x7f90019a60] Unable to convert39KB sq=    0B f=0/0   

Any tips / tricks on getting 8k going?

 

With the orangepi distribution it can play 8k but the colors are all washed out making it unusable and I would rather go with Armbian anyway.

 

Cheers.

Link to comment
Share on other sites

On 1/4/2023 at 4:48 PM, Avatar Ng said:

now mine official bullseye Debian image is able to get up and running on SPI Flash+SATA SSD, a bit tricky though.

I'd like to know if this is faster than the ~350MB/s of the Gen3x1 NVMe/PCIe interface. SATA is capable of running at ~500MB/s. Could you run "hdparm -t --direct /dev/sda" (or whatever interface you SATA SSD is) and post the result?

Link to comment
Share on other sites

04.01.2023 в 22:48, Avatar Ng сказал:

Special thanks to @wizetek @Nodon and others helpful folks. It seems like NVMe SSD is default supported (bootloader "/usr/lib/linux-u-boot-legacy-orangepi5_1.0.8_arm64/rkspi_loader.img" ), however SATA SSD need a special bootloader (#1 /usr/share/orangepi5/rkspi_loader_sata.img ), #2 and also to enable following in /dev/sda1 (boot partition "/boot/orangepiEnv.txt"),

My SATA SSD still doesn't work after these steps:

orangepi@orangepi5:$ dmesg | grep pci

 

[    5.517433] reg-fixed-voltage vcc3v3-pcie2x1l2: Looking up vin-supply from device tree
[    5.517493] vcc3v3_pcie2x1l2: supplied by vcc5v0_sys
[    5.574978] vcc3v3_pcie2x1l2: 1800 mV, enabled
[    5.575052] reg-fixed-voltage vcc3v3-pcie2x1l2: vcc3v3_pcie2x1l2 supplying 1800000uV
[    6.297427] rk-pcie fe190000.pcie: invalid prsnt-gpios property in node
[    6.297438] rk-pcie fe190000.pcie: Looking up vpcie3v3-supply from device tree
[    6.298122] rk-pcie fe190000.pcie: missing legacy IRQ resource
[    6.298140] rk-pcie fe190000.pcie: IRQ msi not found
[    6.298146] rk-pcie fe190000.pcie: use outband MSI support
[    6.298152] rk-pcie fe190000.pcie: Missing *config* reg space
[    6.298173] rk-pcie fe190000.pcie: host bridge /pcie@fe190000 ranges:
[    6.298205] rk-pcie fe190000.pcie:      err 0x00f4000000..0x00f40fffff -> 0x00f4000000
[    6.298222] rk-pcie fe190000.pcie:       IO 0x00f4100000..0x00f41fffff -> 0x00f4100000
[    6.298242] rk-pcie fe190000.pcie:      MEM 0x00f4200000..0x00f4ffffff -> 0x00f4200000
[    6.298255] rk-pcie fe190000.pcie:      MEM 0x0a00000000..0x0a3fffffff -> 0x0a00000000
[    6.298289] rk-pcie fe190000.pcie: Missing *config* reg space
[    6.298319] rk-pcie fe190000.pcie: invalid resource
[    6.504341] rk-pcie fe190000.pcie: PCIe Linking... LTSSM is 0x2
[    6.529881] rk-pcie fe190000.pcie: PCIe Linking... LTSSM is 0x2
[    6.556554] rk-pcie fe190000.pcie: PCIe Linking... LTSSM is 0x2
[    6.583214] rk-pcie fe190000.pcie: PCIe Linking... LTSSM is 0x2
[    6.609879] rk-pcie fe190000.pcie: PCIe Linking... LTSSM is 0x2
[    6.636549] rk-pcie fe190000.pcie: PCIe Linking... LTSSM is 0x2
[    6.663215] rk-pcie fe190000.pcie: PCIe Linking... LTSSM is 0x2
[    6.689880] rk-pcie fe190000.pcie: PCIe Linking... LTSSM is 0x2
[    6.716548] rk-pcie fe190000.pcie: PCIe Linking... LTSSM is 0x2
[    6.743214] rk-pcie fe190000.pcie: PCIe Linking... LTSSM is 0x2
[    6.980685] ehci-pci: EHCI PCI platform driver
[    7.787429] rockchip-pm-domain fd8d8000.power-management:power-controller: Looking up pcie-supply from device tree
[    7.787466] rockchip-pm-domain fd8d8000.power-management:power-controller: Looking up pcie-supply property in node /power-management@fd8d8000/power-controller failed
[    9.183383] rk-pcie fe190000.pcie: PCIe Link Fail
[    9.183400] rk-pcie fe190000.pcie: failed to initialize host

 

Link to comment
Share on other sites

@royk You say you got HDR working with your instructions, but I seem to not be able to reproduce your result. I built the image from the latest master and renamed the overlay files from rock-5b-* to rk3588-*, but Kodi would still not trigger my TV's HDR mode. I've also renamed them to rockchip-rk3588-* and explicitly added them to overlays in armbianEnv.txt (as my overlay_prefix is rockchip-rk3588, that should work, right?), but that didn't help either. Oddly enough, Kodi doesn't even display that my test files are HDR in its menu, so maybe something is wrong there (I have verified that they are HDR content).

 

Do you know of another way of verifying the HDR support? 

 

I'm also currently investigating HDMI audio passthrough and will report back later if I get it working. I'm hoping Efe's latest changes help here.

 

I've also noticed that the kernel headers produced by the buildscripts does not seem to work for module builds out of the box when cross-compiling because it lacks the scripts/module.lds file for me. That appears to be caused by the cleaning here in packages/armbian/builddeb:

if is_native; then
    # echo "Skip scripts folder cleaning" >&2
    # echo "Skip creating postinst prerm scripts for headers" >&2
    deploy_kernel_headers $kernel_headers_dir
    create_package $kernel_headers_packagename $kernel_headers_dir
else
    # Clean up the executables that are left over from
    # cross-compilation for a different host architecture.
    (
        cd $srctree
        make M=scripts clean
    )
    deploy_kernel_headers $kernel_headers_dir
    create_package $kernel_headers_packagename $kernel_headers_dir "headers"
fi

This used to be prevented by https://github.com/armbian/build/blob/master/patch/misc/general-packaging-5.10.y.patch#L239, I think, but that patch's no longer applied, and instead the custom builddeb is used. @Igor Since this seems to be a regression or an inconsistency between native and cross compilation as far as I can tell, would a PR that adds something similar to that ldstemp mechanism to the new builddeb script be accepted?

Link to comment
Share on other sites

1 hour ago, Marvin Rösch said:

Since this seems to be a regression or an inconsistency between native and cross compilation as far as I can tell, would a PR that adds something similar to that ldstemp mechanism to the new builddeb script be accepted?

 

Fix for packaging mechanism https://github.com/armbian/build/tree/master/packages/armbian won't be accepted as the problem is not there. This has to be solved with a kernel patch. Since this is a private kernel, it doesn't get most of common fixes. I remember lds problem was present some time ago in all kernels, but solution is long gone from my head.

Link to comment
Share on other sites

@Marvin Rösch Are you sure you've got hardware acceleration? When you play a video in Kodi and press o you could see if the hardware of software decoder is in use. AFAIK it only works under gbm (direct login to Kodi Dekstop environment), in Wayland I'm getting a black screen but the the audio does play, in X11 there is no acceleration.

I see I forgot to mention that in Kodi you need to set: Setting --> Player --> Videos:  Allow using DRM decoder - On, Allow hardware acceleration with DRM PRIME - On, Render method - Direct to Plane.

Link to comment
Share on other sites

Finally managed to boot from PCIE M2 SATA(not NVME) without SDcard on orangepi images:

1. Boot from sdcard

2. sudo dd if=/usr/share/orangepi5/rkspi_loader_sata.img of=/dev/mtdblock0 && sudo sync

3. Add

overlays=ssd-sata

to file /boot/orangepiEnv.txt

4. Reboot

5. Now your disk should be detected as sda(not nvme0n1) in fdisk -l, lsblk, etc

6. Copy orangepi image that you used on sdcard to sbc via rsync/scp

7. sudo dd bs=1M if=/path/your/orangepi_linux5.10.110.img of=/dev/sda status=progress && sudo sync

8. Mount /boot/ from new disk:

sudo mount /dev/sda1 /mnt/

9. Add

overlays=ssd-sata

to file /mnt/orangepiEnv.txt

10. sudo umount /mnt/ && sudo sync

11. poweroff

12. remove SDcard and start SBC

 

Now you should boot from your PCIE M2 SATA disk:

orangepi@orangepi5:~$ lsblk 
NAME      MAJ:MIN RM   SIZE RO TYPE MOUNTPOINTS
sda         8:0    0 476.9G  0 disk 
├─sda1      8:1    0   256M  0 part /boot
└─sda2      8:2    0 471.9G  0 part /var/log.hdd
                                    /
mtdblock0  31:0    0    16M  0 disk 
zram0     254:0    0   3.8G  0 disk [SWAP]
zram1     254:1    0   200M  0 disk /var/log
orangepi@orangepi5:~$ fdisk -l
Disk /dev/ram0: 4 MiB, 4194304 bytes, 8192 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes


Disk /dev/zram0: 3.75 GiB, 4031504384 bytes, 984254 sectors
Units: sectors of 1 * 4096 = 4096 bytes
Sector size (logical/physical): 4096 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes


Disk /dev/mtdblock0: 16 MiB, 16777216 bytes, 32768 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: gpt
Disk identifier: C07C704A-CF6D-4888-9D60-DC9506262463

Device           Start   End Sectors  Size Type
/dev/mtdblock0p1    64  7167    7104  3.5M Linux filesystem
/dev/mtdblock0p2  7168  7679     512  256K Linux filesystem
/dev/mtdblock0p3  7680  8063     384  192K Linux filesystem
/dev/mtdblock0p4  8064  8127      64   32K Linux filesystem
/dev/mtdblock0p5  8128  8191      64   32K Linux filesystem
/dev/mtdblock0p6  8192 16383    8192    4M Linux filesystem
/dev/mtdblock0p7 16384 32734   16351    8M Linux filesystem


Disk /dev/sda: 476.94 GiB, 512110190592 bytes, 1000215216 sectors
Disk model: TS512GMTS430S   
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: gpt
Disk identifier: 58FCCC02-859A-5041-ADA7-14802AADF341

Device      Start       End   Sectors   Size Type
/dev/sda1   61440    585727    524288   256M Linux extended boot
/dev/sda2  585728 990183423 989597696 471.9G Linux filesystem


Disk /dev/zram1: 200 MiB, 209715200 bytes, 51200 sectors
Units: sectors of 1 * 4096 = 4096 bytes
Sector size (logical/physical): 4096 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes
orangepi@orangepi5:~$ sudo smartctl -a /dev/sda
smartctl 7.2 2020-12-30 r5155 [aarch64-linux-5.10.110-rockchip-rk3588] (local build)
Copyright (C) 2002-20, Bruce Allen, Christian Franke, www.smartmontools.org

=== START OF INFORMATION SECTION ===
Model Family:     Silicon Motion based SSDs
Device Model:     TS512GMTS430S
Serial Number:    G769530482
LU WWN Device Id: 5 7c3548 1cf19a072
Firmware Version: R0427GN1
User Capacity:    512,110,190,592 bytes [512 GB]
Sector Size:      512 bytes logical/physical
Rotation Rate:    Solid State Device
Form Factor:      M.2
TRIM Command:     Available, deterministic, zeroed
Device is:        In smartctl database [for details use: -P show]
ATA Version is:   ACS-3 T13/2161-D revision 5
SATA Version is:  SATA 3.3, 6.0 Gb/s (current: 6.0 Gb/s)
Local Time is:    Sun Jan  8 15:38:24 2023 CST
SMART support is: Available - device has SMART capability.
SMART support is: Enabled

=== START OF READ SMART DATA SECTION ===
SMART overall-health self-assessment test result: PASSED

General SMART Values:
Offline data collection status:  (0x80)	Offline data collection activity
					was never started.
					Auto Offline Data Collection: Enabled.
Self-test execution status:      (   0)	The previous self-test routine completed
					without error or no self-test has ever 
					been run.
Total time to complete Offline 
data collection: 		(    0) seconds.
Offline data collection
capabilities: 			 (0x7b) SMART execute Offline immediate.
					Auto Offline data collection on/off support.
					Suspend Offline collection upon new
					command.
					Offline surface scan supported.
					Self-test supported.
					Conveyance Self-test supported.
					Selective Self-test supported.
SMART capabilities:            (0x0002)	Does not save SMART data before
					entering power-saving mode.
					Supports SMART auto save timer.
Error logging capability:        (0x01)	Error logging supported.
					General Purpose Logging supported.
Short self-test routine 
recommended polling time: 	 (   2) minutes.
Extended self-test routine
recommended polling time: 	 (  30) minutes.
Conveyance self-test routine
recommended polling time: 	 (   2) minutes.

SMART Attributes Data Structure revision number: 16
Vendor Specific SMART Attributes with Thresholds:
ID# ATTRIBUTE_NAME          FLAG     VALUE WORST THRESH TYPE      UPDATED  WHEN_FAILED RAW_VALUE
  1 Raw_Read_Error_Rate     0x0000   100   100   000    Old_age   Offline      -       0
  5 Reallocated_Sector_Ct   0x0000   100   100   000    Old_age   Offline      -       0
  9 Power_On_Hours          0x0000   100   100   000    Old_age   Offline      -       5
 12 Power_Cycle_Count       0x0000   100   100   000    Old_age   Offline      -       26
148 Total_SLC_Erase_Ct      0x0000   100   100   000    Old_age   Offline      -       7
149 Max_SLC_Erase_Ct        0x0000   100   100   000    Old_age   Offline      -       1
150 Min_SLC_Erase_Ct        0x0000   100   100   000    Old_age   Offline      -       0
151 Average_SLC_Erase_Ct    0x0000   100   100   000    Old_age   Offline      -       0
159 DRAM_1_Bit_Error_Count  0x0000   100   100   000    Old_age   Offline      -       0
160 Uncorrectable_Error_Cnt 0x0000   100   100   000    Old_age   Offline      -       0
161 Valid_Spare_Block_Cnt   0x0000   100   100   000    Old_age   Offline      -       29
163 Initial_Bad_Block_Count 0x0000   100   100   000    Old_age   Offline      -       29
164 Total_Erase_Count       0x0000   100   100   000    Old_age   Offline      -       141
165 Max_Erase_Count         0x0000   100   100   000    Old_age   Offline      -       2
166 Min_Erase_Count         0x0000   100   100   000    Old_age   Offline      -       0
167 Average_Erase_Count     0x0000   100   100   000    Old_age   Offline      -       0
168 Max_Erase_Count_of_Spec 0x0000   100   100   000    Old_age   Offline      -       1000
169 Remaining_Lifetime_Perc 0x0000   100   100   000    Old_age   Offline      -       100
177 Wear_Leveling_Count     0x0000   100   100   050    Old_age   Offline      -       0
181 Program_Fail_Cnt_Total  0x0000   100   100   000    Old_age   Offline      -       0
182 Erase_Fail_Count_Total  0x0000   100   100   000    Old_age   Offline      -       0
192 Power-Off_Retract_Count 0x0000   100   100   000    Old_age   Offline      -       5
194 Temperature_Celsius     0x0000   100   100   000    Old_age   Offline      -       37
195 Hardware_ECC_Recovered  0x0000   100   100   000    Old_age   Offline      -       0
196 Reallocated_Event_Count 0x0000   100   100   016    Old_age   Offline      -       0
199 UDMA_CRC_Error_Count    0x0000   100   100   050    Old_age   Offline      -       0
232 Available_Reservd_Space 0x0000   100   100   000    Old_age   Offline      -       100
241 Host_Writes_32MiB       0x0000   100   100   000    Old_age   Offline      -       1378
242 Host_Reads_32MiB        0x0000   100   100   000    Old_age   Offline      -       197
245 TLC_Writes_32MiB        0x0000   100   100   000    Old_age   Offline      -       5076

SMART Error Log Version: 1
No Errors Logged

SMART Self-test log structure revision number 1
No self-tests have been logged.  [To run self-tests, use: smartctl -t]

SMART Selective self-test log data structure revision number 1
 SPAN  MIN_LBA  MAX_LBA  CURRENT_TEST_STATUS
    1        0        0  Not_testing
    2        0        0  Not_testing
    3        0        0  Not_testing
    4        0        0  Not_testing
    5        0        0  Completed [00% left] (0-65535)
Selective self-test flags (0x0):
  After scanning selected spans, do NOT read-scan remainder of disk.
If Selective self-test is pending on power-up, resume after 0 minute delay.

 

On armbian PCIE M2 SATA SSD doesn't work. @Efe Çetin can you please add this patch https://github.com/armbian/build/issues/4655 ?

Edited by b-baka
Link to comment
Share on other sites

root@orangepi5:~# df -h
Filesystem      Size  Used Avail Use% Mounted on
tmpfs           1.6G   10M  1.6G   1% /run
/dev/sda2        15G  3.0G   12G  21% /
tmpfs           7.7G     0  7.7G   0% /dev/shm
tmpfs           5.0M  4.0K  5.0M   1% /run/lock
tmpfs           7.7G  4.0K  7.7G   1% /tmp
/dev/sda1       256M  153M  104M  60% /boot
/dev/zram1       47M  6.5M   37M  15% /var/log
tmpfs           1.6G   68K  1.6G   1% /run/user/1000
tmpfs           1.6G   36K  1.6G   1% /run/user/0
root@orangepi5:~# fdisk -l | grep "sda"
GPT PMBR size mismatch (31116287 != 60555263) will be corrected by write.
The backup GPT table is not on the end of the device.
Disk /dev/sda: 28.88 GiB, 31004295168 bytes, 60555264 sectors
/dev/sda1   32768   557055   524288  256M Linux extended boot
/dev/sda2  557056 30801920 30244865 14.4G Linux filesystem
root@orangepi5:~# dmesg | grep "sda"
[   18.017284] sd 0:0:0:0: [sda] 60555264 512-byte logical blocks: (31.0 GB/28.9 GiB)
[   18.017693] sd 0:0:0:0: [sda] Write Protect is off
[   18.017704] sd 0:0:0:0: [sda] Mode Sense: 45 00 00 00
[   18.017970] sd 0:0:0:0: [sda] Write cache: disabled, read cache: enabled, doesn't support DPO or FUA
[   18.171956]  sda: sda1 sda2
[   18.173880] sd 0:0:0:0: [sda] Attached SCSI removable disk
[   18.494457] EXT4-fs (sda2): mounted filesystem with writeback data mode. Opts: (null)
[   19.977272] EXT4-fs (sda2): re-mounted. Opts: commit=600,errors=remount-ro
[   20.685924] FAT-fs (sda1): utf8 is not a recommended IO charset for FAT filesystems, filesystem will be case sensitive!
root@orangepi5:~# cat /etc/armbian-release 
# PLEASE DO NOT EDIT THIS FILE
BOARD=orangepi5
BOARD_NAME="Orange Pi 5"
BOARDFAMILY=rockchip-rk3588
BUILD_REPOSITORY_URL=https://github.com/armbian/build.git
BUILD_REPOSITORY_COMMIT=8ce93a2eb-dirty
VERSION=23.02.0-trunk
LINUXFAMILY=rockchip-rk3588
ARCH=arm64
IMAGE_TYPE=user-built
BOARD_TYPE=wip
INITRD_ARCH=arm64
KERNEL_IMAGE_TYPE=Image
BRANCH=legacy
root@orangepi5:~# 

 

 The newly compiled armbian already supports SPI Flash + USB3.0 boot Linux system.

Link to comment
Share on other sites

Tested image Armbian 23.02.0-trunk.0143.

@Efe Çetin SATA SSD works for me after adding following in file "/boot/armbianEnv.txt"

overlays=opi5-sata

 

Not only that, USB cold plug is working well, also asked me for WiFi in initial setup is very convenient.

I'll further test out install SPI+SATA boot

 

Here's my stats:

https://paste.armbian.com/ogifupomir

Overall, a very satisfying build, thanks for the community hard work by making this far 👏 😄.

Edited by Avatar Ng
typo
Link to comment
Share on other sites

On 1/8/2023 at 1:14 AM, royk said:

Render method - Direct to Plane.

Ahhh, thanks a bunch, @royk, I was missing this particular setting, now my TV switches to HDR when I play the right content. I also looked into why that setting is required at all, and it looks like the Rockchip DRM driver does not create any overlay planes that could be used as targets for intermediate HDR rendering.

 

I'm looking into why that might be, because as far as I can tell, the VOP2 driver that gets loaded for the RK3588 should set up at least a few overlay planes (see https://github.com/radxa/kernel/blob/linux-5.10-gen-rkr3.4/drivers/gpu/drm/rockchip/rockchip_vop2_reg.c and the actual implementation in drm_vop2.c). Maybe there's some option in the device tree that still needs to be enabled. There is something about multi area support in the driver source, possibly that is it.

 

I'm still looking into audio passthrough as well. I got the option enabled in Kodi and have enabled passthrough for various formats, but my soundbar still displays that it receives regular stereo LPCM, where it displays e.g. Dolby Digital if I pay something directly from my TV.

Link to comment
Share on other sites

08.01.2023 в 16:10, Efe Çetin сказал:

@b-baka it was already added in https://github.com/armbian/build/commit/b9170c2f22fb00b3334b0bfd984f1af6ffcd4e0b by @danielpinto8zz6 Can you try latest builds?

 

Overlay Name: opi5-sata

Thank you! PCIE M2 SATA work great after adding overlay you mentioned!

 

1 час назад, buvaluy сказал:

Does anybody use aliexpress acrilic case for OP5?  Does it have enought room for ssd at the bottom?

There is also new case https://aliexpress.ru/item/1005005115126370.html

I think it'll have much better temeratures than acrylic.

Link to comment
Share on other sites

MTD-Flash+SATA SSD, still doesn't work out-of-the-box.

 

Steps to reproduce:

Attempt#1

1. sudo armbian-install

2. choose “MTD-Flash+USB/NVME/SATA SSD”

3. Chose /dev/sda2 for root fs I believe

4. Chose “Y” to write bootloader to /dev/mtdblock0

5. sudo poweroff

6. When device really power off,take out the sdcard, reboot by plugging power.

 

reboot fails, yellow led not flashing; only red and blue led (sata ssd’s led)

 

Attempt#2
1. clear out content of MTD flash and SATA SSD using dd

2. Use nand-armbian-install to update MTD Flash only

3. Use balena-etcher to clone sdcard to SATA SSD.

4. sudo poweroff

5. When device really power off,take out the sdcard, reboot by plugging power.

 

reboot fails, yellow led not flashing; only red and blue led (sata ssd’s led)

Link to comment
Share on other sites

@Avatar Ng you should burn https://github.com/orangepi-xunlong/orangepi-build/blob/cf2eec97c417a513d30ca8c65f10ac35f48c07ef/external/packages/bsp/rk3588/usr/share/orangepi5/rkspi_loader_sata.img instead of using armbian-install. I'll make a post about ssd installation guide, soon.

 

@mrkev no i didn't test it due to i don't have CEC drive but i'll check it, thanks

Link to comment
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Guest
Reply to this topic...

×   Pasted as rich text.   Restore formatting

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

Loading...
×
×
  • Create New...

Important Information

Terms of Use - Privacy Policy - Guidelines