From: bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ@public.gmane.org
To: nouveau-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org
Subject: [Bug 18336] New: nv10 : doesn't detect connected dvi monitor
Date: Sat, 1 Nov 2008 03:46:48 -0700 (PDT) [thread overview]
Message-ID: <bug-18336-8800@http.bugs.freedesktop.org/> (raw)
http://bugs.freedesktop.org/show_bug.cgi?id=18336
Summary: nv10 : doesn't detect connected dvi monitor
Product: xorg
Version: 7.3
Platform: Other
OS/Version: Linux (All)
Status: NEW
Severity: normal
Priority: medium
Component: Driver/nouveau
AssignedTo: nouveau-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org
ReportedBy: msirapian-GANU6spQydw@public.gmane.org
QAContact: xorg-team-go0+a7rfsptAfugRpC6u6w@public.gmane.org
Hi,
I have a NV11 with two DFP monitors connected : one via a VGA connection (main
screen), the second, via its DVI input to the DVI output of NV11. With nouveau,
only VGA-0 is seen.
Both are connected at boot. Under Windows, they work and are recognized. With
nvidia blob, it used to work until lately, as their legacy driver is broken for
the dvi output of NV11 (and they won't fix it, naturally).
So the symptom is simple : only vga monitor is seen.
sirapian@enigma:~$ xrandr -q
Screen 0: minimum 320 x 200, current 1024 x 768, maximum 2704 x 1050
VGA-0 connected 1024x768+0+0 (normal left inverted right x axis y axis) 307mm x
230mm
I've read the xorg.log, it seems to see 4 DCB entries, which are merged to one,
and only VGA monitor is seen. In a former xorg.log, when I used the blob, it
saw there 2 DCBs, and the two monitors were identified.
I attached my xorg.0.log.
I'm using the experimental debian packages (the latest ones).
If you need further information or investigation, please tell me.
--
Configure bugmail: http://bugs.freedesktop.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
next reply other threads:[~2008-11-01 10:46 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-11-01 10:46 bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ [this message]
[not found] ` <bug-18336-8800-V0hAGp6uBxMKqLRl/0Ahz6D7qz1kEfGD2LY78lusg7I@public.gmane.org/>
2008-11-01 10:49 ` [Bug 18336] nv10 : doesn't detect connected dvi monitor bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2008-11-05 18:00 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2008-11-05 19:29 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2008-11-05 19:31 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2009-04-30 13:23 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2010-07-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-18336-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.