Slackware wifi driver installing issues
 

Hi,
I use Slackware 14 x86_64 with MATE as the default graphic manager and slim. For networking, I use networkmanager which works good on wireless. My laptop use the infamous Broadcom B43 card. Obviously, although my wired connection works perfectly, my wireless connection is not recognized.

I then installed the driver broadcom-sta acconding the instructions there: http://www.slackwiki.com/Broadcom_Wireless

The package was installed successfully, but when I rebooted, networkmanager did not detect any wireless connection and iwconfig displayed only I then removed the broadcom-sta package and rebooted but iwconfig still did not detected any wireless extension. I had to delete /etc/modprobe.d/blacklist.conf to see iwconfig detecting wlan0 as before.

Therefore, I am very confused and I wonder what should I do in order to see my wireless functioning...

The Broadcom b43 works OK with slackware. Running one atm. If you have encryption on your network, read
man wpa_passphrase, and set up the /etc/wpa_supplicant.conf correctly.

I have lines 100-204 or thereabouts commented out to stop it trying to set a nickname, which produces an error.

Try to keep all your settings in rc.wireless.conf. To get on by hand, try
copy the mac address of your ap. You'll need to paste it later.
The ssid is yours ssid, and the paste is your mac address the <> come out.. Then

and you should be in. If not, it's your firmware. Check

http://www.linuxwireless.org/en/users/Drivers/b43

Sorry, I did not understand: Should I reinstall the broadcom-sta driver?

This is what appears after iwlist wlan0 scan |less

I didn't use broadcom-sta. I used b43 and b43-fw-cutter. Follow instructions, moved to
http://wireless.kernel.org/en/users/Drivers/b43

One thing to note is to use the correct version of b43-fw-cutter for your wifi.

I've reinstalled broadcom-sta without blacklisting and nothing has changed. I wish to install b43 but I get stuck
I'm confronted to various issues with Slack and I'm struggling to solve them unsuccessfully. Before declaring game over with Slackware, I'll try to get the wifi working.

It doesn't look like you're using the SlackBuild script properly. Perhaps try what's in the SlackBuilds.org FAQ before just running the SlackBuild assuming it'll somehow magically install the driver.

I already read the FAQ. I already read the Howto. I already have installed many Slackbuilds. Therefore, I assume that I basically now how to use the Slackbuilds proprely.
I checked the md5sum of the source as well as the slackbuilds which was correct, and I don't understand the origin of this extremely annoying issue, that's why I posted here for asking some help.

Then in that case a more verbose log would be: `bash -ex b43-firmware.SlackBuild > build.log 2>&1'

Ok, fine, here is the log:

It seems like this package was not installed because of a wrong MD5sum in the info file. You can run md5sum on the b43-firmware package and enter that value in the MD5SUM= parameter in the b43-firmware.info file.

Sorry I don't understand: Since I wanted to create the package of b43-firmware, should I replace the md5sum in b43-firmware.info by the value 490d4e149ecc45eb1a91f06aa75be071 as indicated in the error?

Download the Slackbuild tar.gz package for b43-firmware and unpack it. Download the broadcom-wl-5.10.56.27.3_mipsel.tar.bz2 package and add it to the b43-firmware directory. Run 'md5sum broadcom-wl-5.10.56.27.3_mipsel.tar.bz2' and enter the md5sum value in the b43-firmware.info file. Then run 'sh b43-firmware.SlackBuild' as root and install it with 'installpkg /tmp/b43*t?z'.

The same error reappears. The md5sum displayed by broadcom-wl-5.10.56.27.3_mipsel.tar.bz2 was the same as the md5 in the info file.

I replaced the md5sum again but this time by 490d4e149ecc45eb1a91f06aa75be071 but it fails again with the same error.
This time, I really don't know what to do.

The only thing I did with broadcom-wl was extract the firmware many moons ago. They give the instructions on that page I sent you to.

The b43 module loads the appropriate firmware when it finds the card. This has been talked out many times, so why not do a search of LQ for older threads and do it that way.

Well, I have followed the instructions here: http://wireless.kernel.org/en/users/...entioned_above
However, after , I find out that this issue about md5sum is following me.

You do not need the Broadcom-STA driver for the b43 card you have. I recommend you remove it from your system as all your card requires is the loadable firmware:

Download, build, and install these EXACT packages from SlackBuilds to get your card working:

http://slackbuilds.org/repository/14.../b43-fwcutter/

http://slackbuilds.org/repository/14.../b43-firmware/

I'm guessing you have the 14e4:432c revision judging from the lspci readout you provided.

Secondly, you should not have to edit your scripts just to get the card working and provide the WPA/WPA2 keys for secure wi-fi. I recommend you install NetworkManager or Wicd to manage the network for you. Both come by default with Slackware 14.0, with NetworkManager installed by default on a full installation, and Wicd is located in the /extras directory.

Yes, I have already installed the slackbuild b43-fwcutter but I can't install firmware:
http://www.linuxquestions.org/questi...6/#post4984538
http://www.linuxquestions.org/questi...6/#post4984538
http://www.linuxquestions.org/questi...6/#post4986705

Can't instal;l firmware? That's always a bitch. This instruction
will work only if
1. You have cd'ed to the directory where you have the broadcom package unarchived, & 'ls' shows the broadcom-wl package

2. You have exactly version broadcom-wl-5.100.138. If not, correct it.

3. There is a file wl_apsta.o.

You will know you got it when you see a few filenames come up on the terminal you're working with, as the various firmware files are extracted.

Sorry for the reply delayed.
I've cd'ed to the directory where broadcom-wl-5.100.138 is there (the version is correct) as well as the repertories config and Linux and wl_apsta.o.
However, Gives only
Same disappointing result as root.

I use the broadcom-sta driver myself and if you do use that you need to blacklist the b43 & ssb drivers and then reboot.

broadcom-sta did not worked for me.
http://www.linuxquestions.org/questi...6/#post4983401

@Lenslivan: You're simply not giving enough effort to make these suggestions work, or enough feedback to allow us to suggest anything else. Try these intstructions
The first updates the database, which takes time. 2
2nd finds the file. Then point bw43-fwcutter at the file and try again

the broadcom-sta will work if you blacklist the b43 & ssb drivers in /etc/modprobe.d/blacklist.conf and then re-boot.

If you do not blacklist those driver then it will not work.

My first message was a bit confusing but I blaklisted b43 and ssb and anyway it did not work.

I'm far from being an expert. You have to tell me what should I do, ask to give the output of commands, etc...

The first updates the database, which takes time. 2
2nd finds the file. Then point bw43-fwcutter at the file and try again
The command Updatedb remained silent (no output). wl_apasta.o exists and was found at $HOME/broadcom-wl-5.100.138/linux/wl_apsta.o as expected.
The same error appears.
However, when I "cd" to the directory where wl_apasta.o is located ( $HOME/broadcom-wl-5.100.138/linux/wl_apsta.o ), it respond by the following:

Up.

Re-up.

Seems like you have written the name of the wl_apasta.o file wrongly?

The errors you have are rather weird, b43-fwcutter shouldn't be having problems with extracting the firmware since the checksums for wl_apsta.o are correct. However, it is claiming that the checksums are "unknown".

Have you tried redownloading and reinstalling b43-fwcutter?

Quite possibly the wrong version of the b43-fwcutter is being used. IIRC, newer is not necessarily better. This version works for one thing, that one for another. At least that USED to be the way.

http://wireless.kernel.org/en/users/Drivers/b43