Description of problem: There is a bug in the driver of BCM43224 devices released with Mageia 1. This makes Wi-Fi useless on battery. This new version fixes the problem on my laptop, it will be hard to find the same hardware in QA I think...
New version of what Jose?
broadcom-wl-5.100.82.112-1.mga1 according to the BS :)
It is a new version of the proprietary driver. But of course, they never provide a patch to current version, so we have to get it all.
Status: NEW => ASSIGNED
I'm not sure how we'll test this one, I think leuhmanu has broadcom wifi. We can maybe put a call out on the ML if not.
José is this driver just for that one specific wifi card or does it cover a range?
More info here I think - http://www.broadcom.com/support/802.11/linux_sta.php The rpm is dkms-broadcom-wl. --- These packages contain Broadcom's IEEE 802.11a/b/g/n hybrid Linux® device driver for use with Broadcom's BCM4311-, BCM4312-, BCM4313-, BCM4321-, BCM4322-, BCM43224-, and BCM43225-, BCM43227- and BCM43228-based hardware. --- From the website.
Hello I have the card: BCM4313 so I can not confirm that the update solve the bug. (And I have never see this issue with this one.) But I can confirm that the new version works as the old on x86_64 arch. ;)
Hum I have every minute 4 'ERROR' in syslog / dmesg Nov 9 02:14:36 vosdook kernel: ERROR @wl_cfg80211_get_station : Wrong Mac address Nov 9 02:14:36 vosdook kernel: ERROR @wl_cfg80211_get_station : Wrong Mac address Nov 9 02:14:36 vosdook kernel: ERROR @wl_dev_intvar_get : error (-1) Nov 9 02:14:36 vosdook kernel: ERROR @wl_cfg80211_get_tx_power : error (-1) Nov 9 02:15:01 vosdook CROND[10403]: (apache) CMD ( /usr/share/bugzilla/bin/whine.pl > /dev/null 2>&1) Nov 9 02:15:36 vosdook kernel: ERROR @wl_cfg80211_get_station : Wrong Mac address Nov 9 02:15:36 vosdook kernel: ERROR @wl_cfg80211_get_station : Wrong Mac address Nov 9 02:15:36 vosdook kernel: ERROR @wl_dev_intvar_get : error (-1) Nov 9 02:15:36 vosdook kernel: ERROR @wl_cfg80211_get_tx_power : error (-1) Nov 9 02:16:36 vosdook kernel: ERROR @wl_cfg80211_get_station : Wrong Mac address Nov 9 02:16:36 vosdook kernel: ERROR @wl_cfg80211_get_station : Wrong Mac address Nov 9 02:16:36 vosdook kernel: ERROR @wl_dev_intvar_get : error (-1) Nov 9 02:16:36 vosdook kernel: ERROR @wl_cfg80211_get_tx_power : error (-1) do you know why ?
No, but : - do you have the same problem after a reboot? - is it a problem introduced by the new driver? - does the wifi still work?
(In reply to comment #7) > Hello I have the card: BCM4313 so I can not confirm that the update solve the > bug. (And I have never see this issue with this one.) > But I can confirm that the new version works as the old on x86_64 arch. ;) I think your card should be better handled by the free b43 driver, did you try it?
(In reply to comment #9) > No, but : > - do you have the same problem after a reboot? yes > - is it a problem introduced by the new driver? yes > - does the wifi still work? yes I have test on cauldron and I can't see this ERROR (before the update, the device was called eth1 and now it's wlan1) In Mageia 1 the device is also called eth1 (In reply to comment #10) > (In reply to comment #7) > > Hello I have the card: BCM4313 > I think your card should be better handled by the free b43 driver, did you try > it? No because according to http://wireless.kernel.org/en/users/Drivers/b43 it's not supported. I don't think my 'issue' is a blocker for the update.
(In reply to comment #11) > I have test on cauldron and I can't see this ERROR (before the update, the > device was called eth1 and now it's wlan1) I also have the ERROR messages in Mageia 1. According to http://www.broadcom.com/docs/linux_sta/README.txt : + Added cfg80211 API support. So I think there is a feature in the 2.6.38 kernel with this API that throws lots of debug messages, while in cauldron we have 3.x kernels that solve the problem. I agree with you this should not block the update.
Thomas, do you know if we can remove the debug messages ?
CC: (none) => tmb
Thomas could you comment on this matter please, thanks.
There is now #3618 that brings an update package. So when it is validated, we should just push : broadcom-wl-5.100.82.112-2.mga1 for both bugs.
Depends on: (none) => 3618
Update pushed.
Status: ASSIGNED => RESOLVEDResolution: (none) => FIXED
ERROR @wl_cfg80211_get_station : Wrong Mac address ERROR @wl_cfg80211_get_station : Wrong Mac address ERROR @wl_dev_intvar_get : error (-1) ERROR @wl_cfg80211_get_tx_power : error (-1) ERROR @wl_cfg80211_get_station : Wrong Mac address ERROR @wl_cfg80211_get_station : Wrong Mac address ERROR @wl_dev_intvar_get : error (-1) ERROR @wl_cfg80211_get_tx_power : error (-1) ERROR @wl_cfg80211_get_station : Wrong Mac address ERROR @wl_cfg80211_get_station : Wrong Mac address ERROR @wl_dev_intvar_get : error (-1) I have this too in my dmesg, but wlan is working perfectly.
CC: (none) => n54