On Tue, 30 Nov 2010, Tom H <tomh0665@gmail.com> writes: > So 10_linux isn't the problem. Another script is somehow picking up > 2.6.32... It depends. If 10_linux is expected to find currently running kernel as well, your are right; otherwise, wrong. I thought that the current kernel is somehow automatically added to the list without an intervention from /etc/grub.d scripts. Anyway, there still is a problem. Regards.