[gentoo-user] Lilo EBDA is big yet computer boots (multiple choice)

[gentoo-user] Lilo EBDA is big yet computer boots (multiple choice)

[Chris Stankevitz]

Hello,

1. When my machine boots, just after I tell lilo which kernel to load,
lilo reports "EBDA is big; kernel setup stack overlaps LILO second
stage"

2. I chose lilo over grub because of some gentoo handbook comment
about multilib that frightened me.

3. My machine boots fine.  I have to be paying close attention to even
see that message since the screen quickly clears during the kernel
boot sequence.

4. I do not know how long this has been happening, but I just noticed
it today.  Possible coincidence: just upgraded gcc and recompiled
world and the kernel today.

5. I ran /sbin/lilo after compiling and installing the kernel.  I even
ran it a few more times just to be on the safe side.

===

Question: Why am I getting the error "EBDA is big"?

a) You did not run /sbin/lilo after installing the kernel [FALSE see (5)]

b) There is something very wrong and your machine is unable to boot
[FALSE see (3)]

c) Just be thankful your machine boots.  Don't you have anything
better to worry about?

d) Use grub and hope that this problem goes away without really
understanding it.

e) People get this message yet are able to boot when their kernels are
too big.  Randomly convert a component to a loadable module;
recompile; reboot; repeat until problem goes away.

f) [your answer here]

Thank you,

Chris


===

PS: My kernel install procedure:

make -j4 && make -j4 modules_install && cp /boot/kernel
/boot/kernel.bak && cp /boot/.config /boot/.config.bak && cp
arch/x86_64/boot/bzImage /boot/kernel && cp .config /boot/.config &&
emerge --oneshot nvidia-drivers && emerge --oneshot virtualbox-modules
&& /sbin/lilo

===

PPS: Output of lilo -v

# /sbin/lilo -v
LILO version 22.8, Copyright (C) 1992-1998 Werner Almesberger
Development beyond version 21 Copyright (C) 1999-2006 John Coffman
Released 19-Feb-2007 and compiled at 14:08:13 on Jan 13 2013

Warning: LBA32 addressing assumed
Reading boot sector from /dev/sda
Using MENU secondary loader
Calling map_insert_data
Warning: The boot sector and map file are on different disks.

Boot image: /boot/kernel
Added kernel *

Boot image: /boot/kernel.bak
Added bak

Boot image: /boot/safe
Added safe

Boot other: /dev/sda3, on /dev/sda, loader CHAIN
Added windows

Writing boot sector.
/boot/boot.0800 exists - no boot sector backup copy made.
2 warnings were issued.