Re: Matrox G400 Dualhead

Re: Matrox G400 Dualhead

[J Brook]

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

 Petr, I had a look at the drivers/video/matrox subdir and there's no
difference between 2.4.2 and 2.4.3, however there are differences in
the drivers/video dir to do with framebuffers. The files that have
been changed in drivers/video/ are:
  creatorfb.c
  fbmem.c
  fonts.c
  modedb.c
  sbus.c

 I know nothing about the nature of the changes that have been made
though!

 It does seem to be a kernel problem rather than a X4.0.3 problem
seeing as how 4.0.3 works fine under 2.4.2, and that using fbset on
the framebuffer console in 2.4.3 solves the problem.

     John
----------------
jbk@postmark.net

Re: [lkml]Re: Matrox G400 Dualhead

[thunder7]

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

Re: [lkml]Re: Matrox G400 Dualhead

[James Simmons]

>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


MS: (n) 1. A debilitating and surprisingly widespread affliction that
renders the sufferer barely able to perform the simplest task. 2. A disease.

James Simmons  [jsimmons@linux-fbdev.org]               ____/|
fbdev/console/gfx developer                             \ o.O|
http://www.linux-fbdev.org                               =(_)=
http://linuxgfx.sourceforge.net                            U
http://linuxconsole.sourceforge.net