AMD Linux Graphics Drivers and How They Are Used in Slackware.

at0 · 08-14-2023, 04:25 PM

Sadly but startkwayland didn't work too. I've build kernel 6.4.10 as it was proposed but for the moment no luck with X's. Good that at least I have console available and can see what happens directly on the PC, not by SSH.

I think that this time the problem may be as described here:

Quote:

Originally Posted by Nille_kungen

I had problems with x-server with latest current.
I booted my backup kernel (6.2.5) and everything is fine so it seems to be the kernel.

So if I'll have time I'll try to build kernel from 6.2.x branch (since one of Ubuntu works for me too)

Edit: Kernel 6.2.16 didn't help to fix the issue. Only runlevel 3 console available.

garpu · 08-14-2023, 05:24 PM

Did you try swapping the 2 firmware files out? It looks like there's a significant regression in them that affects the 7600 booting.

at0 · 08-15-2023, 06:32 AM

Quote:

Originally Posted by garpu

Did you try swapping the 2 firmware files out? It looks like there's a significant regression in them that affects the 7600 booting.

Finally I've got everything working (apparently). There are no more error messages in dmesg log. The problem appears to be 100% firmware regression. I've replaced gc_11_0_* firmware in Slackware with those from my working Ubuntu. Then I've successfully started Slackware64-current system with KDE Plasma both with 6.2.16 and 6.4.10 kernels.

So the solution was - (updating kernel to something >6.2 (actually this was not necessary - LTS 6.1.46 works well) and using "correct" firmware.

Thanks all for your suggestions and time! Hope this will be also fixed upstream.

Edit: Maybe this was because of the issues addressed by these patches: https://git.kernel.org/pub/scm/linux...7aecdb52b5ff5f
Will try to use the "reverted" firmware after Pat will publish new firmware package for current.

garpu · 08-16-2023, 07:18 PM

Quote:

Originally Posted by at0

Edit: Maybe this was because of the issues addressed by these patches: https://git.kernel.org/pub/scm/linux...7aecdb52b5ff5f
Will try to use the "reverted" firmware after Pat will publish new firmware package for current.

Code:

a/kernel-firmware-20230814_0e048b0-noarch-1.txz: Upgraded.

Firmware and a kernel update today!

at0 · 08-17-2023, 02:32 AM

Quote:

Originally Posted by garpu

Code:

a/kernel-firmware-20230814_0e048b0-noarch-1.txz: Upgraded.

Firmware and a kernel update today!

Upgraded firmware and installed kernel 6.1.46 - boot was successful. There are a couple of warnings related to amd in dmesg but looks like everything works.
So that was firmware-only issue and I've just installed the new video card (RX 7600) at the wrong time - in those very couple of days when we've had a broken firmware.

Code:

[    0.000000] Linux version 6.1.46 (root@z-mp.slackware.lan) (gcc (GCC) 13.2.0, GNU ld version 2.41-slack151) #1 SMP PREEMPT_DYNAMIC Wed Aug 16 13:38:27 CDT 2023
[    0.000000] Command line: BOOT_IMAGE=/boot/vmlinuz root=/dev/nvme0n1p3
[    0.000000] BIOS-provided physical RAM map:
[    0.000000] BIOS-e820: [mem 0x0000000000000000-0x000000000009ffff] usable
.....
[    0.670015] amd_gpio AMDI0030:00: Invalid config param 0014
.....
[   48.791761] amdgpu 0000:2d:00.0: amdgpu: [drm] [PLANE:55:plane-3] async flip with non-fast update
[  837.779327] [drm] REG_WAIT timeout 1us * 150000 tries - optc32_disable_crtc line:152

PS: Backed up current kernel and firmware packages just in case...

cwizardone · 08-21-2023, 12:35 PM

Quote:

Linux 6.6 AMDGPU Driver To Expose Current & Average Power For Capable GPUs
By Michael Larabel. 21 August 2023.
On Friday AMD sent out another pull request of AMDGPU/AMDKFD driver changes for the upcoming Linux 6.6 merge window. With the Linux 6.5 release due out likely in one week and the cut-off having passed for new "feature" code for DRM-Next, this latest AMDGPU pull request was centered around bug-fixes but also with a few minor additions.............

The full story can be read at, https://www.phoronix.com/news/Linux-...GPU-More-HWMON

cwizardone · 10-24-2023, 10:30 AM

Quote:

AMD Making It More Clear When Their RadeonSI OpenGL Driver Is Being Used
By Michael Larabel. 24 October 2023.
AMD's RadeonSI Gallium3D driver has been around for a decade since the Radeon HD 7000 "Southern Islands" graphics card days while finally the OpenGL renderer string is being changed to reflect "RadeonSI" as the name of the driver in use...........

The full story can be found at, https://www.phoronix.com/news/Radeon...ually-Print-It

cwizardone · 04-11-2024, 07:49 AM

Quote:

Open-Source Radeon Driver Enables Support For Vulkan Video H.264/H.265 Encode
By Michael Larabel. 11 April 2024.
The open-source Radeon Vulkan driver within Mesa, RADV, has merged its support for handling Vulkan Video accelerated encoding for H.264 and H.265......

Read all about it at, https://www.phoronix.com/news/RADV-V...Ideo-H265-H264

garpu · 05-08-2024, 07:32 AM

So when trying to find a fix this weekend, the amdgpu people wanted amdgpu_gem_info. Is this a kernel debugging thing, because I couldn't find where/what it was. (And I've never done actual kernel debugging/bisecting.)

Petri Kaukasoina · 05-08-2024, 08:01 AM

Quote:

Originally Posted by garpu

So when trying to find a fix this weekend, the amdgpu people wanted amdgpu_gem_info. Is this a kernel debugging thing, because I couldn't find where/what it was. (And I've never done actual kernel debugging/bisecting.)

I don't have an amd gpu, but try

Code:

mount -t debugfs none /sys/kernel/debug

and look for it under /sys/kernel/debug.

garpu · 05-08-2024, 08:29 AM

Quote:

Originally Posted by Petri Kaukasoina

I don't have an amd gpu, but try

Code:

mount -t debugfs none /sys/kernel/debug

and look for it under /sys/kernel/debug.

Cool, thanks! Didn't think of that. I didn't notice anything, but to be fair, I'm not sure where I should be looking.

Petri Kaukasoina · 05-08-2024, 08:30 AM

Maybe

Code:

find /sys/kernel/debug -name amdgpu_gem_info

garpu · 05-08-2024, 08:51 AM

There it is! And it's in dri/0/, which makes the rest of their conversation make sense, when one person said their GPU was no longer dri/0, but dri/1. Thanks!