From: bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ@public.gmane.org
To: nouveau-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org
Subject: [Bug 13323] New: 7600Go: RandR12 fails to drive external DVI
Date: Tue, 20 Nov 2007 13:22:45 -0800 (PST) [thread overview]
Message-ID: <bug-13323-8800@http.bugs.freedesktop.org/> (raw)
http://bugs.freedesktop.org/show_bug.cgi?id=13323
Summary: 7600Go: RandR12 fails to drive external DVI
Product: xorg
Version: git
Platform: Other
OS/Version: All
Status: NEW
Severity: normal
Priority: medium
Component: Driver/nouveau
AssignedTo: nouveau-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org
ReportedBy: chalserogers-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org
QAContact: xorg-team-go0+a7rfsptAfugRpC6u6w@public.gmane.org
On my laptop with a 7600GO, internal 1680x1050 LVDS LCD and external 1280x1024
single-DVI LCD connected.
Setting randr12 to true in xorg.conf results in no signal being sent to the
external DVI monitor. Instead, the laptop's screen goes a speckled purple
which then bleeds into white, and messes up the colours at the console, too.
Restarting X without randr12 "true" works (but doesn't drive the external
monitor, obviously), and fixes the console colours.
I'll attach the Xorg log for this session.
A couple of weeks ago I sent in a mmio trace of the nvidia driver initialising
X with this setup. Feel free to ask for it again.
--
Configure bugmail: http://bugs.freedesktop.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.
next reply other threads:[~2007-11-20 21:22 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-11-20 21:22 bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ [this message]
[not found] ` <bug-13323-8800-V0hAGp6uBxMKqLRl/0Ahz6D7qz1kEfGD2LY78lusg7I@public.gmane.org/>
2007-11-20 21:23 ` [Bug 13323] 7600Go: RandR12 fails to drive external DVI bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2007-11-20 21:47 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2007-11-23 9:28 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2007-11-25 11:25 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2007-11-29 9:10 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2007-11-29 9:11 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2008-01-17 14:05 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2008-01-17 22:54 ` 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-13323-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.