From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 95306] Random Blank(black) screens on "Carrizo"
Date: Thu, 05 Jan 2017 19:05:03 +0000 [thread overview]
Message-ID: <bug-95306-502-O6ApM3FUBc@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-95306-502@http.bugs.freedesktop.org/>
[-- Attachment #1.1: Type: text/plain, Size: 1555 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=95306
--- Comment #37 from cyrwyn <cyrwyn@gmail.com> ---
I also have an HP g121wm laptop with an A10 8700p apu/gpu chipset (carrizo R6).
Ever since the removal of the catalyst driver and replacement with the Xorg
amdgpu driver at least 6 months ago, shortly after the kernel loads and detects
hardware the screen blanks, the keyboard doesn't respond, although numlock and
capslock are working, but any of the alt+ctl or reisub commands won't work,
however the system does continue to load in the background. I suppose this
occurs when kernel mode setting kicks in. I can only get a working screen using
nomodeset in the command line, which limits me to an 800x600 fb screen. AMD
support tells me there is no support for R6 graphics in amdgpu pro, but an Xorg
support person tells me that their Xorg version of amdgpu (not pro) does
support this carrizo chipset. I've tried the latest Xorg amdgpu to no avail.
Apparently, the basic Xorg.ati driver won't work with this chipset. I even get
conflicting accounts of how to set up this card with the vesa driver! I haven't
been able to achieve it and I'm a 24 year Linux user! I've tried this with all
kernels since 4.3 and am now running 4.8.11 and the problem remains. BTW I run
PClinuxos with KDE.
Is this even a bug or just an unusual configuration issue?
I don't have the amdgpu driver installed at the moment, but here are my dmesg
and Xorg.log files.
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 2330 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
next prev parent reply other threads:[~2017-01-05 19:05 UTC|newest]
Thread overview: 85+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-06 20:27 [Bug 95306] Random Blank(black) screens on "Carrizo" bugzilla-daemon
2016-05-06 20:32 ` bugzilla-daemon
2016-08-05 17:31 ` bugzilla-daemon
2016-08-05 17:34 ` bugzilla-daemon
2016-08-09 19:27 ` bugzilla-daemon
2016-08-22 15:54 ` bugzilla-daemon
2016-08-22 15:56 ` bugzilla-daemon
2016-08-22 15:56 ` bugzilla-daemon
2016-08-22 15:58 ` bugzilla-daemon
2016-08-23 1:13 ` bugzilla-daemon
2016-08-23 14:11 ` bugzilla-daemon
2016-08-24 0:45 ` bugzilla-daemon
2016-08-24 17:19 ` bugzilla-daemon
2016-08-24 17:30 ` bugzilla-daemon
2016-08-24 17:39 ` bugzilla-daemon
2016-08-24 17:40 ` bugzilla-daemon
2016-08-25 6:34 ` bugzilla-daemon
2016-09-08 10:50 ` bugzilla-daemon
2016-09-09 3:29 ` bugzilla-daemon
2016-09-15 16:38 ` bugzilla-daemon
2016-10-07 1:19 ` bugzilla-daemon
2016-10-07 1:29 ` bugzilla-daemon
2016-10-07 10:51 ` bugzilla-daemon
2016-10-07 13:53 ` bugzilla-daemon
2016-10-07 13:54 ` bugzilla-daemon
2016-10-07 13:59 ` bugzilla-daemon
2016-10-07 14:00 ` bugzilla-daemon
2016-10-07 14:04 ` bugzilla-daemon
2016-10-07 14:05 ` bugzilla-daemon
2016-10-07 20:08 ` bugzilla-daemon
2016-10-08 0:31 ` bugzilla-daemon
2016-11-07 21:04 ` bugzilla-daemon
2016-11-08 3:36 ` bugzilla-daemon
2016-11-08 8:10 ` bugzilla-daemon
2016-11-08 13:35 ` bugzilla-daemon
2016-11-08 13:36 ` bugzilla-daemon
2016-11-23 2:43 ` bugzilla-daemon
2016-11-29 12:32 ` bugzilla-daemon
2016-11-29 18:40 ` bugzilla-daemon
2017-01-05 19:05 ` bugzilla-daemon [this message]
2017-01-05 19:09 ` bugzilla-daemon
2017-01-05 19:12 ` bugzilla-daemon
2017-01-05 19:14 ` bugzilla-daemon
2017-01-05 19:30 ` bugzilla-daemon
2017-01-06 17:30 ` bugzilla-daemon
2017-01-09 7:02 ` bugzilla-daemon
2017-01-09 15:16 ` bugzilla-daemon
2017-01-09 15:18 ` bugzilla-daemon
2017-01-09 15:25 ` bugzilla-daemon
2017-01-09 20:51 ` bugzilla-daemon
2017-01-09 20:54 ` bugzilla-daemon
2017-01-10 7:08 ` bugzilla-daemon
2017-01-13 20:10 ` bugzilla-daemon
2017-01-16 5:11 ` bugzilla-daemon
2017-01-24 13:48 ` bugzilla-daemon
2017-01-25 1:13 ` bugzilla-daemon
2017-01-30 20:27 ` bugzilla-daemon
2017-02-01 16:32 ` bugzilla-daemon
2017-02-10 1:18 ` bugzilla-daemon
2017-02-10 19:01 ` bugzilla-daemon
2017-02-10 19:05 ` bugzilla-daemon
2017-02-12 5:09 ` bugzilla-daemon
2017-02-22 1:02 ` bugzilla-daemon
2017-02-22 1:19 ` bugzilla-daemon
2017-03-03 22:10 ` bugzilla-daemon
2017-03-04 7:51 ` bugzilla-daemon
2017-03-04 7:56 ` bugzilla-daemon
2017-03-06 15:31 ` bugzilla-daemon
2017-03-06 19:57 ` bugzilla-daemon
2017-03-06 20:10 ` bugzilla-daemon
2017-11-21 21:57 ` bugzilla-daemon
2017-11-21 22:21 ` bugzilla-daemon
2017-12-06 16:35 ` bugzilla-daemon
2017-12-06 17:14 ` bugzilla-daemon
2017-12-06 17:17 ` bugzilla-daemon
2017-12-06 17:26 ` bugzilla-daemon
2017-12-07 5:54 ` bugzilla-daemon
2017-12-08 7:38 ` bugzilla-daemon
2017-12-11 3:19 ` bugzilla-daemon
2017-12-11 16:22 ` bugzilla-daemon
2017-12-13 1:01 ` bugzilla-daemon
2017-12-14 20:43 ` bugzilla-daemon
2017-12-19 5:10 ` bugzilla-daemon
2017-12-25 15:34 ` bugzilla-daemon
2017-12-27 9:11 ` 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-95306-502-O6ApM3FUBc@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).