Armbian does not have things like "vendor-lockin" or something and descriptions like "does not work" aren't much helpful as well. Either way, we cannot help with 3rd party OS since we neither know them nor deal with them, so I suggest to ask at the place where you got the image you are attempting to use get from, like http://friendlyarm.com/

Ah, this board has n out of tree dt as well which most likely overwrites the patch. Try adjusting this file: ~/build/patch/kernel/archive/rockchip64-6.18/dt/rk3576-nanopi-r76s.dts

I'll give it a go when ready for download 🙂 ljones

I am trying to get the ARM performance assessment setup working (I'm trying to get Mali profiling for OpenCL code) on the Rock 5B+, and I've hit a blocker. The main component to this is some kernel configuration (CONFIG_ARM_SPE_PMU) and a loadable module. Oddly, those work fine in a custom kernel build. What I am hitting appears to be some missing interrupt setup that renders all those components inert. (It has to be a custom build to get CONFIG_ARM_SPE_PMU set. The issue is that even with the kernel configured and the module loaded, the SPE component remains inactive. ARM has its own system report tool which analyzes a setup, and that tool is reporting an issue: And indeed, nothing seems to show in cat /proc/interrupts. The man page for the module suggests this is the issue: It says: KPTI is definitely disabled and the SPE PMU loads (it's in lsmod) but it still doesn’t show in /sys/bus/event_source/devices/. Nothing relevant seemed to show in dmesg either. Frankly, I have no idea where to look for the SPE interrupt, or how to set it up. If anybody has any pointers or suggestions, I'd be extremely grateful.

deleted my patch file in userpatches cp output/patch/kernel-rockchip64-current.patch patch/kernel/archive/rockchip64-6.18/rk3588-1300-arm64-dts-rock5t-eth-reset.patch definitely saw the patch get applied during the build ./compile.sh BOARD=rock-5t BRANCH=current RELEASE=trixie kernel-dtb # cat output/logs/log-kernel-dtb-cd035955-4094-4e6f-b86d-89fe0287a2ce.log.ans |grep eth-reset patch/kernel/archive/rockchip64-6.18/rk3588-1300-arm64-dts-rock5t-eth-reset.patch -> 223/230: rk3588-1300-arm64-dts-rock5t-eth-reset(:1) (+20/-0)[1M] {rk3588-rock-5t.dts} │ rk3588-1300-arm64-dts-rock5t-eth-reset copied the rk3588-rock-5t.dtb over to my Rock5t's /boot/dtb/rockchip/ folder, rebooted it and ..... it didn't work # dmesg |grep -e 'r8169\|RTL8125B' [ 2.286822] r8169 0003:31:00.0: enabling device (0000 -> 0003) [ 2.314767] r8169 0003:31:00.0 eth0: RTL8125B, 00:48:54:20:XX:XX, XID 641, IRQ 123 [ 2.314803] r8169 0003:31:00.0 eth0: jumbo features [frames: 16362 bytes, tx checksumming: ko] [ 2.347904] r8169 0003:31:00.0 enP3p49s0: renamed from eth0 [ 5.367059] Realtek Internal NBASE-T PHY r8169-3-3100:00: attached PHY driver (mii_bus:phy_addr=r8169-3-3100:00, irq=MAC) [ 5.560727] r8169 0003:31:00.0 enP3p49s0: Link is Down [ 7.870963] r8169 0003:31:00.0 enP3p49s0: Link is Up - 1Gbps/Full - flow control rx/tx So either I'm doing something wrong, 1st time building something on this build framework, or this patch just doesn't work on my Rock5t. Ethernet should be the same on the consumer and industrial boards right?