Ask Your Question

Yet another Fedora20/Win8 dualboot issue

asked 2014-08-24 21:49:08 -0500

Octavarium gravatar image

updated 2014-08-25 18:12:50 -0500

Hello there!

I looked around a little bit but only found one related thread, which solution I already tried.

So here it is : I bought a new laptop with windows 8.1 included, and wanted to do, well, as the title said.
- shrank win partition,
- created a live usb using live USB creator,
- disabled secureboot (got invalid signature error otherwise when trying to boot from usb, maybe that's my problem),
- booted from usb > installed Fedora without issue > rebooted… only to get to UEFI menu.

So now I can neither launch Fedora nor Win, can't even access Grub, and on the boot tab of uefi menu, no boot options are available, I only get the choice to delete the non-existing ones.

I can still boot from usb, which I did to install Fedora a second time, but nothing changed.

I also made a new live usb using a macbook following the wiki tutorial, still didn't work.

Any other way than trying to install it over and over again? Do you think I will have to reinstall windows once Fedora will be operational (it shouldn't have touched the win partition, if I'm not mistaken)?

Thanks in advance.

EDIT : Well, I ended up removing Fedora and reinstalling Windows, but I still can't manage to boot anything else than a live usb.
Guess I messed something up in my uefi partition at some point. There's a "repair startup" tool in windows troubleshooting options, but it didn't find anything wrong. I'll look around to find a way to restore it.

edit retag flag offensive close merge delete


  • First of all, the secure boot violation shouldn't happen. But, hey, it happened to me too! And my UEFI dual boot with Win8 works just fine.
  • Second of all, can you go into the UEFI (BIOS) Boot menu (not GRUB) and boot into Windows? In my case, I had to use a DVD to install Fedora.
    • What sort of partitioning did you choose? Did you let Fedora do the partitioning for you? Or did you do them yourself?
    • Do you have an install disk of Windows?
    • What is the error when you try to access GRUB?
abadrinath gravatar imageabadrinath ( 2014-08-24 22:49:08 -0500 )edit
  • Alright, that's reassuring.
  • Not at all, as I said, UEFI gives me no boot options. I am stuck in a "boot > uefi > reboot >uefi…" loop.

    • At first, I wanted to do my own, but I noticed that the default Fedora partitioning was what I was aiming at, so I went with that.
    • Unfortunately not, manufacturers don't seem to bother providing them anymore, but if I have to reinstall win, I think I could manage to borrow one.
    • Same as above, I don't even have the chance to see any Grub-related material. Nobody would ever guess that there actually is an OS on this laptop, let alone two.

So you recommend a DVD instal?

Octavarium gravatar imageOctavarium ( 2014-08-25 04:17:32 -0500 )edit

Hi, try Lili , Maintains a constant development.

davidva gravatar imagedavidva ( 2014-08-25 04:27:30 -0500 )edit

Thanks, will do, I'll give it a try right now. Even if I guess that's not the issue here, as I already tried several usb created with different means, always got the same result. But I'll definitely use it for future installs.

Octavarium gravatar imageOctavarium ( 2014-08-25 04:36:49 -0500 )edit

@Octavarium - during the install, are there any errors reported? Is the fedora installation present and accessible from a live image? If you can get to those files, please put the files from /var/log/anaconda/ into so we can have a less anecdotal view of the problem.

randomuser gravatar imagerandomuser ( 2014-08-25 22:49:10 -0500 )edit

1 Answer

Sort by » oldest newest most voted

answered 2014-08-26 13:53:56 -0500

updated 2014-08-26 14:05:35 -0500

A couple things from your log stand out. You have lines like this:

  • bootloader GRUB2 on X86 platform
  • bootloader stage1 target device is sda
  • Création de biosboot sur /dev/sda6 ( The BIOSBOOT partition is used for BIOS installs on GPT drives.)

Compare to my EFI system:

  • bootloader EFIGRUB on EFI platform
  • bootloader stage1 target device is sdb1 (sdb1 is my EFI system partition)

It looks like you turned on BIOS mode in your firmware. This would explain why Fedora isn't in the firmware menu - it wasn't booted in UEFI mode. It also explains why Windows isn't showing in the boot menu - windows boots via UEFI, and you turned that off.

There is another possiblity - on many systems, removable media will have two entries in the firmware boot menu, something like:

Generic Mass Storage USB Device
UEFI: Generic Mass Storage Device

You could have chosen the non-UEFI one to cause Fedora to boot in BIOS mode, then directed the installer to reformat the existing EFI partition, thus removing the Windows bootloader data. would show if that happened.

edit flag offensive delete link more


Alright, thanks a lot for your help so far.
So first of all, here are anaconda.program.log, and I have trouble pasting the rest (data restriction?), will edit post later.
As for the stick, I created it using the dd command, so it should be fine on this end.
And if I remeber correctly, you are right on your second assumption (guess you'll see it in the log) I booted on the via non-UEFI to avoid secureboot issues. But I'm quite certain I made sure not to touch the EFI partition.
So all I have to do is to install again using the UEFI boot?

EDIT : So, I tried booting with UEFI, and came with another problem.
I dug around a little bit and found this thread which pretty much described my situation, if not for the fact that the error comes up when booting from a ...(more)

Octavarium gravatar imageOctavarium ( 2014-08-26 16:52:15 -0500 )edit

Yeah, that log shows a BIOS install. 'basic graphics mode' iirc passes 'nomodeset' or similar to the kernel - after you install, yum update your system and try removing that before selecting the latest kernel in the GRUB menu. If it works, there are instructions around for recreating /boot/efi/EFI/fedora/grub.cfg. If not, you can get the nvidia binary drivers from - and again, you'll want to recreate your grub.cfg without nomodeset. I'm not sure what to say about the Windows installation, I'm guessing you reinstalled that in BIOS mode too?

randomuser gravatar imagerandomuser ( 2014-08-26 19:20:14 -0500 )edit

Alternatively, if you did install both Windows and Fedora in BIOS mode, you could tell the system to boot from the drives instead of the UEFI entries and move on. There are advantages to investing a little time to get the UEFI setup, but it's your call.

randomuser gravatar imagerandomuser ( 2014-08-26 19:21:54 -0500 )edit

Whew, took me quite some time, but I guess I'm pretty close to what i wanted in the first place.
So, I reinstalled Fedora & Win with UEFI, and they're now both here as UEFI boot options, both operational. Win is not showing in Grub, but for what I saw, it's a pretty common issue, so I'll deal with it later. Now the only thing left to do is removing nomodeset, which I haven't achieved yet.
After running yum update, I edited /etc/default/grub to remove nomodeset and ran grub2-mkconfig -o /boot/efi/EFI/fedora/grub.cfg and rebooted, but it didn't work (boot stuck at fedora logo). So I followed this, once again updated grub.cfg, but still got stuck at fedora logo (should I give the nonfree drivers a try?).
Anyway, what I really needed was to fix my mistake, and it ...(more)

Octavarium gravatar imageOctavarium ( 2014-08-27 01:45:53 -0500 )edit

@Octavarium - you did give the nonfree drivers a try, that's what you linked to. Anyway, glad you got it working. Look around for other questions as you work out the details, and feel free to @'tag' me if you think I can help.

randomuser gravatar imagerandomuser ( 2014-08-27 08:34:08 -0500 )edit

Question Tools

1 follower


Asked: 2014-08-24 21:49:08 -0500

Seen: 594 times

Last updated: Aug 26 '14