From: dkwo <dkwo@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: efibootmgr kernel hook does not create entry
Date: Mon, 08 Aug 2022 16:09:23 +0200 [thread overview]
Message-ID: <20220808140923.qnZo2wUr7bqjBc1tr_huSJ-0kHZtPByHarFTBZ86UMw@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-38533@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 5688 bytes --]
New comment by dkwo on void-packages repository
https://github.com/void-linux/void-packages/issues/38533#issuecomment-1208180438
Comment:
For some reason, the entry is created, but not placed in bootorder:
```
$ doas efibootmgr
BootCurrent: 0001
Timeout: 0 seconds
BootOrder: 0001,0017,0018,0019,001A,001B,001C
Boot0001* Void Linux with test kernel HD(1,GPT,4a04d763-6e6c-4f50-a11b-c5d1092ccee5,0x800,0x100000)/File(\vmlinuz-5.18.16_1)6c006f0067006c006500760065006c003d0034002000720064002e006c0075006b0073002e006e0061006d0065003d00380030003900640066003400320037002d0064003700640035002d0034003000380063002d0061003100390035002d003300620065003600650038003600380031003300330033003d006300720079007000740072006f006f007400200072006f006f0074003d002f006400650076002f006d00610070007000650072002f006300720079007000740072006f006f0074002000720064002e006c0075006b0073002e006f007000740069006f006e0073003d006400690073006300610072006400200069006e0069007400720064003d005c0069006e0069007400720061006d00660073002d0035002e00310038002e00310036005f0031002e0069006d006700
Boot0010 Setup FvFile(721c8b66-426c-4e86-8e99-3457c46ab0b9)
Boot0011 Boot Menu FvFile(126a762d-5758-4fca-8531-201a7f57f850)
Boot0012 Diagnostic Splash Screen FvFile(a7d8d9a6-6ab0-4aeb-ad9d-163e59a7a380)
Boot0013 Lenovo Diagnostics FvFile(3f7e615b-0d45-4f80-88dc-26b234958560)
Boot0014 Startup Interrupt Menu FvFile(f46ee6f4-4785-43a3-923d-7f786c3c8479)
Boot0015 Rescue and Recovery FvFile(665d3f60-ad3e-4cad-8e26-db46eee9f1b5)
Boot0016 MEBx Hot Key FvFile(ac6fd56a-3d41-4efd-a1b9-870293811a28)
Boot0017* USB CD VenMsg(bc7838d2-0f82-4d60-8316-c068ee79d25b,86701296aa5a7848b66cd49dd3ba6a55)
Boot0018* USB FDD VenMsg(bc7838d2-0f82-4d60-8316-c068ee79d25b,6ff015a28830b543a8b8641009461e49)
Boot0019* NVMe0 VenMsg(bc7838d2-0f82-4d60-8316-c068ee79d25b,001c199932d94c4eae9aa0b6e98eb8a400)
Boot001A* ATA HDD0 VenMsg(bc7838d2-0f82-4d60-8316-c068ee79d25b,91af625956449f41a7b91f4f892ab0f600)
Boot001B* USB HDD VenMsg(bc7838d2-0f82-4d60-8316-c068ee79d25b,33e821aaaf33bc4789bd419f88c50803)
Boot001C* PCI LAN VenMsg(bc7838d2-0f82-4d60-8316-c068ee79d25b,78a84aaf2b2afc4ea79cf5cc8f3d3803)
Boot001D* IDER BOOT CDROM PciRoot(0x0)/Pci(0x16,0x2)/Ata(0,1,0)
Boot001E* IDER BOOT Floppy PciRoot(0x0)/Pci(0x16,0x2)/Ata(0,0,0)
Boot001F* ATA HDD VenMsg(bc7838d2-0f82-4d60-8316-c068ee79d25b,91af625956449f41a7b91f4f892ab0f6)
Boot0020* ATAPI CD VenMsg(bc7838d2-0f82-4d60-8316-c068ee79d25b,aea2090adfde214e8b3a5e471856a354)
$ doas xbps-reconfigure -f linux5.18
linux5.18: configuring ...
Executing post-install kernel hook: 20-booster ...
Executing post-install kernel hook: 50-efibootmgr ...
linux5.18: configured successfully.
$ doas efibootmgr
BootCurrent: 0001
Timeout: 0 seconds
BootOrder: 0001,0017,0018,0019,001A,001B,001C
Boot0000* Void Linux with kernel 5.18 HD(1,GPT,4a04d763-6e6c-4f50-a11b-c5d1092ccee5,0x800,0x100000)/File(\vmlinuz-5.18.16_1)6c006f0067006c006500760065006c003d0034002000720064002e006c0075006b0073002e006e0061006d0065003d00380030003900640066003400320037002d0064003700640035002d0034003000380063002d0061003100390035002d003300620065003600650038003600380031003300330033003d006300720079007000740072006f006f007400200072006f006f0074003d002f006400650076002f006d00610070007000650072002f006300720079007000740072006f006f0074002000720064002e006c0075006b0073002e006f007000740069006f006e0073003d006400690073006300610072006400200069006e0069007400720064003d002f0069006e0069007400720061006d00660073002d0035002e00310038002e00310036005f0031002e0069006d006700
Boot0001* Void Linux with test kernel HD(1,GPT,4a04d763-6e6c-4f50-a11b-c5d1092ccee5,0x800,0x100000)/File(\vmlinuz-5.18.16_1)6c006f0067006c006500760065006c003d0034002000720064002e006c0075006b0073002e006e0061006d0065003d00380030003900640066003400320037002d0064003700640035002d0034003000380063002d0061003100390035002d003300620065003600650038003600380031003300330033003d006300720079007000740072006f006f007400200072006f006f0074003d002f006400650076002f006d00610070007000650072002f006300720079007000740072006f006f0074002000720064002e006c0075006b0073002e006f007000740069006f006e0073003d006400690073006300610072006400200069006e0069007400720064003d005c0069006e0069007400720061006d00660073002d0035002e00310038002e00310036005f0031002e0069006d006700
Boot0010 Setup FvFile(721c8b66-426c-4e86-8e99-3457c46ab0b9)
Boot0011 Boot Menu FvFile(126a762d-5758-4fca-8531-201a7f57f850)
Boot0012 Diagnostic Splash Screen FvFile(a7d8d9a6-6ab0-4aeb-ad9d-163e59a7a380)
Boot0013 Lenovo Diagnostics FvFile(3f7e615b-0d45-4f80-88dc-26b234958560)
Boot0014 Startup Interrupt Menu FvFile(f46ee6f4-4785-43a3-923d-7f786c3c8479)
Boot0015 Rescue and Recovery FvFile(665d3f60-ad3e-4cad-8e26-db46eee9f1b5)
Boot0016 MEBx Hot Key FvFile(ac6fd56a-3d41-4efd-a1b9-870293811a28)
Boot0017* USB CD VenMsg(bc7838d2-0f82-4d60-8316-c068ee79d25b,86701296aa5a7848b66cd49dd3ba6a55)
Boot0018* USB FDD VenMsg(bc7838d2-0f82-4d60-8316-c068ee79d25b,6ff015a28830b543a8b8641009461e49)
Boot0019* NVMe0 VenMsg(bc7838d2-0f82-4d60-8316-c068ee79d25b,001c199932d94c4eae9aa0b6e98eb8a400)
Boot001A* ATA HDD0 VenMsg(bc7838d2-0f82-4d60-8316-c068ee79d25b,91af625956449f41a7b91f4f892ab0f600)
Boot001B* USB HDD VenMsg(bc7838d2-0f82-4d60-8316-c068ee79d25b,33e821aaaf33bc4789bd419f88c50803)
Boot001C* PCI LAN VenMsg(bc7838d2-0f82-4d60-8316-c068ee79d25b,78a84aaf2b2afc4ea79cf5cc8f3d3803)
Boot001D* IDER BOOT CDROM PciRoot(0x0)/Pci(0x16,0x2)/Ata(0,1,0)
Boot001E* IDER BOOT Floppy PciRoot(0x0)/Pci(0x16,0x2)/Ata(0,0,0)
Boot001F* ATA HDD VenMsg(bc7838d2-0f82-4d60-8316-c068ee79d25b,91af625956449f41a7b91f4f892ab0f6)
Boot0020* ATAPI CD VenMsg(bc7838d2-0f82-4d60-8316-c068ee79d25b,aea2090adfde214e8b3a5e471856a354)
```
next prev parent reply other threads:[~2022-08-08 14:09 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-08 13:06 [ISSUE] " dkwo
2022-08-08 14:09 ` dkwo [this message]
2022-08-08 15:24 ` dkwo
2022-08-11 21:58 ` prez
2022-08-11 21:58 ` prez
2022-08-12 16:36 ` TeusLollo
2022-08-12 16:38 ` TeusLollo
2022-08-13 3:07 ` prez
2022-08-13 8:32 ` dkwo
2022-08-22 12:18 ` sgn
2022-08-22 15:12 ` TeusLollo
2022-08-22 15:13 ` TeusLollo
2022-08-22 15:41 ` Duncaen
2022-08-22 15:58 ` dkwo
2022-08-22 15:58 ` [ISSUE] [CLOSED] " dkwo
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20220808140923.qnZo2wUr7bqjBc1tr_huSJ-0kHZtPByHarFTBZ86UMw@z \
--to=dkwo@users.noreply.github.com \
--cc=ml@inbox.vuxu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).