<html> <head> <base href="https://bugs.freedesktop.org/"> </head> <body> <div> <a class="bz_bug_link bz_status_NEW " title="NEW - Black screens on A10-8780P (Carrizo) + R7 M260/M265 (Topaz) Combo" href="https://bugs.freedesktop.org/show_bug.cgi?id=97055#c15">Comment # 15</a> on <a class="bz_bug_link bz_status_NEW " title="NEW - Black screens on A10-8780P (Carrizo) + R7 M260/M265 (Topaz) Combo" href="https://bugs.freedesktop.org/show_bug.cgi?id=97055">bug 97055</a> from <a class="email" href="mailto:darktjm@gmail.com" title="Thomas J. Moore <darktjm@gmail.com>"> Thomas J. Moore</a> <pre>(In reply to SET from <a href="show_bug.cgi?id=97055#c13">comment #13</a>) > My HP laptop with AMD A10-7300 (Kaveri iGPU, Topaz dGPU) has a fully working > X up to kernel 4.9 (not beyond) with these module options applied as such : Thanks. I probably went through that particular set of options back when I was still banging my head against the wall trying to make it work (and tried it again just now in case it miraculously started working). It does nothing for me in 4.9, but may help others. Right now, turning amdgpu off entirely (via modprobe.blacklist=amdgpu or nomodeset if compiled in) is the only thing that reliably works (and thus using efifb instead). And, in case anyone reading this thinks otherwise, it's not just X that doesn't work; the console doesn't work, either (on the rare occasions the console works and stays working, X and Mesa work as well). The only thing that consistently works with the amdgpu driver is the backlight. The display is still black, and maybe occasionally will get some stray pixels temporarily lit up during boot, as if the display is pointing to nonexistent memory.</pre> </div> <hr> You are receiving this mail because: <ul> <li>You are the assignee for the bug.</li> </ul> </body> </html>