On Mon, Mar 2, 2015 at 2:00 AM, Fernando Rodriguez <frodriguez.develo...@outlook.com> wrote: > On Saturday, February 28, 2015 12:50:37 PM Tom H wrote: >> On Fri, Feb 27, 2015 at 5:47 PM, Fernando Rodriguez >> <frodriguez.develo...@outlook.com> wrote: >>> >>> Efibootmgr is not a boot manager, it's an utility to interface with the EFI >>> firmware on the motherboard and you don't need to hardcode the command line > on >>> the kernel, look at the -u option of efibootmgr. You can even load an > initrd >>> with it by specifying the efi_memmap boot option. I use something like this > (it >>> shoulld work with any firmware because Windows uses it): >>> >>> efibootmgr -p 2 -c -b 0001 -l "\EFI\Linux\vmlinuz.efi" -L "Gentoo Linux" -u >>> "root=/dev/sda2 resume=/dev/sda3 quiet splash efi_memmap >>> initrd=/EFI/Linux/initramfs.img" >> >> Interesting. I must be over-complicating things because I use the >> following when I want to use the EFI stub without gummiboot: >> >> # cat /boot/efi/efi-extra.txt \ >> | iconv -f ascii -t ucs2 \ >> | efibootmgr -b 0000 -c -L 3.19.0 -l vmlinuz-3.19.0 -u -@ - >> >> where >> >> # cat /boot/efi/efi-extra.txt >> initrd=initrd.img-3.19.0 >> root=UUID=b51ee688-137c-47ec-9635-b69434b4e1f8 ro >> init=/lib/systemd/systemd > > It's a good idea to do that as it's less error prone. I don't know if you need > iconv in the pipeline but if you put the arguments on the command line it's > not needed. I just called my kernel vmlinuz.efi so I don't need to do that > everytime I update it and use grub if I need to boot an alternate kernel or > boot with different options.
Thanks. Next time that I feel adventurous, I'll replace my gummiboot nvram entry with a vmlinuz one without cat and iconv. I made big changes after the last efi boot thread on this list so I'll wait a bit. :)
