Active threads

Indeed. Comparing sources between kernel 6.12 and 6.15, I could only spot one difference in the drm_atomic_helper_connector_hdmi_check() function so I have tested applying this via a patch and the build compiled successfully. Testing the build I found that reboot now works and shutdown finishes with just a blank display. If it is indeed the same issue then this patch will likely fix the problem. Based on what I found it may impact certain Rockchip Socs also: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/drivers/gpu/drm/display/drm_hdmi_state_helper.c?h=linux-6.15.y&id=0d337b40ca1e532af42516d9e9024baad466319a drv-drm-atomic-helper-null-pointer-fix.patch Thanks Ryzer

And how to compile openvfd with this patch? How to apply this patch to openvfd?

Not supported by forum software. Keeping Facebook and Google operational requires constant attention and adjustement, while others worked so far without troubles.

Added instructions for joining your home lab: https://docs.armbian.com/WifiPerformance/#adding-a-new-device

Hi and thank you for the advice. The USB end of the dongle goes to my desktop PC. I compared the time stamps of the last issue and found that the PC was actually switched off during the last issue, having been switched on 10 minutes after the last sysrq log entry. So for the moment I will watch the findings of auditd, although the startup msgs from yesterday looked somewhat suspicious (?): 2025-06-23T18:23:09.799581+02:00 bananapipro2 systemd[1]: Starting auditd.service - Security Auditing Service... 2025-06-23T18:23:09.910646+02:00 bananapipro2 auditd[18408]: Audit daemon is low on disk space for logging 2025-06-23T18:23:09.911684+02:00 bananapipro2 auditd[18408]: Audit daemon is suspending logging due to low disk space. 2025-06-23T18:23:09.912308+02:00 bananapipro2 auditd[18408]: No plugins found, not dispatching events 2025-06-23T18:23:09.917468+02:00 bananapipro2 auditd[18408]: Init complete, auditd 3.0.9 listening for events (startup state enable) 2025-06-23T18:23:10.181350+02:00 bananapipro2 systemd[1]: Started auditd.service - Security Auditing Service. Greetings.

That should make it. You can always try to see if it works and search online if not.

Armbian_25.2.2_Rock-5-itx_noble_vendor_6.1.99_gnome_desktop.img.xz I first tried this, as it was the first version offered at the top of the page. No matter what I tried, sound would *not* work. Not speakers, not HDMI, nada, zip. I then started trying earlier versions further down the page. Armbian_25.2.2_Rock-5-itx_bookworm_vendor_6.1.99_cinnamon-backported-mesa_desktop.img.xz And this one, sound *did* work, at least through the speaker jack anyway, but I suspect HDMI would too. I'm really suspecting something kernel related is going here (that "Rockchip BSP" note right above it makes me suspect that). In any case, I'd like to use the kernel where sound is working and put a gnome shell in front of it. Which I take means digging into the build system for armbian? I can figure that out on my own but before I get started on that, what I'm looking for from the forumistas, is an indication of which specific kernel I need to use to make sure sound works. What do I need to make sure to specify so I get the behavior of that second install that worked? And Cinnamon may be better or something, but gnome is what I'm used to.

FYI. HDMI out is broken on those board at the moment. Try to access the board remotely. We don't have people to maintain those old boards.

looks like a kernel oops does the unit run properly afterwards?

Thank you for that information. From a cursory look, it seems as if that is only binary images, no source (violating GPL).

I will try to make that easier and more automatic with APA, eventually.

Thank you for letting us know as it allows an interested party to more easily bisect the regression.

download all files attenmented . sudo cp *.dtbo /boot/dtb/allwinner/overlay open /boot/armbianEnv.txt , add this line: overlays=spi-spidev spidev1_1 and reboot, you should find and use /dev/spidev1.1 sun50i-h616-spidev1_0.dtbo sun50i-h616-spidev1_0.dtso sun50i-h616-spidev1_1.dtbo sun50i-h616-spidev1_1.dtso

Moved to Community supported forum as this isn't a standard support board.

OrangePi 4A Bluetooth Mouse Keyboard connectivity issue Solved The solution to the problem when mouse pairs / connects with BT but doesnt work Prebuilt kernel files are available https://github.com/defencedog/orangepi4A/blob/main/Bluetooth%20Mouse%20Not%20Working%20Solved.md

True. Also on most computers we have eth0 Not just eth Devices naming is a cosmetic thing from the outside / user perspection, while it has consistency issue from the inside and currently breaks initial (default netplan) configuration. Our job is not to tell user how to configure his network, but that network devices gets up at first boot. Now they do. Job done.

From the picture - I can only guess that kernel package was somehow not upgraded properly as kernel image files are missing. Perhaps they were removed by accident or there was some disk / file system troubles involved. @Chris007 Try hints from here: https://docs.armbian.com/User-Guide_Troubleshooting/

This is being worked on https://lore.kernel.org/linux-sunxi/20250526002924.2567843-1-james.hilliard1@gmail.com/T/#t There is a version of this that was ported over from a vendor kernel to Armbian. https://github.com/armbian/build/pull/6617

Okay, then you have to adjust the source to mitigate the issue. Also log excerpts are often useless. My random guess is that uboot is some old outdated version depending on python2 which has been deprecated years ago.

Last month in Nice, active media developers came together for the annual Linux Media Summit to exchange insights and tackle ongoing challenges in the media subsystem. Here’s a brief summary of the key discussions and upcoming areas of focus. View the full article

duplicate

To anyone this may help, removing hc4 related packages and replacing them with c4 packages did the job. Only to discover that, for whatever reason, I actually had an HC4 board and convince myself that it was a C4 ... Anyway, the reverse process also worked as expected and my board is now running 25.051.1 happily, except for the samsung SSD not recognized at boot, and requires to be hot plugged just after the linux kernel starts in order to be seen by the system, as it is described in other threads.

@junji. Can you explain me how you proceed to boot this OS image Armbian-unofficial_25.05.0-trunk_X96q-lpddr3-v1-3_bookworm_edge_6.12.11_xfce_desktop.img.xz ?

I have same hardware issue here. Did you fix this problem?

For a few weeks I've been using the latest official release from May 26, 2025, running just fine from my NVME drive. But then I turned it on and at the screen where you get the Amrbian grey/red logo in the middle of the screen and the spinning circle, it went no further. The spinning circle would either stop rotating or disappear after a minute or so. I can SSH into the device. But when I use remote desktop from a Windows PC, the full and functioning desktop is there. It's just not on my TV screen any more. I've done the usual HDMI cable testing and powering off the TV completely, but no change. The fact that the desktop is accessible remotely does indicate that it must be loading in some fashion. Took a log here: https://paste.next.armbian.com/qococumoga