Bug 830573

Just for the completeness: a quite ancient System Rescue CD version 1.2.0 with kernel 2.6.29 boots just fine.

Matthew?

I'm having this same issue on my Asus UX31, trying to get dual boot Win7 / Fedora 17 running. I booted the install dvd in EFI mode, pointed Fedora to the existing EFI partition, and continued the install as usual. 

My BIOS now has two boot options in the list: Win7 bootmanager & Fedora bootmanager (Grub2 isn't mentioned anywhere). If I select the Win7 as first option, the thing boots properly. If I select the Fedora as first option, I get the error we're discussing here: "Trying to allocate ...". 

I'm assuming I somehow added Fedora EFI boot stuff onto the existing EFI boot partition, instead of getting a clean install (since the Win7 is still booting).

Also for me the issue is appearing if I try to boot the live versions, I tried the USB 17 just as a test.

Any tips on how to fix this boot / install Fedora 17 (next to Win7) cleanly?

(In reply to comment #3)
> I'm having this same issue on my Asus UX31, trying to get dual boot Win7 /
> Fedora 17 running. I booted the install dvd in EFI mode, pointed Fedora to
> the existing EFI partition, and continued the install as usual. 
> 
> My BIOS now has two boot options in the list: Win7 bootmanager & Fedora
> bootmanager (Grub2 isn't mentioned anywhere). If I select the Win7 as first
> option, the thing boots properly. If I select the Fedora as first option, I
> get the error we're discussing here: "Trying to allocate ...". 
> 
> I'm assuming I somehow added Fedora EFI boot stuff onto the existing EFI
> boot partition, instead of getting a clean install (since the Win7 is still
> booting).
> 
> Also for me the issue is appearing if I try to boot the live versions, I
> tried the USB 17 just as a test.
> 
> Any tips on how to fix this boot / install Fedora 17 (next to Win7) cleanly?

Additional info:

I can boot into F17 using rescatux bootusb (latest, 0,30b6), I'm posting this from inside :). Anyway, this is not a solution, but at least it takes the urgency away - somewhat. 

And yes, the rescatux boot menu showed only the F17 entry, no entry for Win7.

Feel free to ask for logs etc., I'd happily provide, but I can't guess what you need to be able to help me.

Matthew, Josh: if you had any tip for a workaround that would enable me to boot and install F17 on that machines, it would help a lot (a kernel option, maybe? I tried "noefi" with no success).

Sara: I'm not sure if this the same bug. I was unable to boot the installation media.

Milos, for installing, I used the dvd. I also had trouble getting the install/live media to boot. On top of that you need to boot them in UEFI mode for the install to succeed (if you boot them in BIOS mode, you'll get an error at partitioning about the lack of a bios-boot partition).

I can boot the F17 install dvd from an external dvd-drive, that I know. Did you try booting from the install dvd? 
I also just tried F17 live image from a USB key again, I can boot it, but not in EFI mode. I don't know about live image on cd, I don't have one lying around.


For booting the installed distro, now that is really proving difficult. I finally managed to get some serious live in it (as in booting without external attached drives/usb keys/...) by, horror, using a ubuntu live distribution from usb. That way I could chroot into my install F17 distro, and install grub2-efi. In fact the entire package was missing from the install, I had to add it. I have no clue how it could happen that this was not installed from the beginning. I did choose to install it, and I did see the install finish cleanly up until the 'Congratulations' screen. 

In any case, I now have a working grub2 on my efi partition, and I can boot everything manually. As in:

set root=(hd0,gpt5)
linux /boot/vmlinuz-... (tab autocompletes)
initrd /boot/init... (tab autocompletes)
boot

All that I have left to do is figure out where to put my config file, or how to tell grub2 where it is. Clearly the thing is not finding it now. Any tips?

It was too easy; the config files had to be in /boot/grub2, and they ended up in /boot/grub.

I'm booting F17 cleanly now. The Windows entry in grub2 is still reporting 'invalid efi path', but that's a problem for another day.

Sara, I'm really not sure whether this is the same issue. I was unable to boot even from the F17 DVD. I tried back with no luck until F13. Hence I installed F13 and preupgraded to F15 and then to F17. Quite a cumbersome way, but now everything works and boots just fine (I didn't have to touch any configuration after the upgrades).

Unfortunately there is no way for us to respin the F17 media, so there is nothing that can be done against this bug. If you could possibly test the F18 alpha and beta spins, that would be a tremendous help. If the issue still occurs please open a new bug against F18

Justin: this is just to confirm that I have tried Fedora 18 Alpha KDE x86_64 Live CD, and it boots fine.