Quote:
Originally Posted by leopard
I tried to do that. Every time I tried to run my script it wouldn't accept my password because it wasn't the right kind.
In the help file that the .conf file pointed me too, there was only a short snippet about using wpa_passphrase to generate the special kind of password, but it didn't say how I implement it into the script.
|
Which script are you referring to? I'm not sure why you'd need to generate a passphrase, since you should already have one for your network.
Quote:
Originally Posted by leopard
Is this a can-do-with-lots-of-work or is it a straight out cant-do-period?
I can not stand using Windows anymore. Should I just use Ubuntu and wait for a new Slackware with a newer kernel to come out before I try it again?
I have tried to install Debian too, and it had similar problems.
I think these more stable, slow-to-release Linux distros just haven't got the newer kernel I need to run my system.
If this last piece of info is of any use at all, I am for sure that my Ubuntu install used the ath5k driver for wireless and atl1c for Ethernet. Thanks...
|
I don't think there's much of a problem - your wireless works, so it's just a matter of configuring it correctly. If you had to use WPA Supplicant under Ubuntu, is it possible to copy the config file (when you're running the live CD, of course)?
Obviously it's your choice if you'd rather use another distro! The kernel with Slackware, though, should be fine for your hardware.
Again, your wireless seems to work - it just seems to be a configuration issue. About your Ethernet - can you try a "modprobe atl1c" and see if that gives you an eth0 device?
