Dual Boot configuration for Windows 10 and openSUSE with full UEFI and Secureboot support?
Linux - NewbieThis Linux forum is for members that are new to Linux.
Just starting out and have a question?
If it is not in the man pages or the how-to's this is the place!
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
morten@morten:~$ suse su
No command 'suse' found, did you mean:
Command 'muse' from package 'muse' (universe)
Command 'fuse' from package 'fuse-emulator-sdl' (universe)
Command 'fuse' from package 'fuse-emulator-gtk' (universe)
suse: command not found
I have windows 10 and Ubuntu Mate on so far so good.
But when i try to install Suse it not add windows 10 to thh bootloader - how do to i correct that?
Do you mean that Windows 10 and Ubuntu Mate worked well in dual booting, with GRUB having entries for Win10 as well?
Since you installed the Suse last, I guess it is Suse's GRUB which shows up at the beginning. As it seems that Suse's GRUB cannot add an entry for your Windows, you can try to add it manually to /boot/grub/grub.cfg
Code:
menuentry 'Windows 10' {
set root='hdX,gptY'
chainloader /EFI/Windows/Boot/bootmgfw.efi
}
Replace hdX with your hard drive's label (e.g. if it is the first hard drive then it surely is hd0). Also replace gptY with the partition number corresponding to your EFI partition (e.g. gpt1 if it is the first partition).
If you find that there is no effect on the boot menu, just check grub's folder on the EFI partition. Some systems keep a grub.cfg there. Then you just copy the /boot/grub/grub.cfg there. Don't forget to make a backup of the working grub.cfg before you do anything .
Last edited by aragorn2101; 10-18-2017 at 03:39 AM.
morten@morten:~$ suse su
No command 'suse' found, did you mean:
Command 'muse' from package 'muse' (universe)
Command 'fuse' from package 'fuse-emulator-sdl' (universe)
Command 'fuse' from package 'fuse-emulator-gtk' (universe)
suse: command not found
Yes i can boot into opensuse.
suse su is incorrect.
Open the terminal in Open Suse and type:
Code:
su -
Hit Enter one time than put in your password and hit Enter.
Than type:
Code:
grub2-mkconfig -o /boot/grub2/grub.cfg
I'd be very surprised if this doesn't work. However, if it does than follow aragorn2101's instruction for adding the menu entry manually if need be.
-------------------------------------------------------------------------
another option is to let ubuntu control the booting by either going into the bios and changing the boot order to ubuntu or boot up ubuntu and reinstall ubuntu grub with: sudo grub-install and rerun
sudo update-grub in ubuntu to pick up the open suse in the ubuntu grub menu.
Last edited by colorpurple21859; 10-18-2017 at 09:24 AM.
As it seems that Suse's GRUB cannot add an entry for your Windows, you can try to add it manually to /boot/grub/grub.cfg
You aren't supposed to edit grub.cfg manually anymore as it is a generated file and will be overwritten next time. Custom entries need to be placed in the /etc/grub.d/40_custom file. Menu entries placed here will be permanent and are added to grub.cfg each time it is regenerated.
Also you aren't supposed to refer to drive letters directly anymore as these can change. You should use the UUID of the EFI partition to do a search.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.