[driverloader] Cisco 350 MiniPCI, WPA -- any success stories?
Linuxant support (Jonathan)
support at linuxant.com
Thu Sep 30 11:26:37 EDT 2004
yes, please try with older versions of the Windows XP driver to see if
there is a difference. Even if they do not support WPA, you could try to
see if you have the same problem with 'iwlist scanning' and report
You could also try with previous versions of DriverLoader to see if
there is a difference. You can obtain them at :
Do not try with versions prior to 2.04 and these versions were not
compatible with 188.8.131.52 kernels.
Again, please report success/failure.
Technical specialist / Linuxant
support at linuxant.com
Steven Ihde wrote:
> On Wed, Sep 29, 2004 at 09:23:51AM +0000, Linuxant support (Jonathan) wrote:
>>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.
> I'm able to connect with no security or with WEP, but it seems flaky.
> If the first thing I do is execute dhclient, it works OK. But after
> running dhclient, "iwlist wlan0 scanning" won't work (gives the same
> error message about "Operation not supported"). If I kill dhclient
> and restart it, sometimes it works, sometimes it doesn't. When things
> go bad I see numerous error messages of the form "driverloader:
> ndisSetInformation: 802_11_<whatever> st=<some error> ...". Once this
> happens the driver seems never to recover. Sometimes the interface
> will still transport data in this state (e.g., ping will still work).
> It's still the case that the first "iwlist wlan0 scanning" works fine,
> and then it immediately stops working.
>>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
> You mean, older versions? I don't think older versions of this driver
> support WPA. Have you ever had a report of success with a ThinkPad
> T30 and a Cisco 350 MiniPCI? What driver was used?
> I have an ACPI kernel; could this contribute to the problem? I
> juggled the interrupts around a little to get the wireless card on its
> own interrupt so it didn't have to share, but this made no difference
> that I could see.
>>If you require more assistance, please send at support at linuxant.com the
>>output of 'dumpdiag'. Type the following in a root shell:
>>Just send us the generated file located in /tmp
>>('driverloaderdiag.txt'). It'll help us solve the problem.
> Sent separately to avoid flooding the list.
More information about the driverloader