[BETA PATCH] VESA mode support for syscons

YONETANI Tomokazu qhwt+dragonfly-submit at les.ath.cx
Tue Aug 24 07:36:49 PDT 2004

On Sun, Aug 22, 2004 at 12:38:27AM +0200, Sascha Wildner wrote:
> here is a patch that makes syscons support 16/32 bit video modes with 
> direct memory model:
> http://www.yoyodyne.de/tmp/syscons.patch
> After patch application and kernel recompilation it should be possible 
> to select these modes with vidcontrol, e.g. for a 1024x768 console you 
> have to type:
> # vidcontrol MODE_280
> You can obtain a list of valid mode numbers with 'vidcontrol -i mode'. 
> Generally, this patch adds support for all modes with numbers >=272 and 
> 16/32 bits depth.


> Here are some remarks:
> 1) On my machine here at home, when a screen saver exits into one of 
> those new modes the colors are either way too dark in the 16 bit modes 
> or nothing can be seen at all in 32 bit modes (setting the video mode 
> again helps). On a friend's machine it works the way it should! This is 
> strange and it would be nice if I could get feedback from you on how the 
> screen saver is behaving on your system.

As far as I tested, this didn't reproduce on my Dynabook SS3500. Most
screen savers restored the mode correctly.
fade_saver didn't fade in 16/32 bits depth. daemon_saver and star_saver
didn't work. When green_saver is activated, the screen went blank and
never responded to keystroke until I rebooted. Other screen savers worked

> 3) If moused is active you'll get minor drawing errors when selecting 
> text with the mouse. But they vanish after you move the mouse around a bit.

It just works the same way as in 80x25 mode here.

> 6) I haven't tested the whole stuff with X (which I don't have 
> installed), e.g. if it is possible to switch to X and back again.

As far as I tested, this is working. I can switch between X and
console mode without any problem.


More information about the Submit mailing list