Bug 9950

Summary: broadcom wifi gives error when searching networks
Product: Mageia Reporter: AL13N <alien>
Component: RPM PackagesAssignee: Base system maintainers <basesystem>
Status: RESOLVED OLD QA Contact:
Severity: normal    
Priority: Normal CC: alien, ennael1, mageia, mageia, marja11, pterjan, thierry.vignaud, tmb
Version: CauldronKeywords: NEEDINFO
Target Milestone: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Source RPM: ldetect-lst CVE:
Status comment:

Description AL13N 2013-05-02 19:15:07 CEST
in net-applet, try to find wifi networks, and when you start it, it gives an error that driver 'x' doesn't work.

you can select a second entry, which does work.

it's extremely annoying and very visible.

Reproducible: 

Steps to Reproduce:
AL13N 2013-05-02 19:15:51 CEST

Priority: Normal => release_blocker
CC: (none) => alien, mageia, pterjan, thierry.vignaud, tmb

Comment 1 Thomas Backlund 2013-05-02 19:42:12 CEST
This is due to my broadcom tests... will soon be fixed.

Assignee: bugsquad => tmb
Source RPM: (none) => ldetect-lst

Comment 2 AL13N 2013-05-02 19:54:47 CEST
oic! in that case, let me know if i can retest liveCD.
Comment 3 AL13N 2013-05-02 19:56:15 CEST
btw: is there a special hardware you need for testing? i can ask around some more for specific hardware...

i think you mentioned bbs or something?
Comment 4 Thomas Backlund 2013-05-04 18:11:26 CEST
There is now new sets of isos to test broadcom wireless configuration

And to make it more fun...
there is now 4 isos so you can test on both i586 & x86_64 and with
both Gnome and KDE4.

NOTE! the isos have "CD" in their name, but most of them are bigger
than 700M so you need a DVD media if you want to burn them,
otherwise I suggest to use a usb stick to boot from, using:

dd if=name_of_iso of=/path/to/usb/stick bs=1M

And to find the isos:

http://mirrors.kernel.org/mageia/people/tmb/mga3-wl-test/
http://ftp.acc.umu.se/mirror/mageia/people/tmb/mga3-wl-test/
http://distrib-coffee.ipsl.jussieu.fr/pub/linux/Mageia/people/tmb/mga3-wl-test/

(and soon on any mirror carrying mageia people/tmb/mga3-wl-test/ tree)
Comment 5 Anne Nicolas 2013-05-05 22:11:24 CEST
Reporter please test this new iso as soon as possible as we are starting the very last week for bug fixes before final release

CC: (none) => ennael1

Comment 6 AL13N 2013-05-05 23:59:28 CEST
ah right, i sent an email to -dev ML (and thomas) with my findings

in short, it's ok-ish, but i have some rfkill weirdness going on, and my button stays red, even if it works.
Comment 8 Sander Lepik 2013-05-06 08:35:17 CEST
bcma doesn't seem to control lights/buttons yet. But if the network is now usable I will decrease priority.

Priority: release_blocker => Normal
CC: (none) => sander.lepik
Severity: major => normal

Comment 9 AL13N 2013-05-06 10:20:47 CEST
not sure if it should drop in priority, if the light keeps being red, i imagine a lot of people are gonna keep pressing it and thinking that it just fails...

and on the livecd's it's not like you can fix it afterwards...
Comment 10 AL13N 2013-05-06 10:21:21 CEST
to compare, the previous test from tmb, (with the dual networks detected) actually had working lights.
Comment 11 Sander Lepik 2013-05-06 19:33:48 CEST
(In reply to AL13N from comment #10)
> to compare, the previous test from tmb, (with the dual networks detected)
> actually had working lights.

I'm quite sure wl driver had something to do with it then. The light is not that important and we can't make it work if the driver doesn't support it yet. For sure it's not a release critical problem.
Comment 12 AL13N 2013-05-06 22:57:49 CEST
no, i doubt it, the wl driver in the previous setup was in the local repository and not on the iso by default.

this was bcma/brccmsmac on the image of 26-04 (with the dual entries)
Comment 13 Samuel Verschelde 2015-05-06 20:00:41 CEST
Is this bug still present in Mageia 5RC ISOs?

Keywords: (none) => NEEDINFO

Comment 14 Marja Van Waes 2016-08-28 10:17:24 CEST
(In reply to Samuel Verschelde from comment #13)
> Is this bug still present in Mageia 5RC ISOs?

Please reopen if it still is

Status: NEW => RESOLVED
CC: (none) => marja11
Resolution: (none) => OLD
Assignee: tmb => basesystem