[SOLVED] Graphics does not work on new HP Elitebook with AMD Ryzen 5 PRO

hua · 05-22-2019, 01:07 PM

Hi all,

Can anyone suggest how to get the graphics work on my new Laptop? I would like to use Slackware (14.2 or current) on it. Unfortunately when I have installed a clean 14.2 the boot was hanging on some step - fb: switching to amdgpudrmfb...

I tried to set the nomodeset which solved the boot issue however I cannot start KDE.
I have upgraded all the packages (latest kernel) from the stable 14.2. This did not help.
I have upgraded to Slackware64-current with kernel 4.19.44. This did not help either (however it fixed the CPU hierarchy warning). I am not sure what to try first - customize X config, downgrade kernel to 4.15x, or recompile kernel with some additional tuning, maybe pass more kernel boot options?

This is my elilo.conf append section:
append="root=/dev/cryptvg/root nomodeset vga=normal ro resume=/dev/cryptvg/swap"

This is the exact CPU:
AMD Ryzen 5 PRO 2500U w/ Radeon Vega Mobile Gfx

The graphics:
Non-VGA unclassified device: Advanced Micro Devices, Inc. [AMD] Raven/Raven2/Renoir Non-Sensor Fusion Hub KMDF driver

I would like to keep this 4.19.44 kernel since only this kernel stopped to report CPU cache hierarchy warnings...
If I could fix the issue with KDE start I would like to upgrade to plasma5.

I am not sure if I understood it properly but I think the nomodeset actually disabled the attempt to use the AMD GPU...

Thanks for suggestions in advance

bassmadrigal · 05-22-2019, 02:01 PM

Did you just upgrade the kernel or the whole distro? If it was the first, that likely wouldn't be enough and you'd need to move the whole distro to -current. If you already did that, it's hard to guess what might be the issue.

The next step would be to get logs. Maybe the dmesg output along with the contents of /var/log/Xorg.0.log.

Timothy Miller · 05-22-2019, 02:44 PM

So, I'm not a Slackware user, so might not be able to help beyond the broadest ability. But I had to figure out how to make the EXACT same cpu/igp work on Debian Stretch, so I know what it entailed there.

What version is your mesa drivers? I know the older mesa drivers will NOT work with Vega graphics.

What version of amd/ati graphics firmware do you have? Again, only the newish firmware works with Vega.

Obviously with kernel 4.19, the drivers themselves should DEFINITELY be new enough, so I'm betting you either have older non-vega firmware, or your mesa drivers are still too old.

Nille_kungen · 05-22-2019, 04:16 PM

I use an ACER laptop with 2500u with slackware64-current multilib and it works works great out of the box with current and some ivrs overrides.
I can't say anything about plasma5 since i use stock KDE4.
Earlier bios/UEFI wasn't working as good as i should and i needed to boot with pci=noacpi but with later kernels and bios update things started to work better.
Linux 4.19 supports my hardware so i use stock kernel in current but i do still need an ivrs override "ivrs_ioapic[4]=00:14.0 ivrs_ioapic[5]=00:00.2" but you have another laptop so things differ.
Upgrading the bios/UEFI to latest available fixed many things for me so it can be a good start.

What happens when you try to start KDE?
Don't downgrade the kernel since it will only introduce new problems that needs workarounds.

could you post the output from
lspci -knn
cat /proc/interrupts
dmesg

hitest · 05-22-2019, 09:06 PM

Quote:

Originally Posted by bassmadrigal

Did you just upgrade the kernel or the whole distro? If it was the first, that likely wouldn't be enough and you'd need to move the whole distro to -current.

I agree. There have been many changes in Slackware since July 2016. It may be easier to do a clean install of Slackware64-current for your new hardware. Best of luck!

Slackware64-current

hua · 05-23-2019, 07:28 AM

Quote:

Originally Posted by hitest

I agree. There have been many changes in Slackware since July 2016. It may be easier to do a clean install of Slackware64-current for your new hardware. Best of luck!

Slackware64-current

I did a full upgrade. Thanks for the link! I did not know there is an iso image for current. I will try to reinstall from this image.

hitest · 05-23-2019, 06:54 PM

Quote:

Originally Posted by hua

Thanks for the link! I did not know there is an iso image for current. I will try to reinstall from this image.

You're welcome!

mrapathy · 05-23-2019, 07:25 PM

I am using current iso from 3-5-19 it has upgrades need for newer hardware for me it was a hauppauge usb tv tuner which is now working with no kernel patching. needed current and a audio package to get battletech working too. slackware 14.2 is soo old its crazy not to get current image.
havent had issues some have had with current.

would love to be having issues with ryzen cpu and newer video but what I got gets me by for now. wish I knew how I got such good hardware in past.

bassmadrigal · 05-24-2019, 12:20 AM

Quote:

Originally Posted by mrapathy

slackware 14.2 is soo old its crazy not to get current image.

It really depends on what you're running it on and what you need to do with your system. I am running 14.2 on a Ryzen system (albeit with a 4.19.x kernel, but I almost always run newer series of kernels on my stable releases), but on my new Ryzen APU system (upgrading my HTPC to gift my old one to my father-in-law so he'll have something to keep him occupied after his knee surgery), I will need to run -current since 14.2 has no support for Ryzen APU graphics.

In my usage, I'm not finding many limitations on 14.2 other than hardware support (there's been a few minor software limitations if I'm wanting the latest version of some programs -- this will vary drastically depending on what software you need to run).

hua · 05-27-2019, 12:06 PM

Unfortunately, the result is the same with fresh new install from the current iso. However it seems the system does not crash it just does not display the desktop after the "fb: switching to amdgpudrmfb from EFI VGA" message.

It's very interesting that I was able to start KDE one time when I connected my second external display to the HDMI port. Both screens were working and the laptop display was working even after I disconnected the HDMI port. However after reboot the screen does not start again. Strange.

I think this is the relevant part of dmesg:

Code:

[   18.555993] fb: switching to amdgpudrmfb from EFI VGA
[   18.557122] Console: switching to colour dummy device 80x25
[   18.557743] [drm] initializing kernel modesetting (RAVEN 0x1002:0x15DD 0x103C:0x83D5 0xD1).
[   18.558297] [drm] register mmio base: 0xE0700000
[   18.558302] [drm] register mmio size: 524288
[   18.558333] [drm] add ip block number 0 <soc15_common>
[   18.558336] [drm] add ip block number 1 <gmc_v9_0>
[   18.558340] [drm] add ip block number 2 <vega10_ih>
[   18.558343] [drm] add ip block number 3 <psp>
[   18.558347] [drm] add ip block number 4 <powerplay>
[   18.558350] [drm] add ip block number 5 <dm>
[   18.558353] [drm] add ip block number 6 <gfx_v9_0>
[   18.558357] [drm] add ip block number 7 <sdma_v4_0>
[   18.558360] [drm] add ip block number 8 <vcn_v1_0>
[   18.559361] [drm] VCN decode is enabled in VM mode
[   18.559368] [drm] VCN encode is enabled in VM mode
[   18.559371] [drm] VCN jpeg decode is enabled in VM mode
[   18.597266] [drm] BIOS signature incorrect 0 0
[   18.597287] resource sanity check: requesting [mem 0x000c0000-0x000dffff], which spans more than PCI Bus 0000:00 [mem 0x000c0000-0x000c3fff window]
[   18.597298] caller pci_map_rom+0x6a/0x1b0 mapping multiple BARs
[   18.597316] amdgpu 0000:03:00.0: Invalid PCI ROM header signature: expecting 0xaa55, got 0xffff
[   18.622476] ieee80211 phy0: Selected rate control algorithm 'iwl-mvm-rs'
[   18.622908] thermal thermal_zone6: failed to read out thermal zone (-61)
[   18.635959] [drm] BIOS signature incorrect 0 0
[   18.636066] [drm:amdgpu_get_bios [amdgpu]] *ERROR* Unable to locate a BIOS ROM
[   18.636076] amdgpu 0000:03:00.0: Fatal error during GPU init
[   18.636082] [drm] amdgpu: finishing device.
[   18.636635] amdgpu: probe of 0000:03:00.0 failed with error -22

hua · 05-28-2019, 12:15 AM

Oh again. I did not do my troubleshooting properly. When I googled the above error message I have found some discussions about UEFI settings.
The issue was caused by improper UEFI BIOS boot settings.Once I configured the proper BIOS boot settings and fixed the bootloader by eliloconfig it boots and starts KDE properly.

Thanks to all for effort.

Edit: I configured legacy boot off and selected UEFI boot only.

Nille_kungen · 05-28-2019, 12:09 PM

Did you need to append any overrides?
Do you have the latest bios installed? If everything works then there's no need to upgrade bios/UEFI.
That error doesn't matter if it still loads, it only means that it failed to load one vbios but it should load another.

hua · 05-29-2019, 08:30 AM

No. I did not append any overrides. I have upgraded/downgraded the BIOS several times (during troubleshooting) but now I have the latest.
Right now everything works perfectly. I can also see in dmesg that the amdgpu is properly initialized without any errors. So I am happy with the result.