[SOLVED] iwlist works but not further (Linksys WUSB54G)

Dear Experts.

I am experiencing some trouble with WUSB54G (v1) on Debian with my Toshiba laptop.

I followed ndiswrapper instruction except for locating inf file, (because the link is not valid) so I used inf file from CD-ROM (this one is identical to v1 driver available at current linksys.com).

http://ndiswrapper.sourceforge.net/m...p/Installation

Things worked well (hardware 5041:2234 is detected), but not quite at final stage.

iwlist wlan0 scan

gives me access points and ESSID's.... but warning message (??)

Warning: Driver for device wlan0 recommend version 18 of Wireless Extension,
but has been compiled with version 17, therefore some driver features
may not be available...

and quality is 0/100 at all cells detected, (Atheros card, D-link DWL-G630 works at same location.)

several after iwconfig's, "iwconfig wlan0" looks like

Warning: Driver for device wlan0 recommend version 18 of Wireless Extension,
but has been compiled with version 17, therefore some driver features
may not be available...

wlan0     IEEE 802.11g  ESSID:off/any  
          Mode:Managed  Frequency:2.462 GHz  Access Point: 00:00:00:00:00:00   
          Bit Rate:2 Mb/s   
          RTS thr:2347 B   Fragment thr:2346 B   
          Encryption key:off
          Power Management:off
          Link Quality:0  Signal level:0  Noise level:0
          Rx invalid nwid:0  Rx invalid crypt:0  Rx invalid frag:0
          Tx excessive retries:0  Invalid misc:0   Missed beacon:0

then dhcpclient cannot find any connection at all....

One thing which may not be good is that "dmesg" gives me the following line:

wlan0: encryption modes supported: WEP; TKIP with WPA; AES/CCMP with WPA

Network here does not accept WEP....., but it is supposed to be off (see iwconfig).

What can I do??

If my driver on CD-ROM is the problem, where can I get the right one??

I appreciate anybodies suggestion.

That warning you are seeing is due to a mismatch between the wireless extensions version in the kernel and the wireless tools package. And yes, this mismatch can cause weird problems. I'm guessing you recently upgraded your kernel and if that is true, you also need to upgrade to the most recent version of wireless tools. I would guess that a newer version would be availble via one of the Debian repositories, or you can download the source code from here and compile your own.

Thanks,

I think I have the latest wireless tool.

# iwconfig -v  
iwconfig  Wireless-Tools version 27
          Compatible with Wireless Extension v11 to v17.

Kernel was re-compiled, so that warning went away, however, no connection yet!!

I'm still a bit suspicious that you do have a mismatch since the earlier warnings said you needed wireless tools v18 and your last post said you have wireless tools v17.

What happens when you try to set the SSID with iwconfig? From the output in your first post, it doesn't look like the card is configured at all.

I have not figured out yet. Following I did.

#1. install (compile) beta version of wireless tool. -> no change.
#2. set ID by iwconfig. -> iwconfig wlan0 showed ID, but no connection.
#3. use old ndiswapper -> no change.

I did not see "warning" at all, so I assume that wireless extension mismatch is gone.

"iwlist wlan0 scan" always gives me "Quality:0/100", ID and AP look good.

#2. set ID by iwconfig. -> iwconfig wlan0 showed ID, but no connection.

Things to check:
- WEP/WPA encryption is turned off at the router
- SSID broadcast is turned on at the router (some drivers seem to need this to associate).
- Try changing mode from Managed to Auto (it shouldn't make a difference but sometimes it does).

I'd also look through your log files (/var/log/syslog and /var/log/messages) and see if ndiswrapper or some other networking bit is complaining about something.

"iwlist wlan0 scan" always gives me "Quality:0/100",

I see that all the time as well, even for networks I'm actively using. I have the feeling the ndiswrapper probably isn't getting all the info a native linux driver can and that is the reason for the 0/100.

Your trick works! (setting ESSID and mode manually.)

Now quality is 100/100.???

Still some trouble.
With some other USB devices, kernel freezes (disk file broken !!! need manual fsck)

Thanks.