Originally Posted by Dan
Leonard ... I've merged a bunch of your post together. Here's the deal. One thread per subject per customer. Do not open another thread about your grub problem. Keep it here and work it out here.
I am happy to keep it all here. Let me summarize where I am now. Please excuse me if this duplicates a previous posting.
I have installed Fedora 17 on a second disk, /dev/sdb with Windows 7 already installed on /dev/sda. During the Fedora 17 installation I chose to put grub in the first sector of /boot (/devsdb1). I've done this twice now and I am pretty sure I got it right. I get a /boot/grub directory with only a splashscreen file in it. I also get a /boot/grub2 directory with a lot of files in it including a grub.cfg file which is very complex. There is no grub.conf anywhere in sight.
I then booted Windows 7 and started EASY BCD (2.12). It gives me two choices: grub(legacy) and grub2 tor Linux. The first choice allows me to specify the location, which I do as /dev/sdb1. But then on booting Linux I get a screen with the single word GRUB and nothing else happens. If I specify grub2 to EASYBCD, it tells me it will find what it need automatically and doesn't allow me a choice of location. On booting, I get a grub command line interface. (I don't know if this is provided by the Fedora end or whether it is an EASY BCD grub interface.) But I can specify manually a kernel and initrd file and then boot into Fedora 17.
But I can't get it to boot Fedora 17 automatically, as it did in all previous versions of Fedora, up to Fedora 15.
I heard from the author of USB BCD, who suggested a way to automate what I have been doing manually to boot.:
"If you are able to manually key in the correct commands to boot into
Fedora, the easiest option would be to install NeoGrub, then type out
those commands in the NeoGrub configuration file:
That will help. but it is not a complete solution to the problem, unless I can figure out how to write something that will deal with kernel upgrades and or even select a kernel.
He also told me:
"We will look into why automated booting into Fedora 17 does not work,
this is not the first report we have received regarding this issue."
So I think I am not just being stupid. There really seems to be a problem, which I hope will be resolved soon.