From: bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ@public.gmane.org
To: nouveau-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org
Subject: [Bug 51362] New: DisplayPort output on nVidia Quadro K2000M (ThinkPad W530) doesn't work
Date: Sat, 23 Jun 2012 18:20:23 +0000 [thread overview]
Message-ID: <bug-51362-8800@http.bugs.freedesktop.org/> (raw)
https://bugs.freedesktop.org/show_bug.cgi?id=51362
Bug #: 51362
Summary: DisplayPort output on nVidia Quadro K2000M (ThinkPad
W530) doesn't work
Classification: Unclassified
Product: xorg
Version: git
Platform: x86-64 (AMD64)
OS/Version: Linux (All)
Status: NEW
Severity: normal
Priority: medium
Component: Driver/nouveau
AssignedTo: nouveau-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org
ReportedBy: e.swanson+xorgbugs-5lA2vZBjcqn3oGB3hsPCZA@public.gmane.org
QAContact: xorg-team-go0+a7rfsptAfugRpC6u6w@public.gmane.org
Created attachment 63375
--> https://bugs.freedesktop.org/attachment.cgi?id=63375
Kernel Log
I've disabled Optimus in the BIOS, so only the K2000M is running. Xrandr shows
all my available ports, but no matter what mode I set on the DisplayPort
(connected to an Acer monitor via a known-good MiniDP to HDMI adapter), I get
the error "Input Not Supported" on my monitor.
What other information besides the kernel log can I submit to help with this
bug?
--
Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
next reply other threads:[~2012-06-23 18:20 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-23 18:20 bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ [this message]
[not found] ` <bug-51362-8800-V0hAGp6uBxMKqLRl/0Ahz6D7qz1kEfGD2LY78lusg7I@public.gmane.org/>
2012-06-23 18:28 ` [Bug 51362] DisplayPort output on nVidia Quadro K2000M (ThinkPad W530) doesn't work bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2012-06-23 18:37 ` [Bug 51362] [NVE7] " bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2012-06-23 19:17 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2012-06-24 1:22 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2012-06-24 1:41 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2012-06-24 1:42 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2012-06-24 1:42 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2012-06-29 15:58 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2012-07-27 11:23 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2012-07-28 3:04 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2012-07-28 3:05 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2013-08-30 23:36 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2013-08-31 2:19 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2013-08-31 2:56 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2013-08-31 3:26 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2013-09-02 15:06 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2013-09-02 15:09 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2013-09-02 15:10 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2013-09-02 15:15 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2013-09-02 15:19 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2013-09-02 15:20 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2013-09-02 17:45 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2013-09-03 15:28 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2013-09-13 19:12 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2014-01-23 23:55 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
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-51362-8800@http.bugs.freedesktop.org/ \
--to=bugzilla-daemon-cc+yj3umiyqdupfqwhejaq@public.gmane.org \
--cc=nouveau-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.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.