All Activity

@Hqnicolas would it be possible to have the driver @guenter pointed out in the base image?

I think the core problem is that headers were compiled with Ubuntu compiler / userspace and you try to use it on Debian. I used this on Ubuntu, which is the reason why it worked. We are aware of this problem - headers should be distro specific. Which adds complexity on our side ...

Feel free to pr any missing overlay here: https://github.com/armbian/linux-rockchip

moved to csc https://docs.armbian.com/User-Guide_FAQ/#why-no-universal-image tl;dr: You are using the wrong image. Get/build one for your board

It works, but I found that the i2c dtbo file I needed was not in the armbian repository, so I manually extracted it from the radxa official image.

Armbian 25.8.1 Noble Gnome (Kernel: 6.1.115) + libMali (https://github.com/ginkage/libmali-rockchip) + box64 3.7 (https://ryanfortner.github.io/box64-debs/) + wine-9.22-staging-tkg-amd64-wow64 (https://github.com/Kron4ek/Wine-Builds/releases/tag/9.22) + DXVK-Sarek v1.11.1 - Mali GPU Fix by Ayman-Zeyada (https://github.com/Ayman-Zeyada/DXVK-Sarek/releases/tag/v1.11.1-mali-fix) ~60fps@1080p HK: SilkSong

What? Sharing various gaming experiences with RK3588 (Orange Pi 5) on Armbian. Why? Because RK3588 is a capable gaming chipset, Armbian is a good OS; Vulkan on RK3588 is getting better over time (PanVk) How? Posting your gaming results here (preferably with setup and screenshots/videos) so people can learn more.

We already did that. I think the problem is that our keys are not packed (yet) but added at build time. When a person upgrades from Bookworm to Trixie, this will show up, while on new Trixie images this shouldn't manifest. @zital debian Is this the case? https://github.com/armbian/configng/commit/5d866b9b105bfd46cb341c21c70ba76e32e1fea2 We are signing with old and new key (which is aligned with current standards) since then.

Hi everyone, I recently got an ESP-WROOM-32 Development Board to use as a companion board for my Armbian SBC setup. My goal is to have the ESP32 collect sensor data and send it to the Armbian host over serial or WiFi. It works okay at first, but after a while running a Python script, the ESP32 crashes or stops sending data. Setup Details: Armbian running on a Banana Pi (or similar SBC) ESP-WROOM-32 connected over serial (USB-to-TTL) and also configured via WiFi Python script (on the Armbian side) reads from the serial port / receives via a simple socket over WiFi Power supply is stable; using 3.3 V TTL logic on ESP and stable USB power Now here are my issues: Script runs fine for some minutes (5–10), then suddenly no data from ESP3. ESP32 sometimes reboots (observed via onboard LED), sometimes appears alive but unresponsive. Logs show no obvious error messages; serial just quiet or times out I've tried lowering the serial baud rate. Added delays / sleeps in code to reduce data flood. Ensured the USB-power to ESP32 is stable / using good cable. Tried Py serial and different socket listener scripts Could USB-TTL or serial USB drivers under Armbian be causing issues (overheating, buffer overflows)? Would switching fully to WiFi (TCP/UDP) instead of serial help stability? Any tools or logging tips on Armbian to catch the crash (kernel logs, serial trace, etc.)? Thanks in advance for any advice. Jordan

I don't see it as the very latest bleeding edge kernel version. I see it as a newish Linux, which already has the armbian patches updated for. Some CPUs end up with newer or older Linux versions, due to varying levels of development success. For example, sunxi's armbian edge is 6.15.4 today, but the linux trunk is up to 6.17-rc6 ... (not available in Armbian)

I tried it on 6.16.7, and the log started working: [ 4.838111] rockchip-drm display-subsystem: [drm] fb0: rockchipdrmfb frame buffer device Error again after initialization: [ 5.118148] rockchip-drm display-subsystem: [drm] Cannot find any crtc or sizes [ 5.637839] rockchip-drm display-subsystem: [drm] Cannot find any crtc or sizes

I have an Orangepi5 ultra RK5388. I have tried the following versions of Armbian13. It doesn't recognize my USBs so I don't have a keyboard. vendor: https://armbian.systemonachip.net/dl/orangepi5-plus/archive/Armbian_25.8.1_Orangepi5-plus_trixie_vendor_6.1.115_minimal.img.xz.sha This one won't start ,current: https://armbian.systemonachip.net/dl/orangepi5-plus/archive/Armbian_25.8.1_Orangepi5-plus_trixie_current_6.12.43_minimal.img.xz There is also no reference to Debian13 in any repository on the Orangepi website.

Has anyone ever gotten the Radxa Zero 3w working in gadget mode? I bought a Zero 3w about a week ago and have been beating this horse most of the time. I can't get the device to connect via USB. A or C. When I try to connect (radxa.local) it will always go through wifi. If I have wlan0 disabled or even my internet off it just will NOT connect. It clearly is using wifi to connect even if I use the hostname. Maybe this is something simple but I and another engineer I work with have been scratching our heads about it. The obligatory AI search was an endless loop of everything we had already tried. Anybody have any advice?

@hexdump hey mate , do you know if new armbian image still uses an offset of 8192 sector ? i'm trying the workaround you proveded in first page for linux hanging excatly after 60 seconds , but it only worked with multitool.img . with new armbian images it doesn't even boot after applying the trick 🙁 thanks

What type of monitor do you have connected? If you have another monitor, I'd try that. What I find works best is a monitor that is native 1920x1080. I sometimes have issues with monitors that are higher resolution or lower resolution than a standard 1080P display. Otherwise finding the uart pads is the only other advice I have, so that you can see what is going on during the boot.

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.

Thanks for the background information. I installed the orange pi 5 - 6.1.115 release with XFCE desktop. I edited the armbianEnv.txt to set up the pointer to the orange pi pro dtb entry. and booted it up just fine. With this, most things work well, To run the OS on the nvme M.2 drive, you cannot boot up from the nvme m.2 drive. Through some mistake that was made by the designers, you must always boot from an SD card for the initramfs to work enough to find the nvme m.2 drive. I made a copy - of the SD card to a second SD card on a separate system. Used this SD card to restart the Orange Pi 5 pro. Then changed the UUID of the /dev/nvme0n1p1 partition. (tune2fs -U) updated the armbianEnv.txt file on the boot SD card and the nvme0n1p1 drive. and rebooted - Now root is mounted to /dev/nvme0n1p1 partition. I have to leave the SD card in the slot to boot the system. but I am running off the NVME drive - Gen3 x 4 which should run at roughly 800-1000 MB/s on average according to Tom's hardware. That is probably 10x most SD cards transfer rate. Bottom line - I have a working Orange Pi 5 pro running on an NVMe M.2 drive - with the ability to get 10x throughput over using an SD card and up to 8TB of storage . Now it wasn't simple to actually set it up. It took some research and a learning curve. So I am not too happy about the lack of upfront information about getting this to work. But it is working. I had tried too build a real time kernel for this system. I did rebuild a kernel, but when I set the RT config up - I didn't have list of configuration question answers ready - Needed more information. The general idea was to get a fast multicore system with huge storage capacity and use this to run robotic systems. I am missing the real time kernel, I will run some latency tests to check the worst case jitter and look for a config setup. I see that there is now a Raspberry Pi 4 and Raspberry P5 real time kernel on a debian 12 release. I will see if I can get any build information for the real time kernel build. Thanks for the feedback. I will start looking for a different sbc model - among the platinum supported group.

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

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

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.

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 🤜🤛