hggdh2,
> This did not need reporting the hardware at the time, and I am not
sure it needs it now. The issue is quite simple: wl spams the log.
Are you kidding me? You think reporting a driver bug doesn't require
reporting which of the 9+ different hardware it supports?
I will reiterate: I had this exact problem. I removed the wl driver
(the bcmwl-kernel-source package), causing the in-tree driver to be
used, and the problem was solved. Therefore it is a duplicate of bug
1097519, which states that the correct driver needs to be used.
If you disagree, you are going to have to prove that this bug exists by:
1. Reporting your hardware. Otherwise no one can take this report seriously.
2. Testing all the other drivers (b43, broadcom-sta, and brcmsmac) and proving
they all have the same problem. If one of the other drivers works, then this
bug report is moot.
Alternatively, you are going to have to explain why a driver developer
needs to fix bcmwl-kernel-source when other existing drivers work fine,
e.g. if one of the other three drivers doesn't work for you. But if
that were the case, the solution might be to fix the other driver, not
to fix this one. We need fewer redundant drivers, not more.
** Changed in: bcmwl (Ubuntu)
Status: Confirmed => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1107155
Title:
wl continuously spams syslog
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bcmwl/+bug/1107155/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
