All Activity

Hello, I have experimented with a Realtek USB 2.5Gbe USB Ethernet dongle and find that it works fine with the vendor kernel but not with kernels 6.12.x or 6.18.y. I have included an iperf3 example below, you can see that the dongle manages a few runs at high speed before it quietly fails and seizes up. I use a number of these dongles and they tend to work fine on other set-ups. Any thoughts about a resolution? dmesg output: [Tue Mar 17 11:37:00 2026] usb 2-1: new SuperSpeed USB device number 2 using xhci-hcd [Tue Mar 17 11:37:00 2026] usb 2-1: New USB device found, idVendor=0bda, idProduct=8156, bcdDevice=31.00 [Tue Mar 17 11:37:00 2026] usb 2-1: New USB device strings: Mfr=1, Product=2, SerialNumber=6 [Tue Mar 17 11:37:00 2026] usb 2-1: Product: USB 10/100/1G/2.5G LAN [Tue Mar 17 11:37:00 2026] usb 2-1: Manufacturer: Realtek [Tue Mar 17 11:37:00 2026] usb 2-1: SerialNumber: 0013000001 [Tue Mar 17 11:37:00 2026] usbcore: registered new device driver r8152-cfgselector [Tue Mar 17 11:37:00 2026] r8152-cfgselector 2-1: reset SuperSpeed USB device number 2 using xhci-hcd [Tue Mar 17 11:37:01 2026] r8152 2-1:1.0 eth0: v1.12.13 [Tue Mar 17 11:37:01 2026] usbcore: registered new interface driver r8152 [Tue Mar 17 11:37:01 2026] usbcore: registered new interface driver cdc_ether [Tue Mar 17 11:37:01 2026] usbcore: registered new interface driver cdc_ncm [Tue Mar 17 11:37:01 2026] usbcore: registered new interface driver cdc_wdm [Tue Mar 17 11:37:01 2026] usbcore: registered new interface driver cdc_mbim [Tue Mar 17 11:37:01 2026] r8152 2-1:1.0 enx00e04c680142: renamed from eth0 [Tue Mar 17 11:37:02 2026] xhci-hcd xhci-hcd.3.auto: WARN: HC couldn't access mem fast enough for slot 1 ep 6 [Tue Mar 17 11:37:02 2026] r8152 2-1:1.0 enx00e04c680142: intr status -63 [Tue Mar 17 11:37:07 2026] xhci-hcd xhci-hcd.3.auto: WARN: HC couldn't access mem fast enough for slot 1 ep 6 [Tue Mar 17 11:37:07 2026] r8152 2-1:1.0 enx00e04c680142: intr status -63 [Tue Mar 17 11:37:35 2026] xhci-hcd xhci-hcd.3.auto: WARN: HC couldn't access mem fast enough for slot 1 ep 6 [Tue Mar 17 11:37:35 2026] r8152 2-1:1.0 enx00e04c680142: intr status -63 Subsequent iperf3 example: iperf3 -c nx1 Connecting to host nx1, port 5201 [ 5] local 192.168.1.191 port 58598 connected to 192.168.1.14 port 5201 [ ID] Interval Transfer Bitrate Retr Cwnd [ 5] 0.00-1.00 sec 221 MBytes 1.85 Gbits/sec 0 5.35 MBytes [ 5] 1.00-2.00 sec 280 MBytes 2.35 Gbits/sec 0 5.35 MBytes [ 5] 2.00-3.00 sec 280 MBytes 2.35 Gbits/sec 0 5.35 MBytes [ 5] 3.00-4.00 sec 18.1 MBytes 152 Mbits/sec 1 1.41 KBytes [ 5] 4.00-5.00 sec 0.00 Bytes 0.00 bits/sec 0 1.41 KBytes [ 5] 5.00-6.00 sec 0.00 Bytes 0.00 bits/sec 0 1.41 KBytes [ 5] 6.00-7.00 sec 0.00 Bytes 0.00 bits/sec 0 1.41 KBytes [ 5] 7.00-8.00 sec 0.00 Bytes 0.00 bits/sec 0 1.41 KBytes [ 5] 8.00-9.00 sec 0.00 Bytes 0.00 bits/sec 0 1.41 KBytes [ 5] 9.00-10.00 sec 0.00 Bytes 0.00 bits/sec 0 1.41 KBytes - - - - - - - - - - - - - - - - - - - - - - - - - [ ID] Interval Transfer Bitrate Retr [ 5] 0.00-10.00 sec 800 MBytes 670 Mbits/sec 1 sender [ 5] 0.00-10.86 sec 796 MBytes 615 Mbits/sec receiver

You may be experiencing the same issue that other people are encountering: https://github.com/tauri-apps/tauri/issues/12787 @Giunti Can you confirm that this is the same issue as the one reported above? Thank you.

We made several test install on Windows 11 and it always worked ... bugs are possible. Best here: https://github.com/armbian/imager/issues And add perhaps more information about the OS, hardware, any special settings that might play a role here. I don't think there is. As far as I can recall, we haven't see this problem yet. Let's ping main developer - if he has any ideas. @SuperKali But as this is a complex software with possible bugs deep down in some libraries, or even Windows itself - I assume you run with all updates?

I have a ROCK 3A that reaches Maskrom/recovery but will not boot any Radxa or Armbian SD image and produces no useful UART output. UART is configured per Radxa docs at 1500000 8N1 on the debug header, and the exact same adapter/host/settings work on another ROCK 3A. There is no eMMC and no NVMe installed. I also tried resetting/loading SPI via Maskrom using rkdeveloptool db rk356x_spl_loader_ddr1056_v1.12.109_no_check_todly.bin, then loading Radxa’s rock-3a-spi-image-gef9f6b1caad.img. Radxa’s ROCK 3A loader directory contains the matching SPI artifacts, including rock-3a-spi-image-gef9f6b1caad.img, rock-3a-idbloader-gef9f6b1caad.img, and rock-3a-u-boot-gef9f6b1caad.itb, along with RK356x SPL loader binaries. Looking for guidance on whether this points to SPI/SPL/DDR init or a board hardware fault.

This week in Armbian development saw significant progress across board support and kernel updates. New boards such as the Cainiao CNIOT Core, EByte ECB41-PGE, DG SVR 865 Tiny, and NORCO EMB-3531 received initial support, expanding hardware compatibility. Kernel patches were rewritten for the meson64 and rockchip64 platforms, aligning with version 6.18.18, while edge releases were bumped to 7.0-rc3 and rc4. Improvements included enhanced SD card and audio support for SpacemiT and Youyeetoo YY3588 boards, as well as refined configuration checks and display fixes. Several upstream patches were dropped or disabled, and the Dependabot schedule was updated for daily maintenance. Additional fixes addressed USB modes, Docker host-gateway resolution, and Xorg display issues, rounding out a productive week for the Armbian project. ChangesAdd cainiao-cniot-core board and cainiao vendor image. by @retro98boy in armbian/armbian.github.io#251Add EByte Vendor // ECB41-PGE board. by @vidplace7 in armbian/armbian.github.io#250add recomputer rk3576-devkit dts. by @ackPeng in armbian/linux-rockchip#451Add support for the Radxa Display 10 FHD to the Rock 5B Plus. by @FlorianKohn in armbian/linux-rockchip#453add: initial support for DG SVR 865 Tiny board (SM8250/QCS8250). by @Lemon1151 in armbian/build#9423arch: arm: dts: add EByte ECB41-PGE (RK3506g2). by @vidplace7 in armbian/linux-rockchip#454armbian-zram-config: refine check for existing /tmp mount. by @vidplace7 in armbian/build#9514cainiao cniot core improve. by @retro98boy in armbian/build#9526chore: update Dependabot schedule to daily updates. by @igorpecovnik in armbian/build#9537csc board: Add NORCO EMB-3531 initial support. by @retro98boy in armbian/build#9456Drop patches that landed upstream and fix two. by @igorpecovnik in armbian/build#9544edge: bump 7.0 to rc4. by @EvilOlaf in armbian/build#9543extension: ccache-remote: fix Docker host-gateway for hostnames resolving to loopback. by @iav in armbian/build#9505fix(orangepi5max): change usbdrd_dwc3_0 mode from otg to host. by @Echoflare in armbian/linux-rockchip#449fix: correct repository dispatch event type name. by @igorpecovnik in armbian/armbian.github.io#254framework run_host_x86_binary_logged - support 32-bit x86. by @tabrisnet in armbian/build#9466Gateway AM-GZ80x: Update $board and meson-axg family conf. by @pyavitz in armbian/build#9533maint: meson64-current: rewrite patches against 6.18.18. by @EvilOlaf in armbian/build#9528maint: rockchip64-current: rewrite kernel patches against 6.18.18. by @EvilOlaf in armbian/build#9527meson64: a311d: Fix Xorg display when etnaviv enabled. by @retro98boy in armbian/build#9524Odroid-M2: Support for weather board zero. by @mlegenovic in armbian/build#9523odroidn2: u-boot: bump to v2026.04-rc3; make fancy, incl LWIP. by @rpardini in armbian/build#9507OrangePi 3 LTS: Update $board.conf file. by @pyavitz in armbian/build#9495OrangePi-RV2/R2S: add sdcard and emmc for Linux-7.x. by @sven-ola in armbian/build#9539Reword BTF memory check. by @x13-me in armbian/build#9502RK3506: Add spidev overlays for RK3506 family. by @vidplace7 in armbian/linux-rockchip#450rockchip64: bump edge to 7.0-rc3. by @EvilOlaf in armbian/build#9445rockchip64: cleanup old patchsets. by @EvilOlaf in armbian/build#9498rockchip: Add CSC board EByte ECB41-PGE (RK3506G). by @vidplace7 in armbian/build#9513rockchip: refresh LibreELEC patch import for edge 6.19 kernel. by @paolosabatino in armbian/build#9506rockchip: restore proper LE patches for rockchip armhf. by @paolosabatino in armbian/build#9530rpi4b: bump edge to 7.0. by @EvilOlaf in armbian/build#9529Spacemit rv2 rename dtb. by @sven-ola in armbian/build#9531SpacemiT: Add SD card support, CPU freq scaling and other fixups. by @pyavitz in armbian/build#9518SpacemiT: Disable patches that made it upstream (7.0-rc4). by @pyavitz in armbian/build#9540spacemit: enable powervr drm driver for current 6.18 kernels. by @sven-ola in armbian/build#9515sunxi: bump edge to 6.19.y, current to 6.18.y and legacy to 6.12.y. by @EvilOlaf in armbian/build#9381Youyeetoo YY3588: Enable ES8388 audio support + RK3588 I2S MCLK gate fix . by @SuperKali in armbian/build#9534View the full article

After some experimentation, I realized that the full xfce images are working fine, likely because NetworkManager is built in. The minimal CLI images, even after switching to NetworkManager per the instructions here, never worked for me to retain Wifi after a reboot. I'm going through the process of removing the XFCE desktop from my install as CPU utilization in Klipper is very high otherwise.

FWIW, I am running -edge kernel from armbian with respective dtb (linux-dtb-edge-rockchip64 package), and it's quite stable. vmlinuz-6.18.0-rc6-edge-rockchip64 dtb-6.18.0-rc6-edge-rockchip64 🤞

For information: First reboot and crash same that before use rk3399-kobol-helios64.dtb-6.12.xx-L2-hs400-opp. 😞 Back to 6.12.58, rk3399-kobol-helios64.dtb-6.12.xx-L2-hs400-opp and freeze to this setting Me and my brother have helios64 with 6.18.10 Kernel : RAID 10 / LVM / LUKS and crash always when "cryptsetup open..." start Crash when many I/O Crash when use Full CPUs With rk3399-kobol-helios64.dtb-6.12.xx-L2-hs400-opp and Kernel 6.12.58 or 6.12.(XX below): Me, never crash but I reboot often and power off often for personal choice. My brother have uptime upper than 100 or 200 days with problem, freeze or crash Bye

Hi everybody, I running Helios64 with kernel 6.12.58 since a long time and the prahal dtb file rk3399-kobol-helios64.dtb-6.12.xx-L2-hs400-opp and my helios64 work well. Today, Armbian upgrade to 6.18.10 kernel. Is this update use the same change or patch like in rk3399-kobol-helios64.dtb-6.12.xx-L2-hs400-opp ? Is rk3399-kobol-helios64.dtb-6.12.xx-L2-hs400-opp work with 6..18.10 kernel ? Is I must to downgrade to 6.12.58 kernel with rk3399-kobol-helios64.dtb-6.12.xx-L2-hs400-opp and freeze at this kernel version ? Thanks for answer.

@naceur abdelkader Your post has nothing to do with Armbian. Please find a more appropriate site to ask your question. This site is for Armbian linux.

Dear Sir/Madam, I am writing to request the official firmware for my Trenspeed H616 device. I accidentally installed an Orange Pi firmware, which caused my device to lose the Google Play Store and essential services. Device specifications: Board: T98_616_LP3_210222 Memory: 4GB RAM / 32GB storage Current version: Android 10 I would greatly appreciate it if you could provide a link to the official firmware or instructions for the correct update, ensuring that it includes Google Play Store and core services. Thank you very much for your assistance.

Download the RV2 image. It's basically the same plus DKMS (including headers) for building the bcmdhd wifi driver. You need to change the "fdt" line in /boot/extlinux/extlinux.conf for rv2->r2s (DTB file is there), e.g before uploading with mount -o offset=$(( 512 * 8192 )) Armbian-....img /mnt/

@sven-ola The nightly is on 6.19 without headers, so I can't build any additional drivers. The nightly is working on the R2S with ethernet ports and no heating issues, no load average problems. How do I get a 6.18 build (Current)? Thanks.

PCIe is a rabbit hole for it's own. I have a Wifi card that cannot issue in-line-interrupts ("MSI") for some reason so the firmware upload fails, while working fine with same driver in my PC. I simply don't use it. ASPM quirks also seems not to be too uncommon, a simple grep quirk_disable_aspm drivers/pci/quirks.c|wc -l shows 21...

@maxsub with a recent kernel, temp and load should be fine. The exiting question is: all 4 Ethernet ports are working?

Schematics-wise no - at leasts I don't see a diff in the RV2_SCH.pdf. Electrical-wise probably - other traces, so maybe more or less crosstalk, better or worse gnd and such. From a software perspective: this is PCIE-B and C (while A is unused). That PCIe active state power management seems to be a source of endless pleasure, maybe the NVME vendors all have digested the wrong specs or so. Anyhow: if it works now, it's fine probably.

My n2 works fine btw. https://paste.armbian.com/cocivagayi

@sven-ola Nightly build fixed the load problem and heat problem on R2S: linux-image-current-spacemit/now 26.2.0-trunk.574 riscv64 [installed,local] Armbian Linux current kernel image 6.18.18-current-spacemit This is my current uname -r: 6.18.18-current-spacemit

Setting pcie_aspm=off makes the drive work in the top slot albeit one order of magnitude slower than in the bottom slot. If I swap the kernel parameter with pcie_aspm.policy=performance, I've got a working drive and it's operating at normal speed. Thanks a bunch! Seeing that there are differences in behavior between the two M.2 slots, does that mean they're connected differently?

> apt search linux-headers linux-headers-6.19.6+deb14+1-common/testing 6.19.6-2 all Common header files for Linux 6.19.6+deb14+1 linux-headers-6.19.6+deb14+1-riscv64/testing 6.19.6-2 riscv64 Header files for Linux 6.19.6+deb14+1-riscv64 linux-headers-riscv64/testing 6.19.6-2 riscv64 Header files for Linux riscv64 configuration (meta-package) > uname -r 6.18.18-current-spacemit

I installed 6.18.18-current-spacemit from the nightly but can't find the headers package to build the GPU support. The repo has 6.19.x headers but no 6.18.x headers.

FT232R, CH340 or CP2104 are known to work nicely. Search for any usb uart adapter built around one of these. Don't get CP2102 because if you ever get a rockchip board it would be useless.

If you'd like to get the LEDs working with armbian, you can run these commands (or one of the other ones if you want different indications): run modprobe ledtrig-netdev to check if it's loading the driver properly. If not, add the file /etc/modules-load.d/ledtrig.conf add just this line: ledtrig-netdev Then, create /etc/tmpfiles.d/leds.conf and add this: w /sys/class/leds/green:lan/trigger - - - - netdev w /sys/class/leds/green:lan/device_name - - - - eth0 w /sys/class/leds/green:lan/link - - - - 1 w /sys/class/leds/green:lan/tx - - - - 1 w /sys/class/leds/green:lan/rx - - - - 1 w /sys/class/leds/green:wan/trigger - - - - netdev w /sys/class/leds/green:wan/device_name - - - - eth1 w /sys/class/leds/green:wan/link - - - - 1 w /sys/class/leds/green:wan/tx - - - - 1 w /sys/class/leds/green:wan/rx - - - - 1 w /sys/class/leds/red:power/trigger - - - - activity Note that "red:power" is actually the "green:sys" LED. I don't see a way to control the red power led (which is fine, the green:sys is what want to control anyway). I also use NetworkManager and set my ethernet names to eth0 and eth1 instead of the default names... Here's all the choices available for "triggers": none usb-gadget usb-host kbd-scrolllock kbd-numlock kbd-capslock kbd-kanalock kbd-shiftlock kbd-altgrlock kbd-ctrllock kbd-altlock kbd-shiftllock kbd-shiftrlock kbd-ctrlllock kbd-ctrlrlock disk-activity disk-read disk-write mtd nand-disk heartbeat cpu cpu0 cpu1 cpu2 cpu3 cpu4 cpu5 activity default-on panic usbport mmc1 rfkill-any rfkill-none r8169-0-100:00:link r8169-0-100:00:10Mbps r8169-0-100:00:100Mbps r8169-0-100:00:1Gbps stmmac-0:01:link stmmac-0:01:10Mbps stmmac-0:01:100Mbps stmmac-0:01:1Gbps netdev "activity" is also a good one for red:power if you prefer that to "heartbeat"

I changed the devicedesc, but game still shows same error. And the launcher shows it is another name. (Nvdia Geforce 6800).Ps: must go bed for now XD.

Not sure its related, but on the MusePi Pro I was getting odd happenings with the PCIe. Adding this to the command line resolved it my case: nvme_core.default_ps_max_latency_us=0 pcie_aspm=off pcie_port_pm=off