When your system is EFI and it boots Windows in EFI, you should install openSUSE in EFI (and the installer should do that automatically).
All should be the same.
When your system is not EFI and then your Windows is not EFI and your openSUSE should also be not EFI (again this should be automatically).
When, for whatever reason you want to change your system from not EFI to EFI (and the firmware allows this), then you should install everything new in EFI. Same of course the other way.
From your story above, I am not sure you followed these simple rules (that are normally followed by the installation automatically).
When I installed opensuse for the first time, I didn’t provide separate partition for /boot/efi. This made my complete system unbootable(no Linux and No windows)
I agree that whether efi or not efi, the installation procedure should have take care automatically.
There is an option in my HP envy laptop bios to enable/disable legacy mode. Trying both enable and disable options always showed no menus at bottom when booting from USB pendrive. It always showed “c-command E-edit”
So I went ahead and create separate FAT partitions for /boot/efi.
I didn’t had separate EFI partition earlier when I had dual boot Windows 7 and leap 42
parted command showed below results
GNU Parted 3.2
Using /dev/sda
Welcome to GNU Parted! Type ‘help’ to view a list of commands.
(parted) p
Model: ATA Hitachi HTS54505 (scsi)
Disk /dev/sda: 500GB
Sector size (logical/physical): 512B/4096B
Partition Table: msdos
Disk Flags:
I google and tried one solution to know whether efi or not
the folder: /sys/firmware/efi is present in my system which validates the EFI system.
Now looking at results of parted
parted command showed below results of parted below, is first partition of 209 mb(ntfs) is efi partition from windows ???
GNU Parted 3.2
Using /dev/sda
Welcome to GNU Parted! Type ‘help’ to view a list of commands.
(parted) p
Model: ATA Hitachi HTS54505 (scsi)
Disk /dev/sda: 500GB
Sector size (logical/physical): 512B/4096B
Partition Table: msdos
Disk Flags:
There is an important, but not easy to find feature on the forums.
Please in the future use CODE tags around copied/pasted computer text in a post. It is the # button in the tool bar of the post editor. When applicable copy/paste complete, that is including the prompt, the command, the output and the next prompt.
Then, you show an msdos partitioned disk, not a gpt one. So I doubt that the system is using EFI. And that is supported by the fact that you say there wasn’t an EFI partition originally.
When that is all correct, IMHO you should not even try to go for EFI. I have no idea what you did and if it broke something. As I am not using multi boot with Windows and as I have only one EFI system, that was handled by the installer without problems, we better wait for other people that know more about this.
Enable legacy mode is not the same as boot legacy mode.
I have two computers with UEFI support. If I disable legacy, then I can only boot UEFI. However, if I enable legacy, I can still boot UEFI. On one of my computers (a Dell), I hit F12 during boot. And it lists both UEFI booting options and legacy booting options. I can choose either.
On the other computer (a Lenovo), I can set it to “prefer UEFI” or to “prefer CSM”. If I want legacy boot, I set it to prefer CSM.
I don’t know how to set your computer to boot the installer in legacy mode. There is probably a setting if you look for it. From your description, you booted the installer in UEFI mode.
It should also be possible to switch to legacy booting. But I have not tested that with Leap 15.0, so I don’t know if it works. The trick would be to run Yast bootloader, and change from using “grub2-efi” to just using “grub2”. If you do that, you will probably get scary sounding warnings.
If I have time, I’ll experiment with that later today (in a VM) to see whether it still works.
@hcvv I will follow your suggestions in future…Thanks @nrickert I will try booting in legacy mode according to your suggestions… and report status soon
I don’t know how to set your computer to boot the installer in legacy mode. There is probably a setting if you look for it. From your description, you booted the installer in UEFI mode.
As told earlier, the only setting in BIOS is to enable/diable legacy mode(along with boot orders for both legacy/EFI modes separately) But it was also mentioned there that when both are available and even if legacy mode is enabled, EFI mode will be given preference. That’s why for me if always booted in EFI mode.
It should also be possible to switch to legacy booting. But I have not tested that with Leap 15.0, so I don’t know if it works…
During installation setup I didn’t find any option which allowed to choose between legacy/EFI mode
For installed opensuse leap 15, we can always open yast and open bootloader option and try to change to grub2 etc, but I am scared trying that option because it may break even single OS(opensuse) booting also(I tried something like that yesterday and as a result leap 15 was unable to boot. So I reinstalled leap 15 again).
I can only tell you what I would do, in the same circumstances. I cannot guarantee that it won’t break something (such as making it unbootable), although I think it will work.
Before I start, I need to know more about your computer. Is there only one hard drive, or are there two hard drives?
If there is only one hard drive, is that the one described in post #6 in this thread?
I’m asking partly because you mentioned creating an EFI partition, but I am unable to work out which is the EFI partition.
The above partition #8 is the one I created for /boot/efi while installing opensuse leap 15
Also I was mentioning about above partition #1 in my post #6
I have the same problem everytime I do a new install. The solution was quite simple:
Boot openSUSE Leap
Go to Yast-System-Boot loader-Boot loader option Tab-Set a new Timeout in Seconds.
Save
Reboot
The idea is that it will redetect foreigner OSes and it will add them to the boot menu.
DO NOT CHANGE ANYTHING ELSE !
Waiting for your feedback.
Be sure fast boot is off in Windows. Also no “Dynamic disks” set in Windows If either is true Linux can not see the Windows partition thus can not boot to Windows.
From the output it appears you have a DOS partitioned drive and there fore can not use a EFI boot. Since there did not exist a EFI boot partition for Windows it must have been installed in MBR boot mode and you can not chain between two OS if they use different boot methods. Also MBR boot requires a boot flag and I don’t see one. SO not sure exactly how you managed this.
ubiroute@linux-1hcj:~> /usr/sbin/efibootmgr
BootCurrent: 0000
Timeout: 0 seconds
BootOrder: 0001,3000,2001,2002,2003
Boot0000* EFI HDD Device
Boot0001* opensuse-secureboot
Boot0002* Notebook Hard Drive
Boot2001* USB Drive (UEFI)
Boot3000* Internal Hard Disk or Solid State Disk
ubiroute@linux-1hcj:~>