Hide Forgot
From Bugzilla Helper: User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.6) Gecko/20040312 Description of problem: I have a Linksys WPC 11 v3 wireless card and a Thinkpad 600X notebook. When I insert the WPC11 card the orinoco_cs module is loaded, but no new interface (eth0 or other) shows up. Kudzu show this when the card is in: [ (0) wwalker@traveller:~ ]$ sudo kudzu -p -b pcmcia - class: NETWORK bus: PCMCIA detached: 0 device: eth0 driver: orinoco_cs desc: "Linksys Instant Wireless Network PC Card WPC11 v3" vendorId: 0274 deviceId: 1613 function: 0 slot: 1 Version-Release number of selected component (if applicable): kudzu-1.1.53-1 How reproducible: Always Steps to Reproduce: 1. Insert WPC11 v3 Linksys wireless (802.11b) card Actual Results: ifconfig -a shows no eth or wlan interfaces dmesg shows that orinoco_cs was loaded, but nothing else Expected Results: an interface should have shown up and DHCP should have then happened. Additional info: Thinkpad 600X Fedora Core 2 test2
Do you have a config file for it?
Uh, which config file? one in wireless, or modules.conf?
/etc/sysconfig/network-scripts/ifcfg-eth0 (or whatever the device name is)
[ (0) wwalker@traveller:~ ]$ cat /etc/sysconfig/network-scripts/ifcfg-eth0 # Linksys Instant Wireless Network PC Card WPC11 v3 DEVICE=eth0 ONBOOT=yes BOOTPROTO=dhcp
What sort of kernel messages do you get when you insert the card?
I left the card at the office today. But all it shows in dmesg is the ident lines from orinoco and orinoco_cs modules, nothing else. Apr 4 15:07:08 traveller kernel: orinoco.c 0.13e (David Gibson <hermes@gibson.dropbear.id.au> and others) Apr 4 15:07:08 traveller kernel: orinoco_cs.c 0.13e (David Gibson <hermes@gibson.dropbear.id.au> and others)
What happens if you plug it in and then do 'service pcmcia restart'?
Created attachment 99176 [details] pcmcia restart kernel message output. no idea why it's trying to load prism2.
Can you attach your /etc/pcmcia/config?
Created attachment 99179 [details] /etc/pcmcia/config
Odd, there's really no reason it should be trying prism2. That's where the problem lies. No references to prism2 in /etc/modprobe.conf?
Reinstalled with FC2 final problem went away, worked fine.