Quote:
Originally Posted by tshering
Hi Ben,
Thank you for your observations. It is not clear to me what actually was happening.
Evidently the effects were the same as those experienced by trekk, the cause however was different. With the new models (Aura One, and Ed 2) PRODUCT_ID was empty, and therefore loading g_file_storage.ko failed. In your case however the cause is that /dev/mmcblk1p1 exists, even though there is no external sd present. Do you have any idea how this can happen? By the way, umount -l /mnt/sd does not cause a problem, even if the sd is not mounted. Is it possible that the problem started when you removed the sd and tried to enable usb almost at the same time, so that /dev/mmcblk1p1 existed at the time of testing its presence and was gone at the time of loading g_file_storage.ko? Enabling usb should work whether an external sd is present or not.
|
tshering, tx for the feedback. And my apologies for my late answer.
Actually, the external sd was already out of the Aura for months. So, no that's not it. Also, the Kobo was already powered off and on many times and even reset a number of times to get from Nickel back to KSM.
So regardless if the sd card is there or not, the device /dev/mmcblk1p1 stays once it is created ... you would expect the device tree to get cleaned up if devices disappear. Maybe not so in the (old) Kobo kernel ?
Cheers, Ben