<?xml version="1.0"?>
<rss version="2.0"><channel><title>NanoPi R6S/R6C Latest Topics</title><link>https://testforum.armbian.com/forum/271-nanopi-r6sr6c/</link><description>NanoPi R6S/R6C Latest Topics</description><language>en</language><item><title>U-Boot 2026.01-rc2 no HDMI-audio</title><link>https://testforum.armbian.com/topic/56627-u-boot-202601-rc2-no-hdmi-audio/</link><description><![CDATA[<p>
	While doing various tests, also other bootloader than EDK2-UEFI v1.1 that I had in <abbr title="embedded MultiMediaCard">eMMC</abbr>, I discovered that with 2026.01-rc2_armbian-2026.01-rc2-S365a-Pa203-He3cc-V062a-Bbf55-R448a kernel 6.18.0-rc7-edge-rockchip64 did not find/enable audio via HDMI.
</p>

<p>
	I moved the computer to other room where I rely on the speakers in the monitor, else I would not have discovered it as I also use networked pulseaudio.
</p>

<p>
	 
</p>

<p>
	What works is 2025.01-armbian-2025.01-S6d41-Pdb4b-H2194-V062a-Bb703-R448a, so sort of last-known-good, got that via:
</p>

<p>
	sudo apt install linux-u-boot-nanopi-r6c-current=25.8.1 and wrote the binary with dd to <abbr title="embedded MultiMediaCard">eMMC</abbr>
</p>

<p>
	 
</p>

<p>
	Another issue is that the monitor does get out of sleep too late, so the loglevel=7 effect can only be seen on extra serial console, whereas with the UEFI bootloader, the HDMI gets always initalized properly, so before kernel is loaded.
</p>

<p>
	 
</p>

<p>
	Note that this is with booting via grub. So with EDK2-UEFI v1.1 bootloader, I get a normal Debian graphical kernel selection menu, like on x86-64. With Opensuse Tumbleweed it is slightly different, as that also automatically duplicates on serial console (if 't' is pressed , from 'text'). So this is actually quite ideal. The only disadvantage is that it does not want to store boot entries (but works on ROCK5B in SPI-flash).
</p>

<p>
	 
</p>

<p>
	I probably need an own build on SD-card first to see how 2026.01 (or later) can do the same as EDK2-UEFI v1.1 more or less.
</p>

<p>
	 
</p>

<p>
	I should note that with EDK2-UEFI v1.1 bootloader, I do not load the <abbr title="Device tree blob">DTB</abbr> that comes with the kernel version. I used the setting 'vendor' or 'mainline' in the UEFI settings, that gets stored well actually. Now with the 25.8.1 U-Boot, I manually added a devitree loader line in grub.cfg, but that will be overwritten, so need to see what makes sense.
</p>

<p>
	 
</p>
]]></description><guid isPermaLink="false">56627</guid><pubDate>Sun, 07 Dec 2025 13:51:45 +0000</pubDate></item><item><title>Unable to boot from SD card (Only Armbian OS from SD Card Gets Booted)</title><link>https://testforum.armbian.com/topic/59426-unable-to-boot-from-sd-card-only-armbian-os-from-sd-card-gets-booted/</link><description><![CDATA[<p>
	Hi There,
</p>

<p>
	 
</p>

<p>
	Board: NanoPi R6S
</p>

<p>
	<br />
	I've flashed armbian OS via armbian imager tool + microSD card and installed the os into <abbr title="embedded MultiMediaCard"><abbr title="embedded MultiMediaCard">emmc</abbr></abbr> using armbian-install.
</p>

<p>
	Os was working fine then i realize that the minimum required kernel drivers are not available (npu/tpu/<abbr title="Graphic processing unit (3D acceleration)"><abbr title="Graphic processing unit (3D acceleration)">gpu</abbr></abbr>).
</p>

<p>
	I have tried to install more than a dozen operating systems including that I used before, but the booting process doesn't work.
</p>

<p>
	After lots of try I realized that only armbian os is getting booted from the SD card.
</p>

<p>
	Mask button which should bypass <abbr title="embedded MultiMediaCard"><abbr title="embedded MultiMediaCard">emmc</abbr></abbr> and force to boot from microSD card is not working after flashing armbian os.
</p>

<p>
	I couldn't connect the NanoPi R6S via USB A to A link for direct flashing.
</p>

<p>
	 
</p>

<p>
	When i flash os other than armbian, it does not boot and no output at HDMI.
</p>

<p>
	When MASK button is pressed before boot, the device seems using somewhat 3W current and stays on with red led, connected keybords will get power but no HDMI output.
</p>

<p>
	 
</p>

<p>
	How to restore the bootloader and other required partitions with its original version so that i can start booting os other than armbian.
</p>

<p>
	 
</p>

<p>
	Please help.
</p>
]]></description><guid isPermaLink="false">59426</guid><pubDate>Fri, 01 May 2026 15:27:37 +0000</pubDate></item><item><title>Need help with video decode acceleration on NanoPi R6S</title><link>https://testforum.armbian.com/topic/54381-need-help-with-video-decode-acceleration-on-nanopi-r6s/</link><description><![CDATA[<p>
	I have been pulling my hair out trying to get the acceleration performance (smooth 4K video playback in mpv / chromium) in Armbian (any of the MESA/<abbr title="Video processing unit (encoding/decoding)">VPU</abbr> marked releases) that I am getting from the FriendlyElec distributions. In my naive mind, I thought the MESA/<abbr title="Video processing unit (encoding/decoding)">VPU</abbr> version would get me there, but mpv stutters on 4K videos. I suspect this is because Armbian avoids the proprietary drives. A long time ago, Armbian Ubuntu versions were able to be 'amended' with the Amazingfate/liujianfeng1994 repository, but I have not been able to make that work in a while.
</p>

<p>
	Could someone point me to a guide that allows me to get similar performance with Armbian as I am getting with FriendlyElec?
</p>

<p>
	Thanks bunch in advance!
</p>
]]></description><guid isPermaLink="false">54381</guid><pubDate>Fri, 08 Aug 2025 19:47:17 +0000</pubDate></item><item><title>HDMI audio multichannel wrong mapping (in 6.18.12-current-rockchip64)</title><link>https://testforum.armbian.com/topic/58073-hdmi-audio-multichannel-wrong-mapping-in-61812-current-rockchip64/</link><description><![CDATA[<p>
	Does anybody know how one could correct multichannel HDMI audio mapping in the current-rockchip64 build or kernel?
</p>

<p>
	 
</p>

<p>
	When I run 
</p>

<pre class="ipsCode prettyprint lang-html prettyprinted"><span class="pln">speaker-test -c6 -D plughw:0,0</span></pre>

<p>
	on
</p>

<pre class="ipsCode prettyprint lang-html prettyprinted"><span class="pln">(kernel) 6.1.115-vendor-rk35xx
+
(dtb) dtb-6.1.115-vendor-rk35xx</span></pre>

<p>
	<u>Everything is mapped correctly and I hear audio from all the correct channels.</u>
</p>

<p>
	 
</p>

<p>
	When I run the same command on 
</p>

<pre class="ipsCode prettyprint lang-html prettyprinted"><span class="pln">(kernel) 6.18.12-current-rockchip64
+
(dtb) dtb-6.18.12-current-rockchip64</span></pre>

<p>
	<u>I get <strong>no audio</strong> on <strong>center</strong> and <strong>rear right</strong> channels (<strong>others are working</strong>).</u>
</p>

<p>
	 
</p>

<p>
	Is this a mistake or error in the <abbr title="Device tree blob"><abbr title="Device tree blob">DTB</abbr></abbr> file of <abbr title="Device tree blob"><abbr title="Device tree blob">dtb</abbr></abbr>-6.18.12-current-rockchip64 (<u>rk3588s-nanopi-r6s.<abbr title="Device tree blob"><abbr title="Device tree blob">dtb</abbr></abbr></u>) ?
</p>

<p>
	How can we correct this?
</p>
]]></description><guid isPermaLink="false">58073</guid><pubDate>Wed, 18 Feb 2026 17:47:44 +0000</pubDate></item><item><title>how i updated to from bookworm to trixie</title><link>https://testforum.armbian.com/topic/55345-how-i-updated-to-from-bookworm-to-trixie/</link><description><![CDATA[<p>
	I recently updated from bookworm to trixie, here's how i did it:
</p>

<p>
	 
</p>

<p>
	<strong>commands</strong>:
</p>

<pre class="ipsCode prettyprint lang-html prettyprinted"><span class="pln">sudo apt update
sudo apt upgrade -y
sudo cp -p /etc/apt/sources.list /etc/apt/sources.list.bak
sudo sed -i 's,bookworm,trixie,g' /etc/apt/sources.list
sudo cp -p /etc/apt/sources.list.d/armbian.list /etc/apt/sources.list.d/armbian.list.bak 
sudo sed -i 's,bookworm,trixie,g' /etc/apt/sources.list.d/armbian.list
sudo apt dist-upgrade</span></pre>

<p>
	 
</p>

<p>
	<strong>/etc/apt/sources.list</strong> :
</p>

<pre class="ipsCode prettyprint lang-html prettyprinted"><span class="pln">deb http://deb.debian.org/debian trixie main contrib non-free non-free-firmware
# deb-src http://deb.debian.org/debian trixie main contrib non-free non-free-firmware

deb http://deb.debian.org/debian trixie-updates main contrib non-free non-free-firmware
# deb-src http://deb.debian.org/debian trixie-updates main contrib non-free non-free-firmware

deb http://deb.debian.org/debian trixie-backports main contrib non-free non-free-firmware
# deb-src http://deb.debian.org/debian trixie-backports main contrib non-free non-free-firmware

deb http://security.debian.org/ trixie-security main contrib non-free non-free-firmware
# deb-src http://security.debian.org/ trixie-security main contrib non-free non-free-firmware</span></pre>

<p>
	 
</p>

<p>
	<strong>/etc/apt/sources.list.d/armbian.list</strong><span>:</span>
</p>

<pre class="ipsCode prettyprint lang-html prettyprinted"><span class="pln">deb [signed-by=/usr/share/keyrings/armbian.gpg] http://beta.armbian.com trixie main trixie-utils trixie-desktop</span></pre>

<p>
	 
</p>
]]></description><guid isPermaLink="false">55345</guid><pubDate>Sun, 28 Sep 2025 16:38:41 +0000</pubDate></item><item><title>update to edge kernel rolling release 6.16.x</title><link>https://testforum.armbian.com/topic/55343-update-to-edge-kernel-rolling-release-616x/</link><description><![CDATA[<p>
	My setup is still running, yay! I even updated to Trixie and all worked out fine.
</p>

<p>
	 
</p>

<p>
	But I'm stuck on edge kernel 6.12.x, I saw that rolling had 6.16.x. So how do I install/convert to the rolling 6.16.x edge kernel ?
</p>
]]></description><guid isPermaLink="false">55343</guid><pubDate>Sun, 28 Sep 2025 16:31:06 +0000</pubDate></item><item><title>Support for lowers power states (freeze / s2idle) seems to be broken on FriendlyElec boards</title><link>https://testforum.armbian.com/topic/54035-support-for-lowers-power-states-freeze-s2idle-seems-to-be-broken-on-friendlyelec-boards/</link><description><![CDATA[<p>
	I have tested this on a NanoPi R5C as well as on NanoPC-T6 (non-<abbr title="Long term support"><abbr title="Long term support">LTS</abbr></abbr>). For the later I also tested a vender provided Kernel / OS Installation.<br />
	<br />
	What happens is that whenever some Power-Saving is requested, the board will seemingly fully power down and is not responsive to anything,<br />
	at best the reset button will do its work, R5C requires a power-cycle.<br />
	<br />
	The last kernel msgs are these (see <a href="https://www.kernel.org/doc/Documentation/power/states.txt" rel="external nofollow">https://www.kernel.org/doc/Documentation/power/states.txt</a><span class="ipsEmoji">😞</span><br />
	 
</p>

<pre class="ipsCode prettyprint lang-html prettyprinted"><span class="pln">#  echo freeze &gt; /sys/power/state 
[   54.373374] PM: suspend entry (s2idle)
[   54.671033] Filesystems sync: 0.297 seconds
[   54.775176] Freezing user space processes
[   54.780065] Freezing user space processes completed (elapsed 0.004 seconds)
[   54.780769] OOM killer disabled.
[   54.781078] Freezing remaining freezable tasks
[   54.782928] Freezing remaining freezable tasks completed (elapsed 0.001 seconds)
[   54.791332] r8169 0002:01:00.0 wan1: Link is Down</span></pre>

<p>
	<br />
	<br />
	I am at a loss how to diagnose this further. To me it appears that there is some vital power-source to CPU or RAM switched off.
</p>
]]></description><guid isPermaLink="false">54035</guid><pubDate>Thu, 24 Jul 2025 08:24:20 +0000</pubDate></item><item><title>NanoPi R6S wrong network interface naming</title><link>https://testforum.armbian.com/topic/48010-nanopi-r6s-wrong-network-interface-naming/</link><description><![CDATA[<p>
	Unfortunately, there seems not yet to be an area in this forum for NanoPi R6C/S, so here we go ...
</p>

<p>
	 
</p>

<p>
	Here is the default Armbian /etc/udev/rules.d/70-persistent-net.rules
</p>

<p>
	 
</p>

<p>
	SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*", KERNELS=="fe1c0000.ethernet", NAME:="wan"<br>
	SUBSYSTEM=="net", ACTION=="add", DRIVERS=="r8169", KERNELS=="0003:31:00.0", NAME:="lan1"<br>
	SUBSYSTEM=="net", ACTION=="add", DRIVERS=="r8169", KERNELS=="0004:41:00.0", NAME:="lan2"
</p>

<p>
	 
</p>

<p>
	This does not match up with the labels on the case!
</p>

<p>
	Here is the correct config we have updated and tested on a NanoPi R6S at <em>Afritic Group</em>:
</p>

<p>
	 
</p>

<p>
	SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*", KERNELS=="fe1c0000.ethernet", NAME:="lan2"<br>
	SUBSYSTEM=="net", ACTION=="add", DRIVERS=="r8169", KERNELS=="0003:31:00.0", NAME:="wan"<br>
	SUBSYSTEM=="net", ACTION=="add", DRIVERS=="r8169", KERNELS=="0004:41:00.0", NAME:="lan1"<br>
	<br>
	So now with this updated config, the internal and external names match up!
</p>

<p>
	 
</p>

<p>
	<a class="ipsAttachLink ipsAttachLink_image" href="https://testforum.armbian.com/uploads/monthly_2024_12/armbian.png.c974d2f63e1a5ea34394cfd116ab549d.png" data-fileid="13634" data-fileext="png" rel=""><img alt="armbian.png" class="ipsImage ipsImage_thumbnailed" data-fileid="13634" width="463" src="https://testforum.armbian.com/uploads/monthly_2024_12/armbian.png.c974d2f63e1a5ea34394cfd116ab549d.png" loading="lazy" height="277.8"></a>
</p>
]]></description><guid isPermaLink="false">48010</guid><pubDate>Mon, 09 Dec 2024 23:45:50 +0000</pubDate></item></channel></rss>
