ifconfig shows only lo (after Hardy -> Jaunty + KDE 3.5 upgrade)
Linux - NetworkingThis forum is for any issue related to networks or networking.
Routing, network cards, OSI, etc. Anything is fair game.
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.
ifconfig shows only lo (after Hardy -> Jaunty + KDE 3.5 upgrade)
As a result of mishaps (failed dependencies and such) during an upgrade, I am now in a situation where ifconfig shows only lo. No eth0, no wlan0 (on a laptop running wireless). I've installed wicd (not easy when you don't have a net connection) but when I start it, it gives a "failed" message.
Before the upgrade, my wireless was working fine. It still works fine in my Windows partition.
I could go through the history of how I got here, but it probably isn't very relevant to solving the problem I now have. I assume I need to reconstruct some network-related files in /etc -- but which ones? And what should I put in them?
Once I've gotten eth0 and wlan0 back, I assume my next step should be to try wicd again.
and try to find it, and select it as a module (type "m" when selected), you can also press "?" to get info on the selected thing, the look for something like this: "if you compile this as a module, choose M here, the module will be called <name of the module>"
then pres escape until you get out and remeber to save the config
then execute:
Code:
make modules && make modules_install && modprobe <name of the module>
If it came up then you probably have a good driver.
which command brought it up?
What was the IP address and default gateway after it came up?
can you bring it back up and then do
Code:
$ ifconfig eth0
and post the results back here in your thread?
Also if you can see the IP and the default gateway try to ping them to see if you have any connectivity and post short versions of those ping tests here
I got the wired connection back by inserting an entry for eth0 in /etc/network/interfaces. However, I've had no such luck with the wireless connection. I inserted an entry for ath0 in that same table and even added ath0_pci to the list of modules in /etc/modules, but still can't get the connection working. I'm about ready to save my home directory, ditch the existing installation, and install the KDE 3.5 version of Jaunty from the beginning.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.