Package: grub-efi-amd64 Version: 2.02~beta2-22
Hello! I use Debian testing on my Lenovo ThinkPad X120e. I installed Debian 7.5 (or 7.6, don't remember) and updated it to "testing" according to the Debian manuals, so now it is Debian 8. My ThinkPad X120e has a buggy EFI BIOS implementation. It is not possible to use efibootmgr and get a working EFI boot selection. At least it was not possible back then (with Debian 7.5). Windows did the trick, but since the BIOS is quite buggy from the beginning, I cannot say if/how often it actually used the generel \EFI\boot\bootx64.efi installed by Windows 7 anyway. But at least with Windows 7 a manual EFI boot selection worked. But dual booting Debian (or any other Linux) with Windows 7 distroyed the Debian EFI boot entry everytime I (once) booted into Windows from either the EFI boot selection or GRUB. Somehow the Debian EFI boot entry changed or was altered or got distroyed. It was still there, and I could read it, but EFI would no longer boot it. I finally ended up copying \EFI\debian\grubx64.efi to \EFI\boot\bootx64.efi, with Windows being a boot option from GRUB (using the EFI bootloader \EFI\Microsoft\Boot\bootmgfw.efi, but the automatic OS detection handles this nicely by itself). This really _is_ the only stable solution for any buggy EFI implementation. (I have a very similar issue on a Proworx desktop PC featureing a Gegabyte mainboard, of which I found out that it only supports the fallback EFI boot method.) MY ISSUE: Recently I ran some updates, one of them apparently a GRUB and/or kernel update, rendering my system unbootable. I have no idea why. I did not run update-grub or grub-install manually and I don't know if the dpkg triggers ran them, but the file in \EFI\Debian had a new date and the one in \EFI\boot did not. GRUB loaded to a very basic (and limited) command prompt and was unable to find any modules, so I could not even manually boot. I used a Debian 7.6 installation DVD in rescue mode and copied the file \EFI\debian\grubx64.efi once again manually to \EFI\boot\bootx64.efi so it booted again. QUESTION: I found bug #708430, but how is it fixed? I cannot find a dpkg-trigger for this workaround. The only proove I currently have: if GRUB gets updated, the file date in \EFI\debian\grubx64.efi is updated whereas \EFI\boot\bootx64.efi then differs (using cmp to compate them) and has an older date. IDEA FOR A SOLUTION: Add a trigger to optinally additionally install to \EFI\boot and not only to \EFI\debian when running grub-install. Cheers, Andreas. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
