Bug 24958

Summary:	error in path to ucode5.fw when setting up a new wireless interface via drakconnect in mcc
Product:	Mageia	Reporter:	Mike Rambo <mhrambo3501>
Component:	RPM Packages	Assignee:	Kernel and Drivers maintainers <kernel>
Status:	RESOLVED FIXED	QA Contact:
Severity:	normal
Priority:	Normal	CC:	lists.jjorge, mageiatools, marja11
Version:	7
Target Milestone:	---
Hardware:	All
OS:	Linux
Whiteboard:
Source RPM:	b43-openfwwf	CVE:
Status comment:
Attachments:	screenshot of the error

Description Mike Rambo 2019-06-15 18:44:49 CEST

Description of problem:
When setting up a new wireless interface in mcc the path to ucode5.fw is not found.

Steps to Reproduce:
1. open mcc
2. choose network + internet
3. choose Set up a new network interface
4. choose wireless
5. choose wlan0 (this laptop is an older dell d531 with bcm4311 wireless)

The result of the above is an error "The following component is missing: /lib/firmware/b43/ucode5.fw" (see attached png). The actual path to ucode5.fw is /lib/firmware/b43-open/ucode5.fw. My workaround was to symlink b43-open to b43 which allowed finding the firmware. I don't know if the problem is actually in b43-openfwwf or in mcc's drakconnect but we have to start somewhere.

Comment 1 Mike Rambo 2019-06-15 18:45:50 CEST

Created attachment 11095 [details]
screenshot of the error

Marja Van Waes 2019-06-16 13:15:32 CEST

Assignee: bugsquad => kernel
CC: (none) => lists.jjorge, mageiatools, marja11

Comment 2 José Jorge 2019-06-16 21:11:17 CEST

(In reply to Mike Rambo from comment #0)
> I don't know if the problem is actually in b43-openfwwf or in mcc's drakconnect but we have to start somewhere.

It is in b43-openfwwf. The kernel used to search in both paths, but I see this has also changed in MGA6 latest kernel...

I have submitted  b43-openfwwf-5.2-13.mga7 to updates_testing. Please test to ensure it fixes the problem for everyone.

Status: NEW => ASSIGNED

Comment 3 Mike Rambo 2019-06-17 18:46:43 CEST

This does fix the problem. Thanks.

Comment 4 Mike Rambo 2019-09-06 13:31:32 CEST

I've had no futher problem. Should have marked it fixed back in June.

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