Upgrade to Ubuntu 9.04: no ethernet.

Asked by Wayne Miller

I was using Ubuntu 6.XX on an older machine with a Celeron processor and integrated ethernet on MB. This older version installed properly and came up working. Recently, after successfully installing Ubuntu 9.04, I get no internet connection. The traffic indicator on the ethernet switch indicates that the ethernet port is not active. How do I repair the broken connection?

Question information

Language:
English Edit question
Status:
Solved
For:
Ubuntu gnome-nettool Edit question
Assignee:
No assignee Edit question
Solved by:
zvacet
Solved:
Last query:
Last reply:
Revision history for this message
marcobra (Marco Braida) (marcobra) said :
#1

1) Please switch off the router and the pc IMPORTANT → unplugging them from the net.
2) Please plug out and plug in again all your network cable connections
3) Switch your router on
4) Switch your pc on
5) Please force a renew of your dynamic ip by opening a terminal and typing

Please open a Terminal from the menu Applications → Accessories → Terminal and type or copy and paste:

sudo dhclient

give your user password when requested, you don't see nothing when you type it, then press enter

If this doesn't solve...

Please open a terminal and please type this commands:

lspci | grep -i eth

and

ifconfig | grep -i inet

Please copy and paste a bit of result here...

Revision history for this message
Wayne Miller (wlm) said :
#2

Since I can't get access to the internet on the problem machine, I can't copy and paste, but here is a bit of what I'm seeing:

After sudo dhclient command:
Software notice for DHCP
Series of HHCPDISCOVER lines
No DHCPOFFERS made
No working leases in persistant database - sleeping

After lspci | grep -i inet: no response

After ifconfig | grep -i inet:
inet addr:127.0.0.1 mask: 255.0.0.0
inet6 addr: ::1/128 scope: host
inet6 addr (lots of stuff, I suspect a wireless response)
inet addr (more stuff...)

After doing this, when I try to launch foxfire, instead of getting "unable to find site", I get an "offline" message.

Revision history for this message
Wayne Miller (wlm) said :
#3

More information: using gnome-nettool, I get a response of 127.0.0.1. When I ping with that address, I get responses on the nettool screen (1.5ms,typ), but the terminal screen shows S WIDGET (widget)' failed for each ping.

Revision history for this message
marcobra (Marco Braida) (marcobra) said :
#4

Seems your internal integrated ethernet card is not recognized...

We need some info about that internal card to help you

Do you have some 6.XX install cd to boot from and to read the

lspci | grep -i inet

answer terminal command ?

Thank you

Revision history for this message
marcobra (Marco Braida) (marcobra) said :
#5

Also be sure the pc we are talking of have the minimum requested to run Ubuntu 9.04

http://www.ubuntu.com/getubuntu/releasenotes/904

Hth

Revision history for this message
Wayne Miller (wlm) said :
#6

It took me a while to locate the old bootable CD for the 6.XX version. I have it up and running now. The lspci | grep -i inet command gets no response, just as it did with the 9.06 installation.

As for the PC having sufficient resources to handle the installation of 9.06, I didn't see any issues that were listed on the website you directed me to. The installation was clean with no warnings or errors. The HD is 40 G. According to the system monitor, the memory is allocated 122.6 M to user and 332.3 M to swap.

Incidently, operating the PC from the 6.XX CD (which is really slow), there is no internet connection, as there was when it was installed on the HD. I have another Ubuntu machine running 9.06 that connects on this port, so I know the line is good.

Revision history for this message
Ryan Dwyer (ryandwyer) said :
#7

I think it's quite obvious there is no DHCP server on the network ("No DHCPOFFERS made").

ifconfig | grep -i inet:
inet addr:127.0.0.1 mask: 255.0.0.0
inet6 addr: ::1/128 scope: host
inet6 addr (lots of stuff, I suspect a wireless response)
inet addr (more stuff...)

The first two would be the lo/localhost device, which is why the IP is 127.0.0.1.

The older installation would have had the IP configured statically, in which case you need to do the same.

Revision history for this message
Wayne Miller (wlm) said :
#8

I don't recall having to manually enter the IP on the old system. Upon the latest suggestion, I tried to enter the host IP using the system network tools and using the foxfire network preferences menu, but with no success. Should I be executing a command from terminal mode?

Revision history for this message
Best zvacet (ivicakolic) said :
#9

In network manager select wired and there try to sett static connection,or you can do the same in DSL if you use username &password to connect.Ask your ISP for nameservers if you don't know them.

Revision history for this message
Wayne Miller (wlm) said :
#10

Thanks zvacet, that solved my question.