Description of problem: I work on wifi connection with iwl3945 driver. After wake up from suspend, connection doesn't work automatically. When I try to choose networks available I see all networks twice and when I try to choose my network, it doesn't work. I have to add my hidden network one more time in network setting menu. Additionally connection to hidden networks take too long time. Below could be found logs from dmesg: [10769.737974] r8169 0000:02:00.0: eth0: link down [10769.739342] ADDRCONF(NETDEV_UP): eth0: link is not ready [10769.823309] iwl3945 0000:08:00.0: Error setting Tx power (-5). [10769.825696] ADDRCONF(NETDEV_UP): wlan0: link is not ready [10863.384590] wlan0: authenticate with 00:22:6b:86:8a:57 (try 1) [10863.393320] wlan0: authenticated [10863.398943] wlan0: associate with 00:22:6b:86:8a:57 (try 1) [10863.415601] wlan0: RX AssocResp from 00:22:6b:86:8a:57 (capab=0x411 status=0 aid=1) [10863.415606] wlan0: associated [10863.435640] ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready [10874.002059] wlan0: no IPv6 routers present Version-Release number of selected component (if applicable): [root@Akurat ~]# rpm -qa|grep -i networkmanager NetworkManager-glib-0.8.999-2.git20110509.fc15.x86_64 NetworkManager-gnome-0.8.999-2.git20110509.fc15.x86_64 NetworkManager-0.8.999-2.git20110509.fc15.x86_64 Steps to Reproduce: 1. Suspend 2. Wake up 3. Check Actual results: It doesn't connect automatically. Expected results: It should connect to prefer network after wake up.
The same problem after reboot
Does # rmmod iwl3945 # modprobe iwl3945 help after wakeup? (In reply to comment #1) > The same problem after reboot Do you mean that even right after boot it doesn't work? Or after reboot followed with next suspend/wake? Please could you post your /var/log/messages file.
It is sufficient to choose my networks, I haven't to remove module and install one more time. I mean that wifi works after reboot automatically, but after suspend and wake it doesn't work.
Are the duplicated networks in Gnome shell applet or nm-applet? Could you suspend/wake up the computer and grab /var/log/messages file and nm-tool output?
Created attachment 499179 [details] message logs
Created attachment 499180 [details] nm-tool grab I couldn't find my hidden networks in nm-tool, but I could choose in Network Manager icon in right top side
No I don't have duplicated networks
No I have this problem after power down/power up too. fragment of dmesg: [ 24.903810] r8169 0000:02:00.0: eth0: link down [ 24.904551] ADDRCONF(NETDEV_UP): eth0: link is not ready [ 25.247562] iwl3945 0000:08:00.0: loaded firmware version 15.32.2.9 [ 25.312590] iwl3945 0000:08:00.0: Error setting Tx power (-5). [ 25.315143] ADDRCONF(NETDEV_UP): wlan0: link is not ready fragment of /var/log/messages: May 17 23:47:47 Akurat NetworkManager[822]: <info> (wlan0): supplicant interface state: starting -> ready May 17 23:47:47 Akurat NetworkManager[822]: <info> (wlan0): device state change: unavailable -> disconnected (reason 'supplicant-available') [20 30 42] May 17 23:47:47 Akurat NetworkManager[822]: <info> (wlan0): supplicant interface state: ready -> inactive It seems that logs are the same
I have a similar problem. I have add "intel_iommu=off" in my grub.conf. Now, all work perfectly. My card is intel 5300.
This message is a notice that Fedora 15 is now at end of life. Fedora has stopped maintaining and issuing updates for Fedora 15. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At this time, all open bugs with a Fedora 'version' of '15' have been closed as WONTFIX. (Please note: Our normal process is to give advanced warning of this occurring, but we forgot to do that. A thousand apologies.) Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, feel free to reopen this bug and simply change the 'version' to a later Fedora version. Bug Reporter: Thank you for reporting this issue and we are sorry that we were unable to fix it before Fedora 15 reached end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged to click on "Clone This Bug" (top right of this page) and open it against that version of Fedora. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete. The process we are following is described here: http://fedoraproject.org/wiki/BugZappers/HouseKeeping