Issues with AMD Vega 11

I managed to find the cause in the journalctl logs after removing the dates and being able to diff.

In the non-working version, I get these entries:

kernel: [drm] amdgpu kernel modesetting enabled.
kernel: amdgpu: Virtual CRAT table created for CPU
kernel: amdgpu: Topology: Add CPU node
kernel: [drm] initializing kernel modesetting (RAVEN 0x1002:0x15DD 0x103C:0x8626 0xD6).
kernel: [drm] register mmio base: 0xB0600000
kernel: [drm] register mmio size: 524288
kernel: [drm] add ip block number 0 <soc15_common>
kernel: [drm] add ip block number 1 <gmc_v9_0>
kernel: [drm] add ip block number 2 <vega10_ih>
kernel: [drm] add ip block number 3 <psp>
kernel: [drm] add ip block number 4 <powerplay>
kernel: [drm] add ip block number 5 <dm>
kernel: [drm] add ip block number 6 <gfx_v9_0>
kernel: [drm] add ip block number 7 <sdma_v4_0>
kernel: [drm] add ip block number 8 <vcn_v1_0>
kernel: usbcore: registered new interface driver usbhid
kernel: usbhid: USB HID core driver
kernel: input: PixArt HP USB Optical Mouse as /devices/pci0000:00/0000:00:01.2/0000:01:00.0/usb2/2-3/2-3.3/2-3.3.1/2-3.3.1:1.0/0003:03F0:094A.0001/input/input3
kernel: hid-generic 0003:03F0:094A.0001: input,hidraw0: USB HID v1.11 Mouse [PixArt HP USB Optical Mouse] on usb-0000:01:00.0-3.3.1/input0
kernel: [drm] BIOS signature incorrect 0 0
kernel: resource: resource sanity check: requesting [mem 0x00000000000c0000-0x00000000000dffff], which spans more than PCI Bus 0000:00 [mem 0x000c0000-0x000cbfff window]
kernel: caller pci_map_rom+0x69/0x1a0 mapping multiple BARs
kernel: amdgpu 0000:0a:00.0: Invalid PCI ROM header signature: expecting 0xaa55, got 0xffff
kernel: [drm] BIOS signature incorrect 0 0
kernel: amdgpu 0000:0a:00.0: amdgpu: Unable to locate a BIOS ROM
kernel: amdgpu 0000:0a:00.0: amdgpu: Fatal error during GPU init
kernel: amdgpu 0000:0a:00.0: amdgpu: amdgpu: finishing device.
kernel: amdgpu 0000:0a:00.0: probe with driver amdgpu failed with error -22
kernel: usb 2-3.3.2: New USB device found, idVendor=046d, idProduct=c31c, bcdDevice=49.20
kernel: usb 2-3.3.2: New USB device strings: Mfr=1, Product=2, SerialNumber=0
kernel: usb 2-3.3.2: Product: USB Keyboard
kernel: usb 2-3.3.2: Manufacturer: Logitech
kernel: PM: Image not found (code -22)

And for the working version this section looks like this:

kernel: [drm] amdgpu kernel modesetting enabled.
kernel: amdgpu: Virtual CRAT table created for CPU
kernel: amdgpu: Topology: Add CPU node
kernel: [drm] initializing kernel modesetting (RAVEN 0x1002:0x15DD 0x103C:0x8626 0xD6).
kernel: [drm] register mmio base: 0xB0600000
kernel: [drm] register mmio size: 524288
kernel: [drm] add ip block number 0 <soc15_common>
kernel: [drm] add ip block number 1 <gmc_v9_0>
kernel: [drm] add ip block number 2 <vega10_ih>
kernel: [drm] add ip block number 3 <psp>
kernel: [drm] add ip block number 4 <powerplay>
kernel: [drm] add ip block number 5 <dm>
kernel: [drm] add ip block number 6 <gfx_v9_0>
kernel: [drm] add ip block number 7 <sdma_v4_0>
kernel: [drm] add ip block number 8 <vcn_v1_0>
kernel: usbcore: registered new interface driver usbhid
kernel: usbhid: USB HID core driver
kernel: input: PixArt HP USB Optical Mouse as /devices/pci0000:00/0000:00:01.2/0000:01:00.0/usb2/2-3/2-3.3/2-3.3.1/2-3.3.1:1.0/0003:03F0:094A.0001/input/input3
kernel: hid-generic 0003:03F0:094A.0001: input,hidraw0: USB HID v1.11 Mouse [PixArt HP USB Optical Mouse] on usb-0000:01:00.0-3.3.1/input0
kernel: [drm] BIOS signature incorrect 0 0
kernel: resource: resource sanity check: requesting [mem 0x00000000000c0000-0x00000000000dffff], which spans more than PCI Bus 0000:00 [mem 0x000c0000-0x000cbfff window]
kernel: caller pci_map_rom+0x69/0x1a0 mapping multiple BARs
kernel: amdgpu 0000:0a:00.0: amdgpu: Fetched VBIOS from ROM BAR
kernel: amdgpu: ATOM BIOS: SWBRT34978.001
kernel: [drm] VCN decode is enabled in VM mode
kernel: [drm] VCN encode is enabled in VM mode
kernel: [drm] JPEG decode is enabled in VM mode
kernel: usb 2-3.3.2: new low-speed USB device number 8 using xhci_hcd
kernel: amdgpu 0000:0a:00.0: vgaarb: deactivate vga console
kernel: amdgpu 0000:0a:00.0: amdgpu: Trusted Memory Zone (TMZ) feature enabled
kernel: [drm] vm size is 262144 GB, 4 levels, block size is 9-bit, fragment size is 9-bit
kernel: amdgpu 0000:0a:00.0: amdgpu: VRAM: 1024M 0x000000F400000000 - 0x000000F43FFFFFFF (1024M used)
kernel: amdgpu 0000:0a:00.0: amdgpu: GART: 1024M 0x0000000000000000 - 0x000000003FFFFFFF
kernel: [drm] Detected VRAM RAM=1024M, BAR=1024M
kernel: [drm] RAM width 128bits DDR4
kernel: [drm] amdgpu: 1024M of VRAM memory ready
kernel: [drm] amdgpu: 7459M of GTT memory ready.
kernel: [drm] GART: num cpu pages 262144, num gpu pages 262144
kernel: [drm] PCIE GART of 1024M enabled.
kernel: [drm] PTB located at 0x000000F401E00000
kernel: amdgpu: hwmgr_sw_init smu backed is smu10_smu
kernel: [drm] Found VCN firmware Version ENC: 1.15 DEC: 3 VEP: 0 Revision: 0
kernel: amdgpu 0000:0a:00.0: amdgpu: Will use PSP to load VCN firmware
kernel: amdgpu 0000:0a:00.0: amdgpu: reserve 0x400000 from 0xf43fc00000 for PSP TMR
kernel: amdgpu 0000:0a:00.0: amdgpu: RAS: optional ras ta ucode is not available
kernel: amdgpu 0000:0a:00.0: amdgpu: RAP: optional rap ta ucode is not available
kernel: amdgpu 0000:0a:00.0: amdgpu: SECUREDISPLAY: securedisplay ta ucode is not available

So, the important bit is probably:

kernel: amdgpu 0000:0a:00.0: Invalid PCI ROM header signature: expecting 0xaa55, got 0xffff
kernel: [drm] BIOS signature incorrect 0 0
kernel: amdgpu 0000:0a:00.0: amdgpu: Unable to locate a BIOS ROM
kernel: amdgpu 0000:0a:00.0: amdgpu: Fatal error during GPU init
kernel: amdgpu 0000:0a:00.0: amdgpu: amdgpu: finishing device.
kernel: amdgpu 0000:0a:00.0: probe with driver amdgpu failed with error -22

While in the working session it finds the ROM (despite “BIOS signature incorrect”):

kernel: amdgpu 0000:0a:00.0: amdgpu: Fetched VBIOS from ROM BAR
kernel: amdgpu: ATOM BIOS: SWBRT34978.001

Can we get anywhere from there?

According to this: [SOLVED] Amdgpu driver BIOS ROM not found at boot in Ryzen 2500U / Kernel & Hardware / Arch Linux Forums the issue is using legacy boot, which I am using. Switching to UEFI is supposed to solve the issue. So I will reinstall Manjaro with UEFI.

1 Like

Before you do that, it is quite simple to switch from BIOS to UEFI without reinstalling. I did it earlier this year using Manjaro’s instructions: 4 Switching from BIOS to UEFI

1 Like

Thanks, that’s good advice! Since I had nothing installed on this installation, I’ll do it cleanly, though.

1 Like

Switching to UEFI did it… What a hassle!

1 Like

This topic was automatically closed 3 days after the last reply. New replies are no longer allowed.