Hi Jon, On Thu, May 05, 2016 at 10:01:44PM +0200, Jon Jahren wrote: >Package: debian-installer >Severity: important > >Dear Maintainer, > >When attempting to install Debian testing on an efi system using a nightly >build because the alpha installer stalls with a systemd dependency, the efi >partition it creates does not boot, and you have to install in legacy mode to >get it to boot as normal. The problem with this though, is that the legacy mode >does not correctly detect other efi installations(e.g Windows). > >>From what I gather, after manually mounting the efi system boot after >installing a legacy boot system, some files are missing. The only file I have >is grubx64.efi, while for instance an Ubuntu install has: >grubx64.efi >shimx64 >MokManager.efi >grub.cfg >fwupx64.efi >fw/
No, the only thing Debian needs (for now) is the grubx64.efi file. If it's got that far, then the system should be booting; the problem is more likely to be somewhere else. What hardware do you have, please? Also: the issue with the systemd dependency has also been fixed for a while; the latest alpha build is now quite old and you might also be better using a recent daily or ewwkly build instead. -- Steve McIntyre, Cambridge, UK. [email protected] You lock the door And throw away the key There's someone in my head but it's not me
