All Activity

This is my current uptime, with a running smb, torrent server, and 4 docker containers. It's a shame that the voltage fix never seems to be “officially” adopted. A system hardly needs to be any more stable than this

I am using :- [ Ubuntu 24.04 (Noble)](https://dl.armbian.com/rock-5b-plus/Noble_vendor_server) from :- [Radxa Rock 5B Plus - Armbian](https://www.armbian.com/rock-5b-plus/) Trying to turn fan on on Radxa Rock 5B+ selecting the device using armbian-config actually makes it disappear I am getting `line 3: echo: write error:Device or resource busy`

We're aware

@rpq399 HI! Can you share links to firmware and usb modules and the way to reinstall before the reboot, please?

duplicate

I have tried A lot of ROMs and they do not work. The device is not working now. Please help. Thank you.

I'm also seeing the expired LE Certificate today. I posted my report in the Beginners Section here to get more visibility, but it's waiting for moderator approval.

Firefox Browser screenshot:

Err:6 https://apt.armbian.com noble InRelease Certificate verification failed: The certificate is NOT trusted. The certificate chain uses expired certificate. Could not handshake: Error in the certificate verification. [IP: 152.53.81.238 443]

Let's Encrypt Certificate has expired for apt.armbian.com openssl s_client -connect apt.armbian.com:443 -servername apt.armbian.com < /dev/null 2>&1 | grep -E "(Verify return code|subject|issuer|notBefore|notAfter)" notAfter=Sep 25 23:05:16 2025 GMT notAfter=Sep 25 23:05:16 2025 GMT subject=CN=apt.armbian.com issuer=C=US, O=Let's Encrypt, CN=E6 Verify return code: 10 (certificate has expired)

Not sure if I posted this in the right location, kindly move the thread as necessary. Or please let me know where.

@JaydenWithaWhy Multitool is supposed to resize the partition to the whole size of the media as soon as you run it for the first time on the box. About the "command not found" and black box issues, I'm not aware about. When you see the Terms, you can scroll up and down and Enter key will just proceed to the main menu. Where did you download the software?

Could you please be more explicit or point me to some tutorial? In the readme the only info I can see are how to build U-Boot for s905x in the version I already have, or newer but for different chips s905x2 and s905x3. Thanks again for your help

Hello! I am quite new to using Armbian, and I have been having some trouble trying to boot into Multitool. Before I explain my problem, I will describe what I have been using, which is an RK3328 X88 Pro 10. The image I tried using alongside Multitool was Armbian_23.11.1_RK3328-Box_jammy_current_6.1.63.img. First off the bat, Multitool was only 377 MB, even though the min SD I was using is 117 GB, which I am not sure if that was done on purpose, but I made it more difficult to find an image that fit. Next, when Mulitool booted in, I was greeted with the Terms of Software page, which would only let me scroll up and down. If I try any other keyboard keys (I do not have the remote; it has been lost for years). A black box from the bottom of the screen, opening some kind of terminal, saying "Line 17: command not found" when it opens, all I can do is type like a text editor where hitting enter does not get a response from the software. I don't know what to do at all, so I hope one of you guys could understand the predicament I'm in

If you're still able to boot from microsd (which should be prefered over emmc if Armbian uboot is used) you can chroot into the system on eMMC and downgrade packages, either manually (apt/dpkg) or with armbian-config.

No clue, sorry. Maybe the driver might be optimized to work best with wayland. Maybe there is a fix pending or already merged into newer Linux version.

Addendum: An Easy Way To Bypass Grub's Self-Centric Orientation & Eliminate The Need For OS-Prober 1. Assuming you already have your EFI partition set up, for any OS that's mounting the EFI partition, stop that. In the /etc/fstab file, comment out (with a #) the line where it's mounted (i.e. as /boot/efi/). 2. Install grub on each OS. You can keep the /boot/grub/ directory on the same partition as root. Each installed OS will just update its own grub.cfg whenever it's needed. # If the your OS doesn't have a /boot/efi/ directory, create one. mkdir /boot/efi # Install grub. This will force it to install even though it won't detect a genuine EFI. grub-install --efi-directory /boot/efi --force Remember if you need to disable os-prober (recommended), just comment-out its line in /etc/default/grub. 3. Optional: Eliminate the pesky EFI Firmware menu entry in each OS this way: cd /etc/grub.d mkdir skip.d mv 30_uefi-firmware skip.d/ 4. Update Grub with your current kernels update-grub 5. Create a small partition for grub. 64 MB will suffice. 6. Choose an OS's grub, and copy all files from /boot/grub/ to that small grub partition. 7. On that grub partition, create a new grub.cfg. Here is a sample: set timeout=10 # Load Modules insmod all_video insmod part_gpt insmod ext2 insmod png # Setup Background loadfont unicode terminal_output gfxterm background_image /grub-16x9.png set color_normal=white/black set color_highlight=black/white # Menu Entries menuentry 'Orange PI Bookworm' { search.fs_uuid df078711-12a0-4637-9264-bac72ee25e4c root set prefix=($root)'/boot/grub' configfile $prefix/grub.cfg } menuentry 'Debian Trixie' { search.fs_uuid 1b6add1b-05ac-4568-bf54-1f920a6f8e3e root set prefix=($root)'/boot/grub' configfile $prefix/grub.cfg } menuentry 'Armbian 25.8.1 Bookworm' { search.fs_uuid ecb0ae86-8f5c-477e-bcd0-bc77ee5ebee9 root set prefix=($root)'/boot/grub' configfile $prefix/grub.cfg } menuentry 'Armbian 25.8.1 Trixie' { search.fs_uuid 6f2d1972-8868-4fb2-bde4-e14325ea4d31 root set prefix=($root)'/boot/grub' configfile $prefix/grub.cfg } menuentry 'Armbian 25.8.1 Noble (Ubuntu 24.04)' { search.fs_uuid d974e989-b201-48c6-b74b-f9ab5dfdfdae root set prefix=($root)'/boot/grub' configfile $prefix/grub.cfg } Of course, change the menu entry titles and UUIDs to your own. 8. Copy the background image you'd like to use to your grub partition. On Debian, background images for grub are typically stored some place like this: /usr/share/desktop-base/emerald-theme/grub Note in the sample grub.cfg file, grub-16x9.png is the background image named. If you want to use a .jpg instead of a .png, change the insmod png to insmod jpeg. 9. In your EFI partition, modify the grub.cfg to be as follows: search.fs_uuid 3D53-E216 root set prefix=($root)'/' configfile $prefix/grub.cfg ...changing the UUID to that of your grub partition. Usage Select the OS you want. That will take you to the OS's own grub menu, which will likely show you two options, the main boot option and "Advanced" boot options. If you select an operating system and wish to change your mind, the ESCAPE key will return you to your previous menu. Problems I did this and everything worked well except the Armbian Noble (Ubuntu) entry. I coped Debian Bookworm's grub to my grub partition, and either Ubuntu's grub is buggy or apparently Ubuntu's grub used language in its grub.cfg that Debian's grub didn't like. It boots into Ubuntu automatically, but it doesn't show any boot menu. I set its timeout for 10 seconds, so it sits with a blank screen for 10 seconds before it boots. Update: I replaced the grub files on my grub partition with those from Debian Trixie. Same results with Armbian Noble (Ubuntu).

Thank you for replying so fast, really appreciate it. No factory reset will solve this? Best regards and thanks again

Read the instructions from this site. It will tell you that if you have ever booted another os like coreelec, you will have made your box incompatible with the Armbian build.

Hi everyone, I’m trying to run Armbian on my old Mecool BB2 Pro TV box but I can’t get it to boot at all – the device always goes straight into Android. Device specs: Model: Mecool BB2 Pro CPU: Amlogic S912 (octa-core Cortex-A53) GPU: ARM Mali-T820MP3 RAM: 3GB DDR3 eMMC: 16GB Connectivity: 2× USB, HDMI, AV, SPDIF, Ethernet Gigabit Wi-Fi/Bluetooth: (chip unknown, maybe AP6255) What I tried so far: Burned several Armbian images with Etcher and DD in Linux. Tried both SD card and USB stick. Tested multiple DTBs: gxm_q200_3g, gxm_q201_3g, p212_3g, and some generic ones. Formatted SD card partition as FAT16 as suggested in some guides. Flashed u-boot.bin manually using dd with byte skipping (e.g. bs=1 skip=444 seek=444 conv=fsync). CoreELEC partially boots, so the box can boot from external media. With Armbian, however, it never even attempts to boot – it just goes straight into Android. What I’m looking for: Confirmation if Armbian can run on this device at all. Which DTB (if any) is recommended for this specific model. Any tips for debugging why Armbian is skipped but CoreELEC boots. If anyone has managed to run Armbian on this box, I’d really appreciate your guidance. Thanks in advance!

Hi there, I ran octoprint and klipper on a orangepi zero (not at the same time). Octoprint from docker and klipper I cannot remember. Octoprint ran fine but it did have some issues when the CPU got overloaded with loading a new gcode file while printing for example. If you do things one by one it should be OKish. Btw i ran octoprint in a 512MB version, not on the 256MB one. Groetjes,

So I looked into this, and unfortunately, no dice. I am happy to investigate further, if you so wish, but I'm happy enough with the way it works currently (auto patching the dtb after a kernel update) so am unlikely to go exploring further on my own. To let you know what I did: copied the dtbo to /boot/dtb/amlogic/overlay/meson-gxl-s905w-tx3-mini-openvfd.dtbo Added to /boot/extlinux/extlinux.conf: fdtoverlays /dtb/amlogic/overlay/meson-gxl-s905w-tx3-mini-openvfd.dtbo (I also tried with /boot prepended to the path as well, but same issue) note: I assume FDTOVERLAYS is a typo from the armbianEnv.txt days, so I went with the lowercase as that is standard for extlinux The device would not come up on the network. I plugged in an HDMI monitor and found that it would hang at: ethernet end0: renamed from eth0 Which is.... odd. I suspect one of 2 things: My entry in extlinux.conf is incorrect (entirely plausible, I'm struggling to find documentation, I've just gone on what you've said, and also changed the capitalisation!) U-Boot overlays are applied differently than fdtoverlay in Linux. It’s possible U-Boot leaves something unaligned or adds an unexpected property, and the kernel hits a corner case. I realise that the above is noway near enough information, however, connecting directly to serial is not realistic at this stage, but I can attach a netconsole if needs be, as we are reaching the kernel, and provide further output. Like I say though, I will only do this if you think there is value in it. Whilst my method might not be the preferred way, it does work, at least.

@pochopsp You would need to use the information in that readme and patch and apply it to a newer u-boot (i.e port the patch to a newer u-boot) and build then a newer u-boot than the 2020.07 currently shipped.

Hi @SteeMan thanks for your reply. I'm not sure I understand your suggestion, however, I tried going in /boot/build-u-boot and the instructions (file readme.txt in the very same folder) suggest that the latest available u-boot for my device (s905x) is indeed the one that I already have (2020.07 from march 2023). The newer u-boot are for s905x2 or s905x3

Addendum: How To Include Devicetree Overlays Since Grub does not have devicetree overlay support, we need to merge the desired overlay(s) in with the main devicetree (.dtb) file we're using. Part of the device-tree-compiler package is this command: fdtoverlay An example from Armbian 25.8.1 Trixie running on the Orange Pi 5 Plus, to enable GPU acceleration in the Vendor (6.1) kernel. In sudo: cd /boot/dtb-6.1.115-vendor-rk35xx/rockchip fdtoverlay -i rk3588-orangepi-5-plus.dtb -o rk3588-orangepi-5-plus-panthor.dtb overlay/rockchip-rk3588-panthor-gpu.dtbo Of course, to have that load automatically from grub using the modification above, you'll need to rename (or move) the original .dtb to something else, then rename the one with the -panthor suffix to the original name to take its place.