Active threads

I was considering rebuilding the initrd image for orange pi 5 as I think there was an issue in what was put on the image file. But now I have an a system settup with 6.1.115 - I should be good.

Awesome, @guenter. I'm debugging a board support layer for the Home Assistant OS, which targets the H96 Max. The fabulous work found in this thread, has been both inspiration and foundation for the port to Buildroot. With your very welcome direction, guenter, I'll have a far more polished result, if I ever get my images to boot. Thanks, so much, one and all, M.

Hello, I am selling a working unit of Kobol Helios64 with the fix done, without drives. Based in Czech Republic, able to send within EU. Please DM me if interested.

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

Hello there, I followed from afar the advancement of the support on TV boxes for a while already, and I happened to stumble uppon a very cheap one on my local market. The specs are the following : -Amlogic S905W -2GB of ram -16GB of EMMC Following are some pictures I took, that shows the bare PCB. I hope that it will help answering questions I have. After looking into many written tutorials on getting armbian to boot on such machine, I have tested all .dtb files that are available, as long as quadruple-checked the u-boot file that needed to be used with that specific chip. I made sure to also press that buttom behind the jack-port before plugging in the board to hopefully boot onto the armbian install. Here are a few things I have observed. On all 3 available DTB files for the s905w, when using the u-boot-s905x-s912 file, none of them got me a picture after the first "splash screen". I have watched the power consumption during the "boot" and have seen the power fluctuating between 1.6 and 2.4W, until it setteled to 1.4W and stopped fluctuating. My very premature conclusion is that it somehow booted armbian but did not give me picture. The display that I am using was also showing that something was powered on, trying to send a picture but was not giving correct signal. Here's where my abilities end off. I do not know where to go next and what to try. I have not seen obvious pads to try connecting to UART, and I need assistance with going forward with that specific board. If anyone with experience can guide me, I'd appreciate it grately! Thank you in advance and hope this message finds the right person PS: The board boots fine to Android 7.1 otherwise, when not trying to boot to the SD card, so the machine is confirmed to be working!

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.

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

TV Box Name: H96 MAX V56 CPU: RockChip RK3566 Armbian build file name: Armbian_community_24.8.0-trunk.6_H96-tvbox-3566_jammy_current_6.6.32_gnome_desktop.img.xz Kernel Version: 6.6.32 Kernel Version: 6.12.6 Distribution Installed (focal, buster, etc): Jammy Working Ethernet (Yes/No): yes Max Ethernet Speed that works (100/1000): 1000 Gigabit Does wifi work (Yes/No): Yes Does bluetooth work (Yes/No): depends on User WorkAround Does HDMI audio work (Yes/No): Yes Additional Comments (provide any additional information you feel is important): No TF-Card Boot and No USB boot all done by Rockchip Hardware flash Topic 4/32gb Topic 8/64gb

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?

Any progress on this?

Yes. This is an example of a rk3588 based board of mine: overlay_prefix=rockchip-rk3588 overlays=panthor-gpu opp-oc-24ghz The overlay names come from /boot/dtb/*/ find an overlay matching your soc and needs and enable by putting its name to overlays=. Then reboot. Having a serial console to read uboot logs can show if it has been loaded properly or in case it did not why.

Well I was able to build by changing the docker image with this option : DOCKER_ARMBIAN_BASE_IMAGE=ubuntu:jammy The two other images (debian:bookworm and ubuntu:noble) simply do not work