Search the Community

On my NanoPi-R6C I have been doing several U-boot updates (writes with dd to areas in 1st 32k) and so far so good. But behavior has changed w.r.t. eMMC v.s. SD-card. I want to do some U-boot build config changes, so the risk it that something might go wrong and I would need USB MASKROM mode to do writes to eMMC I think. The NanoPi-R6C wiki is not very clear with 'connect USB', but it turn out that this should be a connection via type-A to type-A and it does not work in the USB2 port. I have a USB2-only type-A to type-A cable and used that. The NanoPi-R6C appears in the USB device list ('lsusb') and also the tool is seeing the device: /tmp/upgrade_tool_v2.30_for_linux/upgrade_tool LD Using /tmp/upgrade_tool_v2.30_for_linux/config.ini List of rockusb connected(1) DevNo=1 Vid=0x2207,Pid=0x350b,LocationID=12 Mode=Maskrom SerialNo= However, as soon as I want to read blocks from eMMC for example or try any other commands, connection is lost. Now I think that maybe for actual data transfer, USB3 wires in the cable are needed, so the question is: Will it work when I buy/use an USB3 type-A to type-A cable?

Armbian/Jammy is working like a charm, thanks guys. Settings up the encryption was a bit of bitch but its working as you can see. Any chance of adding encryption to the installer?

qemu-system-aarch64 -M virt -cpu host -enable-kvm ... only works reliably when 1 CPU core ( -smp 1). When a VM has 2 cores, it randomly worked I experienced. If virt-manager pick 2 equal cores, VM UEFI/BIOS/kernel runs OK, but if a Cortex-A76 and Cortex-A55, all sorts of exceptions are shown or just lockup 2x or 1x 100% usage. In order to still be able to use KVM, start qemu-system-aarch64 as follows: taskset --cpu-list 4-7 qemu-system-aarch64 -M virt -cpu host -enable-kvm -smp 4 ... or taskset --cpu-list 0-3 qemu-system-aarch64 -M virt -cpu host -enable-kvm -smp 4 ... Mainline kernel 6.8.x or later does not have this problem. It can transparently use all 8 cores. Userspace is Debian Bookworm based.

Hiya, Are the mirrors out of sync? or did I break something E: Failed to fetch http://deb.debian.org/debian/dists/bookworm-backports/non-free-firmware/binary-arm64/by-hash/SHA256/bc6dc27f7f88e60504fae9d9271e4dabaaa76b8a3a35ac6ec579e24d01d0ea16 E: Failed to fetch http://fi.mirror.armbian.de/beta/dists/bookworm/main/by-hash/SHA512/31775333c7d89a377fd3d2aac261ef684faeaba308fcf85b3c9ddc7f4f4a61712f5e398bc3b23464fd77d3eabd2b86e92b5dcc8dc2e44a27926f546708418c1a Hash Sum mismatch Hashes of expected file: - Filesize:5041046 [weak] - SHA512:31775333c7d89a377fd3d2aac261ef684faeaba308fcf85b3c9ddc7f4f4a61712f5e398bc3b23464fd77d3eabd2b86e92b5dcc8dc2e44a27926f546708418c1a - SHA256:9338b164942fc9bf1fa6f069d440576bfc2d52d572ca08aa295d2b641e15bc34 - SHA1:e946e275f83429aaacfc505978d8954329f5c842 [weak] - MD5Sum:2470b93cb2c8b144eecb3741d16190e2 [weak] Hashes of received file: - SHA512:95942ee2a9dd6434ee2f1684e69b4f26f27c52522735fb512967c703b5a1088a8f52e71b930973274bacc8083e9228bb3059afbb99ac6fcd428df2c9a1f537bc - SHA256:a53944749f834dc3d01d751c8210741324b9ca9c0bda997e6658750cac61f0cb - SHA1:d5333daa8e6d4186b298a3e79d1a41328da71119 [weak] - MD5Sum:9fa931f4f569d5cbda969b6ac5a51eca [weak] - Filesize:5041046 [weak] Last modification reported: Fri, 11 Oct 2024 03:54:42 +0000 Release file created at: Fri, 11 Oct 2024 03:54:44 +0000 E: Some index files failed to download. They have been ignored, or old ones used instead.

To prevent APT from installing <other-device> kernels that will render an installation useless I did the following: To see which kernel is running: $ uname -r 6.11.2-current-rockchip-rk3588 To see which kernels are installed: $ dpkg --get-selections 'linux-image*' inux-image-current-rockchip-rk3588 install linux-image-edge-rockchip-rk3588 install Its clear to see that I need "rockchip-rk3588" kernels and not the other 1000+ so wonderfully provides. Now that I know which kernel is used and which are not, I will allow and block what I need: $ sudo nano /etc/apt/preferences.d/kernel The first entry allows the installation of any rockchip-rk3588 kernels that my device can use. The second entry blocks the installation of any other kernel. Package: linux-image-*-rockchip-rk3588 Pin: release * Pin-Priority: 1000 Package: linux-image-* Pin: release * Pin-Priority: -1 To check if the policy is recognized run this command: $ apt-cache policy ... linux-image-6.9.7+bpo-rt-arm64 -> 6.9.7-1~bpo12+1 with priority -1 linux-image-6.1.0-11-cloud-arm64 -> 6.1.38-4 with priority -1 > linux-image-edge-rockchip-rk3588 -> 24.11.0-trunk.249 with priority 1000 > linux-image-edge-rockchip-rk3588 -> 24.11.0-trunk.238 with priority 1000 linux-image-6.1.0-11-rt-arm64 -> 6.1.38-4 with priority -1 linux-image-6.1.0-22-rt-arm64 -> 6.1.94-1 with priority -1 linux-image-6.1.0-11-arm64 -> 6.1.38-4 with priority -1 linux-image-6.10.6+bpo-arm64-dbg -> 6.10.6-1~bpo12+1 with priority -1 $ You can clearly see that all kernels are disabled with priority -1 except those for the rockchip-rk3588 To test this simulate the installation: $ sudo apt install --simulate linux-image-6.9.7+bpo-rt-arm64 [sudo] password for test: Reading package lists... Done Building dependency tree... Done Reading state information... Done Package linux-image-6.9.7+bpo-rt-arm64 is not available, but is referred to by another package. This may mean that the package is missing, has been obsoleted, or is only available from another source However the following packages replace it: linux-image-6.9.7+bpo-rt-arm64-unsigned E: Package 'linux-image-6.9.7+bpo-rt-arm64' has no installation candidate $ Success

Hiya peoples, Finally figured out what caused my black screen after updating After installing a new kernel (via apt) the '/boot/dtb' symlink is not updated, and fails to boot properly. lrwxrwxrwx 1 root root 31 Oct 7 11:38 dtb -> dtb-6.11.2-edge-rockchip-rk3588 lrwxrwxrwx 1 root root 38 Oct 7 08:49 Image -> vmlinuz-6.11.2-current-rockchip-rk3588 lrwxrwxrwx 1 root root 38 Oct 7 08:49 uInitrd -> uInitrd-6.11.2-current-rockchip-rk3588 So I wrote a systemd service that: 1. Runs before shutdown/reboot 2. Changes into the /boot directory 3. Reads the version from the dtb symlink 4. Reads the version from the Image symlink 5. Compares the versions 6. And if they do NOT match, creates a new dtb symlink that matches the Image symlink version. [Unit] Description=match dtb symlink with kernel version DefaultDependencies=no Before=shutdown.target [Service] Type=oneshot ExecStart=/bin/sh -c 'set -x;cd /boot;dtb=$(readlink dtb|sed 's,^dtb-,,');vmlinuz=$(readlink Image|sed 's,vmlinuz-,,');[ "$dtb" = "$vmlinuz" ] || ln -sf dtb-$vmlinuz dtb' TimeoutStartSec=0 [Install] WantedBy=shutdown.target To use this: 1. sudo nano /etc/systemd/system/dtb-match-kernel.service and paste in the text above. 2. sudo systemd enable dtb-match-kernel.service You can check the journal if it works with: 3. journalctl -u dtb-match-kernel.service or the /boot directory lrwxrwxrwx 1 root root 31 Oct 7 11:39 dtb -> dtb-6.11.2-current-rockchip-rk3588 lrwxrwxrwx 1 root root 38 Oct 7 08:49 Image -> vmlinuz-6.11.2-current-rockchip-rk3588 lrwxrwxrwx 1 root root 38 Oct 7 08:49 uInitrd -> uInitrd-6.11.2-current-rockchip-rk3588 Dantes

Hello, When choosing Boot from eMMC - system on SATA, USB or NVMe in armbian-install using the Armbian 24.8.3 Bookworm Minimal / IOT, Kernel: 6.1.75, Release date: Sep 14, 2024 image on my NanoPi R6C, I get the following error: The wird device name is also mentioned on the two preceeding dialogs ("it is highly recommended to wipe all partitions" and "this will wipe all data"). I took a look at the argmbian-install script and the check_partitions routine seems to assume that $diskcheck contains something that, when prefixed with /dev, can be used in the of parameter of the dd command. It is computed as root_uuid=$(sed -e 's/^.*root=//' -e 's/ .*$//' < /proc/cmdline) root_partition=$(blkid | tr -d '":' | grep "${root_uuid}" | awk '{print $1}') root_partition_name=$(echo $root_partition | sed 's/\/dev\///g') root_partition_device_name=$(lsblk -ndo pkname $root_partition) diskcheck=$(lsblk -l | awk -F" " '/ disk / {print $1}' | grep -E '^sd|^nvme|^mmc' | grep -v "$root_partition_device_name" | grep -v boot) With the following block devices (zram omitted) NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINTS mmcblk0 179:0 0 28.9G 0 disk mmcblk0boot0 179:32 0 4M 1 disk mmcblk0boot1 179:64 0 4M 1 disk mmcblk1 179:96 0 29.7G 0 disk └─mmcblk1p1 179:97 0 29.4G 0 part /var/log.hdd nvme0n1 259:0 0 1.9T 0 disk this evaluates to root_uuid=UUID=be8e5867-07c9-4cae-842b-22fd411851ba root_partition=/dev/mmcblk1p1 root_partition_name=mmcblk1p1 root_partition_device_name=mmcblk1 diskcheck=mmcblk0 nvme0n1 To me it seems that the computation of diskcheck assumes that lsblk will return at most one "disk" that is not the root device and not a boot partition. On my system, which has an EMMC, an NVME SSD and is booting from an sdcard, this assumption does not hold. Or maybe, including ^sd and ^mmc in the check is not the right thing to do here? Am I doing something wrong here, do I have an unsupported block device layout or is this a bug in the armbian-install script? Is there maybe a workaround? Thank you!

Hi, I had some issues regarding WireGuard that are solved now. Since my armbian release already contains wireguard I have no need to install it. However I wanted to prevent any future mistake rendering my installation unbootable. So after some searching and experimenting I did the following: In order to block a package a file must be created in /etc/apt/preferences.d/ , in my case I called it wireguard $ sudo tee /etc/apt/preferences.d/wireguard &>/dev/null <<EOF Package: wireguard Pin: release * Pin-Priority: -1 EOF This is what it looks like now when trying to install the package: $ sudo apt install wireguard Reading package lists... Done Building dependency tree... Done Reading state information... Done Package wireguard is not available, but is referred to by another package. This may mean that the package is missing, has been obsoleted, or is only available from another source E: Package 'wireguard' has no installation candidate Unfortunately this still gave me the option to autoremove wireguard-tools sudo apt autoremove Reading package lists... Done Building dependency tree... Done Reading state information... Done The following packages will be REMOVED: wireguard-tools 0 upgraded, 0 newly installed, 1 to remove and 0 not upgraded. After this operation, 366 kB disk space will be freed. Do you want to continue? [Y/n] n Abort. So I marked the wireguard-tools package as manual because I still need it: $ sudo apt-mark manual wireguard-tools wireguard-tools set to manually installed. And now it does not bother me with "unneeded" packages warning when using apt : $ sudo apt autoremove Reading package lists... Done Building dependency tree... Done Reading state information... Done 0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. Yay!

Hi, I tried to install WireGuard, but it resulted in a non-bootable-system Wasn't WireGuard integrated in the kernel ? How does this apply to Armbian ? Available rk3588 kernels: $ sudo apt search linux-image.*rk3588 Sorting... Done Full Text Search... Done linux-image-current-rockchip-rk3588/bookworm,now 24.11.0-trunk.152 arm64 [installed] Armbian Linux current kernel image 6.10.11-current-rockchip-rk3588 linux-image-edge-rockchip-rk3588/bookworm 24.11.0-trunk.152 arm64 Armbian Linux edge kernel image 6.11.0-edge-rockchip-rk3588 $ Apt tries to install this kernel: $ sudo apt install wireguard wireguard-tools Reading package lists... Done Building dependency tree... Done Reading state information... Done The following additional packages will be installed: linux-image-6.10.6+bpo-arm64-16k linux-image-arm64-16k Suggested packages: firmware-linux-free linux-doc-6.10 debian-kernel-handbook Recommended packages: apparmor The following NEW packages will be installed: linux-image-6.10.6+bpo-arm64-16k linux-image-arm64-16k wireguard wireguard-tools 0 upgraded, 4 newly installed, 0 to remove and 0 not upgraded. Need to get 87,9 MB of archives. After this operation, 169 MB of additional disk space will be used. Do you want to continue? [Y/n] n Abort. $

Dear Community, This might only be with the NanoPI-r6c images, but the SHASUM contains a temporary path which you don't have an thus fails. Since we cannot change the SHASUM because then the ASC would fail, I have a temporary workaround: sed 's,/.*/,,' armbian.img.sha | sha256sum -c In a script you could either 1. CD into the directory of the image 2. Run the SHASUM there 3. Use $OLDPWD to return or correct the SHASUM inline: sha256sum /path/to/file | sed 's,/.*/,,' > armbian.img.sha Dantes

I'm trying to setup disk encryption, but for some reason its not opening devices after installing cryptsetup-bin on the installation image. After typing the password it just hangs and does nothing $ cryptsetup open /dev/sda sda_crypt Anyone?

I upgraded from my own-compiled Armbian kernel 6.8.0-rc5 to 6.8.4 and there are now very annoying stall when for example I drag a KDE Konsole window. Also when I play a 1080p50 HEVC video, as son as a move the mouse, the whole video stalls. Besides 6.8.0-rc5, the normal apt provide 6.8.1-edge-rockchip-rk3588 also works OK. 6.8.5 has the same issue as 6.8.4. As indicated, I use KDE, X11, compositor disabled. Enabled makes no difference. OS base is Armbian Bookworm, but I have also used kernels 6.8.1 and 6.8.4 with a rootfs copied from an RaspberryPiOS and Opensuse-Tumbleweed. RPiOs is also Debian Bookworm, Tumbleweed is latest, KDE6. So it is not KDE6. KDE Wayland leaves black screen still (doesn't work), but that is not a showstopper. Is anyone else experiencing the same? PS: I run mainline as the vendor kernel 6.1.43 fails on running KVM (some tag of the Cortex-A55 is unknown) so qemu-KVM don't work/start and running VMs is a key use-case I bought the NanoPi-R6C for.

I have Armbian running on a NanoPi R6C 8GB with 32GB eMMC. I made a new Armbian image with the build framework that uses newest linux-u-boot-nanopi-r6s-legacy 23.8.0-trunk linux-dtb-legacy-rk35xx 23.8.0-trunk linux-image-legacy-rk35xx 23.8.0-trunk Booted from microSD this system has an idle power consumption of 0,92w. I can access both the eMMC and microSD storage. When i transfer this system from microSD to eMMC with "nand-sata-install" to boot & OS on eMMC and cold boot without the microSD, the idle power consumption increases to 1,21w. After a shutdown and booting from the microSD again the idle power consumption is back at 0,92w. So far i have not been able to find a reason for this. The only things i noticed was: (microSD) Device Start End Sectors Size Type /dev/mmcblk1p1 32768 557055 524288 256M Linux extended boot /dev/mmcblk1p2 557056 61702144 61145089 29.2G Linux filesystem (eMMC) Device Start End Sectors Size Type /dev/mmcblk0p1 32768 59998207 59965440 28.6G Linux filesystem While microSD uses a vfat partition for /boot and an EXT4 partition for the OS the eMMC has a single EXT4 partition for everything. Does that change how the system is booting? https://github.com/radxa/u-boot/commit/bf47e8171f44804c7f2004f53d3f05801f8dbbb8 Different drive strength settings in u-boot for when eMMC is boot drive or not? Can that really increase the power usage of the eMMC by 0,3w?

When I reboot with kernel 6.8.4 (edge) installed by apt upgrade, I noticed my scripts that uses snapper for remove differential backups. It turns out that, if no cleanup algorithm option is used, snapshot is created. Before the reboot, with kernel 6.8.1 version, there was no issue. I on Armbian Bookworm, but also with other Debian Bookworm based OS running those same kernel binaries. Same failure with 6.8.5 Currently I don't know any more, I could run this faulty kernel in a VM as the .config is such that it also boots on virt hardware (virt-7.2 as Bookworm uses). EDIT: Also in a VM, the problem is there: root@armbian64:/tmp# snapper create -d cleantest --cleanup-algorithm number Creating snapshot failed. root@armbian64:/tmp# snapper create -d cleantest root@armbian64:/tmp# uname -a Linux armbian64 6.8.4-edge-rockchip-rk3588 #1 SMP PREEMPT Thu Apr 4 18:25:06 UTC 2024 aarch64 GNU/Linux

Is it possible to activate PCIe ASPM L1 substates with the NanoPi R6C / RK3588s Soc in general? > lspci -vvv | grep ASPM LnkCtl: ASPM L1 Enabled; RCB 64 bytes, Disabled- CommClk+ L1SubCap: PCI-PM_L1.2+ PCI-PM_L1.1+ ASPM_L1.2+ ASPM_L1.1+ L1_PM_Substates+ L1SubCtl1: PCI-PM_L1.2- PCI-PM_L1.1- ASPM_L1.2- ASPM_L1.1- My M.2 NVMe SSD supports all L1 substates but setting pcie_aspm.policy to "powersupersave" has no effect. Max is "powersave" to activate ASPM L1 and that works. Is this a limitation of the SoC or just not implemented in the armbian driver / kernel?

On my NanoPi R6C I downloaded the Armbian 23.11 Bookworm CLI and booted the machine from the SD card. Then I installed gnome and firefox. Most things works so far, but I get no sound over hdmi (there is no headphone jack). The gnome - settings - sound shows only the dummy device. Youtube videos play ok, but somewhat laggy and with very high processor load (all cores close to 100% on the gnome system monitor).

Now I'm no expert but I got Mate working maybe there are some shortcuts I did not take, but it works great. So feel free to point out any flaws or improve it, #!/bin/sh -vx packages=' cryptsetup libblockdev-crypto2 engrampa firefox ffmpeg libavcodec-extra gufw lightdm lightdm-settings slick-greeter ubuntu-mate-wallpapers-common mate-desktop-environment-extras mate-applet-brisk-menu mate-applets mate-calc mate-indicator-applet ayatana-indicator-application ayatana-indicator-bluetooth ayatana-indicator-common ayatana-indicator-display ayatana-indicator-keyboard ayatana-indicator-messages ayatana-indicator-notifications ayatana-indicator-power ayatana-indicator-printers ayatana-indicator-session ayatana-indicator-sound mate-media mate-menu mate-power-manager mate-sensors-applet mate-session-manager mate-settings-daemon mate-screensaver mate-tweak mate-utils eom mpv plank pluma network-manager-gnome software-properties-gtk libcanberra-gtk-module libcanberra-gtk3-module ubuntu-advantage-tools gnome-software gnome-system-tools update-manager xorg ' apt update -y apt upgrade -y apt install -y $packages ##### fix 'Software' desktop file so it shows up in the 'Control Center' sed -i \ 's,^Categories=.*,Categories=System;Settings,g' \ /usr/share/applications/org.gnome.Software.desktop ##### no default wallpaper, set a mate wallpaper to the login screen cat << EOF > /etc/lightdm/slick-greeter.conf [Greeter] background=/usr/share/backgrounds/ubuntu-mate-common/Grey-Jazz.jpg EOF #sudo apt remove zsh openssh-server openssh-sftp-server avahi-autoipd evolution-data-server* #echo net.ipv6.conf.all.disable_ipv6=1 #net.ipv6.conf.default.disable_ipv6=1 #net.ipv6.conf.lo.disable_ipv6=1 #' |sudo tee -a /etc/sysctl.conf mate-install

My audio volume was very very low, and very annoyingly I had to boost to 200% 300% which had the problem that the volume buttons were not working properly. You just cant see anything above 100% unless you go into the control panel. Now when it comes to audio I'm the village idiot, but I found a proper solution I think. After some experimentation I found that the module "module-cli-protocol-unix" ( #20 in my case) can be amplified with pactl set-sink-input-volume 20 10db Now YMMV depending on your attached hardware, so change the 10db to whatever suits your situation. After that I made it permanent by adding it to the /etc/pulse/default.pa like this: # Default volume amplification set-sink-input-volume 20 10db Yay!

I am unable to play files over SMB, but I can't seem to figure out what the problem is exactly. From what I can tell it *seems* ffmpeg is compiled without networking support, at least this is what smplayer was complaining about: [ffmpeg] Protocol not found. Make sure ffmpeg/Libav is compiled with networking support. Failed to open smb://192.168.1.1/transmission/myfile.mkv. Exiting... (Errors when loading file) But when I look at the ffmpeg switches it was compiled with: --enable-libsmbclient and seems to be present. Now I'm a complete linux n00b, does anyone have an idea ?

It seems a package is missing from the Armbian 23.8 Bookworm CLI that results in this error. I encountered an add-apt-repository: traceback error. To fix it just run: sudo apt install python3-launchpadlib

What Works: - USB2 and USB3 - PCIe2 - GMAC - eMMC on HS200 mode - Cpufreq - User and maskrom buttons Dmesg Output: https://paste.armbian.com/onelomofit You can download them from Rolling releases section on https://www.armbian.com/nanopi-r6s/ page. Images include devicetrees for R6S and R6C. If you have R6C, you must change the devicetree from armbianEnv.txt.

As you can see the WAN-port/NIC registers fine with a label from the nanopi-r6c device tree $ grep fe1c0000 /boot/dtb/rockchip/rk3588s-nanopi-r6c.dtb grep: /boot/dtb/rockchip/rk3588s-nanopi-r6c.dtb: binary file matches dmesg: dmesg | grep fe1c0000 [ 7.287277] rk_gmac-dwmac fe1c0000.ethernet: init for RGMII_RXID [ 7.287373] rk_gmac-dwmac fe1c0000.ethernet: User ID: 0x30, Synopsys ID: 0x51 [ 7.287377] rk_gmac-dwmac fe1c0000.ethernet: DWMAC4/5 [ 7.287381] rk_gmac-dwmac fe1c0000.ethernet: DMA HW capability register supported [ 7.287385] rk_gmac-dwmac fe1c0000.ethernet: RX Checksum Offload Engine supported [ 7.287388] rk_gmac-dwmac fe1c0000.ethernet: TX Checksum insertion supported [ 7.287391] rk_gmac-dwmac fe1c0000.ethernet: Wake-Up On Lan supported [ 7.287423] rk_gmac-dwmac fe1c0000.ethernet: TSO supported [ 7.287426] rk_gmac-dwmac fe1c0000.ethernet: Enable RX Mitigation via HW Watchdog Timer [ 7.287430] rk_gmac-dwmac fe1c0000.ethernet: Enabled Flow TC (entries=2) [ 7.287433] rk_gmac-dwmac fe1c0000.ethernet: TSO feature enabled [ 7.287437] rk_gmac-dwmac fe1c0000.ethernet: Using 32 bits DMA width However the LAN-port does not have such a label in dmesg output. [ 7.932846] pci 0003:31:00.0: [10ec:8125] type 00 class 0x020000 [ 7.932902] pci 0003:31:00.0: reg 0x10: initial BAR value 0x00000000 invalid [ 7.932905] pci 0003:31:00.0: reg 0x10: [io size 0x0100] [ 7.932958] pci 0003:31:00.0: reg 0x18: [mem 0x00000000-0x0000ffff 64bit] [ 7.932993] pci 0003:31:00.0: reg 0x20: [mem 0x00000000-0x00003fff 64bit] [ 7.933301] pci 0003:31:00.0: supports D1 D2 [ 7.933303] pci 0003:31:00.0: PME# supported from D0 D1 D2 D3hot D3cold [ 7.948845] pci 0003:31:00.0: BAR 2: assigned [mem 0xf3200000-0xf320ffff 64bit] [ 7.948873] pci 0003:31:00.0: BAR 4: assigned [mem 0xf3210000-0xf3213fff 64bit] [ 7.948899] pci 0003:31:00.0: BAR 0: assigned [io 0x1000-0x10ff] [ 7.950294] r8125 0003:31:00.0: enabling device (0000 -> 0003) [ 7.967108] r8125 0003:31:00.0 (unnamed net_device) (uninitialized): Invalid ether addr 00:00:00:00:00:00 [ 7.967112] r8125 0003:31:00.0 (unnamed net_device) (uninitialized): Random ether addr a2:83:9c:9c:cc:e8

I have the newest Armbian 28.08.0-trunk image running on a NanoPi R6C with a 4TB NVMe SSD. The NanoPi is only connected to power and 1G ethernet via the 1G WAN port. When using the machine as NAS with Samba and a Windows client connected there is a strange problem when receiving large files. The files are stored on the NVMe SSD with ~450MB/s read/write via PCIe 2.1x1. When transmitting files from the NanoPi to a SMB client the 1G ethernet is maxed out but when receiving files the connection drops down to ~60 MB/s every few seconds. This instantly gets fixed when using the 2.5G LAN port instead of the 1G WAN port. On that port the RX looks exactly the same as the TX. Both with 112MB/s maxed out speed. I noticed that the 1G WAN port is a combination of GMAC in RK3588s SoC and a Realtek RTL8211F Transceiver while the 2.5G LAN port is a dedicated Realtek RTL8125BG. So i suspect there is something wrong with that combination of GMAC and Realtek Transceiver on the 1G WAN port. I already tried changing the rgmii rx settings with an overlay, but that didn't have any effect. Driver problem?!

I did a lot of power consumption tests with my NanoPi R6C and noticed something strange when switching from kernel 5.10.110 to kernel 5.10.160. Hardware NanoPi R6C 4GB 32GB Sandisk High Endurance microSD Card Ugreen 18W USB Power Supply Software Armbian 23.5.1 Nanopi-r6s bookworm Default settings (only changing fdtfile=rockchip/rk3588s-nanopi-r6s.dtb to fdtfile=rockchip/rk3588s-nanopi-r6c.dtb in /boot/armbianEnv.txt) Switching between legacy 5.10.160 and legacy 5.10.110 kernels with armbian-config With just 1Gbit Ethernet and the power supply connected in idle (measured at wall): kernel 5.10.110: 0,92W kernel 5.10.160: 1,21W I also tested different M.2 SSD, with ASPM L1 enabled/disabled, HDMI and USB devices connected/not connected. I even tried different usb power supply. In every case the power consumption with kernel 5.10.160 is higher with no apparent benefit. You could argue that it is not a big difference but when running the system from a battery it is! What is causing this increased power consumption? I tried to run a lot of commands to find the difference between the 2 kernels but could not find a significant one. WinDiff between the 2 kernels:

Download: https://www.armbian.com/nanopi-r6s/ (unofficial WIP support)