User-Agent: Mozilla/5.0 (Windows NT 5.1; rv:2.0b8pre) Gecko/20101113 Firefox/4.0b8pre Build Identifier: Mozilla/5.0 (Windows NT 5.1; rv:2.0b8pre) Gecko/20101113 Firefox/4.0b8pre I can't enable hardware accelerated layers on my Radeon 9800 PRO 128 MB in beta 7 or Minefield. I have the newest DirectX package (June 2010) and tried drivers 9.1 and 10.2 (10.2 are latest, 9.1 are older but less buggy). I'm Using fully updated Windows XP 32-bit with SP3. All layers.* and gfx.* settings in about:config are in default state (tried also with a new profile). I tried Vendor ID spoofing in Minefield (to 0), but it changes nothing. Reproducible: Always Steps to Reproduce: 1. Install Firefox 4 beta 7 or Minefield 2. Start 3. Open about:support - the result is "GPU Accelerated Windows 0/1" Actual Results: Adapter Description: RADEON 9800 PRO Vendor ID: 1002 Device ID: 4e48 Adapter RAM: Unknown Adapter Drivers: ati2dvag Driver Version: 8.593.100.0 Driver Date: 2-10-2010 Direct2D Enabled: false DirectWrite Enabled: false GPU Accelerated Windows: 0/1 Expected Results: GPU Accelerated Windows: 1/1 (Direct3D)
Component: General → Graphics
Product: Firefox → Core
QA Contact: general → thebes
blocking2.0: --- → ?
It seems the GPU doesn't support 4096x4096 textures: http://forums.mozillazine.org/viewtopic.php?p=10125401#p10125401 I would suggest publishing a list of supported devices (and probably some older, but DX9 capable GPUs, with the reason why they do not work) or implement a feature, that would show what tests failed. The Radeon 9800 is a DX9 capable card, that's why I was confused when it didn't work.
Please renom if & when this bug gets confirmed.
blocking2.0: ? → ---
It seems like this is confirmed; the only question is whether we should say something in about:support about why d3d is disabled in this case...
Status: UNCONFIRMED → NEW
Ever confirmed: true
https://wiki.mozilla.org/Blocklisting/Blocked_Graphics_Drivers The minimum required ATI driver is 10.6. Can you try that on recent Firefox (7-10)? But you probably still won't get anything. Yes, the reason for disabling (texture size) should be shown in about:support, I'd vote for that.
(In reply to Boris Zbarsky (:bz) from comment #3) > It seems like this is confirmed; the only question is whether we should say > something in about:support about why d3d is disabled in this case... Seems bug 673490 could be for that.
Depends on: 673490
You need to log in before you can comment on or make changes to this bug.