public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Trevor-Hemsley@dial.pipex.com (Trevor Hemsley)
To: linux-kernel@vger.kernel.org
Subject: Re: Matrox G400 Dualhead
Date: Mon, 02 Apr 2001 22:55:36	[thread overview]
Message-ID: <20010402221831Z131407-407+5602@vger.kernel.org> (raw)

On Mon, 2 Apr 2001 17:43:42, Petr Vandrovec <vandrove@vc.cvut.cz> 
wrote:

> Trevor Hemsley wrote:
> 
> > I get this as well on my G200. From observation it appears that the
> > refresh rate is being doubled when you exit X and that's why the
> > console appears blank. On my system I normally use
> > 
> > modprobe matroxfb vesa=263 fv=85
> > 
> > to give a large text console. On return from X, if I blindly type
> > 
> > fbset "640x480-60"
> > 
> > then I get a visible screen back but my monitor tells me that it's
> > running at 640x480@119Hz. Same thing for 800x600-60 only this one says
> > 120Hz.
> 
> Unfortunately Matrox datasheet says that it is impossible :-( Can you
> try 'fbset -depth 0; fbset -depth 8' ?

Yes, that fixes it. Issuing the first fbset command brings me back 
some sort of display, all fsck'ed up but vaguely readable with 
shimmering bits of text all over it in the wrong places. The second 
fbset gets it back correctly at the right resolution and right refresh
rate. Thanks, a workaround at least.

-- 
Trevor Hemsley, Brighton, UK.
Trevor-Hemsley@dial.pipex.com

             reply	other threads:[~2001-04-02 22:18 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-04-02 22:55 Trevor Hemsley [this message]
  -- strict thread matches above, loose matches on Subject: below --
2001-05-27 22:48 Matrox G400 Dualhead mythos
2001-05-28  3:13 ` Rafael Herrera
2001-05-28  8:43   ` mythos
2001-05-28 16:16     ` Rafael Herrera
2001-04-01 20:22 mythos
2001-04-02 17:36 ` Petr Vandrovec
2001-03-31 17:46 J Brook
2001-03-31 11:01 Trevor Hemsley
2001-04-02 17:39 ` Petr Vandrovec
2001-03-31  0:12 J Brook
2001-03-31  1:59 ` Petr Vandrovec
2001-03-31  7:09 ` Rafael E. Herrera
2001-03-30 20:13 mythos
2001-03-30 20:45 ` Alan Olsen
2001-03-30 21:10   ` mythos

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=20010402221831Z131407-407+5602@vger.kernel.org \
    --to=trevor-hemsley@dial.pipex.com \
    --cc=linux-kernel@vger.kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox