SlackwareThis Forum is for the discussion of Slackware Linux.
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.
Introduction to Linux - A Hands on Guide
This guide was created as an overview of the Linux Operating System, geared toward new users as an exploration tour and getting started guide, with exercises at the end of each chapter.
For more advanced trainees it can be a desktop reference, and a collection of the base knowledge needed to proceed with system and network administration. This book contains many real life examples derived from the author's experience as a Linux system and network administrator, trainer and consultant. They hope these examples will help you to get a better understanding of the Linux system and that you feel encouraged to try out things on your own.
Click Here to receive this Complete Guide absolutely free.
There is no such network controller as the BCM543225, though there is a BCM43225, is that the actual output you posted or did you accidentally insert that "5" when posting?
Please provide the verbose output:
If it does turn out to be a BCM43225, that uses the brcm80211 module which is included in kernel 2.6.37 - which is 13.37's kernel. If it's not loaded then it may be due to the lack of firmware - not sure where the broadcom firmware is in slackware, possibly in the "kernel-firmware" package or perhaps in a separate package?
All the Broadcom cards I've installed under Slackware needed firmware. Firmware goes in Slackware under /lib/firmware. As far as I'm aware - there is no official firmware package for Broadcom cards for Slackware. Officially, it is recommended to use fwcutter and make your own firmware from the corresponding Windows driver for your card. Unofficially ( ) I have always found firmware already cut for me on one website or another. Make sure you do something like:
# dmesg | grep Broadcom
or similar in order to find out exactly what name the firmware file should have. Normally the kernel will complain during the boot that a certain firmware file is missing - and this is how you will know what name to give to the firmware file, once you get it.
Firmware doesn't work on all the Broadcom chipsets. FWCutter will strip firmware from various prebuilt Linux drivers modules but the process doesn't work for all cards because matching the firmware and chipset without knowing which firmware package to download is hit or miss with any chipsets in the 43xx series, and even then firmware still doesn't always work.
The STA driver is Broadcom's official driver. Just about all 43xx series or later cards will work with the STA driver provided you have the right kernel for it.
The BCM543225 is a very new chipset (802.11-N). You may be required to rebuild your kernel before building the module to gain proper support. I "think" kernel 126.96.36.199 or 188.8.131.52 should be adequate but you may be required to use kernel 3.0.7 in conjunction with the proprietary STA driver.
...b43-fwcutter tool [...] will extract firmware from the Windows driver...
Firmware will work if you either download the correct file and name it with the name expected by the kernel, or manually extract it from the correct version of the Windows driver for the chipset you have using fwcutter.
Again, according to http://linuxwireless.org/en/users/Drivers , the currently supported Broadcom wifi modules are b43, b43legacy, brcmsmac, brcmfmac. The detail pages state that all the four modules require firmware files. It might seem like sometime firmware is not needed, because on other distributions firmware is already included in the appropriate folder, so the user needs to do nothing.
I've never read that... oddly because I've read it like this:
This firmware is copyrighted by Broadcom and must be extracted from Broadcom's proprietary drivers.
The only driver or utility that I've known to require a Windows driver has always been ndiswrapper. I've always assumed the "driver packs" that have been downloadable from the websites for extracting firmware are precompiled portions of the Linux proprietary drivers like prebuilt object files using GCC and such.
Currently b43-fwcutter supports Apple MacOS X, Microsoft Windows 98/ME/2000/XP and Linux drivers, but keep in mind that b43-fwcutter doesn't support all driver versions.
One learns something new everyday
I believe the whole point of firmware is to have binary blobs which other people can't inspect - in order to protect some of the internal spec of various chips from being revealed to the world. They tend to be proprietary (i.e. - the open source developers wouldn't have access to the source) - and delivered ready compiled by the manufacturer (or extracted in compiled/binary form from some of their other drivers) - thus probably nobody really knows what tools are used to make them in the first place.