From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 105005] No image after downtime (RX460)
Date: Fri, 09 Feb 2018 19:11:05 +0000 [thread overview]
Message-ID: <bug-105005-502-Wmv67RkSSD@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-105005-502@http.bugs.freedesktop.org/>
[-- Attachment #1.1: Type: text/plain, Size: 542 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=105005
--- Comment #9 from Dmitry <terapy-session@bk.ru> ---
I will not be able to do, not enough skill.
Tried to drag through TV files, TV breaks after the loss of the signal on the
main machine. Also tried to register in the console dmesg creation with the
switched-off screen, but nothing left. Perhaps there is a bug not with the
video, and no signal from keyboard and mouse. Why not get out of standby.
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 1284 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:[~2018-02-09 19:11 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-07 19:29 [Bug 105005] No image after downtime (RX460) bugzilla-daemon
2018-02-07 20:24 ` bugzilla-daemon
2018-02-07 20:24 ` bugzilla-daemon
2018-02-07 21:48 ` bugzilla-daemon
2018-02-07 21:50 ` bugzilla-daemon
2018-02-08 6:11 ` bugzilla-daemon
2018-02-08 9:26 ` bugzilla-daemon
2018-02-08 9:29 ` bugzilla-daemon
2018-02-08 12:05 ` bugzilla-daemon
2018-02-08 14:36 ` bugzilla-daemon
2018-02-09 19:11 ` bugzilla-daemon [this message]
2018-02-19 12:03 ` bugzilla-daemon
2018-02-21 6:13 ` bugzilla-daemon
2018-02-21 8:52 ` bugzilla-daemon
2018-02-23 8:24 ` bugzilla-daemon
2018-02-23 16:52 ` bugzilla-daemon
2018-03-18 19:47 ` 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-105005-502-Wmv67RkSSD@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