From: bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ@public.gmane.org
To: nouveau-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org
Subject: [Bug 27905] DVI monitor is blank - DVI detected as Display Port ?
Date: Tue, 4 May 2010 15:37:45 -0700 (PDT) [thread overview]
Message-ID: <20100504223745.D33FD13004F@annarchy.freedesktop.org> (raw)
In-Reply-To: <bug-27905-8800-V0hAGp6uBxMKqLRl/0Ahz6D7qz1kEfGD2LY78lusg7I@public.gmane.org/>
https://bugs.freedesktop.org/show_bug.cgi?id=27905
--- Comment #13 from Ben Skeggs <skeggsb-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org> 2010-05-04 15:37:45 PDT ---
(In reply to comment #12)
> LVDS-1 is closed; in nv, it means it is disconnected. Please see xrandr outputs
> below.
I don't recall nv (unless by nv you mean the proprietary driver) doing anything
of the sort. In any case, nouveau does something similar in this case, hence
LVDS being reported as "unknown connection". We do this instead of
"disconnected" so that X will setup LVDS still if the lid is closed and nothing
else is plugged in.
>
> Also, I tried the following command lines :
> xrandr --output LVDS-1 --off
> xrandr --output DP-1 --auto
>
> -> nothing happens. Screen DVI-1 is still blank.
Right, so now you're probably hitting another bug I've seen reported in a few
places where docking station DVI fails on systems where it could be either DP
or DVI on the docking station.
> Then I open the laptop and issued :
>
> xrandr --output LVDS-1 --auto
>
> I got :
>
> xrandr: cannot find crtc for output LVDS-1
>
> It means that it tries to display on both DP-1 and VGA-1, right ?
Correct.
>
> BTW, in gnome's display preferences, I correctly get both monitors displayed,
> but still, the monitor on DVI stays blank.
>
> Again : I have no monitor on DisplayPort (and I have no DisplayPort on the
> docking station). I have one monitor on VGA and one monitor on DVI (and LVDS as
> well, which is off most of the time).
As I mentioned above, the VBIOS reports the connectors as DisplayPort as the
docking station could potentially have DP instead of DVI-D connectors. There's
no way for us to tell which the manufacturer wired up, so we assume it's DP.
This has no effect on functionality.
Ok, my question for you is: Are you able to make your VBIOS setup the DVI
display during POST instead of the LVDS panel? There may be options in your
BIOS setup to allow this. If so, let me know and we may be able to get traces
that'll help me track this problem down for you.
Ben.
--
Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
next prev parent reply other threads:[~2010-05-04 22:37 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-29 22:37 [Bug 27905] New: DVI monitor is blank - DVI detected as Display Port ? bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
[not found] ` <bug-27905-8800-V0hAGp6uBxMKqLRl/0Ahz6D7qz1kEfGD2LY78lusg7I@public.gmane.org/>
2010-04-29 22:38 ` [Bug 27905] " bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2010-04-29 23:02 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2010-04-29 23:48 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2010-04-29 23:51 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2010-04-29 23:54 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2010-04-30 6:34 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2010-04-30 17:38 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2010-04-30 17:41 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2010-05-01 2:53 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2010-05-03 8:35 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2010-05-03 22:47 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2010-05-04 11:29 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2010-05-04 22:37 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ [this message]
2010-05-04 23:11 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2010-05-04 23:26 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2010-05-05 7:14 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2010-05-05 23:29 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2010-05-06 9:47 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2010-11-15 17:43 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2011-01-06 19:15 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2011-12-06 20:08 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2013-08-19 15:01 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2013-08-19 15:53 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2013-09-21 17:24 ` 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=20100504223745.D33FD13004F@annarchy.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.