Bug 439615
Summary: | NetworkManager wifi fails on logout/login | ||||||||
---|---|---|---|---|---|---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | Emil Librea III <thirdlibrea> | ||||||
Component: | kernel | Assignee: | John W. Linville <linville> | ||||||
Status: | CLOSED CURRENTRELEASE | QA Contact: | Fedora Extras Quality Assurance <extras-qa> | ||||||
Severity: | high | Docs Contact: | |||||||
Priority: | low | ||||||||
Version: | 8 | CC: | dcbw, grgustaf, jane.lv, rather.b.sailing, wtogami | ||||||
Target Milestone: | --- | ||||||||
Target Release: | --- | ||||||||
Hardware: | i686 | ||||||||
OS: | Linux | ||||||||
Whiteboard: | |||||||||
Fixed In Version: | 2.6.24.4-64.fc8 | Doc Type: | Bug Fix | ||||||
Doc Text: | Story Points: | --- | |||||||
Clone Of: | Environment: | ||||||||
Last Closed: | 2008-04-03 19:42:37 UTC | Type: | --- | ||||||
Regression: | --- | Mount Type: | --- | ||||||
Documentation: | --- | CRM: | |||||||
Verified Versions: | Category: | --- | |||||||
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |||||||
Cloudforms Team: | --- | Target Upstream Version: | |||||||
Embargoed: | |||||||||
Attachments: |
|
Description
Emil Librea III
2008-03-29 17:06:04 UTC
does it work if you rmmod the driver module for your wireless card while logged out, then modprobe it and log in again? this would indicate a driver problem. What wireless card/hardware do you have? using an Intel 3945abg card on an Acer Aspire 5583WXMi laptop sorry, don't know what you mean by 'rmmod while logged out' (fairly new to linux). in any case, have tried rmmod iwl3945, which successfully kills the connection (while logged in to X from a root terminal). After a few seconds, however, the connection comes back on (don't need to modprobe) and NM picks up the WEP access point from where it left off. i've also realized that rmmoding iwl3945 is the best way to restart NM so that it successfully connects after I log off then log back in. Before I reported this issue, i had to kill NM, NMDispatcher and wpa-supp then restart NM and enter my keyring password to get a successful connection. hope this helps. if not, please advise exact procedure you want me to do. thanks Created attachment 299745 [details]
Message log extract
Message log extract attached right after i execute rmmod iwl3945 Another iwlwifi one for you John... thoughts on how to further debug? Maybe hardware vs. software scanning with disable_hw_scan=1 or something? When an rmmod fixes an issue with NM, I usually find there are driver issues... Created attachment 299753 [details]
var/log/messages output for failing wireless connect
I also suffer from this problem, it is very frustrating as my laptop has 2 logins and this problem means that wireless will only work for the first time login after boot. First association with access point works fine. After logout NetworkManager will not longer connect until reboot. I have attached the output from /var/log/messages which shows the cycle that NetworkManager / wpa_supplicant gets into. I get the following in dmesg output repeated lots of times: wlan0: RX disassociation from 00:30:bd:fb:29:e1 (reason=7) I am happy to try and get any debugging info required if you can provide instructions :) I can confirm that rmmod from a root console after logging out means that the wireless will connect correctly on next login. System Details: uname -a Linux mini-manicminer 2.6.24.3-50.fc8 #1 SMP Thu Mar 20 14:47:10 EDT 2008 i686 i686 i386 GNU/Linux Network card: iwl3945: Intel(R) PRO/Wireless 3945ABG/BG Network Connection driver for Linux, 1.2.26kds iwl3945: Copyright(c) 2003-2008 Intel Corporation Laptop: Acer 5920 Firmware: rpm -qa |grep -i iwl iwl3945-firmware-2.14.1.5-2 Network Manager: NetworkManager-0.7.0-0.6.7.svn3235.fc8 Do you have a line like this in /etc/modprobe.conf? options iwl3945 disable_hw_scan=1 Could you either add it or remove it and try again with/without it to see what difference it may make? tnx - adding the line above to modprobe.conf fixes the problem. is this a fix or a temporary workaround? I would like to believe it is the latter. Let's hope so... I added: options iwl3945 disable_hw_scan=1 to /etc/modules.conf This appears to be a successful workaround, I hope this helps identifying what is wrong with the hardware based scanning. Cheers. Further note, with the disable_hw_scan set wireless also successfully works after suspend / wakeup cycle. Sounds like hardware scan support (which only iwl3945 and iwl4965 use) is broken again... I have just updated to kernel 2.6.24.4-64.fc8, removed the line options iwl3946 disable_hw_scan=1 from /etc/modprobe.conf and looks like the update has fixed the problem. Please advise if you need more information. Ah, thanks for the report! I also tested today with the hw_scan line removed and the problem is NOT fixed for me :) [steve@mini-manicminer ~]$ uname -a Linux mini-manicminer 2.6.24.4-64.fc8 #1 SMP Sat Mar 29 09:54:46 EDT 2008 i686 i686 i386 GNU/Linux I get stuck in the same /var/log/messages cycle as in my attached log extract. Adding the line back in again and everything works. so for me this is not fixed. |