All Activity

Update: I managed to brick my box to a dead Android screen. Then got it upgraded to Android 7.1.1 cause I finally found an image. Booted armbian and it gets all the way to log in screen using the meson-gxm-s912-mecool-bb2-pro.dtb but it doesn't detect anything on the USB ports with a "debounce" error on both of them and seems that the nic is up but I don't see the box in my DHCP server. Any advice is greatly appreciated Best regards

May be worth looking into armbian-install script? Just a thought.

Instructions to build mpv, for anyone trying it with trixie... I don't see any pre-compilation options related to v4l2request https://forums.raspberrypi.com/viewtopic.php?t=360902#p2172777 https://github.com/mpv-player/mpv-build https://www.youtube.com/watch?v=KdyX3k8vOhw

From my tests, ffmpeg works fine with hardware acceleration under Debian Trixie, but packaged mpv (AFAIR it is v0.4.0) does always fails hardware decoding.

Hello again I have recreated /var/log/nginx and also /var/spool/postfix as it wasn't also not copied and postfix@-.service didn't start. Now I see that /srv does not get populated with the mount points of disks by-uuid... Excuse me if I repeat my question: what gets copied over with armbian-install? Just to have a list of what I have to recreate. Thank you.

Has anybody had success with ffmpeg-v4l2request under Debian TRIXIE? I have seen successful reports from Jammy and Noble users... are they still having success?

No one has ever submitted this for inclusion in Armbian. This is a community supported board. If anyone were to submit this as a PR it would almost certainly be included as the approval process for community supported boards is a low bar, basically that it doesn't break the build.

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