[eepro100] collisions
Pooya Woodcock
root@pooya.dhs.org
Fri, 19 Jan 2001 16:18:33 -0500 (EST)
hello.
my 2.4.0 "kernelized" linux box has an eepro100 as follows:
-----info------
eepro100.c:v1.09j-t 9/29/99 Donald Becker
http://cesdis.gsfc.nasa.gov/linux/drivers/eepro100.html
eepro100.c: $Revision: 1.35 $ 2000/11/17 Modified by Andrey
V. Savochkin <saw@saw.sw.com.sg> and others
eth0: Intel Corporation 82557 [Ethernet Pro 100], 00:A0:C9:D7:CD:77,
IRQ 11.
Board assembly 678400-001, 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 (0x49caa8d6).
Receiver lock-up workaround activated.
with ifconfig for it as follows:
eth0 Link encap:Ethernet HWaddr 00:A0:C9:D7:CD:77
inet addr:*.*.*.* Bcast:*.*.*.* Mask:255.255.255.0
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:523598 errors:0 dropped:0 overruns:0 frame:0
TX packets:375423 errors:0 dropped:0 overruns:0 carrier:0
collisions:614 txqueuelen:100
Interrupt:11
and mii-diag output as follows:
Using the default interface 'eth0'.
Basic registers of MII PHY #1: 0000 780d 02a8 0150 01e1 0021 0000 ffff.
Basic mode control register 0x0000: Auto-negotiation disabled, with
Speed fixed at 10 mbps, half-duplex.
You have link beat, and everything is working OK.
Your link partner is generating 10baseT link beat (no autonegotiation).
-----end info--------
question: i must have a 10mbps half duplex connection (for now). is there
a way to eliminate all of the collisions? full duplex 10baseT creates many
frame errors. i thought that the intel eepro100 series of nics would
eliminate many collisions (even in half duplex 10bT). i understand that
the percentage of collision wrt/ total packet transfer is minimal, but hey
why not have a perfect 0. i will soon make use of the 100mbps but not for
at least 4-5 months.
Regards,
Pooya