After upgrading to Mageia 2 I have problems with network not working when resuming from suspend or hibernate. The wireless interface seems correctly configured (it has an ip assinged) and woriking . However there is no route defined `sudo ip route` is empty. Trying to reconnect to the network with drakroam makes everything work fine.
Created attachment 2439 [details] log of network failure Attached system logs of network beeing resumed after suspend.
Created attachment 2440 [details] log of network connecting correctly Attached system logs of a working connection made with drakroam after a suspend.
Assignee: bugsquad => mageiaSummary: no network after suspend or hibernate => wifi network has no route after suspend or hibernateSeverity: normal => major
*** Bug 6426 has been marked as a duplicate of this bug. ***
CC: (none) => lists.jjorge
Have there been any updates or solutions? I have to reconnect every time I come out of hibernation. Thank you, Jeff
CC: (none) => jeffrobinsSAEHardware: i586 => All
No, I could not find what triggers this regression. As workaround, I use "route add default gw ipaddress_of_gateway" instead of a full reconnect
I switched to networkmanager and this solved the issue for me.
I'm seeing this now as well under KDE. I have the laptop on AC constantly, and I have Power Management set to only shut off the screen when the lid is closed. Recently (~1 month), KDE started ignoring this setting and hibernating, and I see the same behavior - the wireless does not reconnect automatically. I have to open network applet and reconnect manually. NetworkManager is not involved here. So the symptoms match
CC: (none) => ftg
(In reply to comment #7) > I'm seeing this now as well under KDE. I have the laptop on AC constantly, and > I have Power Management set to only shut off the screen when the lid is closed. > Recently (~1 month), KDE started ignoring this setting and hibernating, and I > see the same behavior - the wireless does not reconnect automatically. I have > to open network applet and reconnect manually. > > NetworkManager is not involved here. So the symptoms match This bug depends on WiFi hardware : only 1 of my 3 laptops is affected by it. It has a Broadcom BCM43224. Using a USB WiFi stick does not trigger the bug.
Having recently gotten NM to work on my laptop, I should mention that the failure to reconnect only occurs when NM is *not* controlling the device. If NM *is* controlling the wireless (a broadcom as well), it reconnects just fine.
My wife has the same issue. I think the issue is that the DHCP lease has ended but that NM is restarting the interface on resume whereas drakx_net (really some pm script) doesn't. It works fine for ethernet as ifplugd will detect the link change and proceeds with dhcp-client
CC: (none) => thierry.vignaud
(In reply to comment #10) I don't think so : the ip address is given, it is only the route which is missing. And this only happens on broadcom hardware on MGA2 - not on MGA1 - AFAIK. I think the driver behaviour is th problem as changing between the mess of broadcom drivers changes this bug also. My laptops with Intel Wifi also resume nicely without NM.
This message is a reminder that Mageia 2 is nearing its end of life. Approximately one month from now Mageia will stop maintaining and issuing updates for Mageia 2. At that time this bug will be closed as WONTFIX (EOL) if it remains open with a Mageia 'version' of '2'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Mageia version prior to Mageia 2's end of life. Bug Reporter: Thank you for reporting this issue and we are sorry that we may not be able to fix it before Mageia 2 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Mageia, you are encouraged to click on "Version" and change it against that version of Mageia. 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 Mageia release includes newer upstream software that fixes bugs or makes them obsolete. -- The Mageia Bugsquad
Mageia 2 changed to end-of-life (EOL) status on ''22 November''. Mageia 2 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Mageia please feel free to click on "Version" change it against that version of Mageia and reopen this bug. Thank you for reporting this bug and we are sorry it could not be fixed. -- The Mageia Bugsquad
Status: NEW => RESOLVEDResolution: (none) => OLD