All Activity

Thank you. R2S has a built in eMMC and USB. The only way to get a new image is to boot from USB but it seems like I have to manually load the image in u-boot. Is the u-boot script (boot.txt) for the build somewhere in GitHub?

Have you tried all of the gxm dtb files? Per the instructions (https://forum.armbian.com/topic/33676-installation-instructions-for-tv-boxes-with-amlogic-cpus)

@maxsub I was not even aware, that boot from USB is a thing. The RV2 boots from SD via extlinux, here is the relevant uboot output. HTH [ 3.458] Retrieving file: /boot/extlinux/extlinux.conf [ 3.490] 1: Armbian-unofficial [ 3.490] Retrieving file: /boot/uInitrd [ 4.772] Retrieving file: /boot/Image [ 5.767] append: root=UUID=c79489b6-9fea-4a53-a334-d91a0f30843a earlycon=sbi console=tty1 console=ttyS0,115200 logleve l=1 rw no_console_suspend consoleblank=0 fsck.fix=yes fsck.repair=yes net.ifnames=0 splash plymouth.ignore-serial-consol es [ 5.785] Retrieving file: /boot/dtb/spacemit/k1-orangepi-rv2.dtb [ 5.838] Uncompressing Kernel Image [ 6.218] Moving Image from 0x10000000 to 0x200000, end=2c90000 [ 6.245] ## Loading init Ramdisk from Legacy Image at 21000000 ... [ 6.248] Image Name: uInitrd [ 6.251] Image Type: RISC-V Linux RAMDisk Image (gzip compressed) [ 6.258] Data Size: 20347839 Bytes = 19.4 MiB [ 6.263] Load Address: 00000000 [ 6.266] Entry Point: 00000000 Verifying Checksum ... OK [ 6.363] ## Flattened Device Tree blob at 31000000 [ 6.365] Booting using the fdt blob at 0x31000000 [ 6.370] Loading Ramdisk to 7ca0b000, end 7dd72bbf ... OK [ 6.391] Loading Device Tree to 000000007c9eb000, end 000000007ca0a097 ... OK Starting kernel ...

i am trying to install armbian on a vorke z6 plus s912 amlogic box. As there is no S912 dtb, i tried using /dtb/amlogic/meson-gxm-t95z-plus.dtb with this iamge: Armbian_26.02.0_amlogic_s912-t95z-plus_trixie_6.18.15_server_2026.03.01.img.gz renamed u-boot-s905x-s912.bin to u-boot.ext After inserting and pressing the reset button, before applying power, i get into the recovery menu What dtb file or image can i use to get armbian running?

Depends on the image you are using. The image for 3 LTS should work for the 3 LTS. The image for the 3 (without lts) will not.

Without uart hard to tell.

I ran into a problem. Flashed the nightly build to the eMMC on the R2S and now it won’t boot from USB. I can see the usb drive in u-boot and kernel.img and dtb. What’s the default address to load the kernel and dtb on these boards? thank you.

I followed the instructions and have OpenGL ES 3 working now. I wasn't able to build Yamagi Quake 2 because of a version issue with one of the packages. I copied a build from the Muse Pi Pro and now I can run it at 1080p, and sometimes it even hits 60fps!

Hello, I am trying to run Armbian on my Orange Pi 3 LTS. The official Orange Pi image works normally: Orangepi3-lts_3.0.8_debian_bullseye_server_linux5.16.17 However, when I flash the Armbian image: Armbian 26.2.1 Minimal / IoT I get several boot errors during startup: [FAILED] Failed to start Apply Kernel Variables. [FAILED] Failed to start Dispatcher daemon for systemd-networkd. [FAILED] Failed to start Helper to synchronize boot up for ifupdown. [DEPEND] Dependency failed for Raise network interfaces. The system continues booting, but these errors appear every time. Hardware: Board: Orange Pi 3 LTS Image: Armbian 26.2.1 Minimal / IoT Storage: TF card Questions: Are these errors expected on this board? Is there a configuration issue with network initialization? Is this image fully supported for Orange Pi 3 LTS? Thank you.

@xiboliyadongtu Then copy x64/d3d11.dll, x64/dxgi.dll files to the same folder as blackdesert64.exe and try to run it without the launcher.

Hi everyone, I'm facing an issue with Armbian installation on Rock 5B Plus. Hardware Board: Radxa ROCK 5B+ (RK3588) Storage: NVMe #1 (system): 256 GB, in M.2 slot 1 NVMe #2 (backup): 128 GB, in M.2 slot 2 Boot: MTD flash + NVMe Power supply: both POE+ HAT 25W and official power supply 30W Software Armbian: 25.11.2 Desktop ubuntu Kernel: 6.1.115-vendor-rk35xx Boot configured via armbian-install → “Boot from MTD Flash, system on NVMe” Initial install steps Wrote Armbian image to microSD and booted from SD. Used armbian-install to install: Boot from MTD Flash, system on NVMe #1 Powered off, removed SD, left only NVMe #1 installed. Board boots fine from SPI+NVMe #1: blue LED, OS comes up, Green LED, everything OK. Power off the board and plug NVME #2 (preformatted ext4 with gparted and empty, the disk works because I tried the procedure the other way around, using the second disk as the main one) Power on. Solid blue light, no OS, no HDMI output (I don't have UART) lsblk -f with microSD plugged: mtdblock0 mmcblk1 └─mmcblk1p1 ext4 1.0 armbi_root 2e67f233-22a9-46c9-90a7-8f0e0f2d3154 21.7G 22% /var/log.hdd / zram0 [SWAP] zram1 36M 16% /var/log zram2 nvme1n1 ├─nvme1n1p1 ext4 1.0 cacf66ca-ea9b-4dc4-b7b3-185f18e7c64f 100G 6% /mnt/main └─nvme1n1p2 ext4 1.0 data a7d6675c-3ca6-4a87-85cf-7d91856fd79c nvme0n1 └─nvme0n1p1 ext4 1.0 armbi_backup 5aadc790-715a-4f48-bbbc-ce4bfd2717bd 110.8G 0% /mnt/backup /boot/armbianEnv.txt looks correct verbosity=1 bootlogo=true console=both extraargs=cma=256M overlay_prefix=rockchip-rk3588 overlays=panthor-gpu fdtfile=rockchip/rk3588-rock-5b-plus.dtb rootdev=UUID=cacf66ca-ea9b-4dc4-b7b3-185f18e7c64f rootfstype=ext4 usbstoragequirks=0x2537:0x1066:u,0x2537:0x1068:u /etc/fstab looks correct # <file system> <mount point> <type> <options> <dump> <pass> tmpfs /tmp tmpfs defaults,nosuid 0 0 UUID=cacf66ca-ea9b-4dc4-b7b3-185f18e7c64f / ext4 defaults,noatime,commit=120,errors=remount-ro,x-gvfs-hide 0 1 UUID=5aadc790-715a-4f48-bbbc-ce4bfd2717bd /mnt/backup ext4 defaults,nofail 0 2 <--- also tried without this line I've also tried by "forcing" the mount of NMVE #2 by adding it to /etc/fstab of NVME #1 but nothing changes. Could you please help me understand if this is an issue related to my configuration or could be a bug? Thanks

this game do have a file named blackdesert64.exe

i just delete the default file named umu-defalut. and i try to start the launcher, but it still crash. Did i got right things? log

This game cant start without the launcher, I will try these options

@xiboliyadongtu Can this game be started without a launcher? Is there an executable file besides BlackDesertLauncher.exe (like BlackDesert.exe)? The BlackDesertLauncher.exe is definitely a 32-bit file. So, you might need to run it with GE-Proton10-32 in WoW64 mode. Delete the created GE-Proton10-32's prefix to make sure. Then start it again with envs If everything is right, you will see the Dxvk output log with something like below:

i delete the previous 64-bit version of DXVK, copy the 32-bit version DXVK, and tried to luanch the game; the game dispalyed a logo and then disappeared. Maybe it have crashed. log-dxvk log-zink

In the world of TV boxes "identical looking" means nothing, as manufacturers build each batch with the lowest cost components available at the time. There are many cases where identical looking boxes even contain different cpus ( ie amlogic vs rockchip). My recommendation would be first to verify the markings on the boards (there is usually some sort of board identifying text on the board)to really see if they are the same under the hood.

You aren't using Armbian. The balbes150 builds were a fork of Armbian and know one here would know what sources they were built with. So this question is really off topic for Armbian.

Hello everyone, I have two identical-looking "arm-64" Amlogic TV boxes (S805X-based, meson-gxl-s805x-p241.dtb), both running the same Armbian image (kernel 5.9.0-arm-64 from balbes150 build). Both boxes have BCM43430 WiFi+BT combo (AP6212 module) on SDIO (mmc1). Problem: - STB 1: WiFi works perfectly (BCM43430/1 stepping) - STB 2: WiFi fails to initialize (BCM43430/2 stepping) — always ends with "HT Avail timeout (1000000): clkctl 0x50" Key dmesg from STB 1 (working): [ 7.719726] brcmfmac: F1 signature read @0x18000000=0x1541a9a6 [ 7.736079] brcmfmac: brcmf_fw_alloc_request: using brcm/brcmfmac43430-sdio for chip BCM43430/1 [ 7.976301] brcmfmac: brcmf_c_preinit_dcmds: Firmware: BCM43430/1 wl0: Mar 30 2021 01:12:21 version 7.45.98.118 (7d96287 CY) FWID 01-32059766 → wlan0 appears and connects normally Key dmesg from STB 2 (not working): [ 7.564287] brcmfmac: F1 signature read @0x18000000=0x1542a9a6 [ 7.568240] brcmfmac: brcmf_fw_alloc_request: using brcm/brcmfmac43430-sdio for chip BCM43430/2 [ 8.644057] brcmfmac: brcmf_sdio_htclk: HT Avail timeout (1000000): clkctl 0x50 [ 9.652082] brcmfmac: brcmf_sdio_htclk: HT Avail timeout (1000000): clkctl 0x50 → No wlan0 interface created What I already tried on STB 2: 1. Copied entire /lib/firmware/brcm folder from STB 1 → same timeout 2. Symlinked brcmfmac43430a0-sdio.bin / .txt → same timeout 3. Symlinked Raspberry Pi 3 variant (brcmfmac43430-sdio.raspberrypi,3-model-b.txt) → same 4. Created symlink for board-specific file: ln -sf brcmfmac43430-sdio.txt brcmfmac43430-sdio.amlogic,p241.txt → still fails 5. Added various NVRAM tweaks (boardflags3=0x48200100, LPO=1, sd_drivestrength=6, etc.) → no change 6. Tried sdio_overclock=0 (and 25000000) → module says "unknown parameter 'sdio_overclock' ignored" (not supported in this kernel 5.9 build) Current /lib/firmware/brcm contents (relevant files): - brcmfmac43430-sdio.bin - brcmfmac43430-sdio.txt - brcmfmac43430a0-sdio.bin - brcmfmac43430a0-sdio.txt - brcmfmac43430-sdio.raspberrypi,3-model-b.txt - brcmfmac43430-sdio.amlogic,p241.txt (now exists) modinfo brcmfmac shows no sdio_overclock or drive_strength parameter available. Questions: - Has anyone seen BCM43430/2 stepping specifically fail like this while /1 works on the same image? - Is there a known good NVRAM .txt for BCM43430/2 on Amlogic boxes? - Any other module parameters or DTB tweaks that could slow down SDIO clock or force LPO mode? - Or is this most likely a hardware difference (LPO crystal issue on the module/board)? Any help or pointers greatly appreciated — really want to avoid buying USB dongles if possible. Thanks! ls /lib/firmware/brcm bcm4329.hcd BCM4330B1.hcd bcm4330.hcd BCM43342.hcd BCM4334B0.hcd BCM43430A1.hcd BCM43430B0.hcd bcm43438-sdio.hcd BCM4343A0.hcd BCM4345C0_003.001.025.0162.0000_Generic_UART_37_4MHz_wlbga_ref_iLNA_iTR_eLG.hcd BCM4345C0.amlogic,sm1.hcd BCM4345C0.firefly,rk3566-roc-pc.hcd BCM4345C0.radxa,zero2.hcd BCM4345C0.raspberrypi,4-compute-module.hcd BCM4345C5.hcd BCM4356A2.hcd BCM4359C0.hcd BCM4362A2.hcd BCM4362A2-khadas-vim4.hcd brcmfmac4329-sdio.bin brcmfmac4329-sdio.txt brcmfmac4330-sdio.amlogic,q200-n1.txt brcmfmac4330-sdio.bin brcmfmac4330-sdio.rockchip,rk3318-box.txt brcmfmac4330-sdio.txt brcmfmac43342-sdio.bin brcmfmac43342-sdio.txt brcmfmac4334-sdio.bin brcmfmac4334-sdio.rockchip,rk3318-box.txt brcmfmac43362-sdio.bin brcmfmac43362-sdio.txt brcmfmac4339-sdio.1CK.txt brcmfmac4339-sdio.bin brcmfmac4339-sdio.txt brcmfmac4339-sdio.ZP.txt brcmfmac43430a0-sdio.bin brcmfmac43430a0-sdio.txt brcmfmac43430b0-sdio.bin brcmfmac43430b0-sdio.rockchip,fine3399.bin brcmfmac43430b0-sdio.txt brcmfmac43430-sdio.bin brcmfmac43430-sdio.clm_blob brcmfmac43430-sdio.raspberrypi,3-model-b.bin brcmfmac43430-sdio.raspberrypi,3-model-b.txt brcmfmac43430-sdio.raspberrypi,model-zero-2-w.bin brcmfmac43430-sdio.raspberrypi,model-zero-2-w.txt brcmfmac43430-sdio.txt brcmfmac43436s-sdio.bin brcmfmac43436s-sdio.raspberrypi,model-zero-2-w.bin brcmfmac43436s-sdio.raspberrypi,model-zero-2-w.txt brcmfmac43455-sdio.amlogic,sm1.bin brcmfmac43455-sdio.amlogic,sm1.txt brcmfmac43455-sdio.bin brcmfmac43455-sdio.clm_blob brcmfmac43455-sdio.firefly,rk3566-roc-pc.bin brcmfmac43455-sdio.firefly,rk3566-roc-pc.txt brcmfmac43455-sdio.radxa,zero2.bin brcmfmac43455-sdio.radxa,zero2.txt brcmfmac43455-sdio.raspberrypi,3-model-b-plus.bin brcmfmac43455-sdio.raspberrypi,4-compute-module.bin brcmfmac43455-sdio.raspberrypi,4-compute-module.txt brcmfmac43455-sdio.raspberrypi,4-model-b.bin brcmfmac43455-sdio.raspberrypi,4-model-b.txt brcmfmac43455-sdio.raspberrypi,5-model-b.bin brcmfmac43455-sdio.raspberrypi,5-model-b.clm_blob brcmfmac43455-sdio.raspberrypi,5-model-b.txt brcmfmac43455-sdio.txt brcmfmac43456-sdio.bin brcmfmac43456-sdio.clm_blob brcmfmac43456-sdio.radxa,rockpi4b.bin brcmfmac43456-sdio.radxa,rockpi4b.txt brcmfmac43456-sdio.radxa,zero2.bin brcmfmac43456-sdio.radxa,zero2.txt brcmfmac43456-sdio.radxa,zero.bin brcmfmac43456-sdio.radxa,zero.txt brcmfmac43456-sdio.raspberrypi,400.bin brcmfmac43456-sdio.raspberrypi,400.txt brcmfmac43456-sdio.txt brcmfmac4356-sdio.bin brcmfmac4356-sdio.clm_blob brcmfmac4356-sdio-nanopi-m4v2.bin brcmfmac4356-sdio-nanopi-m4v2.txt brcmfmac4356-sdio.txt brcmfmac4359-sdio.bin brcmfmac4359-sdio.txt brcmfmac43752-pcie.bin brcmfmac43752-pcie.clm_blob brcmfmac43752-pcie.txt brcmfmac43752-sdio.9tripod,x3568-v4.bin brcmfmac43752-sdio.9tripod,x3568-v4.txt brcmfmac43752-sdio.bin brcmfmac43752-sdio.clm_blob brcmfmac43752-sdio.firefly,rk3568-roc-pc.bin brcmfmac43752-sdio.firefly,rk3568-roc-pc.txt brcmfmac43752-sdio.txt brcmfmac-ap6330-sdio.bin brcmfmac-ap6330-sdio.txt clm_bcm43752a2_ag.blob config_bcm43456c5_ag.txt config_bcm43752a2_ag.txt config.txt fw_bcm43456c5_ag_apsta.bin fw_bcm43456c5_ag.bin fw_bcm43752a2_ag_apsta.bin fw_bcm43752a2_ag.bin fw_bcm43752a2_ag_p2p.bin nvram_ap6256.txt nvram_ap6275s.txt SYN43711A0.hcd

@xiboliyadongtu as your ss, the launcher is 32-bits. So, can you copy x32/d3d11.dll, x32/dxgi.dll files to the game folder and try again?

Thank you very much for your suggestions; I have tested both of them using Protonge. I replaced the BdO launcher to rule out any issues with Chinese language support. Both suggestions caused the launcher to display an error window. Furthermore, I tested the solution involving DXVK using Wine 11.4 staging, but the launcher only displayed a black window; I have uploaded the logs and screenshots. Additionally, I downloaded the Windows version of VKcube, which displays the rotating cube correctly. Translated with DeepL.com (free version) log-protonge.txt log-wine11.4staging.txt

I had similar issues with the original camera. But after days of testing even with the official radxa image I think I found the possible problem. There is a batch of boards with a wrong csi connector, the pins are not correct. I found it here: https://github.com/radxa-build/radxa-zero3/issues/15 I send a mail to my supplier and they will send me a fixed cable, I can give an update if it's fixed.

Wifi works normaly only trought NetworkManager.

Success: tested RV2 with GPU on Armbian-noble-nightly. It's a bit hacky but should work. I created a mirror of the relevant packages from Spacmit/Bianbu. Only packages with source, specific to k1x / video / gpu plus chromium. Mirror project is here, in case you want to mirror yourself or miss a package: https://codeberg.org/sven-ola/spacemit-mirror After getting up Armbian-noble-xfce4-nightly on your Spacemit/K1 board (that includes Ky X1) Add mirror repo to /etc/apt/sources.list.d/sven-ola.sources (Note: this is experimental) Types: deb deb-src URIs: https://privat-in.de/armbian Suites: noble Components: main Signed-By: /etc/apt/trusted.gpg.d/sven-ola.gpg Get my repo key with wget -O /etc/apt/trusted.gpg.d/sven-ola.gpg https://privat-in.de/armbian/key.gpg Give the mirror some weight, add an /etc/apt/preferences.d/sven-ola file Package: * Pin: release o=Sven-Ola Pin-Priority: 1000 Install GPU support apt-get update apt-get install img-gpu-powervr apt-get dist-upgrade Note: this will downgrade mesa-25.x to mesa-24.x from Bianbu/Spacemit Install a Wayland-enabled GUI (tested: gnome) apt-get install gnome-core systemctl disable lightdm If asked, select gdm from gnome instead of lightdm from xfce4. After rebooting, click on your user, then stop and select Gnome with the lower right gearwheel icon. I also installed glmark2-es2-wayland to check if that runs. It shows 417@800x600 which is faster than software mesa...

I just tested the latest Armbian distros, Armbian 26.2.0-trunk.493 XFCE and Armbian 26.2.0-trunk.493 Minimal / IOT, and none worked. Then I tried Radxa system images, rock-4se_bookworm_kde_r4.output_512.img.xz did not work. So I got confused because my Rock 4SE v 1.53 SBC worked a long time ago. Found backup of old boot image, which I used with the NVMe drive, because it could not boot on its own. And do you know what? Finally, I saw a picture on the screen with boot log information, which made me happy because it proved my SBC had not died. Then I started looking at some old system images for this board and found one which is booting, it is rock-4se_debian_bullseye_kde_b38.img.