Date: Tue, 3 Apr 2007 08:18:07 -0700 From: Freddie Cash <fcash@ocis.net> To: stable@freebsd.org Subject: Re: Changing Console Resolution - Vidcontrol Message-ID: <200704030818.07775.fcash@ocis.net> In-Reply-To: <200704031015.19451.doconnor@gsoft.com.au> References: <8d23ec860704021055n12e7ec05h300effc21e54713e@mail.gmail.com> <200704021354.57395.fcash@ocis.net> <200704031015.19451.doconnor@gsoft.com.au>
next in thread | previous in thread | raw e-mail | index | archive | help
On Monday 02 April 2007 05:45 pm, Daniel O'Connor wrote: > On Tuesday 03 April 2007 06:24, Freddie Cash wrote: > > 1024x768 is a pretty standard VESA mode used on a lot of people's > > text consoles. :) On most videocards, MODE_279 will be 1024x768 > > w/16 bpp colour. Check the output of "vidcontrol -i". You'll see a > > lot of different modes, some text, some > > raster/bitmap/VESA/whatever-you-call-it. > > > > This has nothing to do with X or any GUI. > > I don't understand why people who want high resolution consoles don't > run X. Why should we run X on a server just to get a larger text console? Or on a laptop that we don't always want to wait for X to load? Sometimes, it's nice to be able to use the entire screen without having to load up a lot of unneeded software, like the entire X stack. > It is a *lot* faster for the vast majority of cards (ie ones which > aren't doing VESA modes). > > Scrolling a screen full of text at a decent resolution using VESA == > slideshow. Not in my experience on a Toshiba laptop using a Radeon 7000 chipset. In VMWare, scrolling a 1024x768 screen during a port compile is chunky. But doing so on my laptop I see no difference between the text console and a tab in Konsole. -- Freddie Cash fcash@ocis.net
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200704030818.07775.fcash>