You are not logged in.
The adapter wad recognized by the system. It was using the rtl8187 module. When I type iwconfig, there is an entry of wlan0. The result of "iwlist scan" looks to be just right. But when I type "iwconfig wlan0 essid ...", the link quality, signal level are all 0. However, in the result of "iwlist scan", these values are non-zero.
Then I started to wonder maybe rtl8187 is not totally compatible with this card. Therefore I installed ndiswrapper, and downloaded the inf files for nearly every version NETGEAR has supplied. I followed the instructions in http://wiki.archlinux.org/index.php/Wir … diswrapper . After I disabled rtl8187 and enabled ndiswrapper in rc.conf, "iwlist scan" begins to show no meaningful results at all. Sometimes it finds a "managed" source with essid "", sometimes it just finds nothing. no other results have been found.
I am confused...
How should I handle this? Any other one has similar experiences?
Offline
when I type "iwconfig wlan0 essid ...", the link quality, signal level are all 0. However, in the result of "iwlist scan", these values are non-zero.
iwconfig displays the status of your own interface, iwlist the status of other wifi devices within range. They will be different. If you're getting zero values locally, you are not associating correctly - I expect it also displays "Not Associated".
After your connection attempt, check your logs for details - if it fails, there will be an error message to help you on your way.
Offline
Yes, "Access Point: Not-Associated".
In dmesg's result:
wlan: authenticated
wlan0: associate with AP 00:18:3a:ae:d0:74
wlan0: associate with AP 00:18:3a:ae:d0:74
wlan0: associate with AP 00:18:3a:ae:d0:74
wlan0: association with AP 00:18:3a:ae:d0:74 timed out
Where else should I look at to find interesting logs?
It's now the rtl8187 module. So how, normally, should I handle this?
Thank you for your reply
Last edited by xuehuichao (2009-01-12 00:20:17)
Offline
Without any further detail, my best guess is that you're out of range of that particular AP.
Offline
It is very close to the AP. That is not a problem.
I've googled regarding this problem. It seems that something in kernel's configuration is not compatible with WG111v2. I'll try to recompile the kernel to solve this problem.
Thank you for your help
Offline