Everytime I reboot I have to wait many minutes before the NIC auto-negotiates and connects. The problem seems to be at the PHY layer as the LED does not light up at all ... see time span between 23:22:20 and 23:23:52 : 

Quote

Linux rock-5-itx 6.18.43-current-rockchip64 #4 SMP PREEMPT Thu Aug  6 17:27:09 UTC 2026 aarch64 GNU/Linux
Aug 17 23:22:20 rock-5-itx kernel: r8169 0003:31:00.0: enabling device (0000 -> 0003)
Aug 17 23:22:20 rock-5-itx kernel: r8169 0003:31:00.0 eth0: RTL8125B, 00:e0:4c:XX:XX:XX, XID 641, IRQ 129
Aug 17 23:22:20 rock-5-itx kernel: r8169 0003:31:00.0 eth0: jumbo features [frames: 16362 bytes, tx checksumming: ko]
Aug 17 23:22:20 rock-5-itx kernel: r8169 0004:41:00.0: enabling device (0000 -> 0003)
Aug 17 23:22:20 rock-5-itx kernel: r8169 0004:41:00.0 eth1: RTL8125B, 00:e0:4c:XX:XX:XX, XID 641, IRQ 130
Aug 17 23:22:20 rock-5-itx kernel: r8169 0004:41:00.0 eth1: jumbo features [frames: 16362 bytes, tx checksumming: ko]
Aug 17 23:22:20 rock-5-itx kernel: r8169 0003:31:00.0 enP3p49s0: renamed from eth0
Aug 17 23:22:20 rock-5-itx kernel: r8169 0004:41:00.0 enP4p65s0: renamed from eth1
Aug 17 23:22:20 rock-5-itx systemd[1]: systemd-hibernate-clear.service - Clear Stale Hibernate Storage Info skipped, unmet condition check ConditionPathExists=/sys/firmware/efi/efivars/HibernateLocation-8cf2644b-4b0b-428f-9387-6d876050dc67
Aug 17 23:22:20 rock-5-itx kernel: panthor fb000000.gpu: [drm] Firmware protected mode entry not be supported, ignoring
Aug 17 23:22:20 rock-5-itx kernel: panthor fb000000.gpu: [drm] Firmware git sha: 95a25d71030715381f33105394285e1dcc860a65 
Aug 17 23:23:49 rock-5-itx kernel: Realtek Internal NBASE-T PHY r8169-3-3100:00: attached PHY driver (mii_bus:phy_addr=r8169-3-3100:00, irq=MAC)
Aug 17 23:23:50 rock-5-itx kernel: r8169 0003:31:00.0 enP3p49s0: Link is Down
Aug 17 23:23:50 rock-5-itx kernel: Realtek Internal NBASE-T PHY r8169-4-4100:00: attached PHY driver (mii_bus:phy_addr=r8169-4-4100:00, irq=MAC)
Aug 17 23:23:50 rock-5-itx kernel: r8169 0004:41:00.0 enP4p65s0: Link is Down
Aug 17 23:23:52 rock-5-itx kernel: r8169 0003:31:00.0 enP3p49s0: Link is Up - 1Gbps/Full - flow control rx

 

Why is this happening? Only enP3p49s0 is plugged in and NetworkManager-wait-online.service is disabled. 

Thanks

I built the core minimal image successfully a few times while I was experimenting with kernel config options and then finally when I enabled all the settings I wanted somehow a different component of the build process started failing repeatedly since last few days:

Quote

./compile.sh BOARD=rock-5-itx RELEASE=resolute BUILD_DESKTOP=no BUILD_MINIMAL=yes 

...

Fetching SHA1 of 'tag' 'refs/heads/v2026.04^{}' [ https://github.com/u-boot/u-boot.git ] SHA1 of tag refs/heads/v2026.04^{} [ '' ]
Failed to fetch SHA1 of 'tag' 'refs/heads/v2026.04^{}' [ https://github.com/u-boot/u-boot.git ]

Command failed, retrying in 5s [ obtain_makefile_body_from_url https://raw.githubusercontent.com/u-boot/u-boot/88dc2788777babfd6322fa655df549a019aa1e69/Makefile ]

...
 

Why is this happening. All I did was edit linux-rockchip-rk3588-edge.config and symlink linux-rockchip-rk3588-current.config -> linux-rockchip-rk3588-edge.config

I also tried the Armbian Imager and the SD creation was very easy and smooth. 

I selected the recommended release based on Ubuntu 24.04 + Gnome desktop.

Unfortunately when the desktop was about to start, everything when black, stucked and zero interface. On the other hand, the OS is alive and I can connect remotely via SSH.

Did anyone have the same problem? Possible solution?

[EDIT]. 

sudo systemctl restart gdm and desktop pops up. Restarting the system, black again.

I'm a complete Linux noob so please forgive my ignorance. But I do have 25+ years experience in IT so am relatively conversant with basic principles - so please be patient   I did try to search for any previous threads but couldn't find any.

I'm trying to setup a RADXA Rock 5 ITX with OpenMediaVault for my NAS.

I have a 2TB NVMe m.2 SSD that I'll use for the OS.

For the NAS storage I'm using 4x Western Digital 16TB SATA III drives.

I downloaded the Armbian 25.2.2 bootable image from https://www.armbian.com/radxa-rock-5-itx/ and used Balena Etcher (the legit version from Balena-io) to make my bootable microSD card.

When I boot, I receive an error message of "failed to mount /dev/mount/mmcblk0p1 as root file system"

I'm guessing this is because there is no emmc on this board other than what's provided for RooibOS flash?

Do I just need to reconfigure the Armbian Bookworm setup script to use / look for the NVMe m.2 SSD instead of the emmc? If so, is there a way to do that on a Windows PC? If not, I may just have to go with the standard RooibOS install using Armbian Noble just to get a Linux system up and running, then edit the Armbian setup script, reflash the Rock 5 ITX and start again?

Or is there something else I'm missing?

Thanks in advance for your help.

After 5 years of loyal service, my Helios64 SBC just died on me last night.

Would a Radxa Rock5 ITX+ and a M.2 to Hexa SATA Adapter could be a good drop in replacement to reuse the case?

Both are Mini-ITX so it would fit.

I know I would lose the front panel lights and power/reset button, and I would need to cut the back panel to fit the I/O shield but these are minor problems.

What I am more concerned with, is if it is at all possible to power the 5 HDD from the radxa board (as the Helios 64 board didi).

Helios engineers had made it possible to do it with minimum power, mainly by starting up the drives sequentially.

Can the molex 4-Pin connector on the Radxa can do it?
Provided I could buy/make an adapter to connect it to the J8 harness of the case?

That would definitely be a great thing if I could reuse that very fine enclosure.

Thanks for your input on that matter.

I'm new to this forum but i follow the SBC comunity for a long time. I have a Pine 64,  a bunch of raspberryies, 2 nanopies and some "japanese" arm64 tablet. Now i have bought a Radxa 5 Mini-ITX and i'm very happy with it. I was capable to compile ffmpeg with the rockchip extensions and exploit the RK3588 VPU and the NPU with face recognition. Now i was testing the HDMI Input of the board and unfortunaly discovered that the video is capturing just fine but i'm out of luck with the audio side. On the kernel 6.1.115 (last BSP at the moment i think) the recording device of the audio input is not visible in 

arecode -l

This is what i see:

**** List of CAPTURE Hardware Devices ****
card 4: rockchipes8316 [rockchip-es8316], device 0: dailink-multicodecs ES8316 HiFi-0 [dailink-multicodecs ES8316 HiFi-0]
  Subdevices: 1/1
  Subdevice #0: subdevice #0

But the hdmi input audio card is still found under /proc/asound/cards:

root@rock-5-itx:~# cat /proc/asound/cards
 0 [rockchiphdmi1  ]: rockchip-hdmi1 - rockchip-hdmi1
                      rockchip-hdmi1
 1 [rockchiphdmi0  ]: rockchip-hdmi0 - rockchip-hdmi0
                      rockchip-hdmi0
 2 [rockchiphdmi2  ]: rockchip-hdmi2 - rockchip-hdmi2
                      rockchip-hdmi2
 3 [rockchiphdmiin ]: rockchip-hdmiin - rockchip-hdmiin
                      rockchip-hdmiin
 4 [rockchipes8316 ]: rockchip-es8316 - rockchip-es8316
                      rockchip-es8316
 5 [rockchipspdiftx]: simple-card - rockchip,spdif-tx1
                      rockchip,spdif-tx1

Furthermore if i go under /proc/asound/pcm:

root@rock-5-itx:~# cat /proc/asound/pcm
00-00: rockchip-hdmi1 i2s-hifi-0 : rockchip-hdmi1 i2s-hifi-0 : playback 1
01-00: rockchip-hdmi0 spdif-hifi-0 : rockchip-hdmi0 spdif-hifi-0 : playback 1
02-00: rockchip-hdmi2 spdif-hifi-0 : rockchip-hdmi2 spdif-hifi-0 : playback 1
03-00: rockchip-hdmiin i2s-hifi-0 :
04-00: dailink-multicodecs ES8316 HiFi-0 : dailink-multicodecs ES8316 HiFi-0 : playback 1 : capture 1
05-00: fe4f0000.spdif-tx-dit-hifi dit-hifi-0 : fe4f0000.spdif-tx-dit-hifi dit-hifi-0 : playback 1

So the HDMI Input is still found (rockchip-hdmiin) but is not exposing any playback or capture jack

So i tried to investigate and found that rockchip as changed the sound driver at some point as i found out here: https://zhuanlan.zhihu.com/p/664345417 (Link in Chinese)

(I don't know if i can post link so let me know)

Now i found that if i manualy install the 6.1.75 Kernel i found the device and i am able to record the audio:

root@rock-5-itx:~# arecord -l
**** List of CAPTURE Hardware Devices ****
card 0: rockchiphdmiin [rockchip-hdmiin], device 0: rockchip-hdmiin i2s-hifi-0 [rockchip-hdmiin i2s-hifi-0]
  Subdevices: 1/1
  Subdevice #0: subdevice #0
card 1: rockchipes8316 [rockchip-es8316], device 0: dailink-multicodecs ES8316 HiFi-0 [dailink-multicodecs ES8316 HiFi-0]
  Subdevices: 1/1
  Subdevice #0: subdevice #0

Anyone can't test this? Maybe is for all the RK3588 or only the Radxa 5 ITX.

https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/arch/arm64/boot/dts/rockchip?h=v6.18&id=07c53a9e970712b1a479dd0ec4adfe184482c22f

ROCKCHIP_DW_DP is needed in order to have working 2nd HDMI port.

In menuconfig :  Device Drivers  --->   Direct Rendering Manager (XFree86 4.Graphics support  ---> 1.0 and higher DRI support)  --->     Rockchip specific extensions for Synopsys DW DP

<pre>

  │ CONFIG_ROCKCHIP_DW_DP:                                                                                                                                                  │  
  │                                                                                                                                                                         │  
  │ This selects support for Rockchip SoC specific extensions                                                                                                               │  
  │ to enable Synopsys DesignWare Cores based DisplayPort transmit                                                                                                          │  
  │ controller support on Rockchip SoC, If you want to enable DP on                                                                                                         │  
  │ rk3588 based SoC, you should select this option.                                                                                                                        │  
  │                                                                                                                                                                         │  
  │ Symbol: ROCKCHIP_DW_DP [=n]                                                                                                                                             │  

</pre>

https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/arch/arm64/boot/dts/rockchip/rk3588-extra.dtsi?h=v6.18&id=64566e35757faded57a65d65e84b5ca95974ee19

I think that they also worked during the very first boot of the system but after ``` apt update  && apt upgrade ``` and reboot, they stop working.

Any advice would be much appreciated.

```

rock-5-itx:~$ lsblk
NAME         MAJ:MIN RM   SIZE RO TYPE MOUNTPOINTS
mtdblock0     31:0    0    16M  0 disk
mmcblk0      179:0    0   7.3G  0 disk
mmcblk0boot0 179:32   0     4M  1 disk
mmcblk0boot1 179:64   0     4M  1 disk
zram0        252:0    0  11.6G  0 disk [SWAP]
zram1        252:1    0    50M  0 disk /var/log
zram2        252:2    0     0B  0 disk
nvme0n1      259:0    0 476.9G  0 disk
└─nvme0n1p1  259:1    0 472.1G  0 part /var/log.hdd
                                       /

```

https://paste.armbian.com/qiwimusofo

Instead, try this. Set vlc audio back to pulseaudio (or automatic, seems to map to the same thing) and then change these two lines in /etc/pulse/daemon.conf:

-; default-sample-rate = 44100
-; alternate-sample-rate = 48000

+default-sample-rate = 48000
+alternate-sample-rate = 44100
 

Restart pulseaudio with systemctl --user restart pulseaudio and see if vlc plays nice with everything else as well as supporting smooth playback after seeking. It does for me. It seems that forcing pulseaudio to resample causes all sorts of hilarity (vlc seems to like putting everything out at 48000). I'm sure there's a reason why. I'm also sure if I know, I'll be sorry I do.

I wonder, how hard is it to get the Vulkan video hardware decoding working? Has anyone gotten it to work?

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!

I want to try UEFI boot on this board. And I have one question. Can I use Rockchip vendor kernel with Armbian UEFI?

I first tried this, as it was the first version offered at the top of the page. No matter what I tried, sound would *not* work. Not speakers, not HDMI, nada, zip. I then started trying earlier versions further down the page.

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

And this one, sound *did* work, at least through the speaker jack anyway, but I suspect HDMI would too. I'm really suspecting something kernel related is going here (that "Rockchip BSP" note right above it makes me suspect that).

In any case, I'd like to use the kernel where sound is working and put a gnome shell in front of it. Which I take means digging into the build system for armbian? I can figure that out on my own but before I get started on that, what I'm looking for from the forumistas, is an indication of which specific kernel I need to use to make sure sound works. What do I need to make sure to specify so I get the behavior of that second install that worked?

And Cinnamon may be better or something, but gnome is what I'm used to.

I've been at this for two weeks now with different images, including Armbian and Radxa OS, even going so far as trying to build Armbian myself from scratch. The image I am currently using is however the most stable I have experienced so far. Am I missing something? How do I get hardware decoding to work?

Edit: Link to armbianmonitor output

I've done this before for other systems using these without too much trouble but when I tried with this board it's not working. Admittedly I haven't hooked it up to a scope to look at the signals, but I'm suspicious of the high baudrate being to blame. I have a couple USB adapters that work (so I know the console itself works), but I want to rackmount this box and wire it up to my console server. I need RS232 to do that.

   I am currently using rock-5-itx to setup a NAS. Everything is working fine.

uname -a:

Linux amberbyte 6.1.75-vendor-rk35xx #1 SMP Thu Nov 28 03:16:11 UTC 2024 aarch64 GNU/Linux

Now, I wanted to update RKNPU version from 0.9.7 to 0.9.8. So, again I recompiled the image with the updated drivers. Using Pi-imager flashed it onto an SD card. When I tried to boot I am getting the following error message from the serial output: 
 

./compile.sh build BOARD=rock-5-itx BRANCH=vendor BUILD_DESKTOP=no BUILD_MINIMAL=yes EXPERT=yes KERNEL_CONFIGURE=yes RELEASE=bookworm

DDR 9fffbe1e78 cym 24/02/04-10:09:20,fwver: v1.16
LPDDR5, 2400MHz
channel[0] BW=16 Col=10 Bk=16 CS0 Row=16 CS1 Row=16 CS=2 Die BW=16 Size=4096MB
channel[1] BW=16 Col=10 Bk=16 CS0 Row=16 CS1 Row=16 CS=2 Die BW=16 Size=4096MB
channel[2] BW=16 Col=10 Bk=16 CS0 Row=16 CS1 Row=16 CS=2 Die BW=16 Size=4096MB
channel[3] BW=16 Col=10 Bk=16 CS0 Row=16 CS1 Row=16 CS=2 Die BW=16 Size=4096MB
Manufacturer ID:CH0 RX Vref:26.3%, TX Vref:21.0%,21.0%
CH1 RX Vref:27.1%, TX Vref:22.0%,22.0%
CH2 RX Vref:27.1%, TX Vref:24.0%,21.0%
CH3 RX Vref:27.5%, TX Vref:21.0%,20.0%
change to F1: 534MHz
change to F2: 1320MHz
change to F3: 1968MHz
change to F0: 2400MHz
out
U-Boot SPL board init
U-Boot SPL 2017.09-armbian-2017.09-S2284-P8c48-Hfac6-Ve5ad-Bda0a-R448a (Nov 20 2024 - 17:06:35)
Trying to boot from MMC2
spl: partition error
Trying fit image at 0x4000 sector
## Verified-boot: 0
## Checking atf-1 0x00040000 ... sha256(7612223b82...) + OK
## Checking uboot 0x00200000 ... sha256(af1962bdff...) + OK
## Checking fdt 0x00324010 ... sha256(e3b0c44298...) + OK
fdt_record_loadable: FDT_ERR_BADMAGIC
## Checking atf-2 0xff100000 ... sha256(70505bb764...) + OK
fdt_record_loadable: FDT_ERR_BADMAGIC
## Checking atf-3 0x000f0000 ... sha256(b2af21b504...) + OK
fdt_record_loadable: FDT_ERR_BADMAGIC
Jumping to U-Boot(0x00200000) via ARM Trusted Firmware(0x00040000)
Total: 813.644/1063.106 ms

INFO:    Preloader serial: 2
NOTICE:  BL31: v2.3():v2.3-868-g040d2de11:derrick.huang, fwver: v1.48
NOTICE:  BL31: Built : 15:02:44, Dec 19 2024
INFO:    spec: 0x1
INFO:    code: 0x88
INFO:    ext 32k is not valid
INFO:    ddr: stride-en 4CH
INFO:    GICv3 without legacy support detected.
INFO:    ARM GICv3 driver initialized in EL3
INFO:    valid_cpu_msk=0xff bcore0_rst = 0x0, bcore1_rst = 0x0
INFO:    l3 cache partition cfg-0
INFO:    system boots from cpu-hwid-0
INFO:    disable memory repair
INFO:    idle_st=0x21fff, pd_st=0x11fff9, repair_st=0xfff70001
INFO:    dfs DDR fsp_params[0].freq_mhz= 2400MHz
INFO:    dfs DDR fsp_params[1].freq_mhz= 534MHz
INFO:    dfs DDR fsp_params[2].freq_mhz= 1320MHz
INFO:    dfs DDR fsp_params[3].freq_mhz= 1968MHz
INFO:    BL31: Initialising Exception Handling Framework
INFO:    BL31: Initializing runtime services
WARNING: No OPTEE provided by BL2 boot loader, Booting device without OPTEE initialization. SMC`s destined for OPTEE will return SMC_UNK
ERROR:   Error initializing runtime service opteed_fast
INFO:    BL31: Preparing for EL3 exit to normal world
INFO:    Entry point address = 0x200000
INFO:    SPSR = 0x3c9
No valid device tree binary found - please append one to U-Boot binary, use u-boot-dtb.bin or define CONFIG_OF_EMBED. For sandbox, use -d <file.dtb>
initcall sequence 00000000002b8500 failed at call 00000000002aaf6c (err=-1)
### ERROR ### Please RESET the board ###

I get the same error when I use the desktop image too:

 

./compile.sh build BOARD=rock-5-itx BRANCH=vendor BUILD_DESKTOP=yes BUILD_MINIMAL=no DESKTOP_APPGROUPS_SELECTED='browsers desktop_tools internet programming' DESKTOP_ENVIRONMENT=gnome DESKTOP_ENVIRONMENT_CONFIG_NAME=config_base EXPERT=yes KERNEL_CONFIGURE=yes RELEASE=bookworm

But when I use the image downloaded from the armbian website is getting booted up without any issue and it has updated RKNPU drivers. But I have to build a kernel because I want the LSI MEGARAID drivers enabled. 

Also when I want to make RKNPU driver modular <M> it is unable to finish building the image with an error saying it is unable to find rknpu.ko.

So, why is this happenning and is there a way to update the drivers without going through building the kernel?

Thank you in advance and any help will be helpful.

I am wanting to try running OPNsense under proxmox, but before that I wanted to setup the type-C port as a management port. I have added g_cdc in /etc/modules to load the kernel module and if I run a vendor kernel, it works fine. I plug my laptop in to the boards type-C port and it shows up as an ethernet adapter and I can SSH directly to the Rock 5 ITX. I however would like to use a mainline kernel instead as it generally runs better thanks to the amazing work of the community here. Running 6.12, this same functionality does not work and nothing appears in the network adapters on my laptop when plugging in.
Looking on mainline-status, I see that the type-C support (ie USB-C (fusb302)), has been sent but not accepted yet. Once this has been merged and I update to the newest kernel, will the type-C port work like I hope?

Any help or advice would be much appreciated!

I'm quite new to SBC and linux. On one hand I'm learning a lot, but on the other hand I'm struggling to make it work as I would like.

I already have a low performance Zimaboard (just 2GB Ram) that I use as a NAS and I want the ROCK 5 ITX  8GB to be used as a general purpose apps server for home automation, streaming music, listening music, etc.

One of my use case I'm playing with is the following:

1) music files are on the NAS

2) Music files are played from the Rock5 ITx via the speakers plugged into the headphone jack,

3) The music player is controlled remotely using Lyrion Music Server + Squeezelite.

I've already tested the above using the official rock-5-itx_bookworm_kde_b3.output.img.xz image and it works: no rocket science . 

Unfortunately the vendor official image is not very stable: the docker containers crash randomly and even if the SATA drives are detected and mounted at boot time, the got disconnected randomly after some hours.

That's why I decided to go experimental and now I'm playing with the following setup and 6 containers running:

 OS: Armbian-unofficial 25.05.0-trunk bookworm aarch64
       ?******************;            Host: Radxa ROCK 5 ITX
      '*n` .'`^,;;,^`'. ,cc.           Kernel: Linux 6.15.0-rc1-edge-rockchip64
     !^         ^^         ":          Shell: bash 5.2.15
    Itttt?'   ~~]rr]   `{tttt,         Terminal: /dev/pts/0
    \tttttt!""I_]r("""~tttttt1         CPU: rk3588 (8) @ 2.40 GHz
  '_tttttttttttt)ftttttttttttti.       GPU: Rockchip rk3588-mali [Integrated]
 \*ztttttttttttttttttttttttttf**[      Memory: 1.80 GiB / 7.75 GiB (23%)
l**c)tttttttttttttttttttttttt(z**,     Swap: 0 B / 3.87 GiB (0%)
.z*x.`tttttttttttttttttttttttt.`u*n    Disk (/): 11.90 GiB / 232.35 GiB (5%) - ext4
>`   (tttttttttttttttttttttt]   "I     Disk (/media/bidone): 44.76 GiB / 3.58 TiB (1%) - ext4
     ,tttttttttttttttttttttt`          Disk (/var/log): 5.31 MiB / 46.84 MiB (11%) - ext4
     ./tttttfttttttttfttttt(           Local IP (wlP2p33s0): 192.168.X.X
      'I)))(\()(tt))|\()({;'           Locale: it_IT.UTF-8

Coming back to the play-music-locally use-case, I've a problem with the sound card because I cannot hear the audio.

Here the output from Armbianmonitor:

https://paste.armbian.com/apaxoburiz

I've both ALSA and PulseAudio. Alsamixer works:

Hereunder other outputs, but I'm not expert enough to understand what's going on and why audio is not played by the speakers plugged to the board. No sound with "speaker-test" and "/etc/modprobe.d/sound.conf" doesn't exsist.

HDMI audio is not detected, but I can live without for the moment.

 cat /proc/asound/cards
 0 [rk3588es8316   ]: rk3588-es8316 - rk3588-es8316
                      rk3588-es8316

sudo dmesg | grep 'snd\|audio\|firmware'
[    0.000000] psci: PSCIv1.1 detected in firmware.
[    0.150543] /i2c@fec90000/audio-codec@11: Fixed dependency cycle(s) with /i2s@fe470000
[    1.495212] /i2s@fe470000: Fixed dependency cycle(s) with /i2c@fec90000/audio-codec@11
[    1.495240] /i2c@fec90000/audio-codec@11: Fixed dependency cycle(s) with /i2s@fe470000
[   15.623287] rtw89_8852be 0002:21:00.0: loaded firmware rtw89/rtw8852b_fw-1.bin

 inxi -A
Audio:
  Device-1: audio-graph-card driver: asoc_audio_graph_card
  Device-2: rk3588-dw-hdmi-qp driver: dwhdmiqp_rockchip
  API: ALSA v: k6.15.0-rc1-edge-rockchip64 status: kernel-api
  Server-1: PulseAudio v: 16.1 status: active

 aplay -l
**** List of PLAYBACK Hardware Devices ****
card 0: rk3588es8316 [rk3588-es8316], device 0: fe470000.i2s-ES8316 HiFi ES8316 HiFi-0 [fe470000.i2s-ES8316 HiFi ES8316 HiFi-0]
  Subdevices: 0/1
  Subdevice #0: subdevice #0

alsactl init
alsa-lib parser.c:2783:(load_toplevel_config) Unable to find the top-level configuration file '/usr/share/alsa/ucm2/ucm.conf'.
alsa-lib main.c:1541:(snd_use_case_mgr_open) error: failed to import hw:0 use case configuration -2
Found hardware: "rk3588-es8316" "" "" "" ""
Hardware is initialized using a generic method

Thank you: advices are appreciated.

In that case the system loads to rescue mode, asking for the root password and even if entered correctly does not identify. All comes back to working state with a shutdown and a reboot.
Notice : I've made a donation to support the team. Please help.

this week my Rock 5 ITX+ board arrived and I started installing Armbian with vendor kernel (now on 6.1.99-vendor-rk35xx).

This board has slightly different hardware than the original ITX. It has two M.2 M-key (2-lanes) instead of one M.2 M-key and four SATA ports.

I think because of the different hardware configuration the DTB has to be changed as no SATA controller is present on the board.

With the ITX DTB I am experiencing problems with not regonizing NVME disks when activating ASPM in armbianEnv.txt.

I have no experience in editing DTBs or applying patches, so I need help to figure out what to do to make things work.

armbianmonitor log: https://paste.next.armbian.com/asoxunogeg

Thanks

Thomas

I wanted to know if anyone know if there are any power limits from the SATA power ports, the question is can you power 1 or more 3.5" NAS disks at the same time? Or as a precaution, I take power from the PSU?

Thanks,
Dany