Somebody in the thread at some point said:
> On Sat, Jul 21, 2007 at 10:29:07AM +0100, Andy Green wrote:
>> Somebody in the thread at some point said:
>>> Installing: kernel ####################### [25/71]
>>> grubby fatal error: unable to find a suitable template
>> What is in your /boot/grub/grub.conf at the moment?
>>
>> You might also try copying that file to, eg, /tmp/grub.conf and running
>> grubby by hand with a test like
>>
>> export KERNVER=2.6.1234 ; grubby --config-file /tmp/grub.conf
>> --add-kernel /boot/vmlinuz-$KERNVER --initrd=/boot/initrd-$KERNVER.img
>> --title $KERNVER --set-default=/boot/vmlinuz-$KERNVER --copy-default
>>
>> This works as expected here and makes a fake entry at the top of
>> /tmp/grub.conf. Does it create the template error for you?
>>
>
> Yep - same error.
>
> grub.conf looks like this -
I can reproduce it with your grub.conf... but... I can also reproduce it
if I change my working grub.conf so that the file named in the kernel
line doesn't exist. Eg
kernel /vmlinuz-2.6.22-rc7 ro root=LABEL=/
works okay, but if I deliberately change it
kernel /vmlinuz-2.6.22-rc7x ro root=LABEL=/
then I get your error. The difference is that /boot/vmlinuz-2.6.22-rc7
exists and the ..rc7x file doesn't.
straceing grubby with the ..rc7x bogus edit shows...
access("/boot/vmlinuz-2.6.22-rc7x", R_OK) = -1 ENOENT (No such file or
directory)
access("/boot/vmlinuz-2.6.22-rc7x", R_OK) = -1 ENOENT (No such file or
directory)
write(2, "grubby fatal error: unable to fi"..., 55grubby fatal error:
unable to find a suitable template
) = 55
Therefore... does /boot/vmlinuz-2.6.21-1.3194.fc7 exist on your box?
-Andy
