Bug 6875 - Broadcom wifi 43225 break after upgrade to mga2
Summary: Broadcom wifi 43225 break after upgrade to mga2
Status: RESOLVED OLD
Alias: None
Product: Mageia
Classification: Unclassified
Component: RPM Packages (show other bugs)
Version: 2
Hardware: i586 Linux
Priority: Normal normal
Target Milestone: ---
Assignee: Mageia Bug Squad
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2012-07-27 08:28 CEST by Arnaud Vacquier
Modified: 2012-10-10 04:11 CEST (History)
0 users

See Also:
Source RPM:
CVE:
Status comment:

Attachments
error : impossible to find the network interface for selected device (using driver wl) (61.10 KB, image/png)
2012-07-27 08:28 CEST, Arnaud Vacquier 		Details
RPMs installed after the hardware detection (29.33 KB, image/png)
2012-07-27 08:30 CEST, Arnaud Vacquier 		Details
View All Add an attachment (proposed patch, testcase, etc.)

Description Arnaud Vacquier 2012-07-27 08:28:50 CEST 
Created attachment 2583 [details]
error : impossible to find the network interface for selected device (using driver wl)

Description of problem:
On Mageia 1 KDE 32 wifi run perfect after install RPM "dkms-broadcom-wl" only
After upgrade Mga1 -> Mga2 the wifi is broken

by :

su
mgaapplet-upgrade-helper --new_distro_version=2

Version-Release number of selected component (if applicable):
Mageia 2 KDE 32bits updated


So, I activated Core / Nonfree / backport (not tainted, not debug,not testing)
And i open hardware detection, he ask me to install :

broadcom kernel desktop (not here before without nonfree)
i allow but it still does not work

thank you
Comment 1 Arnaud Vacquier 2012-07-27 08:30:05 CEST 
Created attachment 2584 [details]
RPMs installed after the hardware detection
Comment 2 Manuel Hiebel 2012-08-19 15:53:34 CEST 
Does ifconfig show you the interface ?
is iwconfig scan working ?
can you _attach_ the output of lsmod and lspcidrake -v ?

Component: Installer => RPM Packages

Arnaud Vacquier 2012-10-10 04:11:18 CEST

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