I installed OpenSUSE 42.2 beside Windows 10. So far no problems.
But after shutting down Opensuse and choosing Windows 10 in grub2 at the next startup my laptop freezes at the Lenovo Logo or at the “User - Welcome”-screen. To fix that I have to kill the laptop with longpressing the startbutton. On the next startup I again choose Win 10 and it starts normally.
The same problem appears everytime I want to switch from Suse to Win 10.
Does someone discovered the same problem or maybe can help me?
Thanks.
Laptop: Lenovo 500S-13ISK with i5 Skylake, Intel Graphics
(Before 42.2 I used Tumbleweed, but the daily updates were annoying, so I wanted to switch to 42.2 - but there should be no remains from the tumbleweed installation, because I completly reinstalled the laptop…)
Sorry, forgot to mention this. That’s the only help I found on Google, but it doesn’t help…
Because of your answer I now tried it a second time. The only difference I noticed is, that with fastboot on it freezes at the “User - Welcome”-screen and with fastboot off it already freezes at the Lenovo-Boot-Logo.
But maybe this is just coincidence?
You still need fastboot disabled, or dualbooting will just not work properly.
Once you have done that, then you will need to analyze the problem some more. Among problems: Did you install openSUSE in Legacy or UEFI? I am guessing that W10 is installed UEFI, and if you later installed openSUSE in Legacy, you will have a headache. Both OSes should be installed as UEFI or both as Legacy, they should not be mixed.
There are other possible causes of your problem, as well, but begin with disabling fastboot and checking your installs.
It is confusing since some UEFI have a fast boot option also. Any and all fast boot options In Windows or the UEFI(BIOS)must be off. I think both OS are installed using the same boot method or Windows would not even have tried to start
I didn’t know before, that there is a 2nd fastboot option in the bios. Now I turned it off, but also doesn’t help.
(With Tumbleweed both fastboot settings were “on”, with no noticeable issues. My only problem was the high update frequency…)
im not sure what completly reinstall means?
your problem is wierd, but here is another avenue of attack:
did you remove the directory from /boot/efi (?whatever the path is)
did you also remove the nvram entry using sudo efibootmgr?
if not you should check
[ps the most important fast boot option is the one in windows itself - double check this one]
I meant with reinstall, that I restore a complete HDD-backup which was created before I installed Tumbleweed.
So the /boot/efi folder only contains the boot entry for Win 10. I checked this in the BIOS after the restore finished.
Then I installed OpenSUSE 42.2 - now the BIOS contains boot entries for opensuse-secureboot and Win 10.
Opensuse-secureboot is set as boot-priority 1 so it boots into the grub2 bootloader.
Is it possible, that this boot error with Windows can be caused from the 4.4 kernel?
I initially choosed Tumbleweed because my wireless card wasn’t included in the 4.1 kernel from 42.1.
The last kernel version I used with Tumbleweed was 4.8 and 4.9 - both were working fine.
Hi
Seems that you quite well know what you are doing
Modern UEFI-BIOSs have a way to store boot entries, which is independent and seperate from the data on the (HDD) drives, these are entries in the ROM of the (UEFI) BIOS.
There has been a (command line) tool to remove those entries.
Don’t remember that now in detail, because it was years ago.
Output of efibootmgr:
BootCurrent: 0004
BootOrder: 0004, 0000, 0003,…
Boot0000* openSUSE
Boot0001* EFI Network 0 for IPv4
Boot0002* EFI Network 0 for IPv6
Boot0003* Windows Boot Manager
Boot0004* opensuse-secureboot
Boot2001* EFI USB Device
Boot2002* EFI DVD/CDROM
Boot2003* EFI Network
Today I installed Tumbleweed over 42.2 just to test it again. Now everything works fine again… I dont get it…
My idea with the kernel was caused by an experience I had with a Ubuntu Live CD on another PC this week.
After shutting down the Live System and rebooting Windows. Windows wasn’t able to connect to the network.
It showed no network adapter in the device manager. To fix that I had to go in the BIOS, switch WLAN from ON -> OFF -> ON to reactive the network adaptors.
So is it possible that some device or so is still “blocked” by Linux and this may freezes Windows?
The update frequency of Tumbleweed has decreased since Leap 42.2 came out.
Anyway, please read the following clear warning:
If you did run Tumbleweed with both fastboot settings “on” with no noticeable issues, this does not mean that you will not have issues in the future that way.
The point is that windoze doesn’t write all changes in the NTFS filesystem to the disk if fastboot is enabled.
So problems will arise if you should ever write data on a NTFS partition of a system configured that way.
In other words: your risk is that you may loose data or even shoot your windoze.
You will get no sign of any trouble beforehand, and you’ll only discover it when it’s too late.
Clear enough?
And, this is not something specific to openSUSE, but this is relevant for any other OS accessing your NTFS partition(s) of windoze 10 - i.e. any Linux, and even e.g. a windoze 7 installed on the same machine.
If you would like to remove openSUSE completely, then you’ll probably want to remove the boot entries in the BIOS ROM / BIOS static RAM using efibootmgr from some Linux live media - I installed one openSUSE the usual way on an USB stick, which is one possibility.
The thing with the WLAN difficulties you encountered is something completely different:
I had a similar problem after I unintendedly turned off WLAN with a hardware switch at the side of my DELL laptop.
The tool that helped me then was rfkill (command line as admin).
You have to actively install rfkill in opensuse, because it isn’t installed by default.
Besides, there just has been an update of GRUB2 in Leap 42.2.
So if GRUB2 is / has been the cause of the freezing that you observed then …
My only problem was the high update frequency…)
