Personal tools

Blocklisting/Blocked Graphics Drivers

From MozillaWiki

< Blocklisting(Difference between revisions)
Jump to: navigation, search
(Intel cards)
(How to force-enable blocked graphics features)
(25 intermediate revisions by 3 users not shown)
Line 59: Line 59:
 
=== Intel cards ===
 
=== Intel cards ===
  
We require the following Intel driver versions, or newer (September 2010), see {{bug|594877}}:
+
We require the following Intel driver versions, or newer (September 2010), see {{bug|594877}}.
 +
* You can determine the driver version by entering <tt>about:support</tt> in the Firefox location bar; look under the Graphics section.
 +
* The "GPU family" below doesn't necessarily match the "Adapter Description" in <tt>about:support</tt>. Indeed, Intel has multiple, overlapping product numbering schemes. For example, the "965 chipset family" encompasses the Q965 which is a GMA 3150 chip, and the G965 which is a GMA X3000 chip. Details of your Intel graphics chip are available from the Adapter tab of the Display Settings dialog in Windows. For example, in Windows Vista, one way to get to this in Windows Vista is right-click the desktop, choose Personalize > Display Settings > Display Settings > Monitor > Advanced Settings...  > Adapter, and look for the Adapter String under Adapter Information.
 +
* Intel GPUs have been grouped by families in the table below. For example, by "GMA X3000" we mean all Intel GMA X3000, X3100, X3500 products.
 
{| width="100%" cellspacing="1" cellpadding="1" border="1"
 
{| width="100%" cellspacing="1" cellpadding="1" border="1"
 
|-
 
|-
Line 156: Line 159:
  
 
For layers acceleration, we also block all old graphics adapters that do not fully support OpenGL 2.1 in hardware (use slow software fallbacks), or that can't render to non-power-of-two texture-backed framebuffers. That includes the following generations of GPUs: ATI Radeon X1000 and older, NVIDIA Geforce FX and older, and Intel GMA 950 and older.
 
For layers acceleration, we also block all old graphics adapters that do not fully support OpenGL 2.1 in hardware (use slow software fallbacks), or that can't render to non-power-of-two texture-backed framebuffers. That includes the following generations of GPUs: ATI Radeon X1000 and older, NVIDIA Geforce FX and older, and Intel GMA 950 and older.
 +
 +
For MSAA, we block all ATI cards except for AMD Radeon HD 6490M (device id 0x6760) and ATI Radeon HD 4670 (device id 0x9488). See Chromium issue 83153 [http://code.google.com/p/chromium/issues/detail?id=83153].
  
 
== On X11 ==
 
== On X11 ==
Line 163: Line 168:
 
WebGL is enabled by default, so it works if your OpenGL driver is whitelisted or if you bypass the blocking (see below).
 
WebGL is enabled by default, so it works if your OpenGL driver is whitelisted or if you bypass the blocking (see below).
  
Layers acceleration is not yet enabled by default because it's not entirely ready (there still are some visual glitches). You can enable it by setting '''layers.acceleration.force-enabled=true''' in about:config.
+
Layers acceleration is not yet enabled by default (see {{bug|594876}}). You can enable it by setting '''layers.acceleration.force-enabled=true''' in about:config.
  
Regarding OpenGL drivers, there is a very big difference between Firefox 4/5 on the one hand, and Firefox 6+ on the other hand.
+
The following drivers are whitelisted:
 +
* Mesa drivers are whitelisted if the Mesa version is at least 7.10.3 (see {{bug|659560}}).
 +
* For the NVIDIA driver, versions 257.21 and newer are whitelisted, exactly like on Windows (see above).
 +
* For the FGLRX (proprietary ATI) driver, we whitelist the newer versions that implement OpenGL 3.0 or newer. Indeed, FGLRX does not return any version number of its own, so we had to use the OpenGL version as a differentiator.
  
=== OpenGL on X11 in Firefox 4 and 5 ===
+
== On Android ==
  
In Firefox 4 and 5, only the NVIDIA proprietary driver is currently whitelisted because of many crashes in other drivers (see {{bug|616416}}, {{bug|622294}}, {{bug|621699}}, {{bug|589546}}), and difficulty determining driver info without risking crashing ([http://lists.freedesktop.org/archives/mesa-dev/2011-February/005267.html see this conversation]). Define the '''MOZ_GLX_IGNORE_BLACKLIST''' environment variable to bypass that.
+
OpenGL layers is always disabled, no matter what configuration we're on.
 
+
=== OpenGL on X11 in Firefox 6 and newer ===
+
 
+
In Firefox 6 and newer, we manage to safely get driver information, so we are able to whitelist the good drivers. The following drivers are whitelisted:
+
* Free Mesa-based drivers are whitelisted if the Mesa version is at least 7.10.
+
** In Firefox 6 only, Gallium3D drivers are blacklisted (see {{bug|624935}}). In Firefox 7 and newer, Gallium3D is no longer blacklisted.
+
* For the NVIDIA driver, versions 257.21 and newer are whitelisted, exactly like on Windows (see above).
+
* For the FGLRX (proprietary ATI) driver, we whitelist the newer versions that implement OpenGL 3.0 or newer. Indeed, FGLRX does not return any version number of its own, so we had to use the OpenGL version as a differentiator.
+
  
 
= How to force-enable blocked graphics features =
 
= How to force-enable blocked graphics features =
Line 184: Line 184:
  
 
To force-enable WebGL, go to about:config and set '''webgl.force-enabled=true'''.
 
To force-enable WebGL, go to about:config and set '''webgl.force-enabled=true'''.
 +
 +
To force-enable WebGL anti-aliasing, go to about:config and set '''webgl.msaa-force=true'''.
  
 
To force-enable Layers Acceleration, go to about:config and set '''layers.acceleration.force-enabled=true'''.
 
To force-enable Layers Acceleration, go to about:config and set '''layers.acceleration.force-enabled=true'''.
  
 
On Windows Vista and Windows 7, to force-enable Direct2D Content Acceleration, go to about:config and set '''gfx.direct2d.force-enabled=true'''.
 
On Windows Vista and Windows 7, to force-enable Direct2D Content Acceleration, go to about:config and set '''gfx.direct2d.force-enabled=true'''.
 
In Firefox 4 and 5 (not in Firefox 6 and newer), on X11 platforms (like Linux), the driver blacklist is implemented differently and bypassing it requires you to also define the '''MOZ_GLX_IGNORE_BLACKLIST''' environment variable. You can run Firefox using this command line:<br/>
 
<code>MOZ_GLX_IGNORE_BLACKLIST=1 firefox</code>
 
  
 
On Windows, you can also spoof your graphics system information to help debug driver blacklisting issues: see {{bug|604771}}.
 
On Windows, you can also spoof your graphics system information to help debug driver blacklisting issues: see {{bug|604771}}.
  
 
If force-enabling a feature doesn't work, that probably means that your hardware doesn't support it. For example, layers acceleration currently requires support for 4Kx4K textures, which rules out some graphics cards, [http://software.intel.com/en-us/articles/intel-gma-3000-and-x3000-developers-guide/ like the Intel G31/G33].
 
If force-enabling a feature doesn't work, that probably means that your hardware doesn't support it. For example, layers acceleration currently requires support for 4Kx4K textures, which rules out some graphics cards, [http://software.intel.com/en-us/articles/intel-gma-3000-and-x3000-developers-guide/ like the Intel G31/G33].

Revision as of 19:47, 13 February 2012

Contents

Downloaded blacklist

This is a list of all the GPU/driver/OS combinations that we have blocked using the downloaded Video card blacklisting feature of Firefox 4.

GPU Driver OS Features Reason Bug
NVIDIA NVS 3100M <= 258.96 Windows 7 Layers acceleration and Direct2D Driver crashes multiple times per day bug 635044
All NVIDIA hardware >= 7.0.0.0 Windows XP Layers acceleration Driver version does not match known NVIDIA drivers bug 638936, bug 639698

Compiled-in blacklist

The compiled-in blacklist is implemented separately for each OS/platform (Windows, Mac, X11).

On Windows

All vendors other than AMD/ATI, NVIDIA, Intel are blocked (bug 623338). This was required primarily by various crashes on virtual machines with unusual vendor names (bug 621411). We're open to whitelisting more vendors if needed.

Windows 2003 is identified as Windows XP for the present purposes.

Layers acceleration is blocked on Windows versions older than Windows XP.

NVIDIA cards

We require NVIDIA driver version 257.21 or newer (June 2010), see bug 623338.

Notice that 257.21 is the commercial version number. This corresponds to the last 5 digits in the technical version number, which for instance is 8.17.12.5721 on Windows 7/Vista.

On NVIDIA GeForce 6100/6150/6200 TurboCache cards, we block Direct3D 9 accelerated layers, see bug 612007, bug 644787, bug 645872.

On Optimus devices, ANGLE rendering for WebGL is blocked (bug 636870). So WebGL should still work, but will use the OpenGL driver.

AMD/ATI cards

We require ATI driver version 10.6 or newer (June 2010), see bug 623338.

Notice that 10.6 is the commercial version number. The actual check is performed on the technical version number, and we require it to be at least 8.741.0.0.

We block the OpenGL drivers on ATI cards on Windows, see bug 619773. This does not affect default functionality, as we use ANGLE instead of OpenGL by default for WebGL rendering anyway.

Intel cards

We require the following Intel driver versions, or newer (September 2010), see bug 594877.

  • You can determine the driver version by entering about:support in the Firefox location bar; look under the Graphics section.
  • The "GPU family" below doesn't necessarily match the "Adapter Description" in about:support. Indeed, Intel has multiple, overlapping product numbering schemes. For example, the "965 chipset family" encompasses the Q965 which is a GMA 3150 chip, and the G965 which is a GMA X3000 chip. Details of your Intel graphics chip are available from the Adapter tab of the Display Settings dialog in Windows. For example, in Windows Vista, one way to get to this in Windows Vista is right-click the desktop, choose Personalize > Display Settings > Display Settings > Monitor > Advanced Settings... > Adapter, and look for the Adapter String under Adapter Information.
  • Intel GPUs have been grouped by families in the table below. For example, by "GMA X3000" we mean all Intel GMA X3000, X3100, X3500 products.
Windows version GPU family Required driver version
Windows XP Intel GMA 500 6.14.11.1018
Windows XP Intel GMA 900 6.14.10.4764
Windows XP Intel GMA 950 6.14.10.4926
Windows XP Intel GMA 3150 6.14.10.5260
Windows XP Intel GMA X3000 6.14.10.5218
Windows XP Intel GMA X4500/HD 6.14.10.5284
Windows Vista Intel GMA 500 7.14.10.1006
Windows Vista Intel GMA 900 All versions are blocked
Windows Vista Intel GMA 950 7.14.10.1504
Windows Vista Intel GMA 3150 7.14.10.2124
Windows Vista Intel GMA X3000 7.15.10.1666
Windows Vista Intel GMA X4500/HD 8.15.10.2202
Windows 7 Intel GMA 500 5.0.0.2026
Windows 7 Intel GMA 900 All versions are blocked
Windows 7 Intel GMA 950 8.15.10.1930
Windows 7 Intel GMA 3150 8.14.10.2117
Windows 7 Intel GMA X3000 8.15.10.1930
Windows 7 Intel GMA X4500/HD 8.15.10.2202

We block Direct3D 10 features (including Direct2D) on buggy installations where the Intel driver version reported in the Windows Registry is not equal to the version of the driver DLL, igd10umd32.dll/igd10umd64.dll. See bug 590373.

Up to and including Firefox 6, on certain GPUs in the GMA X3000 generation (G35, GL960, GM965), we block Direct2D. See bug 595364. In Firefox 7 and newer, Direct2D is no longer blacklisted on these GPUs.

We block the OpenGL drivers on Intel cards on Windows, see bug 625118. This does not affect default functionality, as we use ANGLE instead of OpenGL by default for WebGL rendering anyway.

Dual-GPU systems

Our current blacklisting implementation does not properly support dual-GPU systems (bug 628129).

On Mac

For WebGL, we require Mac OS version 10.6 or newer. See bug 636611

For layers acceleration, we require Mac OS version 10.6.3 or newer. See bug 629016. One exception is <video> acceleration, which is enabled on all Mac OS versions.

For layers acceleration, we also block all old graphics adapters that do not fully support OpenGL 2.1 in hardware (use slow software fallbacks), or that can't render to non-power-of-two texture-backed framebuffers. That includes the following generations of GPUs: ATI Radeon X1000 and older, NVIDIA Geforce FX and older, and Intel GMA 950 and older.

For MSAA, we block all ATI cards except for AMD Radeon HD 6490M (device id 0x6760) and ATI Radeon HD 4670 (device id 0x9488). See Chromium issue 83153 [1].

On X11

XRender is used via Cairo, and is not subject to any blacklisting.

WebGL is enabled by default, so it works if your OpenGL driver is whitelisted or if you bypass the blocking (see below).

Layers acceleration is not yet enabled by default (see bug 594876). You can enable it by setting layers.acceleration.force-enabled=true in about:config.

The following drivers are whitelisted:

  • Mesa drivers are whitelisted if the Mesa version is at least 7.10.3 (see bug 659560).
  • For the NVIDIA driver, versions 257.21 and newer are whitelisted, exactly like on Windows (see above).
  • For the FGLRX (proprietary ATI) driver, we whitelist the newer versions that implement OpenGL 3.0 or newer. Indeed, FGLRX does not return any version number of its own, so we had to use the OpenGL version as a differentiator.

On Android

OpenGL layers is always disabled, no matter what configuration we're on.

How to force-enable blocked graphics features

If you would like to forcibly enable a graphics feature that is blocked on your system, follow these instructions. Warning: do this at your own risk. There usually are good reasons why features are blocked.

To force-enable WebGL, go to about:config and set webgl.force-enabled=true.

To force-enable WebGL anti-aliasing, go to about:config and set webgl.msaa-force=true.

To force-enable Layers Acceleration, go to about:config and set layers.acceleration.force-enabled=true.

On Windows Vista and Windows 7, to force-enable Direct2D Content Acceleration, go to about:config and set gfx.direct2d.force-enabled=true.

On Windows, you can also spoof your graphics system information to help debug driver blacklisting issues: see bug 604771.

If force-enabling a feature doesn't work, that probably means that your hardware doesn't support it. For example, layers acceleration currently requires support for 4Kx4K textures, which rules out some graphics cards, like the Intel G31/G33.