User Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:18.0) Gecko/18.0 Firefox/18.0 Build ID: 20120930030610 Steps to reproduce: installed latest AMD Radeon beta driver, technical version 22.214.171.124 on Win7 x64, Radeon 7850. Actual results: Driver was blocked. Expected results: Should not have been blocked according to block list: https://wiki.mozilla.org/Blocklisting/Blocked_Graphics_Drivers
Please attach the output of about:support
Component: Untriaged → Graphics
Product: Firefox → Core
I had just reverted to 8.6 to get hardware acceleration.. now i re-installed to get the about:support data and now it's not blocked anymore :-/
To determine the version, Firefox use a registry key. Maybe it hasn't been updated with the Beta driver. Can you still attach the about:support log to see which version it considers (8.9 or 9.1)?
Yeah, i probably tested without rebooting. I went to the Device Manager to confirm the driver version had been updated. Here's my about:support Graphics section: Adapter Description AMD Radeon HD 7800 Series Adapter Drivers aticfx64 aticfx64 aticfx64 aticfx32 aticfx32 aticfx32 atiumd64 atidxx64 atidxx64 atiumdag atidxx32 atidxx32 atiumdva atiumd6a atitmm64 Adapter RAM 2048 Device ID 0x6818 Direct2D Enabled true DirectWrite Enabled true (6.1.7601.17789) Driver Date 9-13-2012 Driver Version 126.96.36.199 GPU #2 Active false GPU Accelerated Windows 1/1 Direct3D 10 Vendor ID 0x1002 WebGL Renderer no information AzureCanvasBackend direct2d AzureContentBackend direct2d AzureFallbackCanvasBackend cairo
Status: UNCONFIRMED → RESOLVED
Last Resolved: 6 years ago
Resolution: --- → INVALID
I'm seeing the same thing with the driver being blocked. I HAVE fully rebooted (several times) since installing the beta driver (and Device Manager confirms that the driver version is 188.8.131.52). About:support -- Adapter Description RDPDD Chained DD Vendor ID 0x0000 Device ID 0x0000 Adapter RAM Unknown Adapter Drivers RDPDD Adapter Description (GPU #2) ATI Radeon HD 5700 Series Vendor ID (GPU #2) 0x1002 Device ID (GPU #2) 0x68b8 Adapter RAM (GPU #2) 1024 Adapter Drivers (GPU #2) aticfx64 aticfx64 aticfx64 aticfx32 aticfx32 aticfx32 atiumd64 atidxx64 atidxx64 atiumdag atidxx32 atidxx32 atiumdva atiumd6a atitmm64 Driver Version (GPU #2) 184.108.40.206 Driver Date (GPU #2) 9-13-2012 Direct2D Enabled Blocked for your graphics card because of unresolved driver issues. DirectWrite Enabled false (6.1.7601.17789) ClearType Parameters DISPLAY1 [ Gamma: 2200 Pixel Structure: RGB ClearType Level: 100 Enhanced Contrast: 50 ] DISPLAY5 [ Gamma: 2200 Pixel Structure: RGB ClearType Level: 100 Enhanced Contrast: 50 ] WebGL Renderer Blocked for your graphics card because of unresolved driver issues. GPU Accelerated Windows 0. Blocked for your graphics card because of unresolved driver issues.
Status: RESOLVED → REOPENED
Ever confirmed: true
Resolution: INVALID → ---
Version: 18 Branch → 16 Branch
It's blocked because your detected primary GPU (RDPDD Chained DD) is unknown. Is it blocked if you set your ATI GPU as your primary GPU?
Apologies. It seems that my fiance RDP'd into my machine earlier in the day while Firefox was open. Evidently that causes Firefox to degrade in such a manner (display driver-wise), even after the RDP session is severed and one logs into the desktop locally? Has that always been the behavior? I can confirm that restarting FF did successfully enable everything (as the ATI driver became the only display device). Should a bug be opened about the other behavior, or is the only way to solve it by restarting Firefox after any RDP session (if Firefox was open at the time of the session)? Thanks, and sorry for the false alarm.
Status: REOPENED → RESOLVED
Last Resolved: 6 years ago → 6 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.