[SOLVED] Current (14.2) and DRI 3 and DRI_PRIME ain't working.

Nille_kungen · 04-24-2016, 10:09 AM

After i patched it everything works as it should i got DRI 3 and xrandr --listproviders shows right id.

Code:

$ grep DRI /var/log/Xorg.0.log
[    63.852] (**) RADEON(0): Option "DRI" "3"
[    66.063] (**) RADEON(G0): Option "DRI" "3"
[    71.846] (II) glamor: EGL version 1.4 (DRI2):
[    71.995] (II) RADEON(G0): [DRI2] Setup complete
[    71.995] (II) RADEON(G0): [DRI2]   DRI driver: radeonsi
[    71.995] (II) RADEON(G0): [DRI2]   VDPAU driver: radeonsi
[    72.001] (**) RADEON(G0): DRI3 enabled
[    73.489] (II) RADEON(0): [DRI2] Setup complete
[    73.489] (II) RADEON(0): [DRI2]   DRI driver: r600
[    73.489] (II) RADEON(0): [DRI2]   VDPAU driver: r600
[    73.489] (**) RADEON(0): DRI3 enabled
[    73.569] (II) GLX: Initialized DRI2 GL provider for screen 0

Code:

$ xrandr --listproviders
Providers: number : 2
Provider 0: id: 0x86 cap: 0xf, Source Output, Sink Output, Source Offload, Sink Offload crtcs: 4 outputs: 3 associated providers: 0 name:ARUBA @ pci:0000:00:01.0
Provider 1: id: 0x4f cap: 0xf, Source Output, Sink Output, Source Offload, Sink Offload crtcs: 0 outputs: 0 associated providers: 0 name:HAINAN @ pci:0000:01:00.0

Code:

$ DRI_PRIME=1 glxinfo |grep OpenGL
OpenGL vendor string: X.Org
OpenGL renderer string: Gallium 0.4 on AMD HAINAN (DRM 2.43.0, LLVM 3.8.0)
OpenGL core profile version string: 4.1 (Core Profile) Mesa 11.2.1
OpenGL core profile shading language version string: 4.10
OpenGL core profile context flags: (none)
OpenGL core profile profile mask: core profile
OpenGL core profile extensions:
OpenGL version string: 3.0 Mesa 11.2.1
OpenGL shading language version string: 1.30
OpenGL context flags: (none)
OpenGL extensions:
OpenGL ES profile version string: OpenGL ES 3.0 Mesa 11.2.1
OpenGL ES profile shading language version string: OpenGL ES GLSL ES 3.00
OpenGL ES profile extensions:

voyagerok · 04-25-2016, 10:32 AM

Great work, thank you! I reverted that commit on 4.5.1 kernel, and everything seems to be ok.

ReaperX7 · 04-25-2016, 10:36 AM

I would submit that patch to Patrick via the Slackware Mailing list. I've rarely seen patches to fix things added to the kernel in Slackware, but this is a good find.

Nille_kungen · 04-25-2016, 04:43 PM

I wouldn't call it a good find it's actually git that does the magic it only takes time to do the needed compilation.
If it's of interest i could post how i bisected.
The patch has been reverted in kernel 4.6-RC5 and i think it will be reverted in 4.4.y and 4.5.y as well, it should be safe to revert this commit.
I could send it to Pat but i think he and the rest of the team reads the forum especially now when we are so close to a release but i can send it if requested.
This bug is something that will affect many users and i think the commit should be reverted in the stable 14.2 release.

ReaperX7 · 04-25-2016, 09:22 PM

If it affects the kernel, then I would submit it anyway. Unless the next LTS kernel has it then maybe wait and see then.

volkerdi · 04-25-2016, 11:48 PM

Quote:

Originally Posted by ReaperX7

I would submit that patch to Patrick via the Slackware Mailing list. I've rarely seen patches to fix things added to the kernel in Slackware, but this is a good find.

We've never patched a kernel bug before unless it was a critical security issue. But I hope this will end up in the 4.4.9 kernel.

Nille_kungen · 04-26-2016, 02:24 AM

Quote:

Originally Posted by volkerdi

We've never patched a kernel bug before unless it was a critical security issue. But I hope this will end up in the 4.4.9 kernel.

I e-mailed Alex Deucher and he wrote "I reverted the patch. The revert should end up in stable once the stable maintainers apply it." so it should be reverted in 4.4.9.

gradinaruvasile · 05-01-2016, 04:31 AM

BTW this affects dual Intel+AMD cards as well. runpm doesnt work, both cards are permanently running. Disabling runpm makes possible the toggling on/off the dedicated card and dri_prime works too.

Nille_kungen · 05-05-2016, 11:46 AM

Fixed with the upgrade to kernel 4.4.9 in current.

volkerdi · 05-05-2016, 01:34 PM

Quote:

Originally Posted by Nille_kungen

Fixed with the upgrade to kernel 4.4.9 in current.

Thanks very much for bisecting this and getting it fixed upstream!

Nille_kungen · 05-05-2016, 01:54 PM

Quote:

Originally Posted by volkerdi

Thanks very much for bisecting this and getting it fixed upstream!

There's actually only 2 options, 1) trace and report the bug and make sure it gets fixed, 2) learn to live with it.
I'm one of those people that can't learn to live with it

Richard Cranium · 05-05-2016, 08:51 PM

Quote:

Originally Posted by Nille_kungen

There's actually only 2 options, 1) trace and report the bug and make sure it gets fixed, 2) learn to live with it.
I'm one of those people that can't learn to live with it

There's option 3 that some people use: Complain about it, hoping that someone else finds and fixes the problem.

I'm glad you didn't even think that #3 was an option.