Linux - Laptop and NetbookHaving a problem installing or configuring Linux on your laptop? Need help running Linux on your netbook? This forum is for you. This forum is for any topics relating to Linux and either traditional laptops or netbooks (such as the Asus EEE PC, Everex CloudBook or MSI Wind).
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.
Ive been using my Dell 600m with Fedora Core 2 for quite some time now without problems. I have an IPW2200bg wireless card, which I was using with the DriverLoader driver wrapper. Just yesterday, my wireless connection stopped working. When I tried to activate it, it gave me the following message:
Determining IP information for eth1...External network device eth1 is not ready. Aborting..
I had at the time been using the driverloader 30 day trial, so I figured it might have expired. So I purchased a license key for $20, and entered it in. It accepted it as a valid key, but now when I try to start my wireless device it still says "Determining IP information for eth1...External network device eth1 is not ready. Aborting..". This leads me to believe that its not a problem with driverloader, but rather with something else.
I am quite stumped as to what the problem may be. My router seems to be working fine, as I can still connect to it via the ethernet ports, and the wireless settings on the administration setup are still the same. Im starting college in a week, and Im going to need to have a wireless connection working by then, so this is sort of important. Hopefully someone here can lend me a hand. If anyone can, I would really appreciate it.
One tack I would take on this is to identify when the change happened (closer than
a day - say within an hour if you can) then try to track down what files
actually changed. You can do this with "find" but the syntax is hard - do a "man find".
If you can identify what files changed at the time it stopped working
it could be a good clue as to what the problem is.
The next thing you can do is track down the code the message comes from
(use combinations of find and grep to find it, its probably a shell somewhere).
Then you need to understand the code where its called from and so on.
I appreciate debugging like this is hard detective work. Hope this helps a little.