Linux - Wireless NetworkingThis forum is for the discussion of wireless networking in 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.
I'm running the new Slackware 14.0 64 on an HPdv2945. I have installed the SlackBuild fwcutter and B43. I now can pull up WICD and see my network along with others in the neighborhood. I just can't connect to them.
I run iwlist scan and it shows wlan0 having a lot of network choices but won't connect. My network is WPA secured so I thought I might be typing the password incorrectly but there is also a neighbor network unsecured and it won't connect either. My network does the authorization thing but fails to get an IP.
The best kept secret there is wpa_passphrase. You need a chunk of the output from that in /etc/wpa_supplicant.conf. Then run 'iwlist wlan0 scan |less' and copy your wireless point's ap.
Finally this command
Thanks, I had a little problem. I wasn't really sure what Your_essid ap meant. Assuming Your_essid ap meant my network name but was still unclear about where to put it in the command above. Is it...
1) wpa_supplicant -c/etc/wpa_supplicant.conf -Dwext -iwlan0 && iwconfig wlan0 essid "Ace"
2) wpa_supplicant -c/etc/wpa_supplicant.conf -Dwext -iwlan0 && iwconfig wlan0 essid Your_essid ap "Ace"
3) wpa_supplicant -c/etc/wpa_supplicant.conf -Dwext -iwlan0 && iwconfig wlan0 essid Your_essid ap your_ap "Ace"
I typed in the wpa_supplicant -c/etc/wpa_supplicant.conf -Dwext -iwlan0 && iwconfig wlan0 essid "Ace" and the command started and never finished. I had to Ctrl-C to close. Then it held the file open.
Thanks Business Kid. I didn't have any luck but I appreciate the attempt.
Ok here is all I've done.
1) Installed fwcutter and B43 firmware that I used on Slackware 13.37 64. Didn't work. I could see various networks but couldn't get connected.
2) ran the command above as business kid recommended. I got a lot of "Use and Option" type replies. Like you get with you type a command without a parameter. Still no luck
3) Downloaded Broadcom_sta for Slack 14. Didn't have any luck. Couldn't even see the networks any more. (I did clean out the B43)
4) Cleaned B_sta and installed a newer Slack Build of Fwcutter and B43 firmware from a Slack 14 library site. I could see networks in wicd again but couldn't connect. I even made it past the authorization stage just wouldn't try to get an IP.
5) I ran iwconfig wlan0 essid "Ace" and then dhcpcd wlan0. no errors, it just didn't change anything.
6) Oddly enough, I also clicked around on wpa_supplicant gui. It seen my network and said it got a good IP. I was able to bring up the Google page in sea monkey and then I was dropped. The whole time wicd still didn't see me being connected nor would let me connect. After that the wpa gui wouldn't see my network.
So I've been looking around and while I'm FAR from a kernel expert it appears that B43 802.11 b/g WLAN just isn't really supported with the new Slackware 14. Is this true? If so I can quit trying to fit a square peg in a round hole and go back to 13.37 64
Meanwhile until I hear back from someone that knows more than me, I'm going to run through the process again, just to see if I've over looked something.
B43 is supported, or I wouldn't be getting through.
With b43-fwcutter, you need an exact varsion for your hardware and an command which should show piles of firmware being spat through to /lib/firmware. You should have stuff like this in /var/log/messages
bash-4.2$ grep -i b43 /var/log/messages
Oct 20 13:07:00 harriet kernel: b43-pci-bridge 0000:30:00.0: PCI INT A disabled
Oct 20 13:07:00 harriet kernel: b43-pci-bridge 0000:30:00.0: PCI INT A -> GSI 18 (level, low) -> IRQ 18
Oct 20 13:07:00 harriet kernel: b43-phy0: Loading firmware version 478.104 (2008-07-01 00:50:23)
Oct 20 13:59:23 harriet kernel: b43-pci-bridge 0000:30:00.0: PCI INT A disabled
Oct 20 13:59:23 harriet kernel: b43-pci-bridge 0000:30:00.0: PCI INT A -> GSI 18 (level, low) -> IRQ 18
Oct 20 13:59:23 harriet kernel: b43-phy0: Loading firmware version 478.104 (2008-07-01 00:50:23)
There is actually a later version of the driver.
You find the exact version you need at http://www.linuxwireless.org/en/users/Drivers/b43 and how to use it. This page is the gospel on b43. I think I compiled from source. Beware that the broadcom sta driver blacklists b43, so hack modprobe.d/blacklist and remove b43. If your b43 appears on usb, you also need b43-pci-bridge, a driver hidden ssb.ko (Sonics Silicon Backplane).
Well I still not getting any network connections. With the latest configuration, I'm not even getting wicd to see the networks. Below is what I've done. May be you can see what I've missed.
1)grep -i b43 /var/log/messages gave me -- lsp/var/log/messages:Oct 20 11:05:28 darkstar kernel: [ 11.110808] b43-phy0: Broadcom 4312 WLAN found (core revision 15)
2) lspci -vnn -d 14e4: gave me -- Network controller : Broadcom Corporation BCM4312 802.11b/g LP-PHY [14e4:4315] (rev 01)
3) The website you gave me shows 4315 was highly supported.
4) There wasn't a Slackware section, so I used "Other 3.2+" Fwcutter and firmware.
5) Installed fwcutter b43-fwcutter-015.tar.bz2
5) Installed b43-firmware/broadcom-wl-5.100.138.tar.bz2
6) Rebooted several times, no luck.
7) I ran iwconfig wlan0 essid "Ace" and dhcpcd wlan0. I got the light on the laptop to change to blue showing a connection of some sort but it didn't change my situation.
8) I ran iwlist scan and wlan0 sees all the local networks in the neighborhood but wpa_supplicant_gui and wicd does not.
9) Checked modprobe.d/blacklist and seen where bc43xx was blacklisted. I both left it and then commented it out. No luck. There wasn't anything for B43 or ssb etc. There actually wasn't a single blacklist file, the blacklist files seem to be for each item. IE not blacklist.conf but rather bc43xx_blacklist.conf (paraphrase name) and nivdia_XXXXXX.blacklist.conf
So thats where I'm at. All of this was done on top of a brand new installation of Slackware 14 64. You stated you were getting on with Slackware 14_64 did you use the same fwcutter / firmware file as I? Did you use the section under "Other" or did you go with a different distro? Lastly, instead of using 3.2+ kernal section or should i have went with 2.X+?
1. The firmware, in a b43/ directory from /lib/firmware
2. rc.wireless.conf which is untouched. My much hacked one was swapped out during the install
3. rc.inet1.conf which has a few tweaks in the  section. You may want to comment out
Grab those in the next day or two, and try them. The rc. files go in /etc/rc.d. I have the 4312 and it works on those. You did doctor up wpa_supplicant.conf with the output of wpa_passphrase??
Hey Business Kid, I appreciate all the effort. I wasn't able to get a connection. The boot up hangs at a certain point and tries to get a carrier. It gets an 8 sec time out and continues with the boot up. Also Wicd doesn't see any networks once I'm in KDE.
I think this week I'll go back to 13.37 64. The setup was alot easier as I remember and I've been without my computer for over a week. Plus I'm worried that if 14.0 takes dating various files and running numerous commands from the prompt just to get on my network, then when I take the laptop anywhere away from the house, I'm going to have to go through updating various files for the new network. I didn't have that with the 13.37 64. Once I set up the card, I could log on to about any network by just clicking connect.
Again I do appreicate all the trouble you went through. I'll just wait until I have more time and knowledge to try 14.0 again. Right now I'm updating files because different web-sites are telling me exactly what to type and where. As a result, I don't fully understand what is going on so I don't know what is missing or correct order to do various commands.
I never used wicd. I set up the psk with wpa_passphrase, and then the rc scripts did it and wicd or nothing else is needed. The wifi for 13.37 is the same as the wifi for 14.0. The program versions may have been bumped up but the scripts are the same.
Get specific, Ace, or you'll never get connected. Do it by hand. Get stuck. Tell us exactly where you are stuck. No need to upgrade, downgrade, or change distros. Then when we ask you to try something, try it and be precise as to the error messages. All we can go on is your description of the problem and error behaviour.
You're not telling us error behaviour.
With that 8 sec delay, you're not associating. Post the last few lines of
grep b43-phy0 /var/log/messages
Ok. You convinced me. I'm going put in a fresh copy of 14.0. Then I will run lspci then lsmod and drop it in here so you can see what we get right out of the gate. Then I'll read up on wpa passphase and psk then go where it leads.. I'll keep you posted .
Make sure you haven't got 'fast ethernet switching' or anything like it enabled in the kernel. What that does is switch off the wifi if you configure the lan, or vice-versa.
The connect sequence is
ifconfig wlan0 up
iwlist wlan0 scan |less #copy your AP mac address
iwconfig essid "Ace" ap <paste your AP mac address> #This associates you, and wpa_supplicant should be automatic
iwconfig wlan0 # Check you are associated
Each stage has to succeed before the next will work
In the cloistered days of old, an English monarch and his virgin wife got married without sufficient knowledge of each other to do what comes naturally, and people only gathered that when there was no offspring for some years :-/. You're in a similar position - you have it perfect, you just need to set it up. Stop fixing it, and try the above sequence. Losing the carrier can be a signal strength problem. What's the quality for your ap in iwlist?
If you can't associate, try
wpa_supplicant -c/etc/wpa_supplicant.conf -Dwext -iwlan0 && iwconfig essid "Ace" ap <paste your AP mac address>
That may grab a terminal, and run 'dhcpcd wlan0' from another if it does.
ifconfig wlan0 up Ran fine, no errors and back to the prompt.
iwlist wlan0 scan |less #copy your AP mac address Ran fine, copied MAC address
iwconfig essid "Ace" ap <paste your AP mac address> #This associates you, and wpa_supplicant should be automatic Gave me “Ace unknown command” error. I had to type iwconfig wlan0 essid "Ace" ap 00:00:00:00:00 then it ran fine and dropped to prompt again.
iwconfig wlan0 # Check you are associated Ran Fine No errors, though it just dropped to the prompt. It didn't say anything about being associated or not
dhcpcd wlan0 Ran Fine no errors
Over all went well but no connection. I did get the blue activation light on the computer however.
wpa_supplicant -c/etc/wpa_supplicant.conf -Dwext -iwlan0 && iwconfig essid "Ace" ap 00:00:00:00:00 This didn’t give an error but it doesn’t go back to the prompt. It drops to a blank line and sits. I left it for 15 mins. Finally I had to Ctrl-Z to stop the process. I reran but I get and open file error. Went to var/wpa_supplicant (I believe) and had to delete wlan0 file . I reran again, and got the same result as the first attempt. A hang up.
I don’t have wicd installed so I don’t not if the networks are seen or not. I do know that iwlist sees all the networks close to my house including mine.
Any suggestions? I’m not trying to throw in your lap. I just don’t know where to go from here. You’ve covered what I knew to do a long while back.
Also, I’ve never worked with the kernel. I can’t say if I have fast switching activated or not. I’ll research it when I get home.
Last edited by Ace Blackwell; 10-25-2012 at 10:23 AM.