So After zypper dup, winsows 10 boots instead of Tumbleweed.
This has happened to me before. The solution was always to then boot suse through my mobo bootmenu,.then go into yast, bootoptions, check if its set right and exit by clicking oke.
So I tried to do the same again but this time I got an error.
Uitvoeren van opdracht '"/usr/sbin/shim-install", "--config-file=/boot/grub2/grub.cfg"]]' mislukt.
Foutuitvoer: Installeren voor x86_64-efi-platform.
Installatie is afgerond. Er werden geen fouten gerapporteerd.
Could not prepare Boot variable: No space left on device
After some googling, I went into yast again and uncheck something about vram.
This helped to some extent, there was no error anymore, but after a reboot I see that bloody windows throbber again.
Not what I should see, a grub menu with tumbleweed.
If you edit each /etc/default/grub’s GRUB_DISTRIBUTOR= to include a unique string, such as “opensusetw” and GRUB_DISTRIBUTOR=“opensuse154”, then your /boot/efi/EFI/ directories will acquire directories opensusetw and opensuse154 when next the two Grubs have again been updated. After that, there won’t be any confusion in efibootmgr output if you remove the opensuse directory that each is stomping over the other in in the BIOS NVRAM. That ought to stop the BIOS from seeing the confusion as a reason to jump ship to the unique Windows EFI directory.
The above never happened to me, presumably because I figured out what I am doing. http://mistelberger.net/chillin.svg
When being confused it’s always a good idea to stick to the facts and post them in your comment:
6700K:~ # fdisk -lo Device,Size,Type
Disk /dev/sda: 465.76 GiB, 500107862016 bytes, 976773168 sectors
Disk model: Samsung SSD 850
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: gpt
Disk identifier: 90C1973B-4A41-4E96-85BA-B7358EA77CCC
Device Size Type
/dev/sda1 101M EFI System
/dev/sda2 30G Linux filesystem
/dev/sda3 30G Linux filesystem
/dev/sda4 106G Linux filesystem
/dev/sda5 48.8G Linux filesystem
/dev/sda6 16M Microsoft reserved
/dev/sda7 29.7G Linux filesystem
/dev/sda8 59.6G Linux filesystem
/dev/sda9 30G Linux filesystem
/dev/sda10 16G Linux swap
/dev/sda11 56.3G Linux filesystem
/dev/sda12 58.7G Microsoft basic data
/dev/sda13 524M Windows recovery environment
Restarting Windows instead of shutting it down does change the boot order. To fix this you may boot into Windows and go from there to UEFI boot menu. Move Tumbleweed to the top, save the change and quit. This will fix the boot order and queue Windows as the second entry of the boot order:
Last night I started to wonder, but you already answered the thing I was wondering about.
If I booted 0006 it is the right hard disk, because I selected the opensuse tumbleweed disk in my bios boot menu.
I think, I did not have to boot windows, because the way my pc is set up.
First screen you see at my pc, is a screen with an asrock logo and then bottom right 4 lines.
F something to enter the UEFI,
F11 to enter the boot menu, and two more lines.
Then if all is well, grub pops up after 8 seconds.
I do know however some pc are setup so you will not see that first screen.
Then you will have to go into windows and from there enter the UEFI.
Learned something new, before I used to fix this through YAST, but for reason unknown (and not important), that did not work this time.
Totally happy again, if I just turn on my pc, Tumbleweed will start. If I want to boot windows I need to select it in grub.
I am starting to wonder more and more if my next pc will still be dual boot Linux / Windows.
It might be dual boot but no more windows.
Last week had a big issue
I tried to start windows, and had a lot of trouble to get my password right. lol!
This proofs mostly how long ago it was I had booted windows. it took around 1.5 hours for windows to update… ( do not turn of your pc… >:( )
Log in to windows once, and you instantly remember why you went to Linux.