All Activity

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

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

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.