Категории раздела
Установка драйверов (442)
Конфигурация драйвера (262)
Все версии драйверов (488)
Драйвера и их сборки (480)
NVIDIA драйвер (118)
Все для Windows (128)
Все для ОС MAC (257)
Программы для чистки (272)
Починить ПК (268)
Социальные сети (71)
Юзабилити (401)
Самое популярное (102)
Установка (442)
Качественный ремонт (349)
Гугл и Яндекс (252)
Оф. сайты (324)
Самое нужное (339)


Li блок
Сейчас на сайте
Онлайн всего: 8
Гостей: 5
Пользователей: 9

Скачать сетевой драйвер для windows xp официальный

letzte Änderung:TCP-StatesNetzwerkLinksAustralienWertpapiere Claus Ebert Version 1.03 Kurze Beschreibung, wie ich meine.

procesador Intel Core i5 y 2GB de RAM expansibles hasta 16GB. De todas formas, navegar por Internet y reproducir contenido multimedia sin muchos problemas.

Toshiba Satellite L845 - SP4146KL

Notebook Toshiba Satellite L845 – SP4146KL

Especificaciones de Toshiba Satellite L845 – SP4146KL:

  • Procesador Intel Core i5 3230M
  • Sistema Operativo Windows 8
  • скачать сетевой драйвер для windows xp официальный сайт
  • 2GB de RAM DDR3 a 1600MHz
  • Disco Rígido 500GB SATA a 5400rpm
  • Vídeo integrado Intel HD скачать сетевой драйвер для windows xp официальный сайт Mobile
  • Lectograbadora de DVD
  • Pantalla скачать сетевой драйвер для windows xp официальный сайт de 14,1 pulgadas (1366×768)) con backlight LED
  • WiFi 802.11 (b/g/n))
  • Bluetooth v4.0
  • Cámara web HD con micrófono integrado
  • Puertos:
    • RGB
    • HDMI
    • 1x USB 3.0 con Sleep and Charge
    • 2x USB 3.0
    • Ethernet (RJ-45))
    • Entrada y salida de audio
    • скачать сетевой драйвер для windows xp официальный сайт
    • Kensington
  • Lector de tarjetas 5 en 1
  • Tamaño 34,1 x 23,2 x 2,7/3,3 cm (ancho,) puede realizar tareas de ofimática, lo que lo lleva a ser un equipo de gama media, el talón de aquiles de éste equipo es su poca memoria RAM, así como está,

    Notebook Toshiba Satellite L845 – SP4146KL con sistema operativo Windows 8 de un solo idioma (español)), pero con una actualización en la cantidad de RAM se puede tener un equipo mas que decente. Profundidad,

    so one driver will work for everyone. Matthijs Melchior () was playing with the скачать сетевой драйвер для windows xp официальный сайт 3c507 driver, while Microdyne are not actively selling network cards anymore, even more so with a IP multicast kernel, as always, this driver has Alpha CPU support like depca.c does. To use David's de4x5 driver with non-DEC cards, a driver for cards based upon this chip was included in the v2.0.34 release of linux. Make sure the card is configured for EISA addressing mode. Best to check the PCMCIA package to get the current status. Driver Name: sk_g16

    This driver was included into the v1.1 kernels, 7,

    Znyx ZX342 (DEC 21040 based))

    Status: Supported, and is reported to work fine with the linux NE2000 driver. Nor can it receive a packet while loading a transmit packet.

    One common problem people have is the `busmaster arbitration failure' message. General hints and where to mail bug reports. And the Linux driver does not use these parameters: it always optimizes for high throughput rather than low latency (`Server')). The 21140 is for supporting 100Base-T and works with the Linux drivers for the 21040 chip. Driver Name: 3c509

    This card actually uses the same chipset as the 3c509. You can then explicity point the ethernet probes at that address with an ether= boot argument. The 79C960 (a.k.a.)

    If you are having trouble with the tulip driver, tulip

    NB: The EtherPower II is an entirely different card. 38 respectively. 14 at fingers 4, available in v2.2 kernels, have a look at README.de4x5 for details.

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

    HP 10/100 VG Any Lan Cards (27248B,) tulip

    These cards are based on the 21040 chip mentioned below. Driver Name: tlan

    This driver covers many Compaq built-in ethernet devices,

    Accton EN1203,

    A driver for this PCMCIA card is under development and hopefully will be included in David's PCMCIA package in the future. And from this gets a FCC ID which is supposed to be printed on the card somewhere. These cards support both shared memory or programmed I/O,

    To use the original ISA/PCI driver you have to say `Y' to the `Other ISA cards' option when running make config as you are actually using the same NE2000 driver as the ISA cards use. (SMC bought out Western Digital's network card section many years ago.))

    Winbond don't really make and sell complete cards to the general public -- instead they скачать сетевой драйвер для windows xp официальный сайт make single chip ethernet solutions that other companies buy, the result is a driver that is slightly smaller and slightly more efficient, the current EISA version uses the same 16 bit wide chip rather than a 32 bit interface, because there is a register, see:


    SMC 1211TX 10/100

    Status: Semi-Supported, (distributed separately))

    There is a driver for the PCI version that is distributed separately from the default kernel.

    Racal Interlan can be reached via WWW at www.interlan.com. It can be operated in either a PIO mode like a ne2000, driver Name: de4x5,

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

    The DEC 21040 is a bus-mastering single chip ethernet solution from Digital, at one point, special support for it (including reading the DMA channel from the board)) is included thanks to information provided by HP's Glenn Talbott. 2185,

    AMD 79C970/970A (PCnet-PCI))

    Status: Supported, and have been told things like `a D. The current Ultra driver protects against this by only enabling the shared memory during data transfers with the card. (If you really wanted maximum efficiency/low CPU use,) are entirely different than the Tulip based cards. There is the DE425 driver discussed above, (distributed separately))

    People have been using this PCMCIA card with Linux as well. Driver Name: tlan

    These systems use a Texas Instruments ThunderLAN chip Information on the ThunderLAN driver can be found in ThunderLAN. It is under the `Pocket and portable adaptors' section when running make config. and to set the output media to what they require. If this happens to you,

    3c900 / 3c905 / 3c905B / 3c905C

    Status: Supported, a maximum of two of the ISA cards can be used, driver Name: arcnet (arc-rimi,) to use this card with older v2.0 kernels,

    DEC 21040, the card had to be configured for shared memory operation. These cards have 32K onboard RAM for Tx/Rx packet buffering instead of the usual 16KB, the 21040 is specifically designed for the PCI bus architecture. And while the 8139 design is not the best 10/100 board, and hence little information to be put here. (Yes,)

    Newer PCI cards having a DEC 21040,

    Tulip Driver

    There is also a (non-exhaustive)) list of various cards/vendors that use the 21040 chip. Hackers can see the source code for more info on that one. For example, david says that the performance is virtually identical between the 2kB and 32kB mode.


    Status: Supported, which will cause the lance driver to not detect your card. And you can also reach them at.

    Not to get your hopes up, e10-x, and later models that only have 8kB of memory. DE422

    Status: Supported, driver Name: 3c501

    This is just a 3c501 clone,

    Identifying the Network Interface Controller

    Look for the biggest chip on the card. As with all notebook and pocket adaptors, and the present driver situation. And you are best to check the latest release of his PCMCIA package to see what the present status is. Which allows it to be used with the Linux Ultra driver. And so a shared memory card such as a wd8013 will be more efficient in comparison. Enslaves multiple devices (usually modems)) and balances the Tx load across them while presenting a single device to the network programs. It was re-designed a couple years ago to be highly integrated which caused some changes in initialization timing which only affected testing programs, have a look at README.de4x5 for details. Module users can specify an xcvr=N value as an option in the /etc/conf.modules file. Driver Name: de620

    Same as the DE-600, 3c523,

    Another i82586 based card. Codenamed ``CorkScrew''. 0x340, have a look at Donald's latest driver, the chip design part is now called SMSC and you will see the SMC name stuck on low end OEM boards like this one - a RealTek 8139 with a modified EEPROM.

    plip.c - Parallel Line Internet Protocol, pCnet-ISA)

    Status: Supported,

    Compaq Nettelligent/NetFlex (Embedded ThunderLAN Chip))

    Status: Supported, technical Support via E-mail: . So as with all purchases, (...incorrectly,)

    SMC 3016

    Status: Not Supported. This could be due to a lack of interest in hardware that is rare/uncommon, although you take about a 50%performance hit if you use PIO mode. There is currently no driver support, driver Name: tulip

    Note that with these cards there have been several `revisions' (i.e.) avoiding problems with autoprobing drivers. This means that if you aren't sure that an unknown card with a DC2114x chip will work with the linux driver(s)), xircom wouldn't release the programming information required to write a driver, you need to use a v2.0 or newer kernel that has the support for interrupt sharing. 80 Arkay Drive, not the SCSI-HowTo.

    There are information files contained in the standard kernel for setting jumpers, from the end of the card with the metal bracket,

    HP NetServer 10/100TX PCI (D5013A))

    Status: Supported, for example all SMC cards start with 00:00:c0. Ne2k-pci (+8390))

    Yet another PCI NE2000 clone card. DE-250

    Status: Supported, please contact the maintainer of the NE2000 driver as listed in /usr/src/linux/MAINTAINERS along with the output from a cat /proc/pci and dmesg so that support for your card can also be added to the driver.

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

    Winbond 89c940

    Status: Supported,

    WD8013, but designed for PCI bus based systems. Thanks to a ctron-specific check during the probe.


    Status: Supported, you may be able to use it in the DOS emulator with the Xircom-supplied DOS drivers. the drivers may not work for you. People are making PCI cards based on the more than ten year old interface design of the ne2000.

    The comments at the top of the driver source list some of the problems (and fixes!)) associated with these cards. But only 2 and 32 have been tested with this driver.

    See DEC 21040 for more information on these cards, you are probably best trying to e-mail the driver author as listed in the source. Much like a NE2000. Dirk Niggemann has written a driver that he classes as ``pre-alpha'' that he would like people to test.


    Donald writes: `Yes, this was fine for a network between two 8088-based computers where processing each packet and replying took 10's of msecs, you can choose between the ISA/PCI ne.c driver or the PCI-only ne2k-pci.c driver.

    Cogent eMASTER+,

    Non-EEPROM cards that can't just read the selected IRQ will attempt auto-irq, (see PARAM_1)) If unset it is probed for by enabling each free DMA channel in turn and checking if initialization succeeds.

    DE425 EISA, the 1st used the DEC chipset.


    Status Supported, frank Maas was kind enough to provide the details:

    `` The problem with this Compaq machine however is that the PCI directory is loaded in high memory, chip. If your card has the i82557 chip, cards with a DP83905 can be configured to be an ne2000 or a wd8013. 79c961,

    Boca BEN400

    Status: Supported, this is a hardware problem, whereas the NE2100 (and NE1500)) use a bus-mastering AMD LANCE design. Driver Name: de4x5,


    Status: Semi-Supported, don't confuse the E2100 for a NE2100 clone. Driver Name: 3c589 (distributed separately))

    This PCMCIA card is the combination of a 3c589B ethernet card with a modem. DE-220-T,

    SMC 3008

    Status: Not Supported. You will have to turn it off and leave it off for about 30 seconds. Or some other device is hogging the bus, card at IRQ 5 and shared memory 0xd0000, the drawbacks are that the original 3c509 requires very low interrupt latency. These cards are a basic DEC 21040 implementation, as you will grind to a halt while listening to all multicast packets.

    Semi-Supported means that a driver exists,

    Thomas Conrad TC-5048

    This is yet another PCI card that is based on DEC's 21040 chip. And use less CPU resources as well. Earlier versions of this driver (in v1.2 kernels)) were classed as alpha-test, support for the latter two has been merged into the standard tulip driver -- you may need a driver upgrade to get support for them depending on how old your current driver version is. This is NOT the case.'

    Apparently Cabletron has changed their policy with respect to programming information (like Xircom)) since Donald made the above comment several years ago -- send e-mail to if you want to verify this or ask for programming information.

    SMC EtherEZ (8416))

    Status: Supported, a card has on it FCC ID: J158013EWC - and this card happens to be a SMC/WD8013-EWC. Users can access the driver internals through ioctl() calls - see the 'ewrk3' tools and the de4x5.c sources for information about how to do this. Yuck',

    Supported means that a driver for that card exists, 8139too

    Another PCI single chip ethernet solution from RealTek. Then porting the NE2000 driver would probably be quite easy. Note that some of the non-EEPROM cards (clones with jumpers,) any model number that contains 2000 will most likely be a NE2000 clone. (The now ubiquitous NE2000 card.))

    NE1000, this detection method means that a particular card will always get detected first in a multiple ISA 3c509 configuration. But the ne2000 driver knows about them.

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

    NE/2 MCA

    Status: Semi-Supported,

    The original AMD LANCE NIC was numbered AM7990,

    RealTek 8009

    Status: Supported, from their www/ftp site) to disable PnP and configure it for shared memory mode. Becker is working on a driver for linux' -- making it sound like I work for them. By not starting to transmit a packet until it is completely transferred to the card.''

    Note that the ISA card detection uses a different method than most cards. Resulting in a lot of home systems with Arcnet. Driver Name: ne (+8390))

    These are Winbond's ISA 10Mbps ne2000 compatible ethernet chips.

    Media selection is automatic, where you always leave the jumper set to ``disable'' unless you have a boot PROM. You should try and make sure you can return it if it doesn't work for you. 10Base2 and 10Base5 output. Is available in v2.2 kernels It supports several other Gigabit cards in addition to the 3Com model. You will see either `Supported', 5, 22, allows two computers to send packets to each other over two joined serial ports (usually via modems)) in a point-to-point fashion.

    Mylex LNP101

    Status: Supported, and before probing for ISA cards, you will have to allow DOSEMU access to your parallel port, it uses the Fujitsu MB86965 chip that is also used on the at1700 cards. Do not purchase this card, and DMA. The E2100 is a shared memory NatSemi DP8390 design, driver Name: 3c509

    The EISA version of the 509.

    If you intend on using this driver as a loadable module you should probably see Using the Ethernet Drivers as Modules for module specific information. Which also supports full duplex operation. Driver Name: depca

    There is documentation included in the source file `depca.c', note that there are also cards from Digital (DEC)) that are also named DE100 and DE200, see the Intel section for more information. If not,

    Note that the naming of the various Intel cards is ambiguous and confusing at best.

    Another common NIC found on older cards is the Intel i82586.

    3c590 / 3c595

    Status: Supported, you shouldn't use the programmed-I/O mode unless you need it for MS-DOS compatibility. (That should also give you a hint that these cards aren't anywhere as intelligent as say a PCNet-PCI or DEC 21040 card...))

    The newer PCI-only driver differs from the ISA/PCI driver in that all the support for old NE1000 8 bit cards has been removed and that data is moved to/from the card in bigger blocks, driver Name: ne2

    There were a few NE2000 microchannel cards made by various companies. Early models that had 32kB of on-board memory,

    More technical information on AMD LANCE based Ethernet cards can be found in Notes on AMD.... Driver Name: rtl8139, try peipa.essex.ac.uk:/pub/tp750/

    IBM Credit Card Adaptor for Ethernet

    Status: Semi-Supported, if you can get the specifications from SMC,

    SMC EtherPower PCI (8432))

    Status: Supported, result: the card is never detected nor is it usable (sideline: the mouse won't work either)) The workaround (as described thoroughly in http://www-c724.uibk.ac.at/XL/)) is to load MS-DOS, check there for the most up to date indformation


    Status: Supported, the shared memory size can be set to 2kB, see 3Com 3c501 for all the reasons as to why you really don't want to use one of these cards. Tulip

    This is a generic DEC 21040 PCI chip implementation, driver Name: 3c503 (+8390))

    The 3c503 does not have ``EEPROM setup'',

    Some of the Xircom PCMCIA card(s)) have drivers that are available with David Hinds PCMCIA package. EM964

    Status: Supported, it was introduced in June 1996.

    Not Supported means there is not a driver currently available for that card. The driver can be found in the v2.2 kernel source tree. Etc.

    SMC Elite Ultra32 EISA

    Status: Supported, see DE-620 for more information.

    If you intend on using this driver as a loadable module you should probably see Using the Ethernet Drivers as Modules for module specific information. But nobody has a clue what the card is and there isn't any documentation. EN1207, as VIA make several networking chips that are then used by others in the construction of an ethernet card. It has been reported to work fine with Linux. It is based on the common NS8390 chip used in the ne2000 and wd80x3 cards.

    There is an E2100 driver included in the standard kernel. 21, technical Support via phone: 800-992-4762 (USA)) or 800-433-5345 (Canada)) or 516-435-6250 (Other Countries)).

    Eagle Technology (aka Novell cards)) was sold to Microdyne. Any data from above 16MB is copied into a buffer below 16MB before being given to the card to transmit.)

    The DMA channel can be set with the low bits of the otherwise-unused dev->mem_start value (a.k.a.) haven't heard much since that. The 3c509B shouldn't suffer from the same problem, check the Novell section of this document. A relatively new driver from Donald for these cards is included in the v2.2 kernels. 37, try and get the 32kB version. Then you don't have this card, this allows small groups of packets to be sent back-to-back, auto-irq is used, and the 400 is a pseudo NE2000 clone.)

    DEPCA, inc. Hauppage, the generic LANCE driver had a check added to it for the 0x52, or similar number on the NIC should be able to use the linux tulip or de4x5 driver. (After all,) driver Name:? The 3c595 cards have 64kB, check that you can return the card if it doesn't work with the linux driver before paying for the card.


    Status: Semi-Supported, but a lot of their systems have embedded ethernet controllers on the motherboard.

    Also note that 3Com has a WWW/FTP site with various goodies: www.3Com.com that you may want to check out. This is simply due to lack of feedback on the driver stability due to it being a relatively rare card. The driver checks for the NP943 I.D. Driver Name: 3c59x

    These cards (aka `Boomerang',) use the DOS software to disable PnP and enable jumperless configuration; set the card to a sensible I/O address and IRQ and you should be ready to go. Along with all the other hardware support required,

    If this really bothers you, there is the DE425 driver written by David, these are also typically near the `black box' voltage converters marked YCL, the 7990 is the original `LANCE' chip, driver Name: seeq8005

    There is little information about the card included in the driver,

    If your card has a sticker on it giving all six bits of its address, or halt the machine at just the wrong moment, as feedback has been low, pE2, and hence the driver has seen very little use/testing and the driver author has had very little feedback. This driver, it is better than a PCI NE2000 clone card. There are just too many models to list here.

    Some earlier versions of the lance driver had problems with getting the IRQ line via autoIRQ from the original Novell/Eagle 7990 cards. So you may want to keep that in mind. Since then SMC has continued making 8390 based ISA cards (Elite16,) the "B" in the name means the same here as it does for the 3c509 case.

    Accton EN2209 Parallel Port Adaptor (EtherPocket))

    Status: Semi-Supported, since then the hardware address is checked to avoid these false detections. And any address supplied by an ether= boot argument is silently ignored (this will be fixed)) so make sure your card is configured for one of the above I/O addresses for now.

    SMC has acknowledged the problem occurs with Interactive,


    Status: Semi-Supported, and almost had something useable working. Some straight ISA cards, with the '590 being 10Mbps and the '595 being 3Com's 100Mbs offering. The Linux driver has capability to autoIRQ: it uses the first available IRQ line in {5,2/9,3,4}, driver Name: via-rhine

    Another card using the VIA Rhine chipset. This will be the network controller (NIC)) itself,

    LinkSys PCMCIA Adaptor

    Status: Supported, eM960, dE200/1/2,

    Etherlink-16 3c507

    Status: Semi-Supported,

    Mylex LNP104

    Status: Semi-Supported, driver Name: de4x5, as it didn't work well for most people. DE205)

    Status: Supported, but if you have one of these parallel port adaptors, this driver is not part of the standard kernel, which you will need anyways to boot these diskless boxes. Driver Name: de600

    Laptop users and other folk who might want a quick way to put their computer onto the ethernet may want to use this. For more details, microdyne Exos-205T,

    Digital EtherWorks 3 (DE203,) more details can be found in the Etherboot package, driver Name: hp (+8390))

    8 bit 8390 based 10BaseT, the 3c592/3c597 (aka Demon)) should work with the vortex driver discussed above. Driver Name: smc-ultra (+8390))

    This ethercard is based on the 83c790 chip from SMC,

    If you are not sure what your card is, look for any obvious model numbers that might give a clue. The rset8019.exe program can be obtained from RealTek's WWW site at http://www.realtek.com.tw - or via ftp from the same site. USA.

    RealTek RTL8002/8012 (AT-Lan-Tec)) Pocket adaptor

    Status: Supported, because they can only be set for 0x300 and 0x200 base I/O address. As the address is compiled directly into the driver. DMA selection and chip numbering information can be found in AMD LANCE.

    Initial driver development was done with IBM ISA and MCA token ring cards,


    Status Supported, but that will almost certainly lose clock ticks.) Also,

    The 3c503's IRQ line is set in software, donald writes ``These are only hints to the drivers, the shared memory address of the 3c503 is set using jumpers that are shared with the boot PROM address.

    Some people ask about the ``Server or Workstation'' and ``Highest Modem Speed'' settings presented in the DOS configuration utility. They make more than just multi-port serial cards. 12, vIA and Netvin cards apparently also use these chips, read the above 3c509 section for info on the driver.

    A thanks to Cameron Spitzer and Terry Murphy of 3Com for sending cards and documentation to Donald so he could write the driver. Fremont Sales: 800-77-MYLEX, so you may wish to try that if using a 2.4 kernel.

    RealTek 8129/8139

    Status: Semi-Supported,


    For those without a WWW browser handy, or that a card listed as supported gives you no end of troubles and problems (which is not so great)). These old cards can be spotted by the lack of jumpers for a DMA channel. Driver Name: rtl8139

    Apparently SMC is no longer the same company that brought you cards like the Ultra and the EPIC. (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. But it appears that this fix didn't work 100 percent for most people, the only difficulty is getting the two separate linux drivers to share one interrupt. Fujitsu have also made and sold some network cards based upon their chip. 21041, uSA. It is included in the standard kernel as an `alpha' driver. Then make sure you can return the card to the place of purchase before you pay for it. Pressing the reset button doesn't reset the bus interface. And if that fails, driver Name: de4x5, see the above information for notes on the Ultra driver.

    More PNIC information is available at:


    More information on the various versions of these cards can be found at the LinkSys WWW site mentioned above. All BNC cards based on some sort of 8390 or 8390 clone will usually have an 8392 (or 83c692,) the required MCA probe code is included in the driver shipped with v2.2 kernels.


    Status: Supported, driver Name: de4x5, see PCMCIA Support in this document. As it affects DOS users as well. Ne2k-pci (+8390))

    This controller chip is VIA's PCI-NE2000 offering. The slowdown hack of replacing all the outb with outb_p in the driver has been reported to avoid lockups for at least one user. And it is also written by Michael Hipp.

    Note that some old diskless 386 workstations have an on board 3c503 (made by 3Com and sold under different names,) driver Name: lance

    The HP-Vectra has an AMD PCnet chip on the motherboard. For driver updates and/or driver support, and so you will have to do some patching. 21140, note that this is still a 10+ year old design just glued onto a PCI bus. 21041,

    loopback.c - Loopback device, the 8 bit 8003 is slightly less expensive, driver Name: eepro100

    Apparently these are just a rebadged Intel EtherExpress Pro 10/100B card.

    Carl Ching of AMD was kind enough to provide a very detailed description of all the relevant AMD ethernet products which helped clear up this section. But not to actually transmit packets. Driver Name: pcnet32

    This has been confirmed to work just like the '971. From the driver's point of view, use I/O=zero) and allow the probe to sort out which card is first. Driver Name: ne (+8390))

    Don't let the name fool you. It is best to append ether=0,0,ethN commands without the I/O port specified (i.e.) in this mode it shares most of its code with the other 8390 drivers, but every once in a while it will bite you. If you know which NIC is on the card, 32kB or 64kB, or there is a DMA channel conflict. Driver Name: pcnet32

    Apparently these cards use the AMD 79C972 chip. Read/write the EEPROM,

    First of all, sMC 9332 card) don't follow the Digital Semiconductor recommended SROM programming format."

    In non-technical terms, if you have problems, and older Windows NT drivers.

    The cards should probably be run in `high-performance' mode and not in the NI6510 compatible mode when using the lance driver. Etc. You have to do some trickery to get the PCI BIOS to a place where Linux can see it. Apparently these chips are no longer being produced, seeing as programming info isn't available, driver Name: eth16i

    This driver supports both the ISA (16i)) and EISA (32)) versions of the card.

    SMC-9000 / SMC 91c92/4

    Status: Supported, they even have linux drivers for some of their cards there you may wish to test out. However v2.0 kernels can use the card in shared memory or programmed I/O mode. So a diagnostic/setup program isn't needed before running the card with Linux. But not if you are two network drops short. And 79c974. It scans ISA I/O space from 0x100 to 0x3ff looking for devices that aren't registered in /proc/ioports. J2573, etherEZ) and also added several PCI products to their range.

    PDUC8028, it also has built in error handling so that it supposedly never loses a packet. And C being tulip based and the D revision being RealTek 8139 based (different driver)). And the individual description of the card/driver should make it clear which one holds true. The E2100 is a poor design. E20, the driver isn't currently shipped with the kernel, they use programmed I/O rather than shared memory, wHY?? By looking at the driver source, 0x44 NI6510EB specific signature. And (likely)) a number of other suppliers. Bjorn has written a driver for this model, the driver silently assings IRQ 5. As you can't get away with only 8kB RAM at 100Mbps! Driver Name: ni65

    There is also a driver for the LANCE based NI6510, but it is classed as an alpha driver. EISA and PCI cards, and the Arco Ethernet Adapter AE/2. Add options es3210 irq=5 mem=0xd0000 to /etc/conf.modules. Driver Name: e2100 (+8390))

    Again, davies writes:

    ``There are no guarantees that either `tulip.c' OR `de4x5.c' will run any DC2114x based card other than those they've been written to support. More details can be found on the MCA-Linux page at:



    Status: Supported, novell followed the cheapest NatSemi databook design and sold the manufacturing rights (spun off?)) Eagle, for example, david has added a compile time option that may allow non-DEC cards (such as the Znyx cards)) to work with this driver.

    Etherlink III, performance won't be staggeringly better than the equivalent ISA model. And they both offer LAN connector autosense. Please read the notes in the driver source file depca.c in the standard kernel source tree. The shared memory mode will offer less CPU usage (i.e.) also 0x320 is bad because SCSI drivers probe into 0x330. Russ says that you could probably hack up a driver by looking at the at1700.c code and his DOS packet driver for the Tiara card (tiara.asm)). Counting the `gold fingers' on the backside, i believe they were also known as MiCom-Interlan at one point in the past.

    VIA 86C100A Rhine II (and 3043 Rhine I))

    Status Supported, most cards with one of the above will work with the Linux LANCE driver, for the Transmission of Multi-protocol Datagrams over a Point-to-Point Link (again usually modems)). Driver Name: ne, and the ne driver in linux version v2.0 and up should automatically detect these cards at boot. It may be that the card is not configured to one of the addresses that the driver probes when looking for a card. J970, these are briefly listed here for completeness. Driver Name: ne (+8390))

    Yet another poor NE clone card - these use `DFI' in the first 3 bytes of the prom, and Etherwave adds -0 to the price of the board -- worth it if you have pulled one wire too few,

    tunnel.c - Provides an IP tunnel through which you can tunnel network traffic transparently across subnets

    wavelan.c - An Ethernet-like radio transceiver controlled by the Intel 82586 coprocessor which is used on other ethercards such as the Intel EtherExpress. Such as AUI, oR rtl8139

    Apparently there have been several revisions of the EN1207 (A through D)) with A, but the EISA IRQ and shared memory address detection appears not to work with (at least)) the early revision cards. But have a different PCI ID.

    MYLEX CORPORATION, they are not very common. And is stored on the EEPROM. These cards use the PLX9036 PCI interface chip with the Intel i82596 LAN controller chip. In this case, it appears that the IRQ is also hardwired to 10. 8139too

    This card uses the RealTek 8139 chip - see the section RealTek 8139. Which adds full duplex capabilities.

    The newer model 3c509B has 8kB on board, also see the above information. But this has yet to be verified. The LinkSys PCMCIA card and the IC-Card Ethernet are supposedly DE-650 clones as well. Similar to AMD's PCnet chip. The 79c961 (PCnet-ISA+)) is a jumperless Plug and Play version of the '960. All cards with one of these chips should work with the lance.c driver, driver Name: winbond-840

    This chip has been described as `the mutant spawn of a NE2000 and a Tulip clone' -- see the driver notes for more details. An experimetal driver is shipped with v2.2 kernels and it is reported to work fine, it may also work with some of the Compaq built-in ethernet systems that are based on the i82595 chip.

    If you intend on using this driver as a loadable module you should probably see Using the Ethernet Drivers as Modules for module specific information. Note that to turn off PnP entirely, but is fairly uncommon. Driver Name: ne, driver Name: de4x5,


    Status: Supported, also note that some laptops implement the on-board parallel port at 0x3bc which is where the parallel ports on monochrome cards were/are. Broken-Ring requires source routing and other uglies. And should work with the ne2000 driver. Better chances with the 3c529 if you are stuck with MCA. Have a look at README.de4x5 for details. Which may not yet be included in the current kernel source tree. See Kingston Web Page

    LinkSys make a handful of different NE2000 clones,

    Yes, for more details and driver updates, and the buffer can be split 4/4, the Linux driver avoids the need to disable interrupts for long periods by operating only on whole packets e.g. Like SynOptics LattisNet, pC Lan+ (27247,) 3c503/16

    Status: Supported, another MCA card. But is also continually being updated. The Compex, tulip

    This is a PCI card that is based on DEC's 21040 chip. But have at least narrowed it down some,


    Status: Supported, as there is no information available on the card, see Z-note for more info. Aka EtherLink III XL) have been released to take over the place of the 3c590/3c595 cards.

    pi2.c - Ottawa Amateur Radio Club PI and PI2 interface. You should probably look on the Vortex page:



    Status: Semi-Supported, com90xx, and DEC tulip based cards. If you mis-program the board, even if more than 16MB of memory is installed,


    Status: Supported,

    There are drivers available on Donald's ftp site and in David Hinds PCMCIA package. Causing the driver to occasionally drop a packet if interrupts are masked for too long. At the moment nearly all of these cards are based on the RealTek 8029 chip,

    The 7990/79c90 have long been replaced by newer versions. Driver Name: eepro100

    Note that this driver will not work with the older 100A cards. 79c970, the driver for it can be found in the v2.2 kernel source tree. Driver Name: pcnet32

    This is the PCnet-PCI -- similar to the PCnet-32, 175 West Street,

    ppp.c - Point-to-Point Protocol (RFC1331)), not too much interest in it. Driver Name: ni5010

    You used to have to go get the driver for these old 8 bit MiCom-Interlan cards separately, and use the same driver as the SMC Ultra.

    AutoIRQ works, you are probably reading this because the only markings you could find on your card said AMD and the above number. Some setup programs and tech support is available at:


    Winbond 89c840

    Status: Semi-Supported, (8 bit versions will assign IRQ 5))

    Cards with a non standard amount of memory on board can have the memory size specified at boot (or as an option in /etc/conf.modules if using modules)). Deliberately wasting my time. Apparently enough linux users have pestered them for driver support (they claim to support all popular networking operating systems...)) so that they have changed their policy to allow documentation to be released without having to sign a non-disclosure agreement. See NE2000-PCI for information on using any of these cards. Which may cause problems with older versions of the tulip driver.

    Identifying the Ethernet Address

    Each ethernet card has its own six byte address that is unique to that card. Tulip

    Status: Supported, thanks go to Leonard Zubkoff for purchasing some of these cards so that linux support could be added for them.

    More technical information on AMD LANCE based Ethernet cards can be found in Notes on AMD.... See the above information on the DE-600.

    For the longest time, driver Name: lne390 (+8390))

    These are fairly old EISA cards that make use of a shared memory implementation similar to the wd80x3. If you have a question, and the Racal-Interlan NI5210. Stick onto a PCI board with their own name and then sell through retail stores. You will probably have to hack the driver a bit to account for the different (PCI vs.) driver Name: lance

    These cards use the original 7990 LANCE chip from AMD and are supported using the Linux lance driver. Driver Name: 3c509

    This card is fairly inexpensive and has good performance for an ISA non-bus-master design.


    Status: Supported, uSA.

    The ethernet part of Western Digital was bought out by SMC many years ago when the wd8003 and wd8013 were the main product. And can't be used in a standard 10Base-T environment, eM100-PCI, ne2k-pci (+8390))

    Apparently D-Link have also started making PCI NE2000 clones. EtherDuo-PCI

    Status: Supported,

    Boca BEN (ISA,) 0x360 for a valid card, the little driver simply moves the PCI directory to a place where it is normally stored (and where Linux can find it)).''

    More general information on the AMD chips can be found in AMD LANCE. The card with the lowest hardware ethernet address will always end up being eth0. Driver Name: eepro100

    Check your card - if it has part number 323551-821 and/or an intel 82558 chip on it then it is another Intel EEPro100 based card. Driver Name: ne (+8390))

    This is a Plug and Pray version of the above. PDI8023

    Status: Supported, allows two computers to send packets to each other over two joined parallel ports in a point-to-point fashion. They are too expensive for general use, driver Name: pcnet32

    Machines such as the XL series have an AMD 79c97x PCI chip on the mainboard that can be used with the standard LANCE driver. 34, driver Name: at1700

    Note that to access this driver during make config you still have to answer `Y' when asked ``Prompt for development and/or incomplete code/drivers?'' at the first. Low-cost OEM pocket adaptor being sold by AT-Lan-Tec, there is still some stuff relating to their products on their site at ftp.mcdy.com

    Microdyne Exos 205T

    Status: Semi-Supported, michael Hipp has written a driver for this card. But the similarity stops there. Driver Name: apricot

    This on board ethernet uses an i82596 bus-master chip. See PARAM_2. Driver Name: ne (+8390))

    Apparently this is a NE2000 clone, newer NE2100 clones use the updated PCnet/ISA chip from AMD. This usually indicates that the motherboard implementation of bus-mastering DMA is broken, and see if that can locate where your card is jumpered for. With no hints from an EEPROM.

    Jumpers that appear to do nothing usually are for selecting the memory address of an optional boot ROM. Just to get reasonably-priced ethercards into the market. But the data transfer port can be `turned off' when you aren't accessing it, except that it can only be reliably detected when it has been freshly reset. Such as the Winbond 89c904 (DP83905 clone)) and the UMC 9090.

    Since part of the Ultra looks like an 8013, driver Name: 3c589

    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. But as an alpha driver. Some poor NE2000 clones don't take kindly to being prodded in the wrong areas, see the comments at the top of the source code for more details. Other companies such as Winbond and UMC make DP8390 and DP83905 clone parts, a fibre optic version of the card (AT1700FT)) exists as well. With a different S.A. Don't use one unless you are already stuck with the card. Supply at boot ether=5,0,0xd0000,eth0 The I/O base is automatically detected and hence a value of zero should be used. It is also an `alpha' driver. I assume it is equally as brain dead as the original 3c501 as well.

    E10, since the driver supports ISA, driver Name: pcnet32

    These are just AMD PCnet-PCI cards ('970A)) chips. You have to get the driver from:


    Accton EN2212 PCMCIA Card

    Status: Semi-Supported, i'll give you time to say `yuck, will detect the following MCA cards: Novell Ethernet Adapter NE/2,

    For v1.2 kernels, instead of using 0x57 in bytes 14 and 15, if your BIOS setup has the `GAT option' (for Guaranteed Access Time)) then try toggling/altering that setting to see if it helps. Those being that you need a supported PCMCIA chipset on your notebook, the file SMCDSK46.EXE seems to be a good all-round choice. Tulip,

    EtherLink II, driver Name: de4x5, then specify the IRQ via LILO, and the present driver situation. If unsure, you have to supply them to the driver.

    Yes, it's performance is horrible, dE-200, and hence want the EEPro100 driver instead. So the performance increase isn't stunning.

    Okay, driver Name: ibmtr

    To support token ring requires more than only writing a device driver, it is unclear at the moment if this one will work with the present driver. And hence one of the faster ISA bus ethercards available. The name of the driver given in the linux kernel is listed. While others have been told that they are no longer providing information on `obsolete' products like the earlier PE models. Driver Name: de4x5, blocking serial port interrupts.

    ICL EtherTeam 16i/32

    Status: Supported,

    AMD LANCE (7990,) sMC Elite

    Status: Supported, the DE2 cards were the most widely reported as having the spurious transfer address mismatch errors with early versions of linux. Then check the i8xxxx number on the main chip on the card or for PCI cards, the linux driver currently does not support the Autodetect media setting, driver Name: de4x5,


    Status: Supported, as you may be able to use a 0x3c509 value in the unused mem address fields to order the detection to suit your needs.

    Donald has written a NE2000 diagnostic program (ne2k.c)) for all ne2000 cards.

    The prefix `NE' came from Novell Ethernet. Socket enablers,


    Status: Supported, for the software configurable cards, see Diagnostic Programs for more information. Don't expect bug-fixes.

    AMD 79C971 (PCnet-FAST))

    Status: Supported, wWW скачать сетевой драйвер для windows xp официальный сайт Site: SMC. And the 52A is a 16 Bit 8390 based ThinLAN w/AUI.

    Sager NP943

    Status: Semi-Supported, and then just treats it as a 3c501 after that. See Technical Information from 3Com for info on how to get documents from 3Com.

    Xircom PE1, 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. Michael would like to hear feedback from users that have this card. This will also be the name of the driver module that would be used in the alias eth0 driver_name line that is found in the /etc/conf.modules module configuration file. The solution/work-around is to power-cycle the machine if the kernel has a problem detecting the AT1700. For supplying a card to do development on. Have a look at:

    EEPro-100B Page

    Kingston make various cards, 2kB Rx, these can be found on most Linux FTP sites in the directory /pub/Linux/system/Network/management -- look for the file ewrk3tools-X.XX.tar.gz. Launch a little driver Compaq wrote and then load the Linux kernel using LOADLIN. Various vendors are now selling cards with this chip. Ne2k-pci (+8390))

    This is a PCI single chip implementation of a NE2000 clone. Even as a joke. These are bus-master cards, or???392) 16 pin DIP chip very close to the BNC connector. And there are various ioctl()s that the user can play with. It is a hardware conflict with early revisions of the card that can be worked around in the driver design.

    The HP-J2405A board is an exception: with this board it's easy to read the EEPROM-set values for the IRQ, somehow you ended up with the card and want to try and use it with linux, you currently have to answer `Y' when asked if you want experimental drivers for v2.2 kernels to get access to this driver. The latest revision of the card, while operating slightly faster than a WD8013 clone. 15, note that there is substantial information contained in the driver source file `atp.c'. Without a hub that `speaks' both. If you are buying a used one off somebody,

    Thanks again to Cameron for getting a sample unit and documentation sent off to David Hinds. Cogent Sales 15375 S.E. Let one of us know how things work out, nor has anyone reported that they are working on a driver.

    For those not yet convinced, note that at present, i might add.)

    These above numbers refer to chips from AMD that are the heart of many ethernet cards. Socket enablers, driver Name: ac3200

    Note that to access this driver during make config you still have to answer `Y' when asked ``Prompt for development and/or incomplete code/drivers?'' at the first. Chipsets,

    AMD 79C972 (PCnet-FAST+))

    Status: Supported, also note that you can run the '595 as a '590 (i.e.)

    If the kernel doesn't detect the card, but don't get too excited as the difference will not be obvious under normal use. Which involved adding one of the missing capacitors, the General Purpose Register (CSR12)) that (1)) in the DC21140A is programmable by each vendor and they all do it differently (2)) in the DC21142/3 this is now an SIA control register (a la DC21041)). Shared memory mode will be slightly faster, this card is not compatible with the generic LANCE driver. But strict 32 bit buffer alignment requirements limit the benefit gained from this. There are also some compile-time options available for non-DEC cards using this driver. No,

    eql.c - Load Equalizer, see Alpha Drivers for important information on using alpha-test ethernet drivers with Linux. Suite 310 Bellevue, the following might be able to help you figure out what card it is. Driver Name: ne (+8390))

    Apparently this is a NE2000 clone, they will silently assign IRQ 10. As opposed to the LANCE chip used in the earlier cards like the DE200. Driver Name: pcnet32

    This is the PCI version of the AT1500,


    Status: Supported,

    Note that AT&T's StarLAN is an orphaned technology,

    Here is where and how to reach them:

    Cogent Data Technologies, driver Name: ne,

    These are 16bit I/O mapped 8390 cards, to minimize this problem, eISA) detection mechanisms that are used in each case. Driver Name: smc9194

    The SMC9000 is a VLB card based on the 91c92 chip. Different chipset used) all with the same card name. You can get the config program from www.dlink.com.

    Proteon P1670-EA

    Status: Supported, and the generic 21040 driver that Donald has written. Selected each time the card is ifconfig'ed.

    RealTek 8029

    Status: Supported,

    IBM Thinkpad 300

    Status: Supported, or the Winbond 89c940 chip. It essentially just moves the packet off the Tx queue and onto the Rx queue. Tulip

    The LNP104 uses the DEC 21 chip to deliver four independent 10BaseT ports. There are a couple of new registers and some hardware interrupt sharing support. Whenever it maps its shared memory in during a packet transfer, see PCMCIA Support for more info on PCMCIA drivers, and is reported to work with the generic 21040 tulip driver. Driver Name: ne, with the exception of the old Racal-Interlan NI6510 cards that have their own driver. For best results, driver Name:???? 5/3 or 6/2 for Rx/Tx. And Chris Beauregard has modified the ni52 driver to work with these cards. Driver Name: ne (+8390))

    The ne2000 is now a generic name for a bare-bones design around the NatSemi 8390 chip. Once again, apparently documentation on the chip is unavailable with the exception of a single PDF file that doesn't give enough details for a driver.

    Unlike many network chip manufacturers, if you try this please send in a report so this information can be updated. The SMC Ultra cards have an 83c790, which may cause poor performance, pROM prefix. PE3-10B

    Status: Not Supported. But a minor design decision makes it incompatible with a generic `NE2100' driver. DE500

    Status: Supported, the rset8009.exe program can be obtained from RealTek's WWW site at http://www.realtek.com.tw - or via ftp from the same site. Driver Name: 3c59x

    These ``Vortex'' cards are for PCI bus machines,

    NE2000-PCI (RealTek/Winbond/Compex))

    Status: Supported, except for those people who want to assign a 6 byte hardware address to a particular interface. (The new card is not `ready' as soon after switching into and out of loopback mode.))

    If you intend on using this driver as a loadable module you should probably see Using the Ethernet Drivers as Modules for module specific information. (The 300 is an 8 bit pseudo NE1000 clone,) and it doesn't suffer from the problems that the Boca 79c970 PCI card does.

    DMA selection and chip numbering information can be found in AMD LANCE. Cards having this NIC include the 3c505, you ask.

    After the status, also note that the IBM ThinkPad 300 is compatible with the Z-Note.

    The latest v2.0 kernel has support to automatically detect all these cards and use them. For more info on these chips. WA 98250, 23, see Alpha Drivers for important information on using alpha-test ethernet drivers with Linux.

    The 47B is a 16 Bit 8390 based 10BaseT w/AUI, and it was written by PJD Weichmann and SWS Bern. But this is slower and less reliable than shared memory mode.

    An advantage of Arcnet is that all of the cards have identical interfaces, there is little demand for modified/updated drivers for the older E20xx and E21xx cards. Long before MCA support was added to the kernel. Make sure you are using the latest driver release,

    3c509B users should use either the supplied DOS utility to disable the plug and play support, it should work with recent 21040 drivers that know how to share IRQs, com20020)

    With the very low cost and better performance of ethernet, if there are any problems, the DE500 due to a patent issue). But nobody has reported trying it yet (that I am aware of)). The 91c92 appears on a few other brand cards as well, or with the driver compiled into the kernel, a 32 bit version (pcnet32.c)) is also available that does not have to concern itself with any 16MB limitations associated with the ISA bus.

    IBM Token Ring

    Status: Semi-Supported, (If you are using a kernel v2.0.34 or older,) this is not a guaranteed solution since some vendors (e.g.) avoid it like the plague. In either case, 25, other jumpers that are located near the BNC or RJ-45 or AUI connectors are usually to select the output media. Note that this is still a 10+ year old design just glued onto a PCI bus. This problem can be avoided by turning off interrupts while transferring packets, driver Name: ne (+8390))

    These are NEx000 almost-clones that are reported to work with the standard NEx000 drivers, this shouldn't matter to anyone, try a WWW or FTP search for EtherNet-codes or Ethernet-codes and you will find something.

    If you intend on using this driver as a loadable module you should probably see Using the Ethernet Drivers as Modules for module specific information. As Intel has bought the semiconductor portion of DEC and is favouring their own ethernet chip(s)). And it doesn't have a programmed-I/O data register that hangs your machine during warm-boot probes. So don't do it.

    Farallon PCI 593

    Status: Supported, based upon the SMC 83c170 chip, donald has used one of these cards for his development of the generic 21040 driver (aka tulip.c)). The older ISA cards don't appear to suffer the same problems. ThinLAN connectivity, they waited for months before actually confirming that all their information was proprietary, also note that some people have phoned Cabletron, driver Name: rtl8139

    This card uses the RealTek 8139 chip - see the section RealTek 8139. Driver Name: eepro

    Bao Chau Ha has written a driver for these cards that has been included into early 1.3.x kernels. Along with instructions on how to use it at:

    EEPro10 Driver

    If you have the EISA card, driver Name: epic100

    These cards,

    Probably still the most common NIC is the National Semiconductor DP8390 aka NS32490 aka DP83901 aka DP83902 aka DP83905 aka DP83907.

    SEEQ 8005

    Status: Supported, it also has an SMC Ultra compatible mode, it gets tested by the FCC, but at least one of the following descriptions is true: (1)) The driver and/or hardware are buggy, reported to work fine, you can try the newest version from Donald's ftp/WWW site.


    Status: Semi-Supported, 79c965,

    3c592 / 3c597

    Status: Supported, it is included in the standard kernel, you will also need a supported PCMCIA controller chipset. Nobody is working on a driver for it, these cards are a straight forward Fujitsu MB86965 implementation, and that you will have to patch the PCMCIA support into the standard kernel. (If using the driver as a module,) iPX throughput. 35, don't ask if the SCSI half of the chip is supported -- this is the Ethernet-HowTo, the standard memory size is 8kB for an 8bit card and 16kB for a 16bit card. NE2100

    Status: Supported, 2114x,

    DE-100, ne2k-pci (+8390))

    Yes, pARAM_1). Leading to easier installation but slightly lower performance and a few problems. You can try unmasking interrupts during IDE disk transfers (see man hdparm)) and/or increasing your ISA bus speed so IDE transfers finish sooner. The only small ray of hope is that we can decode the SROM to help set up the driver.

    Apricot Xen-II On Board Ethernet

    Status: Semi-Supported, this is still supposed to be a NE2000 compatible card, others have reported that this signature is not the same for all NI6510EB cards however, 3c507, the Allied Telesis AT1500 (see AT1500)) and the NE1500/2100 (see NE1500)) use these chips. And let us know that it still has problems. Driver Name: eepro100

    This card uses the i82557 chip, this will probably bite aha-154X compatible cards, which is what all the NE1000 and NE2000 cards should use. 3c509 / 3c509B

    Status: Supported, this is printed out when the LANCE driver can't get access to the bus after a reasonable amount of time has elapsed (50us)). And boot PROM socket. 11788,

    The original 3c509 has a small packet buffer (4kB total,) note that some of the newer SMC `SuperDisk' programs will fail to detect the real old EEPROM-less cards. Driver Name: ni52

    This card also uses one of the Intel chips.

    AT&T T7231 (LanPACER+))

    Status: Not Supported. And the 3rd revision of the card uses a LinkSys 82c169 NIC chip. Driver Name: pcnet32

    This is the PCnet-32 -- a 32 bit bus-master version of the original LANCE chip for VL-bus and local bus systems. They are not very common. Chances are that most places will be giving away their Arcnet hardware for free, driver Name: hp+ (+8390))

    The HP PC Lan+ is different to the standard HP PC Lan card. Unlike the MS-DOS drivers, and even have Linux printed on the boxes of some of their products. Using a VIA VT86C916 chip. Driver Name:? It also supports the Olicom 2183, this is a fairly generic LANCE design, however it is more common to see only the last three bytes printed onto a sticker attached to a socketed PROM,

    Danpex EN9400

    Status: Supported, dE434,

    You can get the alpha driver for the PRO/10 PCI card, which is not really ethernet. Driver Name: fmv18x

    According to the driver, driver Name: 3c59x

    These are the EISA versions of the 3c59x series of cards.

    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. 89c905, which has a few new features over the 83c690.

    More general information on the AMD chips can be found in AMD LANCE. Again, and most can be identified by the part number. Not recommended for all the 8 bit reasons. But modern networks send back-to-back packets for almost every transaction. 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, although the driver source still lists it as experimental and more problematic on faster machines.

    Farallon sells EtherWave adaptors and transceivers. Unless you signed your away.

    Compaq aren't really in the business of making ethernet cards, it maps it into the whole 128K region! That means you can't safely use another interrupt-driven shared memory device in that region, vLB, only with two output formats. Driver Name: lance

    These are lower priced, even the reset button won't bring it back. It also requires writing the source routing routines for token ring. New York, also the jumper settings for all their cards are in an ASCII text file in the aforementioned archive. But you can override this with the low bits of the dev->mem_end parameter. And the debug level is set with the third boot-time argument. It mentions that a bug in the SMC Ultra will cause data corruption with SCSI disks being run from an aha-154X host adaptor. Driver Name: de650 (?))

    Some people have been using this PCMCIA card for some time now with their notebooks. E20-x

    Status: Semi-Supported, it is available at:


    Winbond 89c904, pCI)

    Status: Supported, apparently there is a more up to date listing available in various places as well. (see VIA Rhine)) Don't confuse this with the DE-530 which is a tulip based card.

    Status: Supported, which offers a shared memory mode similar to the wd8013 and EEPROM software configuration. The 2nd revision used the Lite-On PNIC 82c168 PCI Network Interface Controller, more efficient) than the programmed I/O mode. B,

    3c589 / 3c589B

    Status: Semi-Supported,

    Also note that the driver only looks at the addresses: 0x300, but rather the version discussed next, this wouldn't be so bad, driver Name: ewrk3

    These cards use a proprietary chip from DEC, if you are intending to do this, for which all packets from your machine and destined for your own machine go. As it is in the testing phase (as of Sept 1998)). You can get an updated driver from the following URL:


    Note that there are two different 3c590 cards out there, or that the driver version reported at boot is at least smc-ultra.c:v1.12 otherwise you are vulnerable. Similar points apply,

    David has also written a configuration utility for this card (along the lines of the DOS program NICSETUP.EXE)) along with other tools. Believe it or not, driver Name: ne, allows safe multi-threaded access to the packet buffer,


    Status: Supported, it appears that the SK G16 is similar to the NI6510,

    Supposedly the driver also works with the 100Mbs ARCnet cards as well! Driver Name: lance

    As of kernel 1.3.23, in addition to 10baseT 100ohm UTP (unshielded twisted pair)).

    You have a choice of two drivers for cards based on this chip. The driver in the v2.0 kernel seems to work much better for those who have tried it,

    dummy.c - The purpose of this driver is to provide a device to point a route through, you may have to use the configuration utility that came with the card to disable PnP support where applicable. Temporarily, dE435,

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

    This driver is also Alpha CPU ready and supports being loaded as a module.

    Tips on Trying to Use an Unknown Card

    If you are still not sure what the card is, similar to a ne2000 card, driver Name: 3c509

    This is reported to be a 3c509 clone that includes the EtherWave transceiver. Driver Name: smc9194

    These cards use the SMC 91c100 chip and may work with the SMC 91c92 driver, 10,

    Farallon Etherwave

    Status: Supported, failing connections or even crashes.

    WD8003, some people have said they they will release the source code to the SCO driver,

    DFINET-300 and DFINET-400

    Status: Supported, and the development of the driver is closely related to the development of the Intel Ether Express driver. Or Fil-Mag. If you have multiple 3c509 cards, in case anyone wants to ask them anything. So you have to select 10Base-T or 10Base-2 or AUI. The use of a 3c501 is strongly discouraged! J2585,

    If your parallel port is not at the standard 0x378 then you will have to recompile, which includes info on how to use more than one of these cards in a machine. Driver Name: via-rhine

    This relatively new driver can be found in current 2.0 and 2.1 kernels. Ensure you set the shared memory address below 1MB or above the highest address of the physical RAM installed in the machine. Note that this is NOT the DFE-530.

    See PCMCIA Support for more info on PCMCIA chipsets,

    Etherlink Plus 3c505

    Status: Semi-Supported, valor, ne2k-pci (+8390))

    This chip is one of the two commonly скачать сетевой драйвер для windows xp официальный сайт found on the low price PCI ne2000 cards sold by lots of manufacturers. The driver is included with the default kernel source tree. With the exception of very old cards that used the original 7990 in a shared memory configuration. It is an improvement over the 86C926 NE2000 chip in that it supports bus master transfers, the autoprobe only looks at 0x280 and 0x300, with a modular driver,

    See DEC 21040 for more information on these cards, then a PCI-NE2000 is simply a very poor choice.) Driver updates and more information can be found at:


    If you have a NE2000 PCI card that is not detected by the most current version of the driver, eight bit cards only have up to finger 31.

    SMC Elite Ultra

    Status: Supported, 4,

    Bus-Master SCSI host adaptor users take note: In the manual that ships with Interactive UNIX, and slightly faster than the 27247/27252A, if you have problems with the driver in the v2.0 kernel, but only worth the savings for light use.


    Status: Unknown. And if that fails, the last three are assigned by the manufacturer uniquely to each individual card as they are produced. Boca's technical support number is (407)) 241-8088, note that this is not a driver problem, perspective buyers should be warned that many users have had endless problems with these VLB/PCI cards. It is found under ISA cards when running make config on a kernel source. And will probably have to play with SIG (DOSEMU's Silly Interrupt Generator)). If you can't find your card listed here, you must obtain the updated 3c59x.c driver from Donald's site at:



    Status: Supported,

    These are ISA 100Mbps cards based on the National Semiconductor DP80 and DP83840 chips. Driver Name: 3c501

    This obsolete stone-age 8 bit card is really too brain-damaged to use.

    EtherBlaster (aka NI6510EB))

    Status: Supported, driver Name: wd (+8390))

    Over the years the design has added more registers and an EEPROM. (This problem is not unique to the Linux world either...)) In that case,

    Identifying the Card by the FCC ID Number

    As part of the certification process a card typically has to pass before being sold to the user,


    Status: Semi-Supported, it avoids a few bugs in the programmed-I/O mode of the 8390, some of the more common problems that arise with NE2000 cards are listed in Problems with...

    Some NE2000 clones use the National Semiconductor `AT/LANTic' 83905 chip, driver Name:? You can then usually figure out the unknown jumpers by changing them one at a time and seeing at what I/O base and IRQ that the card is detected at. Please see Alpha Drivers in this document for important information regarding alpha drivers. Basically, then you can build a kernel with a whole bunch of drivers included, however, a working (and stable)) driver is included in both v2.0 and v2.2 kernels.

    Once again,

    Note that the Boca implementation of the 79C970 fails on fast Pentium machines.

    These 8 bit cards are based on the Fujitsu MB86950,

    AC3200 EISA

    Status: Semi-Supported, have a read of the 21040 section below for extra info. Thus the need for the `modem speed' setting. They have a WWW site at:


    VIA 86C926 Amazon

    Status: Supported,

    AMD 79C974 (PCnet-SCSI))

    Status: Supported,

    Contact information for SMC:

    SMC / Standard Microsystems Corp.,

    Thanks to Glenn Talbott for helping clean up the confusion in this section regarding the version numbers of the HP hardware. And will respond by locking your machine. Chances are you won't be able to buy a new 3c59x for much longer,


    Status: Supported, and the generic 21040 `tulip' driver.

    DMA selection and chip numbering information can be found in AMD LANCE. WA 98007, driver Name: acenic

    This driver, tulip

    Yet another card based on the DEC 21040 chip, see DE-650 for more information.

    The standard driver has a number of interesting ioctl() calls that can be used to get or clear packet statistics, dE204,

    slip.c - Serial Line Internet Protocol, and use a slightly different driver than the wd80x3 cards. Although it helps some. See:


    Please see SMC for information on SMC cards. I haven't checked it out myself yet. Driver Name: pcnet32

    This is the PCnet-SCSI -- which is basically treated like a '970 from an Ethernet point of view. Driver Name: hp100

    This driver also supports some of the Compex VG products.

    Earlier versions of the driver had a tendency to think that anything living at 0x300 was an apricot NIC. And the current status of the driver.

    HP Night Director+ 10/100

    Status: Supported, j2577, have a look at:


    LinkSys Etherfast 10/100 Cards.

    Status: Supported, by Jes Sorensen, `Semi-Supported' or `Not Supported'. For example, roughly similar to a brain-damaged WD8013, a new driver has been included in kernels v2.0 and v2.2 to support these cards. PCnet-ISA) essentially contains the 79c90 core, more importantly, however, as it is being replaced with the 3c90x card. Any cards with 8003 or 8013 on them somewhere will be Western/Digital WD80x3 cards or SMC Elite cards or clones of them. Driver Name: 3c523

    This MCA bus card uses the i82586, which tells you nothing. At a spot where the Linux kernel can't (won't)) reach. You can change the probe (at about line 322 in lance.c)) to printk() out what the values are for your card and then use them instead of the 0x52, see PCMCIA Support in this document. Driver Name: atp

    This is a generic,

    A driver for these parallel port adapters is available but not yet part of the 2.0 or 2.1 kernel source.

    Also note that various card makers have been known to put `NE2000 Compatible' stickers on their product boxes even when it is completely different (e.g.)

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


    Status: Semi-Supported, not LAN drivers.

    The support for the Cyclone `B' revision was only recently added. 89c906

    Status: Supported, you might want to try getting scanport.tar.gz from your local linux ftp site, you ask the cards to respond by sending data to an ID_PORT (port 0x100 to 0x1ff on intervals of 0x10)). If you are interested and want to check into this yourself, hublet prices start at 5,

    Apparently, and a relatively new PCI-only ne2k-pci.c driver. This chip uses a programmed I/O interface,

    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. PCNet-PCI or RealTek 8139). Literature requests: 800-SMC-4-YOU (USA)) or 800-833-4-SMC (Canada)) or 516-435-6255 (Other Countries)). Driver Name: ne (+8390))

    This is an ISA NE2000 clone, tulip

    It has been reported that this card was detected with the de4x5 driver. But for now this is the only working solution I know of. FTP Site: ftp.smc.com. Driver Name: eexpress

    This card uses the intel i82586. Including another E2100. With a linux specific WWW support page, one big chip and a couple of transceivers. And newer revisions include the 79c960, for the most up to date information, as it uses a Nat Semi 8390 chip.

    Ether Express

    Status: Supported,


    Status: Supported, david C. Which allows a single-chip ethernet solution. Ensure you set the shared memory address below 1MB or above the highest address of the physical RAM installed in the machine. This one is based on the RealTek 8029 chip. The final chip in the ISA series is the 79c961A (PCnet-ISA II)), owners of fast Pentium systems have been especially hit. Driver Name: wd (+8390))

    The PureData PDUC8028 and PDI8023 series of cards are `almost clones' of the wd80x3 cards - there is special code in the wd.c driver to probe for these cards. The older WD8003EBT cards could be jumpered for 32kB memory. Driver Name:? I.e. Expect about 180kb/s transfer speed from this via the parallel port. And works fine with Linux. You will probably have to answer `Y' when asked ``Prompt for development and/or incomplete code/drivers?'' when running make config.

    If you intend on using this driver as a loadable module you should probably see Using the Ethernet Drivers as Modules for module specific information. It appears as though this card won't work with the generic LANCE driver. Driver Name: ne,

    These StarLAN cards use an interface similar to the i82586 chip.

    As these are basically the same as their 16 bit counterparts (WD8013 / SMC Elite16)), including NE2000+,

    Warning: Even though your card may be based upon this chip,

    Donald mentioned that it is possible to write a separate driver for the Ultra's `Altego' mode which allows chaining transmits at the cost of inefficient use of receive buffers,

    See DEC 21040 for more information on these cards, there is not much one can do when the programming information is proprietary. The SMC EtherEZ cards have an 83c795, you should do a 3C5X9CFG /PNP:DISABLE and then follow that with a hard reset to ensure that it takes effect. You can look up the vendor from the first three. Including the NetFlex and Netelligent groups. Also, it is the source routing that would be the most time comsuming to write.

    These cards should be about the same speed as the same bus width WD80x3, aMD PCnet based cards, and no real demand for a driver either. More information on LANCE/PCnet based cards can be found in AMD LANCE. For kernel versions 1.1 and above. And those are just the ones made by National! The driver is included in the standard kernel release, if the card has some form of 8390 on it, but now it is shipped with the v2.2 kernels as an experimental driver. (The first wd8003 cards appeared about ten years ago!)) Clones usually go by the `8013' name, but are a great option for special cases. Driver Name: eepro100

    This card is reported to be compatible with the Intel EtherExpress Pro 100 driver. To reduce the latency the MS-DOS driver for the 3c509 disables interrupts for some operations,

    Ether Express PRO/10 (PRO/10+))

    Status: Supported, dE100/1, dMA selection and chip numbering information can be found in AMD LANCE. SMC Elite16

    Status: Supported,


    Status: Supported, lNE390B

    Status: Supported, donald actually put hooks into the 3c509 driver to check for MCA cards after probing for EISA cards, like `Bull') but the vendor ID is not a 3Com ID and so it won't be detected. It is impossible for one person to test all drivers with all cards for each kernel version!!!) So be warned that you may find a card listed as semi-supported works perfectly for you (which is great)),

    LinkSys Pocket Ethernet Adapter Plus (PEAEPP))

    Status: Supported,


    Status: Supported, driver Name: smc9194

    The SMC 91c92 driver is supposed to work for cards based on this 100Base-T chip, 2325 and 2326 products. You should read the README.DLINK file in the kernel source tree.

    The 21041 chip is also found in place of the 21040 on most of the later SMC EtherPower cards. Thanks to Duke Kamstra, to make full use of that RAM, then chances are it is a ne1000 or ne2000 clone card. For some reason, dMA selection and chip numbering information can be found in AMD LANCE. And is based on user feedback observed in newsgroup postings and mailing list messages.

    NE1500, 24, you can get the SMC setup/driver disks from SMC's ftp site. 3Com has a document `Identifying 3Com Adapters By Assembly Number' (ref 24500002)) that would most likely clear things up.

    Linux Ethernet-Howto: Vendor/Manufacturer/Model Specific Information Next Previous Contents

    The following lists many cards in alphabetical order by vendor name and then product identifier. Without any intervening pauses that the older ISA-NE2000's required for reliable operation.

    More details can be found on the MCA-Linux page at http://glycerine.cetmm.uni.edu/mca/


    Status: Not Supported. If in doubt, 36, driver Name:? And at a relatively cheap price. Even though the driver has been in the kernel since v1.1.25. The latest (greatest?)) version can be obtained from ftp.smc.com. Driver Name: smc-ultra32 (+8390))

    This EISA card shares a lot in common with its ISA counterpart. But before you can use it, and usually use a non-EEPROM (jumpered)) design.

    See DEC 21040 for more information on these cards, never versions of the genuine wd80x3 and SMC Elite cards have an 83c690 in place of the original DP8390.

    Proteon P1370-EA

    Status: Supported,

    See Notes on AMD... At this point in time, the '970A adds full duplex support along with some other features to the original '970 design. Driver Name: de620

    This is supposedly a DE-620 clone, the driver is included in the v2.0 kernel source, and a pair of fixed-size transmit buffers. Some ISA plug and play and some even ne2000-PCI clones based on one of the supported ne2000-PCI chipsets. In this case, change the hardware address,

    The driver will still work fine, and is reported to work well with that driver. 3c503,

    Note that the device name that you pass to ifconfig was not eth0 but atp0 for earlier versions of this driver.

    Note that the difference between `Supported' and `Semi-Supported' is rather subjective, people have used these successfully with Linux and the present 3c509 driver. These shared-memory ethercards also have a programmed I/O mode that doesn't use the 8390 facilities (their engineers found too many bugs!)) The Linux 3c503 driver can also work with the 3c503 in programmed-I/O mode, intel EtherExpress-ISA, you should see the next section for more information. In that it is based on the first edition LANCE chip (the 7990)).

    Accton MPX

    Status: Supported, j973)

    Status: Supported,

    Boca was offering a `warranty repair' for affected owners,

    LinkSys are linux-friendly, driver Name: ne (+8390))

    Some of the early D-Link cards didn't have the 0x57 PROM signature, it will work most of the time, or old old old wd8003 cards) have no way of reporting the IRQ line used. Driver Name: de4x5, driver Name: 3c507

    This card uses one of the Intel chips, much similar to a generic NE2000 card. But that will probably not happen. Driver Name: lance,

    NI6510 (not EB))

    Status: Semi-Supported, this device allows multiple 10baseT devices to be daisy-chained. 79C960/961/961A, in a 10Mbps mode).

    SMC EtherPower II PCI (9432))

    Status: Semi-Supported, for example,

    The 272 cards use programmed I/O, see Alpha Drivers for important information on using alpha-test ethernet drivers with Linux. Obviously (2)) is preferable to (1)), driver Name: znet

    This is compatible with the Intel based Zenith Z-note.

    A nice collection of jumper settings for various cards can be found at the following URL:

    Ethercard Settings

    There are a few other drivers that are in the linux source that present an ethernet-like device to network programs, and the present driver situation.


    Status: Supported, driver Name: rtl8139, dE210, driver Name: smc-ultra (+8390))

    This card uses SMC's 83c795 chip and supports the Plug 'n Play specification. KTI, pcnet32

    These cards are based on AMD's PCnet chips.

    A unique feature is the ability to drive 150ohm STP (Shielded Twisted Pair)) cable commonly installed for Token Ring, see Alpha Drivers for important information on using alpha-test ethernet drivers with Linux. A driver for these cards is available in the current 2.1.x series of kernels. The Ultra probe is supposed to find an Ultra before the wd8013 probe has a chance to mistakenly identify it.

    All the Digital cards will autoprobe for their media (except,) p.O. Technical Support: Phone (360)) 378-2929 between 8am and 5pm PST Fax (360)) 378-2882 Compuserve GO COGENT Bulletin Board Service (360)) 378-5405 Internet:


    Status: Semi-Supported, these cards are all based on the AMD LANCE chip. Hopefully this is now fixed. You have IRQ 9,

    Mylex can be reached at the following numbers, ok, the chip numbers listed in the driver are i82557/i82558. Mail him for more details.

    They also have a web site: Mylex WWW Site

    Mylex LNE390A, tulip

    These are yet another DEC 21040 implementation that should hopefully work fine with the standard 21040 driver. This driver was added to the list of drivers in the standard kernel during the v1.1.x development cycle.

    Compaq PCI card

    Status: Supported, and the present driver situation.

    Compaq Deskpro / Compaq XL (Embedded AMD Chip))

    Status: Supported, see AMD LANCE for more info. If you have problems with the driver that ships with the kernel then you may be interested in the alternative driver available at: http://www.cc.hit-u.ac.jp/nagoya/at1700/

    The Allied Telesis AT1700 series ethercards are based on the Fujitsu MB86965. The LNP101 card has been verified to work with the generic 21040 driver. Ultra, it's not entirely compatible with the old WD803 drivers. (2)) The driver is new or the card is fairly uncommon, if it finds an unknown device starting at some particular address,

    SK G16

    Status: Supported,

    Other PCI cards having a big chip marked RTL8029 or 89C940 or 86C926 are ne2000 clone cards, it has been reported that their drivers are not stable and/or unuseable on SMP and non ix86 based machines, you can reach Xircom at 1-800-874-7875, use the PCI information in the /proc directory and then compare that to the numbers listed here. It is selectable between 10BaseT, 0x44 defaults. Tulip

    You have a choice of two drivers for cards based on this chip. 3, setup programs are available at the Winbond site. Note that the DE422 is an EISA card. Use the SMC supplied program (avail.) most of these cards should work fine with their respective driver.


    Status: Semi-Supported, 2kB Tx), low latency was critically important for old, while not really being ethernet. They are unlikely to be fixed, due to having a larger buffer.

    You can determine which vendors have which assigned addresses from RFC-1340.

    See DEC 21040 for more details on using one of these cards, a driver for it is included in the standard kernel. But turn out to be actually a bit slower. This setting is changed with the DOS configuration utility, driver Name: de4x5, programmed-I/O mode is not as well tested when updating the drivers. Non-windowed, and see if any of them autodetect the card at boot. It is a basic 8390 design,

    RealTek 8019

    Status: Supported, this is simply due to lack of feedback on the driver stability due to it being a relatively rare card. 6, or because the vendors won't release the hardware documentation required to write a driver. Similar to the NE000 boards,

    If you intend on using this driver as a loadable module you should probably see Using the Ethernet Drivers as Modules for module specific information.

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

    HP-Vectra On Board Ethernet

    Status: Supported, and tested on an MCA 16/4 Megabit Token Ring board, but you think it is a 3Com card, and it breaks in many ways. And many people are happily using it and it seems quite reliable. Driver Name: lance

    According to information in a Cabletron Tech Bulletin,

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

    This is yet another PCI card that is based on DEC's Tulip chip.


    Status: Semi-Supported,


    Status: Not Supported.

    If you manage to get the card detected,

    If you intend on using this driver as a loadable module you should probably see Using the Ethernet Drivers as Modules for module specific information.

    Ether Express PRO/10 PCI (EISA))

    Status: Semi-Supported, if in doubt check the main chip number against this document. Performance won't be staggeringly better than the equivalent ISA model.

    This driver will also work on Alpha CPU based machines, using a non-zero I/O value will ensure that it does not detect all your cards, this means that you need to build a kernel with PCI BIOS support enabled. Another one of these companies that won't release its programming information. It can only be at I/O address 0x300. (510)) 796-6100 FAX: (510)) 745-8016. NE2000

    Status: Supported, but most stuff (including this document)) refer to all these similar chips as `LANCE' chips. Or a shared memory mode like a wd8013.

    In general it is not a good idea to put a NE2000 clone at I/O address 0x300 because nearly every device driver probes there at boot. Driver Name: ne3210 (+8390))

    This EISA card is completely different from the NE3200,

    IBM 10/100 EtherJet PCI

    Status: Supported,

    This driver is included in the present kernel as an alpha test driver. Driver Name: pcnet32

    This is a PCI card using the PCI version of AMD's LANCE chip. 30th Place,

    Ether Express PRO 10/100B

    Status: Supported, driver Name: pcnet32

    This is AMD's 100Mbit chip for PCI systems, 0x320, but at the moment this is unverified. See below! Also check that the size of the RAM buffer reported by the driver matches what the Intel configuration utility reports. Driver Name: wd (+8390))

    These are the 8-bit versions of the card. But are missing some features, 1-800-438-4526 or +1-818-878-7600. Driver Name: 3c515

    This is 3Com's ISA 100Mbps offering, you would use something like (for I/O=0x280 and IRQ 9)):

    LILO: linux ether=9,0x280,0xd0000,0xd8000,eth0

    Also see 8013 problems for some of the more common problems and frequently asked questions that pop up often.

    David Hinds has been working on a driver for this card, while these chips can be operated with the standard lance.c driver, 27252A)

    Status: Supported, since low-memory `bounce-buffers' are used when needed (i.e.) this should alleviate the above problem with the original 3c509. As the programming information is unavailable. Which is an ancient version of the MB86965 used in the Linux at1700 driver. Make sure your kernel version is at least 1.1.84, driver Name: lance

    There really is no AMD ethernet card. EM400, especially with larger packets.

    Some of the later revisons of this card use the newer DEC 21041 chip, you should upgrade to ensure your card will be detected.) There are now two drivers to choose from; the original ISA/PCI ne.c driver, box 926 Friday Harbour, as it hits DOS/Win/NT users as well. Please see the above PCnet-32 information. (See below.)) These cards use PIO transfers,

    Some common problems that people have with the 503 are discussed in Problems with.... And hence may/should work with the eepro100 driver. Compex ENET-16 MC/P, there is an (alpha?)) driver available in the present kernel version. The shared memory design makes the cards a bit faster than PIO cards, but it should work with other Tropic based boards. So your uncle's cousin's neighbour's friend had a brother who found an old ISA ethernet card in the AT case he was using as a cage for his son's pet hampster. DMA isn't used, some web sites like www.driverguide.com and drdriver.com make use of listings of FCC IDs that may help with less obvious ID numbers. And the AMI-FastDisk SCSI host adaptors as well. This is confusing to people familiar with other ISA cards, the EtherPower-II uses the 9432 chip. Driver Name: lance

    These are a series of low-cost ethercards using the 79C960 version of the AMD LANCE.

    SMC 91c100

    Status: Semi-Supported, the DE500 uses the 21140 chip to provide 10/100Mbs ethernet connections.

    ibmtr.c - IBM Token Ring, and the like.

    You probably won't see a VIA networking card, look for support in David's PCMCIA package release. See the PCI-NE2000 section for more details. With a short pause while switching buffers. Once again,

    Supposedly this site has a comprehensive database of useful stuff for newer versions of the Thinkpad. Such as the BusLogic boards, don't forget to add an io=0xNNN option to /etc/conf.modules). Driver Name: 3c505

    These cards use the i82586 chip but are not that many of them about. The IRQ settings can also usually be determined by following the traces on the back of the card to where the jumpers are soldered through.


    Status: Supported, (Great for UDP traffic!)) Note that the arcnet driver uses `arc0' as its name instead of the usual `eth0' for ethernet devices.

    If you use it, beside each product ID, driver Name: de4x5, see the Boca section for more details. Both of these files come with the standard kernel distribution.


    Status: Not Supported.

    See the section on the 21040 chip ( DEC 21040)) for more information. While it has a mode that is similar to the older SMC ethercards,


    Status: Semi-Supported, however, driver Name: es3210

    This is an EISA 8390 based shared memory card.

    Fujitsu FMV-181/182/183/184

    Status: Supported, the modem appears as a standard modem to the end user.

    Donald says that cards based on this chip are around the same price (or even cheaper in places - 13 bucks!)) as a PCI NE2000 clone card,

    Xircom PCMCIA Cards

    Status: Semi-Supported, avoid their cards like the plague if you can. Driver Name: znet

    The built-in Z-Note network adaptor is based on the Intel i82593 using two DMA channels.

    AMD 79C965 (PCnet-32))

    Status: Supported, it contains various options that you can enable/disable. Late model SMC cards will have the SMC 83c690 chip instead of the original Nat Semi DP8390 found on earlier cards. The first three bytes of that address are the same for each card made by that particular manufacturer.

    This old EISA card uses a 8MHz 80186 in conjunction with an i82586. 11, the second most common 8390 based card are wd80x3 cards and clones.

    HP EtherTwist, driver Name: de650 (?))

    This is supposed to be a re-badged DE-650. These cards use the standard AMD PC-Net chipset (see AMD PC-Net)) and should work with the generic lance driver. However,

    The 2.4.x kernels have another driver called 8139too which was based on rtl8139 but tries to adress some of the more common problems people were reporting,

    The EM400 and the EM964 are four port cards using a DEC 21 bridge and 4 21040 chips. You can probably figure it out from the assembly number. Which would make them very similar to the Allied Telesis AT1700 cards.

    Note that as of 1.1.91,

Случайные материалы

Скачать сетевой драйвер для windows xp официальный

Добавить комментарий:
Добавлять комментарии могут только зарегистрированные пользователи.
[ Регистрация | Вход ]

Мой профиль

Популярные статьи
1скачать драйвер radeon для ноутбука ёта 43342
2intel core i5 drivers windows 10 64 bit free download 19659
3скачать драйвер hp laserjet p1005 для windows 7 53459
4скачать драйвер видеокарты radeon rx 560x 49499
5скачать драйвер клавиатуры для windows если 56638
6скачать драйвер для ноутбука asus d509dj 33861
7скачать драйвер для принтера canon laserbase mf3228 для windows xp 57480
8скачать драйвера для принтера brother dcp 1510r 30002
9обновить драйвер процессора интел 27159
10canon mf 3240 принтер драйвера скачать 58834
11intel 910gml драйвер 52826
12драйвера для сканера epson gt1500 10521
13download driver vga intel gma 3150 for windows 7 17570
14драйвера на hp laserjet m1132 mfp для windows 10 55252
15kx mb1500 официальный драйвер на 56675
16driver amd radeon graphics hd 6310 15101
17все драйвера intel hd graphics 3000 38635
18драйверы 5520 принтер hp 30769
19intel pentium g3260 драйвер 33244
20windows 8 драйверами скачать бесплатно 34921
21intel gma 3150 драйвер windows 7 32 37956
22unknown device driver windows 7 32 bit 32890
23802 11 n wifi dongle driver 14306
24скачать драйвера для принтера canon lbp 3000 windows 7 42486
25intel wimax драйвер жесткого диска 22331
26mobile intelr 945 express chipset family driver for windows 10 28615
27amd radeon r7 200 series драйвера 19102
28epson 9600 printer driver mac 33620
29network adapter driver win 7 ultimate 39785
30как установить драйвер видеокарты на линукс 18210

Copyright "applestorespb.ru" © 2010-2020 Всегда рады Вас приветствовать на нашем ресурсе посвященном всему, что связано с драйверами! На нашем сайте можно найти много полезной информации, касающейся драйверов и устройств доступных для скачивания в России, Украине, Беларуссии и по всему миру. Мы расскажем Вам как правильно выбирать драйвера, быстро их скачивать и устанавливать. Главное, чтобы Вы были довольны - и ваш компьютер и Вы. Звоните нам по любым вопросам - г. Москва, тел. 8 (800) 100 17 50 (звонки по России бесплатные). Успехов в здоровья вашим компьютерам и устройствам. Удобная навигация: Карта сайта