If this is your first visit, be sure to
check out the FAQ by clicking the
link above. You may have to register
before you can post: click the register link above to proceed. To start viewing messages,
select the forum that you want to visit from the selection below.

randomizer: it may relate to theming. grub2 seems considerably slower to render when themed on some hardware, compared to when un-themed.

The theme is really nothing but a purple background. I would hope that this wouldn't be too taxing on the system

This has me wondering what precisely we are all referring to when talking about how long it takes to render. Are we talking about the time between when the bootloader screen first appears until it has fully rendered or the time between a completed POST sequence and when it has fully rendered? The delay I'm referring to is mostly between the end of the POST and when the bootloader menu first appears, which is a couple of seconds. This delay is much shorter with other distros.

You can still multiboot if your motherboard allows you to have a boot menu (probably does). You just create more entries to it.

Yeah, both my ThinkPads have a crappy boot manager menu, which basically just lists whatever it sees in Bootnnnn NVRAM variables. Right now, my one-and-only entry, called "ubuntu," points to \EFI\ubuntu\grubx64.efi. EFI boot appears to allow me to skip the irrelevant GRUB stuff and directly boot-load the kernel. Just need to spend a couple hours learning how to stitch it all together.

instead of root=/dev/sda2 you could use in the case you have got gpt this:

Code:

echo root=PARTUUID=$(blkid -p -s PART_ENTRY_UUID -o value /dev/root)

Thats usually not needed for only 1 internal hd, but would not hurt of course. A partuuid is the id of the partition and NOT the id of the filesystem, this is not supported without initrd. It is possible to boot with initrd as well, but i think you wanted to boot with max speed.

instead of root=/dev/sda2 you could use in the case you have got gpt this:

Code:

echo root=PARTUUID=$(blkid -p -s PART_ENTRY_UUID -o value /dev/root)

Thats usually not needed for only 1 internal hd, but would not hurt of course. A partuuid is the id of the partition and NOT the id of the filesystem, this is not supported without initrd. It is possible to boot with initrd as well, but i think you wanted to boot with max speed.

You dont need to embed that, it can be read from the filesystem. You only have to be sure that your hd can be mounted without extra drivers - thats default for ubuntu kernels when you dont use raid. But in the case you want to boot with initrd, thats a piece of cake as well.

As you see you have to write the path to the initrd relatively to the efi partition, you can add a \ in front, but that is optional. You have to use \ and not / because that's the UEFI syntax. So whats your problem now? Btw you can use the root=UUID=... statement you usually get by

Code:

echo root=UUID=$(blkid -p -s UUID -o value /dev/root)

if you want when you use an initrd as well, thats the uuid of the filesystem - this would even work when you use mbr partitions - the efi fat partition must be a PRIMARY one in that case!

Well you can reuse the ubuntu shim/grub for all purpose Because it allows boot of unsigned kernels. Basically they use both shim to chainload to grub. shim can be configured to allow only a signed binary (when you build it plain it is just a chainloader). Fedora wants to use signed kernels, somewhere are kernel patches to do that, maybe you find the link. With one working shim/grub combination you can boot every system - well it depends how many features ubuntu allows in the signed grub, if chainloader is possible you can start any other efi binary (signed or not) - and even win.