Date: Mon, 23 May 2005 09:51:28 +0200 From: Jeremie Le Hen <jeremie@le-hen.org> To: Xin LI <delphij@frontfree.net> Cc: freebsd-current@FreeBSD.org, delphij@FreeBSD.org Subject: Re: [CALL FOR TESTERS] VESA High Resolution Console support from DragonFly Message-ID: <20050523075128.GP850@obiwan.tataz.chchile.org> In-Reply-To: <20050523003843.GO850@obiwan.tataz.chchile.org> References: <20050522112612.GA37841@frontfree.net> <20050523003843.GO850@obiwan.tataz.chchile.org>
next in thread | previous in thread | raw e-mail | index | archive | help
Xin, > I have used the patch for five minutes now and it seems to work well. > I can switch to multiple resolutions (640x480, 800x600, 1024x768), switch > console. When I set a non-supported resolution, the screen stay blanked > a few seconds and then goes back to the last resolution telling this > operation is not supported by device. Perfect. Nearly perfect :-). I use the fade saver and when I woke up this morning, going back from the screen saver turned the VESA console text into blue. Not the whole text, just the non-brilliant one. This is not the case on non-VESA consoles. Switching to another console suffices to get back the orignal text color. I didn't tested whether the blue turns into another color if I change the default text color, but displaying various colors with vim (blue, red, yellow), it appears that all colors are, at least, darkened. Note that as far as I tested, this is not specific to any screensaver, it seems to be ensued by a generic piece of code. I tried changing the resolution and I managed to get another color : instead of blue, I got red :-). Regards, -- Jeremie Le Hen < jeremie at le-hen dot org >< ttz at chchile dot org >
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20050523075128.GP850>