I must add, everything works just fine with the WiFi apart from the SSD
getting hammered with repeated writes on to the syslog.
--
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
For Flying Spaghetti Monster's sake This bug still happens on
Trusty. How hard is it to fix the issue so that my /var/log/syslog
doesn't grow to multiple GBs in a single day and still remains useful?!
Stop bickering and put a simple fix in, i.e. only reporting the error
once, not every two
@Adam,
I used your instructions in comment #15 and although it seemed to
work, but after the restart the wireless would not work. The reason was
that immediately after the restart, before the reboot, the 'wl' driver
was still loaded and continued to provide network access. But after the
For completeness:
I am using kernel 3.8:
Linux work 3.8.0-30-generic #44~precise1-Ubuntu SMP Fri Aug 23 18:32:41 UTC
2013 x86_64 x86_64 x86_64 GNU/Linux
On Ubuntu 12.04 installed using:
sudo apt-get install linux-image-generic-lts-raring
linux-headers-generic-lts-raring
--
You
@gurjeet,
I'd recommend you just download the saucy .deb and install it
(http://packages.ubuntu.com/saucy/amd64/bcmwl-kernel-source/download for
64-bit).
It solves basically every problem the bcmwl driver had (ever) had.
AFAIK.
--
You received this bug notification because you are a member of
@Bernardo,
Thanks so much!!! That indeed eliminated the clutter in kernel logs!
I had added this line to syslog to prune out the messages from
syslog (but not the kernel logs)
:msg, contains, wl_cfg80211_get_station : Could not get ~
I can now remove this and live in peace with
@accountexist: can you give us just the patch?
--
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:
A modified version of the wl driver (just commented the errors out, so
they wont pop up) can be found here:
http://www.mediafire.com/download/8gq5vz3bghi1hhu/wl.tar.gz
The compiled-binary version can be found here:
http://www.mediafire.com/download/50hzvm0pbbcxzlq/wl.ko
It's not a permament fix
13.04 with kernel 3.8.0-26 and BCM4331 card.
bcmwl-kernel-source 6.20.155.1
dmesg output:
[ 6592.905573] ERROR @wl_cfg80211_get_station : Could not get rssi (-1)
[ 6594.903577] ERROR @wl_cfg80211_get_station : Could not get rate (-1)
[ 6594.903582] ERROR @wl_cfg80211_get_station : Could not get
Lubuntu 12.04 kernel 3.2.0-48-generic.
I was getting the sys.log spammed by ERROR @wl_cfg80211.
I was using Broadcom Corporation BCM4321 for wireless and the driver
was wl: bcmwl-kernel-source.
I uninstalled everything that was installed and at
http://wireless.kernel.org/en/users/Drivers/b43
No it's not 1097519.
This bug is about bcmwl, not about open-source vs closed-source policy
decisions. BTW, the bcmwl driver is the *only* working driver for many
chipsets, so whether the bug is reported in connection with a chipset
supported by other driver IS IRRELEVANT. bcmwl has bugs that
I'm affected by this bug, and I have a BCM4321 chip
Please note that the patch linked in comment #18 is NOT ENOUGH
that only deals with the Could not get rssi error (from get_station),
but the log is being spammed also with messages of
could not get rate from get_station
error from invar_get
On Wed, Jun 12, 2013 at 10:27 AM, Dario Bertini berda...@gmail.com
wrote:
I'm affected by this bug, and I have a BCM4321 chip
Please note that the patch linked in comment #18 is NOT ENOUGH
that only deals with the Could not get rssi error (from get_station),
but the log is being spammed
Bernardo,
The problem for some users seems to be that the wrong driver is being
used. For myself and some others who commented here, using a different
driver made the the card work and didn't print the messages. Those
messages may be indicating a problem; if so, hiding them might not be
the
I am the OP. 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.
This happens with version 6.20.155.1+bdcom-0ubuntu6 on all Ubuntu
versions.
By the way, wireless works perfectly here. *THAT* would need reporting
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
Adam Porter: This a bug of a _specific_ driver. Whether your hardware
works with alternative driver or not has _zero_ coreleation with this
bug. Stop _spamming_.
** Changed in: bcmwl (Ubuntu)
Status: Incomplete = Confirmed
--
You received this bug notification because you are a member of
@Adam Porter: I think you are conflating two (or more) different issues.
The issue on *this* bug is that bcmwl spams the logs. It is *NOT* that
it does, or does not, work. It is *NOT* about the b43, broadcom-sta, or
brcmsmac drivers. As far as this bug is concerned, these other drivers
are
hggdh2,
Wow, instead of just posting the output of $(lspci | grep Broadcom),
you're refusing and arguing.
Again: If one of the other drivers works, then this bug report is moot.
If brcmsmac (the in-tree driver, which is Completely open source host
drivers, no binary object files.) works, the
$ lspci | grep Broadcom
03:00.0 Network controller: Broadcom Corporation BCM43224 802.11a/b/g/n (rev 01)
$
There. Now that I have stated what is my Broadcom card, please DO NOT
CHANGE THE BUG STATUS AGAIN. This is a *valid* bug, no matter what you
think. Given that you are unable to understand
http://wireless.kernel.org/en/users/Drivers/brcm80211#Supported_Chips
BCM43224
--
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
From what I can gather the original reporter was concerned about the
excessive number of messages in their syslog regarding the wl driver.
There is in fact a patch for this here:
http://pkgbuild.com/git/aur-mirror.git/commit/broadcom-
wl?id=e87e8290a6d1abd88c064d51cc94f19b137bae11
here are the
On Tue, Jun 11, 2013 at 3:28 PM, Brian Murray br...@ubuntu.com wrote:
As such it'd be great if Adam Porter could
submit a new bug report regarding his issue of the incorrect driver
being used. Once a new bug report has been created I'll personally
ensure that someone looks at it.
Again,
@Adam Porter,
YOU are completely ridiculous. This bug is about the wl module reporting
too much on the kernel log, not about whatever problem you may have with
Raring.
There is a patch that fixes this bug.
** This bug is no longer a duplicate of bug 1097519
Wrong driver used for older
This is absolutely ridiculous! Raring has been out for months now, and
this bug was reported months before:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1114281
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1163401
I upgraded my perfectly-working netbook from Quantal to
*** This bug is a duplicate of bug 1097519 ***
https://bugs.launchpad.net/bugs/1097519
** This bug has been marked a duplicate of bug 1154219
Older Broadcom chipsets require older driver [Raring, Saucy]
** This bug is no longer a duplicate of bug 1154219
Older Broadcom chipsets require
I have a shit loads of ERROR @wl_cfg80211_get_station : Wrong Mac
address but wl works better than b43 after all.
--
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
I have this bug on Kubuntu 13.04 x64 with Acer TM B113-E notebook.
b43-fwcutter have not help for me.
I am reconfigure rsyslog.conf and add new line before /var/log/syslog rule:
:msg, contains, ERROR @wl_cfg80211_get_station : Could not get ~
*.*;auth,authpriv.none -/var/log/syslog
and
** Changed in: bcmwl (Ubuntu)
Importance: Undecided = Medium
--
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
See bug #114281
Still left not assigned and affects thousands of users, even in tthe Ubuntu
12.0.4 LTS
Ubuntu is a No go for me actually.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1107155
Well, after some hours trying to solve the issue, i found the trick !
(it does work for me on a Lenovo with a BCM4312)
Uninstall completely bcmwl-kernel-source ! (seems buggy)
Install instead b43-fwcutter and firmware-b43-lpphy-installer (for
BCM4312), or the others BCM installers according to
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: bcmwl (Ubuntu)
Status: New = Confirmed
--
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
I had the same issue (12.04 with kernel 3.5 and the new dkms module).
See here:
https://bugs.launchpad.net/ubuntu/+source/bcmwl/+bug/923809/comments/22
Applying the user-ioctl.patch patch found here:
https://aur.archlinux.org/packages.php?ID=19514 removed those two
error/warning messages.
33 matches
Mail list logo
