All of lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 72051] New: [JUNIPER] with kernel 3.12 some HDMI screens are not recognized
Date: Tue, 26 Nov 2013 20:30:47 +0000	[thread overview]
Message-ID: <bug-72051-502@http.bugs.freedesktop.org/> (raw)


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

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

          Priority: medium
            Bug ID: 72051
          Assignee: dri-devel@lists.freedesktop.org
           Summary: [JUNIPER] with kernel 3.12 some HDMI screens are not
                    recognized
          Severity: normal
    Classification: Unclassified
                OS: Linux (All)
          Reporter: eugene.shalygin+bugzilla.FDO@gmail.com
          Hardware: x86-64 (AMD64)
            Status: NEW
           Version: unspecified
         Component: DRM/Radeon
           Product: DRI

Created attachment 89860
  --> https://bugs.freedesktop.org/attachment.cgi?id=89860&action=edit
xrandr -q --verbose with screen 1 connected

I have two external screens, say screen 1 and 2. Screen 1 have HDMI input and
screens 2 is connected via HDMI-to-DVI adapter.

With kernel 3.12 screen 1 is not recognized on connect anymore. Booting kernel
3.11.9 makes it work again.

When I connect screen 1 nothing appears not in Xorg.0.log nor in dmesg

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

[-- Attachment #1.2: Type: text/html, Size: 2558 bytes --]

[-- Attachment #2: Type: text/plain, Size: 159 bytes --]

_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/dri-devel

             reply	other threads:[~2013-11-26 20:30 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-11-26 20:30 bugzilla-daemon [this message]
2013-11-26 20:31 ` [Bug 72051] [JUNIPER] with kernel 3.12 some HDMI screens are not recognized bugzilla-daemon
2013-11-26 20:32 ` bugzilla-daemon
2013-11-26 20:33 ` bugzilla-daemon
2013-11-26 20:33 ` bugzilla-daemon
2013-11-26 22:15 ` bugzilla-daemon
2013-11-26 22:17 ` bugzilla-daemon
2013-11-27 15:50 ` bugzilla-daemon
2013-12-16 18:34 ` bugzilla-daemon
2013-12-16 23:40 ` bugzilla-daemon
2013-12-17 12:34 ` bugzilla-daemon
2013-12-17 13:43 ` bugzilla-daemon
2013-12-17 16:08 ` bugzilla-daemon
2013-12-17 16:15 ` bugzilla-daemon
2013-12-18 11:44 ` bugzilla-daemon
2019-11-19  8:40 ` 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-72051-502@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.