![](https://seccdn.libravatar.org/avatar/9435667f7160374bc34a8600b686aecd.jpg?s=120&d=mm&r=g)
27.11.2016 01:27, L. A. Walsh пишет:
Andrei Borzenkov wrote:
As far as I can tell
- early boot (platform dependent) kernel code fills in screen_info structure describing current video mode at the time kernel is booted
This *seems* to partly contradict the code in lilo. It allows "vga="ask|ext|extended|normal|NNN|0xHHH" and claims that this vga setting is done in lilo.
Yes, it was not exactly accurate. vga= is interpreted by bootloader, translated into number and put in list of parameters for kernel; later real-mode code in kernel picks up this value and initializes screen_info. If no vga= was present on kernel command line, it defaults to the value built in kernel image, which defaults to normal text mode VGA in upstream Makefile. 32 bit kernel entry point entirely bypasses real-mode code and expects screen_info that contains valid information. In this case it is filled in by bootloader (or, apparently, by kexec code as we have seen). ...
Now I notice one point of potential problem: lilo sets the vga mode to 43 lines x 133 columns, but I don't think the kernel is getting the "news", since about 146 lines into the boot log, I see a message:
Console: colour VGA+ 80x25 console [tty0] enabled console [ttyS0] enabled
---- I.e. the kernel maybe thinks the VGA screen is in 80x25...which isn't how 'lilo' left it.
Please show full dmesg for your bare metal boot and for you kexec boot as well as lilo section for your kernel. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org