[SOLVED] Boot Loader Problem on Slackware64 13.37 (UEFI & GPT disk)
SlackwareThis Forum is for the discussion of Slackware Linux.
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Introduction to Linux - A Hands on Guide
This guide was created as an overview of the Linux Operating System, geared toward new users as an exploration tour and getting started guide, with exercises at the end of each chapter.
For more advanced trainees it can be a desktop reference, and a collection of the base knowledge needed to proceed with system and network administration. This book contains many real life examples derived from the author's experience as a Linux system and network administrator, trainer and consultant. They hope these examples will help you to get a better understanding of the Linux system and that you feel encouraged to try out things on your own.
Click Here to receive this Complete Guide absolutely free.
Yes, I found: git://people.freedesktop.org/~kay/gummiboot
I will check it out later this evening.
Excerpt from README;
Simple UEFI boot loader which executes configured EFI images, where the
default entry is selected by a configured pattern (glob) or an on-screen
Operates on the EFI System Partition (ESP) only. Configuration file fragments,
kernels, initrds, other EFI images need to reside on the EFS. Linux kernels
need to be built with CONFIG_EFI_STUB to be able to be directly executed as
an EFI image.
Reads simple and entirely generic boot loader configurion files; one
file per boot loader entry to select from.
Pressing the space (or most other) keys during bootup will show
an on-screen menu with all configured loader entries to select from.
Pressing enter on the selected entry loads and starts the EFI image.
If no timeout is configured and no key pressed during bootup, the default
entry is booted right away.
The config files should be named like:
$ cat /boot/loader/entries/fedora-3.5.4-1.fc18.x86_64.conf
title Fedora 18 (3.5.4-1.fc17.x86_64)
$ cat /boot/loader/entries/custom-kernel.conf
title My test Kernel - without initramfs
$ cat /boot/loader/entries/redhat-grub.conf
$ cat /boot/loader/entries/zzz-efi-shell.conf
title EFI Shell
Paths are automatically converted from '/' to '\', and a leading '\' is
added if needed.
Loader options can be stored in:
$ cat /boot/loader/loader.conf
The timeout is specified in seconds, the default is 0, which suppresses the
menu. If a timeout is given, in the config file or in the EFI variable
"LoaderConfigTimeout", the on-screen menu with the default entry selected is
shown, and a timer counting downwards.
Pressing the '+' or '-' key in the menu will set or clear a custom timeout
value. The setting is stored persistently in the EFI variable "LoaderConfigTimeout".
The default entry is selected by a pattern match on the configuration file
names. The matched strings are basenames of the config files translated to
lowercase and without the ".conf" suffix. The last matching entry in the
sorted list is selected. If no match pattern is specified, the last entry in
the list is selected.
This will automatically select the latest Fedora kernel entry:
This will automatically select the latest Fedora 18 kernel:
Pressing the 'd' key in the menu will mark the selected entry as the default
boot entry. The entry is identified by a leading '*'. Pressing the 'd' key again
will clear the setting. The setting is stored persistently in the EFI variable
The EFI variable LoaderEntryOneShot= can be used to specify a loader entry
for the next and only the next reboot. The variable will always be cleared
directly after it is read.
Before executing the selected image, the boot entry indentifier is stored in
the EFI variable "LoaderEntrySelected" and available during runtime at:
The allocated random UUID 4a67b082-0a4c-41cf-b6c7-440b29bb8c4f is meant to be
shared across tools which implement the config file layout, format, and the EFI
Last edited by onebuck; 06-25-2012 at 07:33 PM.