GNOME Bugzilla – Bug 605880
[zd1201] NM makes my wireless connection unusable
Last modified: 2014-09-23 10:10:33 UTC
Hello. This case is very strange. First, I own a ZyXEL ZyAIR B-220 802.11b adapter: http://descargardrivers.es/photos/Z/y/x/ZyxelZyAIR-B-220-1-pic.jpg It uses zd1201 module which is inside the kernel. However I couldn't connect to internet because of NetworkManager. I configured it but it kept trying to connect but never finished and started again and again. My adapter works out of the box if I remove network-manager-gnome, restart and I configure my connection using iwconfig. But again if I start NetworkManager, my connection will stop working. I cannot get it working again by stopping the NetworkManager daemon. I need to unplug the usb stick and unload the zd1201 module. Then I can configure my connection manually again. I'm running Ubuntu 9.10 and package versions are: network-manager 0.8~a~git.20091013t193206.679d548-0ubuntu1 network-manager-gnome 0.8~a~git.20091014t134532.4033e62-0ubuntu1 Related info (I'm not the only one!): https://bugs.launchpad.net/ubuntu/+bug/293706 https://bugs.launchpad.net/ubuntu/+source/hal/+bug/115812 Thanks in advance.
This may be related: https://bugzilla.gnome.org/show_bug.cgi?id=603409
Created attachment 150663 [details] daemon.log In this log you can see how I can get IP by DHCP and then I start NetworkManager and it cannot connect. The wep key correct, I have modified it in the log.
Looks like the driver simply isn't connecting; we'd need to get wpa_supplicant debug output for that. Can you get some supplicant debug output by following the directions here? http://live.gnome.org/NetworkManager/Debugging Look in the "Debugging WiFi Connections" section. That will help us determine why the driver is failing to connect to the AP.
Created attachment 150718 [details] wpa_supplicant.log Here is the logfile but correct me if I'm wrong: I'm not using WPA, may this file help?
Created attachment 150720 [details] Verbose wpa_supplicant.log I have created a config file like the one here: http://lists.freebsd.org/pipermail/freebsd-doc/2009-January/015375.html and I removed an undocumented parameter "-s" of wpa_supplicant. Now the output is much more helpful I hope :)
Also, for what it's worth, zd1201 linux driver doesn't support WPA. http://bugzilla.kernel.org/show_bug.cgi?id=5631
Hello Dan, did you have time to look at the logs? Any news? I don't have the usb stick right now with me because I have moved and I left it at home and so, I cannot provide more logs at the moment. But if you located the problem, I would pleasantly try to start talking with some driver maintainer or kernel hackers in order to get it fixed.
Closing this bug report as no further information has been provided. Please feel free to reopen this bug if you can provide the information asked for. Thanks!
(In reply to comment #8) > Closing this bug report as no further information has been provided. Please > feel free to reopen this bug if you can provide the information asked for. > Thanks! Fabio the status was NEEDINFO but the information is provided...
A few questions: 1) what kernel version? 2) what kind of WEP key does your AP use? passphrase? hex key? ascii key?
It was ubuntu 9.10, so I guess kernel was some revision of 2.6.31 (I don't have that desktop computer here right now). The WEP key my AP uses is hexadecimal.
The supplicant logs indicate (as long as the config file is correct for the network) that the driver is just broken upstream. I think I have a zd1201, so I'll try to investigate why the driver fails with wpa_supplicant but works with iwconfig. The driver is pretty old and doesn't support WPA at all, so perhaps there's something we could do in wpa_supplicant to make it cooperate better.
(the point here that wpa_supplicant is used to control all wifi connections, and wpa_supplicant is certainly capable of doing unencrypted and WEP connections too. And if some driver doesn't work with wpa_supplicant, we need to fix wpa_supplicant or the driver or both.)
Still valid?
(In reply to comment #14) > Still valid? Pavel, I think we can close it but I doubt if it should be marked as resolved.
Ok I found you can say a reason. Closed now.