I know you said your card has RJ-45, but SOME of the eePro cards have
both BNC plugs and RJ-45. If you are using The BNC, it sounds like you
forgot to put on the termination resisters. If you are using the RJ-45,
makes sure that is the primary data path. Just a shot. I don't know
how to monitor data in Linux either.
ken
>
>
> Hi all. I just purchased an eepro100, and it's not
> performing as well as
> I expected. If I use 'ping -f remotehost' to a host on the
> same subnet,
> the hub collision light turns on solid, and percentage of
> packets lost is
> about 2% for 60k packets. Collisions are 25k from that it appears.
>
> I'm using an Acer 16 port hub, which I'm sure isn't the
> highest quality,
> but using 'ping -f' between two other hosts shows little or
> no collisions.
> I've tried replacing the cables, etc, to no avail. I've
> downloaded the
> 5/3/99 driver:
>
> eth0: Intel PCI EtherExpress Pro100 at 0xef00,
> 00:90:27:8B:x:y, IRQ 10.
> Receiver lock-up bug exists -- enabling work-around.
> Board assembly 721383-006, Physical connectors present: RJ45
> Primary interface chip i82555 PHY #1.
> General self-test: passed.
> Serial sub-system self-test: passed.
> Internal registers self-test: passed.
> ROM checksum self-test: passed (0x04f4518b).
> eepro100.c:v1.08 5/3/99 Donald Becker
>
> Does this receiver bug significantly reduce thruput? I just
> got the card,
> should I return it?
>
> Thanks,
> Dave
>
>
> -
> To unsubscribe from this list: send the line "unsubscribe
> linux-net" in
> the body of a message to [EMAIL PROTECTED]
>
-
To unsubscribe from this list: send the line "unsubscribe linux-net" in
the body of a message to [EMAIL PROTECTED]
