|
Here's how a connected wifi looks
Quote:
Sorry about errors. The wireless tools (iwconfig, iwlist) both always need wlan0 as the first argument. To see how it's going, just run 'ifconfig wlan0' after the 'dhcpcd wlan0' line - see if wlan0 has an IP. 169.254.x.x is not a working IP, but the default when it fails to get one. you should see this sort of stuff from the dhcpcd command, btw Quote:
|
Well BK, I am now speaking to you from Slackware 14.0 64 with Broadcom 4312. It was a long process. I appreciate all your help and patience.
Here is what finally got me over the hump. I ran your previous suggestions ifconfig wlan0 up iwlist wlan0 scan|less (I think I have my MAC address memorized at this point) iwconfig wlan0 essid "Ace" ap 00:00:00:00:00:00 At this point I ran iwconfig wlan0 and seen that I wasn't associated I ran wpa_supplicant -c/etc/wpa_supplicant.conf -Dwext -iwlan0 && iwconfig essid "Ace" ap 00:00:00:00:00:00 as usual it just dropped to the next line and hung up. Then I went and pulled up the wpa_supplicant.conf file and noticed it didn't have any information in it. Including my passphase. So I surfed around and learn what needed to be in the file. I updated the file by hand and reran all the previous commands. The wpa_supplicant command associated and connected. It still hung up (I may have had something entered wrong still. I'll clean it up later) then I ran iwconfig wlan0 and seen I was associated. Lastly I ran dhcpcd wlan0 and here I am. For the moment I'm going to start populating my computer with all my files and programs. In time I'll clean up a few quirky items and then I'll dive in to what is exactly happening with the wpa_supplicant.conf file and fully understanding the process so I'll be able to duplicate next time on my own. Again, Thanks for all your help. Scottie has nothing on you (nod to Ireland) Ace |
Great that you're going. Here's my /etc/wpa_supplicant.conf
Quote:
You should be able to configure rc.wireless.conf and maybe touch up section [4] in rc.inet1.conf which will override any settings in wireless.conf. |
I am only having one issue. I lose connection pretty quickly and I have to log off and restart. My signal shows being 62/70. However when I do the wpa_supplicant command, it associates and connects but hangs after CONTROL EVENT blah blah blah. I have to Ctrl-Z to get to move on. It does t stop me from getting on but could be contributing to the dropping out. Meanwhile is there a way to add all the set up commands to a boot up script. So I don't have to type every time . Also what happens if I take the laptop some where else? Do I have to type the Essid for those networks too? Just asking.
Thanks Ace |
That wpa_supplicant.conf works on my place, and unprotecrted networks. The section between the { & } is the output of 'man wpa_passphrase. IIRC, B43 doesn't do WEP, but does all forms of wpa.
To go live at boot: The config files I offered were here https://skydrive.live.com/#cid=99361...4096FF2C07!208 The rc.wireless.conf & rc.inet1.conf work in my place, the local College, and a few hotels at least. There is often an issue with resolv.conf if they use their own dns (and disallow yours) but you can sort that on a place by place basis. If the dns doesn't come up right, find out what it should be, set DHCP_KEEPRESOLV="yes" and try again. On the dropouts, I've no idea. 62/70 is fine. What issues the CONTROL_EVENT? |
Business Kid,
Well I finally got everything to work correctly. Your help was greatly appreciated. At the point I was at previously, I couldn't stay on line but for 2-3 mins before I was dropped and had to do everything over to get it back up and running. So I tried uninstalling the fwcutter and b43 and installed broadcom_sta. Still no luck. At that point I decided I was going back to 13.37_64. This ended up being a good thing. To bore you with a long story, I installed 13.37_64. I down loaded fwcutter and b43 firmware. Didn;t have any luck so I looked around and found some slack builds with older version levels for 13.37_64. I then installed Wicd 1.6.X.X I think, from my previous installation. It let me stay on line and it logged on to a local unsecured network. However when I went to enter my pass key, it wouldn't leave the set up screen. It acted like it was waiting on me to hit Ok. To cut to the chase, I realized my mistake. I had Wicd for 32 bit. I guess it worked previously before I started installing 14.0_64, because I had the multilibs installed for 32bit. Sure enough, once I got 1.7.2.1 _64 I was on strong. Energized with new determination, I reinstalled 14.0_64. Installed fwcutter 014 and b43-firmware-5.10.56.27.3. I installed Wicd 1.7.2.4_64 (Slack Build) and I've been running strong ever since. Also as a side note, I noticed 13.37 wpa_supplicant.conf had my ESSID and passkey and also a generic "ALL" type set up as well. Upon installing 14.0_64 the wpa_supplicant.conf only had two lines, like last time. Don't remember specifically but was something about controlXXXXXXX. So I replaced it with the one from my 13.37_64 installation. Not sure if it amounted to anything given I copied it first before installing wicd. But just as an FYI. I hope my adventure and conclusion helped someone running 14.0_64. Now that the wireless thing is over, I really am liking the upgrade to 14.0. Again, thanks for all you help. Ace |
Thanks, Ace. I spent a Month here in the beginning installing distros & trying to get online, and another few days when I went encrypted. But once you master it, you're made up. And it's so much more intellectually satisfying than something like gnome's NetworkManager.
|
| All times are GMT -5. The time now is 12:04 PM. |