All Activity

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

There is probs away to pull in those apt sources from Bianbu, but I haven't messed with it yet. Types: deb URIs: http://archive.spacemit.com/bianbu/ Suites: noble/snapshots/v2.2 noble-security/snapshots/v2.2 noble-porting/snapshots/v2.2 noble-customization/snapshots/v2.2 noble-updates/snapshots/v2.2 bianbu-v2.2-updates Components: main universe restricted multiverse Signed-By: /usr/share/keyrings/bianbu-archive-keyring.gpg Would need to go on gitee or mount one of their imgs and get that *-keyring.gpg

so i am testing your edge build of 6.18 kernel and it works great. but one of the things i would like to do is to enable the intel and amd graphics drivers for testing(ive got an external intel gpu on the nvme slot). on normal debian i just download the kernel do a make menuconfig and specify, im new to armbian and see it uses a compile.sh script. i didnt see a branch on your github for the edge kernel, just saw rv2 and rv2-ky. so im kind of curious as to where i clone from to get your edge kernel branch.

Yes, I more or less thought about that orangepi.org Ubuntu from their downloads. At least this Ubuntu image shows some OpenGL capabilities with the preinstalled glmark2. I also tried that "Bianbu" image from Spacemit with my kernel, but that Gnome3/Wayland is slower than a slug probably because in case you want to play with that: I've uploaded that image to https://privat-in.de as a playground, root password is "bianbu" and you may need to resize the root partition to your SD card or so. Also I've overlooked that there is a "bianbu 3.0.1" so this is 3.0

@Nick A Wi-fi chip is SV6256P

Thank you for such a detailed answer! I'll try to explain a little why I need this. I use OpiRV2 not only as a server for my applications (and, in a sense, for testing some add-ons for automating my home), but also to use OpiRV2 to install Kodi for viewing my home server tvheadend (as they say, to use 2 in 1 to the fullest). But this is impossible without hardware video decoding. I use Kodi without running the Mate and XFCE desktops - because from experience, to use hardware video decoding, you need to run Kodi with the /usr/bin/kodi-standalone --windowing=gbm parameter on single-board motherboards. This works fine on OpiZero3, etc., but here it's a pain in the ass 🙂 Even SD video is completely slow because software codecs are used. I understand that you don't need this and are not interested in it, so I'll just say - thank you for the great work you've done. PS: Regarding Ubuntu-Noble, which can be downloaded from Xunlong - which image are you talking about? If it's from here - http://www.orangepi.org/html/hardWare/computerAndMicrocontrollers/service-and-support/Orange-Pi-RV2.html , then it's terrible - nothing works there, including HDMI audio.

Hello @Malay, et.al, the motivation behind my attempt to include Armbian support for OpiRV2 is to have a better device for my Nextcloud-for-private-persons project. For this, I need a device that can be run at home with a current kernel and headless, but with decent storage. I already have a device (Orange Pi Zero 3, right on the photo), but Orange Pi RV2 (to the left) offers two(!) m.2 slots for NVMEs, some Wifi and Eth as well as decent computing power. Also, both have some extra NOR flash to store LUKS keys and decent pricing. Also that RiscV64 has some appeal, admitted 😉 Without GPU support, you can run Mate, LXDE, and XFCE for a GUI, which should be OK for some management tasks. I doubt that RV2 will ever make a good Youtube player, however that may be archived by replacing the Armbian userspace with that Ubuntu-Noble userspace that you can download from Xunlong. This Ubunut also comes with a RiscV64 port of Chromium which is also needed for Youtube and not avail from Debian, but source code *.dsc seems to be offered in the Bianbu pool so that may work out. Anyhow - that GPU porting attempt was based on the PowerVR addons offered as code drop on git@gitee.com:spacemit-buildroot/mesa3d.git. Our Chinese friends grabbed mesa 22.3.5, added their IMG BXE-2-32 this+that to the sources, cherry-picked their way up to mesa 24.0.1 and throw the result over the fence. At least without inking the code via Windows notepad, so no white-space chaos this time. Now, porting this with the closed binary *.so as heavy baggage is all about stable API. Large internal API change -> end of party. I am no graphics specialist, so take this with a pinch of salt. Debian offers mesa since 24.3 with an additional package: mesa-libgallium, you need this for the GPU desktops (Cinnamon, and probably Gnome / KDE). OK - someone or something needs the API from the Mesa internal Gallium driver suite, this needs to be compiled (a *.a is there). So I started to bring that code drop from 24.0 to 24.3, only to stumble over internal API changes. Concrete: we previously have some numeric constants __DRI_IMAGE_COMPONENTS_this+that 0xabcde in Mesa describing image formats (RGB32, BGRA24, 656-16, and so on). The code drop adds a couple of formats probably specific for PowerVR, but the Mesa project completely removed those constants ("nobody uses this"). At that point I thought: this is pointless, I'll pass... HTH // Sven-Ola

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

Hello @sven-ola ! It's sad. I had a small hope 🙂 But still, thank you very, very much for your work on the firmware! After removing sudo rm -r cache/ output/ -f and adding the command SKIP_ARMBIAN_REPO=yes - WiFi now works

No works， UART output null. I think that UART is disabld by OEM. because a working tvbox , UART also output is null

thanks a lot, I will try it soon

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/

I just upgraded my Linux Mint from 22.2 to 22.3 "Zena" ... CLEAN INSTALL, with "git" installed I started a typical armbian build folder, as per: https://github.com/armbian/build?tab=readme-ov-file#quick-start But then I got this error: [🌱] Build host OS release [ zena ] [🌱] Build host architecture [ amd64 ] [💥] error! [ Unsupported build system: 'zena' ] I know that Mint 22.3 was released just last month, but I needed something in the new Linux kernel. I can use Mint 22.2 in another computer (where armbian is working OK)... but what is the typical delay for a new Linux Mint to become supported? Then I tried with $ sudo apt install docker.io , and got a little further: $ ./compile.sh [🚸] Docker is installed, but not usable [ can't use Docker; check your Docker config / groups / etc ] [💥] Problem detected [ Docker installed but not usable ] [💥] Exiting in 10 seconds [ Press <Ctrl-C> to abort, <Enter> to ignore and continue ] Counting down: 9... 8... 7... 6... 5... 4... 3... 2... 1... 0... [💥] error! [ Exiting due to 'Docker installed but not usable' ] [💥] Exiting with error 43 [ at /home/roberto/armbian-2026-feb/build/lib/functions/logging/traps.sh:1 exit_with_error() --> lib/functions/logging/traps.sh:1 exit_if_countdown_not_aborted() --> lib/functions/general/countdown.sh:41 cli_standard_relaunch_docker_or_sudo() --> lib/functions/cli/utils-cli.sh:261 cli_standard_build_pre_run() --> lib/functions/cli/cli-build.sh:14 armbian_cli_pre_run_command() --> lib/functions/cli/utils-cli.sh:122 cli_entrypoint() --> lib/functions/cli/entrypoint.sh:79 main() --> ./compile.sh:50 More info: my docker is version 28.2.2 $ apt list docker.io Listing... Done docker.io/noble-updates,now 28.2.2-0ubuntu1~24.04.1 amd64 [installed] docker v17.6 needed. Reference: https://docs.armbian.com/Developer-Guide_Building-with-Docker/

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:

@zcrselfhttps://github.com/NickAlilovic/build/releases/tag/Mainline try this image.

Armbian supports boards, not bare SoCs. This thread is about xt-q8l-v10 rk3288 board, which is supported by community and not officially. If you want official support, prefer a SBC which is declared as officially supported, like the Asus Tinkerboard. Community supported boards are "best effort", officially supported boards are usually checked before new armbian releases to maintain general support and functionality.

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

Hello everyone, I have a device from this brand. An ISP in Turkey distributes this device. It needs to be unlocked. I want to install Armbian on it. However, it doesn’t look like any device I’ve seen online. The motherboard is different from all the devices I checked. Is there anyone who can help me? I can access the device via ADB. I can install APK files. The device has an S905X processor and 1 GB of RAM. It is running Android 9.

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!