Bug 16300 - broadcom-wl driver is missing in mga6
Summary: broadcom-wl driver is missing in mga6
Status: RESOLVED FIXED
Alias: None
Product: Mageia
Classification: Unclassified
Component: RPM Packages (show other bugs)
Version: Cauldron
Hardware: x86_64 Linux
Priority: Normal major
Target Milestone: ---
Assignee: José Jorge
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2015-07-05 20:37 CEST by Nikita Krupenko
Modified: 2015-07-07 13:32 CEST (History)
1 user (show)

See Also:
Source RPM: broadcom-wl
CVE:
Status comment:

Attachments
Output of the lspcidrake -v (4.89 KB, text/plain)
2015-07-06 10:33 CEST, Nikita Krupenko 		Details
Output of the rpm -qa --last (167.40 KB, text/plain)
2015-07-06 10:36 CEST, Nikita Krupenko 		Details
View All Add an attachment (proposed patch, testcase, etc.)

Description Nikita Krupenko 2015-07-05 20:37:18 CEST 
Description of problem:
I have laptop with Broadcom BCM43228 Wi-Fi chipset. After updating to mga6 my wireless network interface disappeared. I have dkms-broadcom-wl installed and also modules for some older kernels, but not for 4.1.


Version-Release number of selected component (if applicable):


How reproducible:


Steps to Reproduce:
1.
2.
3.


Reproducible: 

Steps to Reproduce:
Comment 1 Samuel Verschelde 2015-07-06 10:06:09 CEST 
How was the update made? 

Please attach the output of lspcidrake -v and rpm -qa --last.
Comment 2 Nikita Krupenko 2015-07-06 10:33:16 CEST 
Created attachment 6819 [details]
Output of the lspcidrake -v
Comment 3 Nikita Krupenko 2015-07-06 10:36:23 CEST 
Created attachment 6820 [details]
Output of the rpm -qa --last
Samuel Verschelde 2015-07-06 10:45:01 CEST

CC: (none) => tmb
Assignee: bugsquad => lists.jjorge
Source RPM: (none) => broadcom-wl

Comment 4 Thomas Backlund 2015-07-07 13:32:10 CEST 
Yeah, sorry I forgot to fix up the build for 4.0+ series kernels, it's now fixed with:

broadcom-wl-6.30.223.248-3.mga6
kmod-broadcom-wl-6.30.223.248-36.mga6

Status: NEW => RESOLVED
Resolution: (none) => FIXED
Note You need to log in before you can comment on or make changes to this bug.