Posted: Thu Apr 10, 2003 8:27 pm Post subject: pcmcia drivers functioning, but not loading during boot

--------------------------------------------------------------------------------

I recently upgraded my laptop from RH8 to RH9. All in all the upgrade went well, but since the upgrade getting pcmcia to work properly has been a strugle. I have 2 pcmcia cards, the first is a 3com 3c574 ethernet card and a netgear MA401 wireless card. After the install and a rebuild of the drivers, the netgear came right up without issue. The 3com was failing however, so I decided to remove the eth0 configs in order to reinstall. Since I did this unfortunately, the PCMCIA drivers won't load during boot seemingly no matter what I do.

I clearly watch as init reports that pcmcia gets the [ OK ] during boot, but the looking at the syslog I see the following:

Apr 10 12:59:30 Q-redhat kernel: Linux Kernel Card Services 3.1.22
Apr 10 12:59:30 Q-redhat kernel: options: [pci] [cardbus] [pm]
Apr 10 12:59:30 Q-redhat kernel: ds: no socket drivers loaded!
Apr 10 12:59:30 Q-redhat kernel: unloading Kernel Card Services

Due to this, the actual cards never initialize and are in essence dead.
However, after running the following successive commands:

/sbin/insmod pcmcia_core
/sbin/insmod yenta_socket
/sbin/insmod ds
/etc/rc.d/rc3.d/S24pcmcia start
/sbin/cardmgr

Everything comes up and works great. Thus my main question is how can I get these 3 modules to properly load during boot? I can hack around with putting something in rc.local, but would rather do this properly.

Thanks in advance.

add them to the modules.conf file.

I had considered this but couldn't determine the right syntax from the man page, can you offer what the additional lines I may need would be?

It almost seems as though either the pcmcia_core & yenta_socket drivers aren't loading or the ds driver is set to load before these two and thus can't find what it needs and shuts the cardmgr down.

Any ideas??

So you want ds, when loaded to find yenta_socket and pcmcia_core loaded. There is nothing seriously wrong with adding the /sbin/insmod lines to rc.local. If you added them to /etc/modules.conf, they would load sooner, that's all. To me, I would like all module-load-unload-related-info to go under /etc/modules.conf, if it works.

/sbin/modprobe is recommended over plain /sbin/insmod. modprobe kind of wraps insmod in some fashion, thereby facilitating higher level features.

Try..
May work or not depending on your startup scripts, I guess. Also, the redhat version of modutils are different that GNU modutils, I've heard.