Skip to contentSkip to conversation

ethernet driver probs (tulip, de4x5, 3c509)

DISCUSSION Manfred Bartz 2 participants 3 messages Feb 19, 2001 – Feb 20, 2001

lore
Share & tools
lore
#0 lore raw

I have 3 NICs (2*DEC, 1*3c509) in my gateway (P75, 40M RAM).

tulip.o in 2.4.1 insists on selecting 10baseT, no command line option can convince it otherwise. tulip.o in 2.2.16 auto detected media and worked fine.

de4x5.o in 2.4.1 needs to be told the media, then works fine. de4x5.o in 2.2.16 auto detected media and worked fine.

3c509.0 in 2.4.1 insists on AUI media when cold-booted (power off, then on), no command line option can convince it otherwise. First cold-booting into kernel 2.2.16 and then warm-booting into 2.4.1 works; it will then use the config stored in EEPROM. Same if I cold-boot into DOS, run the 3c509 config utility and then warm-boot into 2.4.1. This makes it impossible for the system to reboot with kernel 2.4.1 after power failure.

That 3 (three!) ethernet drivers which worked flawlessly in 2.2.16 misbehave in 2.4.1 to varying degrees seems to me to indicate that there might be some underlying problem affecting all those drivers.

Any thoughts or suggestions?

Signature · 1 line
Manfred
#1 lore raw
Quoted 5 lines · Manfred Bartz

I have 3 NICs (2*DEC, 1*3c509) in my gateway (P75, 40M RAM).

tulip.o in 2.4.1 insists on selecting 10baseT, no command line option can convince it otherwise. tulip.o in 2.2.16 auto detected media and worked fine.

A little info on your cards would be helpful. With well over 100 different types of Tulip cards, I can't just read your mind :)

lspci, tulip-diag, and dmesg output would all be helpful.

Quoted 2 lines

de4x5.o in 2.4.1 needs to be told the media, then works fine. de4x5.o in 2.2.16 auto detected media and worked fine.

de4x5 is going away, anyway.

Jeff

#2 lore raw
Quoted 9 lines · Jeff Garzik
Quoted 5 lines · Manfred Bartz

I have 3 NICs (2*DEC, 1*3c509) in my gateway (P75, 40M RAM).

tulip.o in 2.4.1 insists on selecting 10baseT, no command line option can convince it otherwise. tulip.o in 2.2.16 auto detected media and worked fine.

A little info on your cards would be helpful. With well over 100 different types of Tulip cards, I can't just read your mind :)

The problem seems to be generic. It is always related to media selection and occurs with at least 3 different NICs which are based on the 21040 and 21041 chips.

Quoted 1 line

lspci, tulip-diag, and dmesg output would all be helpful.

I have not got lspci but since the driver reports the correct IRQ and IO-ports that should be no issue. (I'll install lspci if necessary).

Outputs of dmesg, tulip-diag, and some other info is now at:

        <http://www.logi.cc/tulip/>
Quoted 4 lines
Quoted 2 lines

de4x5.o in 2.4.1 needs to be told the media, then works fine. de4x5.o in 2.2.16 auto detected media and worked fine.

de4x5 is going away, anyway.

Pity. It works and I really like the manual options interface... :/

Signature · 1 line
Manfred