Linux - NewbieThis Linux forum is for members that are new to Linux.
Just starting out and have a question?
If it is not in the man pages or the how-to's this is the place!
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 downloaded the drivers from Broadcom's website (http://www.broadcom.com/support/802.11/linux_sta.php). I have a 64-bit processor and dowloaded the 64-bit tar. I think I installed it incorrectly because whenever I connect to the internet via wifi my computer freezes and has to be powered down. Should I untar it from the terminal? I mean I really have no idea. It could be something completely different. The only other thing I can think of is that I'm using Fedora 16 and there is some incompatibility in the driver, but I don't see why that would be an issue.
Can you provide some more information? What exactly did you do, I mean how did you install the driver? Where there any errors when executing those commands? If so, what were the errors? What's the output of:
How did I install the driver? Well I'm not really sure. I downloaded the tar and extracted the files to the desktop. The website says "NOTE: You must read the LICENSE.TXT file in the lib directory [the tar contains lib & src directories, and a makefile] before using this software." So I opened the file, but my computer said it was an executable. I executed it anyways, and when I went to look at my 'Network Connections', I could use the wireless tab. So I tried connecting to my home network, and it froze twice.
I attached a screenshot of the results. (Yes, I know I shouldn't always be working in the root)
Did you follow the README.TXT file on the Broadcom website? I feel like you might have installed your driver a different way. Ive followed it that way and it works everytime.
yeah so initially what I did was to just doubleclick on the makefile. I guess it *technically* installed b/c it got the network manager to recognize the BCM4313. So I just went back, read the readme, and tried following directions. I attached two screenshots to show what codes I have run on the command line. After the first screenshot, I installed kernel-devel. My problem currently is when I try to make the makefile, it tells me a directory doesn't exist.
Do you have the header files for the your kernel installed? If I'm not mistaking it's called kernel-headers in Fedora. Looks like it's looking for the header files and cannot find them.
Distribution: fedora (redhat, slackware, suse in the past)
Posts: 2
Rep:
I got to the same place--it wouldn't compile. Not necessarily the same reason, but the same effect. (By the way, this is on an HP g6 and fedora 17).
So after I tried using the hybrid driver from broadcom, I tried using the built in driver (brcmsmac). Both failed. (Actually brcmsmac worked, but poorly and not with all routers.)
I ended up getting these rpms online (since I couldn't use yum), and going oldschool with 'rpm -ivh <all-three-files>'. Of course you need the fc16 versions, and maybe 32 bit....
> broadcom-wl-5.100.82.112-2.fc17.1.noarch.rpm
> kmod-wl-3.3.4-5.fc17.x86_64-5.100.82.112-2.fc17.11.x86_64.rpm
> kmod-wl-5.100.82.112-2.fc17.11.x86_64.rpm
I also had to add these lines to /etc/modprobe.d/blacklist.conf
blacklist b43
blacklist brcmsmac
Once I got that straight, I get a strong signal and fast connection.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.