Wireless card looping write log

If you found these line in your kern.log, syslog

Jan 27 13:54:51 xango3 kernel: [98499.658770] ERROR @wl_cfg80211_get_station : Could not get rate (-1)
Jan 27 13:54:51 xango3 kernel: [98499.658778] ERROR @wl_cfg80211_get_station : Could not get rssi (-1)
Jan 27 13:54:52 xango3 dhclient: DHCPREQUEST of 192.168.1.133 on eth2 to 192.168.1.2 port 67
Jan 27 13:54:56 xango3 kernel: [98504.646146] net_ratelimit: 22 callbacks suppressed
Jan 27 13:54:56 xango3 kernel: [98504.646152] ERROR @wl_cfg80211_get_station : Could not get rate (-1)
Jan 27 13:54:56 xango3 kernel: [98504.646158] ERROR @wl_cfg80211_get_station : Could not get rssi (-1)
Jan 27 13:54:57 xango3 kernel: [98505.562569] ERROR @wl_cfg80211_get_station : Could ...

 That mean something happen like in https://bugs.launchpad.net/ubuntu/+source/bcmwl/+bug/1107155

 and Oedipe point me to the exit
"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 your type of BCM.
Reboot => done ! No more "wl continuously spams syslog" and my wifi is stable and strong now." 

 After uninstall then install something new, then REBOOT!
So thank Oedipe and launchpad

Comments

Post a Comment

Popular posts from this blog

Return Code 127

Exit codes and kill-job signals The exit code from a batch job is a standard Unix termination status, the same sort of number you get in a shell script from checking the " $? " variable after executing a command. Typically, exit code 0 (zero) means successful completion. Codes 1-127 are typically generated by your job itself calling  exit()  with a non-zero value to terminate itself and indicate an error. In BaBar we don't make very much use of this. The most common such value you might see is 64, which is the value used by Framework to say that its event loop is being stopped before all the requested data have been read, typically because time ran out. In recent BaBar releases you might also see 125, which we use as a code for a generic "severe error"; the job log should contain a message stating what the error was. Exit codes in the range 129-255 represent jobs terminated by Unix " signals ". Each type of signal has a number, and what's r
Read more