ethernet/3com/vortex.rst

33 	- 3c590 Vortex 10Mbps
34 	- 3c592 EISA 10Mbps Demon/Vortex
39 	- 3c900 Boomerang 10baseT
40 	- 3c900 Boomerang 10Mbps Combo
41 	- 3c900 Cyclone 10Mbps TPO
42 	- 3c900 Cyclone 10Mbps Combo
43 	- 3c900 Cyclone 10Mbps TPC
44 	- 3c900B-FL Cyclone 10base-FL
48 	- 3c905B Cyclone 10/100/BNC
58 	- 3c575 [Megahertz] 10/100 LAN  CardBus
67 	- 3c982 Hydra Dual Port A
91   Where N is a number from 0 to 7.  Anything above 3 produces a lot
102   The individual options are composed of a number of bitfields which
108 	0	10baseT
109 	1	10Mbs AUI
111 	3	10base2 (BNC)
118 	10      Use default setting from EEPROM
121   When generating a value for the 'options' setting, the above media
162   PAUSE command, which means that they will stop sending packets for a
163   short period if they receive a PAUSE frame from the link partner.
165   The driver only allows flow control on a link which is operating in
178   for receiving.  When a packet arrives, the driver has to decide
180   a smaller buffer and copy the packet across into it.
182   This is a speed/space tradeoff.
191   transmit packets in a single invocation.  It does this in a loop.
194   is exceeded the interrupt service routine gives up and generates a
200   in hardware.  Linux has used the Rx checksumming for a long time.
209   decision.  If you think that Tx checksums are causing a problem, you
216   The driver drops a message in the logfiles to indicate whether or
220   performance improvement for the sendfile() system call, but a small
254 A number of the older NICs such as the 3c590 and 3c900 series have
255 10base2 and AUI interfaces.
257 Prior to January, 2001 this driver would autoselect the 10base2 or AUI
258 port if it didn't detect activity on the 10baseT port.  It would then
259 get stuck on the 10base2 port and a driver reload was necessary to
260 switch back to 10baseT.  This behaviour could not be prevented with a
268 it will permanently select the 10baseT port.  Automatic selection of
275 This is a common error which is almost always caused by another host on
280 As a last resort, you can force the 3c59x driver into full-duplex mode
285 but this has to be viewed as a workaround for broken network gear and
323   The driver uses a one-minute heartbeat for adapting to changes in
325   This means that when, for example, a machine is unplugged from a hubbed
326   10baseT LAN plugged into a  switched 100baseT LAN, the throughput
331   On a side note, adding HAS_NWAY seems to share a problem with the
335   we've noticed for a while but haven't had the time to track down.
346     If autonegotiation is a problem, you may need to specify "speed
347     100" and "duplex full" as well (or "speed 10" and "duplex half").
361 If you believe you have a driver problem here are some of the
364 - Is it really a driver problem?
370 - OK, it's a driver problem.
372    You need to generate a report.  Typically this is an email to the
376 - The contents of your report will vary a lot depending upon the
377   problem.  If it's a kernel crash then you should refer to
384    - A copy of the banner message which the driver generates when
387      eth0: 3Com PCI 3c905C Tornado at 0xa400,  00:50:da:6a:88:f0, IRQ 19
393      a full detection message.  Please do this::
397    - If it is a PCI device, the relevant output from 'lspci -vx', eg::
406        00: b7 10 00 92 07 00 10 02 74 00 00 02 08 20 00 00
407        10: 01 a4 00 00 00 00 00 db 00 00 00 00 00 00 00 00
408        20: 00 00 00 00 00 00 00 00 00 00 00 00 b7 10 00 10
409        30: 00 00 00 00 dc 00 00 00 00 00 00 00 05 01 0a 0a
411    - A description of the environment: 10baseT? 100baseT?
417      If this is a large file and you are sending your report to a
438 	 a) modprobe driver debug=7
449 	 a) Run 'vortex-diag -aaee' and 'mii-diag -v' when the card is
456 end up working on this problem for a week or more as the maintainer