Bug 17990 - Broadcom 4318 wifi not working on 4.4.X kernels
Summary: Broadcom 4318 wifi not working on 4.4.X kernels
Status: RESOLVED FIXED
Alias: None
Product: Mageia
Classification: Unclassified
Component: RPM Packages (show other bugs)
Version: Cauldron
Hardware: All Linux
Priority: Normal major
Target Milestone: ---
Assignee: José Jorge
QA Contact:
URL:
Whiteboard: MGA5TOO
Keywords: 6dev1, 6sta1
Depends on:
Blocks:
 
Reported: 2016-03-14 03:24 CET by Thomas Andrews
Modified: 2016-05-30 18:33 CEST (History)
1 user (show)

See Also:
Source RPM: b43-openfwwf
CVE:
Status comment:


Attachments
requested log (73.98 KB, text/x-log)
2016-03-14 18:27 CET, Thomas Andrews
Details
second log (74.88 KB, text/x-log)
2016-03-16 19:28 CET, Thomas Andrews
Details
additional firmware (6.48 KB, application/x-tar)
2016-03-18 15:12 CET, Thomas Andrews
Details

Description Thomas Andrews 2016-03-14 03:24:28 CET
Description of problem:
In the March 10 and March 11 Classical Mageia 6 isos, the Broadcom 4318-based desktop wifi card is not showing any activity on wlan0, as it has in past Mageia releases. 

When you attempt to set up a connection, then options for using the Air Force 1 controller or ndiswrapper are showing, but not the one for wlan0. The Air Force 1 option has never worked, and ndiswrapper is undesirable. 

In the past, the wlan0 option doesn't show if the b43-openfwwf package is not installed. This time, b43-openfwwf is installed, but still the wlan0 option isn't there.
Thomas Andrews 2016-03-14 03:24:44 CET

Whiteboard: (none) => 6dev1

Comment 1 Marja Van Waes 2016-03-14 09:14:48 CET
It should be something like wlp5s0 instead of wlan0, now

@ Zézinho

Assigning to you, as b43-openfwwf maintainer, because of 

> In the past, the wlan0 option doesn't show if the b43-openfwwf package is not
> installed.

please reassign if needed.

Keywords: (none) => 6dev1
CC: (none) => marja11
Assignee: bugsquad => lists.jjorge
Source RPM: (none) => b43-openfwwf
Whiteboard: 6dev1 => (none)

Comment 2 José Jorge 2016-03-14 12:17:28 CET
I don't have a Cauldron with 4318 to test, so please give your dmesg and ifconfig at least.

Status: NEW => ASSIGNED

Comment 3 Thomas Andrews 2016-03-14 13:02:19 CET
(In reply to José Jorge from comment #2)
> I don't have a Cauldron with 4318 to test, so please give your dmesg and
> ifconfig at least.

I'm afraid my skills in these procedures have a bad habit of atrophying when not used, and I haven't used them in several months. I keep forgetting how to get this stuff, so if you would give me more specific instructions I will be happy to comply. 

I can only provide information from the 32-bit installation at present, but as the symptoms are the same I believe the source is the same in 64-bit, too.
Comment 4 José Jorge 2016-03-14 17:26:52 CET
attach to this bug the file resulting from this commands :

/sbin/ifconfig > file.log
dmesg >> file.log
Comment 5 Thomas Andrews 2016-03-14 18:27:41 CET
Created attachment 7571 [details]
requested log

There you go, Jose. If I can be of more service, just ask.
Comment 6 José Jorge 2016-03-16 12:01:55 CET
Looks like new kernels have changed the path where they search the firmware :

 b43-phy0 ERROR: Firmware file "b43-open/ucode5.fw" request failed (err=-11)

So I changed this in b43-openfwwf. Please update to b43-openfwwf-5.2-8.mga6 that is currently building and report if it works.
Comment 7 Thomas Andrews 2016-03-16 14:05:44 CET
Will do, but first I have to set up a wired connection, load a mirror, get updates, etc. Depending on how up to date my mirror of choice is, that may take a while.

Sounds to my uninformed brain like this could affect almost all firmwares. Something to check into, perhaps?
Comment 8 Thomas Andrews 2016-03-16 19:28:02 CET
Created attachment 7576 [details]
second log

No apparent change. I was able to establish an ethernet connection, then proceeded to get updates. Booted again, then tried to establish a new wireless connection via MCC. No change from before. 

I then disconnected the ethernet connection and tried again. Same result. I then tried a complete shutdown and boot, this time with the ethernet cable disconnected from my router. Same result.

Attaching another log, so you can see if there have been any changes.

On a possibly related note, the ethernet connection did not come up automatically as it should. MCC showed the connection as working, but I could not use the Internet. Disconnected and reconnected in MCC, same result. It wasn't until after I disconnected and then configured and started a new connection through MCC that it started to work. On the reboot following getting the updates, the ethernet connection was still functioning correctly.
Comment 9 Thomas Andrews 2016-03-16 19:30:49 CET
The log is suggesting that I need to download the needed firmware from elsewhere, the way I used to have to do. Is that supposed to be necessary?
Comment 10 Thomas Andrews 2016-03-16 20:08:46 CET
(In reply to Thomas Andrews from comment #8)
> 
> On a possibly related note, the ethernet connection did not come up
> automatically as it should. MCC showed the connection as working, but I
> could not use the Internet. Disconnected and reconnected in MCC, same
> result. It wasn't until after I disconnected and then configured and started
> a new connection through MCC that it started to work. On the reboot
> following getting the updates, the ethernet connection was still functioning
> correctly.

The above appears to be covered in Bug # 17683.
Comment 11 José Jorge 2016-03-16 22:18:15 CET
(In reply to Thomas Andrews from comment #9)
> The log is suggesting that I need to download the needed firmware from
> elsewhere, the way I used to have to do. Is that supposed to be necessary?

No. This is the purpose of this package. But it seems you did your update BEFORE the new version hitted the mirrors.

Can you confirm you have b43-openfwwf-5.2-8.mga6 version installed?
Comment 12 Thomas Andrews 2016-03-16 23:04:56 CET
Yes, that is indeed the version that's installed. I remember seeing it on the list of 400+ updates, but I didn't remember the specific version.
Comment 13 José Jorge 2016-03-17 23:24:24 CET
Well it seems it requires one file that is not in this package : pcm5.fw

ERROR: Firmware file "b43/ucode5.fw" request failed (err=-11)
ERROR: Firmware file "b43-open/pcm5.fw" request failed (err=-11)

Please give ls /lib/firmware/b43*
Comment 14 Thomas Andrews 2016-03-18 02:59:04 CET
The contents of b43-open:

b0g0bsinitvals5.fw  
b0g0initvals5.fw  
ucode5.fw

There is no b43 folder. This is from BEFORE getting the latest round of updates, which includes kernel 4.4.6. Proceeding with that extensive upgrade over a wired connection now, but I don't expect any changes.

My test of the kernel upgrade to 4.4.6 in Mageia 5, same hardware, produces the same symptoms. Wifi was working before the upgrade, as that was what I used to download it. In that system, there is no b43-open directory, but there is a b43, containing the same files as above. Probably the same problem, eh?
Comment 15 claire robinson 2016-03-18 09:27:51 CET
An update will also be required for mga5 as new mga5 kernels are also affected by this. Setting blocks bug 18031

Blocks: (none) => 18031
Whiteboard: (none) => MGA5TOO

claire robinson 2016-03-18 10:28:12 CET

Blocks: 18031 => (none)
Depends on: (none) => 18031

Comment 16 Thomas Andrews 2016-03-18 15:08:48 CET
I do believe I have it. I got wifi to work again with M5, anyway. 

Looking around, I found the file openfwwf-jam-5,3.tar.bz on http://netweb.ing.unibs.it/~openfwwf/. I downloaded it, extracted it, and found the following files:

b0g0bsinitvals5.fw  
b0g0initvals5.fw  
pcm5.fw  
ucode5.fw

As root, I created /lib/firmware/b43-open, and copied the above files into it.

Upon rebooting, I had my wifi back, apparently working perfectly.
Comment 17 Thomas Andrews 2016-03-18 15:12:39 CET
Created attachment 7584 [details]
additional firmware

I'm having difficulty getting back to the site of the actual download, so I'm uploading it here.
Comment 18 Thomas Andrews 2016-03-18 15:59:27 CET
(In reply to Thomas Andrews from comment #16)
> I do believe I have it. I got wifi to work again with M5, anyway. 
> 
> Looking around, I found the file openfwwf-jam-5,3.tar.bz on
> http://netweb.ing.unibs.it/~openfwwf/. I downloaded it, extracted it, and
> found the following files:
> 
> b0g0bsinitvals5.fw  
> b0g0initvals5.fw  
> pcm5.fw  
> ucode5.fw
> 
> As root, I created /lib/firmware/b43-open, and copied the above files into
> it.
> 
> Upon rebooting, I had my wifi back, apparently working perfectly.

Forgot to mention, though it should have been obvious, that I left M5's /lib/firmware/b43 folder alone.
Comment 19 Thomas Andrews 2016-03-18 17:56:01 CET
Further experimentation reveals that the attached firmware works just as well, if not better, if it is placed in /lib/firmware/b43/ without there being any b43-open folder at all. This is true of both M6 and M5.

So, it looks to me like all we have to do is update the older(?) b43-openfwwf to the attached 5.3 version, and we'll have it.
Comment 20 José Jorge 2016-03-18 18:48:13 CET
(In reply to Thomas Andrews from comment #19)
> Further experimentation reveals that the attached firmware works just as
> well, if not better, if it is placed in /lib/firmware/b43/ without there
> being any b43-open folder at all. This is true of both M6 and M5.
> 
> So, it looks to me like all we have to do is update the older(?)
> b43-openfwwf to the attached 5.3 version, and we'll have it.

Yes, but there is no source code upstream for the 5.3 version. I have mailed them asking for it.

this version seems to provide a new file : pcm5.fw which is missing in recent kernels...
Comment 21 Thomas Andrews 2016-05-04 20:56:16 CEST
Still valid in the initial round of Live sta1 Plasma isos. Most likely it's the same with the classicals as well, but I have not tried one of them yet.

Adding 6sta1 to the keyword list.

Keywords: (none) => 6sta1
Summary: Broadcom 4318 wifi not working => Broadcom 4318 wifi not working on Mageia 6 Cauldron

Thomas Backlund 2016-05-24 13:47:03 CEST

Depends on: 18031 => (none)

Comment 22 Thomas Andrews 2016-05-24 15:28:26 CEST
Still valid with the May 23 round of sta1 Plasma Live isos.
Comment 23 Thomas Andrews 2016-05-26 23:20:16 CEST
Also valid with the upcoming Mga5 4.4.11 kernel upgrade. Bug #18031.

Unless a copy of pcm5.fw is placed in /lib/firmware/b43 along with the files provided in b43-openfwwf, wifi will not work with any of the 4.4.x kernels I've tried so far.
Thomas Andrews 2016-05-26 23:21:07 CEST

Summary: Broadcom 4318 wifi not working on Mageia 6 Cauldron => Broadcom 4318 wifi not working on 4.4.X kernels

Comment 24 José Jorge 2016-05-29 10:24:00 CEST
I have submitted a workaround the silence of upstream : the pcm5.fw is now provided from the upstream binary 5.3 tarball.

This was also submitted to MGA5 updates.

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

Comment 25 Thomas Andrews 2016-05-30 00:54:21 CEST
Reopening because sorry to say we are not quite there yet. 

The new b43-openfwwf works- eventually - with the 4.4.11 MGA5 kernel update. But when booting my Dell Dimension E310, there is approximately an 80 second delay between the time the network icon appears in the panel and the wireless connection is established. Once the connection is eventually established, everything works fine.

If, however, I rename b43-open in /lib/firmware to b43, there is no discernible delay at all. The connection comes up immediately, and works as well as it always has. 

I have absolutely no idea why this would be, but that's the way it is, anyway.

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

Comment 26 José Jorge 2016-05-30 12:07:34 CEST
(In reply to Thomas Andrews from comment #25)
> 
> I have absolutely no idea why this would be, but that's the way it is,
> anyway.

The Open Source firmware provides different capabilities, as no hardware crypto. So the kernel source code seems to wait for some time before using it.
I'm not sure the workaround is a solution, as this is a new behaviour in kernel 4.4.x. I think you should report the bug upstream to kernel.org .

I'd prefer not changing the path, as it will conflict files if the user installs proprietary firmware.
Comment 27 José Jorge 2016-05-30 13:36:41 CEST
I forgot to mention the conflicting package :

b43-firmware-install

It installs proprietary firmware in /lib/firmware/b43 . So I am closing this bug, as this package provides what it is meant to : an open-source firmware.

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

Comment 28 Thomas Andrews 2016-05-30 18:33:29 CEST
(In reply to José Jorge from comment #27)
> I forgot to mention the conflicting package :
> 
> b43-firmware-install
> 
> It installs proprietary firmware in /lib/firmware/b43 . So I am closing this
> bug, as this package provides what it is meant to : an open-source firmware.

Should be interesting to see how it works with the Mageia 6 Live media, if at all.

But the bug has been closed twice now, so that's that.

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