>From the output of ifconfig, we know your machine does not have a
physical ethernet interface registered so no amount of configuration in
the network manager or is going to help you I'm afraid.

Could you attach the entire output of just the dmesg command please so
we can diagnose further please?

Did the machine ship to you like this with Ubuntu preinstalled ?
If it did, I would contact them also to let them know as they should
have tested that the Ubuntu installation would work 'out of the box'
with the network adaptors in the laptops they sell.

Guy.

On Thu, 2009-02-19 at 16:08 +0000, Rowan wrote:

> Thanks for the suggestions,  Guy.
> 
> "sudo dmesg grep eth0" gives:
> 
> usage: dmesg [-c][-n level][-s bufsize]
> 
> "sudo ifconfig -a" gives the same as "sudo ifconfig", namely, local 
> loopback only.
> 
> 
> Guy Thouret wrote:
> > On Thu, 2009-02-19 at 15:23 +0000, Simos wrote:
> >> A google search for 'RTL8111/8168B Intrepid' reveals the following 
> >> bug report
> >> https://bugs.edge.launchpad.net/ubuntu/+bug/285430
> >
> > If the OS is actually aware of the physical ethernet interface this 
> > bug may be relevant.
> > >From the output we have seen so far, eth0 did not show up in the list 
> > of interfaces so it is either non-existant or not activated (up).
> >
> > Rowan:
> > Can you enter the following commands and post the output:
> >
> > dmesg | grep eth0
> > ifconfig -a
> >
> > The first command will show any output from a kernel driver trying to 
> > register the eth0 interface.
> > The second command will list all network interfaces registered on your 
> > machine regardless of their state.
> >
> > Here is an example output, we should hope to see something similar:
> > g...@guy-laptop:~$ dmesg | grep eth0
> > [    0.448004] 0000:00:19.0: eth0: (PCI Express:2.5GB/s:Width x1) 
> > 00:13:77:3c:04:fe
> > [    0.448007] 0000:00:19.0: eth0: Intel(R) PRO/1000 Network Connection
> > [    0.448035] 0000:00:19.0: eth0: MAC: 5, PHY: 6, PBA No: ffffff-0ff
> >
> > g...@guy-laptop:~$ ifconfig -a
> > ...
> > eth0      Link encap:Ethernet  HWaddr 00:13:77:3c:04:fe 
> >           UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
> >           RX packets:0 errors:0 dropped:0 overruns:0 frame:0
> >           TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
> >           collisions:0 txqueuelen:1000
> >           RX bytes:0 (0.0 B)  TX bytes:0 (0.0 B)
> >           Memory:fc300000-fc320000
> > ... (only relevant part shown)
> >
> > If we see output from both commands, then you do indeed have a 
> > registered physical ethernet interface on your machine.
> > If we do not see output or see errors this would sugggest a driver 
> > issue or a physical fault with the ethernet interface.
> > A driver issue we can help you overcome.
> > If there's a physical fault with the ethernet interface, send the 
> > machine back for a replacement.
> >
> > If the dmesg | grep eth0 command shows no output, if you attach the 
> > output of just the dmesg command by itself we'll probably be able to 
> > diagnose the exact cause of the failure.
> >
> > Guy. 
> 
> 
-- 
ubuntu-uk@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-uk
https://wiki.ubuntu.com/UKTeam/

Reply via email to