mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: thunder7@xs4all.nl
To: linux-kernel@vger.kernel.org
Subject: Re: [lkml]Re: Matrox G400 Dualhead
Date: Sun, 1 Apr 2001 10:55:39 +0200	[thread overview]
Message-ID: <20010401105539.A892@middle.of.nowhere> (raw)
In-Reply-To: <20010331174638.16806.qmail@venus.postmark.net>
In-Reply-To: <20010331174638.16806.qmail@venus.postmark.net>; from jbk@postmark.net on Sat, Mar 31, 2001 at 05:46:38PM +0000

On Sat, Mar 31, 2001 at 05:46:38PM +0000, J Brook wrote:
> > I have a similar problem with my G450, booting into the framebuffer,
> > then loading xdm and working in X, and then switching back to the 
> > console. I may have another detail to add in that when I switch back
> > to the console from X, my monitor blanks and displays the warning 
> > that the frequencies are out of range.
> 
>  I think I have a work around. Boot up 2.4.3 with the framebuffer
> enabled as normal. Log in as root and use the fbset program to change
> the settings for all the framebuffers.
> eg.
> 
> fbset -a 1024x768-70
> 
> or whatever works for you. fbset has its own man page.
> 
> This makes everything hunky-dory for me, in that after running fbset
> I
> can go in and out of X without ever losing the video signal.
> 
Well, that certainly doesn't work for me (2.4.2-ac28, G400):

fbset -i:

mode "1600x1200-80"
    # D: 205.846 MHz, H: 99.347 kHz, V: 79.989 Hz
    geometry 1600 1200 1600 5241 16
    timings 4858 272 48 32 5 152 5
    accel true
    rgba 5/11,6/5,5/0,0/0
endmode

Frame buffer device information:
    Name        : MATROX
    Address     : 0xd4000000
    Size        : 16773120
    Type        : PACKED PIXELS
    Visual      : TRUECOLOR
    XPanStep    : 8
    YPanStep    : 1
    YWrapStep   : 0
    LineLength  : 3200
    MMIO Address: 0xd6000000
    MMIO Size   : 16384
    Accelerator : Matrox G400

01:00.0 VGA compatible controller: Matrox Graphics, Inc. MGA G400 AGP (rev 03) (prog-if 00 [VGA])
	Subsystem: Matrox Graphics, Inc. Millennium G400 32Mb SGRAM
	Flags: bus master, medium devsel, latency 32, IRQ 10
	Memory at d4000000 (32-bit, prefetchable) [size=32M]
	Memory at d6000000 (32-bit, non-prefetchable) [size=16K]
	Memory at d7000000 (32-bit, non-prefetchable) [size=8M]
	Expansion ROM at <unassigned> [disabled] [size=64K]
	Capabilities: <available only to root>

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.

Thanks,
Jurriaan
-- 
BOFH excuse #329:

Server depressed, needs Prozak
GNU/Linux 2.4.2-ac28 SMP/ReiserFS 2x1743 bogomips load av: 0.20 0.05 0.01

  reply	other threads:[~2001-04-01  8:51 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-03-31 17:46 J Brook
2001-04-01  8:55 ` thunder7 [this message]
2001-04-01 14:40 [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=20010401105539.A892@middle.of.nowhere \
    --to=thunder7@xs4all.nl \
    --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®