[SOLVED] Installing wifi drivers for Broadcom card on Netbook, Slackware 14.2
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.
Installing wifi drivers for Broadcom card on Netbook, Slackware 14.2
Hi all,
In my continuing quest to get Slack working I attempted to get it up and running on my Samsung N110 netbook. The install was fine but wifi didn't work. I went back to Debian and the wifi worked fine.
Now as I understand it, this is because the Broadcom drivers are included with Debian. I went to Slackdocs to read up on wifi and it seems rather complicated to me as a Slack newbie. However, I came across this which looks quite straightforward for my Broadcom 4313 card:
If indeed I can build the package from Slackbuilds, I suppose I could just use a USB drive to transfer the package over rather than having to use a wired connection [the USB method will be easier for me].
After a reboot, it should work, as far as I can tell. The only reason I am posting this, in what seems a potentially straightforward setup, is that making a Slackbuilds package looks easier than following the guide to getting wifi working that I found on Slackdocs [this guide here - https://docs.slackware.com/slackbook:wifi].
Am on the right path here or am I missing anything?
Last edited by Lysander666; 01-03-2018 at 04:26 AM.
You could (after installing b43-fwcutter & b43-firmware from SBo) use the tried and true manual configuring, or you can install wicd and connect to your WiFi, or even easier (easiest I think) is to just # chmod +x /etc/rc.d/rc.networkmanager and use NetworkManager that should already be in your system tray.
I hope this is what you're looking for.
#Edit
Oops, I meant after installing broadcom-sta if that is what you need, not b43's.
You could (after installing b43-fwcutter & b43-firmware from SBo) use the tried and true manual configuring, or you can install wicd and connect to your WiFi, or even easier (easiest I think) is to just # chmod +x /etc/rc.d/rc.networkmanager and use NetworkManager that should already be in your system tray.
I hope this is what you're looking for.
#Edit
Oops, I meant after installing broadcom-sta if that is what you need, not b43's.
The chmod sounds the easiest, thank you for that. I take it that since wicd is in the ISO chmod is all I need to do.
The chmod sounds the easiest, thank you for that. I take it that since wicd is in the ISO chmod is all I need to do.
While wicd is included on the ISO, it is not installed by default. It is in the extra/ directory which users are able to install once they've booted into Slackware.
By default, Slackware uses Network Manager for wireless connections, but provides wicd as an installable alternate.
Thanks for the help bass, in this instance the fault was my own. I was always selecting DHCP at #netconfig, when I should have selected Network Manager. On a reboot, Slack was able to connect to 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.