From mboxrd@z Thu Jan 1 00:00:00 1970 From: bugzilla-daemon@freedesktop.org Subject: [Bug 97055] Black screens on A10-8780P (Carrizo) + R7 M260/M265 (Topaz) Combo Date: Sat, 13 Aug 2016 00:44:28 +0000 Message-ID: References: Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="===============1854393164==" Return-path: Received: from culpepper.freedesktop.org (culpepper.freedesktop.org [131.252.210.165]) by gabe.freedesktop.org (Postfix) with ESMTP id 14F656EC6C for ; Sat, 13 Aug 2016 00:44:28 +0000 (UTC) In-Reply-To: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: dri-devel-bounces@lists.freedesktop.org Sender: "dri-devel" To: dri-devel@lists.freedesktop.org List-Id: dri-devel@lists.freedesktop.org --===============1854393164== Content-Type: multipart/alternative; boundary="14710490670.Dd58AcaA8.1118"; charset="UTF-8" --14710490670.Dd58AcaA8.1118 Date: Sat, 13 Aug 2016 00:44:27 +0000 MIME-Version: 1.0 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: http://bugs.freedesktop.org/ Auto-Submitted: auto-generated https://bugs.freedesktop.org/show_bug.cgi?id=3D97055 --- Comment #7 from Thomas J. Moore --- (In reply to Tom from comment #6) > https://uloz.to/!qq2wDEC87/linux45-4-5rc6-1-x86-64-pkg-tar-xz Not insane enough yet to try a binary kernel, ever, even from a more reputa= ble source than some site in a language I don't even understand. > If I wait 2 minutes before booting the > system I have no problems as long as I don't suspend it. I don't understand what this means. Do you let it sit in the bootloader fo= r 2 minutes, or what? > It may be more stable for you too. The official kernels are stable for me, once the display comes up and stays= up for more than a minute. Most of the time, this involves doing a quick boot with power management enabled, starting X, then rebooting normally, with po= wer management disabled. Sometimes this does not work, which doesn't surprise = me, since this is basically just blindly throwing shit at the wall until someth= ing sticks. I'm not going to even try suspending until I can at least reliably boot.=20 Suspending always brings its own set of problems, and has never worked 100% reliably for me. In related news, 4.8-rc1 still doesn't work. Actually, it's worse, in that= X won't start at all (something about unable to schedule ib on the TOPAZ). I= 'm pretty sure that's a different issue, though, so I won't elaborate (or repo= rt, until this bug is fixed first). --=20 You are receiving this mail because: You are the assignee for the bug.= --14710490670.Dd58AcaA8.1118 Date: Sat, 13 Aug 2016 00:44:27 +0000 MIME-Version: 1.0 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: http://bugs.freedesktop.org/ Auto-Submitted: auto-generated

Comment= # 7 on bug 97055<= /a> from Thomas J. Moore
(In reply to Tom from c=
omment #6)
> https://uloz.to/!qq2wDEC87/linux45-4-5rc6-1-x86-6=
4-pkg-tar-xz

Not insane enough yet to try a binary kernel, ever, even from a more reputa=
ble
source than some site in a language I don't even understand.

> If I wait 2 minutes before booting the
> system I have no problems as long as I don't suspend it.

I don't understand what this means.  Do you let it sit in the bootloader fo=
r 2
minutes, or what?

> It may be more stable for you too.

The official kernels are stable for me, once the display comes up and stays=
 up
for more than a minute.  Most of the time, this involves doing a quick boot
with power management enabled, starting X, then rebooting normally, with po=
wer
management disabled.  Sometimes this does not work, which doesn't surprise =
me,
since this is basically just blindly throwing shit at the wall until someth=
ing
sticks.

I'm not going to even try suspending until I can at least reliably boot.=20
Suspending always brings its own set of problems, and has never worked 100%
reliably for me.

In related news, 4.8-rc1 still doesn't work.  Actually, it's worse, in that=
 X
won't start at all (something about unable to schedule ib on the TOPAZ).  I=
'm
pretty sure that's a different issue, though, so I won't elaborate (or repo=
rt,
until this bug is fixed first).


You are receiving this mail because:
  • You are the assignee for the bug.
= --14710490670.Dd58AcaA8.1118-- --===============1854393164== Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: base64 Content-Disposition: inline X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX18KZHJpLWRldmVs IG1haWxpbmcgbGlzdApkcmktZGV2ZWxAbGlzdHMuZnJlZWRlc2t0b3Aub3JnCmh0dHBzOi8vbGlz dHMuZnJlZWRlc2t0b3Aub3JnL21haWxtYW4vbGlzdGluZm8vZHJpLWRldmVsCg== --===============1854393164==--