Your message dated Wed, 25 Jun 2014 15:41:07 -0500 with message-id <[email protected]> and subject line Re: efibootmgr: fails to modify existing boot entries has caused the Debian Bug report #726051, regarding efibootmgr: fails to modify existing boot entries 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 [email protected] immediately.) -- 726051: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=726051 Debian Bug Tracking System Contact [email protected] with problems
--- Begin Message ---Package: efibootmgr Version: 0.5.4-7 Severity: normal Dear Maintainer, Using : # efibootmgr -b <n> -l <new_path> -L <new_name> fails to apply the expected changes to the <n>'s entry. No related message is displayed in dmesg when trying to do so. On the other hand, adding/removing entries and changing boot order does work as expected. Below a "screen" copy of one attempt on my system (Asus G55VW) : ---------------------------------------------------------------------- root@debian:~# efibootmgr -b 0 -L rEFInd BootCurrent: 0003 Timeout: 0 seconds BootOrder: 0003,0000,0005,0001,0004,0002 Boot0000* Uber boot manager : rEFInd Boot0001* elilo Boot0002* Network Card Boot0003* debian Boot0004* Windows Boot Manager Boot0005* EFI shell root@debian:~# efibootmgr -v BootCurrent: 0003 Timeout: 0 seconds BootOrder: 0003,0000,0005,0001,0004,0002 Boot0000* Uber boot manager : rEFInd HD(1,800,64000,cc17e3d7-fb34-45f0-ad03-8ecea7e2ebfd)File(\EFI\refind\refind_x64.efi)WINDOWS.........x...B.C.D.O.B.J.E.C.T.=.{.9.d.e.a.8.6.2.c.-.5.c.d.d.-.4.e.7.0.-.a.c.c.1.-.f.3.2.b.3.4.4.d.4.7.9.5.}...-................ Boot0001* elilo HD(1,800,64000,cc17e3d7-fb34-45f0-ad03-8ecea7e2ebfd)File(\EFI\elilo\elilo.efi) Boot0002* Network Card BIOS(6,0,00)AMGOAMNO........i.A.t.h.e.r.o.s. .B.o.o.t. .A.g.e.n.t.........................rN.D+..,.\...........:..Gd-.;.A..MQ..L.A.t.h.e.r.o.s. .B.o.o.t. .A.g.e.n.t......AMBO Boot0003* debian HD(1,800,64000,cc17e3d7-fb34-45f0-ad03-8ecea7e2ebfd)File(\EFI\debian\grubx64.efi) Boot0004* Windows Boot Manager HD(1,800,64000,cc17e3d7-fb34-45f0-ad03-8ecea7e2ebfd)File(\EFI\Microsoft\Boot\bootmgfw.efi) Boot0005* EFI shell HD(1,800,64000,cc17e3d7-fb34-45f0-ad03-8ecea7e2ebfd)File(\EFI\tools\shell.efi) ---------------------------------------------------------------------- Feel free to request more info or further tests if needed. regards, Alexandre Hoïde -- System Information: Debian Release: jessie/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.10-3-amd64 (SMP w/8 CPU cores) Locale: LANG=fr_CH.UTF-8, LC_CTYPE=fr_CH.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages efibootmgr depends on: ii libc6 2.17-93 ii libpci3 1:3.2.0-3 ii zlib1g 1:1.2.8.dfsg-1 efibootmgr recommends no packages. efibootmgr suggests no packages. -- no debconf information
--- End Message ---
--- Begin Message --- 0.7.0-1 is a couple major versions newer, available in testing/unstable and has a large change set. I'm closing this bug. Please reopen it if the issue you see persists.-- Jared Domínguez Server OS Engineering Dell | Enterprise Solutions Group
--- End Message ---
