30 replies to this topic

[hispanico957]

Its strange from first installation with usb stick appear this message/error and also every update from web

 

 

but the image run well without problem ?!?

 

Thank for advise

Hispa

Edited by hispanico957, 16 March 2017 - 00:33.

[WanWizard]

Which box?

[WTE]

It looks like that's just a check to see if an SDcard or internal eMMC is available/connect.

[Pr2]

Have you installed some sort of MultiBoot?

[hispanico]

I have Zgemma h2h and install in normal way no multiboot.
I have a mmc inserted on dec but i dont think is the problem

Hispa

[WanWizard]

If you have an MMC inserted, can you telnet into the box, issue the command

ls -l /sys/block/mcc

and post the output here?

 

This is part of the mdev-mount script, the check is done to dfferentiate between an internal MMC card, and an SD-Card plugged into a reader (which should be removable).

[Taapat]

On zgemma /sys/block/mmc does not exist, exist mmcblk0.

This already been discussed: https://forums.openp...ed/#entry647457

Edited by Taapat, 16 March 2017 - 22:07.

[WanWizard]

Ah, ok.

 

How about this in /etc/mdev/mdev-mount.sh (line 60+):

if [ -d /sys/block/$DEVBASE ]; then
	REMOVABLE=`cat /sys/block/$DEVBASE/removable`
	readlink -fn /sys/block/$DEVBASE/device | grep -qs 'pci\|ahci\|sata'
	EXTERNAL=$?
else
	REMOVABLE=`cat /sys/block/$MDEV/removable`
	readlink -fn /sys/block/$MDEV/device | grep -qs 'pci\|ahci\|sata'
	EXTERNAL=$?
fi

could you check if this fixes it?

[Taapat]

What you think?

https://github.com/O...e-core/pull/188

[WanWizard]

Looks a lot more complex than my suggestion?

[Taapat]

Looking at this issue, I saw that my offer replace DEVBASE with MDEV is incorrect.

For mmc MDEV is mmcblk[0-9]p[0-9] (mmcblk0p1 on my zgemma): https://github.com/O...x/mdev.conf#L41

Therefore require more complex changes to change DEVBASE to mmcblk[0-9] (mmcblk0).

Edited by Taapat, 17 March 2017 - 14:29.

[WanWizard]

DEVBASE should be the device. It was originally created for MDEV's like "sda1" etc, where DEVBASE becomes "sda".
 
Perhaps we should say: if the length > 7, use the first 7, otherwise the first 3? So it becomes "mmcblk0".

[Taapat]

Please check mdev-mount.sh.

Links are in my post before.

mdev-mount.sh can be used only for [hs]d[a-z][0-9]? with 3 character DEVBASE [hs]d[a-z] and for mmcblk[0-9]p[0-9] with 7 character DEVBASE mmcblk[0-9].

Another option currently is not intended.

[WanWizard]

That should be ok.

 

According to your post in the other topic, you have "/sys/block/mmcblk0/removable" so with $MDEV=mmcblk0p1 and $DEVBASE=mmcblk0, it should work for your mmc card if we add support to mdev-mount,sh for a 7-char DEVBASE like I proposed in my previous post? 

[Taapat]

You want to set DEVBASE taking into account MDEV length.

Although a specific example how you would like to see are not shown.

 

I propose to set DEVBASE depending on the MDEV type.

I believe that the 7-char DEVBASE is specific only for mmc and may be incorrect for others.

Therefore, I propose to use the 7-char DEVBASE only for mmc.

[WanWizard]

You can always double check, since /sys/block/$DEVBASE must exist.

[Taapat]

And you're sure that this will not be a reason to mount mtdbloc or something like that, which shall not be mounted?

Therefore I believe that it is better to use the name.

 

But of course, you can make changes to the way witch you feel better.

 

It looks like that the next time, when someone write about this issue, I can point to this unused PR, rather than to another topic .

[WanWizard]

What is the output of

cat /sys/block/$DEVBASE/device/model

?

[WanWizard]

Found another issue.

 

MiLo did a merge from master to master-next last year, which caused a merge conflict, after which incorrect parts got into the mdev-mount.sh script.

 

So some cleanup is needed too...

[WanWizard]

https://github.com/O...54898b60b7e6d61 and  https://github.com/O...cb3063adb0a6825