eth0 not detected

DJ Lucas dj at linuxfromscratch.org
Tue May 2 19:03:06 PDT 2006


randhir phagura wrote:

> No the kernel does detect but does not bring-up eth0.
> 
> The dmesg gives the following, as related to eth0:
> 
> eth0: OEM i82557/i82558 10/100 Ethernet, 00:02:A5:A4:3F:BF, IRQ 11.
>  Receiver lock-up bug exists -- enabling work-around.
>  Board assembly 729857-001, Physical connectors present: RJ45
>  Primary interface chip i82555 PHY #1.
>  General self-test: passed.
>  Serial sub-system self-test: passed.
>  Internal registers self-test: passed.
>  ROM checksum self-test: passed (0x04f4518b).
>  Receiver lock-up workaround activated.
> e100: Intel(R) PRO/100 Network Driver, 3.4.14-k2-NAPI
> e100: Copyright(c) 1999-2005 Intel Corporation
> 
> The dmesg is similar to my older LFS booted with kernel-2.6.14.
> 

Does ip or kernel give any other output?  Try this once the system is up:

ip link set eth0 up # or down
echo $?

Maybe do a 'dmesg -n 7' before hand to see all the kernel messages on 
the console.

The output should be the same, but maybe not...we'll see.

If that fails, as I expect it should, try 'ip addr show' and see if eth0 
is in the list at all, but I can't see why it would be.  I'm just 
grasping for straws in hopes that something obvious will show up to help 
you.

-- DJ Lucas




More information about the lfs-support mailing list