have openSuse 12.3 running on an UEFI system with Secure Boot in Multiboot mode aside to Windows 8. Everything was fine, Suse with Secure Boot working super.
Until kernel update to 3.7.10-1.1.1 (3.7.10-1.4.1). (no idea why YAST2 shows both numbers but thats how it it is).
After the update process the system does not but at all boot into Suse, saying no bootable system, not even GRUB is being displayed.
Only after new install and avoiding the kernel update everything running fine again. I am no longer daring kernel updates, but this can not be the solution in the long run.
starting from openSUSE 12.3 YaST keeps multiple(3) kernels. This is to provide a way to ensure booting into desktop in event of an kernel update failure. Grub not showing up is generally not releated to kernel update failure. Then again i might be wrong
Maybe the update was bad and the new kernel is not up to snuff according to secure boot. Thus try turn secure boot off and try it try running updates again if you can boot and maybe it gets fixed and if you are that paranoid you can turn it on again later and see if things still work.
On 05/25/2013 03:06 PM, gogalthorp wrote:
>
> Maybe the update was bad and the new kernel is not up to snuff according
> to secure boot. Thus try turn secure boot off and try it try running
> updates again if you can boot and maybe it gets fixed and if you are
> that paranoid you can turn it on again later and see if things still
> work.
>
> Just a thought
>
>
There was an update to grub that may have caused the problem. For me I
had the opposite problem. I have a laptop with Windows 8 and installed
openSUSE 12.3 on it.
Before the update I could only boot Windows 8 with the BIOS in UEFI and
in secure mode. I had to change to legacy mode in the BIOS to boot
openSUSE. Now I can boot both Windows 8 and openSUSE in UEFI but not
secure boot. I can still boot Windows 8 using secure boot but also with
secure boot off.
I do not know what actually caused the change but it happened after an
update in early May.
It was a pain changing the BIOS when I wanted to boot a different
operating system and now I do not need to but I am missing the benefit
of secure boot (What ever that is?).
No, it is clear for me that normally a shared EFI partition should be used. And you have to direct to it when choosing the manual partition configuration at install.
BTW I used grub2-efi.
Well I think it has nothing to do with being paranoid but once you have to live with the Microsoft world as it is and run Windows 8 in multiboot environment as some programs and functionalities are simply only available on Windows, you need to run in secure boot and don’t want to flip around in UEFI every you boot to the other system.
I am happy that we have Suse, as it is the only distro besides Ubuntu (as far as I know) that is capable of secure boot. I am aware that secure boot in Suse is experimental, but I want to use it and thought it good idea to share my experience. Maybe it can a little bit contribute to improve Suse even more.
was a black screen with only text mode message “…no valid bootable system found…” or something similar. I am not 100% sure any more but I think there was also “…background could be a system change after a recent upgrade…” that’s all.
and I don’t dare to reproduce and get my photo camera to take a picture
My understanding is there are those who disagree and who believe that having a separate EFI partition for GNU/Linux is more safe. I myself don’t know and I’m just reading and attempting to learn.
wrt GNU/Linux distributions that support Secure boot, I am aware of Ubuntu , Fedora, and openSUSE. Its also possible others (such as Arch ? ) support this . For example this linlap article notes Fedora, Ubuntu, and openSUSE: Dealing with UEFI and Secure Boot on Linux [Linux Wiki Guides]
took some time of not daring to reinstall, but then after backups meanwhile have reinstalled completely and now updating kernels works fine, nor problems any more, switching in multiboot in secure boot mode between Win8 and opensuse works fine and very fast
I think I have must have made a mistake in my first install ( I suspect it was the tickmark for secure boot option (but then on the other hand it shouldn’t have booted at all).)
With help from more knowledgeable users on this forum, I was also fortunate to be successful in installing openSUSE-12.3 , with secure boot, on my Ultrabook. I’m quite pleased with this.
I just ran in to a similar problem on a Lenovo G780. Installed 12.3 and it secure booted without problems alongside windows. But after my first upgrade a reboot send the machine straight into windows again.
Booting into BIOS (On this Lenovo by switching it on using the small button besides the power button) I noticed that there was 3 entries and that the opensuse-secureboot was not on top. Moving secureboot to the top solved the problem.
