SlackwareThis Forum is for the discussion of Slackware Linux.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
Exellent If you start to have trouble, a report would be appreciated.
Maybe I'll try upgrading my kernel sometime soon.
Yes, the lib80211 module seems to load on boot, with the wl. This command was issued immediately after booting (with non-functioning wireless):
Any idea about lib80211_crypt_tkip? Should that be there as well?
Thanks again.
That all looks fine as far as I can tell. When it isn't working, check the output of dmesg for errors with the wireless. Might give some clue.
What kind of encryption are you using? How are you managing the network? If you're not, I would recommend trying WICD to manage your connections and see if that helps.
[edit: you say you're using 2.6.32 and the driver isn't working quite right.. what's it doing, or not doing? I wonder if it would be less hassle than what I'm dealing with now..]
In kernel 2.6.33 (Slackware-Current), the b43 driver gives fatal DMA errors. It *kinda* works if I load wl first, unload wl, and then load b43.
With the 2.6.32.x kernels, the b43 driver caused very high CPU usage for me.
Update: Kernel 2.6.34-RC1: Works for about 20 seconds, then disconnects and won't reconnect
My PCI-ID is also 14e4:4315, btw.
If you decide to try kernel 2.6.33, the broadcom-sta driver needs to be patched or else it won't compile
I seem to have gotten it sorted out. First, I found a command sequence that seemed to make it work consistently:
Code:
iwconfig eth1 essid <my essid>
iwconfig eth1 key <my key>
ifconfig eth1 down
ifconfig eth1 up
/etc/rc.d/rc.inet1 eth1_start
Then today at work I noticed that on my work laptop my essid & key were in rc.wireless.conf, not rc.inet1.conf (as it was on this laptop). I moved the settings to rc.wireless.conf, and it worked. I've rebooted 5 times, and it's worked each time.
I remember reading somewhere that rc.wireless.conf was being phased out, and that using rc.inet1.conf was preferred. Can someone explain what's going on here?
And, slackwaredenny, you'll probably have more luck if you start a new post with your question.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.