SlackwareThis Forum is for the discussion of Slackware Linux.
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.
So I installed a new wifi card, all seemed well, picked up the network great and was connected and surfing. Was going through WICD to change some old settings, and WICD became completely unresponsive, I couldn't do anything, it finally forced the program to close, then X stopped responding and my screen went blank. I let it sit there for a while, and nothing happened, so I hit my power button, my HD activity light started to flash, and for a split second my screen came back, console screen, that was filled with errors that read "MAGIC COOKIE" I restarted, I can login as root, or as any other user, but when I try to start X, all I get is the blank screen again.
Just curious where I should start my journey at resolving this.
I would erase all recently updated wicd configuration files in ~/.wicd, /etc/wicd and /var/lib/wicd/configurations, cross my fingers and startx (I suppose that you are in runlevel 3).
But first you may look for useful information in /var/log/messages, /var/log/syslog and /var/log/Xorg.0.log.
Last resort, erase all files in aforementioned wicd directories then reinstall wicd.
In addition to Didiers advice, you might consider deleting any stale files in the tmp directory eg /tmp/ksocket-<yourusername> and .X11-unix
The reason I say this is that X has failed and will not restart. The Magic cookie errors you saw could be X authentication failures, and a clearout from/tmp may help. I cant understand the connection with wicd, but you have nothing to lose by trying this.
Thanks for the info guys. I was finally able to get back into X, and just out of curiosity I did lspci -k and my wifi card was there, and the driver was in use. I can open wicd, and it lists every wireless network around here, so I try and connect to mine (unsecured by the way) and it locks up tighter than a drum with the message at the bottom of wicd "flushing routing table"
I am running an ubuntu live CD right now, just for the sake of trying to figure out where to go next. I am using wicd 1.7, slackware 13.37, and a linksys wmp600n wifi card.
If this were a wifi driver issue - would it even go as far as being able to list the in-range networks?
Thanks again!
--Paul--
Last edited by Twister512; 12-20-2011 at 09:12 PM.
Reason: found more details
Without an error log it is not possible to see what it is exactly, but the Wicd GUI is a simple Gtk program, it shouldn't normally be able to crash X. I would suspect a driver problem (and yes, it may be triggered only by certain function calls in the driver software, so it may successfully list the networks but hang when trying to connect). On the other hand a driver failure would be expected to segfault either the driver module and dependent software, or the kernel itself. I wouldn't expect an X freeze. Did you check the logs under /var/log?
Thanks for the help guys, I looked at wicd error logs, but nothing that pointed to a direct problem. I removed, and re-installed wicd and now I don't have the crashing problems. Now the problem is this: I can connect to my network, after a random short amount of time, it will disconnect, and then I cannot even locate a wireless network. A reboot will fix this, but only temporarily as it happens again. I shall post the output of my wicd log as soon as I get back home.
So you have two kernel modules loaded but one driver in use - at least that's what it looks like to me, although not sure why this would happen.
I would try blacklisting the rt2800pci module to see if you have better luck with the rt2860sta module (which should load instead) To blacklist a module, simply list in /etc/modprobe.d/blacklist.
Failing that, I would upgrade the kernel if you are comfotable doing it. The driver for my wireless chipset took a giant leap forward with kernel 3.2.0-rc6, i.e it works perfectly now (not related to your hardware, but just wanted to highlight that drivers are improving all the time).
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.