I can confirm this bug on Mageia 3 alpha2 LiveDVD. Not quite sure about the hardware tho'.. Maybe it was the same, maybe not, but the message was the same.

CC: (none) => sander.lepik
Hardware: i586 => All

you don't have a third part wlan0 ? (or eth1/2)

(bcm4313 for me)

Whiteboard: (none) => 3alpha2

what do you mean by "third part wlan0?

Network Center shows the right devices: one for LAN and one for WLAN (Broadcom BCM4312).

lspcidrake:
wl  : Broadcom Corporation|BCM4312 802.11b/g LP-PHY [NETWORK_OTHER] (rev: 01)

Created attachment 3005 [details]
Window Network Center

This bug is still valid in 3alpha3.

Error message in dmesg:

[   14.208268] b43-phy0: Broadcom 4312 WLAN found (core revision 15)
[   14.223079] b43-phy0 debug: Found PHY: Analog 6, Type 5, Revision 1
[   14.223097] b43-phy0 debug: Found Radio: Manuf 0x17F, Version 0x2062, Revision 2
[   14.230356] Broadcom 43xx driver loaded [ Features: PMNLS ]
[   14.246201] b43-phy0 ERROR: Firmware file "b43/ucode15.fw" not found
[   14.246205] b43-phy0 ERROR: Firmware file "b43-open/ucode15.fw" not found
[   14.246208] b43-phy0 ERROR: You must go to http://wireless.kernel.org/en/users/Drivers/b43#devicefirmware and download the correct firmware for this driver version. Please carefully read all instructions on this website.
[   14.246662] cfg80211: World regulatory domain updated:
[   14.246666] cfg80211:   (start_freq - end_freq @ bandwidth), (max_antenna_gain, max_eirp)
[   14.246669] cfg80211:   (2402000 KHz - 2472000 KHz @ 40000 KHz), (300 mBi, 2000 mBm)
[   14.246671] cfg80211:   (2457000 KHz - 2482000 KHz @ 20000 KHz), (300 mBi, 2000 mBm)
[   14.246673] cfg80211:   (2474000 KHz - 2494000 KHz @ 20000 KHz), (300 mBi, 2000 mBm)
[   14.246675] cfg80211:   (5170000 KHz - 5250000 KHz @ 40000 KHz), (300 mBi, 2000 mBm)
[   14.246677] cfg80211:   (5735000 KHz - 5835000 KHz @ 40000 KHz), (300 mBi, 2000 mBm)
 



After i did:

# rmmod ssb
# rmmod b43
# rmmod wl
# modprobe wl

not loading the b43 module anymore the device showed the access points in the network manager, but when i tried to connect to the internet i got a "Could not connect ..."
I noticed that the network-icon in the task bar did not change while it was trying to connect to the internet like it usually does.

Also i can not turn on or off the wlan device on the laptop, there is no reaction when i press the wlan button.

So, i think the modules b43 and ssb should not be loaded at booting time like it is now in Mageia2, but i don't understand why it does not connect to the internet.

thanks and best regards
egc

*** Bug 7809 has been marked as a duplicate of this bug. ***

CC: (none) => inster.css

This bug has something to do with bug #6122.

My device id is 14e4:4353 and i think it should also use bcma instead of wl. If i removed ssb, b43 and wl + reloeaded bcma then i saw APs. I couldn't connect tho'. net_applet is screwing my wpa_supplicant.conf for some reason. Doesn't see my network as WPA protected and is trying to configure it as WEP protected. So i can't install NM either to try with this one. Anyway, there is some nice conflict with modules that we didn't have in mga2.

CC: (none) => thierry.vignaud, tmb
Whiteboard: 3alpha2 => 3alpha3

Created attachment 3219 [details]
mga3b1_wifi_fail.txt

Output from "journalctl -f" showing messages when wi-fi connection attempted
in Mageia 3 beta 1 (Mageia-3-beta1-LiveDVD-GNOME-x86_64-DVD) on an HP ProBook 6555b: with Broadcom wi-fi:
07:00.0 Network controller: Broadcom Corporation BCM43224 802.11a/b/g/n (rev 01)

re: comment-8 (above):
step 1: 
urpmi.addmedia nonfree rsync://distrib-coffee.ipsl.jussieu.fr/mageia/distrib/cauldron/x86_64/media/nonfree/release/

step 2:
urpmi dkms dlms-broadcom-wl

step 3:
reboot

step 4:
Configure wifi with drakroam. SSID of wireleaa access point is found but connection fails. Attachment mga3b1_wifi_fail.txt shows the messages from "journalctl -f" when the connection is attempted.

CC: (none) => paul.blackburn

paul you issue seems not the same

or it is, lets see you can reproduce after new iso

(a probably fix for this issue too https://bugs.mageia.org/show_bug.cgi?id=8343)

@Manuel, OK I will test again for new iso

This bug is still valid in 3beta1

So i did some more testing with beta1 LiveDVD.

* First i had to rmmod these modules: b43, brcmsmac, bcma and wl.
* Then i added b43 and wl into blacklist.
* modprobe bcma.
* After that i configured my network and ran "service network restart" to make wpa_supplicant reload itself too.

After these steps my network was running OK.

So this hardware is working fine with bcma module and other modules should be blacklisted:

wl : Broadcom Corporation|BCM43224 802.11a/b/g/n [NETWORK_OTHER] (vendor:14e4 device:4353 subv:1028 subd:000e) (rev: 01)

Testing results with Mageia 3 beta2 KDE LiveDVD x86_64:

* Wifi can't be configured with draknetcenter (same old message: Unabel to find network interface for selected device (using wl driver).).

* lspcidrake still thinks wl is the right module for my device.

* wl module is not loaded.

* Loaded modules: brcmsmac, brcmutil, b43, bcma.

How to get it working:
1. Add b43 into blacklist.
2. rmmod b43, brcmsmac and bcma.
3. modprobe bcma.
4. Restart draknetcenter and configure new interface (wlan0).

Remaining problems:
* b43 is not blacklisted and stops bcma from working.
* Draknetcenter is showing device that is connected to wl module - shouldn't be there at all.
* lspcidrake shows wl as suggested module (probably connected with the previous problem).

This bug is still valid in 3 beta2 for
02:00.0 Network controller: Broadcom Corporation BCM4312 802.11b/g LP-PHY (rev 01)

I still get the message:
"Unabel to find network interface for selected device (using wl driver)." and
there are no accesspoints listed.

And dmesg says:

[   12.447776] b43-phy0: Broadcom 4312 WLAN found (core revision 15)
[   12.462087] b43-phy0: Found PHY: Analog 6, Type 5 (LP), Revision 1
[   12.462104] b43-phy0 debug: Found Radio: Manuf 0x17F, Version 0x2062, Revision 2
[   12.469429] Broadcom 43xx driver loaded [ Features: PMNLS ]
[   12.556705] b43-phy0 ERROR: Firmware file "b43/ucode15.fw" not found
[   12.556709] b43-phy0 ERROR: Firmware file "b43-open/ucode15.fw" not found
[   12.556712] b43-phy0 ERROR: You must go to http://wireless.kernel.org/en/users/Drivers/b43#devicefirmware and download the correct firmware for this driver version. Please carefully read all instructions on this website.

I have a similar problem with a Broadcom 43228 interface.

With kernel-desktop-3.8.0-0.rc5.1.mga3-1-1.mga3 when I try to configure a wlan interface with drakconnect, I only an only suggested the windows driver, no additional wlan software (as with past releases).

I then manually requested broadcom-wl-kernel-desktop-latest-5.100.82.112-58.mga3.nonfree to be installed (which also brought in dkms-minimal), with a slightly confusing result: I get a radiobutton with three alternative choices for the wireless interface
- Broadcom Corporation BCM43228 802.11 1/b/g/n (comes up as selected)
- eth1: eth1
- use a Windows driver ( with ndiswrapper)

When I hit "next" with the initially selected (Broadcom) interface, I get "Unable to find network interface for selected device (using wl driver).

Selecting eth1 gets me farther: the interface sees my wlan and asks me to select it, but after further configuration, the connection fails.

Under Mageia 2 I had been able to use my wlan interface with network manager - did not try network manager so far, have run out of time (or rather: of patience of my wife) and give top priority to sort out all the kde 4.9.97 regressions.

But I wanted to file that the BCM43228

CC: (none) => juergen.harms

Sorry, the post run away while I did some checking. The last sentence is:

But I wanted to file that the BCM43228 belongs to the set of problematice devices, and that I am ready to help clarifying - once constructive testing makes sense.

Broadcom Corporation BCM4313 802.11b/g/n Wireless LAN Controller (rev 01)

Can't use the network applet nor the Mageia Control Center to connect to my hidden SSID.
However i can get it to work through command line (iwconfig)...
My wireless device is now eth0 and my wired is eth1 ??

Don't know why in dmesg i've got:
eth0: Broadcom BCM4727 802.11 Hybrid Wireless Controller 5.100.82.112

CC: (none) => tipaul2003

I also got 3 options when configuring a wireless network through Control Center:
- Broadcom bcm4313
- eth0 : eth0
- Use Windows driver (ndiswrapper)

eventually, only selecting eth0 don't report anything.
Selecting Broadcom will show "hardware not found"
And i dont want to install the ndiswrapper stuff...

Question:
Why using the broadcom-wl proprietary driver in Mageia when there is open source brcmsmac/brcmfmac driver available ? :

brcmsmac/brcmfmac 
Open source kernel driver 

b43 
Reversed engineered kernel driver 

broadcom-wl 
Proprietary Broadcom STA driver

On most other distro i've used, they tend to use the open source one by default and it works just fine for my hardware...

Even Arch Linux have this warning about the WL driver :

broadcom-wl 
-----------
Warning: Even though this driver has matured a lot throughout the years and works quite good nowadays, it's usage is recommended only when none of the two opensource drivers support your device. Please refer to project b43's page for list of supported devices.

Yes, we are trying to achieve this, but it will take some time and we need testers.

I'm willing to test/help you out.
I'm not a programmer (have some basic knowledge in 'C' and java) but can manage bash scripts.
Started using Linux as my main OS more than 15 years ago. :D

New findings:
Deactivated my hidden essid on my router and now Mageia can connect automatically at startup without any intervention...

Seems like the WL driver don't like hidden ssid...

An update on the situation for my specific configuration ( BCM43228, 65-bit Dell Latitude E6530)

I tried to go the "official way": fresh install of Beta, full update (Kernel 3.8.1-desktop), Broadcom wl-kernel-desktop-latest-5.100.82.112-62.mga3.nonfree plus dependencies).

Result: the interface "sees" the network and its ssid, but then fails to connect.

Worse: follwing this experiment, my wired interface does not work any more - the connection comes up with a message that the connection is up, but that the internet connection test fails (and a ping my local router is rejected with a message that there is no path to its address). This situation is solid, even after a reboot I do not get any network access.

Looking at my ifcfg-eth1, and comparing it to the one of my Mageia2 system, I see that there is no netmask entry, and the the metric is set to 5 instead of 10 - but correcting these values does not help.

Any advice how to get at least my wired connection back without a re-install?

Are you using NM or Mageia tools?

Using the Mageia tools - I precisely had wanted to test and compare these 2 alternatives - see where cauldron stands - when I got stuck without any network access.

But in the meantime I had success. Did an upgrade install, and that gave me back at least my wired connection (I did not say in comment 27 that I had, evidently tried to reconfigure the wired access from scratch).

I just now installed networkmanager and knetworkmanger, and the wireless connection came up like a charm.

Conclusion: Wireless does presently not work with the Mageia tools, but NM is OK as a workaround (should it be promoted from workaround to officially suggested solution?)

I really think that the sensible thing to do at this point is to disable b43/wl for the specific chipsets with which people are having problems.  

I understand the reluctance to flip completely to bcrmsmac for devices where b43 or wl is already working.

It's pretty clear that the "multiple device" listings shown by drakconnect are the result of multiple drivers trying to control the same device and colliding with each other.

Since NM seems to work with the problematic devices, it would make sense to compare the NM driver selection mechanism with drakconnect's, and change drakconnect for those devices accordingly.

Is there a single point of driver selection in the drakx tools these days, or does harddrake try to roll its own when it detects a "new" device ?

CC: (none) => ftg

I agree that a certain dose of pragmatism is indicated. The time is running out that is available to make sure that users of laptops with (only - possibly) wireless interfaces can use Mageia3 and get their interface to work out of the box - being aware that a good fraction of this remaining time will be needed to assess and test in multiple environments whatever will be perceived as "the Mageia wireless interface".

Test results with beta3 - getting worse :/

- Broadcom drivers are missing from LiveDVD. There is no chance that normal user is able to create connection.
- b43 and brcmsmac (bcma) are still loaded by default, so even if Broadcom drivers would be on DVD it wouldn't work.
- For some strange reason shorewall is blocking wlan0 completely (when I configure brcmsmac like in comments above..).

So no progress in beta3 :(

Created attachment 3600 [details]
Error message about missing wl driver

This is the error message in beta3.
I can not install the driver because i have no internet connection :-(

I guess you did this on a liveCD. I just checked on the DVD iso of Beta2: that DVD contains the broadcom packages - so you might have a chance once the Beta3 DVDs are out.

But I agree: live CDs are for people who want to check whether Mageia does what they want - it would be foolish of Mageia to automatically trigger a negative reaction from users who depend on having the broadcom interface working before they can download anything.

In case you want to try a work-around which consists in downloading the packages needed for broadcom before installing Mageia 3 (say under Mageia 2) and installing them from what you had downloaded, I suggest you ask (for instance here) for a list that includes all the dependencies to avoid getting stuck with a couple of missing packages - and say whether you need i586 or x86-64.

I can try that. For this I would need the dependencies for i586. Thanks!

(In reply to Sander Lepik from comment #31)
> - b43 and brcmsmac (bcma) are still loaded by default, so even if Broadcom
> drivers would be on DVD it wouldn't work.

Also in my case b43 and bcma are loaded by default, but i actually need the wl driver for my device:
02:00.0 Network controller: Broadcom Corporation BCM4312 802.11b/g LP-PHY (rev 01)

Installing wl driver should block the unwanted ones.

Actually the live medias are somewhat selfcontained, it's just not automated yet since I got sick during iso builds and am not fully recovered yet...

Anyway, all live medias currently carry the matching prebuilt broadcom-wl drivers in /root/broadcom/ so you hve access to them even without network Connection.

Created attachment 3602 [details]
Error message with wl driver

Thank you, Thomas!

I've tried now with wl driver (in liveCD modus), I installed the broadcom-wl packages, then did a 
rmmod b43
rmmod bcma
modprobe wl
but i still can not turn on the wlan device on the laptop (the LED is red, it should be blue) and opening the Networkcenter it shows me the same error as in beta2 and earlier (see attachment).

the wl driver doesn't connect a Dell Inspiron E1405, but the b43 does.
So we should not let the system try to install the wl

CC: (none) => thomas

To add to my posting:
I cannot use the Live CD (or DVD) on this Dell box (and probably not on other Dell's with wide screen)  so I did a network install:
using the wl driver, the box cannot find the interface and the WiFi light doesn't come on. Using the b43 driver it can find the interface the Wi-Fi light does turn on but the box doesn't connect.

(In reply to Paul Ladouceur from comment #21)
> Question:
> Why using the broadcom-wl proprietary driver in Mageia when there is open
> source brcmsmac/brcmfmac driver available ? :

In my case because with the brcmsmac driver I obtain less that 10% the performance of wl (mageia 2, I'll try again with mageia 3).

CC: (none) => luca

beta4 LiveDVD (KDE x86_64) still doesn't work. When I click on the device in net_applet it will install wl driver but after that it still keeps telling me that it can't use the device.

b43, bcma, brcmsmac were all loaded. After I removed them all and also wl, I loaded wl again and reopen net_applet dialog. Now there were two wlan devices, one as before and eth1 that listed networks and was able to connect.

I can get my 4313 to work with both drivers. However, if I try to run the network configuration tool when using the broadcom-wl driver, it doesn't complete. If I reboot after installing the necessary packages, I can usually get the interface to work. To use the free driver, I have to uninstall all broadcom-wl packages, reboot, then load the configuration tool and select wlan0 interface (I believe the broadcom also shows up as eth0 or eth1, but selecting that one just prompts for the installation of broadcom-wl).

As a note, as reported earlier, the performance with the free driver is much less and it appears to be due to poor signal strength.

CC: (none) => philippe.l

This bug is still valid in Mageia3 beta4.
I can not get working it at all.

Test results with RC:

device:
brcmsmac : Broadcom Corporation|BCM43224 802.11a/b/g/n [NETWORK_OTHER] (vendor:14e4 device:4353 subv:1028 subd:000e) (rev: 01)

ISO: KDE4 LiveDVD x86_64

When I start net_applet I can now see my device listed but clicking on it will give this error: Unabel to find network interface for selected device (using brcmsmac driver).

I have no idea why net_applet would show such error as lspcidrake also shows brcmsmac as a driver for this device.

To get the network I have to blacklist b43, rmmod b43, ssb, brcmsmac, bcma and then reload bcma.

After this one extra device shows up when restarting net_applet and this device shows my networks and I'm able to connect.

This bug is still valid in RC for device:
02:00.0 Network controller: Broadcom Corporation BCM4312 802.11b/g LP-PHY (rev 01)

Error message:
Unabel to find network interface for selected device (using b43 driver).
When i do a rmmod b43 and try to load wl driver by modprobe it says "Module not found".

(In reply to Sander Lepik from comment #45)
> Test results with RC:
> 
> device:
> brcmsmac : Broadcom Corporation|BCM43224 802.11a/b/g/n [NETWORK_OTHER]
> (vendor:14e4 device:4353 subv:1028 subd:000e) (rev: 01)
> 
> ISO: KDE4 LiveDVD x86_64
> 
> When I start net_applet I can now see my device listed but clicking on it
> will give this error: Unabel to find network interface for selected device
> (using brcmsmac driver).
> 
> I have no idea why net_applet would show such error as lspcidrake also shows
> brcmsmac as a driver for this device.
> 
> To get the network I have to blacklist b43, rmmod b43, ssb, brcmsmac, bcma
> and then reload bcma.
> 
> After this one extra device shows up when restarting net_applet and this
> device shows my networks and I'm able to connect.


Exactly the same here for me:  On a Dell Studio 17 (1747), Wifi reported as BCM43224.

CC: (none) => nelg

There is now new sets of isos to test broadcom wireless configuration

And to make it more fun...
there is now 4 isos so you can test on both i586 & x86_64 and with
both Gnome and KDE4.

NOTE! the isos have "CD" in their name, but most of them are bigger
than 700M so you need a DVD media if you want to burn them,
otherwise I suggest to use a usb stick to boot from, using:

dd if=name_of_iso of=/path/to/usb/stick bs=1M

And to find the isos:

http://mirrors.kernel.org/mageia/people/tmb/mga3-wl-test/
http://ftp.acc.umu.se/mirror/mageia/people/tmb/mga3-wl-test/
http://distrib-coffee.ipsl.jussieu.fr/pub/linux/Mageia/people/tmb/mga3-wl-test/

(and soon on any mirror carrying mageia people/tmb/mga3-wl-test/ tree)

Hello Thomas,

ref:  Mageia-3-test-LiveCD-GNOME-en-x86_64-CD     b10d3a9b6125e534aa5f0b847c2778b4

I tested configuring broadcom WiFi on an HP 6556b laptop and it's working now.
 Yay! :-)

$ lspcidrake -v | grep Broad
bcma            : Broadcom Corporation|BCM43224 802.11a/b/g/n [NETWORK_OTHER] (vendor:14e4 device:4353 subv:103c subd:1510) (rev: 01)
btusb           : Broadcom Corp|HP Integrated Module [Wireless|Radio Frequency|Bluetooth] (vendor:03f0 device:231d)

The first time I tried I went straight to "drakconnect" but it was only showing ndis wrapper driver.

I needed an extra step in the configuration which was to go to the "hardware" tab
in the Mageia Control Centre and click "Browse and Configure hardware".

This loaded "brcmsmac" and then I was able to add a WiFi network interface in "drakconnect".

Kind Regards
Paul
## sent from Mageia-3-test-LiveCD-GNOME-en-x86_64-CD running on a 4gb USB memory stick on HP 6555b laptop ##

It works here too, so I'll close this bug.

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

(In reply to Thomas Backlund from comment #48)
> There is now new sets of isos to test broadcom wireless configuration
> 
> And to make it more fun...
> there is now 4 isos so you can test on both i586 & x86_64 and with
> both Gnome and KDE4.
> 
> NOTE! the isos have "CD" in their name, but most of them are bigger
> than 700M so you need a DVD media if you want to burn them,
> otherwise I suggest to use a usb stick to boot from, using:
> 
> dd if=name_of_iso of=/path/to/usb/stick bs=1M
> 
> And to find the isos:
> 
> http://mirrors.kernel.org/mageia/people/tmb/mga3-wl-test/
> http://ftp.acc.umu.se/mirror/mageia/people/tmb/mga3-wl-test/
> http://distrib-coffee.ipsl.jussieu.fr/pub/linux/Mageia/people/tmb/mga3-wl-
> test/
> 
> (and soon on any mirror carrying mageia people/tmb/mga3-wl-test/ tree)

Should this work from the LiveCD, or does it require an installation?

My findings are that the wifi internet is not listed at all in drakconnect,
but trying: Mageia Control Centre and click "Browse and Configure hardware". detects a needed package "broadcom-bcma-config" however, installation of broadcom-bcma-config failed with: "unable to open rpmdb", on (224cddc2aec04474d39c700e4d94bd63  Mageia-3-test-LiveCD-KDE4-en-i586-CD.iso).



Testing on:(121807db144a021050498eeea8a20ede  Mageia-3-test-LiveCD-KDE4-en-x86_64-CD.iso), hardware config successfully installs broadcom-bcma-config on the 64 bit live cd.  After this, the wifi interface shows up and works.


Tested on a Dell studio 17

02:00.0 Network controller: Broadcom Corporation BCM4312 802.11b/g LP-PHY (rev 01)
testet on Mageia-3-test-LiveCD-KDE4-en-i586-CD.iso 

It still does not work with this device. The device does not even show up in the Network Center and the LED is on off and I can not turn it on.

Doing an lsmod it shows, that there is loaded the module b43, but this device always worked with the wl driver not with b43. But wl driver seems not to exist anymore because doing a "modprobe wl" shows a fatal error: module not found.
What happened to the wl driver? Thanks!

If you go to Harddrake and browse your hardware, does it want to install a broadcom-ssb-config or broadcom-bcma-config ?

If so, does it work after that ?

If not, the broadcom-wl package is on the iso too, so you can install it either through rpmdrake, or with urpmi as root in a terminal:

urpmi broadcom-wl-kernel-desktop586-latest


Does it work after that

YESS YESS YESS, it works!!! :-)

ok, step by step now:
1. browsing hardware it wanted to install broadcom-ssb-config so i did that, but that didn't change anything.
2. i installed the broadcom-wl-kernel-desktop586-latest and it WORKS!
during installation it needs to remove the package broadcom-ssb-config.
3. i removed the modules b43 and ssb and it still works, so there is no need for these modules.
4. i uninstalled the packages for b43 and it still work, so i think there is no need even for them.

Thanks a lot!!!

Hello Thomas,

ref:  Mageia-3-test-LiveCD-GNOME-en-x86_64-CD     b10d3a9b6125e534aa5f0b847c2778b4

Here is what drakconnect shows first time: 
screenshot:    http://i.imgur.com/C3BvqmO.png

Here is what going to Harddrake and "browse hardware" offers: broadcom-bcma-config
screenshot:    http://i.imgur.com/yZOONoD.png

Yes, it does work.

After "browse hardware" in harddrake, drakconnect shows:
screenshot:    http://i.imgur.com/vQTbzQB.png

Connection success:
screenshot:    http://i.imgur.com/8GELNQU.png

ping-tas-tic:
screenshot:    http://i.imgur.com/C6UixHL.png

Kind Regards
Paul
## sent from Mageia-3-test-LiveCD-GNOME-en-x86_64-CD running on a 4gb USB memory stick on HP 6555b laptop ##

# I ran an lsmod before and after configuring WiFi.
# The following is a diff of the before and after lsmod outputs:

[live@localhost ~]$ diff /tmp/2013_05_05_lsmod_before_wifi.txt /tmp/2013_05_05_lsmod_after_wifi.txt
1a2,9
> nls_iso8859_1          12713  1 
> nls_cp437              16991  1 
> vfat                   17461  1 
> fat                    57336  1 vfat
> af_packet              35490  4 
> arc4                   12615  2 
> brcmsmac              517603  0 
> bcma                   41640  1 brcmsmac
22c30
< xt_LOG                 17521  5 
---
> xt_LOG                 17521  6 
97c105
< nf_conntrack_ipv4      19108  24 
---
> nf_conntrack_ipv4      19108  31 
101c109
< xt_conntrack           12760  5 
---
> xt_conntrack           12760  12 
113c121
< ipv6                  340132  59 ip6table_mangle,ip6t_rpfilter,bridge,nf_defrag_ipv6,xt_TPROXY,ip6t_REJECT,nf_conntrack_ipv6
---
> ipv6                  340132  61 ip6table_mangle,ip6t_rpfilter,bridge,nf_defrag_ipv6,xt_TPROXY,ip6t_REJECT,nf_conntrack_ipv6
131d138
< brcmsmac              517603  0 
134,135c141
< b43                   405761  0 
< mac80211              516080  2 b43,brcmsmac
---
> mac80211              516080  1 brcmsmac
138c144
< cfg80211              500693  3 b43,brcmsmac,mac80211
---
> cfg80211              500693  2 brcmsmac,mac80211
140d145
< ssb                    67874  1 b43
146c151
< rng_core               13292  1 b43
---
> rng_core               13292  0 
151c156
< pcmcia                 61803  2 b43,ssb
---
> pcmcia                 61803  0 
158d162
< bcma                   41640  2 b43,brcmsmac
164c168
< rfkill                 26529  5 cfg80211,hp_wmi,bluetooth
---
> rfkill                 26529  6 cfg80211,hp_wmi,bluetooth
198c202
< usb_storage            61501  1 
---
> usb_storage            61501  2 
209c213
< mmc_core              115787  5 b43,ssb,mmc_block,sdhci,sdhci_pci
---
> mmc_core              115787  3 mmc_block,sdhci,sdhci_pci

Hello Thomas,

ref:  Mageia-3-test-LiveCD-GNOME-en-x86_64-CD     b10d3a9b6125e534aa5f0b847c2778b4

$ lspcidrake -v | grep Broadcom
bcma            : Broadcom Corporation|BCM43224 802.11a/b/g/n [NETWORK_OTHER] (vendor:14e4 device:4353 subv:103c subd:1510) (rev: 01)
btusb           : Broadcom Corp|HP Integrated Module [Wireless|Radio Frequency|Bluetooth] (vendor:03f0 device:231d)


I also tried your alternative suggestion:
    urpmi broadcom-wl-kernel-desktop586-latest

This does not work for me (newly booted live).

At start:
    http://i.imgur.com/A6hTwT2.png

Drakconnect:
    http://i.imgur.com/MCIfJ1s.png

On running: urpmi broadcom-wl-kernel-desktop586-latest 
    http://i.imgur.com/A6hTwT2.png

Drakconnect now shows the broadcom driver option:
    http://i.imgur.com/qjQI8em.png

Looks promising, wireless access points detected and SSIDs displayed:
    urpmi broadcom-wl-kernel-desktop586-latest

Connection attempt fails:
    http://i.imgur.com/Q5VbmGc.png

## sent from Mageia-3-test-LiveCD-GNOME-en-x86_64-CD running on a 4gb USB memory stick on HP 6555b laptop ##

I confirm comment 54 about Broadcom BCM4312 LP-PHY with Mageia-3-test-LiveCD-KDE4-en-i586-CD.iso.
I just tested it with a netbook Lenovo Ideapad S10 with
  Broadcom Corporation|BCM4312 802.11b/g LP-PHY [NETWORK_OTHER]
  (vendor:14e4 device:4315 subv:14e4 subd:04b5) (rev: 01)

It doesn't run OOTB by default with this iso using ssb/b43:
dmesg |grep "ssb\|b43"
[   24.140574] ssb: Found chip with id 0x4312, rev 0x01 and package 0x00
[   24.140604] ssb: Core 0 found: ChipCommon (cc 0x800, rev 0x16, vendor 0x4243)
[   24.140627] ssb: Core 1 found: IEEE 802.11 (cc 0x812, rev 0x0F, vendor 0x4243)
[   24.140650] ssb: Core 2 found: PCMCIA (cc 0x80D, rev 0x0A, vendor 0x4243)
[   24.140673] ssb: Core 3 found: PCI-E (cc 0x820, rev 0x09, vendor 0x4243)
[   24.191680] ssb: Sonics Silicon Backplane found on PCI device 0000:05:00.0
[   26.088591] b43-phy0: Broadcom 4312 WLAN found (core revision 15)
[   26.105276] b43-phy0: Found PHY: Analog 6, Type 5 (LP), Revision 1
[   26.105302] b43-phy0 debug: Found Radio: Manuf 0x17F, Version 0x2062, Revision 2
[   26.310540] b43-phy0 ERROR: Firmware file "b43/ucode15.fw" not found
[   26.310550] b43-phy0 ERROR: Firmware file "b43-open/ucode15.fw" not found
[   26.310558] b43-phy0 ERROR: You must go to http://wireless.kernel.org/en/users/Drivers/b43#devicefirmware and download the correct firmware for this driver version. Please car this website.

With ssb/b43, the BCM4312 802.11b/g LP-PHY needs a firmware (extracted from wl_apsta.o by b43-fwcutter) that we can't provide AFAIK.


But BCM4312 802.11b/g LP-PHY (14e4:4315) works with wl when I install broadcom-wl-kernel-desktop586-latest.

CC: (none) => lmenut

This bug is still valid in Mageia 3 Final for
02:00.0 Network controller: Broadcom Corporation BCM4312 802.11b/g LP-PHY (rev 01)
at least with Live-DVD.

I still get b43 and ssb installed which do not work with this device. So I have to manually uninstall b43 and ssb and install broadcom-wl
It's kind of disappointing ...

Agree with the comments of egc. This ought to work out of the box (the device is hardly "new") and is presumably down to the detection of the device, which is clearly enough identified in the bug report, and when it is that card then don't put ssb/b43 drivers in and use wl instead. So as per what Mageia 2 did before these others were added (so there's a workaround, great, but that won't help people less technically minded)

CC: (none) => andy_jefferson

I wonder what we are testing for, if doesn't get fixed anyway ...

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

That is not very fair- all that testing was due to just as much fixing: it is not the lack of will to fix, but of the lack of will of the problem to let itself be fixed that is frustrating (-

Sorry Juergen, but your statement is really to philosophical for me... 
It sounds more like a tractatus of Sartre than a simple explaination of why something is not fixed even though it's made very clear during the tests, that this certain device does not work with ssb/b43, but only with wl ...

Our (human) resources are very limited. You can get your device working by installing correct driver. That makes this bug less important. We had a lot more serious problems to solve..

If Broadcomm's proprietary drivers would work as they are advertised, we wouldn't have this mess. Agree with Sander, our resources are very limited, certainly more limited than those of who made the proprietary driver and don't trow resources at it to fix it.

One last time: there IS ALREADY a driver that WORKS with the device we were talking about above. So there is no need for any extra human resources or to fix a driver that works (proprietary or not). Am i right?
Ok, if the driver works the only thing to fix in Mageia for the person that already worked on this matter was to tell the system to install and load the working driver for this special device instead of other drivers that don't work. That's all!
What is so hard to understand on this??

I have no problems with installing the working driver, because i already know about it, but there are probably people out there that don't know yet the solution to this problem and they waist a lot of time searching for a solution, if they didn't give up right away ...

Do you understand that most Broadcom devices were not working (some of them not working at all!!!). And there are a lot of them. We really did our best to get them supported but we missed some. Too bad, what can we do. Thomas did most of the hard work here. But he also had to build all the Live isos. Not once, not twice.. but many-many times. And it wasn't just about building them but also fixing problems in them. We missed one stupid driver and you are screaming like the world is ending.. Really, getting those Live isos to boot and work as expected was a bit higher priority than to fix some not detected device problem.
If you have problem with that, well, join the packagers/developers team and help us fix the problems for Mageia 4.

Is it clear enough for you now?

Guys, please calm down...

(In reply to egc from comment #65)
> One last time: there IS ALREADY a driver that WORKS with the device we were
> talking about above. So there is no need for any extra human resources or to
> fix a driver that works (proprietary or not). Am i right?
> Ok, if the driver works the only thing to fix in Mageia for the person that
> already worked on this matter was to tell the system to install and load the
> working driver for this special device instead of other drivers that don't
> work. That's all!

Nope.

There is more than one driver that _works_ with Broadcom Corporation BCM4312, even if it does not happend to work on _your_ system for some reason. So we cant just go ahead and blindly force the broacom-wl driver on everyone with that hw. Not to mention we have reports of the free drivers working better than the proprietary one... 

So the human resouces needed is to make the configuration tools the capability to ask you if you want to use the proprietary driver (like we do for GPUs), and configure the system accordingly.

> What is so hard to understand on this??
> 

Well, the "hard to understand" part is how people seem to forget that all of us working on this is doing it on our free time, and sometimes life "screws ones plans", so we simply didnt have time to do the necessary changes and validate them for mga3. That sucks, but nothing I can do about that now.

So making sure there were broadcom-wl packaging that overrides all free drivers in case nothing else works, was the best we could do before mga3 release time to give all the choice they want. Maybe you dont like that decision, but that's now reality.

> I have no problems with installing the working driver, because i already
> know about it, but there are probably people out there that don't know yet
> the solution to this problem and they waist a lot of time searching for a
> solution, if they didn't give up right away ...

Well, if they dont know how to read errata / ask on forums or on mls...

I have a section in the errata at: 
https://wiki.mageia.org/en/Mageia_3_Errata#Broadcom_Wireless


Anyway, if you want to continue to figure out why the free driver does not work on your hw we can do so, but for me that will be in a couple of months due to health issues...

Probably the sensible path forward for MGA4 and possible update for MGA3 is to expand the drakconnect logic that lists driver choices (linux, Windows via ndiswrapper) to list multiple linux driver choices if they exist, and modify the help to indicate that the top choice is the recommended one, but that if it doesn't work for you you can choose another.  I get the feeling that this won't be the last proprietary or even open-source driver that will be forked or reimplemented.

There's precedent for this in the way that system-config-printer presents driver choices.

(In reply to Sander Lepik from comment #66)
> We missed one stupid driver and you
> are screaming like the world is ending.. 

No, you are screaming like "world is ending", i don't even need this driver anymore.
> 
> Is it clear enough for you now?

Yesssssssirrrrr!!

(In reply to Thomas Backlund from comment #67)
> There is more than one driver that _works_ with Broadcom Corporation
> BCM4312, even if it does not happend to work on _your_ system for some
> reason. So we cant just go ahead and blindly force the broacom-wl driver on
> everyone with that hw. Not to mention we have reports of the free drivers
> working better than the proprietary one... 

Sorry, i didn't know about that. I thought we found the solution for this specific hardware installing the wl driver ...
If there would have been a note earlier in the bug report on what you wrote here i would have understood why "my" kind of solution is "ignored" by the packagers.

> So making sure there were broadcom-wl packaging that overrides all free
> drivers in case nothing else works, was the best we could do before mga3
> release time to give all the choice they want. 

How did Ubuntu solve this, it seems to work there or am i wrong?

> I have a section in the errata at: 
> https://wiki.mageia.org/en/Mageia_3_Errata#Broadcom_Wireless

ok, that's already a help for most of newbies.

> Anyway, if you want to continue to figure out why the free driver does not
> work on your hw we can do so, 

I'm sorry, but i don't have this device anymore, it broke down a few days ago ...
However, thanks for explanation and get well soon!

egc

no possibility to check anymore

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