Jump to content

Recommended Posts

Posted

Dear all,

I got myself an Radxa Rock 5 ITX+ as I thought I'd saw that this board had premium support.

After it arrived, I saw that only the ITX (non-plus) variant had premium support, which since latest Armbian release some days ago seems to has been downgraded to standard support.

 

I cleared both the eMMC and SPI flash to make sure the preinstalled OS were gone and would not interfere with the boot up process.

Then I built myself a latest image with trixie  and vendor kernel but I realized that (after booting from sdcard successfully), the Nvme was never picked up.

The ITX+ has two M.2 full-size slots instead of only one - and is missing the SATA controller instead.

To make sure I did nothing wrong with the building process I grabbed myself some old images like e.g.

 

Armbian_24.11.1_Rock-5-itx_bookworm_vendor_6.1.75_cinnamon-backported-mesa_desktop.img.xz

Armbian_25.2.2_Rock-5-itx_bookworm_vendor_6.1.99_cinnamon-backported-mesa_desktop.img.xz

 

but they don't show working Nvmes either.

 

So I got myself the latest nightly Trixie build (Rolling releases images with Armbian Linux v6.1 / Build Date: Sep 6, 2025 / Debian Debian 13 (Trixie)) from https://www.armbian.com/radxa-rock-5-itx/ and booted that, to also see that both populated Nvme slots are not picked up.

 

lspci shows two Nvmes:

 

0000:01:00.0 Non-Volatile memory controller: Solid State Storage Technology Corporation NVMe SSD M.2 (rev 01)
0001:11:00.0 Non-Volatile memory controller: Solid State Storage Technology Corporation NVMe SSD M.2 (rev 01)

 

Bot dmesg shows issues during boot:

 

[   14.165404] pci 0001:10:00.0: Primary bus is hard wired to 0
[   14.165410] pci 0001:10:00.0: bridge configuration invalid ([bus 01-ff]), reconfiguring
[   14.165514] pci 0001:11:00.0: [1e95:3500] type 00 class 0x010802
[   14.165568] pci 0001:11:00.0: reg 0x10: [mem 0x00000000-0x00003fff 64bit]
[   14.165794] pci_bus 0000:01: busn_res: can not insert [bus 01-ff] under [bus 00-0f] (conflicts with (null) [bus 00-0f])
[   14.165901] pci 0000:01:00.0: [1e95:3500] type 00 class 0x010802
[   14.166009] pci 0000:01:00.0: reg 0x10: [mem 0x00000000-0x00003fff 64bit]
[   14.166147] pci 0001:11:00.0: 15.752 Gb/s available PCIe bandwidth, limited by 8.0 GT/s PCIe x2 link at 0001:10:00.0 (capable of 31.504 Gb/s with 8.0 GT/s PCIe x4 link)
[   14.166379] cpu cpu6: l=15000 h=85000 hyst=5000 l_limit=0 h_limit=2208000000 h_table=0
[   14.166699] pci_bus 0001:11: busn_res: [bus 11-1f] end is updated to 11
[   14.166721] pci 0001:10:00.0: BAR 8: assigned [mem 0xf1200000-0xf12fffff]
[   14.166729] pci 0001:10:00.0: BAR 6: assigned [mem 0xf1300000-0xf130ffff pref]
[   14.166729] pci 0000:01:00.0: 15.752 Gb/s available PCIe bandwidth, limited by 8.0 GT/s PCIe x2 link at 0000:00:00.0 (capable of 31.504 Gb/s with 8.0 GT/s PCIe x4 link)
[   14.166737] pci 0001:11:00.0: BAR 0: assigned [mem 0xf1200000-0xf1203fff 64bit]
[   14.166785] pci 0001:10:00.0: PCI bridge to [bus 11]
[   14.166792] pci 0001:10:00.0:   bridge window [mem 0xf1200000-0xf12fffff]
[   14.168281] pcieport 0001:10:00.0: PME: Signaling with IRQ 128
[   14.168548] nvme nvme0: pci function 0001:11:00.0
[   14.168576] nvme 0001:11:00.0: enabling device (0000 -> 0002)
[   14.176536] pci 0000:00:00.0: BAR 8: assigned [mem 0xf0200000-0xf02fffff]
[   14.176542] pci 0000:00:00.0: BAR 6: assigned [mem 0xf0300000-0xf030ffff pref]
[   14.176546] pci 0000:01:00.0: BAR 0: assigned [mem 0xf0200000-0xf0203fff 64bit]
[   14.176569] pci 0000:00:00.0: PCI bridge to [bus 01-ff]
[   14.176573] pci 0000:00:00.0:   bridge window [mem 0xf0200000-0xf02fffff]
[   14.177418] pcieport 0000:00:00.0: PME: Signaling with IRQ 138
[   14.177557] nvme nvme1: pci function 0000:01:00.0
[   14.177582] nvme 0000:01:00.0: enabling device (0000 -> 0002)
[   14.181202] nvme nvme0: Removing after probe failure status: -19
[   14.185702] cpu cpu6: EM: OPP:1008000 is inefficient
[   14.185716] cpu cpu6: EM: OPP:816000 is inefficient
[   14.185965] cpu cpu6: EM: created perf domain
[   14.190212] nvme nvme1: Removing after probe failure status: -19
 

( full log: https://paste.next.armbian.com/labujaguke.yaml )

 

Any idea on how to fix this and get them working? That would be really lovely,

Thanks a lot for all your support! :)

 

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