Werner

Providing logs with armbianmonitor -u helps with troubleshooting and significantly raises chances that issue gets addressed.

https://debug.armbian.de

https://docs.armbian.com/Developer-Guide_User-Configurations/#user-provided-image-customization-script Simply put something like code { font-family: Consolas,"courier new"; color: crimson; background-color: rgba(0, 0, 0, 0.2); padding: 2px; font-size: 105%; } dpkg -i /tmp/overlay/yourawesomeapplication.deb in there and it will be executed close to the end of the build process.

On first boot did you cancel out between settings root pw and user creation? Not sure but the motd box might be enabled after first boot initialization has been completed successful only.

I doubt that Raspian supports this board.

moved tried removing emmc?

[ 5.124489] usb 1-2: New USB device found, idVendor=125f, idProduct=a35a, bcdDevice= 1.00 [ 5.138662] usb 1-2: New USB device strings: Mfr=2, Product=3, SerialNumber=1 [ 5.151816] usb 1-2: Product: HD650 [ 5.163401] usb 1-2: Manufacturer: ADATA [ 5.174874] usb 1-2: SerialNumber: 469093854006 [ 5.271985] usb-storage 1-2:1.0: USB Mass Storage device detected [ 5.284494] scsi host0: usb-storage 1-2:1.0 [ 5.305338] usbcore: registered new interface driver uas [ 6.304167] scsi 0:0:0:0: Direct-Access ADATA HD650 0 PQ: 0 ANSI: 6 [ 6.319922] sd 0:0:0:0: [sda] Spinning up disk... [ 7.010572] EXT4-fs (mmcblk0p2): mounted filesystem with writeback data mode. Quota mode: none. [ 7.359204] . [ 7.937317] systemd[1]: System time before build time, advancing clock. [ 8.383175] .................................................................................................not responding... [ 128.008368] sd 0:0:0:0: [sda] Read Capacity(10) failed: Result: hostbyte=0x00 driverbyte=DRIVER_OK [ 128.023616] sd 0:0:0:0: [sda] Sense Key : 0x2 [current] [ 128.035289] sd 0:0:0:0: [sda] ASC=0x4 ASCQ=0x1 [ 128.046964] sd 0:0:0:0: [sda] 0 512-byte logical blocks: (0 B/0 B) [ 128.059173] sd 0:0:0:0: [sda] 0-byte physical blocks [ 135.008044] sd 0:0:0:0: [sda] Test WP failed, assume Write Enabled [ 141.957722] sd 0:0:0:0: [sda] Asking for cache data failed [ 141.969473] sd 0:0:0:0: [sda] Assuming drive cache: write through [ 141.982023] sd 0:0:0:0: [sda] Attached SCSI disk So it seems like it is being detected. Everything beyond is out of scope of Armbian and userspace related.

https://www.google.com/search?client=firefox-b-lm&q=how+to+mount+a+usb+drive+in+linux No success?

Providing logs with armbianmonitor -u helps with troubleshooting and significantly raises chances that issue gets addressed. Did you check for other mmcblkX devices?

moved to feature requests same answer as here: https://forum.armbian.com/topic/41272-rockchip-rk3066-board/#comment-194743

6.11-rc is already available via edge branch. https://github.com/armbian/build/pull/7015

https://debug.armbian.de

That would probably be deb [signed-by=/usr/share/keyrings/armbian.gpg] http://apt.armbian.com noble main noble-utils noble-desktop This only affects Armbian-related packages. Everything from upstream userspace is out of scope of Armbian.

There is no dedicated record for this, yes. But you can check for file extension changes on specific board configuration files in the commits like:https://github.com/armbian/build/commits/main/config/boards/orangepizero.csc

https://debug.armbian.de

moved to userspace

Did code { font-family: Consolas,"courier new"; color: crimson; background-color: rgba(0, 0, 0, 0.2); padding: 2px; font-size: 105%; } apt update beforehand? Images do not come with pre-installed apt lists since they would be outdated the moment the image was assembled.

Try this:https://github.com/armbian/build/pull/7082

Tag will be added once this board was introduced in the build framework. Section is only for boards that suffice standard support criteria.

We cannot support 3rd party OS. Why 3rd party? Because Armbian does not exist for this SoC and if it does its a fork we cannot support either.

I suggest to ask at dietpi's place for question about installation. We cannot support 3rd party OS. Not sure where you dug out such an old Armbian image. Check automated builds here: https://github.com/armbian/community/ -> Releases HW is community maintained so its status is unknown to Armbian team.

https://debug.armbian.de Thats not for the plus model?

Search for "H6" in this section.

If your device has UEFI support: https://www.armbian.com/uefi-arm64/ If not, no. Generic support w/o standardization is impossible.

Probably Amlogic. No clue though why they decided to alter the naming for debug console on this soc.