Legacy > UEFI, 15.5 > 15.6 Pre-install Upgrade Questions

I am upgrading from Legacy BIOS to UEFI. At the same time, I’m upgrading 15.5 to 15.6. I’d like to make sure I know what I’m doing.

As far as I can tell during pre-install, there are only a few parameters I need to worry about. When the following window comes up, I should have these settings in boot code options:

If there are any settings that I need to know about under the other tabs, please tell me.

And as far as I can tell, when I reach the installation settings screen, then everything else should go smoothly:

Please tell me if there are any other settings on this screen that might concern me.

And there’s one more screen. I can’t understand where I should encounter it.

UEFI-shim-trust-opensuse-cert

Is this also a preinstall screen for UEFI?

Thanks in advance.

Randolph

The blue mok screen is only if you use secure boot.

If you use secure boot, all installed kernel modules have to be signed with a trusted key.

If the key is not in the database, you get:
Mok Example

1 Like

Hello @HealingMindNOS ,

You won’t be able to switch to UEFI unless you already have a mounted efi partition, which I do not think is required with legacy bios.

If you dual boot with windows, it will already be there, just make sure you mount it. If not, you might have to do some filesystem rearranging.

Sorry, but I think this is a bit unclear and the answers show it.

What are you upgrading? Your hardware?
When not the you must have now UEFI supporting hardware/firmware, but the operating systems on it are still BIOS?
Are you using multi-boot?

And to add. The screens you show remind me of a new installation going on. Not of any Upgrade.

I captured the screens from the reading material as well as I could find for the subject of UEFI.

Is this on the same computer?

Do you have an EFI partition mounted at “/boot/efi”?

If you try to upgrade using “zypper dup” you are going to run into problems. If you do have an EFI partition mounted at “/boot/efi” and if you upgrade using the DVD installer (or even the NET installer) it should mostly work. But you must boot the installer media in EFI mode.

Perhaps, it’s better to say I would like to change my firmware from Legacy BIOS to UEFI?

It looks like this is what I need. I upgraded to the latest firmware already, but I thought that upgrading from 15.5 to 15.6 would take care of this. It looks like I have make sure secure boot works first.

That then depends on the manufacturer of your system. Can you get that firmware somewhere? And then is the hardware able to support that firmware? And how do you install it on the system? Etc.

I assume that when that succeeds, you have to see this as a complete new system and then do a fresh install of Leap 15.6 on it. Check that the system boots the installation medium in UEFI mode and then do a normal install.

If you want secure boot on or not is something different.

I’m talking about the firmware BIOS Version

UEFI-BIOSVersion

That was easy, but as far as working with SDB:NVIDIA drivers - openSUSE Wiki, this may be beyond my understanding / ability. But I will try.

I must be misunderstanding. I get the impression from book-startup_en.pdf and book-reference_en.pdf that I need secure boot on a UEFI platform.

Hello @HealingMindNOS ,

It is REALLY easy to misunderstand.

The use of UEFI does not require secure boot.

I have a TUF mobo, a couple or a few years older than what you appear to be running. To actually use secure boot on mine, the secureboot setting must be set to “Windows OS”, not “Other OS”. I am not positive, but using secure boot may require you to disable legacy boot (under csm perhaps?).

Even with secure boot enabled on the motherboard, Leap will not boot in secure boot mode until it is explicitly enabled and the cert registered with mok.

Unfortunately, I’m getting a little cross eyed looking at this trying to figure out what I have and how to fill in the blanks:

For nvidia-driver-G0X (X >= 6):

mokutil --import /usr/share/nvidia-pubkeys/MOK-nvidia-driver-G0-<driver_version>-<kernel_flavor>.der --root-pw

For nvidia-gfxG0X (X < 6):

mokutil --import /usr/share/nvidia-pubkeys/MOK-nvidia-gfxG0-<driver_version>-<kernel_flavor>.der --root-pw

As far as my settings, I’m still on “Other OS” and “Legacy:”


Therefore, a successful boot of OSS 15.6 installation disk on the UEFI platform is a test? I would like to know more.

I have a grub 2 folder, no efi folder there.

UEFI booting requires an EFI partition. And if your disk is using DOS partitioning, then that needs to be a primary partition.

I was hoping that upon setting up the UEFI platform that upgrading to 15.6 would write that EFI partition for me. When I looked at PluginFlag:legacy bios · fwupd/fwupd Wiki · GitHub a while back, I thought it would be that easy. I would like to know how to insert that partition.

Hello @HealingMindNOS ,

In order to use secure boot, from first screen pic … you MUST choose “Windows UEFI mode”.

From second screen pic, you want either “UEFI driver first”, or possible “Ignore”. UEFI driver first will still allow for legacy boot. I am going to GUESS that “Ignore” means disable legacy boot. My bios presents that option somewhat differently, under a CSM menu.

I prefer to have legacy boot completely disabled, but it is not required to my knowledge.

Cheers

1 Like

It’s rarely anything like simple to add a primary partition, except during initial disk partitioning. Typically inserting a primary partition takes considerable mental effort. There needs to be freespace adjacent to an existing primary partition to do it. Usually there is none, so existing partition(s) need to be moved, deleted, resized and/or other disk configuration activity. Also, there are only 4 primary partition slots available per disk “table”, one of which is typically used for an extended. If all 4 are already in use, then a slot must be freed, meaning an existing primary must be deleted or moved into extended space as a logical, or possibly converted in place, freeing a primary slot. Without seeing output from fdisk -l and/or parted -l, we can’t begin to suggest a possible way forward.