Bug 116414

If you just want to change the default driver on your system, then have a look
in /etc/modprobe.d/prism2.

Please provide 'hwinfo --netcard'

FYI: If your card gets driven by hostap, then wpa_supplicant will be used by  
default to establish the WLAN connection (even non-WPA ones), so you can't  
fully trust hwinfo output. 'rcnetwork status wlan0' gives you some more input.  

Hmm, when I restarted my laptop, the wireless worked correctly, but the driver 
used was hostap_cs!  Very odd.... 
 
I've tried changing it to prism2_cs in Yast.  No errors occur, but even on 
reboot, hostap_cs is used.   
 
iwconfig now seems able to change channels (it definitely did not work before, 
even after reboots).   
 
Even so, here is the output of hwinfo --netcard: 
 
---------------- 
40: PCMCIA 01.0: 0282 WLAN controller 
  [Created at pcmcia.87] 
  UDI: /org/freedesktop/Hal/devices/pcmcia_54785_2 
  Unique ID: M7bu.LiEYpxsybr2 
  Parent ID: ruGf.qcMpx0aRxCB 
  SysFS ID: /devices/pci0000:00/0000:00:02.1/1.0 
  SysFS BusID: 1.0 
  Hardware Class: network 
  Model: "IEEE 802.11 Wireless LAN/PC Card" 
  Hotplug: PCMCIA 
  Socket: 1 
  Vendor: pcmcia 0xd601 
  Device: pcmcia 0x0002 "IEEE 802.11 Wireless LAN/PC Card" 
  Driver: "hostap_cs" 
  Device File: wifi0 
  Device Files: wifi0, wlan0 
  Features: WLAN 
  HW Address: 00:c0:6f:05:54:e4 
  WLAN channels: 1 2 3 4 5 6 7 8 9 10 11 
  WLAN frequencies: 2.412 2.417 2.422 2.427 2.432 2.437 2.442 2.447 2.452 
2.457 2.462 
  WLAN bitrates: 1 2 5.5 11 
  WLAN encryption modes: WEP40 WEP104 
  WLAN authentication modes: open sharedkey 
  Module Alias: 
"pcmcia:mD601c0002f06fn00pfn00pa00000000pbEFCCAFE9pc00000000pd00000000" 
  Driver Info #0: 
    Driver Status: hostap_cs is active 
    Driver Activation Cmd: "modprobe hostap_cs" 
  Driver Info #1: 
    Driver Status: orinoco_cs is not active 
    Driver Activation Cmd: "modprobe orinoco_cs" 
  Driver Info #2: 
    Driver Status: prism2_cs is not active 
    Driver Activation Cmd: "modprobe prism2_cs" 
  Extra Info: IEEE 802.11 Wireless LAN/PC Card 
  Config Status: cfg=no, avail=yes, need=no, active=unknown 
  Attached to: #13 (CardBus bridge) 
---------------- 
 
This seems to indicated that hostap_cs is active and the other drivers are 
not.  That is strange as I specifically set up prism2_cs as the correct driver 
in Yast. 
 
Here is the output from rcnetwork status wlan0: 
 
---------------- 
    wlan0 
    wlan0     configuration: wlan-id-00:c0:6f:05:54:e4 
    wlan0     DHCP client (dhcpcd) is running 
    wlan0     IP address: 10.206.2.253/24 
wlan0     IEEE 802.11b  ESSID:"woodlawn"  Nickname:"thinkpad" 
          Mode:Managed  Frequency:2.422 GHz  Access Point: 00:06:25:55:D9:45 
          Bit Rate:11 Mb/s   Sensitivity=1/3 
          Retry min limit:8   RTS thr:off   Fragment thr:off 
          Encryption key:off 
          Power Management:off 
          Link Quality=92/92  Signal level=-24 dBm  Noise level=-97 dBm 
          Rx invalid nwid:0  Rx invalid crypt:7  Rx invalid frag:0 
          Tx excessive retries:0  Invalid misc:251   Missed beacon:0 
---------------- 
 
How can I force it to use prism2_cs?  I thought I'd done that correctly 
before, but apparently not.  And, it is very odd that hostap_cs is working now 
when it definitely did not before.  I will try plugging the card in an out a 
few times to see if perhaps the card itself is part of the problem. 

You can force to use other drivers by changing the driver to be loaded by 
modifying /etc/modprobe.d/prism2. But it's quite inconvenient, so you may 
rather want to use 'switch_prism_driver' to change the driver. Just call this 
script with hostap, orinoco, or wlan-ng (for prism2_cs) as argument.  
  
As your card is working now, I'll close this bug. Please reopen if there  
remain any problems.