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.
I have just recently installed the BCM4306 wireless via fwcutter and now whenever i try to connect out using my ethernet it will ping places but i cannot oppen them in my firefox or konquerer browser ( i also have a aname server set up so there shouldn't be any problem less the two devices are conflicting).
Also i am still new at connecting with the wireless so if anyone could help me with that it would be much appreciated. Thanks
Personally I have never had any luck getting the native Broadcom driver working. I compile a customer 2.6.17.13 kernel without Broadcom support and use ndiswrapper to support my 4318 card. This has worked perfectly for me.
I would suggest that you download and compile the latest ndiswrapper version, and blacklist the broadcom module or remove it when you compile a new kernel.
Personally I have never had any luck getting the native Broadcom driver working. I compile a customer 2.6.17.13 kernel without Broadcom support and use ndiswrapper to support my 5406 card. This has worked perfectly for me.
I would suggest that you download and compile the latest ndiswrapper version, and blacklist the broadcom module or remove it when you compile a new kernel.
Bob
I'm new to Slackware and getting ready to run into the same scenario. When you say "blacklist the module" does Slackware come with a Broadcom module already loaded? How do I find it...using slackpkg?
This doesn't sound like a driver problem, but rather a DNS or gateway problem. Can you navigate to LQ by IP address (64.179.4.146)? You might want to fill us in on the details of how you are configuring your card and getting an IP address as well.
As far as bcm43xx goes, the 4306 is one of the better supported chipsets. I've got the 4306 and it does work under bcm43xx.
@j0rd4n
As for Slackware containing bcm43xx, that driver was introduced into the 2.6.17 kernel, so if your kernel is later than that, it very well might be there. Check the output of lsmod to see if it is loading. If you want to stop it, just add it to /etc/modprobe.d/blacklist.
As for Slackware containing bcm43xx, that driver was introduced into the 2.6.17 kernel, so if your kernel is later than that, it very well might be there. Check the output of lsmod to see if it is loading. If you want to stop it, just add it to /etc/modprobe.d/blacklist.
If it does include this module in the 2.6.17 kernel, does that mean I don't need to use ndsiwrapper or fwcutter?
If it does include this module in the 2.6.17 kernel, does that mean I don't need to use ndsiwrapper or fwcutter?
If you have bcm43xx, you don't need ndiswrapper but you do need fwcutter. The bcm43xx driver needs firmware in order to function and since no distro ships firmware, you need to created it with fwcutter. However, once you've created the firmware files, you don't need fwcutter again.
If you have bcm43xx, you don't need ndiswrapper but you do need fwcutter. The bcm43xx driver needs firmware in order to function and since no distro ships firmware, you need to created it with fwcutter. However, once you've created the firmware files, you don't need fwcutter again.
Ah, this is starting to make sense. I just found your website that has the tutorial on how to do this. It looks good. I'll walk through it when I get back to my machine. Thank you very much for your help.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.