<?xml version="1.0"?>
<rss version="2.0"><channel><title>Off-topic Latest Topics</title><link>https://forum.armbian.com/forum/10-off-topic/</link><description>Off-topic Latest Topics</description><language>en</language><item><title>RK3568 (Rockchip) + OP-TEE on Yocto: Need Source-Proven TA Development Path (Not rkbin/prebuilt)</title><link>https://forum.armbian.com/topic/58616-rk3568-rockchip-op-tee-on-yocto-need-source-proven-ta-development-path-not-rkbinprebuilt/</link><description><![CDATA[<p>
	Hi everyone,
</p>

<p>
	I’m working on an RK3568-based platform (Yocto build, Rockchip BSP) and I’ve reached a blocker regarding OP-TEE / Trusted Application (TA) development. Anyone knows how to get <br />
	 
</p>

<p>
	RK3568 + Linux + OP-TEE source/build path
</p>

<p>
	Rockchip vendor SDK with RK3568 OP-TEE source
</p>

<p>
	a repo showing rk3568 + optee_os + TA dev kit for Linux
</p>
]]></description><guid isPermaLink="false">58616</guid><pubDate>Sat, 21 Mar 2026 19:11:09 +0000</pubDate></item><item><title>Orange Pi CM4</title><link>https://forum.armbian.com/topic/32807-orange-pi-cm4/</link><description><![CDATA[<p>
	Hello,<br />
	Could anybody provide plans/recommendations about Armbian and Orange Pi CM4 board?
</p>

<p>
	Thanks in advance.
</p>
]]></description><guid isPermaLink="false">32807</guid><pubDate>Sun, 24 Dec 2023 08:07:43 +0000</pubDate></item><item><title>Clarification on GPL 2.0 License Applicability</title><link>https://forum.armbian.com/topic/58196-clarification-on-gpl-20-license-applicability/</link><description><![CDATA[<p>
	As someone not familiar with all the ins and outs of GPL specifically, how does GPL in the armbian/build project play with userpatches? Is it expected that a commercial hardware device using Armbian would need to open-source the customize-image.sh script?
</p>

<p>
	 
</p>

<p>
	Thanks!
</p>
]]></description><guid isPermaLink="false">58196</guid><pubDate>Fri, 27 Feb 2026 16:41:16 +0000</pubDate></item><item><title>Armbian Debian suggestion</title><link>https://forum.armbian.com/topic/58186-armbian-debian-suggestion/</link><description><![CDATA[<p>
	Hi,
</p>

<p>
	 
</p>

<p>
	No sure if this is the place to post this but here it goes.
</p>

<p>
	 
</p>

<p>
	I use the Debian distro for my armbian deployments. Every time I deploy, and the system comes with systemd-resolved it gives me problems. I always have to remove it and use the /etc/resolv.conf file by it self.
</p>

<p>
	 
</p>

<p>
	I would suggest removing this, it's not necessary or useful.
</p>

<p>
	 
</p>

<p>
	-Cheers
</p>
]]></description><guid isPermaLink="false">58186</guid><pubDate>Thu, 26 Feb 2026 15:00:51 +0000</pubDate></item><item><title>Z1  SE ATV root</title><link>https://forum.armbian.com/topic/58151-z1-se-atv-root/</link><description><![CDATA[<p>
	Hello everyone,
</p>

<p>
	 
</p>

<p>
	I'm looking on how to get patched boot.img from this firmware: <a href="https://disk.yandex.ru/d/10ARWp8CEpWr_Q" rel="external nofollow">https://disk.yandex.ru/d/10ARWp8CEpWr_Q</a>
</p>

<p>
	It is Z1 se android box with h313 chip and 2/16 gb ram
</p>

<p>
	What i tried is: magisk latest apk (unsupported)
</p>

<p>
	If anyone could help me,my telegram account is: @jasmin8111
</p>

<p>
	 
</p>
]]></description><guid isPermaLink="false">58151</guid><pubDate>Tue, 24 Feb 2026 11:37:13 +0000</pubDate></item><item><title>&#x1F449; Multitool RK3318 / RK3328 TV Box</title><link>https://forum.armbian.com/topic/58136-%F0%9F%91%89-multitool-rk3318-rk3328-tv-box/</link><description><![CDATA[<p>
	Hello averyone  I'm trying to download the multitool.img.xz can someone please help me find it or share a valide link?
</p>
]]></description><guid isPermaLink="false">58136</guid><pubDate>Mon, 23 Feb 2026 10:22:10 +0000</pubDate></item><item><title>Can't find where to upload avatar image, with email sign-on: help?</title><link>https://forum.armbian.com/topic/56744-cant-find-where-to-upload-avatar-image-with-email-sign-on-help/</link><description><![CDATA[<p>
	Hi everyone! <span><img alt=":)" data-emoticon="" height="20" src="https://forum.armbian.com/uploads/emoticons/default_smile.png" srcset="https://forum.armbian.com/uploads/emoticons/smile@2x.png 2x" title=":)" width="20" /></span>
</p>

<p>
	<span>I'm obviously new here, and I simply wanted to give my profile a picture, but failed to find that option in the "profile &gt; account settings".</span>
</p>

<p>
	I assume it's easy, and to be honest I like to take the time to ask a real person here. <span><img alt=":D" data-emoticon="" height="20" src="https://forum.armbian.com/uploads/emoticons/default_biggrin.png" srcset="https://forum.armbian.com/uploads/emoticons/biggrin@2x.png 2x" title=":D" width="20" /></span>
</p>

<p>
	 
</p>

<p>
	<span>Is there an option to upload an avatar image?</span>
</p>

<p>
	<span>Thank you!</span>
</p>
]]></description><guid isPermaLink="false">56744</guid><pubDate>Mon, 15 Dec 2025 22:09:43 +0000</pubDate></item><item><title>Video : Pi-Apps on Armbian on the Radxa Dragon Q6A</title><link>https://forum.armbian.com/topic/57452-video-pi-apps-on-armbian-on-the-radxa-dragon-q6a/</link><description><![CDATA[<div class="ipsEmbeddedVideo" contenteditable="false">
	<div>
		<iframe allowfullscreen="" frameborder="0" height="113" title="Pi-Apps on Armbian on the Radxa Dragon Q6A" width="200" data-embed-src="https://www.youtube-nocookie.com/embed/d552kzX0YeM?feature=oembed"></iframe>
	</div>
</div>

<p>
	 
</p>
]]></description><guid isPermaLink="false">57452</guid><pubDate>Sat, 17 Jan 2026 23:28:51 +0000</pubDate></item><item><title>Jide Remix Mini (1G/2G) can now (since February) use unofficial armbian</title><link>https://forum.armbian.com/topic/56916-jide-remix-mini-1g2g-can-now-since-february-use-unofficial-armbian/</link><description><![CDATA[<p>
	In the past (2019)
</p>
<iframe allowfullscreen="" data-controller="core.front.core.autosizeiframe" data-embedauthorid="10076" data-embedcontent="" data-embedid="embed7875711494" src="https://forum.armbian.com/topic/9606-new-life-for-jide-remix-mini-a64-unsupported/?do=embed" style="height:250px;max-width:502px;"></iframe>

<p>
	there was no chance to use the A64-CPU Jide Remix Mini with armbian, because of a blocked -u-boot<br />
	<br />
	But today I found a site (from February 2025 on github)<br />
	<a href="https://github.com/r4nd3l/revived_remix_mini_pc?tab=readme-ov-file" rel="external nofollow">https://github.com/r4nd3l/revived_remix_mini_pc?tab=readme-ov-file</a><br />
	which can make the Closed Jide Remix Mini to boot from SDCard with a modified u-boot <img alt=":)" data-emoticon="" height="20" src="https://forum.armbian.com/uploads/emoticons/default_smile.png" srcset="https://forum.armbian.com/uploads/emoticons/smile@2x.png 2x" title=":)" width="20" /><br />
	<br />
	There at the github page is a modified u-boot and a modified A64 armbian for the Jide Remix Mini.<br />
	Jide did leave us with a closed/blocked device <span><img alt=":(" data-emoticon="" height="20" src="https://forum.armbian.com/uploads/emoticons/default_sad.png" srcset="https://forum.armbian.com/uploads/emoticons/sad@2x.png 2x" title=":(" width="20" /> AT this time the 16GB <abbr title="embedded MultiMediaCard">emmc</abbr> isnt useable, but using SDCard is a start for upcycling the Jide Remix Mini <span><img alt=":)" data-emoticon="" height="20" src="https://forum.armbian.com/uploads/emoticons/default_smile.png" srcset="https://forum.armbian.com/uploads/emoticons/smile@2x.png 2x" title=":)" width="20" /></span></span>
</p>

<p>
	 
</p>

<p>
	<img class="ipsImage ipsImage_thumbnailed" data-fileid="15713" data-ratio="77.59" width="937" alt="Remix_Armbian_console.jpg.1a2598993d244e7dbd68e2081fdce253.jpg" src="https://forum.armbian.com/uploads/monthly_2025_12/Remix_Armbian_console.jpg.1a2598993d244e7dbd68e2081fdce253.jpg" />
</p>
]]></description><guid isPermaLink="false">56916</guid><pubDate>Thu, 25 Dec 2025 12:15:21 +0000</pubDate></item><item><title>Corrupted Armbian repositories</title><link>https://forum.armbian.com/topic/57313-corrupted-armbian-repositories/</link><description><![CDATA[<p>
	The update from the "armbian.com/beta" repository has not been working for quite some time now. Repositories are broken, sizes in InRelease do not match sizes in subbranches. Mirror synchronization has been going on for about a week now?!
</p>

<p><a href="https://forum.armbian.com/uploads/monthly_2026_01/scrcpy.png.77b189c524bb4b394a6de69df5a44a12.png" class="ipsAttachLink ipsAttachLink_image" ><img data-fileid="15772" src="https://forum.armbian.com/uploads/monthly_2026_01/scrcpy.png.77b189c524bb4b394a6de69df5a44a12.png" data-ratio="49.2" width="1000" class="ipsImage ipsImage_thumbnailed" alt="scrcpy.png"></a></p>]]></description><guid isPermaLink="false">57313</guid><pubDate>Fri, 09 Jan 2026 11:50:15 +0000</pubDate></item><item><title>U-Boot gives errors and loads array of pixels.</title><link>https://forum.armbian.com/topic/57305-u-boot-gives-errors-and-loads-array-of-pixels/</link><description><![CDATA[<p>
	Hello, i'm trying to make Arch work on my H3, it boots to uboot, loads fine and says RAM size and reads /boot/boot.scr, but when it tries to ext4load something it gives a error of ` ** fs_devread read error - block` and ` ** No partition table - mmc 0`, everything after `321 bytes read in 24 ms (33.2 KiB/s)` loads by arrays of pixels, i never seen these before on Armbian, H3Droid or any other img file.
</p>

<p>
	 
</p>

<p>
	[ EDIT ]
</p>

<p>
	Turns out, U-Boot defaults to 400000hz on SD card while saying its mode is SD High Speed (50MHz), i still cant fix the issue...
</p>
]]></description><guid isPermaLink="false">57305</guid><pubDate>Fri, 09 Jan 2026 03:53:46 +0000</pubDate></item><item><title>Server version missing from the product page</title><link>https://forum.armbian.com/topic/56877-server-version-missing-from-the-product-page/</link><description><![CDATA[<p>
	I've noticed that since yesterday the `server` Armbian images disappeared from the product pages.
</p>

<p>
	Example: <a href="https://www.armbian.com/radxa-rock-5-itx/" rel="external nofollow">https://www.armbian.com/radxa-rock-5-itx/</a>
</p>

<p>
	 
</p>

<p>
	I can no longer see them. Is it a bug, or something expected from now on.
</p>

<p>
	 
</p>

<p>
	I also noticed the <a href="https://armbian.chi.auroradev.org/dl/rock-5-itx/" rel="external nofollow">https://armbian.chi.auroradev.org/dl/rock-5-itx/</a> folder is empty.
</p>
]]></description><guid isPermaLink="false">56877</guid><pubDate>Tue, 23 Dec 2025 13:58:26 +0000</pubDate></item><item><title>Unisoc UWE5621DS on RK3566 device?  calling Orange Pi experts</title><link>https://forum.armbian.com/topic/23999-unisoc-uwe5621ds-on-rk3566-device-calling-orange-pi-experts/</link><description><![CDATA[<p>
	Hi
</p>

<p>
	I have an RK3566 board with a Unisoc UWE5621DS wifi/BT chip on it.
</p>

<p>
	I have had a number of kernels running on this board (4.19.209 BSP, 6.0 mainline, 6.1-rc1 mainline) but the wifi is a problem.
</p>

<p>
	I noticed that there is an Orange Pi 5.17 kernel that includes a driver for UWE5622.  I'm not sure how close 5621DS is to 5622
</p>

<p>
	Also I think that this kernel is meant for the Orange Pi 4 which has an RK3399, whereas I have RK3566.
</p>

<p>
	Anyone any thoughts on what is most likely to work?
</p>
]]></description><guid isPermaLink="false">23999</guid><pubDate>Sun, 16 Oct 2022 10:07:05 +0000</pubDate></item><item><title>Hello everyone!</title><link>https://forum.armbian.com/topic/56664-hello-everyone/</link><description>I find this forum very interesting. There's a lot of useful information here.</description><guid isPermaLink="false">56664</guid><pubDate>Wed, 10 Dec 2025 10:42:01 +0000</pubDate></item><item><title>Pinebook (non-Pro) battery swollen - No complete start without it?</title><link>https://forum.armbian.com/topic/56126-pinebook-non-pro-battery-swollen-no-complete-start-without-it/</link><description><![CDATA[<p>
	Yesterday I did start to install armbian trixie iot on my Pinebook.<br />
	Second part in debian - after the u-boot) starts, but then the Pinebook shuts off, because of a low battery(?)
</p>

<p>
	I did charge the whole day and powered off in the evening.<br />
	 
</p>

<p>
	Today the Pinebook stand on my table with a swollen battery. I removed it and happily it doesnt crash anything else than the battery holder.
</p>

<p>
	 
</p>

<p>
	But now it doenst boot up complete like with a low battery.
</p>

<p>
	After the u-boot debian trixie does boot , but at the middle of the messages it does shutdown <img alt=":(" data-emoticon="" height="20" src="https://forum.armbian.com/uploads/emoticons/default_sad.png" srcset="https://forum.armbian.com/uploads/emoticons/sad@2x.png 2x" title=":(" width="20" /><br />
	Can it run completly without battery? I have normally a 5V/2Ah power-supply connected and that did work the last years.
</p>

<p>
	 
</p>

<p>
	Now I can only try to use a 5V/60W quick-charge Power-Supply.<br />
	Anyone has experiences with that?<br />
	<br />
	Thanks for info in advance...
</p>

<p>
	 
</p>

<p>
	<img class="ipsImage ipsImage_thumbnailed" data-fileid="15360" data-ratio="59.25" width="800" alt="Pinebook_A64_Accu_3.jpg.4441403f53495ebbdf076ed1ec7bea2a.jpg" src="https://forum.armbian.com/uploads/monthly_2025_11/Pinebook_A64_Accu_3.jpg.4441403f53495ebbdf076ed1ec7bea2a.jpg" />
</p>

<p>
	<img class="ipsImage ipsImage_thumbnailed" data-fileid="15361" data-ratio="61.63" width="800" alt="Pinebook_A64_Accu_2.jpg.c7d537322b5823dcae16b5bf3ead7cfb.jpg" src="https://forum.armbian.com/uploads/monthly_2025_11/Pinebook_A64_Accu_2.jpg.c7d537322b5823dcae16b5bf3ead7cfb.jpg" />
</p>

<p>
	<img class="ipsImage ipsImage_thumbnailed" data-fileid="15362" data-ratio="62.38" width="800" alt="Pinebook_A64_Accu_1.jpg.a59189ad352ed3711b4886e0ab073bfd.jpg" src="https://forum.armbian.com/uploads/monthly_2025_11/Pinebook_A64_Accu_1.jpg.a59189ad352ed3711b4886e0ab073bfd.jpg" />
</p>
]]></description><guid isPermaLink="false">56126</guid><pubDate>Sat, 08 Nov 2025 11:55:24 +0000</pubDate></item><item><title>No audio output via I&#xB2;S (PCM5102) on Orange Pi Zero 2W (H618)</title><link>https://forum.armbian.com/topic/56135-no-audio-output-via-i%C2%B2s-pcm5102-on-orange-pi-zero-2w-h618/</link><description><![CDATA[<p>
	Hi,
</p>

<p>
	I’m working on enabling I²S audio output using a PCM5102 DAC on an Orange Pi Zero 2W (<abbr title="System On a Chip">SoC</abbr>: Allwinner H618) running Armbian_community_25.11.0-trunk.334_trixie_current_6.12.47_minimal.
</p>

<p>
	Despite several tests and rebuild attempts, I haven’t been able to obtain any sound output from the I²S interface.<br />
	Below is a summary of what has been done so far.
</p>

<p>
	 
</p>

<p>
	<u>Hardware setup</u>
</p>

<p>
	Board: Orange Pi Zero 2W
</p>

<p>
	<abbr title="System On a Chip">SoC</abbr>: Allwinner H618
</p>

<p>
	DAC: PCM5102 (I²S input, analog stereo output)
</p>

<p>
	Connections:
</p>

<p>
	I2S0 → used for DAC (pins LRCK, BCLK, DIN, GND, 3.3V)
</p>

<p>
	Confirmed pin mappings according to H618 documentation and available <abbr title="Device tree source">DTS</abbr> files.
</p>

<p>
	OS Image:<br />
	Armbian_community_25.11.0-trunk.334_Orangepizero2w_trixie_current_6.12.47_minimal
</p>

<p>
	<u>What has been done</u>
</p>

<p>
	1. Kernel confirmed to be mainline-based (6.12.47-current-sunxi64).
</p>

<p>
	<em>Linux orangepizero2w 6.12.47-current-sunxi64 #1 SMP aarch64 GNU/Linux</em>
</p>

<p>
	2. Checked kernel symbols to verify presence of sunxi audio modules:<br />
	Shows <em>sound/<abbr title="System On a Chip">soc</abbr>/sunxi/sun8i-codec.c</em> among others.<br />
	Created a custom overlay at <em>/boot/overlay-user/sun50i-h618-i2s0-pcm5102.dtso</em>, based on examples from sun8i boards, with simple-audio-card referencing the i2s0 controller.
</p>

<p>
	Enabled overlay in <em>/boot/armbianEnv.txt <span>:<br />
	user_overlays=sun50i-h618-i2s0-pcm5102</span></em>
</p>

<p>
	Rebooted and verified device tree loading → No audio device or sound card is registered.
</p>

<p>
	Also tried with predefined overlay <em>sun50i-h618-i2s2-pcm5102</em> included in the Armbian tree → no sound card detected (aplay -l returns “no soundcards found”).
</p>

<p>
	<u>Findings</u>
</p>

<p>
	It seems that the H618 <abbr title="System On a Chip">SoC</abbr> has no upstream audio codec driver (unlike H616 which includes sun8i-codec).
</p>

<p>
	The I²S controller node exists in the mainline kernel sources, but may not be fully supported or linked to a DAI (Digital Audio Interface) for external DACs.
</p>

<p>
	simple-audio-card bindings appear to compile correctly in the overlay, but the device never registers in ALSA.
</p>

<p>
	<u>Questions</u>
</p>

<p>
	Is there any working <abbr title="Device tree source">DTS</abbr> overlay or patch enabling I²S output (no internal codec) for the H618 platform?
</p>

<p>
	If not, what would be the correct approach — patching the <abbr title="Device tree source">DTS</abbr> at kernel source level or adding a compatible binding manually?
</p>

<p>
	Has anyone successfully used a PCM5102 (or similar DAC) with the H618-based boards under Armbian?
</p>

<p>
	<u>My goal</u>
</p>

<p>
	To have a functional stereo I²S audio output through PCM5102 (or any compatible DAC), recognized as an ALSA sound card in Linux.
</p>

<p>
	Any help, hints, or working overlay examples would be greatly appreciated.
</p>

<p>
	Thanks in advance for your time and expertise!
</p>

<p>
	Jose Cardoso
</p>

<p>
	 
</p>
]]></description><guid isPermaLink="false">56135</guid><pubDate>Sat, 08 Nov 2025 23:51:14 +0000</pubDate></item><item><title>Dual board for tailscale/headscale ewon replica</title><link>https://forum.armbian.com/topic/56114-dual-board-for-tailscaleheadscale-ewon-replica/</link><description><![CDATA[<p>
	Hi 
</p>

<p>
	 
</p>

<p>
	I'm looking to emulate an industrial device such as eWon or ESA router by using an <abbr title="Single board computer">sbc</abbr> with dual eth and tailscale/headscale. What is the best and cheapest board? better if with a decent chassis. I'm interested in something like nanopi Rx or orangepi Rx. Any idea? 
</p>

<p>
	 
</p>

<p>
	thank you
</p>
]]></description><guid isPermaLink="false">56114</guid><pubDate>Fri, 07 Nov 2025 11:30:26 +0000</pubDate></item><item><title>Random board not booting up from EMMC</title><link>https://forum.armbian.com/topic/55701-random-board-not-booting-up-from-emmc/</link><description><![CDATA[<pre class="ipsCode prettyprint lang-html prettyprinted"><span class="pln">DDR d5483af87d cym 23/11/23-16:15:24,fwver: v1.15
LPDDR4X, 2112MHz
channel[0] BW=16 Col=10 Bk=8 CS0 Row=16 CS1 Row=16 CS=2 Die BW=16 Size=2048MB
channel[1] BW=16 Col=10 Bk=8 CS0 Row=16 CS1 Row=16 CS=2 Die BW=16 Size=2048MB
channel[2] BW=16 Col=10 Bk=8 CS0 Row=16 CS1 Row=16 CS=2 Die BW=16 Size=2048MB
channel[3] BW=16 Col=10 Bk=8 CS0 Row=16 CS1 Row=16 CS=2 Die BW=16 Size=2048MB
Manufacturer ID:0x0
ch:0 dq0 fail,write:0x1,read:0x0
ch:0 dq1 fail,write:0x2,read:0x0
ch:0 dq2 fail,write:0x4,read:0x0
ch:0 dq3 fail,write:0x8,read:0x0
ch:0 dq4 fail,write:0x10,read:0x0
ch:0 dq5 fail,write:0x20,read:0x0
ch:0 dq6 fail,write:0x40,read:0x0
ch:0 dq7 fail,write:0x80,read:0x0
ch:0 dq8 fail,write:0x100,read:0x0
ch:0 dq9 fail,write:0x200,read:0x0
ch:0 dq10 fail,write:0x400,read:0x0
ch:0 dq11 fail,write:0x800,read:0x0
ch:0 dq12 fail,write:0x1000,read:0x0
ch:0 dq13 fail,write:0x2000,read:0x0
ch:0 dq14 fail,write:0x4000,read:0x0
ch:0 dq15 fail,write:0x8000,read:0x0
ch:0 dq0 fail,write:0xfffffffe,read:0x0
ch:0 dq1 fail,write:0xfffffffd,read:0x0
ch:0 dq2 fail,write:0xfffffffb,read:0x0
ch:0 dq3 fail,write:0xfffffff7,read:0x0
ch:0 dq4 fail,write:0xffffffef,read:0x0
ch:0 dq5 fail,write:0xffffffdf,read:0x0
ch:0 dq6 fail,write:0xffffffbf,read:0x0
ch:0 dq7 fail,write:0xffffff7f,read:0x0
ch:0 dq8 fail,write:0xfffffeff,read:0x0
ch:0 dq9 fail,write:0xfffffdff,read:0x0
ch:0 dq10 fail,write:0xfffffbff,read:0x0
ch:0 dq11 fail,write:0xfffff7ff,read:0x0
ch:0 dq12 fail,write:0xffffefff,read:0x0
ch:0 dq13 fail,write:0xffffdfff,read:0x0
ch:0 dq14 fail,write:0xffffbfff,read:0x0
ch:0 dq15 fail,write:0xffff7fff,read:0x0
error
ERR</span></pre>

<p>
	 
</p>

<p>
	I am using Orangepi5B, 
</p>

<p>
	OS: Copy of Orangepi5b_1.0.8_debian_bookworm_desktop_xfce_linux6.1.43<br />
	<br />
	Providing sufficient power, with 5V and 4A. <br />
	<br />
	any solution to recover from this phase ? <br />
	<br />
	i have also inserted the SD card, but using that i am also getting error, it is not booting up. 
</p>
]]></description><guid isPermaLink="false">55701</guid><pubDate>Mon, 13 Oct 2025 13:06:50 +0000</pubDate></item><item><title>os-release does not match the current update</title><link>https://forum.armbian.com/topic/55615-os-release-does-not-match-the-current-update/</link><description><![CDATA[<p>
	Recently, first when updating the OrangePi 3B, and now the BananaPi M2 Ultra, the /ect/os-release file, *PRETTY_NAME=*trunk.XXX*, has stopped updating correctly. XXX doesn't change and doesn't match the current value.
</p>

<p>
	 
</p>

<p>
	<em>(rolling release)</em>
</p>
]]></description><guid isPermaLink="false">55615</guid><pubDate>Thu, 09 Oct 2025 18:57:14 +0000</pubDate></item><item><title>I2S and external DAC: only one channel</title><link>https://forum.armbian.com/topic/55252-i2s-and-external-dac-only-one-channel/</link><description><![CDATA[<p>
	Hi everyone,
</p>

<p>
	 
</p>

<p>
	I got my OrangePi Zero 2W to work with MAX98357A board, the violet one, but I can only hear one channel. I didn't modify ALSA much, just focused on <abbr title="Device tree source">DTS</abbr>:<br />
	<br />
	 
</p>

<pre class="ipsCode prettyprint lang-html prettyprinted"><span class="pln">...
    fragment@1 {
        target-path = "/soc";
        __overlay__ {
            ahub0_plat: ahub0_plat {
                #sound-dai-cells = &lt;0&gt;;
		compatible	= "allwinner,sunxi-snd-plat-ahub";
                apb_num		= &lt;2&gt;;	/* for dma port 5 */
		dmas		= &lt;&amp;dma 5&gt;, &lt;&amp;dma 5&gt;;
		dma-names	= "tx", "rx";
		playback_cma	= &lt;128&gt;;
		capture_cma	= &lt;128&gt;;
		tx_fifo_size	= &lt;128&gt;;
		rx_fifo_size	= &lt;128&gt;;
                tdm_num         = &lt;0&gt;;
                tx_pin          = &lt;0&gt;;
                rx_pin          = &lt;0&gt;;

		pinctrl-names = "default", "sleep";
                pinctrl_used;
		pinctrl-0 = &lt;&amp;ahub_daudio0_pins_a&gt;, &lt;&amp;ahub_daudio0_pins_b&gt;, &lt;&amp;ahub_daudio0_pins_c&gt;;
		pinctrl-1 = &lt;&amp;ahub_daudio0_pins_d&gt;;

                status = "okay";
            };
            ahub0_mach: ahub0_mach {
                compatible = "allwinner,sunxi-snd-mach";
		soundcard-mach,name = "ahubi2s0";
		soundcard-mach,format = "i2s";
                soundcard-mach,frame-master = &lt;&amp;ahub0_cpu&gt;;
                soundcard-mach,bitclock-master = &lt;&amp;ahub0_cpu&gt;;
                soundcard-mach,slot-num         = &lt;2&gt;;
                soundcard-mach,slot-width       = &lt;32&gt;;

		status = "okay";

                ahub0_cpu: soundcard-mach,cpu {
		    sound-dai = &lt;&amp;ahub0_plat&gt;;
                    soundcard-mach,pll-fs   = &lt;4&gt;;
                    soundcard-mach,mclk-fs  = &lt;0x100&gt;;
		};

		ahub0_codec: soundcard-mach,codec {
		};
            };
            hdmi: hdmi@6000000 {
                status = "disabled";
            };
        };
    };
...</span></pre>

<p>
	 
</p>

<p>
	Did I miss something, and now I'm hearing only the left channel?
</p>

<p>
	 
</p>

<p>
	Has anyone managed to listen to stereo using external DAC?
</p>

<p>
	 
</p>

<p>
	Best!
</p>
]]></description><guid isPermaLink="false">55252</guid><pubDate>Fri, 19 Sep 2025 16:08:07 +0000</pubDate></item><item><title>Link on Tinkerboard S Wiki Page leads to Online Casino</title><link>https://forum.armbian.com/topic/48429-link-on-tinkerboard-s-wiki-page-leads-to-online-casino/</link><description><![CDATA[<p>
	Hi there,
</p>

<p>
	i just noticed that the link which should explain how to enter Maskrom Mode on the Tinkerboard S <a href="https://www.armbian.com/tinkerboard/" rel="external nofollow">https://www.armbian.com/tinkerboard/</a> does not point to the Wiki but to a site for an online Casino.
</p>

<p>
	Seems that tinkerboarding.co.uk does not exist anymore.
</p>

<p>
	Maybe someone could remotve that link.
</p>
]]></description><guid isPermaLink="false">48429</guid><pubDate>Thu, 19 Dec 2024 15:20:47 +0000</pubDate></item><item><title>New Armbian version which contains NPU driver and kernel newer than 6.3</title><link>https://forum.armbian.com/topic/54349-new-armbian-version-which-contains-npu-driver-and-kernel-newer-than-63/</link><description><![CDATA[<p>
	Hi,
</p>

<p>
	I'm looking a newer armbian iso image which contains those futures. Is there any link? I'm going to test on Turing RK1 (RK3588) machine.
</p>

<p>
	Regards.
</p>

<p>
	 
</p>
]]></description><guid isPermaLink="false">54349</guid><pubDate>Wed, 06 Aug 2025 10:38:27 +0000</pubDate></item><item><title>How to setup shell on ttyFIQ0 debug uart port on rk3566</title><link>https://forum.armbian.com/topic/54155-how-to-setup-shell-on-ttyfiq0-debug-uart-port-on-rk3566/</link><description><![CDATA[<p>
	I have followed this <strong><a href="https://wiki.t-firefly.com/en/ROC-RK3566-PC/linux_compile_linux5.10.html" rel="external nofollow">guide</a></strong> for Firefly SDK Buildroot and I am unable to get the shell on uart2(ttyS2) or fiq-debugger port.
</p>

<p>
	I have checked multiple blogs, tickets, and forums, and edited .<abbr title="Device tree source"><abbr title="Device tree source">dts</abbr></abbr> and .dtsi to:<br />
	 
</p>

<ul>
	<li>
		Disable fiq-debugger and use uart2 as shell
	</li>
	<li>
		Disable uart2 and enable fiq-debugger (default file mode)
	</li>
	<li>
		Route fiq-debugger to uart 0x00 by editing serial ID and other configs to use uart2 (ttyS2)<br />
		 
	</li>
</ul>

<p>
	…<strong>but I am unable to get shell access on console</strong>.
</p>

<p>
	I am a beginner in this, so I apologize in advance as I feel there might be a small issue I am unable to identify.<br />
	 
</p>

<p>
	Here are the relevant files/content:<br />
	<br />
	<strong>rk3568-linux.dtsi</strong>
</p>

<pre class="ipsCode">/ {
    aliases {
        mmc0 = &amp;sdhci;
        mmc1 = &amp;sdmmc0;
        mmc2 = &amp;sdmmc1;
        mmc3 = &amp;sdmmc2;
    };

    chosen: chosen {
        bootargs = "earlycon=uart8250,mmio32,0xfe660000 console=ttyFIQ0 root=PARTUUID=614e0000-0000 rootfstype=ext4 rw rootwait rootdelay=5 debug";
        /*bootargs = "earlycon=uart8250,mmio32,0xfe660000 console=ttyS2,1500000n8 rw root=PARTUUID=614e0000-0000 rootwait";*/
    };

    fiq-debugger {
        label = "fiq-debugger-uart2";
        compatible = "rockchip,fiq-debugger";
        rockchip,serial-id = &lt;2&gt;;
        rockchip,wake-irq = &lt;0&gt;;
        /* If enable uart uses irq instead of fiq */
        rockchip,irq-mode-enable = &lt;1&gt;;
        rockchip,baudrate = &lt;1500000&gt;;  /* Only 115200 and 1500000 */
        interrupts = &lt;GIC_SPI 252 IRQ_TYPE_LEVEL_LOW&gt;;
        pinctrl-names = "default";
        pinctrl-0 = &lt;&amp;uart2m0_xfer&gt;;
        status = "okay";
    };</pre>

<p>
	 
</p>

<p>
	<strong><span style="font-size:20px;">One problem I can think of is that it's unable to mount root. Here are the logs:</span></strong>
</p>

<pre class="ipsCode prettyprint lang-html prettyprinted"><span class="pln">DDR 2d653b3476 typ 24/01/20-15:04:19,fwver: v1.21
ln
LP4/4x derate en, other dram:1x trefi
ddrconfig:0
LPDDR4X, 324MHz
BW=32 Col=10 Bk=8 CS0 Row=16 CS=1 Die BW=16 Size=2048MB
tdqss: cs0 dqs0: -24ps, dqs1: -72ps, dqs2: -72ps, dqs3: -120ps, 

change to: 324MHz
PHY drv:clk:36,ca:36,DQ:29,odt:0
vrefinner:24%, vrefout:41%
dram drv:40,odt:0
clk skew:0x62
rx vref: 32.4%
tx vref: 34.0%

change to: 528MHz
PHY drv:clk:36,ca:36,DQ:29,odt:0
vrefinner:24%, vrefout:41%
dram drv:40,odt:0
clk skew:0x58
rx vref: 32.4%
tx vref: 38.0%

change to: 780MHz
PHY drv:clk:36,ca:36,DQ:29,odt:60
vrefinner:16%, vrefout:41%
dram drv:40,odt:0
clk skew:0x58
rx vref: 15.6%
tx vref: 40.0%

change to: 1560MHz(final freq)
PHY drv:clk:36,ca:36,DQ:29,odt:60
vrefinner:16%, vrefout:22%
dram drv:40,odt:80
vref_ca:00000071
clk skew:0x2b
rx vref: 17.6%
tx vref: 21.8%
cs 0:
the read training result:
DQS0:0x31, DQS1:0x35, DQS2:0x31, DQS3:0x31, 
min  : 0x3  0x5  0x3  0x2  0x4  0x1  0x2  0x5 , 0x2  0x8  0x8  0x8  0x3  0x7  0x6  0x6 ,
       0x4  0x2  0x4  0x3  0x3  0x6  0x5  0x8 , 0x4  0x3  0x3  0x2  0x2  0x6  0x5  0x4 ,
mid  :0x1d 0x1f 0x1c 0x1c 0x1f 0x1c 0x1d 0x1e ,0x1a 0x1e 0x1e 0x1e 0x1a 0x20 0x20 0x21 ,
      0x1e 0x1d 0x1e 0x1f 0x1c 0x1f 0x1e 0x1f ,0x1c 0x1a 0x1a 0x1b 0x19 0x1d 0x21 0x1a ,
max  :0x38 0x39 0x36 0x36 0x3a 0x38 0x39 0x38 ,0x32 0x34 0x34 0x35 0x32 0x39 0x3a 0x3c ,
      0x38 0x38 0x38 0x3b 0x36 0x38 0x37 0x37 ,0x34 0x32 0x32 0x34 0x31 0x34 0x3d 0x30 ,
range:0x35 0x34 0x33 0x34 0x36 0x37 0x37 0x33 ,0x30 0x2c 0x2c 0x2d 0x2f 0x32 0x34 0x36 ,
      0x34 0x36 0x34 0x38 0x33 0x32 0x32 0x2f ,0x30 0x2f 0x2f 0x32 0x2f 0x2e 0x38 0x2c ,
the write training result:
DQS0:0x27, DQS1:0x1d, DQS2:0x1d, DQS3:0x14, 
min  :0x5f 0x60 0x5f 0x5e 0x5e 0x5d 0x5f 0x60 0x5e ,0x4e 0x52 0x50 0x51 0x50 0x53 0x53 0x52 0x4e ,
      0x57 0x54 0x55 0x56 0x53 0x55 0x53 0x55 0x55 ,0x4b 0x4c 0x4b 0x4a 0x49 0x4a 0x4c 0x4c 0x4a ,
mid  :0x77 0x79 0x78 0x76 0x78 0x76 0x77 0x79 0x76 ,0x67 0x69 0x69 0x6a 0x68 0x6c 0x6c 0x6c 0x68 ,
      0x70 0x6e 0x6f 0x70 0x6d 0x6e 0x6d 0x6e 0x6f ,0x61 0x61 0x60 0x61 0x5f 0x60 0x66 0x61 0x62 ,
max  :0x90 0x93 0x91 0x8f 0x92 0x90 0x8f 0x93 0x8f ,0x80 0x81 0x82 0x83 0x81 0x86 0x86 0x86 0x83 ,
      0x89 0x89 0x89 0x8a 0x87 0x87 0x88 0x87 0x89 ,0x78 0x77 0x76 0x78 0x76 0x77 0x81 0x76 0x7a ,
range:0x31 0x33 0x32 0x31 0x34 0x33 0x30 0x33 0x31 ,0x32 0x2f 0x32 0x32 0x31 0x33 0x33 0x34 0x35 ,
      0x32 0x35 0x34 0x34 0x34 0x32 0x35 0x32 0x34 ,0x2d 0x2b 0x2b 0x2e 0x2d 0x2d 0x35 0x2a 0x30 ,
CA Training result:
cs:0 min  :0x57 0x4e 0x57 0x45 0x56 0x44 0x4c ,0x50 0x45 0x4b 0x47 0x51 0x40 0x4f ,
cs:0 mid  :0x8f 0x91 0x8e 0x89 0x8c 0x87 0x76 ,0x88 0x87 0x87 0x87 0x88 0x81 0x77 ,
cs:0 max  :0xc7 0xd4 0xc5 0xcd 0xc3 0xcb 0xa1 ,0xc1 0xca 0xc3 0xc8 0xbf 0xc3 0xa0 ,
cs:0 range:0x70 0x86 0x6e 0x88 0x6d 0x87 0x55 ,0x71 0x85 0x78 0x81 0x6e 0x83 0x51 ,
out
U-Boot SPL board init
U-Boot SPL 2017.09-g606f72bd97a-240527 #lxh (May 30 2024 - 16:08:15), fwver: v1.14
unknown raw ID 0 0 0
unrecognized JEDEC id bytes: 00, 00, 00
Trying to boot from MMC2
MMC: no card present
mmc_init: -123, time 0
spl: mmc init failed with error: -123
Trying to boot from MMC1
SPL: A/B-slot: _a, successful: 0, tries-remain: 7
Trying fit image at 0x4000 sector
## Verified-boot: 0
## Checking atf-1 0x00040000 ... sha256(b5946ac63d...) + OK
## Checking uboot 0x00a00000 ... sha256(c843395069...) + OK
## Checking fdt 0x00b47be0 ... sha256(b3854af6ad...) + OK
## Checking atf-2 0xfdcc1000 ... sha256(b8dca786b4...) + OK
## Checking atf-3 0x0006b000 ... sha256(2f91089eb7...) + OK
## Checking atf-4 0xfdcce000 ... sha256(86ef885748...) + OK
## Checking atf-5 0xfdcd0000 ... sha256(0b2b146c60...) + OK
## Checking atf-6 0x00069000 ... sha256(a9a1e63bef...) + OK
## Checking optee 0x08400000 ... sha256(28fba8b7d7...) + OK
Jumping to U-Boot(0x00a00000) via ARM Trusted Firmware(0x00040000)
Total: 122.975/222.356 ms

INFO:    Preloader serial: 2
NOTICE:  BL31: v2.3():v2.3-645-g8cea6ab0b:cl, fwver: v1.44
NOTICE:  BL31: Built : 16:36:43, Sep 19 2023
INFO:    GICv3 without legacy support detected.
INFO:    ARM GICv3 driver initialized in EL3
INFO:    pmu v1 is valid 220114
INFO:    l3 cache partition cfg-0
INFO:    dfs DDR fsp_param[0].freq_mhz= 1560MHz
INFO:    dfs DDR fsp_param[1].freq_mhz= 324MHz
INFO:    dfs DDR fsp_param[2].freq_mhz= 528MHz
INFO:    dfs DDR fsp_param[3].freq_mhz= 780MHz
INFO:    Using opteed sec cpu_context!
INFO:    boot cpu mask: 0
INFO:    BL31: Initializing runtime services
INFO:    BL31: Initializing BL32
I/TC: 
I/TC: OP-TEE version: 3.13.0-791-g185dc3c92 #hisping.lin (gcc version 10.2.1 20201103 (GNU Toolchain for the A-profile Architecture 10.2-2020.11 (arm-10.16))) #2 Tue Apr 16 10:47:32 CST 2024 aarch64, fwver: v2.12 
I/TC: OP-TEE memory: TEEOS 0x200000 TA 0xc00000 SHM 0x200000
I/TC: Primary CPU initializing
I/TC: CRYPTO_CRYPTO_VERSION_NEW no support. Skip all algo mode check.
I/TC: Primary CPU switching to normal world boot
INFO:    BL31: Preparing for EL3 exit to normal world
INFO:    Entry point address = 0xa00000
INFO:    SPSR = 0x3c9


U-Boot 2017.09(u-boot commit id: 30d6e6f55d2b943c0910c3f69ccf4d302272ee71)(sdk version: rk356x_linux5.10_release_20241220_v1.4.0c.xml)-g30d6e6f55d-231220 #rk3566 (Jul 25 2025 - 04:23:32 -0700)

Model: Rockchip RK3568 Evaluation Board
MPIDR: 0x81000000
PreSerial: 2, raw, 0xfe660000
DRAM:  2 GiB
Sysmem: init
Relocation Offset: 7d217000
Relocation fdt: 7b9f88c8 - 7b9fece8
CR: M/C/I
Using default environment

optee api revision: 2.0
dwmmc@fe2b0000: 1, dwmmc@fe2c0000: 2, sdhci@fe310000: 0
Card did not respond to voltage select!
mmc_init: -95, time 9
switch to partitions #0, OK
mmc0(part 0) is current device
Bootdev(scan): mmc 0
MMC0: HS200, 200Mhz
PartType: EFI
TEEC: Waring: Could not find security partition
DM: v1
** Unrecognized filesystem type **
boot mode: recovery (misc)
RESC: 'recovery', blk@0x0005ec45
resource: sha256+
FIT: no signed, no conf required
DTB: rk-kernel.dtb
HASH(c): OK
I2c0 speed: 100000Hz
PMIC:  RK8090 (on=0x10, off=0x00)
vdd_logic init 900000 uV
vdd_gpu init 900000 uV
vdd_npu init 900000 uV
io-domain: OK
INFO:    ddr dmc_fsp already initialized in loader.
Could not find baseparameter partition
Model: Rockchip RK3568 EVB1 DDR4 V10 Board
MPIDR: 0x81000000
Rockchip UBOOT DRM driver version: v1.0.1
VOP have 3 active VP
vp0 have layer nr:2[1 5 ], primary plane: 5
vp1 have layer nr:3[0 2 4 ], primary plane: 4
vp2 have layer nr:1[3 ], primary plane: 3
Using display timing dts
dsi@fe060000:  detailed mode clock 132000 kHz, flags[a]
    H: 1080 1095 1097 1127
    V: 1920 1935 1937 1952
bus_format: 100e
VOP update mode to: 1080x1920p60, type: MIPI0 for VP1
VP1 set crtc_clock to 132000KHz
VOP VP1 enable Smart0[500x501-&gt;500x501@290x709] fmt[1] addr[0x7dfb8000]
final DSI-Link bandwidth: 876 Mbps x 4
edp@fe0c0000 disconnected
xfer: num: 2, addr: 0x50
xfer: num: 2, addr: 0x50
Monitor has basic audio support
Could not find baseparameter partition
hdmi@fe0a0000:  detailed mode clock 148500 kHz, flags[5]
    H: 1920 2008 2052 2200
    V: 1080 1084 1089 1125
bus_format: 2025
VOP update mode to: 1920x1080p60, type: HDMI0 for VP0
VP0 set crtc_clock to 148500KHz
VOP VP0 enable Smart1[500x501-&gt;500x501@710x289] fmt[1] addr[0x7dfb8000]
CEA mode used vic=16
final pixclk = 148500000 tmdsclk = 148500000
PHY powered down in 0 iterations
PHY PLL locked 1 iterations
PHY powered down in 0 iterations
PHY PLL locked 1 iterations
sink has audio support
hdmi_set_clk_regenerator: fs=48000Hz ftdms=148.500MHz N=6144 cts=148500
No FDT memory address configured. Default at 0x08300000
CLK: (sync kernel. arm: enter 816000 KHz, init 816000 KHz, kernel 0N/A)
  apll 1104000 KHz
  dpll 780000 KHz
  gpll 1188000 KHz
  cpll 1000000 KHz
  npll 1200000 KHz
  vpll 792000 KHz
  hpll 148500 KHz
  ppll 200000 KHz
  armclk 1104000 KHz
  aclk_bus 150000 KHz
  pclk_bus 100000 KHz
  aclk_top_high 500000 KHz
  aclk_top_low 400000 KHz
  hclk_top 150000 KHz
  pclk_top 100000 KHz
  aclk_perimid 300000 KHz
  hclk_perimid 150000 KHz
  pclk_pmu 100000 KHz
Net:   eth1: ethernet@fe010000, eth0: ethernet@fe2a0000
Hit key to stop autoboot('CTRL+C'):  0 
ANDROID: reboot reason: "recovery"
Not AVB images, AVB skip
No valid android hdr
Android image load failed
Android boot failed, error -1.
## Booting FIT Image at 0x78e6ee80 with size 0x02988a00
Fdt Ramdisk skip relocation
## Loading kernel from FIT Image at 78e6ee80 ...
   Using 'conf' configuration
## Verified-boot: 0
   Trying 'kernel' kernel subimage
     Description:  unavailable
     Type:         Kernel Image
     Compression:  uncompressed
     Data Start:   0x78e9c880
     Data Size:    36663808 Bytes = 35 MiB
     Architecture: AArch64
     OS:           Linux
     Load Address: 0x00280000
     Entry Point:  0x00280000
     Hash algo:    sha256
     Hash value:   52e85544b6ef286735dcfc1c2e290d1c3cf36129bedb96035f3fee232d62fc8c
   Verifying Hash Integrity ... sha256+ OK
## Loading ramdisk from FIT Image at 78e6ee80 ...
   Using 'conf' configuration
   Trying 'ramdisk' ramdisk subimage
     Description:  unavailable
     Type:         RAMDisk Image
     Compression:  uncompressed
     Data Start:   0x7b193a80
     Data Size:    6700451 Bytes = 6.4 MiB
     Architecture: AArch64
     OS:           Linux
     Load Address: 0x0a200000
     Entry Point:  unavailable
     Hash algo:    sha256
     Hash value:   91e0d1694a981ddb0df34381f9b38c931919c54a282185df61d8d34824ba44e5
   Verifying Hash Integrity ... sha256+ OK
   Loading ramdisk from 0x7b193a80 to 0x0a200000
## Loading fdt from FIT Image at 78e6ee80 ...
   Using 'conf' configuration
   Trying 'fdt' fdt subimage
     Description:  unavailable
     Type:         Flat Device Tree
     Compression:  uncompressed
     Data Start:   0x78e6f680
     Data Size:    184435 Bytes = 180.1 KiB
     Architecture: AArch64
     Load Address: 0x08300000
     Hash algo:    sha256
     Hash value:   ef1cdb3ec5d9ac9d9333fe87220ea8fcea1a482226a77e48aebd9565e5840a0b
   Verifying Hash Integrity ... sha256+ OK
   Loading fdt from 0x08300000 to 0x08300000
   Booting using the fdt blob at 0x08300000
   Loading Kernel Image from 0x78e9c880 to 0x00280000 ... OK
   kernel loaded at 0x00280000, end = 0x02577200
   Using Device Tree in place at 0000000008300000, end 0000000008330072
vp1 adjust cursor plane from 0 to 1
vp0, plane_mask:0x22, primary-id:5, curser-id:1
vp1 adjust cursor plane from 1 to 0
vp1, plane_mask:0x15, primary-id:4, curser-id:0
vp2, plane_mask:0x8, primary-id:3, curser-id:-1
WARNING: could not set reg FDT_ERR_BADOFFSET.
## reserved-memory:
  drm-logo@00000000: addr=7df00000 size=2e0000
  drm-cubic-lut@00000000: addr=7ff00000 size=8000
  ramoops@110000: addr=110000 size=f0000
Adding bank: 0x00200000 - 0x08400000 (size: 0x08200000)
Adding bank: 0x09400000 - 0x80000000 (size: 0x76c00000)
== DO RELOCATE == Kernel from 0x00280000 to 0x00200000
Total: 1428.11/1473.545 ms

Starting kernel ...

[    1.478776] Booting Linux on physical CPU 0x0000000000 [0x412fd050]
[    1.478800] Linux version 5.10.198 (rk3566@ubuntu) (firefly: 34d433bc5e75/2507250416) (sdk version: rk356x_linux5.10_release_20241220_v1.4.0c.xml) (aarch64-none-linux-gnu-gcc (GNU Toolchain for the A-profile Architecture 10.3-2021.07 (arm-10.29)) 10.3.1 20210621, GNU ld (GNU Toolchain for the A-profile Architecture 10.3-2021.07 (arm-10.29)) 2.36.1.20210621) #2 SMP Fri Jul 25 04:16:45 PDT 2025
[    1.480827] random: crng init done
[    1.485246] Machine model: Rockchip RK3568 EVB1 DDR4 V10 Board
[    1.520346] earlycon: uart8250 at MMIO32 0x00000000fe660000 (options '')
[    1.525703] printk: bootconsole [uart8250] enabled
[    1.527450] efi: UEFI not found.
[    1.565235] Zone ranges:
[    1.565489]   DMA      [mem 0x0000000000200000-0x000000007fffffff]
[    1.566077]   DMA32    empty
[    1.566352]   Normal   empty
[    1.566625] Movable zone start for each node
[    1.567028] Early memory node ranges
[    1.567367]   node   0: [mem 0x0000000000200000-0x00000000083fffff]
[    1.567958]   node   0: [mem 0x0000000009400000-0x000000007fffffff]
[    1.568552] Initmem setup node 0 [mem 0x0000000000200000-0x000000007fffffff]
[    1.583943] cma: Reserved 16 MiB at 0x000000007e800000
[    1.584513] psci: probing for conduit method from DT.
[    1.585000] psci: PSCIv1.1 detected in firmware.
[    1.585437] psci: Using standard PSCI v0.2 function IDs
[    1.585934] psci: Trusted OS migration not required
[    1.586397] psci: SMC Calling Convention v1.2
[    1.587184] percpu: Embedded 30 pages/cpu s83800 r8192 d30888 u122880
[    1.587906] Detected VIPT I-cache on CPU0
[    1.588324] CPU features: detected: GIC system register CPU interface
[    1.588932] CPU features: detected: Virtualization Host Extensions
[    1.589521] CPU features: detected: ARM errata 1165522, 1319367, or 1530923
[    1.590195] alternatives: patching kernel code
[    1.592350] Built 1 zonelists, mobility grouping on.  Total pages: 511496
[    1.592999] Kernel command line: storagemedia=emmc androidboot.storagemedia=emmc androidboot.mode=normal  androidboot.verifiedbootstate=orange rw rootwait earlycon=uart8250,mmio32,0xfe660000 console=ttyFIQ0 root=PARTUUID=614e0000-0000 rootfstype=ext4 comm-07/25/2025 androidboot.fwver=ddr-v1.21-2d653b3476,spl-v1.14,bl31-v1.44,bl32-v2.12,uboot--boot
[    1.596658] Dentry cache hash table entries: 262144 (order: 9, 2097152 bytes, linear)
[    1.597645] Inode-cache hash table entries: 131072 (order: 8, 1048576 bytes, linear)
[    1.598377] mem auto-init: stack:off, heap alloc:off, heap free:off
[    1.623130] Memory: 1974968K/2078720K available (18688K kernel code, 3484K rwdata, 6848K rodata, 6656K init, 592K bss, 87368K reserved, 16384K cma-reserved)
[    1.624565] SLUB: HWalign=64, Order=0-3, MinObjects=0, CPUs=4, Nodes=1
[    1.625216] ftrace: allocating 57076 entries in 223 pages
[    1.699063] ftrace: allocated 223 pages with 7 groups
[    1.699857] rcu: Hierarchical RCU implementation.
[    1.700308] rcu:     RCU event tracing is enabled.
[    1.700736] rcu:     RCU dyntick-idle grace-period acceleration is enabled.
[    1.701368] rcu:     RCU restricting CPUs from NR_CPUS=8 to nr_cpu_ids=4.
[    1.701984]     Rude variant of Tasks RCU enabled.
[    1.702413] rcu: RCU calculated value of scheduler-enlistment delay is 30 jiffies.
[    1.703125] rcu: Adjusting geometry for rcu_fanout_leaf=16, nr_cpu_ids=4
[    1.707979] NR_IRQS: 64, nr_irqs: 64, preallocated irqs: 0
[    1.710120] GICv3: GIC: Using split EOI/Deactivate mode
[    1.710623] GICv3: 320 SPIs implemented
[    1.710986] GICv3: 0 Extended SPIs implemented
[    1.711438] GICv3: Distributor has no Range Selector support
[    1.711979] GICv3: 16 PPIs implemented
[    1.712370] GICv3: CPU0: found redistributor 0 region 0:0x00000000fd460000
[    1.713125] ITS [mem 0xfd440000-0xfd45ffff]
[    1.713583] ITS@0x00000000fd440000: allocated 8192 Devices @29d0000 (indirect, esz 8, psz 64K, shr 0)
[    1.714482] ITS@0x00000000fd440000: allocated 32768 Interrupt Collections @29e0000 (flat, esz 2, psz 64K, shr 0)
[    1.715448] ITS: using cache flushing for cmd queue
[    1.716282] GICv3: using LPI property table @0x00000000029f0000
[    1.716952] GIC: using cache flushing for LPI property table
[    1.717490] GICv3: CPU0: using allocated LPI pending table @0x0000000002a00000
[    1.718229] rcu:     Offload RCU callbacks from CPUs: (none).
[    1.747595] arch_timer: cp15 timer(s) running at 24.00MHz (phys).
[    1.748186] clocksource: arch_sys_counter: mask: 0xffffffffffffff max_cycles: 0x588fe9dc0, max_idle_ns: 440795202592 ns
[    1.749207] sched_clock: 56 bits at 24MHz, resolution 41ns, wraps every 4398046511097ns
[    1.751046] Console: colour dummy device 80x25
[    1.751507] Calibrating delay loop (skipped), value calculated using timer frequency.. 48.00 BogoMIPS (lpj=80000)
[    1.752480] pid_max: default: 32768 minimum: 301
[    1.753027] Mount-cache hash table entries: 4096 (order: 3, 32768 bytes, linear)
[    1.753733] Mountpoint-cache hash table entries: 4096 (order: 3, 32768 bytes, linear)
[    1.755737] rcu: Hierarchical SRCU implementation.
[    1.756841] Platform MSI: interrupt-controller@fd440000 domain created
[    1.757947] PCI/MSI: /interrupt-controller@fd400000/interrupt-controller@fd440000 domain created
[    1.759121] EFI services will not be available.
[    1.759831] smp: Bringing up secondary CPUs ...
I/TC: Secondary CPU 1 initializing
I/TC: Secondary CPU 1 switching to normal world boot
I/TC: Secondary CPU 2 initializing
I/TC: Secondary CPU 2 switching to normal world boot
I/TC: Secondary CPU 3 initializing
I/TC: Secondary CPU 3 switching to normal world boot
[    1.761484] Detected VIPT I-cache on CPU1
[    1.761517] GICv3: CPU1: found redistributor 100 region 0:0x00000000fd480000
[    1.761535] GICv3: CPU1: using allocated LPI pending table @0x0000000002a10000
[    1.761585] CPU1: Booted secondary processor 0x0000000100 [0x412fd050]
[    1.762848] Detected VIPT I-cache on CPU2
[    1.762872] GICv3: CPU2: found redistributor 200 region 0:0x00000000fd4a0000
[    1.762886] GICv3: CPU2: using allocated LPI pending table @0x0000000002a20000
[    1.762924] CPU2: Booted secondary processor 0x0000000200 [0x412fd050]
[    1.764135] Detected VIPT I-cache on CPU3
[    1.764158] GICv3: CPU3: found redistributor 300 region 0:0x00000000fd4c0000
[    1.764172] GICv3: CPU3: using allocated LPI pending table @0x0000000002a30000
[    1.764207] CPU3: Booted secondary processor 0x0000000300 [0x412fd050]
[    1.764296] smp: Brought up 1 node, 4 CPUs
[    1.771711] SMP: Total of 4 processors activated.
[    1.772165] CPU features: detected: Privileged Access Never
[    1.772691] CPU features: detected: LSE atomic instructions
[    1.773216] CPU features: detected: User Access Override
[    1.773718] CPU features: detected: 32-bit EL0 Support
[    1.774202] CPU features: detected: Common not Private translations
[    1.774792] CPU features: detected: RAS Extension Support
[    1.775300] CPU features: detected: Data cache clean to the PoU not required for I/D coherence
[    1.776119] CPU features: detected: CRC32 instructions
[    1.776605] CPU features: detected: Speculative Store Bypassing Safe (SSBS)
[    1.777260] CPU features: detected: RCpc load-acquire (LDAPR)
[    1.804632] CPU: All CPU(s) started at EL2
[    1.806383] devtmpfs: initialized
[    1.828377] Registered cp15_barrier emulation handler
[    1.828873] Registered setend emulation handler
[    1.829471] clocksource: jiffies: mask: 0xffffffff max_cycles: 0xffffffff, max_idle_ns: 6370867519511994 ns
[    1.830425] futex hash table entries: 1024 (order: 4, 65536 bytes, linear)
[    1.831550] pinctrl core: initialized pinctrl subsystem
[    1.832560] DMI not present or invalid.
[    1.833174] NET: Registered protocol family 16
[    1.835190] DMA: preallocated 256 KiB GFP_KERNEL pool for atomic allocations
[    1.836001] DMA: preallocated 256 KiB GFP_KERNEL|GFP_DMA pool for atomic allocations
[    1.838940] Registered FIQ tty driver
[    1.839643] thermal_sys: Registered thermal governor 'fair_share'
[    1.839648] thermal_sys: Registered thermal governor 'step_wise'
[    1.840224] thermal_sys: Registered thermal governor 'user_space'
[    1.840790] thermal_sys: Registered thermal governor 'power_allocator'
[    1.841634] thermal thermal_zone1: power_allocator: sustainable_power will be estimated
[    1.843073] cpuidle: using governor menu
[    1.843716] hw-breakpoint: found 6 breakpoint and 4 watchpoint registers.
[    1.844477] ASID allocator initialised with 65536 entries
[    1.847188] ramoops: dmesg-0    0x20000@0x0000000000110000
[    1.848564] ramoops: console    0x80000@0x0000000000130000
[    1.849073] ramoops: pmsg    0x50000@0x00000000001b0000
[    1.849909] printk: console [ramoops-1] enabled
[    1.850340] pstore: Registered ramoops as persistent store backend
[    1.850924] ramoops: using 0xf0000@0x110000, ecc: 0
[    1.890274] rockchip-gpio fdd60000.gpio0: probed /pinctrl/gpio0@fdd60000
[    1.891365] rockchip-gpio fe740000.gpio1: probed /pinctrl/gpio1@fe740000
[    1.892557] rockchip-gpio fe750000.gpio2: probed /pinctrl/gpio2@fe750000
[    1.893722] rockchip-gpio fe760000.gpio3: probed /pinctrl/gpio3@fe760000
[    1.894834] rockchip-gpio fe770000.gpio4: probed /pinctrl/gpio4@fe770000
[    1.895577] rockchip-pinctrl pinctrl: probed pinctrl
[    1.919656] fiq_debugger fiq_debugger.0: IRQ fiq not found
[    1.920212] fiq_debugger fiq_debugger.0: IRQ wakeup not found
[    1.920764] fiq_debugger_probe: could not install nmi irq handler
[[    1.921420] printk: console [ttyFIQ0] enabled
    1.921420] printk: console [ttyFIQ0] enabled
[    1.922221] printk: bootconsole [uart8250] disabled
[    1.922221] printk: bootconsole [uart8250] disabled
[    1.922910] Registered fiq debugger ttyFIQ0
[    1.923596] vcc3v3_sys: supplied by dc_12v
[    1.923857] vcc5v0_sys: supplied by dc_12v
[    1.924095] vcc5v0_usb: supplied by dc_12v
[    1.924519] vcc5v0_host: supplied by vcc5v0_usb
[    1.924970] vcc5v0_otg: supplied by vcc5v0_usb
[    1.925567] vcc2v5-sys: supplied by vcc3v3_sys
[    1.925819] vcc3v3_vga: supplied by vcc3v3_sys
[    1.926073] pcie30_avdd0v9: supplied by vcc3v3_sys
[    1.926316] pcie30_avdd1v8: supplied by vcc3v3_sys
[    1.926671] vcc3v3_pcie: supplied by dc_12v
[    1.926837] vcc3v3_bu: supplied by vcc5v0_sys
[    1.928112] iommu: Default domain type: Translated 
[    1.931420] SCSI subsystem initialized
[    1.931637] usbcore: registered new interface driver usbfs
[    1.931679] usbcore: registered new interface driver hub
[    1.931717] usbcore: registered new device driver usb
[    1.931810] mc: Linux media interface: v0.10
[    1.931839] videodev: Linux video capture interface: v2.00
[    1.931915] pps_core: LinuxPPS API ver. 1 registered
[    1.931923] pps_core: Software ver. 5.3.6 - Copyright 2005-2007 Rodolfo Giometti </span><span class="tag">&lt;giometti</span><span class="pln">@</span><span class="atn">linux</span><span class="pln">.</span><span class="atn">it</span><span class="tag">&gt;</span><span class="pln">
[    1.931940] PTP clock support registered
[    1.931978] EDAC MC: Ver: 3.0.0
[    1.932856] arm-scmi firmware:scmi: SCMI Notifications - Core Enabled.
[    1.932919] arm-scmi firmware:scmi: SCMI Protocol v2.0 'rockchip:' Firmware version 0x0
[    1.934767] Advanced Linux Sound Architecture Driver Initialized.
[    1.935160] Bluetooth: Core ver 2.22
[    1.935198] NET: Registered protocol family 31
[    1.935206] Bluetooth: HCI device and connection manager initialized
[    1.935220] Bluetooth: HCI socket layer initialized
[    1.935229] Bluetooth: L2CAP socket layer initialized
[    1.935247] Bluetooth: SCO socket layer initialized
[    1.935670] rockchip-cpuinfo cpuinfo: SoC        : 35662000
[    1.935682] rockchip-cpuinfo cpuinfo: Serial        : efdfa4c53e24272c
[    1.936394] clocksource: Switched to clocksource arch_sys_counter
[    2.364285] NET: Registered protocol family 2
[    2.364457] IP idents hash table entries: 32768 (order: 6, 262144 bytes, linear)
[    2.365532] tcp_listen_portaddr_hash hash table entries: 1024 (order: 2, 16384 bytes, linear)
[    2.365574] TCP established hash table entries: 16384 (order: 5, 131072 bytes, linear)
[    2.365661] TCP bind hash table entries: 16384 (order: 6, 262144 bytes, linear)
[    2.365856] TCP: Hash tables configured (established 16384 bind 16384)
[    2.365968] UDP hash table entries: 1024 (order: 3, 32768 bytes, linear)
[    2.366002] UDP-Lite hash table entries: 1024 (order: 3, 32768 bytes, linear)
[    2.366141] NET: Registered protocol family 1
[    2.366581] RPC: Registered named UNIX socket transport module.
[    2.366592] RPC: Registered udp transport module.
[    2.366598] RPC: Registered tcp transport module.
[    2.366604] RPC: Registered tcp NFSv4.1 backchannel transport module.
[    2.367546] PCI: CLS 0 bytes, default 64
[    2.368202] Trying to unpack rootfs image as initramfs...
[    2.577996] Freeing initrd memory: 6540K
[    2.580226] rockchip-thermal fe710000.tsadc: tsadc is probed successfully!
[    2.581235] hw perfevents: enabled with armv8_cortex_a55 PMU driver, 7 counters available
[    2.585203] Initialise system trusted keyrings
[    2.585344] workingset: timestamp_bits=62 max_order=19 bucket_order=0
[    2.589409] squashfs: version 4.0 (2009/01/31) Phillip Lougher
[    2.589939] NFS: Registering the id_resolver key type
[    2.589975] Key type id_resolver registered
[    2.589984] Key type id_legacy registered
[    2.590020] ntfs: driver 2.1.32 [Flags: R/O].
[    2.590214] jffs2: version 2.2. (NAND) Â© 2001-2006 Red Hat, Inc.
[    2.590482] fuse: init (API version 7.32)
[    2.590758] SGI XFS with security attributes, no debug enabled
[    2.621789] NET: Registered protocol family 38
[    2.621822] Key type asymmetric registered
[    2.621832] Asymmetric key parser 'x509' registered
[    2.621873] Block layer SCSI generic (bsg) driver version 0.4 loaded (major 242)
[    2.621883] io scheduler mq-deadline registered
[    2.621891] io scheduler kyber registered
[    2.622565] rockchip-csi2-dphy-hw fe870000.csi2-dphy-hw: csi2 dphy hw probe successfully!
[    2.623415] rockchip-csi2-dphy csi2-dphy0: csi2 dphy0 probe successfully!
[    2.631873] rockchip-snps-pcie3-phy fe8c0000.phy: failed to find rockchip,pipe_grf regmap
[    2.635139] rk-pcie 3c0800000.pcie: invalid prsnt-gpios property in node
[    2.635528] pwm-backlight backlight: supply power not found, using dummy regulator
[    2.635974] pwm-backlight backlight1: supply power not found, using dummy regulator
[    2.636615] iep: Module initialized.
[    2.636687] mpp_service mpp-srv: ea89a0945141 author: Yandong Lin 2023-12-20 video: rockchip: mpp: fix watch dog interrupt storm issue
[    2.636698] mpp_service mpp-srv: probe start
[    2.638637] mpp_vdpu2 fdea0400.vdpu: Adding to iommu group 1
[    2.638821] mpp_vdpu2 fdea0400.vdpu: probe device
[    2.639266] mpp_vdpu2 fdea0400.vdpu: probing finish
[    2.639808] mpp_vepu2 fdee0000.vepu: Adding to iommu group 3
[    2.639983] mpp_vepu2 fdee0000.vepu: probing start
[    2.640369] mpp_vepu2 fdee0000.vepu: probing finish
[    2.641016] mpp-iep2 fdef0000.iep: Adding to iommu group 4
[    2.641182] rockchip_p3phy_rk3568_init: lock failed 0x6890000, check input refclk and power supply
[    2.641197] mpp-iep2 fdef0000.iep: probe device
[    2.641200] phy phy-fe8c0000.phy.9: phy init failed --&gt; -110
[    2.641206] rk-pcie 3c0800000.pcie: fail to init phy, err -110
[    2.641219] rk-pcie 3c0800000.pcie: phy init failed
[    2.641488] mpp-iep2 fdef0000.iep: allocate roi buffer failed
[    2.641708] mpp-iep2 fdef0000.iep: probing finish
[    2.642217] mpp_jpgdec fded0000.jpegd: Adding to iommu group 2
[    2.642398] mpp_jpgdec fded0000.jpegd: probe device
[    2.642855] mpp_jpgdec fded0000.jpegd: probing finish
[    2.644380] mpp_service mpp-srv: probe success
[    2.648948] dma-pl330 fe530000.dmac: Loaded driver for PL330 DMAC-241330
[    2.648987] dma-pl330 fe530000.dmac:     DBUFF-128x8bytes Num_Chans-8 Num_Peri-32 Num_Events-16
[    2.650760] dma-pl330 fe550000.dmac: Loaded driver for PL330 DMAC-241330
[    2.650784] dma-pl330 fe550000.dmac:     DBUFF-128x8bytes Num_Chans-8 Num_Peri-32 Num_Events-16
[    2.651545] rockchip-pvtm fde00000.pvtm: pvtm@0 probed
[    2.651675] rockchip-pvtm fde80000.pvtm: pvtm@1 probed
[    2.651779] rockchip-pvtm fde90000.pvtm: pvtm@2 probed
[    2.652375] rockchip-system-monitor rockchip-system-monitor: system monitor probe
[    2.653014] arm-scmi firmware:scmi: Failed. SCMI protocol 22 not active.
[    2.653342] Serial: 8250/16550 driver, 10 ports, IRQ sharing disabled
[    2.654375] fe6c0000.serial: ttyS8 at MMIO 0xfe6c0000 (irq = 78, base_baud = 1500000) is a 16550A
[    2.656749] rockchip-vop2 fe040000.vop: Adding to iommu group 8
[    2.666107] rockchip-vop2 fe040000.vop: [drm:vop2_bind] vp0 assign plane mask: 0x22, primary plane phy id: 5
[    2.666152] rockchip-vop2 fe040000.vop: [drm:vop2_bind] vp1 assign plane mask: 0x15, primary plane phy id: 4
[    2.666164] rockchip-vop2 fe040000.vop: [drm:vop2_bind] vp2 assign plane mask: 0x8, primary plane phy id: 3
[    2.666287] rockchip-vop2 fe040000.vop: [drm:vop2_bind] Cluster1-win0 as cursor plane for vp0
[    2.666454] rockchip-vop2 fe040000.vop: [drm:vop2_bind] Cluster0-win0 as cursor plane for vp1
[    2.666577] [drm] failed to init overlay plane Cluster0-win1
[    2.666586] [drm] failed to init overlay plane Cluster1-win1
[    2.666757] rockchip-drm display-subsystem: bound fe040000.vop (ops 0xffffffc00934e2e8)
[    2.667385] rockchip-drm display-subsystem: bound fe0c0000.edp (ops 0xffffffc00935b9f0)
[    2.667656] dwhdmi-rockchip fe0a0000.hdmi: Detected HDMI TX controller v2.11a with HDCP (DWC HDMI 2.0 TX PHY)
[    2.668168] dwhdmi-rockchip fe0a0000.hdmi: registered DesignWare HDMI I2C bus driver
[    2.668420] dwhdmi-rockchip fe0a0000.hdmi: IRQ index 1 not found
[    2.668778] rockchip-drm display-subsystem: bound fe0a0000.hdmi (ops 0xffffffc00935ce78)
[    2.668863] dw-mipi-dsi-rockchip fe060000.dsi: failed to find panel or bridge: -517
[    2.675548] cacheinfo: Unable to detect cache hierarchy for CPU 0
[    2.676181] brd: module loaded
[    2.680772] loop: module loaded
[    2.681156] zram: Added device: zram0
[    2.681384] lkdtm: No crash points registered, enable through debugfs
[    2.683977] ahci fc800000.sata: supply ahci not found, using dummy regulator
[    2.684124] ahci fc800000.sata: supply phy not found, using dummy regulator
[    2.684352] ahci fc800000.sata: supply target not found, using dummy regulator
[    2.684474] ahci fc800000.sata: forcing port_map 0x0 -&gt; 0x1
[    2.684516] ahci fc800000.sata: AHCI 0001.0300 32 slots 1 ports 6 Gbps 0x1 impl platform mode
[    2.684530] ahci fc800000.sata: flags: ncq sntf pm led clo only pmp fbs pio slum part ccc apst 
[    2.684547] ahci fc800000.sata: port 0 is not capable of FBS
[    2.685599] scsi host0: ahci
[    2.685863] ata1: SATA max UDMA/133 mmio [mem 0xfc800000-0xfc800fff] port 0x100 irq 19
[    2.688258] spi-nand spi4.0: unknown raw ID 00000000
[    2.688292] spi-nand: probe of spi4.0 failed with error -524
[    2.690563] rk_gmac-dwmac fe010000.ethernet: IRQ eth_lpi not found
[    2.690827] rk_gmac-dwmac fe010000.ethernet: supply phy not found, using dummy regulator
[    2.690970] rk_gmac-dwmac fe010000.ethernet: clock input or output? (output).
[    2.690982] rk_gmac-dwmac fe010000.ethernet: TX delay(0x4f).
[    2.690992] rk_gmac-dwmac fe010000.ethernet: RX delay(0x26).
[    2.691007] rk_gmac-dwmac fe010000.ethernet: integrated PHY? (no).
[    2.691271] rk_gmac-dwmac fe010000.ethernet: init for RGMII
[    2.691503] rk_gmac-dwmac fe010000.ethernet: User ID: 0x30, Synopsys ID: 0x51
[    2.691518] rk_gmac-dwmac fe010000.ethernet:     DWMAC4/5
[    2.691529] rk_gmac-dwmac fe010000.ethernet: DMA HW capability register supported
[    2.691538] rk_gmac-dwmac fe010000.ethernet: RX Checksum Offload Engine supported
[    2.691545] rk_gmac-dwmac fe010000.ethernet: TX Checksum insertion supported
[    2.691552] rk_gmac-dwmac fe010000.ethernet: Wake-Up On Lan supported
[    2.691614] rk_gmac-dwmac fe010000.ethernet: TSO supported
[    2.691624] rk_gmac-dwmac fe010000.ethernet: Enable RX Mitigation via HW Watchdog Timer
[    2.691633] rk_gmac-dwmac fe010000.ethernet: TSO feature enabled
[    2.691641] rk_gmac-dwmac fe010000.ethernet: Using 32 bits DMA width
[    2.827890] rk_gmac-dwmac fe2a0000.ethernet: IRQ eth_lpi not found
[    2.828216] rk_gmac-dwmac fe2a0000.ethernet: supply phy not found, using dummy regulator
[    2.828348] rk_gmac-dwmac fe2a0000.ethernet: clock input or output? (output).
[    2.828361] rk_gmac-dwmac fe2a0000.ethernet: TX delay(0x3c).
[    2.828371] rk_gmac-dwmac fe2a0000.ethernet: RX delay(0x2f).
[    2.828385] rk_gmac-dwmac fe2a0000.ethernet: integrated PHY? (no).
[    2.828645] rk_gmac-dwmac fe2a0000.ethernet: init for RGMII
[    2.828837] rk_gmac-dwmac fe2a0000.ethernet: Version ID not available
[    2.828854] rk_gmac-dwmac fe2a0000.ethernet:     DWMAC4/5
[    2.828865] rk_gmac-dwmac fe2a0000.ethernet: DMA HW capability register supported
[    2.828874] rk_gmac-dwmac fe2a0000.ethernet: Ring mode enabled
[    2.828884] rk_gmac-dwmac fe2a0000.ethernet: Using 32 bits DMA width
[    2.963581] usbcore: registered new interface driver rtl8150
[    2.963658] usbcore: registered new interface driver r8152
[    2.975181] ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver
[    2.975225] ehci-pci: EHCI PCI platform driver
[    2.975300] ehci-platform: EHCI generic platform driver
[    2.975579] phy phy-fe8b0000.usb2-phy.4: illegal mode
[    2.977627] ehci-platform fd800000.usb: EHCI Host Controller
[    2.977823] ehci-platform fd800000.usb: new USB bus registered, assigned bus number 1
[    2.977933] ehci-platform fd800000.usb: irq 20, io mem 0xfd800000
[    2.989803] ehci-platform fd800000.usb: USB 2.0 started, EHCI 1.00
[    2.989971] usb usb1: New USB device found, idVendor=1d6b, idProduct=0002, bcdDevice= 5.10
[    2.989982] usb usb1: New USB device strings: Mfr=3, Product=2, SerialNumber=1
[    2.989991] usb usb1: Product: EHCI Host Controller
[    2.989999] usb usb1: Manufacturer: Linux 5.10.198 ehci_hcd
[    2.990006] usb usb1: SerialNumber: fd800000.usb
[    2.990403] hub 1-0:1.0: USB hub found
[    2.990439] hub 1-0:1.0: 1 port detected
[    2.993109] ehci-platform fd880000.usb: EHCI Host Controller
[    2.993267] ehci-platform fd880000.usb: new USB bus registered, assigned bus number 2
[    2.993380] ehci-platform fd880000.usb: irq 22, io mem 0xfd880000
[    2.999446] ata1: SATA link down (SStatus 0 SControl 300)
[    3.006412] ehci-platform fd880000.usb: USB 2.0 started, EHCI 1.00
[    3.006579] usb usb2: New USB device found, idVendor=1d6b, idProduct=0002, bcdDevice= 5.10
[    3.006591] usb usb2: New USB device strings: Mfr=3, Product=2, SerialNumber=1
[    3.006600] usb usb2: Product: EHCI Host Controller
[    3.006607] usb usb2: Manufacturer: Linux 5.10.198 ehci_hcd
[    3.006614] usb usb2: SerialNumber: fd880000.usb
[    3.007047] hub 2-0:1.0: USB hub found
[    3.007082] hub 2-0:1.0: 1 port detected
[    3.007767] ohci_hcd: USB 1.1 'Open' Host Controller (OHCI) Driver
[    3.007807] ohci-platform: OHCI generic platform driver
[    3.008112] phy phy-fe8b0000.usb2-phy.4: illegal mode
[    3.008132] ohci-platform fd840000.usb: Generic Platform OHCI controller
[    3.008292] ohci-platform fd840000.usb: new USB bus registered, assigned bus number 3
[    3.008414] ohci-platform fd840000.usb: irq 21, io mem 0xfd840000
[    3.067205] usb usb3: New USB device found, idVendor=1d6b, idProduct=0001, bcdDevice= 5.10
[    3.067224] usb usb3: New USB device strings: Mfr=3, Product=2, SerialNumber=1
[    3.067234] usb usb3: Product: Generic Platform OHCI controller
[    3.067242] usb usb3: Manufacturer: Linux 5.10.198 ohci_hcd
[    3.067250] usb usb3: SerialNumber: fd840000.usb
[    3.067637] hub 3-0:1.0: USB hub found
[    3.067673] hub 3-0:1.0: 1 port detected
[    3.068165] ohci-platform fd8c0000.usb: Generic Platform OHCI controller
[    3.068316] ohci-platform fd8c0000.usb: new USB bus registered, assigned bus number 4
[    3.068410] ohci-platform fd8c0000.usb: irq 23, io mem 0xfd8c0000
[    3.127197] usb usb4: New USB device found, idVendor=1d6b, idProduct=0001, bcdDevice= 5.10
[    3.127217] usb usb4: New USB device strings: Mfr=3, Product=2, SerialNumber=1
[    3.127226] usb usb4: Product: Generic Platform OHCI controller
[    3.127234] usb usb4: Manufacturer: Linux 5.10.198 ohci_hcd
[    3.127241] usb usb4: SerialNumber: fd8c0000.usb
[    3.127630] hub 4-0:1.0: USB hub found
[    3.127665] hub 4-0:1.0: 1 port detected
[    3.128918] xhci-hcd xhci-hcd.0.auto: xHCI Host Controller
[    3.129110] xhci-hcd xhci-hcd.0.auto: new USB bus registered, assigned bus number 5
[    3.129236] xhci-hcd xhci-hcd.0.auto: hcc params 0x0220fe64 hci version 0x110 quirks 0x0000800002010010
[    3.129294] xhci-hcd xhci-hcd.0.auto: irq 94, io mem 0xfd000000
[    3.129415] xhci-hcd xhci-hcd.0.auto: xHCI Host Controller
[    3.129550] xhci-hcd xhci-hcd.0.auto: new USB bus registered, assigned bus number 6
[    3.129569] xhci-hcd xhci-hcd.0.auto: Host supports USB 3.0 SuperSpeed
[    3.129706] usb usb5: New USB device found, idVendor=1d6b, idProduct=0002, bcdDevice= 5.10
[    3.129750] usb usb5: New USB device strings: Mfr=3, Product=2, SerialNumber=1
[    3.129760] usb usb5: Product: xHCI Host Controller
[    3.129768] usb usb5: Manufacturer: Linux 5.10.198 xhci-hcd
[    3.129775] usb usb5: SerialNumber: xhci-hcd.0.auto
[    3.130183] hub 5-0:1.0: USB hub found
[    3.130220] hub 5-0:1.0: 1 port detected
[    3.130547] usb usb6: We don't know the algorithms for LPM for this host, disabling LPM.
[    3.130644] usb usb6: New USB device found, idVendor=1d6b, idProduct=0003, bcdDevice= 5.10
[    3.130656] usb usb6: New USB device strings: Mfr=3, Product=2, SerialNumber=1
[    3.130665] usb usb6: Product: xHCI Host Controller
[    3.130673] usb usb6: Manufacturer: Linux 5.10.198 xhci-hcd
[    3.130680] usb usb6: SerialNumber: xhci-hcd.0.auto
[    3.131025] hub 6-0:1.0: USB hub found
[    3.131058] hub 6-0:1.0: 1 port detected
[    3.131456] usbcore: registered new interface driver cdc_acm
[    3.131466] cdc_acm: USB Abstract Control Model driver for USB modems and ISDN adapters
[    3.131668] usbcore: registered new interface driver uas
[    3.131752] usbcore: registered new interface driver usb-storage
[    3.131837] usbcore: registered new interface driver usbserial_generic
[    3.131861] usbserial: USB Serial support registered for generic
[    3.131922] usbcore: registered new interface driver cp210x
[    3.131945] usbserial: USB Serial support registered for cp210x
[    3.132004] usbcore: registered new interface driver ftdi_sio
[    3.132027] usbserial: USB Serial support registered for FTDI USB Serial Device
[    3.132142] usbcore: registered new interface driver keyspan
[    3.132170] usbserial: USB Serial support registered for Keyspan - (without firmware)
[    3.132193] usbserial: USB Serial support registered for Keyspan 1 port adapter
[    3.132214] usbserial: USB Serial support registered for Keyspan 2 port adapter
[    3.132233] usbserial: USB Serial support registered for Keyspan 4 port adapter
[    3.132281] usbcore: registered new interface driver option
[    3.132305] usbserial: USB Serial support registered for GSM modem (1-port)
[    3.132460] usbcore: registered new interface driver oti6858
[    3.132483] usbserial: USB Serial support registered for oti6858
[    3.132524] usbcore: registered new interface driver pl2303
[    3.132547] usbserial: USB Serial support registered for pl2303
[    3.132594] usbcore: registered new interface driver qcserial
[    3.132617] usbserial: USB Serial support registered for Qualcomm USB modem
[    3.132672] usbcore: registered new interface driver sierra
[    3.132695] usbserial: USB Serial support registered for Sierra USB modem
[    3.133895] usbcore: registered new interface driver usbtouchscreen
[    3.134321] .. rk pwm remotectl v2.0 init
[    3.134556] input: fe6e0030.pwm as /devices/platform/fe6e0030.pwm/input/input0
[    3.134906] remotectl-pwm fe6e0030.pwm: pwm version is 0x2130000
[    3.134957] remotectl-pwm fe6e0030.pwm: Controller support pwrkey capture
[    3.135510] i2c /dev entries driver
[    3.136758] fan53555-regulator 0-001c: Failed to get chip ID!
[    3.139285] rk808 0-0020: chip id: 0x8090
[    3.139345] rk808 0-0020: No cache defaults, reading back from HW
[    3.163032] rk808 0-0020: source: on=0x10, off=0x00
[    3.163075] rk808 0-0020: support dcdc3 fb mode:-22, 1
[    3.163087] rk808 0-0020: support pmic reset mode:0,0
[    3.168518] rk808-regulator rk808-regulator: there is no dvs0 gpio
[    3.168563] rk808-regulator rk808-regulator: there is no dvs1 gpio
[    3.168979] vdd_logic: supplied by vcc3v3_sys
[    3.170003] vdd_gpu: supplied by vcc3v3_sys
[    3.170592] vcc_ddr: supplied by vcc3v3_sys
[    3.171182] vdd_npu: supplied by vcc3v3_sys
[    3.172111] vcc_1v8: supplied by vcc3v3_sys
[    3.172676] vdda0v9_image: supplied by vcc3v3_sys
[    3.174112] vdda_0v9: supplied by vcc3v3_sys
[    3.175208] vdda0v9_pmu: supplied by vcc3v3_sys
[    3.176287] vccio_acodec: supplied by vcc3v3_sys
[    3.177714] vccio_sd: supplied by vcc3v3_sys
[    3.178799] vcc3v3_pmu: supplied by vcc3v3_sys
[    3.180253] vcca_1v8: supplied by vcc3v3_sys
[    3.181361] vcca1v8_pmu: supplied by vcc3v3_sys
[    3.182441] vcca1v8_image: supplied by vcc3v3_sys
[    3.183889] vcc_3v3: supplied by vcc3v3_sys
[    3.184798] vcc3v3_sd: supplied by vcc3v3_sys
[    3.185354] rk817-battery: Failed to locate of_node [id: -1]
[    3.185507] rk817-battery rk817-battery: Failed to find matching dt id
[    3.185647] rk817-charger: Failed to locate of_node [id: -1]
[    3.185742] rk817-charger rk817-charger: Failed to find matching dt id
[    3.188764] input: rk805 pwrkey as /devices/platform/fdd40000.i2c/i2c-0/0-0020/rk805-pwrkey/input/input1
[    3.194888] rk808-rtc rk808-rtc: registered as rtc0
[    3.196613] rk808-rtc rk808-rtc: setting system clock to 2022-08-07T16:54:13 UTC (1659891253)
[    3.200010] &lt;</span><span class="tag">&lt;GTP-INF&gt;</span><span class="pln">&gt;[gt1x_ts_probe:560] GTP Driver Version: V1.4&lt;2015/07/10&gt;
[    3.200049] &lt;</span><span class="tag">&lt;GTP-INF&gt;</span><span class="pln">&gt;[gt1x_ts_probe:561] GTP I2C Address: 0x14
[    3.200117] &lt;</span><span class="tag">&lt;GTP-ERR&gt;</span><span class="pln">&gt;[gt1x_parse_dt:341] vdd_ana not specified, fallback to power-supply
[    3.200253] &lt;</span><span class="tag">&lt;GTP-INF&gt;</span><span class="pln">&gt;[gt1x_parse_dt:348] Power Invert,no 
[    3.200333] &lt;</span><span class="tag">&lt;GTP-INF&gt;</span><span class="pln">&gt;[gt1x_reset_guitar:788] GTP RESET!
[    3.201636] i2c i2c-4: 1 i2c clients have been registered at 0x36
[    3.205139] rockchip-mipi-csi2-hw fdfb0000.mipi-csi2-hw: enter mipi csi2 hw probe!
[    3.205319] rockchip-mipi-csi2-hw fdfb0000.mipi-csi2-hw: probe success, v4l2_dev:mipi-csi2-hw!
[    3.206470] rkisp_hw fdff0000.rkisp: Adding to iommu group 7
[    3.206676] rkisp_hw fdff0000.rkisp: is_thunderboot: 0
[    3.206709] rkisp_hw fdff0000.rkisp: can't request region for resource [mem 0xfdff0000-0xfdffffff]
[    3.206738] rkisp_hw fdff0000.rkisp: max input:0x0@0fps
[    3.206889] rkisp_hw fdff0000.rkisp: no find phandle sram
[    3.207393] rkisp rkisp-vir0: rkisp driver version: v02.04.00
[    3.207545] rkisp rkisp-vir0: No memory-region-thunderboot specified
[    3.207746] rkisp rkisp-vir0: Entity type for entity rkisp-isp-subdev was not initialized!
[    3.207767] rkisp rkisp-vir0: Entity type for entity rkisp-csi-subdev was not initialized!
[    3.210389] usbcore: registered new interface driver uvcvideo
[    3.210407] USB Video Class driver (1.1.1)
[    3.212050] Bluetooth: HCI UART driver ver 2.3
[    3.212068] Bluetooth: HCI UART protocol H4 registered
[    3.212075] Bluetooth: HCI UART protocol ATH3K registered
[    3.212143] usbcore: registered new interface driver bfusb
[    3.212191] usbcore: registered new interface driver btusb
[    3.213087] cpu cpu0: bin=0
[    3.213152] cpu cpu0: leakage=29
[    3.213196] cpu cpu0: pvtm = 87290, from nvmem
[    3.213212] cpu cpu0: pvtm-volt-sel=2
[    3.213263] cpu cpu0: soc version=0, speed=2
[    3.215246] sdhci: Secure Digital Host Controller Interface driver
[    3.215266] sdhci: Copyright(c) Pierre Ossman
[    3.215273] Synopsys Designware Multimedia Card Interface Driver
[    3.216053] sdhci-pltfm: SDHCI platform and OF driver helper
[    3.216557] dwmmc_rockchip fe000000.dwmmc: No normal pinctrl state
[    3.216577] dwmmc_rockchip fe000000.dwmmc: No idle pinctrl state
[    3.216695] dwmmc_rockchip fe000000.dwmmc: IDMAC supports 32-bit address mode.
[    3.216728] dwmmc_rockchip fe000000.dwmmc: Using internal DMA controller.
[    3.216741] dwmmc_rockchip fe000000.dwmmc: Version ID is 270a
[    3.216788] dwmmc_rockchip fe2b0000.dwmmc: No normal pinctrl state
[    3.216797] dwmmc_rockchip fe000000.dwmmc: DW MMC controller at irq 54,32 bit host data width,256 deep fifo
[    3.216807] dwmmc_rockchip fe2b0000.dwmmc: No idle pinctrl state
[    3.216919] dwmmc_rockchip fe2b0000.dwmmc: IDMAC supports 32-bit address mode.
[    3.216943] dwmmc_rockchip fe2b0000.dwmmc: Using internal DMA controller.
[    3.216955] dwmmc_rockchip fe2b0000.dwmmc: Version ID is 270a
[    3.216997] dwmmc_rockchip fe2b0000.dwmmc: DW MMC controller at irq 63,32 bit host data width,256 deep fifo
[    3.217190] dwmmc_rockchip fe000000.dwmmc: allocated mmc-pwrseq
[    3.217205] mmc_host mmc3: card is non-removable.
[    3.218407] arm-scmi firmware:scmi: Failed. SCMI protocol 17 not active.
[    3.218507] SMCCC: SOC_ID: ARCH_SOC_ID not implemented, skipping ....
[    3.219465] cryptodev: driver 1.12 loaded.
[    3.219527] hid: raw HID events driver (C) Jiri Kosina
[    3.219865] usbcore: registered new interface driver usbhid
[    3.219874] usbhid: USB HID core driver
[    3.225081] usbcore: registered new interface driver snd-usb-audio
[    3.227275] rk817-codec rk817-codec: DMA mask not set
[    3.227812] rk817_codec_parse_dt_property: rk809 have no io-channels defined
[    3.227832] invalid rk817-&gt;hp_det_gpio: -2
[    3.227844] invalid gpio: -2
[    3.230073] mmc_host mmc1: Bus speed (slot 0) = 375000Hz (slot req 400000Hz, actual 375000HZ div = 0)
[    3.234880] rk-multicodecs rk809-sound: Failed to get ADC channel
[    3.235080] rk-multicodecs rk809-sound: ASoC: Property 'rockchip,audio-routing' does not exist or its length is not even
[    3.236246] rk817-codec rk817-codec: rk817_probe: chip_name:0x80, chip_ver:0x94
[    3.243494] input: rockchip-rk809 Headset as /devices/platform/rk809-sound/sound/card0/input2
[    3.244686] Initializing XFRM netlink socket
[    3.245108] NET: Registered protocol family 10
[    3.245847] Segment Routing with IPv6
[    3.245913] NET: Registered protocol family 17
[    3.245936] NET: Registered protocol family 15
[    3.246066] Bluetooth: RFCOMM socket layer initialized
[    3.246102] Bluetooth: RFCOMM ver 1.11
[    3.246116] Bluetooth: HIDP (Human Interface Emulation) ver 1.2
[    3.246128] Bluetooth: HIDP socket layer initialized
[    3.246173] [BT_RFKILL]: Enter rfkill_rk_init
[    3.246182] [WLAN_RFKILL]: Enter rfkill_wlan_init
[    3.246855] [WLAN_RFKILL]: Enter rfkill_wlan_probe
[    3.246908] [WLAN_RFKILL]: wlan_platdata_parse_dt: wifi_chip_type = ap6398s
[    3.246917] [WLAN_RFKILL]: wlan_platdata_parse_dt: enable wifi power control.
[    3.246924] [WLAN_RFKILL]: wlan_platdata_parse_dt: wifi power controled by gpio.
[    3.246947] [WLAN_RFKILL]: wlan_platdata_parse_dt: WIFI,poweren_gpio = 125 flags = 0.
[    3.246968] [WLAN_RFKILL]: wlan_platdata_parse_dt: WIFI,host_wake_irq = 124, flags = 0.
[    3.246980] [WLAN_RFKILL]: wlan_platdata_parse_dt: The ref_wifi_clk not found !
[    3.246987] [WLAN_RFKILL]: rfkill_wlan_probe: init gpio
[    3.246994] [WLAN_RFKILL]: rfkill_set_wifi_bt_power: 1
[    3.247002] [WLAN_RFKILL]: Exit rfkill_wlan_probe
[    3.247783] [BT_RFKILL]: bluetooth_platdata_parse_dt: get property: uart_rts_gpios = 73.
[    3.247812] [BT_RFKILL]: bluetooth_platdata_parse_dt: get property: BT,reset_gpio = 96.
[    3.247826] [BT_RFKILL]: bluetooth_platdata_parse_dt: get property: BT,wake_gpio = 98.
[    3.247839] [BT_RFKILL]: bluetooth_platdata_parse_dt: get property: BT,wake_host_irq = 97.
[    3.247901] [BT_RFKILL]: Request irq for bt wakeup host
[    3.247997] [BT_RFKILL]: ** disable irq
[    3.248090] [BT_RFKILL]: bt_default device registered.
[    3.248218] Key type dns_resolver registered
[    3.249163] mmc0: SDHCI controller on fe310000.sdhci [fe310000.sdhci] using ADMA
[    3.249365] os04a10 4-0036: driver version: 00.01.05
[    3.249384] os04a10 4-0036:  Get hdr mode failed! no hdr default
[    3.249404] os04a10 4-0036: detect os04a10 lane 4
[    3.249551] os04a10 4-0036: could not get default pinstate
[    3.249561] os04a10 4-0036: could not get sleep pinstate
[    3.249606] os04a10 4-0036: supply avdd not found, using dummy regulator
[    3.249805] os04a10 4-0036: supply dovdd not found, using dummy regulator
[    3.249857] os04a10 4-0036: supply dvdd not found, using dummy regulator
[    3.286006] mmc0: Host Software Queue enabled
[    3.286040] mmc0: new HS200 MMC card at address 0001
[    3.286766] mmcblk0: mmc0:0001 AJTD4R 14.6 GiB 
[    3.287004] mmcblk0boot0: mmc0:0001 AJTD4R partition 1 4.00 MiB
[    3.287266] mmcblk0boot1: mmc0:0001 AJTD4R partition 2 4.00 MiB
[    3.287524] mmcblk0rpmb: mmc0:0001 AJTD4R partition 3 4.00 MiB, chardev (236:0)
[    3.289751] os04a10 4-0036: Unexpected sensor id(000000), ret(-5)
[    3.290682]  mmcblk0: p1 p2 p3 p4 p5 p6 p7 p8
[    3.293529] &lt;</span><span class="tag">&lt;GTP-ERR&gt;</span><span class="pln">&gt;[_do_i2c_write:432] I2c transfer error! (-6)
[    3.293570] &lt;</span><span class="tag">&lt;GTP-ERR&gt;</span><span class="pln">&gt;[gt1x_init:2319] Reset guitar failed!
[    3.293578] &lt;</span><span class="tag">&lt;GTP-INF&gt;</span><span class="pln">&gt;[gt1x_reset_guitar:788] GTP RESET!
[    3.321735] ov5695 4-0036-1: driver version: 00.01.04
[    3.321868] ov5695 4-0036-1: supply avdd not found, using dummy regulator
[    3.322011] ov5695 4-0036-1: supply dovdd not found, using dummy regulator
[    3.322081] ov5695 4-0036-1: supply dvdd not found, using dummy regulator
[    3.323161] ov5695 4-0036-1: Unexpected sensor id(000000), ret(-5)
[    3.323841] gc8034 4-0037: driver version: 00.01.09
[    3.323880] gc8034 4-0037: Failed to get power-gpios, maybe no use
[    3.323951] gc8034 4-0037: supply dovdd not found, using dummy regulator
[    3.324064] gc8034 4-0037: supply dvdd not found, using dummy regulator
[    3.324114] gc8034 4-0037: supply avdd not found, using dummy regulator
[    3.324157] gc8034 4-0037: lane_num(4)  pixel_rate(319887360)
[    3.324173] gc8034 4-0037: could not get default pinstate
[    3.324181] gc8034 4-0037: could not get sleep pinstate
[    3.336627] gc8034 4-0037: gc8034 read reg:0xf0 failed !
[    3.336852] gc8034 4-0037: gc8034 read reg:0xf1 failed !
[    3.336865] gc8034 4-0037: Unexpected sensor id(000000), ret(-6)
[    3.337750] Loading compiled-in X.509 certificates
[    3.339194] pstore: Using crash dump compression: deflate
[    3.340423] rga: rga2, irq = 31, match scheduler
[    3.340933] rga: rga2 hardware loaded successfully, hw_version:3.2.63318.
[    3.340965] rga: rga2 probe successfully
[    3.341300] rga_iommu: IOMMU binding successfully, default mapping core[0x4]
[    3.341557] rga: Module initialized. v1.3.1
[    3.355356] vendor storage:20190527 ret = 0
[    3.386801] &lt;</span><span class="tag">&lt;GTP-ERR&gt;</span><span class="pln">&gt;[_do_i2c_write:432] I2c transfer error! (-6)
[    3.386835] &lt;</span><span class="tag">&lt;GTP-ERR&gt;</span><span class="pln">&gt;[gt1x_init:2319] Reset guitar failed!
[    3.386844] &lt;</span><span class="tag">&lt;GTP-INF&gt;</span><span class="pln">&gt;[gt1x_reset_guitar:788] GTP RESET!
[    3.433465] mmc_host mmc3: Bus speed (slot 0) = 375000Hz (slot req 400000Hz, actual 375000HZ div = 0)
[    3.447118] mpp_rkvenc fdf40000.rkvenc: Adding to iommu group 5
[    3.447352] mpp_rkvenc fdf40000.rkvenc: probing start
[    3.447823] mpp_rkvenc fdf40000.rkvenc: bin=0
[    3.447852] mpp_rkvenc fdf40000.rkvenc: Failed to get leakage
[    3.447904] mpp_rkvenc fdf40000.rkvenc: pvtm = 87290, from nvmem
[    3.447919] mpp_rkvenc fdf40000.rkvenc: pvtm-volt-sel=1
[    3.448100] mpp_rkvenc fdf40000.rkvenc: avs=0
[    3.448219] mpp_rkvenc fdf40000.rkvenc: failed to find power_model node
[    3.448231] mpp_rkvenc fdf40000.rkvenc: failed to initialize power model
[    3.448239] mpp_rkvenc fdf40000.rkvenc: failed to get dynamic-coefficient
[    3.448975] mpp_rkvenc fdf40000.rkvenc: probing finish
[    3.449368] mpp_rkvdec2 fdf80200.rkvdec: Adding to iommu group 6
[    3.449586] mpp_rkvdec2 fdf80200.rkvdec: rkvdec, probing start
[    3.449981] mpp_rkvdec2 fdf80200.rkvdec: shared_niu_a is not found!
[    3.449994] rkvdec2_init:1022: No niu aclk reset resource define
[    3.450004] mpp_rkvdec2 fdf80200.rkvdec: shared_niu_h is not found!
[    3.450010] rkvdec2_init:1025: No niu hclk reset resource define
[    3.450221] mpp_rkvdec2 fdf80200.rkvdec: bin=0
[    3.450329] mpp_rkvdec2 fdf80200.rkvdec: leakage=54
[    3.450344] mpp_rkvdec2 fdf80200.rkvdec: leakage-volt-sel=0
[    3.450383] mpp_rkvdec2 fdf80200.rkvdec: pvtm = 87290, from nvmem
[    3.450395] mpp_rkvdec2 fdf80200.rkvdec: pvtm-volt-sel=1
[    3.450560] mpp_rkvdec2 fdf80200.rkvdec: avs=0
[    3.450685] mpp_rkvdec2 fdf80200.rkvdec: failed to find power_model node
[    3.450697] mpp_rkvdec2 fdf80200.rkvdec: failed to initialize power model
[    3.450706] mpp_rkvdec2 fdf80200.rkvdec: failed to get dynamic-coefficient
[    3.450829] mpp_rkvdec2 fdf80200.rkvdec: sram_start 0x00000000fdcc0000
[    3.450840] mpp_rkvdec2 fdf80200.rkvdec: rcb_iova 0x0000000010000000
[    3.450848] mpp_rkvdec2 fdf80200.rkvdec: sram_size 45056
[    3.450855] mpp_rkvdec2 fdf80200.rkvdec: rcb_size 65536
[    3.450864] mpp_rkvdec2 fdf80200.rkvdec: min_width 512
[    3.450916] mpp_rkvdec2 fdf80200.rkvdec: link mode probe finish
[    3.450986] mpp_rkvdec2 fdf80200.rkvdec: probing finish
[    3.452318] mali fde60000.gpu: Kernel DDK version g18p0-01eac0
[    3.452744] rockchip-dmc dmc: bin=0
[    3.452848] rockchip-dmc dmc: leakage=54
[    3.452865] rockchip-dmc dmc: leakage-volt-sel=0
[    3.452900] mali fde60000.gpu: bin=0
[    3.452921] rockchip-dmc dmc: pvtm = 87290, from nvmem
[    3.452937] rockchip-dmc dmc: pvtm-volt-sel=1
[    3.452953] mali fde60000.gpu: leakage=8
[    3.452956] rockchip-dmc dmc: soc version=0, speed=1
[    3.453000] mali fde60000.gpu: pvtm = 87290, from nvmem
[    3.453017] mali fde60000.gpu: pvtm-volt-sel=2
[    3.453031] mali fde60000.gpu: soc version=0, speed=2
[    3.453160] rockchip-dmc dmc: avs=0
[    3.453181] rockchip-dmc dmc: current ATF version 0x102
[    3.453578] mali fde60000.gpu: avs=0
[    3.453601] W : [File] : drivers/gpu/arm/bifrost/platform/rk/mali_kbase_config_rk.c; [Line] : 143; [Func] : kbase_platform_rk_init(); power-off-delay-ms not available.
[    3.453956] rockchip-dmc dmc: normal_rate = 780000000
[    3.453970] rockchip-dmc dmc: reboot_rate = 1560000000
[    3.453979] rockchip-dmc dmc: suspend_rate = 324000000
[    3.453987] rockchip-dmc dmc: video_4k_rate = 780000000
[    3.453996] rockchip-dmc dmc: video_4k_10b_rate = 780000000
[    3.454004] rockchip-dmc dmc: boost_rate = 1560000000
[    3.454012] rockchip-dmc dmc: fixed_rate(isp|cif0|cif1|dualview) = 1560000000
[    3.454020] rockchip-dmc dmc: performance_rate = 1560000000
[    3.454043] rockchip-dmc dmc: failed to get vop pn to msch rl
[    3.454056] mali fde60000.gpu: GPU identified as 0x2 arch 7.4.0 r1p0 status 0
[    3.454144] mali fde60000.gpu: No priority control manager is configured
[    3.454222] rockchip-dmc dmc: l=0 h=2147483647 hyst=5000 l_limit=0 h_limit=0 h_table=0
[    3.454421] mali fde60000.gpu: No memory group manager is configured
[    3.454831] rockchip-dmc dmc: could not find power_model node
[    3.456356] mali fde60000.gpu: l=0 h=2147483647 hyst=5000 l_limit=0 h_limit=0 h_table=0
[    3.457010] rockchip-iodomain fdc20000.syscon:io-domains: pmuio2(3300000 uV) supplied by vcc3v3_pmu
[    3.457218] rockchip-iodomain fdc20000.syscon:io-domains: vccio1(3000000 uV) supplied by vccio_acodec
[    3.457453] rockchip-iodomain fdc20000.syscon:io-domains: vccio3(3300000 uV) supplied by vccio_sd
[    3.457634] rockchip-iodomain fdc20000.syscon:io-domains: vccio4(3300000 uV) supplied by vcc_3v3
[    3.457739] rockchip-iodomain fdc20000.syscon:io-domains: vccio5(3300000 uV) supplied by vcc_3v3
[    3.457806] rockchip-iodomain fdc20000.syscon:io-domains: vccio6(3300000 uV) supplied by vcc_3v3
[    3.457871] rockchip-iodomain fdc20000.syscon:io-domains: vccio7(3300000 uV) supplied by vcc_3v3
[    3.458044] mali fde60000.gpu: Probed as mali0
[    3.462994] rockchip-vop2 fe040000.vop: [drm:vop2_bind] vp0 assign plane mask: 0x22, primary plane phy id: 5
[    3.463021] rockchip-vop2 fe040000.vop: [drm:vop2_bind] vp1 assign plane mask: 0x15, primary plane phy id: 4
[    3.463033] rockchip-vop2 fe040000.vop: [drm:vop2_bind] vp2 assign plane mask: 0x8, primary plane phy id: 3
[    3.463264] rockchip-vop2 fe040000.vop: [drm:vop2_bind] Cluster1-win0 as cursor plane for vp0
[    3.463396] rockchip-vop2 fe040000.vop: [drm:vop2_bind] Cluster0-win0 as cursor plane for vp1
[    3.463546] [drm] failed to init overlay plane Cluster0-win1
[    3.463556] [drm] failed to init overlay plane Cluster1-win1
[    3.463738] rockchip-drm display-subsystem: bound fe040000.vop (ops 0xffffffc00934e2e8)
[    3.464900] rockchip-drm display-subsystem: bound fe0c0000.edp (ops 0xffffffc00935b9f0)
[    3.465181] dwhdmi-rockchip fe0a0000.hdmi: Detected HDMI TX controller v2.11a with HDCP (DWC HDMI 2.0 TX PHY)
[    3.466067] dwhdmi-rockchip fe0a0000.hdmi: registered DesignWare HDMI I2C bus driver
[    3.466729] dwhdmi-rockchip fe0a0000.hdmi: IRQ index 1 not found
[    3.467866] input: hdmi_cec_key as /devices/platform/fe0a0000.hdmi/dw-hdmi-cec.5.auto/input/input3
[    3.468868] rockchip-drm display-subsystem: bound fe0a0000.hdmi (ops 0xffffffc00935ce78)
[    3.469037] rockchip-drm display-subsystem: bound fe060000.dsi (ops 0xffffffc00935e7d0)
[    3.471713] rockchip-drm display-subsystem: route-edp: failed to get logo,offset
[    3.507154] rockchip-vop2 fe040000.vop: [drm:vop2_isr] *ERROR* POST_BUF_EMPTY irq err at vp1
[    3.518113] &lt;</span><span class="tag">&lt;GTP-ERR&gt;</span><span class="pln">&gt;[_do_i2c_write:432] I2c transfer error! (-6)
[    3.518149] &lt;</span><span class="tag">&lt;GTP-ERR&gt;</span><span class="pln">&gt;[gt1x_init:2319] Reset guitar failed!
[    3.518158] &lt;</span><span class="tag">&lt;GTP-INF&gt;</span><span class="pln">&gt;[gt1x_reset_guitar:788] GTP RESET!
[    3.543128] usb 3-1: new full-speed USB device number 2 using ohci-platform
[    3.559594] rockchip-dp fe0c0000.edp: failed to get hpd plug in status
[    3.651673] &lt;</span><span class="tag">&lt;GTP-ERR&gt;</span><span class="pln">&gt;[_do_i2c_write:432] I2c transfer error! (-6)
[    3.651694] &lt;</span><span class="tag">&lt;GTP-ERR&gt;</span><span class="pln">&gt;[gt1x_init:2319] Reset guitar failed!
[    3.651701] &lt;</span><span class="tag">&lt;GTP-INF&gt;</span><span class="pln">&gt;[gt1x_reset_guitar:788] GTP RESET!
[    3.676482] mmc_host mmc3: Bus speed (slot 0) = 375000Hz (slot req 375000Hz, actual 375000HZ div = 0)
[    3.736884] rockchip-dp fe0c0000.edp: failed to get hpd plug in status
[    3.742027] rockchip-drm display-subsystem: [drm] fb0: rockchipdrmfb frame buffer device
[    3.743068] [drm] Initialized rockchip 3.0.0 20140818 for display-subsystem on minor 0
[    3.743657] input: adc-keys as /devices/platform/adc-keys/input/input4
[    3.752546] RKNPU fde40000.npu: Adding to iommu group 0
[    3.753045] RKNPU fde40000.npu: RKNPU: rknpu iommu is enabled, using iommu mode
[    3.753395] RKNPU fde40000.npu: can't request region for resource [mem 0xfde40000-0xfde4ffff]
[    3.753998] [drm] Initialized rknpu 0.9.3 20231121 for fde40000.npu on minor 1
[    3.754604] RKNPU fde40000.npu: bin=0
[    3.754660] RKNPU fde40000.npu: leakage=4
[    3.754700] RKNPU fde40000.npu: pvtm = 87290, from nvmem
[    3.754718] RKNPU fde40000.npu: pvtm-volt-sel=2
[    3.754734] RKNPU fde40000.npu: soc version=0, speed=2
[    3.755313] RKNPU fde40000.npu: avs=0
[    3.755486] RKNPU fde40000.npu: l=0 h=2147483647 hyst=5000 l_limit=0 h_limit=0 h_table=0
[    3.756011] RKNPU fde40000.npu: failed to find power_model node
[    3.756025] RKNPU fde40000.npu: RKNPU: failed to initialize power model
[    3.756033] RKNPU fde40000.npu: RKNPU: failed to get dynamic-coefficient
[    3.757133] cfg80211: Loading compiled-in X.509 certificates for regulatory database
[    3.763131] cfg80211: Loaded X.509 cert 'sforshee: 00b28ddf47aef9cea7'
[    3.765086] I : [File] : drivers/gpu/arm/mali400/mali/linux/mali_kernel_linux.c; [Line] : 406; [Func] : mali_module_init(); svn_rev_string_from_arm of this mali_ko is '', rk_ko_ver is '5', built at '00:56:26', on 'Jul 25 2025'.
[    3.765548] Mali: 
[    3.765551] Mali device driver loaded
[    3.765579] rkisp rkisp-vir0: clear unready subdev num: 3
[    3.765794] platform regulatory.0: Direct firmware load for regulatory.db failed with error -2
[    3.765808] cfg80211: failed to load regulatory.db
[    3.766203] rkisp-vir0: update sensor failed
[    3.768214] vÏ
[    3.774529] usb 3-1: New USB device found, idVendor=046d, idProduct=c534, bcdDevice=29.01
[    3.774550] usb 3-1: New USB device strings: Mfr=1, Product=2, SerialNumber=0
[    3.774560] usb 3-1: Product: USB Receiver
[    3.774568] usb 3-1: Manufacturer: Logitech
[    3.783435] input: Logitech USB Receiver as /devices/platform/fd840000.usb/usb3/3-1/3-1:1.0/0003:046D:C534.0001/input/input5
[    3.785369] &lt;</span><span class="tag">&lt;GTP-ERR&gt;</span><span class="pln">&gt;[_do_i2c_write:432] I2c transfer error! (-6)
[    3.785392] &lt;</span><span class="tag">&lt;GTP-ERR&gt;</span><span class="pln">&gt;[gt1x_init:2319] Reset guitar failed!
[    3.785400] &lt;</span><span class="tag">&lt;GTP-ERR&gt;</span><span class="pln">&gt;[gt1x_init:2345] Init failed, use default setting
[    3.840514] hid-generic 0003:046D:C534.0001: input,hidraw0: USB HID v1.11 Keyboard [Logitech USB Receiver] on usb-fd840000.usb-1/input0
[    3.845995] input: Logitech USB Receiver Mouse as /devices/platform/fd840000.usb/usb3/3-1/3-1:1.1/0003:046D:C534.0002/input/input6
[    3.870375] &lt;</span><span class="tag">&lt;GTP-ERR&gt;</span><span class="pln">&gt;[_do_i2c_read:390] I2c Transfer error! (-6)
[    3.870400] &lt;</span><span class="tag">&lt;GTP-ERR&gt;</span><span class="pln">&gt;[gt1x_get_chip_type:895] I2c communication error.
[    3.870409] &lt;</span><span class="tag">&lt;GTP-ERR&gt;</span><span class="pln">&gt;[gt1x_init:2355] Get chip type failed!</span></pre>

<p>
	 
</p>
]]></description><guid isPermaLink="false">54155</guid><pubDate>Mon, 28 Jul 2025 12:40:04 +0000</pubDate></item><item><title>New Here&#x2014;Just Saying Hi from Poland!</title><link>https://forum.armbian.com/topic/53940-new-here%E2%80%94just-saying-hi-from-poland/</link><description><![CDATA[<p>
	Hi Armbian folks,
</p>

<p>
	I’m new to the forum and joined today (07:42 PM CEST, July 20, 2025). I’ve recently started playing around with single-board computers, like an Orange Pi 5 I set up with Armbian a while back—it’s been a fun challenge! I’m based in Poland and enjoy tinkering with tech in my spare time.
</p>

<p>
	I’d love to hear what brings you all here—any cool hobbies or projects you’re working on? I’m thinking of trying something simple like a media server or smart home setup, but I’m open to ideas. What do you enjoy doing with your SBCs or other gear?
</p>

<p>
	Looking forward to chatting with you!
</p>
]]></description><guid isPermaLink="false">53940</guid><pubDate>Sun, 20 Jul 2025 17:44:07 +0000</pubDate></item><item><title>Hiii</title><link>https://forum.armbian.com/topic/53892-hiii/</link><description><![CDATA[<p>
	Hii this is my first post 
</p>
]]></description><guid isPermaLink="false">53892</guid><pubDate>Fri, 18 Jul 2025 18:12:27 +0000</pubDate></item><item><title>Armbian Forum GitHub Signin ?</title><link>https://forum.armbian.com/topic/52144-armbian-forum-github-signin/</link><description><![CDATA[<p>
	Why can I not sign in with GitHub ?
</p>
]]></description><guid isPermaLink="false">52144</guid><pubDate>Mon, 26 May 2025 22:05:44 +0000</pubDate></item><item><title>Wifi Performance Benchmark test</title><link>https://forum.armbian.com/topic/5246-wifi-performance-benchmark-test/</link><description><![CDATA[<p>
	I have seen many Wifi Benchmarks for speed only and not for reliability.
</p>

<p>
	I stopped doing wifi benchmarks for speed since i get very different values for the same board a few hours later,.
</p>

<p>
	For real life projects reliability and availability is what matters when you depends solely in wifi network.
</p>

<p>
	I would strongly suggest <a contenteditable="false" data-ipshover="" data-ipshover-target="https://forum.armbian.com/index.php?/profile/7-tkaiser/&amp;do=hovercard" data-mentionid="7" href="https://forum.armbian.com/index.php?/profile/7-tkaiser/" rel="">@tkaiser</a> to include "reliability" in his tests, maybe a new thread.
</p>

<p>
	As for example  you can try <strong>iperf</strong> with -<strong>t 1000</strong>, <strong>-t 2000, -t 3000 and <span style="font-size:14px;">-t 10000</span></strong> (if it allows?).
</p>

<p>
	Try this with your board and see what happens...
</p>
]]></description><guid isPermaLink="false">5246</guid><pubDate>Sat, 23 Sep 2017 13:07:49 +0000</pubDate></item><item><title>For sale: Kobol Helios64 battery backup</title><link>https://forum.armbian.com/topic/52999-for-sale-kobol-helios64-battery-backup/</link><description><![CDATA[<p>
	Hi all,
</p>

<p>
	If anyone is interested, I have a Helios64 backup battery pack lying around that I did order back in the day, but never got around to installing/using it. (Have a separate UPS.) From my guess this thing is &lt;6 years old, but again, never seen any charge or discharge.
</p>

<p>
	PM me when interested.
</p>

<p>
	Groetjes,
</p>

<p>
	 
</p>

<p>
	PS Available for pickup in the San Jose, Bay Area, CA (USA) or can send domestically thru USPS.
</p>
]]></description><guid isPermaLink="false">52999</guid><pubDate>Tue, 17 Jun 2025 21:20:03 +0000</pubDate></item><item><title>Kobol Helios 64 for sale</title><link>https://forum.armbian.com/topic/52918-kobol-helios-64-for-sale/</link><description><![CDATA[<p>
	Selling a fully working Helios64 NAS from Kobol. It has been running continuously since purchase without any issues.<br />
	Includes 4x Western Digital Red 4TB HDDs (16TB total), all in good health and used only in this setup.
</p>

<p>
	All original parts are included: case, power supply, cables, and accessories.<br />
	Note: the 1GbE Ethernet fix has not been applied.
</p>

<p>
	 
</p>

<p>
	Selling because I recently upgraded to a new NAS.
</p>

<p>
	Located in the Netherlands.
</p>

<p>
	 
</p>

<p>
	Pickup possible or shipping within the EU.
</p>

<p>
	Contact me for pricing or questions.
</p>
]]></description><guid isPermaLink="false">52918</guid><pubDate>Sun, 15 Jun 2025 14:09:39 +0000</pubDate></item><item><title>SBC recommendation for a small server?</title><link>https://forum.armbian.com/topic/52736-sbc-recommendation-for-a-small-server/</link><description><![CDATA[<p>
	In one post here I saw a <em>"please buy hardware we recommend"</em> quote, and I appreciate that, but I wasn't able to find a recommended boards list - is there even one? Or should I just use the standard/platinum support filtering on the main page?
</p>

<p>
	 
</p>

<p>
	Anyway, I could also use some help / recommendation for a general purpose <abbr title="Single board computer">SBC</abbr> as I ... didn't by one for years. I'm looking for a more recent <abbr title="Single board computer">SBC</abbr> to run a small, low power server (think pihole, homeassistant, zigbee, etc). I don't have specific requirements, but I'd like the board to have some kind of "long term support" and I'd also like to choose something that the armbian team would recommend, maybe from a manufacturer that supports armbian directly, or at least provides good documentation. Headless install, may use <abbr title="General purpose input/output">GPIO</abbr>, at least 3 USB ports, built-in ethernet + wifi + BT (not sure if there's an <abbr title="Single board computer">SBC</abbr> that would support zigbee natively?). And also, avoid using an SD card. Ability to use <abbr title="embedded MultiMediaCard">eMMC</abbr> or SSD would be important.
</p>

<p>
	 
</p>

<p>
	Where I'm coming from: I still run two first-gen Raspberry Pis as webcams + dataloggers (the 26 pin <abbr title="General purpose input/output">GPIO</abbr> ones with 256 and 512 MB RAM respectively) and I used OrangePi One and Lite as two surprisingly stable servers for years (one a small postfix mailserver + datalogger, the other even running 4 docker containers). I like using low-level hardware to its limits<span><span class="ipsEmoji">🙂</span></span> I have recently upgraded to an already outdated OrangePi PC+ that I found in the drawer - at least it has 1 GB of RAM and I was starting running into limits with the 512 MB ones. So yeah - I don't need the top of the range <abbr title="Single board computer">SBC</abbr> but something ... reasonably priced (think ~40 €) that will run well for years to come. I heard good stuff about the Radxa boards with Rockchip SoCs but I have no experience as I haven't bought new SBCs in ... years. Thanks in advance <span><span class="ipsEmoji">🙂</span> </span>
</p>
]]></description><guid isPermaLink="false">52736</guid><pubDate>Mon, 09 Jun 2025 15:55:52 +0000</pubDate></item><item><title>Orange-Pi 3B, how to transfer from sd card to nvme</title><link>https://forum.armbian.com/topic/52162-orange-pi-3b-how-to-transfer-from-sd-card-to-nvme/</link><description><![CDATA[<p>
	Please help, I've tried everything.
</p>
]]></description><guid isPermaLink="false">52162</guid><pubDate>Tue, 27 May 2025 08:32:01 +0000</pubDate></item><item><title>Armbian uses PIRACY TRACKERS to distribute images????????</title><link>https://forum.armbian.com/topic/51886-armbian-uses-piracy-trackers-to-distribute-images/</link><description><![CDATA[<p>
	WOW, I was really unhappy when I saw this, just goes to show you not to trust even projects like ARMBIAN on where they will connect to from your network,  advise before anyone finds themselves in trouble having to explain why some of these connections.....
</p>

<p>
	 
</p>

<p>
	I was downloading Armbian image and then got a warning that I couldn't connect to site called "FOREVER PIRATES" and became concerned...
</p>

<p>
	 
</p>

<p>
	You can read it yourself...
</p>

<p>
	 
</p>

<p>
	<a href="https://imgur.com/a/IQyzlvr" rel="external nofollow">https://imgur.com/a/IQyzlvr</a>
</p>

<p>
	<a class="ipsAttachLink ipsAttachLink_image" href="https://forum.armbian.com/uploads/monthly_2025_05/Screenshot2025-05-10081110.png.32bcb5d1b7cc8044ee53e0b7a897a170.png" data-fileid="14469" data-fileext="png" rel=""><img alt="Screenshot 2025-05-10 081110.png" class="ipsImage ipsImage_thumbnailed" data-fileid="14469" data-ratio="53.8" width="1000" src="https://forum.armbian.com/uploads/monthly_2025_05/Screenshot2025-05-10081110.thumb.png.6d7bc42d7bef1b0ff5d926094d3610f3.png" /></a>
</p>

<p>
	<a class="ipsAttachLink ipsAttachLink_image" href="https://forum.armbian.com/uploads/monthly_2025_05/Screenshot2025-05-10081131.png.10466ab8354205ef6367287a87fbd02a.png" data-fileid="14470" data-fileext="png" rel=""><img alt="Screenshot 2025-05-10 081131.png" class="ipsImage ipsImage_thumbnailed" data-fileid="14470" data-ratio="53.8" width="1000" src="https://forum.armbian.com/uploads/monthly_2025_05/Screenshot2025-05-10081131.thumb.png.ca8811b1eb883d69abeeadfa0fe36e26.png" /></a>
</p>
]]></description><guid isPermaLink="false">51886</guid><pubDate>Sat, 10 May 2025 15:12:55 +0000</pubDate></item><item><title>What are we running as routers / firewalls these days?</title><link>https://forum.armbian.com/topic/51043-what-are-we-running-as-routers-firewalls-these-days/</link><description><![CDATA[<p>
	I’ve been rocking a Solidrun clearfog base with Armbian for ~10 years now as my home router and was very happy with it until a few months ago when the newer software updates began to break it. I think the software support is beginning to rot due to not many users and thus no push to maintain it. I figure it’s time to start looking for a replacement.
</p>

<p>
	 
</p>

<p>
	I have a Rock 5 ITX that could do it but I’ve been trying to keep it on the vendor kernel so it can transcode in hardware for Jellyfin - but that vendor kernel has issues reliably detecting the SATA controllers - and I don’t want to have to reboot my router multiple times to get the hardware to work after applying updates.
</p>

<p>
	 
</p>

<p>
	i also just got a Radxa Orion o6 which is awesome hardware but still quite raw. I don’t trust it for a router and it’d be overkill anyways.
</p>

<p>
	 
</p>

<p>
	And I have some stupidly powerful x64 systems that eat a bunch of power but are otherwise up to the task. But I don’t want to go that way.
</p>

<p>
	 
</p>

<p>
	What do you use these days for affordable, performant, and low power routers? At least two gbe ports (10g or multigig preferred), enough CPU to NAT and forward for 500m/30m cable connection, and handle wireguard at a good clip. Preferred serial console … support for Debian / Armbian. I don’t care about a <abbr title="Graphic processing unit (3D acceleration)">GPU</abbr>. What do people use these days?
</p>
]]></description><guid isPermaLink="false">51043</guid><pubDate>Fri, 11 Apr 2025 03:30:37 +0000</pubDate></item><item><title>Recommendations for small/cheap SBC with integrated CAN.</title><link>https://forum.armbian.com/topic/50906-recommendations-for-smallcheap-sbc-with-integrated-can/</link><description><![CDATA[<p>
	So,
</p>

<p>
	 
</p>

<p>
	For a project I'm looking into a logger/monitor <abbr title="Single board computer">SBC</abbr> attached to an automotive device with CAN bus to solve customer issues more easily.
</p>

<p>
	I rather not fuzz around with (deeply) embedded stuff and keep options open (e.g. wireless connectivity/sensors). Like the old and trusty H3, preferably low-voltage, cheap and stable, no AI required or Armbian support.
</p>

<p>
	 
</p>

<p>
	Any recommendations?
</p>
]]></description><guid isPermaLink="false">50906</guid><pubDate>Fri, 04 Apr 2025 16:36:07 +0000</pubDate></item><item><title>Is ARMBian kernel customisation backported to the main line ?</title><link>https://forum.armbian.com/topic/50879-is-armbian-kernel-customisation-backported-to-the-main-line/</link><description><![CDATA[<p>
	Hello,
</p>

<p>
	 
</p>

<p>
	If I compile the mainline kernel after a
</p>

<pre class="ipsCode prettyprint lang-html prettyprinted"><span class="pln">make -j2 Bananapi_defconfig</span></pre>

<p>
	Will I get a suitable kernel or am I obliged to use ARMbian build script ?
</p>

<p>
	 
</p>

<p>
	The question behind is, I'm testing Arch on several (unsupported) SBCs at customers requests, and 
</p>

<ul>
	<li>
		on the BananaPI-M1, the HDMI is not working, 
	</li>
	<li>
		on the OrangePI PC2, both the network and <abbr title="embedded MultiMediaCard">eMMC</abbr> don't work. Obviously, everything is perfectly working on my ARMbian boxes <span class="ipsEmoji">😄</span>
	</li>
</ul>

<p>
	 
</p>

<p>
	Thanks
</p>
]]></description><guid isPermaLink="false">50879</guid><pubDate>Wed, 02 Apr 2025 17:29:58 +0000</pubDate></item><item><title>Odroid XU4</title><link>https://forum.armbian.com/topic/50781-odroid-xu4/</link><description><![CDATA[<p>
	I have an odroid xu4 and want to thank you for the great work ...
</p>

<p>
	 
</p>

<pre class="ipsCode prettyprint lang-html prettyprinted"><span class="pln">    _             _    _
   /_\  _ _ _ __ | |__(_)__ _ _ _
  / _ \| '_| '  \| '_ \ / _` | ' \
 /_/ \_\_| |_|_|_|_.__/_\__,_|_||_|

 v25.2.2 for Odroid XU4 running Armbian Linux 6.6.75-current-odroidxu4

 Packages:     Debian stable (bookworm)
 IP addresses: (LAN) IPv4: 192.168.178.24 IPv6: fd0b:5278:d32e:0:1d4d:933a:afcc:c02 (WAN) 188.136.105.135

 Performance:

 Load:         1%               Up time:       27 days 5:26
 Memory usage: 4% of 1.94G
 CPU temp:     47°C              Usage of /:   5% of 29G
storage/:      3% of 234G

 Tips:

 Support our crowdfunding project
 https://forum.armbian.com/crowdfunding/project/16-help-armbian-grow-support-joi
 n-our-team/

 Commands:</span></pre>

<p>
	 
</p>

<p>
	Danke ...
</p>
]]></description><guid isPermaLink="false">50781</guid><pubDate>Fri, 28 Mar 2025 08:45:25 +0000</pubDate></item><item><title>Selling Kobol Helios64</title><link>https://forum.armbian.com/topic/45391-selling-kobol-helios64/</link><description><![CDATA[<p>
	Hey all,
</p>

<p>
	 
</p>

<p>
	Selling my Helios64 as I've recently upgraded my server if anyone is looking.
</p>

<p>
	 
</p>

<p>
	Fully built, original condition with all drive bays and screws. Sadly no original packaging, seem to have discarded that for some reason and it has been sitting in direct sunlight so has a slither of fading on the top but still working away fine up until a few days ago.
</p>

<p>
	 
</p>

<p>
	Drop me a PM if you're interested or are looking to get some pics. Given it's size and weight I'd only be looking to ship this within the UK, possibly mainland Europe at a push.
</p>

<p>
	 
</p>

<p>
	Thanks <span><img alt=":)" data-emoticon="" height="20" src="https://forum.armbian.com/uploads/emoticons/default_smile.png" srcset="https://forum.armbian.com/uploads/emoticons/smile@2x.png 2x" title=":)" width="20" /></span>
</p>
]]></description><guid isPermaLink="false">45391</guid><pubDate>Fri, 20 Sep 2024 18:59:50 +0000</pubDate></item><item><title>Identifying RAM Part Number / Names</title><link>https://forum.armbian.com/topic/50090-identifying-ram-part-number-names/</link><description><![CDATA[<p>
	For example, what is the name of the two 2GB DDR 4 ram on the<strong> nanopi neo3 board?</strong>
</p>

<p>
	 
</p>

<p>
	<img alt="neo3.png" class="ipsImage" data-ratio="35.89" height="323" width="900" src="https://i.postimg.cc/rwXMxDKr/neo3.png" />
</p>

<p>
	 
</p>

<p>
	<img alt="neo33.png" class="ipsImage" data-ratio="67.80" height="529" width="1000" src="https://i.postimg.cc/pLdjgVfy/neo33.png" />
</p>
]]></description><guid isPermaLink="false">50090</guid><pubDate>Wed, 26 Feb 2025 14:58:40 +0000</pubDate></item><item><title>Kobol Helios64 for sale (Germany)</title><link>https://forum.armbian.com/topic/50063-kobol-helios64-for-sale-germany/</link><description><![CDATA[<p>
	I'm selling my Helios 64 with original box and small parts. Apart from a few attempts, it's basically a new one. The modification for the network interface was made. If you interested please send me a PM.
</p>

<p>
	 
</p>

<p>
	Thanks
</p>
]]></description><guid isPermaLink="false">50063</guid><pubDate>Tue, 25 Feb 2025 18:33:23 +0000</pubDate></item><item><title>Armbian forum email confirmation error</title><link>https://forum.armbian.com/topic/49986-armbian-forum-email-confirmation-error/</link><description><![CDATA[<p>
	I logged in to the Armbian forums today, for the first time in a long time.
</p>

<p>
	 
</p>

<p>
	I got a message that I had to confirm my email. I didn't capture a screenshot and the screen is now gone.
</p>

<p>
	 
</p>

<p>
	I promptly received an email, subject: We've Missed You! Your Account is Active Again. This had some details of my recent access and: "If this was you, please ignore this email. Otherwise, you should secure your account immediately."
</p>

<p>
	 
</p>

<p>
	There was a button: Review Activity &amp; Secure Account. I clicked that button. A page opened with the message: Oops! The page you are trying to access is not available to guests, but may be available if you sign in.
</p>

<p>
	 
</p>

<p>
	I went back to the page that I got when I tried to login, telling me a confirmation email had been sent. At the bottom was a link to resend the confirmation email. I clicked that and this time I promptly got an email with subject: Please confirm your email address change. It had a button: Confirm this address. I clicked it and was then logged in.
</p>

<p>
	 
</p>

<p>
	So, I got in, but it was a bit roundabout. When I first logged in and got the page indicating I need to confirm my email, it seems the email confirmation email wasn't sent. The welcome back email advising of recent activity was fine, except that the button in it went to a non-existent page. The button URL, slightly redacted, was: <a href="https://forum.armbian.com/index.php?app=core&amp;module=system&amp;controller=redirect&amp;url=https://forum.armbian.com/settings/devices/&amp;key=7bf9da8ce073f8a229581159983ea0985f15b7b6e061339ed3bc8dd6b49000ce&amp;email=1&amp;type=loginAfterInactivity" rel="">https://forum.armbian.com/index.php?app=core&amp;module=system&amp;controller=redirect&amp;url=https://forum.armbian.com/settings/devices/&amp;key=**********&amp;email=1&amp;type=loginAfterInactivity</a>. The Resend confirmation email link on the initial page after login worked fine. So, a couple of minor problems with the forum authentication.
</p>

<p>
	 
</p>

<p>
	I looked through the forums and none looked appropriate to an issue with the forums themselves, so I have posted here. Apologies if it is off topic for the off topic forum <span class="ipsEmoji">😉</span> Please let me know if there is a better way to get this to the attention of those managing the forums. On the other hand, it is only a minor issue and there are probably more important / valuable things to do, so no worries if this stays as-is.
</p>

<p>
	 
</p>

<p>
	Regards,<br />
	Ian
</p>
]]></description><guid isPermaLink="false">49986</guid><pubDate>Sat, 22 Feb 2025 06:02:35 +0000</pubDate></item><item><title>Building Kernel Module for 6.1.99 Fails</title><link>https://forum.armbian.com/topic/49881-building-kernel-module-for-6199-fails/</link><description><![CDATA[
<div class="ipsMargin_top">
    
    
    
</div><p>
	Downloaded the latest build<br />
	Armbian_25.2.1_Orangepi5_bookworm_vendor_6.1.99_minimal.img
</p>

<p>
	 
</p>

<p>
	Cloned the git repo for rtl88x2bu
</p>

<p>
	Built the new module with
</p>

<p>
	 
</p>

<p>
	cd /usr/src/linux-headers-6.1.99-vendor-rk35xx/arch/
</p>

<p>
	ln -s arm64 aarch64
</p>

<p>
	cd /rtl88x2bu<br />
	make KVER=6.1.99-vendor-rk35xx -j8<br />
	make KVER=6.1.99-vendor-rk35xx install<br />
	<br />
	modprobe 88x2bu.ko<br />
	<br />
	Looked at dmesg, and I see that it gives a message that the kernel is tainted and the module will not load.   No working wifi.   This same procedure worked fine with the 6.1.75 kernel of a previous release.
</p>
]]></description><guid isPermaLink="false">49881</guid><pubDate>Mon, 17 Feb 2025 20:46:45 +0000</pubDate></item><item><title>How to hard reset ARMbian on STB HG680P</title><link>https://forum.armbian.com/topic/49893-how-to-hard-reset-armbian-on-stb-hg680p/</link><description><![CDATA[<p>
	So first I want to change my Armbian STB IP settings to Static with the command
</p>

<p>
	<br />
	source /etc/network/interfaces.d/*
</p>

<p>
	 
</p>

<p>
	#Network is managed by Network manager
</p>

<p>
	#auto lo
</p>

<p>
	#iface lo inet loopback
</p>

<p>
	 
</p>

<p>
	auto eth0
</p>

<p>
	iface eth0 inet static
</p>

<p>
	             address 10.10.10.10
</p>

<p>
	             subnetmask 255.255.255.0
</p>

<p>
	             gateway 10.10.10.1
</p>

<p>
	             broadcast 10.10.10.255
</p>

<p>
	             hwaddess ether MAC Address
</p>

<p>
	 
</p>

<p>
	and i save the setting when i reboot the config i cant access the IP address in SSH nor CasaOS Web UI. i need help
</p>

<p>
	 
</p>

<p>
	 
</p>
]]></description><guid isPermaLink="false">49893</guid><pubDate>Tue, 18 Feb 2025 10:48:49 +0000</pubDate></item><item><title>Kudos to the Armbian team  :)</title><link>https://forum.armbian.com/topic/49255-kudos-to-the-armbian-team/</link><description><![CDATA[<p>
	I can't even imagine the amount of work involved on both sides of the (debian) development fence, as well as the admins, mods, community contributors, ..., here, that help make <strong>Armbian</strong> a viable <abbr title="Single board computer"><abbr title="Single board computer">SBC</abbr></abbr> (ARM) whatever OS. -and here's to RISC-*, and let it not be too encumbered. <img alt=";)" data-emoticon="" height="20" src="https://forum.armbian.com/uploads/emoticons/default_wink.png" srcset="https://forum.armbian.com/uploads/emoticons/wink@2x.png 2x" title=";)" width="20" />
</p>

<p>
	My "Armbian_24.11.1_Odroidc4_noble_current_6.6.60-kisak.img" works very well on my lowly Odroid-C4.
</p>

<p>
	I don't know your names, but
</p>

<p>
	Thankyou all. <span><img alt=":)" data-emoticon="" height="20" src="https://forum.armbian.com/uploads/emoticons/default_smile.png" srcset="https://forum.armbian.com/uploads/emoticons/smile@2x.png 2x" title=":)" width="20" /></span>
</p>

<p>
	 
</p>
]]></description><guid isPermaLink="false">49255</guid><pubDate>Sat, 11 Jan 2025 14:23:20 +0000</pubDate></item><item><title>As a new member I want suggestion</title><link>https://forum.armbian.com/topic/45854-as-a-new-member-i-want-suggestion/</link><description><![CDATA[<p>
	Hey everyone,
</p>

<p>
	 
</p>

<p>
	I am  a tech lover with a passion for single board computers &amp; opensource projects. I want to exploring the capabilities of Armbian and want to share insights on optimizing performance for various applications.
</p>

<p>
	I want to learn as well as start my own conversation to answer my question and learn more.
</p>

<p>
	If there are any posts or resources that are suggested for new users. Please share with me.
</p>

<p>
	I am grateful. <span class="ipsEmoji">😊</span><br />
	 
</p>
]]></description><guid isPermaLink="false">45854</guid><pubDate>Sat, 05 Oct 2024 12:00:23 +0000</pubDate></item><item><title>Upstream support for Rockchip's RK3588: Progress and future plans</title><link>https://forum.armbian.com/topic/48542-upstream-support-for-rockchips-rk3588-progress-and-future-plans/</link><description><![CDATA[<p>
	See <a href="https://www.collabora.com/news-and-blog/news-and-events/rockchip-rk3588-upstream-support-progress-future-plans.html" rel="external nofollow">https://www.collabora.com/news-and-blog/news-and-events/rockchip-rk3588-upstream-support-progress-future-plans.html</a>
</p>
]]></description><guid isPermaLink="false">48542</guid><pubDate>Mon, 23 Dec 2024 20:49:45 +0000</pubDate></item><item><title>Wireguard DNS assist please</title><link>https://forum.armbian.com/topic/47960-wireguard-dns-assist-please/</link><description><![CDATA[<p>
	Hi all,
</p>

<p>
	seeking some assistance kinder stuck on this.
</p>

<p>
	So i have managed to install it on Rocky Linux 9 ok with "dnf install wireguard-tools" configured it fine and upto nearly last step however stuck here trying to start with "systemctl start <abbr title="Wireguard">wg</abbr>-quick@wg0"
</p>

<p>
	getting this error:
</p>

<p>
	[root@localhost ~]# sudo systemctl start <abbr title="Wireguard">wg</abbr>-quick@wg0<br />
	Job for <abbr title="Wireguard">wg</abbr>-quick@wg0.service failed because the control process exited with error code.<br />
	See "systemctl status <abbr title="Wireguard">wg</abbr>-quick@wg0.service" and "journalctl -xeu <abbr title="Wireguard">wg</abbr>-quick@wg0.service" for details.
</p>

<p>
	 
</p>

<p>
	When I check sudo journalctl -u <abbr title="Wireguard">wg</abbr>-quick@wg0
</p>

<p>
	I see this:
</p>

<p>
	Starting WireGuard via <abbr title="Wireguard">wg</abbr>-quick(8) for wg0...<br />
	Dec 08 00:52:40 localhost <abbr title="Wireguard">wg</abbr>-quick[51890]: [#] ip link add wg0 type wireguard<br />
	Dec 08 00:52:40 localhost <abbr title="Wireguard">wg</abbr>-quick[51890]: [#] <abbr title="Wireguard">wg</abbr> setconf wg0 /dev/fd/63<br />
	Dec 08 00:52:40 localhost <abbr title="Wireguard">wg</abbr>-quick[51890]: [#] ip -4 address add 10.0.0.4/24 dev wg0<br />
	Dec 08 00:52:40 localhost <abbr title="Wireguard">wg</abbr>-quick[51890]: [#] ip link set mtu 1420 up dev wg0<br />
	Dec 08 00:52:40 localhost <abbr title="Wireguard">wg</abbr>-quick[51913]: [#] resolvconf -a wg0 -m 0 -x<br />
	Dec 08 00:52:40 localhost <abbr title="Wireguard">wg</abbr>-quick[51917]: mkdir: cannot create directory '/run/resolvconf': Permission denied<br />
	Dec 08 00:52:40 localhost <abbr title="Wireguard">wg</abbr>-quick[51915]: Failed to create needed directory /run/resolvconf<br />
	Dec 08 00:52:40 localhost <abbr title="Wireguard">wg</abbr>-quick[51890]: [#] ip link delete dev wg0<br />
	Dec 08 00:52:41 localhost systemd[1]: <abbr title="Wireguard">wg</abbr>-quick@wg0.service: Main process exited, code=exited, status=1/FAILURE<br />
	Dec 08 00:52:41 localhost systemd[1]: <abbr title="Wireguard">wg</abbr>-quick@wg0.service: Failed with result 'exit-code'.<br />
	Dec 08 00:52:41 localhost systemd[1]: Failed to start WireGuard via <abbr title="Wireguard">wg</abbr>-quick(8) for wg0.
</p>

<p>
	 
</p>

<p>
	Now, I have already created folder /run/resolvconf with su permission still can get it to start..
</p>

<p>
	 
</p>

<p>
	Any guidance on this please ?
</p>

<p>
	I am missing something... ?
</p>

<p>
	 
</p>

<p>
	many thanks
</p>

<p>
	 
</p>

<p>
	 
</p>
]]></description><guid isPermaLink="false">47960</guid><pubDate>Sat, 07 Dec 2024 14:30:40 +0000</pubDate></item><item><title>Embedded Intern</title><link>https://forum.armbian.com/topic/47907-embedded-intern/</link><description><![CDATA[
<div class="ipsMargin_top">
    
    
    
</div><p>
	Is it possible to perfrom CSI data extraction using nexmon tool happens in the following phones with the respective firmware patches given below and how?<br />
	Samsung Galaxy S22 Plus - 20_82_42_sta (r994653)<br />
	Google Pixel 7 and 7 Pro - 20_101_36_2 (r994653) and 20_101_57 (r1035009)<br />
	Google Pixel 8 - 24_671_6_9 (r1031525)
</p>
]]></description><guid isPermaLink="false">47907</guid><pubDate>Thu, 05 Dec 2024 06:19:19 +0000</pubDate></item><item><title>snapd frozen on uuptodate jammy for a bpi-m5</title><link>https://forum.armbian.com/topic/47718-snapd-frozen-on-uuptodate-jammy-for-a-bpi-m5/</link><description><![CDATA[<p>
	uptodated today, jammy on <abbr title="Banana Pi"><abbr title="Banana Pi">bpi</abbr></abbr>-m5 running 3d printer with klipper etc. With snapd frozen, so is firefox. possible fix?
</p>

<p>
	passwd f-u, I am that other contributing member but finally got it reset.
</p>
]]></description><guid isPermaLink="false">47718</guid><pubDate>Thu, 28 Nov 2024 14:05:16 +0000</pubDate></item><item><title>Benchmarking CPUs</title><link>https://forum.armbian.com/topic/7763-benchmarking-cpus/</link><description><![CDATA[<p>
	I've run some sysbench (v0.4.12) tests. More will come later as I will get Raspberry Pi 3 Model B+ and Orange Pi RK3399.
</p>

<p>
	 
</p>

<p>
	Banana Pi = ARMv71 A20 @ 960 MHz (not sure about current clock, not overclocked)
</p>

<p>
	 
</p>

<p>
	Banana Pi Armbian (2 cores, 2 threads) - 1 thread - 1057 events in 60 seconds, which gives 17.62 events per second
</p>

<p>
	Banana Pi Armbian (2 cores, 2 threads) - 2 threads - 2003 events in 60 seconds, which gives 33.38 events per second
</p>

<p>
	i7-8700K @ 4.7 GHz VM with Mint 18.3 x64 in VirtualBox on Windows 10 (4 cores, 4 threads) - 1 thread - 10000 events in 4 seconds, which gives 2500 events per second
</p>

<p>
	i7-8700K @ 4.7 GHz Mint 18.3 x64 stand-alone (6 cores, 12 threads) - 12 threads - 10000 events in 1.47 second, which gives 6802 events per second
</p>

<p>
	 
</p>

<p>
	For the above and only CPU - i7-8700K is from 75 to 386 times faster than Banana Pi CPU.
</p>
]]></description><guid isPermaLink="false">7763</guid><pubDate>Sun, 22 Jul 2018 06:11:29 +0000</pubDate></item><item><title>Wanke Cloud NAS is use armbian?</title><link>https://forum.armbian.com/topic/46388-wanke-cloud-nas-is-use-armbian/</link><description><![CDATA[<p>
	just want ask is Wanke Cloud NAS is use armbian? I bought this thrift item
</p>

<p><a href="https://forum.armbian.com/uploads/monthly_2024_10/WhatsAppImage2024-10-16at22_36.46_9aa4c945.jpg.5cf12e78eb78633cf64a1aae4e2709b5.jpg" class="ipsAttachLink ipsAttachLink_image" ><img data-fileid="13330" src="https://forum.armbian.com/uploads/monthly_2024_10/WhatsAppImage2024-10-16at22_36.46_9aa4c945.thumb.jpg.dfea6e6fe3a27f6cb116422a3775f976.jpg" data-ratio="177.73" width="422" class="ipsImage ipsImage_thumbnailed" alt="WhatsApp Image 2024-10-16 at 22.36.46_9aa4c945.jpg"></a></p>
<p><a href="https://forum.armbian.com/uploads/monthly_2024_10/WhatsAppImage2024-10-16at22_36.45_f4b056ce.jpg.c697e2b4122244483e0bb7f0c58cc0af.jpg" class="ipsAttachLink ipsAttachLink_image" ><img data-fileid="13331" src="https://forum.armbian.com/uploads/monthly_2024_10/WhatsAppImage2024-10-16at22_36.45_f4b056ce.thumb.jpg.ff185f298d0881717539b32d8141d2cf.jpg" data-ratio="177.73" width="422" class="ipsImage ipsImage_thumbnailed" alt="WhatsApp Image 2024-10-16 at 22.36.45_f4b056ce.jpg"></a></p>]]></description><guid isPermaLink="false">46388</guid><pubDate>Wed, 16 Oct 2024 14:41:20 +0000</pubDate></item><item><title>SBC colocation ***worldwide provider megalist***</title><link>https://forum.armbian.com/topic/46067-sbc-colocation-worldwide-provider-megalist/</link><description><![CDATA[<p>
	Hi Armbians <img alt=";)" data-emoticon="" height="20" src="https://forum.armbian.com/uploads/emoticons/default_wink.png" srcset="https://forum.armbian.com/uploads/emoticons/wink@2x.png 2x" title=";)" width="20" />
</p>

<p>
	 
</p>

<p>
	Maybe some of you already wanted to put your <abbr title="Single board computer"><abbr title="Single board computer">SBC</abbr></abbr> in a professional data center and operate it as a standalone server for DNS, VPN, Tor, or whatever.
</p>

<p>
	That is exactly why I have put together a huge list of worldwide DC provider options, that are willing to colocate <abbr title="Single board computer"><abbr title="Single board computer">SBC</abbr></abbr>‘s.
</p>

<p>
	It could certainly be of interest to one or the other.
</p>

<p>
	Check my list here:
</p>

<p>
	 
</p>

<p>
	<strong><a href="https://sbc-dc.pages.dev" rel="external nofollow">*** <abbr title="Single board computer"><abbr title="Single board computer">SBC</abbr></abbr> colocation/ <abbr title="Single board computer"><abbr title="Single board computer">SBC</abbr></abbr> hosting worldwide provider megalist ***</a></strong>
</p>
]]></description><guid isPermaLink="false">46067</guid><pubDate>Thu, 10 Oct 2024 19:36:12 +0000</pubDate></item><item><title>Net-ISP-Balance - Load-balance your Internet connection across two or more ISPs for improved bandwidth and reliability</title><link>https://forum.armbian.com/topic/45795-net-isp-balance-load-balance-your-internet-connection-across-two-or-more-isps-for-improved-bandwidth-and-reliability/</link><description><![CDATA[<p>
	I followed the steps outlined in the instructions, and they worked very well for me with (10 ISPs) 4G dongles using PPP connections.
</p>

<p>
	<strong>TV Box Model tested: MXQ Pro 4K, 5G (H3 Allwinner), ISO: Sunvell 69. I started with Debian 10 and later upgraded to Debian 11.</strong>  I also use a second USB 3.0 LAN card, as well as the dongles connected through a USB hub with an independent power supply. 
</p>

<p>
	 
</p>

<p>
	<strong>For more information, you can check the following resources:</strong>
</p>

<p>
	 
</p>

<p>
	Installing the Perl dependencies took some time.
</p>

<p>
	<strong>Net-ISP-Balance Documentation</strong>
</p>

<p>
	<a href="https://lstein.github.io/Net-ISP-Balance/" rel="external nofollow">https://lstein.github.io/Net-ISP-Balance/</a>
</p>

<p>
	 
</p>

<p>
	<strong>Net-ISP-Balance GitHub Repository</strong>
</p>

<p>
	<a href="https://github.com/lstein/Net-ISP-Balance" rel="external nofollow">https://github.com/lstein/Net-ISP-Balance</a>
</p>

<p>
	<img alt="image.png.7e92c45a73715b8529077077f5d7e3a6.png" class="ipsImage ipsImage_thumbnailed" data-fileid="13251" data-ratio="75.00" width="960" src="https://forum.armbian.com/uploads/monthly_2024_10/image.png.7e92c45a73715b8529077077f5d7e3a6.png" />
</p>

<p>
	<strong>Thanks to Lincoln D. Stein</strong>
</p>

<p>
	 
</p>
]]></description><guid isPermaLink="false">45795</guid><pubDate>Thu, 03 Oct 2024 12:58:42 +0000</pubDate></item><item><title>firefox won't update, mirror file wrong size</title><link>https://forum.armbian.com/topic/45634-firefox-wont-update-mirror-file-wrong-size/</link><description><![CDATA[<p>
	neither apt nor snap will update firefox, apt says possible mirror update in progress. snap refresh or snap list says its current.  Call me puzzled. Which do I uninstall???
</p>

<p>
	.
</p>
]]></description><guid isPermaLink="false">45634</guid><pubDate>Sun, 29 Sep 2024 20:11:05 +0000</pubDate></item><item><title>RK3288 and Chrome OS</title><link>https://forum.armbian.com/topic/45497-rk3288-and-chrome-os/</link><description><![CDATA[<p>
	I have 40 huge Chinees tablets for product configuration but the company wont react anymore. Tablets/ half pc Currently runs on Android 7 on the device is it possible to have LAN connection, 3x USB, Simcard slot, SD reader on and off button. And have 1080p touchscreen.
</p>

<p>
	 
</p>

<p>
	What are the he possibilities can it run on windows, chrome os newer versions of Android ?
</p>
]]></description><guid isPermaLink="false">45497</guid><pubDate>Wed, 25 Sep 2024 12:08:11 +0000</pubDate></item><item><title>Banana Pi BPI-M5 Pro with Rockchip RK3576</title><link>https://forum.armbian.com/topic/38891-banana-pi-bpi-m5-pro-with-rockchip-rk3576/</link><description><![CDATA[<p>
	Banana Pi <abbr title="Banana Pi">BPI</abbr>-M5 Pro adopts the second-generation 8nm high-performance AIOT platform Rockchip RK3576, with a 6 TOPS computing power NPU and support for up to 32GB of large memory. It supports 8K video encoding and decoding, offers rich interfaces including dual gigabit Ethernet ports, WiFi 6 &amp; BT5, and various video outputs. Compatible with multiple operating systems, it is suitable for ARM-based PCs, edge computing devices, personal mobile internet devices, and other digital multimedia applications.
</p>

<p>
	 
</p>

<p>
	<img alt="banana_pi_bpi-m5_pro_banner_3.jpg" class="ipsImage" data-ratio="40.00" height="320" width="800" src="https://docs.banana-pi.org/bpi-m5pro/banana_pi_bpi-m5_pro_banner_3.jpg" />
</p>

<p>
	 
</p>

<p>
	Key Parameter
</p>

<p>
	<abbr title="System On a Chip">SoC</abbr>: Rockchip RK3576
</p>

<p>
	CPU: Integrated with four Cortex-A72 cores @ 2.2GHz and four Cortex-A53 cores @ 1.8GHz, along with a separate NEON co-processor.
</p>

<p>
	<abbr title="Graphic processing unit (3D acceleration)">GPU</abbr>: ARM Mali G52 MC3 <abbr title="Graphic processing unit (3D acceleration)">GPU</abbr>
</p>

<p>
	NPU: Up to 6 TOPs computing power (INT8), supports INT4/INT8/INT16 mixed operations.
</p>

<p>
	<abbr title="Video processing unit (encoding/decoding)">VPU</abbr>/Encoding &amp; Decoding:
</p>

<p>
	Hardware Decoding: Supports H.264, H.265, VP9, AV1, and AVS2 up to 8K@30fps or 4K@120fps.
</p>

<p>
	Hardware Encoding: Supports H.264 and H.265 up to 4K@60fps, high-quality JPEG encoder/decoder supports up to 4K@60fps.
</p>

<p>
	RAM: 8/16GB 32-bit LPDDR4x, default is 16GB. RK3576 supports a maximum of 16GB.
</p>

<p>
	Flash: 32/128GB <abbr title="embedded MultiMediaCard">eMMC</abbr>, default is 128GB <abbr title="embedded MultiMediaCard">eMMC</abbr>.
</p>

<p>
	Operating Voltage: Wide input voltage range, from 4.5V to 23V (voltage error ±5%).
</p>

<p>
	Operating Temperature: 0°C to 80°C
</p>

<p>
	Operating Systems:
</p>

<p>
	Official Rockchip Support: Android 14, Debian 11, Buildroot
</p>

<p>
	Third-party Support: Armbian
</p>

<p>
	PCB: 8-layer PCB board design
</p>

<p>
	Weight: 43g
</p>

<p>
	Dimensions: 92mm × 62mm
</p>

<p>
	 
</p>

<p>
	<img alt="banana_pi_bpi-m5_pro_interface.jpg" class="ipsImage" data-ratio="93.75" height="750" width="618" src="https://docs.banana-pi.org/bpi-m5pro/banana_pi_bpi-m5_pro_interface.jpg" />
</p>
]]></description><guid isPermaLink="false">38891</guid><pubDate>Thu, 09 May 2024 06:28:31 +0000</pubDate></item><item><title>How to use with write protected filesystems todays?</title><link>https://forum.armbian.com/topic/19870-how-to-use-with-write-protected-filesystems-todays/</link><description><![CDATA[<p>
	Hello!
</p>

<p>
	 
</p>

<p>
	I wish to make my OrangePi 'failsafe' in regards of spontaneous power losses and such, so I need to have it running write protected, with writes going to a special partition or just RAM.
</p>

<p>
	 
</p>

<p>
	My searches yielded an 'ancient' way to freeze the root filesystem using overlayroot, which isn't supoprted anymore (<a href="https://docs.armbian.com/User-Guide_Advanced-Features/" rel="external nofollow">https://docs.armbian.com/User-Guide_Advanced-Features/</a>)
</p>

<p>
	 
</p>

<p>
	As I think that this kind of 'headless embedded usage' is an usual scenario for <abbr title="Single board computer"><abbr title="Single board computer">SBC</abbr></abbr> running Armbian and having seen there was a method for doing so before, I assume there probably is a popular modern method for doing so, but I couldn' find it.
</p>

<p>
	How would I do this with the current Bullseye release on my Prange Pi Plus 2E?
</p>

<p>
	Or am I suppsed to use the classic kernel?
</p>

<p>
	Thank you!
</p>
]]></description><guid isPermaLink="false">19870</guid><pubDate>Wed, 16 Feb 2022 00:10:52 +0000</pubDate></item><item><title>My Ethernet controller for raspberry circuit issue</title><link>https://forum.armbian.com/topic/44846-my-ethernet-controller-for-raspberry-circuit-issue/</link><description><![CDATA[<p>
	Hi all,
</p>

<p>
	One question here. I am making an electronic design that was previously completed by a third party. It has a Raspberry Pi Zero 2W attached, an Ethernet controller module based on the ENC28J60, and an RJ45 connector. Here the Ethernet controller module is similar to the GeeekPi ENC28J60 Overlays HAT V1.02 board.<br />
	Added: ENC28J60 's Main Specs ref: <a href="https://www.kukelec.com/products/ENC28J60-I--SS.html" rel="external nofollow">https://www.kukelec.com/products/ENC28J60-I--SS.html</a>
</p>

<p>
	 
</p>

<p>
	The issue is that the Raspberry Pi is unable to establish a network connection via Ethernet, as the ENC28J60 chip is not even recognized. I have checked the Raspberry Pi’s configuration, and it is correct and consistent with the chosen SPI pins. While reviewing the design, I noticed some things that caught my attention and differ from what is specified in the ENC28J60 datasheet. In the attachment, I have highlighted the key issues in rea and orange and marked things I am unsure:
</p>

<p><a href="https://forum.armbian.com/uploads/monthly_2024_09/Ethernetcontrollerforraspberrycircuitissuediagram.png.0e5664c876374c9db51444d9618b8587.png" class="ipsAttachLink ipsAttachLink_image" ><img data-fileid="13017" src="https://forum.armbian.com/uploads/monthly_2024_09/Ethernetcontrollerforraspberrycircuitissuediagram.thumb.png.4a33c91b6910b553772fed9378a5b4c6.png" data-ratio="53" width="1000" class="ipsImage ipsImage_thumbnailed" alt="Ethernet controller for raspberry circuit issue diagram.png"></a></p>]]></description><guid isPermaLink="false">44846</guid><pubDate>Wed, 04 Sep 2024 09:55:32 +0000</pubDate></item><item><title>how to reset factory default ARMBian?</title><link>https://forum.armbian.com/topic/43952-how-to-reset-factory-default-armbian/</link><description><![CDATA[<p>
	Hi guys, I want to ask, how to reset ARMbian to reset factory default during fresh install
</p>

<p>
	 
</p>

<p>
	because i can't find it in armbian config<br />
	<br />
	Thanks
</p>

<p>
	 
</p>

<p>
	<img class="ipsImage ipsImage_thumbnailed" data-fileid="12909" data-ratio="89.49" width="742" alt="Screenshotfrom2024-08-2021-58-59.png.2f71bc3792eae9ae69f58d1cde191da6.png" src="https://forum.armbian.com/uploads/monthly_2024_08/Screenshotfrom2024-08-2021-58-59.png.2f71bc3792eae9ae69f58d1cde191da6.png" />
</p>
]]></description><guid isPermaLink="false">43952</guid><pubDate>Tue, 20 Aug 2024 15:04:43 +0000</pubDate></item><item><title>Any SBC/SoM baseboard that can plug into a desktop PCIe slot?</title><link>https://forum.armbian.com/topic/43101-any-sbcsom-baseboard-that-can-plug-into-a-desktop-pcie-slot/</link><description><![CDATA[<p>
	Hi,
</p>

<p>
	 
</p>

<p>
	Curious if there's something like Intel ME that I can use to control my PC and use as a coprocessor when booted, maybe if it had a Coral TPU or something. I remember hearing something about a <abbr title="Raspberry Pi"><abbr title="Raspberry Pi">RPi</abbr></abbr> CM4 base board that has a PCIe connector that can plug into a 1x or 2x slot. (Don't remember exactly which one.)
</p>

<p>
	 
</p>

<p>
	Thanks in advance.
</p>

<p>
	 
</p>

<p>
	edit: Also. Use it for <abbr title="General purpose input/output"><abbr title="General purpose input/output">GPIO</abbr></abbr> and serial ports.
</p>
]]></description><guid isPermaLink="false">43101</guid><pubDate>Sun, 28 Jul 2024 18:56:29 +0000</pubDate></item><item><title>Looking for Help with the Development of Custom Kernel Modules for Armbian</title><link>https://forum.armbian.com/topic/43077-looking-for-help-with-the-development-of-custom-kernel-modules-for-armbian/</link><description><![CDATA[<p>
	Hello Everyone <span class="ipsEmoji">🤗</span>,
</p>

<p>
	 
</p>

<p>
	I'm not too familiar with <a href="https://forum.armbian.com/forum/" rel="">Armbian</a> or ARM-based platforms in general. I'm working on an endeavour that calls for creating a unique kernel module, thus any advice or materials you could offer would be really helpful.<br />
	<br />
	<strong>This is a quick synopsis of the assignment and the difficulties I'm having:</strong><br />
	<br />
	<strong>Project Synopsis:</strong>
</p>

<p>
	<br />
	I'm using Armbian Buster on an Orange Pi 4. My objective is to create a unique kernel module that communicates with a particular piece of hardware—a temperature sensor attached to the I2C bus. The module's job is to read sensor data and provide user-space applications with access to it.<br />
	<br />
	<strong>Actions To Date:</strong><br />
	 
</p>

<ul>
	<li>
		<strong>Kernel Source and Toolchain: </strong>On my development computer running Ubuntu 20.04, I had no trouble downloading the Armbian kernel source and installed the cross-compilation toolchain.
	</li>
	<li>
		<strong>Skeleton of a Basic Module: </strong>I've created a simple "Hello, World" kernel modules and installed it into the Orange Pi with success.
	</li>
	<li>
		<strong>I2C Bus Communication:</strong> I've worked with communication over the I2C bus in user-space before using programs like <a href="https://www.kali.org/tools/i2c-tools/" rel="external nofollow">i2c-tools</a>, but it's been difficult to translate this to a kernel module.
	</li>
</ul>

<p>
	 
</p>

<p>
	<strong>Obstacles:</strong>
</p>

<p>
	 
</p>

<ol>
	<li>
		<strong>Using the I2C Bus to Communicate:</strong> I'm having trouble figuring out how to use my kernel module to access and interact with the I2C bus. The majority of the materials I've come across are either out-of-date or hardware-specific.
	</li>
	<li>
		<strong>Correct Module Integration:</strong> Making sure that my module can be loaded and unloaded securely and without causing instability in the system, as well as that it is correctly linked with the kernel.
	</li>
	<li>
		<strong>Handling Errors and Troubleshooting:</strong> Methods that work well for debugging kernels modules, particularly for hardware communication problems.
	</li>
</ol>

<p>
	 
</p>

<p>
	<strong>Queries:</strong>
</p>

<p>
	 
</p>

<ul>
	<li>
		Could you please direct me to any tutorials or recommended resources that are particular to Armbian and kernels module development?<span class="ipsEmoji">🤔</span>
	</li>
	<li>
		What are the most effective ways to communicate with an Armbian kernel module over the I2C bus?<span> </span><span class="ipsEmoji">🤔</span>
	</li>
	<li>
		Existing modules or sample projects in the Armbian the environment that I could look at to gain more insight into this <a href="https://www.igmguru.com/erp-training/sac-analytics-cloud-online-training/" rel="external nofollow">sap sac</a> process?<span> </span><span class="ipsEmoji">🤔</span>
	</li>
</ul>

<p>
	 
</p>

<p>
	I am eager to know your insights. Thank you <span class="ipsEmoji">🙏</span> in advance.
</p>
]]></description><guid isPermaLink="false">43077</guid><pubDate>Sun, 28 Jul 2024 08:20:30 +0000</pubDate></item><item><title>Need Guidance as In what category should I post?</title><link>https://forum.armbian.com/topic/43038-need-guidance-as-in-what-category-should-i-post/</link><description><![CDATA[<p>
	Hello there,<br />
	<br />
	This is my first post after just joining this discussion, so please forgive me and provide kind assistance if I have posted to the wrong subsection!<br />
	<br />
	As a new member in this forum and wish to share and gain some knowledge. I am looking forward to create my own discussion to resolve my query and gain some knowledge though I have taken part in various discussion which is definitely helped me a lot.<br />
	<br />
	Also in what category should be taken depends on what factors?<br />
	<br />
	Thankyou in advance.
</p>
]]></description><guid isPermaLink="false">43038</guid><pubDate>Sat, 27 Jul 2024 14:21:06 +0000</pubDate></item><item><title>BlueALSA: Bluetooth-Audio using ALSA (not PulseAudio)</title><link>https://forum.armbian.com/topic/6480-bluealsa-bluetooth-audio-using-alsa-not-pulseaudio/</link><description><![CDATA[<p>
	Yesterday I did get a new little Bluetooth-Speaker, but without AUX - I rechecked some Bluetooth-Commands.
</p>

<p>
	But could never connect,  because the Pi missed the protocol A2DP - which was only available with PulseAudio as Bluetooth-Module <img alt=":(" data-emoticon="" height="20" src="https://forum.armbian.com/uploads/emoticons/default_sad.png" srcset="https://forum.armbian.com/uploads/emoticons/sad@2x.png 2x" title=":(" width="20"></p>

<p>
	 
</p>

<p>
	So I used my 2nd <strong>OrangePi On</strong>e with <strong>USB-Bluetooth-Dongle</strong> and <strong>mainline-kerne</strong>l for this challenge:<br>
	ARMBIAN 5.38 stable <strong>Debian GNU/Linux 9 (stretch)</strong> 4.14.18-sunxi
</p>

<p>
	Linux opi-one-<strong>main 4.14.18</strong>-sunxi #24 SMP Fri Feb 9 16:24:32 CET 2018 armv7l GNU/Linux
</p>

<p>
	<br>
	I like ALSA more than PulseAudio - I searched for ALSA and Bluetooth-Audio - and did found no good news about Audio and Bluetooth while using ALSA.<br>
	At the second search I did found the Project
</p>

<p>
	<strong>BlueALSA</strong> (formerly know as <strong>BluezALSA</strong>) :  <a href="https://github.com/Arkq/bluez-alsa" rel="external nofollow">https://github.com/Arkq/bluez-alsa</a>
</p>

<p>
	 
</p>

<p>
	While BlueALSA isnt available as .deb-package (and if then only on the RPi) I did use the following sites for<strong> documentation:</strong>
</p>

<div class="ipsSpoiler" data-ipsspoiler="">
	<div class="ipsSpoiler_header">
		<span>Spoiler</span>
	</div>

	<div class="ipsSpoiler_contents">
		<p>
			 
		</p>

		<p>
			<a href="https://github.com/Arkq/bluez-alsa" rel="external nofollow">https://github.com/Arkq/bluez-alsa</a><br><a href="https://geeks-r-us.de/2017/08/18/bluetooth-a2dp-lautsprecher-am-raspberry-pi/" rel="external nofollow">https://geeks-r-us.de/2017/08/18/bluetooth-a2dp-lautsprecher-am-raspberry-pi/</a><br><a href="https://www.onli-blogging.de/1587/Mit-BlueALSA-Bluetooth-Headset-unter-ALSA-ansprechen.html" rel="external nofollow">https://www.onli-blogging.de/1587/Mit-BlueALSA-Bluetooth-Headset-unter-ALSA-ansprechen.html</a><br><a href="http://denvycom.com/blog/playing-audio-over-bluetooth-on-rasbperry-pi-command-line/" rel="external nofollow">http://denvycom.com/blog/playing-audio-over-bluetooth-on-rasbperry-pi-command-line/</a><br><a href="https://github.com/Arkq/bluez-alsa/issues/8#issuecomment-262914039" rel="external nofollow">https://github.com/Arkq/bluez-alsa/issues/8#issuecomment-262914039</a>
		</p>

		<p>
			<a href="https://kofler.info/bluetooth-konfiguration-im-terminal-mit-bluetoothctl/" rel="external nofollow">https://kofler.info/bluetooth-konfiguration-im-terminal-mit-bluetoothctl/</a>
		</p>

		<p>
			 
		</p>

		<p>
			 
		</p>
	</div>
</div>

<p>
	 
</p>

<p>
	As <strong>Dependencies</strong> I had to install the following packages:<br>
	apt-get install libasound2-dev dh-autoreconf libortp-dev bluez bluetooth bluez-tools libbluetooth-dev libusb-dev libglib2.0-dev libudev-dev libical-dev libreadline-dev libsbc1 libsbc-dev <strong>libfdk-aac-dev</strong>
</p>

<p>
	 
</p>

<p>
	<strong>libfdk-aac-dev </strong>is one more than at the RPi-Documetation page.
</p>

<p>
	 
</p>

<p>
	For <strong>creating</strong> / compiling <strong>BlueALSA</strong> I did use the follwoing commands:<br>
	cd /home/guido<br>
	git clone <a href="https://github.com/Arkq/bluez-alsa.git" rel="external nofollow">https://github.com/Arkq/bluez-alsa.git</a><br>
	cd bluez-alsa/<br>
	autoreconf --install<br>
	mkdir build &amp;&amp; cd build<br>
	../configure --disable-hcitop --with-alsaplugindir=/usr/lib/arm-linux-gnueabihf/alsa-lib<br>
	make &amp;&amp; sudo make install
</p>

<p>
	 
</p>

<p>
	When BlueALSA has been created, then you can start <strong>BlueALSA as background task</strong>:<br>
	bluealsa --disable-hfp &amp;
</p>

<p>
	 
</p>

<p>
	Now - for using your bluetooth-speaker/headset - with BlueALSA you have to <strong>intoduce</strong> the <strong>device</strong> to the bluetooth-stack <strong>using bluetoothctl</strong>:<br>
	bluetoothctl &gt;<br>
	scan on<br>
	[NEW] Device <strong>30:23:23:F4:48:2C</strong> <em><strong>TH-S10U</strong></em><br>
	scan off<br>
	pair <strong>30:23:23:F4:48:2C</strong><br>
	trust <strong>30:23:23:F4:48:2C</strong><br>
	exit
</p>

<p>
	 
</p>

<p>
	After that <strong>power off&amp;on</strong> the bt-speaker device and the device will<strong> connect automatically </strong>as a<strong> trusted device</strong>.
</p>

<p>
	 
</p>

<p>
	Before we try our first audio-command we had to export one thing to make BlueALSA mor system-friendly:<br><strong>export LIBASOUND_THREAD_SAFE=0</strong>because of a message while compiling:
</p>

<div class="ipsSpoiler" data-ipsspoiler="">
	<div class="ipsSpoiler_header">
		<span>Spoiler</span>
	</div>

	<div class="ipsSpoiler_contents">
		<p>
			 
		</p>

		<p>
			configure: WARNING:               *** alsa-lib &gt;= 1.1.2 ***<br>
			configure: WARNING: Starting from alsa-lib 1.1.2, it is possible to enable<br>
			configure: WARNING: thread-safe API functions. Unfortunately, this feature<br>
			configure: WARNING: is not mature enough - software plugins may experience<br>
			configure: WARNING: random deadlocks (bluez-alsa PCM plugin is affected).<br>
			configure: WARNING: Either compile alsa-lib without this feature or export<br>
			configure: WARNING: LIBASOUND_THREAD_SAFE=0 while using bluealsa PCM.
		</p>

		<p>
			 
		</p>
	</div>
</div>

<p>
	 
</p>

<p>
	Now you can try your <strong>first commands</strong> for <strong>getting audio</strong> out of the device:
</p>

<p>
	 
</p>

<p>
	<u><strong>Text to speech:</strong></u>
</p>

<p>
	<strong>espeak</strong> "Hello, how are you?" -w /home/guido/espeak.wav -s145<br><strong>aplay</strong> -D bluealsa:HCI=hci0,DEV=<strong>30:23:23:F4:48:2C</strong>,PROFILE=<strong>a2dp</strong> /home/guido/espeak.wav
</p>

<p>
	 
</p>

<p>
	<u><strong>Internetradio:</strong></u>
</p>

<p>
	<strong>mpg123</strong> -a bluealsa:HCI=hci0,DEV=<strong>30:23:23:F4:48:2C</strong>,PROFILE=<strong>a2dp</strong> -@ /home/guido/ffh80s.pls
</p>

<p>
	 
</p>

<p>
	For shorting the command you could create a <strong>~/.asoundrc</strong> with the following content:
</p>

<p>
	defaults.bluealsa.interface "hci0"<br>
	defaults.bluealsa.device "<strong>30:23:23:F4:48:2C</strong>"<br>
	defaults.bluealsa.profile "<strong>a2dp</strong>"<br>
	defaults.bluealsa.delay 10000
</p>

<p>
	 
</p>

<p>
	Now you can the <strong>shorter</strong> version of the <strong>command</strong>:
</p>

<p>
	mpg123 -a bluealsa -@ /home/guido/ffh80s.pls
</p>

<p>
	 
</p>

<p>
	For set the volume of such a device you have to know the "real" name of the device out of the bluetoothctl and the name of the used protocol:
</p>

<p>
	<strong>Device:</strong> 30:23:23:F4:48:2C <em><strong>TH-S10U</strong></em><br><strong>Protocol:</strong> <em><strong>A2DP</strong></em><br>
	amixer -D bluealsa sset '<em><strong>TH-S10U - A2DP </strong></em>' 70%
</p>

<p>
	 
</p>

<p>
	Here as information the dmesg-part of my bluetooth-dongle:
</p>

<div class="ipsSpoiler" data-ipsspoiler="">
	<div class="ipsSpoiler_header">
		<span>Spoiler</span>
	</div>

	<div class="ipsSpoiler_contents">
		<p>
			[346859.531251] usb 4-1: new full-speed USB device number 2 using ohci-platform<br>
			[346859.807299] usb 4-1: New USB device found, idVendor=0a12, idProduct=0001<br>
			[346859.807317] usb 4-1: New USB device strings: Mfr=0, Product=2, SerialNumber=0<br>
			[346859.807329] usb 4-1: Product: CSR8510 A10<br>
			[346859.963820] Bluetooth: Core ver 2.22<br>
			[346859.963906] NET: Registered protocol family 31<br>
			[346859.963910] Bluetooth: HCI device and connection manager initialized<br>
			[346859.963928] Bluetooth: HCI socket layer initialized<br>
			[346859.963938] Bluetooth: L2CAP socket layer initialized<br>
			[346859.963965] Bluetooth: SCO socket layer initialized<br>
			[346859.975588] usbcore: registered new interface driver btusb<br>
			[346860.184710] Bluetooth: BNEP (Ethernet Emulation) ver 1.3<br>
			[346860.184718] Bluetooth: BNEP filters: protocol multicast<br>
			[346860.184734] Bluetooth: BNEP socket layer initialized<br>
			[346901.432957] Bluetooth: RFCOMM TTY layer initialized<br>
			[346901.432979] Bluetooth: RFCOMM socket layer initialized<br>
			[346901.432998] Bluetooth: RFCOMM ver 1.11<br>
			[347059.966606] input: 30:23:23:F4:48:2C as /devices/virtual/input/input1
		</p>
	</div>
</div>

<p>
	 
</p>
]]></description><guid isPermaLink="false">6480</guid><pubDate>Thu, 15 Feb 2018 08:30:05 +0000</pubDate></item><item><title>How to Create a Bootable Live Image from Current Armbian Installation?</title><link>https://forum.armbian.com/topic/37834-how-to-create-a-bootable-live-image-from-current-armbian-installation/</link><description><![CDATA[<p>
	I'm running Armbian on my ARM-based single-board computer, and I would like to create a bootable live image from my current installation. This way, I can use the image to boot other devices with the same configuration, software, and customizations that I've set up on my current system.
</p>

<p>
	I've looked through the Armbian documentation, but I couldn't find a straightforward guide on how to accomplish this task. Can someone please provide step-by-step instructions on how to create a bootable live image from my current Armbian installation?
</p>

<p>
	Ideally, I'd like to be able to create an image file (e.g., .img or .iso) that I can write to a USB drive or an SD card, making it bootable on other ARM devices compatible with Armbian.
</p>

<p>
	Please let me know if you need any additional details about my current setup or if there are any specific tools or utilities I should be aware of for this process.
</p>

<p>
	Thank you in advance for your help!
</p>
]]></description><guid isPermaLink="false">37834</guid><pubDate>Mon, 22 Apr 2024 12:23:16 +0000</pubDate></item><item><title>rock64 with community debian - daily updates require reboots</title><link>https://forum.armbian.com/topic/41687-rock64-with-community-debian-daily-updates-require-reboots/</link><description><![CDATA[<p>
	Hello all,
</p>

<p>
	 
</p>

<p>
	I had diet-pi on my rock64 for the last few years but recently decided to install armbian debian community maintained firmware.
</p>

<p>
	 
</p>

<p>
	Everything is working fine but I seem to get a new core fw on an almost daily basis (armbian-bsp-cli-rock64-current) and the board needs to be rebooted each time.
</p>

<p>
	 
</p>

<p>
	An I using the wrong repo or is this normal?
</p>

<p>
	 
</p>

<p>
	Should i consider running stock debian instead of armbian?
</p>
]]></description><guid isPermaLink="false">41687</guid><pubDate>Thu, 27 Jun 2024 22:11:16 +0000</pubDate></item><item><title>Please tell me how to install IMX462 MIPI CAMERA so that it is recognized by NAS SDK 3588.</title><link>https://forum.armbian.com/topic/41560-please-tell-me-how-to-install-imx462-mipi-camera-so-that-it-is-recognized-by-nas-sdk-3588/</link><description><![CDATA[<p>
	Please tell me how to install IMX462 MIPI CAMERA so that it is recognized by NAS SDK 3588.
</p>

<p>
	Since I am a beginner, I cannot configure <abbr title="Device tree source">DTS</abbr> or create a driver.
</p>

<p>
	I need help.
</p>

<p>
	<a href="https://patchwork.kernel.org/project/linux-arm-kernel/list/?series=862403" rel="external nofollow">Linux ARM Kernel Architecture - Patchwork </a> I think there is a patch related to imx462 here, but I don't know how to use it. Please tell me how to use it.
</p>
]]></description><guid isPermaLink="false">41560</guid><pubDate>Tue, 25 Jun 2024 07:19:57 +0000</pubDate></item><item><title>Recommendations for an Arm Development platform.</title><link>https://forum.armbian.com/topic/40180-recommendations-for-an-arm-development-platform/</link><description><![CDATA[<p>
	Hi,
</p>

<p>
	 
</p>

<p>
	I've been looking around for an Arm development platform. Banana Pi seems to be about the best value for money. I've been looking around at some TV boxes. However, I see mixed opinions about these being a option. SBCs seem to be almost twice the price of similar spec Arm TV box. Processing power and memory are mostly my priorities. Anything over 4GB seems insanely expensive.
</p>

<p>
	 
</p>

<p>
	I can do SMD soldering work. So modding at TV box is an option.
</p>

<p>
	 
</p>

<p>
	Are there any options for an 8gb Octa core system that isn't going to cost more than a decent PC?
</p>
]]></description><guid isPermaLink="false">40180</guid><pubDate>Wed, 29 May 2024 01:01:52 +0000</pubDate></item><item><title>How to create or setup Wifi Vendo system operated by coin acceptor?</title><link>https://forum.armbian.com/topic/41151-how-to-create-or-setup-wifi-vendo-system-operated-by-coin-acceptor/</link><description><![CDATA[
<div class="ipsMargin_top">
    
    
    
</div><p>
	As a beginner in the system I intend to do is how to start the construction of a Wifi Vending Machine operated by coinslot call in philippines is PESO WIFI. Maybe someone is working on it
</p>

<p>
	these are samples of the appearance between client and admin side.<br />
	<br />
	Client Portal:<br />
	<a class="ipsAttachLink ipsAttachLink_image" href="https://forum.armbian.com/uploads/monthly_2024_06/image.png.a48e071ba6f226ccbd2feffdd3bc6620.png" data-fileid="12638" data-fileext="png" rel=""><img class="ipsImage ipsImage_thumbnailed" data-fileid="12638" data-ratio="116.10" width="646" alt="image.thumb.png.588284e61cf30690dd7b84c73a0971d1.png" src="https://forum.armbian.com/uploads/monthly_2024_06/image.thumb.png.588284e61cf30690dd7b84c73a0971d1.png" /></a>
</p>

<p>
	 
</p>

<p>
	Admin side:<br />
	<img class="ipsImage ipsImage_thumbnailed" data-fileid="12639" data-ratio="223.33" width="150" alt="image.png.913017ef8a002d45ada108ea51a4bb01.png" src="https://forum.armbian.com/uploads/monthly_2024_06/image.png.913017ef8a002d45ada108ea51a4bb01.png" /><br />
	<br />
	 
</p>
]]></description><guid isPermaLink="false">41151</guid><pubDate>Fri, 14 Jun 2024 03:15:40 +0000</pubDate></item><item><title>Hi! After 5 years...</title><link>https://forum.armbian.com/topic/41250-hi-after-5-years/</link><description><![CDATA[<p>
	Hello Armbian Forum!<br />
	I hope you are all well.
</p>

<p>
	It's been more than 5 years since I last visited here, a lot of things has changed in my life since then. I saw my posts complaining about apt speed, that I could get 200kbps speed, now I am building +200gbps infrastructures for tens of thousands of servers.<br />
	I felt a little bit of nostalgia visiting this forum because of that. And here I am, just I wanted to say hi!<br />
	I hope you all also had a great time in the last 5 years just like me.
</p>
]]></description><guid isPermaLink="false">41250</guid><pubDate>Sat, 15 Jun 2024 21:03:16 +0000</pubDate></item><item><title>Improve UX on Armbian download pages</title><link>https://forum.armbian.com/topic/40988-improve-ux-on-armbian-download-pages/</link><description><![CDATA[<p>
	We are well aware that our download pages are no perfect and generally there is always room for improvements, so we are constantly trying to improve them. Better UX and useful information saves time.  Help us saving your time!
</p>

<p>
	 
</p>

<p>
	Things like:
</p>

<p>
	 
</p>

<p>
	<img class="ipsImage ipsImage_thumbnailed" data-fileid="12629" data-ratio="20.28" data-unique="4o6keusrr" width="784" alt="image.png" src="https://forum.armbian.com/uploads/monthly_2024_06/image.png.50373ef28fd50c5f811d7e15f0fad4a8.png">
</p>

<p>
	 
</p>

<p>
	<a href="https://armbian.atlassian.net/browse/AR-2363" ipsnoembed="true" rel="external nofollow">https://armbian.atlassian.net/browse/AR-2363</a>
</p>

<p>
	 
</p>
]]></description><guid isPermaLink="false">40988</guid><pubDate>Mon, 10 Jun 2024 13:56:57 +0000</pubDate></item><item><title>Sharing my pet-project - A WireGuard (+ IP Tables) based VPN setup and its management UI (web)</title><link>https://forum.armbian.com/topic/40886-sharing-my-pet-project-a-wireguard-ip-tables-based-vpn-setup-and-its-management-ui-web/</link><description><![CDATA[<p>
	Hi,
</p>

<p>
	 
</p>

<p>
	I developed this app just while having a look at django + angular -&gt; <a href="https://github.com/vijaygill/wg-ui-plus" rel="external nofollow">https://github.com/vijaygill/<abbr title="Wireguard"><abbr title="Wireguard">wg</abbr></abbr>-ui-plus</a>
</p>

<p>
	 
</p>

<p>
	I thought of sharing it with open-source communiity which has given me a lot!
</p>

<p>
	 
</p>

<p>
	It allows me to have finer control over what a given VPN client can access (using IP Tables rules - managed by the code itself)
</p>

<p>
	 
</p>

<p>
	I hope somebody finds it useful.
</p>

<p>
	 
</p>

<p>
	It is comes as docker image (published on every push to dev / master) so updates are quite frequent for now due to tweaks / fixes. 
</p>

<p>
	 
</p>

<p>
	I developed it on an Orange Pi 5+ running on Armbian <span><img alt=":)" data-emoticon="" height="20" src="https://forum.armbian.com/uploads/emoticons/default_smile.png" srcset="https://forum.armbian.com/uploads/emoticons/smile@2x.png 2x" title=":)" width="20" />.</span>
</p>

<p>
	 
</p>

<p>
	The LIVE instance is running on a Raspberry Pi.
</p>

<p>
	 
</p>

<p>
	Thanks
</p>

<p>
	V
</p>

<p>
	 
</p>
]]></description><guid isPermaLink="false">40886</guid><pubDate>Sat, 08 Jun 2024 12:50:04 +0000</pubDate></item><item><title>Unable to load sketch on internal Arduino due in udoo quad</title><link>https://forum.armbian.com/topic/40163-unable-to-load-sketch-on-internal-arduino-due-in-udoo-quad/</link><description><![CDATA[<p>
	Hi.
</p>

<p>
	I'm using armbian 24.05 Ubuntu jammy xfce 30.
</p>

<p>
	I've downloaded Arduino ide 1.8 for arm32 Linux. I replaced original Arduino due bossac with custom bossac for udoo in Arduino due Tools in order to make ide see atmel sam3xe on udoo, but bossac didn't find it. 
</p>

<p>
	I've tried super user access and chmod on bossac and on ttyxmc (internal Arduino due programming seirla port) 
</p>

<p>
	 
</p>

<p>
	With old armbian build it worked, but now not. 
</p>

<p>
	 
</p>

<p>
	Cheers
</p>
]]></description><guid isPermaLink="false">40163</guid><pubDate>Tue, 28 May 2024 21:14:52 +0000</pubDate></item><item><title>How to customize bootlogo in build</title><link>https://forum.armbian.com/topic/39394-how-to-customize-bootlogo-in-build/</link><description><![CDATA[<p>
	Hello everyone! I'm compiling firmware for orangepizero3，then you want to customize the bootlogo.
</p>

<p>
	I tried to replace my bootlogo with armbian-logo-png in xx, but the compiled firmware did not change, so I would like to ask you how to modify it
</p>

<p>
	My compile command:./compile.sh BOARD=orangepizero3 BRANCH=current BUILD_DESKTOP=yes BUILD_MINIMAL=no DESKTOP_APPGROUPS_SELECTED='browsers multimedia' DESKTOP_ENVIRONMENT=xfce DESKTOP_ENVIRONMENT_CONFIG_NAME=config_base KERNEL_CONFIGURE=no RELEASE=bookworm PLYMOUTH=yes  build
</p>

<p>
	 
</p>

<p>
	<br />
	 
</p>
]]></description><guid isPermaLink="false">39394</guid><pubDate>Fri, 17 May 2024 10:01:33 +0000</pubDate></item><item><title>UserSpace and HID -  Add Device ID</title><link>https://forum.armbian.com/topic/39305-userspace-and-hid-add-device-id/</link><description><![CDATA[
<div class="ipsMargin_top">
    
    
    
</div><p>
	Newbie
</p>

<p>
	Using LinuxMint 21.3
</p>

<p>
	 
</p>

<p>
	I have been searching for answer to below question,  and have been referred to UserSpace as it may have an answer. Referral from    greg kh on Linusfoundation org.
</p>

<p>
	 
</p>

<p>
	Question:
</p>

<p>
	Linux Mint 21.3 Using LibreCalc With USB RFID tag readers, (2 or more reader) most enter direct into open focus spreadsheet. However with no device number. Have same pid and vid. As the read from USB tag goes to the spreadsheet, can the device number eg 03 and the bus number eg 004  (either or both) be appended to the data read, into the spreadsheet. This would enable spreadsheet identify each reader and its location, to manipulate the tag reads by the location etc.
</p>

<p>
	 
</p>

<p>
	If so, how do I go about setting up?
</p>

<p>
	 
</p>

<p>
	This is a common issue with USB and HID, there is no device ID.   A standard terminal script for LinuxMint would be great and make the USB devices more usable.
</p>

<p>
	Thankyou
</p>

<p>
	Charles Harris
</p>
]]></description><guid isPermaLink="false">39305</guid><pubDate>Tue, 14 May 2024 08:15:56 +0000</pubDate></item><item><title>Android Auto Wireless smart box - what's inside?</title><link>https://forum.armbian.com/topic/34888-android-auto-wireless-smart-box-whats-inside/</link><description><![CDATA[<p>
	Recently I've bought small box which is kind if "wireless interface" for wired AA: <a href="https://www.aliexpress.com/item/1005006001314624.html" rel="external nofollow">https://www.aliexpress.com/item/1005006001314624.html</a>
</p>

<p>
	It works quite nicely with my Ford S-Max but I'm very curious man and got it open (aka teardown). Chips cannot be identified, they lack any marks. But there is DEBUG UART <span><img alt=":)" data-emoticon="" height="20" src="https://forum.armbian.com/uploads/emoticons/default_smile.png" srcset="https://forum.armbian.com/uploads/emoticons/smile@2x.png 2x" title=":)" width="20" /></span>
</p>

<p>
	First I connected it into my PC. Removable disk appeared with a few files that keeps my phone's BT address and such information. Nothing really interesting.
</p>

<p>
	Then I powered up device when holding the button, it didn't start but went into some "flashing mode" I think - it was identified as USB\VID_1F3A&amp;PID_EFE8 which means <em>sunxi <abbr title="System On a Chip">SoC</abbr> OTG connector in FEL/flashing mode</em> as far as I could google it. <strong>So Allwinner inside?</strong>
</p>

<p>
	At last I soldered pins to UART but I got only <em>"U-Boot(01/24/2024)"</em> and nothing more <span><span class="ipsEmoji">😕</span> It doesn't react to keybord at all.</span>
</p>

<p>
	 
</p>

<p>
	<span>I'm not experienced in "hacking" such ARM things, so maybe someone has any idea how to break booting and get into some console? Any idea what could I do to get into OS? <span><img alt=":)" data-emoticon="" height="20" src="https://forum.armbian.com/uploads/emoticons/default_smile.png" srcset="https://forum.armbian.com/uploads/emoticons/smile@2x.png 2x" title=":)" width="20" /></span></span>
</p>

<p>
	 
</p>

<p><a href="https://forum.armbian.com/uploads/monthly_2024_02/chrome_KOR0m9LXoq.png.205bef227a3757ef8d4e72a05a6398fc.png" class="ipsAttachLink ipsAttachLink_image" ><img data-fileid="11809" src="https://forum.armbian.com/uploads/monthly_2024_02/chrome_KOR0m9LXoq.thumb.png.95b33f2bbba93fbfda0d2c70ad085452.png" data-ratio="49.7" width="1000" class="ipsImage ipsImage_thumbnailed" alt="chrome_KOR0m9LXoq.png"></a></p>
<p><a href="https://forum.armbian.com/uploads/monthly_2024_02/AAWireless_teardown.jpg.9cde2ff180c845e01fbeaf89a9c25658.jpg" class="ipsAttachLink ipsAttachLink_image" ><img data-fileid="11810" src="https://forum.armbian.com/uploads/monthly_2024_02/AAWireless_teardown.thumb.jpg.affe4393785f834b1efda37886548736.jpg" data-ratio="100.4" width="747" class="ipsImage ipsImage_thumbnailed" alt="AAWireless_teardown.jpg"></a></p>]]></description><guid isPermaLink="false">34888</guid><pubDate>Mon, 19 Feb 2024 20:22:34 +0000</pubDate></item><item><title>Lichee Pi zero</title><link>https://forum.armbian.com/topic/9081-lichee-pi-zero/</link><description><![CDATA[<p>
	Didn't know this thing was ever going to see the light of day:  <a href="https://www.aliexpress.com/item/Lichee-Pi-Zero-1GHz-Cortex-A7-512Mbit-DDR-Development-Board-Module-Mini-PC/32931418720.html" rel="external nofollow">https://www.aliexpress.com/item/Lichee-Pi-Zero-1GHz-Cortex-A7-512Mbit-DDR-Development-Board-Module-Mini-PC/32931418720.html</a>
</p>

<p>
	 
</p>

<p>
	I see the original board outline is still there, but it grew a bit of a waistline  <span><img alt=":lol:" data-emoticon="" src="https://forum.armbian.com/uploads/emoticons/default_laugh.png" title=":lol:"></span>
</p>

<p>
	 
</p>

<p>
	<span>A valid question is why, and I'm not sure, nor will I buy it, just thought it interesting that it popped up.  With complete kernel support for VDEC/VENC/ camera this is actually somewhat interesting, so maybe some people would like to play with it.  I'm sure <a contenteditable="false" data-ipshover="" data-ipshover-target="https://forum.armbian.com/profile/4351-icenowy/?do=hovercard" data-mentionid="4351" href="https://forum.armbian.com/profile/4351-icenowy/" rel="">@Icenowy</a> knows more than is humanly possible about the capabilities and whether it's worth talking about.  <img alt=";)" data-emoticon="" height="20" src="https://forum.armbian.com/uploads/emoticons/default_wink.png" srcset="https://forum.armbian.com/uploads/emoticons/wink@2x.png 2x" title=";)" width="20"></span>
</p>
]]></description><guid isPermaLink="false">9081</guid><pubDate>Sun, 16 Dec 2018 16:29:20 +0000</pubDate></item><item><title>Seeking for RTL8189FTV and RTL8211E chips</title><link>https://forum.armbian.com/topic/35617-seeking-for-rtl8189ftv-and-rtl8211e-chips/</link><description><![CDATA[<p>
	Hello ...
</p>

<p>
	 
</p>

<p>
	I'm seeking for any device(s) with RTL8189FTV and RTL8211E chips.
</p>

<p>
	It's does not matter "what it is" ...
</p>

<p>
	(old unneeded, broken one, etc.- or any kind of trash)
</p>

<p>
	 
</p>

<p>
	I have one damaged <abbr title="Orange Pi">OPI</abbr> Zero Plus and I can back it into the life ...
</p>

<p>
	now actually work and boot, but ETH and WIFI chips are burned.
</p>

<p>
	 
</p>

<p>
	I'm in Slovakia ....
</p>

<p>
	 
</p>

<p>
	Thanks
</p>
]]></description><guid isPermaLink="false">35617</guid><pubDate>Mon, 04 Mar 2024 18:29:21 +0000</pubDate></item><item><title>"The system deletes the home directory I created while building the system during startup."</title><link>https://forum.armbian.com/topic/36775-the-system-deletes-the-home-directory-i-created-while-building-the-system-during-startup/</link><description><![CDATA[<p>
	 I am a developer from China and am not very familiar with English, so the following content is translated through Google Translate.
</p>

<p>
	When I successfully flash the image file of the built system onto the development board, the system seems to delete the directory under /home upon the first boot (from my observation).
</p>

<p>
	The build command being used ：./compile.sh build BOARD=firefly-rk3399 BRANCH=current BUILD_DESKTOP=no BUILD_MINIMAL=yes KERNEL_CONFIGURE=no RELEASE=focal 
</p>

<p>
	<strong>This is an excerpt from customize-image.sh.</strong>
</p>

<pre class="ipsCode">Main() {
	case $RELEASE in
		stretch)
			# your code here
			# InstallOpenMediaVault # uncomment to get an OMV 4 image
			;;
		buster)
			# your code here
			;;
		bullseye)
			# your code here
			;;
		bionic)
			# your code here
			;;
		focal)
			# your code here
			echo "12345678"
			cjia_xxx
			;;
	esac

} # Main


cjia_xxx()
{

		  rm /root/.not_logged_in_yet
        username=cjia
        pass=cjia

        # Check if user already exists.
        grep -q "$username" /etc/passwd
        if [ $? -eq $SUCCESS ] 
        then	
            echo "User $username does already exist."
            echo "please chose another username."
            exit $E_USEREXISTS
        fi  

        #Preerequisite for mkpasswd : whois

        useradd  -d /home/"$username" -m -g users -s /bin/bash "$username"
        #Allow no one else to access the home directory of the user
        chmod 750 /home/"$username" 
        echo "$username":"$pass"|chpasswd
        echo "the account is setup"


        PUBLIC_KEY="ssh-rsa AAAAB3NzaC1yc2EAAAADAQABAAABgQsdfsdfsfsdfa6r2jUg5Wmnk7m97BccU+itsqEUe0IOUKslOdHlGQcos9APLEZk1jec/a/7eGCcCVfTNznW8Wskg+o/nyZDBCeQL7TMs5L2TlBoJpOudo42bxEp0lqTe8nS/cKPv3EZT0mMdFh3JbSqmF0eou6rbui0EjInzh9+CqB/fsuErunJ700N+uZ0l9dJ7Fofj1Ws1rptk0Ezer8YmIaDfvm4mFY7pQTHIqphqZ0IhBRXrBbL5XFv53cevvdfpkLA6y4LplWnIysdfsdfsdfsdeqG+r1licfbQYYqpACr8jFuv7T6Q2BaMfDF5AKZ8UeuIe66lFX+5MpD25WM+LamlEnBmh67d1SYOadSGBXC5RSs5Vp9hX1Nff2tfVN+kyvsfPe/v0D/ScJdqKCCR+w3SResv/aFZPW524tI32ehU1q7G2XYqdayxbA5QLjIxwo+NJn6Bc="
        CJIA_HOME="/home/cjia"
        mkdir -p $CJIA_HOME/.ssh
        echo "$PUBLIC_KEY" &gt;&gt; $CJIA_HOME/.ssh/known_hosts
        chown cjia:cjia $CJIA_HOME/.ssh/known_hosts
        chmod 600 $CJIA_HOME/.ssh/known_hosts
        cat $CJIA_HOME/.ssh/known_hosts
        cd /home/cjia
        ls -al
        pwd
        su cjia -c "pwd"
  }</pre>

<p>
	<strong>Corresponding log output</strong>
</p>

<pre class="ipsCode">[<span class="ipsEmoji">🐳</span>|<span class="ipsEmoji">🔨</span>]   the account is setup
[<span class="ipsEmoji">🐳</span>|<span class="ipsEmoji">🔨</span>]   chown: invalid group: ‘cjia:cjia’
[<span class="ipsEmoji">🐳</span>|<span class="ipsEmoji">🔨</span>]   ssh-rsa AAAAB3NzaC1yc2EAAAADAQABAAABgQsdfsdfsdfsdphekfmCKihCw5UKzXPhdeMxAsa6r2jUg5Wmnk7m97BccU+itsqEUe0IOUKslOdHlGQcos9APLEZk1jec/a/7eGCcCVfTNznW8Wskg+o/nyZDBCeQL7TMs5L2TlBoJpOudo42bxEp0lqTe8nS/cKPv3EZT0mMsdfsdfsdfsdEjInzh9+CqB/fsuErunJ700N+uZ0l9dJ7Fofj1Ws1rptk0Ezer8YmIaDfvm4mFY7pQTHIqphqZ0IhBRXrBbL5XFv53cevvdfpkLA6y4LplWnIyE5lqESVyp9m5Vj+rYMHdGTiIr2il2aN+xKcAeqG+r1licfbQYYqpACr8jFuv7T6Q2BaMfDF5AKZ8UeuIe66lFX+5MpD25WM+LamlEnBmh67d1SYOadSGBXC5RSs5Vp9hX1Nff2tfVN+kyvsfPe/v0D/ScJdqKCCR+w3SResv/sdfsdfsdfsdyxbA5QLjIxwo+NJn6Bc= cjia@DESKTOP-T9MJO61
[<span class="ipsEmoji">🐳</span>|<span class="ipsEmoji">🔨</span>]   total 12
[<span class="ipsEmoji">🐳</span>|<span class="ipsEmoji">🔨</span>]   drwxr-x--- 3 cjia users  120 Mar 26 12:41 .
[<span class="ipsEmoji">🐳</span>|<span class="ipsEmoji">🔨</span>]   drwxr-xr-x 3 root root    60 Mar 26 12:41 ..
[<span class="ipsEmoji">🐳</span>|<span class="ipsEmoji">🔨</span>]   -rw-r--r-- 1 cjia users  220 Feb 25  2020 .bash_logout
[<span class="ipsEmoji">🐳</span>|<span class="ipsEmoji">🔨</span>]   -rw-r--r-- 1 cjia users 3771 Mar 26 12:28 .bashrc
[<span class="ipsEmoji">🐳</span>|<span class="ipsEmoji">🔨</span>]   -rw-r--r-- 1 cjia users  807 Feb 25  2020 .profile
[<span class="ipsEmoji">🐳</span>|<span class="ipsEmoji">🔨</span>]   drwxrwxr-x 2 root root    60 Mar 26 12:41 .ssh
[<span class="ipsEmoji">🐳</span>|<span class="ipsEmoji">🔨</span>]   /home/cjia
[<span class="ipsEmoji">🐳</span>|<span class="ipsEmoji">🔨</span>]   /home/cjia</pre>

<p>
	 
</p>

<p>
	When logging in for the first time
</p>

<p>
	<img class="ipsImage ipsImage_thumbnailed" data-fileid="12034" data-ratio="58.82" width="595" alt="image.png.9afd3a4addb18fe64e1930e653b205bf.png" src="https://forum.armbian.com/uploads/monthly_2024_03/image.png.9afd3a4addb18fe64e1930e653b205bf.png" />
</p>
]]></description><guid isPermaLink="false">36775</guid><pubDate>Wed, 27 Mar 2024 01:32:23 +0000</pubDate></item><item><title>Help need with dumping firmware on Allwinner based device using FEL or serial console</title><link>https://forum.armbian.com/topic/36735-help-need-with-dumping-firmware-on-allwinner-based-device-using-fel-or-serial-console/</link><description><![CDATA[<p>
	I have IQAir AirVision pro and i'm try to reverse engineer it
</p>

<p>
	it uses uboot sunxi (allwinner)
</p>

<p>
	 
</p>

<p>
	was following this video
</p>

<div class="ipsEmbeddedVideo" contenteditable="false">
	<div>
		<iframe allowfullscreen="" frameborder="0" height="113" title="Extracting Firmware from Linux Router using the U-Boot Bootloader and UART" width="200" data-embed-src="https://www.youtube-nocookie.com/embed/006ROXEYSeI?start=328&amp;feature=oembed"></iframe>
	</div>
</div>

<p>
	according to video i need to know where flash chip is mapped in to memory then use md print whole firmware then used <a href="https://github.com/nmatt0/firmwaretools/blob/master/parse-uboot-dump.py" rel="external nofollow">https://github.com/nmatt0/firmwaretools/blob/master/parse-uboot-dump.py</a> to convert to firmware as he used bdinfo to get address (which is not present), what i do?
</p>

<p>
	 
</p>

<p>
	Is there any way through which i can extract frimware from device? (like using FEL Mode)
</p>

<p>
	 
</p>

<p>
	also
</p>

<p>
	found <a href="https://github.com/zador-blood-stained/h3-fel-mass-storage" rel="external nofollow">https://github.com/zador-blood-stained/h3-fel-mass-storage</a>
</p>

<p>
	is it possible do same on Allwinner A33
</p>

<p>
	 
</p>

<p>
	logs
</p>

<p>
	<a href="https://xdaforums.com/attachments/boot-txt.6083991/" rel="external nofollow">https://xdaforums.com/attachments/boot-txt.6083991/</a>
</p>

<p>
	<a href="https://xdaforums.com/attachments/depthcharge-print_all-txt.6084119/" rel="external nofollow">https://xdaforums.com/attachments/depthcharge-print_all-txt.6084119/</a>
</p>

<p>
	<a href="https://xdaforums.com/attachments/uboot_sunxi_printenv-txt.6083992/" rel="external nofollow">https://xdaforums.com/attachments/uboot_sunxi_printenv-txt.6083992/</a>
</p>

<p>
	<a href="https://xdaforums.com/attachments/uboot_more-info-txt.6084356/" rel="external nofollow">https://xdaforums.com/attachments/uboot_more-info-txt.6084356/</a>
</p>

<p>
	 
</p>
]]></description><guid isPermaLink="false">36735</guid><pubDate>Tue, 26 Mar 2024 11:51:38 +0000</pubDate></item><item><title>Can&#x2019;t read any posts</title><link>https://forum.armbian.com/topic/36643-can%E2%80%99t-read-any-posts/</link><description><![CDATA[<p>
	Any reason why even after being registered for a month and having validated my email, I still cannot see any posts in any of the topics on this entire forum?
</p>

<p>
	 
</p>

<p>
	For some reason it was just a mobile phone issue. 
</p>
]]></description><guid isPermaLink="false">36643</guid><pubDate>Sat, 23 Mar 2024 02:00:44 +0000</pubDate></item><item><title>OpenWrt Build support for Orange Pi R1 H3</title><link>https://forum.armbian.com/topic/35604-openwrt-build-support-for-orange-pi-r1-h3/</link><description><![CDATA[<p>
	Hi All,
</p>

<p>
	 
</p>

<p>
	I am looking for the steps to build custom Linux preferably <strong>OpenWrt distro </strong>(otherwise Ubuntu or any other distro should be fine at this moment) for <strong>Orange Pi R1 H3</strong>.
</p>

<p>
	I searched it in <a href="https://www.armbian.com/download/?device_support=Community%20maintained&amp;tx_maker=xunlong" rel="external nofollow">https://www.armbian.com/download/?device_support=Community maintained&amp;tx_maker=xunlong</a> for the same.
</p>

<p>
	But did find anything for <strong>Pi R1 H3 board.</strong>
</p>

<p>
	 
</p>

<p>
	Thanks in advance for helping me...<br />
	<br />
	Warm regards,
</p>

<p>
	 
</p>

<p>
	Manoj
</p>
]]></description><guid isPermaLink="false">35604</guid><pubDate>Mon, 04 Mar 2024 10:34:04 +0000</pubDate></item><item><title>Torrent for OPI PC2</title><link>https://forum.armbian.com/topic/35566-torrent-for-opi-pc2/</link><description><![CDATA[<p>
	The minimal (Bookworm) torrent of <a href="https://www.armbian.com/orange-pi-pc2/" rel="external nofollow">Orange Pi PC2</a> was only shared by one source when I added it today, and that source is only at 71%.
</p>

<p>
	Not sure if this is another person also trying to download and the original source no longer shared, or if this is the original source and it is broken.<br />
	<br />
	I can ofc download the file via https, but felt I wanted to let you know.
</p>
]]></description><guid isPermaLink="false">35566</guid><pubDate>Sun, 03 Mar 2024 11:48:19 +0000</pubDate></item><item><title>SOLD - Selling Helios64 full bundle</title><link>https://forum.armbian.com/topic/35385-sold-selling-helios64-full-bundle/</link><description><![CDATA[<p>
	Hi folks,
</p>

<p>
	 
</p>

<p>
	I upgraded my server towards a bigger machine and unfortunately neither my parents nor brothers need a reliable fileserver. So this little machine goes on sale.
</p>

<p>
	 
</p>

<p>
	- Helios64 with all trays + 2 SSD inserts
</p>

<p>
	- Fully assembled
</p>

<p>
	- Original packaging
</p>

<p>
	- Changed the two fans for Noctuas in order to get an even more silent server
</p>

<p>
	 
</p>

<p>
	What's missing is the Battery for UPS. Mine was faulty and caused me some random reboots. 
</p>

<p>
	Condition is mint / very good.
</p>

<p>
	 
</p>

<p>
	System is stable with 5.15.93 running OMV6.
</p>

<p>
	 
</p>

<p>
	If you would like pictures of the machine itself please drop me a note.
</p>

<p>
	 
</p>

<p>
	 
</p>

<p>
	<a class="ipsAttachLink ipsAttachLink_image" href="https://forum.armbian.com/uploads/monthly_2024_02/Bildschirmfoto2024-02-28um11_52_27.jpg.8b23d66eaa6bef405bfea7ca73fd985c.jpg" data-fileid="11873" data-fileext="jpg" rel=""><img alt="Bildschirmfoto 2024-02-28 um 11.52.27.jpg" class="ipsImage ipsImage_thumbnailed" data-fileid="11873" data-ratio="38.8" width="1000" src="https://forum.armbian.com/uploads/monthly_2024_02/Bildschirmfoto2024-02-28um11_52_27.thumb.jpg.81e2c3e0b0a75567f54091ec2f280e55.jpg" /></a>
</p>
]]></description><guid isPermaLink="false">35385</guid><pubDate>Thu, 29 Feb 2024 18:18:01 +0000</pubDate></item><item><title>Suggestion for new SBC to buy</title><link>https://forum.armbian.com/topic/33097-suggestion-for-new-sbc-to-buy/</link><description><![CDATA[<p>
	Hello guys,
</p>

<p>
	 
</p>

<p>
	After seeing a friend bought and tried a Raspberry Pi 5 device, I am very excited about what can be done with such a small single-board computer. So now I'm interested in getting a suitable single-board computer to buy. What <abbr title="Single board computer"><abbr title="Single board computer">SBC</abbr></abbr> is suitable to buy if I want to use virtualization sofware such as VMware ESXi for ARM? Running multiple OS at once, is my mainly use. Getting used to Intel CPU &amp; Windows and now I want to switch to ARM and <abbr title="System On a Chip">Linux</abbr> environment.
</p>

<p>
	 
</p>

<p>
	Thanks in advanced.
</p>
]]></description><guid isPermaLink="false">33097</guid><pubDate>Sun, 07 Jan 2024 20:40:19 +0000</pubDate></item><item><title>I just want to buy a t-shirt or two...</title><link>https://forum.armbian.com/topic/33555-i-just-want-to-buy-a-t-shirt-or-two/</link><description><![CDATA[<p>
	This does not look good...<br />
	Did someone forget to renew the certificates?
</p>

<p>
	 
</p>

<p>
	<a class="ipsAttachLink ipsAttachLink_image" href="https://forum.armbian.com/uploads/monthly_2024_01/image.png.cad53ce79b0f1d2708a561831ad1479d.png" data-fileid="11737" data-fileext="png" rel=""><img class="ipsImage ipsImage_thumbnailed" data-fileid="11737" data-ratio="68.10" width="1000" alt="image.thumb.png.d98b838f8a18b5bcbe630edf993db078.png" src="https://forum.armbian.com/uploads/monthly_2024_01/image.thumb.png.d98b838f8a18b5bcbe630edf993db078.png" /></a>
</p>
]]></description><guid isPermaLink="false">33555</guid><pubDate>Tue, 30 Jan 2024 15:50:01 +0000</pubDate></item><item><title>Instruction on how to use wireless WoL (Wake on LAN) using RTL8189FS (RTL8189FTV) module</title><link>https://forum.armbian.com/topic/33452-instruction-on-how-to-use-wireless-wol-wake-on-lan-using-rtl8189fs-rtl8189ftv-module/</link><description><![CDATA[<p style="text-align:center;">
	<span style="font-size:26px;">Instruction on how to use wireless WoL (Wake on LAN) using RTL8189FS example in <strong>Armbian 23.x Bookworm</strong></span><br />
	(This wireless WIFI adapter is installed in Oprange Pi <strong>Lite</strong>/Oprange Pi <strong>Plus(2E)</strong>/Orange Pi <strong>Zero Plus</strong>/Oprange Pi <strong>PC Plus</strong>/Oprange Pi <strong>2</strong>/etc...)
</p>

<p>
	 
</p>

<p>
	<span style="font-size:18px;">1. First of all we need to change the device tree configuration file <strong><abbr title="Device tree source"><abbr title="Device tree source">dts</abbr></abbr></strong> file for our single board. The point is that for most WIFI drivers for SDIO interface there is a normal configuration of single board wake-up via interrupt and therefore there is no need to go into <strong><abbr title="Device tree source"><abbr title="Device tree source">dts</abbr></abbr></strong>. In the driver for RTL8189FS (aka RTL8189FTV) there is NO such feature as "host-wake" interrupt and we will have to make small changes to wake up the single board when Magic packet (WoL) is detected through the "<abbr title="General purpose input/output"><abbr title="General purpose input/output">gpio</abbr></abbr>-keys" button module.</span>
</p>

<p>
	<span style="font-size:18px;">The same method will most likely work for the related RTL8189ES (aka RTL8189ETV) adapter, but keep in mind that here you will most likely need other settings in the <strong><abbr title="Device tree source"><abbr title="Device tree source">dts</abbr></abbr></strong> file, since the gpios (for wifi_rst and wifi_wake) for your single-board adapter will be under a different number.</span>
</p>

<p>
	 
</p>

<div class="ipsSpoiler" data-ipsspoiler="">
	<div class="ipsSpoiler_header">
		<span>Скрытый текст</span>
	</div>

	<div class="ipsSpoiler_contents">
		<p>
			1.1. Copy the attached file without txt extension somewhere on the single board dir.
		</p>

		<p>
			<em>(note that here the <strong>sw4</strong> (or Power) button configuration is additionally fixed to allow safe shutdown/wakeup of the device, since some time ago this option was broken in new kernels).</em>
		</p>

		<p>
			 
		</p>

		<p>
			1.2. Regarding the same path where our <abbr title="Device tree source"><abbr title="Device tree source">dts</abbr></abbr> file is, create a <strong>dtbo</strong> file:
		</p>

		<pre class="ipsCode prettyprint lang-html prettyprinted"><span class="pln">sudo dtc -@ -I dts -O dtb -o /boot/dtb/overlay/sun8i-h3-wol-wakeup-for-rtl8189fs.dtbo wol-wakeup-for-rtl8189fs.dts</span></pre>

		<p>
			 
		</p>

		<p>
			1.3. Activate System-&gt;Hardware-&gt;wol-wakeup-for-rtl8189fs our created profile via armbian-config:
		</p>

		<pre class="ipsCode prettyprint lang-html prettyprinted"><span class="pln">sudo armbian-config</span></pre>

		<p>
			<img alt="COM7-PuTTY24_01.202418_39_09.png.f824fd14cc17c434441eca5f1857f419.png" class="ipsImage ipsImage_thumbnailed" data-fileid="11702" data-ratio="60.12" width="642" src="https://forum.armbian.com/uploads/monthly_2024_01/COM7-PuTTY24_01.202418_39_09.png.f824fd14cc17c434441eca5f1857f419.png" />
		</p>

		<p>
			 
		</p>

		<p>
			Click <strong>Save</strong> then <strong>Back</strong>, in the window agree to <strong>Reboot</strong>
		</p>

		<p>
			 
		</p>

		<p>
			1.4. After rebooting the suspend mode of these devices should work properly, because the <strong>KEY_POWER</strong> and <strong>keep-power-in-suspend</strong> options were missing, you can check the suspend mode with the command:
		</p>

		<pre class="ipsCode prettyprint lang-html prettyprinted"><span class="pln">sudo systemctl suspend</span></pre>

		<p>
			<em>(keep in mind that the power/wake button must work properly to wake up the single board, but we should have already fixed this problem with our <strong>dtbo</strong> configuration file)</em>
		</p>
	</div>
</div>

<p>
	 
</p>

<p>
	<span style="font-size:18px;">2 The second step is to compile and install a new driver for RTL8189FS with WoL function enabled, I will do it on the single board itself. You can also do cross compilation (do it on your computer).</span>
</p>

<p>
	 
</p>

<div class="ipsSpoiler" data-ipsspoiler="">
	<div class="ipsSpoiler_header">
		<span>Скрытый текст</span>
	</div>

	<div class="ipsSpoiler_contents">
		<p>
			2.1. Install dependencies:
		</p>

		<pre class="ipsCode prettyprint lang-html prettyprinted"><span class="pln">sudo apt update
sudo apt install git build-essential dkms linux-headers-current-sunxi</span></pre>

		<p>
			 
		</p>

		<p>
			<em>2.2. Clone the driver repository, go to a convenient folder in advance, I do it directly in <strong>~/</strong> directory:</em>
		</p>

		<pre class="ipsCode prettyprint lang-html prettyprinted"><span class="pln">git clone https://github.com/jwrdegoede/rtl8189ES_linux -b rtl8189fs
cd rtl8189ES_linux</span></pre>

		<p>
			 
		</p>

		<p>
			2.3. Do the replacement in Makefile, note you can also manually edit say in <strong>nano</strong> and put "=y" for these options, but I will use <strong>sed</strong>:
		</p>

		<pre class="ipsCode prettyprint lang-html prettyprinted"><span class="pln">sed -i 's/CONFIG_WOWLAN = n/CONFIG_WOWLAN = y/' Makefile
sed -i 's/CONFIG_GPIO_WAKEUP = n/CONFIG_GPIO_WAKEUP = y/' Makefile
sed -i 's/CONFIG_RTW_DEBUG = y/CONFIG_RTW_DEBUG = n/' Makefile</span></pre>

		<p>
			 
		</p>

		<p>
			2.4. Now before compiling we need to make sure we have a path (after installing linux-headers-current-sunxi):
		</p>

		<pre class="ipsCode prettyprint lang-html prettyprinted"><span class="pln">ls /lib/modules/$(uname -r)/build</span></pre>

		<p>
			And also need the full path (starting from /) where the <strong>rtl81899ES_linux</strong> sources folder is located.
		</p>

		<p>
			 
		</p>

		<p>
			2.5. Now compile the driver:
		</p>

		<pre class="ipsCode prettyprint lang-html prettyprinted"><span class="pln">make ARCH=arm -C /lib/modules/$(uname -r)/build M=/home/deoptim/rtl8189ES_linux modules -j4</span></pre>

		<p>
			<em>(note that the path of the <strong>rtl81899ES_linux</strong> src here is my path, you should replace it with your own)</em>
		</p>

		<p>
			 
		</p>

		<p>
			<em>2.6. After successful compilation and before installing the driver, make a backup copy of the existing <strong>8189fs.ko</strong> module:</em>
		</p>

		<pre class="ipsCode prettyprint lang-html prettyprinted"><span class="pln">sudo mv /lib/modules/$(uname -r)/kernel/drivers/net/wireless/rtl8189fs/8189fs.ko /lib/modules/$(uname -r)/kernel/drivers/net/wireless/rtl8189fs/8189fs._</span></pre>

		<p>
			 
		</p>

		<p>
			2.7. You can now install the driver:
		</p>

		<pre class="ipsCode prettyprint lang-html prettyprinted"><span class="pln">sudo make install MODDESTDIR=/lib/modules/$(uname -r)/kernel/drivers/net/wireless/rtl8189fs/</span></pre>

		<p>
			 
		</p>

		<p>
			2.8. Add additional parameters to module config file (when it firs time load module at boot process) to /etc/modprobe.d/8189fs.conf file and again, I use <strong>sed</strong>:
		</p>

		<pre class="ipsCode prettyprint lang-html prettyprinted"><span class="pln">sudo sed -i 's/options 8189fs rtw_power_mgnt=0 rtw_enusbss=0/options 8189fs rtw_power_mgnt=0 rtw_enusbss=0 rtw_wakeup_event=0x5 rtw_wowlan_sta_mix_mode=0x1/' /etc/modprobe.d/8189fs.conf</span></pre>

		<p>
			<em>(there are details about the important <strong>rtw_wakeup_event</strong> parameter in the "Additionally" section)</em>
		</p>

		<p>
			 
		</p>

		<p>
			2.9. Now you can already <strong>reboot the single board</strong>, which is highly recommended. Or hot-swap the module with a command(without reboot):
		</p>

		<pre class="ipsCode prettyprint lang-html prettyprinted"><span class="pln">sudo modprobe -r 8189fs &amp;&amp; sudo modprobe 8189fs</span></pre>

		<p>
			 
		</p>

		<div class="ipsSpoiler" data-ipsspoiler="">
			<div class="ipsSpoiler_header">
				<span>Скрытый текст</span>
			</div>

			<div class="ipsSpoiler_contents">
				<p>
					To restore the original module:
				</p>

				<pre class="ipsCode prettyprint lang-html prettyprinted"><span class="pln">sudo mv /lib/modules/$(uname -r)/kernel/drivers/net/wireless/rtl8189fs/8189fs._ /lib/modules/$(uname -r)/kernel/drivers/net/wireless/rtl8189fs/8189fs.ko
sudo /sbin/depmod -a
sudo modprobe -r 8189fs &amp;&amp; sudo modprobe 8189fs</span></pre>

				<p>
					 
				</p>
			</div>
		</div>

		<p>
			 
		</p>
	</div>
</div>

<p>
	 
</p>

<p>
	<span style="font-size:18px;">3. How to use WoL.</span>
</p>

<p>
	 
</p>

<div class="ipsSpoiler" data-ipsspoiler="">
	<div class="ipsSpoiler_header">
		<span>Скрытый текст</span>
	</div>

	<div class="ipsSpoiler_contents">
		<p>
			3.1. The first physical device phy0 is used to detect WoL, for example the command "<strong>iw dev</strong>" gives us the following list:
		</p>

		<pre class="ipsCode prettyprint lang-html prettyprinted"><span class="pln">deoptim@homeassistant:~$ iw dev
phy#1
        Interface wlan1
                ifindex 3
                wdev 0x100000001
                addr 02:81:e1:xx:xx:xx
                type managed
                txpower 12.00 dBm
phy#0
        Interface wlan0
                ifindex 2
                wdev 0x1
                addr 02:81:e1:xx:xx:xx
                ssid Apple Network XXXXXX
                type managed
                txpower 12.00 dBm
deoptim@homeassistant:~$</span></pre>

		<p>
			So the first interface we have <strong>wlan0</strong> (for the device phy#0), pay attention and memorize or write down the mac addr for it (not from this list address, but your configuration of course <img alt=":)" data-emoticon="" height="20" src="https://forum.armbian.com/uploads/emoticons/default_smile.png" srcset="https://forum.armbian.com/uploads/emoticons/smile@2x.png 2x" title=":)" width="20" /> ), it is at this address we will wake up single board and it is from the interface <strong>wlan0</strong> need to connect to the router or access point.
		</p>

		<p>
			 
		</p>

		<p>
			3.2. In order for the WoL mode to work, you need to enable it with the option (as in <a href="https://www.cyberciti.biz/faq/configure-wireless-wake-on-lan-for-linux-wifi-wowlan-card/" rel="external nofollow">this instruction</a><span class="ipsEmoji">😞</span>
		</p>

		<pre class="ipsCode prettyprint lang-html prettyprinted"><span class="pln">sudo iw phy0 wowlan enable any</span></pre>

		<p>
			<em>(note, if you want to use WoL permanently, this procedure should be repeated every time you boot the system, for example, write a command in the /etc/<abbr title="Release candidate"><abbr title="Release candidate">rc</abbr></abbr>.local file, also other options than "<strong>any" </strong>for this RTL8189FS driver do not work, the <strong>rtw_wakeup_event</strong> module parameter is used to filter a specific event (more details in the "Additionally" section). For example, to disable WoL you should change the enable value in the same <strong>iw</strong> utility parameter to "<strong>wowlan disable"</strong>.)</em>
		</p>

		<p>
			 
		</p>

		<p>
			<em>3.3. Now if we put our single board into sleep mode with the command:</em>
		</p>

		<pre class="ipsCode prettyprint lang-html prettyprinted"><span class="pln">sudo systemctl suspend</span></pre>

		<p>
			We will see that the single board has fallen asleep without disconnecting from the router or access point. Now if you try to wake it up using any standard WoL utility (<a href="https://www.nirsoft.net/utils/wake_on_lan.html" rel="external nofollow">for example</a> for Windows, or use <strong>wakeonlan</strong> for Linux), the single board will wake up.
		</p>
	</div>
</div>

<p>
	 
</p>

<p>
	<span style="font-size:18px;">4. Additionally.</span><br />
	 
</p>

<div class="ipsSpoiler" data-ipsspoiler="">
	<div class="ipsSpoiler_header">
		<span>Скрытый текст</span>
	</div>

	<div class="ipsSpoiler_contents">
		<p>
			4.1. Disadvantages and restrictions relate to the fact that the system uses two interfaces wlan0 and wlan1 - there are cases when a single board connected as a client swaps these interfaces for this connection.<br />
			If an access point (Hotspot) is used as the second interface - there may be configuration problems and wakeup will not work properly. So it is advisable to either <strong>NOT use</strong> the second interface (maybe even disable it at the compilation stage) or if the second interface is used - disable <strong>wlan1</strong> before starting the service "sudo systemctl suspend" and bring it up again after waking up.<br />
			<strong>upd:</strong> In my case I got out of the problem with this script /lib/systemd/system-sleep/my_script (give <strong>chmod +x</strong> exec permissions):
		</p>

		<pre class="ipsCode prettyprint lang-html prettyprinted"><span class="pln">#!/bin/sh
case $1/$2 in
  pre/*)
    echo "Going to $2..."
    systemctl stop watchdog.service
    if [ $(nmcli -f GENERAL.STATE dev show wlan0 | sed 's/.*\s//') != "(connected)" ]
    then
      nmcli dev con wlan0
      sleep 5
    fi
    ;;
  post/*)
    echo "Waking up from $2..."
    systemctl start watchdog.service
    ;;
esac</span></pre>

		<p>
			 
		</p>

		<p>
			4.2. The <strong>rtw_wakeup_event</strong> module parameter in the /etc/modprobe.d/8189fs.conf file configures the event at which the WIFI module wakes up the single board can be the following parameters:
		</p>

		<pre class="ipsCode prettyprint lang-html prettyprinted"><span class="pln">/*
 * bit[0]: magic packet wake up
 * bit[1]: unucast packet(HW/FW unuicast)
 * bit[2]: deauth wake up
 */</span></pre>

		<p>
			Accordingly, we used 0x5 (bit[0] and bit[2]) to filter magic packet and deauth (if we get disconnected from the access point, we need to wake up - otherwise we can't). You can choose the parameter for your needs individually or all at once. In the source code 0x7 was used by default (all bits were selected), but in this case ?false? triggering is possible, in practice it looked like unexpected waking up almost immediately after falling asleep.
		</p>

		<p>
			 
		</p>

		<p>
			4.3. Sometimes Magic packet is not enough and we need to use event Deauth (disconnecting from the access point) - the point is that we are not always sure that the router or access point is OK and it will not disconnect itself or drop our connection. In this case, if <abbr title="Single board computer"><abbr title="Single board computer">SBC</abbr></abbr> waking up from WoL is important, it is important for the single board to track which event wake it up, for example: if it were wake-up by event Deauth =&gt; then check if we are connected to the access point again =&gt; go back to suspend after a pause. If it were wake-up by event Magic Packet, then perform other actions.....<br />
			In this case, the wake-up event identifier via the WoL utility will help that's where it is in the driver:
		</p>

		<pre class="ipsCode prettyprint lang-html prettyprinted"><span class="pln">deoptim@homeassistant:~$ cat /proc/net/rtl8189fs/wlan0/wowlan_last_wake_reason
last wake reason: 0x25
deoptim@homeassistant:~$</span></pre>

		<p>
			 
		</p>

		<p>
			Here is an example where I rebooted my router (the options in <strong>rtw_wakeup_event</strong> were bit0 and bit2):
		</p>

		<pre class="ipsCode prettyprint lang-html prettyprinted"><span class="pln">deoptim@homeassistant:~$ cat /proc/net/rtl8189fs/wlan0/wowlan_last_wake_reason
last wake reason: 0x10
deoptim@homeassistant:~$</span></pre>

		<p>
			 
		</p>

		<p>
			Here are the possible values from the sources:
		</p>

		<pre class="ipsCode prettyprint lang-html prettyprinted"><span class="pln">typedef enum _WAKEUP_REASON{
	RX_PAIRWISEKEY					= 0x01,
	RX_GTK							= 0x02,
	RX_FOURWAY_HANDSHAKE			= 0x03,
	RX_DISASSOC						= 0x04,
	RX_DEAUTH						= 0x08,
	RX_ARP_REQUEST					= 0x09,
	FW_DECISION_DISCONNECT			= 0x10,
	RX_MAGIC_PKT					= 0x21,
	RX_UNICAST_PKT					= 0x22,
	RX_PATTERN_PKT					= 0x23,
	RTD3_SSID_MATCH					= 0x24,
	RX_REALWOW_V2_WAKEUP_PKT		= 0x30,
	RX_REALWOW_V2_ACK_LOST			= 0x31,
	ENABLE_FAIL_DMA_IDLE			= 0x40,
	ENABLE_FAIL_DMA_PAUSE			= 0x41,
	RTIME_FAIL_DMA_IDLE				= 0x42,
	RTIME_FAIL_DMA_PAUSE			= 0x43,
	RX_PNO							= 0x55,
	AP_OFFLOAD_WAKEUP				= 0x66,
	CLK_32K_UNLOCK					= 0xFD,
	CLK_32K_LOCK					= 0xFE
}WAKEUP_REASON;</span></pre>

		<p>
			 
		</p>

		<p>
			(for some reason 0x25 is not in the list, strange..... <strong>upd</strong>: the <a href="https://play.google.com/store/apps/details?id=com.bitklog.wolon" rel="external nofollow">WolOn utility</a> on Android unexpectedly gave another correct output as <strong>0x21</strong>, i.e. the output still depends on the utility you use, I remind you that <strong>0x25</strong> is a Windows WoL utility).
		</p>

		<p>
			 
		</p>

		<p>
			By the way, we can change the <strong>wow_wakeup_event</strong> parameter (aka <strong>rtw_wakeup_event</strong>) on the fly, so we don't need to reboot the module if we need to do it quickly:
		</p>

		<pre class="ipsCode prettyprint lang-html prettyprinted"><span class="pln">sudo sh -c 'echo 5 &gt; /proc/net/rtl8189fs/wlan0/wow_wakeup_event'</span></pre>

		<p>
			 
		</p>

		<p>
			4.4. It is also possible to wake-up a single board by event Pattern - it will wake-up when a packet with possible such patterns is sent (<a href="https://usermanual.wiki/Document/QuickStartGuideforWOW.399483868/help" rel="external nofollow">detailed instructions</a><span class="ipsEmoji">😞</span>
		</p>

		<pre class="ipsCode prettyprint lang-html prettyprinted"><span class="pln">/*
* IP filter This pattern if for a frame containing a ip packet:
* AA:AA:AA:AA:AA:AA:BB:BB:BB:BB:BB:BB:CC:CC:DD:-:-:-:-:-:-:-:-:EE:-:-:FF:FF:FF:FF:GG:GG:GG:GG:HH:HH:II:II
*
* A: Ethernet destination address
* B: Ethernet source address
* C: Ethernet protocol type
* D: IP header VER+Hlen, use: 0x45 (4 is for ver 4, 5 is for len 20)
* E: IP protocol
* F: IP source address ( 192.168.0.4: C0:A8:00:2C )
* G: IP destination address ( 192.168.0.4: C0:A8:00:2C )
* H: Source port (1024: 04:00)
* I: Destination port (1024: 04:00)
*/</span></pre>

		<p>
			 
		</p>

		<p>
			This pattern is put in directly by the <strong>iwpriv</strong> utility (not <strong>iw</strong> for this driver, I repeat, only the "<strong>any"</strong> option works here), for example:
		</p>

		<pre class="ipsCode prettyprint lang-html prettyprinted"><span class="pln">sudo iwpriv wlan0 wow_set_pattern pattern=-:-:-:-:-:-:-:-:-:-:-:-:08:00:45:-:-:-:-:-:-:-:-:06:-:-:0A:00:01:F6:-:-:-:-:13:C5:-:-</span></pre>

		<p>
			(where <span>:<strong>08</strong>:<strong>00</strong>:  is </span><a href="https://en.wikipedia.org/wiki/EtherType" rel="external nofollow">Internet Protocol version 4 (IPv4)</a> and <span>:<strong>06</strong>:  is </span><a href="https://en.wikipedia.org/wiki/IEEE_802.2" rel="external nofollow">Reserved for DoD IP</a>)
		</p>

		<p>
			 
		</p>

		<p>
			To clear a pattern, you must use the command:
		</p>

		<pre class="ipsCode prettyprint lang-html prettyprinted"><span class="pln">sudo iwpriv wlan0 wow_set_pattern clean</span></pre>

		<p>
			 
		</p>

		<p>
			You can find out whether the current pattern is written to the driver (or not) by command:
		</p>

		<pre class="ipsCode prettyprint lang-html prettyprinted"><span class="pln">cat /proc/net/rtl8189fs/wlan0/wow_pattern_info</span></pre>

		<p>
			 
		</p>

		<p>
			When the single board wakes-up on the current pattern, there will be this value:
		</p>

		<pre class="ipsCode prettyprint lang-html prettyprinted"><span class="pln">deoptim@homeassistant:~$ cat /proc/net/rtl8189fs/wlan0/wowlan_last_wake_reason
last wake reason: 0x23
deoptim@homeassistant:~$</span></pre>

		<p>
			 
		</p>

		<p>
			 
		</p>

		<p>
			4.5. The number of wake-up's or interrupt statistics for a given wake-up (for each core) for the entire single board operation (before power off/reboot) can be viewed with the command:
		</p>

		<pre class="ipsCode prettyprint lang-html prettyprinted"><span class="pln">deoptim@homeassistant:~$ cat /proc/interrupts  | grep wifi-host-wakeup
 83:          4          0          1          0  sunxi_pio_edge  42 Edge      wifi-host-wakeup
deoptim@homeassistant:~$</span></pre>

		<p>
			 
		</p>
	</div>
</div>

<p>
	 
</p>

<p>
	<a class="ipsAttachLink" data-fileext="txt" data-fileid="11701" href="https://forum.armbian.com/applications/core/interface/file/attachment.php?id=11701&amp;key=70db9bc47b7928b8c92841092e02ba85" rel="">wol-wakeup-for-rtl8189fs.<abbr title="Device tree source"><abbr title="Device tree source">dts</abbr></abbr>.txt</a>
</p>

<p>
	<a class="ipsAttachLink" data-fileext="pdf" data-fileid="11707" href="https://forum.armbian.com/applications/core/interface/file/attachment.php?id=11707&amp;key=f681500e61f4006b342e8172932f4d80" rel="">QuickStartGuideforWOW.399483868.pdf</a>
</p>

<p>
	<a href="https://4pda.to/forum/index.php?showtopic=750921&amp;view=findpost&amp;p=127832091" rel="external nofollow">Link to original source</a>
</p>
]]></description><guid isPermaLink="false">33452</guid><pubDate>Fri, 26 Jan 2024 13:29:30 +0000</pubDate></item><item><title>OPI5+ 32GB RAM</title><link>https://forum.armbian.com/topic/33375-opi5-32gb-ram/</link><description><![CDATA[<p>
	Has anyone heard any news on where and when this is available ?
</p>

<p>
	some of the AliExpress stores just appears to be sold out of the 32gb ram version.
</p>
]]></description><guid isPermaLink="false">33375</guid><pubDate>Tue, 23 Jan 2024 11:43:18 +0000</pubDate></item><item><title>[WTS] Orange Pi 800 64GB version (Europe)</title><link>https://forum.armbian.com/topic/33055-wts-orange-pi-800-64gb-version-europe/</link><description><![CDATA[<p>
	I have an Orange Pi 800 64GB version for sale located in Denmark, Europe. If you fancy a hackable Orange Pi with support for a lot of Linux based distributions in a nice package with a lot of connection possibilities and a built in keyboard but don't want to pay EU import VAT this is your chance!
</p>

<p>
	If desired I can flash it for you with OS of choice.
</p>

<p>
	Condition: Like-new in box but with minor wear inside box (see images). This does not have any impact regarding transportation.<br />
	Price idea: 100€ + shipping<br />
	Ships to: All EU countries<br />
	Payment method: PayPal
</p>

<p>
	If you have any questions please let me know.<br />
	<br />
	I'll attend FOSDEM '24 hence I can send it from Brussels or deliver it in person if this is agreed upon prior to the event.
</p>

<p>
	 
</p>

<p>
	<a class="ipsAttachLink ipsAttachLink_image" href="https://forum.armbian.com/uploads/monthly_2024_01/20230619_154337.jpg.6e3abdf8431550434403428ae36d219b.jpg" data-fileid="11556" data-fileext="jpg" rel=""><img alt="20230619_154337.jpg" class="ipsImage ipsImage_thumbnailed" data-fileid="11556" data-ratio="56.3" width="1000" src="https://forum.armbian.com/uploads/monthly_2024_01/20230619_154337.thumb.jpg.903c3bcfcecbd5c210a478f3f3d51a77.jpg" /></a>
</p>

<p>
	<a class="ipsAttachLink ipsAttachLink_image" href="https://forum.armbian.com/uploads/monthly_2024_01/20230910_002408.jpg.7faae19717c31db183d687cab9bfab79.jpg" data-fileid="11554" data-fileext="jpg" rel=""><img alt="20230910_002408.jpg" class="ipsImage ipsImage_thumbnailed" data-fileid="11554" data-ratio="56.3" width="1000" src="https://forum.armbian.com/uploads/monthly_2024_01/20230910_002408.thumb.jpg.07df32b8d8a0a4f6c2912bc6dbde71fb.jpg" /></a>
</p>

<p>
	<a class="ipsAttachLink ipsAttachLink_image" href="https://forum.armbian.com/uploads/monthly_2024_01/20230619_154428.jpg.6b3c2a31ce615e3d5e7f5b102e6520d6.jpg" data-fileid="11555" data-fileext="jpg" rel=""><img alt="20230619_154428.jpg" class="ipsImage ipsImage_thumbnailed" data-fileid="11555" data-ratio="177.73" width="422" src="https://forum.armbian.com/uploads/monthly_2024_01/20230619_154428.thumb.jpg.ea18c50fb3372516a1f6dd3ae698b0e3.jpg" /></a><a class="ipsAttachLink ipsAttachLink_image" href="https://forum.armbian.com/uploads/monthly_2024_01/20230619_154421_2.jpg.ae23ebf0102556e4116c2f87f2ba4676.jpg" data-fileid="11557" data-fileext="jpg" rel=""> <img alt="20230619_154421_2.jpg" class="ipsImage ipsImage_thumbnailed" data-fileid="11557" data-ratio="210.08" width="357" src="https://forum.armbian.com/uploads/monthly_2024_01/20230619_154421_2.thumb.jpg.3a7193fc0c9678ab76db82334935d0f4.jpg" /></a>
</p>

<p>
	 
</p>
]]></description><guid isPermaLink="false">33055</guid><pubDate>Wed, 03 Jan 2024 22:18:34 +0000</pubDate></item><item><title>Java UIO updated for latest Armbian and JDK 21.</title><link>https://forum.armbian.com/topic/33013-java-uio-updated-for-latest-armbian-and-jdk-21/</link><description><![CDATA[<p>
	Java UIO offers robust Java interfaces optimized for Linux Userspace IO, emphasizing high performance. Engineered from scratch, it leverages contemporary kernel APIs, libraries, and cutting-edge code generation methodologies, embodying a state-of-the-art cross-platform solution. Rather than reinventing established paradigms, Java UIO harnesses existing standards, avoiding redundant development commonly observed in other IO libraries. Seamlessly supporting JDK 21 <abbr title="Long term support">LTS</abbr>, this framework integrates Project Lombok to streamline code, enhancing readability and conciseness.
</p>

<p>
	 
</p>

<p>
	<a href="https://github.com/sgjava/javauio" rel="external nofollow">https://github.com/sgjava/javauio</a>
</p>
]]></description><guid isPermaLink="false">33013</guid><pubDate>Sun, 31 Dec 2023 17:28:22 +0000</pubDate></item><item><title>Has anyone tried openRGB with armbian?</title><link>https://forum.armbian.com/topic/32578-has-anyone-tried-openrgb-with-armbian/</link><description><![CDATA[<p>
	Hi there,<br />
	<br />
	Has anyone tried openRGB with armbian?<br />
	I found a few references to Raspberry Pi and openRGB, but nothing really usable.<br />
	I would like to build a Kubernetes cluster and use an RGB fan to display the status of the cluster (and of course try to cool it down).<br />
	<br />
	Thanks.
</p>
]]></description><guid isPermaLink="false">32578</guid><pubDate>Fri, 15 Dec 2023 22:30:58 +0000</pubDate></item><item><title>Armbian Support for older ARM netbook?</title><link>https://forum.armbian.com/topic/32260-armbian-support-for-older-arm-netbook/</link><description><![CDATA[<p>
	I got an older Toshiba AC100 with Tegra processor. Is there a possibility to get Armbian running on this netbook? 
</p>
]]></description><guid isPermaLink="false">32260</guid><pubDate>Tue, 05 Dec 2023 20:01:53 +0000</pubDate></item><item><title>Linux kernel memory leak seen - skb_data_cache and skb_head_cache are major contributors</title><link>https://forum.armbian.com/topic/32321-linux-kernel-memory-leak-seen-skb_data_cache-and-skb_head_cache-are-major-contributors/</link><description><![CDATA[<p>
	Hi All,
</p>

<p>
	 
</p>

<p>
	I'm working with a linux5.4.213 (arm) - OpenWRT based (QCA driver) Mesh AP. Currently the device is running into Out of memory and looking at the slab info, we see skb_head_cache and skb_data_cache accounting a major increase.
</p>

<p>
	 
</p>

<p>
	But i don't have any clue on how to go about debugging the same. I came across similar issues discussed years ago, but there were no conclusion or methods to debug/triage the issue further.
</p>

<p>
	 
</p>

<p>
	We gave a shot with kmemtracer, but that seems to pretty much point to false positives and the module itself was contributing to leak and we were asked to turn the configs off.
</p>

<p>
	 
</p>

<p>
	If someone could point me on what the next set of debugging steps could be, would really help.
</p>

<p>
	 
</p>

<p>
	Thanks in advance!
</p>
]]></description><guid isPermaLink="false">32321</guid><pubDate>Thu, 07 Dec 2023 15:22:35 +0000</pubDate></item><item><title>RK3399 RAM overclocking rockpro64</title><link>https://forum.armbian.com/topic/18153-rk3399-ram-overclocking-rockpro64/</link><description><![CDATA[<p>
	Hi guys! 
</p>

<p>
	so, i've noted a major difference between the friendlyarm rk3399 sbcs and the other models, ant that's bc the friendly arm rk3399s run at 1866 mhz while the other models run at 1600 mhz. 
</p>

<p>
	that means 100 glmark2 points less, for example.I would like to know how to use this bootloader instead, and even then, how to even go further.
</p>

<p>
	 
</p>

<p>
	I overclocked my rockpro64 to 2.2 ghz for the big cores and 1.8 for the low power cores.
</p>

<p>
	Its interesting how much performance we can get with this cosmetic changes. obviously,its at my own risk. 
</p>

<p>
	the rockpro64 was tested at higher frequencies than 1866 mhz, so I would expect at least that armbian should bump the ram freq of the bootloader up to that frequency.
</p>

<p>
	 
</p>

<p>
	I would like to know how to unpack this bootloader, and how to ... use it, basically.. 
</p>

<p>
	 
</p>

<p>
	best regards!!
</p>

<p>
	 
</p>

<p>
	 
</p>

<p>
	 <a class="ipsAttachLink" contenteditable="false" data-fileid="8013" href="https://forum.armbian.com/applications/core/interface/file/attachment.php?id=8013" data-fileext="bin" rel="">rk3399_ddr_933MHz_v1.11.bin</a>
</p>
]]></description><guid isPermaLink="false">18153</guid><pubDate>Thu, 20 May 2021 02:12:50 +0000</pubDate></item><item><title>Installing headers and building driver for RTL8188 WiFi dongle for orange pi pc [`nmcli dev wifi list` not works]</title><link>https://forum.armbian.com/topic/17325-installing-headers-and-building-driver-for-rtl8188-wifi-dongle-for-orange-pi-pc-nmcli-dev-wifi-list-not-works/</link><description><![CDATA[<p>
	I just build  the build the driver for my RTL8188FTV that supported by rtl8188fu. It works as wifi hot spot but has some problems with  nmcli . I share what is done and I hope it be useful for others.
</p>

<p>
	 
</p>

<p>
	0. Install dkms , make and git:
</p>

<p>
	 
</p>

<pre class="ipsCode prettyprint lang-html prettyprinted">
<span class="pln">apt install dkms make git</span></pre>

<p>
	 
</p>

<p>
	1. Remove any existing source and dkms config for module <span>:</span>
</p>

<p>
	 
</p>

<p>
	<br />
	 
</p>

<pre class="ipsCode prettyprint lang-html prettyprinted">
<span class="pln"> dkms remove rtl8188fu/1.0 --all

 rm -f /lib/firmware/rtlwifi/rtl8188fufw.bin

 rm -f /etc/modprobe.d/rtl8188fu.conf

 rm -r /var/lib/dkms/rtl8188fu
</span></pre>

<p>
	 
</p>

<p>
	2.  Get current kernel version and install matching headers:
</p>

<p>
	 
</p>

<pre class="ipsCode prettyprint lang-html prettyprinted">
<span class="pln">uname -a </span></pre>

<p>
	 
</p>

<p>
	My results are:
</p>

<p>
	 
</p>

<p>
	<em> Linux orangepipc 5.10.21-<strong>sunxi </strong>#<strong>21.02.3</strong> SMP Mon Mar 8 00:28:04 UTC 2021 armv7l GNU/Linux</em>
</p>

<p>
	 
</p>

<p>
	so my matching kernel headers package would be `linux-headers-current-sunxi=21.02.3` . You might replace `sunxi` and `21.02.3` depending on your top results. I installed it by specifying version:
</p>

<pre class="ipsCode prettyprint lang-html prettyprinted">
<span class="pln"> apt install linux-headers-current-sunxi=21.02.3
</span></pre>

<p>
	 
</p>

<p>
	3. Make kernels headers scripts:
</p>

<pre class="ipsCode prettyprint lang-html prettyprinted">
<span class="pln">cd /usr/src/linux-headers-$(uname -r)
make scripts</span></pre>

<p>
	 
</p>

<p>
	4.  Clone arm branch from driver repository<span>:</span>
</p>

<p>
	 
</p>

<pre class="ipsCode prettyprint lang-html prettyprinted">
<span class="pln">git clone -b arm https://github.com/kelebek333/rtl8188fu rtl8188fu-arm</span></pre>

<p>
	 
</p>

<p>
	5. Disable power saving in make config. find and replace this variable in `./rtl8188fu-arm/Makefile` and set as below:
</p>

<pre class="ipsCode prettyprint lang-html prettyprinted">
<span class="pln">CONFIG_POWER_SAVING = n 
CONFIG_WIFI_MONITOR = y</span></pre>

<p>
	 
</p>

<p>
	 
</p>

<p>
	6. Build and install driver:
</p>

<pre class="ipsCode prettyprint lang-html prettyprinted">
<span class="pln">ln -s /lib/modules/$(uname -r)/build/arch/arm /lib/modules/$(uname -r)/build/arch/armv7l
dkms add ./rtl8188fu-arm
dkms build rtl8188fu/1.0
dkms install rtl8188fu/1.0
cp ./rtl8188fu/firmware/rtl8188fufw.bin /lib/firmware/rtlwifi/</span></pre>

<p>
	 
</p>

<p>
	 
</p>

<p>
	 
</p>

<p>
	# Known problems <span><span>:</span></span>
</p>

<p>
	- ` nmcli dev wifi list` not works.
</p>

<p>
	 
</p>

<p>
	Refrences:
</p>

<p>
	- <a href="https://github.com/kelebek333/rtl8188fu/tree/arm#how-to-install-for-arm-devices" rel="external nofollow">https://github.com/kelebek333/rtl8188fu/tree/arm#how-to-install-for-arm-devices</a>
</p>

<p>
	- <a href="https://docs.armbian.com/User-Guide_Advanced-Features/#how-to-build-a-wireless-driver" rel="external nofollow">https://docs.armbian.com/User-Guide_Advanced-Features/#how-to-build-a-wireless-driver</a>
</p>

<p>
	- <a href="https://forum.armbian.com/topic/13628-help-me-to-setup-a-wifi-ap-via-command-line/?do=findComment&amp;comment=104106" rel="">https://forum.armbian.com/topic/13628-help-me-to-setup-a-wifi-ap-via-command-line/?do=findComment&amp;comment=104106</a>
</p>

<p>
	 
</p>

<p>
	- <a href="https://github.com/ulli-kroll/rtl8188fu" rel="external nofollow">https://github.com/ulli-kroll/rtl8188fu</a>
</p>

<p>
	- <a href="https://askubuntu.com/a/1131265/483814" rel="external nofollow">https://askubuntu.com/a/1131265/483814</a>
</p>

<p>
	- <a href="https://github.com/brektrou/rtl8821CU#arm-architecture-tweak-for-this-driver-this-solves-compilation-problem-of-this-driver" rel="external nofollow">https://github.com/brektrou/rtl8821CU#arm-architecture-tweak-for-this-driver-this-solves-compilation-problem-of-this-driver</a>
</p>
]]></description><guid isPermaLink="false">17325</guid><pubDate>Sun, 21 Mar 2021 12:29:11 +0000</pubDate></item><item><title>OverlayFS - read only root filesystem</title><link>https://forum.armbian.com/topic/19296-overlayfs-read-only-root-filesystem/</link><description><![CDATA[<p>
	Hi,
</p>

<p>
	 
</p>

<p>
	is possible to setup overlayf on Amrbian? I'm using Orange Pi Zero.
</p>

<p>
	 
</p>

<p>
	I found only this <a href="https://docs.armbian.com/User-Guide_Advanced-Features/#how-to-freeze-your-filesystem-outdated" rel="external nofollow">https://docs.armbian.com/User-Guide_Advanced-Features/#how-to-freeze-your-filesystem-outdated</a> and docs is outdated.
</p>

<p>
	 
</p>

<p>
	On Rapsbian I can enable overlayfs directly from <em>raspi-config</em>. Is there any way how to do the same on Armbian?
</p>

<p>
	 
</p>

<p>
	Thanks for help.
</p>

<p><a href="https://forum.armbian.com/uploads/monthly_2021_11/39652baf78d22a4cee93adab41cb4bf8198168c6.png.1740bf76d2468175139e30fcd8dda4ad.png" class="ipsAttachLink ipsAttachLink_image"><img data-fileid="8476" src="https://forum.armbian.com/uploads/monthly_2021_11/39652baf78d22a4cee93adab41cb4bf8198168c6.png.1740bf76d2468175139e30fcd8dda4ad.png" data-ratio="59.16" width="715" class="ipsImage ipsImage_thumbnailed" alt="39652baf78d22a4cee93adab41cb4bf8198168c6.png"></a></p>]]></description><guid isPermaLink="false">19296</guid><pubDate>Tue, 16 Nov 2021 14:09:44 +0000</pubDate></item><item><title>i want to dive into the creating of file-systems on Linux.&#xA0;</title><link>https://forum.armbian.com/topic/30076-i-want-to-dive-into-the-creating-of-file-systems-on-linux%C2%A0/</link><description><![CDATA[<p>
	 
</p>

<p>
	i want to dive into the creating of file-systems on Linux. 
</p>

<p>
	 
</p>

<p>
	 
</p>

<p>
	so i have some ideas:  can you give me some hints on these steps.  
</p>

<p>
	 
</p>

<p>
	can i break all down and say so: - in order to do the very first steps in creating a file system
</p>

<p>
	<br />
	... basically, I'm trying to do the following steps:
</p>

<p>
	- create a disk image of about 500MB;<br />
	- create a GPT;<br />
	- create a FAT32 partition in the first 300MB(I'll call it UEFI);<br />
	- create a FAT32 partition in the remaining bytes(I'll call it SYSTEM);<br />
	- create the following subdirectory in the UEFI partition: /EFI/BOOT/;
</p>

<p>
	<br />
	that said we have the following things: 
</p>

<p>
	Layouting a disk image and copying files into it
</p>

<p>
	 
</p>

<pre class="ipsCode prettyprint lang-html prettyprinted"><span class="pln">mkfs.vfat /dev/md3</span></pre>

<p>
	 
</p>

<p>
	# Creates an empty disk image of 33MB.
</p>

<p>
	 
</p>

<pre class="ipsCode prettyprint lang-html prettyprinted"><span class="pln">`dd if=/dev/zero of=uefi.img bs=1M count=330</span></pre>

<p>
	 
</p>

<p>
	# Formats the disk image as FAT32
</p>

<p>
	 
</p>

<pre class="ipsCode prettyprint lang-html prettyprinted"><span class="pln">mkfs.vfat uefi.img -F 32</span></pre>

<p>
	<br />
	 
</p>

<p>
	# Creates the requested subdirectories.
</p>

<p>
	<br />
	 
</p>

<pre class="ipsCode prettyprint lang-html prettyprinted"><span class="pln">mmd -i uefi.img ::/EFI
mmd -i uefi.img ::/EFI/BOOT</span></pre>

<p>
	<br />
	 
</p>

<p>
	look forward to  hear from you<br />
	 
</p>
]]></description><guid isPermaLink="false">30076</guid><pubDate>Thu, 07 Sep 2023 12:16:34 +0000</pubDate></item><item><title>faulty realtek wifi driver freezes computer rtw88_8821ce</title><link>https://forum.armbian.com/topic/30618-faulty-realtek-wifi-driver-freezes-computer-rtw88_8821ce/</link><description><![CDATA[<p>
	I bought few Geobooks 1E  and all had regardless distro same issue. Random hangups immediately or few minutes after boot finished or after few days of run or hours.
</p>

<p>
	 
</p>

<p>
	On Armbian distro after trying some other things I enabled kernel messages in sysctl.conf. And then I got something like, luckily immediately when login prompt appeared, <span><span>:</span></span>
</p>

<p>
	rtw_8821ce 0000:01:00.0: failed to dequeue 4088 skb Tx queue 5, .... when laptop stopped responding to keyboard immediately afterwards.
</p>

<p>
	 
</p>

<p>
	After some research I found solution, plugged USB lan adapter, disabled wifi otherwise it would knocked system down a did these next steps to replace wifi driver and hopefully after reboot 4 of these laptops this driver seems to work better without hangups.
</p>

<p>
	<br />
	 
</p>

<p>
	nano /etc/modprobe.d/rtw88_8821ce.conf &amp;&amp; update-initramfs -k all -u
</p>

<p>
	ADD NEXT LINES INTO OPENED FILE =&gt;
</p>

<p>
	blacklist rtw88_8821ce<br />
	options rtw88_core disable_lps_deep=y <br />
	options rtw88_pci disable_msi=y disable_aspm=y
</p>

<p>
	 
</p>

<p>
	 
</p>

<p>
	NEXT COMMANDS:<br />
	sudo apt update &amp;&amp; sudo apt install bc module-assistant build-essential dkms git -y<br />
	cd /usr/src &amp;&amp; git clone <a href="https://github.com/tomaspinho/rtl8821ce.git" rel="external nofollow">https://github.com/tomaspinho/rtl8821ce.git</a><br />
	cd rtl8821ce<br />
	sudo m-a prepare<br />
	sudo ./dkms-install.sh<br />
	sudo nano /etc/modprobe.d/rtw88_8821ce.conf<br />
	blacklist rtw88_8821ce
</p>

<p>
	 
</p>

<p>
	note: it should work without "options" lines which I found elsewhere as solution to resolve this problem without driver update
</p>

<p>
	 
</p>

<p>
	 
</p>
]]></description><guid isPermaLink="false">30618</guid><pubDate>Sat, 07 Oct 2023 22:57:07 +0000</pubDate></item><item><title>Mali GPU vulnerabilities</title><link>https://forum.armbian.com/topic/30544-mali-gpu-vulnerabilities/</link><description><![CDATA[<p>
	Been hearing some news lately about some pretty big ARM Mali <abbr title="Graphic processing unit (3D acceleration)">GPU</abbr> vulnerabilities. Old boards could be affected, including ones that are not maintained.
</p>

<p>
	 
</p>

<p>
	<a href="https://hothardware.com/news/arm-warns-of-mali-gpu-vulnerabilities" rel="external nofollow">https://hothardware.com/news/arm-warns-of-mali-<abbr title="Graphic processing unit (3D acceleration)">gpu</abbr>-vulnerabilities</a>
</p>

<p>
	 
</p>

<p>
	<a href="https://developer.arm.com/Arm%20Security%20Center/Mali%20GPU%20Driver%20Vulnerabilities" rel="external nofollow">https://developer.arm.com/Arm Security Center/Mali <abbr title="Graphic processing unit (3D acceleration)">GPU</abbr> Driver Vulnerabilities</a>
</p>

<p>
	 
</p>

<p>
	<a href="https://arstechnica.com/security/2023/10/vulnerable-arm-gpu-drivers-under-active-exploitation-patches-may-not-be-available/" rel="external nofollow">https://arstechnica.com/security/2023/10/vulnerable-arm-<abbr title="Graphic processing unit (3D acceleration)">gpu</abbr>-drivers-under-active-exploitation-patches-may-not-be-available/</a>
</p>

<p>
	 
</p>

<p>
	I have a Rockchip RK3399 that may also be affected by this. Can Armbian do anything to help mitigate this problem? A handful of boards use these GPUs.
</p>
]]></description><guid isPermaLink="false">30544</guid><pubDate>Wed, 04 Oct 2023 10:16:36 +0000</pubDate></item><item><title>Linux on the Ouya</title><link>https://forum.armbian.com/topic/16796-linux-on-the-ouya/</link><description><![CDATA[<p>
	Hello,
</p>

<p>
	 
</p>

<p>
	I got the itch to experiment with Linux on ARM. I tried to get an Odroid N2+ bit seems to be unavailable everywhere. The best thing I could get at a reasonable cost was a Nanopi M4v2, it'll arrive in about 3 weeks.
</p>

<p>
	 
</p>

<p>
	While I wait I remembered that I have an Ouya laying around and I asked myself:
</p>

<p>
	 
</p>

<p>
	Is it possible to install linux on an Ouya?
</p>

<p>
	 
</p>

<p>
	Searching the internet there are very old guides from 2013 to install ubuntu, had the situation improved? Anyone here tried?
</p>
]]></description><guid isPermaLink="false">16796</guid><pubDate>Sun, 17 Jan 2021 05:59:19 +0000</pubDate></item><item><title>&#xA3;22.99 used GeoBook 1E - Intel Celeron N3450 - 4GB RAM - 64GB SSD on Ebay</title><link>https://forum.armbian.com/topic/30117-%C2%A32299-used-geobook-1e-intel-celeron-n3450-4gb-ram-64gb-ssd-on-ebay/</link><description><![CDATA[<p>
	Hi, I just got 2 of these. Everything is fine but you need to order power adapter 12V 2A with 3.5mm x 1.35mm connector.
</p>

<p>
	Unfortunately due to earlier version of BIOS compare to same looking GeoBook 1E but with dualcore Celeron N4020 it cannot boot from microSD card.
</p>

<p>
	Speakers are rubbish but it could be good for some low powered machine projects.
</p>

<p>
	And one advice. Do not change "Quick boot" option in BIOS setting or it will not boot and you will need to unplug battery to reset BIOS.
</p>

<p>
	 
</p>

<p>
	It work with both Windows 11 or Linux with no  extra drivers mods needed. 5Ghz wifi and bluetooth also included.
</p>

<p>
	 
</p>

<p>
	<a href="https://www.ebay.co.uk/itm/166222480445" rel="external nofollow">https://www.ebay.co.uk/itm/166222480445</a>
</p>
]]></description><guid isPermaLink="false">30117</guid><pubDate>Sat, 09 Sep 2023 12:39:59 +0000</pubDate></item><item><title>Armbian on old Android device (rooted)</title><link>https://forum.armbian.com/topic/29791-armbian-on-old-android-device-rooted/</link><description><![CDATA[<p>
	I am writing this as i am searching to find some info.<br />
	Why i ended here you may ask?<br />
	I was searching google for pointers and i ended in topic here about Android TV boxes that can have <abbr title="embedded MultiMediaCard">Emmc</abbr> reflashed with Armbian or dual boot.<br />
	Yes you can say, "why you not post to xda-developers forum then?"<br />
	Most of stuff there regarding to this device are fixing buggy fake android and unbrick topics. <br />
	<br />
	----------------------------------------------------------------------------------------<br />
	Device i have is using old Android 6 and is rooted.<br />
	I also have full dump of device ROM if something happen.<br />
	<br />
	<abbr title="System On a Chip">SoC</abbr> is based on Mediatek AC8227L<br />
	CPU is 4x Armv7L running at 1.1ghz<br />
	RAM 2GB DDR3L<br />
	<abbr title="Graphic processing unit (3D acceleration)">GPU</abbr> is Mali 450 with OpenGL ES1.1/2.0<br />
	----------------------------------------------------------------------------------------<br />
	<br />
	I know ARM <abbr title="System On a Chip">SoC</abbr> need to have baked image and cannot run on any similar armbian image.<br />
	I have experience with flashing android devices and have few ARM based boards:<br />
	<abbr title="Raspberry Pi">RPI</abbr> Zero (armv6)<br />
	<abbr title="Raspberry Pi">RPI</abbr> 3B (Cortex-A53)<br />
	<abbr title="Raspberry Pi">RPI</abbr> 3A (Cortex-A53)<br />
	<abbr title="Raspberry Pi">RPI</abbr> Zero2 (Cortex-A53)<br />
	Pine64 (Cortex A5)<br />
	OrangePI Zero (4x arm7L)<br />
	<br />
	For example<br />
	OrangePi-Zero (armv7L) that use Mali 400 <abbr title="Graphic processing unit (3D acceleration)">GPU</abbr> have Armbian image here.<br />
	<br />
	I know nobody will make image for me here.<br />
	As is say i am searching to find some info about this.<br />
	 
</p>
]]></description><guid isPermaLink="false">29791</guid><pubDate>Wed, 23 Aug 2023 14:20:09 +0000</pubDate></item></channel></rss>
