From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 98037] HD6450 KMS failure
Date: Tue, 04 Oct 2016 14:38:11 +0000 [thread overview]
Message-ID: <bug-98037-502-KEgphvKCIJ@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-98037-502@http.bugs.freedesktop.org/>
[-- Attachment #1.1: Type: text/plain, Size: 662 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=98037
--- Comment #5 from Alex Deucher <alexdeucher@gmail.com> ---
(In reply to Will Lewis from comment #4)
> The error occurs before I even get to X. This machine boots to a console
> login screen, at which point I login and potentially start X. However,
> during the initial boot, I get kernel output until the radeon module gets
> loaded, at which point the screen goes blank and tells me it has no signal.
>
> Do you want me to try to start X in the dark, so to speak, and grab the log
> after rebooting?
Yes please.
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 1471 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:[~2016-10-04 14:38 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <bug-98037-502@http.bugs.freedesktop.org/>
2016-10-04 8:33 ` [Bug 98037] HD6450 KMS failure bugzilla-daemon
2016-10-04 14:03 ` bugzilla-daemon
2016-10-04 14:31 ` bugzilla-daemon
2016-10-04 14:38 ` bugzilla-daemon [this message]
2016-10-05 13:19 ` bugzilla-daemon
2016-10-05 14:03 ` bugzilla-daemon
2016-10-06 13:38 ` bugzilla-daemon
2019-11-19 9:19 ` 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-98037-502-KEgphvKCIJ@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).