Difference between revisions of "Supported Hardware/Video cards"
Justincase (talk | contribs) m (use template:bug) |
Justincase (talk | contribs) m (forgot to close the template:bug usage) |
||
Line 304: | Line 304: | ||
| {{failed}} | | {{failed}} | ||
| {{rev|63595}} | | {{rev|63595}} | ||
− | | VESA driver works only in Debug mode, otherwise you receive BSOD with code 0x0000007E {{bug|8320|jira. Latest native driver installation wizard splashes error message and fails {{bug|8321|jira}}. | + | | VESA driver works only in Debug mode, otherwise you receive BSOD with code 0x0000007E {{bug|8320|jira}}. Latest native driver installation wizard splashes error message and fails {{bug|8321|jira}}. |
| [[User:Svyatpro|Svyatpro]] | | [[User:Svyatpro|Svyatpro]] | ||
| [http://us.download.nvidia.com/Windows/307.83/307.83-desktop-winxp-32bit-international-whql.exe ForceWare 307.83] | | [http://us.download.nvidia.com/Windows/307.83/307.83-desktop-winxp-32bit-international-whql.exe ForceWare 307.83] |
Revision as of 04:47, 14 June 2014
Please update this page with the status of each Video card that is tested. Please add a link to the site where the driver was obtained, driver version and OS version. AS YOU CAN SEE, THE LIST IS IN ALPHABETICAL ORDER. PLEASE KEEP IT THIS WAY.
Driver types
- VBE driver (vbemp.sys)
- Supports only graphic cards supporting VESA BIOS version v2.0 and higher.
- Supports all available resolutions (640x480 and higher)
- Supports all available color resolutions (8, 16, 24, 32 bits)
- VGA driver (vgamp.sys)
- Supports a standard resolution of 640x480x4 (4 bit = 16 colors)
- Its presence is necessary at all times, for emergency debug fallback.
- Native driver
- This is the Video Adapter's own Windows driver.
Possible statuses
Status | Description |
---|---|
Works | Works without any major problems |
Not tested | No test has been performed |
Failed | Fails to work or crashes ReactOS |
Run w/o result | Run without fundamental functionality |
Tested video cards
This page is probably outdated The information on this page might not be valid for the current state of ReactOS. |
Video | VGA | VESA | Native | Revision | Comments | Tester | Download URL | |
---|---|---|---|---|---|---|---|---|
3DFX Voodoo3 16MB | Works | Works | Works | r47092 | Supports all color bitdepths up to 24bit. | Haos | Windows 2000 / XP driver | |
ATI 3D Rage II+ | Not tested | Works | Works | r41228 | Mouse cursor is not being drawn in VGA mode. | Haos | ||
ATI Mobitity Radeon 7500 | Not tested | Works | Works | Missing | Used ATI Driver from lenovo on a T30, stuck into .iso, installs and shows in device manager, no problems that I saw, worked fine. wasn't able to test any opengl apps though. You can't install drivers from the installer as it doesn't work. | Techsalvager | ||
ATI Mobitity Radeon HD 2400 | Not tested | Works | Not tested | 0.3.10 | Kario | |||
ATI Radeon 9250 PCI | Works | Works | Not tested | r42978 | Techsalvager | |||
ATI Radeon 9500 AGP | Works | Works | Failed | r47092 | Slipstreamed ati drivers from amd website into ros cd, crash on 4th stage, #5362. | Haos | ||
ATI Radeon 9550 AGP | Not tested | Works | Works | r43292 | Slipstreamed ati drivers from amd website into ros cd, drivers load and run natively. no hardware acceleration yet. | Techsalvager | ||
ATI Radeon 9600 Pro AGP | Not tested | Works | Works | r43304 | No slipstream: I have extracted drivers from Windows XP (after installing Catalyst 9.6) and put them in a CD. Then I used ROS wizard for installation, it installed fine and the VGA is recognised. No hw acceleration. | Ey3 | ||
ATI Radeon HD 2100 onboard | Works | Works | Not tested | r42978 | Techsalvager | |||
ATI Radeon HD 3100 Graphics | Works | Works | Failed | r40825 | Driver installation fails (ATI Catalyst™ 9.5 IGP). | Unknown | link | |
ATI Radeon X1300 AGP | Not tested | Works | Works | r43304 | Slipstreamed ati drivers from amd website into ros cd, drivers load and run natively. no hardware acceleration yet. | Techsalvager | ||
ATI Radeon X1300XT AGP | Not tested | Works | Not tested | r43304 | Ey3 | |||
ATI Radeon X300 PCIe | Not tested | Works | Not tested | r42978 | Techsalvager | |||
ATI Radeon X800GTO | Works | Works | Not tested | Missing | No known problems. | Bongmaster | ||
ATI Rage Pro 128 Ultra 32mb | Works | Works | Works | r44458 | ATI package uses 16bit InstallShield. Native drivers from ATI suffer from #4354, native drivers bundled in Windows XP work fine. | Geoz, Haos | ||
Intel I815 (IGP I752) | Works | Failed | Failed | r47121 | vga driver works fine, vesa failed (video driver init error), native driver failed (installation wizard crash) | m0z4rt | xp_driver_ziped xp_driver_exe | |
Intel Extreme Graphics (integrated Intel 845GE chipset) | Works | Works | Not tested | Missing | Unknown | |||
Intel GMA3100 (integrated Intel G31 chipset) | Not tested | Works | Failed | r63592 | Native driver setup wizard passes driver installation procedure as well, after reboot ReactOS receives BSOD with error 0x0000001E, CORE-8319 | Svyatpro | winxp_14374.zip | |
Intel HD Graphics 3000 (integrated) | Works | Failed | Not tested | 0.3.15 | visual artifacts present. | prmartin | ||
Intel Corporation Mobile 915GM/GMS/910GML Express Graphics Controller (rev 03) | Not tested | Not tested | Not tested | r47135 | m0z4rt | |||
Matrox MGA-100 AGP 2MB | Works | Works | Works | r41438 | Minor issues, see #4563 | Haos | ||
Matrox Millenium G400 AGP 32MB | Works | Works | Works | Missing | Minor issues, see #4563, opengl ICD doesnt work. | Haos | ||
NVIDIA TNT RIVA 16MB | Works | Works | Failed | used drivers 44.x going to test with 71.89 that Haos used on the TNT2 | Techsalvager | |||
NVIDIA TNT2 Model 64 32MB | Works | Works | Works | r41438 | OpenGL ICD doesnt work. | Haos | Driver | |
NVIDIA Geforce 2 MX 32MB AGP 4x | Works | Works | Works | 0.3.12 | m0z4rt | Driver | ||
NVIDIA GeForce 4 MX440 AGP 8x | Not tested | Failed | Not tested | r42978 | system crash on 2nd stage same as the geforce fx 5200 problem | Techsalvager | ||
NVIDIA GeForce 4 Ti 4200 128MB AGP | Works | Works | Failed | Missing | Drivers do not install | LinoSP | Windows XP / Windows 2000 | |
NVIDIA GeForce FX 5200 128MB AGP | Not tested | Works | Failed | r58347 | Real hardware. Official Nvidia Driver installation makes Reactos unresponsive. CORE-6964 | |||
NVIDIA GeForce 5900 PCIe | Failed | Failed | Not tested | Missing | No debug output due to system used on had no serial port, will test on another system later. | Techsalvager | ||
NVIDIA Quadro 4 980 XGL | Not tested | Works | Works | r42978 | Installer fails to install video drivers, common, will test with a slipstream disc of files. EDIT: slipstream of nvidia drivers to cd works, ROS loads native nvidia drivers, after reboot ROS locks up. | Techsalvager | ||
NVIDIA GeForce 6600 PCI-E | Not tested | Works | Failed | r63595 | VESA driver works only in Debug mode, otherwise you receive BSOD with code 0x0000007E CORE-8320. Latest native driver installation wizard splashes error message and fails CORE-8321. | Svyatpro | ForceWare 307.83 | |
S3 Trio64+ | Works | Failed | Works | Missing | Doesnt support VESA 2.0. For VGA, please see point 3 of "Known Issues". With native Windows XP drivers, see #4354 | Haos | ||
S3 VIRGE 86c325 | Failed | Failed | Not tested | Missing | Doesnt support VESA 2.0. For VGA, please see point 3 of "Known Issues". | Unknown | ||
S3 VIRGE/DX 86c375 | Works | Failed | Not tested | r47121 | vga driver work fine, vesa failed (video driver init error), native not tested | m0z4rt | NT4.0 ziped | |
S3 Salvage | Not tested | Works | Works | Missing | Works using drivers but has problem and drops into the debugger, running cont will contiune to desktop, no working 3d acccerlation as of yet. | Techsalvager | ||
Trident 9880 Blade3D | Works | Works | Works | 0.3.15rc2 | Used the XP driver files: trid3d.inf, trid3d.dll, and trid3dm.sys. Placed the files in the appropriate folders after the first stage setup. After second stage completed, it used the XP drivers and showed the desktop. The mouse cursor appears as a white block with garbage, and the scroll bars display an odd pattern, but otherwise it seems to work. | SomeGuy | ||
VIA/S3G UniChrome IGP 64MB (KM400) | Works | Works | Failed | r40825 | Driver installation fails (KM400/KM266 PRO/P4M800 Chipset VGA Driver). | Unknown | Windows XP / Windows 2000 | |
VM QEMU Cirrus CL-54xx | Works | Works | Works | Missing | Requires ReactOS VESA driver being present at all times, see #2286 | Unknown | ||
VM VirtualBox Video | Works | Works | Works | Missing | Own driver starts up in 640x480x8, but supports all modes up to 1024x768x32. Necessary for Vbox OpenGL 3d host acceleration passthrough (it doesnt work in VirtualBox 3.1.0 - see add.4) | Haos | ||
VM VMWARE Video | Works | Works | Works | Missing | No known problems. | Unknown |
Known issues
- VESA Driver accepts only VESA 2.0 compatible adapters.
- 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. This causes installation of a Windows XP driver to be attempted even though such a driver file may not be in the Windows 2000 driver directory. As ReactOS does not fail when copying a nonexistent file, successful installation is reported; alas the driver file is not copied to the system32\driver directory. This will cause a "Successful install, please restart" window to appear at every boot.
Original drivers (VGA/VESA) are hardcoded, so the native ones are not really used #2286.- VirtualBox 3.1.0 Video driver is no longer providing 3d acceleration in ReactOS, due to missing Mm functionality #4996. Silencing the UNIMPLEMENTED macro in both functions in question is a possible workaround.
- Windows XP/Windows Server 2003 drivers should be used, as earlier ones are very likely to fail.