I don't know how Windows handles UEFI, but from the Debian side it's pretty
Set up your partitions
Use the GPT partition scheme, not MBR.
To boot from a GPT partition with UEFI a dedicated boot partition is mandated,
called the EFI SYSTEM PARTITION (ESP). It is not mandatory, but the most
compatible way is to use a FAT32 partition. A size of 200 MiB should be fine
for most cases.
To register the partition as a ESP, it has to be flagged with the
In contrast to MBR schemes, the boot flag is only used to indicate the ESP,
not the partitions to be able to boot from.
UEFI uses a directory structure
\EFI\<vendor>\<application>.efi to store
UEFI applications. A directory separator is denoted by a backslash, even on
Linux. could be a distribution name, the actual value is not relevant
to the UEFI.
Applications can be system utilities like memory checkers or an UEFI shell. It
can also be an OS loader or the operating system itself. These applications
need to be registered in the UEFI to be able to be launched at boot time.
The Linux kernel version >=3.3 can be loaded directly by the UEFI. The kernel can act as its own loader. This is called EFISTUB. The following kernel configurations are needed.
A kernel with this configuration is currently not in Debian stable, yet. You can either
bake your own kernel or use the one from the experimental tree in that case you can skip the next paragraph.
Note: A boot manager like GRUB is not needed.
Compiling the kernel
If you decide to compile the kernel here are short instructions how to do that. If you run into problems, there is plenty of information available on how to compile a kernel.
Getting the source
git clone git://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux-2.6.git
Check out one particular version
git checkout v3.6
Make the settings that are needed on your system or leave it as it
is if you have nothing to customize. This writes the kernel
configuration to the file
Make sure the settings from the previous paragraph are set. It also
makes sense to select
CONFIG_INPUT_EVBUG=n. Otherwise your logs
will be filled with GiB of junk.
INSTALL_MOD_STRIP=1 make-kpkg --uc --us binary-arch
The packages are created in the parent directory.
dpkg -i linux-image-3.5.0_Custom.deb linux-headers-3.5.0_Custom.deb
mkinitramfs -o /boot/initrd.img-3.6.0-amd64 3.6.0
3.6.0 is the kernel version. It defaults to the running kernel,
which is not a good choice, since you are still running the old
Setting things up
To be able to boot the Linux kernel, it has to be copied to the ESP together
with the initramfs. Given that the ESP is mounted at
NOTE: To ensure compatibility with most systems the extenstion
efi has to
be added to the kernel.
Now the kernel can be registered in the UEFI. We use the tool
echo "root=UUID=3a4287b6-b3a7-4721-da38-acc38a928278 ro rootfstype=ext4 add_efi_memmap initrd=\\EFI\\debian\\initrd.img-3.6.0" |
iconv -f ascii -t ucs2 |
--disk /dev/sda \
--part 4 \
--label "Debian Linux kernel 3.6.0" \
--loader "\\EFI\\debian\\vmlinuz-3.6.0" \
The argument of
--disk is the device where the kernel resides, not the ESP.
--part is the partition number where the kernel resides.
--label is the
entry in the UEFI boot menu.
To see a list of the available entries, just launch
arguments. Syntax to delete a particular entry
efibootmgr -b entry (hex) -B
efibootmgr -b 001a -B
These instructions don't handle the case of a kernel update. The kernel and initramfs are not automatically copied to the ESP.
That's all you need from the Linux side, I don't know what it takes to add