Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > linux.debian.bugs.dist > #1016637
| From | Kevin Locke <kevin@kevinlocke.name> |
|---|---|
| Newsgroups | linux.debian.bugs.dist |
| Subject | Bug#963805: efibootmgr: Could not parse device path: Invalid argumen |
| Date | 2020-07-05 18:40 +0200 |
| Message-ID | <ApfQm-Rd-9@gated-at.bofh.it> (permalink) |
| References | <AmnAK-5Wc-9@gated-at.bofh.it> <AmnAK-5Wc-9@gated-at.bofh.it> |
| Organization | linux.* mail to news gateway |
On Sat, 2020-06-27 at 20:13 +0200, Mikhail Morfikov wrote: > it looks like that efibootmgr works well, but when the "-v" flag is used, I get > the following output: > > # efibootmgr -v > BootCurrent: 001A > Timeout: 0 seconds > BootOrder: > 001A,001B,0019,0018,0001,0002,0003,0007,0008,0009,000A,000D,000B,000C,000E,000F,0010,0011,0012 > Boot0000 SetupCould not parse device path: Invalid argument I am experiencing the same issue. FYI, it is caused by a bug in libefiboot1 37-2.1, which can be worked around by downgrading to 37-2 until a fix is released. See https://bugs.debian.org/963475 and https://github.com/rhboot/efibootmgr/issues/133#issuecomment-632578892 Best, Kevin
Back to linux.debian.bugs.dist | Previous | Next — Previous in thread | Find similar | Unroll thread
Bug#963805: efibootmgr: Could not parse device path: Invalid argumen Mikhail Morfikov <mmorfikov@gmail.com> - 2020-06-27 20:20 +0200 Bug#963805: efibootmgr: Could not parse device path: Invalid argumen Kevin Locke <kevin@kevinlocke.name> - 2020-07-05 18:40 +0200
csiph-web