Hello, I gave in and decided to get myself a gaming laptop, this is an Alienware 2015, 15" laptop.
I decided to give it 2 M2 sticks and 1 SSHD.
One M2 stick has W10 and formatted SSHD with 2 partitions. One Windows dedicated partition and one Shared.
One M2 stick has OpenSUSE LEAP 42.2.
I first had some issues even booting from installed LEAP 42.2 since the W10 was automatically installed as Intel Secure Boot setting, and AHCI boot incapable. Eventually, I was able to access the M2 with OpenSUSE on it. At the initial boot, the Boot Loader and Grub detected W10 Windows Boot Manager.
After checking LEAP installation(which I will ask for help in another thread), I gave it a reboot. At the reboot the Windows Boot Manager from GRUB menu disappeared. It seems to have been gone for good.
W10 seems 100% fine, I can boot from it fine. Also, if I interrupt the boot, and boot from OpenSUSE M2, it boots fine to OpenSUSE.
Since then, os-prober does not detect W10, and Boot Loader is not detecting W10 either.
I have no idea what’s going on. How did it detect the OS the first initial boot after fresh install, but never again? Could someone help me shove the Windows Boot Manager back to the Grub Menu please?
Sounds like MS Windows 10 was installed to boot with UEFI.
So openSUSE ist installed to be booted in Legacy mode.
You switched your UEFI to Legacy mode in order to boot openSUSE. So, did you switch it back to UEFI mode in order to boot MS Windows 10 again or can you boot MS Windows 10 while your UEFI is still switched to Legacy mode?
As far as i know you have to use UEFI boot mode for openSUSE as well if your MS Windows is installed in UEFI mode.
But there is no need to reinstall openSUSE in order to switch it from Legacy boot mode to UEFI boot mode.
Just a note, though strictly speaking you do not have to have a separate home it is recommended you have /home on its own partition because that isolates your data and settings from the system in case you want to switch OS or reinstall. Also DO NOT use a Windows partition for /home the Windows file systems are not designed for Linux and things will break :’(
can we set up the EFI for OpenSUSE after it has laready been installed with / and swap partitions only?
gogalthorp. I appreciate the suggestion for separate /home but personal history and experience taught me so far, due to the customization I do, having separate /home partition would be extremely inefficient for me compared to just cloning /home into a back up drive, because often distribution upgrade or changing distribution completely breaks the OS for me. I rather save/backup the data for specific computer to be installed specifically somewhere, but having a separate /home if anything has always given me grief due to unflexible size of partitions.
Reviewing this, should I really re-install and MAKE SURE that it is EFI mode? Also, could someone explain how to verify that, I usually always installed with / and swap, with just one SSD in at a time, and never had to change much from the installation configuration.
I do recall installing boot in MBR for my toughbook installation where a 500GB SSD holds all 2 OS + Shared partition.
To boot in EFI mode you must have a efi boot partition some where to handle the boot code handoff from the UEFI
Ways to know if using EFI boot
1 there is a /boot/efi directory
2 Yast-bootloader shows boot code to use grub2-efi not just grub2
If you do not have the above you boot legacy (MBR)
I think you can change by first setting to mounting the efi boot partition at /boot/efi in Yast Note you can have your own efi boot partition on the same drive as openSUSE or use the existing one and share with Windows. Note2 that an efi boot partition has special type EF00 that shows it is the EFI boot and is FAT32 formatted. Note3 if you want to use secure boot be sure to check the box for it.
then in the bootloader section change the boot code to grub2-efi and be sure scan for foreign OS box is checked that should reinstall grub in efi mode
No, /boot/efi of type ef00 and formatted vfat is a unique partition between 100~260MB (Think it can be up to 512MB) on a gpt type disk.
Then the system BIOS/UEFI will recognize and when the systems install, eg openSUSE, Win7 up if the system is a) set to UEFI booting and b) install media is booted from a medium that is designed to boot for a UEFI system. For example if a Win disk is prepared via say Rufus you can select either/both UEFI or Legacy (MBR) boot disks. The openSUSE install medium will take it’s lead from the BIOS settings UEFI/Legacy on what method to use.
So, from your output Windows is booting in uefi mode, so in your install you need to use /dev/sdc2, set the partition to /boot/efi and NOT TO FORMAT… Or create a partition on /dev/sdb say 100MB set the type to ef00 and format to vfat, then re-install…
NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT
sda 8:0 0 29.1G 0 disk
├─sda1 8:1 0 260M 0 part /boot/efi <- Common efi for SLE/WinX
├─sda2 8:2 0 16M 0 part <-WinX reserved
├─sda3 8:3 0 20.9G 0 part <- WinX
└─sda4 8:4 0 8G 0 part [SWAP] <- swap never used but there...
sdb 8:16 0 111.8G 0 disk
├─sdb1 8:17 0 40G 0 part / <- SLED 15
└─sdb2 8:18 0 71.8G 0 part /data <- My data (no /home...)