https://bugzilla.suse.com/show_bug.cgi?id=1224025 https://bugzilla.suse.com/show_bug.cgi?id=1224025#c1 --- Comment #1 from Stefan Hundhammer <shundhammer@suse.com> --- If your machine's BIOS / UEFI firmware lets you choose the boot mode (PC legacy vs. secure boot (UEFI)) on the fly, that's a severe bug in that BIOS / UEFI firmware because that boot mode will be purely temporary, and the next regular boot will almost certainly be whatever is configured in the machine's CMOS RAM (the settings that you can configure with the BIOS / UEFI firmware). Worse, even if they do also override subsequent boots, it will clash with existing operating systems. If you have a Windows installation that is set up for secure boot (UEFI) and then you use that override menu to boot into a Linux installation DVD or USB stick in PC legacy boot mode, that Linux will of course use PC legacy boot. If it resizes your Windows, you will end up with two operating systems with conflicting boot modes; one of them will no longer boot. For all variants of SUSE Linux, you can easily see from the installation medium boot screen already if you are booting into PC legacy or UEFI mode: https://doc.opensuse.org/documentation/leap/startup/html/book-startup/cha-bo... If you see a row of function key descriptions at the bottom, it's PC legacy (BIOS boot) mode:
F1 F2 F3 F4 F5 F6 Help Language Video mode Source Kernel Driver English Default Default Default No
If you don't see those function key descriptions, just a Grub menu, it's UEFI mode: https://doc.opensuse.org/documentation/leap/startup/html/book-startup/cha-bo...
C: Command Line E: Edit Entry -- You are receiving this mail because: You are on the CC list for the bug.