Active threads

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.

Disabling the GPU solves the problem, but I don't know the root cause of the issue.

hi there, I'm a complete Linux noob so please forgive my ignorance. But I do have 25+ years experience in IT so am relatively conversant with basic principles - so please be patient I did try to search for any previous threads but couldn't find any. I'm trying to setup a RADXA Rock 5 ITX with OpenMediaVault for my NAS. I have a 2TB NVMe m.2 SSD that I'll use for the OS. For the NAS storage I'm using 4x Western Digital 16TB SATA III drives. I downloaded the Armbian 25.2.2 bootable image from https://www.armbian.com/radxa-rock-5-itx/ and used Balena Etcher (the legit version from Balena-io) to make my bootable microSD card. When I boot, I receive an error message of "failed to mount /dev/mount/mmcblk0p1 as root file system" I'm guessing this is because there is no emmc on this board other than what's provided for RooibOS flash? Do I just need to reconfigure the Armbian Bookworm setup script to use / look for the NVMe m.2 SSD instead of the emmc? If so, is there a way to do that on a Windows PC? If not, I may just have to go with the standard RooibOS install using Armbian Noble just to get a Linux system up and running, then edit the Armbian setup script, reflash the Rock 5 ITX and start again? Or is there something else I'm missing? Thanks in advance for your help.

Thank you for making us aware of the problem. But kindly also search the forum and other publicly accessible places of information: https://disk.yandex.ru/d/kK6KIqHShRHLyw/20230620/u-boot-station-m2-EDK2-EFI.img and higher level directories @Igor Can you update the website, please?

Hi subhan i don't wait kernel update , i just use a script who create a user-overlay who enable the sound on the OPI zero 2w via HDMI , i2S via the 40 pin hat or jack connector via the expansion board and the µc is a H618 In fact the main board except for HDMI have no output for sound , so i think it's better to stay with a user-overlay ☺️

Thanks!! Thanks for the overview. ES8388 Codec Driver Something to add to my previous comment here (2 comments up). I've noticed that, with the edge kernel, ALSA calls the ES8388 the 8328 instead. I've also seen the 8328 referenced in the devicetree .dtb file (via a hex viewer). I happened across where it appears to be, in two repositories: https://github.com/armbian/linux-rockchip/tree/rk-6.1-rkr5.1/sound/soc/codecs https://github.com/torvalds/linux/tree/master/sound/soc/codecs In both of those directories, there is an es8328.c, es8328.h and other es-... numbers in that range, but no es8388 file. To any developer reading this, it might be worthwhile to create es8388.h and es8388.c as copies of their respective es8328 counterparts, then have the es8388 files used in the build and referenced in the devicetrees instead of the es8328. This would create the clear (and correct) workspace to make the necessary modification(s) to fix the issue (of the volume apparently being right-shifted by 7 or 8 bits - re my previous comment). I've noticed in the es8328.h file, there are several configuration constants defined. It could be as simple as modifying one of those in the es8388.h to match the actual es8388 codec.

Hi I got error when applying the patch you shared. Can I know how to fix it? Ca

They did. Or at least the kernel is built, and this was reported (https://linux-arm-kernel.infradead.narkive.com/WmgM10BC/rfc-v1-0-5-arm-initial-support-for-marvell-armada-1500) . This family of chipset includes the original Google TV and some others.

Hello brent, have you got a hint, on how it could be done? Best regards Manuel

“Looks like the 6.6.x branch still has stability issues on sunxi64 — falling back to legacy 6.1 seems safest until patches land. Curious if anyone’s tested with 6.7+ to see if it’s resolved?”

thank you for reporting back, @ER Samson

@SteeMan, okay, thank you for explanation.

Thank you for the heads-up, @Kluas. Your Packages file is uptodate. It is indeed a mirror issue. Just wait or use a different mirror. $ wget -qO- https://xogium.performanceservers.nl/apt/dists/bookworm/main/binary-arm64/Packages.bz2|bzgrep 25.8.1 -8|grep ^Package.*armbian-bsp-cli-odroidc4-current -A18 | grep -e ^SHA512 -e ^Size Size: 435180 SHA512: 7e978f3ef834a0a01e52728dd72062f573fb7f973b3dedbdf36a6efd58972c5fab93c526a3945a9b6e0ff28a81bc4ade80029cf8ddb149f5d1a4ffaf8a6c2ab1 $ wget -qO- https://xogium.performanceservers.nl/apt/pool/main/a/armbian-bsp-cli-odroidhc4-current/armbian-bsp-cli-odroidhc4-current_25.8.1_arm64__1-PCee86-Va97e-He458-B1e5d-Rf36a.deb | sha512sum c0a4948328da1996a6d4df7adf33ff36dcd9f4bb377c4727d2a8f244e8809668754abb1fbee741fdfb2a0573690ebd858afdbb350f0fec4f6519b65b1b9cb385 - $ wget -qO- https://xogium.performanceservers.nl/apt/pool/main/a/armbian-bsp-cli-odroidhc4-current/armbian-bsp-cli-odroidhc4-current_25.8.1_arm64__1-PCee86-Va97e-He458-B1e5d-Rf36a.deb | wc -c 434960

I have used/tested KDE-neon a while ago December 2024 I see from rootfs backup, that was on a ROCK3A and to enjoy KDE6. Maybe now if you want KDE6, Trixie has it, so as base Armbian (Debian) then upgrade and/or install KDE plasma (sudo tasksel to select and install). I have it on my ROCK5B, at least with edge kernel it works all as expected, compared with KDE6 on Opensuse Tumbleweed and Debian Trixie on N100 miniPC. In-place upgrade went fine, although the whole user environment from KDE5 is gone and you start from scratch new template KDE6 when upgrade from Bookworm->Trixie. If you want latest KDE, then Neon is now already newer than the 6.3 in Trixie AFAIR, but it seems to me that integration issues can be expected. I see Ubuntu Noble (Kubuntu) has KDE5 still.

It was a network problem. Problem fixed after global activation of a clash proxy. Thanks a lot!

Sorry to bump an old thread. I am having the exact same issue here with that predefined build. I tried building moonlight-qt from source after installing ffmpeg-rockchip, I still cant get hardware decoding working... I am on a pure Wayland setup. Anyone have any tips to get this to work? What needs to be changed in the qt.pro files?

What does the following command show? sudo fdtoverlay -v -i /sys/firmware/fdt -o /dev/null /path/to/your_overlay.dtbo panel-simple-dsi ... Expected bpc in {6,8} but got: 0 So possibly the default with the older kernel was by accident correct and now you should define it. And it seems that you use an overlay meant for the 5a on a 5c?

Can you try if any of the H3 images from libre-elec would get you video acceleration? https://libreelec.tv/downloads/allwinner/ i once tried the orange pi pc image in my orange pi zero lts (h3) and it worked

hello "I need the MiniLoaderAll.bin for RK229Q-221P-V1.3 (2020.10.10). do you have it

That issue was just dealt with by disabling cruft instead. If you want to test a newer uboot with a reenabled cruft you will again need to go into building and testing, followed by a PR.

@Nick A 👍