eth0 not detected
rsphagura at hotmail.com
Wed May 3 18:21:13 PDT 2006
DJ Lucas wrote on Tue, 02 May 2006 21:03:06:
>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
>Maybe do a 'dmesg -n 7' before hand to see all the kernel messages on the
>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.
The outputs of various commands you suggested are as below:
# demesg -n 7
# ip link set eth0 up
# no such device
# echo $?
# ip addr show
1. Intel: <BPOADCST, MULTICAST> mtu 1500 qdisc noop qlen 1000
link/ether 00:02:a5:a4:3f:bf brd ff:ff:ff:ff:ff:ff
2. lo <LOOPBACK,UP> mtu 16436 qdisc noqueue
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
3. dummy0: <BROADCAST,NOARP> mtu 1500 qdisc noop
link/ether 02:78:ca:b5:ab:f1 brd ff:ff:ff:ff:ff:ff
4. gre0: <NOARP> mtu 1476 qdisc noop
link/gre 00:00:00:00 brd 00:00:00:00
Does this indicate something to you?
Thanks and Regards
More information about the lfs-support