<html> <head> <base href="https://bugs.freedesktop.org/"> </head> <body> <div> <a class="bz_bug_link bz_status_NEW " title="NEW - PRIME output screen satys black on 1002:15d8 with 128MB VRAM" href="https://bugs.freedesktop.org/show_bug.cgi?id=111228#c4">Comment # 4</a> on <a class="bz_bug_link bz_status_NEW " title="NEW - PRIME output screen satys black on 1002:15d8 with 128MB VRAM" href="https://bugs.freedesktop.org/show_bug.cgi?id=111228">bug 111228</a> from <a class="email" href="mailto:hhfeuer@gmx.de" title="Maik Freudenberg <hhfeuer@gmx.de>"> Maik Freudenberg</a> <pre>Both amdgpu and modesetting driver were tested, same effect. Most notewothy in the non-prime modesetting driver case is this: [ 5.477] (EE) modeset(0): [DRI2] No driver mapping found for PCI device 0x1002 / 0x15d8 [ 5.477] (EE) modeset(0): Failed to initialize the DRI2 extension. [ 5.477] (--) RandR disabled [ 5.480] (II) SELinux: Disabled on system [ 5.480] (II) AIGLX: Screen 0 is not DRI2 capable [ 5.480] (EE) AIGLX: reverting to software rendering On those other systems mentioned with 2GB VRAM, the modesetting driver runs fine in any case. This seems to be a different bug with the modesetting driver, though. Non-prime+amdgpu driver runs fine. Since the display starts to work after a suspend/resume cycle, seems to be a kernel bug?</pre> </div> <hr> You are receiving this mail because: <ul> <li>You are the assignee for the bug.</li> </ul> </body> </html>