Slackware installed: XML, file system and internet errors...
Linux - NewbieThis Linux forum is for members that are new to Linux.
Just starting out and have a question?
If it is not in the man pages or the how-to's this is the place!
Notices
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.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
Hmm, I'm not sure. Are you sure that's the correct network? Did you check the MAC address (click "Properties" for the network and then "Information")? Could you also post your config file, /etc/wicd/wireless-settings.conf? Obviously, please remove any keys present in said file.
Hmm, I'm not sure. Are you sure that's the correct network? Did you check the MAC address (click "Properties" for the network and then "Information")? Could you also post your config file, /etc/wicd/wireless-settings.conf? Obviously, please remove any keys present in said file.
I am for sure that it isn't a User error, my connection has 100% signal strength while the others one don't even reach 20%.
I will go and grab that information for you. Will the password be a hash or cleartype?
EDIT: I will also check the MAC. But I think it is right.
Oh, and two things: my networks name is "Access Denied," so don't let that influence your intrepretation of the log file.
The other thing is I just confirmed that using a passphrase instad of a PSK did not change much. The connection still failed; with same error.
Thanks Again for your help; I know this is an odd case.
Last edited by lupusarcanus; 12-23-2009 at 07:15 AM.
The passwords will be in plain text (which I assume you mean by "cleartype").
Yes that is a correct assumption, sorry.
Oh and I edited the post above; please take another glance at it, its important.
All right then, I'll be back in a minute.
The Physical Address (looks like a MAC) that Windows System Tray Icon for WLAN -> Support -> Details is not the same one listed in this file. I don't know, however, if the Physical Address and the MAC are the same thing or not.
What if you change "enctype = wpa" to "enctype = wpa-psk"? You may need to restart wicd for this to take effect, which you can do with "/etc/rc.d/rc.wicd restart".
Other than that, I'm not sure I'm afraid.
As for aircrack-ng, Slackware doesn't have a package for it, but you can get a SlackBuild script for it from www.slackbuilds.org. SlackBuild scripts are used to build Slackware packages.
Edit: also, perhaps report your thread and ask for it to be moved to the Slackware forum - you're likely to get better help if someone in there sees it.
Well, I was thinking of using aircrack-ng to see whether or not the MAC listed in that files is correct or not; but I forget if this wireless card supports monitor mode.
I will be sure to try changing the enctype = wpa to enctype = wpa-psk.
Also, what if I changed it to: enctype = wpa2-psk
Would that help?
Unfortunately, I'm out of ideas . Hopefully when this gets moved to the Slackware forum, someone will have an idea.
Having said that, what I would do is to try and connect without wicd. So, you'll want to stop the wicd service (/etc/rc.d/rc.wicd stop). Then, you'll need to edit the config file for WPA Supplicant, /etc/wpa_supplicant.conf (in there, it tells you where you can find a sample config file to see the options you can use). Once you've done that, do
ifconfig wlan0 up
wpa_supplicant -c/etc/wpa_supplicant.conf -Dwext -iwlan0
If the wpa_supplicant command gives promising output, then do
dhcpcd wlan0
to get an IP address. You'll probably need to run dhcpcd in another terminal, because of wpa_supplicant.
Unfortunately, I'm out of ideas . Hopefully when this gets moved to the Slackware forum, someone will have an idea.
Having said that, what I would do is to try and connect without wicd. So, you'll want to stop the wicd service (/etc/rc.d/rc.wicd stop). Then, you'll need to edit the config file for WPA Supplicant, /etc/wpa_supplicant.conf (in there, it tells you where you can find a sample config file to see the options you can use). Once you've done that, do
ifconfig wlan0 up
wpa_supplicant -c/etc/wpa_supplicant.conf -Dwext -iwlan0
If the wpa_supplicant command gives promising output, then do
dhcpcd wlan0
to get an IP address. You'll probably need to run dhcpcd in another terminal, because of wpa_supplicant.
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.
Last edited by lupusarcanus; 12-23-2009 at 10:09 PM.
I also tried to run dhcpcd wlan0 in a terminal while wicd ran and it hung for a long time (much longer than before) then it connected with O% signal strength, then lost the connection again. (fairly quickly).
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...
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.