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!
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.
I'm running the most recent version of Xubuntu on an older Dll XPS400, Intel Pentium D processor, ath9k chipset NIC.
Here's the problem:
When I boot into Xubuntu from a powered-off state, the wireless will not connect. The system will detect the card and networks in range, but will not connect at all. I've tried various solutions related to the ath9k card (like turning off hardware encryption), to no avail.
Here's the odd part: I also have Windows 7 partition on the same computer. When I boot into Windows and allow it to fully boot (including logging in, etc.), and then RESTART the computer from Windows and boot into Xubuntu, the wireless connects flawlessly!
I can only assume that Windows does something with regard to the wirless NIC that Xubuntu doesn't, and that whatever Windows does holds if the computer is rebooted, but doesn't if the computer is powered off entirely.
Might anyone have any idea about:
1. What Windows is doing that Xubuntu isn't?
2. Why that's not changing during a reboot, but does change during a complete power-off/restart?
3. How to fix things so that wireless will connect in Xubuntu when booting from a powered-off state?
Luckily, I don't tend to reboot all that often, so it's not too terrible a workaround to boot into Windows and then immediately reboot into Xubuntu. On the other hand, that's annoying enough that I'd like to fix the core problem if I can.
Let's try and find out what is actually wrong. Boot up try these commands, and post the results. If there's no output, just say so. I am making the guess that your wifi is wlan0. If it's something else, replace wlan0 with that.
Does your Dell have a switch or key combination to turn your wireless card on and off? I've had problems in the past with laptops that use a key combination to activate/deactivate the wireless card. Often the key combination won't work in linux and if you deactivate in windows wireless won't come up, or not function properly on a restart to linux from windows. You might also want to look at your wireless settings in your bios setup. It looks like your wireless needs a specific signal from windows to properly activate from a cold boot and that once activated the state of the wireless card is saved on a restart to linux. There may be something in the bios setup which is triggering this behavior, either in the wireless settings or the power management.
Thanks everyone for all the advice on this. It did indeed turn out to be a firmware issue: Windows was loading the firmware, which stuck around for a reboot into linux, and of course didn't in a fully powered-off state. Installing the atheros firmware in linux seems to have solved the problem.
I really appreciate all the help and suggestions! Little problems like this can become major annoyances when they persist, so thanks for making that little corner of my life easier.