[SOLVED] Trouble with AMDGPU

Sigi · 2023-08-27 21:06:38

I feel so ashamed about this one that I post in the Newbie corner despite being an Archer since 2005

So I have a Thinkpad with Intel and AMD graphics. And I had it running smoothly for a year. But since the "mesa hickup" a few months ago I can't get graphics to properly work again.
I don't have an xorg.conf anymore and no PRIME. Worked great that way until recently...
Whenever AMD should kick in for the heavy lifting, the screen is "tearing" in those areas, i.e. playing videos in VLC. I can use "--disable-gpu" for some programs and they work properly.

I've now tried almost all can think of, currently that means I deinstalled most amd related drivers. Had the oglp ones for a while which I also deinstalled.

# inxi -G
Graphics:
  Device-1: Intel CometLake-U GT2 [UHD Graphics] driver: i915 v: kernel
  Device-2: AMD Lexa [Radeon 540X/550X/630 / RX 640 E9171 MCM]
    driver: amdgpu v: kernel
  Device-3: Azurewave Integrated Camera driver: uvcvideo type: USB
  Display: server: X.Org v: 21.1.8 with: Xwayland v: 23.2.0 driver: X:
    loaded: intel dri: radeonsi gpu: i915 resolution: 1920x1080~60Hz
  API: OpenGL v: 4.6 Mesa 23.1.6 renderer: AMD Radeon 550X Series
    (polaris12 LLVM 15.0.7 DRM 3.52 6.4.12-arch1-1)

# xrandr --listproviders
Providers: number : 1
Provider 0: id: 0x47 cap: 0xb, Source Output, Sink Output, Sink Offload crtcs: 4 outputs: 5 associated providers: 0 name:Intel

xrandr lists only 1 provider currently.

Any tips on what I could try? Followed the wiki for AMDGPU. I have xf86-video-amdgpu installed.

Last edited by Sigi (2023-08-28 19:19:15)

Sigi · 2023-08-27 21:22:55

# lspci -vnn
00:02.0 VGA compatible controller [0300]: Intel Corporation CometLake-U GT2 [UHD Graphics] [8086:9b41] (rev 02) (prog-if 00 [VGA controller])
	Subsystem: Lenovo CometLake-U GT2 [UHD Graphics] [17aa:507a]
	Flags: bus master, fast devsel, latency 0, IRQ 137
	Memory at c1000000 (64-bit, non-prefetchable) [size=16M]
	Memory at a0000000 (64-bit, prefetchable) [size=256M]
	I/O ports at 4000 [size=64]
	Expansion ROM at 000c0000 [virtual] [disabled] [size=128K]
	Capabilities: [40] Vendor Specific Information: Len=0c <?>
	Capabilities: [70] Express Root Complex Integrated Endpoint, MSI 00
	Capabilities: [ac] MSI: Enable+ Count=1/1 Maskable- 64bit-
	Capabilities: [d0] Power Management version 2
	Capabilities: [100] Process Address Space ID (PASID)
	Capabilities: [200] Address Translation Service (ATS)
	Capabilities: [300] Page Request Interface (PRI)
	Kernel driver in use: i915
	Kernel modules: i915
...
03:00.0 Display controller [0380]: Advanced Micro Devices, Inc. [AMD/ATI] Lexa [Radeon 540X/550X/630 / RX 640 / E9171 MCM] [1002:6987] (rev c0)
	Subsystem: Lenovo Lexa [Radeon 540X/550X/630 / RX 640 / E9171 MCM] [17aa:507a]
	Flags: bus master, fast devsel, latency 0, IRQ 138
	Memory at b0000000 (64-bit, prefetchable) [size=256M]
	Memory at c0000000 (64-bit, prefetchable) [size=2M]
	I/O ports at 3000 [size=256]
	Memory at c2300000 (32-bit, non-prefetchable) [size=256K]
	Expansion ROM at c2340000 [disabled] [size=128K]
	Capabilities: [48] Vendor Specific Information: Len=08 <?>
	Capabilities: [50] Power Management version 3
	Capabilities: [58] Express Legacy Endpoint, MSI 00
	Capabilities: [a0] MSI: Enable+ Count=1/1 Maskable- 64bit+
	Capabilities: [100] Vendor Specific Information: ID=0001 Rev=1 Len=010 <?>
	Capabilities: [270] Secondary PCI Express
	Capabilities: [320] Latency Tolerance Reporting
	Capabilities: [370] L1 PM Substates
	Kernel driver in use: amdgpu
	Kernel modules: amdgpu

seth · 2023-08-27 21:39:10

no PRIME … Whenever AMD should kick in … xrandr lists only 1 provider currently

W/o prime AMD won't kick in - please post your Xorg log, https://wiki.archlinux.org/title/Xorg#General

But apparently you're also using xf86-video-intel.
Just try to remove all xf86-video-* packages (but the missing output provider inidcates more problems, notably since the chip doesn't look like a 3D controller only)

Sigi · 2023-08-27 22:06:59

I tried this but then X didn't start anymore until I reinstalled xf86-video-intel. For some reason my /var/log/Xorg.0.log is 3 weeks old. Is this somewhere else now?

Sigi · 2023-08-27 22:11:42

Also: I seem to be able to use DRI_PRIME=1 to force programs to use intel instead of the AMD card. But I guess solving the AMD trouble is still the better path...

seth · 2023-08-28 05:38:26

You're looking at the wrong location for the xorg log (see the link I posted, rootless x11 servers will log in ~/.local/share/xorg) and if removing xf86-video-intel "breaks" your Xorg server, you reference it in some local config.

grep -ri intel /{etc,usr/share}/X11/xorg.conf*

If you're really using "DRI_PRIME=1" to use the intel card, that/some config must also turn the amd chip into the primary GPU - do you use optimus-manager or so?

Sigi · 2023-08-28 19:11:55

Thanks already a lot for your time!

I'm not using optimus-manager but I found the correct log in .local and this helped some:

[    43.402] (EE) AIGLX error: dlopen of /usr/lib/dri/i965_dri.so failed (/usr/lib/dri/i965_dri.so: cannot open shared object file: No such file or directory)
[    43.402] (EE) AIGLX error: unable to load driver i965

Trying out switching to mesa-amber now...

edit: This did it!! It works! Thanks sooo much SETH!

Last edited by Sigi (2023-08-28 19:16:35)

seth · 2023-08-28 19:46:17

You don't want to use mesa-amber w/ a cometlake chip; the error you see is common for xf86-video-intel - which you also don't want to use.
Post your xorg log and the grep result from #6, if we're gonna fix this, we're gonna fix this right

Sigi · 2023-08-28 21:11:14

Alright, I like your enthusiasm I went back to mesa, deinstalled xf86-video-{amdgpu,intel} and removed what I had in 30-intel.conf ("intel" driver and "DRI3").
Current xorg log:
http://ix.io/4EMQ

seth · 2023-08-28 21:17:46

More a compulsion neurosis - you're running on the intel chip, AMD should be available throug DRI_PRIME and both are operated by the modesetting driver.
There's only one output and it's wired to the intel chip.

Did you replace mesa-amber w/ mesa again?
How does the system perform clinically?
Any tearing or other issues?

Sigi · 2023-08-28 21:22:12

seth wrote:

More a compulsion neurosis - you're running on the intel chip, AMD should be available throug DRI_PRIME and both are operated by the modesetting driver.
There's only one output and it's wired to the intel chip.
Did you replace mesa-amber w/ mesa again?

Yes

How does the system perform clinically?
Any tearing or other issues?

All works great as far as I can say. My problems with tearing, "--dasable-gpu" etc are solved. Video plays. Xrandr shows two outputs.

Do you have a crypto tipjar or something?

seth · 2023-08-28 21:34:54

Arch takes donations, https://archlinux.org/donate/
I do this for personal entertainment.

Sigi · 2023-08-29 11:43:14

seth wrote:

Arch takes donations, https://archlinux.org/donate/
I do this for personal entertainment.

Donated 20$ just now, thanks again! You're awesome.

Arch Linux

#1 2023-08-27 21:06:38

[SOLVED] Trouble with AMDGPU

#2 2023-08-27 21:22:55

Re: [SOLVED] Trouble with AMDGPU

#3 2023-08-27 21:39:10

Re: [SOLVED] Trouble with AMDGPU

#4 2023-08-27 22:06:59

Re: [SOLVED] Trouble with AMDGPU

#5 2023-08-27 22:11:42

Re: [SOLVED] Trouble with AMDGPU

#6 2023-08-28 05:38:26

Re: [SOLVED] Trouble with AMDGPU

#7 2023-08-28 19:11:55

Re: [SOLVED] Trouble with AMDGPU

#8 2023-08-28 19:46:17

Re: [SOLVED] Trouble with AMDGPU

#9 2023-08-28 21:11:14

Re: [SOLVED] Trouble with AMDGPU

#10 2023-08-28 21:17:46

Re: [SOLVED] Trouble with AMDGPU

#11 2023-08-28 21:22:12

Re: [SOLVED] Trouble with AMDGPU

#12 2023-08-28 21:34:54

Re: [SOLVED] Trouble with AMDGPU

#13 2023-08-29 11:43:14

Re: [SOLVED] Trouble with AMDGPU

Board footer