On 20 October 2001, Michel D?nzer said:
> The console's video mode shouldn't matter. What does matter is that the
> X server uses the framebuffer device interface, otherwise it still has
> to save and restore the hardware state. If your X driver doesn't support
> Option "UseFBDev" you're SOL.
My card is a Matrox G400, and "man mga" says this driver has a
"UseFBDev" option, so I guess I'm not SOL. Cool.
> Yes, use fbset -x to get an X mode definition. But as I pointed out, it
> shouldn't matter. The important thing is that the two VCs you want to
> switch between use the same mode.
Just to clarify: do you mean that the two VCs must have the same mode
before starting X on either of them? (On reflection, I can't see how
*else* to interpret that, but I want to be sure.)
I guess that means I have to put the right "video=matrox:vesa:..." so
that the kernel framebuffer sets the mode on the VCs destined to run X
to the mode that I want to run X with.
A curious aside: is it possible to fbset the mode of a different VC?
Eg. if I'm in VC 1, fbset only changes the mode of that VC. Can I make
it change the mode of VC 7? (Yes, I know this is a Linux framebuffer
question, but I thought I'd take a chance here.) I ask because I'd like
to avoid endless reboots just to get the mode timings the sync between
my FB VCs and X.
Thanks for the tips --
Greg
--
Greg Ward - software developer [EMAIL PROTECTED]
MEMS Exchange http://www.mems-exchange.org
_______________________________________________
Xpert mailing list
[EMAIL PROTECTED]
http://XFree86.Org/mailman/listinfo/xpert
