All Activity

Googling suggests the need for Armbian to re-issue their signing keys. Note, I don't think this means they have to generate a new one. Just re-sign it. https://www.redhat.com/en/blog/updating-gpg-keys-for-fedora-and-rhel https://github.com/fwupd/fwupd/issues/7124 @Igor

@GBEM I'm running: _ _ _ __ __ _ _ _ /_\ _ _ _ __ | |__(_)__ _ _ _ ___ _ _ _ _ ___ / _|/ _(_)__(_)__ _| | / _ \| '_| ' \| '_ \ / _` | ' \___| || | ' \/ _ \ _| _| / _| / _` | | /_/ \_\_| |_|_|_|_.__/_\__,_|_||_| \_,_|_||_\___/_| |_| |_\__|_\__,_|_| v25.8.1 for h96-tvbox-3566 running Armbian Linux 6.12.44-current-rockchip64 Packages: Debian stable (bookworm), possible distro upgrade (trixie) Support: DIY (community maintained) IPv4: SNIPP Performance: Load: 2% Uptime: 8 days 8:01 Memory usage: 3% of 7.50G CPU temp: 38°C Usage of /: 12% of 57G Commands: Configuration : armbian-config Monitoring : htop Last login: Mon Sep 15 15:59:34 2025 from 192.168.1.48 I can switch the blue leds with: root@tvbox:/home/gt# echo 0 >/sys/class/leds/led-power/brightness root@tvbox:/home/gt# echo 1 >/sys/class/leds/led-power/brightness as root. sudo didn't work. I used the project: gt@tvbox:~/tm16xx-display$ git config --get remote.origin.url https://github.com/jefflessard/tm16xx-display.git I created a dtbo which is loaded during boot: gt@tvbox:~/tm16xx-display$ cat /boot/armbianEnv.txt ...... user_overlays=tm16xx ..... The mentioned project provides a service which updates the front display with the time.

Tried for several days to get this working with the latest kernel and headers (never got it working and always got the same linkonce error). So I just abandoned the idea of Armbian for x86 and installed Debian which did work, perhaps when the Motorcomm YT6801 driver hits mainline I'll give it another try.

I've tried a reboot by disabling the overlay line in armbianEnv.txt and I've got one of my 2 LEDs back. It seems that ledconf-3 is no longer working for me. @jock If you have some time to check it out, that would be great... Thanks again.

Hi all and especially @jock I'm back, I restarted my old MX10 box, on the latest version RK3318-box with rk3318-box.dtb and ledconf-3 as I did before, the box starts well but I have some error messages in my dmesg, and moreover I lost control of the LEDs of the box... Probably a small modification to be made in the .dtb file. https://paste.armbian.com/ibiricarek 🤜🤛

Visit us at the STMicroelectronics booth, where Collabora will highlight how the STM32MP2 chip empowers edge AI solutions for industrial applications. View the full article

current isn't ideal for any rk3588 hw anyway due to lack of hw features mainlined for now. edge or vendor working best.

Let's say the world has been extra certain to bring me IRL problems 😄, as far as a bootloader being present, the Libre Computer Tritium boards are as barebones as can be possible, so any issues should be shared across any/all other H5 boards and really not board specific.

@Dominik Wójt Hey, I've picked up my mxq box again looking to put a newer OS on it. It seems the image you provided works with HDMI. Thanks! However, if I build it from the normal armbian repo it does not work. Any chance you can share what changes you made?

after struggling to make keyboard in french as locale is not taken account sudo dpkg-reconfigure locales sudo dpkg-reconfigure keyboard-configuration sudo systemmctl restart console-setup.service setupcon <-- winner Screenshot taken with screengrab , How am I supposed to live without you screengrab the music..

I loose the HDMI signal and screen get black because startx (main launcher script to enter Xorg!) from xinit package has been forgotten to be installed. After doing the magic combination CTRL+ALT+F1/F2 and login in console mode, this will fix the issue and open the gates of cinnamon sudo apt install xinit Enjoy , SoSie

I'll provide some background on what you are experiencing. 6.1 is the vendor kernel. This is what comes from rockchip and is a hacked together set of code that they release to board builders. Armbian doesn't have really any interest in maintaining this code base. 6.12 is mainline Linux directly from kernel.org with some additional.patches applied. It often tales years for the open source community to get new CPU variants incorporated into the mainline kernel code base, as the vendors (rockchip and OrangePi in this case) don't generally contribute. So 6.12 is actually far behind in feature support for your board. The edge kernel, 6 16 would be better. But if you want a feature complete kernel.for your board, the 6.1 vendor kernel is best. If you want security updates but can deal with lack of some features, then the edge kernel should be your choice (at least until early next year when Armbian current moves to the next Linux LTS release). Also, from the perspective of best boards under Armbian, you probably are better off with Armbian supported boards, not a community supported board which by definition doesn't have anyone maintaining it. Final note, is that Orange Pi as a company does nothing to support the open source community. I'd say their main goal is to pump out new hardware as fast as possible and not supporting older hardware in any way to force people to spend more money with them. In general support and software is a huge cost and doesn't provide any profit for them, so they choose not to provide it.

Please forgive my ignorance, I haven't been back here for some time. Did anyone ever work-out how to control the blue enclosure illumination, and front panel display for this device? I would be very grateful for code snippets, or and suggestions on how to approach investigating the above. I spoke to HSTC. They didn't speak back, so beyond this plea, I'm not feeling optimistic. Thanks, M.

Same. But once you're in, you can run armbian-config and switch to the edge kernel. It'll work better. Just don't switch to the "current" kernel. 6.1 = Vendor Kernel 6.12 = Current Kernel 6.16 = Edge Kernel

I am downloading three different builds from 6.12 for orange pi 5. I have an orange pi 5 pro but since there is not dtb entry in 6.12 for that sbc in the Armbian 25.8.1 6.12.28 dtb file I used the orange pi 5b.dtb entry which works with the Armbian 25.8.1 6.1.115 images. The result is that the initramfs cant find a root disk - and when checking for drives in initramfs - there are none ls /dev/disks/by-uuid. So the initramfs file isn't running correctly as its not finding drives. I went back and loaded Armbian_24.8.1_Rock-5c-trixid_current_6.12.42_minimal.image and that boots up to root login. However if I change the card type to orangepi-5b. I cannot boot - in exactly the same manner - no drives found by initramfs. I have decided to go back to Armbian_25.8.1_Orangepi5-trixie_vendor_6.1.115_xfce_desktop.img - flash that and change the armbianEnv.txt to use the orangepi-5-pro setting. At 6.1.115, the image dtb/rockchip directory still has an entry for the orangepi-5-pro. - the new one doesn't. I am curious if I am just out of luck getting updates for orange pi 5 pro? will orange pi 5b be supported in the future? I have working images for debian 13 - and 6.1.115 versions, so my orange pi 5 is useable as is. I bought this sbc as I could get a useable NVME M.2 drive. I see that all new Orange pi sbc's are using the RK3588 chipset not the RK3588s variant. Opinions - there are new Orange Pi 5 variants - Ultra, Max, Plus etc. I dont need tons of HDMI, I want an NVME M.2 slot or two to run the OS on fast drives. -Or should I abandon Orange Pi and look elsewhere.

Hi. The same problem. Works only Armbian Linux v6.1 =(

Hi everyone, I was experience some strange things with two similar devices, the first I installed in february this year, mesa v.24.x and EGL 1.4 and it was working fine The other one I installed this week and it turns out that it uses mesa v.25.x and EGL 1.5, although performance was great with most 3D apps (like glmark2) I had poor performance under sway/kitty or the retroarch menu for instance (something like 15 fps). It took me a few days to find a solution so if you have similar issues please try installing mesa with the kisak repository as it fixed my problems sudo add-apt-repository ppa:kisak/kisak-mesa -y sudo apt update sudo apt upgrade the last command should upgrade mesa to a more recent version than what's in the ubuntu ppa.

Hi, you need the radxa dedicated tool to do it : https://opensource.rock-chips.com/wiki_Rkdeveloptool Once it is compiled and installed, you need to start the device in "maskrom mode", to do that, push the maskrom button located under the board near the hdmi output then power the device while holding the button. The led should turn and stays on. To check if the device is ready, run the following command : rkdeveloptool ld it should print something like that : DevNo=1 Vid=0x2207,Pid=0x350a,LocationID=302 Maskrom it means the device is ready to receive data then you need to upload the bootloader : sudo rkdeveloptool db rk356x_spl_loader_ddr1056_v1.12.109_no_check_todly.bin and finally you can upload the armbian img : sudo rkdeveloptool wl 0 Armbian-XXX.img make sure your device is properly cooled before doing those operations because heat can freeze the process. you can find the loader and more info here : https://docs.radxa.com/en/zero/zero3/low-level-dev/rkdeveloptool there's a windows version of rkdeveloptool too you can find on their website.

That should work for me. Thanks to everyone, who have participated.

before: Orange Pi Zero (H+), CPU: Allwinner H3 (SUN8I 1680) Model: Xunlong Orange Pi Zero DRAM: 512 MiB TF card is Samsung Evo Plus 64GB; After writing the TF card with Win32DiskImager, the same issue occurred: normal boot-up and shutdown, but when executing a reboot, it gets stuck at the final stage of service termination before restarting. ...... [ OK ] Reached target shutdown.target - System Shutdown. [ OK ] Deactivated swap dev-zram0.swap - /dev/zram0. [ OK ] Reached target umount.target - Unmount All Filesystems. [ OK ] Reached target final.target - Late Shutdown Services. [ OK ] Finished systemd-reboot.service - System Reboot. [ OK ] Reached target reboot.target - System Reboot. [44967.125952] systemd-shutdown[1]: Failed to set timeout to 10min: Invalid argument systemd-shutdown[1]: Failed to set timeout to 10min: Invalid argument [44967.761002] reboot: Restarting system This is where it starts to lose responsiveness! after: Following someone's guidance, I was told to install or update u-boot: run armbian-install, then selected “Install/Update the bootloader on SD card (/dev/mmcblk0)”. After the update completed, needed to shut down the system and disconnect the power (the first time I performed a reboot here, but it got stuck again at the final stage of stopping services before restarting, just like before). so I had to disconnect the power, then plug it back in for an automatic boot-up. After that, performing a reboot worked normally without getting stuck). ...... [ OK ] Reached target shutdown.target - System Shutdown. [ OK ] Deactivated swap dev-zram0.swap - /dev/zram0. [ OK ] Reached target umount.target - Unmount All Filesystems. [ OK ] Reached target final.target - Late Shutdown Services. [ OK ] Finished systemd-reboot.service - System Reboot. [ OK ] Reached target reboot.target - System Reboot. [44967.125952] systemd-shutdown[1]: Failed to set timeout to 10min: Invalid argument systemd-shutdown[1]: Failed to set timeout to 10min: Invalid argument [44967.761002] reboot: Restarting system U-Boot SPL 2024.01-armbian-2024.01-S866c-P7738-Ha5c2-Vd711-Bb703-R448a (Aug 16 2025 - 02:09:48 +0000) DRAM: 512 MiB Trying to boot from MMC1 ns16550_serial serial@1c28000: pinctrl_select_state_full: uclass_get_device_by_phandle_id: err=-19 U-Boot 2024.01-armbian-2024.01-S866c-P7738-Ha5c2-Vd711-Bb703-R448a (Aug 16 2025 - 02:09:48 +0000) Allwinner Technology CPU: Allwinner H3 (SUN8I 1680) Model: Xunlong Orange Pi Zero DRAM: 512 MiB Core: 69 devices, 18 uclasses, devicetree: separate WDT: Not starting watchdog@1c20ca0 MMC: mmc@1c0f000: 0, mmc@1c10000: 1 Loading Environment from FAT... Unable to use mmc 0:1... In: serial,usbkbd Out: serial Err: serial Net: eth0: ethernet@1c30000 starting USB... Bus usb@1c1a000: sun4i_usb_phy phy@1c19400: External vbus detected, not enabling our own vbus USB EHCI 1.00 ...... You can see that immediately after the log entry "[44967.761002] reboot: Restarting system", the system begins booting.

Hello @Going, I mean If uboot is available on a sdcard plugged in, it will boot on it else on emmc, Sometimes when UUID are the same, it is the last device discovered that overlaps. Wehen cloning emmc UUID back to sdcard do'nt change. My mind was to have a multiboot like refind or ventoy that helps if a system crashed. having a failsafe system aside to fix it graphically can be a must. Changing /boot/boot.cmd that affect u-boot may do the work

Apologies for being late to the party, and please excuse me for commenting on something which may already have been fixed. What is the difference between enabling the flag, and allowing whatever apps to work if they can, and disabling it so they certainly can't work? Seems to me that enabling it would make most sense, since H3 SOCs support it.

Thank you all for your input. And a big thank to @djurny I will double check if end user can add static route on their Windows machine or whatever PC1 is. route add 10.10.10.2 mask 255.255.255.255 192.168.100.101 As this solution appears to work. Alternative way is bridging the NICs however Device1 requires separate subnet from NIC1.... Thank you again.

Summary Update: A Look At Pure Ubuntu (no Armbian) --> The bug was there, then it was not! Initial Observation: Debian 13 (Trixie) The Bug Is Present Operating System: Debian GNU/Linux 13 KDE Plasma Version: 6.3.6 KDE Frameworks Version: 6.13.0 Qt Version: 6.8.2 Kernel Version: 6.16.4-edge-rockchip64 (64-bit) Graphics Platform: Wayland Ubuntu 25.04 The Bug Is Present Distributor ID: Ubuntu Description: Ubuntu 25.04 Release: 25.04 Codename: plucky Operating System: Ubuntu 12 KDE Plasma Version: 6.3.4 KDE Frameworks Version: 6.12.0 Qt Version: 6.8.3 Kernel Version: 6.16.0-17-generic (64-bit) Graphics Platform: Wayland Ubuntu 25.10 The Bug Is Gone! Distributor ID: Ubuntu Description: Ubuntu Questing Quokka (development branch) Release: 25.10 Codename: questing Operating System: Ubuntu 13 KDE Plasma Version: 6.4.5 KDE Frameworks Version: 6.17.0 Qt Version: 6.8.3 Kernel Version: 6.16.0-17-generic (64-bit) Graphics Platform: Wayland Conclusion The bug was in Ubuntu. Then it wasn't. So the answers to how to fix it are likely in the changes made in or by Ubuntu.

I have a question regarding the configuration of the /etc/asound.conf file... are there any changes in the new kernel that prevent this from happening? I've noticed that my USB audio card no longer loses its settings and its position doesn't change. However, to be sure, I tried editing the /etc/asound.conf file... but it turns out to be impossible 🙂 That is, after saving the settings in /etc/asound.conf... ALSA doesn't work! 🙂 Moreover, the blocking for certain selected devices doesn't work either. In my case, the blocking is: HDMI Audio... in the file: /etc/modprobe.d/blacklist.conf blacklist sun9i_hdmi_audio blacklist snd_soc_simple_card Are these changes related to the detection/blocking, etc., of block devices in Linux?