eth0 died on reboot

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



I removed an unused pci card from my PC. After I restarted it, eth0 was dead. (no I didn't remove my network card ;-) )
The network card is built into the motherboard.

Using another computer, I have verified that the port on the router and the cable are both good.

Does anybody have any ideas what I could try next?

Thanks
Dennis


[root@amor ~]# service network restart
Shutting down loopback interface:                          [  OK  ]
Bringing up loopback interface:                            [  OK  ]
Bringing up interface eth0:  
Determining IP information for eth0...PING 192.168.1.254 (192.168.1.254) from 192.168.1.65 eth0: 56(84) bytes of data.

--- 192.168.1.254 ping statistics ---
4 packets transmitted, 0 received, +3 errors, 100% packet loss, time 2999ms
, pipe 3
failed.
                                                           [FAILED]
[root@amor ~]# 

What happens during network restart on /var/log/messages:
tail -f /var/log/messages
Sep  8 12:24:50 amor kernel: ADDRCONF(NETDEV_UP): eth0: link is not ready
Sep  8 12:24:50 amor dhclient: DHCPREQUEST on eth0 to 255.255.255.255 port 67
Sep  8 12:24:58 amor dhclient: DHCPREQUEST on eth0 to 255.255.255.255 port 67
Sep  8 12:25:06 amor dhclient: DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 5
Sep  8 12:25:11 amor dhclient: DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 14
Sep  8 12:25:25 amor dhclient: DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 21
Sep  8 12:25:46 amor dhclient: DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 10
Sep  8 12:25:56 amor dhclient: DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 10
Sep  8 12:26:05 amor dhclient: DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 1
Sep  8 12:26:07 amor dhclient: No DHCPOFFERS received.
Sep  8 12:26:07 amor dhclient: Trying recorded lease 192.168.1.65
Sep  8 12:26:07 amor avahi-daemon[2606]: Joining mDNS multicast group on interface eth0.IPv4 with address 192.168.1.65.
Sep  8 12:26:07 amor avahi-daemon[2606]: New relevant interface eth0.IPv4 for mDNS.
Sep  8 12:26:07 amor avahi-daemon[2606]: Registering new address record for 192.168.1.65 on eth0.IPv4.
Sep  8 12:26:10 amor avahi-daemon[2606]: Withdrawing address record for 192.168.1.65 on eth0.
Sep  8 12:26:10 amor avahi-daemon[2606]: Leaving mDNS multicast group on interface eth0.IPv4 with address 192.168.1.65.
Sep  8 12:26:10 amor avahi-daemon[2606]: Interface eth0.IPv4 no longer relevant for mDNS.


Here from dmesg, eth0 is found and a driver e10001 is installed:
dmesg
e1000e: Intel(R) PRO/1000 Network Driver - 0.2.0
e1000e: Copyright (c) 1999-2007 Intel Corporation.
ACPI: PCI Interrupt 0000:00:19.0[A] -> GSI 20 (level, low) -> IRQ 20
PCI: Setting latency timer of device 0000:00:19.0 to 64
iTCO_wdt: Intel TCO WatchDog Timer Driver v1.02 (26-Jul-2007)
iTCO_wdt: Found a ICH8 or ICH8R TCO device (Version=2, TCOBASE=0x0460)
iTCO_wdt: initialized. heartbeat=30 sec (nowayout=0)
eth0: (PCI Express:2.5GB/s:Width x1) 00:16:76:c4:cd:10
eth0: Intel(R) PRO/1000 Network Connection
eth0: MAC: 4, PHY: 6, PBA No: ffffff-0ff
ACPI: PCI Interrupt 0000:00:1f.3[B] -> GSI 21 (level, low) -> IRQ 21

here from lsmod and lspci it looks like the driver really is installed and the card really was seen
lsmod | grep e1000e
e1000e                 84709  0 

lspci
00:19.0 Ethernet controller: Intel Corporation 82566DC Gigabit Network Connection (rev 02)

__________________________________________________
Correo Yahoo!
Espacio para todos tus mensajes, antivirus y antispam ¡gratis! 
Regístrate ya - http://correo.yahoo.com.mx/ 

-- 
fedora-list mailing list
fedora-list@xxxxxxxxxx
To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list
Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines

[Index of Archives]     [Current Fedora Users]     [Fedora Desktop]     [Fedora SELinux]     [Yosemite News]     [Yosemite Photos]     [KDE Users]     [Fedora Tools]     [Fedora Docs]

  Powered by Linux