dri-devel.lists.freedesktop.org archive mirror
 help / color / mirror / Atom feed
From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 97221] monitor miss detection, philips 242G5
Date: Mon, 19 Sep 2016 20:31:12 +0000	[thread overview]
Message-ID: <bug-97221-502-sikJOTqKPD@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-97221-502@http.bugs.freedesktop.org/>


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

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

--- Comment #6 from Thomas <w3bm4573r@gmx.de> ---
Same Probleme here with other monitors.
But the system freezes totally because i've two of the same.

The Effect is only when the monitor is going in engery saving mode. (Not the 
system, this is disabled).

After this the system did not wake up every time and i can't reactivate it.

Sometime i got an error under gnome like this:
could not set the configuration for CRTC79

Then the system is activated, but the second monitor is still offline afer a
couple of seconds an pressing the ok button everything works fine.

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

[-- Attachment #1.2: Type: text/html, Size: 1464 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:[~2016-09-19 20:31 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-08-05 19:56 [Bug 97221] monitor miss detection, philips 242G5 bugzilla-daemon
2016-08-05 19:57 ` bugzilla-daemon
2016-08-05 20:53 ` bugzilla-daemon
2016-09-19 20:24 ` bugzilla-daemon
2016-09-19 20:29 ` bugzilla-daemon
2016-09-19 20:29 ` bugzilla-daemon
2016-09-19 20:30 ` bugzilla-daemon
2016-09-19 20:31 ` bugzilla-daemon [this message]
2019-11-19  7:58 ` 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-97221-502-sikJOTqKPD@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).