armbian-install not detecting devices on RockPi-S correctly

[Meestor_X]

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.

Edited Sunday at 05:09 PM by Meestor_X

[Meestor_X]

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".

[Meestor_X]

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?

[going]

16 часов назад, Meestor_X сказал:

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.

Please post the output of the df -h and lsblk commands here.

Which image are you using and which version of u-boot is running on your board? (this can be seen in the UART console)

[Meestor_X]

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...

[going]

1 час назад, Meestor_X сказал:

mmcblk1     179:0    0  59.6G  0 disk 
└─mmcblk1p1 179:1    0    59G  0 part /var/log.hdd

Is this your SD card?

 

1 час назад, Meestor_X сказал:

mmcblk0     179:32   0   3.6G  0 disk 
└─mmcblk0p1 179:33   0   3.5G  0 part /media/emmc

This is your eMMC just 3.6G in size.
This is the first time I have met this variant.
We need to think about whether it is possible to add an exception for this case.

 

[Meestor_X]

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

[Meestor_X]

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.

[going]

18 часов назад, Meestor_X сказал:

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.

 

On 99% of the devices I know, eMMC is initialized in the OS as /dev/mmcblk0, but there are cases when this is not the case.

# 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

This part of the code was implemented due to the fact that on some eMCC platforms there can be

both /dev/mmsblk0 and /dev/mmcblk1(2)

This works for chips that provide boot0\boot1 partitions to write the bootloader.

 

I think we can add more sophisticated logic to handle this exception for these chips.

You can add here the name of the chip on your device.
The translation may not be accurate. Please specify if something is not clear.

[Meestor_X]

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