| View previous topic :: View next topic |
| Author |
Message |
Number6 n00b

Joined: 24 Nov 2003 Posts: 11 Location: Las Vegas, NV, USA
|
Posted: Sun Jul 13, 2008 3:46 pm Post subject: (Solved) PCMCIA loads manually but not automatically @boot? |
|
|
So I've been installing Gentoo on a Dell 8200 laptop.
All the great documentation on the site has been very helpful. I've got a working kernel (without using genkernel!) and a functional KDE desktop.
Now, I'm just trying to get a few last things working and Google doesn't seem to help anymore.
I have a wireless pcmcia card. So before I can get the wireless working, I got to add in PCMCIA support.
I've spent about a day and a half trying different compile options, but I can't get PCMCIA support to work when added in the boot runlevel. I did check the documentation but I didn't get anything helpful there.
However, I can compile pcmcia support as a module, i82092 support as a module, yenta_socket as a module and it still fails on bootup. BUT, all I do after I login is type "modprobe i82092" and then "modprobe pcmcia" and then it works and then I can see my wireless card when I do a lspci.
What am I missing here? Why won't pcmcia work while booting? I get the following error while booting: "cardmgr failed to start. Make sure you have PCMCIA modules built or support compiled into the kernel."
Any help would be greatly appreciated. Thanks!
Last edited by Number6 on Sun Jul 13, 2008 6:57 pm; edited 1 time in total |
|
| Back to top |
|
 |
cwr Veteran

Joined: 17 Dec 2005 Posts: 1288
|
Posted: Sun Jul 13, 2008 4:38 pm Post subject: |
|
|
I compile PCMCIA support into the kernel; I don't really see why you'd want
it as a module, since you aren't going to rip the PCMCIA socket off the motherboard.
The wireless card driver (orinoco_cs in my case) gets built as a module, and udev
and hal then set up networking via the /lib/udev and /etc/init.d/net.whatever scripts.
(Don't ask me how they all fit together; it's a maze of twisty little shell scripts, and
I've never really understood the exact path through them.)
Anyhow, it mostly seems to work. When it doesn't I force it with a shell script:
#!/bin/sh
# Load the orinoco driver.
modprobe orinoco_cs
# Bring up the interface.
ifconfig eth1 up
# Call the dhcp client.
/sbin/dhclient -e PEER_ROUTERS=no -e PEER_DNS=no -e PEER_NTP=no -e IF_METRIC=2000 -q -1 -pf /var/run/dhclient-eth1.pid eth1
# Show the routing table
route -n
# eof
Good luck - Will |
|
| Back to top |
|
 |
Number6 n00b

Joined: 24 Nov 2003 Posts: 11 Location: Las Vegas, NV, USA
|
Posted: Sun Jul 13, 2008 6:58 pm Post subject: |
|
|
Solved
I was able to get it to work when compiled in natively. |
|
| Back to top |
|
 |
|
|
You cannot post new topics in this forum You cannot reply to topics in this forum You cannot edit your posts in this forum You cannot delete your posts in this forum You cannot vote in polls in this forum
|
|