Ok, I had been using Red Hat, Fedora, and then finally Vector Linux (based on Slack 9). I got wireless to work in all of these...so I know I can get this to work...but like before, a new distro = new problems!

I got fed up of installing this stuff manually when I installed Vector, so I made an install script. This worked great! I modified it for Slack 10, and it almost works

In VL I had a problem with the AP's MAC address not being found...this was solved by using 'dhcpcd' rather than 'dhclient'. Now, that little trick doesn't work.
What I can do is I can setup iwconfig to give me info about wlan0, except no AP MAC...but ifconfig doesn't show it by default. I have to use 'ifconfig wlan0' for it to return any info about wlan0, and then all it says is everything it is supposed to say, but Errors: 3.

I haven't spent much time on this yet, because my house is about 30 degrees celsius...which is more than little Canadian boy like me is capable of handling
So I was just hoping someone had a quick solution.

Thanks

I haven't used Vector, but if you wrote a script for Vector, it should work for Slackware. Maybe you should post it and we can take a look.

Slackware uses dhcpcd to connect to DHCP servers.....Again, post the script and any error messages.

Also post what you do get back from iwconfig and ifconfig.

Oh...Ouch.

I believe my script was used in Slackware 9 by someone, so the problem appears to be unique to my installation of slack 10. There are no error messages...everything works except dhcpcd no longer detects the AP's MAC. I will post any info I feel to be relevant, but for now I'll just put a little more time into it. I'm lazy and don't feel like saving my output to a file, then opening it in Windows...so I if I get really stuck I'll post again with specifics.

Thanks though.

Ok, so, there are no error messages that I can find, but I have found some interesting stuff. If I run dhcpcd the acx_pci module shows that it is not being used (using lsmod). But if I specify an ip address using ifconfig, then the module is used. Also, dhcpcd increases the # if tx errors. I've tried playing with all the settings I know of...so for now I am going to try to reinstall Slackware 10, and see if starting from scratch works. I am still trying to figure out why this only became a problem in Slack...and in Vector (though not quite the same) I'm using kernel 2.4.26, and the acx100 pci driver from the sourceforge project.