Bug 5863 - Wifi connection doesn't come up
Summary: Wifi connection doesn't come up
Alias: None
Product: Mageia
Classification: Unclassified
Component: RPM Packages (show other bugs)
Version: Cauldron
Hardware: i586 Linux
Priority: Normal normal
Target Milestone: ---
Assignee: Mageia Bug Squad
QA Contact:
Keywords: NEEDINFO
Depends on:
Reported: 2012-05-12 09:39 CEST by papoteur
Modified: 2013-01-06 11:21 CET (History)
5 users (show)

See Also:
Source RPM:
Status comment:


Description papoteur 2012-05-12 09:39:53 CEST
Reported for focus39
Description of problem:
Wifi connection doesn't come up, after configuration with drakx-net.
Fabricant: âAtheros Communications
Description: âAR8131 Gigabit Ethernet
Bus: âPCI Express
Fabricant: âAtheros Communications
Description: âAR8131 Gigabit Ethernet
Module: âath9k
Mode de fonctionnement : Géré
Mode de chiffrement WPA/WPA2 avec clef prépartagé (PSK)

The available wifi points are showed, but after selected one and entered password, the connection is not established.

The user says that he get a message "Le câble réseau n'est pas branché" (the ethernet wire is not pluged)
Comment 1 Robert Courtright 2012-05-13 23:34:03 CEST
I too am having the same problem with Mageia 2 RC.

It sees all networks but when I out in my password the connection fails.
Mageia 1 and Win 7 both work on same laptop a Dell Inspiron N5040 with a
Atheros AR9285 Wireless card.

CC: (none) => rbcourt

Comment 2 Manuel Hiebel 2012-05-14 17:11:16 CEST
some errors in /var/log/syslog ?
Comment 3 papoteur 2012-05-15 12:36:58 CEST
The problems connections are present only at the first boot. After the reboot, the wifi works.
You can access to the syslog file here :
papoteur 2012-05-15 12:37:16 CEST

Severity: major => normal

Comment 4 Robert Courtright 2012-05-15 14:16:08 CEST
This is not the case here. I've set the connection and rebooted. No Matter what I do the wireless will not connect to my network.
Comment 5 Frank Griffin 2012-05-15 14:41:18 CEST

   service networkmanager stop
   systemctl disable NetworkManager.service

NM is known to interfere with wireless interfaces even when they aren't being managed by NM.

CC: (none) => ftg

Comment 6 Robert Courtright 2012-05-16 05:06:44 CEST
Thanks Frank!

That got mine to work!
Comment 7 Marja Van Waes 2012-05-26 13:05:00 CEST

This bug was filed against cauldron, but we do not have cauldron at the moment.

Please report whether this bug is still valid for Mageia 2.

Thanks :)


Keywords: (none) => NEEDINFO

Comment 8 papoteur 2012-07-13 19:50:30 CEST
Problem is still valid.
A other user reported it.
He found a workaround with desinstallation of networkmanager.
roelof Wobben 2013-01-04 11:31:03 CET

CC: (none) => balcaen.john, r.wobben

Comment 9 roelof Wobben 2013-01-04 11:31:34 CET
@John : Can you take a look at this bug ?

Comment 10 John Balcaen 2013-01-05 21:10:25 CET
There is nothing i can do on this.
roelof Wobben 2013-01-05 21:45:41 CET

CC: balcaen.john => (none)

roelof Wobben 2013-01-05 21:46:32 CET

CC: (none) => mageia, tmb

Comment 11 roelof Wobben 2013-01-05 21:47:05 CET
@blino or @tmb : 

Can you shine a light on this matter ?

Comment 12 Frank Griffin 2013-01-06 04:03:13 CET
NM used to not properly honor NM_CONTROLLED=no, and would screw around with interfaces (especially wireless) that were supposed to be controlled by ifplugd.  I believe it no longer does this.  

The OP should verify whether the problem still occurs with current NM and an /etc/sysconfig/network-scripts/ifcfg-wlan0 (or whatever interface name) that specifies NM_CONTROLLED=no.

The last I heard of problems with ifplugd-controlled wifi in cauldron was that a kernel change had borked ifplugd's ability to start wifi interfaces.  To the best of my knowledge, this has not been fixed, so if the OP is still having the problem, this could be the cause.  However, if it is, removing NM will not make it work.

If that is the cause, you can follow the procedure in bug#2160 to get NM working with wireless under KDE.
Comment 13 papoteur 2013-01-06 11:21:49 CET
Focus39 does not give any news, but indicated that the problem is solved.
Thus, we can close.

Resolution: (none) => FIXED

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