[driverloader] Cisco 350 MiniPCI, WPA -- any success stories?

Linuxant support (Jonathan) support at linuxant.com
Wed Sep 29 10:23:51 EDT 2004


before you attempt to use WPA, please try with or without WEP to see if 
you are able to connect and use your wireless interface.

Since you have problems with the 'iwlist scanning' command, please try 
with different versions of the Windows XP driver to see if there is a 

If you require more assistance, please send at support at linuxant.com the 
output of 'dumpdiag'. Type the following in a root shell:

dldrconfig --dumpdiag

Just send us the generated file located in /tmp 
('driverloaderdiag.txt'). It'll help us solve the problem.


Technical specialist / Linuxant
support at linuxant.com

Steven Ihde wrote:
> I'm trying to get the Cisco 350 MiniPCI adapter in my ThinkPad T30 to
> work with WPA-PSK security.  I'm running Debian sarge with the
> prebuilt 2.6.8-1-686 kernel.
> Does anybody have success or failure stories to report?  I haven't seen any
> reports out there describing success or failure either way.
> I'll describe the problems I'm having.  Installation seemed to go
> fine.  After a cold boot, encouraging messages appear in the log (note
> WPA is listed as supported):
> Sep 28 15:13:29 localhost kernel: wlan0: New link status: Disconnected (0002)
> Sep 28 15:13:29 localhost kernel: wlan0: WPA, TKIP, WEP128, WEP64 supported
> Sep 28 15:13:29 localhost kernel: wlan0: Cisco Systems352 series Wireless LAN Adapter. at 0000:02:02.0 (MAC address 00:02:8A:5C:84:58) ready
> Then I issue "ifconfig wlan0 up", followed by "wpa_supplicant -dd -c
> /etc/wpa_supplicant.conf -i wlan0" and this shows up in the kernel
> log:
> Sep 28 15:20:33 localhost kernel: driverloader: ndisQueryInformation: 802_11_BSSID_LIST st=NOT_SUPPORTED W=0 N=0
> wpa_supplicant acts like it's timing out.
> After killing wpa_supplicant, "iwlist wlan0 scanning" returns "wlan0:
> Interface doesn't support scanning : Operation not supported".
> However, if the very first thing I do after booting is "iwlist wlan0
> scanning", it seems to work exactly once (returning the correct list
> of SSIDs in this area) -- then the next time I run iwlist, it's
> "Failed to read scan data" and the same NOT_SUPPORTED message shows up
> in the kernel log.
> Any idea what's going on here?
> Thanks,
> Steve

More information about the driverloader mailing list