for you guys struggling with setting up the wireless oldskool, I suggest using wicd to take care of the wireless stuff. I set up a nice package that takes care of making the changes in rc.inet1.conf and such, so you only need to reboot your computer, and set up your wireless settings in the wicd tray in your selected WM/DE.
http://nawcom.com/files/slack/wicd-1.4.2-i486-3bpn.tgz I know some people were having issues with this using dhclient in slackware, since slackware uses dhcpcd, so i fixed that up. Give it a try ;) And to the parent, the ath5k driver is what you're looking for for that wireless device. [Added note: I have yet to build a 64 bit package, so if anyone wants it done, I will make it happen.] |
nawcom,
Please post your SlackBuild script for that wicd package. Edit: Otherwise, why would we trust you and install your package, without knowing how you built it or having any experience with packages you've built. |
Quote:
|
reasguk ->
first, comment out this part of rc.inet1.conf: Quote:
if this doesn't help, kill the existing wpa_supplicant process, and post the output of #wpa_supplicant - Dwext -iwlan0 -c/etc/wpa_supplicant.conf -dd |
Quote:
|
Quote:
Michelino Chionchio at Slacky EU that he used to start with: Code:
less usr/doc/wicd-1.4.2/wicd.SlackBuild you can see the build tag is 1mch, not 3bpn. |
Everything that I modified is done in the post install script mainly makes a backup of rc.inet1.conf so it doesn't scew up wicd's dhcp work with inet1s, and the patches are already taken care of on networking.py to work with dhcpcd. if you need a SlackBuild you can look here where Workman applied the main fix i pointed out. http://rlworkman.net/pkgs/sources/12...icd.SlackBuild Sorry if I caused any issues which where credit is due.
I'm updating slack-desc to make sure original credit goes to the slacky.eu man Again it is my mistake and apologize. |
For SlackBuilds, I prefer Alien Bob's. Here's his for wicd.
|
Quote:
Quote:
Code:
# wpa_supplicant -Dwext -iwlan0 -c/etc/wpa_supplicant.conf -dd For info, I'm connected on my notepad via the AP it can't find to post this, so the AP is up and running! Does that help at all? resaguk |
Quote:
|
resaguk - is that for the ath5k kernel driver, or the madwifi driver? If you're using -iwlan0, I'll believe you're using the ath5k driver
There's been several notes that -Wext is still having problems with the madwifi driver. Also, it looks like you have "scan ssid=0" set in the wpa_supplicant.conf file. Since scanning is off for that interface, it looks like it's not looking for the beacon of the AP you're trying to connect to. |
Quote:
Quote:
Code:
# wpa_supplicant -Dwext -iwlan0 -c/etc/wpa_supplicant.conf -dd |
I know you're trying a lot, but you're in somewhat of the place I was/am. Two questions, do you have a wired connection on this box (whether you're using it or not doesn't necessarily matter yet)? Have you tried to use wifi on the Linux box while the notepad you mentioned is also connected?
You'll remember I mentioned that I have a WPC100 (Linksys - w/ Atheros 5416). I've built (using Alien Bob's build scripts) the madwifi-current (which has the 5416 support) package and then (re)built and installed the wpa_supplicant package (which has to know about the driver, that's why it's built again). I have similar results to yours (except for the ndiswrapper stuff) when trying to associate and have come up with the following bizarre behavior (which you should try to duplicate, _really_). If I leave the BSSID enabled on my router, I can connect wirelessly if, and only if, I first boot up with a wired connection, then invoke wpa_supplicant (first I try the non-daemonized method, just to see the output (-dd) and know that it will connect). When I see that it will, I exit the routine and daemonize (-Bw) wpa_supplicant. Once it's connected that way I can run dhcpcd on 'ath0' (wlan0 with the madwifi driver attached) and check the result with iwconfig (there's also hardly a timeout waiting for a prompt after invoking the DHCP client daemon). Once I know I have an address, I take 'eth0' down and use the wifi connection. Clunky, I know, but I haven't had time to tweak rc.inet1 so that it won't time out trying to get an IP addy for eth0 when there's no wired connection. Also, when I disable BSSID, I have the added wrinkle of having to have another wifi connection up and running in order for wpa_supplicant to locate the AP. I've read that there are problems with non-broadcast SSIDs, but I'm not about to have my router broadcast to the neighborhood that it's up and running. That's the weirdness I face with wifi, it smells a lot like what you seem to be going through. Since you're still using ndiswrapper, I can't be certain, but you might want to give the above a try. Also, I would strongly urge you to go to Alien Bob's build script site and get the '-current' package build script for madwifi. It has support for the Atheros 5416, and you should then be able to use -Dmadwifi when invoking supplicant. Best of luck, Geoff. |
Quote:
Wifi while connected on notepad? Yes, so far all the times I've been posting here I've had my notepad up and running when I've been trying to get my box to connect. Quote:
Quote:
Iain |
|
All times are GMT -5. The time now is 04:42 AM. |