dri-devel Archive on lore.kernel.org
 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: Tue, 03 Jan 2017 23:38:38 +0000	[thread overview]
Message-ID: <bug-97055-502-yHg4pN1TMB@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-97055-502@http.bugs.freedesktop.org/>


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

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

--- Comment #15 from Thomas J. Moore <darktjm@gmail.com> ---
(In reply to SET from comment #13)
> 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.

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

[-- Attachment #1.2: Type: text/html, Size: 2179 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:[~2017-01-03 23:38 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
2017-01-02 21:54 ` bugzilla-daemon
2017-01-02 22:06 ` bugzilla-daemon
2017-01-03 23:38 ` bugzilla-daemon [this message]
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-yHg4pN1TMB@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