I may be breathing air too close to the exhaust pipe, but I had the same
eth0 failed during initialize message as you. I solved it by doing a total
re-install of Linux on my machine. Not knowing what I was doing during the
first install, but after the third install I've never had the eth0 problem
again.
Oh well, that's my story -- I'm sure somebody else has a better solution
on this list...
Dave
----- Original Message -----
From: <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Wednesday, January 24, 2001 9:12 AM
Subject: [newbie] Cable Modem Woes
> Hi:
>
> I am trying to connect my box running linux-mandrake 7.2 with @Home. I am
able
> to configure the eth0 interface and it does show up when I do a ifconfig
and a
> netstat -r. I used netconf to assign the host name, DNS server names etc.
While
> I am able to ping the machine with the IP address i give to the eth0
interface,
> I cannot reach anything outside the box.
>
> This is a short summary of what I did:
>
> # insmod rtl8139
> # ifconfig eth0 192.168.1.10 netmask 255.255.255.0 up
> # route add default eth0
>
> after that i went into netconf and gave it the host name, DNS server
address
> etc. I check all the related .conf files.
>
> If i ping 192.168.1.10 it goes through. But if try to ping anything else
it
> just fails.
>
> I tried using dhclient to see if it is able to reach @Home's DHCP server
but to
> no avail.
>
> Another thing that I noticed is that every time I reboot, the eth0
interface
> fails to come up and I have to manually bring up that interface.
>
> This is my setup, I have a a nic connected to a hub, connected to a cable
> modem. I have two other windows boxes connected to the hub, which I turned
off
> as I first wanted to get the linux box working. The windows boxes work
fine.
>
> I think I am missing some key procedure in this. Can someone please tell
me
> what I am doing wrong?
>
> Thanks in advance.
> Surya
>
>
