Supported Hardware/Network cards

From ReactOS Wiki
Revision as of 12:13, 18 November 2011 by Igorko (talk | contribs)
Jump to: navigation, search
Supported Hardware/Network cards

Please update this page with the status of each NIC that is tested. Try to test a Windows XP driver and if that fails try a Windows 2000 driver (but be sure to mention the failure of the XP driver in your comments). AS YOU CAN SEE, ITS LISTED ALPHABETICALLY, SO PLEASE COMPLY TO THIS ORDER.

Possible statuses

Status Description
Works Works without any major problems
Not tested No test has been performed.
Failed Fails to work or crashes ROS

Tested NICs

NIC Chipset Status Revision Comments Tester Driver Target OS
3COM 3C900-TPO EtherLink XL Parallel tasking II Performance 40-0336-004 Works 41356 See bug 2 below, you need to use expand.exe on EL90XND5.SY_ and copy it to %windir%\system32\drivers. gabriel_it Multisection INF (Windows 2000/Windows XP)
3COM 3C905B-TX-NM Parallel tasking II Performance 40-0483-005 Failed 42095 ReactOS crashes after restart. See #4330. See bug 2 below, you need to use expand.exe on EL90XBC5.SY_ and copy it to %windir%\system32\drivers. gabriel_it Multisection INF (Windows 2000/Windows XP)
3COM 3C905B-TX-M 3com 920-ST06 Works 41235 Works using XP native driver. Haos Windows XP
3COM 3C905CX-TX-M 3com 920-ST06 Failed 48899 #4330 Netzimme Windows XP
3COM 3CSOHO100-TX (OfficeConnect FastEthernet) 3com Failed 41722 See #4330. I only found Windows 9x and Windows 2000 Drivers. Timitry Windows 2000
Accton EN1207B-TX Accton DECchip 21143 Works 41235 Works using XP native driver. Haos Windows XP
Accton EN1207D-TX Accton MPX EN5038A1 Failed 41356 It installs but doesn't work. See #3796 (see bug 1 below). gabriel_it Windows 2000/Windows XP
Accton EN1207D-TX / WOL Accton MPX EN5038B Failed 41356 It installs but doesn't work. (probably bug 1 below). gabriel_it Windows 2000
ADMtek AN983B ADMTek AN983B Works 40588 It installs and works on real hardware, using Windows 2000 drivers. Haos Windows 2000
AMD PCnet™-PRO AMD Am79C976 Works Missing Works using our pcnet driver Unknown ReactOS
AMD PCnet™-FAST III AMD Am79C973/Am79C975 Works Missing Works using our pcnet driver Unknown ReactOS
AMD PCnet™-FAST+ AMD Am79C972 Works Missing Works using our pcnet driver Unknown ReactOS
Broadcom 440x 10/100 Works 41291 Working using official XP drivers. aicom Windows XP
Compex ReadyLINK RL100-TX/PCI Compex RL2000-9881 Failed Missing Compex own driver is too old, NDIS 3.0, see #4530. Haos
Compex ReadyLINK RL2000-PCI Compex RL2000-9881 Works Missing Use Winbond W89C940 drivers (Compex ones have inf file way too old). Haos
D-Link DFE-528TX Realtek RTL8139 Failed Missing Haos
D-Link DFE-530TX Works 40673 Working with builds >= 40673 Unknown
Davicom DM9102AF Works 40821 Used Windows 2000 drivers downloaded from vendor's site. Works with Windows XP offical drivers as well Techsalvager Windows 2000/Windows XP
HP J2585B 10/100VG Works 40487 Driver installs and works on real hardware. Unknown
Intel PRO/100 Works 41134 Works on real hardware (replace XP driver files with Windows 2000 ones) aicom Windows 2000
Intel PRO/100 VE Works 42095 PC Fujitsu-Siemens Scenic D i845D 1331 gabriel_it Windows 2000
Intel PRO/1000 Works 40673 Works with builds >= 40673 (replace Windows XP driver files with Windows 2000 ones) aicom Windows 2000
Intel PRO 1000 MT Dual Server Adapter Failed 41930 Tested with Windows 2000 drivers, failed to work, needs more testing when I can get a serial port out of the computer Techsalvager Windows 2000
Intel 8255x (10/100) Intel 8255x Family Failed 43437 Tested with WinXP drivers, BSOD at restart Ey3 Windows XP
Linksys LNE100TX Linksys LNE100TX Works 40475 Works with builds >= 40475 using official Windows 2000 drivers aicom Windows 2000
MSI PC60G-F Wireless Germany MSI Atheros AR5001 Works Missing It installs and works using Windows 2000/Windows XP driver, but ReactOS lacks wireless support so the card is not really usable. Netzimme Windows XP
NE2000-compatible cards Novell NE2000 Works Missing Works using our ne2000 driver Unknown ReactOS
Netgear FA311 REV-B1 Netgear Works 41930 Works using XP drivers extracted from xp install using driver doubler Techsalvager Windows XP
Netgear MA311 Netgear Failed 43304 Wireless 32bit PCI Model MA311 802.11b, Failed using XP drivers from installer. Techsalvager Windows XP
Netgear FA311 REV-B1 Netgear Works 41930 Works using XP drivers extracted from xp install using driver doubler Techsalvager Windows XP
Nforce2 MCP on Elitegroup N2U400-A Elitegroup Works 54402 Works using XP drivers from motherboard driver pack. igorko Windows XP
QEMU Realtek 8139 QEMU RTL8139 QEMU Works 40673 Works with builds >= 40673 using Windows 2000 drivers aicom Windows 2000
Pluscom NGP-RTL8169 Realtek RTL8169 Failed Missing Installation fails. Geoz
Realtek Semiconductor Co., Ltd. RTL-8029(AS) [1] RTL-8029(AS) Works 0.3.12 Work out of box on real hardware. m0z4rt ReactOS
Realtek 8139C Realtek Realtek Semiconductor Co., Ltd. RTL-8139/8139C/8139C+ [10ec:8139] (rev 10) Works 48899 Windows XP drivers work. Official Realtek drivers work too. Netzimme Windows XP
Realtek 8139D Realtek RTL8139D Works 43280 Windows 2000 driver, v.5.713.121.2009 works fine. DHCP assings IP right after NIC is installed. Ey3 Windows 2000/Windows XP
Realtek RTL8168C/8111C PCI-E Gigabit Ethernet NIC Realtek RTL8168C/8111C Failed 41096 It installs but doesn't work using Windows 2000 drivers (see bug 2 below). Driver LinoSP Windows 2000
VIA Rhine II Fast Ethernet VIA VT6102 [Rhine-II] (rev78) Works 41809 It installs and works on real hardware, using x86 Windows XP drivers. Other VIA Rhine Family Fast Ethernet might work. LinoSP Windows XP

Known bugs

  1. NdisMRegisterInterrupt gets called with InterruptVector == 0 and InterruptLevel == 0 which causes it to fail.
  2. Some INF files have both Windows 2000 and Windows XP sections, with separate drivers for both. When trying to install the Windows 2000 driver version ReactOS is being detected as Windows XP, thus Windows XP driver is attempted to be installed, even though its driver file may be missing in the Windows 2000 driver directory. As ReactOS does not fail when copying non existent files, successful installation is reported, alas driver file is not copied to system32\driver directory. This will cause "Successful install, please restart" window to appear at every boot.