Take the 2-minute tour ×

My intent in a very near future is to set up a dual boot system with Windows 8 and Debian Linux (for testing purposes) on a Lenovo Ideapad 205, that has UEFI BIOS.

I saw several articles about the new Windows 8 features regarding faster boot on UEFI and this may cause a sort of incompatibility with GRUB and, in general, Linux distributions.

How much is it true? In other words, could I expect some problems when installing those OSs in the following order?

  1. Install Windows 8 on a first partition, like 50% of the HDD size.
  2. Then install Debian with GRUB2 in another partition set, at this point GRUB2 should replace the default Windows MBR.
share|improve this question
Please edit your question to include links to those articles you read. –  Moab Sep 6 '12 at 17:16
You don't need grub when you have UEFI. UEFI is capable of selecting the OS loader on its own. Information about how to set up Debian on UEFI –  Marco Sep 6 '12 at 17:32
Here is a detailed guide for installing Debian on a PC with UEFI Secure-Boot Windows 8 pre-Installed. –  user187428 Jan 12 '13 at 11:46
add comment

2 Answers

up vote 3 down vote accepted

Since you said near future the question probably doesn't apply anymore, but I want to answer it to clarify the situation in case some people have the same doubt as you.

You shouldn't have any problems for that setup, whether the laptop was already bought with Windows 8 or not.

What you read about incompatibilities is probably related to a security feature of UEFI called Secure Boot which requires bootloaders (ideally anything accessing hardware directly) to be digitally signed so they can be verified, which among other things prevents malware targeting boot loaders or man-in-the-middle attacks when booting over the network.

For the Windows 8 certification (for new machines), Microsoft requires that feature to be implemented and enabled by default; so unsigned or compromised bootloaders wouldn't be able to boot by default. But, Microsoft also requires that the user should be able to disable that feature altogether if he want to (if the machine doesn't have an ARM processor), with it disabled everything would work as usual.

Anyway, many systems with UEFI that didn't ship with Windows 8 don't even implement Secure Boot, so it's even less hassle.

The problem may be when you want to have Secure Boot enabled but also compile your own bootloader or kernel. In that case all that's you'd need to sign them (maybe only the bootloader) and add the public key to the UEFI storage so that anything signed with your private key would be verified as secure, but you'd have to buy the key to sign it.

Regarding what you say about Windows 8 booting faster, it won't cause any problem in that setup either. It's something they called hybrid boot which uses hibernation to cache most of the core system instead of a traditional boot sequence; but it happens in any kind of system not only UEFI based ones (remember that Windows 8 works in BIOS based systems as well).

In any case if that gives you any kind of problem it can be disabled too and the traditional startup is still available.

I hope that clarifies things.

share|improve this answer
add comment

There should be no problems at all if the computer did not originally come with Windows 8 installed (if you are indeed "installing" 8 on a primary partition yourself).

If your plan is to buy a UEFI computer that comes with Windows 8, then things get a little more interesting. however, most Linux distributions have already solved this proble of boot code signing. Ubuntu and Fedora in particular have already found solutions for this and Debian has been discussing it too. I am sure that it will be solved in a couple of months.

share|improve this answer
add comment

Your Answer


