Thanks a lot. So, we have pretty much finish the bisect but the faulty commit (10feec8db921f3cd754f0f496e2fbf43763b1ccb) doesn't seem to contain anything particularly suspicious. I'll need to spend a little bit more time looking at that, but at this point there are two possibilities:
1) The problem is somewhere else (grub? initrd generation?) 2) I may have done something wrong during the bisect I'll take a closer look at all this, and come back to you later. In the meantime, can I ask you to validate your grub configuration? From previous comments, it looks like you're pretty comfortable with grub, so you could for example try to manually boot a (failing) kernel using the grub shell. Have you tried this before? Oh, and just in case: could you also make sure you have a corresponding initrd file for each of these kernels (i.e., for each /boot/vmlinuz-* you need a corresponding initrd.img-*)? About you're comments on the installation: those messages seem to be correct. There are links in / that link to the latest kernel image and to the latest initrd (just run "ls -l /" and you'll see them). Since you've been installing the same version of the kernel several times (the test kernels were all slightly different kernels but with the same version), these links don't actually get updated as they are already pointing to the correct kernel. And you're right: when you install a new kernel, grub-update is executed at the end. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1013647 Title: no boot at kernel load 3.2.0-25-generic To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1013647/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
