Re: dldr_wpa_supplicant doesn't see wlan0

Hi,

can you try to use the 'iwlist scanning' command in a root shell? As 
long as you do not see an access point in the output of that command, 
you will be unable to use DriverLoader, no matter if you use encryption 
or not.

If you can't see an access point, please make sure that your wireless 
card is activated. It is possible that you might have to press a button 
or look in the BIOS for an option to activate the card. It is also 
possible that you will have to press the button in Windows XP and then 
reboot in Linux as some wireless button requires a driver to make it 
work. Such Linux drivers and information on how to use them might be 
available at :

http://rfswitch.sourceforge.net/?page=laptop_matrix

Please also try with different versions of the Windows XP driver.

Make sure that your access point broadcast it's ESSID and make sure that 
the ESSID string is not empty. You should also disable all MAC address 
filtering and make sure that the channel is set between 1 and 11. If 
your access point have a CTS protection mode, please disable it. You 
should also make sure that you use the latest firmware version for your 
access point.

Regards,


Jonathan
Technical specialist / Linuxant
www.linuxant.com
[email protected]



Jonathan Byrne wrote:
> I just installed driverloader on Kubuntu Dapper (6.06) (but using a 
> Breezy 2.6.12-9-386 kernel because the Dapper kernel won't boot on this 
> machine for some as yet undetermined reason) with the Windows drivers 
> for a Linksys WPC54G (ver. 3) running on a Thinkpad 600X. The 
> driverloader web interface shows device wlan0 using driver lsbcmnds and 
> the MAC address of the WPC54G, so this seems to have gone successfully.
> 
> The wpa_supplicant that comes with Kubuntu complained that driverloader 
> was an unsupported driver, so I removed it and installed 
> dldr-wpa-supplicant. When I run dldrwpaconfig, it says:
> 
> "Automatically selected the wireless interface 'wlan0'. Supports WPA and 
> WPA2 with TKIP and AES.
> 
> ERROR: No wireless interface were detected by the 'iwlist' tool for 
> the 'wlan0' interface. Before you attempted to use this supplicant, you 
> should make sure that you are able to use DriverLoader with WEP enabled 
> first."
> 
> Trying WEP seems counterintuitive, insofar as if it can't detect an 
> interface, whether WEP works or not is neither here nor there (and 
> since my network is WPA-only, that won't work either without 
> reconfiguring to use WEP, but I can do that if needed).
> 
> Also, using the iwlist command in a shell does gather information from 
> the card, so that seems to go against what dldrwpaconfig is saying 
> about iwlist.
> 
> Does anyone have any ideas?
> 
> TIA,
> 
> Jonathan
> _______________________________________________
> driverloader mailing list
> [email protected]
> https://www.linuxant.com/mailman/listinfo/driverloader