Bug 6405 - Wifi won't reconnect after resume from suspend to ram
Summary: Wifi won't reconnect after resume from suspend to ram
Status: RESOLVED FIXED
Alias: None
Product: Mageia
Classification: Unclassified
Component: RPM Packages (show other bugs)
Version: Cauldron
Hardware: i586 Linux
Priority: Normal normal
Target Milestone: ---
Assignee: Olivier Blin
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2012-06-10 22:15 CEST by Tamás Hajdu
Modified: 2012-10-01 17:22 CEST (History)
0 users

See Also:
Source RPM: drakx-net
CVE:
Status comment:


Attachments

Description Tamás Hajdu 2012-06-10 22:15:39 CEST
Description of problem:
Wifi won't autoconnect/reconnect the network after resume (and the network still available of course)

Version-Release number of selected component (if applicable):
Cauldron 

How reproducible:
Always

Steps to Reproduce:
1.add wifi network to known network
2.connect
3.suspend/resume
4.net_applet shows the interface active, but it's not connected and stays that way.

HW:
rhinkpad r61
intel 4965AGN (kedron)
Comment 1 Tamás Hajdu 2012-06-18 19:27:24 CEST
I have updated my system and now it seems, the wifi reconnects after resume and also if network lost. I also added option swcrypto=off, what was mentioned for iwlagn, but anyway tried that too. Now I have removed it as I think there is no such option for iwl4965. Anyway the half of the problem is solved, so now it is reconnecting, but still keeps losing the network. And also after a couple of tries (absolutely random as I feel it) it can't reconnect. Trying it manually drakroam brings up the settings window, with all the settings ok, but one. Somehow it switches WEP instead of WPA2/PSK.
Manuel Hiebel 2012-06-20 15:05:58 CEST

Assignee: bugsquad => mageia
Source RPM: (none) => drakx-net

Comment 2 Tamás Hajdu 2012-06-20 18:15:00 CEST
I think I have written too early. The bug is still applies to my system at least. Sometimes wifi is reconnected, sometimes not. The only thing which had not happened to me in the last week or so, is that drakroam had not forgotten the encryption type.
Comment 3 Marja Van Waes 2012-07-06 15:04:13 CEST
Please look at the bottom of this mail to see whether you're the assignee of this  bug, if you don't already know whether you are.


If you're the assignee:

We'd like to know for sure whether this bug was assigned correctly. Please change status to ASSIGNED if it is, or put OK on the whiteboard instead.

If you don't have a clue and don't see a way to find out, then please put NEEDHELP on the whiteboard.

Please assign back to Bug Squad or to the correct person to solve this bug if we were wrong to assign it to you, and explain why.

Thanks :)

**************************** 

@ the reporter and persons in the cc of this bug:

If you have any new information that wasn't given before (like this bug being valid for another version of Mageia, too, or it being solved) please tell us.

@ the reporter of this bug

If you didn't reply yet to a request for more information, please do so within two weeks from now.

Thanks all :-D
Comment 4 Tamás Hajdu 2012-07-07 16:20:13 CEST
Hi!

The problem persists, the applet shows the wifi is not connected after resume, but drakroam still reports it to be connected. 

If you need any info please ask!

HW: Thinkpad R61, Intel 4965abn, using n.

Status: NEW => ASSIGNED

Comment 5 Tamás Hajdu 2012-10-01 17:22:04 CEST
problem disappeared with updates. Though the sleep through kde4 suspend mechanism (qdbus) works only once, I have filed an other bug report for that.

Status: ASSIGNED => RESOLVED
Resolution: (none) => FIXED


Note You need to log in before you can comment on or make changes to this bug.