[Bug 117591] amdgpu: Black screens on A10-8700P (Carrizo) + R7 M260/M265 (Topaz) Combo

[bugzilla-daemon at bugzilla.kernel.org]

https://bugzilla.kernel.org/show_bug.cgi?id=117591

Thomas J. Moore <darktjm at gmail.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |darktjm at gmail.com

--- Comment #10 from Thomas J. Moore <darktjm at gmail.com> ---
I have almost identical hardware, but a much different experience (kernel
4.6.2, 4.6.3, 4.6.4, 4.7-rc4 on Gentoo).  For me, I rarely, if ever, get a
non-black screen.  Sometimes, when the machine has been running a while before
rebooting, I get good video up until init gets loaded. During the many
hours/days I beat my head against this problem, on very rare occasions
everything would just start working.  This problem is made worse by the fact
that I have no other machines to connect with (I could still execute commands
blindly, when lucky, or prepare scripts to do what I wanted with minimal chance
for typos) and the fact that the keyboard appears to have issues.  When I first
got the machine, I used efifb, and it worked (and still works) perfectly all
the time (except, of course, no 3d, and no brightness control, and no
resolution switching in X).  Among other things, I played with all the various
power management toggles (including runpm) and nothing helped.  I still can't
get video on the console, although I have finally stumbled on a workaround for
X that sometimes works OK (and may benefit from runpm=0, but I'd have to try
again from a cold boot after long powerdown, since that's when the video acts
up the most): xrandr --output eDP --crtc 1.  Most of the time this causes video
to appear in X.  Sometimes that video is flickery, and sometimes toggling the
crtc between 0 and 1 causes the flickering to disappear.  Almost all the time
when X is killed with crtc 1 enabled, the machine hangs, as well, but that's
not really a big deal.  Given the severe lack of documentation for drm, I
haven't tried to make a console program with similar effect, and my attempts at
tracing the kernel module to force "crtc 1" to be chosen by default have all
ended in frustration.  Then again, since the machine sometimes (even if very,
very rarely) "just works", I'm not sure why I would have to swtich the crtc in
the first place.

-- 
You are receiving this mail because:
You are watching the assignee of the bug.