Search the Community

Is there an Armbian image with home assistant that isn't minimalistic? or Is there a way to install HA on a more robust desktop armbian 25.2 image for the Orange Pi 5 Plus? I feel the orange pi 5 is robust enough to handle HA under a desktop Armbian environment than other SBCs.

i also have issues to move the system to the nvme ssd 😞 my base is the Armbian 25.5.1 with 6.1.115 (vendor kernel) image .... "copied" (usbimager) it to the sdcard and its booting ... 🙂 so I upgraded the system on the sdcard, still running 🙂 I read some posts and advices .... so I partioned the nvme with one big partition (/dev/nvme0n1p1) running armbian-install choosing option 7, (loading/upgrading bootloader to mtd ) after this i choose option 4 (boot from mtd, system on sata, usb ... ) only possible selection was /dev/nvme0n1 ... looked ok said yes to everything no Error system goes to shutdown /power off removed power, removed sdcard plugin power again .... and ... no boot 😞 serial console saying: DDR 9fa84341ce typ 24/09/06-09:51:11,fwver: v1.18 ch0 ttot10 ch1 ttot10 ch2 ttot10 ch3 ttot10 ch0 ttot18 LPDDR4X, 2112MHz channel[0] BW=16 Col=10 Bk=8 CS0 Row=16 CS1 Row=16 CS=2 Die BW=16 Size=2048MB ch1 ttot18 channel[1] BW=16 Col=10 Bk=8 CS0 Row=16 CS1 Row=16 CS=2 Die BW=16 Size=2048MB ch2 ttot18 channel[2] BW=16 Col=10 Bk=8 CS0 Row=16 CS1 Row=16 CS=2 Die BW=16 Size=2048MB ch3 ttot18 channel[3] BW=16 Col=10 Bk=8 CS0 Row=16 CS1 Row=16 CS=2 Die BW=16 Size=2048MB Manufacturer ID:0xff DQS rds:h1,h1 CH0 RX Vref:27.1%, TX Vref:21.8%,22.8% DQ rds:h1 l0 h2 l0 h1 h5 l0 l0, l0 h3 l0 h3 h7 h2 l0 h1 DQS rds:l0,h1 CH1 RX Vref:28.5%, TX Vref:23.8%,23.8% DQ rds:h1 h2 h1 h3 h1 h3 l0 h1, h1 h4 h1 h4 h1 h3 l0 h4 DQS rds:l0,h1 CH2 RX Vref:27.5%, TX Vref:23.8%,22.8% DQ rds:h1 h3 h2 h1 h1 h6 h4 h1, h1 h2 h6 l0 h6 h2 h6 h3 DQS rds:h1,l0 CH3 RX Vref:29.7%, TX Vref:21.8%,20.8% DQ rds:h5 h3 h2 h1 h3 h2 h2 h2, h5 h2 h1 h2 h4 l0 l0 h5 stride=0x2, ddr_config=0x4 hash ch_mask0-1 0x20 0x40, bank_mask0-3 0xa00 0x1400 0x2800 0x0, rank_mask0 0x401000 change to F1: 528MHz ch0 ttot10 ch1 ttot10 ch2 ttot10 ch3 ttot10 change to F2: 1068MHz ch0 ttot14 ch1 ttot14 ch2 ttot14 ch3 ttot14 change to F3: 1560MHz ch0 ttot16 ch1 ttot16 ch2 ttot16 ch3 ttot16 change to F0: 2112MHz ch0 ttot18 ch1 ttot18 ch2 ttot18 ch3 ttot18 out U-Boot SPL board init U-Boot SPL 2017.09-armbian-2017.09-S3e40-P187d-He5fc-Ve691-Bb703-R448a (May 30 2025 - 10:51:06) sfc cmd=03H(6BH-x4) Trying to boot from MMC2 MMC: no card present mmc_init: -123, time 0 spl: mmc init failed with error: -123 Trying to boot from MTD2 Trying fit image at 0x4000 sector ## Verified-boot: 0 ## Checking atf-1 0x00040000 ... sha256(7612223b82...) + OK ## Checking uboot 0x00200000 ... sha256(11a994b967...) + OK ## Checking fdt 0x00354c30 ... sha256(e3b0c44298...) + OK fdt_record_loadable: FDT_ERR_BADMAGIC ## Checking atf-2 0xff100000 ... sha256(70505bb764...) + OK fdt_record_loadable: FDT_ERR_BADMAGIC ## Checking atf-3 0x000f0000 ... sha256(b2af21b504...) + OK fdt_record_loadable: FDT_ERR_BADMAGIC Jumping to U-Boot(0x00200000) via ARM Trusted Firmware(0x00040000) Total: 496.285/765.931 ms INFO: Preloader serial: 2 NOTICE: BL31: v2.3():v2.3-868-g040d2de11:derrick.huang, fwver: v1.48 NOTICE: BL31: Built : 15:02:44, Dec 19 2024 INFO: spec: 0x1 INFO: code: 0x88 INFO: ext 32k is valid INFO: ddr: stride-en 4CH INFO: GICv3 without legacy support detected. INFO: ARM GICv3 driver initialized in EL3 INFO: valid_cpu_msk=0xff bcore0_rst = 0x0, bcore1_rst = 0x0 INFO: l3 cache partition cfg-0 INFO: system boots from cpu-hwid-0 INFO: disable memory repair INFO: idle_st=0x21fff, pd_st=0x11fff9, repair_st=0xfff70001 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 ERROR: Error initializing runtime service opteed_fast INFO: BL31: Preparing for EL3 exit to normal world INFO: Entry point address = 0x200000 INFO: SPSR = 0x3c9 No valid device tree binary found - please append one to U-Boot binary, use u-boot-dtb.bin or define CONFIG_OF_EMBED. For sandbox, use -d <file.dtb> initcall sequence 00000000002d2af8 failed at call 00000000002c502c (err=-1) ### ERROR ### Please RESET the board ### if im boot with sdcard in the system and mount /dev/nvm0n1p1 there is the whole system .... inklusive /boot und boot/dtb ..... what didd I miss ? Does anyone hav a link to a working tutorial ?

Hi there I'm using Ubuntu 24.04 (Noble) KDE Neon image from may 26, 2025. After download this image and installing it, Wayland was working fine, not problems at all. Then, after a system upgrade, if i choose Wayland from session manager, the system freezes and i can't boot with Wayland, only X11... Before the update, the system was smooth, now it's really laggy....Like i said, i'm using Desktop image with Armbian Linux v6.12 KDE Neon (Ubuntu 24.04) There's something wrong with the update Anyone knows why is this happening, and any turnaround to use Wayland again?

I've downloaded the Armbian 25.5.1 (Kernel 6.12) Home Assistant image (https://dl.armbian.com/orangepi5-plus/Bookworm_current_minimal-homeassistant), burned to microsd and rebooted the orange pi 5 plus. I burned the image to a microsd cards, inserted the microsd and did a hard reboot of the SBC. The error message is "Gave up waiting for root filesystem device."

Hello all, I'm also bought an orange pi 5 pro :-) I have red a little bit in the Forum (after i'm bought) and I'm a little bit confused now 🙂 I'm new in the embedded (arm) world but have some knowledge from the desktop/x86 windows & linux world. my first expirience with the device was also .... intresting. I'm installed the official (orangepi.org) debian-booksworm image with the 6.1.xx kernel .... and diddnt get the network interfaces to run, and no nvme device available ... next try was with debian-booksworm image and the 5.10..xx kernel and the networks just runned and the nvme showed up. But i think for my need this kernel is just old ... So now im trying armbian (iot version) ..... at the moment with an 6.1.99 vendor kernel. installed weston seatd & co for running some rudimentary OpenGL ES based tests .... but without success. glxgears / glxinfo failing EGLInitialize() cannot create context ... rknpuxxxx.so not found. i think thats the "which /dev/dri device is the right" issue. Have also red that some HW functionally is only available on full blown desktop environments 😞 What do I need: - i dont want to use the device as a desktop replacement - i want to use it as development board for tinkering around with OpenGL ES / OpenCL and get some experience with embedded development. - rudimentary boot2qt functionality based on wayland-egl or eglfs platform (running Qt apps in wayland cage or without window manager) - good opengl es 3.2 support - recent compiler support, gcc13(+) / clang 18 - boost / qt 6.7 + should available as devel packages (don't like to build it for my own, but if its necesarry ...) - opencl support would be nice - media / audio support (QMultimedia) - atm i dont need video acceleration, but maybe later .... So my question: with which Kernel / System should i start with ? is the device a good choice ? I bought it mainly because the 2 nics and the available storage options (nvme / emmc) makes it very flexible for another usage (router backup i.e) Soon or later i have to dig into yocto also maybe ....

After enabling the rk3588-hdmirx overlay in armbian-config device tree overlays, whenever I boot, I am greeted with multiple hdmirx (fdee0000.hdmirx-controller: hdmirx_wait_lock_and_get_timing HDMI pull out, return!) errors on boot. On a previous install, the hdmirx errors would block the entire boot process and it would just hang forever. I do not know the exact cause, but the issues seemed to arise after I ran this command to disable the X Display Server "systemctl set-default multi-user.target". The errors could only be resolved if I plugged in the sd card into another device and removed rk3588-hdmirx from overlays in /boot/armbianEnv.txt . I have since reinstalled Armbian, but the errors still appear during the boot process, however now they do not block the boot process and I am able to successfully boot into Armbian. Is there any solution to get rid of these errors, or ensure that the "fdee0000.hdmirx-controller: hdmirx_wait_lock_and_get_timing HDMI pull out, return!" error doesn't block the boot process without disabling hdmirx? These are my current device details: .. orangepi@orangepi5-plus `:]x**j-,' ----------------------- .,+t***********z\<" OS: Armbian 25.5.1 noble aarch64 ?******************; Host: Orange Pi 5 Plus '*n` .'`^,;;,^`'. ,cc. Kernel: Linux 6.1.115-vendor-rk35xx -<. .[l Uptime: 30 mins // ^^ ^^ \\ Packages: 1822 (dpkg) !^ ^^ ": Shell: bash 5.2.21 'tt}` !~]rj_ ")t/. Display: 3840x2160 @ 60 Hz Itttt?' ~~]rr] `{tttt, DE: KDE Plasma 6.3.90 \tttttt!""I_]r("""~tttttt1 WM: KWin (Wayland) '_tttttttttttt)ftttttttttttti. WM Theme: Breeze \*ztttttttttttttttttttttttttf**[ Theme: Breeze (Dark) [Qt], Yaru [GTK3] l**c)tttttttttttttttttttttttt(z**, Icons: breeze-dark [Qt], Yaru [GTK3] .z*x.`tttttttttttttttttttttttt.`u*n Font: Noto Sans (10pt) [Qt] >` (tttttttttttttttttttttt] "I Cursor: breeze (24px) ,tttttttttttttttttttttt` Terminal: konsole 25.4.1 ./tttttfttttttttfttttt( CPU: rk3588 (8) @ 2.40 GHz 'I)))(\()(tt))|\()({;' GPU: Mesa Mali-G610 (Panfrost) .~~~~~~~|)~~~~~~~< Memory: 4.34 GiB / 15.58 GiB (28%) '[)))))1|()))))))? Swap: 0 B / 7.79 GiB (0%) ",,," ",,,^ Disk (/): 7.82 GiB / Here is the dmesg log after boot up, the hdmirx errors appear near the end: boot_errors.txt

It's been a while since I used Armbian. I have tons of ARM SBCs from a few years back because I think they're fascinating but they either wind up being too slow or just not worth using it for whatever since x86 "SBC like" boards exist and are pretty cheap. Fast forward to now and I'm doing some touchscreen development and just because of how I have things setup I needed 3 things, I2C, Interrupt capable GPIO and an actual DisplayPort. That combination of things is surprisingly hard to find. I had a couple of things on hand, (Seeed Odyssey x86, Odroid H2/H3, Rpi's, Nvidia Jetson Nano). I spent way more time than I should have trying to make each of these work, in the end only the Rpi4 worked because the GPIO is good, problem is the HDMI ports are native. That's kind of a thing with ARM SBC's that's opposite from x86 and desktop GPU's...the native display interface is usually DisplayPort of some form on x86. So with the Pi4 I had to use one of the few HDMI->DP adapters I could find (the other way is common, this way is rare) and it worked but it's kind of jank. The other SBCs had various issues with GPIO even though they had displayports. So I picked up the Orange Pi 5 Plus because it has a typeC/DP which is fine. I think I tried the latest image of Armbian first, and it doesn't boot, there was a post here over a month ago about it so I wound up dropping Armbian cuz that's not a good start. Manjaro Rpi images work well, they have a dev image for the orange Pi but their device tree is missing the typeC displayport connections. Then I tried Orange Pi OS / Arch which looks ugly but the DP works....though the colors are swapped, like the red/green channels are mixed up. I couldn't get I2C2 working either. I saw a post on here about it mentioning the kernel version etc. but I couldn't get it by device wouldn't show up on a scan. So I came back to Armbian, slightly older image with the vendor kernel. Has pretty much the same issues. After some messing around I found that the I2C4_M3 mux overlay works to put the I2C4 bus into play, this one worked for me. So I was able to compile my driver module against the orange Pi source and get it working but I still have this issue with the DP colors being swapped and slightly shifted. Something is off about the DP configuration. Right now I have enough to do what I need to do but I will have to resolve that. I'm leaning towards the issue being in the DT. If anyone has any ideas about this it'd be much appreciated. Just figured I'd tell that little story in case some of the Armbian devs are looking for feedback. Think I'll stick with Armbian since it works better than anything else, though I much prefer Arch based distros. As for the Orange Pi itself, this thing is great. It's an actual development board, with enough interfaces to actually develop something, so I think I'll actually use this one.

Hi im having problems when booting armbian on my OPI5P it is just blinking green and not showing a picture. I am using this version of Armbian: Armbian_25.5.1_Orangepi5-plus_noble_current_6.12.28_gnome_desktop.img and I have tried it on all boot media i have available (NVME, USB and SD card) but none worked. Sorry if there are any gramatical errors, I am from germany and my english isnt the best.

I have built and used it with the latest source and still HDMI audio and analog audio does not work. Is there any way to get HDMI audio to work other than using the vendor kernel?

After installing official Armbian_25.2.1_Orangepi5-plus_bookworm_vendor_6.1.99_xfce_desktop.img to sdcard, then to nvme all is fine, until, I do an apt update & upgrade, after that point chromium fails to run. I explored the logs to see it a failure to load chromium.conf from /etc/chromium.d/chromium.config (failed symbolic link to /etc/armbian/chromium.config). Is there a known workaround besides utilization of firefox?

I am running an unmodified Server version of Armbian Linux v6.12 (Ubuntu 24.04) on an Orange Pi 5 Plus. I need to play sounds using the headphone jack on my SBC. Unfortunately the ES8388 sound chip is not recognized, the aplay -l output is as follows: **** List of PLAYBACK Hardware Devices **** card 0: Analog [Analog], device 0: fe470000.i2s-es8328-hifi-analog es8328-hifi-analog-0 [fe470000.i2s-es8328-hifi-analog es8328-hifi-analog-0] Subdevices: 1/1 Subdevice #0: subdevice #0 The correct output on desktop systems should like this (and it was like this on Desktop Armbian). What should I do to enable the ES8388 sound chip while staying on a server OS? Change something in the boot environment maybe? Install drivers?

Hi, The RK3588 supports frequencies as low as 408MHz, but in armbian the minimum is 1008MHz, which makes the cpu run hotter and draw more power even when idle, compared with the OPI ubuntu version. These are the available frequencies: $ cat /sys/devices/system/cpu/cpufreq/policy0/scaling_available_frequencies 1008000 1200000 1416000 1608000 1800000 $ cat /sys/devices/system/cpu/cpufreq/policy6/scaling_available_frequencies 1200000 1416000 1608000 1800000 2016000 2208000 2400000 I want to add the missing frequencies, I tried to look in the armbian repo for dts files that contain these frequencies, but I couldn't find anything. Is is possible to do this by loading dti files on boot? or does it need a kernel recompile? Thanks!

I'm new to boards with linux and this is my very first attempt to install linux systems on board so there might be something that I cannot be aware of. I tried to install armbian v6.12 on the SD card but after I finish configureing the setup, the wifi doesn't work. Unfortunately I have no wires to connet to the board so now it is unable for me to connect the board to the internet. The problem is exactly the same as the post Wifi module AX210 - Orange Pi 5 Plus - Armbian Community Forums. I can see the network controller through `lspci -v`: And the dmesg shows that iwlwifi cannot find suitable version to use: And I indeed have the firmware I need under /usr/lib/firmware: (the one ended with 59) Unfortunately I have no wires to connet to the board so now I cannot use apt to update and upgrade the system and the firmware in it and cannot use Armbianmonitor.

How do I change the default desktop environment on Debian 12 startup from cinnamon to xfce4? I have installed xfce4 and it's related "goodies", added a .Xclients file containing "startxfc4" in both root and ~/ folder locations. But the unit sometimes boots back into cinnamon. I do not see anything under armbian-config to control the desktop environment or to switch between cli/gui. I recall such options under orangepi-config (at least the cli/gui switching).

I recently bought an orange pi plus and am using the armbian 6.12 server (https://dl.armbian.com/orangepi5-plus/Noble_current_server) I'm wanting to setup hardware acceleration for jellyfin but having trouble with the right steps. I'm using jellyfin inside docker on the orange pi inside armbian. I've found various tutorials but it seems like some of them reference things that no longer exist (like panfork seems to no longer be needed for latest mesa if I'm understanding correctly?), so wanting to see what I need to do to set this up. So it seems like I need to disable panthor and use mali instead, but I can't find in the armbian config menu the option to do that, and not sure if I know how to get the right mali. Any help would be greatly appreciated. armbianmonitor is at https://paste.armbian.com/nurazajipu I've seen these tutorials/posts for reference: * https://akashrajpurohit.com/blog/setup-jellyfin-with-hardware-acceleration-on-orange-pi-5-rockchip-rk3558/ * https://github.com/andyshrk/mesa/blob/panthor-v4/Panfrost-build-howto.md * https://forum.jellyfin.org/t-solved-hw-transcoding-rk3588-arch-not-working?pid=54084 * `https://forum.armbian.com/topic/49115-how-to-install-opencl-on-orangepi-5-plus/` * https://forum.jellyfin.org/t-rockchip-transcode-missing-dev-mali0

I want to install jellyfin on my OrangePi 5 Plus and need OpenCL to enable HDR-SDR mapping. I tried to follow the instruction on Jellyfin's official website: Rockchip VPU | Jellyfin However, I'm stucked on the step of installing OpenCL. I also tried this: Install OpenCL on Debian and Ubuntu and Armbian for Orange Pi 5 RK3588 But no luck either. Both instruction led to broken hardware acceleration in chrome and failing to start kernal in Jellyfin. Logs from ffmpeg: sudo /usr/lib/jellyfin-ffmpeg/ffmpeg -v debug -init_hw_device rkmpp=rk -init_hw_device opencl=ocl@rk Applying option init_hw_device (initialise hardware device) with argument opencl=ocl@rk. arm_release_ver: g13p0-01eac0, rk_so_ver: 10 Failed creating base context during opening of kernel driver. Kernel module may not have been loaded [AVHWDeviceContext @ 0xaaab055f5460] 1 OpenCL platforms found. [AVHWDeviceContext @ 0xaaab055f5460] 1 OpenCL devices found on platform "ARM Platform". arm_release_ver: g13p0-01eac0, rk_so_ver: 10 Failed creating base context during opening of kernel driver. Kernel module may not have been loaded [AVHWDeviceContext @ 0xaaab055f5460] 0.0: ARM Platform / Unknown Device Segmentation fault Logs from Jellyfin: Failed creating base context during opening of kernel driver. Kernel module may not have been loaded Failed creating base context during opening of kernel driver. Kernel module may not have been loaded Logs from clinfo: arm_release_ver: g13p0-01eac0, rk_so_ver: 10 Failed creating base context during opening of kernel driver. Kernel module may not have been loaded I want to know how to correctly enable OpenCL on OrangePi 5 Plus, thank you!

EDIT: I tried using ext4 rather than btrfs and.. somehow that solved it? I don't understand how the SSD file system would change how the bootloader is flashed because if properly flashed, the SD card shouldn't work at all, unless something has changed. Hey all, I wanted to move to the newest version of armbian (25.2.1) and for whatever reason neither `apt update && apt upgrade` nor `armbian-upgrade` (as a sanity check) worked so I wiped the SPI flash using `mtdtools` as prescribed in the forum post linked on the support page. 1) Booted from SD, installed Armbian and the bootloader. 2) Shut down, removed SD and turned on. Machine hung and never booted from NVMe. 3) Thought somehow I did something wrong or there was an error and used MaskROM mode and `rkdeveloptool` to revert it to boot from SD. 4) Repeated step 2 5) Still won't boot from NVMe but boots from SD (should have tried this first) 6) Tried reinstalling the bootloader to SPI flash, get this message: Processing blocks: 394/394 (100%) diff blocks: 0 Done Which reads like the flash is identical to what would is contained in the installer itself so it isn't overwritten. Wiped again and tried to install bootloader again. Still won't boot from NVMe but boots from SD card normally. Also, forgot to include this in my steps: I formatted the NVMe 3 times total and installed/reinstalled Armbian from the `armbian-install` script as a sanity check. Have had no issues in the past with any of this (I think I was on 24.11 most recently) so my first thought was a bug in the installer but am not seeing anyone else having this issue so figured I would ask here just to be sure. My questions are: 1) Has anyone else tried to use the installer on 25.2? I can't imagine there were any (much less breaking) changes but I am perplexed at this point. 2) Is the bootloader file available separately so I can flash it from `rkdeveloptools` Worst case I can image 24.11 on to the SD and try to install the bootloader that way but again, id be surprised if there were major changes. Thanks in advance!

My setup includes orange pi 5 plus, Samsung NVME SSD M2 4 TB with Armbain os. 256 GB eMMC and Intel BE 200 Wi-Fi. There are no drivers for the intel BE 200 Wi-Fi or any instructions to make it work.

I followed this manual I tried to boot , led was green and red , Display did not work. But Orange pi official images ca n boot my machine. How can I solve this problem?

I have installed Armbian 25.02 via an official Armbian image for Armbian 25.02 (Debian 12) Vendor Kernel 6.1.xx, is it possible (and sane) to upgrade to Armbian 25.05 (Debian 12) Vendor Kernel 6.1.xx? If so besides downloading the new image and installing fresh what are one's options?

I would love to use Armbian Build to construct a Debian 12 Bookworm images with KDE Plasma as the windows manager. I note that KDE Plasma isn't an option in the armbian builder. I have no problem building with XFCE or Cinnamon.

Is there a list of Armbian Kernels that include EMMC support? I've tried the vendor kernel build 6.1.99, the LTS 6.12.21, and Bleeding Edge 6.14.0 to find they all lack the mmcblk0 under /dev/ , and lack overlays for it under /boot/dtb/rockchip/overlays/. I have wiped SPI and SPNOR without success.

Hi @ all, long time reader, but never managed to register. Now it is time... as I'm not able to solve this myself, kindly asking for help. I'm stuck, my Orangepi 5 plus stops boot at this: Loading, please wait... Starting systemd-udevd version 252.36-1~deb12u1 Begin: Loading essential drivers ... done. Begin: Running /scripts/init-premount ... (initramfs) What happened before? Last year I bought the Orangepi 5 plus (8GB) and went ahead, testing everything out - having incredible fun with this little box. But with a way to old/slow sd card which finally failed two or three months ago. I went ahead and wrote the Armbian based Cinnamon (Kernel 6.1 incl. MESA/VPU) to a new SD Card. Everything was working flawless, but still ... SD Card. Therefore I bought a 1TB nvme, installed it and used armbian-install to install the bootloader on MTD Flash. Afterwards I got everything working from nvme. Amazing results, it just worked after armbian-install was finished. I shut down the system, removed SD card and used the nvme install from now on for weeks on a daily basis. Several apt-get dist-upgrades no problem at all. The last one done Sunday, if I remember correctly. Until today. I had some spare time and decided to apt-get update and apt-get dist-upgrade again. The commands finished without any error and new updates were done. But now -I wanted to reboot the device- reboot stalled. I see a black screen with above mentioned white text. So, something must have gone wrong I think. The Orangepi boots fine when I insert the SD Card again, also the nvme is there and can be mounted. Seemingly all data is still there. But how to proceed? I'm at a loss. Can anything be done on my side to solve this? Or is a reinstall to be done? The apt history logfile on the nvme (/var/logs/apt/history.log) contains both upgrades I mentioned and reads: Start-Date: 2025-04-01 16:15:10 Commandline: apt-get dist-upgrade Requested-By: edited (1000) Upgrade: armbian-config:arm64 (25.5.0-trunk.286.0324.065110, 25.5.0-trunk.325.0401.114753), tzdata:arm64 (2025a-0+deb12u1, 2025b-0+deb12u1), firefox-nightly:arm64 (138.0a1~20250324091950, 139.0a1~20250401094015), ghostscript-x:arm64 (10.0.0~dfsg-11+deb12u6, 10.0.0~dfsg-11+deb12u7), libgs10-common:arm64 (10.0.0~dfsg-11+deb12u6, 10.0.0~dfsg-11+deb12u7), libgs10:arm64 (10.0.0~dfsg-11+deb12u6, 10.0.0~dfsg-11+deb12u7), ghostscript:arm64 (10.0.0~dfsg-11+deb12u6, 10.0.0~dfsg-11+deb12u7), linux-headers-vendor-rk35xx:arm64 (25.2.3, 25.2.3), libgs-common:arm64 (10.0.0~dfsg-11+deb12u6, 10.0.0~dfsg-11+deb12u7) End-Date: 2025-04-01 16:15:46 Start-Date: 2025-04-02 09:42:43 Commandline: apt-get dist-upgrade Requested-By: edited (1000) Upgrade: linux-image-vendor-rk35xx:arm64 (25.2.3, 25.2.3), firefox-nightly:arm64 (139.0a1~20250401094015, 139.0a1~20250401212749), linux-headers-vendor-rk35xx:arm64 (25.2.3, 25.2.3), armbian-bsp-cli-orangepi5-plus-vendor:arm64 (25.2.2, 25.2.3) End-Date: 2025-04-02 09:44:34 term.log in this directory shows nothing unusual, too. As far as my limited knowledge reaches ofc: Log started: 2025-04-01 16:15:10 (Reading database ... 218528 files and directories currently installed.) Preparing to unpack .../0-tzdata_2025b-0+deb12u1_all.deb ... Unpacking tzdata (2025b-0+deb12u1) over (2025a-0+deb12u1) ... Preparing to unpack .../1-armbian-config_25.5.0-trunk.325.0401.114753_all.deb ... Unpacking armbian-config (25.5.0-trunk.325.0401.114753) over (25.5.0-trunk.286.0324.065110) ... Preparing to unpack .../2-firefox-nightly_139.0a1~20250401094015_arm64.deb ... Unpacking firefox-nightly (139.0a1~20250401094015) over (138.0a1~20250324091950) ... Preparing to unpack .../3-ghostscript-x_10.0.0~dfsg-11+deb12u7_arm64.deb ... Unpacking ghostscript-x:arm64 (10.0.0~dfsg-11+deb12u7) over (10.0.0~dfsg-11+deb12u6) ... Preparing to unpack .../4-ghostscript_10.0.0~dfsg-11+deb12u7_arm64.deb ... Unpacking ghostscript (10.0.0~dfsg-11+deb12u7) over (10.0.0~dfsg-11+deb12u6) ... Preparing to unpack .../5-libgs10_10.0.0~dfsg-11+deb12u7_arm64.deb ... Unpacking libgs10:arm64 (10.0.0~dfsg-11+deb12u7) over (10.0.0~dfsg-11+deb12u6) ... Preparing to unpack .../6-libgs10-common_10.0.0~dfsg-11+deb12u7_all.deb ... Unpacking libgs10-common (10.0.0~dfsg-11+deb12u7) over (10.0.0~dfsg-11+deb12u6) ... Preparing to unpack .../7-libgs-common_10.0.0~dfsg-11+deb12u7_all.deb ... Unpacking libgs-common (10.0.0~dfsg-11+deb12u7) over (10.0.0~dfsg-11+deb12u6) ... Preparing to unpack .../8-linux-headers-vendor-rk35xx_25.2.3_arm64.deb ... Armbian 'linux-headers-vendor-rk35xx' for '6.1.99-vendor-rk35xx': 'prerm' starting. Cleaning directory /usr/src/linux-headers-6.1.99-vendor-rk35xx ... Armbian 'linux-headers-vendor-rk35xx' for '6.1.99-vendor-rk35xx': 'prerm' finishing. Armbian 'linux-headers-vendor-rk35xx' for '6.1.99-vendor-rk35xx': 'preinst' starting. Armbian 'linux-headers-vendor-rk35xx' for '6.1.99-vendor-rk35xx': 'preinst' finishing. Unpacking linux-headers-vendor-rk35xx (25.2.3) over (25.2.3) ... Setting up libgs-common (10.0.0~dfsg-11+deb12u7) ... Setting up linux-headers-vendor-rk35xx (25.2.3) ... Armbian 'linux-headers-vendor-rk35xx' for '6.1.99-vendor-rk35xx': 'postinst' starting. Configuring kernel-headers (6.1.99-vendor-rk35xx) - please wait ... HOSTCC scripts/basic/fixdep HOSTCC scripts/kconfig/conf.o HOSTCC scripts/kconfig/confdata.o HOSTCC scripts/kconfig/expr.o LEX scripts/kconfig/lexer.lex.c YACC scripts/kconfig/parser.tab.[ch] HOSTCC scripts/kconfig/lexer.lex.o HOSTCC scripts/kconfig/menu.o HOSTCC scripts/kconfig/parser.tab.o HOSTCC scripts/kconfig/preprocess.o HOSTCC scripts/kconfig/symbol.o HOSTCC scripts/kconfig/util.o HOSTLD scripts/kconfig/conf # # configuration written to .config # Compiling kernel-headers scripts (6.1.99-vendor-rk35xx) using 8 CPUs - please wait ... SYNC include/config/auto.conf.cmd HOSTCC scripts/dtc/flattree.o HOSTCC scripts/dtc/dtc.o HOSTCC scripts/dtc/fstree.o HOSTCC scripts/dtc/data.o HOSTCC scripts/dtc/livetree.o HOSTCC scripts/dtc/treesource.o HOSTCC scripts/dtc/srcpos.o HOSTCC scripts/dtc/checks.o HOSTCC scripts/dtc/util.o LEX scripts/dtc/dtc-lexer.lex.c YACC scripts/dtc/dtc-parser.tab.[ch] HOSTCC scripts/dtc/libfdt/fdt.o HOSTCC scripts/dtc/libfdt/fdt_ro.o HOSTCC scripts/dtc/libfdt/fdt_wip.o HOSTCC scripts/dtc/libfdt/fdt_sw.o HOSTCC scripts/dtc/libfdt/fdt_rw.o HOSTCC scripts/dtc/libfdt/fdt_strerror.o HOSTCC scripts/dtc/libfdt/fdt_empty_tree.o HOSTCC scripts/dtc/libfdt/fdt_addresses.o HOSTCC scripts/dtc/libfdt/fdt_overlay.o HOSTCC scripts/dtc/fdtoverlay.o HOSTCC scripts/dtc/dtc-lexer.lex.o HOSTCC scripts/dtc/dtc-parser.tab.o HOSTLD scripts/dtc/fdtoverlay HOSTLD scripts/dtc/dtc HOSTCC scripts/kallsyms HOSTCC scripts/sorttable HOSTCC scripts/resource_tool HOSTCC scripts/asn1_compiler HOSTCC scripts/genksyms/genksyms.o YACC scripts/genksyms/parse.tab.[ch] HOSTCC scripts/selinux/mdp/mdp HOSTCC scripts/selinux/genheaders/genheaders LEX scripts/genksyms/lex.lex.c HOSTCC scripts/genksyms/parse.tab.o HOSTCC scripts/genksyms/lex.lex.o HOSTLD scripts/genksyms/genksyms Compiling kernel-headers scripts/mod (6.1.99-vendor-rk35xx) using 8 CPUs - please wait ... CC scripts/mod/empty.o HOSTCC scripts/mod/mk_elfconfig CC scripts/mod/devicetable-offsets.s UPD scripts/mod/devicetable-offsets.h MKELF scripts/mod/elfconfig.h HOSTCC scripts/mod/modpost.o HOSTCC scripts/mod/file2alias.o HOSTCC scripts/mod/sumversion.o HOSTLD scripts/mod/modpost MODPOST scripts/mod/Module.symvers Done compiling kernel-headers (6.1.99-vendor-rk35xx). Done compiling kernel-headers tools (6.1.99-vendor-rk35xx). Armbian 'linux-headers-vendor-rk35xx' for '6.1.99-vendor-rk35xx': 'postinst' finishing. Setting up tzdata (2025b-0+deb12u1) ... Current default time zone: 'Europe/Berlin' Local time is now: Tue Apr 1 16:15:44 CEST 2025. Universal Time is now: Tue Apr 1 14:15:44 UTC 2025. Run 'dpkg-reconfigure tzdata' if you wish to change it. Setting up armbian-config (25.5.0-trunk.325.0401.114753) ... Setting up firefox-nightly (139.0a1~20250401094015) ... Setting up libgs10-common (10.0.0~dfsg-11+deb12u7) ... Setting up libgs10:arm64 (10.0.0~dfsg-11+deb12u7) ... Setting up ghostscript (10.0.0~dfsg-11+deb12u7) ... Setting up ghostscript-x:arm64 (10.0.0~dfsg-11+deb12u7) ... Processing triggers for mailcap (3.70+nmu1) ... Processing triggers for desktop-file-utils (0.26-1) ... Processing triggers for hicolor-icon-theme (0.17-2) ... Processing triggers for libc-bin (2.36-9+deb12u10) ... Processing triggers for man-db (2.11.2-2) ... Log ended: 2025-04-01 16:15:46 Log started: 2025-04-02 09:42:43 (Reading database ... 218527 files and directories currently installed.) Preparing to unpack .../armbian-bsp-cli-orangepi5-plus-vendor_25.2.3_arm64.deb ... Armbian 'armbian-bsp-cli-orangepi5-plus-vendor' for '1-PCe1b9-V4064-H2670-B1e5d-R756d': 'preinst' starting. Armbian 'armbian-bsp-cli-orangepi5-plus-vendor' for '1-PCe1b9-V4064-H2670-B1e5d-R756d': 'preinst' finishing. Unpacking armbian-bsp-cli-orangepi5-plus-vendor (25.2.3) over (25.2.2) ... Armbian 'armbian-bsp-cli-orangepi5-plus-vendor' for '1-PC7d0b-Vcff1-H2670-B6e44-R89c9': 'postrm' starting. Armbian 'armbian-bsp-cli-orangepi5-plus-vendor' for '1-PC7d0b-Vcff1-H2670-B6e44-R89c9': 'postrm' finishing. Preparing to unpack .../firefox-nightly_139.0a1~20250401212749_arm64.deb ... Unpacking firefox-nightly (139.0a1~20250401212749) over (139.0a1~20250401094015) ... Preparing to unpack .../linux-headers-vendor-rk35xx_25.2.3_arm64.deb ... Armbian 'linux-headers-vendor-rk35xx' for '6.1.99-vendor-rk35xx': 'prerm' starting. Cleaning directory /usr/src/linux-headers-6.1.99-vendor-rk35xx ... Armbian 'linux-headers-vendor-rk35xx' for '6.1.99-vendor-rk35xx': 'prerm' finishing. Armbian 'linux-headers-vendor-rk35xx' for '6.1.99-vendor-rk35xx': 'preinst' starting. Armbian 'linux-headers-vendor-rk35xx' for '6.1.99-vendor-rk35xx': 'preinst' finishing. Unpacking linux-headers-vendor-rk35xx (25.2.3) over (25.2.3) ... Preparing to unpack .../linux-image-vendor-rk35xx_25.2.3_arm64.deb ... Armbian 'linux-image-vendor-rk35xx' for '6.1.99-vendor-rk35xx': 'prerm' starting. Armbian 'linux-image-vendor-rk35xx' for '6.1.99-vendor-rk35xx': 'prerm' finishing. Armbian 'linux-image-vendor-rk35xx' for '6.1.99-vendor-rk35xx': 'preinst' starting. Armbian 'linux-image-vendor-rk35xx' for '6.1.99-vendor-rk35xx': 'preinst' finishing. Unpacking linux-image-vendor-rk35xx (25.2.3) over (25.2.3) ... Armbian 'linux-image-vendor-rk35xx' for '6.1.99-vendor-rk35xx': 'postrm' starting. Armbian 'linux-image-vendor-rk35xx' for '6.1.99-vendor-rk35xx': 'postrm' finishing. Setting up linux-image-vendor-rk35xx (25.2.3) ... Armbian 'linux-image-vendor-rk35xx' for '6.1.99-vendor-rk35xx': 'postinst' starting. dkms: running auto installation service for kernel 6.1.99-vendor-rk35xx. dkms: autoinstall for kernel: 6.1.99-vendor-rk35xx. update-initramfs: Generating /boot/initrd.img-6.1.99-vendor-rk35xx update-initramfs: Armbian: Converting to u-boot format: /boot/uInitrd-6.1.99-vendor-rk35xx Image Name: uInitrd Created: Wed Apr 2 09:43:11 2025 Image Type: AArch64 Linux RAMDisk Image (gzip compressed) Data Size: 17096044 Bytes = 16695.36 KiB = 16.30 MiB Load Address: 00000000 Entry Point: 00000000 update-initramfs: Armbian: Symlinking /boot/uInitrd-6.1.99-vendor-rk35xx to /boot/uInitrd '/boot/uInitrd' -> 'uInitrd-6.1.99-vendor-rk35xx' update-initramfs: Armbian: done. Armbian: update last-installed kernel symlink to 'Image'... '/boot/Image' -> 'vmlinuz-6.1.99-vendor-rk35xx' Armbian: Debian compat: linux-update-symlinks install 6.1.99-vendor-rk35xx boot/vmlinuz-6.1.99-vendor-rk35xx Armbian 'linux-image-vendor-rk35xx' for '6.1.99-vendor-rk35xx': 'postinst' finishing. Setting up linux-headers-vendor-rk35xx (25.2.3) ... Armbian 'linux-headers-vendor-rk35xx' for '6.1.99-vendor-rk35xx': 'postinst' starting. Configuring kernel-headers (6.1.99-vendor-rk35xx) - please wait ... HOSTCC scripts/basic/fixdep HOSTCC scripts/kconfig/conf.o HOSTCC scripts/kconfig/confdata.o HOSTCC scripts/kconfig/expr.o LEX scripts/kconfig/lexer.lex.c YACC scripts/kconfig/parser.tab.[ch] HOSTCC scripts/kconfig/lexer.lex.o HOSTCC scripts/kconfig/menu.o HOSTCC scripts/kconfig/parser.tab.o HOSTCC scripts/kconfig/preprocess.o HOSTCC scripts/kconfig/symbol.o HOSTCC scripts/kconfig/util.o HOSTLD scripts/kconfig/conf # # configuration written to .config # Compiling kernel-headers scripts (6.1.99-vendor-rk35xx) using 8 CPUs - please wait ... SYNC include/config/auto.conf.cmd HOSTCC scripts/dtc/dtc.o HOSTCC scripts/dtc/flattree.o HOSTCC scripts/dtc/fstree.o HOSTCC scripts/dtc/data.o HOSTCC scripts/dtc/livetree.o HOSTCC scripts/dtc/srcpos.o HOSTCC scripts/dtc/treesource.o HOSTCC scripts/dtc/checks.o HOSTCC scripts/dtc/util.o LEX scripts/dtc/dtc-lexer.lex.c YACC scripts/dtc/dtc-parser.tab.[ch] HOSTCC scripts/dtc/libfdt/fdt.o HOSTCC scripts/dtc/libfdt/fdt_ro.o HOSTCC scripts/dtc/libfdt/fdt_wip.o HOSTCC scripts/dtc/libfdt/fdt_sw.o HOSTCC scripts/dtc/libfdt/fdt_rw.o HOSTCC scripts/dtc/libfdt/fdt_strerror.o HOSTCC scripts/dtc/libfdt/fdt_empty_tree.o HOSTCC scripts/dtc/libfdt/fdt_addresses.o HOSTCC scripts/dtc/libfdt/fdt_overlay.o HOSTCC scripts/dtc/fdtoverlay.o HOSTCC scripts/dtc/dtc-lexer.lex.o HOSTCC scripts/dtc/dtc-parser.tab.o HOSTLD scripts/dtc/fdtoverlay HOSTLD scripts/dtc/dtc HOSTCC scripts/kallsyms HOSTCC scripts/resource_tool HOSTCC scripts/sorttable HOSTCC scripts/asn1_compiler HOSTCC scripts/genksyms/genksyms.o YACC scripts/genksyms/parse.tab.[ch] HOSTCC scripts/selinux/genheaders/genheaders HOSTCC scripts/selinux/mdp/mdp LEX scripts/genksyms/lex.lex.c HOSTCC scripts/genksyms/parse.tab.o HOSTCC scripts/genksyms/lex.lex.o HOSTLD scripts/genksyms/genksyms Compiling kernel-headers scripts/mod (6.1.99-vendor-rk35xx) using 8 CPUs - please wait ... CC scripts/mod/empty.o HOSTCC scripts/mod/mk_elfconfig CC scripts/mod/devicetable-offsets.s UPD scripts/mod/devicetable-offsets.h MKELF scripts/mod/elfconfig.h HOSTCC scripts/mod/modpost.o HOSTCC scripts/mod/sumversion.o HOSTCC scripts/mod/file2alias.o HOSTLD scripts/mod/modpost MODPOST scripts/mod/Module.symvers Done compiling kernel-headers (6.1.99-vendor-rk35xx). Done compiling kernel-headers tools (6.1.99-vendor-rk35xx). Armbian 'linux-headers-vendor-rk35xx' for '6.1.99-vendor-rk35xx': 'postinst' finishing. Setting up armbian-bsp-cli-orangepi5-plus-vendor (25.2.3) ... Armbian 'armbian-bsp-cli-orangepi5-plus-vendor' for '1-PCe1b9-V4064-H2670-B1e5d-R756d': 'postinst' starting. Armbian 'armbian-bsp-cli-orangepi5-plus-vendor' for '1-PCe1b9-V4064-H2670-B1e5d-R756d': 'postinst' finishing. Setting up firefox-nightly (139.0a1~20250401212749) ... Processing triggers for initramfs-tools (0.142+deb12u1) ... update-initramfs: Generating /boot/initrd.img-6.12.12+bpo-arm64-16k W: Possible missing firmware /lib/firmware/rtl_nic/rtl8126a-3.fw for module r8169 W: Possible missing firmware /lib/firmware/rtl_nic/rtl8126a-2.fw for module r8169 update-initramfs: Armbian: Converting to u-boot format: /boot/uInitrd-6.12.12+bpo-arm64-16k Image Name: uInitrd Created: Wed Apr 2 09:44:31 2025 Image Type: AArch64 Linux RAMDisk Image (gzip compressed) Data Size: 57076607 Bytes = 55738.87 KiB = 54.43 MiB Load Address: 00000000 Entry Point: 00000000 update-initramfs: Armbian: Symlinking /boot/uInitrd-6.12.12+bpo-arm64-16k to /boot/uInitrd '/boot/uInitrd' -> 'uInitrd-6.12.12+bpo-arm64-16k' update-initramfs: Armbian: done. Processing triggers for hicolor-icon-theme (0.17-2) ... Processing triggers for man-db (2.11.2-2) ... Processing triggers for mailcap (3.70+nmu1) ... Processing triggers for desktop-file-utils (0.26-1) ... Log ended: 2025-04-02 09:44:34 Any tips how to resolve this and boot from the nvme again? I know initramfs exists and I can wrap my mind arround it what it does, but in the last years never had to solve anything regarding it. I do not know where to look or start debugging

Hello, this is my first time setting up orange pi + Armbian Linux. I'm a linux newbie. I've been trying to install various version of the Debian 12 Desktop images working. I can always get into it via SSH but never get a display out via HDMI except fro Ubuntu 24.04 Noble Gnome Images Success Armbian_25.2.1_Orangepi5-plus_noble_vendor_6.1.99_gnome_desktop Images Failed Armbian_25.2.1_Orangepi5-plus_bookworm_current_6.12.13_cinnamon-backported-mesa_desktop Armbian_25.2.1_Orangepi5-plus_bookworm_current_6.12.13_xfce_desktop After SSH and setting up roo/user accounts I always get to the message Now starting desktop environment... But it doesn't do anything afterwards. I've done initial troubleshooting verifying that HDMI cables work using different monitors Trying different power supplies trying different microSDs Is there something else I can check on the Debian bookworm variants to see what the issue is? Thanks for taking a look.

Where has enabling things like I2C moved to ? I do not see it any more in armbian-config (at least on the Orange Pi 5 plus image) Thanks