[ALUG] Grub can't find my new kernel, when old kernel works and is in the same directory

[Steve Fosdick]

On Thu, 2009-09-24 at 13:25 +0100, Srdjan Todorovic wrote:
> On 23/09/2009, Steve Fosdick <lists at pelvoux.nildram.co.uk> wrote:
> 
> > Wondering if the installation had silently failed due to running out of
> > space I delete the oldest kernel image which I never use from aptitude
> > and tried installing the 2.6.31 package again whereupon the error went
> > away.
> 
> Do you know if grub version has been updated?

I didn't notice a grub update between the last time grub config would
have been altered by a kernel installation and the first attempt at
2.6.31.

> > I still don't know if the disk space idea was correct or whether there
> > is some other problem, for example a limit to the number of menu entries
> > etc. or something else that re-installing the package fixed.
> 
> Did you try booting using grub command line rather than the menu?

No, I tried an older kernel that was still in the menu and that worked
fine.

> I've 'fixed' the problem by installing grub2 (which is still beta
> apparently), and spending a while converting the syntax to the new
> format. This seems to work, but I'm not sure what the original problem
> was (which irritates me for not knowing).

For me the problem happenned with grub2.

> The grub developers didn't really want to help unless I was running
> grub2 so perhaps this is a grub-legacy bug...
> 
> Regards,
> Srdjan
> 
> _______________________________________________
> main at lists.alug.org.uk
> http://www.alug.org.uk/
> http://lists.alug.org.uk/mailman/listinfo/main
> Unsubscribe?  See message headers or the web site above!
>