lilo wrong kernel [solved] by using Grub2, so not really
Posted: 5. Aug 2012, 20:13
I have current installed in one partition alongside two other 13.37 Salixes. I am using the latest lilo, as available from source or in the current repo. When I run lilo -v from current, the 13.37 Salixes are set to boot from the current kernel, which of course isn't there, so nothing works. If I call lilo from 13.37, current tries to boot with 2.6.37.6, ditto. So at the moment if I want to switch between current and 13.37, I have to run lilo after booting into the other version, and then reboot.
I have tried editing lilo.conf to specify the right kernel (rather than just vmlinuz), but no luck.
This is all the more puzzling because I previously had Slitaz in the guest partition, and it had a 3 series kernel - no such problem. I may have been using the older lilo at that point, but I had to upgrade it from source when I upgraded the kernel in one of my Salixes. Again, there was no difficulty about correctly assigning the correct kernel to each install - it was just that the lilo in the 13.37 repos can't cope with some kernels because of a bug.
I'm posting here rather than to the mailing list because on balance, this looks like a problem I am having with lilo rather than anything to do with current.
I have tried editing lilo.conf to specify the right kernel (rather than just vmlinuz), but no luck.
This is all the more puzzling because I previously had Slitaz in the guest partition, and it had a 3 series kernel - no such problem. I may have been using the older lilo at that point, but I had to upgrade it from source when I upgraded the kernel in one of my Salixes. Again, there was no difficulty about correctly assigning the correct kernel to each install - it was just that the lilo in the 13.37 repos can't cope with some kernels because of a bug.
I'm posting here rather than to the mailing list because on balance, this looks like a problem I am having with lilo rather than anything to do with current.