| 1 |
On Mon, Mar 2, 2015 at 2:18 AM, German <gentgerman@×××××.com> wrote: |
| 2 |
> |
| 3 |
> On Mon, 2 Mar 2015 02:10:33 -0600 |
| 4 |
> Canek Peláez Valdés <caneko@×××××.com> wrote: |
| 5 |
> |
| 6 |
> > On Mon, Mar 2, 2015 at 2:03 AM, German <gentgerman@×××××.com> wrote: |
| 7 |
> > > |
| 8 |
> > > On Mon, 2 Mar 2015 01:41:19 -0600 |
| 9 |
> > > Canek Peláez Valdés <caneko@×××××.com> wrote: |
| 10 |
> > > |
| 11 |
> > > > On Sun, Mar 1, 2015 at 11:11 PM, German <gentgerman@×××××.com> |
| 12 |
wrote: |
| 13 |
> > > > > |
| 14 |
> > > > > Out of curiosity I looked into my /boot partition and found two |
| 15 |
.efi |
| 16 |
> > > > files. One is /boot/efi/gummiboot/gummibootx64.efi and another is |
| 17 |
> > > > /boot/efi/boot/bootx64.efi. I remember I've created |
| 18 |
> > > > /boot/efi/boot/bootx64.efi during install by copying kernel image |
| 19 |
file |
| 20 |
> > to |
| 21 |
> > > > it and supposedly it was for efibootmng. I think gummiboot has |
| 22 |
created |
| 23 |
> > its |
| 24 |
> > > > own gummibootx64.efi. Is that safe to delete */boot/bootx64.efi? |
| 25 |
Thanks |
| 26 |
> > > > |
| 27 |
> > > > They are the same image; do an md5sum of both, you'll see that they |
| 28 |
have |
| 29 |
> > > > the same checksum. |
| 30 |
> > > > |
| 31 |
> > > > I believe Boot/BOOTX64.EFI is the default location where the "BIOS" |
| 32 |
(or |
| 33 |
> > > > whatever is called in UEFI systems) looks for an image to boot, |
| 34 |
> > > > and gummiboot/gummibootx64.efi is just a copy. I'm not sure, but I |
| 35 |
would |
| 36 |
> > > > not delete it: |
| 37 |
> > > |
| 38 |
> > > gummiboot creates both copies of the file. |
| 39 |
> > > |
| 40 |
> > > Well, no, I have created */boot/bootx64.efi manually and |
| 41 |
> > */gummiboot/gummibootx64.efi was created by gummiboot install. |
| 42 |
> > |
| 43 |
> > In my machines boot/bootx64.efi was created by gummiboot, and it's the |
| 44 |
same |
| 45 |
> > ile as gummiboot/gummibootx64.efi (same checksum). |
| 46 |
> > |
| 47 |
> > What does bootctl says? |
| 48 |
> |
| 49 |
> bootctl: command not found. How to use bootctl? |
| 50 |
|
| 51 |
Sorry, my bad; bootctl comes with systemd. I thought it came with gummiboot. |
| 52 |
|
| 53 |
However, "gummiboot status" shows almost the same information. In my case: |
| 54 |
|
| 55 |
Boot Loader Binaries: |
| 56 |
ESP: /dev/disk/by-partuuid/b4abf4dc-abfc-45c5-b356-30db1e0b15b3 |
| 57 |
File: └─/EFI/gummiboot/gummibootx64.efi (gummiboot 45) |
| 58 |
File: └─/EFI/Boot/BOOTX64.EFI (gummiboot 45) |
| 59 |
|
| 60 |
Boot Loader Entries in EFI Variables: |
| 61 |
Title: UEFI OS |
| 62 |
ID: 0x0001 |
| 63 |
Status: active, boot-order |
| 64 |
Partition: /dev/disk/by-partuuid/b4abf4dc-abfc-45c5-b356-30db1e0b15b3 |
| 65 |
File: └─/EFI/BOOT/BOOTX64.EFI |
| 66 |
|
| 67 |
As you can see, Boot/BOOTX64.EFI is actually gummiboot. |
| 68 |
|
| 69 |
Regards. |
| 70 |
-- |
| 71 |
Canek Peláez Valdés |
| 72 |
Profesor de asignatura, Facultad de Ciencias |
| 73 |
Universidad Nacional Autónoma de México |
Archives