Bug 9951

Summary:	Drakroam defaults to "Broadcom wireless" even when active interface is wlan0
Product:	Mageia	Reporter:	Bill Wilkinson <wrw105>
Component:	RPM Packages	Assignee:	Mageia Bug Squad <bugsquad>
Status:	RESOLVED FIXED	QA Contact:
Severity:	normal
Priority:	Normal	CC:	eeeemail, mageia, thierry.vignaud, tmb, wrw105
Version:	Cauldron
Target Milestone:	---
Hardware:	i586
OS:	Linux
Whiteboard:
Source RPM:		CVE:
Status comment:

Description Bill Wilkinson 2013-05-02 22:10:21 CEST

Would it be possible for drakroam to check for the active wireless interface on startup?  When adding a new access point, drakroam always defaults to "Broadcomm..." and attempts to add the wl driver, even when things are working well on wlan0 with either the ssb or b43 driver.  Blacklists in adding the wl driver will stop a working driver.

This has been a problem for me as the wl driver doesn't present with a device node in configuring the wifi device.


Reproducible: 

Steps to Reproduce:

Comment 1 claire robinson 2013-05-03 11:26:22 CEST

This may be resolved when Thomas finalises the broadcom stuff he's been working on.

I'll add some CC's who should know more.

CC: (none) => thierry.vignaud, tmb
Version: 3 => Cauldron

claire robinson 2013-05-03 11:26:32 CEST

CC: (none) => eeeemail

Comment 2 Manuel Hiebel 2013-05-05 12:37:13 CEST

same with the last updates ? 
also there is livecd test iso if you want try, see this comment: https://bugs.mageia.org/show_bug.cgi?id=7828#c48

Comment 3 Bill Wilkinson 2013-05-05 23:49:08 CEST

Hi, Manuel!

I've tried the livecd, and it works beautifully!  If Thomas is getting a cc of this, excellent job!

Drakroam defaulted to wlan0, and after entering the router key, all connected and worked properly.

CC: (none) => wrw105

Comment 4 Sander Lepik 2013-05-05 23:52:03 CEST

Closing then..

Status: NEW => RESOLVED
CC: (none) => sander.lepik
Resolution: (none) => FIXED