Was this your first time installing multiple operating systems on the same PC?
Try running efibootmgr. If you get a ‘not installed’ response, you’ve installed TW in legacy mode. For both to be bootable, Windows and Linux must both be installed in the same mode, either UEFI, or legacy (enabled via CSM setting in BIOS setup). If CSM is enabled, disable it and reinstall TW.
The most likely explanation, is that Windows is using UEFI booting, but you installed Tumbleweed for legacy booting. This might be fixable without complete reinstall, but the reinstall is probably easier.
There should not be such a partition unless you installed Tumbleweed for legacy boot.
To further check, try:
grep LOADER_TYPE /etc/sysconfig/bootloader
For UEFI booting, that should show the loader type as “grub2-efi”, but it probably shows just “grub2”
Thank you,
The reinstall with EPI did it. The error was mine. I have installed multiple times, but all as legacy. I wasn’t familiar with the EPI boot. I was installing this on my daughter’s computer.
Other than to be able to dual boot to a newer windoze system, is there any other reason to install the EPI version verses legacy?
Drives containing system partitions can move between headers on the main board and between machines without making changes. Removing a drive from the case won’t cause any trouble.
Thank you for the insight. The legacy is all I knew about and have always installed that way. Your comments above are great answers, but especially the drive note. That has driven me nuts for years.
Next question,
Can I simply reinstall the bootloader from Legacy to EPI or do I have to reinstall the the whole deal? I am now working on my computer. I am starting from scratch with two new hard drives. I finished the Legacy install, but now want to change it to EPI. I am open to a full reinstall since it is early in the process if that is the best answer.
boot installation media in UEFI mode to rescue mode
mount /dev/<rootdevicename|volumelabel|UUID> /mnt
mount -o bind /dev /mnt/dev
mount -o bind /sys /mnt/sys
mount -o bind /proc /mnt/proc
chroot /mnt
mount -a
At this point you are running the installed system with a few limitations. You can install and remove software, reconfigure most things. So at this point grub2-efi needs to be installed if it hasn’t been already, and the ESP partition needs to be added to /etc/fstab if it isn’t already there. This can be done manually with zypper and your favorite text editor using elevated permissions, or with YaST. YaST will conveniently update your boot loader after you select “probe foreign OS”, or make any other change if it was already selected. Before rebooting, verify success:
(sudo) efibootmgr
If there is an opensuse entry listed ahead of the windows entry, you should be good to reboot normally, newly in UEFI mode, with an entry in Grub for Windows.
Fo me it’s difficult to remember all the detail of what I have done. So I write up and revise it upon important changes, such as switching from legacy to uefi bios.
This should have been written as ‘…efibootmgr and grub2-efi…’. Not likely one would have already been installed and not the other, and they might not be mutually dependent.
I am trying to install a linux only system, but cannot get the installation to accept grub2-efi as an option.
It shows in red, under the Booting at the installation summary at the end:
Unsupported combination of hardware platform x86_64 and bootloader grub2-efi
Additionally, at the end of setting up the Partitions an error shows stating a Bios boot partition is needed. It is set up already. I have not seen this message when installing in the past.
Frustrating!
The only OS being installed is OpenSuse with Cinnamon.
Using a separate partition for /home
Hi
I would boot into a rescue system and pre-allocated the disk with gdisk…
Here is a better example from an ssd, the info is just parted output…
gdisk -l /dev/sda
GPT fdisk (gdisk) version 1.0.1
Partition table scan:
MBR: protective
BSD: not present
APM: not present
GPT: present
Found valid GPT with protective MBR; using GPT.
Disk /dev/sda: 234441648 sectors, 111.8 GiB
Logical sector size: 512 bytes
Disk identifier (GUID): 9ACEE01D-A680-489B-B0B5-9C56E3C655DB
Partition table holds up to 128 entries
First usable sector is 34, last usable sector is 234441614
Partitions will be aligned on 2048-sector boundaries
Total free space is 2014 sectors (1007.0 KiB)
Number Start (sector) End (sector) Size Code Name
1 2048 534527 260.0 MiB 0700 EFI system partition
2 534528 105392127 50.0 GiB 8300 Linux filesystem
3 105392128 231221247 60.0 GiB 8300 Linux filesystem
4 231221248 234441614 1.5 GiB 8200 Linux swap
parted -l /dev/sda
Model: ATA Crucial_CT120M50 (scsi)
Disk /dev/sda: 120GB
Sector size (logical/physical): 512B/4096B
Partition Table: gpt
Disk Flags:
Number Start End Size File system Name Flags
1 1049kB 274MB 273MB fat16 EFI system partition msftdata
2 274MB 54.0GB 53.7GB btrfs Linux filesystem
3 54.0GB 118GB 64.4GB xfs Linux filesystem
4 118GB 120GB 1649MB linux-swap(v1) Linux swap swap
I have both rescue and g-parted disks
Between the two, you recommend the rescue?
I am installing a new system on this SSD, so is there anything to rescue?
I haven’t used the rescue disk for years, I am not quite sure what you mean by:
“into a rescue system and pre-allocated the disk with gdisk…”
clarifying, I am still in the installation tool, process.