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.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
You need the broadcom-sta slackbuild for it to work,just grab it of slackbuilds.org or sbopkg install it with pkgtool reboot and it should work.
i have it too its not easy to compile from source on slack (my opinion) but broadcom has it availiable for download .
b43,ssb,ndiswrapper dont work for 4312 on slack or too my knowledge on any dist,there are different types of cards with the same number 4312 and i have the one with integrated bluetooth and is running slack 13 32bit but i know they are alot of treads here on the subject and onebuck had one for 64bit.
just wrote this answer in general for i know that ther is a lot of new slackware users (like my self) having trouble to get this card too work.
It works, but very inconsistently. It hasn't worked on reboot once yet, and when it does work it seems to do so randomly. I can't find a pattern that makes it work each time.
I reboot, polling for DHCP times out and iwconfig is missing my essid and key & the access point is not associated.
I try setting the essid, no change in iwconfig. Same when I try setting the key. I try again, and again randomly, then it will suddenly work for no apparent reason. Oddly though, my key never shows up (always says "off"). On all my other computers, the key is displayed in iwconfig.
I'm really at a loss here, and I really hope this isn't indicative of what I can expect from this laptop
and I have had it working flawlessly for quite some time (Slackware 12 and 13) with the b43 firmware + fwcutter packages from Slackbuilds.org and wicd as network manager.
and I have had it working flawlessly for quite some time (Slackware 12 and 13) with the b43 firmware + fwcutter packages from Slackbuilds.org and wicd as network manager.
All the best,
Andrew
There are two different chipsets that both appear as BCM4312. You have to look at the pci id.
The 14e4:4312 is supported by the b43 driver and firmware.
The 14e4:4315 is not until 2.6.32, and need the wl driver.
Thanks, I added the above to my blacklist.conf. We'll see what happens next time I reboot.
I will say though that I checked lsmod immediately after boot and neither of those modules were listed.
[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..]
I have the same chipset in my Dell Mini 9. So far I've always used the broadcom wl driver and never had trouble. That's under Arch, so it's been a variety of driver releases and kernel releases that worked under. Current kernel is 2.6.32.9, so maybe I'll give the b43 a try and see how it's doing.
Just did. So far, the b43 is working fine and dandy. Obviously, it's only been a few minutes, so maybe something will crop up with heavier use. But there's no indication of trouble lurking.
Oh, I noticed that before, I had specified both the lib80211 and wl modules to load. When you're having trouble, have you seen if lib80211 was loading as well? And maybe do a depmod -a for good measure.
Just did. So far, the b43 is working fine and dandy. Obviously, it's only been a few minutes, so maybe something will crop up with heavier use. But there's no indication of trouble lurking.
Exellent If you start to have trouble, a report would be appreciated.
Maybe I'll try upgrading my kernel sometime soon.
Quote:
Oh, I noticed that before, I had specified both the lib80211 and wl modules to load. When you're having trouble, have you seen if lib80211 was loading as well? And maybe do a depmod -a for good measure.
Yes, the lib80211 module seems to load on boot, with the wl. This command was issued immediately after booting (with non-functioning wireless):
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.