Active threads

I noticed that the resolution had been changed from 1920x1080 to 1364x768 but when using remote desktop there is no way to change the resolution using the GUI. Is there a terminal command that can do it?

FYI: I managed to fix my eMMC again, I found a working spl_loader bin file to flash with rkdeveloptool. See the following post for details:

To add a datapoint: In the past, I've been succesfully installing to eMMC using `armbian-install` using an Armbian 24.2.1 Jammy image. IIRC I had to change the `ftdfile=` line in `/boot/armbianEnv.txt` (as documented at https://www.armbian.com/orangepi-5/) but it otherwise worked right away. Now recently I have been playing with newer bootloaders and images and kernels (in order to fix an issue where a reboot hangs), and in that process I updated the U-boot on the eMMC, which caused booting from eMMC to fail, and when booting from SD card, I no longer have the eMMC device so I cannot fix this (I think this might be exactly what @sns1081 describes in the first post of this topic). I've been trying to fix this (see this post for details), but on my previous attempt I could not get `rkdeveloptool` to work: it kept giving "Write LBA failed!" errors on on the `wl` command. I suspected this was because I needed the `db` (download bootloader) command first to download and run a bootloader to then handle the `wl` command, but I could not find the right spl_loader file. But with this thread (and in particular this post by @Andrius Vainorius) offered a filename I could google and then found it here: https://dl.radxa.com/rock5/sw/images/loader/rock-5b/release/ With that, at least the db and wl commands work: ❯ sudo ~/bin/rkdeveloptool db ~/Downloads/rk3588_spl_loader_v1.15.113.bin Downloading bootloader succeeded. ❯ sudo ~/bin/rkdeveloptool wl 0 some_img.img Write LBA from file (100%) For this, I cannected USB-C cable to the J11 USB connector in the middle, powered up via the USB-C connector in the corner and pressed the maskrom button on powerup. Note that it did not seem to be necessary to have the rkdeveloptool and the images to write in the same directory, as suggested by others here. Note that the the "some_img.img" is an image I lifted from an SD-card with Armbian 24.2.1 Jammy, so it is not the original clean image, but it does have the same stuff on it. Just the above commands recovered my board: It can boot from eMMC again and the /dev/mmcblk0 eMMC device is available again (both when booting from eMMC and when booting from SD). Analyzing why eMMC was broken before, I compared the serial output from the broken and fixed cases. The main difference is here seems to be the u-boot SPL version. AFAIU, this is what happens: Some ROM bootloader boots, which loads U-boot SPL from eMMC U-boot SPL checks SD-card and then eMMC to load the main U-boot Maybe there is another bootloader stage involved (between ROM and SPL, since there is some serial output before SPL shows up that is different between both cases). Here's a diff of the serial output between both cases (up to the moment where U-boot runs and no more interesting differences appear): --- old-opi5.txt 2025-07-02 21:20:08.631329154 +0200 +++ old-opi5-emmc-fixed.txt 2025-07-02 23:01:17.982196616 +0200 @@ -1,26 +1,24 @@ -üDDR d5483af87d cym 23/11/23-16:15:24,fwver: v1.15 +þDDR V1.11 f1474cf52f cym 23/05/09-11:02:36 LPDDR4X, 2112MHz channel[0] BW=16 Col=10 Bk=8 CS0 Row=16 CS1 Row=16 CS=2 Die BW=16 Size=2048MB channel[1] BW=16 Col=10 Bk=8 CS0 Row=16 CS1 Row=16 CS=2 Die BW=16 Size=2048MB channel[2] BW=16 Col=10 Bk=8 CS0 Row=16 CS1 Row=16 CS=2 Die BW=16 Size=2048MB channel[3] BW=16 Col=10 Bk=8 CS0 Row=16 CS1 Row=16 CS=2 Die BW=16 Size=2048MB Manufacturer ID:0x1 -CH0 RX Vref:29.3%, TX Vref:22.8%,21.8% -CH1 RX Vref:28.9%, TX Vref:20.8%,21.8% +CH0 RX Vref:28.5%, TX Vref:23.8%,22.8% +CH1 RX Vref:29.3%, TX Vref:20.8%,20.8% CH2 RX Vref:29.3%, TX Vref:22.8%,21.8% -CH3 RX Vref:27.9%, TX Vref:20.8%,20.8% +CH3 RX Vref:26.7%, TX Vref:21.8%,21.8% change to F1: 528MHz change to F2: 1068MHz change to F3: 1560MHz change to F0: 2112MHz out U-Boot SPL board init -U-Boot SPL 2017.09 (Feb 25 2025 - 08:48:59) -sfc cmd=9fH(6BH-x4) -unrecognized JEDEC id bytes: ff, ff, ff -unknown raw ID ff ff ff -Trying to boot from MMC2 -spl: partition error +U-Boot SPL 2017.09 (Feb 09 2024 - 18:56:36) +unknown raw ID 0 0 0 +unrecognized JEDEC id bytes: 00, 00, 00 +Trying to boot from MMC1 Trying fit image at 0x4000 sector ## Verified-boot: 0 ## Checking atf-1 0x00040000 ... sha256(7efcd01a0f...) + OK @@ -29,7 +27,7 @@ ## Checking atf-2 0xff100000 ... sha256(1163474a5b...) + OK ## Checking atf-3 0x000f0000 ... sha256(da90adf3a4...) + OK Jumping to U-Boot(0x00200000) via ARM Trusted Firmware(0x00040000) -Total: 304.579/460.237 ms +Total: 245.95 ms INFO: Preloader serial: 2 NOTICE: BL31: v2.3():v2.3-589-g3389cfdda:derrick.huang @@ -42,11 +40,10 @@ INFO: valid_cpu_msk=0xff bcore0_rst = 0x0, bcore1_rst = 0x0 INFO: system boots from cpu-hwid-0 INFO: idle_st=0x21fff, pd_st=0x11fff9, repair_st=0xfff70001 -ERROR: dfs get fsp_params[0] error, 0xfead0004 != 0xfead0003 -ERROR: dfs get fsp_params[1] error, 0x1111 != 0xfead0003 -ERROR: dfs get fsp_params[2] error, 0x0 != 0xfead0003 -ERROR: dfs get fsp_params[3] error, 0x60241520 != 0xfead0003 -ERROR: loader&trust unmatch!!! Please update trust if need enable dmc +INFO: dfs DDR fsp_params[0].freq_mhz= 2112MHz +INFO: dfs DDR fsp_params[1].freq_mhz= 528MHz +INFO: dfs DDR fsp_params[2].freq_mhz= 1068MHz +INFO: dfs DDR fsp_params[3].freq_mhz= 1560MHz INFO: BL31: Initialising Exception Handling Framework INFO: BL31: Initializing runtime services WARNING: No OPTEE provided by BL2 boot loader, Booting device without OPTEE initialization. SMC`s destined for OPTEE will return SMC_UNK @@ -67,18 +64,8 @@ CR: M/C/I Using default environment -no mmc device at slot 1 -Card did not respond to voltage select! -do_rkimg_test: dev_desc is NULL! mmc@fe2c0000: 0, mmc@fe2e0000: 1 -Card did not respond to voltage select! -PCIe-0 Link Fail - -Device 0: unknown device -Card did not respond to voltage select! -switch to partitions #0, OK -mmc0 is current device -Bootdev(scan): mmc 0 +Bootdev(atags): mmc 0 MMC0: Legacy, 52Mhz PartType: EFI DM: v2 Since in both cases, the main U-boot (Feb 09 2024) runs from the SD-card, I suspect that the U-boot SPL (or the preceding bootloader, if any) is somehow involved in setting up the eMMC properly, and the new one does not do the setup properly (or otherwise messes something up). Next things I could try are: Flash a recent Armbian image (different version/flavors) to eMMC using rkdeveloptool and see if any of those produce a working system/eMMC. Figure out how the boot process *really* works and what parts of the eMMC are loaded in what order and how Compare a working and broken armbian image (in the areas that contain bootloader-stuff) and swap out some of these parts to see what is the part that breaks it. However, my main issue is fixing reboots on the older armbian system we are using, so I might not get around to the above anytime soon (OTOH, it seems the newer U-boot SPL actually fixes the reboot issue, so that could motivate me to see if we can upgrade to the new u-boot version without losing eMMC).

@C127 any chance to make a release that already has the ethernet driver compiled and working ?

I keep having trouble with panel-mipi-dbi-spi not finding /lib/firmware/panel-mipi-dbi-spi.bin even if it exists and it works in another Armbian and Raspberry. This happens only with the armbian OS that I compiled with default linux configuration. The armbian OS image that I downloaded from armbian.com can drive the LCD (but has other problems with X11). When I boot my image while watching the serial output, I only see "Starting kernel", then a few lines regarding udev, then the login prompt (sorry, I will be more exact when I get back home). I changed console=both to console=serial, in armbianEnv.txt but I still don't see more kernel or init messages while booting. How can I activate this verbose boot? Is there any chance that the /lib/firmware is not mounted and available to the kernel module in this early stage?

I did so, but openvfd still doesn't work and can't compile.

This partnership ensures customers can build embedded products with long-term maintenance viability that will meet the challenges of tomorrow, such as compliance with the CRA, all built on proven Toradex platforms and upstream-first software. View the full article

I meant to say "armbian", my apologies

Dear all, How can i auto login h96max armbian without input user name&password. Every time i turn on the box, i have to enter the user name&password. I don't want to do that the same to windows OS Thank you,

The foreign added SPI-flash makes it custom in terms of Armbian bootloader. Look how to build U-Boot from Armbian build environment (development basically) or find howto on denx.de. It been a while since I last did that myself, so things might have changed a bit.

Sorry - this is probably an easy one for those that know. But I am trying hard to copy my work and progress and build another NAS out of another T95z Plus box for my brother. All is going well - but on the second box - months after building the first - I installed the latest download. So I have Old box = Armbian Linux 6.12.32-current-meson64 - v25.5.1 New box = Armbian Linux 6.12.34-current-meson64 - v25.8 rolling - Support:for advanced users (rolling release) Both show - Ubuntu stable (noble) - which I think I changed on first boot with Armbian-config. Okay - so I don't think I am an advanced user so that warning has got me worried. So is there another version I should be using? I can't find the old file I downloaded so they would be identical. I have disabled unattended upgrades and things like that. Or am I worrying about nothing. Anyway - thanks as always. I still can't believe I have these cheap things pulled from my dust bin doing a real job again.

TV Box Name: Sunvell T95Z plus Octagon shaped box (I wrote it before – but Beware – apparently a lot of variants) CPU Amlogics S912 Armbian build file name: Armbian_community_25.8.0-trunk.277_Aml-s9xx-box_noble_current_6.12.34 DTB file used: meson-gxm-t95z-plus.dtb – (my other T95z uses meson-gxm-vega-s96.dtb) Kernel Version: 6.12.34 Distribution Installed (focal, buster, etc): Noble Working Ethernet (Yes/No): Yes Max Ethernet Speed that works (100/1000): Not sure how to determine... Does wifi work (Yes/No): No Does bluetooth work (Yes/No): Not tested Does HDMI audio work (Yes/No): Yes Additional Comments (provide any additional information you feel is important): This is my second T95z plus box build. Using as headless server and both seem solid. Confirming what others have said – the build is different inside. This has a different wifi card and eemc. I have a 3rd T95z plus that has the dreaded NAND chip too. Having fun and learning. Using as a simple NAS now with a ZFS pool and works just fine.

My Radxa Rock 4SE does not boot since community-build 25.8.0-trunk.228. Current local builds based on the "main" branch are also affected. The bootloader log gives the following error: Checking hash(es) for config config-1 ... OK Checking hash(es) for Image atf-1 ... sha256+ OK Checking hash(es) for Image u-boot ... sha256+ OK Checking hash(es) for Image fdt-1 ... sha256+ OK Checking hash(es) for Image atf-2 ... sha256+ OK Checking hash(es) for Image atf-3 ... sha256+ OK ERROR: not expected type found -4001165690437497392 This source suggests, that it might be a problem with the ATF. However, my knowledge about details of the boot process are unforunately not sufficient to find a solution to this problem. How to reproduce? Download https://github.com/armbian/community/releases/download/25.8.0-trunk.228/Armbian_community_25.8.0-trunk.228_Rock-4se_bookworm_current_6.12.33_minimal.img.xz Install on SD card Try to boot Rock 4 SE from SD card image

Welcome to custom hardware / division exotics / subdivision retro It is hard already when its new custom hardware and main division. If nobody ported HW to mainline Linux and keep it operational, its usually quite a long path. Armbian provides build framework, that helps in the process, but hard work is still on the one that will deal with the SoC - here you can hope to find someone on forum(s) to share some specific ideas. Adding is fairly straightforward https://docs.armbian.com/Process_Contribute/#adding-a-new-board but if there are sources for boot loader, sources for kernel, or better - support in the mainline kernel. Even when you have all this, it can still be quite challenging. Each such board usually require more people, a team. When I recall how many months we lost on one of Marvell's 🤔 Espressobin is an example how board support can be made super complicated - check history from day one. If board support package is on that level ... its worse out of all we have seen here. And now its an old hardware, not interesting so much. And remain broken as we don't have anyone to deal with it / its not worth.

These errors are fine because moonlight will try all the hw accel APIs like vaapi, vdpau and vulkan, but on rockchip platform we only need rkmpp decoder, as you can see in the log it is detected,

sudo modprobe i2c-dev ?

Can you confirm that you can still run X11 with Linux 6.12?

Ok, the noble_vendor_gnome image actually works. Not out of the box, you have to select "headphones" and most important, the gnome self-test "front left, front right" doesn't work. That's what was fooling me to begin with. But if you play videos, that works just fine. So for anyone on down the line confused by all of this, you need to copy a known good video or soundfile over to see if it will play. Here's the armbianmonior -u for it in any case - https://paste.armbian.com/nutedakeco However, one problem solved, new problem shows up to take its place. The current_ kernel images I've tried no longer boot off the nvme now that I have a SATA drive connected! It just sits there and hangs. The vendor images work OK, although I am seeing the SATA drive mysteriously appear and disappear upon boot. I suppose I should start a new thread for that one? I see a big long thread about SATA drives already.

@balbes150 which bios are you using, the exactly version, i updated to 9.0.0 but i had some issue. Thanks

I was having similar issues with this Armbian version, but on an Orange Pi Zero 3. I suggest trying to download the image again, as they received updates today, at least the Zero 3. In my case, I wasn't able to download any packages because every time the firmware tried to update, the kernel collapsed.

I updated my guide to include the newer "pipewire" audio system software. LINK HERE. I am curious to know if you got sound working on your tv box, and how you did it. Also, what tv box are you using these days?

The previous post was mostly for slightly older releases of Armbian which includes Ubuntu 23 or Debian 10 and lower releases installed on a Tv Box. This short guide is for Ubuntu 24.04 and later releases installed on a Tv Box. This guide should also work for latest versions of Debian (but I didn't test it). Get a generic USB "sound card" audio adapter dongle from AliExpress, eBay, Amazon (etc). See the photo posted above (LINK). These gadgets are often between $2 and $5 USD but they all are usually similar, so I just got the lowest priced one at about $2.50 USD. Insert the USB "sound card" audio adapter dongle into your tv box. Create a new regular user in Linux, and login with the new user (not root). sudo adduser {user-name} Be sure your user is in the group 'audio' and 'sudo', and be sure you have logged in as the user (not root). sudo usermod -a -G audio,sudo {username} Now let's install and setup audio sound using Pipewire and WirePlumber (but not Pulse). First, install alsa base, and mixer software. sudo apt install -y alsa-base alsa-tools alsa-utils alsamixergui qasmixer Make a backup copy of these two text files /etc/modules and /etc/modprobe.d/alsa-base.conf and save the backup copies in your home directory. cp -v /etc/modules $HOME/modules.backup cp -v /etc/modprobe.d/alsa-base.conf $HOME/alsa-base.conf.backup Edit the text file /etc/modules and write “snd-usb-audio” without quotes at the end of the file, and then save and close the file. sudo nano /etc/modules Edit the text file /etc/modprobe.d/alsa-base.conf and change and add some text sudo nano /etc/modprobe.d/alsa-base.conf Put a hash # symbol in front of every “options snd-usb-audio index=-2” that you see in the file /etc/modprobe.d/alsa-base.conf - I found two instances. Add these two lines of text to the bottom of the file /etc/modprobe.d/alsa-base.conf, and then save and close the file. alias snd-card-0 snd-usb-audio options snd-usb-audio index=0 Install pipewire and wireplumber and support files. sudo apt install -y pipewire pipewire-pulse wireplumber pipewire-audio-client-libraries gstreamer1.0-pipewire Optional to install a graphical media player smplayer, vlc, totem, (etc). and optional install a graphical audio player rhythmbox, audacious, (etc). sudo apt install -y smplayer sudo apt install -y audacious In case that the pulse audio system is still installed, we will disable it for the local user. systemctl --user --now disable pulseaudio.service pulseaudio.socket Enable pipewire for the local user systemctl --user --now enable pipewire pipewire-pulse To be sure everything will work, let's reboot sudo reboot Login as the regular user, and run some informative commands to prove that the USB dongle and the pipewire audio system are working. Use alsa player to list audio devices. aplay -l Use alsa player to list PCM audio outputs (use capital "L"). aplay -L Use wireplumber control to show status of audio outputs/inputs via pipewire. wpctl status Use wireplumber control to show a volume level of default output wpctl get-volume @DEFAULT_AUDIO_SINK@ Change the volume using alsa mixer, after running it, press up/down arrow keys, and press "q", "e", "z", "c" and "s" keys. alsamixer Change the volume +/- by ten percent using wireplumber control. wpctl set-volume @DEFAULT_AUDIO_SINK@ 10%+ wpctl set-volume @DEFAULT_AUDIO_SINK@ 10%- * Important * connect a headphone, or amplifier to the 3.5mm output jack 🎧 of the USB adapter dongle and play some audio files. aplay /usr/share/sounds/alsa/Front_Center.wav aplay /usr/share/sounds/alsa/Noise.wav You can also login to the graphical desktop such as lxde or xfce4 and open a video/media player or an audio player software and play some audio files. I used Audacious for this example. Again, audio files are available in the directory /usr/share/sounds/alsa/ From here, you can use the wpctl command (LINK) or another control program for wireplumber. Maybe some of the Pulse audio tools would still work. Audacious works fine when playing locally stored audio files. The same should be true for using SMPlayer or VLC to play video files. Note that depending on the speed of your tv box, Youtube in Chrome / Chromium is sometimes laggy, has delays and resets. Other than that, it's all good. Enjoy ♪ ♫ ☺

Yes, I know about it and I did it right after the update was finished. Maybe it was an isolated case. I did armbin-install again and test 30 reboot again and each one correctly indicated 1Gb RAM 🙂

Well that depends, have you tried adding more space to exclude the possibility that the img actually can fit all the data? If you are using snaps without excluding the containerized mounts on one of them and not the other, it seems like a very logical conclusion that the img actually runs out of space and the "not enough space" is accurate in this situation. Edit: I have never used snaps so I don't know, but I think snaps create containerized mounts every time you boot, and you probably don't want that data on your backup anyway since it will never be used. Others can surely put more light into this than my wild guess about this. Edit 2: This made me a bit curious about how snaps actually work, if they were to randomize the mountpoints and such, but after a tiny bit of searching I found this: https://www.howtogeek.com/660193/how-to-work-with-snap-packages-on-linux/#installing-snap-packages So just editing exclude.txt and adding /snap/* and then add -t option when running shrink-backup should solve this issue. As a matter of fact, I should probably add that as default in the exclude.txt file on the repo and in the script if not using the exclude file, because I don't think you ever want that data on the image... Feedback about this would be highly appreciated before I implement that change, does snap create the directory for each SquashFS within /snap if it does not exist or will it break if it is excluded like I suggest above? Edit 3: According to this each SquashFS is mounted directly to /snap so excluding /snap/* (keeping the actual /snap directory but excluding all content) should work right? Feedback please, I know there are some of you who know how this work, @eselarm maybe?

Thanks a lot. It worked with my Beelink Ultimate GT1 from focal to jammy.