Page 2 of 2

Posted: Thu 09 May 2019, 19:35
by HerrBert
Hello gychang.

Obviously modules are not loaded on boot.

I suggest to do some research on what differs when booting with and without inserted sd-card.

Therefor you should start your pc with inserted card, execute

Code: Select all

lsmod > sd-inserted
file sd-inserted should be in /root/ - copy to save place.

Reboot with removed sd-card, execute

Code: Select all

lsmod > sd-removed
If you now compare the two files, you may find different modules loaded.

The missing modules you can try to load with Boot Manager.
Open Menu -> System -> BootManager, goto tab modules, choose to add modules, in upcoming window search for the missing modules and add them to startup.

Save on exit and reboot.

Posted: Wed 26 Feb 2020, 17:18
by gychang
HerrBert wrote:Hello gychang.

Obviously modules are not loaded on boot.

I suggest to do some research on what differs when booting with and without inserted sd-card.

Therefor you should start your pc with inserted card, execute

Code: Select all

lsmod > sd-inserted
file sd-inserted should be in /root/ - copy to save place.

Reboot with removed sd-card, execute

Code: Select all

lsmod > sd-removed
If you now compare the two files, you may find different modules loaded.

Save on exit and reboot.
Your comments are very clever, logical and make good sense. Unfortunately comparing 2 files several times, I find no difference (also no of loaded drivers are same)...
One way of getting around it is to use it with SD card in the slot and start that way can read and write when I need to do. Any other ideas will be welcome since booting a PC with a SD card in the slot is not norm...

Posted: Wed 26 Feb 2020, 20:36
by bigpup
since booting a PC with a SD card in the slot is not norm...
Why not?
If you have a SD card. There is no reason not to keep in in the SD card slot.
I keep one in my computers slot all the time.
It just acts as another drive to access.
Plus it is a micro SD card and that thing is easy to loose.

Check the inside of that SD card slot for dirt, bent contacts, corrosion, etc.....

Posted: Thu 27 Feb 2020, 15:24
by gychang
bigpup wrote:
since booting a PC with a SD card in the slot is not norm...
Why not?
If you have a SD card. There is no reason not to keep in in the SD card slot.
I keep one in my computers slot all the time.
It just acts as another drive to access.
Plus it is a micro SD card and that thing is easy to loose.

Check the inside of that SD card slot for dirt, bent contacts, corrosion, etc.....
only way I can access another SD card (not the one I booted with), is not to use refresh button on pmount but close and open pmount again... thanks.

Posted: Thu 27 Feb 2020, 23:33
by wiak
For sdcard module loading, in a console try commands:

modprobe sdhci
modprobe sdhci-pci

wiak

Posted: Fri 28 Feb 2020, 00:54
by gychang
wiak wrote:For sdcard module loading, in a console try commands:

modprobe sdhci
modprobe sdhci-pci

wiak
running pmount/gparted after each command does not mount the sd card.

Posted: Fri 28 Feb 2020, 08:06
by wiak
gychang wrote:
wiak wrote:For sdcard module loading, in a console try commands:

modprobe sdhci
modprobe sdhci-pci

wiak
running pmount/gparted after each command does not mount the sd card.
Could you check to see if the above modules are actually loaded after running the commands by entering:

lsmod | grep 'sdhci'

On my system I notice an extra sdhci module is also loaded: sdhci_pltfm. You could therefore maybe also try:

modprobe sdhci_pltfm

Note that sometimes the actual module is named with a hyphen and just appears in the list with an underscore, so maybe:

modprobe sdhci-pltfm

similarly with modprobe sdhci-pci or modprobe sdhci_pci

I haven't checked for the module filenames under /lib and haven't worked with sdcard mounting for ages so may be on the wrong track altogether - maybe BIOS setup related instead, but I'm admittedly just throwing guesses to the wind now.

wiak

Posted: Fri 28 Feb 2020, 08:20
by wiak
Also, one last try, though not sure if BionicPup has following commands (I don't have BionicPup installed). Try:

Code: Select all

udevadm trigger --action=add --type=subsystems
udevadm trigger --action=add --type=devices
udevadm settle
Above is definitely just a last thought which is unlikely to succeed. Sound like your hardware isn't itself being detected unless the SD card is in it at boot time (hoping above three commands helps with that, buit out of ideas otherwise...

wiak

Posted: Fri 28 Feb 2020, 16:55
by gychang
wiak wrote:Also, one last try, though not sure if BionicPup has following commands (I don't have BionicPup installed). Try:

Code: Select all

udevadm trigger --action=add --type=devices
Above is definitely just a last thought which is unlikely to succeed. Sound like your hardware isn't itself being detected unless the SD card is in it at boot time.

wiak
I believe you have provided the answer!! This command "udevadm trigger --action=add --type=devices" seems to be the key.

After a normal boot (without SD card, I can then insert SD or xD card and it detects the card as long as I enter the command on the console. I have to re-enter the command each time I want access to SD, which is not ideal.

Only way I can see is to make a script and trigger keybinding but seems messy. Any further ideas will be great.

Posted: Tue 03 Mar 2020, 04:43
by enrique
@gychang
Let me start by saying I had bad experience in the forum giving advice to users on hardware issues, that requires follow terminal commands. Point is in general I am limiting my help to only users that I see genuinely ask for it. With the skill of terminal commands and smart enough to manage system config files. You started request on Mon 22 Apr 2019, 12:26 and almost a year later you still here. Sorry I did not saw your post earlier. I sent you a PM.