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 - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/