Reported for focus39 Description of problem: Wifi connection doesn't come up, after configuration with drakx-net. Fabricant: âAtheros Communications Description: âAR8131 Gigabit Ethernet Connexion 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)
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
some errors in /var/log/syslog ?
The problems connections are present only at the first boot. After the reboot, the wifi works. You can access to the syslog file here : http://www.mageialinux-online.org/upload/syslog_c9f15.txt
Severity: major => normal
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.
Try: service networkmanager stop systemctl disable NetworkManager.service (reboot) NM is known to interfere with wireless interfaces even when they aren't being managed by NM.
CC: (none) => ftg
Thanks Frank! That got mine to work!
Hi, 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 :) Cheers, marja
Keywords: (none) => NEEDINFO
Hello, Problem is still valid. A other user reported it. http://www.mageialinux-online.org/forum/topic-13158+atheros-ar9285.php He found a workaround with desinstallation of networkmanager.
CC: (none) => balcaen.john, r.wobben
@John : Can you take a look at this bug ? Roelof
@roelof There is nothing i can do on this.
CC: balcaen.john => (none)
CC: (none) => mageia, tmb
@blino or @tmb : Can you shine a light on this matter ? Roelof
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.
Focus39 does not give any news, but indicated that the problem is solved. Thus, we can close.
Status: NEW => RESOLVEDResolution: (none) => FIXED