Bug#963475: Could not parse device path: Invalid argument
Hello,
I was filing a new bug against efibootmgr, but my issue might belong
here as well.
When I invoke `efibootmgr -v`, it gives the error `Could not parse
device path: Invalid argument`
```
omer@omer:~$ efibootmgr
BootCurrent: 0003
Timeout: 1 seconds
BootOrder: 0000,0003,0001,0002
Boot0000* Windows Boot Manager
Boot0001 Hard Drive
Boot0002 USB HDD
Boot0003* debian
omer@omer:~$ efibootmgr -v
BootCurrent: 0003
Timeout: 1 seconds
BootOrder: 0000,0003,0001,0002
Boot0000* Windows Boot ManagerCould not parse device path: Invalid argument
```
A similar error was also reported against Ubuntu [1] and Fedora [2].
[1]: https://bugs.launchpad.net/ubuntu/+source/efivar/+bug/1844320
[2]: https://bugzilla.redhat.com/show_bug.cgi?id=1773175
I have dual boot with Windows 10 and Bullseye. I came across this
error while I was trying to figure out a way to edit Windows' GPT
entry (so that my PC boots to grub even after Windows 10 tampers GPT
entries to put its own boot manager in the first place).
Package versions:
ii efibootmgr 17-1 amd64 Interact with the EFI
Boot Manager
ii libc6:amd64 2.31-1 amd64 GNU C Library: Shared libraries
ii libefiboot1:amd64 37-2.1 amd64 Library to manage UEFI variables
ii libefivar1:amd64 37-2.1 amd64 Library to manage UEFI variables
ii libpopt0:amd64 1.18-1 amd64 lib for parsing
cmdline parameter
In my case, when I compiled the latest efivar [3], `efibootmgr -v` ran
without any issues with the compiled shared objects libefivar.so.1 and
libefiboot.so.1 in its LD_LIBRARY_PATH.
[3]: https://github.com/rhboot/efivar/tree/36297adcb266f07bb06e725a0da377bc6e6aedd0
Best,
Omer
Reply to: