Graphics issue [radeon firmware load and d-bus start]

nenadandric · July 25, 2017, 11:15am

I have an issue with graphics (R7 260X) and Leap 42.2. I was using opensource driver and everything worked well. Except openCL. So I tried amdgpu-pro even though I know it’s not officially supported. And it didn’t work. So I removed it. But some problems appeared.

I have two displays (monitor on DVI and TV on HDMI). And if both cables are connected to the card, PC doesn’t start. Even though if the second screen is turned off. It is stuck in the infinite loop
https://1drv.ms/i/s!AtXdCsq8Yz4OhqFOiJWMIt8w3ALI5w
The thing is, the first part of message appears before disk encryption password is prompted, and it passes without problem. But after I choose to boot to Leap, it gets stuck.

I noticed similar behavior in this thread
https://forums.opensuse.org/showthread.php/512809-Strange-behavior-when-resuming-from-sleep-with-Radeon-card

When I disconnect second screen, there are still those uvd/vce errors, but it boots to KDE. And when I log in, I get “Could not start D bus” errors, like this one.
https://forums.opensuse.org/showthread.php/520628-Could-not-start-D-bus-Can-you-call-qdbus-qt5
The thing is - I just click OK and system works (programs, sleep-resume, etc.). But graphics performance is awful. Just before these things, I have tried Tomb Raider (2013) and worked quite well with my card. Now, it is impossible to get more than 1FPS.

So, does anyone knows what have I done Do I need to re-install Leap 42.2? Or upgrade to 42.3 and hope it will resolve this? There was 2 or 3 minor kernel updates since then but the problem remained.

wolfi323 · July 25, 2017, 12:03pm

Well, how exactly did you install it? How did you remove it?

Can you please post /var/log/Xorg.0.log?

Is kernel-firmware installed?
Try to run mkinitrd, maybe the firmware is missing from the initrd (though the kernel updates should have created a fresh initrd too).

Is that a recent screenshot?
I notice that it shows kernel 4.4.70, but the current one is 4.4.74…

nenadandric · July 25, 2017, 6:17pm

I was following these instructions for (un)installation process. I know it is made for SLED, but I thought it might work
https://support.amd.com/en-us/kb-articles/Pages/How-To-Install-Uninstall-AMDGPU-PRO-driver-on-a-SLED-SLES-12-SP-2-Based-System.aspx

Here is xorg log
https://app.syncwerk.de/f/b0edf14201/

and here is mkinitrd
https://app.syncwerk.de/f/ececa38f9e/
kernel-firmware is installed. Screenshot is older, from month ago. As I said, I waited for few kernel upgrades, hoping it will resolve an issue. And nothing helps. It looks like upgrade to 42.3 is the next step

wolfi323 · July 25, 2017, 9:36pm

So it wasn’t via rpm packages, right?

Well, then likely you didn’t really uninstall it, or the uninstaller left something on your system.

Just to rule out the most obvious thing: you did run amdgpu-pro-uninstall as root?

Here is xorg log
https://app.syncwerk.de/f/b0edf14201/

Unfortunately that requires me to login, which I can’t.

Can you please upload it to susepaste.org?

and here is mkinitrd
https://app.syncwerk.de/f/ececa38f9e/
kernel-firmware is installed.

Well, it can’t find the firmware files it seems.
Maybe the AMD installer/uninstaller removed them?

Try to reinstall kernel-firmware and run mkinitrd again.

sudo zypper in -f kernel-firmware
sudo mkinitrd

nenadandric · July 26, 2017, 6:07am

Here are the same logs
http://paste.opensuse.org/27905069
http://paste.opensuse.org/5397773
Yes I run everything (install/uninstall) as root

I tried reinstalling kernel-firmware but it didn’t help. I upgraded to Leap 42.3. Now everything works great. Though I still get this (similar) error at boot, but besides that message, I haven’t noticed any issues. I’ll try kernel-firmware reinstall again to see if it will fix it, but I it’s not that important as long as everything works
https://1drv.ms/i/s!AtXdCsq8Yz4OhqpNjuTAsf7GUzXM6Q
It looks like Tomb Raider runs even better than earlier (I suppose it’s due to Mesa upgrade), so I’m happy for that

Thank you very much for help

wolfi323 · July 26, 2017, 8:29am

Ok, so the radeon driver is in use.
But:

   126.036] (II) RADEON(0): GPU accel disabled or not working, using shadowfb for KMS
...
   126.166] (WW) RADEON(0): Direct rendering disabled
   126.166] (II) RADEON(0): Acceleration disabled
...
   126.172] (II) AIGLX: Screen 0 is not DRI2 capable
   126.172] (EE) AIGLX: reverting to software rendering
   126.223] (II) AIGLX: enabled GLX_MESA_copy_sub_buffer
   126.224] (II) AIGLX: Loaded and initialized swrast
   126.224] (II) GLX: Initialized DRISWRAST GL provider for screen 0

This of course explains why it’s slow…

I still think that’s related to the “missing” firmware though.

I upgraded to Leap 42.3. Now everything works great. Though I still get this (similar) error at boot, but besides that message, I haven’t noticed any issues.

Which one?
Probably not the one about “Can’t load firmware”…

From what you write, it looks like the remaining message is rather harmless though.

I’ll try kernel-firmware reinstall again to see if it will fix it, but I it’s not that important as long as everything works

I doubt that it will help, that was supposed to fix dracut/mkinitrd not finding the files to include.
But that obviously should be fixed now, otherwise I wouldn’t expect a satisfactory graphics performance…

It looks like Tomb Raider runs even better than earlier (I suppose it’s due to Mesa upgrade), so I’m happy for that

That maybe, and also the whole DRM/low-level graphics stack has been backported from Kernel 4.9 or later.
(it’s in a separate package drm-kmp-default which can be uninstalled in case of problems)

nenadandric · July 27, 2017, 6:17am

Yes, it is can’t laod firmware “Bonaire_vce”
https://1drv.ms/i/s!AtXdCsq8Yz4OhqpNjuTAsf7GUzXM6Q

But nothing regarding VCE is in xorg log

   810.674] (II) RADEON(0): [DRI2] Setup complete   810.674] (II) RADEON(0): [DRI2]   DRI driver: radeonsi
   810.674] (II) RADEON(0): [DRI2]   VDPAU driver: radeonsi
   810.674] (II) RADEON(0): Front buffer size: 16320K
   810.674] (II) RADEON(0): VRAM usage limit set to 193226K
   810.674] (II) RADEON(0): SYNC extension fences enabled
   810.674] (II) RADEON(0): Present extension enabled
   810.674] (==) RADEON(0): DRI3 enabled
   810.674] (==) RADEON(0): Backing store enabled
   810.674] (II) RADEON(0): Direct rendering enabled
   810.787] (II) RADEON(0): Use GLAMOR acceleration.
   810.787] (II) RADEON(0): Acceleration enabled
   810.787] (==) RADEON(0): DPMS enabled
   810.787] (==) RADEON(0): Silken mouse enabled
   810.787] (II) RADEON(0): Set up textured video (glamor)
   810.787] (II) RADEON(0): [XvMC] Associated with GLAMOR Textured Video.
   810.787] (II) RADEON(0): [XvMC] Extension initialized.
   810.787] (II) RADEON(0): RandR 1.2 enabled, ignore the following RandR disabled message.
   810.788] (--) RandR disabled

malcolmlewis · July 27, 2017, 7:14am

On Thu 27 Jul 2017 04:26:01 AM CDT, nenadandric wrote:

wolfi323;2831288 Wrote:
>
> Which one?
> Probably not the one about “Can’t load firmware”…
>
> From what you write, it looks like the remaining message is rather
> harmless though.
>
Yes, it is can’t laod firmware “Bonaire_vce”
https://1drv.ms/i/s!AtXdCsq8Yz4OhqpNjuTAsf7GUzXM6Q

But nothing regarding VCE is in xorg log

Code:

810.674] (II) RADEON(0): [DRI2] Setup complete 810.674] (II)
RADEON(0): [DRI2] DRI driver: radeonsi 810.674] (II) RADEON(0):
[DRI2] VDPAU driver: radeonsi 810.674] (II) RADEON(0): Front
buffer size: 16320K 810.674] (II) RADEON(0): VRAM usage limit set
to 193226K 810.674] (II) RADEON(0): SYNC extension fences enabled
810.674] (II) RADEON(0): Present extension enabled
810.674] (==) RADEON(0): DRI3 enabled
810.674] (==) RADEON(0): Backing store enabled
810.674] (II) RADEON(0): Direct rendering enabled
810.787] (II) RADEON(0): Use GLAMOR acceleration.
810.787] (II) RADEON(0): Acceleration enabled
810.787] (==) RADEON(0): DPMS enabled
810.787] (==) RADEON(0): Silken mouse enabled
810.787] (II) RADEON(0): Set up textured video (glamor)
810.787] (II) RADEON(0): [XvMC] Associated with GLAMOR Textured
Video. 810.787] (II) RADEON(0): [XvMC] Extension initialized.
810.787] (II) RADEON(0): RandR 1.2 enabled, ignore the following
RandR disabled message. 810.788] (–) RandR disabled

Hi
I have a R4/R5 Mullins Sea Island card (same as the Bonaire), I run a
amdgpu kmp and a later version of xf86-video-amdgpu which adds CIK
support in my home repo;

Also tested with 42.3, only need the amdgu and kmp package, plus remove
the drm kmp.

–
Cheers Malcolm °¿° SUSE Knowledge Partner (Linux Counter #276890)
openSUSE Leap 42.2|GNOME 3.20.2|4.4.74-18.20-default
If you find this post helpful and are logged into the web interface,
please show your appreciation and click on the star below… Thanks!

wolfi323 · July 28, 2017, 2:25pm

Well, I suppose you can ignore that then. The Xorg log looks fine now.
VCE (Video Coding Engine, i.e. hardware support for encoding H.264 videos) probably won’t work though, I suppose.

Still a bit strange, as the “missing” file is actually part of kernel-firmware:

rpm -ql kernel-firmware |grep BONAIRE
/lib/firmware/radeon/BONAIRE_ce.bin
/lib/firmware/radeon/BONAIRE_mc.bin
/lib/firmware/radeon/BONAIRE_mc2.bin
/lib/firmware/radeon/BONAIRE_me.bin
/lib/firmware/radeon/BONAIRE_mec.bin
/lib/firmware/radeon/BONAIRE_pfp.bin
/lib/firmware/radeon/BONAIRE_rlc.bin
/lib/firmware/radeon/BONAIRE_sdma.bin
/lib/firmware/radeon/BONAIRE_smc.bin
/lib/firmware/radeon/BONAIRE_uvd.bin
/lib/firmware/radeon/BONAIRE_vce.bin

(that’s on 42.3)

Maybe it’s not been added to the initrd for some reason, or something’s broken there… (the “Invalid ROM contents” message might be relevant)

nenadandric · July 29, 2017, 9:49am

Yes, I see it’s in the firmware. And glxinfo returns “Yes” and vainfo h264 decode is supported. So I suppose everything is ok

glxinfo | grep "direct rendering"
**direct rendering**: Yes

vainfo
libva info: VA-API version 0.39.4
libva info: va_getDriverName() returns 0
libva info: Trying to open /usr/lib64/dri/radeonsi_drv_video.so
libva info: Found init function __vaDriverInit_0_39
libva info: va_openDriver() returns 0
vainfo: VA-API version: 0.39 (libva 1.7.3)
vainfo: Driver version: mesa gallium vaapi
vainfo: Supported profile and entrypoints
      VAProfileMPEG2Simple            : VAEntrypointVLD
      VAProfileMPEG2Main              : VAEntrypointVLD
      VAProfileVC1Simple              : VAEntrypointVLD
      VAProfileVC1Main                : VAEntrypointVLD
      VAProfileVC1Advanced            : VAEntrypointVLD
      VAProfileH264ConstrainedBaseline: VAEntrypointVLD
      VAProfileH264Main               : VAEntrypointVLD
      VAProfileH264High               : VAEntrypointVLD
      VAProfileNone                   : VAEntrypointVideoProc

Thank you very much for support

wolfi323 · July 29, 2017, 12:49pm

I have no idea whether it may be a local problem on your system though, or that’s broken in general…

And glxinfo returns “Yes” and vainfo h264 decode is supported. So I suppose everything is ok

Yes.
As I wrote, VCE is about video encoding, not decoding.
I.e. hardware acceleration for creating a MP4/H.264 video stream, not playing back one.

Decoding (play back) is done by UVD, the “Unified Video Decoder”.

nenadandric · July 29, 2017, 3:19pm

That I don’t need