[Desktop-packages] [Bug 2006646] Re: hwacc branch builds that use minigbm will switch to software compositor on amd.
** Changed in: chromium-browser (Ubuntu) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to chromium-browser in Ubuntu. https://bugs.launchpad.net/bugs/2006646 Title: hwacc branch builds that use minigbm will switch to software compositor on amd. Status in chromium-browser package in Ubuntu: Fix Released Bug description: This pertains to the hwacc branches of snap_from_source chromium builds. Following the guide-0.9.1, we switched from system gbm to minigbm. (These switches are in args.gn) use_system_minigbm = false use_intel_minigbm = true use_amdgpu_minigbm = true This enables us to better support intel hardware. However, there seems to be a regression on other gpus. Chromium will switch to software compositing on amd. When I revert back to system gbm, I get hardware compositing again. See attached screenshot. To reproduce: build chromium in two different ways, and compare the output from the chrome://gpu url. tested on: Radeon RX580 GPU. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/2006646/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2006646] Re: hwacc branch builds that use minigbm will switch to software compositor on amd.
** Changed in: chromium-browser (Ubuntu) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to chromium-browser in Ubuntu. https://bugs.launchpad.net/bugs/2006646 Title: hwacc branch builds that use minigbm will switch to software compositor on amd. Status in chromium-browser package in Ubuntu: Fix Committed Bug description: This pertains to the hwacc branches of snap_from_source chromium builds. Following the guide-0.9.1, we switched from system gbm to minigbm. (These switches are in args.gn) use_system_minigbm = false use_intel_minigbm = true use_amdgpu_minigbm = true This enables us to better support intel hardware. However, there seems to be a regression on other gpus. Chromium will switch to software compositing on amd. When I revert back to system gbm, I get hardware compositing again. See attached screenshot. To reproduce: build chromium in two different ways, and compare the output from the chrome://gpu url. tested on: Radeon RX580 GPU. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/2006646/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2006646] Re: hwacc branch builds that use minigbm will switch to software compositor on amd.
** Merge proposal linked: https://code.launchpad.net/~b-stolk/chromium-browser/+git/snap-from-source/+merge/437855 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to chromium-browser in Ubuntu. https://bugs.launchpad.net/bugs/2006646 Title: hwacc branch builds that use minigbm will switch to software compositor on amd. Status in chromium-browser package in Ubuntu: In Progress Bug description: This pertains to the hwacc branches of snap_from_source chromium builds. Following the guide-0.9.1, we switched from system gbm to minigbm. (These switches are in args.gn) use_system_minigbm = false use_intel_minigbm = true use_amdgpu_minigbm = true This enables us to better support intel hardware. However, there seems to be a regression on other gpus. Chromium will switch to software compositing on amd. When I revert back to system gbm, I get hardware compositing again. See attached screenshot. To reproduce: build chromium in two different ways, and compare the output from the chrome://gpu url. tested on: Radeon RX580 GPU. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/2006646/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2006646] Re: hwacc branch builds that use minigbm will switch to software compositor on amd.
** Merge proposal linked: https://code.launchpad.net/~b-stolk/chromium-browser/+git/snap-from-source/+merge/437819 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to chromium-browser in Ubuntu. https://bugs.launchpad.net/bugs/2006646 Title: hwacc branch builds that use minigbm will switch to software compositor on amd. Status in chromium-browser package in Ubuntu: In Progress Bug description: This pertains to the hwacc branches of snap_from_source chromium builds. Following the guide-0.9.1, we switched from system gbm to minigbm. (These switches are in args.gn) use_system_minigbm = false use_intel_minigbm = true use_amdgpu_minigbm = true This enables us to better support intel hardware. However, there seems to be a regression on other gpus. Chromium will switch to software compositing on amd. When I revert back to system gbm, I get hardware compositing again. See attached screenshot. To reproduce: build chromium in two different ways, and compare the output from the chrome://gpu url. tested on: Radeon RX580 GPU. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/2006646/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2006646] Re: hwacc branch builds that use minigbm will switch to software compositor on amd.
Hard-coding the dri directory to point to the snap's dri dir fixes this, as I now see: Graphics Feature Status Canvas: Hardware accelerated Canvas out-of-process rasterization: Disabled Direct Rendering Display Compositor: Disabled Compositing: Hardware accelerated Multiple Raster Threads: Enabled OpenGL: Enabled Rasterization: Hardware accelerated Raw Draw: Disabled Video Decode: Hardware accelerated Video Encode: Software only. Hardware acceleration disabled Vulkan: Disabled WebGL: Hardware accelerated WebGL2: Hardware accelerated WebGPU: Disabled -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to chromium-browser in Ubuntu. https://bugs.launchpad.net/bugs/2006646 Title: hwacc branch builds that use minigbm will switch to software compositor on amd. Status in chromium-browser package in Ubuntu: In Progress Bug description: This pertains to the hwacc branches of snap_from_source chromium builds. Following the guide-0.9.1, we switched from system gbm to minigbm. (These switches are in args.gn) use_system_minigbm = false use_intel_minigbm = true use_amdgpu_minigbm = true This enables us to better support intel hardware. However, there seems to be a regression on other gpus. Chromium will switch to software compositing on amd. When I revert back to system gbm, I get hardware compositing again. See attached screenshot. To reproduce: build chromium in two different ways, and compare the output from the chrome://gpu url. tested on: Radeon RX580 GPU. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/2006646/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2006646] Re: hwacc branch builds that use minigbm will switch to software compositor on amd.
I've added logging to third_party/minigbm/src/amdgpu.c third_party/minigbm/src/drv.c This yielded: drm_version->name: amdgpu backend_list[0] = amdgpu drv_get_backend(13) returned 0x55bf084e4338 dri_init() failed for path /usr/lib/x86_64-linux-gnu/dri/radeonsi_dri.so driver radeonsi: No such file or directory backend init() failed: -19 [27925:27925:0221/111810.067118:WARNING:ozone_platform_wayland.cc(273)] Failed to find drm render node path. [27925:27925:0221/111810.068456:WARNING:wayland_buffer_manager_gpu.cc(437)] Failed to initialize drm render node handle. Checking with: sudo snap run --shell chromium ...it turns out that there is no /usr/lib/x86_64-linux-gnu/dri/ directory in the snap. NOTE: There is a /snap/chromium/current/usr/lib/x86_64-linux-gnu/dri directory, but that only contains video drivers, like radeonsi_drv_video.so ** Summary changed: - hwacc branch builds with minigbm switch to software compositor on amd. + hwacc branch builds that use minigbm will switch to software compositor on amd. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to chromium-browser in Ubuntu. https://bugs.launchpad.net/bugs/2006646 Title: hwacc branch builds that use minigbm will switch to software compositor on amd. Status in chromium-browser package in Ubuntu: In Progress Bug description: This pertains to the hwacc branches of snap_from_source chromium builds. Following the guide-0.9.1, we switched from system gbm to minigbm. (These switches are in args.gn) use_system_minigbm = false use_intel_minigbm = true use_amdgpu_minigbm = true This enables us to better support intel hardware. However, there seems to be a regression on other gpus. Chromium will switch to software compositing on amd. When I revert back to system gbm, I get hardware compositing again. See attached screenshot. To reproduce: build chromium in two different ways, and compare the output from the chrome://gpu url. tested on: Radeon RX580 GPU. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/2006646/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp