Werner

moved. neither a tutorial nor a review. Check if the user you are using has permission to use docker (usermod -aG docker yourusername) Alternatively use PREFER_DOCKER=no

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

Is the emmc soldered on the board? I don't know this board in particular but it might be simply just sit in a socket.

moved to userspace

Do you have any chance to show us debug uart logs when trying to boot those? Check the link above to get a video on how this works if you don't know.

I wonder why these images even exist. AFAIK support has been added by Joshua for vendor only...

duplicate https://forum.armbian.com/topic/44868-may-i-ask-where-to-add-and-place-the-background-image？？/#comment-201131

https://github.com/NicoD-SBC/armbian-gaming

Just guessing. Thats an Amlogic device. Tried ttyAML...?

There is no simple way to do this. Look at the code and modify. Start looking here: https://github.com/armbian/build/tree/dd6300d4cce9056eb5efa16ce3b656c16734bbe7/packages/plymouth-theme-armbian Gnome DE config is here: https://github.com/armbian/build/tree/main/config/desktop/common/environments/gnome If this is too complicated for you I suggest to book professional consultation: https://calendly.com/armbian/consultation

The what?

https://docs.armbian.com/User-Guide_FAQ/#why-does-hardware-feature-xy-work-in-old-kernel-but-not-in-more-recent-one mixed up. 5.10.y is legacy, 6.1.y is vendor. While it is great to have mainline for this board it is far from feature-complete. If you need more hw features to work you have to use vendor kernel branch. Have you tried to lookup headers via apt? If no success, try building your own kernel packages, or an image with matching headers pre-installed, with the build framework: https://github.com/armbian/build Sometimes it can happen that headers are not available for various reasons. Uncaught packaging failure, mirror unsync, .... Still interesting though since IIRC driver for 8812au should be included by default. However it might have been disabled due to build errors or whatever...

background image for? boot process? desktop? If latter which one? gnome? kde? xfce? Lacking information.

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