Active threads

Continued GPU hacks. I uploaded a medley from Armbian (uboot,kernel) plus OrangePi-Ubuntu-Noble (userspace) from downloaded Xunlong image to my https://privat-in.de site (-> Downloads, grab Armbian+OrangePi.img.xz). Root PW is "orangepi" and it has 3 scripts /boot/boot-6.x.x to switch kernels between 6.6.36-ky, 6.6.99 and 6.18.x (both from Armbian). While the original "ky" kernel has GPU support (instantly visible with the Gnome GUI reacting < 2 seconds), the Armbian kernels have no GPU. Turns out: the kernel DRM driver name needs to be "rvdisplay" instead of "spacemit". This works at least with Armbian-Stable-6.6.99, while Armbian-Edge-6.18.x probably needs further kicking. The Armbian kernels have the following (prelim) change: --- a/drivers/gpu/drm/spacemit/spacemit_drm.c +++ b/drivers/gpu/drm/spacemit/spacemit_drm.c @@ -24,7 +24,7 @@ #include "spacemit_dmmu.h" #include "spacemit_gem.h" -#define DRIVER_NAME "spacemit" +#define DRIVER_NAME "rvdisplay" #define DRIVER_DESC "Spacemit SoCs' DRM Driver" #define DRIVER_MAJOR 1 #define DRIVER_MINOR 0 Note, that Xorg has no GPU, the GPU stuff only works with Wayland (gnome-shell + mutter). Also: no luck with that Bianbu-Linux. It's damn slow Gnome (slower that OrangePi with Software rendering) and none of the kernels brings the GPU to live (even the original Bianbu kernel with a orangepirv2 DTB does not work). @c0rnelius Bananapi R3 and Musepi Pro have working GPU? HTH // Sven-Ola

See here:

The raised U-Boot version here is the culprit: https://github.com/armbian/build/commit/b8844c9 Maybe done by accident, since the commit/PR message does not mention the ZeroPi at all, or that it has been successfully tested on that board. Removing those two lines BOOTBRANCH="tag:v2025.04" BOOTPATCHDIR="v2025-sunxi" , reverting to U-Boot v2024.01 and respective patch dir, solves it for us. Of course, if someone finds time, it would be interesting to find out which missing patches or changes in upstream U-Boot are causing the issue. What I see in our logs is that the last starting and never finishing service is one which calls "udevadm settle", hence waits for udev rules to be processed, endlessly. The NanoPi NEO image boots on the board, but using the NanoPi NEO device tree on the ZeroPi image does not boot, which left only the bootloader as culprit. Maybe it puts some device into a bad state which causes the kernel/udev hang. Duplicate topic:

pq eu não consigo boot com os versoes recentes a melhor para o meu projeto seria esse mesmo. sabes como posso boot com os versoes desta pagina por exemplo esta imagem Armbian_5.37_S9xxx_Ubuntu_xenial_3.14.29_server_20171226.img.xz boot tranquilo mas ubuntu 18 não da para o projeto, esta imagem Armbian_23.11.1_Aml-s9xx-box_jammy_current_6.1.63_minimal.img.xz seria perfeita mas não consigo boot, fica travado tela beelink preta. pode me ajudar? CAIXA BEELINK GT1 ULTIMATE 3GB/32GB

My recent RK3588 kernel adventure: - dual-core H.265 (HEVC) encoding working live at full 4K@60 on armbian-build edge kernel (6.19-rc8) for Rock 5B[+] and Orange Pi 5 Ultra. - fix for setting HDMIRX EDID (this didn't work in mainline on any of my tested hardware) This is out-of-tree (practical focus over upstream goals), but it's stable and producing clean bitstreams. Repo: https://github.com/rcawston/rockchip-rk3588-mainline-patches Feedback welcome.

@zcrself Your board might be missing some components for UART to work properly. Have you tested your TTL to USB adaptor on other boards to see if it works?

Please help. Hello everyone, please help me out. I urgently need to enable secure boot on my Allwinner H3 Nanopi neo core. I tried following the instructions from the forum https://forum.armbian.com/topic/3033-h3-soc-boot-rom-security-e-fuse/#findComment-84051 . But I couldn't burn the E-Fuse. At stage 5, when loading ./sunxi-fel -v -p write 0x2000 of the compiled code and checking whether the changes were applied, sunxi-fel sid/list/version doesn't work. I have to reboot the board, and then I see no result. Please help me solve this problem and burn it so that the bootloader signature is present and it is impossible to boot from the SD card using third-party means. Please, if you have any information, help me.

@marcosdsdba the only driver that works is from kernel 4.4. Unless someone figures out a way to port this to a modern kernel, your only option is to use a usb wifi adapter.

Once board is tested, its moved to its final destination https://www.armbian.com/nanopi-m4-v2/ I tested it KDE was enabled "as is" / at last moment. I am not familiar with KDE much, so I don't know what to enable. I know that there could be issues between Neon and Ubuntu packages, so we kept this minimal. https://github.com/armbian/build/blob/main/config/desktop/noble/environments/kde-neon/config_base/packages Tested boards are moving to /dl Thank you for help.

I don't see it specifically listed, but does Armbian run on the Beaglebone black?

Community support is fine for me, thanks for your job! Are there system packages I shouldn't upgrade with apt to not break OS in my case? Maybe kernel or hardware-specific tools...).

unsupported build environment. As per documentation Noble is supported only. there are a few others "whitelisted" known mostly to work in the scripts, Zena hasn't yet. Check if your user has access to docker (usermod -aG docker yourusername) and check if docker run hello-world runs properly.

Hello, my Cubitruck with Armbian 23.8.1 Bullseye has the false Time and i can't change this. i don't know who is the problem. "date" says me "Mo 9. Feb 19:24:06 CET 2026" but now we have 05:26, when i set date with "sudo date -s "2026-02-09 05:26:00", it looks like it will be override in the next moment, then "date" says sudo date -s "2026-02-09 05:26:00" Mo 9. Feb 05:26:00 CET 2026 root@cubietruck ~ > date Mo 9. Feb 19:26:27 CET 2026 dmesg | grep -i rtc [ 0.000000] Kernel command line: root=UUID=19cf2f1d-1a31-4890-bc04-a2f1c4e4e021 rootwait rootfstype=ext4 console=ttyS0,115200 console=tty1 hdmi.audio=EDID:0 disp.screen0_output_mode=1920x1080p60 panic=10 consoleblank=0 loglevel=1 ubootpart=ba110a34-01 ubootsource=mmc usb-storage.quirks=0x2537:0x1066:u,0x2537:0x1068:u rtc-hctosys=0 sunxi_ve_mem_reserve=0 sunxi_g2d_mem_reserve=0 sunxi_fb_mem_reserve=16 cgroup_enable=memory swapaccount=1 [ 0.000000] Unknown kernel command line parameters "ubootpart=ba110a34-01 ubootsource=mmc rtc-hctosys=0 sunxi_ve_mem_reserve=0 sunxi_g2d_mem_reserve=0 sunxi_fb_mem_reserve=16 cgroup_enable=memory", will be passed to user space. [ 1.553534] sun4i-drm display-engine: [drm] Cannot find any crtc or sizes [ 1.555880] sun4i-drm display-engine: [drm] Cannot find any crtc or sizes [ 1.573650] sunxi-rtc 1c20d00.rtc: registered as rtc0 [ 1.573701] sunxi-rtc 1c20d00.rtc: setting system clock to 2026-02-09T18:15:12 UTC (1770660912) [ 1.755046] axp20x-i2c 1-0034: Backup (RTC) battery charging is enabled [ 2.161281] rtc-hctosys=0 sudo systemctl restart chrony chronyc tracking chronyc sources -v Reference ID : 00000000 () Stratum : 0 Ref time (UTC) : Thu Jan 01 00:00:00 1970 System time : 0.000000000 seconds slow of NTP time Last offset : +0.000000000 seconds RMS offset : 0.000000000 seconds Frequency : 6.181 ppm slow Residual freq : +0.000 ppm Skew : 0.000 ppm Root delay : 1.000000000 seconds Root dispersion : 1.000000000 seconds Update interval : 0.0 seconds Leap status : Not synchronised .-- Source mode '^' = server, '=' = peer, '#' = local clock. / .- Source state '*' = current best, '+' = combined, '-' = not combined, | / 'x' = may be in error, '~' = too variable, '?' = unusable. || .- xxxx [ yyyy ] +/- zzzz || Reachability register (octal) -. | xxxx = adjusted offset, || Log2(Polling interval) --. | | yyyy = measured offset, || \ | | zzzz = estimated error. || | | \ MS Name/IP address Stratum Poll Reach LastRx Last sample =============================================================================== ^? listserver.trexler.at 0 6 0 - +0ns[ +0ns] +/- 0ns ^? time.netzwerge.de 0 6 0 - +0ns[ +0ns] +/- 0ns ^? 2a02:8108:4d82:e400:9677> 0 6 0 - +0ns[ +0ns] +/- 0ns ^? static.179.181.75.5.clie> 0 6 0 - +0ns[ +0ns] +/- 0ns ^? 2a09:e1c1:efc4:1337::123 0 6 0 - +0ns[ +0ns] +/- 0ns ^? 2a01:7e01::f03c:94ff:fee> 2 6 1 0 +50282s[+50282s] +/- 27ms ^? nobody.yourvserver.net 0 6 0 - +0ns[ +0ns] +/- 0ns ^? ctb01.martinmoerch.dk 0 6 0 - +0ns[ +0ns] +/- 0ns ^? fritz.box 0 6 0 - +0ns[ +0ns] +/- 0ns What can be the problem and how can i fix it. Thank you

After digging into more details, I think Armbian has moved to use new U-Boot generated FIT image u-boot-rockchip-spi.bin for SPI boot, however, it doesn't work to boot NVMe rootfs and sometimes breaks the board and I have to erase SPI to get SD card booting. Couldn't find more information how Armbian does MTD boot now. Note that older vendor SPI bootloader can boot kernel 6.18.8 but I ran into other issue like freezing system for a couple of minutes so that I'd say to avoid use old MTD image with 26.2 6.18 kernel.

Have you tried the install instructions and build from here: https://www.armbian.com/amlogic-s9xx-tv-box/

On my Gentoo setup, I never had any USB issues before 6.6, even without the usbcore.autosuspend=-1 option. With 6.6, though, USB doesn’t work for me even with that option enabled. The fix from all2 worked for me, so thanks to that I put together what I think is a slightly more robust solution:

Hello everyone, good day. I have a problem and I want to share it with you, maybe we can find a solution. I have a Next MyBox Android box, model H313, with 2GB of RAM (I don't know the LDDR3 type, but I think it's LDDR3). I want to install Armbian on this device via an SD card, but I have a problem: the eMMC flash memory was faulty and causing a short circuit. I removed and cleaned it, but now when I try to install Armbian like X96Q with the SD card, I can't see a display or an IP address on my router. There's no HDMI display either. If you have any information about this, could you please share it?

@GBEM yes the service file can be improved, also it might be worth it to blacklist some unuseful module like: sudo nano /etc/modprobe.d/blacklist.conf # Add: blacklist btusb blacklist btrtl blacklist btbcm blacklist btintel

UPDATE for Multitool Finally I managed to let the Opensource OP-TEE work with the rockchip miniloader! This means that the Multitool should now work on any board, without freezes and booting issues! The new version can be downloaded from the first page of this thread. Please report if it works for you, thanks!

@jock Hi, I have updated the build source for the leds overlay files (leds 6 and 7) for both the the rockchip64 H50 tvbox and the T9 tvbox, for kernels 6.12 (old non scrolling driver) and 6.18 (new scrolling driver) the version for 6.18 is also fine for 6.19. Have a look at my fork in https://github.com/gpaesano/build. Some modifications are just refinements other are functional. I have built all the images and variants on a ubuntu linux and are running well. I am not familiar with pull requests and do not want to be impolite, so If you think there is some added value please support it. All the best @GmP

If anyone is still interested, I have a Helios 64 that I assembled, looked at, but never got around to using for more than a couple hours. Works fine, does not yet have the 2.5GB fix but I have the instructions for same. No idea what to ask for it but it certainly isn't doing me any good sitting on my shelf. Have the manual, SATA drive bay adapters for 2.5" drives and the like. Make me an offer and pay shipping from Oregon. Let's talk!

https://github.com/armbian/community/releases/download/26.2.0-trunk.385/Armbian_community_26.2.0-trunk.385_Rk3318-box_trixie_current_6.18.8_minimal.img.xz this is the latest console build compatible with T9. You will need to configure a little bit the environment after booting to enable all the features via ssh and wired lan. If the device is still on android the best is to follow the tutorial from @jock in

Thank you. I couldn't even think of such a thing. Lord, why is it necessary to preserve the state of indicators that are needed precisely to show the state of something?

@Nick A No problem. Thanks for your Armbian build as well! I am also looking forward to mainline. Currently I still didn't find open source Mesa driver for Allwinner BSP, GLES is only available as pre-compiled binary for Debian (haven't tested it but it's in the Radxa images). There already are mainline Mesa/Linux IMG GPU supports so I hope things can be ported to mainline soon. Please let me know if anyone finds the source code for Mesa BSP.

All things are possible. The question is who's interested in doing (or funding) the work, and if technical data is available to do it. The build system is at https://github.com/armbian/build. If you know how to build a kernel, device tree, and bootloader, you can define how to do those steps there.