FedoraThis forum is for the discussion of the Fedora Project.
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.
Introduction to Linux - A Hands on Guide
This guide was created as an overview of the Linux Operating System, geared toward new users as an exploration tour and getting started guide, with exercises at the end of each chapter.
For more advanced trainees it can be a desktop reference, and a collection of the base knowledge needed to proceed with system and network administration. This book contains many real life examples derived from the author's experience as a Linux system and network administrator, trainer and consultant. They hope these examples will help you to get a better understanding of the Linux system and that you feel encouraged to try out things on your own.
Click Here to receive this Complete Guide absolutely free.
It looks like it's starting, but not connecting. Have you reached the point of configuring a wireless network and passkey? If not, it could be waiting for a connection to be configured. Have you tried starting the wicd GUI with the command "wicd-client" (you may need to do this as root; if it works, put it in your startup applications).
Let us know what happens. It can help additional troubleshooting.
I guess I will have to go back to NetworkManager, because wicd just won't do it , I get to the point to see AP's available and Properties to set key and IP's and when I click on OK and it does nothing. Nothing is happening.
I prefer wicd, but I did have one Ubuntu system on which wicd stopped working after an upgrade and I had to fall back to network manager. I never figured out why wicd stopped, but, frankly, I didn't try very hard. I found that network manager had improved significantly in the interim.
I've found wicd is EXTREMELY sensative if you have any other network management software installed. So if network-manager is installed still, even if it's not actively configured to manage an interface, I've found wicd will fail.
Also, after setting passkey in wicd, you have to actively tell it to connect again (irritating little thing). If you chose "connect automatically" it will in FUTURE boots connect automatically, but for that one time, will not connect until actively told to again.