Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > linux.debian.bugs.dist > #1019514
| From | Kevin Locke <kevin@kevinlocke.name> |
|---|---|
| Newsgroups | linux.debian.bugs.dist |
| Subject | Bug#963475: libefivar1: "efibootmgr -v" fails with "Could not parse device path: Invalid argument" |
| Date | 2020-07-27 21:00 +0200 |
| Message-ID | <AxgvU-1ee-5@gated-at.bofh.it> (permalink) |
| References | (1 earlier) <AwV86-58D-19@gated-at.bofh.it> <AxeaJ-8oC-7@gated-at.bofh.it> <AxeaJ-8oC-5@gated-at.bofh.it> <AkoAW-6xC-5@gated-at.bofh.it> <AxeaJ-8oC-5@gated-at.bofh.it> |
| Organization | linux.* mail to news gateway |
On Mon, 2020-07-27 at 18:24 +0200, Michel Le Bihan wrote: > Le lundi 27 juillet 2020 à 15:28 +0000, Limonciello, Mario a écrit : >>> On Sun, 2020-07-26 at 14:58, Michel Le Bihan wrote: >>> What's preventing the upstream fix from being applied to this >>> package? >> >> I personally can't reproduce the failure on my system's firmware. >> Can you apply the fix locally and confirm it actually helps? > > I applied the fix and built the package. It didn't help. I also built > latest master and I still have this issue. FWIW, I'm also experiencing the issue that efibootmgr -v produces the error "Could not parse device path: Invalid argument" with libefiboot1 37-2.1, but not 37-2. Building libefiboot1 with fdb8034 and 4e04afc added to debian/patches does solve the issue for me. https://github.com/rhboot/efivar/commit/fdb803402fb32fa6d020bac57a40c7efe4aabb7d.patch https://github.com/rhboot/efivar/commit/4e04afc2df9bbc26e5ab524b53a6f4f1e61d7c9e.patch Best, Kevin P.S. I had to build using GCC 9 due to https://github.com/rhboot/efivar/issues/156
Back to linux.debian.bugs.dist | Previous | Next — Previous in thread | Next in thread | Find similar | Unroll thread
Bug#963475: libefivar1: "efibootmgr -v" fails with "Could not parse device path: Invalid argument" "Francesco Poli (wintermute)" <invernomuto@paranoici.org> - 2020-06-22 09:00 +0200
Bug#963475: libefivar1: "efibootmgr -v" fails with "Could not parse device path: Invalid argument" Francesco Poli <invernomuto@paranoici.org> - 2020-06-27 15:40 +0200
Bug#963475: libefivar1: "efibootmgr -v" fails with "Could not parse device path: Invalid argument" Michel Le Bihan <michel@lebihan.pl> - 2020-07-26 22:10 +0200
Bug#963475: libefivar1: "efibootmgr -v" fails with "Could not parse device path: Invalid argument" Michel Le Bihan <michel@lebihan.pl> - 2020-07-27 18:30 +0200
Bug#963475: libefivar1: "efibootmgr -v" fails with "Could not parse device path: Invalid argument" Kevin Locke <kevin@kevinlocke.name> - 2020-07-27 21:00 +0200
Bug#963475: libefivar1: "efibootmgr -v" fails with "Could not parse device path: Invalid argument" Michel Le Bihan <michel@lebihan.pl> - 2020-07-27 19:20 +0200
Bug#963475: libefivar1: "efibootmgr -v" fails with "Could not parse device path: Invalid argument" Michel Le Bihan <michel@lebihan.pl> - 2020-07-27 20:10 +0200
Bug#963475: Could not parse device path: Invalid argument Omer Ozarslan <omerfaruko@gmail.com> - 2020-07-28 03:20 +0200
Bug#963475: Could not parse device path: Invalid argument Michel Le Bihan <michel@lebihan.pl> - 2020-07-29 22:50 +0200
Bug#963475: Could not parse device path: Invalid argument Michel Le Bihan <michel@lebihan.pl> - 2020-08-01 22:20 +0200
csiph-web