fail to ifup eth0

I am trying to install fedora on one of my pIII computer.
Everything works fine except that eth0 is not working.
here is what I got from /etc/sysconfig/hwconf

class :NETWORK
bug: PCI
detached:0
device:eth0
driver:tulip
desc: "DEC|DECchip 21142/43"
network.hwaddr:00:50:8B:4BCA
......

if I run ifup etho, here is the result
Determining IP information for eth0....failed; no link present. check
cable?

Then I thought there must be something wrong with my physical cable. I
then reinstalled win-xp and confirmed that cable is fine. and here is
the network card information i got from the win-xp
Intel 21143 based PCI Fast Ethernet

Any help are highly appreciated.

jim schrieb:

> Determining IP information for eth0....failed; no link present. check
> cable?

Do you have any other NICs in your box?

timbo
--
Reply to: tim at boneko dot de

Are you running this inside a VM?

Regards,
-Kai

In the Usenet newsgroup comp.os.linux.networking, in article
<(E-Mail Removed) .com>, jim wrote:

>I am trying to install fedora on one of my pIII computer.
>Everything works fine except that eth0 is not working.

>device:eth0
>driver:tulip
>desc: "DEC|DECchip 21142/43"
>network.hwaddr:00:50:8B:4BCA

[compton ~]$ etherwhois 00:50:8B
00-50-8B (hex) COMPAQ COMPUTER CORPORATION
00508B (base 16) COMPAQ COMPUTER CORPORATION
20555 S.H. 249
HOUSTON TX 77070
UNITED STATES
[compton ~]$

>if I run ifup etho, here is the result
>Determining IP information for eth0....failed; no link present. check
>cable?

The fact that you can see the MAC address is a possible good sign. The
"no link present" could still be a configuration issue. See the
Ethernet-HOWTO

206074 Aug 25 2003 Ethernet-HOWTO

which suggests trying the de4x5 driver.

The 'Determining IP information for eth0" sounds as if you are trying to
use DHCP. What happens if you set the system to a static address? See
the file /etc/sysconfig/network-scripts/ifcfg-eth0

Old guy

(E-Mail Removed) (Moe Trin) wrote in
news:(E-Mail Removed):

> In the Usenet newsgroup comp.os.linux.networking, in article
> <(E-Mail Removed) .com>, jim wrote:
>
>>I am trying to install fedora on one of my pIII computer.
>>Everything works fine except that eth0 is not working.
>
>>device:eth0
>>driver:tulip
>>desc: "DEC|DECchip 21142/43"
>>network.hwaddr:00:50:8B:4BCA
>
> [compton ~]$ etherwhois 00:50:8B
> 00-50-8B (hex) COMPAQ COMPUTER CORPORATION
> 00508B (base 16) COMPAQ COMPUTER CORPORATION
> 20555 S.H. 249
> HOUSTON TX 77070
> UNITED STATES
> [compton ~]$
>
>>if I run ifup etho, here is the result
>>Determining IP information for eth0....failed; no link present. check
>>cable?
>
> The fact that you can see the MAC address is a possible good sign. The
> "no link present" could still be a configuration issue. See the
> Ethernet-HOWTO
>
> 206074 Aug 25 2003 Ethernet-HOWTO
>
> which suggests trying the de4x5 driver.
>
> The 'Determining IP information for eth0" sounds as if you are trying to
> use DHCP. What happens if you set the system to a static address? See
> the file /etc/sysconfig/network-scripts/ifcfg-eth0
>
> Old guy
>
>

I wonder if the problem could be the speed/duplex settings. I have
occaisionally come across problems with NIC's autonegotiating with certain
ethernet switches. The OP could try forcing say 100mb fdx using ethtool.

eg.

ethtool -s eth0 speed 100 duplex full autoneg off

Klazmon.

Thank you for your reply. No, I don't have any other NICs in my box.

yes, it is a compaq computer and I was trying to use DHCP.

I use rmmod tulip and insmod de4x5.
after that, I run ifconfig and saw the eth0 information listed there(
it was never listed before :-)
However, the card still doesn't work.

If I issue ifup eth0, it gives me
Cannot get driver information: Operation not supported.

i have a NIC (DC21040 i think it is) that also uses the tulip driver.

the problem i had was that the 2.6.x tulip driver seems to get confused
about the speed of the LAN -- on my NIC, it forces it to operate at
10mbs even though its a 100mbs LAN.

the simplest thing i suggest to you is trying: boot the machine, load
the tulip driver, unplug and replug in the network cable into the back
and then trying to configure network (ifup or whatever)

if this works, then you will want to check the LEDs on the NIC. most
have status for power/activity/100mbs link. if on boot (before the
tulip driver is loaded) the 100mbs LED is lit but is then off when you
load the tulip driver, then you have got the same problem i have which
seems to be the tulip driver forcing the card into the wrong mode --
unplugging/plugging the network cable gets the tulip driver to
recognise the real speed of the network.

i havent found a way to force the tulip driver to believe 100mbs is
available.

I am still trying to get my nic to work
some extra information i found is the following:
>From /var/log/dmesg
PCI: Found IRQ11 for device 00:14.2
PCI: Sharing IRQ11 with 00:12.0

output from ifconfig:
Interrup:11 Base address:0x2000

does the above information mean anything to somebody?
Thanks,

In the Usenet newsgroup comp.os.linux.networking, in article
<(E-Mail Removed) .com>,
(E-Mail Removed) wrote:

>i have a NIC (DC21040 i think it is) that also uses the tulip driver.
>
>the problem i had was that the 2.6.x tulip driver seems to get confused
>about the speed of the LAN -- on my NIC, it forces it to operate at
>10mbs even though its a 100mbs LAN.

Which kernel version? Which driver version?

[compton ~/kernel]$ zgrep -c tulip ChangeLog-2.* | grep -v ':0' | column
ChangeLog-2.0.40.gz:2 ChangeLog-2.4.30.gz:1
ChangeLog-2.4.1.gz:1 ChangeLog-2.4.4.gz:1
ChangeLog-2.4.10.gz:2 ChangeLog-2.6.10.gz:9
ChangeLog-2.4.13.gz:1 ChangeLog-2.6.11.gz:8
ChangeLog-2.4.17.gz:1 ChangeLog-2.6.12.gz:5
ChangeLog-2.4.18.gz:2 ChangeLog-2.6.13-rc1.gz:10
ChangeLog-2.4.19.gz:5 ChangeLog-2.6.3.gz:3
ChangeLog-2.4.20.gz:7 ChangeLog-2.6.4.gz:6
ChangeLog-2.4.21.gz:2 ChangeLog-2.6.5.gz:7
ChangeLog-2.4.22.gz:2 ChangeLog-2.6.6.gz:19
ChangeLog-2.4.23.gz:3 ChangeLog-2.6.7.gz:7
ChangeLog-2.4.26.gz:1 ChangeLog-2.6.8.gz:1
ChangeLog-2.4.27.gz:4 ChangeLog-2.6.9.gz:7
[compton ~/kernel]$

>if this works, then you will want to check the LEDs on the NIC. most
>have status for power/activity/100mbs link. if on boot (before the
>tulip driver is loaded) the 100mbs LED is lit but is then off when you
>load the tulip driver, then you have got the same problem i have which
>seems to be the tulip driver forcing the card into the wrong mode --
>unplugging/plugging the network cable gets the tulip driver to
>recognise the real speed of the network.
>
>i havent found a way to force the tulip driver to believe 100mbs is
>available.

Depending on the age of your kernel, and the tulip driver, you may be able
to use the MII tools application to fix things. See if you have 'mii-diag'
installed.

Old guy