Jonathan Byrne | 2 Jul 02:07 2006

dldr_wpa_supplicant doesn't see wlan0

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?

(Continue reading)

Jonathan Byrne | 2 Jul 03:26 2006

Re: dldr_wpa_supplicant doesn't see wlan0

P.S.

Additional steps I tried included setting my router to B/G mixed network 
with security disabled. I was still unable to connect.
Craig Bell | 2 Jul 05:51 2006
Picon
Picon

Re: dldr_wpa_supplicant doesn't see wlan0

I have the WPC54GS on FC5 on a T30 laptop.  I've tried everything I can 
think of to get WPA working, but so far it is not.  I am working with 
support <at> linuxant.com, but we haven't found the fix yet.

My card works fine with my linksys WRT54GS if I disable security and I 
am in mixed mode.  It usually takes a few minutes after booting to 
finally talk with the router.  I assume you've got your SSID either 
broadcast or in your machine's network settings.  Sorry, I'm not sure 
what else to suggest.

Craig Bell

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 
(Continue reading)

Jonathan Byrne | 2 Jul 06:07 2006

Re: dldr_wpa_supplicant doesn't see wlan0

Hi Craig,

At least you got a little farther than I did <g>

I just bought this card a few days ago, maybe the best suggestion would 
be to put it back in the box and return it to Fry's...

If I didn't like my 600X so much, I'd just get a T-30 with an internal 
Atheros card in it. My wife has one (also running Kubuntu Dapper) and 
it works great.

Jonathan

On Saturday 01 July 2006 20:51, Craig Bell wrote:
> I have the WPC54GS on FC5 on a T30 laptop.  I've tried everything I
> can think of to get WPA working, but so far it is not.  I am working
> with support <at> linuxant.com, but we haven't found the fix yet.
>
> My card works fine with my linksys WRT54GS if I disable security and
> I am in mixed mode.  It usually takes a few minutes after booting to
> finally talk with the router.  I assume you've got your SSID either
> broadcast or in your machine's network settings.  Sorry, I'm not sure
> what else to suggest.
Nick Bruton | 2 Jul 11:18 2006
Picon
Picon

Atheros built in wireless

Hi,

I have just got a new laptop (Toshiba Satellite Pro) with a built in 
wireless card (Atheros AR5005G) But I cant get it to work. All looks OK but 
when I try to ping anything it fails Destination Host Unreachable

Can anyone help please

Thanks Nick

----------------------------------------------------------------------------
Nick Bruton                                          PADI Divemaster #624215
University of Bristol                                Yamaha YZF R1
Computing Service
Tyndall Avenue
Bristol BS8 1UD
Tel: 0117 9288193

Team email: isys-srct <at> bris.ac.uk
Nick Bruton | 2 Jul 13:07 2006
Picon
Picon

Re: Atheros built in wireless

Sorry should have said its a SUSE 10.1 system
kernel is 2.6.16.13-4-default

I can see my access point

Nick

--On Sunday, July 02, 2006 10:18:47 AM +0100 Nick Bruton 
<nick.bruton <at> bristol.ac.uk> wrote:

> Hi,
>
> I have just got a new laptop (Toshiba Satellite Pro) with a built in
> wireless card (Atheros AR5005G) But I cant get it to work. All looks OK
> but when I try to ping anything it fails Destination Host Unreachable
>
> Can anyone help please
>
> Thanks Nick
>
> -------------------------------------------------------------------------
> ---
> Nick Bruton                                          PADI Divemaster
> #624215
> University of Bristol                                Yamaha YZF R1
> Computing Service
> Tyndall Avenue
> Bristol BS8 1UD
> Tel: 0117 9288193
>
(Continue reading)

Linuxant support (Jonathan | 3 Jul 22:29 2006

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
(Continue reading)

Linuxant support (Jonathan | 3 Jul 22:34 2006

Re: Atheros built in wireless

Hi,

please make sure that the wireless interface is correctly configured. On 
SuSE 10.1, we recommend the use of NetworkManager for this task which is 
installed by default.

If you require more assistance, while you think you are connected to the 
access point with NetworkManager, please send at support <at> linuxant.com 
the output of the following commands in a root shell:

---
dldrconfig --info
iwlist wlan0 scanning
ifconfig -a
iwconfig
ip route
ip addr
cat /etc/resolv.conf
ping www.linuxant.com -I wlan0 -c 5
ping 63.246.136.80 -I wlan0 -c 5
tail -n 30 /var/log/messages
---

The commands above expects that your wireless interface is named 
'wlan0', which is the default on SuSE systems.

Regards,

Jonathan
Technical specialist / Linuxant
(Continue reading)

Marty Huntzberry | 4 Jul 01:26 2006
Picon
Picon

using driverloader on one pc with 2 kernels

I have 2 kernels on my pc with a wireless Belkin PCI card and a licensed version of driver loader.  The kernels
are 2.4.32 and 2.6.17.3 and I have an
old 200 MHz pc that I use as a server.  I'd like to see which kernel uses the least resources memorywise on my
server but can only do this if my
wireless card is working.  The instructions to install driverloader say that previous releases must first
be uninstalled.  Could I install the same
version in each kernel and have it work in both?  How-I'm installing from the source tarball?

Marty
Linuxant support (Jonathan | 4 Jul 17:02 2006

Re: using driverloader on one pc with 2 kernels

Hi,

DriverLoader can be uninstalled using the 'dldrconfig --uninstall' 
command in a root shell, this will work with all the different packages 
of DriverLoader, even with the source tarball (generic package in the 
TAR format).

You can use a generic package of DriverLoader with multiple kernels 
without any problems. Simply install DriverLoader while one of the 
kernel is booted, it doesn't matter which one. When you will boot the 
machine with another kernel, the DriverLoader module will be 
automatically built on boot for that new kernel. This will not affect 
your DriverLoader installation with the former kernel, it will still 
work when you will boot the former kernel.

Regards,

Jonathan
Technical specialist / Linuxant
www.linuxant.com
support <at> linuxant.com

Marty Huntzberry wrote:
> I have 2 kernels on my pc with a wireless Belkin PCI card and a licensed version of driver loader.  The kernels
are 2.4.32 and 2.6.17.3 and I have an
> old 200 MHz pc that I use as a server.  I'd like to see which kernel uses the least resources memorywise on my
server but can only do this if my
> wireless card is working.  The instructions to install driverloader say that previous releases must
first be uninstalled.  Could I install the same
> version in each kernel and have it work in both?  How-I'm installing from the source tarball?
(Continue reading)


Gmane