Date: Thu, 2 Mar 2006 18:34:51 +0300 From: FreeLSD <freelsd@rea.mbslab.kiae.ru> To: Ivan Voras <ivoras@fer.hr> Cc: freebsd-current@freebsd.org Subject: Re: VESA Framebuffer Message-ID: <20060302153451.GL1107@rea.mbslab.kiae.ru> In-Reply-To: <44070D88.4080800@fer.hr> References: <b949575f0603011327s16173844sb5fc2de8c6d6120e@mail.gmail.com> <44069A2C.4070307@cs.tu-berlin.de> <44069DAC.8040607@gmail.com> <200603021336.42201.root@solink.ru> <20060302092103.GG1017@rea.mbslab.kiae.ru> <44070D88.4080800@fer.hr>
next in thread | previous in thread | raw e-mail | index | archive | help
Thu, Mar 02, 2006 at 04:21:44PM +0100, Ivan Voras wrote: > Vidcontrol is callable from boot process via settings in rc.conf > (allscrens_flags). Yeah, I used to have allscreens_flags="MODE_291". > >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. > > It doesn't clear it, it "scrolls" them away (at least, it does so when called > at boot). May be it is called "scrolls", but after the boot I do see the following: I can scroll up pressing CapsLock and will see the kernel messages and some output from the /etc/rc, but about twenty lines before the syscons initialization are lost -- they are clean. This is what I call "cleans", but the result is the same as for "scrolls": I do lose some lines of output from the /etc/rc and this is annoying. -- Yours, LSD
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20060302153451.GL1107>