🚀 go-pugleaf

Archive-Name: linux/howto/ethernet/part1
Last-modified: 29 Apr 95

  Linux	Ethernet-Howto
  Paul Gortmaker, Editor.
  v2.3,	11 February 1995

  This is the Ethernet-Howto, which is a compilation of	information
  about	which ethernet devices can be used for Linux, and how to set
  them up. It hopefully	answers	all the	frequently asked questions about
  using	ethernet cards with Linux. Note	that this Howto	is focused on
  the hardware and low level driver aspect of the ethernet cards, and
  does not cover the software end of things. See the NET2-Howto	for that
  stuff.

  1.  Introduction


  The Ethernet-Howto covers what cards you should and shouldn't	buy; how
  to set them up, how to run more than one, and	other common problems
  and questions. It contains detailed information on the current level
  of support for all of	the most common	ethernet cards available.  It
  does not cover the software end of things, as	that is	covered	in the
  NET-2	Howto. Also note that general non-Linux	specific questions about
  Ethernet are not (or at least	they should not	be) answered here. For
  those	types of questions, see	the excellent amount of	information in
  the comp.dcom.lans.ethernet FAQ. You can FTP it from dorm.rutgers.edu
  in the directory /pub/novell/info_and_docs/

  This present revision	covers kernels up to and including v1.1.91

  The Ethernet-Howto is	edited and maintained by:

       Paul Gortmaker, Paul.Gortmaker@anu.edu.au


  The primary source of	the information	for the	Ethernet-Howto is from:

       Donald J. Becker, becker@cesdis.gsfc.nasa.gov


  who we have to thank for writing the vast majority of	ethernet card
  drivers that are presently available for Linux. He also is the
  original author of the NFS server too. Thanks	Donald!	We owe ya one!
  :-)

  Net-surfers may wish to check	out the	following URL:

  Donald Becker
  (http://cesdis.gsfc.nasa.gov/pub/people/becker/whoiam.html)


  1.1.	Using the Ethernet-Howto


  As this guide	is getting bigger and bigger, you probably don't want to
  spend	the rest of your afternoon reading the whole thing. And	you
  don't	have to	read it	all. If	you haven't got	an ethernet card, then
  you will want	to start with ``What card should I buy...''  to	see what
  you should buy, and what you should avoid. If	you have already got an
  ethernet card, but are not sure if you can use it with Linux,	then you
  will want to read ``Vendor Specific...''  which contains specific
  information on each manufacturer, and	their cards. If	you are	having
  trouble with your card, then you will	want to	read the specific
  information about your card mentioned	above, and the troubleshooting
  information in ``the FAQ section''.  If you are interested in	some of
  the technical	aspects	of the device drivers, then you	can find that
  information in ``Technical Information''

  1.2.	Disclaimer and Copyright


  This document	is not gospel. However,	it is probably the most	up to
  date info that you will be able to find. Nobody is responsible for
  what happens to your hardware	but yourself. If your ethercard	or any
  other	hardware goes up in smoke (...nearly impossible!)  we take no
  responsibility. ie. THE AUTHORS ARE NOT RESPONSIBLE FOR ANY DAMAGES
  INCURRED DUE TO ACTIONS TAKEN	BASED ON THE INFORMATION INCLUDED IN
  THIS DOCUMENT.

  This document	is Copyright (c) 1994 by Donald	Becker and Paul
  Gortmaker. Permission	is granted to make and distribute verbatim
  copies of this manual	provided the copyright notice and this
  permission notice are	preserved on all copies.

  Permission is	granted	to copy	and distribute modified	versions of this
  document under the conditions	for verbatim copying, provided that this
  copyright notice is included exactly as in the original, and that the
  entire resulting derived work	is distributed under the terms of a
  permission notice identical to this one.

  Permission is	granted	to copy	and distribute translations of this
  document into	another	language, under	the above conditions for
  modified versions.

  If you are intending to incorporate this document into a published
  work,	please contact me, and I will make an effort to	ensure that you
  have the most	up to date information available. In the past, out of
  date versions	of the Linux howto documents have been published, which
  caused the developers	undue grief from being plagued with questions
  that were already answered in	the up to date versions.


  1.3.	Mailing	Lists and the Linux Newsgroups



  If you have questions	about your ethernet card, please READ this
  document first. You may also want to join the	NET channel of the
  Linux-activists mailing list by sending mail to

       linux-activists-request@niksula.hut.fi


  with the line

       X-Mn-Admin: join	NET


  at the top of	the message body (not the subject). If you want	to learn
  how to use the mailing channels, then	send an	empty message to the
  above	address, and you will get an instruction manual	sent back to you
  in a few hours. However, it is worth noting that the NET channel is
  primarily used for discussion	of the networking code,	and you	may not
  see much discussion about a particular driver.

  Furthermore keep in mind that	the NET	channel	is for development
  discussions only. General questions on how to	configure your system
  should be directed to	comp.os.linux.help unless you are actively
  involved in the development of part of the networking	for Linux.  We
  ask that you please respect this general guideline for content.

  Recently, a similar group of mailing lists has started on the	host
  vger.rutgers.edu, using the much more	common majordomo mailing list
  server. Send mail to majordomo@vger.rutgers.edu to get help with what
  lists	are available, and how to join them.

  Also,	the news groups	comp.sys.ibm.pc.hardware.networking and
  comp.dcom.lans.ethernet should be used for questions that are	not
  Linux	specific.


  1.4.	Related	Documentation


  Much of this info came from saved postings from the comp.os.linux
  groups, which	shows that it is a valuable resource of	information.
  Other	useful information came	from a bunch of	small files by Donald
  himself. Of course, if you are setting up an Ethernet	card, then you
  will want to read the	NET-2 Howto so that you	can actually configure
  the software you will	use.  And last but not least, the contributions
  from the individuals and companies listed in ``Contributors''	is
  greatly appreciated as well. Oh yeah,	if you fancy yourself as a bit
  of a hacker, you can always scrounge some additional info from the
  driver source	files as well. There is	usually	a paragraph in there
  describing any important points.

  For those looking for	information that is not	specific in any	way to
  Linux	(i.e. what is 10BaseT, what is AUI, what does a	hub do,	etc.)  I
  strongly recommend the Ethernet-FAQ from the newsgroup
  comp.dcom.lans.ethernet. Look	on the FTP site	dorm.rutgers.edu in the
  directory /pub/novell/info_and_docs/ or grab it from the following
  URL:

  Ethernet FAQ
  (ftp://dorm.rutgers.edu/pub/novell/info_and_docs/Ethernet.FAQ)

  Don't	let the	fact that it was last revised in 1993 scare you, as not
  much has happened to Ethernet	since then. (Discounting the upcoming
  100Base-whatever, of course.)


  1.5.	New Versions of	this Document


  New versions of this document	can be retrieved via anonymous FTP from
  sunsite.unc.edu, in /pub/Linux/docs/HOWTO/* and various Linux	ftp
  mirror sites.	Updates	will be	made as	new information	/ drivers
  becomes available. If	this copy that you are reading is more than 2
  months old, it is either out of date,	or it means that I have	been
  lazy and haven't updated it.	This document was produced by using the
  SGML system that was specifically set	up for the Linux Howto project,
  and there are	various	output formats available, including, postscript,
  dvi, ascii, html, and	soon TeXinfo.

  I would recommend viewing it in the html (via	Mosaic)	or the
  Postscript/dvi format. Both of these contain cross-references	that are
  lost in the ascii translation.

  If you want to get the official copy off sunsite, here is URL.

  Ethernet-HOWTO (http://sunsite.unc.edu/mdw/HOWTO/Ethernet-HOWTO.html)

  If minor additions and changes have been made, you can view the latest
  working copy from this URL.

  Working Copy (http://rsphy1.anu.edu.au/~gpg109/Ethernet-HOWTO.html)




  2.  What card	should I buy for Linux?


  For impatient	users that just	want a quick, cheap answer the summary
  is: get 16 bit thinnet 8013 cards. For those who want	the absolute
  best performance, get	an AMD PC-Net/Lance based card.	For more detail
  as to	the who	what where and why, read on.


  2.1.	Eight bit vs 16	bit


  Unless you are a light user, or are confined to using	the smaller ISA
  slot,	the use	of the 8 bit cards like	the wd8003, the	3c503 and the
  ne1000 is usually not	worth the cost savings.	Get the	8013 or	the
  3c503/16, or the ne2000 instead. (The	3c501 is not included in this
  discussion, as it shouldn't be used under any	circumstances.)

  However, so not to leave you with a bad taste	in your	mouth if you
  happen to already have one, you can still expect to get about	500kB/s
  ftp download speed to	an 8 bit wd8003	card (on a 16MHz ISA bus) from a
  fast host.  And if most of your net-traffic is going to remote sites,
  then the bottleneck in the path will be elsewhere, and the only speed
  difference you will notice is	during net activity on your local
  subnet.

  A note to NFS	users: Some people have	found that using 8 bit cards in
  NFS clients causes poorer than expected performance, when using 8kB
  (native Sun) NFS packet size.

  The possible reason for this could be	due to the difference in on
  board	buffer size between the	8 bit and the 16 bit cards.  The 8 bit
  cards	have an	8kB buffer, and	the 16 bit cards have a	16kB buffer. The
  Linux	driver will reserve 3kB	of that	buffer (for Tx ping-pong
  buffers), leaving only 5kB for an 8 bit card.	The maximum ethernet
  packet size is about 1500 bytes. Now that 8kB	NFS packet will	arrive
  as about 6 back to back maximum size ethernet	packets. Both the 8 and
  16 bit cards have no problem Rx'ing back to back packets. The	problem
  arises when the machine doesn't remove the packets from the cards
  buffer in time, and the buffer overflows. The	fact that 8 bit	cards
  take an extra	ISA bus	cycle per transfer doesn't help	either.	What you
  can do if you	have an	8 bit card is either set the NFS transfer size
  to 4kB, or try increasing the	ISA bus	speed in order to get the card's
  buffer cleared out faster.


  2.2.	Low price Ethernet cards


  The lowest price seen	so far was in the March	'94 edition of LAN
  magazine. There was an ad for	Addtron	AE-200 cards (jumper settable
  NE2000 clones) for a measly $19 ea!  Unfortunately this offer	has
  since	expired. However, you might want to check to see what their
  everyday price is.

  You can also call AT-LAN-TEC at 301-948-7070.	Ask for	their technical
  support person. As with all purchases, you should indicate you are
  buying this for a Linux system.  NB: Their current NE2000 clone is a
  model	that `traps' other drivers that	probe into their address space.
  AT-LAN-TEC also carries a clone, non-EEPROM 8013 board for somewhat
  more,	and a NE2100 clone.  Either is a better	choice if the very
  lowest price isn't essential.

  And a	recent addition	is the VLB and PCI cards offered by Boca
  Research. These are selling for around the $70 mark, and these are
  supported with the latest kernel. These use the new 32 bit versions of
  the LANCE chip from AMD. See ``Boca Research'' for more info.

  If you require an ISA	card, you can use the the Allied Telesis AT1500
  which	uses the ISA version of	the LANCE chip from AMD.  It is	offered
  at a good price by many vendors.  Even Inmac,	known for their	premium
  markup, has this card	for under $100.	See ``AT-1500''	for more info.



  2.3.	Vendors	and Brands to Avoid


  These	vendors	have decided not to release programming	information
  about	their products,	without	signing	a NDA (non-disclosure
  agreement).  Hence it	is strongly advised that you avoid buying
  products offered from	these companies.

  (1) Cabletron	(see ``Cabletron'')

  (2) Xircom (see ``Xircom'')

  These	particular cards should	be avoided, as they are	obsolete.  The
  reasons as to	why they have been classified as such can be found in
  their	respective sections. For your particular application, these
  reasons may not be a concern,	so you should have a read of the reasons
  listed.

  (1) 3c501 (see ``3Com	3c501'')

  (2) Arcnet based cards (see ``Arcnet'')

  (3) Any 8-bit	cards (see ``Eight bit...'')


  2.4.	Type of	cable that your	card should support


  Unless you have to conform to	an existing network, you will want to
  use thinnet or thin ethernet cable. This is the style	with the
  standard BNC connectors. See ``Cables, Coax...''  for	other concerns
  with different types of ethernet cable.

  Most ethercards also come in a `Combo' version for only $10-$20 more.
  These	have both twisted pair and thinnet transceiver built-in,
  allowing you to change your mind later.

  The twisted pair cables, with	the RJ-45 (giant phone jack) connectors
  is technically called	10BaseT. You may also hear it called UTP
  (Unsheilded Twisted Pair).

  The thinnet, or thin ethernet	cabling, (RG-58	coaxial	cable) with the
  BNC (metal push and turn-to-lock) connectors is technically called
  10Base2.

  The older thick ethernet (10mm coaxial cable)	which is only found in
  older	installations is called	10Base5.

  Large	corporate installations	will most likely use 10BaseT instead of
  10Base2. 10Base2 does	not offer an easy upgrade path to the new
  upcoming 100Base-whatever.


  3.  Vendor/Manufacturer/Model	Specific Information



  The only thing that one needs	to use an ethernet card	with Linux is
  the appropriate driver. For this, it is essential that the
  manufacturer will release the	technical programming information to the
  general public without you (or anyone) having	to sign	your life away.
  A good guide for the likelihood of getting documentation (or,	if you
  aren't writing code, the likelihood that someone else	will write that
  driver you really, really need) is the availability of the Crynwr (nee
  Clarkson) packet driver. Russ	Nelson runs this operation, and	has been
  very helpful in supporting the development of	drivers	for Linux. Net-
  surfers can try this URL to look up Russ' software.

  Russ Nelson's	Packet Drivers (http://www.crynwr.com/crynwr/home.html)

  Given	the documentation, you can write a driver for your card	and use
  it for Linux (at least in theory) and	if you intend to write a driver,
  have a look at ``Skeleton driver'' as	well.  Keep in mind that some
  old hardware that was	designed for XT	type machines will not function
  very well in a multitasking environment such as Linux. Use of	these
  will lead to major problems if your network sees a reasonable	amount
  of traffic.

  Most cards come with drivers for MS-DOS interfaces such as NDIS and
  ODI, but these are useless for Linux.	Many people have suggested
  directly linking them	in or automatic	translation, but this is nearly
  impossible. The MS-DOS drivers expect	to be in 16 bit	mode and hook
  into `software interrupts', both incompatible	with the Linux kernel.
  This incompatibility is actually a feature, as some Linux drivers are
  considerably better than their MS-DOS	counterparts. The `8390' series
  drivers, for instance, use ping-pong transmit	buffers, which are only
  now being introduced in the MS-DOS world.

  Keep in mind that PC ethercards have the widest variety of interfaces
  (shared memory, programmed I/O, bus-master, or slave DMA) of any
  computer hardware for	anything, and supporting a new ethercard
  sometimes requires re-thinking most of the lower-level networking
  code.	(If you	are interested in learning more	about these different
  forms	of interfaces, see ``Programmed	I/O vs.	...''.)

  Also,	similar	product	numbers	don't always indicate similar products.
  For instance,	the 3c50* product line from 3Com varies	wildly between
  different members.

  Enough talk. Let's get down to the information you want.


  3.1.	3Com


  If you are not sure what your	card is, but you think it is a 3Com
  card,	you can	probably figure	it out from the	assembly number. 3Com
  has a	document `Identifying 3Com Adapters By Assembly	Number'	(ref
  24500002) that would most likely clear things	up. See	``Technical
  Information from 3Com'' for info on how to get documents from	3Com.

  Also note that 3Com has a FTP	site with various goodies: ftp.3Com.com
  that you may want to check out.


  3.1.1.  3c501


  Status -- Semi-Supported

  Too brain-damaged to use. Available surplus from many	places.	Avoid it
  like the plague. Again, do not purchase this card, even as a joke.
  It's performance is horrible,	and it breaks in many ways.
  Cameron L. Spitzer of	3Com said: ``I'm speaking only for myself here,
  of course, but I believe 3Com	advises	against	installing a 3C501 in a
  new system, mostly for the same reasons Donald has discussed.	You
  probably won't be happy with the 3C501 in your Linux box. The	data
  sheet	is marked `(obsolete)' on 3Com's Developers' Order Form, and the
  board	is not part of 3Com's program for sending free Technical
  Reference Manuals to people who need them. The decade-old things are
  nearly indestructible, but that's about all they've got going	for them
  any more.''

  For those not	yet convinced, the 3c501 can only do one thing at a time
  -- while you are removing one	packet from the	single-packet buffer it
  cannot receive another packet, nor can it receive a packet while
  loading a transmit packet. This was fine for a network between two
  8088-based computers where processing	each packet and	replying took
  10's of msecs, but modern networks send back-to-back packets for
  almost every transaction.

  Donald writes: `The driver is	now in the std.	kernel,	but under the
  following conditions:	This is	unsupported code. I know the usual
  copyright says all the code is unsupported, but this is _really_
  unsupported. I DON'T want to see bug reports,	and I'll accept	bug
  fixes	only if	I'm in a good mood that	day.

  I don't want to be flamed later for putting out bad software.	I don't
  know all all of the 3c501 bugs, and I	know this driver only handles a
  few that I've	been able to figure out. It has	taken a	long intense
  effort just to get the driver	working	this well.'

  AutoIRQ works, DMA isn't used, the autoprobe only looks at 0x280 and
  0x300, and the debug level is	set with the third boot-time argument.

  Once again, the use of a 3c501 is strongly discouraged!  Even	more so
  with a IP multicast kernel, as you will grind	to a halt while
  listening to all multicast packets. See the comments at the top of the
  source code for more details.


  3.1.2.  3c503, 3c503/16


  Status -- Supported

  3Com shared-memory ethercards. They also have	a programmed I/O mode
  that doesn't use the 8390 facilities (their engineers	found too many
  bugs!)  It should be about the same speed as the same	bus width
  WD80x3, Unless you are a light user, spend the extra money and get the
  16 bit model,	as the price difference	isn't significant. The 3c503
  does not have	``EEPROM setup'', so the diagnostic/setup program isn't
  needed before	running	the card with Linux. The shared	memory address
  of the 3c503 is set using jumpers that are shared with the boot PROM
  address. This	is confusing to	people familiar	with other ISA cards,
  where	you always leave the jumper set	to ``disable'' unless you have a
  boot PROM.

  The Linux 3c503 driver can also work with the	3c503 programmed-I/O
  mode,	but this is slower and less reliable than shared memory	mode.
  Also,	programmed-I/O mode is not tested when updating	the drivers, the
  deadman (deadcard?) check code may falsely timeout on	some machines,
  and the probe	for a 3c503 in programmed-I/O mode is turned off by
  default in some versions of the kernel. This was a panic reaction to
  the general device driver probe explosion; the 3c503 shared memory
  probe	is a safe read from memory, rather than	an extensive scan
  through I/O space. As	of 0.99pl13, the kernel	has an I/O port
  registrar that makes I/O space probes	safer, and the programmed-I/O
  3c503	probe has been re-enabled.  You	still shouldn't	use the
  programmed-I/O mode though, unless you need it for MS-DOS
  compatibility.

  The 3c503's IRQ line is set in software, with	no hints from an EEPROM.
  Unlike the MS-DOS drivers, the Linux driver has capability to	autoIRQ:
  it uses the first available IRQ line in {5,2/9,3,4}, selected	each
  time the card	is ifconfig'ed.	(Older driver versions selected	the IRQ
  at boot time.) The ioctl() call in `ifconfig'	will return EAGAIN if no
  IRQ line is available	at that	time.

  Some common problems that people have	with the 503 are discussed in
  ``Problems with...''.



  3.1.3.  3c505


  Status -- Semi-Supported

  This is a driver that	was written by Craig Southeren
  geoffw@extro.ucc.su.oz.au. These cards also use the i82586 chip.  I
  don't	think there are	that many of these cards about.	 It is included
  in the standard kernel, but it is classed as an alpha	driver.	See
  ``Alpha Drivers'' for	important information on using alpha-test
  ethernet drivers with	Linux.

  There	is also	the file /usr/src/linux/drivers/net/README.3c505 that
  you should read if you are going to use one of these cards.  It
  contains various options that	you can	enable/disable.	 Technical
  information is available in ``Programming the	Intel chips''.


  3.1.4.  3c507

  Status -- Semi-Supported

  This card uses one of	the Intel chips, and the development of	the
  driver is closely related to the development of the Intel Ether
  Express driver.  The driver is included in the standard kernel
  release, but as an alpha driver.

  See ``Alpha Drivers''	for important information on using alpha-test
  ethernet drivers with	Linux. Technical information is	available in
  ``Programming	the Intel chips''.


  3.1.5.  3c509	/ 3c509B


  Status -- Supported

  It's fairly inexpensive and has excellent performance	for a non-bus-
  master design.  The drawbacks	are that the original 3c509 _requires_
  very low interrupt latency. The 3c509B shouldn't suffer from the same
  problem, due to having a larger buffer. (See below.)

  Note that the	ISA card detection uses	a different method than	most
  cards. Basically, you	ask the	cards to respond by sending data to an
  ID_PORT (port	0x100).	Note that if you have some other strange ISA
  card using an	I/O range that includes	the ID_PORT of the 3c509, it
  will probably	not get	detected. Note that you	can change the ID_PORT
  to 0x110 or 0x120 or... in 3c509.c if	you have a conflicting ISA card,
  and the 3c509	will still be happy.  Also note	that this detection
  method means that it is difficult to predict which card will get
  detected first in a multiple ISA 3c509 configuration.	 The card with
  the lowest hardware ethernet address will end	up being eth0. This
  shouldn't matter to anyone, except for those people who want to assign
  a 6 byte hardware address to a particular interface.

  A working 3c509 driver was first included as an alpha-test version in
  the 0.99pl13 kernel sources.	It is now in the standard kernel.

  The original 3c509 has a tiny	Rx buffer (2kB), causing the driver to
  occasionally drop a packet if	interrupts are masked for too long. To
  minimize this	problem, you can try unmasking interrupts during IDE
  disk transfers (see hdparm(8)) and/or	increasing your	ISA bus	speed so
  IDE transfers	finish sooner.	(Note that the driver could be
  completely rewritten to use predictive interrupts, but performance re-
  writes of working drivers are	low priority unless there is some
  particular incentive or need.)

  The newer model 3c509B has 8kB on board, and the driver can set 4, 5
  or 6kB for an	Rx buffer. This	setting	can also be stored on the
  EEPROM. This should alleviate	the above problem with the original
  3c509. At this point in time,	the Linux driver is not	aware of this,
  and treats the 3c509B	as an older 3c509.

  Apparently, 3c509B users may have to use the supplied	DOS utility to
  disable the plug and play support, and to set	the output media to what
  they require.

  Cameron Spitzer writes: ``Beware that	if you put a '509 in EISA
  addressing mode by mistake and save that in the EEPROM, you'll have to
  use an EISA machine or the infamous Test Via to get it back to normal,
  and it will conflict at IO location 0	which may hang your ISA	machine.
  I believe this problem is corrected in the 3C509B version of the
  board.''


  3.1.6.  3c523


  Status -- Not	Supported

  This MCA bus card uses the i82586, and now that people are actually
  running Linux	on MCA machines, someone may wish to try and recycle
  parts	of the 3c507 driver into a driver for this card.


  3.1.7.  3c527


  Status -- Not	Supported

  Yes, another MCA card. No, not too much interest in it.  Better
  chances with the 3c523 or the	3c529.


  3.1.8.  3c529


  Status -- Not	Supported

  This card actually uses the same chipset as the 3c509.  Donald
  actually put hooks into the 3c509 driver to check for	MCA cards after
  probing for EISA cards, and before probing for ISA cards. But	it
  hasn't evolved much further than that. Donald	writes:

  ``I don't have access	to a MCA machine (nor do I fully understand the
  probing code)	so I never wrote the mca_adaptor_select_mode() or
  mca_adaptor_id() routines. If	you can	find a way to get the adaptor
  I/O address that assigned at boot time, you can just hard-wire that in
  place	of the commented-out probe. Be sure to keep the	code that reads
  the IRQ, if_port, and	ethernet address.''

  3.1.9.  3c579


  Status -- Supported

  The EISA version of the 509. The current EISA	version	uses the same 16
  bit wide chip	rather than a 32 bit interface,	so the performance
  increase isn't stunning.  The	EISA probe code	was added to 3c509.c for
  0.99pl14.  We	would be interested in hearing progress	reports	from any
  3c579	users. (Read the above 3c509 section for info on the driver.)

  Cameron Spitzer writes: ``The	3C579 (Etherlink III EISA) should be
  configured as	an EISA	card. The IO Base Address (window 0 register 6
  bits 4:0) should be 1f, which	selects	EISA addressing	mode. Logic
  outside the ASIC decodes the IO address s000,	where s	is the slot
  number. I don't think	it was documented real well. Except for	its IO
  Base Address,	the '579 should	behave EXACTLY like the'509 (EL3 ISA),
  and if it doesn't, I want to hear about it (at my work address).''



  3.1.10.  3c589 / 3c589B


  Status -- Semi-Supported

  Many people have been	using this PCMCIA card for quite some time now.
  Note that support for	it is not (at present) included	in the default
  kernel source	tree. Note that	you will need a	supported PCMCIA
  controller chipset. There are	drivers	available on Donald's ftp site:


       cesdis.gsfc.nasa.gov:/pub/linux/pcmcia/README.3c589 ces-
       dis.gsfc.nasa.gov:/pub/linux/pcmcia/3c589.c ces-
       dis.gsfc.nasa.gov:/pub/linux/pcmcia/dbether.c


  Or for those that are	net-surfing you	can try:

  Don's	PCMCIA Stuff (http://cesdis.gsfc.nasa.gov/linux/pcmcia.html)

  You will still need a	PCMCIA socket enabler as well.

  See ``PCMCIA Support'' for more info on PCMCIA chipsets, socket
  enablers, etc.

  The "B" in the name means the	same here as it	does for the 3c509 case.


  3.2.	Accton



  3.2.1.  Accton MPX


  Status -- Supported

  Don't	let the	name fool you. This is still supposed to be a NE2000
  compatible card. The MPX is supposed to stand	for MultiPacket
  Accelerator, which, according	to Accton, increases throughput
  substantially. But if	you are	already	sending	back-to-back packets,
  how can you get any faster...


  3.2.2.  Accton EN2212	PCMCIA Card


  Status -- Semi-Supported

  David	Hinds has been working on a driver for this card, and you are
  best to check	the latest release of his PCMCIA package to see	what the
  present status is.


  3.3.	Allied Telesis



  3.3.1.  AT1500


  Status --Supported

  These	are a series of	low-cost ethercards using the 79C960 version of
  the AMD LANCE. These are bus-master cards, and thus probably the
  fastest ISA bus ethercards available (although the 3c509 has lower
  latency thanks to predictive interrupts).

  DMA selection	and chip numbering information can be found in ``AMD
  LANCE''.

  More technical information on	AMD LANCE based	Ethernet cards can be
  found	in ``Notes on AMD...''.


  3.3.2.  AT1700


  Status -- Supported

  The Allied Telesis AT1700 series ethercards are based	on the Fujitsu
  MB86965. This	chip uses a programmed I/O interface, and a pair of
  fixed-size transmit buffers. This allows small groups	of packets to
  sent be sent back-to-back, with a short pause	while switching	buffers.

  A unique feature is the ability to drive 150ohm STP (Shielded	Twisted
  Pair)	cable commonly installed for Token Ring, in addition to	10baseT
  100ohm UTP (unshielded twisted pair).

  The Fujitsu chip used	on the AT1700 has a design flaw: it can	only be
  fully	reset by doing a power cycle of	the machine.  Pressing the reset
  button doesn't reset the bus interface. This wouldn't	be so bad,
  except that it can only be reliably detected when it has been	freshly
  reset. The solution/work-around is to	power-cycle the	machine	if the
  kernel has a problem detecting the AT1700.

  Some production runs of the AT1700 had another problem: they are
  permanently wired to DMA channel 5.  This is undocumented, there are
  no jumpers to	disable	the "feature", and no driver dares use the DMA
  capability because of	compatibility problems.	No device driver will be
  written using	DMA if installing a second card	into the machine breaks
  both,	and the	only way to disable the	DMA is with a knife.

  The at1700 driver is included	in the standard	kernel source tree.



  3.4.	AMD / Advanced Micro Devices



  3.4.1.  AMD LANCE (7990, 79C960, PCnet-ISA)


  Status -- Supported

  There	really is no AMD ethernet card.	You are	probably reading this
  because the only markings you	could find on your card	said AMD and the
  above	number.	The 7990 is the	original `LANCE' chip, but most	stuff
  (including this document) refer to all these similar chips as	`LANCE'
  chips. (...incorrectly, I might add.)

  These	above numbers refer to chips from AMD that are the heart of many
  ethernet cards.  For example,	the Allied Telesis AT1500 (see
  ``AT1500'') the NE1500/2100 (see ``NE1500'') and the Boca-VLB/PCI
  cards	(see ``Boca-VLB/PCI'')

  The 79C960 (a.k.a. PCnet-ISA)	contains enhancements and bug fixes over
  the original 7990 LANCE design.

  Chances are that the existing	LANCE driver will work with all	AMD
  LANCE	based cards. (except perhaps the NI65XX	- see ``NI65XX'' for
  more info on that one.)  This	driver should also work	with NE1500 and
  NE2100 clones.

  For the ISA bus master mode all structures used directly by the LANCE,
  the initialization block, Rx and Tx rings, and data buffers, must be
  accessible from the ISA bus, i.e. in the lower 16M of	real memory.  If
  more than 16MB of memory is installed, low-memory `bounce-buffers' are
  used when needed.

  The DMA channel can be set with the low bits of the otherwise-unused
  dev->mem_start value (a.k.a. PARAM_1).  (see ``PARAM_1'') If unset it
  is probed for	by enabling each free DMA channel in turn and checking
  if initialization succeeds.

  The HP-J2405A	board is an exception: with this board it's easy to read
  the EEPROM-set values	for the	IRQ, and DMA.

  See ``Notes on AMD...''  for more info on these chips.


  3.4.2.  AMD 79C961 (PCnet-ISA+)


  Status -- Supported

  This is the PCnet-ISA+  -- an	enhanced version of the	79C960.	 It has
  support for jumper-less configuration	and Plug and Play.  See	the info
  in the above section.


  3.4.3.  AMD 79C965 (PCnet-32)


  Status -- Supported

  This is the PCnet-32 -- a 32 bit bus-master version of the original
  LANCE	chip for VL-bus	and local bus systems.	Minor cleanups were
  added	to the original	lance driver around v1.1.50 to support these 32
  bit versions of the LANCE chip.  The main problem was	that the current
  versions of the '965 and '970	chips have a minor bug.	 They clear the
  Rx buffer length field in the	Rx ring	when they are explicitly
  documented not to. Again, see	the above info.


  3.4.4.  AMD 79C970 (PCnet-PCI)


  Status -- Supported

  This is the PCnet-PCI	-- similar to the PCnet-32, but	designed for PCI
  bus based systems. Again, see	the above info.	 Donald	has modified the
  LANCE	driver to use the PCI BIOS structure that was introduced by Drew
  Eckhardt for the PCI-NCR SCSI	driver.	This means that	you need to
  build	a kernel with PCI BIOS support enabled.


  3.4.5.  AMD 79C974 (PCnet-SCSI)


  Status -- Supported

  This is the PCnet-SCSI --  which is basically	treated	like a '970 from
  an Ethernet point of view. A minor '974 specific fix was added to the
  1.1.8x kernels, so get a 1.1.90 or newer kernel. Also	see the	above
  info.	Don't ask if the SCSI half of the chip is supported -- this is
  the Ethernet-Howto, not the SCSI-Howto.


  3.5.	Ansel Communications



  3.5.1.  AC3200 EISA


  Status -- Semi-Supported

  This driver is included in the present kernel	as an alpha test driver.
  Please see ``Alpha Drivers'' in this document	for important
  information regarding	alpha drivers.	If you use it, let Donald know
  how things work out, as not too many people have this	card and
  feedback has been low.


  3.6.	Apricot



  3.6.1.  Apricot Xen-II On Board Ethernet


  Status -- Supported

  This on board	ethernet uses an i82596	bus-master chip.  It can only be
  at i/o address 0x300.	The author of this driver is Mark Evans. By
  looking at the driver	source,	it appears that	the IRQ	is hardwired to
  10.

  Earlier versions of the driver had a tendency	to think that anything
  living at 0x300 was an apricot NIC.  Since then the hardware address
  is checked to	avoid these false detections.


  3.7.	Arcnet



  Status -- Semi-Supported

  With the very	low cost and better performance	of ethernet, chances are
  that most places will	be giving away their Arcnet hardware for free,
  resulting in a lot of	home systems with Arcnet.

  An advantage of Arcnet is that all of	the cards have identical
  interfaces, so one driver will work for everyone.

  Recent interest in getting Arcnet going has picked up	again and Avery
  Pennarun's alpha driver has been put into the	default	kernel sources
  for 1.1.80 and above.	The arcnet driver uses `arc0' as its name
  instead of the usual `eth0' for ethernet devices.  Bug reports and
  success stories can be mailed	to:

  apenwarr@tourism.807-city.on.ca


  3.8.	AT&T


  Note that AT&T's StarLAN is an orphaned technology, like SynOptics
  LattisNet, and can't be used in a standard 10Base-T environment.


  3.8.1.  AT&T T7231 (LanPACER+)


  Status -- Not	Supported

  These	StarLAN	cards use an interface similar to the i82586 chip. At
  one point, Matthijs Melchior (matthijs.n.melchior@att.com) was playing
  with the 3c507 driver, and almost had	something useable working.
  Haven't heard	much since that.


  3.9.	AT-Lan-Tec / RealTek



  3.9.1.  AT-Lan-Tec / RealTek Pocket adaptor


  Status -- Supported

  This is a generic, low-cost OEM pocket adaptor being sold by AT-Lan-
  Tec, and (likely) a number of	other suppliers. A driver for it is
  included in the standard kernel.  Note that there is substantial
  information contained	in the driver source file `atp.c'.  BTW, the
  adaptor (AEP-100L) has both 10baseT and BNC connections!  You	can
  reach	AT-Lan-Tec at 1-301-948-7070. Ask for the model	that works with
  Linux, or ask	for tech support.

  In the Netherlands a compatible adaptor is sold under	the name SHI-TEC
  PE-NET/CT, and sells for about $125. The vendor was Megasellers.  They
  state	that they do not sell to private persons, but this doesn't
  appear to be strictly	adhered	to.  They are: Megasellers, Vianen, The
  Netherlands. They always advertise in	Dutch computer magazines.  Note
  that the newer model EPP-NET/CT appears to be	significantly different
  than the PE-NET/CT, and will not work	with the present driver.
  Hopefully someone will come up with the programming information and
  this will be fixed up.

  In Germany, a	similar	adaptor	comes as a no-brand-name product. Prolan
  890b,	no brand on the	casing,	only a roman II. Resellers can get a
  price	of about $130, including a small wall transformer for the power.
  The adaptor is `normal size' for the product class, about 57mm wide,
  22mm high tapering to	15mm high at the DB25 connector, and 105mm long
  (120mm including the BNC socket). It's switchable between the	RJ45 and
  BNC jacks with a small slide switch positioned between the two: a very
  intuitive design.

  Donald performed some	power draw measurements, and determined	that the
  average current draw was only	about 100mA @ 5V.  This	power draw is
  low enough that you could buy	or build a cable to take the 5V	directly
  from the keyboard/mouse port available on many laptops. (Bonus points
  here for using a standardized	power connector	instead	of a proprietary
  one.)

  Note that the	device name that you pass to ifconfig is not eth0 but
  atp0 for this	device.



  3.10.	 Boca Research


  Yes, they make more than just	multi-port serial cards.  :-)


  3.10.1.  Boca	BEN (PCI, VLB)


  Status -- Supported

  These	cards are based	on AMD's PCnet chips, used in the AT1500 and the
  like.	You can	pick up	a combo	(10BaseT and 10Base2) PCI card for under
  $70 at the moment.

  Supposedly Boca PCI cards can	have trouble with Pentium systems that
  are operating	faster than 66MHz. You may want	to check with Boca on
  this one. Note that this is not a driver problem, as it hits
  DOS/Win/NT users as well. Any	additional info	on this	as it develops
  would	be appreciated.

  More information can be found	in ``AMD LANCE''.

  More technical information on	AMD LANCE based	Ethernet cards can be
  found	in ``Notes on AMD...''.


  3.11.	 Cabletron


  Donald writes: `Yes, another one of these companies that won't release
  its programming information. They waited for months before actually
  confirming that all their information	was proprietary, deliberately
  wasting my time. Avoid their cards like the plague if	you can.  Also
  note that some people	have phoned Cabletron, and have	been told things
  like `a D. Becker is working on a driver for linux' -- making	it sound
  like I work for them.	This is	NOT the	case.'

  If you feel like asking them why they	don't want to release their low
  level	programming info so that people	can use	their cards, write to
  support@ctron.com.  Tell them	that you are using Linux, and are
  disappointed that they don't support open systems. And no, the usual
  driver development kit they supply is	useless. It is just a DOS object
  file that you	are supposed to	link against. Which you	aren't allowed
  to even reverse engineer.



  3.11.1.  E10**, E10**-x, E20**, E20**-x


  Status -- Semi-Supported

  These	are NEx000 almost-clones that are reported to work with	the
  standard NEx000 drivers, thanks to a ctron-specific check during the
  probe. If there are any problems, they are unlikely to be fixed, as
  the programming information is unavailable.


  3.11.2.  E2100


  Status -- Semi-Supported

  Again, there is not much one can do when the programming information
  is proprietary.  The E2100 is	a poor design. Whenever	it maps	its
  shared memory	in during a packet transfer, it	maps it	into the whole
  128K region! That means you can't safely use another interrupt-driven
  shared memory	device in that region, including another E2100.	 It will
  work most of the time, but every once	in a while it will bite	you.
  (Yes,	this problem can be avoided by turning off interrupts while
  transferring packets,	but that will almost certainly lose clock
  ticks.) Also,	if you mis-program the board, or halt the machine at
  just the wrong moment, even the reset	button won't bring it back. You
  will have to turn it off and leave it	off for	about 30 seconds.

  Media	selection is automatic,	but you	can override this with the low
  bits of the dev->mem_end parameter.  See ``PARAM_2''

  Also,	don't confuse the E2100	for a NE2100 clone.  The E2100 is a
  shared memory	NatSemi	DP8390 design, roughly similar to a brain-
  damaged WD8013, whereas the NE2100 (and NE1500) use a	bus-mastering
  AMD LANCE design.

  There	is an E2100 driver included in the standard kernel.  However,
  seeing as programming	info isn't available, don't expect bug-fixes.
  Don't	use one	unless you are already stuck with the card.



  3.12.	 D-Link


  Some people have had difficulty in finding vendors that carry	D-link
  stuff. This should help.


		  (714)	455-1688  in the US
		  (081)	203-9900  in the UK
		  6196-643011	  in Germany
		  (416)	828-0260  in Canada
		  (02) 916-1600	  in Taiwan




  3.12.1.  DE-100, DE-200, DE-220-T


  Status -- Supported

  The manual says that it is 100 % compatible with the NE2000. This is
  not true. You	should call them and tell them you are using their card
  with Linux, and they should correct their documentation. Some
  pre-0.99pl12 driver versions may have	trouble	recognizing the	DE2**
  series as 16 bit cards, and these cards are the most widely reported
  as having the	spurious transfer address mismatch errors. Note	that
  there	are cards from Digital (DEC) that are also named DE100 and
  DE200, but the similarity stops there.


  3.12.2.  DE-530


  Status -- Semi-Supported

  This appears to be a generic DEC 21040 PCI chip implementation, and
  will most likely work	with the generic 21040 driver.	However, nobody
  has verified this yet, and until that	has happened, it will remain
  listed as Semi-Supported.

  See ``DEC 21040'' for	more information on these cards, and the present
  driver situation.


  3.12.3.  DE-600


  Status -- Supported

  Laptop users and other folk who might	want a quick way to put	their
  computer onto	the ethernet may want to use this. The driver is
  included with	the default kernel source tree.	 Bjorn Ekwall
  bj0rn@blox.se	wrote the driver.  Expect about	80kb/s transfer	speed
  from this via	the parallel port. You should read the README.DLINK file
  in the kernel	source tree.

  Note that the	device name that you pass to ifconfig is now eth0 and
  not the previously used dl0.

  If your parallel port	is not at the standard 0x378 then you will have
  to recompile.	Bjorn writes: ``Since the DE-620 driver	tries to sqeeze
  the last microsecond from the	loops, I made the irq and port address
  constants instead of variables. This makes for a usable speed, but it
  also means that you can't change these assignements from e.g.	lilo;
  you _have_ to	recompile...'' Also note that some laptops implement the
  on-board parallel port at 0x3bc which	is where the parallel ports on
  monochrome cards were/are.

  Supposedly, a	no-name	ethernet pocket	adaptor	marketed under the name
  `PE-1200' is DE-600 compatible.  It is available in Europe from:


	  SEMCON Handels Ges.m.b.h
	  Favoritenstrasse 20
	  A-1040 WIEN
	  Telephone: (+43) 222 50 41 708
	  Fax	   : (+43) 222 50 41 706




  3.12.4.  DE-620


  Status -- Supported

  Same as the DE-600, only with	two output formats.  Bjorn has written a
  driver for this model, for kernel versions 1.1 and above. See	the
  above	information on the DE-600.
  3.12.5.  DE-650


  Status -- Semi-Supported

  Some people have been	using this PCMCIA card for some	time now with
  their	notebooks. It is a basic 8390 design, much like	a NE2000. The
  LinkSys PCMCIA card and the IC-Card Ethernet (available from Midwest
  Micro) are supposedly	DE-650 clones as well.	Note that at present,
  this driver is not part of the standard kernel, and so you will have
  to do	some patching.

  See ``PCMCIA Support'' in this document, and if you can, have	a look
  at:

  Don's	PCMCIA Stuff (http://cesdis.gsfc.nasa.gov/linux/pcmcia.html)


  3.13.	 DFI



  3.13.1.  DFINET-300 and DFINET-400


  Status -- Supported

  These	cards are now detected (as of 0.99pl15)	thanks to Eberhard
  Moenkeberg emoenke@gwdg.de who noted that they use `DFI' in the first
  3 bytes of the prom, instead of using	0x57 in	bytes 14 and 15, which
  is what all the NE1000 and NE2000 cards use. (The 300	is an 8	bit
  pseudo NE1000	clone, and the 400 is a	pseudo NE2000 clone.)



  3.14.	 Digital / DEC



  3.14.1.  DEPCA, DE100, DE200/1/2, DE210, DE422


  Status -- Supported

  As of	linux v1.0, there is a driver included as standard for these
  cards. It was	written	by David C. Davies.  There is documentation
  included in the source file `depca.c', which includes	info on	how to
  use more than	one of these cards in a	machine. Note that the DE422 is
  an EISA card.	These cards are	all based on the AMD LANCE chip.  See
  ``AMD	LANCE''	for more info.	A maximum of two of the	ISA cards can be
  used,	because	they can only be set for 0x300 and 0x200 base I/O
  address.  If you are intending to do this, please read the notes in
  the driver source file depca.c in the	standard kernel	source tree.


  3.14.2.  Digital EtherWorks 3	(DE203,	DE204, DE205)


  Status -- Supported

  Included into	kernels	v1.1.62	and above is this driver, also by David
  C. Davies of DEC. These cards	use a proprietary chip from DEC, as
  opposed to the LANCE chip used in the	earlier	cards like the DE200.
  These	cards support both shared memory or programmed I/O, although you
  take about a 50%performance hit if you use PIO mode. The shared memory
  size can be set to 2kB, 32kB or 64kB,	but only 2 and 32 have been
  tested with this driver. David says that the performance is virtually
  identical between the	2kB and	32kB mode. There is more information
  (including using the driver as a loadable module) at the top of the
  driver file ewrk3.c and also in README.ewrk3.	 Both of these files
  come with the	standard kernel	distribution.

  Other	interesting notes are that it appears that David is/was	working
  on this driver for the unreleased version of Linux for the DEC Alpha
  AXP. And the standard	driver has a number of interesting ioctl() calls
  that can be used to get or clear packet statistics, read/write the
  EEPROM, change the hardware address, and the like. Hackers can see the
  source code for more info on that one.

  David	has also written a configuration utility for this card (along
  the lines of the DOS program NICSETUP.EXE) along with	other tools.
  These	can be found on	sunsite.unc.edu	in the directory
  /pub/Linux/system/Network/management -- look for the file ewrk3tools-
  X.XX.tar.gz.


  3.14.3.  DE425 (EISA), DE434,	DE435


  Status -- Supported

  These	cards are based	on the 21040 chip mentioned below.  Included
  into kernels v1.1.86 and above is this driver, also by David C. Davies
  of DEC. It sure is nice to have support from someone on the inside
  ;-) Have a read of the 21040 section for extra info.

  Note that as of 1.1.91, David	has added a compile time option	that may
  allow	non-DEC	cards (such as the ZYNX	cards) to work with this driver.
  Have a look at README.de4x5 for details.


  3.14.4.  DEC 21040, 21140, Tulip


  Status -- Supported

  The DEC 21040	is a bus-mastering single chip ethernet	solution from
  Digital, similar to AMD's PCnet chip.	The 21040 is specifically
  designed for the PCI bus architecture.  SMC's	new EtherPower PCI card
  uses this chip.  The new 21140 recently announced is for supporting
  100Base-? and	is supposed to be able to work with drivers for	the
  21040	chip.

  You have a choice of two drivers for cards based on this chip. There
  is the DE425 driver discussed	above, and the generic 21040 driver that
  Donald has written.

  To use David's de4x5 driver with non-DEC cards, have a look at
  README.de4x5 for details.

  Donald is doing his generic 21040 driver development on a SMC
  EtherPower PCI card at the moment, and this driver is	included in the
  standard kernel source as of 1.1.84.	Note that this driver is still
  considered an	alpha driver (see ``Alpha Drivers'') at	the moment, and
  should be treated as such. To	use it,	you will have to edit
  arch/i386/config.in and uncomment the	line for CONFIG_DEC_ELCP
  support.





  3.15.	 Farallon

  Farallon sells EtherWave adaptors and	transceivers. This device allows
  multiple 10baseT devices to be daisy-chained.


  3.15.1.  Farallon Etherwave


  Status -- Supported

  This is reported to be a 3c509 clone that includes the EtherWave
  transceiver. People have used	these successfully with	Linux and the
  present 3c509	driver.	They are too expensive for general use,	but are
  a great option for special cases.  Hublet prices start at $125, and
  Etherwave adds $75-$100 to the price of the board -- worth it	if you
  have pulled one wire too few,	but not	if you are two network drops
  short.


  3.16.	 Hewlett Packard


  The 272** cards use programmed I/O, similar to the NE*000 boards, but
  the data transfer port can be	`turned	off' when you aren't accessing
  it, avoiding problems	with autoprobing drivers.

  Thanks to Glenn Talbott for helping clean up the confusion in	this
  section regarding the	version	numbers	of the HP hardware.


  3.16.1.  27245A


  Status -- Supported

  8 Bit	8390 based 10BaseT, not	recommended for	all the	8 bit reasons.
  It was re-designed a couple years ago	to be highly integrated	which
  caused some changes in initialization	timing which only affected
  testing programs, not	LAN drivers. (The new card is not `ready' as
  soon after switching into and	out of loopback	mode.)


  3.16.2.  HP PC Lan+ (27247A, 27247B, 27252A)


  Status -- Supported

  The HP PC Lan+ is different to the standard HP PC Lan	card. This
  driver was added to the list of drivers in the standard kernel at
  about	v1.1.3X. Note that even	though the driver is included, the entry
  in `config.in' seems to have been omitted. If	you want to use	it, and
  it doesn't come up in	`config.in' then add the following line	to
  `config.in' under the	 `HP PCLAN support' line:


	  bool 'HP PCLAN Plus support' CONFIG_HPLAN_PLUS n



  Then run make	config;make dep;make zlilo or whatever.

  The 47B is a 16 Bit 8390 based 10BaseT w/AUI,	and the	52A is a 16 Bit
  8390 based ThinLAN w/AUI.  These cards are high performers (3c509
  speed) without the interrupt latency problems	(32K onboard RAM for TX
  or RX	packet buffering). They	both offer LAN connector autosense, data
  I/O in I/O space (simpler) or	memory mapped (faster),	and soft
  configuration.

  The 47A is the older model that existed before the `B'.  Two versions
  27247-60001 or 27247-60002 have part numbers marked on the card.
  Functionally the same	to the LAN driver, except bits in ROM to
  identify boards differ. -60002 has a jumper to allow operation in non-
  standard ISA busses (chipsets	that expect IOCHRDY early.)



  3.16.3.  HP-J2405A


  Status -- Supported

  These	are lower priced, and slightly faster than the 27247B/27252A,
  but are missing some features, such as AUI, ThinLAN connectivity, and
  boot PROM socket.  This is a fairly generic LANCE design, but	a minor
  design decision makes	it incompatible	with a generic `NE2100'	driver.
  Special support for it (including reading the	DMA channel from the
  board) is included thanks to information provided by HP's Glenn
  Talbott.

  More technical information on	LANCE based cards can be found in
  ``Notes on AMD...''


  3.16.4.  HP-Vectra On	Board Ethernet


  Status -- Supported

  The HP-Vectra	has an AMD PCnet chip on the motherboard.  Earlier
  kernel versions would	detect it as the HP-J2405A but that would fail,
  as the Vectra	doesn't	report the IRQ and DMA channel like the	J2405A.
  Get a	kernel newer than v1.1.53 to avoid this	problem.

  DMA selection	and chip numbering information can be found in ``AMD
  LANCE''.

  More technical information on	LANCE based cards can be found in
  ``Notes on AMD...''


  3.17.	 IBM / International Business Machines



  3.17.1.  IBM Thinkpad	300


  Status -- Supported

  This is compatible with the Intel based Zenith Z-note.  See ``Z-note''
  for more info.

  Supposedly this site has a comprehensive database of useful stuff for
  newer	versions of the	Thinkpad. I haven't checked it out myself yet.

  Thinkpad-info	(http://peipa.essex.ac.uk/html/linux-thinkpad.html)

  For those without a WWW browser handy, try
  peipa.essex.ac.uk:/pub/tp750/


  3.17.2.  IBM Credit Card Adaptor for Ethernet


  Status -- Semi-Supported

  People have been using this PCMCIA card with Linux as	well.  Similar
  points apply,	those being that you need a supported PCMCIA chipset on
  your notebook, and that you will have	to patch the PCMCIA support into
  the standard kernel.

  See ``PCMCIA Support'' in this document, and if you can, have	a look
  at:

  Don's	PCMCIA Stuff (http://cesdis.gsfc.nasa.gov/linux/pcmcia.html)



  3.18.	 Intel Ethernet	Cards



  3.18.1.  Ether Express


  Status -- Semi-Supported

  This card uses the intel i82586. (Surprise, huh?)  The driver	is in
  the standard release of the kernel, as an alpha driver. See ``Alpha
  Drivers'' for	important information on using alpha-test ethernet
  drivers with Linux.

  The reason is	that the driver	works well with	slow machines, but the
  i82586 occasionally hangs from the packet buffer contention that a
  fast machine can cause.  One reported	hack/fix is to change all of the
  outw() calls to outw_p(). Also, the driver is	missing	promiscuous and
  multicast modes. (See	``Multicast and...'')

  There	is also	the standard way of using the chip (read slower) that is
  described in the chip	manual,	and used in other i82586 drivers, but
  this would require a re-write	of the entire driver.

  There	is some	technical information available	on the i82586 in
  ``Programming	the Intel Chips'' and also in the source code for the
  driver `eexpress.c'. Don't be	afraid to read it. ;-)


  3.18.2.  Ether Express PRO


  Status -- Not-Supported

  This card uses the Intel 82595. If it	is as ugly to use as the i82586,
  then don't count on anybody writing a	driver.


  3.19.	 LinkSys



  3.19.1.  LinkSys PCMCIA Adaptor


  Status -- Semi-Supported

  This is supposed to be a re-badged DE-650. See the information on the
  DE-650 in ``DE-650''.
  3.20.	 Microdyne



  3.20.1.  Microdyne Exos 205T


  Status -- Not-Supported

  Another i82586 based card. At	one point, dabn100@hermes.cam.ac.uk had
  written a driver that	``almost worked'' that was based on the	3c507
  code.	More details as	they are received...


  3.21.	 Mylex



  3.21.1.  Mylex LNP101, LNP104


  Status -- Semi-Supported

  These	are PCI	cards that are based on	DEC's 21040 chip. The LNP104
  uses the 21050 chip to deliver four independent 10BaseT ports. The
  standard LNP101 is selectable	between	10BaseT, 10Base2 and 10Base5
  output.  The LNP101 card should work with the	generic	21040 driver,
  but nobody has verified this yet. As for the LNP 104,	well...

  See the section on the 21040 chip (``DEC 21040'') for	more
  information.

  Mylex	can be reached at the following	numbers, in case anyone	wants to
  ask them anything.


	  MYLEX	CORPORATION, Fremont
	  Sales:  800-77-MYLEX,	(510) 796-6100
	  FAX:	  (510)	745-8016.




  3.22.	 Novell	Ethernet, NExxxx and associated	clones.


  The prefix `NE' came from Novell Ethernet. Novell followed the
  cheapest NatSemi databook design and sold the	manufacturing rights
  (spun	off?) Eagle, just to get reasonably-priced ethercards into the
  market. (The now ubiquitous NE2000 card.)

---End of part 1/3---