Active threads

This device is not yet fully compatible with the mainline Linux kernel. Realtek USB 2.5GbE adapters, in particular, are known to have issues when used over USB 3 on these devices. The vendor-provided kernel reportedly offers better tuning for these adapters, though it is still not entirely flawless.

Making progress, but it seems there a number of problems to work through... Here's my current state, comments/suggestions welcome It does seem to eventually be happy(ish) with the BAR setup wth minor DTB changei, but it doesn't seem to even try to load the firmware.... :- [ 950.592779] amdgpu 0000:01:00.0: amdgpu: initializing kernel modesetting (POLARIS12 0x1002:0x699F 0x1458:0x22F2 0xC7). [ 950.592800] amdgpu 0000:01:00.0: amdgpu: register mmio base: 0xF0200000 [ 950.592802] amdgpu 0000:01:00.0: amdgpu: register mmio size: 262144 [ 950.592956] amdgpu 0000:01:00.0: amdgpu: detected ip block number 0 <common_v1_0_0> (vi_common) [ 950.592960] amdgpu 0000:01:00.0: amdgpu: detected ip block number 1 <gmc_v8_1_0> (gmc_v8_0) [ 950.592962] amdgpu 0000:01:00.0: amdgpu: detected ip block number 2 <ih_v3_0_0> (tonga_ih) [ 950.592965] amdgpu 0000:01:00.0: amdgpu: detected ip block number 3 <gfx_v8_0_0> (gfx_v8_0) [ 950.592967] amdgpu 0000:01:00.0: amdgpu: detected ip block number 4 <sdma_v3_1_0> (sdma_v3_0) [ 950.592970] amdgpu 0000:01:00.0: amdgpu: detected ip block number 5 <smu_v1_0_0> (powerplay) [ 950.592972] amdgpu 0000:01:00.0: amdgpu: detected ip block number 6 <dce_v1_0_0> (dm) [ 950.592975] amdgpu 0000:01:00.0: amdgpu: detected ip block number 7 <uvd_v6_3_0> (uvd_v6_0) [ 950.592977] amdgpu 0000:01:00.0: amdgpu: detected ip block number 8 <vce_v3_4_0> (vce_v3_0) [ 950.920388] amdgpu 0000:01:00.0: amdgpu: Fetched VBIOS from ROM BAR [ 950.920394] amdgpu: ATOM BIOS: xxx-xxx-xxx [ 950.920492] [drm] UVD is enabled in VM mode [ 950.920494] [drm] UVD ENC is enabled in VM mode [ 950.920497] [drm] VCE enabled in VM mode [ 950.920500] amdgpu 0000:01:00.0: amdgpu: Trusted Memory Zone (TMZ) feature not supported [ 950.920504] amdgpu 0000:01:00.0: amdgpu: PCIE atomic ops is not supported [ 950.920510] amdgpu 0000:01:00.0: amdgpu: PCI CONFIG reset [ 950.920627] amdgpu 0000:01:00.0: amdgpu: GPU posting now... [ 951.046148] amdgpu 0000:01:00.0: amdgpu: vm size is 128 GB, 2 levels, block size is 10-bit, fragment size is 9-bit [ 951.046277] amdgpu 0000:01:00.0: BAR 2 [mem 0x910000000-0x9101fffff 64bit pref]: releasing [ 951.046282] amdgpu 0000:01:00.0: BAR 0 [mem 0x900000000-0x90fffffff 64bit pref]: releasing [ 951.046315] pcieport 0000:00:00.0: bridge window [mem 0x900000000-0x9101fffff 64bit pref]: releasing [ 951.046323] pcieport 0000:00:00.0: bridge window [mem size 0x80200000 64bit pref]: can't assign; no space [ 951.046325] pcieport 0000:00:00.0: bridge window [mem size 0x80200000 64bit pref]: failed to assign [ 951.046330] pcieport 0000:00:00.0: bridge window [mem size 0x80200000 64bit pref]: can't assign; no space [ 951.046332] pcieport 0000:00:00.0: bridge window [mem size 0x80200000 64bit pref]: failed to assign [ 951.046335] amdgpu 0000:01:00.0: BAR 0 [mem size 0x80000000 64bit pref]: can't assign; no space [ 951.046337] amdgpu 0000:01:00.0: BAR 0 [mem size 0x80000000 64bit pref]: failed to assign [ 951.046339] amdgpu 0000:01:00.0: BAR 2 [mem size 0x00200000 64bit pref]: can't assign; no space [ 951.046341] amdgpu 0000:01:00.0: BAR 2 [mem size 0x00200000 64bit pref]: failed to assign [ 951.046344] amdgpu 0000:01:00.0: BAR 0 [mem size 0x80000000 64bit pref]: can't assign; no space [ 951.046345] amdgpu 0000:01:00.0: BAR 0 [mem size 0x80000000 64bit pref]: failed to assign [ 951.046347] amdgpu 0000:01:00.0: BAR 2 [mem size 0x00200000 64bit pref]: can't assign; no space [ 951.046349] amdgpu 0000:01:00.0: BAR 2 [mem size 0x00200000 64bit pref]: failed to assign [ 951.046352] pcieport 0000:00:00.0: PCI bridge to [bus 01-ff] [ 951.046354] pcieport 0000:00:00.0: bridge window [io 0x300000-0x300fff] [ 951.046357] pcieport 0000:00:00.0: bridge window [mem 0xf0200000-0xf02fffff] [ 951.046360] pcieport 0000:00:00.0: PCI bridge to [bus 01-ff] [ 951.046362] pcieport 0000:00:00.0: bridge window [io 0x300000-0x300fff] [ 951.046364] pcieport 0000:00:00.0: bridge window [mem 0xf0200000-0xf02fffff] [ 951.046367] pcieport 0000:00:00.0: bridge window [mem 0x900000000-0x9101fffff 64bit pref] [ 951.046380] amdgpu 0000:01:00.0: amdgpu: Not enough PCI address space for a large BAR. [ 951.046383] amdgpu 0000:01:00.0: BAR 0 [mem 0x900000000-0x90fffffff 64bit pref]: assigned [ 951.046405] amdgpu 0000:01:00.0: BAR 2 [mem 0x910000000-0x9101fffff 64bit pref]: assigned [ 951.046430] amdgpu 0000:01:00.0: amdgpu: VRAM: 2048M 0x000000F400000000 - 0x000000F47FFFFFFF (2048M used) [ 951.046433] amdgpu 0000:01:00.0: amdgpu: GART: 256M 0x000000FF00000000 - 0x000000FF0FFFFFFF [ 951.046438] [drm] Detected VRAM RAM=2048M, BAR=256M [ 951.046440] [drm] RAM width 128bits GDDR5 [ 951.046690] amdgpu 0000:01:00.0: amdgpu: amdgpu: 2048M of VRAM memory ready [ 951.046695] amdgpu 0000:01:00.0: amdgpu: amdgpu: 15812M of GTT memory ready. [ 951.046733] [drm] GART: num cpu pages 65536, num gpu pages 65536 [ 951.048243] [drm] PCIE GART of 256M enabled (table at 0x000000F400000000). [ 951.048855] [drm] Chained IB support enabled! [ 951.050102] amdgpu: hwmgr_sw_init smu backed is polaris10_smu [ 951.050568] [drm] Found UVD firmware Version: 1.130 Family ID: 16 [ 951.054854] [drm] Found VCE firmware Version: 53.26 Binary ID: 3 [ 951.264633] amdgpu 0000:01:00.0: [drm:amdgpu_ring_test_helper [amdgpu]] *ERROR* ring gfx test failed (-110) [ 951.266003] amdgpu 0000:01:00.0: amdgpu: hw_init of IP block <gfx_v8_0> failed -110 [ 951.266667] amdgpu 0000:01:00.0: amdgpu: amdgpu_device_ip_init failed [ 951.267227] amdgpu 0000:01:00.0: amdgpu: Fatal error during GPU init [ 951.267780] amdgpu 0000:01:00.0: amdgpu: amdgpu: finishing device.

As amazingfate (the Armbian dev for this device) clearly stated on the forum: cellular and camera are not working, only display, touch, wifi, and bluetooth are functional—so it won't replace your phone OS for calls and texts

Can confirm. S905X5M is a different beast than the S905X. If there's interest, I can start another thread with an image and status, once this is somewhat more stable. Currently booting, but not without some debug console interaction on power up. In the meantime, code's up at https://github.com/tparys/build/tree/odroidc5 if anyone wants to go poking

Hello, I hope you don't have any problem. Maybe me and my brother have defective or more unstable helios64 than you. Only thing I can say that Prahal share here the specifics files rk3399-kobol-helios64.dtb-6.XX.xx-L2-hs400-opp in this forum since two years ago my helios64 and my brother's helios64 work stable only with it. I back to 6.12.58 Kernel with rk3399-kobol-helios64.dtb-6.12.xx-L2-hs400-opp file and freeze firmware/kernel with armbian-config.

I am having issues with eMMC detection… The kernel does not detect the eMMC, but apparently U-Boot does. Attached are images.

Hi, I am trying out Armbian 26.2.0-trunk.592 nightly (trixie) on a Radxa Rock PI 4b+ The community supported image boots fine and it is no problem to install Armbian on the on-board eMMC flash, but the installed NVMe SSD on PCIi is no recognised. It looks like the whole PCIe bus is not initialised properly during boot. in the kernel log I see: [ 0.062396] /pcie@f8000000: Fixed dependency cycle(s) with /pcie@f8000000/interrupt-controller [ 2.160749] rockchip-pcie f8000000.pcie: host bridge /pcie@f8000000 ranges: [ 2.160771] rockchip-pcie f8000000.pcie: MEM 0x00fa000000..0x00fbdfffff -> 0x00fa000000 [ 2.160779] rockchip-pcie f8000000.pcie: IO 0x00fbe00000..0x00fbefffff -> 0x00fbe00000 [ 2.869988] rockchip-pcie f8000000.pcie: PCIe link training gen1 timeout! [ 2.870032] rockchip-pcie f8000000.pcie: probe with driver rockchip-pcie failed with error -110 I have searched for quite a while now but could not really find a solution for this. It seems there have been similar problems reported regarding other SOCs using the same chip and I even see patches being proposed (not sure whether the PR has been merged) though at this moment I cannot really see any solution available to this yet. Did anyone else encounter this and is there any fix or workaround for this? I installed the Homeassistant OS image for this board (maintained here: https://github.com/citruz/haos-rockpi), which does not have this issue and allowed me to install and boot from the NVMe drive without any problem. Is anyone aware of the differences in the upstream linux kernel and the one that Armbian ships w.r.t. patches that could make a difference here? regards, Frederik

While waiting for new info, first poke in the dark. rk3399-fix-pci-phy.patch disabled https://testing.armbian.de/r4s/ feel free to test

Perhaps a hardware defect? At least that would be my guess from what it sounds.

Hi Does anyone have any advice on how to get Armbian running on this device. I am comeplety new to Armbian. Is there a generic Allwinner H6 image that I need to modify? Any advice pls? Thanks

Hello, this is my first message here: I want to thank the community for the work done so far, and for allowing to keep functional old devices which would otherwise become (nasty) garbage. Now, I tried to install Armbian on a Wetek Play 2 (Amlogic S905), buit now the box is not booting. I would be grateful if I could get some help, or at least clarification about what happened. Here is what I did so far: Download the image `Armbian_community_26.2.0-trunk.493_Aml-s9xx-box_trixie_current_6.18.13_minimal.img.xz`, and write it on a SD card. Boot from the SD card, by holding the power button when inserting the power cable. The box booted fine. Log in via SSH, and configure the installation. Back-up the full emmc with `dd if=/dev/mmcblk1 of=/mnt/backup/wetek_play2_android_emmc.img bs=4M`. The emmc had the original Android system (with more stuff installed, but I guess the most important part are the first 4 MB...) Run the `/root/install-aml` script. Power-off When powering on again, the box did not boot. I tried to boot from SD by holding the power button, but it did not work. So at this point my questions are: What can I do to recover the situation? What did I made wrong? As additional context, in the past I had also successfully booted LibreELEC from SD, although the last boot before switching to Armbian was to Android. Thanks for your help UPDATE: OK, I think I found the culprit: I overseen the quite important statement "Note: It is not possible to install into emmc on boxes with the s905 cpu". Great.

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.

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.

@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.

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/

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

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.

With the help of AI, dts writing (kernel 5.10) has been achieved. It's basically error-free. Only applicable to shutuo v8 version Results: Wired network is normal Wireless network is normal USB interface is normal rk3288-shutuo-v8.dtb rk3288-shutuo-v8.dts

I see there's an overlay for the R4S called rk3399-dwc3-0-host, but it already seems to be in host mode by default. I can't figure out how to set it to peripheral mode so I can have some usb-gadget love. Anyone figured out a fix?

Good morning I have big problem I have tv box Transpeed-H616_ I update with orange pi But i can't back to old firmware

Hello! I had motherboard BA839_141 V2.0 21021 with this type hardware on the photos. Allwinner H313, 8x D9PSC, Toshiba THGBM5G7A2JBAIR And i want use it only with non graphical linux, can someone help me, because i don't see anywhere images for this one, and the other ones only give me black screen. Device won't start with microSD card.

The problem was in the dtb which comes with the Armbian image, added the fix, now it is working as expected. Attaching the fixed dtb file, just replace it with this one and enjoy! Rename the attached file to k3-am67a-beagley-ai.dtb and copy it to your /boot/dtb/ti/ path and reboot. k3-am67a-beagley-ai.dtb_armbian_fixed

Thanks, gabriel_altoe for your advice. I'm abble to boot from the image you pointed. I have the same board. I success boot with minimal image too from this link: https://github.com/sicXnull/armbian-build/releases/download/v24.8.0-trunk.425/Armbian-unofficial_26.02.0-trunk_X96q-v1-3_bookworm_current_6.12.64_minimal.img.xz