From: Chris Ball <cjb-2X9k7bc8m7Mdnm+yROfE0A@public.gmane.org>
To: Pascal Schoenhardt <stoanhart-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
Cc: nouveau-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org
Subject: Re: NV43 (6600 Go) Report
Date: Tue, 15 May 2007 17:10:10 +0100 [thread overview]
Message-ID: <20070515161010.GA8693@void.printf.net> (raw)
In-Reply-To: <438b0cc70705150323q2356c42flb70d4f0675bbc478-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
Hi Pascal,
On Tue, May 15, 2007 at 11:23:50AM +0100, Pascal Schoenhardt wrote:
> Now, here is the real issue: My laptop has a VGA port and an svideo
> port. To start working on smooth multi-head support for gnome, I
> obviously need use of at least the VGA port. As it stands, nouveau
> does not detect any of these outputs. As I understand it, xrandr
> should be reporting something like this:
Have you tried "xrandr --auto"? It's usually required to run this
command before xrandr picks up on a VGA port connection, because
usually (at least, on Intel) we don't get an interrupt when a
monitor is plugged in.
Which brings me to a question: do we get one on nVidia? Could nouveau
be able to kick off xrandr as soon as a monitor's connected?
(I don't know how well Xrandr actually works on nouveau, I'm afraid.)
- Chris.
--
Chris Ball <cjb-2X9k7bc8m7Mdnm+yROfE0A@public.gmane.org>
next prev parent reply other threads:[~2007-05-15 16:10 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-15 10:23 NV43 (6600 Go) Report Pascal Schoenhardt
[not found] ` <438b0cc70705150323q2356c42flb70d4f0675bbc478-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2007-05-15 16:10 ` Chris Ball [this message]
[not found] ` <20070515161010.GA8693-zkTaxWjgBN6ccd+RBA7C9g@public.gmane.org>
2007-05-15 16:52 ` Pascal Schoenhardt
2007-05-15 18:17 ` Pekka Paalanen
[not found] ` <20070515211717.3a386fc8-cxYvVS3buNOdIgDiPM52R8c4bpwCjbIv@public.gmane.org>
2007-05-17 9:15 ` Pascal Schoenhardt
[not found] ` <438b0cc70705170215s60fa9ff9l74fda2724f783953-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2007-05-17 9:40 ` Pekka Paalanen
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=20070515161010.GA8693@void.printf.net \
--to=cjb-2x9k7bc8m7mdnm+yrofe0a@public.gmane.org \
--cc=nouveau-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org \
--cc=stoanhart-Re5JQEeQqe8AvxtiuMwx3w@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.