From: thunder7@xs4all.nl
To: James Simmons <jsimmons@linux-fbdev.org>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [lkml]Re: [lkml]Re: Matrox G400 Dualhead
Date: Mon, 2 Apr 2001 13:02:24 +0200 [thread overview]
Message-ID: <20010402130224.A4403@middle.of.nowhere> (raw)
In-Reply-To: <Pine.LNX.4.31.0104010737420.736-100000@linux.local>
In-Reply-To: <Pine.LNX.4.31.0104010737420.736-100000@linux.local>; from jsimmons@linux-fbdev.org on Sun, Apr 01, 2001 at 07:40:36AM -0700
On Sun, Apr 01, 2001 at 07:40:36AM -0700, James Simmons wrote:
>
> >If I use X on an accelerated, normal Matrox screen, my monitor complains
> >on exit:
> >
> >fH 49.4 KHz, fV 39.8 Hz
> >
> >(and it doesn't sync at 40 Hz vertical refresh :-( ).
> >
> >This is _half_ of the normal 80 Hz. Using fbset -a "1600x1200-80" before
> >X, of after X, doesn't do anything. Does anybody know what to hack out
> >in X to get it to _not_ reset my G400 to some unusable state? 3.3.6 was
> >didn't do this. I can use the framebuffer-screen just fine, but I miss
> >the DGA extension.
>
> Try adding this to your XF86Config file:
>
> Section "Device"
> ...
> Option UseFBDev
> ...
> EndSection
>
A very neat trick. X can now be ended correctly. Unfortunately, any
scrolling on any VT afterwards gives me a corrupted screen - parts of
the screen from other VT's are inserted below, or over the cursor
position, and at 'half-line' intervals. In typing this email, I've seen
it 5 times already.
I'm willing to test anything - but the corruption is alway gone after I
switch VT's. So getting a screendump is not easy.
Thanks!
Jurriaan
--
Send lawyers, guns, and money,
The shit has hit the fan.
Warren Zevon
GNU/Linux 2.4.2-ac28 SMP/ReiserFS 2x1743 bogomips load av: 0.98 0.54 0.21
next prev parent reply other threads:[~2001-04-02 18:17 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-04-01 14:40 James Simmons
2001-04-02 11:02 ` thunder7 [this message]
2001-04-03 3:16 [lkml]Re: " James Simmons
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=20010402130224.A4403@middle.of.nowhere \
--to=thunder7@xs4all.nl \
--cc=jsimmons@linux-fbdev.org \
--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
all inboxes | Powered by JetHome®