Comment 93 for bug 570765

I hope the following won't be interpreted as an attempt to hijack this thread, but the problem I'm experiencing with multiple-boots and Lucid is not that the GRUB2 menu doesn't display my other OS-loader - it does - but rather that the loader cannot be accessed from it. This on my main (stationary) computer, and on my laptop, both of which are running an AMD x86-64 dual-core processor. The strange thing is that on my laptop, when I click the other OS loader in GRUB (1.98-1ubuntu5), the computer reboots, while on my stationary box, I instead get a black screen with a blinking dash, seemingly waiting for a command. I've checked using GParted, and the non-Ubuntu OS installations are still there, but as noted above, I can't open them. Updating using «sudo update-grub», which I've tried many times, doesn't help - despite the loader in question being registered. I've been experiencing this problem on my laptop ever since Lucid beta 1 was released (the gory details can be found on pp 38 & 39 of the GRUB2 Basics thread (http://ubuntuforums.org/showthread.php?t=1195275&page=38) on the English-language Ubuntu fora, to which I first posted on 23 March), and on my stationary box ever since the release of beta 2....

Henri