Bug#918863: reboot returns to Windows 10 on Lenovo X1

See for a proof of concept.

Bug#918863: reboot returns to Windows 10 on Lenovo X1

Hello Thomas, Am 05.02.19 um 20:50 schrieb Thomas Gaugler: ... > I thought to use the momentum around secure boot within Debian [2] for > supporting it within win32-loader as well. > > The basic idea is to replicate the following commands in win32-loader: > $ # Copy

Bug#918863: reboot returns to Windows 10 on Lenovo X1

The BOOTCFG_IsUEFI function in include/bootcfg.nsh could be used to detect the firmware type (legacy BIOS versus UEFI). I thought to use the momentum around secure boot within Debian [2] for supporting it within win32-loader as well. The basic idea is to replicate the following commands in

Bug#918863: reboot returns to Windows 10 on Lenovo X1

Am 04.02.19 um 13:42 schrieb Didier 'OdyX' Raboud: > Le mardi, 15 janvier 2019, 17.39:00 h CET Bernhard Übelacker a écrit : >> If such a system is detected, maybe a warning could be added? > > Sure. I suggest this would be done very early, but have no clue how to detect > such a system. This

Bug#918863: reboot returns to Windows 10 on Lenovo X1

Le mardi, 15 janvier 2019, 17.39:00 h CET Bernhard Übelacker a écrit : > Therefore I raise the question if win32-loader is really supposed > to work on a secure boot EFI system? No. This was never implemented. win32-loader needs a new maintainer who is willing to tackle exactly these types of

Bug#918863: reboot returns to Windows 10 on Lenovo X1

Hello Tom Brown, dear Maintainer, I just tried to reproduce this on a amd64 qemu EFI VM. >From your description is not clear if you received on reboot the menu to select between "Windows 10" or "Debian GNU/Linux - Continue with install process"? If that is missing you might add the output of

Bug#918863: reboot returns to Windows 10 on Lenovo X1

Package: win32-loader Version: 0.8.3+deb9u1 +net I have a new Lenovo X1 6th Gen running stock Windows 10. It has one internal disk and 16GB Ram. The first thing I did with it was download and run win32-loader. I didn't notice any errors, read the notice about rebooting, waited eagerly for the