| 1 |
On Saturday, February 28, 2015 12:50:37 PM Tom H wrote: |
| 2 |
> On Fri, Feb 27, 2015 at 5:47 PM, Fernando Rodriguez |
| 3 |
> <frodriguez.developer@×××××××.com> wrote: |
| 4 |
> > |
| 5 |
> > Efibootmgr is not a boot manager, it's an utility to interface with the EFI |
| 6 |
> > firmware on the motherboard and you don't need to hardcode the command line |
| 7 |
on |
| 8 |
> > the kernel, look at the -u option of efibootmgr. You can even load an |
| 9 |
initrd |
| 10 |
> > with it by specifying the efi_memmap boot option. I use something like this |
| 11 |
(it |
| 12 |
> > shoulld work with any firmware because Windows uses it): |
| 13 |
> > |
| 14 |
> > efibootmgr -p 2 -c -b 0001 -l "\EFI\Linux\vmlinuz.efi" -L "Gentoo Linux" -u |
| 15 |
> > "root=/dev/sda2 resume=/dev/sda3 quiet splash efi_memmap |
| 16 |
> > initrd=/EFI/Linux/initramfs.img" |
| 17 |
> |
| 18 |
> Interesting. I must be over-complicating things because I use the |
| 19 |
> following when I want to use the EFI stub without gummiboot: |
| 20 |
> |
| 21 |
> # cat /boot/efi/efi-extra.txt \ |
| 22 |
> | iconv -f ascii -t ucs2 \ |
| 23 |
> | efibootmgr -b 0000 -c -L 3.19.0 -l vmlinuz-3.19.0 -u -@ - |
| 24 |
> |
| 25 |
> where |
| 26 |
> |
| 27 |
> # cat /boot/efi/efi-extra.txt |
| 28 |
> initrd=initrd.img-3.19.0 |
| 29 |
> root=UUID=b51ee688-137c-47ec-9635-b69434b4e1f8 ro |
| 30 |
> init=/lib/systemd/systemd |
| 31 |
> |
| 32 |
|
| 33 |
It's a good idea to do that as it's less error prone. I don't know if you need |
| 34 |
iconv in the pipeline but if you put the arguments on the command line it's |
| 35 |
not needed. I just called my kernel vmlinuz.efi so I don't need to do that |
| 36 |
everytime I update it and use grub if I need to boot an alternate kernel or |
| 37 |
boot with different options. |
| 38 |
|
| 39 |
-- |
| 40 |
Fernando Rodriguez |
Archives