Igor

Unfortunately I was not able to work on this topic appropriately and thus could not provide any helpful information.
But in the meantime, others have done a lot of work on this topic. Thank you @uablrek for the link.
So I tried and built a new image (from main branch) after https://github.com/armbian/build/pull/8449 had been merged. I can confirm that the Rock 4SE now boots with this version.
 
Thanks to everyone involved for the solution!

fussing about duplicate post, yes, same problem, different but identical machine.  I have several of these bpi-m5's in service here, And its happened several times while I have reached the age of 90 where short term memory is only weeks.
 
This then. with your link to systemd stuff, is bad code you inherited, blindly. My solution to that was/is to make hostname immutable after editing it.  Much simpler than reading thru half a gigabyte of purposely opaque docs looking for clues.
 
With the advent of led backlighting for monitor screens, CRT screens no longer get burnt in.  So one thing badly needed is a bright red, much bigger mouse pointer that moves at about 1/10 th of its present speed, and an easy way to totally disable screen and mouse blanking. On a 3d printer, they are both a hindrance, adding 10 to 30 seconds to taking action when a printer malfunctions.   And because I use this OS heavily, I also donate a smallish bit of my SS income to your cause on a monthly basis.  Thank you Igor.

@Igor Thanks.  
The weird noise is resolved. It was HDMI cable.
 

up all night, finally got it working. list of stuff I did: download latest 2505 bookworm-xfce and reburn the u-us card 3 times. copied 40 entry /etc/hosts file from working machine. edit /etc/hostname to change it to unique name amanda, then make it immutable as that did not survive a reboot. rm 10-* in etc/netplan, rename armbian.yaml to 10-armbian.yam editing it as needed, and edit /etc/nsswitch.conf to make network setup start as "hostname files dns" rebooting after each stage. So hostname now stays at amanda, and nsswitch.conf works as ordered. I can ping yahoo.com in addition to my other local machines and have now updated 208 pkgs. rebooted looks ok. Now I can get back to making a 20T lvm out of 5 4T SSD's,  But first some breakfast and a shot of insulin, and a nap while the local weather settles, its poured piss out of a cowbarn boot most of the night.  Thank you for the links, they were educational.

@amazingfate can tell that.
https://github.com/armbian/build/blob/main/config/boards/oneplus-kebab.conf#L3

Vendor kernel 6.1.y with mesa-vpu extension https://github.com/armbian/os/blob/main/userpatches/targets-extensions.map#L58 (with patched Chromium) is the only way to come close to what you want.
 
Only this:

Whatever help you can provide know that it is truly appreciated!
 
I will follow your suggestion and try a different kernel and report back my findings, thank you!

Welcome to Armbian forums. Most of general questions are answered in:
https://docs.armbian.com/
https://docs.armbian.com/User-Guide_Board-Support-Rules/
 
Remove those you will get answers there ...

Ok, thank you!

I've made an issue on github:
https://github.com/armbian/build/issues/8403

I don't have time to work on this right away, so to make sure this does not fall off the radar, I opened a ticket in the tracker.

Currently I am running HA supervised on Debian 12 bookworm. Debian boots from USB drive without any issue. So your suggestion should work I believe. Thanks for the suggestion. You are quick as always to reply.

Works with an apt update && upgrade. missing DTB is present, and boots ok.
Thank you for the fast fix team.

If you plan to start from scratch and you don't want to wait hours until repository is updated, yes, rather download and use latest image. Upcoming fix will solve this problem for everyone that still use old image.

This 100% works - we are even running daily automated tests on Bookworm, Jammy and Noble.
https://github.com/armbian/os/actions/runs/15362508470/job/43232345405
 
Manual test on Rockchip64 (Bananapi M7) with 6.12.28-current, latest kernel from daily repository.

System: https://paste.armbian.com/tiwisuhugi
 
Here is build log:
 

And I have ruled out that this is Armbian OS problem.

https://github.com/armbian/build/pull/8334

Impossible.
 

This might help you: https://github.com/amazingfate/armbian-xiaomi-elish/wiki/Flashing-Guide

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 🙂
 

Hi, I would like to share my recent work: a cheap USB Audio Class 1.0 (UAC) input to UAC 2.0 output converter.
 
For folks that may not understand why I have this crazy idea, here is the background:
For some shitty reasons, PS5 does not support outputting audio through certain USB sound card, and that is because PS5 only supports very old USB sound card (UAC 1.0), and usually high end speakers or sound cards would use newer, better UAC 2.0 protocol.
So, this shitty thing happens to me, when I thought my EDIFIER S880 speaker would be a plus for my gaming experience. EDIFIER S880 has a UAC 2.0 in input source, so my PS5 does not support that. So, what I can do is to use another 3.5 jack to connect the speaker to my PS5.
Unfortunately, there is a staticky buzz sound throughout this channel. What's even worse is that EDIFIER S880 has 6 input source selection, but I can only switch to the next source, wait for 2 seconds, and repeat this process 5 times every time I want to switch the audio from my computer to the PS5.
 
After lots of trials and flashing my custom kernel, I finally did it!
The idea is to use a board that has 1 USB otg port to act as a UAC 1.0 sound card, and has another 1 USB host port to connect to the UAC 2.0 speakers, then run programs on that board to redirect sound from USB otg port to USB host port. It is even a plus that the board consumes less power, so we do not need an extra or special power supply for it; this becomes crucial, especially when sharing the same USB connection with the USB otg port (SBC boards are more power-hungry these days!). The standard USB 2.0 protocol only allows 5V 0.5A to the device connected.
I actually built one with an Orange Pi One board, but it turns out that the CPU is not fast enough, and there are sound glitches sometimes.
 
With some research, I found this board that perfectly fits my needs: Radxa zero 3W. Here is the advantage:
- It is cheap, and the one I used is the nearly minimum SKU (1 GB ram with 8 GB onboard eMMC, they also have no onboard eMMC SKU).
- The otg port could handle USB PD protocol, meaning no special hacks are needed, you could get at most 30W of power, if needed (and turns out the normal USB 2.0 port on my PS5 works perfectly, so I guess it consumes less than 5V 1A = 5W)
- It is tiny.
 
However, things don't work right out of the box. At the beginning, I flashed the official, latest Radxa OS, modprobe the g_audio. It is running as a UAC 2.0 device, so it is not the one I want. As a result, I grabbed their kernel source, changed the config to UAC 1.0 gadget, and flashed onto the board, but there seems to be some issues in their kernel fork for UAC 1.0 driver: there was no /dev/snd/controlC0, so the g_audio failed to run.
As a result, I turned to use the Armbian build. This time, the /dev/snd/pcmC0D0c is missing, so g_audio failed to run again.
I then compiled my own kernel, flashed it onto the board. The Armbian build is with kernel 6.1, and the kernel I built is kernel 6.12, then the board failed to boot to the kernel due to U-Boot thought there were some errors.
Luckily, I found that building the whole Armbian image with kernel 6.12 can boot without issues, so I built a custom kernel 6.12 with UAC 1.0 enabled image, modeprobe the g_audio module, and it finally worked!
 
After that, I crafted a simple golang SystemV daemon for bootstrapping and terminating the alsaloop program for redirecting the sound, and used a udev rule to notify that daemon of the attachment/detachment of the USB speaker out event. The converter is finally working!
 
Here is the pre-built image for folks who want a quick test. It is based on the commit b27c86e620dcd9f55daadf52ccc85643dba2a381 from the armbian build repo with the following config modification:
diff --git a/config/kernel/linux-rockchip64-current.config b/config/kernel/linux-rockchip64-current.config index d053d0997..6e360bba7 100644 --- a/config/kernel/linux-rockchip64-current.config +++ b/config/kernel/linux-rockchip64-current.config @@ -3507,3 +3507,8 @@ CONFIG_RATIONAL_KUNIT_TEST=m CONFIG_MEMCPY_KUNIT_TEST=m CONFIG_TEST_MEMCAT_P=m CONFIG_MEMTEST=y + +CONFIG_USB_CONFIGFS_F_UAC1=y +CONFIG_USB_CONFIGFS_F_UAC2=n +CONFIG_USB_F_UAC2=n +CONFIG_GADGET_UAC1=y  
Currently, the "current" build does not detect the Wi-Fi interface, but as it does not affect the audio converting feature, I may not put too much effort into this.

@Stoven @jock
 
We were moving servers around and forgot about https://users.armbian.com
 
Fixed.

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

If nvme is correctly recognized code { font-family: Consolas,"courier new"; color: crimson; background-color: rgba(0, 0, 0, 0.2); padding: 2px; font-size: 105%; } armbian-install should do.

Recreated hdmi patches under kernels 6.12 and kernels 6.15 in pcduino-boards-fixes branch.  When attempting to build with current kernel 6.12.30, with drm patches for sun4i_hdmi_enc.c to use drm_hdmi_connector_mode_valid and drm_atomic_helper_connector_hdmi_check fails to compile. when just applying drm_atomic_helper_connector_hdmi_check patch build compilation is successful. Just need to verify this build works.
 
For kernel 6.15, with just the hdmi patches, we get a working HDMI display output:
 

@Igor, all
just like to say that I installed
 
Armbian_community_25.8.0-trunk.228_Orangepizero3_bookworm_current_6.12.30_minimal.imgArmbian_community_25.8.0-trunk.228_Orangepizero3_bookworm_current_6.12.30_minimal.img
from the boards page
https://www.armbian.com/orange-pi-zero-3/
 
apt update works 'out of the box', no PUBKEY errors
 
thanks for the the updates
@vtech,
you may like to try the same for orange pi zero 2

What do you mean by that? Images that are currently available are still from 25.2 ... new will be created soon. But you can anyway update them standard way: apt update + apt upgrade.