Bug 10196 - Broadcom wireless works in Live CD mode, but not after install from live cd or full dvd
Summary: Broadcom wireless works in Live CD mode, but not after install from live cd o...
Status: RESOLVED FIXED
Alias: None
Product: Mageia
Classification: Unclassified
Component: Installer (show other bugs)
Version: 3
Hardware: All Linux
Priority: Normal major
Target Milestone: ---
Assignee: QA Team
QA Contact:
URL:
Whiteboard: mga3-64-ok
Keywords: validated_update
: 11883 (view as bug list)
Depends on:
Blocks:
 
Reported: 2013-05-21 13:09 CEST by Bill Wilkinson
Modified: 2013-12-18 00:51 CET (History)
6 users (show)

See Also:
Source RPM: meta-task
CVE:
Status comment:


Attachments

Description Bill Wilkinson 2013-05-21 13:09:24 CEST
Mga3

Installed MGA3 from 64-bit dvd. Attempts to configure wireless network with broadcom 4311 leads to no available devices.  Wireless works well under live mode in live CD.

Running MCC shows only :use a Windows driver (with ndiswrapper), as opposed to any other options or even wlan0: use a Windows driver (with ndiswrapper) as expected.

Reproducible: 

Steps to Reproduce:
Comment 1 Sander Lepik 2013-05-21 13:28:42 CEST
Open MCC -> Hardware -> Browse and configure hardware. Does it want to install any extra packages that might help with your device?

If possible, make sure that you have Nonfree repo enabled and connect your computer with cable.

Keywords: (none) => NEEDINFO
CC: (none) => sander.lepik

Comment 2 Bill Wilkinson 2013-05-21 14:40:32 CEST
Sander,

I tried that earlier, nothing added, even when checking the network card.

From the LiveCD, when we get to remove unused hardware, the list includes b43-openfwwf and b43-fwcutter.  Not removing unused hardware during setup with the liveCD does bring up the network. I'm currently installing from the full DVD.

I'll fill in the results here.

CC: (none) => wrw105

Comment 3 Bill Wilkinson 2013-05-21 15:39:00 CEST
Installing b43-openfwwf and b43-fwcutter did it.  Installed them, rebooted, configured the access point, rebooted and I'm live.  Thanks for the help, Sander.
Comment 4 Bill Wilkinson 2013-05-21 15:41:32 CEST
Installing b43-openfwwf and b43-fwcutter allow wifi to connect on wlan0.  Maybe need to check setup scripts on the full DVD, but it's working for me once the software is installed.

Status: NEW => RESOLVED
Resolution: (none) => WORKSFORME

Comment 5 Sander Lepik 2013-05-21 17:51:13 CEST
Pleas run this command: lspcidrake -v

And from the output copy the line about your broadcom device. I think we need to educate our tools about your device.

Status: RESOLVED => REOPENED
CC: (none) => thierry.vignaud, tmb
Version: 3 => Cauldron
Resolution: WORKSFORME => (none)
Whiteboard: (none) => MGA3TOO

Comment 6 Bill Wilkinson 2013-05-21 18:40:27 CEST
ssb             : Broadcom Corporation|BCM4311 802.11a/b/g [NETWORK_OTHER] (vendor:14e4 device:4312 subv:103c subd:1360) (rev: 01)
Comment 7 Thierry Vignaud 2013-05-21 18:49:27 CEST
Have you run harddrake ("hardware" in the control center) and let it install any needed package?
Comment 8 Sander Lepik 2013-05-21 19:16:14 CEST
By comment #2 he did.
Comment 9 Thomas Backlund 2013-05-21 19:24:38 CEST
we need to fix meta-task / rpmsrate-raw

It states:
rpmsrate-raw:  5 DRIVER"b43"  || DRIVER"b43legacy" b43-fwcutter
rpmsrate-raw:  5 DRIVER"b43"  b43-openfwwf

Wich does not trigger as ldetect only sees ssb
Thierry Vignaud 2013-05-21 22:10:37 CEST

Source RPM: (none) => meta-task

Comment 10 Thomas Backlund 2013-12-05 21:09:03 CET
The b43 driver can use b43-openfwwf firmware for some hardware, but it was
not installed as they identify themselves as using ssb driver.

This update resolves this issue

SRPM:
meta-task-3-43.mga3.src.rpm

i586/x86_64:
meta-task-3-43.mga3.noarch.rpm

Keywords: NEEDINFO => (none)
Hardware: x86_64 => All
Version: Cauldron => 3
Assignee: bugsquad => qa-bugs
Whiteboard: MGA3TOO => (none)

Comment 11 Thomas Backlund 2013-12-05 21:09:43 CET
*** Bug 11883 has been marked as a duplicate of this bug. ***

CC: (none) => davidwhodgins

Comment 12 Dave Hodgins 2013-12-05 22:09:20 CET
Bill, Have you installed the meta-task package from core updates testing,
and if so, did it fix the issue for you?
Comment 13 Bill Wilkinson 2013-12-05 22:42:58 CET
Dave,

Haven't had a chance to look at it yet.  Probably later tonight or tomorrow AM (US EST).  By then it will have propagated to my mirror.  I'll post when done.
Comment 14 Bill Wilkinson 2013-12-06 05:52:42 CET
Thomas:

Has this been rebuilt recently?  All I'm seeing in core/updates_testing on mirrors.kernel.org is a package from May 21.

Thanks!

Whiteboard: (none) => feedback

Comment 15 Thomas Backlund 2013-12-06 10:52:47 CET
Thats the correct package, I pushed the suggested fix on the same day this was reported, but then forgot to update this BR

Whiteboard: feedback => (none)

Comment 16 Bill Wilkinson 2013-12-06 14:21:05 CET
Tested under mga3-64.

Installs properly, but wlan0 still defaults to ssb driver. 

Following the package installation, I removed the wlan0 and reconfigured the interface, 
From lspcidrake -v:
ssb             : Broadcom Corporation|BCM4311 802.11a/b/g [NETWORK_OTHER] (vendor:14e4 device:4312 subv:103c subd:1360) (rev: 01)


The two options in the network config in mcc were wlan0:wlan0 and ndiswrapper:*different device name*
Comment 17 Thomas Backlund 2013-12-06 14:35:51 CET
Yeah, thats expected. as the advisory states, the driver shows identifies as "ssb", but atleast if you browse the hw, it should suggest to install b43-openfwwf unless it's already installed.
Comment 18 Bill Wilkinson 2013-12-06 14:57:19 CET
openfwwf was installed on the system--it may have been there when the original update got put into testing.

So it appears to be working properly.  I'll set it as mga3-64-OK and we should just be waiting on the advisory to push to updates.

Whiteboard: (none) => mga3-64-ok

Comment 19 Thomas Backlund 2013-12-06 15:01:24 CET
Advisory is in comment 10 (but I forgot the "advisory" word)

Advisory:
The b43 driver can use b43-openfwwf firmware for some hardware, but it was
not installed as they identify themselves as using ssb driver.

This update resolves this issue
Comment 20 Bill Wilkinson 2013-12-11 03:29:01 CET
Thanks, Thomas!

We just need Claire or Dave to upload the advisory to svn.  As this is a noarch package, it's ready to go as-is.
Comment 21 claire robinson 2013-12-11 12:21:47 CET
Advisory uploaded. Validating.

Could sysadmin please push from 3 core/updates_testing to updates.

Thanks!

Keywords: (none) => validated_update
CC: (none) => sysadmin-bugs

Comment 22 Thomas Backlund 2013-12-18 00:51:35 CET
Update pushed:
http://advisories.mageia.org/MGAA-2013-0130.html

Status: REOPENED => RESOLVED
Resolution: (none) => FIXED


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