Kernel 4.4.7 broke support for my second graphics card and with that DRI 3. In 4.4.7 it gets wrong ID with listproviders, it worked in 4.4.6. Bad: xrandr --listproviders Providers: number : 2 Provider 0: id: 0x76 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: 0x3f cap: 0x0 crtcs: 0 outputs: 0 associated providers: 0 name:HAINAN @ pci:0000:01:00.0 Good values are 0x4f and 0x86. Bisect git bisect bad | tee -a /root/bisect.log 791b5b0d2d01542a87af4b5f8fb2504ce2d5b352 is the first bad commit commit 791b5b0d2d01542a87af4b5f8fb2504ce2d5b352 Author: Alex Deucher <alexander.deucher@amd.com> Date: Wed Mar 2 11:47:29 2016 -0500 drm/radeon: disable runtime pm on PX laptops without dGPU power control commit e64c952efb8e0c15ae82cec8e455ab4910690ef1 upstream. Some PX laptops don't provide an ACPI method to control dGPU power. On those systems, the driver is responsible for handling the dGPU power state. Disable runtime PM on them until support for this is implemented. Reviewed-by: Michel Dänzer <michel.daenzer@amd.com> Signed-off-by: Alex Deucher <alexander.deucher@amd.com> Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org> :040000 040000 ca854413a484531a21c3344a9be531a9656be4ac 7d02c9365298e3d52bc0f1ba1a4481667c27200f M drivers
I confirm this bug on kernels since 4.4.7.
Nice to see that the commit was reverted in 4.6RC5 and i can confirm that 4.6RC now works. I hope it also gets reverted in 4.4.y and 4.5.y as well.
Looking at the info i supplied in http://www.linuxquestions.org/questions/slackware-14/current-14-2-and-dri-3-and-dri_prime-ain't-working-4175578108/ It looks like it's related to 94874 only kernel versions differ. https://bugs.freedesktop.org/show_bug.cgi?id=94874 If the commit is reverted from the 4.4.y and 4.5.y this could be marked as solved.
The commit is reverted in 4.4.9 and 4.5.3
Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.