You are not logged in.
Pages: 1
I'm using the broadcom-wl driver with my bcm4328 a/g/n wireless card and am having some issues that I didn't find anyone else reporting. I installed the driver and setup my rc.conf to use wicd to manage my WEP network (I know WEP sucks, but I don't want to add anymore complexity until everything is working). When I first boot the laptop, wicd finds and automatically connects to my network and everything seems to work. However, after a few hours (sometimes more sometimes less) it loses connection, and I can't get wicd to reconnect. I can get it to reconnect if I open a terminal and modprobe -r wl && moprobe wl. After reloading wl the network works fine again. I've seen people on the forum reporting that broadcom-wl works fine for bcm4328, but it sure looks like a driver issue to me. Does anybody have any idea what's going on?
Offline
I'm using that driver with a bcm4322 chipset if I'm not mistaken (Macbook 5.5).
I have not (yet) encountered those problems. Did you follow the wiki? There are other modules you have to blacklist, f.e. the ssb-module.
Furthermore I can vouch for netcfg instead of wicd to connect. Together with wifi-select and netcfg-tray (both in AUR IIRC), you should have a wicd-replacement with the added benefit you don't need X to connect to a network.
Offline
you should have a wicd-replacement with the added benefit you don't need X to connect to a network.
wicd doesn't need X, the package includes wicd-curses
Offline
I originally installed the module from http://www.broadcom.com/support/802.11/linux_sta.php. After I was having the problems described above, I removed the module and installed the AUR package according to the wiki. This didn't change the issues though. I have b43 and ssb blacklisted and wl and lib80211_crypt_tkip enabled. Though I'm not entirely sure what the difference is between lib80211_crypt_tkip, lib80211_crypt_wep, lib80211, etc. At any rate none of the combinations seemed to make a difference. I did have to do the interface switching fix.
Offline
* posted in wrong thread! Sorry.
Last edited by whiteychs (2009-10-16 19:17:48)
Offline
When this happens:
Does your wireless interface still show up with ifconfig -a?
Does it still say your interface is configured for wireless with iwconfig?
Can you do a scan with iwlist <your-interface-name> scan?
If so, can you manually connect to your network with iwconfig (see wireless wiki)?
Offline
Well, sure as I try and stamp out this problem, it hasn't happened for the past few days. Maybe some update fixed it?
I have a question though, at some point in this process, I tried to run wicd-client as root and I had a segmentation fault. I was trying to shutdown/restart wicd-client on suspend/resume, which apparently was executing as root. Anybody know why this would be?
Offline
aroemike, I am having this same problem on the same hardware. Did you find a solution?
Offline
aroemike, I am having this same problem on the same hardware. Did you find a solution?
I ended up using netcfg which seems to work as expected. I had to downgrade from the most recent version due to wpa issues though.
Offline
Pages: 1