Redhat 8 and eth0 (NIC) status

nathanv117 · 12-30-2002, 01:51 PM

Redhat 8 and eth0 (NIC) status:

When I boot up the system, the NIC shows active. After some time it becomes inactive. Why? When I try toactivate, it does not work most of the time and I have to reboot as I do't know how to activate! Questions:
1. Why it becomes decativated?
2. Why most of the time the recativation does not work?
3. How to stop becoming inactive? Is ther any parm picking has to be done for the card? If yes, where to see the parms?
I could not see any file starting with eth0 in the system!

trickykid · 12-30-2002, 02:12 PM

Check your logs, /var/log/messages to see if anything suspicious is going on there.

When it goes inactive, try a simple:

ifconfig eth0 up

nathanv117 · 01-01-2003, 01:16 PM

The command ifconfig did not reactivate the NIC.
Q: How do I know that the command has been executed?
Enclosing message log for more information. Thanks.

.........booting messages clipped
>>>> Dec 31 15:41:27 localhost network: Bringing up interface eth0: succeeded
Dec 31 15:41:32 localhost xinetd[808]: xinetd Version 2.3.7 started with libwrap options compiled in.
Dec 31 15:41:32 localhost xinetd[808]: Started working: 1 available service
Dec 31 15:41:33 localhost xinetd: xinetd startup succeeded
......... clipped
Dec 31 15:42:18 localhost gconfd (root-1165): Resolved address "xml:readonly:/etc/gconf/gconf.xml.defaults" to a read-only config source at position 2
Dec 31 15:42:21 localhost kernel: Creative EMU10K1 PCI Audio Driver, version 0.19, 05:49:43 Dec 12 2002
Dec 31 15:42:21 localhost kernel: PCI: Found IRQ 10 for device 00:0e.0
Dec 31 15:42:21 localhost kernel: emu10k1: EMU10K1 rev 8 model 0x8027 found, IO at 0xa800-0xa81f, IRQ 10
Dec 31 15:42:21 localhost kernel: ac97_codec: AC97 codec, id: 0x5452:0x4123 (TriTech TR A5)
Dec 31 15:42:22 localhost modprobe: modprobe: Can't locate module sound-service-0-3
Dec 31 15:42:24 localhost kernel: Attached scsi CD-ROM sr0 at scsi1, channel 0, id 0, lun 0
Dec 31 15:42:24 localhost kernel: sr0: scsi3-mmc drive: 24x/40x writer cd/rw xa/form2 cdda tray
Dec 31 15:42:24 localhost kernel: Uniform CD-ROM driver Revision: 3.12
>>>>> No activity before eth0 shut down!
>>>>> Dec 31 16:39:33 localhost network: Shutting down interface eth0: succeeded
Dec 31 16:39:33 localhost network: Shutting down loopback interface: succeeded
Dec 31 16:39:33 localhost /etc/hotplug/net.agent: NET unregister event not supported
Dec 31 16:39:34 localhost apmd[756]: System Suspend
Dec 31 16:51:22 localhost kernel: via-rhine.c:v1.10-LK1.1.14 May-3-2002 Written by Donald Becker
Dec 31 16:51:22 localhost kernel: http://www.scyld.com/network/via-rhine.html
Dec 31 16:51:22 localhost kernel: PCI: Found IRQ 5 for device 00:10.0
Dec 31 16:51:22 localhost kernel: via-rhine: reset did not complete in 10 ms.
Dec 31 16:51:22 localhost kernel: eth0: VIA VT6102 Rhine-II at 0x9800, 00:05:5d:e9:98:42, IRQ 5.
Dec 31 16:51:22 localhost kernel: eth0: MII PHY found at address 8, status 0x782d advertising 05e1 Link 45e1.
Dec 31 16:51:22 localhost kernel: eth0: reset did not complete in 10 ms.
Dec 31 16:51:22 localhost kernel: eth0: Setting full-duplex based on MII #8 link partner capability of 45e1.
Dec 31 16:51:28 localhost dhclient: DHCPREQUEST on eth0 to 255.255.255.255 port 67
Dec 31 16:51:35 localhost dhclient: DHCPREQUEST on eth0 to 255.255.255.255 port 67
Dec 31 16:51:44 localhost dhclient: DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 3
Dec 31 16:51:47 localhost dhclient: DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 6
Dec 31 16:51:53 localhost dhclient: DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 10
Dec 31 16:51:54 localhost dhclient: DHCPREQUEST on eth0 to 255.255.255.255 port 67
Dec 31 16:52:01 localhost dhclient: DHCPREQUEST on eth0 to 255.255.255.255 port 67
Dec 31 16:52:03 localhost dhclient: DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 18
Dec 31 16:52:16 localhost dhclient: DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 5
Dec 31 16:52:21 localhost dhclient: DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 14
Dec 31 16:52:21 localhost dhclient: DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 14
Dec 31 16:52:24 localhost kernel: NETDEV WATCHDOG: eth0: transmit timed out
Dec 31 16:52:24 localhost kernel: eth0: Transmit timed out, status 0000, PHY status 782d, resetting...
Dec 31 16:52:24 localhost kernel: eth0: reset did not complete in 10 ms.
Dec 31 16:52:35 localhost dhclient: DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 9
Dec 31 16:52:35 localhost dhclient: DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 15
Dec 31 16:52:44 localhost dhclient: DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 1
Dec 31 16:52:45 localhost dhclient: No DHCPOFFERS received.
Dec 31 16:52:45 localhost dhclient: Trying recorded lease 192.168.123.125
Dec 31 16:52:48 localhost dhclient: receive_packet failed on eth0: Network is down
Dec 31 16:52:48 localhost netfs: Mounting other filesystems: succeeded
Dec 31 16:52:48 localhost netfs: Mounting other filesystems: succeeded
Dec 31 16:52:49 localhost apmd[756]: Normal Resume after 00:13:15 (-1% unknown) AC power
Dec 31 16:52:50 localhost dhclient: DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 7
Dec 31 16:52:50 localhost dhclient: send_packet: Network is down
Dec 31 16:52:57 localhost dhclient: DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 12
Dec 31 16:52:57 localhost dhclient: send_packet: Network is down
Dec 31 16:53:09 localhost dhclient: DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 8
Dec 31 16:53:09 localhost dhclient: send_packet: Network is down
Dec 31 16:53:17 localhost dhclient: No DHCPOFFERS received.
Dec 31 16:53:17 localhost dhclient: Trying recorded lease 192.168.123.125
>>>> Noticed eth0 is in inactive state
>>>> issued ifconfig eth0 up command . Id did not reactivate eth0!!!
>>>>
Dec 31 16:53:17 localhost kernel: eth0: reset did not complete in 10 ms.
Dec 31 16:59:07 localhost kernel: eth0: reset did not complete in 10 ms.

dfctve_end_user · 01-01-2003, 09:23 PM

what is running dhcp on your network?
router? pc?

nathanv117 · 01-02-2003, 09:39 AM

RH8 PC to Asante Cable router to Cable Modem.
Router runs DHCP.

dfctve_end_user · 01-02-2003, 03:57 PM

can you hit the network at all? (i.e. ping or a web browser)

if not check your values in linuxconf

root@localuser#linuxconf<enter>

dhcp is enabled...
subnet is correct (router has this value)...

nathanv117 · 01-02-2003, 07:44 PM

Everything is ok when I bootup RH. I am able to go to internet, ping, send mail etc. After some time (varies) eth0 becomes inactive!! Some times I am able to activate thru RH gui. Most of the time activation fails!

dfctve_end_user · 01-02-2003, 07:54 PM

when it dies try pinging loopback or the ip of the card.

You will isolate hardware or driver that way.

Could be:

Flaky card
bad cable
bad hub/switch/router.

Also try resetting (unpluging and pluging back in) your hub/switch/router and see if you have the same problem.

nathanv117 · 01-02-2003, 08:19 PM

I will try next time I find eth0 is inactive.
FYI. NIC is/was working fine under W2K for long time.
Installed RH on this PC as dual boot system to learn Linux.
Thanks