On Thu, Aug 05, 1999 at 03:13:15PM +0200, Tim Boykett wrote:
>
> Hi all - battling with the framebuffer device
> for X on my leedel laptop I managed to somehow
> end up with a screwed lilo. When booting I only
> get LIL- which means there is a checksum error in
> the secondary load (whatever that exactly means).
Hmmm, as far as I can remember I read in the lilo documentation that
the map file is corrupted, i. e. a file containing the sector numbers
of all of the files lilo needs. I myself solved this problem by rewriting
the map file; this can be done by typing in just
lilo
> Booting from another source, trying lilo again I get
> the error message that the kernel is too big for several
> kernels that I have previously happily used.
Can you load those older kernels via loadlin, for instance?
Are you sure you used the compressed versions of the kernels, i. e.
vmlinuz instead of vmlinux?
I myself got "kernel too big" only while compiling a new kernel.
All I had to do was to replace "make zImage" by "make bzImage", which
in fact doesn't mean a better compression, but a different way of using
memory areas. Usually with kernels 2.2.x and 2.3.x you are forced to
use make bzImage.
> any ideas? Could this be a real hardware error,
> that the boot sector(s) on my root device /dev/hda3
> are damaged? How ould I find out?
No, I'm sure this not a hardware related error. You did something that made
the map file become wrong. You must rewrite the map file, but before that
you have to find a way to boot the system. If you boot from a different source
make sure you don't mix up the two kernel "worlds".
Bye, Juergen.
--
****************************************************************
* Juergen Leising; email: [EMAIL PROTECTED] *
* http://www.stud.uni-bayreuth.de/~a0037/ *
****************************************************************
