FAILED for eth0

Paul Smith phhs80 at gmail.com
Thu Aug 17 16:23:38 UTC 2006


On 8/17/06, Brad Bonkoski <bbonkoski at mediaguide.com> wrote:
> >> what do you get when you run /sbin/ifconfig -a?
> >> Perhaps the new network card requires a different driver for your
> >> kernel...
> >> And if you are not familiar with the process of building/loading new
> >> modules for the kernel, I am not sure if there is an *easy* way to do
> >> this, except for letting the installer run and guessing what modules you
> >> need....
> >>
> >> >> > When I turn off my computer, I get an OK for everything, except for
> >> >> > eth0. Is there some way of automatically reconfiguring that device?
> >> >>
> >> >> Your query is a bit vague,
> >> >> but the entry in /etc/sysconfig/network-scripts/ifcfg-eth0
> >> >> has to be correct.
> >> >> The various network wizards should hopefully do this.
> >> >
> >> > Thanks, Timothy. I agree that my query is vague, but I do not know how
> >> > to make it more detailed. Maybe someone could tell me what I should
> >> > add to describe better my problem. However, I suspect from what I see
> >> > at shutdown time that the problem is related with HWADDR. The content
> >> > of /etc/sysconfig/network-scripts/ifcfg-eth0 is quoted below:
> >> >
> >> > # more /etc/sysconfig/network-scripts/ifcfg-eth0
> >> > # Realtek Semiconductor Co., Ltd. RTL-8139/8139C/8139C+
> >> > DEVICE=eth0
> >> > BOOTPROTO=none
> >> > HWADDR=00:30:4F:2B:8C:84
> >> > ONBOOT=yes
> >> > TYPE=Ethernet
> >> > NETMASK=255.255.255.0
> >> > IPADDR=192.168.1.2
> >> > USERCTL=no
> >> > IPV6INIT=no
> >> > PEERDNS=yes
> >> > GATEWAY=192.168.1.1
> >> > #
> >> >
> >> > I would like to add that my Ethernet card was changed together with
> >> > the processor upgrade.
> >
> > Thanks, Brad. The result of '/sbin/ifconfig -a' follows:
> >
> > # /sbin/ifconfig -a
> > eth0      Link encap:Ethernet  HWaddr 00:14:85:38:2C:93
> >          inet addr:192.168.1.2  Bcast:192.168.1.255  Mask:255.255.255.0
> >          inet6 addr: fe80::214:85ff:fe38:2c93/64 Scope:Link
> >          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
> >          RX packets:273531 errors:1057 dropped:0 overruns:0 frame:929
> >          TX packets:310170 errors:0 dropped:0 overruns:0 carrier:0
> >          collisions:1057 txqueuelen:1000
> >          RX bytes:181391697 (172.9 MiB)  TX bytes:72930268 (69.5 MiB)
> >          Interrupt:177
> >
> This is good...it shows your device it up and looks to be *working* as
> it has transmitted and received packets...
> Questions:
> Do you have more then 1 Ethernet device in your system?
> Do the network settings listed look accurate?
> Can you ping any internal machines, like your gateway (192.168.1.1)
> Can you ping external machines?

Yes, it is working fine as long as I can be aware of it; I only notice
a message at the shudown time.

No, I do not have any other Ethernet device. I use eth0 to connect to
Internet (through a ISP) and I do not have any network here. So, all
machines are external. Furthermore, I do everything with the Internet
with no problem at all.

Paul




More information about the fedora-list mailing list