>I'm having a problem with my newly compiled kernel (2.2.7, also tried
>my old one, 2.0.36, same problem).
>
>it get's too big for /sbin/lilo....
>1,4mb..
>
>Why ?
LILO can only boot into the lower 640k memory. Its' been a while since I dug
into this.. There are also a limited number of mapping blocks available for
lilo to use when locating large kernels. I don't know exactly how many but
it's possible you exceeded the count (may also be related to highly fragmented
file system.. but not sure in your case).
There are several ways around the limit:
1. try creating a "make bzlilo"... which I haven't had to do yet. This is
supposed to do a better compression.
2. Put as many drivers as possible into loadable modules.
My choice is the second. By making all of my drivers/filesystems as loadable
modules I was able to reduce my boot kernel to 350-400K. Currently I have
built into the boot:
floppy, SCSI, console, ext2fs
Loadable modules:
serial, IDE, dosfs, ntfs, iso9660, CD, MT, audio, network
When I first made my 2.1.115 kernel I had too many things in it too.
Using the modules also has allowed me to change network cards/drivers, update
the iso9660, and CD modules without building another kernel. It also
can boot faster, since the kernel can (now) perform a load-on-demand for
missing modules after the system is up.
-------------------------------------------------------------------------
Jesse I Pollard, II
Email: [EMAIL PROTECTED]
Any opinions expressed are solely my own.
-
Linux SMP list: FIRST see FAQ at http://www.irisa.fr/prive/mentre/smp-faq/
To Unsubscribe: send "unsubscribe linux-smp" to [EMAIL PROTECTED]
