Arch Linux

Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines

Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.

REPEAT: Do NOT report bugs for outdated packages!
Tasklist

FS#25454 - [linux]

Attached to Project: Arch Linux
Opened by matteo cameletti (capnion) - Monday, 08 August 2011, 10:52 GMT
Last edited by Tom Gundersen (tomegun) - Monday, 08 August 2011, 11:13 GMT
Task Type Bug Report
Category Upstream Bugs
Status Closed
Assigned To No-one
Architecture All
Severity High
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

Description:
after upgrading to kernel 3.0 and installing broadcom-wl drivers from AUR, wireless connections stop working. to re-establish the wireless connection it was necessary to blacklist bcma. After that I receive messages at loglevel 4 and 5 that seem to be miscategorized at those levels.





Additional info:
* package version(s)
kernel 3.0
broadcom-wl 5.100.82.38-5

* config and/or log files etc.:
Arch Linux 3.0-ARCH (myhost) (tty1)

myhost login: [ 15.025853] ieee80211 phy0: wl_ops_config: change monitor mode: false (implement)
[ 15.025956] ieee80211 phy0: wl_ops_config: change power-save mode: false (implement)
[ 15.026710] ieee80211 phy0: wl_ops_bss_info_changed: qos enabled: false (implement)
...


Steps to reproduce:
Upgrade to kernel 3.0, install broadcom-wl 5.100.82.38-5 from AUR and blacklist bcma
This task depends upon

Closed by  Tom Gundersen (tomegun)
Monday, 08 August 2011, 11:13 GMT
Reason for closing:  Not a bug
Comment by Tom Gundersen (tomegun) - Monday, 08 August 2011, 11:05 GMT
I think this should be fixed in broadcom-wl. E.g., they could add a file "/lib/modprobe.d/broadcom-wl.conf", containing:

blacklist bcma

Edit: corrected filename.
Comment by matteo cameletti (capnion) - Monday, 08 August 2011, 11:11 GMT
Ok thanks, I will report that in the right place...
but the miscategorized messages are the real problem...

Loading...