Hi everyone, I'm new to creating my own images and I'm learning this just because I'm interested in it. I am trying to build ubuntu 24.04 for my rpi3b using the build configuration for rpi4b. Now I'm trying to automate the process of the first launch (skip the selection of bash, zsh, creating a password for root, creating a regular user, etc.). In one of the topics, I found out that I can delete "rm -rf/root/.not_logged_in_yet" And the system will not ask for the initial setup, but to make all the necessary changes for me, I wrote a small function in customize-image.sh: SettingSystemFirtsRun() { #disable defaut script sudo rm -rf /root/.not_logged_in_yet #setting regul user echo "add user $_userName" sudo useradd -m -c -s /bin/bash "$_userName" "$_userName" -p "$_userPass" #change root pass echo 'change root passssss' echo "root:$_rootPass" | sudo chpasswd # Set hostname permanently echo "Setting hostname to $_Hostname" echo "$_Hostname" > /etc/hostname hostname -b "$_Hostname" # Update hosts file sed -i "s/127.0.1.1.*/127.0.1.1\t$_Hostname/g" /etc/hosts } But when the system starts, I still do not see the directory of the user I am creating in /home, while the user himself is being created. The most important thing is that I really want to implement user creation at the assembly stage, although I am less and less convinced that this is even possible... I do not rule out that there are more concise ways to solve this problem, so I will be glad of any advice, good luck to all. P.S. I read the documentation, but I couldn't find a solution there.

Andrew, thanks for your feedback. I use the dtb released by armbian, I even try to get the dtb from the last image with same kernel, but it is the same. In fact the dtb file for Orange pi 5 is the same that the one I have (sha256 was clear !) I saw this other bug lately : https://github.com/rockchip-linux/kernel/issues/306 You have a Rock5B+ which is not the same thant OrangePI5, I run RK3588s, and you run rk3588. This means that the hardware even if near is not presented to the kernel the same way, ans so this may work for you, ans not for me in 6.1.115. I'm quite sure the issue happened with 6.1.115 kernel, because I encoded x265 easily 1 year ago with previous kernel.

I dropped back to Armbian_24.5.1_Bananapim5_bookworm_current_6.6.31_xfce_desktop.img and while it working, the boot find order of the drives is still random, no two boots is a row report the same lsblk order of disk vs sd* assigbnents. Only by using LABELS have I succeeded in getting them (7 drives) mounted in /etx./fstab. After that dated install an apt upgrade spent about an hour updating 270 some pkgs Just tried to get some of the other partitions mounted and usable, using LABEL= to ID them, got 2 of the 3 on a 1T toshiba drive, but found swapoff -a works, but swapon -a does not, won't even restore whats found at boot. This is from fdisk, also a reboot changed /dev/sdd into /dev/sdb Command (m for help): p Disk /dev/sdb: 931.51 GiB, 1000204886016 bytes, 1953525168 sectors Disk model: MQ01ABD100V Units: sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 4096 bytes I/O size (minimum/optimal): 4096 bytes / 4096 bytes Disklabel type: dos Disk identifier: 0x481e1363 Device Boot Start End Sectors Size Id Type /dev/sdb1 2048 102402047 102400000 48.8G 83 Linux /dev/sdb2 102402048 1748725759 1646323712 785G 83 Linux /dev/sdb3 1748725760 1953523711 204797952 97.7G 82 Linux swap / Solaris but its not swapon-able, note the dos disklable, it s/b gpt, it was done with gparted. ?????? Is there a conversion utility to make gpt or should I wait on working keyboard/mouse kit and let gparted blow it away? So I did, changed 3 parts to 2 and refornatted both and found that swapon should use label's but fails and the reboot to do that moved the toshiba drive from /dev/sdb to /dev/sdd. Howinhell can I stabilize tiis?????

This remembers me a recent set of changes to the DWC3 driver for RK3399 to fix exactly these kind of issues exposed here, including the single-orientation problem, plus some more issues with the displayport over usb type-c functionality. The PR had a lot of comments but finally it got merged because both the author and me tested the whole apparatus and it proved to improve significantly the situation on rk3399: https://github.com/armbian/build/pull/8271 Patches should address some issues in the dwc3 driver in general, and I see from the device tree that rk356x uses the snps,dwc3 compatibility string, so probably also rk356x benefits from them as well. It would although require some device tree tinkering: I tested on Orange PI4 LTS board and the device tree fixes are within this hunk; rk356x-based devices can probably share several declarations but that depends upon the rk356x capabilities. I would start from changing dr_mode to otg and removing regulator-always-on; property from the vbus supply.

Upgrade to Trixie went fine, but pressing the user-button has no effect. I won't look into it further now. I could try with ROCK5B, has a dedicated power button, but also needs to stay active 24/7 as server actually.