<?xml version="1.0"?>
<rss version="2.0"><channel><title>Rockchip Latest Topics</title><link>https://forum.armbian.com/forum/175-rockchip/</link><description>Rockchip Latest Topics</description><language>en</language><item><title>Firefly video rotation issue</title><link>https://forum.armbian.com/topic/59109-firefly-video-rotation-issue/</link><description><![CDATA[<p>
	Video here: <a href="https://drive.google.com/file/d/1kv2QVMMgRizKrjZIGVVMYK3QxkswTA9K/view?usp=sharing" rel="external nofollow">https://drive.google.com/file/d/1kv2QVMMgRizKrjZIGVVMYK3QxkswTA9K/view?usp=sharing</a><br />
	<br />
	Hi there, I have the following stack:
</p>

<p>
	<strong>Model:</strong> ROC-RK3588S-PC V12 (Linux) <strong><abbr title="System On a Chip"><abbr title="System On a Chip">SoC</abbr></abbr>:</strong> Rockchip RK3588 <strong><abbr title="Graphic processing unit (3D acceleration)"><abbr title="Graphic processing unit (3D acceleration)">GPU</abbr></abbr>:</strong> Mali-G610 (<abbr title="driver for Mali Midgard and Bifrost GPUs"><abbr title="driver for Mali Midgard and Bifrost GPUs">Panfrost</abbr></abbr>/Panfork) <strong>Kernel:</strong> 6.1.0-1025-rockchip <strong>OS:</strong> Ubuntu 24.04.1 <abbr title="Long term support"><abbr title="Long term support">LTS</abbr></abbr> (Joshua-Riek image v2.4.0) <strong>Mesa:</strong> Panfork 23.0.5 (git221210 — December 2022) <strong>Chromium:</strong> 114.0.5735.35 (rkmpp7 from jjriek/rockchip-multimedia PPA) <strong>Display: </strong>HDMI-1, 1920x1080@60Hz
</p>

<p>
	The problem: I'm running a kiosk application in Chromium that plays video fullscreen. The display is physically mounted in portrait mode (9:16), so I need to rotate the output 270°. When rotation is applied, a visible vertical line artifact appears running from top to bottom, approximately 5cm from the right edge of the screen. Without rotation, the image is perfectly clean — no artifacts at all.
</p>

<p>
	 
</p>

<p>
	What I've tried (all failed to fix the issue):
</p>

<ol>
	<li>
		CSS rotation (current method): Using transform: rotate(270deg) on the body element. The line artifact appears consistently.
	</li>
	<li>
		xrandr rotation: xrandr --output HDMI-1 --rotate left — same vertical line artifact appears.
	</li>
	<li>
		Kernel DRM rotation: Added video=HDMI-A-1:1920x1080@60,rotate=270 to kernel cmdline in extlinux.conf. Parameter is visible in /proc/cmdline but has no effect — Rockchip DRM driver does not support the rotate parameter.
	</li>
	<li>
		Chromium flags (tested individually and in combinations): 
		<p>
			<strong>--disable-<abbr title="Graphic processing unit (3D acceleration)"><abbr title="Graphic processing unit (3D acceleration)">gpu</abbr></abbr>-compositing</strong> — moved the line to the center of the screen
		</p>

		<p>
			<strong>--disable-<abbr title="Graphic processing unit (3D acceleration)"><abbr title="Graphic processing unit (3D acceleration)">gpu</abbr></abbr>-rasterization</strong> / --disable-<abbr title="Graphic processing unit (3D acceleration)"><abbr title="Graphic processing unit (3D acceleration)">gpu</abbr></abbr>-vsync — made it worse
		</p>

		<p>
			<strong>--use-gl=egl</strong> — no effect
		</p>

		<p>
			<strong>--enable-<abbr title="Graphic processing unit (3D acceleration)"><abbr title="Graphic processing unit (3D acceleration)">gpu</abbr></abbr>-rasterization --enable-zero-copy</strong> — no effect
		</p>

		<p>
			<strong>--default-tile-width=1920 --default-tile-height=1080</strong> — no effect
		</p>

		<p>
			<strong>--<abbr title="Graphic processing unit (3D acceleration)"><abbr title="Graphic processing unit (3D acceleration)">gpu</abbr></abbr>-rasterization-msaa-sample-count=0</strong> — no effect
		</p>

		<p>
			<strong>--force-device-scale-factor=1</strong> — no effect
		</p>

		<p>
			<strong>--use-gl=angle --use-angle=gles-egl --use-cmd-decoder=passthrough</strong> — crashed Chromium
		</p>
	</li>
	<li>
		CSS <abbr title="Graphic processing unit (3D acceleration)"><abbr title="Graphic processing unit (3D acceleration)">GPU</abbr></abbr> optimization properties: Tested translateZ(0), backface-visibility: hidden, will-change: transform on the rotation container — no effect on the artifact.
	</li>
	<li>
		Chromium 132 upgrade: Installed chromium 132.0.6834.159-1~deb12u1+rkmpp from liujianfeng1994/chromium PPA. The vertical line remained, and video playback became unstable (freezing). Reverted to Chromium 114.
	</li>
	<li>
		Mesa upgrade to Ubuntu noble-updates 25.2.8: Removed Panfork PPA and installed standard Ubuntu Mesa 25.2.8. <abbr title="Graphic processing unit (3D acceleration)"><abbr title="Graphic processing unit (3D acceleration)">GPU</abbr></abbr> fell back to llvmpipe (software rendering) — no <abbr title="driver for Mali Midgard and Bifrost GPUs"><abbr title="driver for Mali Midgard and Bifrost GPUs">Panfrost</abbr></abbr> support for Mali-G610 in standard Mesa. Display showed tearing in the center. Reverted to Panfork 23.0.5.
	</li>
</ol>

<p>
	 
</p>

<p>
	Conclusion: The artifact appears with any rotation method (CSS, xrandr, kernel) and persists across Chromium versions and various <abbr title="Graphic processing unit (3D acceleration)"><abbr title="Graphic processing unit (3D acceleration)">GPU</abbr></abbr> flags. This strongly suggests the issue is in the Panfork Mesa / <abbr title="driver for Mali Midgard and Bifrost GPUs"><abbr title="driver for Mali Midgard and Bifrost GPUs">Panfrost</abbr></abbr> compositing layer when handling rotated output on Mali-G610.
</p>

<p>
	Has anyone encountered this issue? Is there a known fix or workaround? Would upgrading to Panthor (with kernel 6.10+ or the 6.1 backport) potentially resolve this?
</p>

<p>
	Any help would be greatly appreciated.
</p>
]]></description><guid isPermaLink="false">59109</guid><pubDate>Mon, 13 Apr 2026 10:49:49 +0000</pubDate></item><item><title>r8152 2-1.4:1.0 enx646266d00873: NETDEV WATCHDOG: CPU: 0: transmit queue 0 timed out</title><link>https://forum.armbian.com/topic/59007-r8152-2-1410-enx646266d00873-netdev-watchdog-cpu-0-transmit-queue-0-timed-out/</link><description><![CDATA[<p>
	First of all thanks to the people maintaining armbian for helios64. I recently upgraded (well I reinstalled) to trixie and everything mostly runs stable for me.
</p>

<p>
	 
</p>

<p>
	However I have a problem with the 2.5GB adapter. It is connected to a 2.5GB switch and when for example running iperf3 I get proper results close to 2.5 GBit. So in general it seems to be running ok. I have a DLNA server (minidlna) running on that machine and when I stream from my TV (streaming via VLC from my laptop triggers the same problems) the network connection drops for a moment and works again after a few seconds (which you can guess is super annoying when watching something). I am not sure what exactly is triggering this. most of the time the network is super stable but during streaming I get hickups.
</p>

<p>
	 
</p>

<p>
	This is what my kernel log spits out when this is happending:
</p>

<p>
	 
</p>

<p>
	```
</p>

<p>
	Apr 09 17:45:54 hermann-walter kernel: xhci-hcd xhci-hcd.0.auto: Event TRB for slot 4 ep 3 with no TDs queued<br />
	Apr 09 17:45:54 hermann-walter kernel: xhci-hcd xhci-hcd.0.auto: Event TRB for slot 4 ep 3 with no TDs queued<br />
	Apr 09 17:45:54 hermann-walter kernel: xhci-hcd xhci-hcd.0.auto: Event TRB for slot 4 ep 3 with no TDs queued<br />
	Apr 09 17:45:54 hermann-walter kernel: xhci-hcd xhci-hcd.0.auto: Event TRB for slot 4 ep 3 with no TDs queued<br />
	Apr 09 17:45:54 hermann-walter kernel: xhci-hcd xhci-hcd.0.auto: Event dma 0x00000000053f8f10 for ep 3 status 1 not part of TD at 00000000053f8ed0 - 00000000053f8ed0<br />
	Apr 09 17:45:54 hermann-walter kernel: xhci-hcd xhci-hcd.0.auto: Event dma 0x00000000053f8f20 for ep 3 status 1 not part of TD at 00000000053f8ed0 - 00000000053f8ed0<br />
	Apr 09 17:45:54 hermann-walter kernel: xhci-hcd xhci-hcd.0.auto: Event dma 0x00000000053f8f30 for ep 3 status 1 not part of TD at 00000000053f8ed0 - 00000000053f8ed0<br />
	Apr 09 17:45:54 hermann-walter kernel: xhci-hcd xhci-hcd.0.auto: Event dma 0x00000000053f8f40 for ep 3 status 1 not part of TD at 00000000053f8ed0 - 00000000053f8ed0<br />
	Apr 09 17:45:54 hermann-walter kernel: xhci-hcd xhci-hcd.0.auto: Event dma 0x00000000053f8f50 for ep 3 status 1 not part of TD at 00000000053f8ed0 - 00000000053f8ed0<br />
	Apr 09 17:45:54 hermann-walter kernel: xhci-hcd xhci-hcd.0.auto: Event dma 0x00000000053f8f60 for ep 3 status 1 not part of TD at 00000000053f8ed0 - 00000000053f8ed0<br />
	Apr 09 17:45:54 hermann-walter kernel: xhci-hcd xhci-hcd.0.auto: Event dma 0x00000000053f8f70 for ep 3 status 1 not part of TD at 00000000053f8ed0 - 00000000053f8ed0<br />
	Apr 09 17:45:54 hermann-walter kernel: xhci-hcd xhci-hcd.0.auto: Event dma 0x00000000053f8f80 for ep 3 status 1 not part of TD at 00000000053f8ed0 - 00000000053f8ed0<br />
	Apr 09 17:45:54 hermann-walter kernel: xhci-hcd xhci-hcd.0.auto: Event dma 0x00000000053f8f90 for ep 3 status 1 not part of TD at 00000000053f8ed0 - 00000000053f8ed0<br />
	Apr 09 17:45:54 hermann-walter kernel: xhci-hcd xhci-hcd.0.auto: Event dma 0x00000000053f8fa0 for ep 3 status 1 not part of TD at 00000000053f8ed0 - 00000000053f8ed0<br />
	Apr 09 17:45:59 hermann-walter kernel: r8152 2-1.4:1.0 enx646266d00873: NETDEV WATCHDOG: CPU: 0: transmit queue 0 timed out 5152 ms<br />
	Apr 09 17:45:59 hermann-walter kernel: r8152 2-1.4:1.0 enx646266d00873: Tx timeout<br />
	Apr 09 17:46:00 hermann-walter kernel: r8152 2-1.4:1.0 enx646266d00873: Tx status -2<br />
	Apr 09 17:46:00 hermann-walter kernel: r8152 2-1.4:1.0 enx646266d00873: Tx status -2<br />
	Apr 09 17:46:00 hermann-walter kernel: r8152 2-1.4:1.0 enx646266d00873: Tx status -2<br />
	Apr 09 17:46:00 hermann-walter kernel: r8152 2-1.4:1.0 enx646266d00873: Tx status -2<br />
	Apr 09 17:46:02 hermann-walter kernel: r8152-cfgselector 2-1.4: reset SuperSpeed USB device number 3 using xhci-hcd<br />
	```<br />
	<br />
	the usb related messages are not always there but the r8152 related messages are always there.
</p>

<p>
	 
</p>

<p>
	I found a similar problem here: <a href="https://github.com/openwrt/openwrt/issues/22130" rel="external nofollow">https://github.com/openwrt/openwrt/issues/22130<br />
	<br />
	I tried replacing the firmware but that </a>didn't help and I later found out that the helios64 uses a different firmware so that explains why it didn't help:
</p>

<p>
	 
</p>

<p>
	```
</p>

<p>
	Apr 10 05:48:30 hermann-walter kernel: r8152 2-1.4:1.0: Loaded FW: rtl_nic/rtl8156a-2.fw, sha256: 7b50f4a307bde7b3f384935537c4d9705457fa42613eb0003ffbc4e19461a1e0<br />
	Apr 10 05:48:30 hermann-walter kernel: r8152 2-1.4:1.0: Loaded FW: rtl_nic/rtl8156a-2.fw, sha256: 7b50f4a307bde7b3f384935537c4d9705457fa42613eb0003ffbc4e19461a1e0<br />
	```
</p>

<p>
	 
</p>

<p>
	does anybody know what is going on? I am quite sure that the problem wasn't there before the upgrade (but I might be mistaken because I only started observing the helios64 again after the upgrade. also it seems to be related to the amount of network traffic going on. i.e. lower bitrate streams seem to not trigger the problem).
</p>

<p>
	 
</p>

<p>
	Streaming via the 1GBit NIC is working fine.
</p>
]]></description><guid isPermaLink="false">59007</guid><pubDate>Fri, 10 Apr 2026 06:50:57 +0000</pubDate></item><item><title>Armbian_24.11.2_Orangepi5_noble_current_6.12.0-kisak NPU driver version</title><link>https://forum.armbian.com/topic/49632-armbian_24112_orangepi5_noble_current_6120-kisak-npu-driver-version/</link><description><![CDATA[<p>
	Hello,
</p>

<p>
	 
</p>

<p>
	I just need to check the NPU driver version on my Orange Pi 5 with Armbian_24.11.2_Orangepi5_noble_current_6.12.0-kisak
</p>

<p>
	 
</p>

<p>
	My command is 
</p>

<pre class="ipsCode prettyprint prettyprinted"><span class="pln">sudo cat </span><span class="pun">/</span><span class="pln">sys</span><span class="pun">/</span><span class="pln">kernel</span><span class="pun">/</span><span class="pln">debug</span><span class="pun">/</span><span class="pln">rknpu</span><span class="pun">/</span><span class="pln">version</span></pre>

<p>
	 
</p>

<p>
	but error No such file or directory
</p>

<p>
	 
</p>

<p>
	Is there NPU driver on this Armbian OS?
</p>
]]></description><guid isPermaLink="false">49632</guid><pubDate>Wed, 05 Feb 2025 07:03:25 +0000</pubDate></item><item><title>Nanopim4v2 sdcard question</title><link>https://forum.armbian.com/topic/58994-nanopim4v2-sdcard-question/</link><description><![CDATA[<p>
	I flashed a home built nanpim4v2  image to two brand new Silicon Power 32GB sdcards and they wont boot whereas SanDisk 32GB boot OK can anyone explain why ?
</p>

<p>
	 
</p>
]]></description><guid isPermaLink="false">58994</guid><pubDate>Thu, 09 Apr 2026 07:49:43 +0000</pubDate></item><item><title>Adding the edge kernel to Rock 2F/2A</title><link>https://forum.armbian.com/topic/56543-adding-the-edge-kernel-to-rock-2f2a/</link><description><![CDATA[<p>
	Hello,
</p>

<p>
	 
</p>

<p>
	These boards (Radxa Rock 2F and Rock 2A) have standard support so there should probably be a forum section for them. In its absence, I created this topic in the section for the most "similar" board.
</p>

<p>
	 
</p>

<p>
	Currently, we only have the `vendor` kernel available for both. It seems that both of them have been mainlined in 6.18, as seen here for example: <a href="https://www.cnx-software.com/2025/12/01/linux-6-18-release-main-changes-arm-risc-v-and-mips-architectures/" rel="external nofollow">https://www.cnx-software.com/2025/12/01/linux-6-18-release-main-changes-arm-risc-v-and-mips-architectures/</a> 
</p>

<p>
	 
</p>

<p>
	The config file for the board currently looks like this:
</p>

<p>
	 
</p>

<pre class="ipsCode prettyprint lang-html prettyprinted"><span class="pln"># Rockchip RK3528 quad core 1-4GB SoC WIFI/BT 0-32GB eMMC
BOARD_NAME="ROCK 2F"
BOARDFAMILY="rk35xx"
BOOTCONFIG="rock-2-rk3528_defconfig"
BOARD_MAINTAINER="CodeChenL"
KERNEL_TARGET="vendor"
KERNEL_TEST_TARGET="vendor"
FULL_DESKTOP="yes"
BOOT_LOGO="desktop"
BOOT_FDT_FILE="rockchip/rk3528-rock-2f.dtb"
BOOT_SCENARIO="spl-blobs"
IMAGE_PARTITION_TABLE="gpt"
enable_extension "radxa-aic8800"
AIC8800_TYPE="usb"</span></pre>

<p>
	 
</p>

<p>
	I tried just adding "edge" in the KERNEL_TARGET line and building an image but this won't be enough to make it boot, will it? Any tutorials on how to get them to work on mainline?
</p>
]]></description><guid isPermaLink="false">56543</guid><pubDate>Tue, 02 Dec 2025 22:36:26 +0000</pubDate></item><item><title>Industrial android board - RK3288 (possible EVB)</title><link>https://forum.armbian.com/topic/58577-industrial-android-board-rk3288-possible-evb/</link><description><![CDATA[<p>
	Hi there!<br />
	<br />
	<br />
	I've got 2 of these industrial android boards (s2809-mb-v1.8c) and I've been trying to get armbian running on the. For a while but so far no success.<br />
	These 2 boards were sold as being tinker boards but I believe that they are EVBs instead.
</p>

<p>
	 
</p>

<p>
	Here are some photos:
</p>

<p>
	<a href="https://ibb.co/4wTm20s9" rel="external nofollow">https://ibb.co/4wTm20s9</a><br />
	<a href="https://ibb.co/Z6PfvZCr" rel="external nofollow">https://ibb.co/Z6PfvZCr</a><br />
	<a href="https://ibb.co/HTFWLKTS" rel="external nofollow">https://ibb.co/HTFWLKTS</a>
</p>

<p>
	 
</p>

<p>
	I have also managed to find a link to the Chinese seller:
</p>

<p>
	<a href="https://m.globalsources.com/product/quad-core-board_1195354789f.htm" rel="external nofollow">https://m.globalsources.com/product/quad-core-board_1195354789f.htm</a>
</p>

<p>
	<br />
	<br />
	Debug method: UART2 (because they don't have HDMI only LVDS and EDP ports)
</p>

<p>
	PMIC: RK808<br />
	<br />
	So far trying to run them on the latest armbian 26 and 25 gets stuck at Starting Kernel.<br />
	<br />
	Ive managed to find a version 20 for the miqi board that loads kernel and boots into armbian bullseye but stops before login using a single core only and only 512mb of ram, anything beyond that just never starts the kernel using tinker and tinker-s DTBs.<br />
	<br />
	I have also managed to get a full dump of a current android image that is running correctly on one of the board and extracted: loader, kernel, <abbr title="Device tree blob"><abbr title="Device tree blob">dtb</abbr></abbr> from the partitions.<br />
	Extracting the images was painful cause none of the <abbr title="Rockchip"><abbr title="Rockchip">rk</abbr></abbr> (linux rkdeveloptool, rkdev and rkandroidtool) methods worked.. only through uboot so that was painful to get 16mb parts from some of the images and join them all.<br />
	<br />
	<br />
	Has anyone ever encountered any of these boards?<br />
	Maybe anyone has an idea on how to get them up and running?<br />
	<br />
	<br />
	Thanks for your help and sorry if this post is under the incorrect forum.
</p>
]]></description><guid isPermaLink="false">58577</guid><pubDate>Wed, 18 Mar 2026 09:16:24 +0000</pubDate></item><item><title>Armbian for Bobcat 300 29x Helium Miner</title><link>https://forum.armbian.com/topic/57321-armbian-for-bobcat-300-29x-helium-miner/</link><description><![CDATA[<p>
	<br />
	<img class="ipsImage ipsImage_thumbnailed" data-fileid="15767" data-ratio="94.07" width="405" alt="image.png.a46ff7d8c9f3197e821e6647e744ea17.png" src="https://forum.armbian.com/uploads/monthly_2026_01/image.png.a46ff7d8c9f3197e821e6647e744ea17.png" /><br />
	<br />
	<br />
	After a ton of time porting the <abbr title="Device tree source">dts</abbr> for modern kernels, i have a working release for the Bobcat 300 29X Variant<br />
	<br />
	<strong>To compile</strong><br />
	<br />
	<a href="https://github.com/sicXnull/armbian-build/tree/Bobcat-29x" rel="external nofollow">https://github.com/sicXnull/armbian-build/tree/Bobcat-29x</a><br />
	<br />
	.
</p>

<pre class="ipsCode prettyprint lang-html prettyprinted"><span class="pln">./compile.sh build BOARD=bobcat-29x BRANCH=current BUILD_DESKTOP=no BUILD_MINIMAL=yes  EXPERT=yes KERNEL_BTF=no KERNEL_CONFIGURE=NO KERNEL_GIT=shallow RELEASE=bookworm</span></pre>

<p>
	<br />
	<strong>Link to Prebuilt</strong><br />
	<br />
	<a href="https://github.com/sicXnull/armbian-build/releases/download/1.0/Armbian-unofficial_26.02.0-trunk_Bobcat-29x_bookworm_current_6.18.4.img.xz" rel="external nofollow">Armbian-unofficial_26.02.0-trunk_Bobcat-29x_bookworm_current_6.18.4.img.xz</a>
</p>

<p>
	<br />
	First check to see if you have a compatible version. Flip the unit over and check the serial number. It will start with G290 or 295. <strong><u>This does not work on 28 or 285.</u></strong>
</p>

<p>
	<br />
	<img class="ipsImage ipsImage_thumbnailed" data-fileid="15770" data-ratio="82.24" width="428" alt="image.png.cb77007d858d67e3eb1dcf1bcf560c12.png" src="https://forum.armbian.com/uploads/monthly_2026_01/image.png.cb77007d858d67e3eb1dcf1bcf560c12.png" /><br />
	<br />
	<strong>How to Flash</strong><br />
	1) Install <a href="https://wiki.radxa.com/Rock3/install/rockchip-flash-tools" rel="external nofollow">Rockchip Flash Tools</a> <br />
	2) Download bootloader (rk356x_spl_loader_ddr1056_v1.10.111.bin) attached <a href="https://dl.radxa.com/rock3/images/loader/rock-3a/rk356x_spl_loader_ddr1056_v1.10.111.bin" rel="external nofollow">here</a>. <br />
	3) Boot device into LOADER mode. 
</p>

<ul>
	<li>
		Plug USB Cable in to back of the unit, powered off. 
	</li>
	<li>
		Open the device. With it powered on hold the reset button for 1 second, then immediately let off and hold the recovery button down until the PC recognizes you in LOADER mode
	</li>
</ul>

<p>
	<img class="ipsImage ipsImage_thumbnailed" data-fileid="15769" data-ratio="144.77" width="449" alt="image.png.ed5651760e463b427a5debf12d7b1374.png" src="https://forum.armbian.com/uploads/monthly_2026_01/image.png.ed5651760e463b427a5debf12d7b1374.png" />
</p>

<p>
	<span></span>
</p>

<p>
	4) Follow the flash procedure found <a href="https://docs.radxa.com/en/zero/zero3/low-level-dev/rkdevtool" rel="external nofollow">here</a>. 
</p>

<p>
	 
</p>

<p>
	<strong>WARNING</strong>
</p>

<p>
	 
</p>

<p>
	<b>While I2C/Spidev is functional, i did not install Helium or the Lora packet forwarder for testing. Flash this image at your own risk if you still wish to use helium mining. </b>
</p>

<p>
	<br />
	 
</p>
<p>
<a class="ipsAttachLink" href="https://forum.armbian.com/applications/core/interface/file/attachment.php?id=15773&amp;key=9d4a4642185810c3880d44dae9d72f28" data-fileExt='bin' data-fileid='15773' data-filekey='9d4a4642185810c3880d44dae9d72f28'>rk356x_spl_loader_ddr1056_v1.10.111.bin</a></p>]]></description><guid isPermaLink="false">57321</guid><pubDate>Sat, 10 Jan 2026 00:25:53 +0000</pubDate></item><item><title>Raxda Display 8 HD on Radxa ROCK 3A</title><link>https://forum.armbian.com/topic/57899-raxda-display-8-hd-on-radxa-rock-3a/</link><description><![CDATA[<p>
	I am trying to setup <a href="https://radxa.com/products/accessories/display-8hd" rel="external nofollow">Raxda Display 8 HD</a> with  <a href="https://radxa.com/products/rock3/3a" rel="external nofollow">Radxa ROCK 3A</a>. On official <a href="https://github.com/radxa-build/rock-3a/releases" rel="external nofollow">Radxa OS</a>, I used <a href="https://docs.radxa.com/en/rock3/rock3a/system-config/rsetup" rel="external nofollow">Rsetup tool</a> to setup overlay for `Radxa Display 8 HD' using <a href="https://docs.radxa.com/en/accessories/display/lcd-8-hd/lcd-8-hd-usage?mode=15pin" rel="external nofollow">official guide</a>. 
</p>

<p>
	How can I do same on <a href="https://www.armbian.com/rock-3a/" rel="external nofollow">Dedicated applications images with Armbian Linux v6.12 ( Home Assistant )</a> ? 
</p>

<p>
	 
</p>

<p>
	I have read <a href="https://docs.armbian.com/User-Guide_Armbian_overlays/" rel="external nofollow">Device Tree overlays guide</a> on armbian docs but I can't find overlay for lcd display in files:
</p>

<p>
	 
</p>

<p><a href="https://forum.armbian.com/uploads/monthly_2026_02/Screenshot2026-02-07at19_06_07.png.bfe7d8f5381f851554130c64d2e5550f.png" class="ipsAttachLink ipsAttachLink_image" ><img data-fileid="16012" src="https://forum.armbian.com/uploads/monthly_2026_02/Screenshot2026-02-07at19_06_07.thumb.png.974ba3027d787fcb9449859591aac4dc.png" data-ratio="103.16" width="727" class="ipsImage ipsImage_thumbnailed" alt="Screenshot 2026-02-07 at 19.06.07.png"></a></p>]]></description><guid isPermaLink="false">57899</guid><pubDate>Sat, 07 Feb 2026 15:19:08 +0000</pubDate></item><item><title><![CDATA[Orange PI 5 (b & +) , RK3588(s) USB thread]]></title><link>https://forum.armbian.com/topic/34726-orange-pi-5-b-rk3588s-usb-thread/</link><description><![CDATA[<p>
	Since I am interested in the connection ability, I figured the info we gather should go into ONE thread. I have tried to build new kernels, but can only see USB controllers and devices two ports.
</p>

<p>
	 
</p>

<p>
	I have seen a lot of work by Sebasitian Reichel @ Collabora, and his patches, but these do not seem to have the desired result on my test board. Orange PI 5.
</p>

<p>
	 
</p>

<p>
	There seems to be an issue with the port mux,  FUSB302, that either connects the last USB to the "vertical" port or to the "USB C" connector.
</p>

<p>
	 
</p>

<p>
	I will comment my findings and attempts to correct this in this thread, and think we could find out where we are if you add your findings, successes and failures,
</p>

<p>
	rather than cluttering everywhere
</p>

<p>
	 
</p>

<p>
	Regards,
</p>

<p>
	 
</p>

<p>
	Gullik
</p>

<p>
	 
</p>

<p>
	 
</p>

<p>
	 
</p>

<p>
	 
</p>
]]></description><guid isPermaLink="false">34726</guid><pubDate>Sat, 17 Feb 2024 12:59:43 +0000</pubDate></item><item><title>[OrangePi-5-Pro] Fan not working.</title><link>https://forum.armbian.com/topic/58666-orangepi-5-pro-fan-not-working/</link><description><![CDATA[<p>
	Anyone got the dedicated Fan header working correctly?<br />
	It won't spin at all.<br />
	Enabled the fanctrl overlay. changed pwm rate,the fan won't budge..<br />
	Tried stress the CPU but this only  cause shutdown
</p>

<p>
	 
</p>
]]></description><guid isPermaLink="false">58666</guid><pubDate>Mon, 23 Mar 2026 14:50:00 +0000</pubDate></item><item><title>[NanoPi M4V2] Lost network connection randomly after upgrading to 6.18.10 kernel</title><link>https://forum.armbian.com/topic/58645-nanopi-m4v2-lost-network-connection-randomly-after-upgrading-to-61810-kernel/</link><description><![CDATA[<p>
	Sorry I'm not able to find the sub category for M4V2 so I chose R4S instead. But please keep in mind that this is a bug report for NanoPi M4V2.
</p>

<p>
	 
</p>

<p>
	So my box has been running well for 5 years without any issue, through multiple system upgrade from armbian buster to trixie. However after I upgrade the kernel from 6.12.58 to 6.18.10 just a couple of days ago, the system started to have some weird behavior. The main symptom is that I'll lose the network connection from the box once it starts up, and it could happen after just a few minutes, or a couple of hours. I have to power cycle the box to get it back online as I don't have any peripherals, and soon I will lose the connection again.
</p>

<p>
	 
</p>

<p>
	Other symptoms I've observed so far:
</p>

<p>
	- Once I lost the connection and powered cycle the box, the timestamp in the log looks confusing. Somehow the system clock paused at the moment when system froze. When it boots up, there could be a large gap between the NTP server and it will have to sync up, and I don't even seem to be able to find any logs before this reboot
</p>

<p>
	- The line `fdtfile=rockchip/rk3399-nanopi-m4v2.<abbr title="Device tree blob"><abbr title="Device tree blob">dtb</abbr></abbr>` in `/boot/armbianEnv.txt` looks to be missing, so I added it back but it didn't fix the issue
</p>

<p>
	 
</p>

<p>
	Eventually I downgraded to 6.12.58 with armbian-config, by timing the time window between the bootup and system freeze. After that the issue seems to be gone. Please find the results for `armbianmonitor -u` at <a href="https://paste.armbian.com/werujijedo" rel="external nofollow">https://paste.armbian.com/werujijedo</a>
</p>

<p>
	 
</p>

<p>
	For those who has the same model as mine, please think twice before upgrading. Do backup your data if you'd like to take the risk.
</p>
]]></description><guid isPermaLink="false">58645</guid><pubDate>Sun, 22 Mar 2026 22:36:37 +0000</pubDate></item><item><title>Nanopi Neo3 Plus (rk3528, new March 2026)</title><link>https://forum.armbian.com/topic/58743-nanopi-neo3-plus-rk3528-new-march-2026/</link><description><![CDATA[<p>
	Hi,
</p>

<p>
	I have started to work on a Nanopi Neo3 Plus image (rk3528-based, similar to Nanopi Zero2), announced early March 2026.
</p>

<p>
	Created a new .<abbr title="Community supported Chip - no official support"><abbr title="Community supported Chip - no official support">csc</abbr></abbr> file, used the Nanopi Zero2 as a template. Built it with the vendor version.
</p>

<p>
	Built it with the vendor kernel., but added the "dt" directory with the rk3528-nanopi-rev02.<abbr title="Device tree source"><abbr title="Device tree source">dts</abbr></abbr> to be "automatically" added to the <abbr title="Device tree source"><abbr title="Device tree source">dts</abbr></abbr> directory and Makefile.
</p>

<p>
	The base console version seems to work ok when I generate a bookworm image.
</p>

<p>
	As I currently only need u-boot, kernel and <abbr title="Device tree blob"><abbr title="Device tree blob">dtb</abbr></abbr>'s to build my own OS (Volumio, volumio.org), it works for me.
</p>

<p>
	 
</p>

<p>
	Of course, I would like to contribute my work (and support it?), but how do I proceed?
</p>

<p>
	I used Armbian's kernel and u-boot build a lot, but not done this before.
</p>
]]></description><guid isPermaLink="false">58743</guid><pubDate>Thu, 26 Mar 2026 00:05:35 +0000</pubDate></item><item><title>cm3588 overlay for fan speed change</title><link>https://forum.armbian.com/topic/48705-cm3588-overlay-for-fan-speed-change/</link><description><![CDATA[<p>
	Hi,
</p>

<p>
	I have installed the latest image <a href="https://www.armbian.com/nanopc-cm3588-nas/" rel="external nofollow">"Minimal/IOT images with Armbian Linux v6.12" </a>with the mainline Kernel. Many thanks<br />
	<a contenteditable="false" data-ipshover="" data-ipshover-target="https://forum.armbian.com/profile/212389-colorfulrhino/?do=hovercard" data-mentionid="212389" href="https://forum.armbian.com/profile/212389-colorfulrhino/" rel="">@ColorfulRhino</a> , <a contenteditable="false" data-ipshover="" data-ipshover-target="https://forum.armbian.com/profile/200522-amazingfate/?do=hovercard" data-mentionid="200522" href="https://forum.armbian.com/profile/200522-amazingfate/" rel="">@amazingfate</a> and many others for their hard  work.
</p>

<p>
	 
</p>

<p>
	I have a board with 32GB RAM and 4x NVMe and it is working with HDMI, USB and network. I have installed XFCE on top by my own.
</p>

<p>
	<br />
	Some parts currently not working (what I have seen so far):
</p>

<p>
	* second HDMI
</p>

<p>
	* HDMI audio
</p>

<p>
	* sensor controlled fan speed
</p>

<p>
	 
</p>

<p>
	This seems to be on the <a href="https://www.cnx-software.com/2024/12/21/rockchip-rk3588-mainline-linux-support-current-status-and-future-work-for-2025/#future-work-hdmi-mipi-dsi-npu" rel="external nofollow">roadmap for 2025</a> for the upstream Kernel.
</p>

<p>
	 
</p>

<p>
	For the fan control I currently use my own overlay and want to share it.<br />
	<br />
	 
</p>

<pre class="ipsCode prettyprint lang-c prettyprinted"><span class="pun">/</span><span class="pln">dts</span><span class="pun">-</span><span class="pln">v1</span><span class="pun">/;</span><span class="pln">
</span><span class="pun">/</span><span class="pln">plugin</span><span class="pun">/;</span><span class="pln">

</span><span class="pun">/</span><span class="pln"> </span><span class="pun">{</span><span class="pln">
	</span><span class="com">/* our pwm-fan comes with 6 cooling levels (0-5) in relation to 255 &lt;0 50 80 120 160 220&gt; */</span><span class="pln">
	</span><span class="com">/* this overlay use the sensors of big core 0 to control cooling by the fan */</span><span class="pln">
	</span><span class="com">/* add new trips for active cooling */</span><span class="pln">
	fragment@0 </span><span class="pun">{</span><span class="pln">
		target</span><span class="pun">-</span><span class="pln">path </span><span class="pun">=</span><span class="pln"> </span><span class="str">"/thermal-zones/bigcore0-thermal/trips"</span><span class="pun">;</span><span class="pln">

		__overlay__ </span><span class="pun">{</span><span class="pln">
			bigcore0</span><span class="pun">-</span><span class="pln">active1 </span><span class="pun">{</span><span class="pln">
				</span><span class="com">/* 55 degree with hysteresis of 5 deg */</span><span class="pln">
				temperature </span><span class="pun">=</span><span class="pln"> </span><span class="pun">&lt;</span><span class="lit">55000</span><span class="pun">&gt;;</span><span class="pln">
				hysteresis </span><span class="pun">=</span><span class="pln"> </span><span class="pun">&lt;</span><span class="lit">5000</span><span class="pun">&gt;;</span><span class="pln">
				type </span><span class="pun">=</span><span class="pln"> </span><span class="str">"active"</span><span class="pun">;</span><span class="pln">
				</span><span class="com">// internal phandles use a small integer to be able to reference</span><span class="pln">
				phandle </span><span class="pun">=</span><span class="pln"> </span><span class="pun">&lt;</span><span class="lit">0x00000001</span><span class="pun">&gt;;</span><span class="pln">
			</span><span class="pun">};</span><span class="pln">
			
			bigcore0</span><span class="pun">-</span><span class="pln">active2 </span><span class="pun">{</span><span class="pln">
				</span><span class="com">/* 60 degree with hysteresis of 2 deg */</span><span class="pln">
				temperature </span><span class="pun">=</span><span class="pln"> </span><span class="pun">&lt;</span><span class="lit">60000</span><span class="pun">&gt;;</span><span class="pln">
				hysteresis </span><span class="pun">=</span><span class="pln"> </span><span class="pun">&lt;</span><span class="lit">2000</span><span class="pun">&gt;;</span><span class="pln">
				type </span><span class="pun">=</span><span class="pln"> </span><span class="str">"active"</span><span class="pun">;</span><span class="pln">
				</span><span class="com">// internal phandles use a small integer to be able to reference</span><span class="pln">
				phandle </span><span class="pun">=</span><span class="pln"> </span><span class="pun">&lt;</span><span class="lit">0x00000002</span><span class="pun">&gt;;</span><span class="pln">
			</span><span class="pun">};</span><span class="pln">
		</span><span class="pun">};</span><span class="pln">
	</span><span class="pun">};</span><span class="pln">
	
	</span><span class="com">/* add cooling maps to use the new trips by the pwm-fan with level 0-5 */</span><span class="pln">
	fragment@1 </span><span class="pun">{</span><span class="pln">
		target</span><span class="pun">-</span><span class="pln">path </span><span class="pun">=</span><span class="pln"> </span><span class="str">"/thermal-zones/bigcore0-thermal/cooling-maps"</span><span class="pun">;</span><span class="pln">

		__overlay__ </span><span class="pun">{</span><span class="pln">
			map1 </span><span class="pun">{</span><span class="pln">
				trip </span><span class="pun">=</span><span class="pln"> </span><span class="pun">&lt;</span><span class="lit">0x00000001</span><span class="pun">&gt;;</span><span class="pln">
				cooling</span><span class="pun">-</span><span class="pln">device </span><span class="pun">=</span><span class="pln"> </span><span class="pun">&lt;</span><span class="lit">0xffffffff</span><span class="pln"> </span><span class="lit">0</span><span class="pln"> </span><span class="lit">1</span><span class="pun">&gt;;</span><span class="pln">
			</span><span class="pun">};</span><span class="pln">

			map2 </span><span class="pun">{</span><span class="pln">
				trip </span><span class="pun">=</span><span class="pln"> </span><span class="pun">&lt;</span><span class="lit">0x00000002</span><span class="pun">&gt;;</span><span class="pln">
				cooling</span><span class="pun">-</span><span class="pln">device </span><span class="pun">=</span><span class="pln"> </span><span class="pun">&lt;</span><span class="lit">0xffffffff</span><span class="pln"> </span><span class="lit">2</span><span class="pln"> </span><span class="lit">5</span><span class="pun">&gt;;</span><span class="pln">
			</span><span class="pun">};</span><span class="pln">
		</span><span class="pun">};</span><span class="pln">
	</span><span class="pun">};</span><span class="pln">
	
	</span><span class="com">/* we need to poll, because in interrupt mode the fan will not stop */</span><span class="pln">
	</span><span class="com">/* alternatively we can use type="passive", a poll interval of 250 ms is already defined for passive */</span><span class="pln">
	fragment@2 </span><span class="pun">{</span><span class="pln">
		target</span><span class="pun">-</span><span class="pln">path </span><span class="pun">=</span><span class="pln"> </span><span class="str">"/thermal-zones/bigcore0-thermal"</span><span class="pun">;</span><span class="pln">

		__overlay__ </span><span class="pun">{</span><span class="pln">
			</span><span class="com">/* for active cooling, in milliseconds */</span><span class="pln">
			polling</span><span class="pun">-</span><span class="pln">delay </span><span class="pun">=</span><span class="pln"> </span><span class="pun">&lt;</span><span class="lit">2000</span><span class="pun">&gt;;</span><span class="pln">
		</span><span class="pun">};</span><span class="pln">
	</span><span class="pun">};</span><span class="pln">

	</span><span class="com">/* adjust the original fan levels &lt;0 50 80 120 160 220&gt; a bit */</span><span class="pln">
	</span><span class="com">/* the fan starts rotating at 40-45, 45 is sufficient to keep &lt;50°C at normal operation */</span><span class="pln">
	fragment@3 </span><span class="pun">{</span><span class="pln">
		target </span><span class="pun">=</span><span class="pln"> </span><span class="pun">&lt;</span><span class="lit">0xffffffff</span><span class="pun">&gt;;</span><span class="pln">
		__overlay__ </span><span class="pun">{</span><span class="pln">
			cooling</span><span class="pun">-</span><span class="pln">levels </span><span class="pun">=</span><span class="pln"> </span><span class="pun">&lt;</span><span class="lit">0</span><span class="pln"> </span><span class="lit">45</span><span class="pln"> </span><span class="lit">80</span><span class="pln"> </span><span class="lit">120</span><span class="pln"> </span><span class="lit">160</span><span class="pln"> </span><span class="lit">255</span><span class="pun">&gt;;</span><span class="pln">
		</span><span class="pun">};</span><span class="pln">
	</span><span class="pun">};</span><span class="pln">

	__fixups__ </span><span class="pun">{</span><span class="pln">
		fan </span><span class="pun">=</span><span class="pln"> </span><span class="str">"/fragment@1/__overlay__/map1:cooling-device:0"</span><span class="pun">,</span><span class="pln"> </span><span class="str">"/fragment@1/__overlay__/map2:cooling-device:0"</span><span class="pun">,</span><span class="pln"> </span><span class="str">"/fragment@3:target:0"</span><span class="pun">;</span><span class="pln">
	</span><span class="pun">};</span><span class="pln">
	
	</span><span class="com">// to adjust finally the internal references</span><span class="pln">
	__local_fixups__ </span><span class="pun">{</span><span class="pln">
		fragment@1 </span><span class="pun">{</span><span class="pln">
			__overlay__ </span><span class="pun">{</span><span class="pln">
				map1 </span><span class="pun">{</span><span class="pln">
					trip </span><span class="pun">=</span><span class="pln"> </span><span class="pun">&lt;</span><span class="lit">0x00000000</span><span class="pun">&gt;;</span><span class="pln">
				</span><span class="pun">};</span><span class="pln">

				map2 </span><span class="pun">{</span><span class="pln">
					trip </span><span class="pun">=</span><span class="pln"> </span><span class="pun">&lt;</span><span class="lit">0x00000000</span><span class="pun">&gt;;</span><span class="pln">
				</span><span class="pun">};</span><span class="pln">

			</span><span class="pun">};</span><span class="pln">
		</span><span class="pun">};</span><span class="pln">
	</span><span class="pun">};</span><span class="pln">
</span><span class="pun">};</span></pre>

<p>
	 
</p>
]]></description><guid isPermaLink="false">48705</guid><pubDate>Mon, 30 Dec 2024 09:16:02 +0000</pubDate></item><item><title>Cannot run sway with hardware acceleration after compiling the latest mesa.</title><link>https://forum.armbian.com/topic/58702-cannot-run-sway-with-hardware-acceleration-after-compiling-the-latest-mesa/</link><description><![CDATA[<p>
	As title says.
</p>

<p>
	Here's the bash script I use to download the dependencies and compile the latest mesa: <a href="https://pastebin.com/1n7Sv0dZ" rel="external nofollow">https://pastebin.com/1n7Sv0dZ</a>
</p>

<p>
	How /boot/*Env* looks like right now: <a href="https://pastebin.com/mUqHs14Y" rel="external nofollow">https://pastebin.com/mUqHs14Y</a>
</p>

<p>
	 
</p>

<p>
	And the error message I get when I try to run sway goes as follows:
</p>

<p>
	 
</p>

<p>
	MESA: error: ZINK: failed to choose pdev
</p>

<p>
	libEGL warning: egl: failed to create dri2 screen
</p>

<p>
	[wlr] [EGL] command: eglInitialize, error: EGL_NOT_INITIALIZED (0x3001), message: "DRI2: failed to create screen"
</p>

<p>
	MESA: error: ZINK: failed to choose pdev
</p>

<p>
	libEGL warning: egl: failed to create dri2 screen
</p>

<p>
	[wlr] [EGL] command: eglInitialize, error: EGL_NOT_INITIALIZED (0x3001), message: "DRI2: failed to create screen"
</p>

<p>
	[wlr] [EGL] command: eglInitialize, error: EGL_NOT_INITIALIZED (0x3001), message: "DRI2: failed to load driver"
</p>

<p>
	[wlr] [EGL] command: eglInitialize, error: EGL_NOT_INITIALIZED (0x3001), message: "eglInitialize"
</p>

<p>
	[wlr] [render/egl.c:268] Failed to initialize EGL
</p>

<p>
	[wlr] [render/egl.c:571] Failed to initialize EGL context
</p>

<p>
	[wlr] [render/gles2/renderer.c:499] Could not initialize EGL
</p>

<p>
	[wlr] [render/wlr_renderer.c:272] Could not initialize renderer
</p>

<p>
	[sway/server.c:236] Failed to create renderer
</p>

<p>
	 
</p>

<p>
	Oddly enough, "eglinfo -B" shows that everything is fine: <a href="https://pastebin.com/6k05DcAS" rel="external nofollow">https://pastebin.com/6k05DcAS</a>
</p>

<p>
	 
</p>

<p>
	How my .bashrc looks like right now: <a href="https://pastebin.com/3W7Qib6U" rel="external nofollow">https://pastebin.com/3W7Qib6U</a>
</p>

<p>
	 
</p>

<p>
	I've tried copying the firmware in (with "cd /lib/firmware<br />
	sudo wget <a href="https://github.com/JeffyCN/mirrors/raw/libmali/firmware/g610/mali_csffw.bin" rel="external nofollow">https://github.com/JeffyCN/mirrors/raw/libmali/firmware/g610/mali_csffw.bin</a><br />
	sudo chmod 644 mali_csffw.bin"), forcing "card0" to be used with the env. value WLR_DRM_DEVICES=/dev/dri/card0, and <abbr title="driver for Mali Midgard and Bifrost GPUs"><abbr title="driver for Mali Midgard and Bifrost GPUs">panfrost</abbr></abbr> with "MESA_LOADER_DRIVER_OVERRIDE=<abbr title="driver for Mali Midgard and Bifrost GPUs"><abbr title="driver for Mali Midgard and Bifrost GPUs">panfrost</abbr></abbr>" and "GALLIUM_DRIVER=<abbr title="driver for Mali Midgard and Bifrost GPUs"><abbr title="driver for Mali Midgard and Bifrost GPUs">panfrost</abbr></abbr>" but none of those options helped. I also added my user to "render" and "video" (with sudo usermod -aG video $USER and sudo usermod -aG render $USER), which also didn't do me any good. I also manually removed any trace of <abbr title="driver for Mali Midgard and Bifrost GPUs"><abbr title="driver for Mali Midgard and Bifrost GPUs">panfrost</abbr></abbr> that was left into the system and reinstalled with "libgl1-mesa-dri" and manually compiling everything in again...and it also didn't worked. I don't know what else I should do, and I'm in the verge of reinstalling everything back in. Please help me. And thanks for reading.
</p>
]]></description><guid isPermaLink="false">58702</guid><pubDate>Tue, 24 Mar 2026 16:46:23 +0000</pubDate></item><item><title>Helios64 - Armbian Trixie with linux 6.18 (incl. opp-microvolt patch)</title><link>https://forum.armbian.com/topic/58597-helios64-armbian-trixie-with-linux-618-incl-opp-microvolt-patch/</link><description><![CDATA[<p>
	The most current download images for Helios64 are now all provided with linux 6.18.xx.
</p>

<p>
	 
</p>

<p>
	I downloaded a minimal image and checked the <abbr title="Device tree blob"><abbr title="Device tree blob">dtb</abbr></abbr>: it would not appear to contain the opp-microvolt patch that made Helios64 finally stable.
</p>

<p>
	 
</p>

<p>
	So for the ones who have stability issues again on Helios64, I attached the patched <abbr title="Device tree blob"><abbr title="Device tree blob">dtb</abbr></abbr> compiled for <span>linux 6.18.xx </span>using the exact same opp-microvolt values as in the previous <abbr title="Device tree blob"><abbr title="Device tree blob">dtb</abbr></abbr> versions I compiled for linux 6.6 and 6.12. The current linux deb files can be downloaded from <a href="http://beta.armbian.com/pool/main/l/" rel="external nofollow">beta.armbian.com</a>, the linux 6.18.18 deb files I used can be downloaded from <a href="https://www.dropbox.com/scl/fi/kk35851t9mz50gb298d9x/debs-6.18.18.zip?rlkey=hjjl9elo9aa29nzjdqxxk5jvu&amp;st=spf9v6hp&amp;dl=1" rel="external nofollow">here</a> (to be installed with 'dpkg -i linux*').
</p>

<p>
	 
</p>

<p>
	In order to install the <abbr title="Device tree blob"><abbr title="Device tree blob">dtb</abbr></abbr>, simply unzip it, copy it into the proper location, update initramfs and reboot:
</p>

<p>
	 
</p>

<pre class="ipsCode prettyprint lang-html prettyprinted"><span class="pln"># install the dtb with the opp-microvolt patch:
unzip rk3399-kobol-helios64.dtb-6.18.18-opp.zip
cp rk3399-kobol-helios64.dtb-6.18.18-opp /boot/dtb/rockchip/rk3399-kobol-helios64.dtb
update-initramfs -u
reboot</span></pre>

<p>
	<a class="ipsAttachLink" data-fileext="zip" data-fileid="16188" href="https://forum.armbian.com/applications/core/interface/file/attachment.php?id=16188&amp;key=459692921733695fb84b5a239f4399b6" rel="">rk3399-kobol-helios64.<abbr title="Device tree blob"><abbr title="Device tree blob">dtb</abbr></abbr>-6.18.18-opp.zip</a>
</p>
]]></description><guid isPermaLink="false">58597</guid><pubDate>Thu, 19 Mar 2026 17:36:14 +0000</pubDate></item><item><title>Orange Pi 5 Pro Not Booting with Armbian</title><link>https://forum.armbian.com/topic/58594-orange-pi-5-pro-not-booting-with-armbian/</link><description><![CDATA[<p>
	Good day,
</p>

<p>
	<br />
	I have recently purchased an Orange Pi 5 Pro and want to use Armbian on it. Armbian (Debian 13 Trixie) does not boot and gives a initramfs error. I have read on erasing the SPI flash memory, but have a few questions. Will erasing the SPI flash memory affect the booting of other operating systems. Is it safe to erase the SPI flash memory? What is the issue around Armbian not booting because of the SPI flash memory? How exactly would I safely erase the SPI flash memory?
</p>

<p>
	<br />
	Thank You
</p>
]]></description><guid isPermaLink="false">58594</guid><pubDate>Thu, 19 Mar 2026 09:30:43 +0000</pubDate></item><item><title>Build failed: "chroot: failed to run command &#x2018;/bin/bash&#x2019;: No such file or directory"</title><link>https://forum.armbian.com/topic/56589-build-failed-chroot-failed-to-run-command-%E2%80%98binbash%E2%80%99-no-such-file-or-directory/</link><description><![CDATA[<p>
	Hi,
</p>

<p>
	 
</p>

<p>
	I'm trying to build the Armbian for Rock64.
</p>

<p>
	Host machine is Ubuntu 24.04 AMD64 (but it is running in VirtualBox under Windows).
</p>

<p>
	Build fails with the following error:
</p>

<p>
	 
</p>

<pre class="ipsCode">[<span class="ipsEmoji">🐳</span>|<span class="ipsEmoji">🌱</span>] Deploying qemu-user-static binary to chroot [ qemu-aarch64-static during image-early ]
[<span class="ipsEmoji">🐳</span>|<span class="ipsEmoji">🔨</span>]   '/usr/bin/qemu-aarch64-static' -&gt; '/armbian/.tmp/rootfs-232e77ba-e6ab-4067-8029-afd44bd1d0b9//usr/bin/qemu-aarch64-static'
chroot: failed to run command ‘/bin/bash’: No such file or directory
[<span class="ipsEmoji">🐳</span>|<span class="ipsEmoji">💥</span>] Error 127 occurred in main shell [ at /armbian/lib/functions/rootfs/distro-specific.sh:276
   create_sources_list_and_deploy_repo_key() --&gt; lib/functions/rootfs/distro-specific.sh:276
        extract_rootfs_artifact() --&gt; lib/functions/rootfs/create-cache.sh:130
                do_with_logging() --&gt; lib/functions/logging/section-logging.sh:81
   get_or_create_rootfs_cache_chroot_sdcard() --&gt; lib/functions/rootfs/create-cache.sh:90
         build_rootfs_and_image() --&gt; lib/functions/main/rootfs-image.sh:14
   full_build_packages_rootfs_and_image() --&gt; lib/functions/main/default-build.sh:36
          do_with_default_build() --&gt; lib/functions/main/default-build.sh:42
         cli_standard_build_run() --&gt; lib/functions/cli/cli-build.sh:25
        armbian_cli_run_command() --&gt; lib/functions/cli/utils-cli.sh:136
                 cli_entrypoint() --&gt; lib/functions/cli/entrypoint.sh:208
                           main() --&gt; compile.sh:50</pre>

<p>
	 
</p>

<p>
	The /bin/bash (/armbian/.tmp/rootfs-232e77ba-e6ab-4067-8029-afd44bd1d0b9/bin/bash) seems an ARM64 and this might be the reason for "failed to run".
</p>

<p>
	 
</p>

<p>
	Is this a known issue? Can I fix it?
</p>

<p>
	I've tried to avoid using chroot in this line, the build goes forward but fails with similar error later.
</p>

<p>
	 
</p>

<p>
	 
</p>
]]></description><guid isPermaLink="false">56589</guid><pubDate>Fri, 05 Dec 2025 09:57:27 +0000</pubDate></item><item><title>Helios64 is not having power</title><link>https://forum.armbian.com/topic/47301-helios64-is-not-having-power/</link><description><![CDATA[<p>
	Hello Everyone,<br />
	Unfortunately my helios64 is not glowing any power LED.<br />
	As soon as I connect the power supply it only shows a blinking orange LED light, that is basically for the battery status.<br />
	My power supply is perfectly fine and even I have tried using with the ATX power supply same result.<br />
	<br />
	Does anyone face this issue and please help me to get my board working again.<br />
	<br />
	Thanks!
</p>

<p>
	<a class="ipsAttachLink ipsAttachLink_image" data-fileext="JPG" data-fileid="13509" href="https://forum.armbian.com/uploads/monthly_2024_11/IMG_8571.JPG.a931f16d5f210458683f56457870c433.JPG" rel=""><img alt="IMG_8571.JPG" class="ipsImage ipsImage_thumbnailed" data-fileid="13509" data-ratio="133.21" width="563" src="https://forum.armbian.com/uploads/monthly_2024_11/IMG_8571.thumb.JPG.f356e4ba348d66b58ff01d7087f19a96.JPG" /></a>
</p>
]]></description><guid isPermaLink="false">47301</guid><pubDate>Wed, 20 Nov 2024 19:30:50 +0000</pubDate></item><item><title>ROCK 3A v1.3 Maskroom OK, NO Boot, NO UART tested power, UART and SD on another board</title><link>https://forum.armbian.com/topic/58560-rock-3a-v13-maskroom-ok-no-boot-no-uart-tested-power-uart-and-sd-on-another-board/</link><description><![CDATA[<p>
	I have a ROCK 3A that reaches Maskrom/recovery but will not boot any Radxa or Armbian SD image and produces no useful UART output. UART is configured per Radxa docs at 1500000 8N1 on the debug header, and the exact same adapter/host/settings work on another ROCK 3A. There is no <abbr title="embedded MultiMediaCard">eMMC</abbr> and no NVMe installed. I also tried resetting/loading SPI via Maskrom using rkdeveloptool db rk356x_spl_loader_ddr1056_v1.12.109_no_check_todly.bin, then loading Radxa’s rock-3a-spi-image-gef9f6b1caad.img. Radxa’s ROCK 3A loader directory contains the matching SPI artifacts, including rock-3a-spi-image-gef9f6b1caad.img, rock-3a-idbloader-gef9f6b1caad.img, and rock-3a-u-boot-gef9f6b1caad.itb, along with RK356x SPL loader binaries. Looking for guidance on whether this points to SPI/SPL/DDR init or a board hardware fault.
</p>
]]></description><guid isPermaLink="false">58560</guid><pubDate>Tue, 17 Mar 2026 06:27:01 +0000</pubDate></item><item><title>Helios64 rk3399-kobol-helios64.dtb-6.XX.xx-L2-hs400-opp Kernel 6.18.10 Crash/Freeze</title><link>https://forum.armbian.com/topic/58558-helios64-rk3399-kobol-helios64dtb-6xxxx-l2-hs400-opp-kernel-61810-crashfreeze/</link><description><![CDATA[<p>
	Hi everybody,
</p>

<p>
	 
</p>

<p>
	I running Helios64 with kernel 6.12.58 since a long time and the prahal <abbr title="Device tree blob"><abbr title="Device tree blob">dtb</abbr></abbr> file rk3399-kobol-helios64.<abbr title="Device tree blob"><abbr title="Device tree blob">dtb</abbr></abbr>-6.12.xx-L2-hs400-opp and my helios64 work well.
</p>

<p>
	Today, Armbian upgrade to 6.18.10 kernel.
</p>

<p>
	Is this update use the same change or patch like in rk3399-kobol-helios64.<abbr title="Device tree blob"><abbr title="Device tree blob">dtb</abbr></abbr>-6.12.xx-L2-hs400-opp ?
</p>

<p>
	Is rk3399-kobol-helios64.<abbr title="Device tree blob"><abbr title="Device tree blob">dtb</abbr></abbr>-6.12.xx-L2-hs400-opp work with 6..18.10 kernel ?
</p>

<p>
	Is I must to downgrade to 6.12.58 kernel with rk3399-kobol-helios64.<abbr title="Device tree blob"><abbr title="Device tree blob">dtb</abbr></abbr>-6.12.xx-L2-hs400-opp and freeze at this kernel version ?
</p>

<p>
	 
</p>

<p>
	Thanks for answer.
</p>
]]></description><guid isPermaLink="false">58558</guid><pubDate>Mon, 16 Mar 2026 19:08:49 +0000</pubDate></item><item><title>Radxa RockPi 4B+ does not recognise the PCIe bus</title><link>https://forum.armbian.com/topic/58572-radxa-rockpi-4b-does-not-recognise-the-pcie-bus/</link><description><![CDATA[<p>
	Hi,
</p>

<p>
	 
</p>

<p>
	I am trying out Armbian 26.2.0-trunk.592 nightly (trixie) on a Radxa Rock PI 4b+
</p>

<p>
	 
</p>

<p>
	The community supported image boots fine and it is no problem to install Armbian on the on-board <abbr title="embedded MultiMediaCard"><abbr title="embedded MultiMediaCard">eMMC</abbr></abbr> flash, but the installed NVMe SSD on PCIi is no recognised. It looks like the whole PCIe bus is not initialised properly during boot. in the kernel log I see:
</p>

<p>
	 
</p>

<pre class="ipsCode prettyprint lang-html prettyprinted"><span class="pln">[    0.062396] /pcie@f8000000: Fixed dependency cycle(s) with /pcie@f8000000/interrupt-controller
[    2.160749] rockchip-pcie f8000000.pcie: host bridge /pcie@f8000000 ranges:
[    2.160771] rockchip-pcie f8000000.pcie:      MEM 0x00fa000000..0x00fbdfffff -&gt; 0x00fa000000
[    2.160779] rockchip-pcie f8000000.pcie:       IO 0x00fbe00000..0x00fbefffff -&gt; 0x00fbe00000
[    2.869988] rockchip-pcie f8000000.pcie: PCIe link training gen1 timeout!
[    2.870032] rockchip-pcie f8000000.pcie: probe with driver rockchip-pcie failed with error -110</span></pre>

<p>
	 
</p>

<p>
	I have searched for quite a while now but could not really find a solution for this. It seems there have been similar problems reported regarding other SOCs using the same chip and I even see patches being proposed (not sure whether the PR has been merged) though at this moment I cannot really see any solution available to this yet.
</p>

<p>
	<br />
	Did anyone else encounter this and is there any fix or workaround for this? 
</p>

<p>
	 
</p>

<p>
	I installed the Homeassistant OS image for this board (maintained here: <a href="https://github.com/citruz/haos-rockpi" rel="external nofollow">https://github.com/citruz/haos-rockpi</a>), which does not have this issue and allowed me to install and boot from the NVMe drive without any problem. Is anyone aware of the differences in the upstream linux kernel and the one that Armbian ships w.r.t. patches that could make a difference here?
</p>

<p>
	 
</p>

<p>
	regards,
</p>

<p>
	 
</p>

<p>
	Frederik
</p>
]]></description><guid isPermaLink="false">58572</guid><pubDate>Tue, 17 Mar 2026 20:06:20 +0000</pubDate></item><item><title>Rock 4 SE not booting</title><link>https://forum.armbian.com/topic/32023-rock-4-se-not-booting/</link><description><![CDATA[<p>
	Hi people!
</p>

<p>
	I'm trying to use Armbian 23.8.1 CLI with the Rock 4 SE board without success.
</p>

<p>
	I write the <abbr title="embedded MultiMediaCard">eMMC</abbr> in the classic way: xzcat Armbian_23.8.1_Rockpi-4b_bookworm_current_6.1.50.img.xz | sudo dd of=/dev/sdb bs=4M status=progress; sync
</p>

<p>
	but nothing seems to happens, i have only the green led on, the blue led is not blinking and the display says "no hdmi signal".
</p>

<p>
	No problems with the image from radxa.
</p>

<p>
	 
</p>

<p>
	Do you have any idea what's going wrong?
</p>
]]></description><guid isPermaLink="false">32023</guid><pubDate>Mon, 27 Nov 2023 12:02:04 +0000</pubDate></item><item><title>Support for EMB-3531(RK3399) for booting from SD card</title><link>https://forum.armbian.com/topic/56257-support-for-emb-3531rk3399-for-booting-from-sd-card/</link><description><![CDATA[<p>
	Hi all,
</p>

<p>
	I would like to ask support for the board EMB-3531. I'm having problem with booting this board from SD card.
</p>

<p>
	Here are some informations about this board. I hope that someone can help me with it.
</p>

<p>
	Thank you so much!
</p>

<p>
	I try to erase the <abbr title="embedded MultiMediaCard">emmc</abbr> and flash the MiniLoaderAll.bin but it doesn't help. Or i don't have a correct image with armbian for this board.
</p>

<p>
	<a href="https://my.kos.org.cn:5154/rockchip/EMB3531/emb3531.pdf" rel="external nofollow">https://my.kos.org.cn:5154/rockchip/EMB3531/emb3531.pdf</a>
</p>

<p>
	 
</p>

<p>
	<a class="ipsAttachLink ipsAttachLink_image" data-fileext="png" data-fileid="15453" href="https://forum.armbian.com/uploads/monthly_2025_11/image.png.227505c1b060715121a95875398ea889.png" rel=""><img alt="image.thumb.png.a96d23e7b16110e442abf25138bff5dc.png" class="ipsImage ipsImage_thumbnailed" data-fileid="15453" data-ratio="51.60" width="1000" src="https://forum.armbian.com/uploads/monthly_2025_11/image.thumb.png.a96d23e7b16110e442abf25138bff5dc.png" /></a>
</p>

<p>
	<a class="ipsAttachLink ipsAttachLink_image" href="https://forum.armbian.com/uploads/monthly_2025_11/image.png.da4f98a35a6cff0cf0355db3381b4896.png" data-fileid="15454" data-fileext="png" rel=""><img alt="image.png" class="ipsImage ipsImage_thumbnailed" data-fileid="15454" data-ratio="87.82" width="854" src="https://forum.armbian.com/uploads/monthly_2025_11/image.thumb.png.6418503871000ed5a834ca9b6bc8b5e7.png" /></a>
</p>
]]></description><guid isPermaLink="false">56257</guid><pubDate>Mon, 17 Nov 2025 09:26:48 +0000</pubDate></item><item><title>orangepi5b : Armbian_25.11.1_Orangepi5-plus_trixie_vendor_6.1.115_minimal.img does not boot</title><link>https://forum.armbian.com/topic/58320-orangepi5b-armbian_25111_orangepi5-plus_trixie_vendor_61115_minimalimg-does-not-boot/</link><description><![CDATA[<p>
	Dear team,
</p>

<p>
	On    Armbian_25.11.1_Orangepi5-plus_trixie_vendor_6.1.115_minimal.img<br />
	not possible to boot completely kernel, sytem reboot in infinie loop
</p>

<p>
	Bellow is the debug log on tty
</p>

<p>
	DDR V1.13 25cee80c4f cym 23/08/11-09:31:58<br />
	LPDDR4X, 2112MHz<br />
	channel[0] BW=16 Col=10 Bk=8 CS0 Row=18 CS1 Row=18 CS=2 Die BW=8 Size=8192MB<br />
	channel[1] BW=16 Col=10 Bk=8 CS0 Row=18 CS1 Row=18 CS=2 Die BW=8 Size=8192MB<br />
	channel[2] BW=16 Col=10 Bk=8 CS0 Row=18 CS1 Row=18 CS=2 Die BW=8 Size=8192MB<br />
	channel[3] BW=16 Col=10 Bk=8 CS0 Row=18 CS1 Row=18 CS=2 Die BW=8 Size=8192MB<br />
	Manufacturer ID:0xff<br />
	CH0 RX Vref:28.9%, TX Vref:22.8%,21.8%<br />
	CH1 RX Vref:27.1%, TX Vref:21.8%,20.8%<br />
	CH2 RX Vref:27.9%, TX Vref:21.8%,22.8%<br />
	CH3 RX Vref:28.9%, TX Vref:20.8%,20.8%<br />
	change to F1: 528MHz<br />
	change to F2: 1068MHz<br />
	change to F3: 1560MHz<br />
	change to F0: 2112MHz<br />
	out<br />
	U-Boot SPL board init<br />
	U-Boot SPL 2017.09-orangepi (Nov 15 2023 - 16:53:25)<br />
	Trying to boot from MMC1<br />
	Trying fit image at 0x4000 sector<br />
	## Verified-boot: 0<br />
	## Checking atf-1 0x00040000 ... sha256(7612223b82...) + OK<br />
	## Checking uboot 0x00200000 ... sha256(d41c62e80b...) + OK<br />
	## Checking fdt 0x00355940 ... sha256(7146109403...) + OK<br />
	## Checking atf-2 0xff100000 ... sha256(70505bb764...) + OK<br />
	## Checking atf-3 0x000f0000 ... sha256(b2af21b504...) + OK<br />
	Jumping to U-Boot(0x00200000) via ARM Trusted Firmware(0x00040000)<br />
	Total: 741.571 ms
</p>

<p>
	INFO:    Preloader serial: 2<br />
	NOTICE:  BL31: v2.3():v2.3-868-g040d2de11:derrick.huang, fwver: v1.48<br />
	NOTICE:  BL31: Built : 15:02:44, Dec 19 2024<br />
	INFO:    spec: 0x1<br />
	INFO:    code: 0x88<br />
	INFO:    ext 32k is valid<br />
	INFO:    ddr: stride-en 4CH<br />
	INFO:    GICv3 without legacy support detected.<br />
	INFO:    ARM GICv3 driver initialized in EL3<br />
	INFO:    valid_cpu_msk=0xff bcore0_rst = 0x0, bcore1_rst = 0x0<br />
	INFO:    l3 cache partition cfg-0<br />
	INFO:    system boots from cpu-hwid-0<br />
	INFO:    disable memory repair<br />
	INFO:    idle_st=0x21fff, pd_st=0x11fff9, repair_st=0xfff70001<br />
	INFO:    dfs DDR fsp_params[0].freq_mhz= 2112MHz<br />
	INFO:    dfs DDR fsp_params[1].freq_mhz= 528MHz<br />
	INFO:    dfs DDR fsp_params[2].freq_mhz= 1068MHz<br />
	INFO:    dfs DDR fsp_params[3].freq_mhz= 1560MHz<br />
	INFO:    BL31: Initialising Exception Handling Framework<br />
	INFO:    BL31: Initializing runtime services<br />
	WARNING: No OPTEE provided by BL2 boot loader, Booting device without OPTEE initialization. SMC`s destined for OPTEE will return SMC_UNK<br />
	ERROR:   Error initializing runtime service opteed_fast<br />
	INFO:    BL31: Preparing for EL3 exit to normal world<br />
	INFO:    Entry point address = 0x200000<br />
	INFO:    SPSR = 0x3c9<br />
	usb dr_mode not found<br />
	usb dr_mode not found
</p>

<p>
	<br />
	U-Boot 2017.09_armbian-2017.09-S3f41-Pdfdd-H6539-Ve691-Bbf55-R448a (Nov 19 2025 - 17:07:00 +0000)
</p>

<p>
	Model: Orange Pi 5 Plus<br />
	MPIDR: 0x0<br />
	PreSerial: 2, raw, 0xfeb50000<br />
	DRAM:  31.7 GiB<br />
	Sysmem: init<br />
	Relocation Offset: eda09000<br />
	Relocation fdt: eb9f7610 - eb9fecd0<br />
	CR: M/C/I<br />
	usb dr_mode not found<br />
	usb dr_mode not found<br />
	Using default environment
</p>

<p>
	DM: v2<br />
	RESC: No bootdev<br />
	Failed to load <abbr title="Device tree blob">DTB</abbr>, ret=-2<br />
	No valid <abbr title="Device tree blob">DTB</abbr>, ret=-22<br />
	Failed to get kernel <abbr title="Device tree blob">dtb</abbr>, ret=-22<br />
	Model: Orange Pi 5 Plus<br />
	[Vendor ERROR]:Invalid boot device type(0)<br />
	## Error: Can't overwrite "ethaddr"<br />
	## Error inserting "ethaddr" variable, errno=1<br />
	## Error: Can't overwrite "eth1addr"<br />
	## Error inserting "eth1addr" variable, errno=1<br />
	[Vendor ERROR]:Invalid boot device type(0)<br />
	rockchip_set_ethaddr: vendor_storage_write failed -19<br />
	[Vendor ERROR]:Invalid boot device type(0)<br />
	mmc@fe2c0000: 1, mmc@fe2e0000: 0<br />
	Card did not respond to voltage select!<br />
	mmc_init: -95, time 14<br />
	switch to partitions #0, OK<br />
	mmc1 is current device<br />
	Boot from SDcard<br />
	Bootdev(scan): mmc 1<br />
	No bootdev<br />
	dev_desc is NULL!<br />
	boot mode: None<br />
	No bootdev<br />
	CLK: (sync kernel. arm: enter 1008000 KHz, init 1008000 KHz, kernel 0N/A)<br />
	  b0pll 24000 KHz<br />
	  b1pll 24000 KHz<br />
	  lpll 24000 KHz<br />
	  v0pll 24000 KHz<br />
	  aupll 24000 KHz<br />
	  cpll 1500000 KHz<br />
	  gpll 1188000 KHz<br />
	  npll 24000 KHz<br />
	  ppll 1100000 KHz<br />
	  aclk_center_root 702000 KHz<br />
	  pclk_center_root 100000 KHz<br />
	  hclk_center_root 396000 KHz<br />
	  aclk_center_low_root 500000 KHz<br />
	  aclk_top_root 750000 KHz<br />
	  pclk_top_root 100000 KHz<br />
	  aclk_low_top_root 396000 KHz<br />
	MMC1: Legacy, 52Mhz<br />
	PartType: EFI<br />
	No bootdev<br />
	dev_desc is NULL!<br />
	No bootdev<br />
	Net:   No ethernet found.<br />
	Hit key to stop autoboot('CTRL+C'):  0 <br />
	starting USB...<br />
	Bus usb@fc000000: usb maximum-speed not found<br />
	Register 2000140 NbrPorts 2<br />
	Starting the controller<br />
	USB XHCI 1.10<br />
	Bus usb@fc800000: USB EHCI 1.00<br />
	Bus usb@fc840000: USB OHCI 1.0<br />
	Bus usb@fc880000: USB EHCI 1.00<br />
	Bus usb@fc8c0000: USB OHCI 1.0<br />
	Bus usb@fc400000: usb maximum-speed not found<br />
	Register 2000140 NbrPorts 2<br />
	Starting the controller<br />
	USB XHCI 1.10<br />
	scanning bus usb@fc000000 for devices... 1 USB Device(s) found<br />
	scanning bus usb@fc800000 for devices... 1 USB Device(s) found<br />
	scanning bus usb@fc840000 for devices... 1 USB Device(s) found<br />
	scanning bus usb@fc880000 for devices... 1 USB Device(s) found<br />
	scanning bus usb@fc8c0000 for devices... 1 USB Device(s) found<br />
	scanning bus usb@fc400000 for devices... cannot reset port 1!?<br />
	1 USB Device(s) found<br />
	       scanning usb for storage devices... 0 Storage Device(s) found
</p>

<p>
	Device 0: unknown device<br />
	switch to partitions #0, OK<br />
	mmc1 is current device<br />
	Could not find misc partition<br />
	ANDROID: reboot reason: "(none)"<br />
	Not AVB images, AVB skip<br />
	android_image_load_by_partname: Can't find part: boot<br />
	Android image load failed<br />
	Android boot failed, error -1.<br />
	Scanning mmc 1:1...<br />
	Found U-Boot script /boot/boot.scr<br />
	4149 bytes read in 24 ms (168 KiB/s)<br />
	## Executing script at 00500000<br />
	Boot script loaded from mmc 1:1<br />
	200 bytes read in 23 ms (7.8 KiB/s)<br />
	14756344 bytes read in 1221 ms (11.5 MiB/s)<br />
	48886272 bytes read in 3964 ms (11.8 MiB/s)<br />
	278734 bytes read in 249 ms (1.1 MiB/s)<br />
	Trying kaslrseed command... Info: Unknown command can be safely ignored since kaslrseed does not apply to all boards.<br />
	Unknown command 'kaslrseed' - try 'help'<br />
	Fdt Ramdisk skip relocation<br />
	No misc partition<br />
	## Loading init Ramdisk from Legacy Image at 0a200000 ...<br />
	   Image Name:   uInitrd<br />
	   Image Type:   AArch64 Linux RAMDisk Image (gzip compressed)<br />
	   Data Size:    14756280 Bytes = 14.1 MiB<br />
	   Load Address: 00000000<br />
	   Entry Point:  00000000<br />
	   Verifying Checksum ... OK<br />
	## Flattened Device Tree blob at 0x08300000<br />
	   Booting using the fdt blob at 0x08300000<br />
	   reserving fdt memory region: addr=8300000 size=aa000<br />
	   Using Device Tree in place at 0000000008300000, end 00000000083acfff<br />
	## reserved-memory:<br />
	  cma: addr=10000000 size=10000000<br />
	  ramoops@110000: addr=110000 size=e0000<br />
	Adding bank: 0x00200000 - 0xf0000000 (size: 0xefe00000)<br />
	Adding bank: 0x100000000 - 0x3fc000000 (size: 0x2fc000000)<br />
	Adding bank: 0x3fc500000 - 0x3fff00000 (size: 0x03a00000)<br />
	Adding bank: 0x400000000 - 0x800000000 (size: 0x400000000)<br />
	Total: 14513.438/14546.469 ms
</p>

<p>
	Starting kernel ...
</p>

<p>
	[   14.549838] Booting Linux on physical CPU 0x0000000000 [0x412fd050]<br />
	[   14.549866] Linux version 6.1.115-vendor-rk35xx (build@armbian) (aarch64-linux-gnu-gcc (Ubuntu 11.4.0-1ubuntu1~22.04) 11.4.0, GNU ld (GNU Binutils for Ubuntu) 2.38) #1 SMP Fri Nov 21 14:02:48 UTC 2025<br />
	[   14.557926] Machine model: Orange Pi 5 Plus<br />
	[   14.558092] efi: UEFI not found.<br />
	[   14.561609] OF: fdt: Reserved memory: failed to reserve memory for node 'drm-logo@0': base 0x0000000000000000, size 0 MiB<br />
	[   14.561630] OF: fdt: Reserved memory: failed to reserve memory for node 'drm-cubic-lut@0': base 0x0000000000000000, size 0 MiB<br />
	[   14.561723] Reserved memory: bypass cma node, using cmdline CMA params instead<br />
	[   14.561729] OF: reserved mem: node cma compatible matching fail<br />
	[   15.092501] Zone ranges:<br />
	[   15.092509]   DMA      [mem 0x0000000000200000-0x00000000ffffffff]<br />
	[   15.092521]   DMA32    empty<br />
	[   15.092526]   Normal   [mem 0x0000000100000000-0x00000007ffffffff]<br />
	[   15.092533] Movable zone start for each node<br />
	[   15.092535] Early memory node ranges<br />
	[   15.092537]   node   0: [mem 0x0000000000200000-0x00000000efffffff]<br />
	[   15.092546]   node   0: [mem 0x0000000100000000-0x00000003fbffffff]<br />
	[   15.092555]   node   0: [mem 0x00000003fc500000-0x00000003ffefffff]<br />
	[   15.092560]   node   0: [mem 0x0000000400000000-0x00000007ffffffff]<br />
	[   15.092571] Initmem setup node 0 [mem 0x0000000000200000-0x00000007ffffffff]<br />
	[   15.112932] On node 0, zone DMA: 512 pages in unavailable ranges<br />
	[   15.178027] On node 0, zone Normal: 1280 pages in unavailable ranges<br />
	[   15.264742] On node 0, zone Normal: 256 pages in unavailable ranges<br />
	[   15.264773] cma: Reserved 256 MiB at 0x00000000e0000000<br />
	[   15.264968] psci: probing for conduit method from DT.<br />
	[   15.264977] psci: PSCIv1.1 detected in firmware.<br />
	[   15.264982] psci: Using standard PSCI v0.2 function IDs<br />
	[   15.264987] psci: MIGRATE_INFO_TYPE not supported.<br />
	[   15.265029] psci: SMC Calling Convention v1.2<br />
	[   15.265418] percpu: Embedded 30 pages/cpu s82728 r8192 d31960 u122880<br />
	[   15.265623] Detected VIPT I-cache on CPU0<br />
	[   15.265675] CPU features: detected: GIC system register CPU interface<br />
	[   15.265680] CPU features: detected: Virtualization Host Extensions<br />
	[   15.265695] CPU features: detected: Qualcomm erratum 1009, or ARM erratum 1286807, 2441009<br />
	[   15.265699] CPU features: detected: ARM errata 1165522, 1319367, or 1530923<br />
	[   15.265705] alternatives: applying boot alternatives<br />
	[   15.266244] Built 1 zonelists, mobility grouping on.  Total pages: 8190984<br />
	[   15.266258] Kernel command line: root=UUID=21f59e6d-0e11-4ba2-85d3-e5fab5604f14 rootwait rootfstype=ext4 splash=verbose console=ttyS2,1500000 console=tty1 consoleblank=0 loglevel=7 ubootpart=f09d1995-765c-164f-bbae-c1ba9ef9a944 usb-storage.quirks= cma=256M  cgroup_enable=cpuset cgroup_memory=1 cgroup_enable=memory androidboot.fwver=bl31-v1.48,uboot-rmbian-201-11/19/2025<br />
	[   15.266782] Unknown kernel command line parameters "splash=verbose ubootpart=f09d1995-765c-164f-bbae-c1ba9ef9a944 cgroup_enable=memory cgroup_memory=1", will be passed to user space.<br />
	[   15.269843] Dentry cache hash table entries: 4194304 (order: 13, 33554432 bytes, linear)<br />
	[   15.271375] Inode-cache hash table entries: 2097152 (order: 12, 16777216 bytes, linear)<br />
	[   15.271384] mem auto-init: stack:off, heap alloc:off, heap free:off<br />
	[   15.271390] software IO TLB: area num 8.<br />
	[   15.283936] software IO TLB: mapped [mem 0x00000000dc000000-0x00000000e0000000] (64MB)<br />
	[   15.542056] Memory: 32255616K/33284096K available (19072K kernel code, 4028K rwdata, 16148K rodata, 8320K init, 700K bss, 766336K reserved, 262144K cma-reserved)<br />
	[   15.542219] SLUB: HWalign=64, Order=0-3, MinObjects=0, CPUs=8, Nodes=1<br />
	[   15.542258] ftrace: allocating 72100 entries in 282 pages<br />
	[   15.670937] ftrace: allocated 282 pages with 4 groups<br />
	[   15.671046] trace event string verifier disabled<br />
	[   15.671273] rcu: Hierarchical RCU implementation.<br />
	[   15.671278] rcu:     RCU event tracing is enabled.<br />
	[   15.671282]     Rude variant of Tasks RCU enabled.<br />
	[   15.671285]     Tracing variant of Tasks RCU enabled.<br />
	[   15.671288] rcu: RCU calculated value of scheduler-enlistment delay is 30 jiffies.<br />
	[   15.689264] NR_IRQS: 64, nr_irqs: 64, preallocated irqs: 0<br />
	[   15.692345] GICv3: GIC: Using split EOI/Deactivate mode<br />
	[   15.692350] GICv3: 480 SPIs implemented<br />
	[   15.692355] GICv3: 0 Extended SPIs implemented<br />
	[   15.692386] Root IRQ handler: gic_handle_irq<br />
	[   15.692402] GICv3: GICv3 features: 16 PPIs<br />
	[   15.692445] GICv3: CPU0: found redistributor 0 region 0:0x00000000fe680000<br />
	[   15.692832] ITS [mem 0xfe640000-0xfe65ffff]<br />
	[   15.692889] ITS@0x00000000fe640000: allocated 8192 Devices @100170000 (indirect, esz 8, psz 64K, shr 0)<br />
	[   15.692921] ITS@0x00000000fe640000: allocated 32768 Interrupt Collections @100180000 (flat, esz 2, psz 64K, shr 0)<br />
	[   15.692937] ITS: using cache flushing for cmd queue<br />
	[   15.692973] ITS [mem 0xfe660000-0xfe67ffff]<br />
	[   15.693021] ITS@0x00000000fe660000: allocated 8192 Devices @1001a0000 (indirect, esz 8, psz 64K, shr 0)<br />
	[   15.693051] ITS@0x00000000fe660000: allocated 32768 Interrupt Collections @1001b0000 (flat, esz 2, psz 64K, shr 0)<br />
	[   15.693066] ITS: using cache flushing for cmd queue<br />
	[   15.693320] GICv3: using LPI property table @0x00000001001c0000<br />
	[   15.693452] GIC: using cache flushing for LPI property table<br />
	[   15.693461] GICv3: CPU0: using allocated LPI pending table @0x00000001001d0000<br />
	[   15.693519] rcu: srcu_init: Setting srcu_struct sizes based on contention.<br />
	[   15.852397] arch_timer: cp15 timer(s) running at 24.00MHz (phys).<br />
	[   15.852409] clocksource: arch_sys_counter: mask: 0xffffffffffffff max_cycles: 0x588fe9dc0, max_idle_ns: 440795202592 ns<br />
	[   15.852420] sched_clock: 56 bits at 24MHz, resolution 41ns, wraps every 4398046511097ns<br />
	[   15.853909] Console: colour dummy device 80x25<br />
	[   15.854617] printk: console [tty1] enabled<br />
	[   15.854661] Calibrating delay loop (skipped), value calculated using timer frequency.. 48.00 BogoMIPS (lpj=80000)<br />
	[   15.854686] pid_max: default: 32768 minimum: 301<br />
	[   15.854763] LSM: Security Framework initializing<br />
	[   15.854894] AppArmor: AppArmor initialized<br />
	[   15.855036] Mount-cache hash table entries: 65536 (order: 7, 524288 bytes, linear)<br />
	[   15.855112] Mountpoint-cache hash table entries: 65536 (order: 7, 524288 bytes, linear)<br />
	[   15.857168] cblist_init_generic: Setting adjustable number of callback queues.<br />
	[   15.857191] cblist_init_generic: Setting shift to 3 and lim to 1.<br />
	[   15.857309] cblist_init_generic: Setting adjustable number of callback queues.<br />
	[   15.857329] cblist_init_generic: Setting shift to 3 and lim to 1.<br />
	[   15.857568] rcu: Hierarchical SRCU implementation.<br />
	[   15.857584] rcu:     Max phase no-delay instances is 1000.<br />
	[   15.859156] Platform MSI: msi-controller@fe640000 domain created<br />
	[   15.859188] Platform MSI: msi-controller@fe660000 domain created<br />
	[   15.859624] PCI/MSI: /interrupt-controller@fe600000/msi-controller@fe640000 domain created<br />
	[   15.859665] PCI/MSI: /interrupt-controller@fe600000/msi-controller@fe660000 domain created<br />
	[   15.859918] EFI services will not be available.<br />
	[   15.860378] smp: Bringing up secondary CPUs ...<br />
	[   15.861025] Detected VIPT I-cache on CPU1<br />
	[   15.861121] GICv3: CPU1: found redistributor 100 region 0:0x00000000fe6a0000<br />
	[   15.861144] GICv3: CPU1: using allocated LPI pending table @0x00000001001e0000<br />
	[   15.861186] CPU1: Booted secondary processor 0x0000000100 [0x412fd050]<br />
	[   15.861927] Detected VIPT I-cache on CPU2<br />
	[   15.862021] GICv3: CPU2: found redistributor 200 region 0:0x00000000fe6c0000<br />
	[   15.862044] GICv3: CPU2: using allocated LPI pending table @0x00000001001f0000<br />
	[   15.862082] CPU2: Booted secondary processor 0x0000000200 [0x412fd050]<br />
	[   15.862741] Detected VIPT I-cache on CPU3<br />
	[   15.862832] GICv3: CPU3: found redistributor 300 region 0:0x00000000fe6e0000<br />
	[   15.862854] GICv3: CPU3: using allocated LPI pending table @0x0000000100200000<br />
	[   15.862889] CPU3: Booted secondary processor 0x0000000300 [0x412fd050]<br />
	[   15.863555] CPU features: detected: Spectre-v4<br />
	[   15.863560] CPU features: detected: Spectre-BHB<br />
	[   15.863564] CPU features: detected: SSBS not fully self-synchronizing<br />
	[   15.863566] Detected PIPT I-cache on CPU4<br />
	[   15.863616] GICv3: CPU4: found redistributor 400 region 0:0x00000000fe700000<br />
	[   15.863629] GICv3: CPU4: using allocated LPI pending table @0x0000000100210000<br />
	[   15.863652] CPU4: Booted secondary processor 0x0000000400 [0x414fd0b0]<br />
	[   15.864307] Detected PIPT I-cache on CPU5<br />
	[   15.864365] GICv3: CPU5: found redistributor 500 region 0:0x00000000fe720000<br />
	[   15.864378] GICv3: CPU5: using allocated LPI pending table @0x0000000100220000<br />
	[   15.864402] CPU5: Booted secondary processor 0x0000000500 [0x414fd0b0]<br />
	[   15.865031] Detected PIPT I-cache on CPU6<br />
	[   15.865087] GICv3: CPU6: found redistributor 600 region 0:0x00000000fe740000<br />
	[   15.865100] GICv3: CPU6: using allocated LPI pending table @0x0000000100230000<br />
	[   15.865123] CPU6: Booted secondary processor 0x0000000600 [0x414fd0b0]<br />
	[   15.865804] Detected PIPT I-cache on CPU7<br />
	[   15.865862] GICv3: CPU7: found redistributor 700 region 0:0x00000000fe760000<br />
	[   15.865874] GICv3: CPU7: using allocated LPI pending table @0x0000000100240000<br />
	[   15.865897] CPU7: Booted secondary processor 0x0000000700 [0x414fd0b0]<br />
	[   15.865964] smp: Brought up 1 node, 8 CPUs<br />
	[   15.866251] SMP: Total of 8 processors activated.<br />
	[   15.866264] CPU features: detected: 32-bit EL0 Support<br />
	[   15.866276] CPU features: detected: Data cache clean to the PoU not required for I/D coherence<br />
	[   15.866293] CPU features: detected: Common not Private translations<br />
	[   15.866306] CPU features: detected: CRC32 instructions<br />
	[   15.866320] CPU features: detected: RCpc load-acquire (LDAPR)<br />
	[   15.866332] CPU features: detected: LSE atomic instructions<br />
	[   15.866344] CPU features: detected: Privileged Access Never<br />
	[   15.866356] CPU features: detected: RAS Extension Support<br />
	[   15.866369] CPU features: detected: Speculative Store Bypassing Safe (SSBS)<br />
	[   15.866461] CPU: All CPU(s) started at EL2<br />
	[   15.866474] alternatives: applying system-wide alternatives<br />
	[   15.876522] devtmpfs: initialized<br />
	[   15.892812] Registered cp15_barrier emulation handler<br />
	[   15.892826] Registered setend emulation handler<br />
	[   15.892915] clocksource: jiffies: mask: 0xffffffff max_cycles: 0xffffffff, max_idle_ns: 6370867519511994 ns<br />
	[   15.892929] futex hash table entries: 2048 (order: 5, 131072 bytes, linear)<br />
	[   15.895047] pinctrl core: initialized pinctrl subsystem<br />
	[   15.895276] DMI not present or invalid.<br />
	[   15.895585] NET: Registered PF_NETLINK/PF_ROUTE protocol family<br />
	[   15.896383] DMA: preallocated 4096 KiB GFP_KERNEL pool for atomic allocations<br />
	[   15.896740] DMA: preallocated 4096 KiB GFP_KERNEL|GFP_DMA pool for atomic allocations<br />
	[   15.896987] DMA: preallocated 4096 KiB GFP_KERNEL|GFP_DMA32 pool for atomic allocations<br />
	[   15.897014] audit: initializing netlink subsys (disabled)<br />
	[   15.897123] audit: type=2000 audit(0.043:1): state=initialized audit_enabled=0 res=1<br />
	[   15.897701] Registered FIQ tty driver<br />
	[   15.897851] thermal_sys: Registered thermal governor 'fair_share'<br />
	[   15.897854] thermal_sys: Registered thermal governor 'step_wise'<br />
	[   15.897859] thermal_sys: Registered thermal governor 'user_space'<br />
	[   15.897864] thermal_sys: Registered thermal governor 'power_allocator'<br />
	[   15.897891] cpuidle: using governor menu<br />
	[   15.898100] hw-breakpoint: found 6 breakpoint and 4 watchpoint registers.<br />
	[   15.898232] ASID allocator initialised with 65536 entries<br />
	[   15.900305] ramoops: dmesg-0    0x18000@0x0000000000110000<br />
	[   15.900313] ramoops: dmesg-1    0x18000@0x0000000000128000<br />
	[   15.900332] ramoops: console    0x80000@0x0000000000140000<br />
	[   15.900343] ramoops: pmsg    0x30000@0x00000000001c0000<br />
	[   15.900607] printk: console [ramoops-1] enabled<br />
	[   15.900614] pstore: Registered ramoops as persistent store backend<br />
	[   15.900620] ramoops: using 0xe0000@0x110000, ecc: 0<br />
	[   15.938715] platform fdd90000.vop: Fixed dependency cycle(s) with /dp@fde50000<br />
	[   15.938752] platform fde50000.dp: Fixed dependency cycle(s) with /vop@fdd90000<br />
	[   15.939044] platform fdd90000.vop: Fixed dependency cycle(s) with /hdmi@fde80000<br />
	[   15.939082] platform fde80000.hdmi: Fixed dependency cycle(s) with /vop@fdd90000<br />
	[   15.944532] platform fed80000.phy: Fixed dependency cycle(s) with /i2c@fec80000/fusb302@22/connector<br />
	[   15.950230] rockchip-<abbr title="General purpose input/output">gpio</abbr> fd8a0000.<abbr title="General purpose input/output">gpio</abbr>: probed /pinctrl/<abbr title="General purpose input/output">gpio</abbr>@fd8a0000<br />
	[   15.950502] rockchip-<abbr title="General purpose input/output">gpio</abbr> fec20000.<abbr title="General purpose input/output">gpio</abbr>: probed /pinctrl/<abbr title="General purpose input/output">gpio</abbr>@fec20000<br />
	[   15.950726] rockchip-<abbr title="General purpose input/output">gpio</abbr> fec30000.<abbr title="General purpose input/output">gpio</abbr>: probed /pinctrl/<abbr title="General purpose input/output">gpio</abbr>@fec30000<br />
	[   15.950968] rockchip-<abbr title="General purpose input/output">gpio</abbr> fec40000.<abbr title="General purpose input/output">gpio</abbr>: probed /pinctrl/<abbr title="General purpose input/output">gpio</abbr>@fec40000<br />
	[   15.951246] rockchip-<abbr title="General purpose input/output">gpio</abbr> fec50000.<abbr title="General purpose input/output">gpio</abbr>: probed /pinctrl/<abbr title="General purpose input/output">gpio</abbr>@fec50000<br />
	[   15.951299] rockchip-pinctrl pinctrl: probed pinctrl<br />
	[   15.952701] platform fdd90000.vop: Fixed dependency cycle(s) with /hdmi@fdea0000<br />
	[   15.952737] platform fdea0000.hdmi: Fixed dependency cycle(s) with /vop@fdd90000<br />
	[   15.956761] KASLR disabled due to lack of seed<br />
	[   15.961962] HugeTLB: registered 1.00 GiB page size, pre-allocated 0 pages<br />
	[   15.961972] HugeTLB: 0 KiB vmemmap can be freed for a 1.00 GiB page<br />
	[   15.961981] HugeTLB: registered 32.0 MiB page size, pre-allocated 0 pages<br />
	[   15.961987] HugeTLB: 0 KiB vmemmap can be freed for a 32.0 MiB page<br />
	[   15.961995] HugeTLB: registered 2.00 MiB page size, pre-allocated 0 pages<br />
	[   15.962001] HugeTLB: 0 KiB vmemmap can be freed for a 2.00 MiB page<br />
	[   15.962008] HugeTLB: registered 64.0 KiB page size, pre-allocated 0 pages<br />
	[   15.962015] HugeTLB: 0 KiB vmemmap can be freed for a 64.0 KiB page<br />
	[   16.019202] raid6: neonx8   gen()  5414 MB/s<br />
	[   16.075957] raid6: neonx4   gen()  5491 MB/s<br />
	[   16.132711] raid6: neonx2   gen()  5094 MB/s<br />
	[   16.189467] raid6: neonx1   gen()  4266 MB/s<br />
	[   16.246230] raid6: int64x8  gen()  1354 MB/s<br />
	[   16.302982] raid6: int64x4  gen()  1714 MB/s<br />
	[   16.359740] raid6: int64x2  gen()  2426 MB/s<br />
	[   16.416500] raid6: int64x1  gen()  2007 MB/s<br />
	[   16.416506] raid6: using algorithm neonx4 gen() 5491 MB/s<br />
	[   16.473245] raid6: .... xor() 4224 MB/s, rmw enabled<br />
	[   16.473252] raid6: using neon recovery algorithm<br />
	[   16.474461] fiq_debugger fiq_debugger.0: error -ENXIO: IRQ fiq not found<br />
	[   16.474476] fiq_debugger fiq_debugger.0: error -ENXIO: IRQ wakeup not found<br />
	[   16.474486] fiq_debugger_probe: could not install nmi irq handler<br />
	[   16.474761] printk: console [ttyFIQ0] enabled<br />
	[   16.474907] Registered fiq debugger ttyFIQ0<br />
	[   16.536509] debugfs: Directory 'vcc_mipicsi1' with parent 'regulator' already present!<br />
	[   16.536530] debugfs: Directory 'vcc_mipicsi1' with parent 'vcc_mipicsi1' already present!<br />
	[   16.536993] iommu: Default domain type: Translated <br />
	[   16.537004] iommu: DMA domain TLB invalidation policy: strict mode <br />
	[   16.537176] SCSI subsystem initialized<br />
	[   16.537262] usbcore: registered new interface driver usbfs<br />
	[   16.537283] usbcore: registered new interface driver hub<br />
	[   16.537301] usbcore: registered new device driver usb<br />
	[   16.537355] mc: Linux media interface: v0.10<br />
	[   16.537378] videodev: Linux video capture interface: v2.00<br />
	[   16.537418] pps_core: LinuxPPS API ver. 1 registered<br />
	[   16.537426] pps_core: Software ver. 5.3.6 - Copyright 2005-2007 Rodolfo Giometti &lt;giometti@linux.it&gt;<br />
	[   16.537440] PTP clock support registered<br />
	[   16.537645] arm-scmi firmware:scmi: Enabled polling mode TX channel - prot_id:16<br />
	[   16.537703] arm-scmi firmware:scmi: SCMI Notifications - Core Enabled.<br />
	[   16.537736] arm-scmi firmware:scmi: SCMI Protocol v2.0 'rockchip:' Firmware version 0x0<br />
	[   16.538652] Advanced Linux Sound Architecture Driver Initialized.<br />
	[   16.538913] Bluetooth: Core ver 2.22<br />
	[   16.538933] NET: Registered PF_BLUETOOTH protocol family<br />
	[   16.538940] Bluetooth: HCI device and connection manager initialized<br />
	[   16.538951] Bluetooth: HCI socket layer initialized<br />
	[   16.538959] Bluetooth: L2CAP socket layer initialized<br />
	[   16.538969] Bluetooth: SCO socket layer initialized<br />
	[   16.539017] NetLabel: Initializing<br />
	[   16.539023] NetLabel:  domain hash size = 128<br />
	[   16.539030] NetLabel:  protocols = UNLABELED CIPSOv4 CALIPSO<br />
	[   16.539060] NetLabel:  unlabeled traffic allowed by default<br />
	[   16.539239] vgaarb: loaded<br />
	[   16.539864] clocksource: Switched to clocksource arch_sys_counter<br />
	[   16.539999] VFS: Disk quotas dquot_6.6.0<br />
	[   16.540025] VFS: Dquot-cache hash table entries: 512 (order 0, 4096 bytes)<br />
	[   16.540234] AppArmor: AppArmor Filesystem Enabled<br />
	[   16.545799] NET: Registered PF_INET protocol family<br />
	[   16.545984] IP idents hash table entries: 262144 (order: 9, 2097152 bytes, linear)<br />
	[   16.552972] tcp_listen_portaddr_hash hash table entries: 16384 (order: 6, 262144 bytes, linear)<br />
	[   16.553150] Table-perturb hash table entries: 65536 (order: 6, 262144 bytes, linear)<br />
	[   16.553184] TCP established hash table entries: 262144 (order: 9, 2097152 bytes, linear)<br />
	[   16.554512] TCP bind hash table entries: 65536 (order: 9, 2097152 bytes, linear)<br />
	[   16.555774] TCP: Hash tables configured (established 262144 bind 65536)<br />
	[   16.555924] MPTCP token hash table entries: 32768 (order: 7, 786432 bytes, linear)<br />
	[   16.556093] UDP hash table entries: 16384 (order: 7, 524288 bytes, linear)<br />
	[   16.556591] UDP-Lite hash table entries: 16384 (order: 7, 524288 bytes, linear)<br />
	[   16.557136] NET: Registered PF_UNIX/PF_LOCAL protocol family<br />
	[   16.557409] RPC: Registered named UNIX socket transport module.<br />
	[   16.557419] RPC: Registered udp transport module.<br />
	[   16.557425] RPC: Registered tcp transport module.<br />
	[   16.557432] RPC: Registered tcp NFSv4.1 backchannel transport module.<br />
	[   16.557855] PCI: CLS 0 bytes, default 64<br />
	[   16.558243] Trying to unpack rootfs image as initramfs...<br />
	[   16.558611] rockchip-thermal fec00000.tsadc: Missing rockchip,grf property<br />
	[   16.559505] rockchip-thermal fec00000.tsadc: tsadc is probed successfully!<br />
	[   16.568269] hw perfevents: enabled with armv8_pmuv3 PMU driver, 7 counters available<br />
	[   16.568770] kvm [1]: IPA Size Limit: 40 bits<br />
	[   16.568788] kvm [1]: GICv3: no GICV resource entry<br />
	[   16.568795] kvm [1]: disabling GICv2 emulation<br />
	[   16.568802] kvm [1]: GIC system register CPU interface enabled<br />
	[   16.573423] kvm [1]: vgic interrupt IRQ9<br />
	[   16.578406] kvm [1]: VHE mode initialized successfully<br />
	[   16.663543] Initialise system trusted keyrings<br />
	[   16.663678] workingset: timestamp_bits=46 max_order=23 bucket_order=0<br />
	[   16.665943] zbud: loaded<br />
	[   16.666774] NFS: Registering the id_resolver key type<br />
	[   16.666796] Key type id_resolver registered<br />
	[   16.666803] Key type id_legacy registered<br />
	[   16.666840] nfs4filelayout_init: NFSv4 File Layout Driver Registering...<br />
	[   16.666849] nfs4flexfilelayout_init: NFSv4 Flexfile Layout Driver Registering...<br />
	[   16.687921] NET: Registered PF_ALG protocol family<br />
	[   16.687937] xor: measuring software checksum speed<br />
	[   16.688466]    8regs           :  6294 MB/sec<br />
	[   16.688870]    32regs          :  8271 MB/sec<br />
	[   16.689210]    arm64_neon      :  9884 MB/sec<br />
	[   16.689217] xor: using function: arm64_neon (9884 MB/sec)<br />
	[   16.689227] Key type asymmetric registered<br />
	[   16.689235] Asymmetric key parser 'x509' registered<br />
	[   16.959955] Freeing initrd memory: 14404K<br />
	[   16.973962] alg: self-tests for CTR-KDF (hmac(sha256)) passed<br />
	[   16.974009] Block layer SCSI generic (bsg) driver version 0.4 loaded (major 241)<br />
	[   16.974123] io scheduler mq-deadline registered<br />
	[   16.974132] io scheduler kyber registered<br />
	[   16.975423] rockchip-csi2-dphy-hw fedc8000.csi2-dphy1-hw: csi2 dphy hw probe successfully!<br />
	[   16.984662] rockchip-hdptx-phy-hdmi fed60000.hdmiphy: hdptx phy init success<br />
	[   16.985526] rockchip-hdptx-phy-hdmi fed70000.hdmiphy: hdptx phy init success<br />
	[   16.987970] dw-pcie fe180000.pcie: invalid resource<br />
	[   16.987986] dw-pcie fe180000.pcie: Failed to initialize host<br />
	[   16.987994] dw-pcie: probe of fe180000.pcie failed with error -22<br />
	[   16.988064] dw-pcie fe190000.pcie: invalid resource<br />
	[   16.988073] dw-pcie fe190000.pcie: Failed to initialize host<br />
	[   16.988080] dw-pcie: probe of fe190000.pcie failed with error -22<br />
	[   16.988190] dw-pcie fe150000.pcie: invalid resource<br />
	[   16.988200] dw-pcie fe150000.pcie: Failed to initialize host<br />
	[   16.988219] dw-pcie: probe of fe150000.pcie failed with error -22<br />
	[   16.988338] dw-pcie fe170000.pcie: invalid resource<br />
	[   16.988348] dw-pcie fe170000.pcie: Failed to initialize host<br />
	[   16.988355] dw-pcie: probe of fe170000.pcie failed with error -22<br />
	[   16.988727] <abbr title="Rockchip">rk</abbr>-pcie fe180000.pcie: using pcie default link_up because of rockchip,default-link-up<br />
	[   16.988880] <abbr title="Rockchip">rk</abbr>-pcie fe190000.pcie: using pcie default link_up because of rockchip,default-link-up<br />
	[   16.988961] <abbr title="Rockchip">rk</abbr>-pcie fe180000.pcie: invalid prsnt-gpios property in node<br />
	[   16.988963] <abbr title="Rockchip">rk</abbr>-pcie fe190000.pcie: invalid prsnt-gpios property in node<br />
	[   16.989036] <abbr title="Rockchip">rk</abbr>-pcie fe190000.pcie: no vpcie3v3 regulator found<br />
	[   16.989154] <abbr title="Rockchip">rk</abbr>-pcie fe180000.pcie: no vpcie3v3 regulator found<br />
	[   16.989171] <abbr title="Rockchip">rk</abbr>-pcie fe150000.pcie: invalid prsnt-gpios property in node<br />
	[   16.989361] <abbr title="Rockchip">rk</abbr>-pcie fe170000.pcie: invalid prsnt-gpios property in node<br />
	[   16.989389] <abbr title="Rockchip">rk</abbr>-pcie fe190000.pcie: host bridge /pcie@fe190000 ranges:<br />
	[   16.989409] <abbr title="Rockchip">rk</abbr>-pcie fe190000.pcie:       IO 0x00f4100000..0x00f41fffff -&gt; 0x00f4100000<br />
	[   16.989439] <abbr title="Rockchip">rk</abbr>-pcie fe190000.pcie:      MEM 0x00f4200000..0x00f4ffffff -&gt; 0x00f4200000<br />
	[   16.989461] <abbr title="Rockchip">rk</abbr>-pcie fe190000.pcie:      MEM 0x0a00000000..0x0a3fffffff -&gt; 0x0a00000000<br />
	[   16.989516] <abbr title="Rockchip">rk</abbr>-pcie fe190000.pcie: iATU unroll: enabled<br />
	[   16.989519] iep: Module initialized.<br />
	[   16.989530] <abbr title="Rockchip">rk</abbr>-pcie fe190000.pcie: iATU regions: 8 ob, 8 ib, align 64K, limit 8G<br />
	[   16.989549] mpp_service mpp-srv: 6c47657a381c author: Yandong Lin 2025-01-16 video: rockchip: mpp: Fix missing enable_irq in timeout work<br />
	[   16.989553] mpp_service mpp-srv: probe start<br />
	[   16.989687] <abbr title="Rockchip">rk</abbr>-pcie fe180000.pcie: host bridge /pcie@fe180000 ranges:<br />
	[   16.989832] <abbr title="Rockchip">rk</abbr>-pcie fe180000.pcie:       IO 0x00f3100000..0x00f31fffff -&gt; 0x00f3100000<br />
	[   16.989847] <abbr title="Rockchip">rk</abbr>-pcie fe180000.pcie:      MEM 0x00f3200000..0x00f3ffffff -&gt; 0x00f3200000<br />
	[   16.989868] <abbr title="Rockchip">rk</abbr>-pcie fe180000.pcie:      MEM 0x09c0000000..0x09ffffffff -&gt; 0x09c0000000<br />
	[   16.989915] <abbr title="Rockchip">rk</abbr>-pcie fe180000.pcie: iATU unroll: enabled<br />
	[   16.989924] <abbr title="Rockchip">rk</abbr>-pcie fe180000.pcie: iATU regions: 8 ob, 8 ib, align 64K, limit 8G<br />
	[   16.991571] mpp_vepu2 jpege-ccu: probing start<br />
	[   16.991584] mpp_vepu2 jpege-ccu: probing finish<br />
	[   16.994566] mpp_rkvdec2 fdc30000.rkvdec-ccu: rkvdec-ccu, probing start<br />
	[   16.994639] mpp_rkvdec2 fdc30000.rkvdec-ccu: ccu-mode: 1<br />
	[   16.994649] mpp_rkvdec2 fdc30000.rkvdec-ccu: probing finish<br />
	[   16.995008] mpp_rkvenc2 rkvenc-ccu: probing start<br />
	[   16.995019] mpp_rkvenc2 rkvenc-ccu: probing finish<br />
	[   16.995612] mpp_service mpp-srv: probe success<br />
	[   17.005549] <abbr title="Rockchip">rk</abbr>-pcie fe150000.pcie: can't get current limit.<br />
	[   17.005806] <abbr title="Rockchip">rk</abbr>-pcie fe150000.pcie: host bridge /pcie@fe150000 ranges:<br />
	[   17.005828] <abbr title="Rockchip">rk</abbr>-pcie fe150000.pcie:       IO 0x00f0100000..0x00f01fffff -&gt; 0x00f0100000<br />
	[   17.005846] <abbr title="Rockchip">rk</abbr>-pcie fe150000.pcie:      MEM 0x00f0200000..0x00f0ffffff -&gt; 0x00f0200000<br />
	[   17.005861] <abbr title="Rockchip">rk</abbr>-pcie fe150000.pcie:      MEM 0x0900000000..0x093fffffff -&gt; 0x0900000000<br />
	[   17.005915] <abbr title="Rockchip">rk</abbr>-pcie fe150000.pcie: iATU unroll: enabled<br />
	[   17.005925] <abbr title="Rockchip">rk</abbr>-pcie fe150000.pcie: iATU regions: 8 ob, 8 ib, align 64K, limit 8G<br />
	[   17.007528] dma-pl330 fea10000.dma-controller: Loaded driver for PL330 DMAC-241330<br />
	[   17.007548] dma-pl330 fea10000.dma-controller:     DBUFF-128x8bytes Num_Chans-8 Num_Peri-32 Num_Events-16<br />
	[   17.008470] dma-pl330 fea30000.dma-controller: Loaded driver for PL330 DMAC-241330<br />
	[   17.008485] dma-pl330 fea30000.dma-controller:     DBUFF-128x8bytes Num_Chans-8 Num_Peri-32 Num_Events-16<br />
	[   17.009395] dma-pl330 fed10000.dma-controller: Loaded driver for PL330 DMAC-241330<br />
	[   17.009410] dma-pl330 fed10000.dma-controller:     DBUFF-128x8bytes Num_Chans-8 Num_Peri-32 Num_Events-16<br />
	[   17.009891] rockchip-pvtm fda40000.pvtm: pvtm@0 probed<br />
	[   17.009963] rockchip-pvtm fda50000.pvtm: pvtm@1 probed<br />
	[   17.010025] rockchip-pvtm fda60000.pvtm: pvtm@2 probed<br />
	[   17.010083] rockchip-pvtm fdaf0000.pvtm: pvtm@3 probed<br />
	[   17.010137] rockchip-pvtm fdb30000.pvtm: pvtm@4 probed<br />
	[   17.010798] rockchip-system-monitor rockchip-system-monitor: system monitor probe<br />
	[   17.011715] Serial: 8250/16550 driver, 10 ports, IRQ sharing disabled<br />
	[   17.012307] febc0000.serial: ttyS9 at MMIO 0xfebc0000 (irq = 45, base_baud = 1500000) is a 16550A<br />
	[   17.013669] random: crng init done<br />
	[   17.013743] led_vk2c21_init<br />
	[   17.013743] =============================================<br />
	[   17.019335] rk_iommu fdca0000.iommu: av1d iommu enabled<br />
	[   17.021625] rockchip-vop2 fdd90000.vop: Adding to iommu group 17<br />
	[   17.031191] rockchip-vop2 fdd90000.vop: [drm:vop2_bind] vp0 assign plane mask: Cluster0 | Esmart0[0x5], primary plane phy id: Cluster0[0]<br />
	[   17.031226] rockchip-vop2 fdd90000.vop: [drm:vop2_bind] vp1 assign plane mask: Cluster1 | Esmart1[0xa], primary plane phy id: Cluster1[1]<br />
	[   17.031245] rockchip-vop2 fdd90000.vop: [drm:vop2_bind] vp2 assign plane mask: Cluster2 | Esmart2[0x140], primary plane phy id: Cluster2[6]<br />
	[   17.031263] rockchip-vop2 fdd90000.vop: [drm:vop2_bind] vp3 assign plane mask: Cluster3 | Esmart3[0x280], primary plane phy id: Cluster3[7]<br />
	[   17.031373] rockchip-vop2 fdd90000.vop: [drm:vop2_bind] Esmart0-win0 as cursor plane for vp0<br />
	[   17.031474] rockchip-vop2 fdd90000.vop: [drm:vop2_bind] Esmart1-win0 as cursor plane for vp1<br />
	[   17.031563] rockchip-vop2 fdd90000.vop: [drm:vop2_bind] Esmart2-win0 as cursor plane for vp2<br />
	[   17.031592] [drm] failed to init overlay plane Cluster0-win1<br />
	[   17.031601] [drm] failed to init overlay plane Cluster1-win1<br />
	[   17.031610] [drm] failed to init overlay plane Cluster2-win1<br />
	[   17.031648] [drm] failed to init overlay plane Cluster3-win1<br />
	[   17.043446] rockchip-vop2 fdd90000.vop: bin=0<br />
	[   17.043668] rockchip-vop2 fdd90000.vop: leakage=35<br />
	[   17.043683] rockchip-vop2 fdd90000.vop: leakage-volt-sel=1<br />
	[   17.043748] rockchip-vop2 fdd90000.vop: error -ENODEV: _opp_set_regulators: no regulator (vop) found<br />
	[   17.043779] rockchip-vop2 fdd90000.vop: failed to set opp config<br />
	[   17.043790] rockchip-vop2 fdd90000.vop: failed to init opp info<br />
	[   17.043799] rockchip-vop2 fdd90000.vop: Unsupported VOP aclk dvfs<br />
	[   17.043821] rockchip-drm display-subsystem: bound fdd90000.vop (ops 0xffff8000093fe4a8)<br />
	[   17.044446] dwhdmi-rockchip fde80000.hdmi: registered ddc I2C bus driver<br />
	[   17.045062] rockchip-drm display-subsystem: bound fde80000.hdmi (ops 0xffff800009417528)<br />
	[   17.045612] dwhdmi-rockchip fdea0000.hdmi: registered ddc I2C bus driver<br />
	[   17.046208] rockchip-drm display-subsystem: bound fdea0000.hdmi (ops 0xffff800009417528)<br />
	[   17.046452] rockchip-drm display-subsystem: bound fde50000.dp (ops 0xffff80000941a588)<br />
	[   17.047805] [drm] Initialized rockchip 4.0.0 20140818 for display-subsystem on minor 0<br />
	[   17.047837] rockchip-drm display-subsystem: failed to parse loader memory<br />
	[   17.047916] rockchip-drm display-subsystem: [drm] Cannot find any crtc or sizes<br />
	[   17.047987] rockchip-drm display-subsystem: [drm] Cannot find any crtc or sizes<br />
	[   17.048017] rockchip-drm display-subsystem: [drm] Cannot find any crtc or sizes<br />
	[   17.048190] rockchip-drm display-subsystem: [drm] run display error_event monitor<br />
	[   17.048860] dw-hdmi-qp-hdcp dw-hdmi-qp-hdcp.2.auto: dw_hdcp_qp_hdcp_probe success<br />
	[   17.048988] dw-hdmi-qp-hdcp dw-hdmi-qp-hdcp.5.auto: dw_hdcp_qp_hdcp_probe success<br />
	[   17.049605] Registered IR keymap <abbr title="Release candidate">rc</abbr>-cec<br />
	[   17.049672] <abbr title="Release candidate">rc</abbr> rc0: dw_hdmi_qp as /devices/platform/fde80000.hdmi/<abbr title="Release candidate">rc</abbr>/rc0<br />
	[   17.049776] input: dw_hdmi_qp as /devices/platform/fde80000.hdmi/<abbr title="Release candidate">rc</abbr>/rc0/input0<br />
	[   17.049983] <abbr title="Rockchip">rk</abbr>-pcie fe170000.pcie: can't get current limit.<br />
	[   17.050179] Registered IR keymap <abbr title="Release candidate">rc</abbr>-cec<br />
	[   17.050246] <abbr title="Release candidate">rc</abbr> rc1: dw_hdmi_qp as /devices/platform/fdea0000.hdmi/<abbr title="Release candidate">rc</abbr>/rc1<br />
	[   17.050340] input: dw_hdmi_qp as /devices/platform/fdea0000.hdmi/<abbr title="Release candidate">rc</abbr>/rc1/input1<br />
	[   17.050375] <abbr title="Rockchip">rk</abbr>-pcie fe170000.pcie: host bridge /pcie@fe170000 ranges:<br />
	[   17.050435] <abbr title="Rockchip">rk</abbr>-pcie fe170000.pcie:       IO 0x00f2100000..0x00f21fffff -&gt; 0x00f2100000<br />
	[   17.050491] <abbr title="Rockchip">rk</abbr>-pcie fe170000.pcie:      MEM 0x00f2200000..0x00f2ffffff -&gt; 0x00f2200000<br />
	[   17.050535] <abbr title="Rockchip">rk</abbr>-pcie fe170000.pcie:      MEM 0x0980000000..0x09bfffffff -&gt; 0x0980000000<br />
	[   17.050626] <abbr title="Rockchip">rk</abbr>-pcie fe170000.pcie: iATU unroll: enabled<br />
	[   17.050653] <abbr title="Rockchip">rk</abbr>-pcie fe170000.pcie: iATU regions: 8 ob, 8 ib, align 64K, limit 8G<br />
	[   17.052457] brd: module loaded<br />
	[   17.055442] loop: module loaded<br />
	[   17.055673] rbd: loaded (major 254)<br />
	[   17.055842] lkdtm: No crash points registered, enable through debugfs<br />
	[   17.058049] rockchip-spi feb20000.spi: no high_speed pinctrl state<br />
	[   17.058457] spi spi2.0: Fixed dependency cycle(s) with /spi@feb20000/rk806single@0/regulators/DCDC_REG7<br />
	[   17.058508] spi spi2.0: Fixed dependency cycle(s) with /spi@feb20000/rk806single@0/pinctrl_rk806/rk806_dvs1_pwrdn<br />
	[   17.058528] spi spi2.0: Fixed dependency cycle(s) with /spi@feb20000/rk806single@0/pinctrl_rk806/rk806_dvs3_null<br />
	[   17.058546] spi spi2.0: Fixed dependency cycle(s) with /spi@feb20000/rk806single@0/pinctrl_rk806/rk806_dvs2_null<br />
	[   17.058565] spi spi2.0: Fixed dependency cycle(s) with /spi@feb20000/rk806single@0/pinctrl_rk806/rk806_dvs1_null<br />
	[   17.059094] rk806 spi2.0: chip id: RK806,ver:0x2, 0x1<br />
	[   17.059226] rk806 spi2.0: ON: 0x40 OFF:0x0<br />
	[   17.059353] rk806 spi2.0: shutdown-sequence missing!<br />
	[   17.059365] rk806 spi2.0: vb-shutdown-sequence missing!<br />
	[   17.059375] rk806 spi2.0: dvs-suspend-control-by missing!<br />
	[   17.068300] avdd_0v75_s0: Bringing 750000uV into 837500-837500uV<br />
	[   17.073038] rk806 spi2.0: no sleep-setting state<br />
	[   17.073056] rk806 spi2.0: no reset-setting pinctrl state<br />
	[   17.073066] rk806 spi2.0: no dvs-setting pinctrl state<br />
	[   17.073767] rockchip-spi feb20000.spi: register misc device rkspi-dev2<br />
	[   17.073782] rockchip-spi feb20000.spi: probed, poll=0, rsd=0, cs-inactive=0, ready=0<br />
	[   17.075148] spi-nor spi5.0: XM25QU128C (16384 Kbytes) read_data x4<br />
	[   17.075192] 1 fixed-partitions partitions found on MTD device sfc_nor<br />
	[   17.075205] Creating 1 MTD partitions on "sfc_nor":<br />
	[   17.075215] 0x000000000000-0x000001000000 : "loader"<br />
	[   17.078062] usbcore: registered new interface driver rndis_wlan<br />
	[   17.078095] usbcore: registered new interface driver asix<br />
	[   17.078117] usbcore: registered new interface driver cdc_ether<br />
	[   17.078140] usbcore: registered new interface driver rndis_host<br />
	[   17.078165] usbcore: registered new interface driver cdc_ncm<br />
	[   17.078294] VFIO - User Level meta-driver version: 0.3<br />
	[   17.078835] platform fc000000.usb: Fixed dependency cycle(s) with /i2c@fec80000/fusb302@22<br />
	[   17.092634] phy phy-fd5d4000.syscon:usb2-phy@4000.3: illegal mode<br />
	[   17.092658] xhci-hcd xhci-hcd.12.auto: xHCI Host Controller<br />
	[   17.092676] xhci-hcd xhci-hcd.12.auto: new USB bus registered, assigned bus number 1<br />
	[   17.092771] xhci-hcd xhci-hcd.12.auto: hcc params 0x0220fe64 hci version 0x110 quirks 0x0002008002010010<br />
	[   17.092804] xhci-hcd xhci-hcd.12.auto: irq 86, io mem 0xfc400000<br />
	[   17.092890] xhci-hcd xhci-hcd.12.auto: xHCI Host Controller<br />
	[   17.092905] xhci-hcd xhci-hcd.12.auto: new USB bus registered, assigned bus number 2<br />
	[   17.092920] xhci-hcd xhci-hcd.12.auto: Host supports USB 3.0 SuperSpeed<br />
	[   17.093014] usb usb1: New USB device found, idVendor=1d6b, idProduct=0002, bcdDevice= 6.01<br />
	[   17.093031] usb usb1: New USB device strings: Mfr=3, Product=2, SerialNumber=1<br />
	[   17.093043] usb usb1: Product: xHCI Host Controller<br />
	[   17.093053] usb usb1: Manufacturer: Linux 6.1.115-vendor-rk35xx xhci-hcd<br />
	[   17.093064] usb usb1: SerialNumber: xhci-hcd.12.auto<br />
	[   17.093386] hub 1-0:1.0: USB hub found<br />
	[   17.093412] hub 1-0:1.0: 1 port detected<br />
	[   17.093604] usb usb2: We don't know the algorithms for LPM for this host, disabling LPM.<br />
	[   17.093672] usb usb2: New USB device found, idVendor=1d6b, idProduct=0003, bcdDevice= 6.01<br />
	[   17.093687] usb usb2: New USB device strings: Mfr=3, Product=2, SerialNumber=1<br />
	[   17.093699] usb usb2: Product: xHCI Host Controller<br />
	[   17.093709] usb usb2: Manufacturer: Linux 6.1.115-vendor-rk35xx xhci-hcd<br />
	[   17.093719] usb usb2: SerialNumber: xhci-hcd.12.auto<br />
	[   17.093981] hub 2-0:1.0: USB hub found<br />
	[   17.094005] hub 2-0:1.0: 1 port detected<br />
	[   17.094125] ehci-platform fc800000.usb: EHCI Host Controller<br />
	[   17.094135] ohci-platform fc840000.usb: Generic Platform OHCI controller<br />
	[   17.094173] ehci-platform fc800000.usb: new USB bus registered, assigned bus number 3<br />
	[   17.094174] ohci-platform fc840000.usb: new USB bus registered, assigned bus number 4<br />
	[   17.094191] ehci-platform fc880000.usb: EHCI Host Controller<br />
	[   17.094203] ehci-platform fc880000.usb: new USB bus registered, assigned bus number 5<br />
	[   17.094221] usbcore: registered new interface driver cdc_acm<br />
	[   17.094220] ohci-platform fc8c0000.usb: Generic Platform OHCI controller<br />
	[   17.094231] cdc_acm: USB Abstract Control Model driver for USB modems and ISDN adapters<br />
	[   17.094240] ohci-platform fc840000.usb: irq 89, io mem 0xfc840000<br />
	[   17.094267] ehci-platform fc800000.usb: irq 87, io mem 0xfc800000<br />
	[   17.094266] ohci-platform fc8c0000.usb: new USB bus registered, assigned bus number 6<br />
	[   17.094283] ehci-platform fc880000.usb: irq 88, io mem 0xfc880000<br />
	[   17.094374] usbcore: registered new interface driver uas<br />
	[   17.094393] ohci-platform fc8c0000.usb: irq 90, io mem 0xfc8c0000<br />
	[   17.094417] usbcore: registered new interface driver usb-storage<br />
	[   17.094723] mousedev: PS/2 mouse device common for all mice<br />
	[   17.095302] .. <abbr title="Rockchip">rk</abbr> pwm remotectl v2.0 init<br />
	[   17.095448] input: febf0030.pwm as /devices/platform/febf0030.pwm/input/input2<br />
	[   17.095659] remotectl-pwm febf0030.pwm: Controller support pwrkey capture<br />
	[   17.095892] i2c_dev: i2c /dev entries driver<br />
	[   17.106548] ehci-platform fc800000.usb: USB 2.0 started, EHCI 1.00<br />
	[   17.106740] usb usb3: New USB device found, idVendor=1d6b, idProduct=0002, bcdDevice= 6.01<br />
	[   17.106758] usb usb3: New USB device strings: Mfr=3, Product=2, SerialNumber=1<br />
	[   17.106771] usb usb3: Product: EHCI Host Controller<br />
	[   17.106781] usb usb3: Manufacturer: Linux 6.1.115-vendor-rk35xx ehci_hcd<br />
	[   17.106791] usb usb3: SerialNumber: fc800000.usb<br />
	[   17.107120] hub 3-0:1.0: USB hub found<br />
	[   17.107157] hub 3-0:1.0: 1 port detected<br />
	[   17.119879] ehci-platform fc880000.usb: USB 2.0 started, EHCI 1.00<br />
	[   17.120221] usb usb5: New USB device found, idVendor=1d6b, idProduct=0002, bcdDevice= 6.01<br />
	[   17.120267] usb usb5: New USB device strings: Mfr=3, Product=2, SerialNumber=1<br />
	[   17.120300] usb usb5: Product: EHCI Host Controller<br />
	[   17.120335] usb usb5: Manufacturer: Linux 6.1.115-vendor-rk35xx ehci_hcd<br />
	[   17.120363] usb usb5: SerialNumber: fc880000.usb<br />
	[   17.120868] hub 5-0:1.0: USB hub found<br />
	[   17.120919] hub 5-0:1.0: 1 port detected<br />
	[   17.127739] rtc-hym8563 6-0051: rtc information is valid<br />
	[   17.130401] rtc-hym8563 6-0051: registered as rtc0<br />
	[   17.130688] rtc-hym8563 6-0051: setting system clock to 2021-01-01T12:03:53 UTC (1609502633)<br />
	[   17.132176] rkcifhw fdce0000.rkcif: Adding to iommu group 16<br />
	[   17.133045] rkcifhw fdce0000.rkcif: No reserved memory region assign to CIF<br />
	[   17.133815] rockchip-mipi-csi2-hw fdd10000.mipi0-csi2-hw: enter mipi csi2 hw probe!<br />
	[   17.133938] rockchip-mipi-csi2-hw fdd10000.mipi0-csi2-hw: probe success, v4l2_dev:mipi0-csi2-hw!<br />
	[   17.133986] rockchip-mipi-csi2-hw fdd20000.mipi1-csi2-hw: enter mipi csi2 hw probe!<br />
	[   17.134073] rockchip-mipi-csi2-hw fdd20000.mipi1-csi2-hw: probe success, v4l2_dev:mipi1-csi2-hw!<br />
	[   17.134116] rockchip-mipi-csi2-hw fdd30000.mipi2-csi2-hw: enter mipi csi2 hw probe!<br />
	[   17.134200] rockchip-mipi-csi2-hw fdd30000.mipi2-csi2-hw: probe success, v4l2_dev:mipi2-csi2-hw!<br />
	[   17.134242] rockchip-mipi-csi2-hw fdd40000.mipi3-csi2-hw: enter mipi csi2 hw probe!<br />
	[   17.134325] rockchip-mipi-csi2-hw fdd40000.mipi3-csi2-hw: probe success, v4l2_dev:mipi3-csi2-hw!<br />
	[   17.134366] rockchip-mipi-csi2-hw fdd50000.mipi4-csi2-hw: enter mipi csi2 hw probe!<br />
	[   17.134447] rockchip-mipi-csi2-hw fdd50000.mipi4-csi2-hw: probe success, v4l2_dev:mipi4-csi2-hw!<br />
	[   17.134488] rockchip-mipi-csi2-hw fdd60000.mipi5-csi2-hw: enter mipi csi2 hw probe!<br />
	[   17.134571] rockchip-mipi-csi2-hw fdd60000.mipi5-csi2-hw: probe success, v4l2_dev:mipi5-csi2-hw!<br />
	[   17.135646] rkisp_hw fdcb0000.rkisp: Adding to iommu group 15<br />
	[   17.135752] rkisp_hw fdcb0000.rkisp: is_thunderboot: 0<br />
	[   17.135764] rkisp_hw fdcb0000.rkisp: Missing rockchip,grf property<br />
	[   17.135785] rkisp_hw fdcb0000.rkisp: max input:0x0@0fps<br />
	[   17.135908] rkisp_hw fdcb0000.rkisp: no find phandle sram<br />
	[   17.137135] usbcore: registered new interface driver uvcvideo<br />
	[   17.138844] cpu cpu0: bin=0<br />
	[   17.139033] cpu cpu0: leakage=12<br />
	[   17.140485] cpu cpu0: pvtm=1415<br />
	[   17.140639] cpu cpu0: pvtm-volt-sel=1<br />
	[   17.142692] cpu cpu4: bin=0<br />
	[   17.142876] cpu cpu4: leakage=9<br />
	[   17.149519] cpu cpu4: pvtm=1633<br />
	[   17.153602] cpu cpu4: pvtm-volt-sel=2<br />
	[   17.154125] usb usb6: New USB device found, idVendor=1d6b, idProduct=0001, bcdDevice= 6.01<br />
	[   17.154175] usb usb6: New USB device strings: Mfr=3, Product=2, SerialNumber=1<br />
	[   17.154209] usb usb6: Product: Generic Platform OHCI controller<br />
	[   17.154236] usb usb6: Manufacturer: Linux 6.1.115-vendor-rk35xx ohci_hcd<br />
	[   17.154263] usb usb6: SerialNumber: fc8c0000.usb<br />
	[   17.154806] hub 6-0:1.0: USB hub found<br />
	[   17.154880] hub 6-0:1.0: 1 port detected<br />
	[   17.156435] cpu cpu6: bin=0<br />
	[   17.156619] cpu cpu6: leakage=9<br />
	[   17.157284] usb usb4: New USB device found, idVendor=1d6b, idProduct=0001, bcdDevice= 6.01<br />
	[   17.157304] usb usb4: New USB device strings: Mfr=3, Product=2, SerialNumber=1<br />
	[   17.157316] usb usb4: Product: Generic Platform OHCI controller<br />
	[   17.157326] usb usb4: Manufacturer: Linux 6.1.115-vendor-rk35xx ohci_hcd<br />
	[   17.157337] usb usb4: SerialNumber: fc840000.usb<br />
	[   17.157593] hub 4-0:1.0: USB hub found<br />
	[   17.157618] hub 4-0:1.0: 1 port detected<br />
	[   17.163211] cpu cpu6: pvtm=1620<br />
	[   17.167264] cpu cpu6: pvtm-volt-sel=2<br />
	[   17.169311] cpu cpu0: avs=0<br />
	[   17.169371] cpu cpu0: rockchip_pvtpll_set_volt_sel: error cfg clk_id=0 voltsel (-1)<br />
	[   17.170661] cpu cpu4: avs=0<br />
	[   17.170714] cpu cpu4: rockchip_pvtpll_set_volt_sel: error cfg clk_id=2 voltsel (-1)<br />
	[   17.171817] cpu cpu6: avs=0<br />
	[   17.171871] cpu cpu6: rockchip_pvtpll_set_volt_sel: error cfg clk_id=3 voltsel (-1)<br />
	[   17.171980] cpu cpu0: l=15000 h=85000 hyst=5000 l_limit=0 h_limit=1608000000 h_table=0<br />
	[   17.172346] cpu cpu0: EM: created perf domain<br />
	[   17.172801] cpu cpu4: l=15000 h=85000 hyst=5000 l_limit=0 h_limit=2208000000 h_table=0<br />
	[   17.181309] cpu cpu4: EM: created perf domain<br />
	[   17.181880] cpu cpu6: l=15000 h=85000 hyst=5000 l_limit=0 h_limit=2208000000 h_table=0<br />
	[   17.191235] cpu cpu6: EM: created perf domain<br />
	[   17.191709] <abbr title="Rockchip">rk</abbr>-pcie fe190000.pcie: PCIe Linking... LTSSM is 0x3<br />
	[   17.192109] <abbr title="Rockchip">rk</abbr>-pcie fe180000.pcie: PCIe Linking... LTSSM is 0x3<br />
	[   17.198244] sdhci: Secure Digital Host Controller Interface driver<br />
	[   17.198283] sdhci: Copyright(c) Pierre Ossman<br />
	[   17.198304] Synopsys Designware Multimedia Card Interface Driver<br />
	[   17.199227] sdhci-pltfm: SDHCI platform and OF driver helper<br />
	[   17.200341] dwmmc_rockchip fe2c0000.mmc: No normal pinctrl state<br />
	[   17.200382] dwmmc_rockchip fe2c0000.mmc: No idle pinctrl state<br />
	[   17.200471] dwmmc_rockchip fe2c0000.mmc: IDMAC supports 32-bit address mode.<br />
	[   17.200513] dwmmc_rockchip fe2c0000.mmc: Using internal DMA controller.<br />
	[   17.200541] dwmmc_rockchip fe2c0000.mmc: Version ID is 270a<br />
	[   17.200611] dwmmc_rockchip fe2c0000.mmc: DW MMC controller at irq 118,32 bit host data width,256 deep fifo<br />
	[   17.202407] mmc0: CQHCI version 5.10<br />
	[   17.202927] ledtrig-cpu: registered to indicate activity on CPUs<br />
	[   17.202984] arm-scmi firmware:scmi: Failed. SCMI protocol 17 not active.<br />
	[   17.203043] SMCCC: SOC_ID: ARCH_SOC_ID not implemented, skipping ....<br />
	[   17.203954] cryptodev: driver 1.12 loaded.<br />
	[   17.204005] hid: raw HID events driver (C) Jiri Kosina<br />
	[   17.204223] usbcore: registered new interface driver usbhid<br />
	[   17.204241] usbhid: USB HID core driver<br />
	[   17.207705] <abbr title="Rockchip">rk</abbr>-pcie fe150000.pcie: PCIe Linking... LTSSM is 0x3<br />
	[   17.210156] SPI driver inv-icm42600-spi has no spi_device_id for invensense,icm42600<br />
	[   17.210188] SPI driver inv-icm42600-spi has no spi_device_id for invensense,icm42602<br />
	[   17.210206] SPI driver inv-icm42600-spi has no spi_device_id for invensense,icm42605<br />
	[   17.210223] SPI driver inv-icm42600-spi has no spi_device_id for invensense,icm42622<br />
	[   17.210699] optee: probing for conduit method.<br />
	[   17.210719] optee: api uid mismatch<br />
	[   17.210731] optee: probe of firmware:optee failed with error -22<br />
	[   17.211532] usbcore: registered new interface driver snd-usb-audio<br />
	[   17.212221] mmc_host mmc1: Bus speed (slot 0) = 400000Hz (slot req 400000Hz, actual 400000HZ div = 0)<br />
	[   17.214974] [Awinic] aw87xxx_pa_init:driver version: v2.2.0<br />
	[   17.216655] rockchip-i2s-tdm fddf0000.i2s: CLK-ALWAYS-ON: mclk: 12288000, bclk: 3072000, fsync: 48000<br />
	[   17.217536] rockchip-i2s-tdm fe470000.i2s: Register PCM for TRCM mode<br />
	[   17.218219] rockchip-i2s-tdm fddf4000.i2s: CLK-ALWAYS-ON: mclk: 12288000, bclk: 3072000, fsync: 48000<br />
	[   17.218428] rockchip-i2s-tdm fddf8000.i2s: Init RX wait-time-ms: 50<br />
	[   17.220863] debugfs: File 'Capture' in directory 'dapm' already present!<br />
	[   17.221896] input: rockchip-dp0 rockchip-dp0 as /devices/platform/dp0-sound/sound/card0/input3<br />
	[   17.223005] input: rockchip-hdmi0 rockchip-hdmi0 as /devices/platform/hdmi0-sound/sound/card1/input4<br />
	[   17.223839] input: rockchip-hdmi1 rockchip-hdmi1 as /devices/platform/hdmi1-sound/sound/card2/input5<br />
	[   17.224333] input: headset-keys as /devices/platform/es8388-sound/input/input6<br />
	[   17.228832] <abbr title="Rockchip">rk</abbr>-pcie fe150000.pcie: PCIe Linking... LTSSM is 0x210022<br />
	[   17.233792] mmc0: SDHCI controller on fe2e0000.mmc [fe2e0000.mmc] using ADMA<br />
	[   17.253053] <abbr title="Rockchip">rk</abbr>-pcie fe170000.pcie: PCIe Linking... LTSSM is 0x3<br />
	[   17.266722] <abbr title="Rockchip">rk</abbr>-pcie fe180000.pcie: PCIe Link up, LTSSM is 0x130011<br />
	[   17.266775] <abbr title="Rockchip">rk</abbr>-pcie fe180000.pcie: PCIe Gen.2 x1 link up<br />
	[   17.266822] <abbr title="Rockchip">rk</abbr>-pcie fe190000.pcie: PCIe Link up, LTSSM is 0x130011<br />
	[   17.266876] <abbr title="Rockchip">rk</abbr>-pcie fe190000.pcie: PCIe Gen.2 x1 link up<br />
	[   17.267011] <abbr title="Rockchip">rk</abbr>-pcie fe180000.pcie: PCI host bridge to bus 0003:30<br />
	[   17.267046] pci_bus 0003:30: root bus resource [bus 30-3f]<br />
	[   17.267075] pci_bus 0003:30: root bus resource [io  0x100000-0x1fffff] (bus address [0xf3100000-0xf31fffff])<br />
	[   17.267108] pci_bus 0003:30: root bus resource [mem 0xf3200000-0xf3ffffff]<br />
	[   17.267114] <abbr title="Rockchip">rk</abbr>-pcie fe190000.pcie: PCI host bridge to bus 0004:40<br />
	[   17.267128] pci_bus 0003:30: root bus resource [mem 0x9c0000000-0x9ffffffff pref]<br />
	[   17.267144] pci_bus 0004:40: root bus resource [bus 40-4f]<br />
	[   17.267186] pci 0003:30:00.0: [1d87:3588] type 01 class 0x060400<br />
	[   17.267201] pci_bus 0004:40: root bus resource [io  0x0000-0xfffff] (bus address [0xf4100000-0xf41fffff])<br />
	[   17.267229] pci 0003:30:00.0: reg 0x38: [mem 0x00000000-0x0000ffff pref]<br />
	[   17.267243] pci_bus 0004:40: root bus resource [mem 0xf4200000-0xf4ffffff]<br />
	[   17.267283] pci_bus 0004:40: root bus resource [mem 0xa00000000-0xa3fffffff pref]<br />
	[   17.267313] pci 0003:30:00.0: supports D1 D2<br />
	[   17.267340] pci 0003:30:00.0: PME# supported from D0 D1 D3hot<br />
	[   17.267338] pci 0004:40:00.0: [1d87:3588] type 01 class 0x060400<br />
	[   17.267400] pci 0004:40:00.0: reg 0x38: [mem 0x00000000-0x0000ffff pref]<br />
	[   17.267484] pci 0004:40:00.0: supports D1 D2<br />
	[   17.267508] pci 0004:40:00.0: PME# supported from D0 D1 D3hot<br />
	[   17.274238] <abbr title="Rockchip">rk</abbr>-pcie fe170000.pcie: PCIe Linking... LTSSM is 0x3<br />
	[   17.285932] pci 0003:30:00.0: Primary bus is hard wired to 0<br />
	[   17.285949] pci 0003:30:00.0: bridge configuration invalid ([bus 01-ff]), reconfiguring<br />
	[   17.286042] pci 0004:40:00.0: Primary bus is hard wired to 0<br />
	[   17.286054] pci 0004:40:00.0: bridge configuration invalid ([bus 01-ff]), reconfiguring<br />
	[   17.286074] pci 0003:31:00.0: [10ec:8125] type 00 class 0x020000<br />
	[   17.286134] pci 0003:31:00.0: reg 0x10: [io  0x0000-0x00ff]<br />
	[   17.286236] pci 0004:41:00.0: [10ec:8125] type 00 class 0x020000<br />
	[   17.286247] pci 0003:31:00.0: reg 0x18: [mem 0x00000000-0x0000ffff 64bit]<br />
	[   17.286326] pci 0004:41:00.0: reg 0x10: initial BAR value 0x00000000 invalid<br />
	[   17.286330] pci 0003:31:00.0: reg 0x20: [mem 0x00000000-0x00003fff 64bit]<br />
	[   17.286338] pci 0004:41:00.0: reg 0x10: [io  size 0x0100]<br />
	[   17.286452] pci 0004:41:00.0: reg 0x18: [mem 0x00000000-0x0000ffff 64bit]<br />
	[   17.286530] pci 0004:41:00.0: reg 0x20: [mem 0x00000000-0x00003fff 64bit]<br />
	[   17.287035] pci 0003:31:00.0: supports D1 D2<br />
	[   17.287046] pci 0003:31:00.0: PME# supported from D0 D1 D2 D3hot D3cold<br />
	[   17.287104] input: rockchip-es8388 Headset as /devices/platform/es8388-sound/sound/card3/input7<br />
	[   17.287133] pci 0004:41:00.0: supports D1 D2<br />
	[   17.287138] pci 0004:41:00.0: PME# supported from D0 D1 D2 D3hot D3cold<br />
	[   17.295300] <abbr title="Rockchip">rk</abbr>-pcie fe170000.pcie: PCIe Linking... LTSSM is 0x3<br />
	[   17.296615] pci_bus 0003:31: busn_res: [bus 31-3f] end is updated to 31<br />
	[   17.296637] pci 0003:30:00.0: BAR 8: assigned [mem 0xf3200000-0xf32fffff]<br />
	[   17.296644] pci 0003:30:00.0: BAR 6: assigned [mem 0xf3300000-0xf330ffff pref]<br />
	[   17.296650] pci 0003:30:00.0: BAR 7: assigned [io  0x100000-0x100fff]<br />
	[   17.296657] pci 0003:31:00.0: BAR 2: assigned [mem 0xf3200000-0xf320ffff 64bit]<br />
	[   17.296687] pci 0003:31:00.0: BAR 4: assigned [mem 0xf3210000-0xf3213fff 64bit]<br />
	[   17.296718] pci 0003:31:00.0: BAR 0: assigned [io  0x100000-0x1000ff]<br />
	[   17.296730] pci 0003:30:00.0: PCI bridge to [bus 31]<br />
	[   17.296735] pci 0003:30:00.0:   bridge window [io  0x100000-0x100fff]<br />
	[   17.296741] pci 0003:30:00.0:   bridge window [mem 0xf3200000-0xf32fffff]<br />
	[   17.297536] pcieport 0003:30:00.0: PME: Signaling with IRQ 135<br />
	[   17.302780] mmc_host mmc1: Bus speed (slot 0) = 148500000Hz (slot req 150000000Hz, actual 148500000HZ div = 0)<br />
	[   17.306649] <abbr title="Rockchip">rk</abbr>-pcie fe150000.pcie: PCIe Link up, LTSSM is 0x230011<br />
	[   17.306685] <abbr title="Rockchip">rk</abbr>-pcie fe150000.pcie: PCIe Gen.3 x4 link up<br />
	[   17.306760] pci_bus 0004:41: busn_res: [bus 41-4f] end is updated to 41<br />
	[   17.306809] pci 0004:40:00.0: BAR 8: assigned [mem 0xf4200000-0xf42fffff]<br />
	[   17.306832] pci 0004:40:00.0: BAR 6: assigned [mem 0xf4300000-0xf430ffff pref]<br />
	[   17.306849] <abbr title="Rockchip">rk</abbr>-pcie fe150000.pcie: PCI host bridge to bus 0000:00<br />
	[   17.306853] pci 0004:40:00.0: BAR 7: assigned [io  0x1000-0x1fff]<br />
	[   17.306866] pci_bus 0000:00: root bus resource [bus 00-0f]<br />
	[   17.306876] pci_bus 0000:00: root bus resource [io  0x200000-0x2fffff] (bus address [0xf0100000-0xf01fffff])<br />
	[   17.306883] pci_bus 0000:00: root bus resource [mem 0xf0200000-0xf0ffffff]<br />
	[   17.306901] pci 0004:41:00.0: BAR 2: assigned [mem 0xf4200000-0xf420ffff 64bit]<br />
	[   17.306909] pci_bus 0000:00: root bus resource [mem 0x900000000-0x93fffffff pref]<br />
	[   17.306947] pci 0004:41:00.0: BAR 4: assigned [mem 0xf4210000-0xf4213fff 64bit]<br />
	[   17.306965] pci 0000:00:00.0: [1d87:3588] type 01 class 0x060400<br />
	[   17.306998] pci 0004:41:00.0: BAR 0: assigned [io  0x1000-0x10ff]<br />
	[   17.307007] pci 0000:00:00.0: reg 0x38: [mem 0x00000000-0x0000ffff pref]<br />
	[   17.307026] pci 0004:40:00.0: PCI bridge to [bus 41]<br />
	[   17.307045] pci 0004:40:00.0:   bridge window [io  0x1000-0x1fff]<br />
	[   17.307065] pci 0004:40:00.0:   bridge window [mem 0xf4200000-0xf42fffff]<br />
	[   17.307072] pci 0000:00:00.0: supports D1 D2<br />
	[   17.307078] pci 0000:00:00.0: PME# supported from D0 D1 D3hot<br />
	[   17.310864] Initializing XFRM netlink socket<br />
	[   17.310895] NET: Registered PF_PACKET protocol family<br />
	[   17.311074] [BT_RFKILL]: Enter rfkill_rk_init<br />
	[   17.311079] [WLAN_RFKILL]: Enter rfkill_wlan_init<br />
	[   17.314541] pcieport 0004:40:00.0: PME: Signaling with IRQ 145<br />
	[   17.316392] <abbr title="Rockchip">rk</abbr>-pcie fe170000.pcie: PCIe Linking... LTSSM is 0x3<br />
	[   17.316925] pci_bus 0000:01: busn_res: can not insert [bus 01-ff] under [bus 00-0f] (conflicts with (null) [bus 00-0f])<br />
	[   17.317003] pci 0000:01:00.0: [c0a9:5427] type 00 class 0x010802<br />
	[   17.317047] [WLAN_RFKILL]: Enter rfkill_wlan_probe<br />
	[   17.317064] [WLAN_RFKILL]: can't find rockchip,grf property<br />
	[   17.317069] [WLAN_RFKILL]: wlan_platdata_parse_dt: wifi_chip_type = ap6275p<br />
	[   17.317073] [WLAN_RFKILL]: wlan_platdata_parse_dt: enable wifi power control.<br />
	[   17.317071] pci 0000:01:00.0: reg 0x10: [mem 0x00000000-0x00003fff 64bit]<br />
	[   17.317078] [WLAN_RFKILL]: wlan_platdata_parse_dt: wifi power controled by <abbr title="General purpose input/output">gpio</abbr>.<br />
	[   17.317103] [WLAN_RFKILL]: wlan_platdata_parse_dt: WIFI,host_wake_irq = 8, flags = 0.<br />
	[   17.317112] [WLAN_RFKILL]: wlan_platdata_parse_dt: The ref_wifi_clk not found !<br />
	[   17.317116] [WLAN_RFKILL]: rfkill_wlan_probe: init <abbr title="General purpose input/output">gpio</abbr><br />
	[   17.317121] [WLAN_RFKILL]: rfkill_set_wifi_bt_power: 1<br />
	[   17.317126] [WLAN_RFKILL]: Exit rfkill_wlan_probe<br />
	[   17.317391] [BT_RFKILL]: bluetooth_platdata_parse_dt: get property: uart_rts_gpios = 148.<br />
	[   17.317411] [BT_RFKILL]: bluetooth_platdata_parse_dt: get property: BT,reset_gpio = 21.<br />
	[   17.317425] [BT_RFKILL]: bluetooth_platdata_parse_dt: get property: BT,wake_gpio = 150.<br />
	[   17.317439] [BT_RFKILL]: bluetooth_platdata_parse_dt: get property: BT,wake_host_irq = 0.<br />
	[   17.317468] [BT_RFKILL]: Request irq for bt wakeup host<br />
	[   17.317510] pci 0000:01:00.0: 31.504 Gb/s available PCIe bandwidth, limited by 8.0 GT/s PCIe x4 link at 0000:00:00.0 (capable of 63.012 Gb/s with 16.0 GT/s PCIe x4 link)<br />
	[   17.317657] [BT_RFKILL]: ** disable irq<br />
	[   17.317702] [BT_RFKILL]: bt shut off power<br />
	[   17.326625] pci 0000:00:00.0: BAR 8: assigned [mem 0xf0200000-0xf02fffff]<br />
	[   17.326659] pci 0000:00:00.0: BAR 6: assigned [mem 0xf0300000-0xf030ffff pref]<br />
	[   17.326686] pci 0000:01:00.0: BAR 0: assigned [mem 0xf0200000-0xf0203fff 64bit]<br />
	[   17.326729] pci 0000:00:00.0: PCI bridge to [bus 01-ff]<br />
	[   17.326747] pci 0000:00:00.0:   bridge window [mem 0xf0200000-0xf02fffff]<br />
	[   17.328210] pcieport 0000:00:00.0: PME: Signaling with IRQ 156<br />
	[   17.328517] nvme nvme0: pci function 0000:01:00.0<br />
	[   17.328614] nvme 0000:01:00.0: enabling device (0000 -&gt; 0002)<br />
	[   17.336856] <abbr title="Rockchip">rk</abbr>-pcie fe170000.pcie: PCIe Linking... LTSSM is 0x3<br />
	[   17.343221] usb 1-1: new high-speed USB device number 2 using xhci-hcd<br />
	[   17.343263] [BT_RFKILL]: bt_default device registered.<br />
	[   17.343442] input: bt-powerkey as /devices/platform/wireless-bluetooth/input/input8<br />
	[   17.343902] Key type dns_resolver registered<br />
	[   17.343955] Key type ceph registered<br />
	[   17.344580] libceph: loaded (mon/osd proto 15/24)<br />
	[   17.347220] registered taskstats version 1<br />
	[   17.347271] Loading compiled-in X.509 certificates<br />
	[   17.351701] zswap: loaded using pool zstd/zbud<br />
	[   17.352322] Key type .fscrypt registered<br />
	[   17.352341] Key type fscrypt-provisioning registered<br />
	[   17.353408] Btrfs loaded, crc32c=crc32c-generic, zoned=no, fsverity=no<br />
	[   17.354271] pstore: Using crash dump compression: deflate<br />
	[   17.354796] Key type encrypted registered<br />
	[   17.355144] AppArmor: AppArmor sha1 policy hashing enabled<br />
	[   17.357936] <abbr title="Rockchip">rk</abbr>-pcie fe170000.pcie: PCIe Linking... LTSSM is 0x3<br />
	[   17.368673] rga3 fdb60000.rga: Adding to iommu group 2<br />
	[   17.369476] rga3 fdb60000.rga: probe successfully, irq = 50, hw_version:3.0.76831<br />
	[   17.369736] rga3 fdb70000.rga: Adding to iommu group 3<br />
	[   17.370447] rga3 fdb70000.rga: probe successfully, irq = 51, hw_version:3.0.76831<br />
	[   17.371705] rga2 fdb80000.rga: probe successfully, irq = 158, hw_version:3.2.63318<br />
	[   17.372080] rga: IOMMU binding successfully, default mapping core[0x1]<br />
	[   17.372305] rga: Module initialized. v1.3.7<br />
	[   17.411406] mpp_vdpu1 fdb51000.avsd-plus: Adding to iommu group 1<br />
	[   17.411965] mpp_vdpu1 fdb51000.avsd-plus: probe device<br />
	[   17.412347] mpp_vdpu1 fdb51000.avsd-plus: reset_group-&gt;rw_sem_on=0<br />
	[   17.412388] mpp_vdpu1 fdb51000.avsd-plus: reset_group-&gt;rw_sem_on=0<br />
	[   17.412509] mpp_vdpu1 fdb51000.avsd-plus: probing finish<br />
	[   17.412897] mpp_vdpu2 fdb50400.vdpu: Adding to iommu group 1<br />
	[   17.413012] mpp_vdpu2 fdb50400.vdpu: probe device<br />
	[   17.413316] mpp_vdpu2 fdb50400.vdpu: reset_group-&gt;rw_sem_on=0<br />
	[   17.413350] mpp_vdpu2 fdb50400.vdpu: reset_group-&gt;rw_sem_on=0<br />
	[   17.413392] mpp_vdpu2 fdb50400.vdpu: probing finish<br />
	[   17.413725] mpp_vepu2 fdb50000.vepu: Adding to iommu group 1<br />
	[   17.413838] mpp_vepu2 fdb50000.vepu: probing start<br />
	[   17.414117] mpp_vepu2 fdb50000.vepu: reset_group-&gt;rw_sem_on=0<br />
	[   17.414148] mpp_vepu2 fdb50000.vepu: reset_group-&gt;rw_sem_on=0<br />
	[   17.414217] mpp_vepu2 fdb50000.vepu: probing finish<br />
	[   17.414574] mpp_vepu2 fdba0000.jpege-core: Adding to iommu group 5<br />
	[   17.414766] mpp_vepu2 fdba0000.jpege-core: probing start<br />
	[   17.414982] mpp_vepu2 fdba0000.jpege-core: attach ccu success<br />
	[   17.415004] mpp_vepu2 fdba0000.jpege-core: probing finish<br />
	[   17.415090] mpp_vepu2 fdba4000.jpege-core: Adding to iommu group 6<br />
	[   17.415160] mpp_vepu2 fdba4000.jpege-core: probing start<br />
	[   17.415245] mpp_vepu2 fdba4000.jpege-core: attach ccu success<br />
	[   17.415265] mpp_vepu2 fdba4000.jpege-core: probing finish<br />
	[   17.415372] mpp_vepu2 fdba8000.jpege-core: Adding to iommu group 7<br />
	[   17.415444] mpp_vepu2 fdba8000.jpege-core: probing start<br />
	[   17.415527] mpp_vepu2 fdba8000.jpege-core: attach ccu success<br />
	[   17.415545] mpp_vepu2 fdba8000.jpege-core: probing finish<br />
	[   17.415654] mpp_vepu2 fdbac000.jpege-core: Adding to iommu group 8<br />
	[   17.415723] mpp_vepu2 fdbac000.jpege-core: probing start<br />
	[   17.415808] mpp_vepu2 fdbac000.jpege-core: attach ccu success<br />
	[   17.415828] mpp_vepu2 fdbac000.jpege-core: probing finish<br />
	[   17.415938] mpp-iep2 fdbb0000.iep: Adding to iommu group 9<br />
	[   17.416016] mpp-iep2 fdbb0000.iep: probe device<br />
	[   17.416595] mpp-iep2 fdbb0000.iep: probing finish<br />
	[   17.416782] mpp_jpgdec fdb90000.jpegd: Adding to iommu group 4<br />
	[   17.416978] mpp_jpgdec fdb90000.jpegd: probe device<br />
	[   17.417155] mpp_jpgdec fdb90000.jpegd: probing finish<br />
	[   17.417324] mpp_rkvdec2 fdc38100.rkvdec-core: Adding to iommu group 12<br />
	[   17.417576] mpp_rkvdec2 fdc38100.rkvdec-core: rkvdec-core, probing start<br />
	[   17.417692] mpp_rkvdec2 fdc38100.rkvdec-core: shared_niu_a is not found!<br />
	[   17.417700] rkvdec2_init:1198: No niu aclk reset resource define<br />
	[   17.417706] mpp_rkvdec2 fdc38100.rkvdec-core: shared_niu_h is not found!<br />
	[   17.417712] rkvdec2_init:1201: No niu hclk reset resource define<br />
	[   17.419384] mpp_rkvdec2 fdc38100.rkvdec-core: no regulator, devfreq is disabled<br />
	[   17.419454] mpp_rkvdec2 fdc38100.rkvdec-core: core_mask=00010001<br />
	[   17.419461] mpp_rkvdec2 fdc38100.rkvdec-core: attach ccu as core 0<br />
	[   17.419580] mpp_rkvdec2 fdc38100.rkvdec-core: sram_start 0x00000000ff001000<br />
	[   17.419587] mpp_rkvdec2 fdc38100.rkvdec-core: rcb_iova 0x00000000fff00000<br />
	[   17.419592] mpp_rkvdec2 fdc38100.rkvdec-core: sram_size 491520<br />
	[   17.419597] mpp_rkvdec2 fdc38100.rkvdec-core: rcb_size 1048576<br />
	[   17.419603] mpp_rkvdec2 fdc38100.rkvdec-core: min_width 512<br />
	[   17.419609] mpp_rkvdec2 fdc38100.rkvdec-core: rcb_info_count 20<br />
	[   17.419614] mpp_rkvdec2 fdc38100.rkvdec-core: [136, 24576]<br />
	[   17.419619] mpp_rkvdec2 fdc38100.rkvdec-core: [137, 49152]<br />
	[   17.419625] mpp_rkvdec2 fdc38100.rkvdec-core: [141, 90112]<br />
	[   17.419630] mpp_rkvdec2 fdc38100.rkvdec-core: [140, 49152]<br />
	[   17.419635] mpp_rkvdec2 fdc38100.rkvdec-core: [139, 180224]<br />
	[   17.419640] mpp_rkvdec2 fdc38100.rkvdec-core: [133, 49152]<br />
	[   17.419645] mpp_rkvdec2 fdc38100.rkvdec-core: [134, 8192]<br />
	[   17.419650] mpp_rkvdec2 fdc38100.rkvdec-core: [135, 4352]<br />
	[   17.419655] mpp_rkvdec2 fdc38100.rkvdec-core: [138, 13056]<br />
	[   17.419661] mpp_rkvdec2 fdc38100.rkvdec-core: [142, 291584]<br />
	[   17.419683] mpp_rkvdec2 fdc38100.rkvdec-core: probing finish<br />
	[   17.419776] mpp_rkvdec2 fdc48100.rkvdec-core: Adding to iommu group 13<br />
	[   17.419943] mpp_rkvdec2 fdc48100.rkvdec-core: rkvdec-core, probing start<br />
	[   17.420028] mpp_rkvdec2 fdc48100.rkvdec-core: shared_niu_a is not found!<br />
	[   17.420034] rkvdec2_init:1198: No niu aclk reset resource define<br />
	[   17.420040] mpp_rkvdec2 fdc48100.rkvdec-core: shared_niu_h is not found!<br />
	[   17.420045] rkvdec2_init:1201: No niu hclk reset resource define<br />
	[   17.420070] mpp_rkvdec2 fdc48100.rkvdec-core: no regulator, devfreq is disabled<br />
	[   17.420099] mpp_rkvdec2 fdc48100.rkvdec-core: core_mask=00020002<br />
	[   17.420116] mpp_rkvdec2 fdc48100.rkvdec-core: attach ccu as core 1<br />
	[   17.420234] mpp_rkvdec2 fdc48100.rkvdec-core: sram_start 0x00000000ff079000<br />
	[   17.420241] mpp_rkvdec2 fdc48100.rkvdec-core: rcb_iova 0x00000000ffe00000<br />
	[   17.420246] mpp_rkvdec2 fdc48100.rkvdec-core: sram_size 487424<br />
	[   17.420251] mpp_rkvdec2 fdc48100.rkvdec-core: rcb_size 1048576<br />
	[   17.420256] mpp_rkvdec2 fdc48100.rkvdec-core: min_width 512<br />
	[   17.420263] mpp_rkvdec2 fdc48100.rkvdec-core: rcb_info_count 20<br />
	[   17.420268] mpp_rkvdec2 fdc48100.rkvdec-core: [136, 24576]<br />
	[   17.420273] mpp_rkvdec2 fdc48100.rkvdec-core: [137, 49152]<br />
	[   17.420278] mpp_rkvdec2 fdc48100.rkvdec-core: [141, 90112]<br />
	[   17.420283] mpp_rkvdec2 fdc48100.rkvdec-core: [140, 49152]<br />
	[   17.420288] mpp_rkvdec2 fdc48100.rkvdec-core: [139, 180224]<br />
	[   17.420293] mpp_rkvdec2 fdc48100.rkvdec-core: [133, 49152]<br />
	[   17.420298] mpp_rkvdec2 fdc48100.rkvdec-core: [134, 8192]<br />
	[   17.420303] mpp_rkvdec2 fdc48100.rkvdec-core: [135, 4352]<br />
	[   17.420308] mpp_rkvdec2 fdc48100.rkvdec-core: [138, 13056]<br />
	[   17.420313] mpp_rkvdec2 fdc48100.rkvdec-core: [142, 291584]<br />
	[   17.420334] mpp_rkvdec2 fdc48100.rkvdec-core: probing finish<br />
	[   17.420437] mpp_rkvenc2 fdbd0000.rkvenc-core: Adding to iommu group 10<br />
	[   17.420538] mpp_rkvenc2 fdbd0000.rkvenc-core: probing start<br />
	[   17.420645] mpp_rkvenc2 fdbd0000.rkvenc-core: rockchip_init_read_margin: no regulator (venc) found: -19<br />
	[   17.420653] mpp_rkvenc2 fdbd0000.rkvenc-core: bin=0<br />
	[   17.420840] mpp_rkvenc2 fdbd0000.rkvenc-core: leakage=11<br />
	[   17.420847] mpp_rkvenc2 fdbd0000.rkvenc-core: leakage-volt-sel=0<br />
	[   17.420897] mpp_rkvenc2 fdbd0000.rkvenc-core: error -ENODEV: _opp_set_regulators: no regulator (venc) found<br />
	[   17.420916] mpp_rkvenc2 fdbd0000.rkvenc-core: failed to set opp config<br />
	[   17.420922] mpp_rkvenc2 fdbd0000.rkvenc-core: failed to init opp info<br />
	[   17.420927] mpp_rkvenc2 fdbd0000.rkvenc-core: failed to init_opp_table<br />
	[   17.420931] rkvenc_init:2147: failed to add venc devfreq<br />
	[   17.420954] mpp_rkvenc2 fdbd0000.rkvenc-core: attach ccu as core 0<br />
	[   17.420973] mpp_rkvenc2 fdbd0000.rkvenc-core: probing finish<br />
	[   17.421052] mpp_rkvenc2 fdbe0000.rkvenc-core: Adding to iommu group 11<br />
	[   17.421155] mpp_rkvenc2 fdbe0000.rkvenc-core: probing start<br />
	[   17.421249] mpp_rkvenc2 fdbe0000.rkvenc-core: rockchip_init_read_margin: no regulator (venc) found: -19<br />
	[   17.421256] mpp_rkvenc2 fdbe0000.rkvenc-core: bin=0<br />
	[   17.421425] mpp_rkvenc2 fdbe0000.rkvenc-core: leakage=11<br />
	[   17.421445] mpp_rkvenc2 fdbe0000.rkvenc-core: leakage-volt-sel=0<br />
	[   17.421474] mpp_rkvenc2 fdbe0000.rkvenc-core: error -ENODEV: _opp_set_regulators: no regulator (venc) found<br />
	[   17.421486] mpp_rkvenc2 fdbe0000.rkvenc-core: failed to set opp config<br />
	[   17.421491] mpp_rkvenc2 fdbe0000.rkvenc-core: failed to init opp info<br />
	[   17.421496] mpp_rkvenc2 fdbe0000.rkvenc-core: failed to init_opp_table<br />
	[   17.421501] rkvenc_init:2147: failed to add venc devfreq<br />
	[   17.421540] mpp_rkvenc2 fdbe0000.rkvenc-core: attach ccu as core 1<br />
	[   17.421556] mpp_rkvenc2 fdbe0000.rkvenc-core: probing finish<br />
	[   17.421642] mpp_av1dec fdc70000.av1d: Adding to iommu group 14<br />
	[   17.421788] mpp_av1dec fdc70000.av1d: probing start<br />
	[   17.421892] mpp_av1dec fdc70000.av1d: probing finish<br />
	[   17.422332] rockchip-dmc dmc: bin=0<br />
	[   17.422343] mali fb000000.<abbr title="Graphic processing unit (3D acceleration)">gpu</abbr>: Kernel DDK version g25p0-00eac0<br />
	[   17.422462] mali fb000000.<abbr title="Graphic processing unit (3D acceleration)">gpu</abbr>: <abbr title="Graphic processing unit (3D acceleration)">GPU</abbr> metrics tracepoint support enabled<br />
	[   17.422502] rockchip-dmc dmc: leakage=35<br />
	[   17.422546] rockchip-dmc dmc: leakage-volt-sel=1<br />
	[   17.422553] rockchip-dmc dmc: <abbr title="System On a Chip">soc</abbr> version=0, speed=1<br />
	[   17.423430] rockchip-dmc dmc: avs=0<br />
	[   17.423441] rockchip-dmc dmc: current ATF version 0x100<br />
	[   17.423598] rockchip-dmc dmc: normal_rate = 1560000000<br />
	[   17.423605] rockchip-dmc dmc: reboot_rate = 2112000000<br />
	[   17.423610] rockchip-dmc dmc: suspend_rate = 528000000<br />
	[   17.423615] rockchip-dmc dmc: video_4k_rate = 1560000000<br />
	[   17.423620] rockchip-dmc dmc: video_4k_10b_rate = 1560000000<br />
	[   17.423625] rockchip-dmc dmc: video_svep_rate = 1560000000<br />
	[   17.423630] rockchip-dmc dmc: boost_rate = 2112000000<br />
	[   17.423635] rockchip-dmc dmc: fixed_rate(isp|cif0|cif1|dualview) = 2112000000<br />
	[   17.423641] rockchip-dmc dmc: performance_rate = 2112000000<br />
	[   17.423646] rockchip-dmc dmc: hdmirx_rate = 2112000000<br />
	[   17.423651] rockchip-dmc dmc: deep_suspend_rate = 2112000000<br />
	[   17.423659] rockchip-dmc dmc: failed to get vop bandwidth to dmc rate<br />
	[   17.423664] rockchip-dmc dmc: failed to get vop pn to msch rl<br />
	[   17.423884] rockchip-dmc dmc: l=15000 h=2147483647 hyst=5000 l_limit=0 h_limit=0 h_table=0<br />
	[   17.425052] mali fb000000.<abbr title="Graphic processing unit (3D acceleration)">gpu</abbr>: bin=0<br />
	[   17.425257] mali fb000000.<abbr title="Graphic processing unit (3D acceleration)">gpu</abbr>: leakage=14<br />
	[   17.425325] debugfs: Directory 'fb000000.<abbr title="Graphic processing unit (3D acceleration)">gpu</abbr>-mali' with parent 'vdd_gpu_s0' already present!<br />
	[   17.426684] WCN: marlin_init entry!<br />
	[   17.426706] mali fb000000.<abbr title="Graphic processing unit (3D acceleration)">gpu</abbr>: pvtm=816<br />
	[   17.426950] mali fb000000.<abbr title="Graphic processing unit (3D acceleration)">gpu</abbr>: pvtm-volt-sel=1<br />
	[   17.427052] debugfs: Directory 'fb000000.<abbr title="Graphic processing unit (3D acceleration)">gpu</abbr>-mali' with parent 'vdd_gpu_s0' already present!<br />
	[   17.427460] RKNPU fdab0000.npu: Adding to iommu group 0<br />
	[   17.427576] RKNPU fdab0000.npu: RKNPU: rknpu iommu is enabled, using iommu mode<br />
	[   17.428673] RKNPU fdab0000.npu: can't request region for resource [mem 0xfdab0000-0xfdabffff]<br />
	[   17.428697] RKNPU fdab0000.npu: can't request region for resource [mem 0xfdac0000-0xfdacffff]<br />
	[   17.428713] RKNPU fdab0000.npu: can't request region for resource [mem 0xfdad0000-0xfdadffff]<br />
	[   17.428958] [drm] Initialized rknpu 0.9.8 20240828 for fdab0000.npu on minor 1<br />
	[   17.429012] mali fb000000.<abbr title="Graphic processing unit (3D acceleration)">gpu</abbr>: avs=0<br />
	[   17.429109] mali fb000000.<abbr title="Graphic processing unit (3D acceleration)">gpu</abbr>: rockchip_pvtpll_set_volt_sel: error cfg clk_id=5 voltsel (-1)<br />
	[   17.429162] W : [File] : drivers/<abbr title="Graphic processing unit (3D acceleration)">gpu</abbr>/arm/bifrost/platform/<abbr title="Rockchip">rk</abbr>/mali_kbase_config_rk.c; [Line] : 144; [Func] : kbase_platform_rk_init(); power-off-delay-ms not available.<br />
	[   17.429703] mali fb000000.<abbr title="Graphic processing unit (3D acceleration)">gpu</abbr>: Register LUT 000a0800 initialized for <abbr title="Graphic processing unit (3D acceleration)">GPU</abbr> arch 0x000a0806<br />
	[   17.429756] mali fb000000.<abbr title="Graphic processing unit (3D acceleration)">gpu</abbr>: r0p0 status 5 not found in HW issues table;<br />
	[   17.429780] mali fb000000.<abbr title="Graphic processing unit (3D acceleration)">gpu</abbr>: falling back to closest match: r0p0 status 0<br />
	[   17.429803] mali fb000000.<abbr title="Graphic processing unit (3D acceleration)">gpu</abbr>: Execution proceeding normally with fallback match<br />
	[   17.429828] mali fb000000.<abbr title="Graphic processing unit (3D acceleration)">gpu</abbr>: <abbr title="Graphic processing unit (3D acceleration)">GPU</abbr> identified as 0x7 arch 10.8.6 r0p0 status 0<br />
	[   17.430001] mali fb000000.<abbr title="Graphic processing unit (3D acceleration)">gpu</abbr>: CSF_GPU_RESET_TIMEOUT is capped from 20666ms to 4500ms<br />
	[   17.430032] mali fb000000.<abbr title="Graphic processing unit (3D acceleration)">gpu</abbr>: KBASE_PRFCNT_ACTIVE_TIMEOUT is capped from 40000ms to 4500ms<br />
	[   17.430058] mali fb000000.<abbr title="Graphic processing unit (3D acceleration)">gpu</abbr>: KBASE_AS_INACTIVE_TIMEOUT is capped from 40000ms to 4500ms<br />
	[   17.430083] mali fb000000.<abbr title="Graphic processing unit (3D acceleration)">gpu</abbr>: CSF_FIRMWARE_STOP_TIMEOUT is capped from 40000ms to 4500ms<br />
	[   17.430193] mali fb000000.<abbr title="Graphic processing unit (3D acceleration)">gpu</abbr>: No priority control manager is configured<br />
	[   17.430219] mali fb000000.<abbr title="Graphic processing unit (3D acceleration)">gpu</abbr>: Large page allocation set to false after hardware feature check<br />
	[   17.430617] mali fb000000.<abbr title="Graphic processing unit (3D acceleration)">gpu</abbr>: No memory group manager is configured<br />
	[   17.430680] mali fb000000.<abbr title="Graphic processing unit (3D acceleration)">gpu</abbr>: Protected memory allocator not available<br />
	[   17.431315] RKNPU fdab0000.npu: RKNPU: bin=0<br />
	[   17.431519] RKNPU fdab0000.npu: leakage=8<br />
	[   17.431560] debugfs: Directory 'fdab0000.npu-rknpu' with parent 'vdd_npu_s0' already present!<br />
	[   17.432338] mali fb000000.<abbr title="Graphic processing unit (3D acceleration)">gpu</abbr>: EM: created perf domain<br />
	[   17.432948] mali fb000000.<abbr title="Graphic processing unit (3D acceleration)">gpu</abbr>: l=15000 h=85000 hyst=5000 l_limit=0 h_limit=800000000 h_table=0<br />
	[   17.438898] mali fb000000.<abbr title="Graphic processing unit (3D acceleration)">gpu</abbr>: * MALI kbase_mmap_min_addr compiled to CONFIG_DEFAULT_MMAP_MIN_ADDR, no runtime update possible! *<br />
	[   17.438952] mali fb000000.<abbr title="Graphic processing unit (3D acceleration)">gpu</abbr>: Probed as mali0<br />
	[   17.439012] RKNPU fdab0000.npu: pvtm=814<br />
	[   17.446487] dwmmc_rockchip fe2c0000.mmc: Successfully tuned phase to 225<br />
	[   17.446562] mmc1: new ultra high speed SDR104 SDHC card at address aaaa<br />
	[   17.447474] mmcblk1: mmc1:aaaa SC16G 14.8 GiB <br />
	[   17.450941] RKNPU fdab0000.npu: pvtm-volt-sel=0<br />
	[   17.451086] debugfs: Directory 'fdab0000.npu-rknpu' with parent 'vdd_npu_s0' already present!<br />
	[   17.453460] RKNPU fdab0000.npu: avs=0<br />
	[   17.453560] RKNPU fdab0000.npu: rockchip_pvtpll_set_volt_sel: error cfg clk_id=6 voltsel (-1)<br />
	[   17.453737] RKNPU fdab0000.npu: l=15000 h=85000 hyst=5000 l_limit=0 h_limit=800000000 h_table=0<br />
	[   17.455683] GPT:Primary header thinks Alt. header is not at the end of the disk.<br />
	[   17.455704] GPT:3235839 != 31116287<br />
	[   17.455713] GPT:Alternate GPT header not at the end of the disk.<br />
	[   17.455722] GPT:3235839 != 31116287<br />
	[   17.455729] GPT: Use GNU Parted to correct GPT errors.<br />
	[   17.455748]  mmcblk1: p1<br />
	[   17.465863] cfg80211: Loading compiled-in X.509 certificates for regulatory database<br />
	[   17.466942] hwmon hwmon8: temp1_input not attached to any thermal zone<br />
	[   17.467045] hwmon hwmon8: temp2_input not attached to any thermal zone<br />
	[   17.475432] nvme nvme0: allocated 64 MiB host memory buffer.<br />
	[   17.487725] cfg80211: Loaded X.509 cert 'sforshee: 00b28ddf47aef9cea7'<br />
	[   17.488498] cfg80211: Loaded X.509 cert 'wens: 61c038651aabdcf94bd0ac7ff06c7248db18c600'<br />
	[   17.489147] clk: Disabling unused clocks<br />
	[   17.489781] usb 1-1: New USB device found, idVendor=05e3, idProduct=0610, bcdDevice=93.91<br />
	[   17.489817] usb 1-1: New USB device strings: Mfr=1, Product=2, SerialNumber=0<br />
	[   17.489837] usb 1-1: Product: USB2.1 Hub<br />
	[   17.489853] usb 1-1: Manufacturer: GenesysLogic<br />
	[   17.490814] rockchip-pm rockchip-suspend: not set pwm-regulator-config<br />
	[   17.491810] rockchip-suspend not set sleep-mode-config for mem-lite<br />
	[   17.491827] rockchip-suspend not set wakeup-config for mem-lite<br />
	[   17.491846] rockchip-suspend not set sleep-mode-config for mem-ultra<br />
	[   17.491863] rockchip-suspend not set wakeup-config for mem-ultra<br />
	[   17.493567] ALSA device list:<br />
	[   17.493584]   #0: rockchip-dp0<br />
	[   17.493597]   #1: rockchip-hdmi0<br />
	[   17.493610]   #2: rockchip-hdmi1<br />
	[   17.493623]   #3: rockchip-es8388<br />
	[   17.541575] hub 1-1:1.0: USB hub found<br />
	[   17.542058] hub 1-1:1.0: 4 ports detected<br />
	[   17.597989] nvme nvme0: 8/0/0 default/read/poll queues<br />
	[   17.610482] usb 2-1: new SuperSpeed USB device number 2 using xhci-hcd<br />
	[   17.632846] usb 2-1: New USB device found, idVendor=05e3, idProduct=0620, bcdDevice=93.91<br />
	[   17.632929] usb 2-1: New USB device strings: Mfr=1, Product=2, SerialNumber=0<br />
	[   17.632981] usb 2-1: Product: USB3.2 Hub<br />
	[   17.633021] usb 2-1: Manufacturer: GenesysLogic<br />
	[   17.653898] hub 2-1:1.0: USB hub found<br />
	[   17.654527] hub 2-1:1.0: 4 ports detected<br />
	[   17.666492] Freeing unused kernel memory: 8320K<br />
	[   17.667221] Run /init as init process<br />
	[   18.013752] input: adc-keys as /devices/platform/adc-keys/input/input9<br />
	DDR V1.13 25cee80c4f cym 23/08/11-09:31:58<br />
	LPDDR4X, 2112MHz<br />
	channel[0] BW=16 Col=10 Bk=8 CS0 Row=18 CS1 Row=18 CS=2 Die BW=8 Size=8192MB<br />
	channel[1] BW=16 Col=10 Bk=8 CS0 Row=18 CS1 Row=18 CS=2 Die BW=8 Size=8192MB<br />
	channel[2] BW=16 Col=10 Bk=8 CS0 Row=18 CS1 Row=18 CS=2 Die BW=8 Size=8192MB<br />
	channel[3] BW=16 Col=10 Bk=8 CS0 Row=18 CS1 Row=18 CS=2 Die BW=8 Size=8192MB<br />
	Manufacturer ID:0xff<br />
	CH0 RX Vref:28.5%, TX Vref:22.8%,21.8%<br />
	CH1 RX Vref:27.1%, TX Vref:21.8%,20.8%<br />
	CH2 RX Vref:27.9%, TX Vref:21.8%,21.8%<br />
	CH3 RX Vref:28.9%, TX Vref:20.8%,20.8%<br />
	change to F1: 528MHz<br />
	change to F2: 1068MHz<br />
	change to F3: 1560MHz<br />
	change to F0: 2112MHz<br />
	out<br />
	U-Boot SPL board init<br />
	U-Boot SPL 2017.09-orangepi (Nov 15 2023 - 16:53:25)<br />
	Trying to boot from MMC1<br />
	Trying fit image at 0x4000 sector<br />
	## Verified-boot: 0<br />
	## Checking atf-1 0x00040000 ... sha256(7612223b82...) + OK<br />
	## Checking uboot 0x00200000 ... sha256(d41c62e80b...) + OK<br />
	## Checking fdt 0x00355940 ... sha256(7146109403...) + OK<br />
	## Checking atf-2 0xff100000 ... sha256(70505bb764...) + OK<br />
	## Checking atf-3 0x000f0000 ... sha256(b2af21b504...) + OK<br />
	Jumping to U-Boot(0x00200000) via ARM Trusted Firmware(0x00040000)<br />
	Total: 741.510 ms
</p>

<p>
	INFO:    Preloader serial: 2<br />
	NOTICE:  BL31: v2.3():v2.3-868-g040d2de11:derrick.huang, fwver: v1.48<br />
	NOTICE:  BL31: Built : 15:02:44, Dec 19 2024<br />
	INFO:    spec: 0x1<br />
	INFO:    code: 0x88<br />
	INFO:    ext 32k is valid<br />
	INFO:    ddr: stride-en 4CH<br />
	INFO:    GICv3 without legacy support detected.<br />
	INFO:    ARM GICv3 driver initialized in EL3<br />
	INFO:    valid_cpu_msk=0xff bcore0_rst = 0x0, bcore1_rst = 0x0<br />
	INFO:    l3 cache partition cfg-0<br />
	INFO:    system boots from cpu-hwid-0<br />
	INFO:    disable memory repair<br />
	INFO:    idle_st=0x21fff, pd_st=0x11fff9, repair_st=0xfff70001<br />
	INFO:    dfs DDR fsp_params[0].freq_mhz= 2112MHz<br />
	INFO:    dfs DDR fsp_params[1].freq_mhz= 528MHz<br />
	INFO:    dfs DDR fsp_params[2].freq_mhz= 1068MHz<br />
	INFO:    dfs DDR fsp_params[3].freq_mhz= 1560MHz<br />
	INFO:    BL31: Initialising Exception Handling Framework<br />
	INFO:    BL31: Initializing runtime services<br />
	WARNING: No OPTEE provided by BL2 boot loader, Booting device without OPTEE initialization. SMC`s destined for OPTEE will return SMC_UNK<br />
	ERROR:   Error initializing runtime service opteed_fast<br />
	INFO:    BL31: Preparing for EL3 exit to normal world<br />
	INFO:    Entry point address = 0x200000<br />
	INFO:    SPSR = 0x3c9<br />
	usb dr_mode not found<br />
	usb dr_mode not found
</p>

<p>
	<br />
	U-Boot 2017.09_armbian-2017.09-S3f41-Pdfdd-H6539-Ve691-Bbf55-R448a (Nov 19 2025 - 17:07:00 +0000)
</p>

<p>
	Model: Orange Pi 5 Plus<br />
	MPIDR: 0x0<br />
	PreSerial: 2, raw, 0xfeb50000<br />
	DRAM:  31.7 GiB<br />
	Sysmem: init<br />
	Relocation Offset: eda09000<br />
	Relocation fdt: eb9f7610 - eb9fecd0<br />
	CR: M/C/I<br />
	usb dr_mode not found<br />
	usb dr_mode not found<br />
	Using default environment
</p>

<p>
	DM: v2<br />
	RESC: No bootdev<br />
	Failed to load <abbr title="Device tree blob">DTB</abbr>, ret=-2<br />
	No valid <abbr title="Device tree blob">DTB</abbr>, ret=-22<br />
	Failed to get kernel <abbr title="Device tree blob">dtb</abbr>, ret=-22<br />
	Model: Orange Pi 5 Plus<br />
	[Vendor ERROR]:Invalid boot device type(0)<br />
	## Error: Can't overwrite "ethaddr"<br />
	## Error inserting "ethaddr" variable, errno=1<br />
	## Error: Can't overwrite "eth1addr"<br />
	## Error inserting "eth1addr" variable, errno=1<br />
	[Vendor ERROR]:Invalid boot device type(0)<br />
	rockchip_set_ethaddr: vendor_storage_write failed -19<br />
	[Vendor ERROR]:Invalid boot device type(0)<br />
	mmc@fe2c0000: 1, mmc@fe2e0000: 0<br />
	Card did not respond to voltage select!<br />
	mmc_init: -95, time 13<br />
	switch to partitions #0, OK<br />
	mmc1 is current device<br />
	Boot from SDcard<br />
	Bootdev(scan): mmc 1<br />
	No bootdev<br />
	dev_desc is NULL!<br />
	boot mode: None<br />
	No bootdev<br />
	CLK: (sync kernel. arm: enter 1008000 KHz, init 1008000 KHz, kernel 0N/A)<br />
	  b0pll 24000 KHz<br />
	  b1pll 24000 KHz<br />
	  lpll 24000 KHz<br />
	  v0pll 24000 KHz<br />
	  aupll 24000 KHz<br />
	  cpll 1500000 KHz<br />
	  gpll 1188000 KHz<br />
	  npll 24000 KHz<br />
	  ppll 1100000 KHz<br />
	  aclk_center_root 702000 KHz<br />
	  pclk_center_root 100000 KHz<br />
	  hclk_center_root 396000 KHz<br />
	  aclk_center_low_root 500000 KHz<br />
	  aclk_top_root 750000 KHz<br />
	  pclk_top_root 100000 KHz<br />
	  aclk_low_top_root 396000 KHz<br />
	MMC1: Legacy, 52Mhz<br />
	PartType: EFI<br />
	No bootdev<br />
	dev_desc is NULL!<br />
	No bootdev<br />
	Net:   No ethernet found.<br />
	Hit key to stop autoboot('CTRL+C'):  0 <br />
	starting USB...<br />
	Bus usb@fc000000: usb maximum-speed not found<br />
	Register 2000140 NbrPorts 2<br />
	Starting the controller<br />
	USB XHCI 1.10<br />
	Bus usb@fc800000: USB EHCI 1.00<br />
	Bus usb@fc840000: USB OHCI 1.0<br />
	Bus usb@fc880000: USB EHCI 1.00<br />
	Bus usb@fc8c0000: USB OHCI 1.0<br />
	Bus usb@fc400000: usb maximum-speed not found<br />
	Register 2000140 NbrPorts 2<br />
	Starting the controller<br />
	USB XHCI 1.10<br />
	scanning bus usb@fc000000 for devices... 1 USB Device(s) found<br />
	scanning bus usb@fc800000 for devices... 1 USB Device(s) found<br />
	scanning bus usb@fc840000 for devices... 1 USB Device(s) found<br />
	scanning bus usb@fc880000 for devices... 1 USB Device(s) found<br />
	scanning bus usb@fc8c0000 for devices... 1 USB Device(s) found<br />
	scanning bus usb@fc400000 for devices... cannot reset port 1!?<br />
	1 USB Device(s) found<br />
	       scanning usb for storage devices... 0 Storage Device(s) found
</p>

<p>
	Device 0: unknown device<br />
	switch to partitions #0, OK<br />
	mmc1 is current device<br />
	Could not find misc partition<br />
	ANDROID: reboot reason: "(none)"<br />
	Not AVB images, AVB skip<br />
	android_image_load_by_partname: Can't find part: boot<br />
	Android image load failed<br />
	Android boot failed, error -1.<br />
	Scanning mmc 1:1...<br />
	Found U-Boot script /boot/boot.scr<br />
	4149 bytes read in 24 ms (168 KiB/s)<br />
	## Executing script at 00500000<br />
	Boot script loaded from mmc 1:1<br />
	200 bytes read in 23 ms (7.8 KiB/s)<br />
	14756344 bytes read in 1221 ms (11.5 MiB/s)<br />
	48886272 bytes read in 3965 ms (11.8 MiB/s)<br />
	278734 bytes read in 249 ms (1.1 MiB/s)<br />
	Trying kaslrseed command... Info: Unknown command can be safely ignored since kaslrseed does not apply to all boards.<br />
	Unknown command 'kaslrseed' - try 'help'<br />
	Fdt Ramdisk skip relocation<br />
	No misc partition<br />
	## Loading init Ramdisk from Legacy Image at 0a200000 ...<br />
	   Image Name:   uInitrd<br />
	   Image Type:   AArch64 Linux RAMDisk Image (gzip compressed)<br />
	   Data Size:    14756280 Bytes = 14.1 MiB<br />
	   Load Address: 00000000<br />
	   Entry Point:  00000000<br />
	   Verifying Checksum ... OK<br />
	## Flattened Device Tree blob at 0x08300000<br />
	   Booting using the fdt blob at 0x08300000<br />
	   reserving fdt memory region: addr=8300000 size=aa000<br />
	   Using Device Tree in place at 0000000008300000, end 00000000083acfff<br />
	## reserved-memory:<br />
	  cma: addr=10000000 size=10000000<br />
	  ramoops@110000: addr=110000 size=e0000<br />
	Adding bank: 0x00200000 - 0xf0000000 (size: 0xefe00000)<br />
	Adding bank: 0x100000000 - 0x3fc000000 (size: 0x2fc000000)<br />
	Adding bank: 0x3fc500000 - 0x3fff00000 (size: 0x03a00000)<br />
	Adding bank: 0x400000000 - 0x800000000 (size: 0x400000000)<br />
	Total: 14512.764/14545.751 ms
</p>

<p>
	Starting kernel ...
</p>

<p>
	[   14.549110] Booting Linux on physical CPU 0x0000000000 [0x412fd050]<br />
	[   14.549137] Linux version 6.1.115-vendor-rk35xx (build@armbian) (aarch64-linux-gnu-gcc (Ubuntu 11.4.0-1ubuntu1~22.04) 11.4.0, GNU ld (GNU Binutils for Ubuntu) 2.38) #1 SMP Fri Nov 21 14:02:48 UTC 2025<br />
	[   14.557192] Machine model: Orange Pi 5 Plus<br />
	[   14.557356] efi: UEFI not found.<br />
	[   14.560874] OF: fdt: Reserved memory: failed to reserve memory for node 'drm-logo@0': base 0x0000000000000000, size 0 MiB<br />
	[   14.560893] OF: fdt: Reserved memory: failed to reserve memory for node 'drm-cubic-lut@0': base 0x0000000000000000, size 0 MiB<br />
	[   14.560986] Reserved memory: bypass cma node, using cmdline CMA params instead<br />
	[   14.560994] OF: reserved mem: node cma compatible matching fail<br />
	[   15.091709] Zone ranges:<br />
	[   15.091717]   DMA      [mem 0x0000000000200000-0x00000000ffffffff]<br />
	[   15.091728]   DMA32    empty<br />
	[   15.091733]   Normal   [mem 0x0000000100000000-0x00000007ffffffff]<br />
	[   15.091740] Movable zone start for each node<br />
	[   15.091742] Early memory node ranges<br />
	[   15.091744]   node   0: [mem 0x0000000000200000-0x00000000efffffff]<br />
	[   15.091753]   node   0: [mem 0x0000000100000000-0x00000003fbffffff]<br />
	[   15.091762]   node   0: [mem 0x00000003fc500000-0x00000003ffefffff]<br />
	[   15.091767]   node   0: [mem 0x0000000400000000-0x00000007ffffffff]<br />
	[   15.091779] Initmem setup node 0 [mem 0x0000000000200000-0x00000007ffffffff]<br />
	[   15.112139] On node 0, zone DMA: 512 pages in unavailable ranges<br />
	[   15.177227] On node 0, zone Normal: 1280 pages in unavailable ranges<br />
	[   15.263945] On node 0, zone Normal: 256 pages in unavailable ranges<br />
	[   15.263976] cma: Reserved 256 MiB at 0x00000000e0000000<br />
	[   15.264171] psci: probing for conduit method from DT.<br />
	[   15.264180] psci: PSCIv1.1 detected in firmware.<br />
	[   15.264186] psci: Using standard PSCI v0.2 function IDs<br />
	[   15.264191] psci: MIGRATE_INFO_TYPE not supported.<br />
	[   15.264232] psci: SMC Calling Convention v1.2<br />
	[   15.264621] percpu: Embedded 30 pages/cpu s82728 r8192 d31960 u122880<br />
	[   15.264826] Detected VIPT I-cache on CPU0<br />
	[   15.264880] CPU features: detected: GIC system register CPU interface<br />
	[   15.264884] CPU features: detected: Virtualization Host Extensions<br />
	[   15.264899] CPU features: detected: Qualcomm erratum 1009, or ARM erratum 1286807, 2441009<br />
	[   15.264903] CPU features: detected: ARM errata 1165522, 1319367, or 1530923<br />
	[   15.264909] alternatives: applying boot alternatives<br />
	[   15.265448] Built 1 zonelists, mobility grouping on.  Total pages: 8190984<br />
	[   15.265462] Kernel command line: root=UUID=21f59e6d-0e11-4ba2-85d3-e5fab5604f14 rootwait rootfstype=ext4 splash=verbose console=ttyS2,1500000 console=tty1 consoleblank=0 loglevel=7 ubootpart=f09d1995-765c-164f-bbae-c1ba9ef9a944 usb-storage.quirks= cma=256M  cgroup_enable=cpuset cgroup_memory=1 cgroup_enable=memory androidboot.fwver=bl31-v1.48,uboot-rmbian-201-11/19/2025<br />
	[   15.265987] Unknown kernel command line parameters "splash=verbose ubootpart=f09d1995-765c-164f-bbae-c1ba9ef9a944 cgroup_enable=memory cgroup_memory=1", will be passed to user space.<br />
	[   15.269048] Dentry cache hash table entries: 4194304 (order: 13, 33554432 bytes, linear)<br />
	[   15.270582] Inode-cache hash table entries: 2097152 (order: 12, 16777216 bytes, linear)<br />
	[   15.270591] mem auto-init: stack:off, heap alloc:off, heap free:off<br />
	[   15.270597] software IO TLB: area num 8.<br />
	[   15.283145] software IO TLB: mapped [mem 0x00000000dc000000-0x00000000e0000000] (64MB)<br />
	[   15.541302] Memory: 32255616K/33284096K available (19072K kernel code, 4028K rwdata, 16148K rodata, 8320K init, 700K bss, 766336K reserved, 262144K cma-reserved)<br />
	[   15.541467] SLUB: HWalign=64, Order=0-3, MinObjects=0, CPUs=8, Nodes=1<br />
	[   15.541506] ftrace: allocating 72100 entries in 282 pages<br />
	[   15.670160] ftrace: allocated 282 pages with 4 groups<br />
	[   15.670271] trace event string verifier disabled<br />
	[   15.670499] rcu: Hierarchical RCU implementation.<br />
	[   15.670504] rcu:     RCU event tracing is enabled.<br />
	[   15.670508]     Rude variant of Tasks RCU enabled.<br />
	[   15.670510]     Tracing variant of Tasks RCU enabled.<br />
	[   15.670514] rcu: RCU calculated value of scheduler-enlistment delay is 30 jiffies.<br />
	[   15.688489] NR_IRQS: 64, nr_irqs: 64, preallocated irqs: 0<br />
	[   15.691607] GICv3: GIC: Using split EOI/Deactivate mode<br />
	[   15.691613] GICv3: 480 SPIs implemented<br />
	[   15.691617] GICv3: 0 Extended SPIs implemented<br />
	[   15.691648] Root IRQ handler: gic_handle_irq<br />
	[   15.691664] GICv3: GICv3 features: 16 PPIs<br />
	[   15.691707] GICv3: CPU0: found redistributor 0 region 0:0x00000000fe680000<br />
	[   15.692106] ITS [mem 0xfe640000-0xfe65ffff]<br />
	[   15.692163] ITS@0x00000000fe640000: allocated 8192 Devices @100170000 (indirect, esz 8, psz 64K, shr 0)<br />
	[   15.692196] ITS@0x00000000fe640000: allocated 32768 Interrupt Collections @100180000 (flat, esz 2, psz 64K, shr 0)<br />
	[   15.692212] ITS: using cache flushing for cmd queue<br />
	[   15.692248] ITS [mem 0xfe660000-0xfe67ffff]<br />
	[   15.692295] ITS@0x00000000fe660000: allocated 8192 Devices @1001a0000 (indirect, esz 8, psz 64K, shr 0)<br />
	[   15.692325] ITS@0x00000000fe660000: allocated 32768 Interrupt Collections @1001b0000 (flat, esz 2, psz 64K, shr 0)<br />
	[   15.692340] ITS: using cache flushing for cmd queue<br />
	[   15.692598] GICv3: using LPI property table @0x00000001001c0000<br />
	[   15.692730] GIC: using cache flushing for LPI property table<br />
	[   15.692739] GICv3: CPU0: using allocated LPI pending table @0x00000001001d0000<br />
	[   15.692796] rcu: srcu_init: Setting srcu_struct sizes based on contention.<br />
	[   15.851599] arch_timer: cp15 timer(s) running at 24.00MHz (phys).<br />
	[   15.851612] clocksource: arch_sys_counter: mask: 0xffffffffffffff max_cycles: 0x588fe9dc0, max_idle_ns: 440795202592 ns<br />
	[   15.851622] sched_clock: 56 bits at 24MHz, resolution 41ns, wraps every 4398046511097ns<br />
	[   15.853115] Console: colour dummy device 80x25<br />
	[   15.853822] printk: console [tty1] enabled<br />
	[   15.853866] Calibrating delay loop (skipped), value calculated using timer frequency.. 48.00 BogoMIPS (lpj=80000)<br />
	[   15.853891] pid_max: default: 32768 minimum: 301<br />
	[   15.853968] LSM: Security Framework initializing<br />
	[   15.854097] AppArmor: AppArmor initialized<br />
	[   15.854239] Mount-cache hash table entries: 65536 (order: 7, 524288 bytes, linear)<br />
	[   15.854316] Mountpoint-cache hash table entries: 65536 (order: 7, 524288 bytes, linear)<br />
	[   15.856375] cblist_init_generic: Setting adjustable number of callback queues.<br />
	[   15.856398] cblist_init_generic: Setting shift to 3 and lim to 1.<br />
	[   15.856517] cblist_init_generic: Setting adjustable number of callback queues.<br />
	[   15.856536] cblist_init_generic: Setting shift to 3 and lim to 1.<br />
	[   15.856776] rcu: Hierarchical SRCU implementation.<br />
	[   15.856792] rcu:     Max phase no-delay instances is 1000.<br />
	[   15.858362] Platform MSI: msi-controller@fe640000 domain created<br />
	[   15.858395] Platform MSI: msi-controller@fe660000 domain created<br />
	[   15.858827] PCI/MSI: /interrupt-controller@fe600000/msi-controller@fe640000 domain created<br />
	[   15.858868] PCI/MSI: /interrupt-controller@fe600000/msi-controller@fe660000 domain created<br />
	[   15.859121] EFI services will not be available.<br />
	[   15.859580] smp: Bringing up secondary CPUs ...<br />
	[   15.860229] Detected VIPT I-cache on CPU1<br />
	[   15.860325] GICv3: CPU1: found redistributor 100 region 0:0x00000000fe6a0000<br />
	[   15.860349] GICv3: CPU1: using allocated LPI pending table @0x00000001001e0000<br />
	[   15.860390] CPU1: Booted secondary processor 0x0000000100 [0x412fd050]<br />
	[   15.861132] Detected VIPT I-cache on CPU2<br />
	[   15.861225] GICv3: CPU2: found redistributor 200 region 0:0x00000000fe6c0000<br />
	[   15.861247] GICv3: CPU2: using allocated LPI pending table @0x00000001001f0000<br />
	[   15.861285] CPU2: Booted secondary processor 0x0000000200 [0x412fd050]<br />
	[   15.861947] Detected VIPT I-cache on CPU3<br />
	[   15.862037] GICv3: CPU3: found redistributor 300 region 0:0x00000000fe6e0000<br />
	[   15.862059] GICv3: CPU3: using allocated LPI pending table @0x0000000100200000<br />
	[   15.862095] CPU3: Booted secondary processor 0x0000000300 [0x412fd050]<br />
	[   15.862758] CPU features: detected: Spectre-v4<br />
	[   15.862763] CPU features: detected: Spectre-BHB<br />
	[   15.862767] CPU features: detected: SSBS not fully self-synchronizing<br />
	[   15.862769] Detected PIPT I-cache on CPU4<br />
	[   15.862820] GICv3: CPU4: found redistributor 400 region 0:0x00000000fe700000<br />
	[   15.862833] GICv3: CPU4: using allocated LPI pending table @0x0000000100210000<br />
	[   15.862856] CPU4: Booted secondary processor 0x0000000400 [0x414fd0b0]<br />
	[   15.863509] Detected PIPT I-cache on CPU5<br />
	[   15.863566] GICv3: CPU5: found redistributor 500 region 0:0x00000000fe720000<br />
	[   15.863580] GICv3: CPU5: using allocated LPI pending table @0x0000000100220000<br />
	[   15.863603] CPU5: Booted secondary processor 0x0000000500 [0x414fd0b0]<br />
	[   15.864232] Detected PIPT I-cache on CPU6<br />
	[   15.864288] GICv3: CPU6: found redistributor 600 region 0:0x00000000fe740000<br />
	[   15.864301] GICv3: CPU6: using allocated LPI pending table @0x0000000100230000<br />
	[   15.864324] CPU6: Booted secondary processor 0x0000000600 [0x414fd0b0]<br />
	[   15.865005] Detected PIPT I-cache on CPU7<br />
	[   15.865062] GICv3: CPU7: found redistributor 700 region 0:0x00000000fe760000<br />
	[   15.865074] GICv3: CPU7: using allocated LPI pending table @0x0000000100240000<br />
	[   15.865097] CPU7: Booted secondary processor 0x0000000700 [0x414fd0b0]<br />
	[   15.865164] smp: Brought up 1 node, 8 CPUs<br />
	[   15.865451] SMP: Total of 8 processors activated.<br />
	[   15.865464] CPU features: detected: 32-bit EL0 Support<br />
	[   15.865476] CPU features: detected: Data cache clean to the PoU not required for I/D coherence<br />
	[   15.865493] CPU features: detected: Common not Private translations<br />
	[   15.865506] CPU features: detected: CRC32 instructions<br />
	[   15.865520] CPU features: detected: RCpc load-acquire (LDAPR)<br />
	[   15.865532] CPU features: detected: LSE atomic instructions<br />
	[   15.865544] CPU features: detected: Privileged Access Never<br />
	[   15.865556] CPU features: detected: RAS Extension Support<br />
	[   15.865569] CPU features: detected: Speculative Store Bypassing Safe (SSBS)<br />
	[   15.865661] CPU: All CPU(s) started at EL2<br />
	[   15.865674] alternatives: applying system-wide alternatives<br />
	[   15.875720] devtmpfs: initialized<br />
	[   15.892004] Registered cp15_barrier emulation handler<br />
	[   15.892018] Registered setend emulation handler<br />
	[   15.892108] clocksource: jiffies: mask: 0xffffffff max_cycles: 0xffffffff, max_idle_ns: 6370867519511994 ns<br />
	[   15.892123] futex hash table entries: 2048 (order: 5, 131072 bytes, linear)<br />
	[   15.894244] pinctrl core: initialized pinctrl subsystem<br />
	[   15.894472] DMI not present or invalid.<br />
	[   15.894782] NET: Registered PF_NETLINK/PF_ROUTE protocol family<br />
	[   15.895581] DMA: preallocated 4096 KiB GFP_KERNEL pool for atomic allocations<br />
	[   15.895938] DMA: preallocated 4096 KiB GFP_KERNEL|GFP_DMA pool for atomic allocations<br />
	[   15.896183] DMA: preallocated 4096 KiB GFP_KERNEL|GFP_DMA32 pool for atomic allocations<br />
	[   15.896214] audit: initializing netlink subsys (disabled)<br />
	[   15.896323] audit: type=2000 audit(0.043:1): state=initialized audit_enabled=0 res=1<br />
	[   15.896895] Registered FIQ tty driver<br />
	[   15.897047] thermal_sys: Registered thermal governor 'fair_share'<br />
	[   15.897050] thermal_sys: Registered thermal governor 'step_wise'<br />
	[   15.897056] thermal_sys: Registered thermal governor 'user_space'<br />
	[   15.897061] thermal_sys: Registered thermal governor 'power_allocator'<br />
	[   15.897088] cpuidle: using governor menu<br />
	[   15.897308] hw-breakpoint: found 6 breakpoint and 4 watchpoint registers.<br />
	[   15.897439] ASID allocator initialised with 65536 entries<br />
	[   15.899515] ramoops: dmesg-0    0x18000@0x0000000000110000<br />
	[   15.899523] ramoops: dmesg-1    0x18000@0x0000000000128000<br />
	[   15.899542] ramoops: console    0x80000@0x0000000000140000<br />
	[   15.899553] ramoops: pmsg    0x30000@0x00000000001c0000<br />
	[   15.899819] printk: console [ramoops-1] enabled<br />
	[   15.899826] pstore: Registered ramoops as persistent store backend<br />
	[   15.899833] ramoops: using 0xe0000@0x110000, ecc: 0<br />
	[   15.937963] platform fdd90000.vop: Fixed dependency cycle(s) with /dp@fde50000<br />
	[   15.938001] platform fde50000.dp: Fixed dependency cycle(s) with /vop@fdd90000<br />
	[   15.938299] platform fdd90000.vop: Fixed dependency cycle(s) with /hdmi@fde80000<br />
	[   15.938333] platform fde80000.hdmi: Fixed dependency cycle(s) with /vop@fdd90000<br />
	[   15.943755] platform fed80000.phy: Fixed dependency cycle(s) with /i2c@fec80000/fusb302@22/connector<br />
	[   15.949452] rockchip-<abbr title="General purpose input/output">gpio</abbr> fd8a0000.<abbr title="General purpose input/output">gpio</abbr>: probed /pinctrl/<abbr title="General purpose input/output">gpio</abbr>@fd8a0000<br />
	[   15.949725] rockchip-<abbr title="General purpose input/output">gpio</abbr> fec20000.<abbr title="General purpose input/output">gpio</abbr>: probed /pinctrl/<abbr title="General purpose input/output">gpio</abbr>@fec20000<br />
	[   15.949949] rockchip-<abbr title="General purpose input/output">gpio</abbr> fec30000.<abbr title="General purpose input/output">gpio</abbr>: probed /pinctrl/<abbr title="General purpose input/output">gpio</abbr>@fec30000<br />
	[   15.950189] rockchip-<abbr title="General purpose input/output">gpio</abbr> fec40000.<abbr title="General purpose input/output">gpio</abbr>: probed /pinctrl/<abbr title="General purpose input/output">gpio</abbr>@fec40000<br />
	[   15.950466] rockchip-<abbr title="General purpose input/output">gpio</abbr> fec50000.<abbr title="General purpose input/output">gpio</abbr>: probed /pinctrl/<abbr title="General purpose input/output">gpio</abbr>@fec50000<br />
	[   15.950520] rockchip-pinctrl pinctrl: probed pinctrl<br />
	[   15.951920] platform fdd90000.vop: Fixed dependency cycle(s) with /hdmi@fdea0000<br />
	[   15.951957] platform fdea0000.hdmi: Fixed dependency cycle(s) with /vop@fdd90000<br />
	[   15.955986] KASLR disabled due to lack of seed<br />
	[   15.961192] HugeTLB: registered 1.00 GiB page size, pre-allocated 0 pages<br />
	[   15.961203] HugeTLB: 0 KiB vmemmap can be freed for a 1.00 GiB page<br />
	[   15.961211] HugeTLB: registered 32.0 MiB page size, pre-allocated 0 pages<br />
	[   15.961218] HugeTLB: 0 KiB vmemmap can be freed for a 32.0 MiB page<br />
	[   15.961225] HugeTLB: registered 2.00 MiB page size, pre-allocated 0 pages<br />
	[   15.961232] HugeTLB: 0 KiB vmemmap can be freed for a 2.00 MiB page<br />
	[   15.961239] HugeTLB: registered 64.0 KiB page size, pre-allocated 0 pages<br />
	[   15.961246] HugeTLB: 0 KiB vmemmap can be freed for a 64.0 KiB page<br />
	[   16.018416] raid6: neonx8   gen()  5472 MB/s<br />
	[   16.075155] raid6: neonx4   gen()  5618 MB/s<br />
	[   16.131893] raid6: neonx2   gen()  5158 MB/s<br />
	[   16.188636] raid6: neonx1   gen()  4247 MB/s<br />
	[   16.245374] raid6: int64x8  gen()  1332 MB/s<br />
	[   16.302114] raid6: int64x4  gen()  1651 MB/s<br />
	[   16.358854] raid6: int64x2  gen()  2422 MB/s<br />
	[   16.415589] raid6: int64x1  gen()  2006 MB/s<br />
	[   16.415595] raid6: using algorithm neonx4 gen() 5618 MB/s<br />
	[   16.472329] raid6: .... xor() 4303 MB/s, rmw enabled<br />
	[   16.472336] raid6: using neon recovery algorithm<br />
	[   16.472953] fiq_debugger fiq_debugger.0: error -ENXIO: IRQ fiq not found<br />
	[   16.472969] fiq_debugger fiq_debugger.0: error -ENXIO: IRQ wakeup not found<br />
	[   16.472979] fiq_debugger_probe: could not install nmi irq handler<br />
	[   16.473257] printk: console [ttyFIQ0] enabled<br />
	[   16.473372] Registered fiq debugger ttyFIQ0<br />
	[   16.532300] debugfs: Directory 'vcc_mipicsi1' with parent 'regulator' already present!<br />
	[   16.532321] debugfs: Directory 'vcc_mipicsi1' with parent 'vcc_mipicsi1' already present!<br />
	[   16.532746] iommu: Default domain type: Translated <br />
	[   16.532757] iommu: DMA domain TLB invalidation policy: strict mode <br />
	[   16.532928] SCSI subsystem initialized<br />
	[   16.533014] usbcore: registered new interface driver usbfs<br />
	[   16.533035] usbcore: registered new interface driver hub<br />
	[   16.533053] usbcore: registered new device driver usb<br />
	[   16.533105] mc: Linux media interface: v0.10<br />
	[   16.533124] videodev: Linux video capture interface: v2.00<br />
	[   16.533165] pps_core: LinuxPPS API ver. 1 registered<br />
	[   16.533173] pps_core: Software ver. 5.3.6 - Copyright 2005-2007 Rodolfo Giometti &lt;giometti@linux.it&gt;<br />
	[   16.533186] PTP clock support registered<br />
	[   16.533387] arm-scmi firmware:scmi: Enabled polling mode TX channel - prot_id:16<br />
	[   16.533442] arm-scmi firmware:scmi: SCMI Notifications - Core Enabled.<br />
	[   16.533475] arm-scmi firmware:scmi: SCMI Protocol v2.0 'rockchip:' Firmware version 0x0<br />
	[   16.534410] Advanced Linux Sound Architecture Driver Initialized.<br />
	[   16.534669] Bluetooth: Core ver 2.22<br />
	[   16.534689] NET: Registered PF_BLUETOOTH protocol family<br />
	[   16.534697] Bluetooth: HCI device and connection manager initialized<br />
	[   16.534706] Bluetooth: HCI socket layer initialized<br />
	[   16.534714] Bluetooth: L2CAP socket layer initialized<br />
	[   16.534724] Bluetooth: SCO socket layer initialized<br />
	[   16.534771] NetLabel: Initializing<br />
	[   16.534777] NetLabel:  domain hash size = 128<br />
	[   16.534784] NetLabel:  protocols = UNLABELED CIPSOv4 CALIPSO<br />
	[   16.534814] NetLabel:  unlabeled traffic allowed by default<br />
	[   16.534987] vgaarb: loaded<br />
	[   16.535312] clocksource: Switched to clocksource arch_sys_counter<br />
	[   16.535451] VFS: Disk quotas dquot_6.6.0<br />
	[   16.535477] VFS: Dquot-cache hash table entries: 512 (order 0, 4096 bytes)<br />
	[   16.535688] AppArmor: AppArmor Filesystem Enabled<br />
	[   16.541390] NET: Registered PF_INET protocol family<br />
	[   16.541587] IP idents hash table entries: 262144 (order: 9, 2097152 bytes, linear)<br />
	[   16.548590] tcp_listen_portaddr_hash hash table entries: 16384 (order: 6, 262144 bytes, linear)<br />
	[   16.548775] Table-perturb hash table entries: 65536 (order: 6, 262144 bytes, linear)<br />
	[   16.548810] TCP established hash table entries: 262144 (order: 9, 2097152 bytes, linear)<br />
	[   16.550133] TCP bind hash table entries: 65536 (order: 9, 2097152 bytes, linear)<br />
	[   16.551395] TCP: Hash tables configured (established 262144 bind 65536)<br />
	[   16.551562] MPTCP token hash table entries: 32768 (order: 7, 786432 bytes, linear)<br />
	[   16.551736] UDP hash table entries: 16384 (order: 7, 524288 bytes, linear)<br />
	[   16.552239] UDP-Lite hash table entries: 16384 (order: 7, 524288 bytes, linear)<br />
	[   16.552787] NET: Registered PF_UNIX/PF_LOCAL protocol family<br />
	[   16.553093] RPC: Registered named UNIX socket transport module.<br />
	[   16.553103] RPC: Registered udp transport module.<br />
	[   16.553110] RPC: Registered tcp transport module.<br />
	[   16.553116] RPC: Registered tcp NFSv4.1 backchannel transport module.<br />
	[   16.553571] PCI: CLS 0 bytes, default 64<br />
	[   16.554000] Trying to unpack rootfs image as initramfs...<br />
	[   16.554359] rockchip-thermal fec00000.tsadc: Missing rockchip,grf property<br />
	[   16.555253] rockchip-thermal fec00000.tsadc: tsadc is probed successfully!<br />
	[   16.569340] hw perfevents: enabled with armv8_pmuv3 PMU driver, 7 counters available<br />
	[   16.569901] kvm [1]: IPA Size Limit: 40 bits<br />
	[   16.569921] kvm [1]: GICv3: no GICV resource entry<br />
	[   16.569929] kvm [1]: disabling GICv2 emulation<br />
	[   16.569935] kvm [1]: GIC system register CPU interface enabled<br />
	[   16.570431] kvm [1]: vgic interrupt IRQ9<br />
	[   16.571014] kvm [1]: VHE mode initialized successfully<br />
	[   16.571739] Initialise system trusted keyrings<br />
	[   16.571868] workingset: timestamp_bits=46 max_order=23 bucket_order=0<br />
	[   16.574131] zbud: loaded<br />
	[   16.574935] NFS: Registering the id_resolver key type<br />
	[   16.574956] Key type id_resolver registered<br />
	[   16.574963] Key type id_legacy registered<br />
	[   16.575000] nfs4filelayout_init: NFSv4 File Layout Driver Registering...<br />
	[   16.575009] nfs4flexfilelayout_init: NFSv4 Flexfile Layout Driver Registering...<br />
	[   16.595061] NET: Registered PF_ALG protocol family<br />
	[   16.595075] xor: measuring software checksum speed<br />
	[   16.595607]    8regs           :  6245 MB/sec<br />
	[   16.596013]    32regs          :  8271 MB/sec<br />
	[   16.596353]    arm64_neon      :  9876 MB/sec<br />
	[   16.596359] xor: using function: arm64_neon (9876 MB/sec)<br />
	[   16.596370] Key type asymmetric registered<br />
	[   16.596377] Asymmetric key parser 'x509' registered<br />
	[   16.949079] Freeing initrd memory: 14404K<br />
	[   16.967740] alg: self-tests for CTR-KDF (hmac(sha256)) passed<br />
	[   16.967781] Block layer SCSI generic (bsg) driver version 0.4 loaded (major 241)<br />
	[   16.967911] io scheduler mq-deadline registered<br />
	[   16.967920] io scheduler kyber registered<br />
	[   16.969233] rockchip-csi2-dphy-hw fedc8000.csi2-dphy1-hw: csi2 dphy hw probe successfully!<br />
	[   16.978456] rockchip-hdptx-phy-hdmi fed60000.hdmiphy: hdptx phy init success<br />
	[   16.979311] rockchip-hdptx-phy-hdmi fed70000.hdmiphy: hdptx phy init success<br />
	[   16.981707] dw-pcie fe180000.pcie: invalid resource<br />
	[   16.981723] dw-pcie fe180000.pcie: Failed to initialize host<br />
	[   16.981731] dw-pcie: probe of fe180000.pcie failed with error -22<br />
	[   16.981800] dw-pcie fe190000.pcie: invalid resource<br />
	[   16.981809] dw-pcie fe190000.pcie: Failed to initialize host<br />
	[   16.981816] dw-pcie: probe of fe190000.pcie failed with error -22<br />
	[   16.981925] dw-pcie fe150000.pcie: invalid resource<br />
	[   16.981934] dw-pcie fe150000.pcie: Failed to initialize host<br />
	[   16.981954] dw-pcie: probe of fe150000.pcie failed with error -22<br />
	[   16.982087] dw-pcie fe170000.pcie: invalid resource<br />
	[   16.982097] dw-pcie fe170000.pcie: Failed to initialize host<br />
	[   16.982104] dw-pcie: probe of fe170000.pcie failed with error -22<br />
	[   16.982476] <abbr title="Rockchip">rk</abbr>-pcie fe180000.pcie: using pcie default link_up because of rockchip,default-link-up<br />
	[   16.982619] <abbr title="Rockchip">rk</abbr>-pcie fe190000.pcie: using pcie default link_up because of rockchip,default-link-up<br />
	[   16.982667] <abbr title="Rockchip">rk</abbr>-pcie fe180000.pcie: invalid prsnt-gpios property in node<br />
	[   16.982746] <abbr title="Rockchip">rk</abbr>-pcie fe190000.pcie: invalid prsnt-gpios property in node<br />
	[   16.982810] <abbr title="Rockchip">rk</abbr>-pcie fe180000.pcie: no vpcie3v3 regulator found<br />
	[   16.982874] <abbr title="Rockchip">rk</abbr>-pcie fe190000.pcie: no vpcie3v3 regulator found<br />
	[   16.982890] <abbr title="Rockchip">rk</abbr>-pcie fe150000.pcie: invalid prsnt-gpios property in node<br />
	[   16.983140] <abbr title="Rockchip">rk</abbr>-pcie fe170000.pcie: invalid prsnt-gpios property in node<br />
	[   16.983294] iep: Module initialized.<br />
	[   16.983392] mpp_service mpp-srv: 6c47657a381c author: Yandong Lin 2025-01-16 video: rockchip: mpp: Fix missing enable_irq in timeout work<br />
	[   16.983391] <abbr title="Rockchip">rk</abbr>-pcie fe180000.pcie: host bridge /pcie@fe180000 ranges:<br />
	[   16.983404] mpp_service mpp-srv: probe start<br />
	[   16.983449] <abbr title="Rockchip">rk</abbr>-pcie fe190000.pcie: host bridge /pcie@fe190000 ranges:<br />
	[   16.983454] <abbr title="Rockchip">rk</abbr>-pcie fe180000.pcie:       IO 0x00f3100000..0x00f31fffff -&gt; 0x00f3100000<br />
	[   16.983474] <abbr title="Rockchip">rk</abbr>-pcie fe180000.pcie:      MEM 0x00f3200000..0x00f3ffffff -&gt; 0x00f3200000<br />
	[   16.983488] <abbr title="Rockchip">rk</abbr>-pcie fe180000.pcie:      MEM 0x09c0000000..0x09ffffffff -&gt; 0x09c0000000<br />
	[   16.983541] <abbr title="Rockchip">rk</abbr>-pcie fe180000.pcie: iATU unroll: enabled<br />
	[   16.983549] <abbr title="Rockchip">rk</abbr>-pcie fe190000.pcie:       IO 0x00f4100000..0x00f41fffff -&gt; 0x00f4100000<br />
	[   16.983568] <abbr title="Rockchip">rk</abbr>-pcie fe190000.pcie:      MEM 0x00f4200000..0x00f4ffffff -&gt; 0x00f4200000<br />
	[   16.983582] <abbr title="Rockchip">rk</abbr>-pcie fe190000.pcie:      MEM 0x0a00000000..0x0a3fffffff -&gt; 0x0a00000000<br />
	[   16.983593] <abbr title="Rockchip">rk</abbr>-pcie fe180000.pcie: iATU regions: 8 ob, 8 ib, align 64K, limit 8G<br />
	[   16.983649] <abbr title="Rockchip">rk</abbr>-pcie fe190000.pcie: iATU unroll: enabled<br />
	[   16.983673] <abbr title="Rockchip">rk</abbr>-pcie fe190000.pcie: iATU regions: 8 ob, 8 ib, align 64K, limit 8G<br />
	[   16.984874] mpp_vepu2 jpege-ccu: probing start<br />
	[   16.984886] mpp_vepu2 jpege-ccu: probing finish<br />
	[   16.988319] mpp_rkvdec2 fdc30000.rkvdec-ccu: rkvdec-ccu, probing start<br />
	[   16.988389] mpp_rkvdec2 fdc30000.rkvdec-ccu: ccu-mode: 1<br />
	[   16.988398] mpp_rkvdec2 fdc30000.rkvdec-ccu: probing finish<br />
	[   16.988771] mpp_rkvenc2 rkvenc-ccu: probing start<br />
	[   16.988782] mpp_rkvenc2 rkvenc-ccu: probing finish<br />
	[   16.989377] mpp_service mpp-srv: probe success<br />
	[   16.999314] <abbr title="Rockchip">rk</abbr>-pcie fe150000.pcie: can't get current limit.<br />
	[   16.999580] <abbr title="Rockchip">rk</abbr>-pcie fe150000.pcie: host bridge /pcie@fe150000 ranges:<br />
	[   16.999606] <abbr title="Rockchip">rk</abbr>-pcie fe150000.pcie:       IO 0x00f0100000..0x00f01fffff -&gt; 0x00f0100000<br />
	[   16.999625] <abbr title="Rockchip">rk</abbr>-pcie fe150000.pcie:      MEM 0x00f0200000..0x00f0ffffff -&gt; 0x00f0200000<br />
	[   16.999640] <abbr title="Rockchip">rk</abbr>-pcie fe150000.pcie:      MEM 0x0900000000..0x093fffffff -&gt; 0x0900000000<br />
	[   16.999696] <abbr title="Rockchip">rk</abbr>-pcie fe150000.pcie: iATU unroll: enabled<br />
	[   16.999706] <abbr title="Rockchip">rk</abbr>-pcie fe150000.pcie: iATU regions: 8 ob, 8 ib, align 64K, limit 8G<br />
	[   17.001264] dma-pl330 fea10000.dma-controller: Loaded driver for PL330 DMAC-241330<br />
	[   17.001284] dma-pl330 fea10000.dma-controller:     DBUFF-128x8bytes Num_Chans-8 Num_Peri-32 Num_Events-16<br />
	[   17.002214] dma-pl330 fea30000.dma-controller: Loaded driver for PL330 DMAC-241330<br />
	[   17.002230] dma-pl330 fea30000.dma-controller:     DBUFF-128x8bytes Num_Chans-8 Num_Peri-32 Num_Events-16<br />
	[   17.003141] dma-pl330 fed10000.dma-controller: Loaded driver for PL330 DMAC-241330<br />
	[   17.003156] dma-pl330 fed10000.dma-controller:     DBUFF-128x8bytes Num_Chans-8 Num_Peri-32 Num_Events-16<br />
	[   17.003619] rockchip-pvtm fda40000.pvtm: pvtm@0 probed<br />
	[   17.003685] rockchip-pvtm fda50000.pvtm: pvtm@1 probed<br />
	[   17.003744] rockchip-pvtm fda60000.pvtm: pvtm@2 probed<br />
	[   17.003801] rockchip-pvtm fdaf0000.pvtm: pvtm@3 probed<br />
	[   17.003855] rockchip-pvtm fdb30000.pvtm: pvtm@4 probed<br />
	[   17.004518] rockchip-system-monitor rockchip-system-monitor: system monitor probe<br />
	[   17.005440] Serial: 8250/16550 driver, 10 ports, IRQ sharing disabled<br />
	[   17.006039] febc0000.serial: ttyS9 at MMIO 0xfebc0000 (irq = 45, base_baud = 1500000) is a 16550A<br />
	[   17.007378] random: crng init done<br />
	[   17.007451] led_vk2c21_init<br />
	[   17.007451] =============================================<br />
	[   17.013034] rk_iommu fdca0000.iommu: av1d iommu enabled<br />
	[   17.015293] rockchip-vop2 fdd90000.vop: Adding to iommu group 17<br />
	[   17.024843] rockchip-vop2 fdd90000.vop: [drm:vop2_bind] vp0 assign plane mask: Cluster0 | Esmart0[0x5], primary plane phy id: Cluster0[0]<br />
	[   17.024878] rockchip-vop2 fdd90000.vop: [drm:vop2_bind] vp1 assign plane mask: Cluster1 | Esmart1[0xa], primary plane phy id: Cluster1[1]<br />
	[   17.024897] rockchip-vop2 fdd90000.vop: [drm:vop2_bind] vp2 assign plane mask: Cluster2 | Esmart2[0x140], primary plane phy id: Cluster2[6]<br />
	[   17.024915] rockchip-vop2 fdd90000.vop: [drm:vop2_bind] vp3 assign plane mask: Cluster3 | Esmart3[0x280], primary plane phy id: Cluster3[7]<br />
	[   17.025023] rockchip-vop2 fdd90000.vop: [drm:vop2_bind] Esmart0-win0 as cursor plane for vp0<br />
	[   17.025118] rockchip-vop2 fdd90000.vop: [drm:vop2_bind] Esmart1-win0 as cursor plane for vp1<br />
	[   17.025207] rockchip-vop2 fdd90000.vop: [drm:vop2_bind] Esmart2-win0 as cursor plane for vp2<br />
	[   17.025235] [drm] failed to init overlay plane Cluster0-win1<br />
	[   17.025244] [drm] failed to init overlay plane Cluster1-win1<br />
	[   17.025253] [drm] failed to init overlay plane Cluster2-win1<br />
	[   17.025294] [drm] failed to init overlay plane Cluster3-win1<br />
	[   17.037197] rockchip-vop2 fdd90000.vop: bin=0<br />
	[   17.037419] rockchip-vop2 fdd90000.vop: leakage=35<br />
	[   17.037433] rockchip-vop2 fdd90000.vop: leakage-volt-sel=1<br />
	[   17.037499] rockchip-vop2 fdd90000.vop: error -ENODEV: _opp_set_regulators: no regulator (vop) found<br />
	[   17.037530] rockchip-vop2 fdd90000.vop: failed to set opp config<br />
	[   17.037540] rockchip-vop2 fdd90000.vop: failed to init opp info<br />
	[   17.037550] rockchip-vop2 fdd90000.vop: Unsupported VOP aclk dvfs<br />
	[   17.037571] rockchip-drm display-subsystem: bound fdd90000.vop (ops 0xffff8000093fe4a8)<br />
	[   17.038217] dwhdmi-rockchip fde80000.hdmi: registered ddc I2C bus driver<br />
	[   17.038833] rockchip-drm display-subsystem: bound fde80000.hdmi (ops 0xffff800009417528)<br />
	[   17.039405] dwhdmi-rockchip fdea0000.hdmi: registered ddc I2C bus driver<br />
	[   17.039987] rockchip-drm display-subsystem: bound fdea0000.hdmi (ops 0xffff800009417528)<br />
	[   17.040222] rockchip-drm display-subsystem: bound fde50000.dp (ops 0xffff80000941a588)<br />
	[   17.041489] [drm] Initialized rockchip 4.0.0 20140818 for display-subsystem on minor 0<br />
	[   17.041520] rockchip-drm display-subsystem: failed to parse loader memory<br />
	[   17.041600] rockchip-drm display-subsystem: [drm] Cannot find any crtc or sizes<br />
	[   17.041665] rockchip-drm display-subsystem: [drm] Cannot find any crtc or sizes<br />
	[   17.041696] rockchip-drm display-subsystem: [drm] Cannot find any crtc or sizes<br />
	[   17.041860] rockchip-drm display-subsystem: [drm] run display error_event monitor<br />
	[   17.042549] dw-hdmi-qp-hdcp dw-hdmi-qp-hdcp.2.auto: dw_hdcp_qp_hdcp_probe success<br />
	[   17.042707] dw-hdmi-qp-hdcp dw-hdmi-qp-hdcp.5.auto: dw_hdcp_qp_hdcp_probe success<br />
	[   17.043265] Registered IR keymap <abbr title="Release candidate">rc</abbr>-cec<br />
	[   17.043333] <abbr title="Release candidate">rc</abbr> rc0: dw_hdmi_qp as /devices/platform/fde80000.hdmi/<abbr title="Release candidate">rc</abbr>/rc0<br />
	[   17.043436] input: dw_hdmi_qp as /devices/platform/fde80000.hdmi/<abbr title="Release candidate">rc</abbr>/rc0/input0<br />
	[   17.043811] Registered IR keymap <abbr title="Release candidate">rc</abbr>-cec<br />
	[   17.043874] <abbr title="Release candidate">rc</abbr> rc1: dw_hdmi_qp as /devices/platform/fdea0000.hdmi/<abbr title="Release candidate">rc</abbr>/rc1<br />
	[   17.043968] input: dw_hdmi_qp as /devices/platform/fdea0000.hdmi/<abbr title="Release candidate">rc</abbr>/rc1/input1<br />
	[   17.045378] <abbr title="Rockchip">rk</abbr>-pcie fe170000.pcie: can't get current limit.<br />
	[   17.045647] <abbr title="Rockchip">rk</abbr>-pcie fe170000.pcie: host bridge /pcie@fe170000 ranges:<br />
	[   17.045673] <abbr title="Rockchip">rk</abbr>-pcie fe170000.pcie:       IO 0x00f2100000..0x00f21fffff -&gt; 0x00f2100000<br />
	[   17.045691] <abbr title="Rockchip">rk</abbr>-pcie fe170000.pcie:      MEM 0x00f2200000..0x00f2ffffff -&gt; 0x00f2200000<br />
	[   17.045706] <abbr title="Rockchip">rk</abbr>-pcie fe170000.pcie:      MEM 0x0980000000..0x09bfffffff -&gt; 0x0980000000<br />
	[   17.045766] <abbr title="Rockchip">rk</abbr>-pcie fe170000.pcie: iATU unroll: enabled<br />
	[   17.045776] <abbr title="Rockchip">rk</abbr>-pcie fe170000.pcie: iATU regions: 8 ob, 8 ib, align 64K, limit 8G<br />
	[   17.046259] brd: module loaded<br />
	[   17.049196] loop: module loaded<br />
	[   17.049418] rbd: loaded (major 254)<br />
	[   17.049585] lkdtm: No crash points registered, enable through debugfs<br />
	[   17.051799] rockchip-spi feb20000.spi: no high_speed pinctrl state<br />
	[   17.052208] spi spi2.0: Fixed dependency cycle(s) with /spi@feb20000/rk806single@0/regulators/DCDC_REG7<br />
	[   17.052260] spi spi2.0: Fixed dependency cycle(s) with /spi@feb20000/rk806single@0/pinctrl_rk806/rk806_dvs1_pwrdn<br />
	[   17.052280] spi spi2.0: Fixed dependency cycle(s) with /spi@feb20000/rk806single@0/pinctrl_rk806/rk806_dvs3_null<br />
	[   17.052299] spi spi2.0: Fixed dependency cycle(s) with /spi@feb20000/rk806single@0/pinctrl_rk806/rk806_dvs2_null<br />
	[   17.052317] spi spi2.0: Fixed dependency cycle(s) with /spi@feb20000/rk806single@0/pinctrl_rk806/rk806_dvs1_null<br />
	[   17.052836] rk806 spi2.0: chip id: RK806,ver:0x2, 0x1<br />
	[   17.052969] rk806 spi2.0: ON: 0x20 OFF:0x2<br />
	[   17.053046] rk806 spi2.0: shutdown-sequence missing!<br />
	[   17.053058] rk806 spi2.0: vb-shutdown-sequence missing!<br />
	[   17.053068] rk806 spi2.0: dvs-suspend-control-by missing!<br />
	[   17.061782] avdd_0v75_s0: Bringing 750000uV into 837500-837500uV<br />
	[   17.066440] rk806 spi2.0: no sleep-setting state<br />
	[   17.066457] rk806 spi2.0: no reset-setting pinctrl state<br />
	[   17.066467] rk806 spi2.0: no dvs-setting pinctrl state<br />
	[   17.067053] rockchip-spi feb20000.spi: register misc device rkspi-dev2<br />
	[   17.067068] rockchip-spi feb20000.spi: probed, poll=0, rsd=0, cs-inactive=0, ready=0<br />
	[   17.068444] spi-nor spi5.0: XM25QU128C (16384 Kbytes) read_data x4<br />
	[   17.068491] 1 fixed-partitions partitions found on MTD device sfc_nor<br />
	[   17.068504] Creating 1 MTD partitions on "sfc_nor":<br />
	[   17.068514] 0x000000000000-0x000001000000 : "loader"<br />
	[   17.071365] usbcore: registered new interface driver rndis_wlan<br />
	[   17.071398] usbcore: registered new interface driver asix<br />
	[   17.071420] usbcore: registered new interface driver cdc_ether<br />
	[   17.071443] usbcore: registered new interface driver rndis_host<br />
	[   17.071468] usbcore: registered new interface driver cdc_ncm<br />
	[   17.071585] VFIO - User Level meta-driver version: 0.3<br />
	[   17.072156] platform fc000000.usb: Fixed dependency cycle(s) with /i2c@fec80000/fusb302@22<br />
	[   17.085814] phy phy-fd5d4000.syscon:usb2-phy@4000.3: illegal mode<br />
	[   17.085838] xhci-hcd xhci-hcd.12.auto: xHCI Host Controller<br />
	[   17.085855] xhci-hcd xhci-hcd.12.auto: new USB bus registered, assigned bus number 1<br />
	[   17.085949] xhci-hcd xhci-hcd.12.auto: hcc params 0x0220fe64 hci version 0x110 quirks 0x0002008002010010<br />
	[   17.085984] xhci-hcd xhci-hcd.12.auto: irq 86, io mem 0xfc400000<br />
	[   17.086068] xhci-hcd xhci-hcd.12.auto: xHCI Host Controller<br />
	[   17.086081] xhci-hcd xhci-hcd.12.auto: new USB bus registered, assigned bus number 2<br />
	[   17.086096] xhci-hcd xhci-hcd.12.auto: Host supports USB 3.0 SuperSpeed<br />
	[   17.086190] usb usb1: New USB device found, idVendor=1d6b, idProduct=0002, bcdDevice= 6.01<br />
	[   17.086206] usb usb1: New USB device strings: Mfr=3, Product=2, SerialNumber=1<br />
	[   17.086218] usb usb1: Product: xHCI Host Controller<br />
	[   17.086228] usb usb1: Manufacturer: Linux 6.1.115-vendor-rk35xx xhci-hcd<br />
	[   17.086239] usb usb1: SerialNumber: xhci-hcd.12.auto<br />
	[   17.086534] hub 1-0:1.0: USB hub found<br />
	[   17.086559] hub 1-0:1.0: 1 port detected<br />
	[   17.086759] usb usb2: We don't know the algorithms for LPM for this host, disabling LPM.<br />
	[   17.086826] usb usb2: New USB device found, idVendor=1d6b, idProduct=0003, bcdDevice= 6.01<br />
	[   17.086841] usb usb2: New USB device strings: Mfr=3, Product=2, SerialNumber=1<br />
	[   17.086853] usb usb2: Product: xHCI Host Controller<br />
	[   17.086862] usb usb2: Manufacturer: Linux 6.1.115-vendor-rk35xx xhci-hcd<br />
	[   17.086873] usb usb2: SerialNumber: xhci-hcd.12.auto<br />
	[   17.087132] hub 2-0:1.0: USB hub found<br />
	[   17.087155] hub 2-0:1.0: 1 port detected<br />
	[   17.087354] usbcore: registered new interface driver cdc_acm<br />
	[   17.087366] cdc_acm: USB Abstract Control Model driver for USB modems and ISDN adapters<br />
	[   17.087412] ehci-platform fc800000.usb: EHCI Host Controller<br />
	[   17.087437] ehci-platform fc800000.usb: new USB bus registered, assigned bus number 3<br />
	[   17.087442] ohci-platform fc840000.usb: Generic Platform OHCI controller<br />
	[   17.087477] usbcore: registered new interface driver uas<br />
	[   17.087486] ehci-platform fc880000.usb: EHCI Host Controller<br />
	[   17.087499] ohci-platform fc840000.usb: new USB bus registered, assigned bus number 4<br />
	[   17.087507] ehci-platform fc880000.usb: new USB bus registered, assigned bus number 5<br />
	[   17.087515] ohci-platform fc8c0000.usb: Generic Platform OHCI controller<br />
	[   17.087521] usbcore: registered new interface driver usb-storage<br />
	[   17.087528] ehci-platform fc800000.usb: irq 87, io mem 0xfc800000<br />
	[   17.087540] ohci-platform fc8c0000.usb: new USB bus registered, assigned bus number 6<br />
	[   17.087610] ehci-platform fc880000.usb: irq 88, io mem 0xfc880000<br />
	[   17.087637] ohci-platform fc840000.usb: irq 89, io mem 0xfc840000<br />
	[   17.087672] ohci-platform fc8c0000.usb: irq 90, io mem 0xfc8c0000<br />
	[   17.087807] mousedev: PS/2 mouse device common for all mice<br />
	[   17.088351] .. <abbr title="Rockchip">rk</abbr> pwm remotectl v2.0 init<br />
	[   17.088497] input: febf0030.pwm as /devices/platform/febf0030.pwm/input/input2<br />
	[   17.088711] remotectl-pwm febf0030.pwm: Controller support pwrkey capture<br />
	[   17.088942] i2c_dev: i2c /dev entries driver<br />
	[   17.098664] ehci-platform fc800000.usb: USB 2.0 started, EHCI 1.00<br />
	[   17.098846] usb usb3: New USB device found, idVendor=1d6b, idProduct=0002, bcdDevice= 6.01<br />
	[   17.098868] usb usb3: New USB device strings: Mfr=3, Product=2, SerialNumber=1<br />
	[   17.098880] usb usb3: Product: EHCI Host Controller<br />
	[   17.098891] usb usb3: Manufacturer: Linux 6.1.115-vendor-rk35xx ehci_hcd<br />
	[   17.098901] usb usb3: SerialNumber: fc800000.usb<br />
	[   17.099188] hub 3-0:1.0: USB hub found<br />
	[   17.099225] hub 3-0:1.0: 1 port detected<br />
	[   17.111996] ehci-platform fc880000.usb: USB 2.0 started, EHCI 1.00<br />
	[   17.112186] usb usb5: New USB device found, idVendor=1d6b, idProduct=0002, bcdDevice= 6.01<br />
	[   17.112206] usb usb5: New USB device strings: Mfr=3, Product=2, SerialNumber=1<br />
	[   17.112219] usb usb5: Product: EHCI Host Controller<br />
	[   17.112229] usb usb5: Manufacturer: Linux 6.1.115-vendor-rk35xx ehci_hcd<br />
	[   17.112240] usb usb5: SerialNumber: fc880000.usb<br />
	[   17.112541] hub 5-0:1.0: USB hub found<br />
	[   17.112579] hub 5-0:1.0: 1 port detected<br />
	[   17.119357] rtc-hym8563 6-0051: rtc information is valid<br />
	[   17.122027] rtc-hym8563 6-0051: registered as rtc0<br />
	[   17.122310] rtc-hym8563 6-0051: setting system clock to 2021-01-01T12:04:12 UTC (1609502652)<br />
	[   17.123836] rkcifhw fdce0000.rkcif: Adding to iommu group 16<br />
	[   17.124707] rkcifhw fdce0000.rkcif: No reserved memory region assign to CIF<br />
	[   17.125519] rockchip-mipi-csi2-hw fdd10000.mipi0-csi2-hw: enter mipi csi2 hw probe!<br />
	[   17.125626] rockchip-mipi-csi2-hw fdd10000.mipi0-csi2-hw: probe success, v4l2_dev:mipi0-csi2-hw!<br />
	[   17.125675] rockchip-mipi-csi2-hw fdd20000.mipi1-csi2-hw: enter mipi csi2 hw probe!<br />
	[   17.125761] rockchip-mipi-csi2-hw fdd20000.mipi1-csi2-hw: probe success, v4l2_dev:mipi1-csi2-hw!<br />
	[   17.125803] rockchip-mipi-csi2-hw fdd30000.mipi2-csi2-hw: enter mipi csi2 hw probe!<br />
	[   17.125884] rockchip-mipi-csi2-hw fdd30000.mipi2-csi2-hw: probe success, v4l2_dev:mipi2-csi2-hw!<br />
	[   17.125925] rockchip-mipi-csi2-hw fdd40000.mipi3-csi2-hw: enter mipi csi2 hw probe!<br />
	[   17.126008] rockchip-mipi-csi2-hw fdd40000.mipi3-csi2-hw: probe success, v4l2_dev:mipi3-csi2-hw!<br />
	[   17.126049] rockchip-mipi-csi2-hw fdd50000.mipi4-csi2-hw: enter mipi csi2 hw probe!<br />
	[   17.126130] rockchip-mipi-csi2-hw fdd50000.mipi4-csi2-hw: probe success, v4l2_dev:mipi4-csi2-hw!<br />
	[   17.126174] rockchip-mipi-csi2-hw fdd60000.mipi5-csi2-hw: enter mipi csi2 hw probe!<br />
	[   17.126254] rockchip-mipi-csi2-hw fdd60000.mipi5-csi2-hw: probe success, v4l2_dev:mipi5-csi2-hw!<br />
	[   17.127328] rkisp_hw fdcb0000.rkisp: Adding to iommu group 15<br />
	[   17.127460] rkisp_hw fdcb0000.rkisp: is_thunderboot: 0<br />
	[   17.127473] rkisp_hw fdcb0000.rkisp: Missing rockchip,grf property<br />
	[   17.127494] rkisp_hw fdcb0000.rkisp: max input:0x0@0fps<br />
	[   17.127612] rkisp_hw fdcb0000.rkisp: no find phandle sram<br />
	[   17.128874] usbcore: registered new interface driver uvcvideo<br />
	[   17.130538] cpu cpu0: bin=0<br />
	[   17.130724] cpu cpu0: leakage=12<br />
	[   17.132184] cpu cpu0: pvtm=1415<br />
	[   17.132337] cpu cpu0: pvtm-volt-sel=1<br />
	[   17.134384] cpu cpu4: bin=0<br />
	[   17.134569] cpu cpu4: leakage=9<br />
	[   17.141177] cpu cpu4: pvtm=1631<br />
	[   17.145225] cpu cpu4: pvtm-volt-sel=2<br />
	[   17.146236] usb usb4: New USB device found, idVendor=1d6b, idProduct=0001, bcdDevice= 6.01<br />
	[   17.146285] usb usb4: New USB device strings: Mfr=3, Product=2, SerialNumber=1<br />
	[   17.146318] usb usb4: Product: Generic Platform OHCI controller<br />
	[   17.146336] usb usb4: Manufacturer: Linux 6.1.115-vendor-rk35xx ohci_hcd<br />
	[   17.146364] usb usb4: SerialNumber: fc840000.usb<br />
	[   17.146918] hub 4-0:1.0: USB hub found<br />
	[   17.146986] hub 4-0:1.0: 1 port detected<br />
	[   17.147605] usb usb6: New USB device found, idVendor=1d6b, idProduct=0001, bcdDevice= 6.01<br />
	[   17.147648] usb usb6: New USB device strings: Mfr=3, Product=2, SerialNumber=1<br />
	[   17.147680] usb usb6: Product: Generic Platform OHCI controller<br />
	[   17.147707] usb usb6: Manufacturer: Linux 6.1.115-vendor-rk35xx ohci_hcd<br />
	[   17.147734] usb usb6: SerialNumber: fc8c0000.usb<br />
	[   17.148054] cpu cpu6: bin=0<br />
	[   17.148238] cpu cpu6: leakage=9<br />
	[   17.148316] hub 6-0:1.0: USB hub found<br />
	[   17.148386] hub 6-0:1.0: 1 port detected<br />
	[   17.154875] cpu cpu6: pvtm=1620<br />
	[   17.158965] cpu cpu6: pvtm-volt-sel=2<br />
	[   17.161011] cpu cpu0: avs=0<br />
	[   17.161071] cpu cpu0: rockchip_pvtpll_set_volt_sel: error cfg clk_id=0 voltsel (-1)<br />
	[   17.162343] cpu cpu4: avs=0<br />
	[   17.162396] cpu cpu4: rockchip_pvtpll_set_volt_sel: error cfg clk_id=2 voltsel (-1)<br />
	[   17.163497] cpu cpu6: avs=0<br />
	[   17.163550] cpu cpu6: rockchip_pvtpll_set_volt_sel: error cfg clk_id=3 voltsel (-1)<br />
	[   17.163656] cpu cpu0: l=15000 h=85000 hyst=5000 l_limit=0 h_limit=1608000000 h_table=0<br />
	[   17.164019] cpu cpu0: EM: created perf domain<br />
	[   17.164469] cpu cpu4: l=15000 h=85000 hyst=5000 l_limit=0 h_limit=2208000000 h_table=0<br />
	[   17.172863] cpu cpu4: EM: created perf domain<br />
	[   17.173582] cpu cpu6: l=15000 h=85000 hyst=5000 l_limit=0 h_limit=2208000000 h_table=0<br />
	[   17.185881] <abbr title="Rockchip">rk</abbr>-pcie fe180000.pcie: PCIe Linking... LTSSM is 0x3<br />
	[   17.185958] <abbr title="Rockchip">rk</abbr>-pcie fe190000.pcie: PCIe Linking... LTSSM is 0x3<br />
	[   17.191130] cpu cpu6: EM: created perf domain<br />
	[   17.193012] sdhci: Secure Digital Host Controller Interface driver<br />
	[   17.193037] sdhci: Copyright(c) Pierre Ossman<br />
	[   17.193051] Synopsys Designware Multimedia Card Interface Driver<br />
	[   17.193849] sdhci-pltfm: SDHCI platform and OF driver helper<br />
	[   17.194318] dwmmc_rockchip fe2c0000.mmc: No normal pinctrl state<br />
	[   17.194337] dwmmc_rockchip fe2c0000.mmc: No idle pinctrl state<br />
	[   17.194395] dwmmc_rockchip fe2c0000.mmc: IDMAC supports 32-bit address mode.<br />
	[   17.194419] dwmmc_rockchip fe2c0000.mmc: Using internal DMA controller.<br />
	[   17.194437] dwmmc_rockchip fe2c0000.mmc: Version ID is 270a<br />
	[   17.194477] dwmmc_rockchip fe2c0000.mmc: DW MMC controller at irq 118,32 bit host data width,256 deep fifo<br />
	[   17.196461] mmc0: CQHCI version 5.10<br />
	[   17.197225] ledtrig-cpu: registered to indicate activity on CPUs<br />
	[   17.197323] arm-scmi firmware:scmi: Failed. SCMI protocol 17 not active.<br />
	[   17.197388] SMCCC: SOC_ID: ARCH_SOC_ID not implemented, skipping ....<br />
	[   17.198275] cryptodev: driver 1.12 loaded.<br />
	[   17.198324] hid: raw HID events driver (C) Jiri Kosina<br />
	[   17.198511] usbcore: registered new interface driver usbhid<br />
	[   17.198520] usbhid: USB HID core driver<br />
	[   17.201596] SPI driver inv-icm42600-spi has no spi_device_id for invensense,icm42600<br />
	[   17.201610] SPI driver inv-icm42600-spi has no spi_device_id for invensense,icm42602<br />
	[   17.201619] SPI driver inv-icm42600-spi has no spi_device_id for invensense,icm42605<br />
	[   17.201628] SPI driver inv-icm42600-spi has no spi_device_id for invensense,icm42622<br />
	[   17.201904] optee: probing for conduit method.<br />
	[   17.201915] optee: api uid mismatch<br />
	[   17.201922] optee: probe of firmware:optee failed with error -22<br />
	[   17.201994] <abbr title="Rockchip">rk</abbr>-pcie fe150000.pcie: PCIe Linking... LTSSM is 0x3<br />
	[   17.202412] usbcore: registered new interface driver snd-usb-audio<br />
	[   17.204456] [Awinic] aw87xxx_pa_init:driver version: v2.2.0<br />
	[   17.205398] rockchip-i2s-tdm fddf0000.i2s: CLK-ALWAYS-ON: mclk: 12288000, bclk: 3072000, fsync: 48000<br />
	[   17.205952] rockchip-i2s-tdm fe470000.i2s: Register PCM for TRCM mode<br />
	[   17.206350] rockchip-i2s-tdm fddf4000.i2s: CLK-ALWAYS-ON: mclk: 12288000, bclk: 3072000, fsync: 48000<br />
	[   17.206474] rockchip-i2s-tdm fddf8000.i2s: Init RX wait-time-ms: 50<br />
	[   17.208277] debugfs: File 'Capture' in directory 'dapm' already present!<br />
	[   17.208855] input: rockchip-dp0 rockchip-dp0 as /devices/platform/dp0-sound/sound/card0/input3<br />
	[   17.209912] input: rockchip-hdmi0 rockchip-hdmi0 as /devices/platform/hdmi0-sound/sound/card1/input4<br />
	[   17.210820] input: rockchip-hdmi1 rockchip-hdmi1 as /devices/platform/hdmi1-sound/sound/card2/input5<br />
	[   17.211616] input: headset-keys as /devices/platform/es8388-sound/input/input6<br />
	[   17.214912] mmc_host mmc1: Bus speed (slot 0) = 400000Hz (slot req 400000Hz, actual 400000HZ div = 0)<br />
	[   17.223172] <abbr title="Rockchip">rk</abbr>-pcie fe150000.pcie: PCIe Linking... LTSSM is 0x210022<br />
	[   17.228179] mmc0: SDHCI controller on fe2e0000.mmc [fe2e0000.mmc] using ADMA<br />
	[   17.247966] <abbr title="Rockchip">rk</abbr>-pcie fe170000.pcie: PCIe Linking... LTSSM is 0x3<br />
	[   17.262142] <abbr title="Rockchip">rk</abbr>-pcie fe190000.pcie: PCIe Link up, LTSSM is 0x130011<br />
	[   17.262214] <abbr title="Rockchip">rk</abbr>-pcie fe190000.pcie: PCIe Gen.2 x1 link up<br />
	[   17.262233] <abbr title="Rockchip">rk</abbr>-pcie fe180000.pcie: PCIe Link up, LTSSM is 0x130011<br />
	[   17.262256] <abbr title="Rockchip">rk</abbr>-pcie fe180000.pcie: PCIe Gen.2 x1 link up<br />
	[   17.262524] <abbr title="Rockchip">rk</abbr>-pcie fe190000.pcie: PCI host bridge to bus 0004:40<br />
	[   17.262578] pci_bus 0004:40: root bus resource [bus 40-4f]<br />
	[   17.262589] <abbr title="Rockchip">rk</abbr>-pcie fe180000.pcie: PCI host bridge to bus 0003:30<br />
	[   17.262614] pci_bus 0004:40: root bus resource [io  0x100000-0x1fffff] (bus address [0xf4100000-0xf41fffff])<br />
	[   17.262637] pci_bus 0003:30: root bus resource [bus 30-3f]<br />
	[   17.262662] pci_bus 0004:40: root bus resource [mem 0xf4200000-0xf4ffffff]<br />
	[   17.262685] pci_bus 0003:30: root bus resource [io  0x0000-0xfffff] (bus address [0xf3100000-0xf31fffff])<br />
	[   17.262703] pci_bus 0004:40: root bus resource [mem 0xa00000000-0xa3fffffff pref]<br />
	[   17.262731] pci_bus 0003:30: root bus resource [mem 0xf3200000-0xf3ffffff]<br />
	[   17.262795] pci 0004:40:00.0: [1d87:3588] type 01 class 0x060400<br />
	[   17.262834] pci 0004:40:00.0: reg 0x38: [mem 0x00000000-0x0000ffff pref]<br />
	[   17.262920] pci_bus 0003:30: root bus resource [mem 0x9c0000000-0x9ffffffff pref]<br />
	[   17.262923] pci 0004:40:00.0: supports D1 D2<br />
	[   17.262935] pci 0004:40:00.0: PME# supported from D0 D1 D3hot<br />
	[   17.262992] pci 0003:30:00.0: [1d87:3588] type 01 class 0x060400<br />
	[   17.263028] pci 0003:30:00.0: reg 0x38: [mem 0x00000000-0x0000ffff pref]<br />
	[   17.263126] pci 0003:30:00.0: supports D1 D2<br />
	[   17.263169] pci 0003:30:00.0: PME# supported from D0 D1 D3hot<br />
	[   17.268681] <abbr title="Rockchip">rk</abbr>-pcie fe170000.pcie: PCIe Linking... LTSSM is 0x3<br />
	[   17.284557] input: rockchip-es8388 Headset as /devices/platform/es8388-sound/sound/card3/input7<br />
	[   17.287639] pci 0004:40:00.0: Primary bus is hard wired to 0<br />
	[   17.287665] pci 0004:40:00.0: bridge configuration invalid ([bus 01-ff]), reconfiguring<br />
	[   17.287819] pci 0004:41:00.0: [10ec:8125] type 00 class 0x020000<br />
	[   17.287867] pci 0003:30:00.0: Primary bus is hard wired to 0<br />
	[   17.287882] pci 0004:41:00.0: reg 0x10: [io  0x0000-0x00ff]<br />
	[   17.287886] pci 0003:30:00.0: bridge configuration invalid ([bus 01-ff]), reconfiguring<br />
	[   17.287951] pci 0004:41:00.0: reg 0x18: [mem 0x00000000-0x0000ffff 64bit]<br />
	[   17.288003] pci 0004:41:00.0: reg 0x20: [mem 0x00000000-0x00003fff 64bit]<br />
	[   17.288094] pci 0003:31:00.0: [10ec:8125] type 00 class 0x020000<br />
	[   17.288194] pci 0003:31:00.0: reg 0x10: initial BAR value 0x00000000 invalid<br />
	[   17.288209] pci 0003:31:00.0: reg 0x10: [io  size 0x0100]<br />
	[   17.288329] pci 0003:31:00.0: reg 0x18: [mem 0x00000000-0x0000ffff 64bit]<br />
	[   17.288412] pci 0003:31:00.0: reg 0x20: [mem 0x00000000-0x00003fff 64bit]<br />
	[   17.288550] pci 0004:41:00.0: supports D1 D2<br />
	[   17.288564] pci 0004:41:00.0: PME# supported from D0 D1 D2 D3hot D3cold<br />
	[   17.288955] pci 0003:31:00.0: supports D1 D2<br />
	[   17.288970] pci 0003:31:00.0: PME# supported from D0 D1 D2 D3hot D3cold<br />
	[   17.289399] pci_bus 0004:41: busn_res: [bus 41-4f] end is updated to 41<br />
	[   17.289435] pci 0004:40:00.0: BAR 8: assigned [mem 0xf4200000-0xf42fffff]<br />
	[   17.289453] pci 0004:40:00.0: BAR 6: assigned [mem 0xf4300000-0xf430ffff pref]<br />
	[   17.289471] pci 0004:40:00.0: BAR 7: assigned [io  0x100000-0x100fff]<br />
	[   17.289490] pci 0004:41:00.0: BAR 2: assigned [mem 0xf4200000-0xf420ffff 64bit]<br />
	[   17.289535] pci 0004:41:00.0: BAR 4: assigned [mem 0xf4210000-0xf4213fff 64bit]<br />
	[   17.289588] pci 0004:41:00.0: BAR 0: assigned [io  0x100000-0x1000ff]<br />
	[   17.289613] pci 0004:40:00.0: PCI bridge to [bus 41]<br />
	[   17.289627] pci 0004:40:00.0:   bridge window [io  0x100000-0x100fff]<br />
	[   17.289631] pci_bus 0003:31: busn_res: [bus 31-3f] end is updated to 31<br />
	[   17.289646] pci 0003:30:00.0: BAR 8: assigned [mem 0xf3200000-0xf32fffff]<br />
	[   17.289653] pci 0004:40:00.0:   bridge window [mem 0xf4200000-0xf42fffff]<br />
	[   17.289661] pci 0003:30:00.0: BAR 6: assigned [mem 0xf3300000-0xf330ffff pref]<br />
	[   17.289667] pci 0003:30:00.0: BAR 7: assigned [io  0x1000-0x1fff]<br />
	[   17.289700] pci 0003:31:00.0: BAR 2: assigned [mem 0xf3200000-0xf320ffff 64bit]<br />
	[   17.289745] pci 0003:31:00.0: BAR 4: assigned [mem 0xf3210000-0xf3213fff 64bit]<br />
	[   17.289789] pci 0003:31:00.0: BAR 0: assigned [io  0x1000-0x10ff]<br />
	[   17.289812] pci 0003:30:00.0: PCI bridge to [bus 31]<br />
	[   17.289826] pci 0003:30:00.0:   bridge window [io  0x1000-0x1fff]<br />
	[   17.289831] <abbr title="Rockchip">rk</abbr>-pcie fe170000.pcie: PCIe Linking... LTSSM is 0x3<br />
	[   17.289851] pci 0003:30:00.0:   bridge window [mem 0xf3200000-0xf32fffff]<br />
	[   17.292635] pcieport 0004:40:00.0: PME: Signaling with IRQ 135<br />
	[   17.292842] pcieport 0003:30:00.0: PME: Signaling with IRQ 144<br />
	[   17.298789] <abbr title="Rockchip">rk</abbr>-pcie fe150000.pcie: PCIe Link up, LTSSM is 0x230011<br />
	[   17.298835] <abbr title="Rockchip">rk</abbr>-pcie fe150000.pcie: PCIe Gen.3 x4 link up<br />
	[   17.299039] <abbr title="Rockchip">rk</abbr>-pcie fe150000.pcie: PCI host bridge to bus 0000:00<br />
	[   17.299071] pci_bus 0000:00: root bus resource [bus 00-0f]<br />
	[   17.299100] pci_bus 0000:00: root bus resource [io  0x200000-0x2fffff] (bus address [0xf0100000-0xf01fffff])<br />
	[   17.299133] pci_bus 0000:00: root bus resource [mem 0xf0200000-0xf0ffffff]<br />
	[   17.299159] pci_bus 0000:00: root bus resource [mem 0x900000000-0x93fffffff pref]<br />
	[   17.299211] pci 0000:00:00.0: [1d87:3588] type 01 class 0x060400<br />
	[   17.299251] pci 0000:00:00.0: reg 0x38: [mem 0x00000000-0x0000ffff pref]<br />
	[   17.299326] pci 0000:00:00.0: supports D1 D2<br />
	[   17.299350] pci 0000:00:00.0: PME# supported from D0 D1 D3hot<br />
	[   17.308621] mmc_host mmc1: Bus speed (slot 0) = 148500000Hz (slot req 150000000Hz, actual 148500000HZ div = 0)<br />
	[   17.310964] <abbr title="Rockchip">rk</abbr>-pcie fe170000.pcie: PCIe Linking... LTSSM is 0x3<br />
	[   17.313985] pci_bus 0000:01: busn_res: can not insert [bus 01-ff] under [bus 00-0f] (conflicts with (null) [bus 00-0f])<br />
	[   17.314101] pci 0000:01:00.0: [c0a9:5427] type 00 class 0x010802<br />
	[   17.314199] pci 0000:01:00.0: reg 0x10: [mem 0x00000000-0x00003fff 64bit]<br />
	[   17.314790] pci 0000:01:00.0: 31.504 Gb/s available PCIe bandwidth, limited by 8.0 GT/s PCIe x4 link at 0000:00:00.0 (capable of 63.012 Gb/s with 16.0 GT/s PCIe x4 link)<br />
	[   17.325574] pci 0000:00:00.0: BAR 8: assigned [mem 0xf0200000-0xf02fffff]<br />
	[   17.325632] pci 0000:00:00.0: BAR 6: assigned [mem 0xf0300000-0xf030ffff pref]<br />
	[   17.325672] pci 0000:01:00.0: BAR 0: assigned [mem 0xf0200000-0xf0203fff 64bit]<br />
	[   17.325735] pci 0000:00:00.0: PCI bridge to [bus 01-ff]<br />
	[   17.325762] pci 0000:00:00.0:   bridge window [mem 0xf0200000-0xf02fffff]<br />
	[   17.328988] pcieport 0000:00:00.0: PME: Signaling with IRQ 154<br />
	[   17.329785] nvme nvme0: pci function 0000:01:00.0<br />
	[   17.330019] nvme 0000:01:00.0: enabling device (0000 -&gt; 0002)<br />
	[   17.332003] <abbr title="Rockchip">rk</abbr>-pcie fe170000.pcie: PCIe Linking... LTSSM is 0x3<br />
	[   17.344648] usb 1-1: new high-speed USB device number 2 using xhci-hcd<br />
	[   17.353051] <abbr title="Rockchip">rk</abbr>-pcie fe170000.pcie: PCIe Linking... LTSSM is 0x3<br />
	[   17.359070] Initializing XFRM netlink socket<br />
	[   17.359119] NET: Registered PF_PACKET protocol family<br />
	[   17.359307] [BT_RFKILL]: Enter rfkill_rk_init<br />
	[   17.359314] [WLAN_RFKILL]: Enter rfkill_wlan_init<br />
	[   17.359725] [WLAN_RFKILL]: Enter rfkill_wlan_probe<br />
	[   17.359747] [WLAN_RFKILL]: can't find rockchip,grf property<br />
	[   17.359753] [WLAN_RFKILL]: wlan_platdata_parse_dt: wifi_chip_type = ap6275p<br />
	[   17.359759] [WLAN_RFKILL]: wlan_platdata_parse_dt: enable wifi power control.<br />
	[   17.359765] [WLAN_RFKILL]: wlan_platdata_parse_dt: wifi power controled by <abbr title="General purpose input/output">gpio</abbr>.<br />
	[   17.359810] [WLAN_RFKILL]: wlan_platdata_parse_dt: WIFI,host_wake_irq = 8, flags = 0.<br />
	[   17.359820] [WLAN_RFKILL]: wlan_platdata_parse_dt: The ref_wifi_clk not found !<br />
	[   17.359826] [WLAN_RFKILL]: rfkill_wlan_probe: init <abbr title="General purpose input/output">gpio</abbr><br />
	[   17.359832] [WLAN_RFKILL]: rfkill_set_wifi_bt_power: 1<br />
	[   17.359838] [WLAN_RFKILL]: Exit rfkill_wlan_probe<br />
	[   17.360248] [BT_RFKILL]: bluetooth_platdata_parse_dt: get property: uart_rts_gpios = 148.<br />
	[   17.360275] [BT_RFKILL]: bluetooth_platdata_parse_dt: get property: BT,reset_gpio = 21.<br />
	[   17.360295] [BT_RFKILL]: bluetooth_platdata_parse_dt: get property: BT,wake_gpio = 150.<br />
	[   17.360314] [BT_RFKILL]: bluetooth_platdata_parse_dt: get property: BT,wake_host_irq = 0.<br />
	[   17.360354] [BT_RFKILL]: Request irq for bt wakeup host<br />
	[   17.360463] [BT_RFKILL]: ** disable irq<br />
	[   17.360553] [BT_RFKILL]: bt shut off power<br />
	[   17.385416] [BT_RFKILL]: bt_default device registered.<br />
	[   17.385611] input: bt-powerkey as /devices/platform/wireless-bluetooth/input/input8<br />
	[   17.386104] Key type dns_resolver registered<br />
	[   17.386157] Key type ceph registered<br />
	[   17.386863] libceph: loaded (mon/osd proto 15/24)<br />
	[   17.389637] registered taskstats version 1<br />
	[   17.389705] Loading compiled-in X.509 certificates<br />
	[   17.394797] zswap: loaded using pool zstd/zbud<br />
	[   17.395342] Key type .fscrypt registered<br />
	[   17.395370] Key type fscrypt-provisioning registered<br />
	[   17.396740] Btrfs loaded, crc32c=crc32c-generic, zoned=no, fsverity=no<br />
	[   17.397270] pstore: Using crash dump compression: deflate<br />
	[   17.397684] Key type encrypted registered<br />
	[   17.398082] AppArmor: AppArmor sha1 policy hashing enabled<br />
	[   17.409984] rga3 fdb60000.rga: Adding to iommu group 2<br />
	[   17.410299] rga3 fdb60000.rga: probe successfully, irq = 50, hw_version:3.0.76831<br />
	[   17.410378] rga3 fdb70000.rga: Adding to iommu group 3<br />
	[   17.410591] rga3 fdb70000.rga: probe successfully, irq = 51, hw_version:3.0.76831<br />
	[   17.411096] rga2 fdb80000.rga: probe successfully, irq = 157, hw_version:3.2.63318<br />
	[   17.411197] rga: IOMMU binding successfully, default mapping core[0x1]<br />
	[   17.411307] rga: Module initialized. v1.3.7<br />
	[   17.428976] mpp_vdpu1 fdb51000.avsd-plus: Adding to iommu group 1<br />
	[   17.429491] mpp_vdpu1 fdb51000.avsd-plus: probe device<br />
	[   17.429863] mpp_vdpu1 fdb51000.avsd-plus: reset_group-&gt;rw_sem_on=0<br />
	[   17.429904] mpp_vdpu1 fdb51000.avsd-plus: reset_group-&gt;rw_sem_on=0<br />
	[   17.430015] mpp_vdpu1 fdb51000.avsd-plus: probing finish<br />
	[   17.430384] mpp_vdpu2 fdb50400.vdpu: Adding to iommu group 1<br />
	[   17.430491] mpp_vdpu2 fdb50400.vdpu: probe device<br />
	[   17.430735] mpp_vdpu2 fdb50400.vdpu: reset_group-&gt;rw_sem_on=0<br />
	[   17.430765] mpp_vdpu2 fdb50400.vdpu: reset_group-&gt;rw_sem_on=0<br />
	[   17.430805] mpp_vdpu2 fdb50400.vdpu: probing finish<br />
	[   17.431113] mpp_vepu2 fdb50000.vepu: Adding to iommu group 1<br />
	[   17.431216] mpp_vepu2 fdb50000.vepu: probing start<br />
	[   17.431487] mpp_vepu2 fdb50000.vepu: reset_group-&gt;rw_sem_on=0<br />
	[   17.431517] mpp_vepu2 fdb50000.vepu: reset_group-&gt;rw_sem_on=0<br />
	[   17.431585] mpp_vepu2 fdb50000.vepu: probing finish<br />
	[   17.431923] mpp_vepu2 fdba0000.jpege-core: Adding to iommu group 5<br />
	[   17.432140] mpp_vepu2 fdba0000.jpege-core: probing start<br />
	[   17.432468] mpp_vepu2 fdba0000.jpege-core: attach ccu success<br />
	[   17.432541] mpp_vepu2 fdba0000.jpege-core: probing finish<br />
	[   17.432853] mpp_vepu2 fdba4000.jpege-core: Adding to iommu group 6<br />
	[   17.433029] mpp_vepu2 fdba4000.jpege-core: probing start<br />
	[   17.433332] mpp_vepu2 fdba4000.jpege-core: attach ccu success<br />
	[   17.433403] mpp_vepu2 fdba4000.jpege-core: probing finish<br />
	[   17.433738] mpp_vepu2 fdba8000.jpege-core: Adding to iommu group 7<br />
	[   17.433922] mpp_vepu2 fdba8000.jpege-core: probing start<br />
	[   17.434221] mpp_vepu2 fdba8000.jpege-core: attach ccu success<br />
	[   17.434292] mpp_vepu2 fdba8000.jpege-core: probing finish<br />
	[   17.434629] mpp_vepu2 fdbac000.jpege-core: Adding to iommu group 8<br />
	[   17.434806] mpp_vepu2 fdbac000.jpege-core: probing start<br />
	[   17.435111] mpp_vepu2 fdbac000.jpege-core: attach ccu success<br />
	[   17.435182] mpp_vepu2 fdbac000.jpege-core: probing finish<br />
	[   17.435611] mpp-iep2 fdbb0000.iep: Adding to iommu group 9<br />
	[   17.435804] mpp-iep2 fdbb0000.iep: probe device<br />
	[   17.436396] mpp-iep2 fdbb0000.iep: probing finish<br />
	[   17.436518] mpp_jpgdec fdb90000.jpegd: Adding to iommu group 4<br />
	[   17.436635] mpp_jpgdec fdb90000.jpegd: probe device<br />
	[   17.436723] mpp_jpgdec fdb90000.jpegd: probing finish<br />
	[   17.436812] mpp_rkvdec2 fdc38100.rkvdec-core: Adding to iommu group 12<br />
	[   17.436973] mpp_rkvdec2 fdc38100.rkvdec-core: rkvdec-core, probing start<br />
	[   17.437048] mpp_rkvdec2 fdc38100.rkvdec-core: shared_niu_a is not found!<br />
	[   17.437054] rkvdec2_init:1198: No niu aclk reset resource define<br />
	[   17.437059] mpp_rkvdec2 fdc38100.rkvdec-core: shared_niu_h is not found!<br />
	[   17.437063] rkvdec2_init:1201: No niu hclk reset resource define<br />
	[   17.437098] mpp_rkvdec2 fdc38100.rkvdec-core: no regulator, devfreq is disabled<br />
	[   17.437135] mpp_rkvdec2 fdc38100.rkvdec-core: core_mask=00010001<br />
	[   17.437141] mpp_rkvdec2 fdc38100.rkvdec-core: attach ccu as core 0<br />
	[   17.437256] mpp_rkvdec2 fdc38100.rkvdec-core: sram_start 0x00000000ff001000<br />
	[   17.437262] mpp_rkvdec2 fdc38100.rkvdec-core: rcb_iova 0x00000000fff00000<br />
	[   17.437267] mpp_rkvdec2 fdc38100.rkvdec-core: sram_size 491520<br />
	[   17.437271] mpp_rkvdec2 fdc38100.rkvdec-core: rcb_size 1048576<br />
	[   17.437277] mpp_rkvdec2 fdc38100.rkvdec-core: min_width 512<br />
	[   17.437282] mpp_rkvdec2 fdc38100.rkvdec-core: rcb_info_count 20<br />
	[   17.437286] mpp_rkvdec2 fdc38100.rkvdec-core: [136, 24576]<br />
	[   17.437291] mpp_rkvdec2 fdc38100.rkvdec-core: [137, 49152]<br />
	[   17.437295] mpp_rkvdec2 fdc38100.rkvdec-core: [141, 90112]<br />
	[   17.437300] mpp_rkvdec2 fdc38100.rkvdec-core: [140, 49152]<br />
	[   17.437304] mpp_rkvdec2 fdc38100.rkvdec-core: [139, 180224]<br />
	[   17.437309] mpp_rkvdec2 fdc38100.rkvdec-core: [133, 49152]<br />
	[   17.437313] mpp_rkvdec2 fdc38100.rkvdec-core: [134, 8192]<br />
	[   17.437318] mpp_rkvdec2 fdc38100.rkvdec-core: [135, 4352]<br />
	[   17.437322] mpp_rkvdec2 fdc38100.rkvdec-core: [138, 13056]<br />
	[   17.437326] mpp_rkvdec2 fdc38100.rkvdec-core: [142, 291584]<br />
	[   17.437345] mpp_rkvdec2 fdc38100.rkvdec-core: probing finish<br />
	[   17.437433] mpp_rkvdec2 fdc48100.rkvdec-core: Adding to iommu group 13<br />
	[   17.437563] mpp_rkvdec2 fdc48100.rkvdec-core: rkvdec-core, probing start<br />
	[   17.437635] mpp_rkvdec2 fdc48100.rkvdec-core: shared_niu_a is not found!<br />
	[   17.437641] rkvdec2_init:1198: No niu aclk reset resource define<br />
	[   17.437645] mpp_rkvdec2 fdc48100.rkvdec-core: shared_niu_h is not found!<br />
	[   17.437650] rkvdec2_init:1201: No niu hclk reset resource define<br />
	[   17.437671] mpp_rkvdec2 fdc48100.rkvdec-core: no regulator, devfreq is disabled<br />
	[   17.437699] mpp_rkvdec2 fdc48100.rkvdec-core: core_mask=00020002<br />
	[   17.437715] mpp_rkvdec2 fdc48100.rkvdec-core: attach ccu as core 1<br />
	[   17.437823] mpp_rkvdec2 fdc48100.rkvdec-core: sram_start 0x00000000ff079000<br />
	[   17.437828] mpp_rkvdec2 fdc48100.rkvdec-core: rcb_iova 0x00000000ffe00000<br />
	[   17.437833] mpp_rkvdec2 fdc48100.rkvdec-core: sram_size 487424<br />
	[   17.437838] mpp_rkvdec2 fdc48100.rkvdec-core: rcb_size 1048576<br />
	[   17.437843] mpp_rkvdec2 fdc48100.rkvdec-core: min_width 512<br />
	[   17.437848] mpp_rkvdec2 fdc48100.rkvdec-core: rcb_info_count 20<br />
	[   17.437852] mpp_rkvdec2 fdc48100.rkvdec-core: [136, 24576]<br />
	[   17.437857] mpp_rkvdec2 fdc48100.rkvdec-core: [137, 49152]<br />
	[   17.437861] mpp_rkvdec2 fdc48100.rkvdec-core: [141, 90112]<br />
	[   17.437866] mpp_rkvdec2 fdc48100.rkvdec-core: [140, 49152]<br />
	[   17.437870] mpp_rkvdec2 fdc48100.rkvdec-core: [139, 180224]<br />
	[   17.437875] mpp_rkvdec2 fdc48100.rkvdec-core: [133, 49152]<br />
	[   17.437879] mpp_rkvdec2 fdc48100.rkvdec-core: [134, 8192]<br />
	[   17.437884] mpp_rkvdec2 fdc48100.rkvdec-core: [135, 4352]<br />
	[   17.437888] mpp_rkvdec2 fdc48100.rkvdec-core: [138, 13056]<br />
	[   17.437893] mpp_rkvdec2 fdc48100.rkvdec-core: [142, 291584]<br />
	[   17.437913] mpp_rkvdec2 fdc48100.rkvdec-core: probing finish<br />
	[   17.437998] mpp_rkvenc2 fdbd0000.rkvenc-core: Adding to iommu group 10<br />
	[   17.438091] mpp_rkvenc2 fdbd0000.rkvenc-core: probing start<br />
	[   17.438188] mpp_rkvenc2 fdbd0000.rkvenc-core: rockchip_init_read_margin: no regulator (venc) found: -19<br />
	[   17.438195] mpp_rkvenc2 fdbd0000.rkvenc-core: bin=0<br />
	[   17.438380] mpp_rkvenc2 fdbd0000.rkvenc-core: leakage=11<br />
	[   17.438386] mpp_rkvenc2 fdbd0000.rkvenc-core: leakage-volt-sel=0<br />
	[   17.438418] mpp_rkvenc2 fdbd0000.rkvenc-core: error -ENODEV: _opp_set_regulators: no regulator (venc) found<br />
	[   17.438436] mpp_rkvenc2 fdbd0000.rkvenc-core: failed to set opp config<br />
	[   17.438441] mpp_rkvenc2 fdbd0000.rkvenc-core: failed to init opp info<br />
	[   17.438445] mpp_rkvenc2 fdbd0000.rkvenc-core: failed to init_opp_table<br />
	[   17.438449] rkvenc_init:2147: failed to add venc devfreq<br />
	[   17.438469] mpp_rkvenc2 fdbd0000.rkvenc-core: attach ccu as core 0<br />
	[   17.438487] mpp_rkvenc2 fdbd0000.rkvenc-core: probing finish<br />
	[   17.438567] mpp_rkvenc2 fdbe0000.rkvenc-core: Adding to iommu group 11<br />
	[   17.438667] mpp_rkvenc2 fdbe0000.rkvenc-core: probing start<br />
	[   17.438753] mpp_rkvenc2 fdbe0000.rkvenc-core: rockchip_init_read_margin: no regulator (venc) found: -19<br />
	[   17.438759] mpp_rkvenc2 fdbe0000.rkvenc-core: bin=0<br />
	[   17.438929] mpp_rkvenc2 fdbe0000.rkvenc-core: leakage=11<br />
	[   17.438934] mpp_rkvenc2 fdbe0000.rkvenc-core: leakage-volt-sel=0<br />
	[   17.438958] mpp_rkvenc2 fdbe0000.rkvenc-core: error -ENODEV: _opp_set_regulators: no regulator (venc) found<br />
	[   17.438970] mpp_rkvenc2 fdbe0000.rkvenc-core: failed to set opp config<br />
	[   17.438975] mpp_rkvenc2 fdbe0000.rkvenc-core: failed to init opp info<br />
	[   17.438979] mpp_rkvenc2 fdbe0000.rkvenc-core: failed to init_opp_table<br />
	[   17.438983] rkvenc_init:2147: failed to add venc devfreq<br />
	[   17.439020] mpp_rkvenc2 fdbe0000.rkvenc-core: attach ccu as core 1<br />
	[   17.439036] mpp_rkvenc2 fdbe0000.rkvenc-core: probing finish<br />
	[   17.439120] mpp_av1dec fdc70000.av1d: Adding to iommu group 14<br />
	[   17.439256] mpp_av1dec fdc70000.av1d: probing start<br />
	[   17.439352] mpp_av1dec fdc70000.av1d: probing finish<br />
	[   17.439820] rockchip-dmc dmc: bin=0<br />
	[   17.439992] rockchip-dmc dmc: leakage=35<br />
	[   17.439999] rockchip-dmc dmc: leakage-volt-sel=1<br />
	[   17.440006] rockchip-dmc dmc: <abbr title="System On a Chip">soc</abbr> version=0, speed=1<br />
	[   17.440182] mali fb000000.<abbr title="Graphic processing unit (3D acceleration)">gpu</abbr>: Kernel DDK version g25p0-00eac0<br />
	[   17.440238] mali fb000000.<abbr title="Graphic processing unit (3D acceleration)">gpu</abbr>: <abbr title="Graphic processing unit (3D acceleration)">GPU</abbr> metrics tracepoint support enabled<br />
	[   17.444985] mali fb000000.<abbr title="Graphic processing unit (3D acceleration)">gpu</abbr>: bin=0<br />
	[   17.445158] mali fb000000.<abbr title="Graphic processing unit (3D acceleration)">gpu</abbr>: leakage=14<br />
	[   17.445178] debugfs: Directory 'fb000000.<abbr title="Graphic processing unit (3D acceleration)">gpu</abbr>-mali' with parent 'vdd_gpu_s0' already present!<br />
	[   17.445636] rockchip-dmc dmc: avs=0<br />
	[   17.445651] rockchip-dmc dmc: current ATF version 0x100<br />
	[   17.445812] rockchip-dmc dmc: normal_rate = 1560000000<br />
	[   17.445819] rockchip-dmc dmc: reboot_rate = 2112000000<br />
	[   17.445825] rockchip-dmc dmc: suspend_rate = 528000000<br />
	[   17.445830] rockchip-dmc dmc: video_4k_rate = 1560000000<br />
	[   17.445836] rockchip-dmc dmc: video_4k_10b_rate = 1560000000<br />
	[   17.445841] rockchip-dmc dmc: video_svep_rate = 1560000000<br />
	[   17.445847] rockchip-dmc dmc: boost_rate = 2112000000<br />
	[   17.445852] rockchip-dmc dmc: fixed_rate(isp|cif0|cif1|dualview) = 2112000000<br />
	[   17.445858] rockchip-dmc dmc: performance_rate = 2112000000<br />
	[   17.445864] rockchip-dmc dmc: hdmirx_rate = 2112000000<br />
	[   17.445870] rockchip-dmc dmc: deep_suspend_rate = 2112000000<br />
	[   17.445877] rockchip-dmc dmc: failed to get vop bandwidth to dmc rate<br />
	[   17.445883] rockchip-dmc dmc: failed to get vop pn to msch rl<br />
	[   17.446111] rockchip-dmc dmc: l=15000 h=2147483647 hyst=5000 l_limit=0 h_limit=0 h_table=0<br />
	[   17.446164] dwmmc_rockchip fe2c0000.mmc: Successfully tuned phase to 235<br />
	[   17.446197] mmc1: new ultra high speed SDR104 SDHC card at address aaaa<br />
	[   17.446645] mmcblk1: mmc1:aaaa SC16G 14.8 GiB <br />
	[   17.450278] mali fb000000.<abbr title="Graphic processing unit (3D acceleration)">gpu</abbr>: pvtm=816<br />
	[   17.452503] GPT:Primary header thinks Alt. header is not at the end of the disk.<br />
	[   17.452589] GPT:3235839 != 31116287<br />
	[   17.452602] GPT:Alternate GPT header not at the end of the disk.<br />
	[   17.452616] GPT:3235839 != 31116287<br />
	[   17.452627] GPT: Use GNU Parted to correct GPT errors.<br />
	[   17.452653]  mmcblk1: p1<br />
	[   17.456624] mali fb000000.<abbr title="Graphic processing unit (3D acceleration)">gpu</abbr>: pvtm-volt-sel=1<br />
	[   17.456736] debugfs: Directory 'fb000000.<abbr title="Graphic processing unit (3D acceleration)">gpu</abbr>-mali' with parent 'vdd_gpu_s0' already present!<br />
	[   17.458413] mali fb000000.<abbr title="Graphic processing unit (3D acceleration)">gpu</abbr>: avs=0<br />
	[   17.458521] mali fb000000.<abbr title="Graphic processing unit (3D acceleration)">gpu</abbr>: rockchip_pvtpll_set_volt_sel: error cfg clk_id=5 voltsel (-1)<br />
	[   17.458566] W : [File] : drivers/<abbr title="Graphic processing unit (3D acceleration)">gpu</abbr>/arm/bifrost/platform/<abbr title="Rockchip">rk</abbr>/mali_kbase_config_rk.c; [Line] : 144; [Func] : kbase_platform_rk_init(); power-off-delay-ms not available.<br />
	[   17.459429] WCN: marlin_init entry!<br />
	[   17.459488] mali fb000000.<abbr title="Graphic processing unit (3D acceleration)">gpu</abbr>: Register LUT 000a0800 initialized for <abbr title="Graphic processing unit (3D acceleration)">GPU</abbr> arch 0x000a0806<br />
	[   17.459541] mali fb000000.<abbr title="Graphic processing unit (3D acceleration)">gpu</abbr>: r0p0 status 5 not found in HW issues table;<br />
	[   17.459562] mali fb000000.<abbr title="Graphic processing unit (3D acceleration)">gpu</abbr>: falling back to closest match: r0p0 status 0<br />
	[   17.459580] mali fb000000.<abbr title="Graphic processing unit (3D acceleration)">gpu</abbr>: Execution proceeding normally with fallback match<br />
	[   17.459599] mali fb000000.<abbr title="Graphic processing unit (3D acceleration)">gpu</abbr>: <abbr title="Graphic processing unit (3D acceleration)">GPU</abbr> identified as 0x7 arch 10.8.6 r0p0 status 0<br />
	[   17.459714] mali fb000000.<abbr title="Graphic processing unit (3D acceleration)">gpu</abbr>: CSF_GPU_RESET_TIMEOUT is capped from 20666ms to 4500ms<br />
	[   17.459739] mali fb000000.<abbr title="Graphic processing unit (3D acceleration)">gpu</abbr>: KBASE_PRFCNT_ACTIVE_TIMEOUT is capped from 40000ms to 4500ms<br />
	[   17.459760] mali fb000000.<abbr title="Graphic processing unit (3D acceleration)">gpu</abbr>: KBASE_AS_INACTIVE_TIMEOUT is capped from 40000ms to 4500ms<br />
	[   17.459780] mali fb000000.<abbr title="Graphic processing unit (3D acceleration)">gpu</abbr>: CSF_FIRMWARE_STOP_TIMEOUT is capped from 40000ms to 4500ms<br />
	[   17.459854] mali fb000000.<abbr title="Graphic processing unit (3D acceleration)">gpu</abbr>: No priority control manager is configured<br />
	[   17.459873] mali fb000000.<abbr title="Graphic processing unit (3D acceleration)">gpu</abbr>: Large page allocation set to false after hardware feature check<br />
	[   17.460184] mali fb000000.<abbr title="Graphic processing unit (3D acceleration)">gpu</abbr>: No memory group manager is configured<br />
	[   17.460228] mali fb000000.<abbr title="Graphic processing unit (3D acceleration)">gpu</abbr>: Protected memory allocator not available<br />
	[   17.460761] RKNPU fdab0000.npu: Adding to iommu group 0<br />
	[   17.460982] RKNPU fdab0000.npu: RKNPU: rknpu iommu is enabled, using iommu mode<br />
	[   17.462436] mali fb000000.<abbr title="Graphic processing unit (3D acceleration)">gpu</abbr>: EM: created perf domain<br />
	[   17.462637] RKNPU fdab0000.npu: can't request region for resource [mem 0xfdab0000-0xfdabffff]<br />
	[   17.462672] RKNPU fdab0000.npu: can't request region for resource [mem 0xfdac0000-0xfdacffff]<br />
	[   17.462696] RKNPU fdab0000.npu: can't request region for resource [mem 0xfdad0000-0xfdadffff]<br />
	[   17.462789] mali fb000000.<abbr title="Graphic processing unit (3D acceleration)">gpu</abbr>: l=15000 h=85000 hyst=5000 l_limit=0 h_limit=800000000 h_table=0<br />
	[   17.463410] [drm] Initialized rknpu 0.9.8 20240828 for fdab0000.npu on minor 1<br />
	[   17.464159] mali fb000000.<abbr title="Graphic processing unit (3D acceleration)">gpu</abbr>: * MALI kbase_mmap_min_addr compiled to CONFIG_DEFAULT_MMAP_MIN_ADDR, no runtime update possible! *<br />
	[   17.464179] mali fb000000.<abbr title="Graphic processing unit (3D acceleration)">gpu</abbr>: Probed as mali0<br />
	[   17.464915] hwmon hwmon8: temp1_input not attached to any thermal zone<br />
	[   17.465049] hwmon hwmon8: temp2_input not attached to any thermal zone<br />
	[   17.466216] RKNPU fdab0000.npu: RKNPU: bin=0<br />
	[   17.466426] RKNPU fdab0000.npu: leakage=8<br />
	[   17.466468] debugfs: Directory 'fdab0000.npu-rknpu' with parent 'vdd_npu_s0' already present!<br />
	[   17.474051] RKNPU fdab0000.npu: pvtm=814<br />
	[   17.475374] nvme nvme0: allocated 64 MiB host memory buffer.<br />
	[   17.479475] RKNPU fdab0000.npu: pvtm-volt-sel=0<br />
	[   17.479591] debugfs: Directory 'fdab0000.npu-rknpu' with parent 'vdd_npu_s0' already present!<br />
	[   17.482014] RKNPU fdab0000.npu: avs=0<br />
	[   17.482107] RKNPU fdab0000.npu: rockchip_pvtpll_set_volt_sel: error cfg clk_id=6 voltsel (-1)<br />
	[   17.482283] RKNPU fdab0000.npu: l=15000 h=85000 hyst=5000 l_limit=0 h_limit=800000000 h_table=0<br />
	[   17.489359] usb 1-1: New USB device found, idVendor=05e3, idProduct=0610, bcdDevice=93.91<br />
	[   17.489411] usb 1-1: New USB device strings: Mfr=1, Product=2, SerialNumber=0<br />
	[   17.489441] usb 1-1: Product: USB2.1 Hub<br />
	[   17.489465] usb 1-1: Manufacturer: GenesysLogic<br />
	[   17.496617] cfg80211: Loading compiled-in X.509 certificates for regulatory database<br />
	[   17.518220] cfg80211: Loaded X.509 cert 'sforshee: 00b28ddf47aef9cea7'<br />
	[   17.519182] cfg80211: Loaded X.509 cert 'wens: 61c038651aabdcf94bd0ac7ff06c7248db18c600'<br />
	[   17.520164] clk: Disabling unused clocks<br />
	[   17.521790] rockchip-pm rockchip-suspend: not set pwm-regulator-config<br />
	[   17.522587] rockchip-suspend not set sleep-mode-config for mem-lite<br />
	[   17.522615] rockchip-suspend not set wakeup-config for mem-lite<br />
	[   17.522644] rockchip-suspend not set sleep-mode-config for mem-ultra<br />
	[   17.522668] rockchip-suspend not set wakeup-config for mem-ultra<br />
	[   17.525353] ALSA device list:<br />
	[   17.525379]   #0: rockchip-dp0<br />
	[   17.525400]   #1: rockchip-hdmi0<br />
	[   17.525419]   #2: rockchip-hdmi1<br />
	[   17.525438]   #3: rockchip-es8388<br />
	[   17.534502] hub 1-1:1.0: USB hub found<br />
	[   17.534766] hub 1-1:1.0: 4 ports detected<br />
	[   17.596619] nvme nvme0: 8/0/0 default/read/poll queues<br />
	[   17.609378] usb 2-1: new SuperSpeed USB device number 2 using xhci-hcd<br />
	[   17.631903] usb 2-1: New USB device found, idVendor=05e3, idProduct=0620, bcdDevice=93.91<br />
	[   17.631965] usb 2-1: New USB device strings: Mfr=1, Product=2, SerialNumber=0<br />
	[   17.632029] usb 2-1: Product: USB3.2 Hub<br />
	[   17.632054] usb 2-1: Manufacturer: GenesysLogic<br />
	[   17.660964] Freeing unused kernel memory: 8320K<br />
	[   17.661384] Run /init as init process<br />
	[   17.663401] hub 2-1:1.0: USB hub found<br />
	[   17.664091] hub 2-1:1.0: 4 ports detected<br />
	[   17.993319] input: adc-keys as /devices/platform/adc-keys/input/input9<br />
	[   18.004482] rockchip-cpuinfo cpuinfo: <abbr title="System On a Chip">SoC</abbr>        : 35881000<br />
	[   18.004516] rockchip-cpuinfo cpuinfo: Serial        : 9f77ef415554aece<br />
	DDR V1.13 25cee80c4f cym 23/08/11-09:31:58<br />
	LPDDR4X, 2112MHz<br />
	channel[0] BW=16 Col=10 Bk=8 CS0 Row=18 CS1 Row=18 CS=2 Die BW=8 Size=8192MB<br />
	channel[1] BW=16 Col=10 Bk=8 CS0 Row=18 CS1 Row=18 CS=2 Die BW=8 Size=8192MB<br />
	channel[2] BW=16 Col=10 Bk=8 CS0 Row=18 CS1 Row=18 CS=2 Die BW=8 Size=8192MB<br />
	channel[3] BW=16 Col=10 Bk=8 CS0 Row=18 CS1 Row=18 CS=2 Die BW=8 Size=8192MB<br />
	Manufacturer ID:0xff<br />
	CH0 RX Vref:28.9%, TX Vref:22.8%,21.8%<br />
	CH1 RX Vref:26.7%, TX Vref:21.8%,20.8%<br />
	CH2 RX Vref:28.9%, TX Vref:20.8%,20.8%<br />
	CH3 RX Vref:28.5%, TX Vref:20.8%,20.8%<br />
	change to F1: 528MHz<br />
	change to F2: 1068MHz<br />
	change to F3: 1560MHz<br />
	change to F0: 2112MHz<br />
	out<br />
	U-Boot SPL board init<br />
	U-Boot SPL 2017.09-orangepi (Nov 15 2023 - 16:53:25)<br />
	Trying to boot from MMC1<br />
	Trying fit image at 0x4000 sector<br />
	## Verified-boot: 0<br />
	## Checking atf-1 0x00040000 ... sha256(7612223b82...) + OK<br />
	## Checking uboot 0x00200000 ... sha256(d41c62e80b...) + OK<br />
	## Checking fdt 0x00355940 ... sha256(7146109403...) + OK<br />
	## Checking atf-2 0xff100000 ... sha256(70505bb764...) + OK<br />
	## Checking atf-3 0x000f0000 ... sha256(b2af21b504...) + OK<br />
	Jumping to U-Boot(0x00200000) via ARM Trusted Firmware(0x00040000)<br />
	Total: 741.283 ms
</p>

<p>
	INFO:    Preloader serial: 2<br />
	NOTICE:  BL31: v2.3():v2.3-868-g040d2de11:derrick.huang, fwver: v1.48<br />
	NOTICE:  BL31: Built : 15:02:44, Dec 19 2024<br />
	INFO:    spec: 0x1<br />
	INFO:    code: 0x88<br />
	INFO:    ext 32k is valid<br />
	INFO:    ddr: stride-en 4CH<br />
	INFO:    GICv3 without legacy support detected.<br />
	INFO:    ARM GICv3 driver initialized in EL3<br />
	INFO:    valid_cpu_msk=0xff bcore0_rst = 0x0, bcore1_rst = 0x0<br />
	INFO:    l3 cache partition cfg-0<br />
	INFO:    system boots from cpu-hwid-0<br />
	INFO:    disable memory repair<br />
	INFO:    idle_st=0x21fff, pd_st=0x11fff9, repair_st=0xfff70001<br />
	INFO:    dfs DDR fsp_params[0].freq_mhz= 2112MHz<br />
	INFO:    dfs DDR fsp_params[1].freq_mhz= 528MHz<br />
	INFO:    dfs DDR fsp_params[2].freq_mhz= 1068MHz<br />
	INFO:    dfs DDR fsp_params[3].freq_mhz= 1560MHz<br />
	INFO:    BL31: Initialising Exception Handling Framework<br />
	INFO:    BL31: Initializing runtime services<br />
	WARNING: No OPTEE provided by BL2 boot loader, Booting device without OPTEE initialization. SMC`s destined for OPTEE will return SMC_UNK<br />
	ERROR:   Error initializing runtime service opteed_fast<br />
	INFO:    BL31: Preparing for EL3 exit to normal world<br />
	INFO:    Entry point address = 0x200000<br />
	INFO:    SPSR = 0x3c9<br />
	usb dr_mode not found<br />
	usb dr_mode not found
</p>

<p>
	<br />
	U-Boot 2017.09_armbian-2017.09-S3f41-Pdfdd-H6539-Ve691-Bbf55-R448a (Nov 19 2025 - 17:07:00 +0000)
</p>

<p>
	Model: Orange Pi 5 Plus<br />
	MPIDR: 0x0<br />
	PreSerial: 2, raw, 0xfeb50000<br />
	DRAM:  31.7 GiB<br />
	Sysmem: init<br />
	Relocation Offset: eda09000<br />
	Relocation fdt: eb9f7610 - eb9fecd0<br />
	CR: M/C/I<br />
	usb dr_mode not found<br />
	usb dr_mode not found<br />
	Using default environment
</p>

<p>
	DM: v2<br />
	RESC: No bootdev<br />
	Failed to load <abbr title="Device tree blob">DTB</abbr>, ret=-2<br />
	No valid <abbr title="Device tree blob">DTB</abbr>, ret=-22<br />
	Failed to get kernel <abbr title="Device tree blob">dtb</abbr>, ret=-22<br />
	Model: Orange Pi 5 Plus<br />
	[Vendor ERROR]:Invalid boot device type(0)<br />
	## Error: Can't overwrite "ethaddr"<br />
	## Error inserting "ethaddr" variable, errno=1<br />
	## Error: Can't overwrite "eth1addr"<br />
	## Error inserting "eth1addr" variable, errno=1<br />
	[Vendor ERROR]:Invalid boot device type(0)<br />
	rockchip_set_ethaddr: vendor_storage_write failed -19<br />
	[Vendor ERROR]:Invalid boot device type(0)<br />
	mmc@fe2c0000: 1, mmc@fe2e0000: 0<br />
	Card did not respond to voltage select!<br />
	mmc_init: -95, time 13<br />
	switch to partitions #0, OK<br />
	mmc1 is current device<br />
	Boot from SDcard<br />
	Bootdev(scan): mmc 1<br />
	No bootdev<br />
	dev_desc is NULL!<br />
	boot mode: None<br />
	No bootdev<br />
	CLK: (sync kernel. arm: enter 1008000 KHz, init 1008000 KHz, kernel 0N/A)<br />
	  b0pll 24000 KHz<br />
	  b1pll 24000 KHz<br />
	  lpll 24000 KHz<br />
	  v0pll 24000 KHz<br />
	  aupll 24000 KHz<br />
	  cpll 1500000 KHz<br />
	  gpll 1188000 KHz<br />
	  npll 24000 KHz<br />
	  ppll 1100000 KHz<br />
	  aclk_center_root 702000 KHz<br />
	  pclk_center_root 100000 KHz<br />
	  hclk_center_root 396000 KHz<br />
	  aclk_center_low_root 500000 KHz<br />
	  aclk_top_root 750000 KHz<br />
	  pclk_top_root 100000 KHz<br />
	  aclk_low_top_root 396000 KHz<br />
	MMC1: Legacy, 52Mhz<br />
	PartType: EFI<br />
	No bootdev<br />
	dev_desc is NULL!<br />
	No bootdev<br />
	Net:   No ethernet found.<br />
	Hit key to stop autoboot('CTRL+C'):  0 <br />
	starting USB...<br />
	Bus usb@fc000000: usb maximum-speed not found<br />
	Register 2000140 NbrPorts 2<br />
	Starting the controller<br />
	USB XHCI 1.10<br />
	Bus usb@fc800000: USB EHCI 1.00<br />
	Bus usb@fc840000: USB OHCI 1.0<br />
	Bus usb@fc880000: USB EHCI 1.00<br />
	Bus usb@fc8c0000: USB OHCI 1.0<br />
	Bus usb@fc400000: usb maximum-speed not found<br />
	Register 2000140 NbrPorts 2<br />
	Starting the controller<br />
	USB XHCI 1.10<br />
	scanning bus usb@fc000000 for devices... 1 USB Device(s) found<br />
	scanning bus usb@fc800000 for devices... 1 USB Device(s) found<br />
	scanning bus usb@fc840000 for devices... 1 USB Device(s) found<br />
	scanning bus usb@fc880000 for devices... 1 USB Device(s) found<br />
	scanning bus usb@fc8c0000 for devices... 1 USB Device(s) found<br />
	scanning bus usb@fc400000 for devices... cannot reset port 1!?<br />
	1 USB Device(s) found<br />
	       scanning usb for storage devices... 0 Storage Device(s) found
</p>

<p>
	............. and so on
</p>
]]></description><guid isPermaLink="false">58320</guid><pubDate>Sun, 08 Mar 2026 08:21:13 +0000</pubDate></item><item><title>OrangePi 5 Pro need help booting into nvme</title><link>https://forum.armbian.com/topic/45535-orangepi-5-pro-need-help-booting-into-nvme/</link><description><![CDATA[<p>
	Hi,
</p>

<p>
	 
</p>

<p>
	Just received this unit yesterday with my surprise and lack of reading, the unit does not include <abbr title="embedded MultiMediaCard"><abbr title="embedded MultiMediaCard">eMMC</abbr></abbr> or SPI so I am unable to boot directly into nvme drive.
</p>

<p>
	 
</p>

<p>
	Are there instructions somewhere on how to setup the device to boot from MicroSD but use nvme as main drive?
</p>

<p>
	 
</p>

<p>
	Thank you.
</p>
]]></description><guid isPermaLink="false">45535</guid><pubDate>Thu, 26 Sep 2024 15:49:47 +0000</pubDate></item><item><title>Orange Pi 5 Pro &#x2013; Device Tree overlays not loading from armbianEnv.txt</title><link>https://forum.armbian.com/topic/58318-orange-pi-5-pro-%E2%80%93-device-tree-overlays-not-loading-from-armbianenvtxt/</link><description><![CDATA[<p>
	<strong>BOARD</strong> - Orange Pi 5 Pro
</p>

<p>
	 
</p>

<p>
	<strong>PROBLEM</strong>
</p>

<p>
	 
</p>

<p>
	Device Tree overlays defined in armbianEnv.txt are not being applied during boot.
</p>

<p>
	The overlay file exists but is not loaded by the system.
</p>

<p>
	 
</p>

<pre class="ipsCode">verbosity=1
bootlogo=false
console=both
extraargs=cma=256M
fdtfile=rockchip/rk3588s-orangepi-5-pro.dtb
rootdev=UUID=a8beb1c4-8079-4e64-8216-8e893f7809d4
rootfstype=ext4
overlays=orangepi-5-pro-disable-leds
usbstoragequirks=0x2537:0x1066:u,0x2537:0x1068:u</pre>

<p>
	 
</p>

<p>
	I also tried with 
</p>

<p>
	 
</p>

<pre class="ipsCode prettyprint lang-html prettyprinted"><span class="pln">overlay_prefix=rockchip
overlays=orangepi-5-pro-disable-leds</span></pre>

<p>
	 
</p>

<p>
	The Kernel is<br />
	 
</p>

<pre class="ipsCode prettyprint lang-html prettyprinted"><span class="pln">Linux orangepi5pro 6.1.115-vendor-rk35xx #1 SMP Mon Feb 23 05:39:00 UTC 2026 aarch64 GNU/Linux</span></pre>

<p>
	 
</p>

<p>
	<strong>Additional Information</strong>
</p>

<p>
	 
</p>

<p>
	I tested the same overlay using the official build system from:
</p>

<p>
	<a href="https://github.com/orangepi-xunlong/orangepi-build" rel="external nofollow">https://github.com/orangepi-xunlong/orangepi-build</a>
</p>

<p>
	and it works correctly there.
</p>

<p>
	 
</p>

<p>
	This suggests the issue may be related to how Armbian loads overlays for RK3588 boards.
</p>

<p>
	 
</p>

<p>
	<strong>Question</strong>
</p>

<p>
	 
</p>

<p>
	Is overlay loading from armbianEnv.txt supported on the Orange Pi 5 Pro with the vendor-rk35xx kernel, or is there another mechanism required (extlinux overlays, user overlays, etc.)?
</p>

<p>
	 
</p>

<p>
	<a href="https://paste.armbian.com/xiteginoku" rel="external nofollow">https://paste.armbian.com/xiteginoku</a>
</p>
]]></description><guid isPermaLink="false">58318</guid><pubDate>Sun, 08 Mar 2026 05:16:15 +0000</pubDate></item><item><title>Rock5a and eMMC</title><link>https://forum.armbian.com/topic/30676-rock5a-and-emmc/</link><description><![CDATA[<p>
	I don't expect an answer at this point but FYI, the <abbr title="embedded MultiMediaCard"><abbr title="embedded MultiMediaCard">eMMC</abbr></abbr> on a Rock5a and latest image does not work properly. It mounts and as soon as you start writing, errors occurs and the FS (ext4) is remounted RO. It happens whether I mount and write manually or I use the armbian-config to transfer the system on the <abbr title="embedded MultiMediaCard"><abbr title="embedded MultiMediaCard">eMMC</abbr></abbr>. Using the Debian distro of radxa, I can write as much as I want on the <abbr title="embedded MultiMediaCard"><abbr title="embedded MultiMediaCard">eMMC</abbr></abbr> w/o errors, so it does not seem to be a failed module, rather something in the armbian kernel.
</p>

<p>
	 
</p>

<p>
	2023-10-10T17:05:03.106367-07:00 rock-5a kernel: [62335.087809] Buffer I/O error on device mmcblk0p1, logical block 648585<br />
	2023-10-10T17:05:04.109720-07:00 rock-5a kernel: [62336.091002] blk_update_request: I/O error, dev mmcblk0, sector 97152552 op 0x1:(WRITE) flags 0x0 phys_seg 6 prio class 0<br />
	2023-10-10T17:05:04.109831-07:00 rock-5a kernel: [62336.091024] EXT4-fs warning (device mmcblk0p1): ext4_end_bio:347: I/O error 10 writing to inode 3015741 starting block 12144078)
</p>

<p>
	 
</p>
]]></description><guid isPermaLink="false">30676</guid><pubDate>Tue, 10 Oct 2023 06:13:00 +0000</pubDate></item><item><title>Turn off the leds (pwr_led)</title><link>https://forum.armbian.com/topic/49843-turn-off-the-leds-pwr_led/</link><description><![CDATA[<p>
	I need to turn off the pwr_led light under the armbian system, thank!
</p>
]]></description><guid isPermaLink="false">49843</guid><pubDate>Sat, 15 Feb 2025 05:59:48 +0000</pubDate></item><item><title>Armsom Sige5 UART10 Overlay</title><link>https://forum.armbian.com/topic/57995-armsom-sige5-uart10-overlay/</link><description><![CDATA[<p>
	I'm trying to enable UART6, UART7, and UART10 via overlays on a sige5 board. UART6 AND UART7 are working fine but I'm not seeing UART10 in the /dev directory. Could someone help me debug this?
</p>
]]></description><guid isPermaLink="false">57995</guid><pubDate>Thu, 12 Feb 2026 21:16:16 +0000</pubDate></item><item><title>BigTreeTech CB2 no vendor config</title><link>https://forum.armbian.com/topic/58265-bigtreetech-cb2-no-vendor-config/</link><description><![CDATA[<p>
	Hi all<br />
	i tried to compile BTT CB2 with bookworm and vendor kernel to get MPP and NPU working, but got that <span>:</span><br />
	sha256sum: config/kernel/linux-rockchip64-vendor.config: No such file or directory<br />
	<br />
	is it missed ? How to compile vendor kernel for MPP support?<br />
	<br />
	thanks<br />
	 
</p>
]]></description><guid isPermaLink="false">58265</guid><pubDate>Tue, 03 Mar 2026 07:59:05 +0000</pubDate></item><item><title>rtl8192fs/rtl8192cs source build</title><link>https://forum.armbian.com/topic/58207-rtl8192fsrtl8192cs-source-build/</link><description><![CDATA[<p>
	I'm putting together a build for a 3D printer, rk3308b-s board that has no ethernet, just a Fn-link wifi chip that is a knock-off of an rtl8192fs.  I pulled the OEM <abbr title="Device tree source">dts</abbr> and it describes the chip as an rtl8192cs.  I'm pretty sure this is an out of kernel driver and my searches indicate I put source in userpatches.  What do I need to add in the board/*.<abbr title="Community supported Chip - no official support">csc</abbr> file to build to an image with the kernel module(s)?
</p>

<p>
	 
</p>

<p>
	I do have a ralink ra2400, a mt7201 and some supported realtek dongles and If connected, I could git the code build and moprobe the module to test.  Ideally, I would like to incorporate the driver via dkms in a armbian build.  Can someone point me to the process?
</p>

<p>
	 
</p>

<p>
	 
</p>
]]></description><guid isPermaLink="false">58207</guid><pubDate>Sat, 28 Feb 2026 04:36:57 +0000</pubDate></item><item><title>Orangepi 5 Ultra. Has problem with OV13850 - got dark image.</title><link>https://forum.armbian.com/topic/58154-orangepi-5-ultra-has-problem-with-ov13850-got-dark-image/</link><description><![CDATA[<p>
	I have installed fresh Armbian IOT community image for Orangepi 5 Max on my Opi5Ultra. Generally works fine, but connected camera (OV13850) not properly works. Via gst-launch I got dark images. Only flashlight or lamp can see on image. In original Orangepi 5 Ultra OS image this issue can be fixed by disabling <u>docker</u> and <u>containerd</u> services and sockets. But Armbian system has not any docker or contanerd services. Can you help me fix this issue? I am going try other cameras - OV9281 and IMX415 and I not have overlays for it. Can somebody publish .dtbo files for those cameras?<span></span><span></span><span></span><span></span><span></span><span></span><span></span>
</p>

<p><a href="https://forum.armbian.com/uploads/monthly_2026_02/frame.jpg.a4d38392e48ff89d5f5806e66601294f.jpg" class="ipsAttachLink ipsAttachLink_image" ><img data-fileid="16094" src="https://forum.armbian.com/uploads/monthly_2026_02/frame.thumb.jpg.9c849db144343eb4d1bddfbc2ec6e564.jpg" data-ratio="56.3" width="1000" class="ipsImage ipsImage_thumbnailed" alt="frame.jpg"></a></p>]]></description><guid isPermaLink="false">58154</guid><pubDate>Tue, 24 Feb 2026 21:51:54 +0000</pubDate></item><item><title>rk3308B Sovol SV06 Ace Klipper using mks skipr as a starting point</title><link>https://forum.armbian.com/topic/57569-rk3308b-sovol-sv06-ace-klipper-using-mks-skipr-as-a-starting-point/</link><description><![CDATA[<p>
	Hi,
</p>

<p>
	 
</p>

<p>
	I'm new to the forums and am looking into replacing OEM Klipper firmware on a Sovol SV06 Ace,
</p>

<p>
	The main board  looks very similar to the MKS Skipr with the following notable differences:
</p>

<p>
	rk3308 B
</p>

<p>
	<abbr title="embedded MultiMediaCard"><abbr title="embedded MultiMediaCard">emmc</abbr></abbr> soldered on
</p>

<p>
	No SD card.
</p>

<p>
	Wifi/Bluetooth added - Original boards used realtek and the latest version uses Broadcom.
</p>

<p>
	 
</p>

<p>
	OEM wifi is hit or miss on connecting and hopefull will be improved with Trixie based Armbian.
</p>

<p>
	Sovol has mostly complied with the GPL and source/configuration files are on github. IIRC the kernel version was 5.1x
</p>

<p>
	 
</p>

<p>
	I'm a long time Linux user (Slackware 8.1), have contributed OpenWRT builds and have built custom Linux kernels.
</p>

<p>
	 
</p>

<p>
	I think I've mapped out the install:
</p>

<p>
	flash the appropriate ambian image to a formated USB2.0 drive - Ideally with wifi ssid/wpa key
</p>

<p>
	ssh sovol@ip login sovol/sovol.  su, suspect the root passwd will be makerbase.
</p>

<p>
	plug in usb, id drive in dmesg and mount
</p>

<p>
	dd if /dev/usb* of=/devmmcblk*
</p>

<p>
	Unmount drive and hopefully boot and access over wifi ssh.
</p>

<p>
	Install/configure Kipper/Mainsail...
</p>

<p>
	 
</p>

<p>
	I have a recovery path that I have tested using rkdeveloptool/upgrade_tool and the original Sovol firmware.
</p>

<p>
	 
</p>

<p>
	I've perused the armbian github pages looking the MKS Skipr build but have not found it yet.
</p>

<p>
	I'm willing to build a tailored (stripped if worthwhile) kernel.
</p>

<p>
	I'd appreciate any comments about broadcom wifi access and if newer kernels and newer wpa supplicant builds improve access enough to make it worthwhile.
</p>

<p>
	Comments on the overall plan.
</p>

<p>
	Pointers 
</p>

<p>
	<a class="ipsAttachLink ipsAttachLink_image" href="https://forum.armbian.com/uploads/monthly_2026_01/Mainboard_Kit_for_SV06_ACE.jpg.4fea29f3d885d0eb04b75b0ba56c1123.jpg" data-fileid="15881" data-fileext="jpg" rel=""><img alt="Mainboard_Kit_for_SV06_ACE.jpg" class="ipsImage ipsImage_thumbnailed" data-fileid="15881" data-ratio="70.51" width="824" src="https://forum.armbian.com/uploads/monthly_2026_01/Mainboard_Kit_for_SV06_ACE.jpg.4fea29f3d885d0eb04b75b0ba56c1123.jpg" /></a>
</p>
<p>
<a class="ipsAttachLink" href="https://forum.armbian.com/applications/core/interface/file/attachment.php?id=15890&amp;key=6f3486e49ef3236163222bc289c69264" data-fileExt='pdf' data-fileid='15890' data-filekey='6f3486e49ef3236163222bc289c69264'>Sovol RG-4Z V1.1 SIZE.pdf</a></p>]]></description><guid isPermaLink="false">57569</guid><pubDate>Thu, 22 Jan 2026 00:15:45 +0000</pubDate></item><item><title>Ethernet and Auto-login Issues on Orange Pi 3B after Latest Update</title><link>https://forum.armbian.com/topic/58142-ethernet-and-auto-login-issues-on-orange-pi-3b-after-latest-update/</link><description><![CDATA[<p>
	I’m using an Orange Pi 3B running Armbian Trixie Minimal as a headless <abbr title="Single board computer">SBC</abbr>. It has been working fine for a couple of months, but after a recent reboot, it failed to connect to the network.
</p>

<p>
	After connecting an HDMI cable to troubleshoot, I realized the system is no longer auto logging in; it gets stuck at the login screen. Once I log in manually, I found that the wired network (Ethernet) isn't working at all, though wireless is functioning fine. I even tried flashing the latest image from the website, but the issues persist.
</p>

<p>
	To summarize, I have two main problems:
</p>

<p>
	- Wired connection (Ethernet) is not working.
</p>

<p>
	- The system no longer auto-logs in after booting.
</p>

<p>
	Has anyone else encountered this with the recent Trixie builds?
</p>
]]></description><guid isPermaLink="false">58142</guid><pubDate>Mon, 23 Feb 2026 16:30:33 +0000</pubDate></item><item><title>rk3308b build using /sys/firmware/ftb on Sovol SV06 Ace</title><link>https://forum.armbian.com/topic/58141-rk3308b-build-using-sysfirmwareftb-on-sovol-sv06-ace/</link><description><![CDATA[<p>
	Per the title, I was able to extract an ftb file and convert it to <abbr title="Device tree blob"><abbr title="Device tree blob">dtb</abbr></abbr> and <abbr title="Device tree source"><abbr title="Device tree source">dts</abbr></abbr> file.  I would like to use the community build framework and build Armbian for SV06 Ace.
</p>

<p>
	The initial plan was to base the new board/*<abbr title="Community supported Chip - no official support"><abbr title="Community supported Chip - no official support">csc</abbr></abbr> files on other rk3308b boards; sakurapi and rock-s0 and then pull configuration values from the OEM <abbr title="Device tree source"><abbr title="Device tree source">dts</abbr></abbr> file.
</p>

<p>
	 
</p>

<p>
	I'm confused about the <abbr title="Device tree source"><abbr title="Device tree source">dts</abbr></abbr> structure in Community builds and the proper locations for defconfig, <abbr title="Device tree source"><abbr title="Device tree source">dts</abbr></abbr> and dtsi files.
</p>

<p>
	 
</p>

<p>
	I've worked with the files in OpenWRT where they are rigidly structured - something that would be a monumental task for Armbian community builds.
</p>

<p>
	 
</p>

<p>
	The OEM <abbr title="Device tree source"><abbr title="Device tree source">dts</abbr></abbr> file does not use any includes/dtsi files.  If successful, I would like to publish on github similiar to <a contenteditable="false" data-ipshover="" data-ipshover-target="https://forum.armbian.com/profile/215357-torte/?do=hovercard" data-mentionid="215357" href="https://forum.armbian.com/profile/215357-torte/" rel="">@Torte</a> <a href="https://github.com/torte71/armbian-mksklipad50" rel="external nofollow">https://github.com/torte71/armbian-mksklipad50</a>
</p>

<p>
	Can someone point me to the relevant documentation for Armbian <abbr title="Device tree source"><abbr title="Device tree source">dts</abbr></abbr> files?
</p>
]]></description><guid isPermaLink="false">58141</guid><pubDate>Mon, 23 Feb 2026 16:29:50 +0000</pubDate></item><item><title>Luckfox Lyra Ultra W armbian doesn't load</title><link>https://forum.armbian.com/topic/56530-luckfox-lyra-ultra-w-armbian-doesnt-load/</link><description><![CDATA[<p>
	Hello everyone! I need help.<br />
	I was very happy to learn that Armbian support is now available for the Luckfox Lyra Ultra W!
</p>

<p>
	<a href="https://blog.armbian.com/github-highlights-5/" rel="external nofollow">https://blog.armbian.com/github-highlights-5/</a>
</p>

<p>
	This board has 8GB of EMCC memory and the firmware needs to be loaded onto this EMCC.
</p>

<p>
	I went to this page in this mini guide
</p>

<p>
	<a href="https://github.com/armbian/build/pull/8862?ref=blog.armbian.com" rel="external nofollow">https://github.com/armbian/build/pull/8862?ref=blog.armbian.com</a>
</p>

<p>
	where is the author @vidplace7  clearly indicates how to correctly compile and install the firmware
</p>

<pre class="ipsCode prettyprint lang-html prettyprinted"><span class="pln">./compile.sh BOARD=luckfox-lyra-ultra-w BRANCH=vendor KERNEL_CONFIGURE=no DEB_COMPRESS=xz KERNEL_BTF=yes INSTALL_ARMBIAN_FIRMWARE=no BUILD_DESKTOP=no BUILD_MINIMAL=yes RELEASE=trixie
Boot from emmc working (write to 0x0 with rkdevtool as the generated image includes the "loader")
Shell works over UART0
AIC8800DC WiFi works
Ethernet works</span></pre>

<p>
	I compiled the Armbian-unofficial_25.11.0-trunk_Luckfox-lyra-ultra-w_trixie_vendor_6.1.115_minimal.img firmware without any problems and ran the RKDevTool_Release_v2.96 program.
</p>

<p>
	I pressed the boot button on the device and the program RKDevTool displayed a message that the Loader device was found.
</p>

<p>
	I checked item 2, selected emcc, the address was 0X0000000, and selected the image to flash: Armbian-unofficial_25.11.0-trunk_Luckfox-lyra-ultra-w_trixie_vendor_6.1.115_minimal.img.<br />
	I pressed RUN.
</p>

<p>
	<img alt="Screenshot_1.png.a789925ca99d1140aa9bc9ad765d612e.png" class="ipsImage ipsImage_thumbnailed" data-fileid="15568" data-ratio="46.64" width="967" src="https://forum.armbian.com/uploads/monthly_2025_12/Screenshot_1.png.a789925ca99d1140aa9bc9ad765d612e.png" /><br />
	The flashing completed successfully.<br />
	The device rebooted, and the red LED lit up for 30 seconds, then went out—and that was it. The device no longer responded and wouldn't boot. If I pressed the BOOT button afterwards, the device didn't respond and didn't enter LOADER mode.<br />
	The only way to restore the device is to short two points on the rear panel and apply power. The device will be detected in RKDevTool in Maskrom mode, and you can load the factory firmware.
</p>

<p>
	Unfortunately, I don't know how to contact the author @vidplace7  - <a href="https://github.com/armbian/linux-rockchip/pull/418" rel="external nofollow">https://github.com/armbian/linux-rockchip/pull/418</a>
</p>

<p>
	Please tell me what I did wrong? And why does the device become bricked after reflashing? I really want to install a normal system on it!
</p>

<p>
	 
</p>

<p>
	 
</p>
]]></description><guid isPermaLink="false">56530</guid><pubDate>Mon, 01 Dec 2025 18:10:06 +0000</pubDate></item><item><title>LuckFox Core3566 flash eMMC</title><link>https://forum.armbian.com/topic/58074-luckfox-core3566-flash-emmc/</link><description><![CDATA[<p>
	Hi all. i got Armbian for luckfox, compiled by builder, and also tried downloaded img binaries. but cannot find clear and complete instruction how to write thtat img to <abbr title="embedded MultiMediaCard"><abbr title="embedded MultiMediaCard">eMMC</abbr></abbr>  and for SDCard .<br />
	<br />
	what tools and steps should be used for get Armbian img boots and works on that board.<br />
	<br />
	thanks in advance<br />
	<br />
	PS. BigTreetech CB2 same problem - no clear info about flash <abbr title="embedded MultiMediaCard"><abbr title="embedded MultiMediaCard">eMMC</abbr></abbr> and SDCard.<br />
	<br />
	 
</p>
]]></description><guid isPermaLink="false">58074</guid><pubDate>Wed, 18 Feb 2026 17:57:05 +0000</pubDate></item><item><title>No LED device nodes since 6.12 (rock64)</title><link>https://forum.armbian.com/topic/58035-no-led-device-nodes-since-612-rock64/</link><description><![CDATA[<p>
	Hello
</p>

<p>
	since kernel 6.12 led (heartbeat and mmc activity) on board rock64 don't work. I've created issue in dietPI github:
</p>

<p>
	<a href="https://github.com/MichaIng/DietPi/issues/7618" rel="external nofollow">https://github.com/MichaIng/DietPi/issues/7618</a>
</p>

<p>
	but DietPI is using armbian kernel.
</p>

<p>
	Now I'm using recent armbian with kernel 6.11.0-edge-rockchip64. Any idea how to restore led activity on recent kernels?
</p>
]]></description><guid isPermaLink="false">58035</guid><pubDate>Sun, 15 Feb 2026 20:10:26 +0000</pubDate></item><item><title>Rock64 What do you use it for ?</title><link>https://forum.armbian.com/topic/56554-rock64-what-do-you-use-it-for/</link><description><![CDATA[<p>
	Hello:
</p>

<p>
	 
</p>

<p>
	To compare all available use of this so great card, we could share our uses.
</p>

<p>
	 
</p>

<p>
	For me i se it with <span>:</span>
</p>

<p>
	<span>-OpenMediaVault for the NAS function; as file copy save and Torrent</span>
</p>

<p>
	<span>-Transmission for the torrent sharing</span>
</p>

<p>
	<span>-2 HDDs to save files on USB 3 and 2.</span>
</p>

<p>
	 
</p>

<p>
	And you ?
</p>

<p>
	 
</p>

<p>
	I have a Rock64 1Gb with external power station 5A power
</p>
]]></description><guid isPermaLink="false">56554</guid><pubDate>Wed, 03 Dec 2025 22:14:57 +0000</pubDate></item><item><title>Update SPI on e25?</title><link>https://forum.armbian.com/topic/58009-update-spi-on-e25/</link><description><![CDATA[<p>
	I assume I should be using the MTD/SPI for u-boot on this device?
</p>

<p>
	If so, how do I update it and choose the boot order?
</p>

<p>
	 
</p>

<p>
	armbian-install complains "No SPI image found." if I select "Install/Update the bootloader on MTD Flash"
</p>
]]></description><guid isPermaLink="false">58009</guid><pubDate>Fri, 13 Feb 2026 19:18:07 +0000</pubDate></item><item><title>Radxa e25 Image not booting</title><link>https://forum.armbian.com/topic/57996-radxa-e25-image-not-booting/</link><description><![CDATA[<p>
	The Radxa bullseye image looks to boot fine, but Armbian forky does not boot at all.
</p>

<p>
	 
</p>
]]></description><guid isPermaLink="false">57996</guid><pubDate>Thu, 12 Feb 2026 23:53:33 +0000</pubDate></item><item><title>Odroid M2 16G</title><link>https://forum.armbian.com/topic/48461-odroid-m2-16g/</link><description><![CDATA[<p>
	 
</p>

<p>
	Because i need a more recent kernel than 5.10 on my odroid m2, i tried armbian.
</p>

<p>
	i searched for the nearest model and i manage to find Radxa Rock 5C (rocky 3588s2)<br />
	i flash <abbr title="embedded MultiMediaCard">emmc</abbr> with Bleeding edge images with Armbian Linux v6.11/ Debian 12 (Bookworm)Minimal / IOT for the rock 5c<br />
	 
</p>

<p>
	in /boot/armbianEnv.txt i changed just one line after installation <span>:</span>
</p>

<p>
	<strong>fdtfile=rockchip/rk3588s-odroid-m2.<abbr title="Device tree blob">dtb</abbr></strong>
</p>

<p>
	 
</p>

<p>
	and after a final apt upgrade i can run version 6.12.1-edge-rockchip-rk3588 of the kernel.
</p>

<p>
	 
</p>

<p>
	for now it seems fine to me.
</p>

<p>
	 
</p>
]]></description><guid isPermaLink="false">48461</guid><pubDate>Fri, 20 Dec 2024 22:26:47 +0000</pubDate></item><item><title>Helios64 Like New for Sale - Make Offer!</title><link>https://forum.armbian.com/topic/57921-helios64-like-new-for-sale-make-offer/</link><description><![CDATA[<p>
	If anyone is still interested, I have a Helios 64 that I assembled, looked at, but never got around to using for more than a couple hours.  Works fine, does not yet have the 2.5GB fix but I have the instructions for same.
</p>

<p>
	No idea what to ask for it but it certainly isn't doing me any good sitting on my shelf. Have the manual, SATA drive bay adapters for 2.5" drives and the like. Make me an offer and pay shipping from Oregon.  Let's talk!
</p>
]]></description><guid isPermaLink="false">57921</guid><pubDate>Sun, 08 Feb 2026 18:13:20 +0000</pubDate></item><item><title>Helios64 at the end of 2025</title><link>https://forum.armbian.com/topic/56353-helios64-at-the-end-of-2025/</link><description><![CDATA[<p>
	Hi folks, long time lurker here.
</p>

<p>
	 
</p>

<p>
	My helios64 is pretty much brand new, didn’t really needed it at that time, only bought it as I found it really cool. I may power it a couple of times per year for some backups (got 3x 6tb in it, no raid so I can take them out when needed, also back up stuff to external drives), it still starts-up from the initial sd card as I never finished setting it up. I also have a 1 bay separate NAS for downloading movies that if fails, I will just replace; and a drive attached directly to my router for easy file swaps; so don’t need much running 24x7.
</p>

<p>
	 
</p>

<p>
	While I work in IT (on the Windows side, so the Armbian stuff is still a learning path for me), the last years have been so busy that I can’t find myself tinkering anymore at the end of the day.
</p>

<p>
	 
</p>

<p>
	To the ones of you that are running one, does it still make sense, or should I maybe switch to something more mainstream?
</p>

<p>
	 
</p>

<p>
	Thank you!
</p>
]]></description><guid isPermaLink="false">56353</guid><pubDate>Sun, 23 Nov 2025 19:31:06 +0000</pubDate></item><item><title>Does anyone have a Kobol Helios64 to sale ? (europe preferably)</title><link>https://forum.armbian.com/topic/30081-does-anyone-have-a-kobol-helios64-to-sale-europe-preferably/</link><description><![CDATA[<p>
	Hello,<br />
	i have trouble with my Helios64 (possibly bricked), so I am interested to by a new one.<br />
	And if i can fix mine, the second one could allow me to participate to armbian support for it.<br />
	 
</p>

<p>
	Anyone have one for sale ? Preferably in Europe.<br />
	<br />
	Thank you.
</p>
]]></description><guid isPermaLink="false">30081</guid><pubDate>Thu, 07 Sep 2023 15:22:05 +0000</pubDate></item><item><title>Board Bring-up Youyeetoo YY3568 RockChip RK3568</title><link>https://forum.armbian.com/topic/49775-board-bring-up-youyeetoo-yy3568-rockchip-rk3568/</link><description><![CDATA[<p>
	Here will be published all the tweaks for the Youyeetoo YY3568 board to enter the mainline with armbian.
</p>

<p>
	 
</p>

<p>
	 <a href="https://github.com/armbian/community/releases" rel="external nofollow">Official Images </a>
</p>

<p>
	 <a href="https://forum.armbian.com/topic/49775-board-bring-up-youyeetoo-yy3568-rockchip-rk3568/#findComment-214183" rel="">Unofficial images</a><br />
	<br />
	Kernel Vendor 6.1:<br />
	<a href="https://github.com/armbian/linux-rockchip/commit/27a98750790114235c72e8420d45f44eff210461" rel="external nofollow">https://github.com/armbian/linux-rockchip/commit/27a98750790114235c72e8420d45f44eff210461</a>
</p>

<p>
	 
</p>

<p>
	Overlays:<br />
	<a href="https://github.com/armbian/linux-rockchip/commit/18f066190842fc6bd509662a2d19588eb9f04612" rel="external nofollow">https://github.com/armbian/linux-rockchip/commit/18f066190842fc6bd509662a2d19588eb9f04612</a>
</p>

<p>
	 
</p>

<p>
	Kernel Vendor 5.1:<br />
	<a href="https://github.com/armbian/linux-rockchip/commit/b5964f997e2267802db0a965e66ec299b8a1f437" rel="external nofollow">https://github.com/armbian/linux-rockchip/commit/b5964f997e2267802db0a965e66ec299b8a1f437</a>
</p>

<p>
	 
</p>

<p>
	 
</p>

<p>
	 
</p>

<p>
	 
</p>

<p style="text-align:center;">
	<a class="ipsAttachLink ipsAttachLink_image" data-fileext="webp" data-fileid="13982" href="https://forum.armbian.com/uploads/monthly_2025_02/up.webp.858bc0b06e0789abc29729c64e848a67.webp" rel=""><span style="font-size:11px;"><img alt="up.thumb.webp.e3958b1492c860d2352f01991fbe8356.webp" class="ipsImage ipsImage_thumbnailed" data-fileid="13982" data-ratio="67.20" width="1000" src="https://forum.armbian.com/uploads/monthly_2025_02/up.thumb.webp.e3958b1492c860d2352f01991fbe8356.webp" /></span></a>
</p>

<p style="text-align:center;">
	<a class="ipsAttachLink ipsAttachLink_image" data-fileext="webp" data-fileid="13983" href="https://forum.armbian.com/uploads/monthly_2025_02/botom.webp.fd8b7287ef41d46dc76123b2a16481c6.webp" rel=""><img alt="botom.thumb.webp.4307d219fba1353fa07037d4f7e357e0.webp" class="ipsImage ipsImage_thumbnailed" data-fileid="13983" data-ratio="47.30" width="1000" src="https://forum.armbian.com/uploads/monthly_2025_02/botom.thumb.webp.4307d219fba1353fa07037d4f7e357e0.webp" /></a>
</p>

<p style="text-align:center;">
	<a class="ipsAttachLink ipsAttachLink_image" data-fileext="webp" data-fileid="13984" href="https://forum.armbian.com/uploads/monthly_2025_02/core.webp.439a3a0af348c91fac2ac9002c626fa2.webp" rel=""><img alt="core.thumb.webp.bb04d1788e57c11efa7df3a1cec8a33a.webp" class="ipsImage ipsImage_thumbnailed" data-fileid="13984" data-ratio="100.00" width="750" src="https://forum.armbian.com/uploads/monthly_2025_02/core.thumb.webp.bb04d1788e57c11efa7df3a1cec8a33a.webp" /></a>
</p>
]]></description><guid isPermaLink="false">49775</guid><pubDate>Tue, 11 Feb 2025 16:55:42 +0000</pubDate></item><item><title>Linux Headers</title><link>https://forum.armbian.com/topic/57705-linux-headers/</link><description><![CDATA[<p>
	On the 25.11.1 Noble release, using the 6.12 kernel, there is no package to install the linux-headers for installed kernel. Is there some place to get them so that it is possible to install a kernel module  for the provided ubuntu-rockchip kernel?
</p>
]]></description><guid isPermaLink="false">57705</guid><pubDate>Fri, 30 Jan 2026 23:26:55 +0000</pubDate></item><item><title>Very strange behavior: complete freeze after boot</title><link>https://forum.armbian.com/topic/57402-very-strange-behavior-complete-freeze-after-boot/</link><description><![CDATA[<p>
	Hello,
</p>

<p>
	 
</p>

<p>
	I have installed a tinkerboard 2S and used it without problems for more than a year now. Today I started Armbian-upgrade to upgrade the system.I use a M2 WIFI card. What happens right after the reboot when the upgrade was done; the system boots normally, showing all information on the monitor, and about 5 seconds after the login prompt is displayed, it completely freezes. That is; the system doesn't react to keypresses on my USB keyboard, and SSH access isn't reacting.
</p>

<p>
	I can ping the device however and I know it is not dead as my .NET core application is running normally and I can access it externally! I use a wifi hotspot configuration; the wifi network is also not available after boot.
</p>

<p>
	 
</p>

<p>
	Now, I have a NanoPI R3C also with M2 wifi and configured exactly the same; it also behaves the same: console freeze, no ssh access. When I remove the Wifi card it does not freeze so it looks like related to the wifi card/configuration. I bought a R67S with wifi as I though it was a hardware failure but now, after upgrading my tinker it appears it's software related.
</p>

<p>
	 
</p>

<p>
	As my Tinkerboard 2S was working flawlessly before I upgraded; are there any known issues in Debian Trixie minimal installation? I use this on both devices.
</p>

<p>
	 
</p>

<p>
	Regards,
</p>

<p>
	 
</p>

<p>
	Frans
</p>
]]></description><guid isPermaLink="false">57402</guid><pubDate>Thu, 15 Jan 2026 16:58:44 +0000</pubDate></item><item><title>A cheap UAC 1.0 in to UAC 2.0 out converter that allows your PS5, switch, etc to use high end speakers</title><link>https://forum.armbian.com/topic/53373-a-cheap-uac-10-in-to-uac-20-out-converter-that-allows-your-ps5-switch-etc-to-use-high-end-speakers/</link><description><![CDATA[<p>
	Hi, I would like to share my recent work: a cheap USB Audio Class 1.0 (UAC) input to UAC 2.0 output converter.
</p>

<p>
	 
</p>

<p>
	For folks that may not understand why I have this crazy idea, here is the background:
</p>

<p>
	For some shitty reasons, PS5 does not support outputting audio through certain USB sound card, and that is because PS5 only supports very old USB sound card (UAC 1.0), and usually high end speakers or sound cards would use newer, better UAC 2.0 protocol.
</p>

<p>
	So, this shitty thing happens to me, when I thought my EDIFIER S880 speaker would be a plus for my gaming experience. EDIFIER S880 has a UAC 2.0 in input source, so my PS5 does not support that. So, what I can do is to use another 3.5 jack to connect the speaker to my PS5.
</p>

<p>
	Unfortunately, there is a staticky buzz sound throughout this channel. What's even worse is that EDIFIER S880 has 6 input source selection, but I can only switch to the next source, wait for 2 seconds, and repeat this process 5 times every time I want to switch the audio from my computer to the PS5.
</p>

<p>
	 
</p>

<p>
	After lots of trials and flashing my custom kernel, I finally did it!
</p>

<p>
	The idea is to use a board that has 1 USB otg port to act as a UAC 1.0 sound card, and has another 1 USB host port to connect to the UAC 2.0 speakers, then run programs on that board to redirect sound from USB otg port to USB host port. It is even a plus that the board consumes less power, so we do not need an extra or special power supply for it; this becomes crucial, especially when sharing the same USB connection with the USB otg port (<abbr title="Single board computer"><abbr title="Single board computer">SBC</abbr></abbr> boards are more power-hungry these days!). The standard USB 2.0 protocol only allows 5V 0.5A to the device connected.
</p>

<p>
	I actually built one with an Orange Pi One board, but it turns out that the CPU is not fast enough, and there are sound glitches sometimes.
</p>

<p>
	 
</p>

<p>
	With some research, I found this board that perfectly fits my needs: <a href="https://radxa.com/products/zeros/zero3w/" rel="external nofollow">Radxa zero 3W</a>. Here is the advantage:
</p>

<p>
	- It is cheap, and the one I used is the nearly minimum SKU (1 GB ram with 8 GB onboard <abbr title="embedded MultiMediaCard"><abbr title="embedded MultiMediaCard">eMMC</abbr></abbr>, they also have no onboard <abbr title="embedded MultiMediaCard"><abbr title="embedded MultiMediaCard">eMMC</abbr></abbr> SKU).
</p>

<p>
	- The otg port could handle USB PD protocol, meaning no special hacks are needed, you could get at most 30W of power, if needed (and turns out the normal USB 2.0 port on my PS5 works perfectly, so I guess it consumes less than 5V 1A = 5W)
</p>

<p>
	- It is tiny.
</p>

<p>
	 
</p>

<p>
	However, things don't work right out of the box. At the beginning, I flashed the official, latest Radxa OS, modprobe the g_audio. It is running as a UAC 2.0 device, so it is not the one I want. As a result, I grabbed their kernel source, changed the config to UAC 1.0 gadget, and flashed onto the board, but there seems to be some issues in their kernel fork for UAC 1.0 driver: there was no /dev/snd/controlC0, so the g_audio failed to run.
</p>

<p>
	As a result, I turned to use the <a href="https://www.armbian.com/radxa-zero-3/" rel="external nofollow">Armbian build</a>. This time, the /dev/snd/pcmC0D0c is missing, so g_audio failed to run again.
</p>

<p>
	I then compiled my own kernel, flashed it onto the board. The Armbian build is with kernel 6.1, and the kernel I built is kernel 6.12, then the board failed to boot to the kernel due to U-Boot thought there were some errors.
</p>

<p>
	Luckily, I found that building the whole Armbian image with kernel 6.12 can boot without issues, so I built a custom kernel 6.12 with UAC 1.0 enabled image, modeprobe the g_audio module, and it finally worked!
</p>

<p>
	 
</p>

<p>
	After that, I <span style="font-family:'Open Sans', '-apple-system', BlinkMacSystemFont, 'Segoe UI', Roboto, Helvetica, Arial, sans-serif, 'Apple Color Emoji', 'Segoe UI Emoji', 'Segoe UI Symbol';">crafted a simple golang SystemV daemon for bootstrapping and terminating the alsaloop program for redirecting the sound, and used a udev rule to notify that daemon of the attachment/detachment of the USB speaker out event. The converter is finally working!</span>
</p>

<p>
	 
</p>

<p>
	Here is the <a href="https://drive.google.com/drive/folders/1oRkGGSDjFqNLxGIW6PeXj5rTHSIQAmyk" rel="external nofollow">pre-built image</a> for folks who want a quick test. It is based on the commit b27c86e620dcd9f55daadf52ccc85643dba2a381 from the <a href="https://github.com/armbian/build" rel="external nofollow">armbian build</a> repo with the following config modification:
</p>

<pre class="ipsCode">diff --git a/config/kernel/linux-rockchip64-current.config b/config/kernel/linux-rockchip64-current.config
index d053d0997..6e360bba7 100644
--- a/config/kernel/linux-rockchip64-current.config
+++ b/config/kernel/linux-rockchip64-current.config
@@ -3507,3 +3507,8 @@ CONFIG_RATIONAL_KUNIT_TEST=m
 CONFIG_MEMCPY_KUNIT_TEST=m
 CONFIG_TEST_MEMCAT_P=m
 CONFIG_MEMTEST=y
+
+CONFIG_USB_CONFIGFS_F_UAC1=y
+CONFIG_USB_CONFIGFS_F_UAC2=n
+CONFIG_USB_F_UAC2=n
+CONFIG_GADGET_UAC1=y</pre>

<p>
	 
</p>

<p>
	Currently, the "current" build does not detect the Wi-Fi interface, but as it does not affect the audio converting feature, I may not put too much effort into this.
</p>

<p>
	<a class="ipsAttachLink ipsAttachLink_image" data-fileext="jpg" data-fileid="14715" href="https://forum.armbian.com/uploads/monthly_2025_06/513919885_24917693217820649_4158967047271126518_n.jpg.be94adde6e6b1b7468aa1d39604b6b38.jpg" rel=""><img alt="513919885_24917693217820649_4158967047271126518_n.jpg" class="ipsImage ipsImage_thumbnailed" data-fileid="14715" data-ratio="75" width="1000" src="https://forum.armbian.com/uploads/monthly_2025_06/513919885_24917693217820649_4158967047271126518_n.thumb.jpg.a386b06b361300d03ca888915e494532.jpg" /></a>
</p>
]]></description><guid isPermaLink="false">53373</guid><pubDate>Sun, 29 Jun 2025 06:37:50 +0000</pubDate></item><item><title>Adding / Modifying Boards - What is the right approach?</title><link>https://forum.armbian.com/topic/57633-adding-modifying-boards-what-is-the-right-approach/</link><description><![CDATA[<p>
	I am working on a new version of the Luckfox Core3566 Board and Patches, as well as adding the Orange PI CM4 board to Armbian. Both rely on the Rockchip RK3566. 
</p>

<p>
	<br />
	Luckfox Core3566
</p>

<p>
	Starting with the Core3566: The current board is just the vendor u-boot and kernel. It lacks PCIe support, but surely it is helpful to be as near to manufacturer configuration in their patches. My board config on the other side is not supporting the vendor specific patches, but based on a clean u-boot v2025.10 and runs nicely with current and edge kernels and also runs smoothly with nvme storage. 
</p>

<p>
	The luckfox-core3566 config is currently maintainerless, but maybe users would like to have this vendor kernel version. 
</p>

<p>
	 
</p>

<p>
	My question: <br />
	1) Would the Armbian rather like to replace the vendor board config with a more future proof board config like mine  
</p>

<p>
	or
</p>

<p>
	2) Keep both board versions ( like rename config/boards/luckfox-core3566.<abbr title="Community supported Chip - no official support"><abbr title="Community supported Chip - no official support">csc</abbr></abbr> to config/boards/luckfox-core3566_vendor.<abbr title="Community supported Chip - no official support"><abbr title="Community supported Chip - no official support">csc</abbr></abbr> ) and let my variant replace the config/boards/luckfox-core3566.<abbr title="Community supported Chip - no official support"><abbr title="Community supported Chip - no official support">csc</abbr></abbr> as default? 
</p>

<p>
	 
</p>

<p>
	3)rd option would be combine both configs, but I had struggle to do so, as my version is using a different u-boot, using a simplified partition setup etc. 
</p>

<p>
	<br />
	<br />
	Orange Pi cm4 
</p>

<p>
	I created a new board configuration to let Orange PI CM4 to work with Armbian as well. It is pretty similar to the bigtreetech cb2, but it's ethernet wiring and pcie powering device config differs from latter.  <br />
	Is it okay to create a MR directly in Github or does it need alignment with Moderators first? 
</p>

<p>
	 
</p>

<p>
	Cheers,
</p>

<p>
	Daniel 
</p>

<p>
	 
</p>

<p>
	PS: Nice to have time to work on embedded arm systems again. I did work on the sunxi based cubieboard and cubietruck back in the days, but job, family and basically life pulled me away from it for such a long time. 
</p>
]]></description><guid isPermaLink="false">57633</guid><pubDate>Mon, 26 Jan 2026 17:45:33 +0000</pubDate></item><item><title>Running Armbian on an Oscal Pad 70 WiFi</title><link>https://forum.armbian.com/topic/57632-running-armbian-on-an-oscal-pad-70-wifi/</link><description><![CDATA[<p>
	Good afternoon. I have a Rockchip 3566 tablet.oscal pad 70 wifi
</p>

<p>
	I'm writing using Google Translate, so there may be some inaccuracies... I apologize for that!
</p>

<p>
	motherboard R863T-RK3566-DK-V1.0
</p>

<p>
	wifi module wxt42j1001s - driver for android only
</p>

<p>
	 I understand it's probably very difficult...isn't the processor too old for our times? Or is installing Armbian probably not an option?<br />
	Thanks from the bottom of my heart to everyone who responded.
</p>

<p>
	<a class="ipsAttachLink ipsAttachLink_image" data-fileext="jpg" data-fileid="15911" href="https://forum.armbian.com/uploads/monthly_2026_01/qirtl2qqOLmkbsqwbgiXz0I3Wnz1XPH9oZJ92IbHEm12J.jpg.bb199b068ffb3a9bd39340ae1ef518bf.jpg" rel=""><img alt="qirtl2qqOLmkbsqwbgiXz0I3Wnz1XPH9oZJ92IbHEm12J.jpg" class="ipsImage ipsImage_thumbnailed" data-fileid="15911" data-ratio="130.21" width="384" src="https://forum.armbian.com/uploads/monthly_2026_01/qirtl2qqOLmkbsqwbgiXz0I3Wnz1XPH9oZJ92IbHEm12J.jpg.bb199b068ffb3a9bd39340ae1ef518bf.jpg" /></a>
</p>

<p>
	<a class="ipsAttachLink ipsAttachLink_image" data-fileext="jpg" data-fileid="15912" href="https://forum.armbian.com/uploads/monthly_2026_01/qirtdU4CKhJOooz1hEe9OoglkgaucHf2RVNni67fiNbF.jpg.75fc84be85258f918a0dcaa08d9378c5.jpg" rel=""><img alt="qirtdU4CKhJOooz1hEe9OoglkgaucHf2RVNni67fiNbF.jpg" class="ipsImage ipsImage_thumbnailed" data-fileid="15912" data-ratio="75" width="500" src="https://forum.armbian.com/uploads/monthly_2026_01/qirtdU4CKhJOooz1hEe9OoglkgaucHf2RVNni67fiNbF.jpg.75fc84be85258f918a0dcaa08d9378c5.jpg" /></a>
</p>

<p>
	<a class="ipsAttachLink ipsAttachLink_image" data-fileext="jpg" data-fileid="15913" href="https://forum.armbian.com/uploads/monthly_2026_01/Screenshot_2025-06-21-18-09-19-939_com_miui.gallery-edit.jpg.b626cb99362c5b2d40b44328ba8ed846.jpg" rel=""><img alt="Screenshot_2025-06-21-18-09-19-939_com.miui.gallery-edit.jpg" class="ipsImage ipsImage_thumbnailed" data-fileid="15913" data-ratio="143.95" width="521" src="https://forum.armbian.com/uploads/monthly_2026_01/Screenshot_2025-06-21-18-09-19-939_com_miui.gallery-edit.thumb.jpg.3251ae4ff1049776f4a4fda30f67bcf7.jpg" /></a>
</p>

<p>
	<a class="ipsAttachLink ipsAttachLink_image" data-fileext="jpg" data-fileid="15914" href="https://forum.armbian.com/uploads/monthly_2026_01/Screenshot_2025-06-21-18-12-43-367_com_miui.gallery-edit.jpg.f0ddecc13b7ec0af398570190412ca57.jpg" rel=""><img alt="Screenshot_2025-06-21-18-12-43-367_com.miui.gallery-edit.jpg" class="ipsImage ipsImage_thumbnailed" data-fileid="15914" data-ratio="149.7" width="501" src="https://forum.armbian.com/uploads/monthly_2026_01/Screenshot_2025-06-21-18-12-43-367_com_miui.gallery-edit.thumb.jpg.b0135dbf041ab973864ffc02cbf9b82c.jpg" /></a>
</p>
]]></description><guid isPermaLink="false">57632</guid><pubDate>Mon, 26 Jan 2026 16:44:02 +0000</pubDate></item><item><title>Rock64 - not booting after Armbian update</title><link>https://forum.armbian.com/topic/50743-rock64-not-booting-after-armbian-update/</link><description><![CDATA[<p>
	I have Rock64 Ver.2 - 1gb model.<br />
	 <br />
	Was working fine with Armbian 24.5.0-trunk.211_Rock64_bookworm_current_6.6.21 - boot from micro SD card<br />
	<br />
	On SSH, I updated to latest version Armbian_25.2.1_Rock64_bookworm_current_6.12.13. Now it does not boot from micro SD card.<br />
	<br />
	I had another micro sd card. I flashed new Armbian_25.2.1_Rock64_bookworm_current_6.12.13 - does not boot.<br />
	<br />
	I had another micro sd card. I flashed OLD Armbian 24.5.0-trunk.211_Rock64_bookworm_current_6.6.21 - it boots. Then updated to latest Armbian &amp; does not boot anymore.<br />
	<br />
	Looks like some " Flashing_u-boot_to_SPI_Flash " - problem.<br />
	<br />
	Please help.<br />
	<br />
	Thanks in advanced
</p>
]]></description><guid isPermaLink="false">50743</guid><pubDate>Tue, 25 Mar 2025 23:15:09 +0000</pubDate></item><item><title>Armbian Cinnamon without start button</title><link>https://forum.armbian.com/topic/56271-armbian-cinnamon-without-start-button/</link><description><![CDATA[<p>
	Hi All,
</p>

<p>
	 
</p>

<p>
	I'm struggling with my Orange PI 5 Plus and various Armbian Flavors for 3 days.
</p>

<p>
	 
</p>

<p>
	My Preferred DE, Armbian_25.8.1_Orangepi5-plus_noble_vendor_6.1.115_kde-neon_desktop, after all setup on second boot... failed msg: wait until boot finishes...
</p>

<p>
	 
</p>

<p>
	XFCE, Sound does not work over HDMI.
</p>

<p>
	 
</p>

<p>
	Finally, Armbian_25.8.1_Orangepi5-plus_trixie_vendor_6.1.115_cinnamon_desktop, is doing well. 
</p>

<p>
	Except for, I'm missing start button.  If I want Firefox, I have to open it via<span></span><span></span> cmd If I want to capture screen... I dont know even the name to call via cmd...
</p>

<p>
	 
</p>

<p>
	See my Phone shot 
</p>

<p>
	<span></span><a href="https://drive.google.com/file/d/1d6K4i_yshHCrKvXR-13VFkpWzPKx8GaA/view?usp=sharing" rel="external nofollow">https://drive.google.com/file/d/1d6K4i_yshHCrKvXR-13VFkpWzPKx8GaA/view?usp=sharing</a><span></span>
</p>

<p>
	 
</p>

<p>
	Could somebody tell me what is wrong?
</p>

<p>
	 
</p>

<p>
	Thanks,
</p>

<p>
	 
</p>

<p>
	 
</p>
]]></description><guid isPermaLink="false">56271</guid><pubDate>Tue, 18 Nov 2025 05:57:12 +0000</pubDate></item><item><title>rock64: "Wrong Ramdisk Image Format" after upgrade to 6.12.9</title><link>https://forum.armbian.com/topic/49358-rock64-wrong-ramdisk-image-format-after-upgrade-to-6129/</link><description><![CDATA[<p>
	Hello,
</p>

<p>
	 
</p>

<p>
	While upgrading my rock64 today, my Linux kernel was upgraded from 6.6.32 to 6.12.9.
</p>

<p>
	After rebooting, the board refused to boot:
</p>

<pre class="ipsCode">Boot script loaded from usb 0                                               |
166 bytes read in 407 ms (0 Bytes/s)                                        |
26129699 bytes read in 1634 ms (15.3 MiB/s)                                 |
36473344 bytes read in 48420 ms (735.4 KiB/s)                               |
54333 bytes read in 826 ms (63.5 KiB/s)                                     |
2825 bytes read in 1653 ms (1000 Bytes/s)                                   |
Applying kernel provided DT fixup script (rockchip-fixup.scr)               |
## Executing script at 09000000                                             |
Unknown command 'kaslrseed' - try 'help'                                    |
Wrong Ramdisk Image Format                                                  |
Ramdisk image is corrupt or invalid                                         |
</pre>

<p>
	 
</p>

<p>
	I tried to manually copy the /boot files from the latest image, but the result was the same.
</p>

<p>
	I was able to recover it by copying the /boot files from an image from the archive (I used Armbian_23.11.1_Rock64_bookworm_current_6.1.63.img.xz), then once booted I used armbian-config to install 6.6.63 which also works fine.
</p>

<p>
	 
</p>

<p>
	I'm just wondering if anyone else noticed the same issue with the 6.12.9 kernel (I did a quick search but I didn't find anything similar recently - sorry if I missed it) or if it's only for me?
</p>
]]></description><guid isPermaLink="false">49358</guid><pubDate>Fri, 17 Jan 2025 16:14:18 +0000</pubDate></item><item><title>Armsom cm5, onboard USB hub is disconnected when booting</title><link>https://forum.armbian.com/topic/57414-armsom-cm5-onboard-usb-hub-is-disconnected-when-booting/</link><description><![CDATA[<p>
	Hello Dear,
</p>

<p>
	 
</p>

<p>
	After flashing <strong>*Armsom-cm5-<abbr title="Raspberry Pi"><abbr title="Raspberry Pi">rpi</abbr></abbr>-cm4-io_*</strong>, there is one critical problem.<br />
	<strong>onboard USB hub always connects and disconnects 2 times when booting</strong>.
</p>

<p>
	<strong>dmesg outputs</strong><span>:</span>
</p>

<pre class="ipsCode">[ 6.190239] hub 1-1:1.0: USB hub found
…
[ 7.868081] rk-pcie 2a200000.pcie: PCIe Link Fail, LTSSM is 0x3, hw_retries=0
[ 7.868642] usb 1-1: USB disconnect, device number 2
…
[ 9.326443] hub 1-1:1.0: USB hub found
…
[ 11.213062] rk-pcie 2a200000.pcie: PCIe Link Fail, LTSSM is 0x3, hw_retries=1
[ 11.213297] usb 1-1: USB disconnect, device number 4</pre>

<p>
	I have tried with many variations, but the onboard hub is always disconnected.
</p>

<ul>
	<li>
		server/desktop
	</li>
	<li>
		community release/ self build
	</li>
	<li>
		several tags from 25.5 to 26.2
	</li>
	<li>
		CONFIG_USB_ONBOARD_HUB  O/X
	</li>
	<li>
		<abbr title="Raspberry Pi"><abbr title="Raspberry Pi">rpi</abbr></abbr> cm4 io board/ Ochin board
	</li>
</ul>

<p>
	However,
</p>

<ul>
	<li>
		Armsom's official image has no problem with the onboard usb hub.
	</li>
	<li>
		CM4-nano-B has no onboard hub, and has no problem with external hub.
	</li>
</ul>

<p>
	So, it<strong> seems to be a SW problem</strong>.
</p>

<p>
	 
</p>

<p>
	Please review this problem.
</p>

<p>
	Thanks.
</p>
]]></description><guid isPermaLink="false">57414</guid><pubDate>Fri, 16 Jan 2026 12:06:34 +0000</pubDate></item><item><title>Armbian updates crashes boot</title><link>https://forum.armbian.com/topic/56961-armbian-updates-crashes-boot/</link><description><![CDATA[<p>
	Hi all! <br />
	<br />
	I have Armbian installed on a rock 4SE (Tagged as 4B as it uses the same image i believe) as the base for an OpenMediaVault. Yesterday i installed the latest version of Bookworm, as i am running OMV7 and that, as far as i can tell, does not work on Trixie. I am not ready to upgrade to Trixie/OMV8, as im not sure there is support for my Penta sata hat yet. <br />
	<br />
	My issue is that if i install the updates, either through OMV interface, or apt, the device does not boot after applying the updates. As far as i can tell from logs etc. something is either wrong with loading the kernel image on boot, or with the image itself. <br />
	If i install Armbian, and then OMV, everything works just fine, i just have 132 pending updates. Including a kernel update that takes the version from 6.1.63, to 6.12.58. <br />
	Have anyone had any similar issues, or any potential solutions? <br />
	<br />
	I can tell that it installed the updates by itself during the night, and is currently waiting for a reboot. And im a but scared to reboot it, since it might not boot correctly. <br />
	<br />
	Thanks in advance!
</p>
]]></description><guid isPermaLink="false">56961</guid><pubDate>Sat, 27 Dec 2025 09:38:15 +0000</pubDate></item><item><title>Helios64 - Armbian 23.08 Bookworm issues (solved)</title><link>https://forum.armbian.com/topic/30074-helios64-armbian-2308-bookworm-issues-solved/</link><description><![CDATA[<p>
	A stable Armbian Bookworm configuration for your Helios64 is provided <a href="https://forum.armbian.com/topic/30074-helios64-armbian-2308-bookworm-issues-solved/page/8/#comment-191029" rel="">here</a> (solved).
</p>

<p>
	*************************************************************************
</p>

<p>
	 
</p>

<p>
	Recently a new Armbian 23.08.1 Bookworm image with linux-6.1.50 was made available for Helios64 on its download page (see <a href="http://armbian.com/helios64" rel="external nofollow">here</a>) - which is as such great <span class="ipsEmoji">😀</span>.
</p>

<p>
	 
</p>

<p>
	Everything  starts up nicely, but unlike the previous Bookworm 23.05 image, the current one has an issue with accessing USB devices. In the boot process the following error occurs: 
</p>

<p>
	 
</p>

<pre class="ipsCode prettyprint lang-html prettyprinted"><span class="pln"># cat /var/log/syslog | grep error
2023-09-07T12:31:05.671598+02:00 helios64 kernel: [    2.537009] dwc3 fe900000.usb: error -ETIMEDOUT: failed to initialize core
2023-09-07T12:31:05.671602+02:00 helios64 kernel: [    2.537107] dwc3: probe of fe900000.usb failed with error -110</span></pre>

<p>
	 
</p>

<p>
	No USB device could be accessed.
</p>

<p>
	 
</p>

<p>
	As this seems to be related to the realtek driver r8152, I compiled and installed the current version of that driver (see below) and after that the USB devices were accessible.
</p>

<p>
	 
</p>

<pre class="ipsCode prettyprint lang-html prettyprinted"><span class="pln"># compile and install the current realtek driver
git clone https://github.com/wget/realtek-r8152-linux.git
cd realtek-r8152-linux...
make 
sudo make install</span></pre>
]]></description><guid isPermaLink="false">30074</guid><pubDate>Thu, 07 Sep 2023 11:16:25 +0000</pubDate></item><item><title>Bigtreetech CB2 and Pi 2 support</title><link>https://forum.armbian.com/topic/38873-bigtreetech-cb2-and-pi-2-support/</link><description><![CDATA[<p>
	<a href="https://biqu.equipment/products/bigtreetech-pi-2-cb2" rel="external nofollow">Bigtreetech CB2 and Pi 2</a> released somewhat recently (April 20th). They use RK3566 and have a lot of nice features. The board and module are intended for 3d printer use but can be used just like any other pi. There is an official linux image on <a href="https://github.com/bigtreetech/CB2/releases" rel="external nofollow">bigtreetech github</a>, and it seems it's a slightly customized armbian. I propose copying that configuration and adding it as a supported board.
</p>

<p>
	 
</p>

<p>
	This is a bit of a personal tangent, but I was also thinking of how I can submit the device tree files to the mainline linux kernel, would that be a good idea? I'm planning to use or at least try Alpine on the board and it would be nice to have the needed files in the linux package already.
</p>
]]></description><guid isPermaLink="false">38873</guid><pubDate>Wed, 08 May 2024 10:31:25 +0000</pubDate></item><item><title>Orange pi 5B - install to emmc doesnt work anymore. Armbian-install behaves oddly</title><link>https://forum.armbian.com/topic/46914-orange-pi-5b-install-to-emmc-doesnt-work-anymore-armbian-install-behaves-oddly/</link><description><![CDATA[<p>
	I have attempted this with the vendor kernels and the mainline kernels, and they both do the same thing. The vendor kernel cannot see the <abbr title="embedded MultiMediaCard"><abbr title="embedded MultiMediaCard">EMMC</abbr></abbr> at all after running updates on it. So that version would kill itself when updated even if it did install and boot off the <abbr title="embedded MultiMediaCard"><abbr title="embedded MultiMediaCard">emmc</abbr></abbr>. The wifi also doesnt work on the mainline, so the options are mainline with no wifi or vendor with no <abbr title="embedded MultiMediaCard"><abbr title="embedded MultiMediaCard">emmc</abbr></abbr>.<br />
	<br />
	<br />
	Install to SD card --&gt; to through setup wizard --&gt; change firmware to 5b instead of 5.--&gt;  reboot --&gt; armbian-install --&gt; boot from <abbr title="embedded MultiMediaCard"><abbr title="embedded MultiMediaCard">emmc</abbr></abbr>, system on <abbr title="embedded MultiMediaCard"><abbr title="embedded MultiMediaCard">emmc</abbr></abbr> ---&gt; spends a long time on counting files ---&gt; file transfer screen flashes by in 1 second. --&gt; shutdown ---&gt; boot from <abbr title="embedded MultiMediaCard"><abbr title="embedded MultiMediaCard">emmc</abbr></abbr>. ---&gt; completely dead, the lights on the board never even flash green like they do with an SD inserted<br />
	<br />
	This has worked in the past, many many versions ago, but it did not do this when it worked "spends a long time on counting files ---&gt; file transfer screen flashes by in 1 second"<br />
	<br />
	Files appear to be there though when mounting the filesystem. Correct uuids in the armbianEnv and fstab<br />
	<br />
	I also attempted to just burn it from the sd to the <abbr title="embedded MultiMediaCard"><abbr title="embedded MultiMediaCard">emmc</abbr></abbr> with dd, but that also didnt work<br />
	<br />
	How can I load a current version of amrbian onto my <abbr title="embedded MultiMediaCard"><abbr title="embedded MultiMediaCard">emmc</abbr></abbr> for the orange pi 5b?
</p>
]]></description><guid isPermaLink="false">46914</guid><pubDate>Tue, 05 Nov 2024 15:46:04 +0000</pubDate></item><item><title>Helios64 - Unable to transfer install from eMMC to SDCard</title><link>https://forum.armbian.com/topic/56982-helios64-unable-to-transfer-install-from-emmc-to-sdcard/</link><description><![CDATA[<p>
	Hi all,
</p>

<p>
	 
</p>

<p>
	I am unable to login to OMV on my Helios64. A bit of sleuthing indicates that this is because the / fs is at 100% capacity. At first, I figured I'll just transfer the system install from the 8GB SD Card I started with to the 16GB internal <abbr title="embedded MultiMediaCard">eMMC</abbr>. Turns out past unfnknblvbl already did that, and now I need to go the other way. 
</p>

<p>
	 
</p>

<p>
	The documentation on the old Kobol site isn't entirely accurate about how to do this. My SDCard is /dev/mmcblk1 and even though it's formatted ext4, it simply doesn't show in armbian-config. In fact, the only device that shows in the Install menu is /dev/md127, which is the RAID array itself. I'd rather not be booting from that for obvious reasons.<br />
	<br />
	Assuming that I'm a bit of a Linux noob (I know just enough to be dangerous), is anyone able to tell me what am I doing wrong?<br />
	<br />
	Thanks! <span class="ipsEmoji">😃</span>
</p>
]]></description><guid isPermaLink="false">56982</guid><pubDate>Sun, 28 Dec 2025 12:21:08 +0000</pubDate></item><item><title>NPU and RKLLM support on Rockchip RK3588 (NanoPC-T6) and RK3576 (NanoPi M5)</title><link>https://forum.armbian.com/topic/56993-npu-and-rkllm-support-on-rockchip-rk3588-nanopc-t6-and-rk3576-nanopi-m5/</link><description><![CDATA[<p>
	Hello,
</p>

<p>
	I am currently working on a project involving local LLM inference on Rockchip SoCs using the rknn-llm framework. I have two specific questions regarding Armbian support for the NPU:<br />
	 1. NanoPi M5 (RK3576): FriendlyElec recently released the NanoPi M5 based on the RK3576. If I use the Armbian image for this board, will I be able to run LLM models using the NPU? I am considering purchasing this board for LLM<br />
	    testing and would like to know if the driver support is already there.<br />
	 2. NanoPC-T6 (RK3588): I have a NanoPC-T6 running Armbian, but I cannot find the /dev/rknpu device node. I have tested this with both 6.1.115-vendor-rk35xx and 6.12.58-current-rockchip64 kernels, but the NPU device is not appearing.<br />
	    Is there a specific overlay or a manual configuration step needed to enable NPU support on these kernels?<br />
	 tried adding tags npu and nanopi m5, but there was no such option.<br />
	I am happy to provide any additional information, logs (such as `armbianmonitor -u`), or command outputs if needed to help diagnose the issue.<br />
	Thank you in advance for your help and guidance!<br />
	<br />
	Best regards,<br />
	A.H.<br />
	 
</p>
]]></description><guid isPermaLink="false">56993</guid><pubDate>Sun, 28 Dec 2025 20:44:40 +0000</pubDate></item><item><title>Rockpi 4B Networking issues</title><link>https://forum.armbian.com/topic/56648-rockpi-4b-networking-issues/</link><description><![CDATA[<p>
	Hi,
</p>

<p>
	I am posting this here to notify you about the serious networking performance issue on my Rockpi 4B board. Ever since I installed the Trixie release, the networking on the board has been poor/not working at all. I cannot even run an <strong>apt update</strong>
</p>

<p>
	 
</p>

<p>
	If I try to connect via SSH, I get<span>:</span><br />
	 
</p>

<pre class="ipsCode prettyprint lang-html prettyprinted"><span class="pln">root@rockpi:~# apt update
0% [Connected to github.armbian.com (185.199.110.153)] [Waiting for headers] [Waiting for headers]client_loop: send disconnect: Connection reset

&gt;ssh root@192.168.0.200
ssh_dispatch_run_fatal: Connection to 192.168.0.206 port 22: Connection timed out</span></pre>

<p>
	 
</p>

<p>
	I don't know where to start / what to check here. When I turn on the board, it works barely at starting, very slowly before becoming unresponsive.
</p>

<p>
	 
</p>

<p>
	<strong>Technical Details:</strong>
</p>

<pre class="ipsCode prettyprint lang-html prettyprinted"><span class="pln">Board: Rockpi 4B
Armbian version: Armbian_community_26.2.0-trunk.44_Rockpi-4b_trixie_current_6.12.60_minimal
Boot media: 250GB M.2 PCIE SSD

Old Working: Armbian_community_25.2.0-trunk.195_Rockpi-4b_bookworm_current_6.6.66_minimal</span></pre>

<p>
	This issue started only after installing the Trixie images. The bookworm image works butter smooth and flawless.
</p>

<p>
	 
</p>

<p>
	I am sorry if I am cross-posting this, but I couldn't find any known related issue on this board. Thanks in advance!
</p>
]]></description><guid isPermaLink="false">56648</guid><pubDate>Tue, 09 Dec 2025 16:18:42 +0000</pubDate></item><item><title>Rockchip MPP drivers Takedown</title><link>https://forum.armbian.com/topic/56947-rockchip-mpp-drivers-takedown/</link><description><![CDATA[<p>
	I was working with OpenHD when it was taken down by GitHub.<br />
	There's something we should be concerned about here in the rockchip section of armbian?<br />
	Original Post:<br />
	<a href="https://github.com/github/dmca/blob/master/2025/12/2025-12-18-ffmpeg.md" rel="external nofollow">https://github.com/github/dmca/blob/master/2025/12/2025-12-18-ffmpeg.md</a><br />
	 
</p>

<p>
	Identify only the specific file URLs within the repository that is infringing:
</p>

<p>
	<a href="https://github.com/rockchip-linux/mpp/blob/develop/mpp/codec/dec/av1/av1d_codec.h" rel="external nofollow">https://github.com/rockchip-linux/mpp/blob/develop/mpp/codec/dec/av1/av1d_codec.h</a><br />
	<a href="https://github.com/rockchip-linux/mpp/blob/develop/mpp/codec/dec/av1/av1d_cbs.c" rel="external nofollow">https://github.com/rockchip-linux/mpp/blob/develop/mpp/codec/dec/av1/av1d_cbs.c</a><br />
	<a href="https://github.com/rockchip-linux/mpp/blob/develop/mpp/codec/dec/av1/av1d_cbs.h" rel="external nofollow">https://github.com/rockchip-linux/mpp/blob/develop/mpp/codec/dec/av1/av1d_cbs.h</a><br />
	<a href="https://github.com/rockchip-linux/mpp/blob/develop/mpp/codec/dec/av1/av1d_parser2_syntax.c" rel="external nofollow">https://github.com/rockchip-linux/mpp/blob/develop/mpp/codec/dec/av1/av1d_parser2_syntax.c</a><br />
	<a href="https://github.com/rockchip-linux/mpp/blob/develop/mpp/codec/dec/h265/h265d_codec.h" rel="external nofollow">https://github.com/rockchip-linux/mpp/blob/develop/mpp/codec/dec/h265/h265d_codec.h</a><br />
	<a href="https://github.com/rockchip-linux/mpp/blob/develop/mpp/codec/dec/h265/h265d_parser.c" rel="external nofollow">https://github.com/rockchip-linux/mpp/blob/develop/mpp/codec/dec/h265/h265d_parser.c</a><br />
	<a href="https://github.com/rockchip-linux/mpp/blob/develop/mpp/codec/dec/h265/h265d_ps.c" rel="external nofollow">https://github.com/rockchip-linux/mpp/blob/develop/mpp/codec/dec/h265/h265d_ps.c</a><br />
	<a href="https://github.com/rockchip-linux/mpp/blob/develop/mpp/codec/dec/vp9/vp9d_codec.h" rel="external nofollow">https://github.com/rockchip-linux/mpp/blob/develop/mpp/codec/dec/vp9/vp9d_codec.h</a><br />
	<a href="https://github.com/rockchip-linux/mpp/blob/develop/mpp/codec/dec/vp9/vp9d_parser.c" rel="external nofollow">https://github.com/rockchip-linux/mpp/blob/develop/mpp/codec/dec/vp9/vp9d_parser.c</a><br />
	<a href="https://github.com/rockchip-linux/mpp/blob/develop/mpp/codec/dec/vp9/vp9data.h" rel="external nofollow">https://github.com/rockchip-linux/mpp/blob/develop/mpp/codec/dec/vp9/vp9data.h</a><br />
	<a href="https://github.com/rockchip-linux/mpp/blob/develop/mpp/codec/dec/vp9/vpx_rac.c" rel="external nofollow">https://github.com/rockchip-linux/mpp/blob/develop/mpp/codec/dec/vp9/vpx_rac.c</a><br />
	<a href="https://github.com/rockchip-linux/mpp/blob/develop/mpp/codec/dec/vp9/vpx_rac.h" rel="external nofollow">https://github.com/rockchip-linux/mpp/blob/develop/mpp/codec/dec/vp9/vpx_rac.h</a>
</p>

<p>
	 
</p>
]]></description><guid isPermaLink="false">56947</guid><pubDate>Fri, 26 Dec 2025 17:29:00 +0000</pubDate></item><item><title>Odroid M1S Image Planned ?</title><link>https://forum.armbian.com/topic/33242-odroid-m1s-image-planned/</link><description><![CDATA[<p>
	Hello!
</p>

<p>
	 
</p>

<p>
	Just wondered if an armbian image was planned for the Odroid M1S?
</p>

<p>
	 
</p>

<p>
	Thank you in advance!
</p>
]]></description><guid isPermaLink="false">33242</guid><pubDate>Mon, 15 Jan 2024 15:31:00 +0000</pubDate></item><item><title>orange pi 3b</title><link>https://forum.armbian.com/topic/56832-orange-pi-3b/</link><description><![CDATA[<p>
	I can't access the download links on the Armbian website; they appear blank and no downloads are available. Please help.
</p>
]]></description><guid isPermaLink="false">56832</guid><pubDate>Sun, 21 Dec 2025 11:52:13 +0000</pubDate></item><item><title>No post after upgraded to 26.2.0-trunk.62</title><link>https://forum.armbian.com/topic/56661-no-post-after-upgraded-to-2620-trunk62/</link><description><![CDATA[<p>
	Hello fellow geeks/nerds,
</p>

<p>
	 
</p>

<p>
	Here still using a Rock Pi 4c on 26.2.0-trunk.44. After upgrading to 26.2.0-trunk.62 the Rockpi just does not come back. No display no network. Wish I could provide more details beside the versions. I've went ahead and froze the kernel updates. If there's a way to maybe pull a log of sorts please let me know and I'll post it.
</p>
]]></description><guid isPermaLink="false">56661</guid><pubDate>Wed, 10 Dec 2025 09:35:03 +0000</pubDate></item><item><title>Rock 3B armbian</title><link>https://forum.armbian.com/topic/49175-rock-3b-armbian/</link><description><![CDATA[<p>
	Hey everyone, was wondering if there was a readily available rock3b armbian image. I have found that the rock3a/3b are quite similar baring an extra ethernet port. So was hoping to see if I could take the rock3a image and make some simple modifications but don't know how. Any help would be appreciated thanks.
</p>
]]></description><guid isPermaLink="false">49175</guid><pubDate>Tue, 07 Jan 2025 14:40:46 +0000</pubDate></item><item><title>cm3588 nas - rtc device</title><link>https://forum.armbian.com/topic/56313-cm3588-nas-rtc-device/</link><description><![CDATA[<p>
	Just an information about the `<strong>edge</strong>` kernel (<strong>6.18</strong>) when used on the <strong>cm3588-nas</strong> system.
</p>

<p>
	 
</p>

<p>
	The rtc driver is <strong>not</strong> initialized on a `<strong>poweron</strong>`.
</p>

<p>
	 
</p>

<p>
	After a poweron, you will see the following in the log.
</p>

<pre class="ipsCode">Nov 11 01:17:10 uhutest kernel: rtc-hym8563 6-0051: could not init device, -6
Nov 11 01:17:10 uhutest systemd[1]: System time advanced to built-in epoch: Tue 2025-11-11 01:17:09 CET</pre>

<p>
	 
</p>

<p>
	If you have `fake-hwclock` running, you will see the following a moment later. fake-hwclock restores the time, but the service will not properly start, because of the rtc device error.
</p>

<pre class="ipsCode">Nov 11 01:17:12 uhutest fake-hwclock.sh[461]: Restoring saved system time
Nov 20 13:22:43 uhutest fake-hwclock.sh[466]: Thu Nov 20 01:22:43 PM CET 2025
Nov 20 13:22:43 uhutest fake-hwclock.sh[468]: hwclock: Cannot access the Hardware Clock via any known method.
Nov 20 13:22:43 uhutest fake-hwclock.sh[468]: hwclock: Use the --verbose option to see the details of our search for an access method.
Nov 20 13:22:43 uhutest systemd[1]: fake-hwclock.service: Main process exited, code=exited, status=1/FAILURE
Nov 20 13:22:43 uhutest systemd[1]: fake-hwclock.service: Failed with result 'exit-code'.
Nov 20 13:22:43 uhutest systemd[1]: Failed to start Restore system time on boot and save it on shutdown.
</pre>

<p>
	 
</p>

<p>
	You would need to restart the fake-hwclock service, if you want that it saves time before the next restart.
</p>

<p>
	 
</p>

<p>
	If you do a `restart` of the system, the rtc device will get properly initialized and time is good. Following is seen in the logs.
</p>

<pre class="ipsCode">Nov 20 13:26:14 uhutest kernel: rtc-hym8563 6-0051: registered as rtc0
Nov 20 13:26:14 uhutest kernel: rtc-hym8563 6-0051: setting system clock to 2025-11-20T12:26:11 UTC (1763641571)

Nov 20 13:26:16 uhutest fake-hwclock.sh[455]: Not restoring old system time
</pre>

<p>
	 
</p>

<p>
	I have seen the issue right now only with the 6-18-<abbr title="Release candidate"><abbr title="Release candidate">RC</abbr></abbr> kernel. The following patch mentioned here works as a pure workaround. <a href="https://patchwork.kernel.org/project/linux-rockchip/patch/20220608161150.58919-2-linux@fw-web.de/" rel="external nofollow">https://patchwork.kernel.org/project/linux-rockchip/patch/20220608161150.58919-2-linux@fw-web.de/</a>
</p>

<p>
	Lets see how the development of kernel 6.18 goes and if the final version will not have this issue.
</p>
]]></description><guid isPermaLink="false">56313</guid><pubDate>Fri, 21 Nov 2025 11:08:37 +0000</pubDate></item><item><title>Orangepi CM5 support</title><link>https://forum.armbian.com/topic/56725-orangepi-cm5-support/</link><description><![CDATA[<p>
	Is there a specific reason why <a href="http://www.orangepi.org/html/hardWare/computerAndMicrocontrollers/details/Orange-Pi-CM5.html" rel="external nofollow">orangepi cm5</a> isn't supported? Or is it simply because nobody has contributed? Because I am willing to add support for it if there aren't any serious issues when building armbian for this board. The <a href="https://www.armbian.com/cf7stdb-entries/orangepi-cm5/" rel="external nofollow">webpage for the board</a> is currently empty.
</p>

<p>
	 
</p>

<p>
	I see two issues when using Armbian on orangepi cm5:
</p>

<p>
	1. The ethernet and the fan won't work. There is a <a href="https://lists.freedesktop.org/archives/dri-devel/2025-October/528656.html" rel="external nofollow">device tree published by Laurent Pinchart</a> that may fix this.
</p>

<p>
	2. armbian-install bricks the board. The only way to recover the device is by enabling maskrom and using rkdeveloptool to flash a new image.
</p>

<p>
	 
</p>

<p>
	Other than these Armbian seems to work fine on orangepi cm5.
</p>

<p>
	 
</p>

<p>
	Has anyone tried using (and also installing) armbian on this board?
</p>
]]></description><guid isPermaLink="false">56725</guid><pubDate>Sun, 14 Dec 2025 19:03:56 +0000</pubDate></item><item><title>Home Assistant Supervisor fails after Docker/Kernel upgrade</title><link>https://forum.armbian.com/topic/56704-home-assistant-supervisor-fails-after-dockerkernel-upgrade/</link><description><![CDATA[<p>
	Hey there!
</p>

<p>
	 
</p>

<p>
	I’ve been running Home Assistant Supervised on Armbian for a while, but lately I keep seeing a repeat issue after system upgrades (Docker or kernel updates).<br />
	<br />
	After upgrading, some HA containers stop unexpectedly, for example:
</p>

<ul>
	<li>
		odroid-c2-homeassistant:2025.12.2 exits with code 137
	</li>
	<li>
		aarch64-addon-configurator:5.8.0 exits with code 143
	</li>
</ul>

<p>
	 
</p>

<p>
	My current setup runs on Helios64/RK3399 · kernel 6.12.58-current-rockchip64 · Docker CE 29.1.3 (f52814d).
</p>

<p>
	 
</p>

<p>
	After digging a bit, I noticed this line in dmesg right after the failures -&gt; apparmor="DENIED" operation="signal" profile="hassio-supervisor" signal=kill
</p>

<p>
	I also found the small watchdog script (supervisor_fix.sh) that restarts the Supervisor when it reports unhealthy, but the upgrade breakage seems to slip through.
</p>

<p>
	 
</p>

<p>
	I’m just thinking out loud here, but maybe something like a post-upgrade AppArmor refresh, or some other small adjustment, could help ?<br />
	Not sure what makes the most sense, so any input would be really appreciated.
</p>

<p>
	 
</p>

<p>
	Thanks for your time and for all the work you put into Armbian!
</p>

<p>
	 
</p>
]]></description><guid isPermaLink="false">56704</guid><pubDate>Sat, 13 Dec 2025 11:42:38 +0000</pubDate></item><item><title>Orange Pi 5 Max SD card booting issue, system normally starts from NVME SSD</title><link>https://forum.armbian.com/topic/51994-orange-pi-5-max-sd-card-booting-issue-system-normally-starts-from-nvme-ssd/</link><description><![CDATA[<p>
	Hi.
</p>

<p>
	I've got a strange issue. When Orange Pi 5 Max was unavailable I installed version for Orange Pi 5 Pro from SD card to NVME SSD. It worked fine Now I decided for fresh install of Armbian dedicated to Max board but I can't boot from SD card.
</p>

<p>
	 
</p>

<p>
	I used exactly the same card and the same power supply as when I installed armbian originally, but when I insert SD card, led goes blue and system is not booting. I don't have any signal on HDMI - monitor goes sleep. When I remove SD card - system boots from SSD and all is working. I removed SSD but system still can't boot from SD card.
</p>

<p>
	 
</p>

<p>
	Do you know any method to boot from SD card or install armbian image in other way? For now I'm considering buying nvme usb case and clonning img directly to ssd but I'd like to avoid that as I don't know if that will work.
</p>
]]></description><guid isPermaLink="false">51994</guid><pubDate>Sat, 17 May 2025 22:55:06 +0000</pubDate></item><item><title>Radxa Rock 2F  bookworm minimal problems</title><link>https://forum.armbian.com/topic/50185-radxa-rock-2f-bookworm-minimal-problems/</link><description><![CDATA[<p>
	I have been trying to run the bookworm minimal image for the Radxa Rock 2F with poor results. Wifi stops working after an "armbian-upgrade" and after apt upgrade.  Doing an nmcli -p r results in WIFI-HW missing response. It seems to me that after the upgrade, something is wrong with the aic8800 driver module. Unfortunately I am too ignorant to be of much help, but any suggestions would be most  welcome.
</p>

<p>
	 
</p>

<p>
	Thank you.
</p>
]]></description><guid isPermaLink="false">50185</guid><pubDate>Sun, 02 Mar 2025 01:11:52 +0000</pubDate></item><item><title><![CDATA[Radxa rock-3c stuck at login & no hdmi]]></title><link>https://forum.armbian.com/topic/56375-radxa-rock-3c-stuck-at-login-no-hdmi/</link><description><![CDATA[<p>
	Hello, I just flashed the latest minimal img  from the github releases (Armbian_community_26.2.0-trunk.7_Rock-3c_trixie_current_6.12.58_minimal.img.xz) but I see no output on hdmi and it gets stuck at login, nothing I type works.
</p>

<p><a href="https://forum.armbian.com/uploads/monthly_2025_11/Screenshot2025-11-24234231.png.c450c4b9fcb66d9cca3965108690f1b4.png" class="ipsAttachLink ipsAttachLink_image" ><img data-fileid="15513" src="https://forum.armbian.com/uploads/monthly_2025_11/Screenshot2025-11-24234231.thumb.png.6162dd892efab5091b316ee9f4695fa0.png" data-ratio="77.4" width="1000" class="ipsImage ipsImage_thumbnailed" alt="Screenshot 2025-11-24 234231.png"></a></p>]]></description><guid isPermaLink="false">56375</guid><pubDate>Mon, 24 Nov 2025 21:46:14 +0000</pubDate></item><item><title>Hard Brick After Failed Armbian Upgrade (Jammy to Noble)</title><link>https://forum.armbian.com/topic/56595-hard-brick-after-failed-armbian-upgrade-jammy-to-noble/</link><description><![CDATA[<p>
	Subject: [R58X] Hard Brick After Failed Armbian Upgrade (Jammy to Noble)
</p>

<p>
	 
</p>

<p>
	Hello,
</p>

<p>
	 
</p>

<p>
	My Mekotronics R58X running Armbian Ubuntu 22.04 (Jammy) hard-bricked after a failed attempt to upgrade to Ubuntu 24.04 (Noble).
</p>

<p>
	Initial Failure: The upgrade crashed, and the device would not boot/log in properly .
</p>

<p>
	 
</p>

<p>
	Recovery Attempt: I successfully flashed a new Ubuntu 24.04 image using the official Mekotronics documentation/tool.
</p>

<p>
	<img alt="image.png.ac9313816714a7b69156ab6acb4196c9.png" class="ipsImage ipsImage_thumbnailed" data-fileid="15586" data-ratio="46.97" width="973" src="https://forum.armbian.com/uploads/monthly_2025_12/image.png.ac9313816714a7b69156ab6acb4196c9.png" />
</p>

<p>
	 
</p>

<p>
	Current Status: After the flash completed successfully and the device went offline, it is now completely dead.
</p>

<p>
	It will not power on.
</p>

<p>
	No LED activity.
</p>

<p>
	I cannot enter recovery mode (Loader or MaskROM) using standard methods.
</p>

<p>
	It appears the device is hard-bricked, possibly due to bootloader corruption. Has anyone recovered an R58X from a similar state?
</p>

<p>
	 
</p>

<p>
	Thank you for your help.
</p>
]]></description><guid isPermaLink="false">56595</guid><pubDate>Fri, 05 Dec 2025 15:07:28 +0000</pubDate></item><item><title>BTRFS support on U-Boot</title><link>https://forum.armbian.com/topic/15930-btrfs-support-on-u-boot/</link><description><![CDATA[<p>
	Since there is a thread about adding ZFS support to the U-Boot build, I thought I'd post a similar request for btrfs.  I was looking through the helios u-boot repo a few days ago and noticed that it isn't built with btrfs support.  While I could make a separate ext4 /boot partition, it would be convenient to have the entire <abbr title="embedded MultiMediaCard">eMMC</abbr> formatted as btrfs.  This allows for me to make easy and fast backups using btrfs send/receive, and also allows for snapshotting prior to upgrades (via e.g. snapper), and rolling back to a different snapshot at boot.
</p>

<p>
	My turris onmia router uses u-boot with btrfs native root, and I've used the snapshot rollback support a couple of times.  They have a fancy snapshot selection that can be done via the reset button without a serial console, but just having the ability to select previous snapshots at the u-boot menu would be quite convenient.
</p>

<p>
	 
</p>

<p>
	I believe all that is needed is to enable CONFIG_CMD_BTRFS.  <a href="https://github.com/u-boot/u-boot/blob/832bfad7451e2e7bd23c96edff2be050905ac3f6/cmd/Kconfig#L2047" rel="external nofollow">https://github.com/u-boot/u-boot/blob/832bfad7451e2e7bd23c96edff2be050905ac3f6/cmd/Kconfig#L2047</a>
</p>

<p>
	 
</p>

<p>
	Thanks for your consideration!
</p>
]]></description><guid isPermaLink="false">15930</guid><pubDate>Fri, 13 Nov 2020 02:33:01 +0000</pubDate></item><item><title>Devterm a06 and kernel 6.x no video</title><link>https://forum.armbian.com/topic/42334-devterm-a06-and-kernel-6x-no-video/</link><description><![CDATA[<p>
	I have a Dev term a06 and have been having problems with the newer releases based on kernel 6.x. After booting one of these, the display does not have backlight or any text/image displayed.  On the last 5.x it boots and works fine. I have not yet tried the HDMI output on the 6.x versions, need to get an adapter, but I'm guessing that the built in display is not discovered. The Dev term does not normally have a serial port, I'd need to solder up an adapter, or I would have looked at it to see if anything was happening.
</p>

<p>
	 
</p>

<p>
	Any suggestions for a very basic Linux user to try? Especially something I can maybe edit after flashing (before first boot). I should be able to get a Linux image up on WSL if needed to read/write the card. I had Kali on WSL, but it broke during an update, but shouldn't be too hard to stand up a new VM.
</p>
]]></description><guid isPermaLink="false">42334</guid><pubDate>Thu, 11 Jul 2024 18:18:03 +0000</pubDate></item><item><title>trying to set up a open media vault server on my radxa 4d</title><link>https://forum.armbian.com/topic/56505-trying-to-set-up-a-open-media-vault-server-on-my-radxa-4d/</link><description><![CDATA[<p>
	hi, im trying to make my radxa 4d in to a open media vault server, iv down loaded the file from armbian's web side but it wont boot, pluging it in to one of my raspberry pi's and useing gparted, i can only see one partision for it and can view it, dose this need a boot loader?
</p>

<p>
	iv also tryed downloading Debian 14 (Forky) from the armbian web site and got that to boot, but the script from armbian-config is broken ( missing stuff like php) and iv tryed the script from open media vault but that errors with eth0 missing.
</p>

<p>
	do i need to  install a boot loader on the armbian open media vault image ?
</p>
]]></description><guid isPermaLink="false">56505</guid><pubDate>Sun, 30 Nov 2025 18:04:42 +0000</pubDate></item><item><title>Can't flash Armbian to EMMC on Orange Pi 5B</title><link>https://forum.armbian.com/topic/49309-cant-flash-armbian-to-emmc-on-orange-pi-5b/</link><description><![CDATA[<p>
	Hello everyone. I can't flash Armbian to <abbr title="embedded MultiMediaCard"><abbr title="embedded MultiMediaCard">EMMC</abbr></abbr> on the OrangePi 5B board. I made an SD card, booted, ran armbian-install, selected Boot from <abbr title="embedded MultiMediaCard"><abbr title="embedded MultiMediaCard">EMMC</abbr></abbr>/System on <abbr title="embedded MultiMediaCard"><abbr title="embedded MultiMediaCard">EMMC</abbr></abbr>, the recording process was successful, but after that the board stops booting at all. When I boot from the SD card again, I see that <abbr title="embedded MultiMediaCard"><abbr title="embedded MultiMediaCard">EMMC</abbr></abbr> is not a device in the system. There is no main mmcblk0, no mmcblk0boot0, no mmcblk0boot1.
</p>

<p>
	 
</p>

<p>
	I was able to get <abbr title="embedded MultiMediaCard"><abbr title="embedded MultiMediaCard">EMMC</abbr></abbr> back only after re-flashing the standard Android firmware using RKDevTool via maskrom. When I flash Android to <abbr title="embedded MultiMediaCard"><abbr title="embedded MultiMediaCard">EMMC</abbr></abbr> and then boot from the SD card with Armbian, /dev/mmcblk0, /dev/mmcblk0boot0 and /dev/mmcblk0boot1 are back in place.
</p>

<p>
	 
</p>

<p>
	Accordingly, I have some confusion:<br />
	1. Why, when booting from an SD card after flashing <abbr title="embedded MultiMediaCard"><abbr title="embedded MultiMediaCard">EMMC</abbr></abbr>, none of the three devices mmcblk0, mmcblk0boot0 and mmcblk0boot1 are visible? What can be flashed there so that it falls off completely?<br />
	2. Why, when processing armbian-install, the system does not boot and how can I flash Armbian to <abbr title="embedded MultiMediaCard"><abbr title="embedded MultiMediaCard">EMMC</abbr></abbr>?
</p>

<p>
	 
</p>

<p>
	I am using the image: Armbian_24.11.2_Orangepi5_bookworm_vendor_6.1.75_minimal.img.xz, I have previously tried others, including larger images with a graphical environment.<br />
	My board: Orange Pi 5B 16G/128G, revision 1.2. I have changed boards, tried three pieces.
</p>
]]></description><guid isPermaLink="false">49309</guid><pubDate>Wed, 15 Jan 2025 04:47:02 +0000</pubDate></item><item><title>Java always crash on OrangPi 5 pro</title><link>https://forum.armbian.com/topic/56488-java-always-crash-on-orangpi-5-pro/</link><description><![CDATA[
<div class="ipsMargin_top">
    
    
    <div class="cTemplateField">
        <span class="cTemplateField_label"></span>
        <span class="cTemplateField_value">Armbianmonitor: 
<div class='ipsType_break ipsContained'>
<a href='https://paste.armbian.com/eluboxafad' target='_blank'  rel="nofollow noreferrer">
	
		
			https://paste.armbian.com/eluboxafad
		
	
</a>
</div></span>
    </div>
    
    
</div><p>
	Orange Pi 5 pro,whith Armbian_community_26.2.0-trunk.7_Orangepi5pro_noble_vendor_6.1.115_gnome_desktop 。
</p>

<p>
	when I try to start Eclipse/idea/vscode or other JavaApp ,  java processes crash and  gets core dump every time, tested on Jdk 17,21 25 ,both openjdk and oracleJDK。
</p>

<p>
	 
</p>

<p>
	It seems there is a compatibility issue between the kernel and the JDK.
</p>

<p>
	How can I fix it? Or I have to wait kenel update?
</p>

<p>
	 
</p>

<p>
	 
</p>

<p>
	<strong>some error like </strong>
</p>

<p>
	Current thread (0x0000ffffa802b9b0):  JavaThread "main"             [_thread_in_vm, id=6202, stack(0x0000ffffaeb62000,0x0000ffffaed60000) (2040K)]
</p>

<p>
	Stack: [0x0000ffffaeb62000,0x0000ffffaed60000],  sp=0x0000ffffaed5ce40,  free space=2027k<br />
	Native frames: (J=compiled Java code, j=interpreted, Vv=VM code, C=native code)<br />
	V  [libjvm.so+0xddc444]  Symbol::as_C_string() const+0x14<br />
	V  [libjvm.so+0xbef608]  Method::print_external_name(outputStream*, Klass*, Symbol*, Symbol*)+0x40<br />
	V  [libjvm.so+0xb07e7c]  LinkResolver::resolve_method(LinkInfo const&amp;, Bytecodes::Code, JavaThread*)+0x154<br />
	V  [libjvm.so+0xb0a85c]  LinkResolver::linktime_resolve_virtual_method(LinkInfo const&amp;, JavaThread*)+0x3c<br />
	V  [libjvm.so+0xb0b204]  LinkResolver::resolve_virtual_call(CallInfo&amp;, Handle, Klass*, LinkInfo const&amp;, bool, JavaThread*)+0x3c<br />
	V  [libjvm.so+0xb0b3a0]  LinkResolver::resolve_invokevirtual(CallInfo&amp;, Handle, constantPoolHandle const&amp;, int, JavaThread*)+0xd4<br />
	V  [libjvm.so+0x887cd4]  InterpreterRuntime::resolve_invoke(JavaThread*, Bytecodes::Code)+0x250<br />
	V  [libjvm.so+0x887f80]  InterpreterRuntime::resolve_from_cache(JavaThread*, Bytecodes::Code)+0x3c<br />
	j  java.util.AbstractSet.removeAll(Ljava/util/Collection;)Z+8 java.base@25.0.1<br />
	j  org.eclipse.osgi.container.ModuleResolver$ResolveProcess.resolveRevisions(Ljava/util/List;ZLorg/eclipse/osgi/container/ModuleResolver$ResolveProcess$ResolveLogger;Ljava/util/Map;)V+424<br />
	j  org.eclipse.osgi.container.ModuleResolver$ResolveProcess.resolveRevisionsInBatch(Ljava/util/Collection;ZLorg/eclipse/osgi/container/ModuleResolver$ResolveProcess$ResolveLogger;Ljava/util/Map;)V+253<br />
	j  org.eclipse.osgi.container.ModuleResolver$ResolveProcess.resolve()Lorg/eclipse/osgi/container/ModuleResolutionReport;+307<br />
	j  org.eclipse.osgi.container.ModuleResolver.resolveDelta(Ljava/util/Collection;ZLjava/util/Collection;Ljava/util/Map;Lorg/eclipse/osgi/container/ModuleDatabase;)Lorg/eclipse/osgi/container/ModuleResolutionReport;+19<br />
	j  org.eclipse.osgi.container.ModuleContainer.resolveAndApply(Ljava/util/Collection;ZZLorg/eclipse/osgi/container/ModuleContainer$ResolutionLock$Permits;)Lorg/eclipse/osgi/report/resolution/ResolutionReport;+256<br />
	j  org.eclipse.osgi.container.ModuleContainer.resolve(Ljava/util/Collection;ZZ)Lorg/eclipse/osgi/report/resolution/ResolutionReport;+63<br />
	j  org.eclipse.osgi.container.ModuleContainer.refresh(Ljava/util/Collection;)Lorg/eclipse/osgi/report/resolution/ResolutionReport;+34<br />
	j  org.eclipse.osgi.storage.Storage.checkSystemBundle([Ljava/lang/String;)V+242<br />
	j  org.eclipse.osgi.storage.Storage.createStorage(Lorg/eclipse/osgi/internal/framework/EquinoxContainer;)Lorg/eclipse/osgi/storage/Storage;+17<br />
	j  org.eclipse.osgi.internal.framework.EquinoxContainer.&lt;init&gt;(Ljava/util/Map;Lorg/osgi/framework/connect/ModuleConnector;)V+146<br />
	j  org.eclipse.osgi.launch.Equinox.&lt;init&gt;(Ljava/util/Map;Lorg/osgi/framework/connect/ModuleConnector;)V+10<br />
	j  org.eclipse.osgi.launch.Equinox.&lt;init&gt;(Ljava/util/Map;)V+3
</p>

<p>
	 
</p>

<p>
	 
</p>
]]></description><guid isPermaLink="false">56488</guid><pubDate>Sat, 29 Nov 2025 13:55:20 +0000</pubDate></item><item><title>Helios64 download links all seem to lead nowhere</title><link>https://forum.armbian.com/topic/56384-helios64-download-links-all-seem-to-lead-nowhere/</link><description><![CDATA[<p>
	Trying to download new images off the Helios64 page but every link seems to lead nowhere:
</p>

<p>
	 
</p>

<pre class="ipsCode prettyprint lang-html prettyprinted"><span class="pln">This armbian.lv.auroradev.org page can’t be found
No webpage was found for the web address: https://armbian.lv.auroradev.org/dl/helios64/archive/Armbian_25.5.1_Helios64_bookworm_current_6.12.28_minimal.img.xz
HTTP ERROR 404</span></pre>

<p>
	Is there another place to get these?
</p>
]]></description><guid isPermaLink="false">56384</guid><pubDate>Tue, 25 Nov 2025 20:21:19 +0000</pubDate></item><item><title>Recent images not booting</title><link>https://forum.armbian.com/topic/56275-recent-images-not-booting/</link><description><![CDATA[<p>
	The first image that boots ok down the list of older images is Armbian_25.5.1_Nanopim4v2_bookworm_current_6.12.28_minimal.img.xz
</p>

<p>
	 
</p>

<p>
	Could not get those images to boot:
</p>

<p>
	Armbian_25.5.1_Nanopim4v2_trixie_current_6.12.32_minimal.img.xz
</p>

<p>
	Armbian_25.5.1_Nanopim4v2_noble_current_6.12.28_minimal.img.xz
</p>

<p>
	Armbian_25.8.1_Nanopim4v2_bookworm_current_6.12.41_minimal.img.xz
</p>

<p>
	 
</p>

<p>
	Anyway, I am happy using the one I found booting.
</p>

<p>
	 
</p>

<p>
	Thanks
</p>

<p>
	 
</p>

<p>
	 
</p>
]]></description><guid isPermaLink="false">56275</guid><pubDate>Tue, 18 Nov 2025 18:02:29 +0000</pubDate></item><item><title>NanoPC-T4, rk3399, after the update `efi_free_pool: illegal free 0x00000000f0f09040`</title><link>https://forum.armbian.com/topic/56252-nanopc-t4-rk3399-after-the-update-efi_free_pool-illegal-free-0x00000000f0f09040/</link><description><![CDATA[<p>
	Updating via `apt update &amp;&amp; apt upgrade` causes Armbian to fail to boot on the single-board computer. I'm attaching the UART logs in the file `failed_log.txt`.
</p>

<p>
	 
</p>

<pre class="ipsCode prettyprint lang-html prettyprinted"><span class="pln">Start-Date: 2025-11-13  04:45:12
Commandline: apt -y upgrade
Upgrade: armbian-bsp-cli-nanopct4-current:arm64 (25.11.0-trunk.146, 25.11.0-trunk.469), linux-dtb-current-rockchip64:arm64 (25.11.0-trunk.146, 25.11.0-trunk.469), linux-image-current-rockchip64:arm64 (25.11.0-trunk.146, 25.11.0-trunk.469), linux-u-boot-nanopct4-current:arm64 (25.11.0-trunk.146, 25.11.0-trunk.469), armbian-firmware:arm64 (25.11.0-trunk.146, 25.11.0-trunk.469)
End-Date: 2025-11-13  04:47:04</span></pre>

<p>
	 
</p>

<p>
	<strong>out:</strong>
</p>

<pre class="ipsCode prettyprint lang-html prettyprinted"><span class="pln">Starting kernel ...

efi_free_pool: illegal free 0x00000000f0f09040
"Synchronous Abort" handler, esr 0x96000004
elr: 00000000002856e4 lr : 00000000002702f0000000f3f9b2f0
x0 : dfb6333a7ba2b4b7 x1 : 00000000f3fba060
x2000000 x5 : dfb6333a7ba2b4b7
x6 : 00000000f0d07000 x7 : 00000000000ef98 x11: 00000000f1f0b5bc
x12: 000000000000ef98 x13: 000003f558a4 x17: 00000000d8136251
x18: 00000000f1f22d90 x19: 000000000000001 x23: 00000000f1f303c0
x24: 00000000f3fdcff0 x25: 00000000000000001 x29: 00000000f1f0b470

Code: eb04005f 54000061 5resetting ...</span></pre>

<p>
	 
</p>

<p>
	To reproduce the issue (~13.11.2025-16.11.2025), simply download and flash the current `Minimal/IOT for Armbian Linux v6.12 [Debian] Debian 12 (Bookworm)` images (`https://www.armbian.com/nanopc-t4/`) and run `apt update &amp; upgrade` on a running system, then reboot. After this, the system, regardless of whether the `SD card` or `<abbr title="embedded MultiMediaCard">EMMC</abbr>` is used, will enter an infinite boot loop (`out` and file `failed_out.txt`). Thank you.
</p>
<p>
<a class="ipsAttachLink" href="https://forum.armbian.com/applications/core/interface/file/attachment.php?id=15450&amp;key=58b09f670948452ef94c21a7cb9dd9d3" data-fileExt='txt' data-fileid='15450' data-filekey='58b09f670948452ef94c21a7cb9dd9d3'>failed_log.txt</a> 
<a class="ipsAttachLink" href="https://forum.armbian.com/applications/core/interface/file/attachment.php?id=15451&amp;key=6819bdc44195c3710a5760a463165c60" data-fileExt='txt' data-fileid='15451' data-filekey='6819bdc44195c3710a5760a463165c60'>armbian_release.txt</a> 
<a class="ipsAttachLink" href="https://forum.armbian.com/applications/core/interface/file/attachment.php?id=15452&amp;key=17ab80c703b8954a35723180259a1388" data-fileExt='txt' data-fileid='15452' data-filekey='17ab80c703b8954a35723180259a1388'>normal_log.txt</a></p>]]></description><guid isPermaLink="false">56252</guid><pubDate>Sun, 16 Nov 2025 19:07:42 +0000</pubDate></item><item><title>Luckfox Lyra zero W unable to boot with community mantained image</title><link>https://forum.armbian.com/topic/56085-luckfox-lyra-zero-w-unable-to-boot-with-community-mantained-image/</link><description><![CDATA[<p>
	Hello everyone!
</p>

<p>
	 
</p>

<p>
	Saw that some luckfox boards were getting supported and I was like: YES!!!
</p>

<p>
	Flashed an sd-card with the community image. Latest I could find is 25.11.0-trunk.413. And plonked in my working Luckfox Lyra Zero W and it failed to boot.
</p>

<p>
	 
</p>

<p>
	From what I gather there seems to be a missing partition called "misc" and I think it is expected about after the current unallocated 16MB(16,777,216 bytes).
</p>

<p>
	I tried creating a 4MB partition after the current unallocated space but it complained about something called "Magic" and my limited u-boot/rockchip/embedded linux experience made me get lost there.
</p>

<p>
	 
</p>

<p>
	This is the serial output: Where the "No misc partition" is where I began. My current board has buildroot flashed to the SPI and boots if i don't have any sd-card inserted.
</p>

<p>
	 
</p>

<pre class="ipsCode">DDR 0ac6b06a19 typ 24/11/13-17:22:47,fwver: v1.04
tREFI:4x, sr_idle:93, pd_idle:13
PHY drv:clk:40,ca:48,DQ:40,odt:240
vrefinner:50%, vrefout:50%
dram drv:40,odt:120
sr_dq:0, sr_ca:0, sr_clk:0
rg:0xc-0x1-0x2, 0x3d-0x0-0x2,status:a007
rdtrn:0x14-0x30-0x4c(0x38)
wrtrn:0x3-0x20-0x3d(0x3a)
DDR3, 750MHz
BW=16 Col=10 Bk=8 CS0 Row=15 CS=1 Size=512MB
out
U-Boot SPL board init
U-Boot SPL 2017.09-g4d88b0a #hxj (Jul 30 2025 - 20:08:42)
sfc cmd=03H(6BH-x4)
SPI Nand ID ef aa 22
unrecognized JEDEC id bytes: ff, ef, aa
Trying to boot from MMC1
No misc partition
spl: partition error
Trying fit image at 0x4000 sector
## Verified-boot: 0
## Checking op-tee 0x00001000 ... sha256(93603ca22c...) + OK
## Checking u-boot 0x00100000 ... sha256(606b868a00...) + OK
## Checking fdt-1 0x0018baf0 ... sha256(6ae9f912c7...) + OK
Jumping to U-Boot(0x00001000)
I/TC: 
I/TC: OP-TEE version: 3.13.0-958-g46dcf51e88a #chenjh (gcc version 10.2.1 20201103 (GNU Toolchain for the A-profile Architecture 10.2-2020.11 (arm-10.16))) #2 Thu Mar  6 10:17:27 CST 2025 arm, fwver: v2.10 
I/TC: Status: cluster=0xc00, core=0xe100, bootcpu=0
I/TC: Next entry point address: 0x03f011a7
I/TC: OP-TEE memory size: TEEOS 0x5e000 TA 0x1000 SHM 0x1000
I/TC: Primary CPU initializing
I/TC: Primary CPU switching to normal world boot</pre>

<p>
	 
</p>
]]></description><guid isPermaLink="false">56085</guid><pubDate>Wed, 05 Nov 2025 17:44:55 +0000</pubDate></item><item><title>Support for vivid unit by uugear</title><link>https://forum.armbian.com/topic/56144-support-for-vivid-unit-by-uugear/</link><description><![CDATA[<p>
	I saw some initial work on supporting uugear's vivid unit (rk3399 based). I was wondering in what state that is, what is required to complete that work and if there are plans to add that support to the mainline?
</p>

<p>
	 
</p>

<p>
	Thanks in advance,
</p>

<p>
	Markus
</p>
]]></description><guid isPermaLink="false">56144</guid><pubDate>Sun, 09 Nov 2025 17:06:10 +0000</pubDate></item><item><title>Kobol Helios64 for sale (soon)</title><link>https://forum.armbian.com/topic/56142-kobol-helios64-for-sale-soon/</link><description><![CDATA[<p>
	Hello, I will soon be selling a working Helios64 from Kobol (with 2.5G fix done from factory).
</p>

<p>
	I also have 3x 6TB hard drive that could come with it if needed.
</p>

<p>
	Based in France, I'm able to send within EU.
</p>

<p>
	Please DM me if interested.
</p>
]]></description><guid isPermaLink="false">56142</guid><pubDate>Sun, 09 Nov 2025 13:52:34 +0000</pubDate></item><item><title>NanoPC-T6 - eMMC I/O errors under heavy load due to HS400 mode</title><link>https://forum.armbian.com/topic/55503-nanopc-t6-emmc-io-errors-under-heavy-load-due-to-hs400-mode/</link><description><![CDATA[<p>
	I've recently switched my FriendlyElec NanoPC-T6 to use the Armbian Linux v6.12 server image, built on the 24th of May 2025. Booting of SD works fine, but when installing to the <abbr title="embedded MultiMediaCard">eMMC</abbr> chip some I/O errors can be found in the kernel logs:
</p>

<p>
	 
</p>

<pre class="ipsCode prettyprint lang-html prettyprinted"><span class="pln">[  151.814773] I/O error, dev mmcblk0, sector 176 op 0x0:(READ) flags 0x80700 phys_seg 10 prio class 2</span></pre>

<p>
	 
</p>

<p>
	This happens when under heavy I/O load - e.g. performing an apt upgrade. I ran badblocks over the entire <abbr title="embedded MultiMediaCard">eMMC</abbr> chip without issue - but that puts a much lower strain on the <abbr title="embedded MultiMediaCard">eMMC</abbr>. Therefore, i'm convinced that the <abbr title="embedded MultiMediaCard">eMMC</abbr> chip itself is fine.
</p>

<p>
	 
</p>

<p>
	Poking around a bit, this seems to be because the A3A444 <abbr title="embedded MultiMediaCard">eMMC</abbr> chip which some NanoPC-T6 SBCs shipped with do not support HS400 mode properly. There is <a href="https://github.com/openwrt/openwrt/issues/18844" rel="external nofollow">an OpenWRT bug report about this</a>, which fixed the issue by <a href="https://github.com/openwrt/openwrt/pull/19926" rel="external nofollow">patching the dtsi to force HS200 mode</a>.
</p>

<p>
	 
</p>

<p>
	My kernel logs confirm that I have the A3A444 <abbr title="embedded MultiMediaCard">eMMC</abbr> chip, and that it is currently running in HS400 mode:
</p>

<p>
	 
</p>

<pre class="ipsCode prettyprint lang-html prettyprinted"><span class="pln">sudo dmesg -e | grep -i mmc
[  +0.015143] mmc0: SDHCI controller on fe2e0000.mmc [fe2e0000.mmc] using ADMA
[  +0.051640] dwmmc_rockchip fe2c0000.mmc: IDMAC supports 32-bit address mode.
[  +0.000020] dwmmc_rockchip fe2c0000.mmc: Using internal DMA controller.
[  +0.000008] dwmmc_rockchip fe2c0000.mmc: Version ID is 270a
[  +0.000025] dwmmc_rockchip fe2c0000.mmc: DW MMC controller at irq 91,32 bit host data width,256 deep fifo
[  +0.000210] dwmmc_rockchip fe2c0000.mmc: Got CD GPIO
[  +0.012806] mmc_host mmc1: Bus speed (slot 0) = 400000Hz (slot req 400000Hz, actual 400000HZ div = 0)
[  +0.007795] mmc0: new HS400 Enhanced strobe MMC card at address 0001
[  +0.000906] mmcblk0: mmc0:0001 A3A444 230 GiB
[  +0.004124]  mmcblk0: p1
[  +0.000720] mmcblk0boot0: mmc0:0001 A3A444 4.00 MiB
[  +0.001831] mmcblk0boot1: mmc0:0001 A3A444 4.00 MiB
[  +0.001742] mmcblk0rpmb: mmc0:0001 A3A444 4.00 MiB, chardev (243:0)
[  +0.227497] EXT4-fs (mmcblk0p1): mounted filesystem a4f48be8-f667-4cac-a9a7-61ce8f9035d1 ro with ordered data mode. Quota mode: none.
[  +0.021022] EXT4-fs (mmcblk0p1): re-mounted a4f48be8-f667-4cac-a9a7-61ce8f9035d1 r/w.</span></pre>

<p>
	 
</p>

<p>
	I've tried to use a user device overlay to use mmc-hs200-1_8v, but this doesn't appear to work. I think this is because Device Overlays can only replace elements or add to the tree? i.e. I cannot use an overlay to remove the existing mmc-hs400-1_8v; and mmc-hs400-enhanced-strobe; entries.
</p>

<p>
	 
</p>

<p>
	Is there a way to do this with a user device overlay, or will I need to try to add a similar patch to OpenWRT's one in the kernel?  This is the first time i've used Armbian so i'm a little unsure about how i'd go about doing the latter.
</p>

<p>
	 
</p>

<p>
	I've found a similar report of this issue from a couple of years ago by <a contenteditable="false" data-ipshover="" data-ipshover-target="https://forum.armbian.com/profile/209066-superkali/?do=hovercard" data-mentionid="209066" href="https://forum.armbian.com/profile/209066-superkali/" rel="">@SuperKali</a>, albeit with no resolution. However, I can see they're now listed as one of the community maintainers for this board so i'm hoping it's OK to mention them in this thread to see if they know how best to force HS200 mode for the <abbr title="embedded MultiMediaCard">eMMC</abbr>!
</p>

<p>
	 
</p>
<iframe allowfullscreen="" data-controller="core.front.core.autosizeiframe" data-embedauthorid="209066" data-embedcontent="" data-embedid="embed3035126226" src="https://forum.armbian.com/topic/30036-nanopc-t6-emmc-error-after-boot?do=embed" style="height:211px;max-width:500px;"></iframe>

<p>
	 
</p>
]]></description><guid isPermaLink="false">55503</guid><pubDate>Sun, 05 Oct 2025 17:37:43 +0000</pubDate></item><item><title>Please Help: Helios64 Kernel Panic, Cannot boot into Armbian_24.8.1_Helios64_bookworm_current_6.6.46-omv_minimal or any current release</title><link>https://forum.armbian.com/topic/55482-please-help-helios64-kernel-panic-cannot-boot-into-armbian_2481_helios64_bookworm_current_6646-omv_minimal-or-any-current-release/</link><description><![CDATA[<p>
	Hi community, 
</p>

<p>
	 
</p>

<p>
	I am experiencing an issue reinstalling Armbian on my Helios64. 
</p>

<p>
	I tried all methods including booting from an SD card, flashing the image onto the <abbr title="embedded MultiMediaCard">eMMC</abbr> directly but every time I boot, I get kernel panic (flashing status light).
</p>

<p>
	I also can't connect to the USB via TTY to diagnose the issue. My macbook keeps detecting the /dev/tty.usbserial-DT03OEIM and the next second it is gone.
</p>

<p>
	 
</p>

<p>
	I wanted to install the original Buster image but I cannot find it anymore in any of the archives. It's kind of disappointing because what's the purpose of an archive then if not hold on to an image for a few years. 
</p>

<p>
	 
</p>

<p>
	My current theories are limited and I can only think that the newer images might not have the correct drivers, but as I said, I can't connect via TTY to even observe the boot log. 
</p>

<p>
	 
</p>

<p>
	I tried pretty much everything at this point: all of the images available (devbian, ubuntu), all flavors of them (minimal, omv). Booting into U-boot, Setting P10, P11 jumpers etc, etc.
</p>

<p>
	 
</p>

<p>
	Can anyone help?
</p>
]]></description><guid isPermaLink="false">55482</guid><pubDate>Sun, 05 Oct 2025 04:20:06 +0000</pubDate></item><item><title>Add NPU support for NanoPC-T6 (RK3588)</title><link>https://forum.armbian.com/topic/52206-add-npu-support-for-nanopc-t6-rk3588/</link><description><![CDATA[<p>
	I am using rk3588-sd-debian-bookworm-core-6.1-arm64-20250123.img.gz
</p>

<p>
	 
</p>

<p>
	It is excellent asides from lacking NPU support. Before I go down the path of learning kernel compilation and scanning poorly documented Rockchip repositories, has anyone got a current version of Armbian that includes NPU support?
</p>

<p>
	 
</p>

<p>
	If not, is there any good guide to using a cross-compile system and integrating third part drivers?.
</p>

<p>
	 
</p>

<p>
	On a slightly different topic I would prefer to not use fuse file systems and run off the NVME drive directly. Are there any resources on this?
</p>
]]></description><guid isPermaLink="false">52206</guid><pubDate>Wed, 28 May 2025 04:59:10 +0000</pubDate></item><item><title>Helios64 HDD Cable Harness issue</title><link>https://forum.armbian.com/topic/54924-helios64-hdd-cable-harness-issue/</link><description><![CDATA[<p>
	Hello,
</p>

<p>
	 
</p>

<p>
	Recently the HDD Cable Harness for my Helios64 malfunctioned.
</p>

<p>
	 
</p>

<p>
	SATA Ports 1 and 2 are both no longer getting power/HDDs are not spinning up.
</p>

<p>
	 
</p>

<p>
	I confirmed that it was power by plugging the SATA cable into ports 3, 4, and 5 on the motherboard which all function.
</p>

<p>
	 
</p>

<p>
	I also iterated through the system by removing all the HDD's and testing each HDD slot one at a time.  All 5 HDDs fucntion individually in a USB drive enclosure, and all 5 function in my server system and I can mount the RAID array.
</p>

<p>
	 
</p>

<p>
	My question is, does anyone know how to contact the Helios/Kobol team so I can purchase a replacement HDD Harness Cable?  
</p>

<p>
	 
</p>

<p>
	I checked on Aliexpress and can't find anything similar so I presume that the cable is custom.
</p>

<p>
	 
</p>

<p>
	Thank you.
</p>
]]></description><guid isPermaLink="false">54924</guid><pubDate>Tue, 02 Sep 2025 14:18:38 +0000</pubDate></item><item><title>Orange PI 5 PRO, option to upgrade kernel in armbian-config is gone.</title><link>https://forum.armbian.com/topic/55847-orange-pi-5-pro-option-to-upgrade-kernel-in-armbian-config-is-gone/</link><description><![CDATA[<p>
	Yesterday, Oct 20th, I installed armbian version "Minimal/IOT images with Armbian Linux v6.1" to the Orange PI 5 PRO and updated kernel using armbian-config to kernel 6.18 RC1(2 options were available 6.12 and 6.18 R1, note 6.12 did not work).
</p>

<p>
	Armbian works fine including vulkan support(I tested with swith emulator) with this kernel(6.18 rc1), but today option to update to any kernel is not available anymore. I'm getting warning "No other kernels available!"
</p>

<p>
	System is pretty stable with this version.
</p>

<p>
	 
</p>

<p>
	stas@orangepi5pro:~$ uname -r<br />
	6.18.0-rc1-edge-rockchip64
</p>

<p>
	 
</p>

<p>
	stas@orangepi5pro:~$ vulkaninfo --summary<br />
	==========<br />
	VULKANINFO<br />
	==========
</p>

<p>
	Vulkan Instance Version: 1.4.309
</p>

<p>
	<br />
	Instance Extensions: count = 24<br />
	-------------------------------<br />
	VK_EXT_acquire_drm_display             : extension revision 1<br />
	VK_EXT_acquire_xlib_display            : extension revision 1<br />
	VK_EXT_debug_report                    : extension revision 10<br />
	VK_EXT_debug_utils                     : extension revision 2<br />
	VK_EXT_direct_mode_display             : extension revision 1<br />
	VK_EXT_display_surface_counter         : extension revision 1<br />
	VK_EXT_headless_surface                : extension revision 1<br />
	VK_EXT_surface_maintenance1            : extension revision 1<br />
	VK_EXT_swapchain_colorspace            : extension revision 5<br />
	VK_KHR_device_group_creation           : extension revision 1<br />
	VK_KHR_display                         : extension revision 23<br />
	VK_KHR_external_fence_capabilities     : extension revision 1<br />
	VK_KHR_external_memory_capabilities    : extension revision 1<br />
	VK_KHR_external_semaphore_capabilities : extension revision 1<br />
	VK_KHR_get_display_properties2         : extension revision 1<br />
	VK_KHR_get_physical_device_properties2 : extension revision 2<br />
	VK_KHR_get_surface_capabilities2       : extension revision 1<br />
	VK_KHR_portability_enumeration         : extension revision 1<br />
	VK_KHR_surface                         : extension revision 25<br />
	VK_KHR_surface_protected_capabilities  : extension revision 1<br />
	VK_KHR_wayland_surface                 : extension revision 6<br />
	VK_KHR_xcb_surface                     : extension revision 6<br />
	VK_KHR_xlib_surface                    : extension revision 6<br />
	VK_LUNARG_direct_driver_loading        : extension revision 1
</p>

<p>
	Instance Layers: count = 2<br />
	--------------------------<br />
	VK_LAYER_MESA_device_select Linux device selection layer 1.4.303  version 1<br />
	VK_LAYER_MESA_overlay       Mesa Overlay layer           1.4.303  version 1
</p>

<p>
	Devices:<br />
	========<br />
	GPU0:<br />
	    apiVersion         = 1.1.305<br />
	    driverVersion      = 25.0.7<br />
	    vendorID           = 0x13b5<br />
	    deviceID           = 0xa8670000<br />
	    deviceType         = PHYSICAL_DEVICE_TYPE_INTEGRATED_GPU<br />
	    deviceName         = Mali-G610<br />
	    driverID           = DRIVER_ID_MESA_PANVK<br />
	    driverName         = panvk<br />
	    driverInfo         = Mesa 25.0.7-2<br />
	    conformanceVersion = 1.4.1.2
</p>

<p>
	 
</p>

<p>
	 
</p>
]]></description><guid isPermaLink="false">55847</guid><pubDate>Tue, 21 Oct 2025 21:35:16 +0000</pubDate></item><item><title><![CDATA[Manually adding new Mesa & Mali drivers to Armbian (Debain 6.12)]]></title><link>https://forum.armbian.com/topic/52513-manually-adding-new-mesa-mali-drivers-to-armbian-debain-612/</link><description><![CDATA[<p>
	Hey everyone, for the past couple of days I've been looking into the Mesa-<abbr title="Video processing unit (encoding/decoding)"><abbr title="Video processing unit (encoding/decoding)">VPU</abbr></abbr> script made by AmazingFate that's used to patch Mesa/<abbr title="Video processing unit (encoding/decoding)"><abbr title="Video processing unit (encoding/decoding)">VPU</abbr></abbr> onto a custom build of Armbian.<br />
	<a href="https://github.com/armbian/build/blob/main/extensions/mesa-vpu.sh" rel="external nofollow">https://github.com/armbian/build/blob/main/extensions/mesa-<abbr title="Video processing unit (encoding/decoding)"><abbr title="Video processing unit (encoding/decoding)">vpu</abbr></abbr>.sh</a><br />
	<br />
	I already have an install of Armbian (Debian XFCE 6.12.28-current-rockchip64 ) on my Rock5b and was looking into applying as much as I can without re-building an image or starting from scratch.<br />
	<br />
	From my understanding, You'd need the vendor rk3588 kernel if you want the best possible compatibility with things like the <abbr title="Video processing unit (encoding/decoding)"><abbr title="Video processing unit (encoding/decoding)">VPU</abbr></abbr> for multimedia acceleration (Someone please correct me if this is not the case lol)
</p>

<p>
	 
</p>

<p>
	What follows is what I was able to piece together after troubleshooting, reading the Mesa changelog &amp; trying to apply as many packages as I can from AmazingFate's kernel extension script. I've also included some tweaks for XFCE to hopefully provide a smooth graphical experience.<br />
	<br />
	Although my Rock5b is used as a headless server and doesnt have anything plugged into the HDMI port, I can say that the following changes have made a huge difference in graphical performance of VNC. <br />
	<br />
	Please keep in mind that i'm not a developer for Armbian. I just wanted to share this as a guide i've put together to hopefully help someone else who's tried the same<br />
	(Please let me know your thoughts or if there was anything i've missed. Like I said, this is what has worked for me)<br />
	(Obviously the correct fix is to rebuild Armbian with Mesa-<abbr title="Video processing unit (encoding/decoding)"><abbr title="Video processing unit (encoding/decoding)">VPU</abbr></abbr>. What follows was done as an experiment)<br />
	<br />
	<strong><span style="font-size:16px;">#################### GUIDE BELOW. THIS IS NOT A SHELL SCRIPT! PLEASE READ AND DO NOT COPY/PASTE ENTIRETY INTO TERMINAL!#############################</span></strong>
</p>

<p>
	<br />
	 
</p>

<pre class="ipsCode prettyprint lang-html prettyprinted"><span class="pln">#### -- 01 Setup AmazingFate Panfork-Mesa repo for mali-g610-firmware 01 -- ####


## 1A: import gpg key and use it to sign repo ##
wget -qO - https://download.opensuse.org/repositories/home:/amazingfate:/panfork-mesa/Debian_12/Release.key | sudo gpg --dearmor -o /etc/apt/trusted.gpg.d/panfork-mesa.gpg


## 1B: Add Repo to apt sources &amp; update ##
echo "deb https://download.opensuse.org/repositories/home:/amazingfate:/panfork-mesa/Debian_12/ /" | sudo tee /etc/apt/sources.list.d/panfork-mesa.list
sudo apt update


## 1C: Install firmware ##
sudo apt install mali-g610-firmware libmali-g610-x11


## 1D: **RECOMMENDED** : Remove panfork-mesa repo ##
sudo rm -rf /etc/apt/sources.list.d/panfork-mesa.list
sudo rm -rf /etc/apt/trusted.gpg.d/panfork-mesa.gpg


#### -- 02 Enable Debian Experimental Repo for recent Mesa Packages 02 -- ####
sudo nano /etc/apt/sources.list


## 2A: Add the following to the bottom of the document... ##
deb http://deb.debian.org/debian unstable main contrib non-free
deb http://deb.debian.org/debian experimental main


## 2B: Update and install Mesa Packages ##
sudo apt update
sudo apt install -t experimental mesa-vulkan-drivers mesa-utils libgl1-mesa-dri libglx-mesa0 mesa-vdpau-drivers mesa-va-drivers mesa-opencl-icd mesa-libgallium


## 2C: **RECOMMENDED** : Re-open apt sources and remove Experimental/Unstable repos... ##
sudo nano /etc/apt/sources.list

#Remove the following and update apt...#
deb http://deb.debian.org/debian unstable main contrib non-free
deb http://deb.debian.org/debian experimental main

sudo apt update


#### -- 03 Add rockchip-multimedia Ubuntu Repo to Apt 03 -- ####
echo "deb [arch=arm64] https://ppa.launchpadcontent.net/liujianfeng1994/rockchip-multimedia/ubuntu jammy main" | sudo tee /etc/apt/sources.list.d/rockchip-multimedia.list


## 3A: Download Key and add convert to gpg ##
curl -o rockchip-multimedia.asc "https://keyserver.ubuntu.com/pks/lookup?op=get&amp;search=0x8065BE1FC67AABDE"
gpg --dearmor rockchip-multimedia.asc
sudo mv rockchip-multimedia.asc.gpg /etc/apt/keyrings/rockchip-multimedia.gpg


## 3B: Add PPA Repo and update ##
echo "deb [arch=arm64 signed-by=/etc/apt/keyrings/rockchip-multimedia.gpg] https://ppa.launchpadcontent.net/liujianfeng1994/rockchip-multimedia/ubuntu jammy main" | sudo tee /etc/apt/sources.list.d/rockchip-multimedia.list
sudo apt update


## 3C: Install packages ##
sudo apt install libv4l-rkmpp chromium gstreamer1.0-rockchip1 rockchip-multimedia-config


## 3D: **OPTIONAL** : Disable rockchip-multimedia PPA repo ##
sudo mv /etc/apt/sources.list.d/rockchip-multimedia.list /etc/apt/sources.list.d/rockchip-multimedia.list.disabled
sudo apt update


#### -- 04 Optimize XFCE/Xorg and Reboot 04 -- ####

## 4A: Open default xorg config ##
sudo nano /etc/X11/xorg.conf.d/01-armbian-defaults.conf


#Add the following... #
Section "Device"
   Identifier "Mali-G610"
   Driver "modesetting"
   Option "DRI" "3"               # Required for Mali GPUs
   Option "GALLIUM_DRIVER" "panfrost"
   Option "PageFlip" "on"          # Reduces tearing
   Option "TearFree" "true"        # Xfce-specific anti-tearing
EndSection


## 4B: Add XFCE Specific tweaks ##
sudo nano /etc/X11/xorg.conf.d/20-xfce-tweaks.conf


#Add the following... #
Section "Extensions"
   Option "COMPOSITE" "Enable"
EndSection

Section "ServerFlags"
   Option "AutoAddGPU" "off"  # Prevents duplicate GPU detection
EndSection    


## 4C: Reboot ##
sudo reboot now</span></pre>

<p>
	 
</p>
]]></description><guid isPermaLink="false">52513</guid><pubDate>Wed, 04 Jun 2025 14:43:46 +0000</pubDate></item><item><title>Custom Build on new version(25.11.0 ) is not enabling Panfrost (Mali) GPU driver (BOARD=orangepi5-plus BRANCH=vendor RELEASE=noble DESKTOP=cinnamon)</title><link>https://forum.armbian.com/topic/55846-custom-build-on-new-version25110-is-not-enabling-panfrost-mali-gpu-driver-boardorangepi5-plus-branchvendor-releasenoble-desktopcinnamon/</link><description><![CDATA[<p>
	Hi Guys,<br />
	I just did a new custom Armbian build  ./compile.sh BOARD=orangepi5-plus BRANCH=vendor RELEASE=noble KERNEL_ONLY=yes KERNEL_CONFIGURE=no.<br />
	The image is Armbian-unofficial_25.11.0-trunk_Orangepi5-plus_noble_vendor_6.1.115_cinnamon_desktop and when I installed it on orangepi I see it is not supporting <abbr title="driver for Mali Midgard and Bifrost GPUs"><abbr title="driver for Mali Midgard and Bifrost GPUs">Panfrost</abbr></abbr>/Mail:<br />
	<strong>glxinfo | grep -E "OpenGL renderer|OpenGL version"</strong><br />
	OpenGL renderer string: <strong>llvmpipe</strong> (LLVM 20.1.2, 128 bits) OpenGL version string: 4.5 (Compatibility Profile) Mesa 25.0.7-0ubuntu0.24.04.2<br />
	<br />
	but for older image Old_Armbian-unofficial_25.08.0-trunk_Orangepi5-plus_noble_vendor_6.1.115_cinnamon_desktop All was well<br />
	<strong>glxinfo | grep -E "OpenGL renderer|OpenGL version"</strong><br />
	OpenGL renderer string: <strong>Mali-G610 (<abbr title="driver for Mali Midgard and Bifrost GPUs"><abbr title="driver for Mali Midgard and Bifrost GPUs">Panfrost</abbr></abbr>) </strong>OpenGL version string: 3.1 Mesa 25.0.7-0ubuntu0.24.04.2 <br />
	<br />
	I did need to enable "ARM Mail Display Processor" under Device Drivers -&gt; Graphics support -&gt; ARM devices before I perform custom build.<br />
	And I did this for both OS version 25.11.0 and 25.08.0.<br />
	But newer version is not able to use it.<br />
	Thanks
</p>

<p>
	Manish
</p>
]]></description><guid isPermaLink="false">55846</guid><pubDate>Tue, 21 Oct 2025 18:46:56 +0000</pubDate></item><item><title>ROCK64 BY PINE64 don't boot</title><link>https://forum.armbian.com/topic/52746-rock64-by-pine64-dont-boot/</link><description><![CDATA[
<div class="ipsMargin_top">
    
    
    
</div><p>
	Good morning:
</p>

<p>
	I've got a ROCK64 and it does't boot from few days. White; Red and Green led stand with light. nothing change even after minutes. I've tried rock64-debian-mrfixit-190531.img.xz, , freedombox-bookworm_all-arm64.img.xz, debian-12.11.0-arm64-netinst.iso, But never go further.
</p>

<p>
	Do you have an idea ?
</p>

<p>
	I've got a 5A power so should not be a problem.
</p>
]]></description><guid isPermaLink="false">52746</guid><pubDate>Mon, 09 Jun 2025 21:02:56 +0000</pubDate></item><item><title>Turing-RK1 HDMI Video Output</title><link>https://forum.armbian.com/topic/55751-turing-rk1-hdmi-video-output/</link><description><![CDATA[<p>
	I have completed a build for the <strong>turing-rk1</strong> <abbr title="Single board computer"><abbr title="Single board computer">SBC</abbr></abbr> with an aim toward getting a functioning graphical console, and possibly installing desktop packages later.  I built an image without issue that picked up kernel 6.17.2.  
</p>

<p>
	 
</p>

<pre class="ipsCode prettyprint lang-html prettyprinted"><span class="pln">git commit: 09160da3b9c1231cf20837e8c857f7e605130449
main branch
Command used: ./compile.sh RELEASE=trixie CARD=turing-rk1 BRANCH=edge
Image created: Armbian-unofficial_25.11.0-trunk_Turing-rk1_trixie_edge_6.17.2.img</span></pre>

<p>
	 
</p>

<p>
	When booted, I get an error from dmesg about VOP drivers and HDMI video does not turn on.  Is this normal for this board or am I doing something wrong?
</p>

<p>
	 
</p>

<pre class="ipsCode prettyprint lang-html prettyprinted"><span class="pln">[    0.965616] rckchip-drm display-subsystem: [drm:rockchip_drm_platform_probe] *ERROR* No available vop found for display-subsystem.</span></pre>

<p>
	 
</p>

<p>
	The git commit that introduced this board in Armbian does appear to include <abbr title="Graphic processing unit (3D acceleration)"><abbr title="Graphic processing unit (3D acceleration)">GPU</abbr></abbr> support, though I'm not really sure if that means the HDMI output should be working.  
</p>

<p>
	 
</p>

<p>
	<a href="https://github.com/armbian/build/commit/d564431dc2e2a16dff8d21391603702b43de06b1#diff-1d2956e936e3a376577f803ce53091b41ed47e906602165217f78912496eac63" rel="external nofollow">https://github.com/armbian/build/commit/d564431dc2e2a16dff8d21391603702b43de06b1#diff-1d2956e936e3a376577f803ce53091b41ed47e906602165217f78912496eac63</a>
</p>

<p>
	Maybe I need to build w/ kernel 6.11.x to enable <abbr title="Graphic processing unit (3D acceleration)">GPU</abbr> support with these patches?
</p>

<p>
	 
</p>

<p>
	Can someone clarify?
</p>
]]></description><guid isPermaLink="false">55751</guid><pubDate>Wed, 15 Oct 2025 17:48:02 +0000</pubDate></item><item><title>Orange Pi 5 Pro - extend SPI4 to 5 chipselect</title><link>https://forum.armbian.com/topic/55727-orange-pi-5-pro-extend-spi4-to-5-chipselect/</link><description><![CDATA[<p>
	I am trying to extend the chipselect from spi4. Because I will need to control more boards, so I tried to transform <abbr title="General purpose input/output"><abbr title="General purpose input/output">GPIO</abbr></abbr> into chipselect (CS). This is the original SPI4:<br />
	 
</p>

<pre class="ipsCode prettyprint lang-xml prettyprinted"><span class="pln">/dts-v1/;

/ {

        fragment@0 {
                target = &lt;0xffffffff&gt;;

                __overlay__ {
                        status = "okay";
                        #address-cells = &lt;0x01&gt;;
                        #size-cells = &lt;0x00&gt;;
                        pinctrl-names = "default";
                        pinctrl-0 = &lt;0xffffffff 0xffffffff 0xffffffff&gt;;

                        spidev@0 {
                                compatible = "rockchip,spidev";
                                status = "okay";
                                reg = &lt;0x00&gt;;
                                spi-max-frequency = &lt;0x2faf080&gt;;
                        };

                        spidev@1 {
                                compatible = "rockchip,spidev";
                                status = "okay";
                                reg = &lt;0x01&gt;;
                                spi-max-frequency = &lt;0x2faf080&gt;;
                        };
                };
        };

        __fixups__ {
                spi4 = "/fragment@0:target:0";
                spi4m1_cs0 = "/fragment@0/__overlay__:pinctrl-0:0";
                spi4m1_cs1 = "/fragment@0/__overlay__:pinctrl-0:4";
                spi4m1_pins = "/fragment@0/__overlay__:pinctrl-0:8";
        };
};</span></pre>

<p>
	<br />
	<br />
	And this is the my change that is compiling with warning:<br />
	 
</p>

<pre class="ipsCode prettyprint lang-xml prettyprinted"><span class="pln">/dts-v1/;

/ {
    fragment@0 {
        target = &lt;0xffffffff&gt;;

        __overlay__ {
            status = "okay";
            #address-cells = &lt;1&gt;;
            #size-cells = &lt;0&gt;;

            pinctrl-names = "default";
            pinctrl-0 = &lt;0xffffffff 0xffffffff 0xffffffff&gt;;

            cs-gpios = &lt;
                0xffffffff 4 1   /* CS2: GPIO1_A4 */
                0xffffffff 6 1   /* CS3: GPIO1_A6 */
                0xffffffff 7 1   /* CS4: GPIO4_A7 */
            &gt;;
            spidev@0 {
                compatible = "rockchip,spidev";
                reg = &lt;0&gt;;
                spi-max-frequency = &lt;50000000&gt;;
                status = "okay";
            };
            spidev@1 {
                compatible = "rockchip,spidev";
                reg = &lt;1&gt;;
                spi-max-frequency = &lt;50000000&gt;;
                status = "okay";
            };
            spidev@2 {
                compatible = "rockchip,spidev";
                reg = &lt;2&gt;;
                spi-max-frequency = &lt;50000000&gt;;
                status = "okay";
            };
            spidev@3 {
                compatible = "rockchip,spidev";
                reg = &lt;3&gt;;
                spi-max-frequency = &lt;50000000&gt;;
                status = "okay";
            };
            spidev@4 {
                compatible = "rockchip,spidev";
                reg = &lt;4&gt;;
                spi-max-frequency = &lt;50000000&gt;;
                status = "okay";
            };
        };
    };

    __fixups__ {
        spi4 = "/fragment@0:target:0";
        spi4m1_cs0 = "/fragment@0/__overlay__:pinctrl-0:0"; /* CS0 */
        spi4m1_cs1 = "/fragment@0/__overlay__:pinctrl-0:4"; /* CS1 */
        spi4m1_pins = "/fragment@0/__overlay__:pinctrl-0:8"; /* SCLK/MISO/MOSI */

        spi4m1_cs2 = "/fragment@0/__overlay__:cs-gpios:0";  /* CS2 */
        spi4m1_cs3 = "/fragment@0/__overlay__:cs-gpios:1";  /* CS3 */
        spi4m1_cs4 = "/fragment@0/__overlay__:cs-gpios:2";  /* CS4 */
    };
};</span></pre>

<p>
	 
</p>
]]></description><guid isPermaLink="false">55727</guid><pubDate>Tue, 14 Oct 2025 13:59:56 +0000</pubDate></item><item><title>CM3588-NAS HDMI Audio enablement</title><link>https://forum.armbian.com/topic/55671-cm3588-nas-hdmi-audio-enablement/</link><description><![CDATA[<p>
	The armbian edge image for the FriendlyElec CM3588-NAS is currently on kernel 6.17 but has no HDMI audio despite it having been added in 6.15 (I think). This is simply because it has not been enabled in the device tree for this board. You can enable it with this user overlay:
</p>

<pre class="ipsCode prettyprint lang-c prettyprinted"><span class="pun">/</span><span class="pln">dts</span><span class="pun">-</span><span class="pln">v1</span><span class="pun">/;</span><span class="pln">
</span><span class="pun">/</span><span class="pln">plugin</span><span class="pun">/;</span><span class="pln">

</span><span class="pun">/</span><span class="pln"> </span><span class="pun">{</span><span class="pln">
        fragment@0 </span><span class="pun">{</span><span class="pln">
                target</span><span class="pun">-</span><span class="pln">path </span><span class="pun">=</span><span class="pln"> </span><span class="str">"/hdmi0-sound"</span><span class="pun">;</span><span class="pln">

                __overlay__ </span><span class="pun">{</span><span class="pln">
                        status </span><span class="pun">=</span><span class="pln"> </span><span class="str">"okay"</span><span class="pun">;</span><span class="pln">
                </span><span class="pun">};</span><span class="pln">
        </span><span class="pun">};</span><span class="pln">


        fragment@1 </span><span class="pun">{</span><span class="pln">
                target</span><span class="pun">-</span><span class="pln">path </span><span class="pun">=</span><span class="pln"> </span><span class="str">"/hdmi1-sound"</span><span class="pun">;</span><span class="pln">

                __overlay__ </span><span class="pun">{</span><span class="pln">
                        status </span><span class="pun">=</span><span class="pln"> </span><span class="str">"okay"</span><span class="pun">;</span><span class="pln">
                </span><span class="pun">};</span><span class="pln">
        </span><span class="pun">};</span><span class="pln">
</span><span class="pun">};</span></pre>

<p>
	 
</p>
]]></description><guid isPermaLink="false">55671</guid><pubDate>Sun, 12 Oct 2025 05:48:36 +0000</pubDate></item><item><title>working with the orange Pi 3B</title><link>https://forum.armbian.com/topic/55544-working-with-the-orange-pi-3b/</link><description><![CDATA[<p>
	at the first launch, I ran into the problem that the board cannot connect to the lan Internet via cable, it writes permanent connection and disconnection in the admin console. therefore, I cannot find out the ip address and understand what to connect to. Please help me if someone knows or has solved this problem.
</p>
]]></description><guid isPermaLink="false">55544</guid><pubDate>Mon, 06 Oct 2025 21:18:26 +0000</pubDate></item><item><title>Building latest moonlight qt version</title><link>https://forum.armbian.com/topic/41474-building-latest-moonlight-qt-version/</link><description><![CDATA[<p>
	Hello:
</p>

<p>
	 
</p>

<p>
	I am tyring to build the latest version of moonlight-qt (6.0.0).
</p>

<p>
	Up until now, I succeded by removing the disable-libdrm and disable-wayland to enable hardware acceleration and use H264, H265 and AV1 all of them through hardware acceleration.
</p>

<p>
	However, I get huge decoding times and they are even variable, ranging from 40ms to 300ms depending on what is going on in the streaming.
</p>

<p>
	The 4.3.1 version provided by <a contenteditable="false" data-ipshover="" data-ipshover-target="https://forum.armbian.com/profile/200522-amazingfate/?do=hovercard" data-mentionid="200522" href="https://forum.armbian.com/profile/200522-amazingfate/" rel="">@amazingfate</a> works very good at 4ms decoding time but I would like to test the new AV1 encoder and features from the latest version.
</p>

<p>
	What steps should I follow to get it working correctly?
</p>

<p>
	 
</p>

<p>
	Thank you in advance
</p>
]]></description><guid isPermaLink="false">41474</guid><pubDate>Fri, 21 Jun 2024 16:25:58 +0000</pubDate></item><item><title>youyeetoo r1  RK3588S  Mali-G610 gpu  support ?</title><link>https://forum.armbian.com/topic/55368-youyeetoo-r1-rk3588s-mali-g610-gpu-support/</link><description><![CDATA[<p>
	Just wonder if there is a good  guide how to make  dri work and allt the supported code´s work  in wayland / xorg or other   / Thanks
</p>
]]></description><guid isPermaLink="false">55368</guid><pubDate>Tue, 30 Sep 2025 19:47:52 +0000</pubDate></item><item><title>Rockpi 4A doesn't boot after package update to 25.8.1</title><link>https://forum.armbian.com/topic/55319-rockpi-4a-doesnt-boot-after-package-update-to-2581/</link><description><![CDATA[<p>
	Hello,
</p>

<p>
	 
</p>

<p>
	I just apt upgrade-ed my Armbian 25.5 from mid-August to 25.8.1 and it doesn't start after software reboot. It is usually headless, I plugged it into a monitor and all I get is a uboot logo in the top left corner. No message, nothing.
</p>

<p>
	The board is the Rockpi 4A. The system is on <abbr title="embedded MultiMediaCard">eMMC</abbr> <span class="ipsEmoji">😩</span>
</p>

<p>
	 
</p>

<p>
	What do I do now to at least roll back ? At worst make a browsable copy of the <abbr title="embedded MultiMediaCard">eMMC</abbr> ?
</p>

<p>
	 
</p>

<p>
	Thanks!
</p>

<p>
	Antoine
</p>
]]></description><guid isPermaLink="false">55319</guid><pubDate>Thu, 25 Sep 2025 20:01:29 +0000</pubDate></item></channel></rss>
