100M FDX or not?
David Arnold <[email protected]>
| Newsgroups | gmane.linux.drivers.eepro100.devel |
|---|---|
| Message-ID | <[email protected]> |
I have 2 linux machines, RH 7.1 and RH 7.2. Both machines have 2 eepro100 cards in them, and they should be able to do 100M FDX automatically, right? But I suspect that 100M FDX is not actually set, so I connected the machines to a 3com 100M switch. The switch has 100M FDX connections to other linux/solaris boxes, so I know it's capable of doing this connection. The LEDs on the switch reveal that the connection is set to 100M, but as HDX, not FDX. So for both cards, I force through 100M FDX in modules.conf. alias eth1 eepro100 options eepro100 options="0x30,0x30" alias eth0 eepro100 Shut down network, rmmod eepro100, restart network. dmesg reveals: ----------------------------------------------------------------------------- eth0: 0 multicast blocks dropped. eth1: 0 multicast blocks dropped. eepro100.c:v1.09j-t 9/29/99 Donald Becker http://cesdis.gsfc.nasa.gov/linux/drivers/eepro100.html eepro100.c: $Revision: 1.36 $ 2000/11/17 Modified by Andrey V. Savochkin <[email protected]> and others PCI: Found IRQ 5 for device 00:0c.0 PCI: Sharing IRQ 5 with 00:09.0 eth0: Intel Corporation 82557 [Ethernet Pro 100], 00:02:B3:8B:85:8F, IRQ 5. Board assembly 751767-004, Physical connectors present: RJ45 Primary interface chip i82555 PHY #1. Secondary interface chip i82555. Forcing 100Mbs full-duplex operation. General self-test: passed. Serial sub-system self-test: passed. Internal registers self-test: passed. ROM checksum self-test: passed (0x3258698e). PCI: Found IRQ 11 for device 00:0d.0 PCI: Sharing IRQ 11 with 00:09.1 PCI: Sharing IRQ 11 with 01:00.0 eth1: Intel Corporation 82557 [Ethernet Pro 100] (#2), 00:02:B3:8B:8D:97, IRQ 11. Board assembly 751767-004, Physical connectors present: RJ45 Primary interface chip i82555 PHY #1. Secondary interface chip i82555. Forcing 100Mbs full-duplex operation. General self-test: passed. Serial sub-system self-test: passed. Internal registers self-test: passed. ROM checksum self-test: passed (0x3258698e). ----------------------------------------------------------------------------- But the switch still thinks the cards are only HDX! I am getting crippling slow xfer rates with ufsdump, sfp and scp. I *think* it's a config error or something with the cards, but I'm stuck.. Unfortunately I can't seem to compile the diagnostic tools on the scyld website pertaining to the eepro100 card - I'll post more detail if needed. Any assistance appreciated. -- David Arnold [email protected]