I've been networking happily with FC2 on a Dell Latitude C640 laptop. When I booted, it used to connect to a wireless AP using orinoco_cs.

Now it doesn't start by itself any more. Searching around I found steps that fix it:
modprobe yenta_socket
cardmgr
ifup eth1
But this lasts only for one session.

How could I have broken it? I got curious and using system-config-network, created an AdHoc wireless connection eth0:1. (It was seen sucessfully by netstumbler on a separate WinXP laptop.) I removed that experimental connection again. But apparently something permanently changed.

How is PCMCIA normally configured? As it simply worked, I'm a bit foggy on that.

More generally, what's the preferred way to automatically 'modprobe' a module (yenta-socket) at boot time?

Thanks!

/Quigi

Normally in a Redhat or Redhat clone the pcmcia is a service that is started during boot. To see if service is started after boted run the command ' /sbin/service --status-all | grep cardmgr '. Now if this is running check your /etc/sysconfig/network-scripts/ifcfg-eth1 and see if the line ' Onboot = yes ' exist. If not then add it or change no to yes. Might as well look at ifcfg-eth0 and make it no on boot. Reason this may happen if the service NetworkManager is running. I myself do not like the way it works on my system so I don't use. I just have a series of scripts to make the most common connection settings per nic based on location I go. If none of this works you can add those lines to /etc/rc.local at the end. This is one of the last few scripts run during boot. Note on this is use the full path of each command. so for ifup use /sbin/ifup.

Brian1

Hi Brian1,

No, cardmgr fails at boot. As module yenta-socket is missing (WHY?) it errors out with "cardmgr[30835]: no sockets found!". I suppose I could put some "modprobe yenta-socket" in some rc script. I just wonder how loading of kernel modules was working before I played with an ad-hoc connection. (A new question reminded me of this open issue.)