Marco Schirrmeister

Still pay attention on how things behave, since all the rk3588 code in 6.x is new. I for example still experience some strange behaviour on the OPi5+ with latest edge kernels, where irq / rtc-hym8563 process uses constantly around 10% cpu. I have not tried to look into it yet, but it is for sure not normal that IRQs are used nonstop like crazy.

I took my OPi5+ apart and inserted the M.2 to SATA to see how it goes with the edge 6.7 image. Works just fine. See below. I did not do anything special, since PCIe3 support is there. It should work with the 5.10 kernel too. If it does not get recognized for you, maybe the adapter is dead. Try it in another system. Kernel info root@falcon ~> uname -a Linux falcon.home.marco.cx 6.7.0-edge-rockchip-rk3588 #1 SMP PREEMPT Sun Jan 7 20:18:38 UTC 2024 aarch64 GNU/Linux M.2 to SATA - ASM1166 root@falcon ~# lspci | grep -i asm 0000:01:00.0 SATA controller: ASMedia Technology Inc. ASM1166 Serial ATA Controller (rev 02) root@falcon ~# lspci -s 0000:01:00.0 -vv | grep -E "(LnkCap:|LnkSta:|Kernel)" LnkCap: Port #0, Speed 8GT/s, Width x2, ASPM L0s L1, Exit Latency L0s <4us, L1 <64us LnkSta: Speed 8GT/s, Width x2 Kernel driver in use: ahci I also did a test with another adapter I had still laying around. M.2 to SATA - JMB585 root@falcon ~# lspci | grep -i jmb 0000:01:00.0 SATA controller: JMicron Technology Corp. JMB58x AHCI SATA controller root@falcon ~# lspci -s 0000:01:00.0 -vv | grep -E "(LnkCap:|LnkSta:|driver)" LnkCap: Port #0, Speed 8GT/s, Width x2, ASPM not supported LnkSta: Speed 8GT/s, Width x2 Kernel driver in use: ahci And here is what my production setup looks like. M.2 to PCIe - PCIe to M.2x2 (ASM2812) - M.2 to SATA ASM1166 root@falcon ~# lspci | grep -i asm 0000:01:00.0 PCI bridge: ASMedia Technology Inc. Device 2812 (rev 01) 0000:02:00.0 PCI bridge: ASMedia Technology Inc. Device 2812 (rev 01) 0000:02:08.0 PCI bridge: ASMedia Technology Inc. Device 2812 (rev 01) 0000:03:00.0 SATA controller: ASMedia Technology Inc. ASM1166 Serial ATA Controller (rev 02) root@falcon ~# lspci -s 0000:02:00.0 -vv | grep -E "(LnkCap:|LnkSta:|driver)" LnkCap: Port #0, Speed 8GT/s, Width x4, ASPM L0s L1, Exit Latency L0s <4us, L1 <64us LnkSta: Speed 8GT/s, Width x2 Kernel driver in use: pcieport root@falcon ~# lspci -s 0000:03:00.0 -vv | grep -E "(LnkCap:|LnkSta:|driver)" LnkCap: Port #0, Speed 8GT/s, Width x2, ASPM L0s L1, Exit Latency L0s <4us, L1 <64us LnkSta: Speed 8GT/s, Width x2 Kernel driver in use: ahci Which are basically this 3 products. https://www.amazon.de/gp/product/B07YDH8KW9 https://de.aliexpress.com/item/1005003908630199.html https://www.amazon.de/gp/product/B0B6RQHY4F

I have no idea what this rk3588-sata2 overlay is supposed to do. But I don't think you need it. For you adapter, I guess you have one of this M.2 to sata adapters like this? https://www.amazon.de/gp/product/B0B6RQHY4F I am pretty sure I tried to use this adapter directly some time ago and it was visible too. But that was the classic Orange Pi 5. In lspci, you should see something like this. 05:00.0 SATA controller: ASMedia Technology Inc. ASM1166 Serial ATA Controller (rev 02) Try to load the edge kernel 6.7 image. That one has received a lot of hardware support for the rk3588. All what it needs is the ahci driver. I do something similar on my OPi5+. I have a M.2 to PCIe riser card. In there is a pcie switch card with a ASM2812 chip. This card has 2 M.2 slots. In there are M.2 to SATA3 adapters with an ASM1166 chip (each 6 ports).

If you used the 6.7.0-rc7 image, then check what overlay and dt file you have configured. This image defaults to the dt file for the original non-plus version. Check and adjust in /boot/armbianEnv.txt the following 2 lines. overlay_prefix=rockchip-rk3588 fdtfile=rockchip/rk3588-orangepi-5-plus.dtb

@Endian, yes bootsize=512 creates a bigger boot partition. The old default is to small when you run an upgrade. It typically runs out of disk space when you do kernel upgrades. Thats why I made it bigger on my test builds.

Without knowing what you did exactly, the following creates a bootable image. ./compile.sh BOARD=rock-5b BRANCH=collabora RELEASE=bookworm KERNEL_CONFIGURE=no BUILD_MINIMAL=no BUILD_DESKTOP=no COMPRESS_OUTPUTIMAGE=img BOOTSIZE=512 You may also need to clear whatever is in your SPI flash.

Getting a ethernet cable is the easiest thing for the initial setup. Otherwise you can use a serial connection and do the first boot setup via serial. Armbian images are not like the Raspian images, where you have a fat partition, that you can easily mount and store some files on it. You could of course do some hacky stuff like mounting the boot or root partition from the img file and pre-configure some stuff, if you know what to do. It will definitely not as easy as just creating an empty file.

I love the Collabora kernel. Finally PCIe 3.0 support. Have a PCIe card connected via a M.2 to PCIe riser adapter. 😎 marco@loop ~> ssh -l pi 192.168.2.212 ____ _ ____ ____ | _ \ ___ ___| | __ | ___|| __ ) | |_) / _ \ / __| |/ / |___ \| _ \ | _ < (_) | (__| < ___) | |_) | |_| \_\___/ \___|_|\_\ |____/|____/ Welcome to Armbian 23.08.0-trunk Bookworm with Linux 6.5.0-rc1-rockchip-rk3588 No end-user support: built from trunk System load: 1% Up time: 8 min Memory usage: 2% of 7.76G IP: 192.168.2.212 Usage of /: 9% of 29G RX today: 12.4 MiB root@rock-5b ~# neofetch root@rock-5b ------------ █ █ █ █ █ █ █ █ █ █ █ OS: Armbian (23.08.0-trunk) aarch64 ███████████████████████ Host: Radxa ROCK 5 Model B ▄▄██ ██▄▄ Kernel: 6.5.0-rc1-rockchip-rk3588 ▄▄██ ███████████ ██▄▄ Uptime: 1 min ▄▄██ ██ ██ ██▄▄ Packages: 538 (dpkg) ▄▄██ ██ ██ ██▄▄ Shell: fish 3.6.0 ▄▄██ ██ ██ ██▄▄ Terminal: /dev/pts/0 ▄▄██ █████████████ ██▄▄ CPU: (8) ▄▄██ ██ ██ ██▄▄ Memory: 178MiB / 7944MiB ▄▄██ ██ ██ ██▄▄ ▄▄██ ██ ██ ██▄▄ ▄▄██ ██▄▄ ███████████████████████ █ █ █ █ █ █ █ █ █ █ █ root@rock-5b ~# lspci 0000:00:00.0 PCI bridge: Rockchip Electronics Co., Ltd RK3588 (rev 01) 0000:01:00.0 PCI bridge: ASMedia Technology Inc. Device 2812 (rev 01) 0000:02:00.0 PCI bridge: ASMedia Technology Inc. Device 2812 (rev 01) 0000:02:08.0 PCI bridge: ASMedia Technology Inc. Device 2812 (rev 01) 0000:03:00.0 SATA controller: JMicron Technology Corp. JMB58x AHCI SATA controller 0004:40:00.0 PCI bridge: Rockchip Electronics Co., Ltd RK3588 (rev 01) 0004:41:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8125 2.5GbE Controller (rev 05) root@rock-5b ~# lspci -s 01:00.0 -vv | grep -E "(LnkCap:|LnkSta:)" LnkCap: Port #0, Speed 8GT/s, Width x8, ASPM L0s L1, Exit Latency L0s <4us, L1 <64us LnkSta: Speed 8GT/s, Width x4 (downgraded) root@rock-5b ~# lspci -s 02:00.0 -vv | grep -E "(LnkCap:|LnkSta:)" LnkCap: Port #0, Speed 8GT/s, Width x4, ASPM L0s L1, Exit Latency L0s <4us, L1 <64us LnkSta: Speed 8GT/s, Width x2 root@rock-5b ~# lspci -s 02:08.0 -vv | grep -E "(LnkCap:|LnkSta:)" LnkCap: Port #8, Speed 8GT/s, Width x4, ASPM L0s L1, Exit Latency L0s <4us, L1 <64us LnkSta: Speed 2.5GT/s, Width x1 root@rock-5b ~# lspci -s 03:00.0 -vv | grep -E "(LnkCap:|LnkSta:)" LnkCap: Port #0, Speed 8GT/s, Width x2, ASPM not supported LnkSta: Speed 8GT/s, Width x2 root@rock-5b ~# lsblk -f -d -o NAME,MAJ:MIN,RM,HOTPLUG,MODEL,SIZE,ROTA,TYPE,TRAN,SUBSYSTEMS,VENDOR | grep -E '(^sd.+)' sda 8:0 0 0 ST2000DM008-2FR102 1.8T 1 disk sata block:scsi:pci:platform ATA sdb 8:16 0 0 ST2000DM008-2FR102 1.8T 1 disk sata block:scsi:pci:platform ATA sdc 8:32 0 0 ST2000DM008-2FR102 1.8T 1 disk sata block:scsi:pci:platform ATA Next step is, ordering a card with an ASM2824 chip and attaching 4 M.2 ASM1166 cards. The Rock 5B is getting closer to be NAS ready.

Looks like you use an image from balbes150. You may want to ask in this thread here, which is about his images. But before asking, read the important comments a few times.

Rene, with an installation of the official image like Bullseye with the 5.10 kernel, it should work. Maybe you did some modifications? If so, try it with a fresh installation. Without any changes I can see "ttyS6". After enabling all uart in armbian-config, I can see more after a reboot. root@rock-5b ~# ls -la /dev/ttyS* crw--w---- 1 root tty 4, 66 May 24 08:55 /dev/ttyS2 crw-rw---- 1 root dialout 4, 67 May 24 08:55 /dev/ttyS3 crw-rw---- 1 root dialout 4, 68 May 24 08:55 /dev/ttyS4 crw-rw---- 1 root dialout 4, 70 May 24 08:55 /dev/ttyS6 crw-rw---- 1 root dialout 4, 71 May 24 08:55 /dev/ttyS7 In the images from balbes150, with some 6.x kernel, I think you can see more ttyS by default.

Same or similar was asked here. You will probably not get a good answer. Be prepared for some harsh words. 😉 My experience from the past is, that this images work sometimes and sometimes not. Even if words like "stable" are mentioned in the rolling release section, don't count on it. I have seen this error in the past as well, when I tried for fun one of the nightly images, but my troubleshooting did not get my anywhere. Only thing I remember is that the UUID that was mentioned was at least correct in terms that it was in the fstab and armbianEnv.txt. It might have something to do with the SPI and what is in there. Maybe also not, who knows.

Could not resolve 'ports.ubuntu.com' Looks like a DNS problem. Maybe only something temporary in your network?

@Kenneth Ekman, how did you build the image? If you build like this as an example, does it work? Not sure if this pulls in all the latest and greatest packages. ./compile.sh BOARD=rock-5b BRANCH=midstream RELEASE=lunar COMPRESS_OUTPUTIMAGE=img KERNEL_CONFIGURE=no BUILD_MINIMAL=no BUILD_DESKTOP=no

Nice work! 👏 My M.2 SATA controller is also recognized. 😍 root@baldeagle ~# neofetch root@baldeagle ---------------------------- █ █ █ █ █ █ █ █ █ █ █ OS: Armbian (20230310b-rpardini) aarch64 ███████████████████████ Host: Radxa ROCK 5 Model B ▄▄██ ██▄▄ Kernel: 6.2.0-rc1-rockchip-rk3588 ▄▄██ ███████████ ██▄▄ Uptime: 1 min ▄▄██ ██ ██ ██▄▄ Packages: 638 (dpkg) ▄▄██ ██ ██ ██▄▄ Shell: fish 3.5.1 ▄▄██ ██ ██ ██▄▄ Terminal: /dev/ttyS2 ▄▄██ █████████████ ██▄▄ CPU: (8) @ 1.800GHz ▄▄██ ██ ██ ██▄▄ Memory: 151MiB / 7693MiB ▄▄██ ██ ██ ██▄▄ ▄▄██ ██ ██ ██▄▄ ▄▄██ ██▄▄ ███████████████████████ █ █ █ █ █ █ █ █ █ █ █ root@baldeagle ~# lspci 0000:00:00.0 PCI bridge: Rockchip Electronics Co., Ltd Device 3588 (rev 01) 0000:01:00.0 SATA controller: JMicron Technology Corp. JMB58x AHCI SATA controller 0002:20:00.0 PCI bridge: Rockchip Electronics Co., Ltd Device 3588 (rev 01) 0004:40:00.0 PCI bridge: Rockchip Electronics Co., Ltd Device 3588 (rev 01) 0004:41:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8125 2.5GbE Controller (rev 05) Looks like the `/boot` partition needs to be increased. `update-initramfs` fails due to not enough space.

For Odroid yes. I have it as well running fine on a HC4. But this thread is about Rock 5 and I see problems on the Rock5 (rk3588). Thats why I wanted to check if there is a list of known issues or limitations, before going to deep into the weeds.

Is there a list with limitations even there are now supported images available for the Rock 5? ZFS from the Armbian repo is not working on the Jammy images.

Confirmed. Issue still present in 23.02 release. root@sperber ~ [100]# cat /var/lib/dkms/zfs/2.1.6/build/build/build.log make: Entering directory '/usr/src/linux-headers-5.10.110-rockchip-rk3588' arch/arm64/Makefile:44: Detected assembler with broken .inst; disassembly will be unreliable /usr/bin/env: 'python2': No such file or directory MODPOST /var/lib/dkms/zfs/2.1.6/build/build/Module.symvers /bin/sh: 1: scripts/mod/modpost: not found make[1]: *** [scripts/Makefile.modpost:169: /var/lib/dkms/zfs/2.1.6/build/build/Module.symvers] Error 127 make[1]: Target '__modpost' not remade because of errors. make: *** [Makefile:1822: modules] Error 2 make: Leaving directory '/usr/src/linux-headers-5.10.110-rockchip-rk3588'

Maybe it also depends on the features or tools you want to use. I want to build a ZFS NAS and Armbian has newer ZFS packages for Jammy. But it does not work on the Orange Pi 5 yet. Hope sooner than later the OPi5 is fully supported and ZFS works.

@grablife You are right, I should have mentioned a few more things on what this is based on. sudo/root, yes, since all of this is very low level stuff, I typically switch to root and run all commands instead of sudo'ing each command The "set UUID" command has a syntax for the "fish" shell. For bash you figured out the correct syntax. 🙂

Thanks for the information where the packages come from. For now I am testing with Debian and I have the zfs package preferred in the apt preferences to pull in a newer version. Which is right now 2.1.7. Will see how all goes and I maybe also give the Armbian Jammy repo a try.

Hello, I have a question for the Armbian UEFI for x86. On the main page https://www.armbian.com/uefi-x86/ it mentions ZFS 2.1.5 ready. When I compare Bullseye and Jammy repos, I only see 2.1+ packages in the Jammy Armbian repo. The Bullseye repo has 2.0.x packages. I saw differences for other packages as well between the distros/repos. Based on the "classic" differences between Bullseye and Jammy, I picked for a server typically Debian. If Jammy is more often updated for Armbian, I guess I have to choose Jammy. Is there anything you can say about which one is "better" or preferred over the other from the available options?

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