This site will have limited functionality while we undergo maintenance to improve your experience. If an article doesn't solve your issue and you want to ask a question, we have our support community waiting to help you at @FirefoxSupport on Twitter and/r/firefox on Reddit.

Search Support

Avoid support scams. We will never ask you to call or text a phone number or share personal information. Please report suspicious activity using the “Report Abuse” option.

Learn More

I have a blacklisted graphic driver (radeon 1950x pro) with no available update -- suggetions for a work around?

  • 2 svar
  • 4 har dette problemet
  • 1 view
  • Siste svar av t0rey

more options

I gave a blacklisted graphics driver for radeon 1950x pro (ATI) that has no available update. From what I can tell, because my driver version are not supported I am suffering from 'glitchy' performances, especially in flash-based websites (eg: the game Zuma Blitz suffers highly from what appears frame-rate issues).

Any suggestions?

I gave a blacklisted graphics driver for radeon 1950x pro (ATI) that has no available update. From what I can tell, because my driver version are not supported I am suffering from 'glitchy' performances, especially in flash-based websites (eg: the game Zuma Blitz suffers highly from what appears frame-rate issues). Any suggestions?

Endret av t0rey

All Replies (2)

more options

Unfortunately there is not much you can do.

However there is no reason to downgrade to 3.6. There is no functionality in Firefox 4 which gets disabled when your driver is blacklisted and which is enabled in Firefox 3.6. You're "only" missing out on faster graphics as well webgl, neither of which are available in Firefox 3.6.

more options

Some websites are 'glitchy' so there must be some impact vs the two versions. For example, a simple flash game like Zuma Blitz suffers from what appears to be frame-rate issues. While 3.6.x does not.

Youtube even is glitchy now. Google's maps. Ect.

And before it's suggested, I have updated flash to double check that wasn't the issue.