Solved! (?) Re: lilo: 'Kernel /vmlinuz is too big'

1999-04-28 Thread Tony Crawford
Hi gang! Got the 586 kernel running! I don't know why. I did make bzlilo instead of make bzImage, and it failed with the same error message from lilo in the second-to-last message. But then I copied the bzImage from that compile "by hand" to /, ran lilo "by hand", and bingo. Go figure. So I'm

Re: lilo: 'Kernel /vmlinuz is too big'

1999-04-27 Thread Peter Allen
--- Begin Message --- Tony Crawford wrote: > > Ralf G. R. Bergs wrote (on 27 Apr 99, at 17:59): > > > You should *definitely* exclude support for things you don't need. This > > makes your kernel much smaller. Very helpful also is to compile things > > I have most everything in modules that goes

Re: lilo: 'Kernel /vmlinuz is too big'

1999-04-27 Thread Ian Peters
On Tue, Apr 27, 1999 at 11:03:25PM +0200, Tony Crawford wrote: > Ian Peters wrote (on 27 Apr 99, at 15:45): > > > > wasn't significantly smaller. Are there some arcana of bzImage-making > > > that I missed in the kernel docs? (and yes, I did make mrproper > > > first!) > > > > Uhh ... it's not

Re: lilo: 'Kernel /vmlinuz is too big'

1999-04-27 Thread Peter Allen
make zlilo works for me. Peter Allen Tony Crawford wrote: > > Ian Peters wrote (on 27 Apr 99, at 15:45): > > > > wasn't significantly smaller. Are there some arcana of bzImage-making > > > that I missed in the kernel docs? (and yes, I did make mrproper > > > first!) > > > > Uhh

Re: lilo: 'Kernel /vmlinuz is too big'

1999-04-27 Thread Tony Crawford
Ian Peters wrote (on 27 Apr 99, at 15:45): > > wasn't significantly smaller. Are there some arcana of bzImage-making > > that I missed in the kernel docs? (and yes, I did make mrproper > > first!) > > Uhh ... it's not supposed to be. It's not smaller, just contains > logic to handle loading th

Re: lilo: 'Kernel /vmlinuz is too big'

1999-04-27 Thread Ian Peters
On Tue, Apr 27, 1999 at 08:40:31PM +0200, Tony Crawford wrote: > It did work, in the sense that a kernel was compiled ... but it > wasn't significantly smaller. Are there some arcana of bzImage-making > that I missed in the kernel docs? (and yes, I did make mrproper > first!) Uhh ... it's not s

Re: lilo: 'Kernel /vmlinuz is too big'

1999-04-27 Thread Tony Crawford
Ralf G. R. Bergs wrote (on 27 Apr 99, at 17:59): > You should *definitely* exclude support for things you don't need. This > makes your kernel much smaller. Very helpful also is to compile things I have most everything in modules that goes in modules ... > floppy > disk, tape, cd-rom drivers, ne

Re: lilo: 'Kernel /vmlinuz is too big'

1999-04-27 Thread Ralf G. R. Bergs
Tony Crawford wrote: > > I got this error after throwing out a 386/387 mainboard and putting > in a Pentium 133/PCI, then recompiling the kernel with the new > processor type and PCI bios support. Now Lilo doesn't want to install > the new kernel, grr-grr! The old one was already over 700 KB and

lilo: 'Kernel /vmlinuz is too big'

1999-04-27 Thread Tony Crawford
Hi Gang! I got this error after throwing out a 386/387 mainboard and putting in a Pentium 133/PCI, then recompiling the kernel with the new processor type and PCI bios support. Now Lilo doesn't want to install the new kernel, grr-grr! The old one was already over 700 KB and the new one is <90