Date: Thu, 2 Mar 2006 12:21:03 +0300 From: FreeLSD <freelsd@rea.mbslab.kiae.ru> To: Bachilo Dmitry <root@solink.ru> Cc: freebsd-current@freebsd.org Subject: Re: VESA Framebuffer Message-ID: <20060302092103.GG1017@rea.mbslab.kiae.ru> In-Reply-To: <200603021336.42201.root@solink.ru> References: <b949575f0603011327s16173844sb5fc2de8c6d6120e@mail.gmail.com> <44069A2C.4070307@cs.tu-berlin.de> <44069DAC.8040607@gmail.com> <200603021336.42201.root@solink.ru>
next in thread | previous in thread | raw e-mail | index | archive | help
> For that you can just build a kernel with "options VESA" and then use > "vidcontrol VESA_800x600" (for example) to have graphical console. > > But what for? Isn't it a purely linux toy? No, not a toy: it is useful when your console is capable to do more than 80x25 without going to Xorg. I used to use it on my notebook, but I retired using it, because I need 1024x768 and it can be set only via vidcontrol. And vidcontrol cleans some amount of text buffer on the ttyv0 and some output from the startup services is lost. It will be great if this will be fixed. Just an example why graphical console can be useful on FreeBSD. -- Yours, LSD In the beginning the universe was created. This has widely been regarded as a bad move. -Douglas Adams
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20060302092103.GG1017>