Where did you install Firefox from? Help Mozilla uncover 3rd party websites that offer problematic Firefox installation by taking part in our campaign. There will be swag, and you'll be featured in our blog if you manage to report at least 10 valid reports!

Pomoc pśepytaś

Glědajśo se wobšudy pomocy. Njenapominajomy was nigda, telefonowy numer zawołaś, SMS pósłaś abo wósobinske informacije pśeraźiś. Pšosym dajśo suspektnu aktiwitu z pomocu nastajenja „Znjewužywanje k wěsći daś“ k wěsći.

Learn More

AMD GPU not utilized by Firefox.

  • 3 wótegrona
  • 1 ma toś ten problem
  • 7 naglědow
  • Slědne wótegrono wót Josh

more options

I am using an AMD RX 580 on a system with a Xeon processor. The latest stable KDE Manjaro. I'm testing using Basemark. When I run basemark on Chrome radeontop reports graphics card usage, as expected. When I run Basemark with Firefox, the GPU is not being utilized. I have tried changing the performance settings and "force enabled" in about:config to no avail. Any suggestions appreciated.

I am using an AMD RX 580 on a system with a Xeon processor. The latest stable KDE Manjaro. I'm testing using Basemark. When I run basemark on Chrome radeontop reports graphics card usage, as expected. When I run Basemark with Firefox, the GPU is not being utilized. I have tried changing the performance settings and "force enabled" in about:config to no avail. Any suggestions appreciated.

Wšykne wótegrona (3)

more options

Have you checked for updated drivers for that AMD RX 580 video card?

more options

I am running linux kernel 5.4.31-1. It is my understanding that the most up to date driver is already in the kernel and that installing an AMD driver makes performance worse. At one time I had tried using an AMD specific driver and the performance of the graphics card was much worse. Besides that, the card works with the same setup using Google Chrome.

more options

One of two things happened that resolved this...either Firefox 75 fixed this, or my installation of opencl-amd AUR from the Manjaro store fixed this. Either way...it's up and running now!