Broadcom BCM43222 - Slackware 13.37 - Doesn't YET work
Linux - HardwareThis forum is for Hardware issues.
Having trouble installing a piece of hardware? Want to know if that peripheral is compatible with 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.
Broadcom BCM43222 - Slackware 13.37 - Doesn't YET work
Greetings,
First and foremost, I'd, like to say it's an honor to be running
Slackware 13.37 ... (Debian is awesome too, however I know slackware
is LINUX) ... big shout out to antiX M11 486 (best lightweight
distro, I, know)
MY PROBLEM:
I've a Broadcom BCM43222 mini PCI 802.11 g/g/n wireless adapter
installed.
When I do an
I've observed that that the driver(s) associated for this
Broadcom BCM43222 aren't running ... therefore ... my first
request is how can I get to run the driver: wl.ko or even the
b43 driver.
MY CONCLUSION:
I thank you all in advance for your support and look forward
in using this mini PCI wireless adapter, so that I could stop
using the PCMIA and USB options ... which run flawlessly at
802.11n
I'd like to add that I've also downloaded: broadcom-sta.tar.gz from Slackbuilds.org
specifically at:
Code:
http://slackbuilds.org/result/?search=broadcom&sv=13.37
selecting the first option: broadcom-sta
which took me to:
http://slackbuilds.org/repository/13.37/network/broadcom-sta/
(broadcom-sta (5.100.82.112)
I then downloaded: broadcom-sta.tar.gz
After uncompressing: broadcom-sta.tar.gz via execution of the below command:
Code:
tar zvxf broadcom-sta.tar.gz
a directory is created named: broadcom-sta
The contents of broadcom-sta is:
Code:
ls broadcom-sta
README doinst.sh
broadcom-sta.SlackBuild* hybrid-portsrc_x86_32-v5_100_82_112.tar.gz
broadcom-sta.info slack-desc
I then executed: broadcom-sta.SlackBuild with:
./broadcom-sta.SlackBuild
NOTE: broadcom-sta.SlackBuild should be executable: chmod +x broadcom-sta.SlackBuild
---
The result of this is ... a file is created in the tmp directory:
NOTE2: Alternatively you could do a pkgtool (in the tgz file directory)
- Select Current option to Install packages from the current directory
- With the options of: Yes, No, Quit ... select Yes
---
If all went well then the broadcom-sta version:5.100.82.112 for Slackware 13.37 installed successfully.
In my case the broadcom-sta driver installed successfully.
However ... the BCM43222 mini PCI wireless card doesn't get recognized by the OS.
Even with this installation method (Slackbuild) my observation remains the same:
Quote:
Posted on: 05-09-12, 10:29 AM by FreeOS-LuvR
In Thread: Broadcom BCM43222 - Slackware 13.37 - Doesn't YET work
I've observed that that the driver(s) associated for this
Broadcom BCM43222 aren't running ... therefore ... my first
request is how can I get to run the driver: wl.ko or even the
b43 driver.
Greetings Ser Olmy,
I did load the driver.
I also did the lsmod command you gave.
What I'm finding is that upon reboot the drive isn't running.
I really would like to see the wl.ko or b43* drivers running.
I think maybe this could get us closer to seeing the
BCM43222 running on Slackware 13.37
Nothing you do from the command line "survives" a reboot. You need to add the necessary command(s) to a startup script.
Drivers are loaded automatically if either the kernel knows about the driver, or the hotplug subsystem (udev) is configured to autoload a module for a specific device. Since this is a third party driver, it's not part of the kernel proper. It would seem that udev doesn't know about it either.
The easiest way to accomplish what you want, is to simply add the modprobe command to one of the startup scripts. The old rc.netdevice file is more or less ideal for this, since it is run before rc.inet1 (which sets IP addresses on NICs). This file doesn't exist on modern Slackware distributions, but the reference to it in rc.modules still exists. Create it, and it will be executed.
Run these commands as root (cut and paste should work):
I followed your instructions and created the file rc.netservice in /etc/rc.d
Code:
########################################################################
## rc.netdevice
## This file is created to troubleshoot: BCM43222 mini PCI wireless card
########################################################################
#!/bin/bash
/sbin/modprobe wl
I ensured that /etc/rc.d/rc.netservice was executable: chmod u+x rc.netservice
I rebooted.
I did an ifconfig and only saw the loopback interface: lo
I then did an ifconfig -a and got the same result: loopback interface
I then ran lsmod | grep wl which returned:
I guess "rc.netservice" is a typo, as you've used the correct name (rc.netdevice) in the comments in the file. Note that "#!/bin/bash" must be the very first line of a bash script, but in this case it seems to work anyway, as the module clearly gets loaded. rc.netdevice is probably being included in rc.modules as a "dot" source file.
The output from lsmod indicates that the wl module is not being used by anything (the 0 at the end of the line), which explains why your wlan card doesn't show up in the ifconfig -a list. Are you sure this is the correct driver for your card?
Try unloading and reloading the wl module with rmmod wl and modprobe wl respectively, and see what appears in the kernel log (dmesg).
I read in an article that the BCM43222 could work but
the interface doesn't show and the author reported it was
indeed the eth1. The article I'm referring to is: http://all-things-linux.blogspot.com...reless-on.html
I made the below configuration in /etc/rc.d/rc.inet1.conf
Code:
...
# Config information for eth1:
IPADDR[1]=""
NETMASK[1]=""
USE_DHCP[1]="yes"
DHCP_HOSTNAME[1]=""
...
I followed in part the instructions from http://www.broadcom.com/docs/linux_sta/README.txt
in 'Common issues:' section (3: Setup to always load at boot time.)
I executed the following successfully:
Code:
...
# cp wl.ko /lib/modules/`uname -r`/kernel/drivers/net/wireless
# depmod -a
...
Due to the results of working with the wl.ko driver and seeing
that it's loaded once ... I've removed the two firmware files, to fully explore the
possibilities of it working.
Linux Wireless should be useful to find 'Broadcom Corporation Device 04d2' ID for correct driver. Which I thinks will be the 'b43'.
Another point is that a newer kernel (3.2) does provide support for more Broadcom drivers & firmware. You would get the new kernel & firmware file and then compile for your system.
The above linked thread does provide some early 'wl' issues.
You did try the broadcom-sta from slackbuilds and blacklisted the 'b43' as instructed?
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.