Date: Fri, 6 Apr 2007 03:42:48 +0200 From: "Michael Schuh" <michael.schuh@gmail.com> To: "Kevin Oberman" <oberman@es.net>, "FreeBSD Stable" <freebsd-stable@freebsd.org> Subject: Re: Changing Console Resolution - Vidcontrol Message-ID: <1dbad3150704051842g20fe8352k331135811e863f3b@mail.gmail.com> In-Reply-To: <20070405234308.7083545055@ptavv.es.net> References: <1dbad3150704051531m59b5342fof2036ec6f5484a73@mail.gmail.com> <20070405234308.7083545055@ptavv.es.net>
next in thread | previous in thread | raw e-mail | index | archive | help
Hi Kevin, yes you are right my systems also loses lines, i believe that the mechanics in vidcontrol or in the kernels syscons device are the sources of this behaviour ...because through the init ( blanks screen and set mode )...... About the buffer at this time I am not really sure, but in the kernel's NOTES files it is setted per default to 200. I think you are right with the scrollback buffer that was the thing that i mean. you could have a "slideshow" or "teleporting" effect on some slow graphic cards, or on cards that not fully supports vesa while you scrolling through the screens, because if you use the vesa driver the output could be slower while having more overhead.. ...read also the postings in the stable-list ( I think from oliver fromme)...... hmmm, if this behavior (losing lines) could not turned out by options or configuring the mode directly after loading the vesa module, I think it is a bug and we should enter it to the GNATS bugtracker.... but first we call help in the list :-) Could anyone, that is deeper in the woods, shed us some light on this behavior and eventually a possible solution? cheers michael --=20 =3D=3D=3D michael-schuh.net =3D=3D=3D Michael Schuh Preu=DFenstr. 13 66111 Saarbr=FCcken phone: 0681/8319664 mobil: 0177/9738644 @: michael.schuh@gmail.com =3D=3D=3D Ust-ID: DE251072318 =3D=3D=3D
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?1dbad3150704051842g20fe8352k331135811e863f3b>