UEFI Boot problems

English Install/Boot/Login
1

Hi community,

before the Tumbleweed forum was closed some people, including me, experiences problems with the UEFI support of Tumbleweed. In particular the reported issues were the following:

  1. Creating an UEFI boot capable boot stick no longer works
  2. Running zypper dup to upgrade to one of the snapshots with broken UEFI setup results in an unbootable system.

There is even a bug filed in bugzilla, but there were no responses or any activity regarding the issue.

For me this means that I am stuck with a months old system.

What I would like to know is: Can anyone give some update regarding the issue? Is someone trying to solve this? Could my susceptible system be used to create a test to catch such issues in the future?

The thread was

https://forums.opensuse.org/showthread.php/508822-UEFI-Mode-Problems

and the bugzilla bug is

https://bugzilla.opensuse.org/show_bug.cgi?id=939456

Cheers

2

Hi
Have you downloaded the latest image (released yesterday) and checked?

I have an older iso image, but used it for an install last night, then just ran a zypper dup to bring the system up to date?

3

I downloaded the live Rescue CD image from the 20150807. It is still broken for USB use on a UEFI box.

4

I tried like one or two days ago.

I think the UEFI becoming non-bootable has to do with the flaky implementation of the laptop manufacturer and further that my system becoming non-bootable probably has the same root cause as the boot stick issue.

For this reason I tried to download the latest snapshot,. Then I created from this a boot stick using SUSE Studio Imagewriter. → No UEFI compliant boot stick…

At the moment I do no updates at all. I wanted to wait for a fix and then try again. This is why it is so important for me to know if this issue is being worked on. :slight_smile:

5

I hope it is being worked on. But I see no evidence.

For the record, I did an install a few days ago – **** the torpedoes, full speed ahead My Tumbleweed install for August

6

I think that there is a bug report and continued interest on the forum should be sufficient to get things in motion.

If nobody feels responsible for this then I will have to either switch back to 13.2 or look for alternatives (Arch/Debian Testing/…). Would just be good to know soon.