[lkml]   [2001]   [Feb]   [5]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
SubjectVESA framebuffer changes in 2.4
Just wondering whether the VESA framebuffer underwent wholesale changes
between 2.2 and 2.4. I use a graphical console (1024x768 @ 8bit colour
depth), and full-screen scrolling performance is *really* bad. When I type
'ls' in a directory with a large amount of files, it becomes really slow.
Under 2.2.18 I have no such problems.

I run my 2.4.1 system in a separate partition, built from scratch, and the
only important difference I can imagine between my 2.2.18 and 2.4.1 configs
is that I use agetty rather than mingetty in 2.4.1.

I can make my scrolling performance in 2.4.1 very good by appending the
following option in lilo.conf:


This makes scrolling down very fast - as fast if not faster than 2.2.18 -
but scrolling up one line at a time is absolutely horrendous - it seems to
redraw the whole screen. It is easy to test this bu using vi to edit a
file. I know this is probably due to the way that ywrap uses the video
card's memory as a buffer for scrolling down, but why is the behaviour so
different from 2.2.18?

BTW, I use an nvidia GeForce DDR 32MB RAM. I don't subscribe to the list,
so please CC replies to



To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to
Please read the FAQ at

 \ /
  Last update: 2005-03-22 12:58    [W:0.027 / U:0.072 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site