Would you mind expanding how you went about doing that, because I'm kind of confused."
Well, some weeks ago after i update kernel, feisty dont boot, so i made a new entry in grub menu.lst with old (working)initrd (which was .bak), and all new kernel boot but with the old initrd , so it was not kernel fault but initrd fault.
When i update to last kernel, the old initrd did not work (not a surprise), and the error message at boot was about modprobe error, so the only thing i can do without rebuild kernel with modules "in" was to add suspected modules in /etc/initramfs-tools/modules....that's all.
(sorry for my english !)
I'm glad to see that it work for other people.
"
To Trevor Wermund
"@cestulia:
Would you mind expanding how you went about doing that, because I'm kind of confused."
Well, some weeks ago after i update kernel, feisty dont boot, so i made a new entry in grub menu.lst with old (working)initrd (which was .bak), and all new kernel boot but with the old initrd , so it was not kernel fault but initrd fault.
When i update to last kernel, the old initrd did not work (not a surprise), and the error message at boot was about modprobe error, so the only thing i can do without rebuild kernel with modules "in" was to add suspected modules in /etc/initramfs- tools/modules. ...that' s all.
(sorry for my english !)
I'm glad to see that it work for other people.