Elie De Brauwer wrote:
I just followed the newbie guide, and to me it looked like lilo was run by the dpkg -i process as it asked me several questions about LILO. I googled on this problem and found someone else suggesting that LILO must be run, so I did lilo -v -v -v and then rebooted. Same problem unfortunately.Did you run lilo after you copied the kernel ? Didn't it give any errors ?
I guess I'm not completely sure how to do that. Not being familiar with lilo.conf I'm not sure what a new entry would look like. From looking at yours it seems one can be labeled default and the others can just be added as additional images. Is this right? I notice in my /boot directory that I have vmlinuz-2.4.18 but that in my lilo.conf I have image=/vmlinuz and that's all. That seems to me like the wrong directory and the wrong filename. Am I right?It is advisable NOT to overwrite your old kernel until you are 100% sure your new kernel works, just give it a different name and add a new entry in your lilo.conf.
My first guess at your problem is that you simly overwrote your old kernel and did not run lilo afterwards. I added an example of my lilo.conf i personally don't ever delete any of my old kernels, i just leave the there for testing etc etc etcboot=/dev/hda root=/dev/hda2 install=/boot/boot-menu.b map=/boot/map prompt delay=100 timeout=100 default=Linux-2.4.20-1 image=/boot/vmlinuz-2.4.19-fb label=LInux-2.4.19-fb vga=794 read-only image=/boot/vmlinuz-2.4.19 label=Linux-2.4.19 read-only image=/boot/vmlinuz-2.4.18-bf2.4 label=Linux-2.4.18 read-only image=/boot/vmlinuz-2.4.20 label=Linux-2.4.20 read-only image=/boot/vmlinuz-2.4.20-1 label=Linux-2.4.20-1 read-only hth- -- Homepage: http://www.de-brauwer.beBSD is for Unix lover Linux is for windows haters,I run Linux -----BEGIN PGP SIGNATURE-----Version: GnuPG v1.2.2 (GNU/Linux) iD8DBQE+1N4upSQix3Sc+ZgRAqcdAKCc82UZ8tpMuKmkV5qfyAJNb4FvjwCeOcej pkb/tvrPp8nLHpO7oG75tuc= =zI6k -----END PGP SIGNATURE-----