On Fri, Mar 04, 2016 at 09:54:56AM -0800, Paul Rogers wrote:
For my latest LFS (7.7, x86-64) build, I'm finally, reluctantly, using
framebuffers to accomodate modern video cards. I put "video=640x480-16"
kernel parameter in GRUB to keep the startup console messages readable &
looking like they were from the kernel startup.
One of the touted reasons for using framebuffers is to prevent
screen "flicker", but when udev runs the screen always blanks for
half a second! Any way to make that faster?
To me, 'flicker' is a flashing screen, not one which blanks and then
redisplays, probably in a different format. On ATI hardware, the
screen stays blank while firmware is loaded - on my Kaveri that
takes a lot longer than on my old R600 and my past R200 (but then it
loads a lot more firmware).
But also, curiously, on the startup messages when the FB takes over,
the "[OK]" part is shifted right one character. Looks strange! The
old "off by one" error?
Look at dmesg to see what size of framebuffer it has switched to.
It sounds as if you perhaps have one extra character of line width
in the framebuffer.
I normally load a console font, and that can change the screen size.
So, again on my Kaveri, the '[OK]' messages do not all line up.
init.d/functions doesn't seem to care about
framebuffers. init.d/console does, but doesn't do anything about line
lengths. stty, in functions, returning a different size? It's
getting that from the kernel, and it's not obvious where functions is
"off by one". Is this fixable?
Does it matter ? My screens get cleared when I login, so the
variable layout is not important to me.
If it does matter to you, I suppose you could try adding a series of
your own "debug" bootscripts to report information from stty or
whatever, and run them before and after the shift. Perhaps write to
a logfile.
