1 |
>> I just remembered another step that I missed - I dont have the syntax |
2 |
>> but "efibootmgr" - google for the correct options. |
3 |
> |
4 |
> Yes ;-) |
5 |
> |
6 |
> I do that for days now. What puzzles me: |
7 |
> |
8 |
> I get the entries into EFI: when I boot I see the entries created by |
9 |
> efibootmgr, but when I chose one of the entries pointing to "GRUB2" or |
10 |
> "gentoo" the PC tells me that the disk isn't bootable. |
11 |
> |
12 |
> And I still don't know what is missing. AFAIK that EFI system partition |
13 |
> is allowed to be within the first 2 TB of the disk (easy on my 1 TB |
14 |
> hdd), has to have the boot-flag set (in parted-terms), and must be type |
15 |
> EF02. When EFI doesn't find something bootable on the disk, my |
16 |
> interpretation is that it can't find that partition? |
17 |
|
18 |
Maybe the boot entry in the EFI firmware is wrong. That's what mine |
19 |
looks like: |
20 |
|
21 |
# efibootmgr -v |
22 |
BootCurrent: 0000 |
23 |
Timeout: 2 seconds |
24 |
BootOrder: 0000,0002,0003,0004 |
25 |
Boot0000* grub2 |
26 |
HD(1,800,40000,2693e7bd-d35e-4a39-9bb9-365ee533d690)File(\EFI\grub2\grubx64.efi) |
27 |
Boot0002* Hard Drive BIOS(2,0,00)USB DISK 1100. |
28 |
Boot0003* Network Card BIOS(6,0,00)Realtek PXE B05 D00. |
29 |
Boot0004* Removable Drive BIOS(1,0,00)HTC Android Phone 0000. |