dri-devel.lists.freedesktop.org archive mirror
 help / color / mirror / Atom feed
From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 97055] Black screens on A10-8780P (Carrizo) + R7 M260/M265 (Topaz) Combo
Date: Sun, 04 Dec 2016 21:54:30 +0000	[thread overview]
Message-ID: <bug-97055-502-cU90SEc2E5@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-97055-502@http.bugs.freedesktop.org/>


[-- Attachment #1.1: Type: text/plain, Size: 1847 bytes --]

https://bugs.freedesktop.org/show_bug.cgi?id=97055

--- Comment #12 from Thomas J. Moore <darktjm@gmail.com> ---
(In reply to Josh from comment #11)
> I too am affected by this issue.

It might help if you add yourself to the CC list.  Not that anyone talks on
this bug but me.

> Is this issue ever going to be fixed?

I have my doubts.  I have made efifb (nomodeset) my default boot now, so I can
at least use this machine.  Can't adjust brightness, play games or watch
full-screen videos, but I guess I'll just have to live with that.  The only way
I expect this will ever get fixed for me is if I get enough money together to
buy a new machine.

The fact is, the only changes I've noticed have been regressions.  The
non-start of X in 4.8 was fixed, but later 4.8-series kernels (and 4.9 kernels
as well) seem to crash badly (panic?  hard to tell, since I have no way of
knowing what happens when the screen is black -- I can't even get LEDs on the
keyboard to flash, since this piece of crap machine also suffers from a
non-linux-compatible keyboard: 
http://unix.stackexchange.com/questions/233396/system-creates-extra-shift-alt-control-keypresses/302890,
and my attempts to get it to log to EFI have been unsuccessful).  The crash
then forces a filesystem check on reboot, which takes forever and I don't have
the patience to deal with that any more.  I was able to get amdgpu running
"properly" (w/o power management) in 4.8.11 eventually using a 4.4.32 kernel to
do the initial boot with power management enabled, but it's still unreliable
enough that it isn't worth trying very often.

I said I wouldn't report any more on the lack of progress, but yeah, 4.8.11 and
4.9-rc7 are still complete garbage, even worse than before.

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

[-- Attachment #1.2: Type: text/html, Size: 2892 bytes --]

[-- Attachment #2: Type: text/plain, Size: 160 bytes --]

_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel

  parent reply	other threads:[~2016-12-04 21:54 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-07-23  2:32 [Bug 97055] Black screens on A10-8780P (Carrizo) + R7 M260/M265 (Topaz) Combo bugzilla-daemon
2016-07-23  2:39 ` bugzilla-daemon
2016-07-31 20:10 ` bugzilla-daemon
2016-08-05 17:34 ` bugzilla-daemon
2016-08-05 17:41 ` bugzilla-daemon
2016-08-09 17:20 ` bugzilla-daemon
2016-08-11 16:38 ` bugzilla-daemon
2016-08-13  0:44 ` bugzilla-daemon
2016-08-14 20:56 ` bugzilla-daemon
2016-08-30 16:11 ` bugzilla-daemon
2016-09-09 15:58 ` bugzilla-daemon
2016-12-04  2:31 ` bugzilla-daemon
2016-12-04 21:54 ` bugzilla-daemon [this message]
2017-01-02 21:54 ` bugzilla-daemon
2017-01-02 22:06 ` bugzilla-daemon
2017-01-03 23:38 ` bugzilla-daemon
2017-06-06 15:38 ` bugzilla-daemon
2017-06-06 15:40 ` bugzilla-daemon
2017-10-26 22:52 ` bugzilla-daemon
2017-11-01 14:54 ` bugzilla-daemon
2017-11-01 15:23 ` bugzilla-daemon
2017-12-18  0:29 ` bugzilla-daemon
2019-01-21  5:07 ` bugzilla-daemon
2019-02-15  5:09 ` bugzilla-daemon
2019-05-15 13:27 ` bugzilla-daemon
2019-07-20  0:35 ` bugzilla-daemon
2019-11-19  8:09 ` bugzilla-daemon
2019-11-22  9:38 ` bugzilla-daemon
2019-11-25  7:22 ` bugzilla-daemon

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=bug-97055-502-cU90SEc2E5@http.bugs.freedesktop.org/ \
    --to=bugzilla-daemon@freedesktop.org \
    --cc=dri-devel@lists.freedesktop.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).