All of lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 105433] Unreliable Modesetting on Tonga with two DVI Screens
Date: Mon, 22 Oct 2018 17:26:21 +0000	[thread overview]
Message-ID: <bug-105433-502-jFxZh5JvlX@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-105433-502@http.bugs.freedesktop.org/>


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

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

--- Comment #7 from Thomas R. <freedesktop-bugs@digital-trauma.de> ---
I've got news! With 4.19, the first modeset will still disable the second
monitor,  including when going into X (without mode change), but after changing
the resolution to something else and back again, it now comes up reliably. This
is much better than before. Also, I get this in dmesg

[drm] dce110_link_encoder_construct: Failed to get encoder_cap_info from VBIOS
with error code 4!

on startup.

I don't know if this helps, and I'd be still willing to help debug given
instructions.

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

[-- Attachment #1.2: Type: text/html, Size: 1506 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:[~2018-10-22 17:26 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-03-10 23:31 [Bug 105433] Unreliable Modesetting on Tonga with two DVI Screens bugzilla-daemon
2018-03-10 23:33 ` bugzilla-daemon
2018-05-17  7:39 ` bugzilla-daemon
2018-05-17  7:42 ` bugzilla-daemon
2018-05-17  7:47 ` bugzilla-daemon
2018-05-21 17:59 ` bugzilla-daemon
2018-09-05 17:20 ` bugzilla-daemon
2018-10-22 17:26 ` bugzilla-daemon [this message]
2018-10-22 22:36 ` bugzilla-daemon
2019-04-15 17:06 ` bugzilla-daemon
2019-04-15 17:59 ` bugzilla-daemon
2019-04-15 18:00 ` bugzilla-daemon
2019-11-20  7: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-105433-502-jFxZh5JvlX@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.