Meestor_X

Maybe not? root@rp-satellite-01:~# for X in 0 1;do echo "mmcblk${X}: $(cat /sys/block/mmcblk${X}/device/type)";done mmcblk0: SD mmcblk1: SD root@rp-satellite-01:~# lsblk NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINTS sdb 8:16 1 238.3G 0 disk └─sdb1 8:17 1 238.3G 0 part /media/usb mmcblk1 179:0 0 59.6G 0 disk └─mmcblk1p1 179:1 0 59G 0 part /var/log.hdd / mmcblk0 179:32 0 3.6G 0 disk └─mmcblk0p1 179:33 0 3.5G 0 part zram0 252:0 0 233.1M 0 disk [SWAP] zram1 252:1 0 50M 0 disk /var/log zram2 252:2 0 0B 0 disk root@rp-satellite-01:~#

Ok, I only use this utility on Radxa products ATM, and AFAIK they can't boot from USB without a bootloader on the eMMC or SD card. If I had an image on a USB flash drive attached to the SBC, where would armbian-install expect to find it mounted? And then, would choice #1 or #3 use the SD card or the USB image? Also, should option #2 not show? I don't know how it would copy from the eMMC to the eMMC... The operation of the script works well, but the menu could be much clearer for the Radxa products.

That seems to work! Let me ask you this, though. Can you clarify what selection #2 means? Selection #1 will copy the eMMC image to the SD card. Selection #3 will copy the SD card to the eMMC (shouldn't the text read "Boot from eMMC - system on SD Card, SATA, USB or NVMe") What is selection #2 for?

Screenshot is in the original post, it still looks the same now.

Thank you. What do you suggest I do? I'm not sure that the "update bootloader" choices are showing the correct devices either.

If I understood a bit better what the script is doing, i.e. this part: Then maybe I could help with updating it to work with the Radxa products.

Correct. Many Radxa SBC’s work this way. RockPi-S, RockPi-S0, RockPi-E, E20c, e25c, e52c, rock-pi-zero, etc.

df -h Filesystem Size Used Avail Use% Mounted on udev 159M 0 159M 0% /dev tmpfs 47M 4.8M 42M 11% /run /dev/mmcblk1p1 58G 3.4G 53G 7% / tmpfs 234M 76K 233M 1% /dev/shm tmpfs 5.0M 0 5.0M 0% /run/lock tmpfs 234M 4.0K 234M 1% /tmp /dev/zram1 47M 2.4M 42M 6% /var/log /dev/mmcblk0p1 3.4G 2.0G 1.3G 62% /media/emmc tmpfs 47M 0 47M 0% /run/user/0 lsblk NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINTS mmcblk1 179:0 0 59.6G 0 disk └─mmcblk1p1 179:1 0 59G 0 part /var/log.hdd / mmcblk0 179:32 0 3.6G 0 disk └─mmcblk0p1 179:33 0 3.5G 0 part /media/emmc zram0 252:0 0 233.1M 0 disk [SWAP] zram1 252:1 0 50M 0 disk /var/log zram2 252:2 0 0B 0 disk lsb_release -a No LSB modules are available. Distributor ID: Debian Description: Armbian 25.8.1 bookworm Release: 12 Codename: bookworm uname -r 6.12.44-current-rockchip64 I don't have an easy way to do the serial terminal thing to check U-Boot. I have updated it to the "latest" using armbian-install, however...

Oh! I guess I reported this same issue a while ago - never got an answer. Is there a github repo to report issues with this program?

Can someone explain these lines? # find real mmcblk device numbered 0, 1, 2 for eMMC, SD for ret in $(find /dev -name 'mmcblk[0-2]' -and -type b) do if [ -b ${ret}boot0 ];then emmc_dev=$ret else sd_dev=$ret fi done On the RockPi-S, $ret would equal mmcblk0 and mmcblk1 which are the eMMC and SD card, respectively. There's no device called "mmcblk0boot0" or "mmcblk1boot0".

Is there a github repo for armbian-install? On the RockPi-S with both eMMC and SD cards installed, it's showing the devices backwards or un-named in the menu. I'd like to open an issue report to see if it can be fixed.

Coming back to this... I'm not having any luck getting overlays to work, but I'll need to get out my serial logger to see what's wrong I guess. I'm trying to get the USB-C into host mode on my RockPi-S. I can do it by editing the rk3308-rock-pi-s.dtb file directly, but not using an overlay file. Here's the overlay file I've tried (usbc-host.dts): /dts-v1/; / { fragment@0 { target-path = "/usb@ff400000"; __overlay__ { dr_mode = "host"; }; }; }; and /dts-v1/; /plugin/; / { fragment@0 { target-path = "/usb@ff400000"; __overlay__ { dr_mode = "host"; }; }; }; Tried using: armbian-add-overlay usbc-host.dts as well as compiling the overlay to a .dtbo and adding the line directly into armbianEnv.txt No joy either way... Also, does anyone know why some .dtbo files also have the line /plugin/; below /dts-v1/; ?

Ok, this is weird (or maybe expected, I'm a newbie to all of this)... I installed fresh 25.2.3/6.12.22, and audio didn't work. Came here and posted. Then I used armbian-config to roll back the kernel to 24.11.3/6.12.11. After that, audio worked again. Then, I ran apt update && apt upgrade and still audio kept working. I'm right back to 25.2.3/6.12.22 it seems? cat /run/motd.dynamic _ _ _ /_\ _ _ _ __ | |__(_)__ _ _ _ / _ \| '_| ' \| '_ \ / _` | ' \ /_/ \_\_| |_|_|_|_.__/_\__,_|_||_| v25.2.3 for Rockpi S running Armbian Linux 6.12.22-current-rockchip64 Packages: Debian stable (bookworm) IP addresses: (LAN) IPv4: 192.168.1.35, 10.42.0.1 IPv6: 2001:56a:7490:ce00:8dd8:6d59:ca7a:fe87 (WAN) xxx.xxx.xxx.xxx Performance: Load: 47% Up time: 0 min Memory usage: 31% of 466M CPU temp: 46°C Usage of /: 10% of 59G Commands: Configuration : armbian-config Monitoring : htop uname -a shows: uname -a Linux rp-satellite-xx 6.12.22-current-rockchip64 #1 SMP PREEMPT Mon Apr 7 08:08:37 UTC 2025 aarch64 GNU/Linux aplay -l shows: aplay -l **** List of PLAYBACK Hardware Devices **** card 0: pcm5102a [pcm5102a], device 0: ff300000.i2s-pcm5102a-hifi pcm5102a-hifi-0 [ff300000.i2s-pcm5102a-hifi pcm5102a-hifi-0] Subdevices: 1/1 Subdevice #0: subdevice #0 card 1: analog [analog], device 0: ff320000.i2s-rk3308-hifi ff560000.codec-0 [ff320000.i2s-rk3308-hifi ff560000.codec-0] Subdevices: 1/1 Subdevice #0: subdevice #0 So, I'm running 6.12.22, and audio is working, but had to do it via apt-upgrade. Any idea why that worked?

Does 25.2.1/6.12.12 work?

Is there a fix for 6.12.22? uname -a Linux rp-satellite-xx 6.12.22-current-rockchip64 #1 SMP PREEMPT Mon Apr 7 08:08:37 UTC 2025 aarch64 GNU/Linux cat /sys/class/gpio/export cat: /sys/class/gpio/export: Permission denied ls /dev/snd/ seq timer aplay -l aplay: device_list:274: no soundcards found...