As in the thread. I have BCM 4313 wireless card and I use proprietary driver for this cuz I couldn't run it on brcmsmac driver. Everything worked fine for a long time. But some time ago I opened system logs and It was full of errors connected with this driver.
Code:
[ 893.305713] ERROR @wl_cfg80211_get_station : Could not get rssi (-1)
[ 895.303435] ERROR @wl_cfg80211_get_station : Could not get rate (-1)
[ 895.303439] ERROR @wl_cfg80211_get_station : Could not get rssi (-1)
[ 897.301276] ERROR @wl_cfg80211_get_station : Could not get rate (-1)
[ 897.301280] ERROR @wl_cfg80211_get_station : Could not get rssi (-1)
[ 897.301345] ERROR @wl_cfg80211_get_station : Could not get rate (-1)
[ 897.301347] ERROR @wl_cfg80211_get_station : Could not get rssi (-1)
Here You can see theese logs. There are thousands of lines like that. I have no idea what could really happened, becouse I wasn't messing with any wireless settings as it worked fine. I use wicd. And here's an output of ifconfig
Code:
eth0 Link encap:Ethernet HWaddr e8:11:32:92:da:1a
UP BROADCAST MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:0 (0.0 B) TX bytes:0 (0.0 B)
eth1 Link encap:Ethernet HWaddr e0:ca:94:9a:51:18
inet addr:192.168.0.2 Bcast:192.168.0.255 Mask:255.255.255.0
inet6 addr: fe80::e2ca:94ff:fe9a:5118/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:5066 errors:0 dropped:0 overruns:0 frame:25103
TX packets:5502 errors:44 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:3127312 (2.9 MiB) TX bytes:884517 (863.7 KiB)
Interrupt:16
lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
inet6 addr: ::1/128 Scope:Host
UP LOOPBACK RUNNING MTU:16436 Metric:1
RX packets:104 errors:0 dropped:0 overruns:0 frame:0
TX packets:104 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:6896 (6.7 KiB) TX bytes:6896 (6.7 KiB)
I'm using gentoo with 3.5.0 gentoo kernel. The same happened with 3.4.2 kernel when I tried to fix it somehow. Any ideas of what could have happened?