1554251 - Enable WebRender on Linux with AMD hardware and Mesa drivers

Status: RESOLVED FIXED

(Core :: Graphics: WebRender, enhancement, P3)

Description

[Andrew Osmond [:aosmond] (he/him)]

Similar to bug 1543217, let's enable WebRender on Linux if the user has AMD hardware and is using recent Mesa drivers.

Comment 1

[Andrew Osmond [:aosmond] (he/him)]

Attachment: Bug 1554251 - Enable WebRender on nightly for AMD hardware with Linux and Mesa drivers.

Comment 2

[Pulsebot]

Pushed by [e-mail]:
https://hg.mozilla.org/integration/mozilla-inbound/rev/cb677c177529
Enable WebRender on nightly for AMD hardware with Linux and Mesa drivers. r=jrmuizel

Comment 3

[Raul Gurzau (:RaulG)]

https://hg.mozilla.org/mozilla-central/rev/cb677c177529

Comment 4

[Viktor Jägersküpper]

With my AMD RV770 (Vendor ID: 0x1002, Device ID: 0x9442, Driver Vendor: mesa/r600, Driver Version: 19.0.5.0) I still get
WEBRENDER_QUALIFIED: blocked-device-too-old by env: Device too old

Mesa Version is obviously higher than 18.0.0.0, but I don't understand the code. Why is my hardware still blocked?

Comment 5

[Andrew Osmond [:aosmond] (he/him)]

(In reply to Viktor Jägersküpper from comment #4)

With my AMD RV770 (Vendor ID: 0x1002, Device ID: 0x9442, Driver Vendor: mesa/r600, Driver Version: 19.0.5.0) I still get
WEBRENDER_QUALIFIED: blocked-device-too-old by env: Device too old

Mesa Version is obviously higher than 18.0.0.0, but I don't understand the code. Why is my hardware still blocked?

We have only selectively turned on WebRender on certain AMD device IDs for the moment. So you are blocked because of your particular card, not because of the driver. The Intel and NVIDIA rollouts have been the same. We expect to add more devices over time as we gain confidence from low crash volumes and no bug reports, so I beg for patience :). You are of course welcome/encouraged to force it on via gfx.webrender.all in the meantime if your experience is good.

Comment 6

[Kyle Ferriter]

I'm using Nightly on Linux with Mesa driver on an Intel graphics card and webrender is not enabled by default.

For WEBRENDER_QUALIFIED I get "blocked-screen-too-large by env: Screen size too large". I'm using a 4k display with GNOME Wayland and 2x scaling. This may just be anecdotal but it seems to work fine when I force it with gfx.webrender.all. Right at startup it's a little wonky and the UI doesn't look right, but after it gets loaded after a few seconds it works well and is smooth. Even without webrender, at startup often the UI is not laid out correctly until I resize the window, forcing it to reevaluate the layouts.

Comment 7

[Darkspirit]

(In reply to Kyle Ferriter from comment #6)

I'm using Nightly on Linux with Mesa driver on an Intel graphics card and webrender is not enabled by default.

For WEBRENDER_QUALIFIED I get "blocked-screen-too-large by env: Screen size too large".

4K needs further optimizations especially for integrated Intel GPUs:
https://mozillagfx.wordpress.com/2019/04/30/webrender-newsletter-44/

I'm using a 4k display with GNOME Wayland and 2x scaling. This may just be anecdotal but it seems to work fine when I force it with gfx.webrender.all.

<3

Right at startup it's a little wonky and the UI doesn't look right, but after it gets loaded after a few seconds it works well and is smooth. Even without webrender, at startup often the UI is not laid out correctly until I resize the window, forcing it to reevaluate the layouts.

That sounds like bug 1502519 (or bug 1521175 or any of its not-as-duplicate-marked sisters). I'm seeing it everyday as well.