> I built a new version of the kernel under RH6.2, currently running
> 2.2.14-5.0smp. The new version is 2.2.17. Compilation and building of the
> required modules succeeded. lilo.conf has also been updated to reflect the ne
> w
> kernel name. System.map, initrd.x.img, vmlinuz and vmlinux
"GYGAX,OTTO (HP-Corvallis,ex1)" wrote:
> I built a new version of the kernel under RH6.2, currently running
> 2.2.14-5.0smp. The new version is 2.2.17. Compilation and building of the
> required modules succeeded. lilo.conf has also been updated to reflect the new
> kernel name. System.map, initr
On Wed, 20 Sep 2000, EXT GYGAX,OTTO (HP-Corvallis,ex1) wrote:
> I built a new version of the kernel under RH6.2, currently running
> 2.2.14-5.0smp. The new version is 2.2.17. Compilation and building of the
> required modules succeeded. lilo.conf has also been updated to reflect the new
You shou
As a first guess, I would imagine that A: you accidentally overwrote
your original kernel, and B, while you did change lilo.conf, you didnt
rerun lilo to write teh changes to the MBR, causing LILO to look for a
kernel image that isnt there.
that or you just didnt quite get lilo configured right.
DO you compile the tar.gz kernel or updated from RPM packages??
If tar.gz ..i think you should take the same configuration as 2.2.14-5smp(rpm)
kernel configuration in the kernel source (/usr/src/linux/config) ..then check if
you want to enable anything in the new 2.2.17 kernel and recompile back
I built a new version of the kernel under RH6.2, currently running
2.2.14-5.0smp. The new version is 2.2.17. Compilation and building of the
required modules succeeded. lilo.conf has also been updated to reflect the new
kernel name. System.map, initrd.x.img, vmlinuz and vmlinux have all been place
