Search the Community

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

I have Linux 6.1.99-vendor-rk35xx #1 SMP Wed Mar 19 11:16:36 UTC 2025 aarch64 aarch64 aarch64 GNU/Linux on my Orange Pi 5 Plus. Trying to setup VM with CPU host-passthrough but can only use cortex-a76 custom with TCG. If I try to use virt type KVM and host-passthrough on virt-manager I get: Error starting domain: internal error: process exited while connecting to monitor: 2025-03-26T08:55:56.040008Z qemu-system-aarch64: Failed to put registers after init: Invalid argument Traceback (most recent call last): File "/usr/share/virt-manager/virtManager/asyncjob.py", line 72, in cb_wrapper callback(asyncjob, *args, **kwargs) File "/usr/share/virt-manager/virtManager/asyncjob.py", line 108, in tmpcb callback(*args, **kwargs) File "/usr/share/virt-manager/virtManager/object/libvirtobject.py", line 57, in newfn ret = fn(self, *args, **kwargs) ^^^^^^^^^^^^^^^^^^^^^^^^^ File "/usr/share/virt-manager/virtManager/object/domain.py", line 1402, in startup self._backend.create() File "/usr/lib/python3/dist-packages/libvirt.py", line 1379, in create raise libvirtError('virDomainCreate() failed') libvirt.libvirtError: internal error: process exited while connecting to monitor: 2025-03-26T08:55:56.040008Z qemu-system-aarch64: Failed to put registers after init: Invalid argument

The images Debian Bookworm "Minimal/IOT images with Armbian Linux v6.12" generate what I understand is bad partition information. Once flashed to the SD card, the partition won't be recognised by Linux hinted by the message "couldn't find valid filesystem superblock", therefore they can't be mounted. The desktop image is fine though and the partitions generated after flashing into the SD card are recognised by the "disks" application. I've also tried with the Ubuntu-rockchip image which also generates correct/mountable partition information. I've tested this for the minimal images for OrangePi Max as well as OrangePi 5 Plus. The images were flashed with both "Raspberry Pi Imager" and "imageusb", since for some reason the recommended "USBImager" won't list my usb devices on Windows

Since at least one week I find the system every morning with solid red led, waiting for a command in uboot. When looking at the journal messages, the last messages are always: Feb 10 23:45:01 etnas2 CRON[5176]: pam_unix(cron:session): session opened for user root(uid=0) by (uid=0) Feb 10 23:45:01 etnas2 CRON[5177]: (root) CMD (/usr/lib/armbian/armbian-truncate-logs) Feb 10 23:45:01 etnas2 CRON[5176]: pam_unix(cron:session): session closed for user root Feb 11 00:00:01 etnas2 CRON[5213]: pam_unix(cron:session): session opened for user root(uid=0) by (uid=0) Feb 11 00:00:01 etnas2 CRON[5212]: pam_unix(cron:session): session opened for user root(uid=0) by (uid=0) Feb 11 00:00:01 etnas2 CRON[5215]: (root) CMD (/usr/lib/armbian/armbian-apt-updates) Feb 11 00:00:01 etnas2 CRON[5214]: (root) CMD (/usr/lib/armbian/armbian-truncate-logs) Feb 11 00:00:01 etnas2 CRON[5212]: pam_unix(cron:session): session closed for user root Feb 11 00:00:03 etnas2 CRON[5213]: pam_unix(cron:session): session closed for user root Feb 11 00:00:49 etnas2 systemd[1]: Starting dpkg-db-backup.service - Daily dpkg database backup service... Feb 11 00:00:49 etnas2 systemd[1]: Starting logrotate.service - Rotate log files... Feb 11 00:00:49 etnas2 systemd[1]: dpkg-db-backup.service: Deactivated successfully. Feb 11 00:00:49 etnas2 systemd[1]: Finished dpkg-db-backup.service - Daily dpkg database backup service. Feb 11 00:00:49 etnas2 armbian-ramlog[5278]: Tue Feb 11 12:00:49 AM CET 2025: Syncing logs to storage Feb 11 00:00:49 etnas2 armbian-ramlog[5281]: sending incremental file list Feb 11 00:00:49 etnas2 armbian-ramlog[5281]: ./ Feb 11 00:00:49 etnas2 armbian-ramlog[5281]: Xorg.0.log Feb 11 00:00:49 etnas2 armbian-ramlog[5281]: Xorg.0.log.old Feb 11 00:00:49 etnas2 armbian-ramlog[5281]: armbian-hardware-monitor.log Feb 11 00:00:49 etnas2 armbian-ramlog[5281]: auth.log Feb 11 00:00:49 etnas2 armbian-ramlog[5281]: boot.log Feb 11 00:00:49 etnas2 armbian-ramlog[5281]: btmp Feb 11 00:00:49 etnas2 armbian-ramlog[5281]: cron.log Feb 11 00:00:49 etnas2 armbian-ramlog[5281]: kern.log Feb 11 00:00:49 etnas2 armbian-ramlog[5281]: lastlog Feb 11 00:00:49 etnas2 armbian-ramlog[5281]: syslog Feb 11 00:00:50 etnas2 armbian-ramlog[5281]: user.log Feb 11 00:00:50 etnas2 armbian-ramlog[5281]: wtmp Feb 11 00:00:50 etnas2 armbian-ramlog[5281]: cups/access_log Feb 11 00:00:50 etnas2 armbian-ramlog[5281]: lightdm/ Feb 11 00:00:50 etnas2 armbian-ramlog[5281]: lightdm/lightdm.log Feb 11 00:00:50 etnas2 armbian-ramlog[5281]: lightdm/lightdm.log.old Feb 11 00:00:50 etnas2 armbian-ramlog[5281]: lightdm/seat0-greeter.log Feb 11 00:00:50 etnas2 armbian-ramlog[5281]: lightdm/seat0-greeter.log.old Feb 11 00:00:50 etnas2 armbian-ramlog[5281]: lightdm/x-0.log Feb 11 00:00:50 etnas2 armbian-ramlog[5281]: lightdm/x-0.log.old Feb 11 00:00:50 etnas2 armbian-ramlog[5281]: samba/log.nmbd Feb 11 00:00:50 etnas2 armbian-ramlog[5281]: samba/log.smbd Feb 11 00:00:50 etnas2 armbian-ramlog[5281]: sent 3,469,661 bytes received 448 bytes 2,313,406.00 bytes/sec Feb 11 00:00:50 etnas2 armbian-ramlog[5281]: total size is 4,794,812 speedup is 1.38 Feb 11 00:00:50 etnas2 systemd-journald[588]: Time spent on flushing to /var/log/journal/1141762e43884d8b9eb5d35b11be4daa is 55.926ms for 1057 entries. Feb 11 00:00:50 etnas2 systemd-journald[588]: System Journal (/var/log/journal/1141762e43884d8b9eb5d35b11be4daa) is 17.4M, max 20.0M, 2.5M free. Feb 11 00:00:50 etnas2 systemd-journald[588]: Received client request to flush runtime journal. Feb 11 00:00:50 etnas2 systemd-journald[588]: Data hash table of /var/log/journal/1141762e43884d8b9eb5d35b11be4daa/system.journal has a fill level at 122.2 (5561 of 4551 items, 2621440 file size, 471 bytes per hash table item), suggesting rotation. Feb 11 00:00:50 etnas2 systemd-journald[588]: /var/log/journal/1141762e43884d8b9eb5d35b11be4daa/system.journal: Journal header limits reached or header out-of-date, rotating. After that no more messages, until the system gets booted again. The issue seems similar to this post. Power supply and system temperatures are fine, the system is running from EMMC memory so issues with SD cards are ruled out. When I boot off e.g. Jonathan Riek's Ubuntu 24.04 using the NVME drive, then all is fine: no nightly crashes. I don't recall this issue when I installed Armbian 24.11.2 back in December, so possibly it came when I upgraded to 24.11.3 using `apt upgrade` (but could be wrong!) I have added the cron job `*/1 * * * * /usr/bin/dmesg > $HOME/kernel-dmesg.txt` as suggested. Looking at `/etc/cron.d` and more precisely `armbian-trunctate-log`, I see that `armbian-trunctate-logs` runs every 15 minutes, but it invokes `armbian-ramlog` in practice only just after mignight probably because `/var/log` is over 75% full. Then `/usr/lib/armbian/armbian-truncate-logs` proceeds to synchronize (using `rsysnc`) the logs files in zram (`/var/log`). After that, the script calls `/usr/sbin/logrotate --force /etc/logrotate.conf` but this rotation takes place on `/var/log.hdd/`. Somehow that does not sound right... I would have thought it would be the other way around.... Finally, it just truncates the files in `/var/log`. That could be dangerous as processes have these files open... Logrotate sends a signal to processes to let them know they should reopen the log files. armbianmonitor -u Thanks in advance for any help.

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 can anyone advise if they have come accross this issue. so somehow HDMIRX seems to be the hdmi input controller starts to freak out for no reason there is nothing plugged into it EVER and will randomly start to outpur this to console im thinking maybe the HDMIRX is faulty and want to remove it, I have tried removing it removed the DTB , decompiled and edited and removed it from DTB, tied to blacklist it but with no effect it does not stop spamming and the device [ 89.603095] rk_hdmirx fdee0000.hdmirx-controller: hdmirx_phy_register_write wait cr write done failed! [ 89.613765] rk_hdmirx fdee0000.hdmirx-controller: hdmirx_phy_register_write wait cr write done failed! [ 89.624917] rk_hdmirx fdee0000.hdmirx-controller: hdmirx_phy_register_write wait cr write done failed! [ 89.635554] rk_hdmirx fdee0000.hdmirx-controller: hdmirx_phy_register_write wait cr write done failed! [ 89.704256] rk_hdmirx fdee0000.hdmirx-controller: hdmirx_controller_init wait timer base lock failed! not for my last attemt i want to check if anyone has the .config for the kernel and perhaps knows what the driver / module is called this way I am guaranteed i will not see it again. Note: I have reinsatlled multiple distros to check and it keeps happening randomly so any input on this would be great. Much appreciated and thanks in advance.

Hi, I've come from Joshua's 24.04 Server build. I was concerned that the support was dropping off as he's having a well deserved break. I've installed the latest Server build from here. https://dl.armbian.com/orangepi5-plus/Noble_current_server-kisak Works fine, have moved it to EMMC and removed the SD card. I use a USB power meter to see how much juice it uses. I noticed this build uses about 20 to 25% more when idle or under load compared to Josh's 6.1 kernel build. I am suspecting 6.12 has enabled more hardware in the OPi5+ and this is the reason. Is there a way to disable some of the HW to lower the idle power usage? On average it uses 5w on idle. Thanks. Loving the Armbian build.

I'm adding this here as I want to contribute to the community, but I'm still not sure how. I've been playing with Armbian Build lately and found it's great for quick build images for testing purposes before it's officially made available. So I started build my own images with i3, mate, kde, and I noticed that, in my personal taste, the one that was better suited for my needs was Sway, but there's no desktop image with it. So I built a Server version and start installing it. I know it may not be of interest of everybody, so I was planning to do it for myself, so I can continue building with the interface, but having Sway "automatically" installed. If/when I'm able to do this, I could put this in CSC mode in the repo, or I shouldn't do that as it's going to bloat the system more as there's no interest in having yet another WM/DE available? I'm thinking of this as an alternative to i3,as I noticed that, in my board, Wayland is performing much better than XOrg/X11.

I'm using Orange Pi 5 Plus, I've updated to latest by apt upgrade but seems to be stuck on old version as you can see 25.2.2 but kernel is still 6.1.75 : # uname -a Linux abeure 6.1.75-vendor-rk35xx #1 SMP Wed Aug 21 11:45:59 UTC 2024 aarch64 GNU/Linux # cat /var/log/apt/history.log Start-Date: 2025-02-25 01:00:39 Commandline: /usr/bin/unattended-upgrade Upgrade: armbian-firmware:arm64 (25.2.1, 25.2.2) End-Date: 2025-02-25 01:00:42 Start-Date: 2025-02-25 01:01:10 Commandline: /usr/bin/unattended-upgrade Upgrade: linux-u-boot-orangepi5-plus-vendor:arm64 (24.11.1, 25.2.2) End-Date: 2025-02-25 01:01:11 Latest version https://www.armbian.com/orange-pi-5-plus/ does not seems to be fetched. Armbian 25.2.1 Bookworm Minimal / IOT Kernel: 6.1.99, Size: 295.5 MB, Release date: Feb 15, 2025 Can you explain what i've missed ?

Happy New Year for all, My old Samsung Monitor stopped working some days ago, and I dont know if it will be fixed, so I decided to buy a new LG 27'' Monitor. My Zorin OS and Windows on X64, Raspbian and Ubuntu On Raspberry PIs are working properly. But booting Armbian - Ubuntu 24.04 (Noble) on "Orange PI 5" and "Orange PI 5 Plus" My New monitor refuses to show any image (only black screen). "Orange PI OS XFCE" on "Orange PI 5" is OK on my new monitor. I took a litle look at boot files but I didn't find anything to fix this problem. Any idea to solve this problem??? Thanks, Cury

I have built quite a few Debian12 Desktop images from github.com/armbian/build for a Debian Bookworm/XFCE/Vendor Kernel environment and noticed that recent vendor kernels do not have I2C-2.M0 as a kernel module listed within armbian-config. It appears that only two kernel modules are to be found, one being Panthos, the other involving a change in frequence of some item. This image does include I2C-2.mo: Armbian-unofficial_25.02.0-trunk_Orangepi5-plus_bookworm_vendor_6.1.84_xfce_desktop.img which includes kernel: Linux Atlas 6.1.99-vendor-rk35xx #1 SMP Fri Feb 21 18:11:03 UTC 2025 aarch64 GNU/Linux But these images do not contain the I2C-2.m0 kernel modules: Armbian-unofficial_25.02.0-trunk_Orangepi5-plus_bookworm_vendor_6.1.84_xfce_desktop.img (same kernel build as Ambian 25.0.2.0-trunk listed above sans I2C-2-m0) Armbian-unofficial_25.05.0-trunk_Orangepi5-plus_bookworm_current_6.12.17_xfce_desktop.img Armbian-unofficial_25.05.0-trunk_Orangepi5-plus_bookworm_vendor_6.1.99_xfce_desktop.img Is it now necessary to customize the compile options for the kernel and choose that module for compilation when building newer vendor images? It would make sense (to me at least) to have each build option to have vendor kernels contain the same precompiled kernel modules for simplicity sake. I'm not even sure if the I2C-2.m0 is available or an option in the later vendor kernels to build.

Hello all, i feel i may have made a fatal mistake. I was running Armbian Bookworm server on an Orange PI 5 Plus. All was well until the latest update. After updating, I thought i'd checkout what's changed in arbian-config. I enabled rolling releases and rebooted when prompted. Sadly, the OPI5+ now wont boot. Anything I can do? Or do I need to reinstall everything? Thanks in advaced for anyone taking the time to help Shad

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!

Hi everybody, I installed Deb 12 Cinnamon Armbian flavor on an Orange PI 5 and Orange PI 5 Plus. This: dl.armbian.com/orangepi5-plus/Bookworm_current_cinnamon-backported-mesa I want to test 'virt-manager' but qemu is not available for installation. Error on console: packages are updated me@orangepi5-plus:~$ sudo apt install qemu [sudo] senha me: Lendo listas de pacotes... Pronto Construindo árvore de dependências... Pronto Lendo informação de estado... Pronto package qemu is not available, mas é referenciado por outro pacote. Isto pode significar que o pacote está faltando, ficou obsoleto ou está disponível somente a partir de outra fonte E: O pacote 'qemu' não tem candidato para instalação Is there a chance to have qemu available. armbianmonitor -u https://paste.next.armbian.com/egexohofom Thanks, Cury

I have a new Orange Pi 5 plus 16GB. Seems a pretty cool board and I want to replace my old Rpi 4 for Media center and Home assistant. I tried several distribution but can't get all my stuff working. The OPI5+ is attached to an onkio 5.1 receiver and the receiver go to a FHD TV. What is want to achieve is in Kodi 1. play video with GPU 2. libCec in Kodi to control Onkio volume 3. Passthrough audio Is there a working solution? Thank you

Hello everyone, This is my 1st post on the forum. My intention with this post is not to report a specific issue that I am running into, but more because I would like to collect info and suggestions from people with more experience than myself. I've recently received an Orange Pi 5 Plus and have spent a bit of time exploring operating systems suitable for this system and have settled on the Armbian solution. I'm a HW designer by trade, and have done some SW work, but I do not consider myself proficient in SW at all. I find my way around things, but that's about as far as it goes.... For the my planned use of the OPi5+, I will need eMMC boot (for the improved OS performance and longevity) and access to the various interfaces (mainly SPI and I2C) on the GPIO header. What I have discovered so far: - Version 6.1 of the Armbian built kernel supports the GPIO interfaces quite well (I haven't actually communicated with anything yet, just got the interfaces showing up in /dev), but I could not get it to see the eMMC storage on the board. I tried various different options and flavours of the 6.1 images and I never saw /dev mmcblk0 listed. - Version 6.10 kernel builds were successful at accessing the eMMC (/dev/mmcblk0 was present) and I have successfully transferred the OS to the eMMC storage on the board. However this version of the kernel has a limited number of device tree overlays (mostly different UART options, and one I2C option). I'm assuming that the 6.10 kernel is quite a new build and that more support for the board's IO should be available soon. Did I overlook something on the 6.1 version regarding the eMMC support? Am I missing something regarding overlays in the 6.10 build? My thinking is to stay with 6.10 as it supports eMMC and it's the newest kernel version. Cheers Volt

HI, On one orangepi5B, it seems not possible to have details from u-boot when starting target. The first messages on HDMI start with the kernel root@hn-orangepi5b-450:~# dmesg |head [ 0.000000] Booting Linux on physical CPU 0x0000000000 [0x412fd050] [ 0.000000] Linux version 6.12.0-current-rockchip-rk3588 (build@armbian) (aarch64-linux-gnu-gcc (Ubuntu 11.4.0-1ubuntu1~22.04) 11.4.0, GNU ld (GNU Binutils for Ubuntu) 2.38) #3 SMP PREEMPT Sun Nov 17 22:15:08 UTC 2024 [ 0.000000] KASLR disabled due to lack of seed [ 0.000000] Machine model: Xunlong Orange Pi 5 [ 0.000000] efi: UEFI not found. [ 0.000000] NUMA: Faking a node at [mem 0x0000000000200000-0x00000004ffffffff] [ 0.000000] NODE_DATA(0) allocated [mem 0x4fdf2d380-0x4fdf300ff] [ 0.000000] Zone ranges: [ 0.000000] DMA [mem 0x0000000000200000-0x00000000ffffffff] [ 0.000000] DMA32 empty root@hn-orangepi5b-450:~# root@hn-orangepi5b-450:~# cat /boot/armbianEnv.txt verbosity=7 bootlogo=false console=both overlay_prefix=rockchip-rk3588 fdtfile=rockchip/rk3588s-orangepi-5.dtb rootdev=UUID=dae561f4-e2f2-4686-9748-31eebe9792c9 rootfstype=ext4 usbstoragequirks=0x2537:0x1066:u,0x2537:0x1068:u root@hn-orangepi5b-450:~# Is there one option to change this behaviour ? Best regards

Hi, I've been compiling my own Armbian images since 6.13-rc5, and now 6.13 and I noticed that when I compile i3, youtube videos and webgl tests don't work as great when I compile i3 with mesa-vpu as it does when I compile e.g., cinnamon. I also noticed that the suffix is not -mesa-desktop, only -desktop. Is it as per design and i3 doesn't include mesa at all, or is it some kind of bug? Thanks!

There's a strange issue with my orange pi 5 plus. When I boot into the ubuntu image, everything is fast, stable and zippy. But when I boot into the openmediavault image, it's incredibly slow. Simple operations like apt upgrade crawl. I noticed the cpu frequency is stuck at 408 MHz in htop in the openmediavault image. I ran a test. I opened another console and ran yes. Went back to htop and the frequency was still stuck at 408 MHz with one core pegged at 100% from the yes. So I fired up the ubuntu image and did the same thing. The core was at 100% but the frequency was at 2304mhz on that core. There is something wrong with the openmediavault image. What do I need to do to fix this?

Hello again, Based on the recommendations provided in a previous ticket, I have decided to attempt to build a custom image for the Orangepi 5 Plus. I read the docs provided in the link of that post and noticed that there is no mention of installing the cross complier tool chain for arm in ubuntu 22.04, which I just downloaded for this purpose. Do I need to install those tools or will that be addressed once I clone the git repo and run the compile.sh BOARD=orangepi5-plus ? Also the instructions mention Multipass and Docker, I have a Debian 12 workstation with virt-manager installed, will that work or will I need a dedicated ubuntu 22.04 host, because in that case I can just build on the host and not in a Multipass VM. thanks -ali

Hi everybody, I installed Deb 12 Cinnamon Armbian flavor. This: dl.armbian.com/orangepi5-plus/Bookworm_current_cinnamon-backported-mesa When I open system setup there is no Idiom/Language Icon. So all apps remains in English. Even if I run "sudo dpkg-reconfigure keyboard-configuration" and "sudo dpkg-reconfigure locales" I found an issue running "armbian-config"/localization/change Keyboard layout, on console this msg "setupcon: We are not on the console, the console is left unconfigured." But if I run "sudo dpkg-reconfigure keyboard-configuration" from a terminal window no error. Thanks, Cury

Hi all, I am used to update my systems every day, but this time.... Yesterday, all of a sudden, after an "apt update" command showed to me there was 222 updates available. Wow, there was many updates on KDE, I left it for later, but after finishing my tasks I made the upgrade. After reboot, at login screen, password was accepted but login screen reappears. I tryed many times. I noticed that login was set to "KDE Wayland"... I changed to "KDE X11" and Bingo... Login ok. But Task bar is shown everything to the left and without the apps. All apps used before last logout were reopened, but all of them were located on top left of screen and no way to change the top app, only terminating the top app to access other app. No ALT TAB works. And at botton right of wallpaper it is saying "Plasma 6.3" in other words, unusable... And now, what can I do? If I reinstall .img I cant upgrade anymore??? Thanks from Brazil, Cury .img used to install: “Armbian - unofficial_25.02.0 - trunk_Orangepi5-plus_noble_vendor _ 6.1.84_kde-neon-kisak _ desktop” My system before crash: Operating System: Ubuntu 24.04 (Neon) KDE Plasma Version: 6.2.5 KDE Frameworks Version: 6.10.0 Qt Version: 6.8.1 Kernel Version: 6.1.84-vendor-rk35xx (64-bit) Graphics Platform: Wayland Processors: 4 × ARM Cortex-A 55, 4 × ARM Cortex-A76 Memory: 15.6 GiB of RAM Graphics Processor: Mali-G610 Product Name: Orange Pi 5 Plus

I installed armbian with a vendor kernel 6.1.75-vendor-rk35xx. I want to be sure the kernel is not updated. I used armbian-config and selected "SY203 - Disable Armbian kernel upgrades" Disable Armbian kernel/firmware upgrades Would you like to continue? after selecting "Yes", the menu shows "SY202 - Enable Armbian firmware upgrades" so I check with apt-mark showhold and it returned only "armbian-firmware" Do I have to put my kernel packages on hold? linux-dtb-vendor-rk35xx linux-headers-vendor-rk35xx linux-image-vendor-rk35xx I find misleading the change in the description from SY203 to SY202: kernel -> firmware

Hello Developers, I ran into some issues installing the latest release on an Orange Pi 5 Plus. The images I downloaded are as follows: Armbian_24.11.2_Orangepi5-plus_noble_current_6.12.0_kde-neon-kisak_desktop.img.xz Armbian_24.11.2_Orangepi5-plus_noble_vendor_6.1.75_gnome-kisak_desktop.img.xz The KDE version will install and boot from the 256GB emmc drive, however it only works if there is a 4K HDMI monitor attached to HDMI1, I was not able to get it to display on a 1920x1200 HDMI monitor nor a USB connected or HDMI connected portable display (2560x1440). The Gnome version will boot with any of those 4 types of displays (4K HDMI, 1920x1200 HDMI and USB C or USB C to HDMI portable display) so in the end I would most likely install the GNOME version and then add KDE or Enlightenment packages to it since I don't like GNOME at all (20 yrs Debian/XFCE4 user). There is one issue I have with the GNOME version: It does not detect the emmc drive and only the SD card and the 500 GB NVME drives are showing up in gparted and fdisk. I am looking forward to using Armbian on an Orange Pi 5 Plus as my daily desktop and I hope this can be easily resolved. I am open to using either version as long as I can use a portable USB C or HDMI display with less than 4K resolution. thanks -ali