Bug 5854 - wlan0 is configured with a roaming daemon but isn't associated
Summary: wlan0 is configured with a roaming daemon but isn't associated
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: Mageia Bug Squad
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2012-05-11 13:54 CEST by Bjarne Thomsen
Modified: 2013-07-13 00:18 CEST (History)
2 users (show)

See Also:
Source RPM: kernel-desktop
CVE:
Status comment:


Attachments

Description Bjarne Thomsen 2012-05-11 13:54:57 CEST
Description of problem:
RT3090 Wireless 802.11n worked until a few weeks ago, but now there are "problems" when configuring WiFi in MCC. The driver is rt2800pci. Data on problem:
lspcidrake
rt2800pci       : Ralink corp.|RT3090 Wireless 802.11n 1T/1R PCIe
lsmod|grep rt2800pci
rt2800pci              18108  0
rt2800lib              52596  1 rt2800pci
rt2x00pci              14116  1 rt2800pci
rt2x00lib              48294  3 rt2x00pci,rt2800lib,rt2800pci
eeprom_93cx6           13134  1 rt2800pci
ifup wlan0
Wireless device wlan0 is configured with a roaming daemon but isn't associated
Determining IP information for wlan0... failed; no link present.  Check cable?
What does this mean?

Version-Release number of selected component (if applicable):
kernel-desktop-3.3.4

How reproducible:
Now it never works.

Steps to Reproduce:
1.
2.
3.
Thierry Vignaud 2012-05-11 14:44:32 CEST

CC: (none) => mageia
Source RPM: kernel-desktop-3.3.4-1 => kernel-desktop-3.3.4-1, drakx-net

Comment 1 Bjarne Thomsen 2012-05-12 21:15:34 CEST
My WiFi "RT3090 Wireless 802.11n" now works with kernel-3.3.5 and/or some associated other updates.
Comment 2 Manuel Hiebel 2012-05-12 22:29:17 CEST
oh great, closing then, thanks

Status: NEW => RESOLVED
Resolution: (none) => FIXED
Source RPM: kernel-desktop-3.3.4-1, drakx-net => kernel-desktop

Comment 3 Desmond Armstrong 2013-07-13 00:18:16 CEST
I have reported a specific problem with Mageia 3 10727 so I think that a problem is lurking here.

We should never have requirement to reboot when we attach to an unencrypted Wi-Fi. So I am unconvinced that the problem is solved. I am on kernel 3.8.13.4 Certainly if we are attaching to a single Wi-Fi access point there is not a problem except in that a re-boot is required - why?

CC: (none) => desmond.armstrong


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