Hello,
I have Radxa Zero 3E (with Ethernet) and everything basic seems to be working - more precisely:
- I’m using only very basic stuff
- I don’t use GPIO (SPI, I2C, hw serial, …)
- I don’t use external USB devices
- I don’t use external HDMI display
But in dmesg output there are some warnings 
and erros 
- dmesg output will be after System details
System details:
-
DietPi version |
cat /boot/dietpi/.version$ cat /boot/dietpi/.version G_DIETPI_VERSION_CORE=9 G_DIETPI_VERSION_SUB=16 G_DIETPI_VERSION_RC=3 G_GITBRANCH='master' G_GITOWNER='MichaIng' G_LIVE_PATCH_STATUS[0]='applied' G_LIVE_PATCH_STATUS[1]='applied' G_LIVE_PATCH_STATUS[2]='applied' -
Distro version |
echo $G_DISTRO_NAME $G_RASPBIAN
→trixie -
Kernel version |
uname --all
→Linux radxaZ3E 6.1.115-vendor-rk35xx #1 SMP Thu Sep 11 07:20:40 UTC 2025 aarch64 GNU/Linux -
Architecture |
dpkg --print-architecture
→arm64 -
SBC model |
echo $G_HW_MODEL_NAMEor (EG: RPi3)
→Radxa ZERO 3 (aarch64) -
Power supply used
→ DC 5.2V 6A (Riden RK6006, Riden RD6012P) -
SD card used
→ Kingston Industrial 16GB (SDCIT2/16GB)-
Filesystem Size Used Avail Use% Mounted on /dev/mmcblk1p1 15G 3.0G 11G 22% /
-
-
dietpi-banner,fastfetch:
dietpi@radxaZ3E:~$ dietpi-banner 1
─────────────────────────────────────────────────────
DietPi v9.16.3 : 20:06 - Mon 09/15/25
─────────────────────────────────────────────────────
- Device model : Radxa ZERO 3 (aarch64)
- Uptime : up 2 hours, 22 minutes
- CPU temp : 44 °C / 111 °F : Optimal temperature
- RAM usage : 189 of 962 MiB (20%)
- Load average : 0.03, 0.02, 0.00 (4 cores)
- FQDN/hostname : radxaZ3E
- LAN IP : 192.168.3.132 (eth0)
- Disk usage (RootFS) : 3.0G of 15G (22%)
─────────────────────────────────────────────────────
dietpi@radxaZ3E:~$ sudo fastfetch
_,met$$$$$gg. root@radxaZ3E
,g$$$$$$$$$$$$$$$P. -------------
,g$$P"" """Y$$.". OS: Debian GNU/Linux 13 (trixie) aarch64
,$$P' `$$$. Host: Radxa ZERO 3
',$$P ,ggs. `$$b: Kernel: Linux 6.1.115-vendor-rk35xx
`d$$' ,$P"' . $$$ Uptime: 2 hours, 22 mins
$$P d$' , $$P Packages: 293 (dpkg)
$$: $$. - ,d$$' Shell: bash 5.2.37
$$; Y$b._ _,d$P' Terminal: dropbear
Y$$. `.`"Y$$$$P"' CPU: rk3566 (4) @ 1.80 GHz
`$$b "-.__ GPU: Arm mali-bifrost [Integrated]
`Y$$b Memory: 188.86 MiB / 961.54 MiB (20%)
`Y$$. Swap: 0 B / 1.06 GiB (0%)
`$$b. Disk (/): 2.99 GiB / 14.57 GiB (21%) - ext4
`Y$$b. Local IP (eth0): 192.168.3.132/16
`"Y$b._ Locale: C.UTF-8
`""""
fastfetch -c all.jsonc
root@radxaZ3E
-------------
_,met$$$$$gg. OS: Debian GNU/Linux 13 (trixie) aarch64
,g$$$$$$$$$$$$$$$P. Host: Radxa ZERO 3
,g$$P"" """Y$$.". Board: zero3-aic8800ds2
,$$P' `$$$. Kernel: Linux 6.1.115-vendor-rk35xx
',$$P ,ggs. `$$b: Init System: systemd 257.8-1~deb13u2
`d$$' ,$P"' . $$$ Uptime: 2 mins
$$P d$' , $$P Loadavg: 0.77, 0.40, 0.15
$$: $$. - ,d$$' Processes: 149
$$; Y$b._ _,d$P' Packages: 293 (dpkg)
Y$$. `.`"Y$$$$P"' Shell: bash 5.2.37
`$$b "-.__ Terminal: dropbear
`Y$$b Terminal Size: 184 columns x 50 rows (1472px x 1000px)
`Y$$. Terminal Theme: #E6E6E6 (FG) - #1E1E1E (BG) [Dark]
`$$b. CPU: rk3566 (4) @ 1.80 GHz - 36.7°C
`Y$$b. CPU Usage: 0%
`"Y$b._ GPU: Arm mali-bifrost [Integrated]
`"""" Memory: 217.42 MiB / 961.54 MiB (23%)
Swap: 0 B / 1.06 GiB (0%)
Disk (/): 2.99 GiB / 14.57 GiB (21%) - ext4
Local IP (eth0): 192.168.3.132/16 fe80::6c1c:d9ff:fee0:5f97/64 (6e:1c:d9:e0:5f:97) [Speed 1 Gbps / MTU 1500] <UP,BROADCAST,RUNNING,MULTICAST,LOWER_UP>
DNS: 192.168.88.10 192.168.88.1
Date & Time: 2025-09-16 11:29:51
Locale: C.UTF-8
Weather: +13°C - Light rain shower
Network IO (eth0): 1.79 KiB/s (IN) - 4.06 KiB/s (OUT)
Disk IO (mmcblk1): 16.00 KiB/s (R) - 0 B/s (W)
Physical Disk (mmcblk1): 14.84 GiB [SSD, Fixed]
Version: fastfetch 2.40.4-debug (aarch64)
dmesg output:
dmesgerrors:
dietpi@radxaZ3E:~$ sudo dmesg -l err
[ 12.114253] OF: fdt: Reserved memory: failed to reserve memory for node 'drm-logo@0': base 0x0000000000000000, size 0 MiB
[ 12.114282] OF: fdt: Reserved memory: failed to reserve memory for node 'drm-cubic-lut@0': base 0x0000000000000000, size 0 MiB
[ 13.174801] fiq_debugger fiq_debugger.0: error -ENXIO: IRQ fiq not found
[ 13.174930] fiq_debugger fiq_debugger.0: error -ENXIO: IRQ wakeup not found
[ 13.174976] fiq_debugger_probe: could not install nmi irq handler
[ 14.506158] rockchip-pvtm fde00000.pvtm: failed to retrieve pvtm_tz
[ 14.506501] rockchip-pvtm fde80000.pvtm: failed to retrieve pvtm_tz
[ 14.506794] rockchip-pvtm fde90000.pvtm: failed to retrieve pvtm_tz
[ 14.509718] arm-scmi firmware:scmi: Failed. SCMI protocol 22 not active.
[ 14.540540] rockchip-vop2 fe040000.vop: Failed to get leakage
[ 14.540902] rockchip-vop2 fe040000.vop: error -ENODEV: _opp_set_regulators: no regulator (vop) found
[ 14.541003] rockchip-vop2 fe040000.vop: failed to set opp config
[ 14.541044] rockchip-vop2 fe040000.vop: failed to init opp info
[ 14.543368] dwhdmi-rockchip fe0a0000.hdmi: error -ENXIO: IRQ index 1 not found
[ 14.823669] rk817-battery rk817-battery: Failed to find matching dt id
[ 14.824087] rk817-charger rk817-charger: Failed to find matching dt id
[ 14.838293] OF: graph: no port node found in /i2c@fe5c0000/fusb302@22
[ 14.863077] cpu cpu0: Failed to get specification_serial_number
[ 14.863192] cpu cpu0: Failed to get leakage
[ 14.879409] arm-scmi firmware:scmi: Failed. SCMI protocol 17 not active.
[ 15.022121] mpp_rkvenc fdf40000.rkvenc: Failed to get leakage
[ 15.022245] debugfs: Directory 'fdf40000.rkvenc-venc' with parent 'vdd_logic' already present!
[ 15.027991] mpp_rkvdec2 fdf80200.rkvdec: shared_niu_a is not found!
[ 15.028019] rkvdec2_init:1198: No niu aclk reset resource define
[ 15.028042] mpp_rkvdec2 fdf80200.rkvdec: shared_niu_h is not found!
[ 15.028061] rkvdec2_init:1201: No niu hclk reset resource define
[ 15.028413] mpp_rkvdec2 fdf80200.rkvdec: Failed to get leakage
[ 15.028573] debugfs: Directory 'fdf80200.rkvdec-vdec' with parent 'vdd_logic' already present!
[ 15.031574] rockchip-dmc dmc: Failed to get specification_serial_number
[ 15.031644] rockchip-dmc dmc: Failed to get leakage
[ 15.031763] mali fde60000.gpu: error -ENXIO: IRQ JOB not found
[ 15.031907] mali fde60000.gpu: error -ENXIO: IRQ MMU not found
[ 15.032001] mali fde60000.gpu: error -ENXIO: IRQ GPU not found
[ 15.032092] mali fde60000.gpu: Insufficient register space, will override to the required size
[ 15.032138] mali fde60000.gpu: Register window unavailable
[ 15.032165] mali fde60000.gpu: Failed to map registers
[ 15.032188] mali fde60000.gpu: Register map failed error = -5
[ 15.032209] mali fde60000.gpu: Device initialization failed
[ 15.034260] rockchip-dmc dmc: failed to get vop pn to msch rl
dmesg warnings:
dietpi@radxaZ3E:~$ sudo dmesg -l warn
[ 12.482687] cacheinfo: Unable to detect cache hierarchy for CPU 0
[ 12.491274] cacheinfo: Unable to detect cache hierarchy for CPU 1
[ 12.492951] cacheinfo: Unable to detect cache hierarchy for CPU 2
[ 12.494685] cacheinfo: Unable to detect cache hierarchy for CPU 3
[ 12.635411] KASLR disabled due to lack of seed
[ 14.515560] led_vk2c21_init
=============================================
[ 14.539410] [drm] all windows should be assigned, full plane mask: Cluster0 | Cluster1 | Esmart0 | Esmart1 | Smart0 | Smart1[0x3f], current plane mask: [0x0]
[ 14.539518] [drm] use default plane mask
[ 14.540174] [drm] failed to init overlay plane Cluster0-win1
[ 14.540717] rockchip-vop2 fe040000.vop: Failed to get reg
[ 14.546115] rockchip-drm display-subsystem: failed to parse loader memory
[ 14.552879] cacheinfo: Unable to detect cache hierarchy for CPU 0
[ 14.576712] rk_gmac-dwmac fe010000.ethernet: supply phy not found, using dummy regulator
[ 14.742873] naneng-combphy fe830000.phy: wait phy status ready timeout
[ 14.771545] rk808 0-0020: No cache defaults, reading back from HW
[ 14.823419] rk817-battery: Failed to locate of_node [id: -1]
[ 14.823882] rk817-charger: Failed to locate of_node [id: -1]
[ 14.837121] typec_fusb302 3-0022: supply vbus not found, using dummy regulator
[ 14.876770] dwmmc_rockchip fe2b0000.mmc: No normal pinctrl state
[ 14.876805] dwmmc_rockchip fe2b0000.mmc: No idle pinctrl state
[ 14.876860] dwmmc_rockchip fe2c0000.mmc: No normal pinctrl state
[ 14.876882] dwmmc_rockchip fe2c0000.mmc: No idle pinctrl state
[ 14.886568] SPI driver inv-icm42600-spi has no spi_device_id for invensense,icm42600
[ 14.886620] SPI driver inv-icm42600-spi has no spi_device_id for invensense,icm42602
[ 14.886643] SPI driver inv-icm42600-spi has no spi_device_id for invensense,icm42605
[ 14.886663] SPI driver inv-icm42600-spi has no spi_device_id for invensense,icm42622
[ 15.022701] mpp_rkvenc fdf40000.rkvenc: using default check_rate_volt
[ 15.029154] mpp_rkvdec2 fdf80200.rkvdec: using default check_rate_volt
[ 15.032315] mali: probe of fde60000.gpu failed with error -5
[ 15.082209] rockchip-pm rockchip-suspend: not set pwm-regulator-config
[ 22.064082] phy_rtl8211f_led_fixup in
[ 22.064234] phy_rtl8211f_led_fixup in val=0x0a42
My running services (instaled via dietpi-software):
-
dietpi@radxaZ3E:~$ sudo dietpi-services status DietPi-Services ───────────────────────────────────────────────────── Mode: status [ OK ] DietPi-Services | apache2 active (running) since Tue 2025-09-16 11:28:17 CEST; 4min 6s ago [ OK ] DietPi-Services | filebrowser active (running) since Tue 2025-09-16 11:28:14 CEST; 4min 9s ago [ OK ] DietPi-Services | node-red active (running) since Tue 2025-09-16 11:28:14 CEST; 4min 9s ago [ OK ] DietPi-Services | webmin active (running) since Tue 2025-09-16 11:28:25 CEST; 3min 59s ago [ OK ] DietPi-Services | cron active (running) since Mon 2025-09-15 23:32:36 CEST; 11h ago [ OK ] DietPi-Services | dropbear active (running) since Tue 2025-09-16 11:28:14 CEST; 4min 9s ago [ INFO ] DietPi-Services | dietpi-vpn inactive (dead) [ INFO ] DietPi-Services | dietpi-cloudshell inactive (dead) [ OK ] DietPi-Services | dietpi-dashboard active (running) since Tue 2025-09-16 11:28:14 CEST; 4min 10s ago [ OK ] DietPi-Services | dietpi-ramlog active (exited) since Mon 2025-09-15 23:32:37 CEST; 11h ago [ OK ] DietPi-Services | dietpi-preboot active (exited) since Mon 2025-09-15 23:32:37 CEST; 11h ago [ OK ] DietPi-Services | dietpi-postboot active (exited) since Tue 2025-09-16 11:28:14 CEST; 4min 10s ago [ INFO ] DietPi-Services | dietpi-wifi-monitor inactive (dead)
Question
Since I’m not familiar with Linux kernel stuff, I just want to ask: are these errors known and safe?
Or are there any efforts underway to fix them?
Thank you
Reply from LLM (GPT5):
click to expand
Main problems (bolded short facts)
-
Device-tree nodes reserve 0 MiB (drm-logo, drm-cubic-lut) — indicates incorrect or incomplete reserved-memory entries in the board DT.
-
Multiple “failed to retrieve” / “Failed to get” leakage/spec_serial_number/pvtm_tz/regulator/etc. — drivers expect DT properties or runtime-regulator/SCMI services that are not present.
-
SCMI protocols 17 and 22 not active — firmware/firmware DT binding for SCMI not enabled or firmware doesn’t expose those protocols.
-
Mali GPU probe failed (error -5 / register mapping failed) — likely wrong/regressed register ranges in DT or resource conflict; GPU driver cannot map MMIO.
-
VOP2/HDMI/overlay initialization failures — display DT configuration or regulators/IRQs missing.
-
rk817/rk808 (PMIC) & typec/fusb302/ethernet/mmc pinctrl warnings — missing/incorrect DT nodes or pinctrl states.
-
KASLR disabled due to lack of seed and cacheinfo: Unable to detect cache hierarchy — CPU/DT cache topology not provided in DT or missing ACPI/firmware support (harmless for functionality but notable).
-
fiq_debugger: IRQ fiq/wakeup not found / could not install nmi irq handler — platform doesn’t expose those IRQs expected by the fiq_debugger driver.
Output from chatGPT (more detailed):
click to see output from ChatGPT
CRITICAL + ERROR LEVEL ISSUES
1. Reserved Memory Nodes Failures
Reserved memory: failed to reserve memory for node 'drm-logo@0' / 'drm-cubic-lut@0'
- Cause: Device tree is trying to reserve memory at address
0x0with size0, which is invalid. 
Fix: Edit the DTB or DTS file and either:
-
Correct the
regproperties of these nodes, -
Or remove them if unused.
-
2. FIQ Debugger IRQs Missing
fiq_debugger: error -ENXIO: IRQ fiq/wakeup not found
- Cause: The
fiq_debuggerdriver is enabled, but the required IRQs aren’t defined. - Fix Options:
-
Disable the
fiq_debuggerin the kernel config or device tree if not used. -
Or, define the required IRQs in DT.
-
3. Power/Voltage/Leakage Setup Failures
rockchip-vop2: Failed to get leakage / no regulator (vop) found
mpp_rkvenc/rkvdec2: Failed to get leakage
rockchip-dmc: Failed to get leakage
- Cause: Device tree lacks power regulator definitions or optional leakage calibration nodes.
- These are important for power management but not mandatory for basic operation.
- Fix:
-
Add regulator nodes and bindings in your DTS if available from vendor trees.
-
If you don’t need DVFS (dynamic voltage/freq scaling), you can ignore some of these.
-
4. GPU Initialization Fails Completely
mali fde60000.gpu: IRQ JOB/MMU/GPU not found
mali: probe of fde60000.gpu failed with error -5
- Cause: GPU node in DT is either incomplete or incompatible with the driver.
- Fix:
-
Ensure you’re using the correct DTB for the Radxa Z3E with Mali GPU support.
-
Verify GPU IRQs are defined in the DT.
-
Alternatively, disable the GPU node if unused.
-
5. HDMI and DRM Issues
dwhdmi-rockchip: IRQ index 1 not found
rockchip-drm: failed to parse loader memory
- HDMI IRQs and memory are not defined correctly.
- Fix:
-
Ensure the HDMI node (
fe0a0000.hdmi) and DRM loader memory are correctly described in DT. -
Possibly missing
reserved-memoryorirqfields.
-
6. SCMI Protocols Inactive
arm-scmi: Failed. SCMI protocol 17/22 not active.
- Your firmware doesn’t expose SCMI protocols needed for clocks, power domains, etc.
- Fix:
-
Update U-Boot or TF-A (ARM Trusted Firmware) to a version that supports SCMI.
-
Or disable SCMI in the kernel and rely on legacy methods.
-
7. Battery and Charger DT Mismatch
rk817-battery: Failed to find matching dt id
rk817-charger: Failed to find matching dt id
-
RK817 PMIC is present but device tree doesn’t define its battery/charger correctly.
-
Fix: Ensure you have the correct sub-nodes for the
rk817:
&rk817 {
battery {
compatible = "rockchip,rk817-battery";
...
};
charger {
compatible = "rockchip,rk817-charger";
...
};
};
WARNING LEVEL ISSUES
1. CPU Cache Hierarchy Unknown
cacheinfo: Unable to detect cache hierarchy for CPU X
- Harmless unless you’re doing fine-tuned performance work.
- Might be fixable with updated kernel and DTB.
2. KASLR Disabled
KASLR disabled due to lack of seed
- Kernel address space layout randomization is off due to missing seed (e.g., no
rngortrusted-firmware). - Security warning, not runtime issue. Could be fixed by enabling
CONFIG_RANDOM_AT_BOOT_TIME.
3. Missing pinctrl states for MMC
dwmmc_rockchip: No normal/idle pinctrl state
- May affect SD card / eMMC suspend/resume or timing stability.
- Fix: Define
pinctrl-namesandpinctrl-0,pinctrl-1formmcnodes.
4. SPI IMU Sensor Missing spi_device_id
SPI driver inv-icm42600-spi has no spi_device_id for invensense,icm426XX
- Harmless unless you’re using one of these IMU sensors.
- Fix: Add
spi_device_identries in the driver or overlay.
What’s Probably Fine
-
Ethernet is falling back to dummy regulator — works unless power switching is required.
-
Some
debugfsmessages are noisy but harmless. -
led_vk2c21_initsuggests at least some peripherals are working.
Summary of Fix Strategy
| Issue Type | Action |
|---|---|
| GPU, DRM, HDMI | Use correct DTB for Radxa Z3E / check driver bindings |
| Reserved Memory | Remove or correct zero-sized reserved memory nodes |
| Power Regulator / Leakage | Add optional regulators or ignore if not using DVFS |
| rk817 battery/charger | Add missing DT bindings |
| MMC pinctrl | Add pinctrl states in DT |
| SCMI | Update TF-A/U-Boot or disable SCMI protocols |
| Unused peripherals | Disable in DT to avoid warnings |
