652071 - Hardware acceleration is Not functioning anymore on my Nightly.

Status: RESOLVED INVALID

(Core :: Graphics, defect)

Description

[Rakshith]

User-Agent:       Mozilla/5.0 (Windows NT 6.1; rv:6.0a1) Gecko/20110421 Firefox/6.0a1
Build Identifier: Mozilla/5.0 (Windows NT 6.1; rv:6.0a1) Gecko/20110421 Firefox/6.0a1

It was working until a few days ago. An update occurred to my nightly and Hardware acceleration doesnt work anymore even If I force it in "about:config"
the hardware acceleration is now defaulted to dx9 from dx10. 

Reproducible: Always




I'm using a x3100 graphics controller. But that doesn't mean you disable hardware acceleration on it. The hardware acceleration test site used to give me about 56 FPS but now it gives only 10 FPS.

Comment 1

[(mostly gone) XtC4UaLL [:xtc4uall]]

Please post the Content of the Graphics Section you can get via "about:support" with the HWA Option ticked.

Comment 2

[Rakshith]

Adapter DescriptionMobile Intel(R) 965 Express Chipset FamilyVendor ID8086Device ID2a02Adapter RAMUnknownAdapter Driversigdumdx32 igd10umd32Driver Version8.15.10.1930Driver Date9-23-2009Direct2D EnabledfalseDirectWrite Enabledfalse (6.1.7600.20905)WebGL RendererGoogle Inc. -- ANGLE -- OpenGL ES 2.0 (ANGLE 0.0.0.611)GPU Accelerated Windows1/1 Direct3D 9

Comment 3

[Rakshith]

They all Were "true" and D2D10 was enabled until recently an update disabled them all even though they are still appearing to be true in "about:config". Does this mean they forcibly disabled this feature in x3100 card?
here's a list of things from my "about:config's custom GFX filter"
pref name                                            Value
gfx.blacklist.direct2d                                 2
gfx.blacklist.layers.direct3d10                        2
gfx.blacklist.layers.direct3d10-1                      2
gfx.direct2d.force-enabled                            true
gfx.font_rendering.cleartype.always_use_for_content   true
gfx.font_rendering.directwrite.enabled                true
gfx.use_text_smoothing_setting                        true

and layers.acceleration.force-enabled is set to true and set all "JIT" to "true".
there are new prefs from yesterdays update  under the a part of their name "params"  with all their values set default to "-1"

Comment 4

[Siddhartha Dugar [:sdrocking]]

I also see this problem.

Comment 5

[Joe Drew (not getting mail)]

Those three gfx.blacklist values mean that your driver has been blocked by the downloaded blocklist, but that card hasn't been blocked by our downloaded blocklist in production.

Can you go to about:support, click "Copy all to clipboard" and then copy that in here? Also, can you look at about:config and copy the value of extensions.blocklist.url?

Comment 6

[Boris Zbarsky [:bzbarsky]]

Note that the force-enabled prefs not working is probably due to that gfx intialization change of zwol's....

Comment 7

[Joe Drew (not getting mail)]

Possibly; I don't remember precisely where force-enabled gets evaluated. gfx.blacklist.* does override all graphics blacklist evaluation, though.

Comment 8

[Rakshith]

about:support




  Application Basics

        Name
        Firefox

        Version
        6.0a1

        User Agent
        Mozilla/5.0 (Windows NT 6.1; rv:6.0a1) Gecko/20110422 Firefox/6.0a1

        Profile Directory

          Open Containing Folder

        Enabled Plugins

          about:plugins

        Build Configuration

          about:buildconfig

  Extensions

        Name

        Version

        Enabled

        ID

        Adblock Plus
        1.3.7a.2973
        true
        {d10d0bf8-f5b5-c8b4-a8b2-2b9879e08c5d}

  Modified Preferences

      Name

      Value

        browser.places.smartBookmarksVersion
        2

        browser.startup.homepage
        about:home

        browser.startup.homepage_override.buildID
        20110422030558

        browser.startup.homepage_override.mstone
        rv:6.0a1

        dom.ipc.plugins.java.enabled
        true

        extensions.lastAppVersion
        6.0a1

        gfx.blacklist.direct2d
        2

        gfx.blacklist.layers.direct3d10
        2

        gfx.blacklist.layers.direct3d10-1
        2

        gfx.direct2d.force-enabled
        true

        gfx.font_rendering.cleartype.always_use_for_content
        true

        gfx.font_rendering.directwrite.enabled
        true

        gfx.use_text_smoothing_setting
        true

        javascript.options.jitprofiling.chrome
        true

        javascript.options.methodjit.chrome
        true

        javascript.options.methodjit_always
        true

        layers.acceleration.force-enabled
        true

        network.cookie.prefsMigrated
        true

        places.database.lastMaintenance
        1303102689

        places.history.expiration.transient_current_max_pages
        64121

        privacy.cpd.cookies
        false

        privacy.cpd.sessions
        false

        privacy.sanitize.migrateFx3Prefs
        true

        privacy.sanitize.timeSpan
        0

        security.OCSP.disable_button.managecrl
        false

        security.disable_button.openCertManager
        false

        security.disable_button.openDeviceManager
        false

        security.warn_viewing_mixed
        false

  Graphics

        Adapter Description
        Mobile Intel(R) 965 Express Chipset Family

        Vendor ID
        8086

        Device ID
        2a02

        Adapter RAM
        Unknown

        Adapter Drivers
        igdumdx32 igd10umd32

        Driver Version
        8.15.10.1930

        Driver Date
        9-23-2009

        Direct2D Enabled
        false

        DirectWrite Enabled
        false (6.1.7600.20905)

        WebGL Renderer
        Google Inc. -- ANGLE -- OpenGL ES 2.0 (ANGLE 0.0.0.611)

        GPU Accelerated Windows
        1/1 Direct3D 9

Comment 9

[Rakshith]

extensions.blocklist.url       =      https://addons.mozilla.org/blocklist/3/%APP_ID%/%APP_VERSION%/%PRODUCT%/%BUILD_ID%/%BUILD_TARGET%/%LOCALE%/%CHANNEL%/%OS_VERSION%/%DISTRIBUTION%/%DISTRIBUTION_VERSION%/%PING_COUNT%/%TOTAL_PING_COUNT%/%DAYS_SINCE_LAST_PING%/

Comment 10

[Joe Drew (not getting mail)]

It's possible that you have a driver version mismatch. (This could result in those prefs being set, too.)

Benoit, can you tell Rakshith how to find out the version of the driver his DLLs are showing?

Comment 11

[Benoit Jacob [:bjacob] (mostly away)]

Rakshith: first, can you go to about:config, filter gfx.blacklist, and reset all the preferences there (gfx.blacklist.*) to their default state? (right-click on them).

To test Joe's idea about a driver version mismatch (could have happened if you recently upgraded your drivers): in the windows explorer, c:\windows\system32 or wherever your system DLLs are, find igd10umd32.dll, right-click, Properties, there you can find a version number. If that version number is different from 8.15.10.1930 that means that your driver is incorrectly installed; Firefox detects that and blocks hw accel in this case.

Comment 12

[Rakshith]

Yes ,I guess there been a mismatch since the version igd10umd32.dll says is 8.14.10.1930

Comment 13

[Rakshith]

so how do I get it working Right?

Comment 14

[Benoit Jacob [:bjacob] (mostly away)]

Thanks for checking this. Your Intel D3D10 driver is mis-installed, which has been a major cause crashes in the past (bug 590373) so Firefox detects that and decides to avoid using D3D10.

You can force-enable features as explained there:
https://wiki.mozilla.org/Blocklisting/Blocked_Graphics_Drivers#How_to_force-enable_blocked_graphics_features
In your case you will need to go to about:config and set layers.acceleration.force-enabled=true and gfx.direct2d.force-enabled=true.

However if you then get crashes, that will really mean that your driver is mis-installed and you will have to reinstall it.

Comment 15

[Joe Drew (not getting mail)]

OK, then everything is working as expected. Let's call this "invalid" because it's not really a bug.

I'm really interested in how this happened. Rakshith, did you reinstall your driver at any time?

Comment 16

[Siddhartha Dugar [:sdrocking]]

(In reply to comment #14)
> You can force-enable features as explained there:
> https://wiki.mozilla.org/Blocklisting/Blocked_Graphics_Drivers#How_to_force-enable_blocked_graphics_features
> In your case you will need to go to about:config and set
> layers.acceleration.force-enabled=true and gfx.direct2d.force-enabled=true

Doesn't help. I still don't see h/w acceleration. And about:config still shows the same gfx.blacklist values.

Comment 17

[Benoit Jacob [:bjacob] (mostly away)]

You may have to go to about:config and reset all the gfx.blacklist prefs.

Joe --> I'm about to file a bug about caching only the downloaded blacklist entries, instead of caching the blacklisting decisions. Do you agree on the principle? Not sure if this is what caused part of the issues there, but at least that would have taken that out of the equation.

Comment 18

[Siddhartha Dugar [:sdrocking]]

(In reply to comment #17)
> You may have to go to about:config and reset all the gfx.blacklist prefs.

Already tried that before posting.
Something I'd like to mention - it works on Aurora when forced but does not work on Nightly. Did something change recently?

Comment 19

[Joe Drew (not getting mail)]

(In reply to comment #17)
> You may have to go to about:config and reset all the gfx.blacklist prefs.
> 
> Joe --> I'm about to file a bug about caching only the downloaded blacklist
> entries, instead of caching the blacklisting decisions. Do you agree on the
> principle? Not sure if this is what caused part of the issues there, but at
> least that would have taken that out of the equation.

Totally agree. We can easily do this by bypassing all special logic (driver version etc) if the aDriverInfo parameter to GetFeatureStatusImpl is non-NULL.

Comment 20

[Rakshith]

A Problem I Notice when reinstalling the same driver (newest). Firefox Takes DLL version number from Device manager? Because there is a mismatch of driver numbers in there too. The igd10umd32.dll  version number in device manager shows 8.15.10.1930 but the same in the windows system files the Same DLL says version 8.14.10.1930  . SO there's a permanent mismatch and B/w the system driver and device manager. And this problem is persistent to other x3100 users as well since core igd10umd32.dll version number is untouched whereas the device manager has made a mistake and Firefox doesn't seem to understand that,putting us at a loss of performance. Is there a fix? or any kind of hack that will get us to manually choose drivers for Firefox? I guess firefox version checking should be be sourced to/by core windows driver files.

Comment 21

[Rakshith]

A Problem I Notice when reinstalling the same driver (newest). Firefox Takes DLL version number from Device manager? Because there is a mismatch of driver numbers in there too. The igd10umd32.dll  version number in device manager shows 8.15.10.1930 but the same in the windows system files the Same DLL says version 8.14.10.1930  . SO there's a permanent mismatch and B/w the system driver and device manager. And this problem is persistent to other x3100 users as well since core igd10umd32.dll version number is untouched whereas the device manager has made a mistake and Firefox doesn't seem to understand that,putting us at a loss of performance. Is there a fix? or any kind of hack that will get us to manually choose drivers for Firefox? I guess firefox version checking should be be sourced to/by core windows driver files than depending on device manager (if it checks driver version through that)

Comment 22

[Benoit Jacob [:bjacob] (mostly away)]

Firefox reads the version number from two places:
 1) straight from the igd10umd32.dll file
 2) from the Windows Registry at System\CurrentControlSet\Control\Class\DriverVersion

If these two version numbers are not the same, it blocks all D3D10 features.

If you want to force-enable D3D10 features, normally following the instructions in comment 14 should be enough. If that that doesn't work for you, that means there's a separate problem here (see my next comment below).

Comment 23

[Benoit Jacob [:bjacob] (mostly away)]

(In reply to comment #16)
> (In reply to comment #14)
> > You can force-enable features as explained there:
> > https://wiki.mozilla.org/Blocklisting/Blocked_Graphics_Drivers#How_to_force-enable_blocked_graphics_features
> > In your case you will need to go to about:config and set
> > layers.acceleration.force-enabled=true and gfx.direct2d.force-enabled=true
> 
> Doesn't help. I still don't see h/w acceleration. And about:config still shows
> the same gfx.blacklist values.

OK, (see below)

(In reply to comment #18)
> (In reply to comment #17)
> > You may have to go to about:config and reset all the gfx.blacklist prefs.
> 
> Already tried that before posting.
> Something I'd like to mention - it works on Aurora when forced but does not
> work on Nightly. Did something change recently?

Nothing that I know about, but regressions may happen so it would be very interesting to track this down. Can you please bisect this using the archived nightly builds,
http://ftp.mozilla.org/pub/mozilla.org/firefox/nightly/
Once we know the precise day when it regressed, we'll be much closer to understanding this problem.

Comment 24

[Benoit Jacob [:bjacob] (mostly away)]

(In reply to comment #22)
> System\CurrentControlSet\Control\Class\DriverVersion

er, sorry, this is probably not a correct key name, but i'm not in Windows at the moment to check. A search for DriverVersion will probably give the actual key on your machine.

Comment 25

[Joe Drew (not getting mail)]

force-enable is broken on Nightly because of bug 651498 - we're working on a fix!

Comment 26

[Rakshith]

(In reply to comment #25)
> force-enable is broken on Nightly because of bug 651498 - we're working on a
> fix!
So is is why HA stopped working?