Grischa Schuering wrote:
I tried to build my own 2.4.18 kernel with make-kpkg --make-menuconfig
--revision=2.4.18-fwipsec.1.0 kernel_image.
Everything seemed fine so far, but when installing the kernel image (ln -s
/boot/vmlinuz.new vmlinuz), lilo, and restarting, the kernel is tried to be
loaded by lilo but then suddenly resets the machine (after the points are being
displayed).
What could be th prob?
Is ist that the kernel I build is not worling properly or
does it have to do anything with my old kernel set up by initrd (what is it
anyway)?
Any ideas ?
This just happened to me and it turned that there were many choices of
architecture and I had chosen (or not noticed that I had chosen) a different
flavor of x86. That was exactly my symptom. Recheck your menuconfig carefully.
BTW: How do I tell Lilo to let me choose e.g. by a boot menu which kernelimage
to boot from?
Here is the part of my /etc/lilo.conf that does that:
# Boot up Linux by default.
#
default=Linux-2.4.18
image=/vmlinuz
label=Linux-2.4.18
read-only
# restricted
# alias=1
image=/vmlinuz-old
label=LinuxOld
read-only
HTH,
Paul Scott
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
