[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#963805: marked as done (efibootmgr: Could not parse device path: Invalid argumen)

Your message dated Sun, 18 Dec 2022 20:14:31 +0000
with message-id <20221218201431.GE1143906@tack.einval.com>
and subject line Re: Bug#963805: efibootmgr: Could not parse device path: Invalid argumen
has caused the Debian Bug report #963805,
regarding efibootmgr: Could not parse device path: Invalid argumen
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact owner@bugs.debian.org
immediately.)


-- 
963805: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=963805
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message --- 
Package: efibootmgr
Version: 17-1
Severity: normal

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512

Dear Maintainer,

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

The list is returned when the "-v" option is omitted:

# efibootmgr
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  Setup
Boot0001  Boot Menu
Boot0002  Diagnostic Splash Screen
Boot0003  Lenovo Diagnostics
Boot0004  Startup Interrupt Menu
Boot0005  ME Configuration Menu
Boot0006  Rescue and Recovery
Boot0007  USB CD
Boot0008  USB FDD
Boot0009  ATAPI CD0
Boot000A* ATA HDD0
Boot000B* ATA HDD1
Boot000C* ATA HDD2
Boot000D* USB HDD
Boot000E  PCI LAN
Boot000F  ATAPI CD1
Boot0010  Other CD
Boot0011* ATA HDD3
Boot0012  Other HDD
Boot0013* IDER BOOT CDROM
Boot0014* IDER BOOT Floppy
Boot0015* ATA HDD
Boot0016* ATAPI CD:
Boot0017* PCI LAN
Boot0018* SHIM MS
Boot0019* SHIM Debian
Boot001A* REFIND
Boot001B* GRUB

The last four entries were added manually. I removed them, but that didn't
help.



- -- System Information:
Debian Release: bullseye/sid
  APT prefers unstable
  APT policy: (990, 'unstable'), (500, 'buildd-unstable'), (300, 'stable'),
(130, 'experimental')
Architecture: amd64 (x86_64)

Kernel: Linux 5.7.5-amd64 (SMP w/4 CPU cores; PREEMPT)
Kernel taint flags: TAINT_RANDSTRUCT
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8),
LANGUAGE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages efibootmgr depends on:
ii  libc6        2.30-8
ii  libefiboot1  37-2.1
ii  libefivar1   37-2.1
ii  libpopt0     1.18-1

efibootmgr recommends no packages.

efibootmgr suggests no packages.




-----BEGIN PGP SIGNATURE-----

iHUEARYKAB0WIQR1ZhNYxftXAnkWpwEy2ctjR5bMoQUCXveMKQAKCRAy2ctjR5bM
oQtEAP92aa3tUk14z56bpArSiiMktoxjpORxqpr5e8rhN3IyLwD/cCqIn764cAxJ
2JzUZjum2U20HjF0niXGUcSlcdX86wg=
=XTrq
-----END PGP SIGNATURE-----

--- End Message ---
--- Begin Message --- 
Trying again, without a typo in the -done address :-/

On Sun, Jul 05, 2020 at 10:19:52AM -0600, Kevin Locke wrote:
>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

Agreed, and this has been fixed for a while now. Closing...

-- 
Steve McIntyre, Cambridge, UK.                                steve@einval.com
Dance like no one's watching. Encrypt like everyone is.
 - @torproject

--- End Message ---
Reply to: