linux-fbdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Michal Suchanek" <hramrach@centrum.cz>
To: Petr Vandrovec <vandrove@vc.cvut.cz>
Cc: linux-fbdev-devel@lists.sourceforge.net
Subject: Re: Matrox (g450) DVI problems in 2.6.17
Date: Mon, 25 Sep 2006 22:52:15 +0200	[thread overview]
Message-ID: <a5d587fb0609251352l16de4533vcff34e5d4e439bde@mail.gmail.com> (raw)
In-Reply-To: <45181B01.2080203@vc.cvut.cz>

On 9/25/06, Petr Vandrovec <vandrove@vc.cvut.cz> wrote:
> Michal Suchanek wrote:
> > Hello from the Matrox DVI land
> >
> > For me matrox DVI framebuffer (sort of) works on Linux 2.6.16.19 and
> > fails on 2.6.17.13.
> >
> > The DVI support on Matroxes is quite flaky I'd guess.
>
> Ask Matrox to release documentation for their hardware...
Well, it looks like nobody releases the docs for thier graphics hardware...
>
> > I got a matrox g450
> >
> > 01:00.0 VGA compatible controller: Matrox Graphics, Inc. G400/G450 (rev 85)
> >
> > and I connect it with DVI to a flat panel.
>
> > For X to work I have to use kernel framebuffer to set the videomode
> > (UseFBDev in X). Otherwise X fails to set the timings correctly
> > (nothing is visible).
> > With kernel framebuffer I get an usable videomode in two steps. First
> > I start the X server, and there is only a message from the monitor
> > about bad timings. However, after switching to the console and back X
> > works well. Sometimes the switch is not needed (usually if started
> > from an already running X server). Works with software suspend as well
> > (as long as dri is not used).
>
> Are not you using ACER's monitor?  Try just powering monitor off and back on
> instead of doing mode switch.

It's an EIZO display. Switching the mode is easier than pressing the
power button but I can try that when I get to start the X server
again.

>
> > With 2.6.17.13 the picture I get is noisy. The lines shift a few
> > pixels horizontally in various directions. It is much like the results
> > I got with g550 when there was no screen connected to DVI at startup.
> > only much more noise (there must be a screen connected to DVI at boot
> > for the framebuffer to work correctly with DVI - at least it had to
> > last time I tried).
>
> Upgrade to 2.6.18, it should behave like 2.6.16 does.
I will try. Thanks

Michal

-------------------------------------------------------------------------
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

  reply	other threads:[~2006-09-25 20:52 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-09-25 17:57 Matrox (g450) DVI problems in 2.6.17 Michal Suchanek
2006-09-25 18:08 ` Petr Vandrovec
2006-09-25 20:52   ` Michal Suchanek [this message]
2006-09-26  7:12   ` Michal Suchanek

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=a5d587fb0609251352l16de4533vcff34e5d4e439bde@mail.gmail.com \
    --to=hramrach@centrum.cz \
    --cc=linux-fbdev-devel@lists.sourceforge.net \
    --cc=vandrove@vc.cvut.cz \
    /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).