eth1 no longer exists

Asked by Thinboy00

I recently suspended (to RAM) an Ubuntu 8.04 Dell B130 whose only significant hardware alteration was a RAM upgrade (up to ~2.0GiB) long before the suspending or this issue. After waking my computer up the first time, it could ping a friend's wireless router (which it had never previously encountered and whose brand name I did not recognize) but couldn't use it as a gateway to the internet. At the time, eth1 existed and I could ping. After a second suspense and awakening, ifup etc. didn't recognize eth1, and nm-applet etc. were under the brain damaged delusion that everything was fine (every other GUI applet and program couldn't get internet). On my system, eth1==wireless and eth0==wired. Oddly enough, even though eth1 no longer exists, I can still ping my router from the command line via what can only be wireless (there aren't any ethernet cables in the same room as the computer, let alone plugged into it). Since rebooting tends to aggravate problems, I'm wondering what to do about this.

Question information

Language:
English Edit question
Status:
Solved
For:
Ubuntu Edit question
Assignee:
No assignee Edit question
Solved by:
Tony Mugan
Solved:
Last query:
Last reply:
Revision history for this message
Tony Mugan (tmugan) said :
#1

So you only see eth0 now with
sudo ifconfig

Do you see the wireless hardware with
sudo mii-tool
sudo mii-diag

Got latest updates recently?

Revision history for this message
Thinboy00 (thinboy00) said :
#2

I also see lo and a special tap interface I set up for QEMU (I barely understand how it works).

No. What are those programs? sudo mii-diag eth1 says eth1 doesn't exist. I know for a fact that eth1 existed previously.

Somewhat recently.

Revision history for this message
Best Tony Mugan (tmugan) said :
#3

I'd bite the bullet and reboot then.
If nothing has changed recently and the network interfaces are misbehaving then a reboot would be a sensibile approach in case some modules failed to load for some odd reason (hardware failure?).

Make sure you still have the Hardy Desktop LiveCD available in case you need it

http://www.ubuntu.com/getubuntu/download

Revision history for this message
Thinboy00 (thinboy00) said :
#4

Thanks Tony Mugan, that solved my question.

Revision history for this message
Thinboy00 (thinboy00) said :
#5

Note: To get it working perfectly (i.e. I can ping google), I had to alter my configuration with nm-applet etc. and then I also had to sudo ifdown eth1 followed (after output had ceased) by sudo ifup eth1. At that point everything began to work normally.