All of lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 42490] NUTMEG DP to VGA bridge not working
Date: Fri, 07 Sep 2012 19:19:10 +0000	[thread overview]
Message-ID: <bug-42490-502-LnPHqcOfDc@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-42490-502@http.bugs.freedesktop.org/>

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

--- Comment #32 from diego.abelenda@gmail.com 2012-09-07 19:19:10 UTC ---
Created attachment 66808
  --> https://bugs.freedesktop.org/attachment.cgi?id=66808
dmesg booting with 2 monitors plugged drm.debug=4

This drm-fixes-3.6 branch just gives me two black screens when I have them both
plugged during the boot. And when X starts I get a 100% processor usage from
the X process and nothing displayed. The Xorg.0.log shows nothing out of the
ordinary. But I think there is something really wrong because my X server never
starts accepting connection from my login manager.

When I boot with only the DVI screen plugged, no problem it boots fine.
After having booted with only the DVI plugging the VGA one works just like
before.

When X puts my screens into DPMS off and I try to wake them up, the VGA goes
back on correctly with this branch whereas it didn't with vanilla kernel.

So there are some good points and some bad points.

Attached is dmesg | grep -e drm -e radeon when both screens are connected,
after X is "started".

-- 
Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.

  parent reply	other threads:[~2012-09-07 19:19 UTC|newest]

Thread overview: 42+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <bug-42490-502@http.bugs.freedesktop.org/>
2011-11-02 21:51 ` [Bug 42490] NUTMEG DP to VGA bridge not working bugzilla-daemon
2011-11-03  2:15 ` bugzilla-daemon
2011-11-03 14:17 ` bugzilla-daemon
2011-11-04  2:15 ` bugzilla-daemon
2011-11-06  2:58 ` bugzilla-daemon
2012-03-12 13:43 ` bugzilla-daemon
2012-04-15  3:00 ` bugzilla-daemon
2012-04-16  4:38 ` bugzilla-daemon
2012-04-27 21:18 ` bugzilla-daemon
2012-04-28  7:39 ` bugzilla-daemon
2012-04-28 10:40 ` bugzilla-daemon
2012-04-28 10:41 ` bugzilla-daemon
2012-04-28 23:01 ` bugzilla-daemon
2012-04-29  8:38 ` bugzilla-daemon
2012-04-29  8:41 ` bugzilla-daemon
2012-04-29  9:14 ` bugzilla-daemon
2012-04-29 12:27 ` bugzilla-daemon
2012-04-29 12:30 ` bugzilla-daemon
2012-04-29 14:45 ` bugzilla-daemon
2012-04-29 15:14 ` bugzilla-daemon
2012-04-29 15:34 ` bugzilla-daemon
2012-04-30  9:54 ` bugzilla-daemon
2012-05-07 19:57 ` bugzilla-daemon
2012-05-08  6:54 ` bugzilla-daemon
2012-09-05 18:31 ` bugzilla-daemon
2012-09-05 18:34 ` bugzilla-daemon
2012-09-07 19:19 ` bugzilla-daemon [this message]
2012-09-07 19:35 ` bugzilla-daemon
2012-09-07 21:07 ` bugzilla-daemon
2012-09-07 21:08 ` bugzilla-daemon
2012-09-07 21:11 ` bugzilla-daemon
2012-09-07 21:28 ` bugzilla-daemon
2012-09-07 21:52 ` bugzilla-daemon
2012-09-08  8:59 ` bugzilla-daemon
2012-09-08 15:46 ` bugzilla-daemon
2012-09-08 18:15 ` bugzilla-daemon
2012-09-09  7:33 ` bugzilla-daemon
2012-09-13 12:21 ` bugzilla-daemon
2012-09-14  7:59 ` bugzilla-daemon
2012-09-30 15:46 ` bugzilla-daemon
2013-09-07 20:51 ` bugzilla-daemon
2019-11-19  8:23 ` 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-42490-502-LnPHqcOfDc@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.