[SOLVED] amdgpu drivers do not load

PFleur · 2023-04-08 02:18:53

After trying an HDMI adapter instead of DVI everything worked

I'm trying to set up the drivers for my system, I followed the Xorg and amdgpu pages installing the xorg-server, mesa, and xf86-video-amdgpu. After I added 'amdgpu' to the modules array of mkinitcpio, regenerated, created modprobe.d/amdgpu.conf and added 'options amdgpu si_support=1 [linebreak] options amdgpu cik_support=0' and, again, regenerated initramfs. None of this worked as even with loading it with kernel parameters 'radeon.si_support=0 amdgpu.si_support=1 radeon.cik_support=0 amdgpu.cik_support=1' it doesn't work.
The following are relevant portions of lspci output

lspci -v | grep -A1 -e VGA -e 3D
01:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] Ellsmere [Radeon RX 470/480/570/570X/580/580X/590] (rev ef) (prog-if 00 [VGA controller])

Last edited by PFleur (2023-08-16 16:12:14)

Scimmia · 2023-04-08 04:16:22

Forget all of that, none of it matters. What does the entire relevant block in lspci -v show? That grep eliminates all of the useful info.

PFleur · 2023-04-08 18:14:16

Scimmia wrote:

Forget all of that, none of it matters. What does the entire relevant block in lspci -v show? That grep eliminates all of the useful info.

01:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] Ellesmere [Radeon RX 470/480/570/570X/580/580X/590] (rev ef) (prog-if 00 [VGA controller])
Subsystem: ASUSTeK Computer Inc. Device 04c2
Flags: bus master, fast devsel, latency 0, IRQ 11
Memory at d0000000 (64-bit, prefetchable) [size=256M]
Memory at e0000000 (64-bit, prefetchable) [size=2M]
I/O ports at e000 [size=256]
Memory at efe00000 (32-bit, non-prefetchable) [size=256K]
Expansion ROM at 000c0000 [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: Emable- Count=1/1 Maskable- 64vit+
Capabilities: [100] Vendor Specific Information: ID=0001 Rev=1 Len= 010 <?>
Capabilities: [150] Advanced Error Reporting
Capabilities: [200] Physical Resizable BAR
Capabilities: [270] Secondary PCI Express
Capabilities: [2b0] Address Translation Service (ATS)
Capabilities: [2c0] Page Request Interface (PRI)
Capabilities: [2d0] Process Address Space ID (PASID)
Capabilities: [320] Latency Tolerance Reporting
Capabilities: [328] Alternative Routing-ID Interpretation (ARI)
Capabilities: [370] L1 PM Substates
Kernel modules: amdgpu

Last edited by PFleur (2023-04-08 21:28:43)

seth · 2023-04-08 19:58:58

Please use [code][/code] tags.
Edit your post in this regard.

Next, please post your complete system journal for the boot:

sudo journalctl -b | curl -F 'file=@-' 0x0.st

PFleur · 2023-04-08 23:57:40

seth wrote:

Please use [code][/code] tags.
Edit your post in this regard.
Next, please post your complete system journal for the boot:
sudo journalctl -b | curl -F 'file=@-' 0x0.st

http://0x0.st.HX9q.txt

Scimmia · 2023-04-09 03:30:33

Apr 08 16:53:24 archuser kernel: Command line: BOOT_IMAGE=/vmlinuz-linux root=UUID=beebe35f-b38b-42cf-8b08-9063a315aabd rw loglevel=3 quiet nomodeset

Modern drivers REQUIRE modesetting. You cannot use nomodeset.

PFleur · 2023-04-09 04:37:35

Scimmia wrote:

Apr 08 16:53:24 archuser kernel: Command line: BOOT_IMAGE=/vmlinuz-linux root=UUID=beebe35f-b38b-42cf-8b08-9063a315aabd rw loglevel=3 quiet nomodeset

Modern drivers REQUIRE modesetting. You cannot use nomodeset.

The issue is whenever I use anything other than

nomodeset

I have a blank screen upon booting after the ramdisc is loaded

Last edited by PFleur (2023-04-09 04:39:58)

loqs · 2023-04-09 04:41:45

Post the full system journal for a boot without nomodeset. You can use `journalctl -b #` where # is a negative integer such that -1 would be the previous boot.

PFleur · 2023-04-09 06:25:05

Thank you for the clarification, the boot journal is then

https://0x0.st/HXp2.txt

seth · 2023-04-09 07:34:43

Apr 08 23:19:59 archuser systemd[1]: Reached target Graphical Interface.
…
Apr 08 23:20:39 archuser systemd-logind[284]: New session 1 of user root.
Apr 08 23:20:39 archuser login[306]: ROOT LOGIN ON tty1

How does that happen? Seems too slow for an autologin?
What is your graphical.target?
Can you boot the multi-user.target (2nd link below)?

Apr 08 23:19:58 archuser kernel: amdgpu 0000:01:00.0: [drm] Cannot find any crtc or sizes

What kind of monitor do you have attached? Can you try another one?
Do you have linux-firmware installed?

Try the LTS kernel as well as passing

amdgpu.audio=0 amdgpu.dpm=0 amdgpu.bapm=0 amdgpu.aspm=0 amdgpu.runpm=0 pcie_aspm=off

to the kernel.
"amdgpu.dpm=0" can be a problem in and by itself, so try w/o it first and only add it as last test.

PFleur · 2023-04-09 17:26:29

seth wrote:

Apr 08 23:19:59 archuser systemd[1]: Reached target Graphical Interface.
…
Apr 08 23:20:39 archuser systemd-logind[284]: New session 1 of user root.
Apr 08 23:20:39 archuser login[306]: ROOT LOGIN ON tty1
How does that happen? Seems too slow for an autologin?
What is your graphical.target?
Can you boot the multi-user.target (2nd link below)?
Apr 08 23:19:58 archuser kernel: amdgpu 0000:01:00.0: [drm] Cannot find any crtc or sizes
What kind of monitor do you have attached? Can you try another one?
Do you have linux-firmware installed?
Try the LTS kernel as well as passing
amdgpu.audio=0 amdgpu.dpm=0 amdgpu.bapm=0 amdgpu.aspm=0 amdgpu.runpm=0 pcie_aspm=off
to the kernel.
"amdgpu.dpm=0" can be a problem in and by itself, so try w/o it first and only add it as last test.

I don't know how to check what my graphical.target is other than

systemctl list-units --type=target
graphical.targer loaded active active Graphical Interface

when setting multi-user.target both as a kernel parameter and
through

systemctl set-default multi-user.target

both led to a blank screen after the loading ramdisk message.

Currently I'm using a Huion Kamvas GT-191 as a monitor and don't have power chords for any other.

For firmware I'm running the latest of linux-firmware along with having updated other firmware packages due to mkinitcpio complaining

running linux-lts with the kernel parameters both with and without 'amdgpu.dpm=0' also lead to a blank screen after the ramdisk is loaded.

seth · 2023-04-09 18:02:10

Currently I'm using a Huion Kamvas GT-191 as a monitor and don't have power chords for any other.

That's a pen display and likely the cause for this.
Ideally first try a proper™ monitor to make sure this is the cause.

You could try to enforce a mode https://www.kernel.org/doc/Documentation/fb/modedb.rst and/or inject an edid, https://wiki.archlinux.org/title/Kernel … s_and_EDID
But I've no experience w/ this kind of graphics tablet

Arch Linux

#1 2023-04-08 02:18:53

[SOLVED] amdgpu drivers do not load

#2 2023-04-08 04:16:22

Re: [SOLVED] amdgpu drivers do not load

#3 2023-04-08 18:14:16

Re: [SOLVED] amdgpu drivers do not load

#4 2023-04-08 19:58:58

Re: [SOLVED] amdgpu drivers do not load

#5 2023-04-08 23:57:40

Re: [SOLVED] amdgpu drivers do not load

#6 2023-04-09 03:30:33

Re: [SOLVED] amdgpu drivers do not load

#7 2023-04-09 04:37:35

Re: [SOLVED] amdgpu drivers do not load

#8 2023-04-09 04:41:45

Re: [SOLVED] amdgpu drivers do not load

#9 2023-04-09 06:25:05

Re: [SOLVED] amdgpu drivers do not load

#10 2023-04-09 07:34:43

Re: [SOLVED] amdgpu drivers do not load

#11 2023-04-09 17:26:29

Re: [SOLVED] amdgpu drivers do not load

#12 2023-04-09 18:02:10

Re: [SOLVED] amdgpu drivers do not load

Board footer