Results 1 to 3 of 3
Hi, I've gotten my wireless to work but it disconnected sometimes and I would have to run 'ifconfig wlan0 down' and then 'ifconfig wlan0 up' to get it working again.
...
- 12-27-2010 #1Just Joined!
- Join Date
- Dec 2010
- Posts
- 6
Help with Broadcom wireless :(
Hi, I've gotten my wireless to work but it disconnected sometimes and I would have to run 'ifconfig wlan0 down' and then 'ifconfig wlan0 up' to get it working again.
Now its completely stopped working, it seems to get stuck associating with my network for some reason. My key is correct though.
My card:
My ifconfig:Code:$ lspci | grep Broadcom 01:00.0 Network controller: Broadcom Corporation BCM4312 802.11b/g (rev 01)
And tons of info from running 'cat /var/log/daemon.log | grep NetworkManager':Code:$ ifconfig eth0 Link encap:Ethernet HWaddr 00:26:22:51:05:4D inet addr:10.0.1.198 Bcast:10.0.1.255 Mask:255.255.255.0 inet6 addr: fe80::226:22ff:fe51:54d/64 Scope:Link UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:56803 errors:0 dropped:0 overruns:0 frame:0 TX packets:29868 errors:0 dropped:0 overruns:0 carrier:1 collisions:0 txqueuelen:1000 RX bytes:83050660 (79.2 Mb) TX bytes:2318656 (2.2 Mb) Interrupt:42 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:0 errors:0 dropped:0 overruns:0 frame:0 TX packets:0 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:0 (0.0 b) TX bytes:0 (0.0 b) wlan0 Link encap:Ethernet HWaddr 00:26:5E:86:66:45 inet6 addr: fe80::226:5eff:fe86:6645/64 Scope:Link UP BROADCAST MULTICAST MTU:1500 Metric:1 RX packets:41 errors:0 dropped:0 overruns:0 frame:0 TX packets:14 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:3372 (3.2 Kb) TX bytes:2532 (2.4 Kb)
http ://pastie.org/1408934 Delete the space, I can't post a url yet
(chestnut is my network)
I have comcast and I heard its been having some problems, so maybe I should use a different dns? LIke google's?
- 12-27-2010 #2
Broadcom cards are endlessly problematic it seems. Anyway, I have the same chipset.
First thing, I see you're using the b43 driver. While this does now support the card you need to pass a couple options to the driver for it to work
See if this helps
If so add to /etc/modprobe.d/modprobe.conf the following lineCode:modprobe -r b43 modprobe b43 pio=1 qos=0
I recall reading somewhere the downside to this is that it hurts performance for protocols other than http.Code:options b43 pio=1 qos=0
Alternately, you can use the broadcom wl driver. This is what I'm currently using. For some reason, and this is new, it's started to go into a deep sleep if I leave the computer unattended for a while, and the card won't wake back up until I unload and reload the driver. I haven't figured out what the trouble is yet or if there is a fix, but it's only mildly annoying. Whether you'd suffer the same I couldn't say.
- 12-27-2010 #3Just Joined!
- Join Date
- Dec 2010
- Posts
- 6
Thanks alot for your help, I did what you said and it works now, though I can't say for how long. I sometimes use some SOCKS5 proxies, so hopefully it wont show.
But I agree broadcom really is a bad choice for linux, unfortunately, I didn't really know much about linux when I bought my netbook.


Reply With Quote
