iGPU and dGPU mix-up in GNOME

Bug #2033157 reported by Christian Pernegger
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
switcheroo-control (Ubuntu)
New
Undecided
Unassigned

Bug Description

This is a DESKTOP with a dGPU (Radeon 6600) and an iGPU (via Ryzen 7600X), both using amdgpu; the latter has not been disabled in the BIOS because I have other uses for it.

Currently there's one monitor attached, to the HDMI output of the dGPU. The expectation is that the dGPU be used for everything by default.

GNOME seems to consider this a hybrid setup, which I suppose it is. Unfortunately it identifies the dGPU as "integrated graphics" and the iGPU as "dedicated graphics". Meaning that it will run "normal" applications on the dGPU thinking it's the iGPU (so far, so good, it's the result that counts), but it will also run applications that are set to prefer the more powerful GPU on the iGPU thinking it's the dGPU.
Or try to, because while simple stuff, like glxgears, works, Steam for example merely crashes in a loop.
Obviously the wording on the context menu is the wrong way round as well, which is very confusing.

$ sudo switcherooctl list
Device: 0
  Name: Advanced Micro Devices, Inc. [AMD®/ATI] Navi 23 [Radeon RX 6600/6600 XT/6600M]
  Default: yes
  Environment: DRI_PRIME=pci-0000_03_00_0

Device: 1
  Name: Advanced Micro Devices, Inc. [AMD/ATI]
  Default: no
  Environment: DRI_PRIME=pci-0000_6e_00_0

The low-level configuration seems to be ok. The dGPU is the first device and the default device, leading me to believe it's GNOME's fault. Since switcheroo-control provides switcheroo-control.service, which in turn enables the GNOME integration, I reported this bug against it, but obviously feel free to move it.

* iGPU and dGPU should be identified and labelled correctly in GNOME.
* Assuming it doesn't make any sense to render stuff on an iGPU that has to go through the dGPU anyway because that has the output, the switcheroo integration (or the entire functionality) should be disabled when the stronger card is the primary card / the boot card / the one with the output anyway.

Workaround: disable switcheroo-control.service.

ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: switcheroo-control 2.4-3build2
ProcVersionSignature: Ubuntu 6.2.0-1009.9~22.04.1-lowlatency 6.2.13
Uname: Linux 6.2.0-1009-lowlatency x86_64
ApportVersion: 2.20.11-0ubuntu82.5
Architecture: amd64
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
Date: Sat Aug 26 16:11:15 2023
InstallationDate: Installed on 2023-08-25 (0 days ago)
InstallationMedia: Ubuntu 22.04.3 LTS "Jammy Jellyfish" - Release amd64 (20230807.2)
SourcePackage: switcheroo-control
UpgradeStatus: No upgrade log present (probably fresh install)

Revision history for this message
Christian Pernegger (fallenguru) wrote :
description: updated
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.