smurfx Posted April 12 Posted April 12 Armbianmonitor: https://paste.armbian.com/nubeniduko Hi everyone, I just installed Armbian on my OrangePi 5, but I can't get it to recognize the NVMe drive. I've tried the official OrangePi Ubuntu distro, and it detects the NVMe without any issues. However, when using Armbian, it simply doesn't show up. I'm not sure what to do at this point. I would really like to use Armbian, but it seems unable to detect the NVMe on this particular device. Interestingly, I have another OrangePi 5 Pro where I installed Armbian, and it recognizes the NVMe and works perfectly fine — but not on the standard OrangePi 5. Does anyone know how to fix this issue, or can you recommend a good alternative? Quote root@orangepi5:~# lsblk NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINTS mtdblock0 31:0 0 16M 0 disk mmcblk0 179:0 0 238.8G 0 disk └─mmcblk0p1 179:1 0 236.3G 0 part /var/log.hdd / zram0 252:0 0 7.8G 0 disk [SWAP] zram1 252:1 0 50M 0 disk /var/log zram2 252:2 0 0B 0 disk Thank you in advance. 0 Quote
eselarm Posted April 12 Posted April 12 (edited) 43 minutes ago, smurfx said: https://paste.armbian.com/nubeniduko Log shows nothing about PCIE when 6.19.0-edge-rockchip64, it does when 6.18.8-current-rockchip64 If you just upgraded the kernel via apt, then this might be the point where an older U-Boot is incompatible with newer kernel. This is the case for all Rockchip devices I have and not strange. It is like it is, so if you want edge or newest or even standard Debian sid/unstable/testing kernel, you will need to look at that in more detail. I have been spending a lot of time on it, it is simply what you want or need. If you want all RK3588 silicon HW support, so like video encoders, stick to vendor based U-Boot and kernel. I you want a generic computer that is good enough for server tasks and web-browsing etc, use mainline based U-Boot and kernel. Of course something else might be wrong, but reporting U-Boot version would be needed and helpful first I think. Edited April 12 by eselarm 0 Quote
smurfx Posted April 12 Author Posted April 12 Hey @eselarm, Thanks for the quick answer. My goal is indeed having a more generic computer for server tasks. The version of the u-boot is: Quote root@orangepi5:~# dpkg -l | grep u-boot ii linux-u-boot-orangepi5-current 26.2.1 arm64 Das U-Boot for orangepi5 ii u-boot-tools 2025.10-0ubuntu0.24.04.2 arm64 companion tools for Das U-Boot bootloader root@orangepi5:~# uname -a Linux orangepi5 6.18.10-current-rockchip64 #2 SMP PREEMPT Wed Feb 11 12:42:01 UTC 2026 aarch64 aarch64 aarch64 GNU/Linux I have switched again to the orangepi5 6.18.10-current-rockchip64 kernel but still not showing nothing. Thank you. 0 Quote
eselarm Posted April 12 Posted April 12 (edited) 10 minutes ago, smurfx said: linux-u-boot-orangepi5-current 26.2.1 You need the U-Boot source-code version; I at least cannot conclude on it; You can watch the start-up via serial console, then you will see. Or like this: root@rock3a:~# strings /dev/mtdblock0 | grep "U-Boot SPL 20" U-Boot SPL 2017.09-armbian (May 20 2024 - 00:46:51) I see you have 2 options: which U-Boot is used: mtdblock0 (the SPI-flash) or mmcblk0 (SD-card) ?? Edited April 12 by eselarm 0 Quote
smurfx Posted April 12 Author Posted April 12 Strangely I can't get any outcome from that command: Quote root@orangepi5:~# lsblk NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINTS mtdblock0 31:0 0 16M 0 disk mmcblk0 179:0 0 238.8G 0 disk └─mmcblk0p1 179:1 0 236.3G 0 part /var/log.hdd / zram0 252:0 0 7.8G 0 disk [SWAP] zram1 252:1 0 50M 0 disk /var/log zram2 252:2 0 0B 0 disk root@orangepi5:~# strings /dev/mtdblock0 | grep "U-Boot SPL 20" root@orangepi5:~# strings /dev/mtdblock0 | grep "U-Boot" root@orangepi5:~# strings /dev/mtdblock0 root@orangepi5:~# grep -a --null-data "U-Boot" /dev/mtdblock0 root@orangepi5:~# Now I am confused if there is something else going on, however, the OrangePi official distro recognised the nvme disk. 0 Quote
smurfx Posted April 12 Author Posted April 12 (edited) The only thing I could manage to get information from was this: Quote root@orangepi5:~# dd if=/dev/mmcblk0 bs=1M count=4 2>/dev/null | strings | grep -i "u-boot" | head -1 u-boot,spl-boot-order I had to rewrite the SPI-flash and now I see: Quote root@orangepi5:~# strings /dev/mtdblock0 | grep "U-Boot SPL 20" U-Boot SPL 2025.10_armbian-2025.10-Se50b-P4b2d-Hd43a-Va0a8-B2eb2-R448a (Feb 01 2026 - 04:51:01 +0000) Not sure if this helps: Quote root@orangepi5:~# dmesg | grep -i pcie [ 9.222778] Kernel command line: root=UUID=5aa117ab-65bd-413a-8ccf-15e93e9db998 rootwait rootfstype=ext4 splash=verbose console=ttyS2,1500000 console=tty1 consoleblank=0 loglevel=1 ubootpart=45beaa53-1a56-470d-b2fc-0279821b1186 usb-storage.quirks=0x2537:0x1066:u,0x2537:0x1068:u cma=256M pcie_aspm=off rockchip_pcie.gen=2 cgroup_enable=cpuset cgroup_memory=1 cgroup_enable=memory [ 9.223332] PCIe ASPM is disabled [ 10.515063] reg-fixed-voltage vcc3v3-pcie2x1l2: Looking up vin-supply from device tree [ 10.515072] vcc3v3_pcie2x1l2: supplied by vcc5v0_sys [ 10.572635] vcc3v3_pcie2x1l2: 1800 mV, enabled [ 10.572742] reg-fixed-voltage vcc3v3-pcie2x1l2: vcc3v3_pcie2x1l2 supplying 1800000uV [ 11.120278] dw-pcie fe190000.pcie: invalid resource [ 11.120285] dw-pcie fe190000.pcie: Failed to initialize host [ 11.120289] dw-pcie: probe of fe190000.pcie failed with error -22 [ 11.121218] rk-pcie fe190000.pcie: invalid prsnt-gpios property in node [ 11.121349] rk-pcie fe190000.pcie: Looking up vpcie3v3-supply from device tree [ 11.122057] rk-pcie fe190000.pcie: can't get current limit. [ 11.122504] rk-pcie fe190000.pcie: host bridge /pcie@fe190000 ranges: [ 11.122546] rk-pcie fe190000.pcie: IO 0x00f4100000..0x00f41fffff -> 0x00f4100000 [ 11.122577] rk-pcie fe190000.pcie: MEM 0x00f4200000..0x00f4ffffff -> 0x00f4200000 [ 11.122599] rk-pcie fe190000.pcie: MEM 0x0a00000000..0x0a3fffffff -> 0x0a00000000 [ 11.122673] rk-pcie fe190000.pcie: iATU unroll: enabled [ 11.122685] rk-pcie fe190000.pcie: iATU regions: 8 ob, 8 ib, align 64K, limit 8G [ 11.324904] rk-pcie fe190000.pcie: PCIe Linking... LTSSM is 0x3 [ 11.345949] rk-pcie fe190000.pcie: PCIe Linking... LTSSM is 0x3 [ 11.366990] rk-pcie fe190000.pcie: PCIe Linking... LTSSM is 0x3 [ 11.387231] rk-pcie fe190000.pcie: PCIe Linking... LTSSM is 0x3 [ 11.408275] rk-pcie fe190000.pcie: PCIe Linking... LTSSM is 0x3 [ 11.429315] rk-pcie fe190000.pcie: PCIe Linking... LTSSM is 0x3 [ 11.450353] rk-pcie fe190000.pcie: PCIe Linking... LTSSM is 0x3 [ 11.471391] rk-pcie fe190000.pcie: PCIe Linking... LTSSM is 0x3 [ 11.492456] rk-pcie fe190000.pcie: PCIe Linking... LTSSM is 0x3 [ 11.513615] rk-pcie fe190000.pcie: PCIe Linking... LTSSM is 0x3 [ 11.816067] rockchip-pm-domain fd8d8000.power-management:power-controller: Looking up pcie-supply from device tree [ 11.816097] rockchip-pm-domain fd8d8000.power-management:power-controller: Looking up pcie-supply property in node /power-management@fd8d8000/power-controller failed [ 13.414988] rk-pcie fe190000.pcie: PCIe Link Fail, LTSSM is 0x3, hw_retries=0 [ 16.337226] rk_pcie_establish_link: 172 callbacks suppressed [ 16.337248] rk-pcie fe190000.pcie: PCIe Linking... LTSSM is 0x3 [ 16.358361] rk-pcie fe190000.pcie: PCIe Linking... LTSSM is 0x3 [ 16.379485] rk-pcie fe190000.pcie: PCIe Linking... LTSSM is 0x3 [ 16.400585] rk-pcie fe190000.pcie: PCIe Linking... LTSSM is 0x3 [ 16.421665] rk-pcie fe190000.pcie: PCIe Linking... LTSSM is 0x3 [ 16.442698] rk-pcie fe190000.pcie: PCIe Linking... LTSSM is 0x3 [ 16.463746] rk-pcie fe190000.pcie: PCIe Linking... LTSSM is 0x3 [ 16.484909] rk-pcie fe190000.pcie: PCIe Linking... LTSSM is 0x3 [ 16.506075] rk-pcie fe190000.pcie: PCIe Linking... LTSSM is 0x3 [ 16.527263] rk-pcie fe190000.pcie: PCIe Linking... LTSSM is 0x3 [ 16.716995] rk-pcie fe190000.pcie: PCIe Link Fail, LTSSM is 0x3, hw_retries=1 [ 17.727355] rk-pcie fe190000.pcie: failed to initialize host Btw, this is the output when I was using the official OrangePI Ubuntu distro: Quote ubuntu@ubuntu:~$ lsblk NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINTS loop0 7:0 0 69.2M 1 loop /snap/core22/1624 loop1 7:1 0 94.4M 1 loop /snap/lxd/30134 loop2 7:2 0 33.7M 1 loop /snap/snapd/21761 loop3 7:3 0 41.8M 1 loop /snap/snapd/26383 sda 8:0 0 1.8T 0 disk └─sda1 8:1 0 1.8T 0 part mmcblk1 179:0 0 238.8G 0 disk ├─mmcblk1p1 179:1 0 4M 0 part └─mmcblk1p2 179:2 0 238.7G 0 part / nvme0n1 259:0 0 238.5G 0 disk Edited April 13 by smurfx 0 Quote
thanh_tan Posted June 19 Posted June 19 (edited) I have same problem, even had rewrite the SPI boot admin@orangepi5:~$ strings /dev/mtdblock0 | grep "U-Boot SPL 20" U-Boot SPL 2026.04_armbian-2026.04-S88dc-P3cfe-H95ba-V7a4e-Bd0d2-R448a (Jun 11 2026 - 06:18:28 +0000) reboot but it doesn't show the nvme disk admin@orangepi5:~$ lsblk NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINTS mtdblock0 31:0 0 16M 0 disk mmcblk0 179:0 0 29.7G 0 disk └─mmcblk0p1 179:1 0 29.4G 0 part /var/log.hdd / zram0 252:0 0 1.9G 0 disk [SWAP] zram1 252:1 0 50M 0 disk /var/log zram2 252:2 0 0B 0 disk I am using v26.5.1 for Orange Pi 5 running Armbian Linux 6.18.8-current-rockchip64 Ubuntu stable (noble) Edited June 19 by thanh_tan 0 Quote
eselarm Posted June 19 Posted June 19 Providing logs with armbianmonitor -u helps with troubleshooting and significantly raises chances that issue gets addressed. and/or lspci output it might also be a power issue or just that you specific nvme does not work with non-vndor kernel also kernel is already at 6.18.35 for current rockchip, maybe see if that fixes something w,r,t, yiour nvme 0 Quote
MAXIM ALEKSEEV Posted 1 hour ago Posted 1 hour ago (edited) orange pi 5 ultra Orange Pi 1.0.0 Jammy with Linux 5.10.160-rockchip-rk3588 NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINTS mtdblock0 31:0 0 16M 0 disk mmcblk0 179:0 0 58.2G 0 disk ├─mmcblk0p1 179:1 0 1G 0 part /boot └─mmcblk0p2 179:2 0 56.6G 0 part /var/log.hdd / zram0 254:0 0 3.9G 0 disk [SWAP] zram1 254:1 0 200M 0 disk /var/log [Thu Jul 9 13:41:39 2026] rk-pcie fe150000.pcie: PCIe Link Fail [Thu Jul 9 13:41:39 2026] rk-pcie fe150000.pcie: failed to initialize host Edited 1 hour ago by MAXIM ALEKSEEV 0 Quote
MAXIM ALEKSEEV Posted 1 hour ago Posted 1 hour ago orangepi@orangepi5ultra:~$ dmesg -T | grep -Ei 'pcie|nvme|ltssm|link fail|fe150000' lspci -nn lsblk [Thu Jul 9 14:07:43 2026] vcc3v3_pcie30: 3300 mV, disabled [Thu Jul 9 14:07:43 2026] reg-fixed-voltage vcc3v3-pcie30: Looking up vin-supply from device tree [Thu Jul 9 14:07:43 2026] vcc3v3_pcie30: supplied by vcc5v0_sys [Thu Jul 9 14:07:43 2026] reg-fixed-voltage vcc3v3-pcie30: vcc3v3_pcie30 supplying 3300000uV [Thu Jul 9 14:07:43 2026] vcc3v3_pcie2x1l0: 3300 mV, enabled [Thu Jul 9 14:07:43 2026] reg-fixed-voltage vcc3v3-pcie2x1l0: Looking up vin-supply from device tree [Thu Jul 9 14:07:43 2026] vcc3v3_pcie2x1l0: supplied by vcc12v_dcin [Thu Jul 9 14:07:43 2026] reg-fixed-voltage vcc3v3-pcie2x1l0: vcc3v3_pcie2x1l0 supplying 3300000uV [Thu Jul 9 14:07:43 2026] reg-fixed-voltage vcc3v3-pcie-eth: Looking up vin-supply from device tree [Thu Jul 9 14:07:43 2026] vcc3v3_pcie_eth: supplied by vcc12v_dcin [Thu Jul 9 14:07:43 2026] vcc3v3_pcie_eth: 3300 mV, enabled [Thu Jul 9 14:07:43 2026] reg-fixed-voltage vcc3v3-pcie-eth: vcc3v3_pcie_eth supplying 3300000uV [Thu Jul 9 14:07:44 2026] rk-pcie fe180000.pcie: invalid prsnt-gpios property in node [Thu Jul 9 14:07:44 2026] rk-pcie fe190000.pcie: invalid prsnt-gpios property in node [Thu Jul 9 14:07:44 2026] rk-pcie fe190000.pcie: Looking up vpcie3v3-supply from device tree [Thu Jul 9 14:07:44 2026] rk-pcie fe180000.pcie: Looking up vpcie3v3-supply from device tree [Thu Jul 9 14:07:44 2026] rk-pcie fe190000.pcie: Looking up vpcie3v3-supply property in node /pcie@fe190000 failed [Thu Jul 9 14:07:44 2026] rk-pcie fe180000.pcie: Looking up vpcie3v3-supply property in node /pcie@fe180000 failed [Thu Jul 9 14:07:44 2026] rk-pcie fe190000.pcie: no vpcie3v3 regulator found [Thu Jul 9 14:07:44 2026] rk-pcie fe180000.pcie: no vpcie3v3 regulator found [Thu Jul 9 14:07:44 2026] rk-pcie fe150000.pcie: invalid prsnt-gpios property in node [Thu Jul 9 14:07:44 2026] rk-pcie fe150000.pcie: Looking up vpcie3v3-supply from device tree [Thu Jul 9 14:07:44 2026] rk-pcie fe190000.pcie: IRQ msi not found [Thu Jul 9 14:07:44 2026] rk-pcie fe190000.pcie: use outband MSI support [Thu Jul 9 14:07:44 2026] rk-pcie fe190000.pcie: Missing *config* reg space [Thu Jul 9 14:07:44 2026] rk-pcie fe190000.pcie: host bridge /pcie@fe190000 ranges: [Thu Jul 9 14:07:44 2026] rk-pcie fe190000.pcie: err 0x00f4000000..0x00f40fffff -> 0x00f4000000 [Thu Jul 9 14:07:44 2026] rk-pcie fe190000.pcie: IO 0x00f4100000..0x00f41fffff -> 0x00f4100000 [Thu Jul 9 14:07:44 2026] rk-pcie fe190000.pcie: MEM 0x00f4200000..0x00f4ffffff -> 0x00f4200000 [Thu Jul 9 14:07:44 2026] rk-pcie fe190000.pcie: MEM 0x0a00000000..0x0a3fffffff -> 0x0a00000000 [Thu Jul 9 14:07:44 2026] rk-pcie fe190000.pcie: Missing *config* reg space [Thu Jul 9 14:07:44 2026] rk-pcie fe170000.pcie: invalid prsnt-gpios property in node [Thu Jul 9 14:07:44 2026] rk-pcie fe190000.pcie: invalid resource [Thu Jul 9 14:07:44 2026] rk-pcie fe170000.pcie: Looking up vpcie3v3-supply from device tree [Thu Jul 9 14:07:44 2026] rk-pcie fe180000.pcie: IRQ msi not found [Thu Jul 9 14:07:44 2026] rk-pcie fe180000.pcie: use outband MSI support [Thu Jul 9 14:07:44 2026] rk-pcie fe180000.pcie: Missing *config* reg space [Thu Jul 9 14:07:44 2026] rk-pcie fe180000.pcie: host bridge /pcie@fe180000 ranges: [Thu Jul 9 14:07:44 2026] rk-pcie fe180000.pcie: err 0x00f3000000..0x00f30fffff -> 0x00f3000000 [Thu Jul 9 14:07:44 2026] rk-pcie fe180000.pcie: IO 0x00f3100000..0x00f31fffff -> 0x00f3100000 [Thu Jul 9 14:07:44 2026] rk-pcie fe180000.pcie: MEM 0x00f3200000..0x00f3ffffff -> 0x00f3200000 [Thu Jul 9 14:07:44 2026] rk-pcie fe180000.pcie: MEM 0x09c0000000..0x09ffffffff -> 0x09c0000000 [Thu Jul 9 14:07:44 2026] rk-pcie fe180000.pcie: Missing *config* reg space [Thu Jul 9 14:07:44 2026] rk-pcie fe180000.pcie: invalid resource [Thu Jul 9 14:07:44 2026] rk-pcie fe170000.pcie: IRQ msi not found [Thu Jul 9 14:07:44 2026] rk-pcie fe170000.pcie: use outband MSI support [Thu Jul 9 14:07:44 2026] rk-pcie fe170000.pcie: Missing *config* reg space [Thu Jul 9 14:07:44 2026] rk-pcie fe170000.pcie: host bridge /pcie@fe170000 ranges: [Thu Jul 9 14:07:44 2026] rk-pcie fe170000.pcie: err 0x00f2000000..0x00f20fffff -> 0x00f2000000 [Thu Jul 9 14:07:44 2026] rk-pcie fe170000.pcie: IO 0x00f2100000..0x00f21fffff -> 0x00f2100000 [Thu Jul 9 14:07:44 2026] rk-pcie fe170000.pcie: MEM 0x00f2200000..0x00f2ffffff -> 0x00f2200000 [Thu Jul 9 14:07:44 2026] rk-pcie fe170000.pcie: MEM 0x0980000000..0x09bfffffff -> 0x0980000000 [Thu Jul 9 14:07:44 2026] rk-pcie fe170000.pcie: Missing *config* reg space [Thu Jul 9 14:07:44 2026] rk-pcie fe170000.pcie: invalid resource [Thu Jul 9 14:07:44 2026] rk-pcie fe150000.pcie: IRQ msi not found [Thu Jul 9 14:07:44 2026] rk-pcie fe150000.pcie: use outband MSI support [Thu Jul 9 14:07:44 2026] rk-pcie fe150000.pcie: Missing *config* reg space [Thu Jul 9 14:07:44 2026] rk-pcie fe150000.pcie: host bridge /pcie@fe150000 ranges: [Thu Jul 9 14:07:44 2026] rk-pcie fe150000.pcie: err 0x00f0000000..0x00f00fffff -> 0x00f0000000 [Thu Jul 9 14:07:44 2026] rk-pcie fe150000.pcie: IO 0x00f0100000..0x00f01fffff -> 0x00f0100000 [Thu Jul 9 14:07:44 2026] rk-pcie fe150000.pcie: MEM 0x00f0200000..0x00f0ffffff -> 0x00f0200000 [Thu Jul 9 14:07:44 2026] rk-pcie fe150000.pcie: MEM 0x0900000000..0x093fffffff -> 0x0900000000 [Thu Jul 9 14:07:44 2026] rk-pcie fe150000.pcie: Missing *config* reg space [Thu Jul 9 14:07:44 2026] rk-pcie fe150000.pcie: invalid resource [Thu Jul 9 14:07:44 2026] rk-pcie fe190000.pcie: PCIe Linking... LTSSM is 0x3 [Thu Jul 9 14:07:44 2026] rk-pcie fe180000.pcie: PCIe Linking... LTSSM is 0x3 [Thu Jul 9 14:07:44 2026] rk-pcie fe170000.pcie: PCIe Linking... LTSSM is 0x3 [Thu Jul 9 14:07:44 2026] rk-pcie fe150000.pcie: PCIe Linking... LTSSM is 0x0 [Thu Jul 9 14:07:44 2026] rk-pcie fe190000.pcie: PCIe Linking... LTSSM is 0x3 [Thu Jul 9 14:07:44 2026] rk-pcie fe170000.pcie: PCIe Linking... LTSSM is 0x3 [Thu Jul 9 14:07:44 2026] rk-pcie fe150000.pcie: PCIe Linking... LTSSM is 0x1 [Thu Jul 9 14:07:44 2026] rk-pcie fe190000.pcie: PCIe Linking... LTSSM is 0x3 [Thu Jul 9 14:07:44 2026] rk-pcie fe170000.pcie: PCIe Linking... LTSSM is 0x3 [Thu Jul 9 14:07:44 2026] rk-pcie fe150000.pcie: PCIe Linking... LTSSM is 0x1 [Thu Jul 9 14:07:44 2026] rk-pcie fe180000.pcie: PCIe Link up, LTSSM is 0x130011 [Thu Jul 9 14:07:44 2026] rk-pcie fe180000.pcie: PCI host bridge to bus 0003:30 [Thu Jul 9 14:07:44 2026] pcieport 0003:30:00.0: PME: Signaling with IRQ 154 [Thu Jul 9 14:07:47 2026] rk-pcie fe170000.pcie: PCIe Link Fail [Thu Jul 9 14:07:47 2026] rk-pcie fe170000.pcie: failed to initialize host [Thu Jul 9 14:07:47 2026] rk-pcie fe190000.pcie: PCIe Link Fail [Thu Jul 9 14:07:47 2026] rk-pcie fe190000.pcie: failed to initialize host [Thu Jul 9 14:07:47 2026] rk-pcie fe150000.pcie: PCIe Link Fail [Thu Jul 9 14:07:47 2026] rk-pcie fe150000.pcie: failed to initialize host [Thu Jul 9 14:07:47 2026] rockchip-pm-domain fd8d8000.power-management:power-controller: Looking up pcie-supply from device tree [Thu Jul 9 14:07:47 2026] rockchip-pm-domain fd8d8000.power-management:power-controller: Looking up pcie-supply property in node /power-management@fd8d8000/power-controller failed [Thu Jul 9 14:07:47 2026] reg-fixed-voltage pcie20-avdd0v85: Looking up vin-supply from device tree [Thu Jul 9 14:07:47 2026] pcie20_avdd0v85: supplied by vdd_0v85_s0 [Thu Jul 9 14:07:47 2026] pcie20_avdd0v85: 850 mV, enabled [Thu Jul 9 14:07:47 2026] reg-fixed-voltage pcie20-avdd0v85: pcie20_avdd0v85 supplying 850000uV [Thu Jul 9 14:07:47 2026] reg-fixed-voltage pcie20-avdd1v8: Looking up vin-supply from device tree [Thu Jul 9 14:07:47 2026] pcie20_avdd1v8: supplied by avcc_1v8_s0 [Thu Jul 9 14:07:47 2026] pcie20_avdd1v8: 1800 mV, enabled [Thu Jul 9 14:07:47 2026] reg-fixed-voltage pcie20-avdd1v8: pcie20_avdd1v8 supplying 1800000uV [Thu Jul 9 14:07:47 2026] reg-fixed-voltage pcie30-avdd0v75: Looking up vin-supply from device tree [Thu Jul 9 14:07:47 2026] pcie30_avdd0v75: supplied by avdd_0v75_s0 [Thu Jul 9 14:07:47 2026] pcie30_avdd0v75: 750 mV, enabled [Thu Jul 9 14:07:47 2026] reg-fixed-voltage pcie30-avdd0v75: pcie30_avdd0v75 supplying 750000uV [Thu Jul 9 14:07:47 2026] reg-fixed-voltage pcie30-avdd1v8: Looking up vin-supply from device tree [Thu Jul 9 14:07:47 2026] pcie30_avdd1v8: supplied by avcc_1v8_s0 [Thu Jul 9 14:07:47 2026] pcie30_avdd1v8: 1800 mV, enabled [Thu Jul 9 14:07:47 2026] reg-fixed-voltage pcie30-avdd1v8: pcie30_avdd1v8 supplying 1800000uV 0003:30:00.0 PCI bridge [0604]: Rockchip Electronics Co., Ltd Device [1d87:3588] (rev 01) 0003:31:00.0 Ethernet controller [0200]: Realtek Semiconductor Co., Ltd. RTL8125 2.5GbE Controller [10ec:8125] (rev 05) NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINTS mtdblock0 31:0 0 16M 0 disk mmcblk0 179:0 0 58.2G 0 disk ├─mmcblk0p1 179:1 0 1G 0 part /boot └─mmcblk0p2 179:2 0 56.6G 0 part /var/log.hdd / zram0 254:0 0 3.9G 0 disk [SWAP] zram1 254:1 0 200M 0 disk /var/log orangepi@orangepi5ultra:~$ 0 Quote
eselarm Posted 25 minutes ago Posted 25 minutes ago 1 hour ago, MAXIM ALEKSEEV said: orange pi 5 ultra Orange Pi 1.0.0 Jammy with Linux 5.10.160-rockchip-rk3588 Ultra is not the standard OPi5 nor OPi5Pro, AFAIR it is also RK3588 v.s. RK3588S wich is a major difference w.r.t. PCIE Use a recent kernel/image, see https://armbian.com/boards/orangepi5-ultra And report brand and type of the M.2 NVME SSD. Some people have asked similar question and turned out to be a M.2 SATA SSD 0 Quote
MAXIM ALEKSEEV Posted 9 minutes ago Posted 9 minutes ago (edited) I tried all the images including Armbian and the result is the same. The disk is a Silicon Power P34A60 256 GB NVME not SATA Edited 9 minutes ago by MAXIM ALEKSEEV 0 Quote
Recommended Posts
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.