I recently upgraded one of my nameservers that was running 5.2 and a 2.2.12 kernel to 6.1. After installing I went to recompile the kernel to strip out the stuff I didn't need. I then ran linuxconf to install the new kernel. The kernel was made with make dep;make boot(It's monolithic). The size of the compiled kernel was around 400k. Linuxconf refused to install the kernel citing /dev/hda1 as not valid although that is where the current kernel root is. I went to manually install the kernel and lilo kept complaining that the image was too big. The kernel built fine and I've tried several times yet lilo still refuses to install the new kernel. I downloaded a src tarball of 2.2.12 from one of the kernel.org mirrors (I had problems in the past with the source that shipped with an earlier version and thought that my be the issue.) Unfortunatly lilo still refused. I've only upgraded one other box to 6.1 and that was from 6.0 and not 5.2 I plan on taking some time this weekend and recompiling on my personal machine to see if the same problem occurs. At this point I am thinking it is a problem with lilo.
Try doing 'make bzImage' instead of 'make zImage'. ------- Additional Comments From 10/08/99 21:23 ------- As an update it is failing with the same probs at home on a 6.0 to 6.1 upgrade. I haven't tried this on a machine with a fresh install. I will find a machine to try it as well
I will try making the image that way. Would that be causing linuxconf to report that my root partition was invalid? At home it says /dev/sda5 is not valid and at the office it says /dev/hda1
make bzImage worked when I manually set up /etc/lilo.conf and ran lilo. Linuxconf still complained that /dev/sda5 wasn't a valid partition as well as /dev/hda1 on the nameserver machine.
Assigned to dledford
The initial bug is caused by zImage instead of bzImage. The linuxconf issue might be a real bug though - assigning to the owner of linuxconf.
Closing because we don't ship linuxconf anymore.