Well, I found something interesting ... The kernel starts when I add quiet=n break=mount arguments to the boot command line in grub. Then, I hit Ctrl+D and it boots right. It works for 2.6.19 and 2.6.20.
If I remove quiet=n or break=mount, it just breaks like before. I think there is an issue with a device that need more time to start. I haven't investigated further, but if you need some precise informations about what's going on, I can get them with some directions. -- no devices found for /dev/md0 at startup https://launchpad.net/bugs/73952 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
