From: "Hans-Jürgen Koch" <hjk@linutronix.de>
To: linux-fbdev-devel@lists.sourceforge.net
Cc: Alex Deucher <alexdeucher@gmail.com>
Subject: Re: Matrox G550, dual head, 1680x1050
Date: Fri, 2 Mar 2007 00:49:54 +0100 [thread overview]
Message-ID: <200703020049.55005.hjk@linutronix.de> (raw)
In-Reply-To: <a728f9f90703011529r1cb92c10y2fbe503f34693507@mail.gmail.com>
Am Freitag, 2. März 2007 00:29 schrieb Alex Deucher:
> On 3/1/07, Hans-Jürgen Koch <hjk@linutronix.de> wrote:
> > Hi,
> > I'm the proud owner of two NEC MultiSync 2070WNX monitors (1680x1050) and
> > a Matrox G550 dual DVI card. I'm now trying to set up a dual head
> > configuration with this equipment.
> >
> > I'm booting with video=matroxfb:vesa:0x1BB, as there is no 1680x1050 vesa
> > mode. This works, both monitors show the same and complain about the
> > wrong resolution.
> >
> > Now I start my X server (xorg.conf below) and wish to get a xinerama
> > setup. Monitor 1 switches to 1680x1050 and shows a nice clean screen.
> > Monitor 2 seems to have problems, though. I guess the card still outputs
> > the 1280x1024 set up at boot time. Colours are correct, but the image is
> > heavily distorted. It looks like the X server thinks it's 1680x1050 but
> > in fact it's still 1280x1024.
> >
> > I spent some time googling, but to no avail. Now my questions:
> >
> > Is this a known limitation of matroxfb?
> > If yes, is it considered a bug? I could spend some time looking into the
> > code. Do I have any chance to get this working in a reasonable dual head
> > configuration? Any hints?
>
> IIRC, the current mga X server doesn't know how to deal with DVI
> (single or dual ports). DVI was only supported with matrox' binary
> module.
>
Hi Alex,
thanks for your fast reply.
Currently, I've got both monitors connected with VGA cables. The card has some
proprietary 60-pin or so connector, and I've got an adapter caple from that
plug to 2xVGA. Both monitors show a stable picture, but only the picture on
monitor #1 is usable. It really looks like the X server is trying to switch
both channels to 1680x1050, but only succeeds with the first one.
Hans
-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys-and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
next prev parent reply other threads:[~2007-03-01 23:50 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-03-01 23:25 Matrox G550, dual head, 1680x1050 Hans-Jürgen Koch
2007-03-01 23:29 ` Alex Deucher
2007-03-01 23:49 ` Hans-Jürgen Koch [this message]
2007-03-01 23:56 ` Hans-Jürgen Koch
2007-03-02 1:49 ` Alex Deucher
[not found] <200703021053.00955.hjk@linutronix.de>
[not found] ` <200703021610.58188.hjk@linutronix.de>
[not found] ` <20070302152414.GC907@code-monkey.de>
2007-03-04 21:47 ` Hans-Jürgen Koch
2007-03-05 4:59 ` Petr Vandrovec
2007-03-05 6:33 ` Geert Uytterhoeven
2007-03-05 20:02 ` Hans-Jürgen Koch
2007-03-06 9:25 ` Petr Vandrovec
2007-03-06 9:48 ` Geert Uytterhoeven
2007-03-06 11:35 ` Petr Vandrovec
2007-03-05 6:59 ` Tilman Sauerbeck
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=200703020049.55005.hjk@linutronix.de \
--to=hjk@linutronix.de \
--cc=alexdeucher@gmail.com \
--cc=linux-fbdev-devel@lists.sourceforge.net \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).