amdgpu-pro driver not being used

rusty725 · 2023-01-31 06:09:39

Hi All,

I've installed the following packages amd-ucode 20230117.7e4f0ed-1, amdgpu-pro-oglp 22.40_1518373-1, amf-amdgpu-pro 22.40_1518373-1, lib32-amdgpu-pro-oglp 22.40_1518373-1, lib32-vulkan-amdgpu-pro 22.40_1518373-1, vulkan-amdgpu-pro 22.40_1518373-1, xf86-video-amdgpu 22.0.0-1

when running glxinfo | grep "OpenGL vendor string" | cut -f2 -d":" | xargs , it returns AMD instead of Advanced Micro Devices, Inc.
lscpi -k , returns

0b:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] Navi 21 [Radeon RX 6800/6800 XT / 6900 XT] (rev c1)
Subsystem: ASRock Incorporation Device 5202
Kernel driver in use: amdgpu
Kernel modules: amdgpu

no vulkan-radeon is installed. However, mesa is installed.

Any help is appreciated.

apaz · 2023-01-31 07:26:55

amdgpu-pro do not work in Arch Linux directly. You have to start the program (for example glxinfo) with "progl". See:
https://wiki.archlinux.org/title/AMDGPU … ary_OpenGL
Without progl it is active by default mesa.

rusty725 · 2023-01-31 07:52:16

Thank You for answering, can I run "progl" in front of scripts ? and just your own opinion which driver set would you recommend to install ?

apaz · 2023-01-31 13:51:13

amdgpu + mesa have higher performance and compatibility than amdgpu-pro. Use the latter (with progl) only for programs that specifically require them. For example, I am forced to use them with DaVinci Resolve.
Another example; Blender works with mesa but needs OpenCL derived from amdgpu-pro. For this I don't need to use progl, but just install the AUR package "opencl-amd".

I also put in "amf" but can't get it to work....

I can't answer for the scripts, but it should work....

rusty725 · 2023-01-31 20:03:08

apaz wrote:

amdgpu + mesa have higher performance and compatibility than amdgpu-pro. Use the latter (with progl) only for programs that specifically require them. For example, I am forced to use them with DaVinci Resolve.
Another example; Blender works with mesa but needs OpenCL derived from amdgpu-pro. For this I don't need to use progl, but just install the AUR package "opencl-amd".
I also put in "amf" but can't get it to work....
I can't answer for the scripts, but it should work....

one last question if you don't mind. I get random black screen upon boot, restarting arch solves it. I wonder if its mesa driver or perhaps I'm missing something like xorg.conf file.

seth · 2023-01-31 21:07:50

Try to enable https://wiki.archlinux.org/title/Kernel … _KMS_start for amdgpu.
Though if you've the kms hook in mkinitcpio.conf, that should be used anyway.

rusty725 · 2023-02-01 01:44:30

seth wrote:

Try to enable https://wiki.archlinux.org/title/Kernel … _KMS_start for amdgpu.
Though if you've the kms hook in mkinitcpio.conf, that should be used anyway.

Thank You, added this, testing

# vim:set ft=sh
# MODULES
# The following modules are loaded before any boot hooks are
# run. Advanced users may wish to specify all system modules
# in this array. For instance:
# MODULES=(piix ide_disk reiserfs)
MODULES=(amdgpu)

Last edited by rusty725 (2023-02-01 01:45:36)

seth · 2023-02-01 06:44:48

a) is the "kms" hook there as well?
b) did you rebuild the initramfs afterwards (mkinicpio -P)?

rusty725 · 2023-02-01 08:45:11

seth wrote:

a) is the "kms" hook there as well?
b) did you rebuild the initramfs afterwards (mkinicpio -P)?

correct me if I'm wrong

# vim:set ft=sh
# MODULES
# The following modules are loaded before any boot hooks are
# run. Advanced users may wish to specify all system modules
# in this array. For instance:
# MODULES=(piix ide_disk reiserfs)
MODULES=(amdgpu)

# BINARIES
# This setting includes any additional binaries a given user may
# wish into the CPIO image. This is run last, so it may be used to
# override the actual binaries included by a given hook
# BINARIES are dependency parsed, so you may safely ignore libraries
BINARIES=()

# FILES
# This setting is similar to BINARIES above, however, files are added
# as-is and are not parsed in any way. This is useful for config files.
FILES=()

# HOOKS
# This is the most important setting in this file. The HOOKS control the
# modules and scripts added to the image, and what happens at boot time.
# Order is important, and it is recommended that you do not change the
# order in which HOOKS are added. Run 'mkinitcpio -H <hook name>' for
# help on a given hook.
# 'base' is _required_ unless you know precisely what you are doing.
# 'udev' is _required_ in order to automatically load modules
# 'filesystems' is _required_ unless you specify your fs modules in MODULES
# Examples:
## This setup specifies all modules in the MODULES setting above.
## No raid, lvm2, or encrypted root is needed.
# HOOKS=(base)
#
HOOKS=(base udev autodetect modconf block filesystems keyboard fsck kms)
## This setup will autodetect all modules for your system and should
## work as a sane default
# HOOKS=(base udev autodetect block filesystems)
#
## This setup will generate a 'full' image which supports most systems.
## No autodetection is done.
# HOOKS=(base udev block filesystems)
#
## This setup assembles a pata mdadm array with an encrypted root FS.
## Note: See 'mkinitcpio -H mdadm' for more information on raid devices.
# HOOKS=(base udev block mdadm encrypt filesystems)
#
## This setup loads an lvm2 volume group on a usb device.
# HOOKS=(base udev block lvm2 filesystems)
#
## NOTE: If you have /usr on a separate partition, you MUST include the
# usr, fsck and shutdown hooks.
HOOKS=(base udev autodetect modconf block filesystems keyboard fsck)

# COMPRESSION
# Use this to compress the initramfs image. By default, zstd compression
# is used. Use 'cat' to create an uncompressed image.
#COMPRESSION="zstd"
#COMPRESSION="gzip"
#COMPRESSION="bzip2"
#COMPRESSION="lzma"
#COMPRESSION="xz"
#COMPRESSION="lzop"
#COMPRESSION="lz4"

# COMPRESSION_OPTIONS
# Additional options for the compressor
#COMPRESSION_OPTIONS=()

initramfs was rebuild

Last edited by rusty725 (2023-02-01 08:58:24)

seth · 2023-02-01 11:22:03

Please use code tags, https://bbs.archlinux.org/help.php#bbcode
Did you add the second

HOOKS=(base udev autodetect modconf block filesystems keyboard fsck)

line?
The preceeding

HOOKS=(base udev autodetect modconf block filesystems keyboard fsck kms)

had the kms hook and that should™ have added the module to the initramfs anyway.
But the second line replaces the definition and that does not have the kms hook.

rusty725 · 2023-02-04 04:23:23

seth wrote:

Please use code tags, https://bbs.archlinux.org/help.php#bbcode
Did you add the second
HOOKS=(base udev autodetect modconf block filesystems keyboard fsck)
line?
The preceeding
HOOKS=(base udev autodetect modconf block filesystems keyboard fsck kms)
had the kms hook and that should™ have added the module to the initramfs anyway.
But the second line replaces the definition and that does not have the kms hook.

sorry couldn't respond earlier, I've added kms to the 2nd hook line, testing for now.

seth · 2023-02-04 07:19:19

You should probably rather just remove the second line - having two entries there is gonna bite you later (when you edit the wrong one and don't figure why it has no impact

The relevant question, though, was whether you originally did have the KMS hook (because then adding the amdgpu module would likely have been idempotent)

rusty725 · 2023-02-04 07:27:08

seth wrote:

You should probably rather just remove the second line - having two entries there is gonna bite you later (when you edit the wrong one and don't figure why it has no impact
The relevant question, though, was whether you originally did have the KMS hook (because then adding the amdgpu module would likely have been idempotent)

no I didn't have kms in any of those lines, switching from nvidia. so should I remove both then or leave 1st or 2nd line ?
Thank You

seth · 2023-02-04 07:59:56

You should™ have
1. ONE uncommented HOOKS like
2. Either the kms hook or amdgpu in the MODULES (or both)

The only relevant thing for the current situation is that

lsinitcpio /boot/initramfs-linux.img | grep amdgpu

shows that it's there.

rusty725 · 2023-02-04 08:30:08

seth wrote:

You should™ have
1. ONE uncommented HOOKS like
2. Either the kms hook or amdgpu in the MODULES (or both)
The only relevant thing for the current situation is that
lsinitcpio /boot/initramfs-linux.img | grep amdgpu
shows that it's there.

sudo lsinitcpio /boot/initramfs-linux.img | grep amdgpu
usr/lib/modules/6.1.9-arch1-1/kernel/drivers/gpu/drm/amd/amdgpu/
usr/lib/modules/6.1.9-arch1-1/kernel/drivers/gpu/drm/amd/amdgpu/amdgpu.ko

Last edited by rusty725 (2023-02-04 09:18:52)

seth · 2023-02-04 08:53:04

Please use "code" tags, not "quote" tags. Edit your post in this regard.

usr/lib/modules/6.1.9-arch1-1/kernel/drivers/gpu/drm/amd/amdgpu/amdgpu.ko

rusty725 · 2023-02-04 09:19:31

seth wrote:

Please use "code" tags, not "quote" tags. Edit your post in this regard.
usr/lib/modules/6.1.9-arch1-1/kernel/drivers/gpu/drm/amd/amdgpu/amdgpu.ko

my bad, is there anything else should be done ?

seth · 2023-02-04 09:21:13

Nope.

Arch Linux

#1 2023-01-31 06:09:39

amdgpu-pro driver not being used

#2 2023-01-31 07:26:55

Re: amdgpu-pro driver not being used

#3 2023-01-31 07:52:16

Re: amdgpu-pro driver not being used

#4 2023-01-31 13:51:13

Re: amdgpu-pro driver not being used

#5 2023-01-31 20:03:08

Re: amdgpu-pro driver not being used

#6 2023-01-31 21:07:50

Re: amdgpu-pro driver not being used

#7 2023-02-01 01:44:30

Re: amdgpu-pro driver not being used

#8 2023-02-01 06:44:48

Re: amdgpu-pro driver not being used

#9 2023-02-01 08:45:11

Re: amdgpu-pro driver not being used

#10 2023-02-01 11:22:03

Re: amdgpu-pro driver not being used

#11 2023-02-04 04:23:23

Re: amdgpu-pro driver not being used

#12 2023-02-04 07:19:19

Re: amdgpu-pro driver not being used

#13 2023-02-04 07:27:08

Re: amdgpu-pro driver not being used

#14 2023-02-04 07:59:56

Re: amdgpu-pro driver not being used

#15 2023-02-04 08:30:08

Re: amdgpu-pro driver not being used

#16 2023-02-04 08:53:04

Re: amdgpu-pro driver not being used

#17 2023-02-04 09:19:31

Re: amdgpu-pro driver not being used

#18 2023-02-04 09:21:13

Re: amdgpu-pro driver not being used

Board footer