Comment 8 for bug 518826

On my system, I hates ta' tell you this, but none. I set up arch on "/" and a "/home" partitions (sda9 and sda8) using a common swap partition I use for both ubuntu karmic and my test partition holding lucid.

As the arch partition is more for learning its system and experimenting with different desktop environments, I purposefully set it up without a separate /boot partition OR a boot loader, relying on my primary grub setup with Ubuntu.

I have seen other reports of users with arch in the forums having the same issue, with the work around being to manually configure grub.cfg with the statement: initrd /boot/kernel26.img on the line following the main arch menu entry.

For the specific purpose of using Lucid to test the latest grub2, it currently manages the other systems at this point, though Karmic does have a boot manager set up (grub 2 same version as lucid's) as a fallback in case there are problems with the lucid beta. (but being the same version of grub2, it also has the same exact issue with the Arch install.)

If you need anything, just let me know and I'll gladly help as I can.