Bug#1055526: efibootmgr: output broken and shows hex dump after update (can be fixed with -u, which is documented as unrelated)

To: Fab Stz <fabstz-it@yahoo.fr>
Cc: 1055526@bugs.debian.org
Subject: Bug#1055526: efibootmgr: output broken and shows hex dump after update (can be fixed with -u, which is documented as unrelated)
From: наб <nabijaczleweli@nabijaczleweli.xyz>
Date: Sun, 1 Jun 2025 20:01:30 +0200
Message-id: <[🔎] wxxj4jscqve73l3ux4htu6g55gfsez2r465tawzbuzklfgnzta@tarta.nabijaczleweli.xyz>
Reply-to: наб <nabijaczleweli@nabijaczleweli.xyz>, 1055526@bugs.debian.org
In-reply-to: <[🔎] 5893918.DvuYhMxLoT@debian>
References: <rzxuy5ingnletm6alc3dkkqbau67q3hg2zcqbup35ln2pj762v@babtop.nabijaczleweli.xyz> <lkpjl7a4d7uxbomq2m3hoo73tsj4bq4rl5hbeypcmdcnkayyxi@babtop.nabijaczleweli.xyz> <[🔎] 4667111.LvFx2qVVIh@debian> <[🔎] 5893918.DvuYhMxLoT@debian> <rzxuy5ingnletm6alc3dkkqbau67q3hg2zcqbup35ln2pj762v@babtop.nabijaczleweli.xyz>

Funnily enough, efibootmgr 18-1:

$ efibootmgr
BootCurrent: 0001
Timeout: 2 seconds
BootOrder: 0001,0004,0002,0003,0007,0000
Boot0000* Enter Setup   FvVol(8063c21a-8e58-4576-95ce-089e87975d23)/FvFile(462caa21-7614-4503-836e-8ab6f4662331)
Boot0001* Debian GNU/Linux trixie/sid with Linux 6.6.9-amd64    HD(1,GPT,b56e9130-b36e-4b7b-9abf-6fe3cb9606c7,0x800,0x79800)/File(\KLAPKI\DD956699294C45E99FFE000DF2D986D6\6.6.9-AMD64\VMLINUZ-6.6.9-AMD64)69006e0069007400720064003d005c006b006c00610070006b0069005c00640064003900350036003600390039003200390034006300340035006500390039006600660065003000300030006400660032006400390038003600640036005c0036002e0036002e0039002d0061006d006400360034005c0069006e0069007400720064002e0069006d0067002d0036002e0036002e0039002d0061006d00640036003400200072006f006f0074003d007a00660073003a004100550054004f00200072006500730075006d0065003d0050004100520054004c004100420045004c003d006300680072007500730074002d007300770061007000200069006e00740065006c005f0069006f006d006d0075003d006f006e002000730079007300630061006c006c002e007800330032003d007900200071007500690065007400
Boot0002* eMMC Device   PciRoot(0x0)/Pci(0x1c,0x0)/eMMC(0)/Ctrl(0x0){auto_created_boot_option}
Boot0003* UEFI Shell    FvVol(8063c21a-8e58-4576-95ce-089e87975d23)/FvFile(7c04a583-9e3e-4f1c-ad65-e05268d0b4d1)
Boot0004* Debian GNU/Linux trixie/sid with Linux 6.6.9-amd64 (verbose debug)    HD(1,GPT,b56e9130-b36e-4b7b-9abf-6fe3cb9606c7,0x800,0x79800)/File(\CHRUST\6.6.9-AMD64\VMLINUZ-6.6.9-AMD64)69006e0069007400720064003d005c006b006c00610070006b0069005c00640064003900350036003600390039003200390034006300340035006500390039006600660065003000300030006400660032006400390038003600640036005c0036002e0036002e0039002d0061006d006400360034005c0069006e0069007400720064002e0069006d0067002d0036002e0036002e0039002d0061006d00640036003400200072006f006f0074003d007a00660073003a004100550054004f00200072006500730075006d0065003d0050004100520054004c004100420045004c003d006300680072007500730074002d007300770061007000200069006e00740065006c005f0069006f006d006d0075003d006f006e002000730079007300630061006c006c002e007800330032003d007900200076006500720062006f0073006500200064006500620075006700
Boot0007* debian        HD(2,GPT,4ad22847-4499-314f-8d8f-866509d94fa6,0x1000,0xff800)/File(\EFI\debian\shimx64.efi)

$ efibootmgr -u
BootCurrent: 0001
Timeout: 2 seconds
BootOrder: 0001,0004,0002,0003,0007,0000
Boot0000* Enter Setup   FvVol(8063c21a-8e58-4576-95ce-089e87975d23)/FvFile(462caa21-7614-4503-836e-8ab6f4662331)
Boot0001* Debian GNU/Linux trixie/sid with Linux 6.6.9-amd64    HD(1,GPT,b56e9130-b36e-4b7b-9abf-6fe3cb9606c7,0x800,0x79800)/File(\KLAPKI\DD956699294C45E99FFE000DF2D986D6\6.6.9-AMD64\VMLINUZ-6.6.9-AMD64)initrd=\klapki\dd956699294c45e99ffe000df2d986d6\6.6.9-amd64\initrd.img-6.6.9-amd64 root=zfs:AUTO resume=PARTLABEL=chrust-swap intel_iommu=on syscall.x32=y quiet
Boot0002* eMMC Device   PciRoot(0x0)/Pci(0x1c,0x0)/eMMC(0)/Ctrl(0x0)걎脈鼑䵙຅᫢ⱒ뉙
Boot0003* UEFI Shell    FvVol(8063c21a-8e58-4576-95ce-089e87975d23)/FvFile(7c04a583-9e3e-4f1c-ad65-e05268d0b4d1)
Boot0004* Debian GNU/Linux trixie/sid with Linux 6.6.9-amd64 (verbose debug)    HD(1,GPT,b56e9130-b36e-4b7b-9abf-6fe3cb9606c7,0x800,0x79800)/File(\CHRUST\6.6.9-AMD64\VMLINUZ-6.6.9-AMD64)initrd=\klapki\dd956699294c45e99ffe000df2d986d6\6.6.9-amd64\initrd.img-6.6.9-amd64 root=zfs:AUTO resume=PARTLABEL=chrust-swap intel_iommu=on syscall.x32=y verbose debug
Boot0007* debian        HD(2,GPT,4ad22847-4499-314f-8d8f-866509d94fa6,0x1000,0xff800)/File(\EFI\debian\shimx64.efi)

Note that Boot0002 turned from {auto_created_boot_option} to 걎脈鼑䵙຅᫢ⱒ뉙.

I can see that Boot0007 is latin in both cases,
but "interpret file paths as text IFF they have »shim« in there" is ass.

Attachment: signature.asc
Description: PGP signature

Reply to:

References:
- Bug#1055526: efibootmgr: output broken and shows hex dump after update (can be fixed with -u, which is documented as unrelated)
  - From: Fab Stz <fabstz-it@yahoo.fr>
- Bug#1055526: efibootmgr: output broken and shows hex dump after update (can be fixed with -u, which is documented as unrelated)
  - From: Fab Stz <fabstz-it@yahoo.fr>

Prev by Date: Bug#1055526: efibootmgr: output broken and shows hex dump after update (can be fixed with -u, which is documented as unrelated)
Next by Date: Processed: Re: efibootmgr: output broken and shows hex dump after update (can be fixed with -u, which is documented as unrelated)
Previous by thread: Bug#1055526: efibootmgr: output broken and shows hex dump after update (can be fixed with -u, which is documented as unrelated)
Next by thread: Bug#1055526: efibootmgr: output broken and shows hex dump after update (can be fixed with -u, which is documented as unrelated)
Index(es):
- Date
- Thread