English Community

Lenovo NotebooksLenovo Yoga Series Notebooks
All Forum Topics
Options

2 Posts

08-22-2020

CH

6 Signins

35 Page Views

  • Posts: 2
  • Registered: ‎08-22-2020
  • Location: CH
  • Views: 35
  • Message 1 of 6

Yoga S940-IWL Dual-booting issues after latest BIOS update

2020-08-23, 13:25 PM

After recently updating the BIOS ("BIOS Update - 10 [64] - AKCN38WW") through Lenovo Vantage on my Yoga S940-IWL, dual-boot is flaky: after a Windows 10 session/reboot I get the Grub menu at boot, but after shutting down or rebooting Debian my computer boots (or reboots) directly into Windows without any kind of prompt.

 

After the BIOS update I was not too surprised to have to chroot into Debian to get Grub back, but that didn't do the trick.

 

I tried the BIOS Utility (F2 while booting) to reorder bootloader priority, but the changes I made in there didn't stick.

 

The bcdedit command inside Windows didn't help much (although another user with a similar issue had more luck, I followed his instructions except for the Ubuntu-specific part). At least since that point I can boot into Debian (but only if I boot Windows first!).

 

Also tried efibootmgr and rEFInd in Debian but that didn't make a difference. Here's a excellent post about these utilities.

 

Here's my current efibootmgr boot order. I don't think it should look like this but if I try to put something else than "0000" first it seems it gets overwritten.

 

BootOrder: 0000,0011,0016,0019,001A,0024,002B

Boot0010  Setup

Boot0011  Boot Menu

Boot0012  Diagnostic Splash

Boot0013  Regulatory Information

Boot0016* USB FDD:

Boot0019* USB CD:

Boot001A* USB LAN:

Boot0024* USB HDD:

Boot002C* NVMe:

 

Would reverting to the previous BIOS version be an option?

 

Any help appreciated, this is time-consuming.

 

MOD: Model added to title -Doc

Reply
Options

9 Posts

09-19-2020

CH

10 Signins

95 Page Views

  • Posts: 9
  • Registered: ‎09-19-2020
  • Location: CH
  • Views: 95
  • Message 2 of 6

Re:Dual-booting issues after latest BIOS update

2020-09-19, 21:22 PM

Hi,

 

 

 

I'm also dual-booting Windows and Ubuntu Linux on my S940.

And after each BIOS update I've had the same issue where the UEFI boot settings are somehow wiped.

 

Until now I managed to recover Ubuntu boot but booting into a live CD and updating grub.

 

 

 

What happens since July's BIOS update.

 

The system always boots by default into Windows (expected).

After rebooting I hit F12

This shows me:

1. nVME

 

Which boots into Windows.

 

This time I change the UEFI boot with bcdedit

 bcdedit /set "{bootmgr}" path \EFI\ubuntu\shimx64.efi

and reboot.

 

This brings back into Ubuntu. Hurra!

 

But checking UEFI boot status with :

 

root@s940:~# efibootmgr

BootCurrent: 0000

Timeout: 0 seconds

BootOrder: 0000,0016,0019,001A,001E,002C

Boot0010  Setup

Boot0011  Boot Menu

Boot0012  Diagnostic Splash

Boot0013  Regulatory Information

Boot0016* USB FDD:

Boot0019* USB CD:

Boot001A* USB LAN:

Boot001E* USB HDD:

Boot002C* NVMe:

 

I see that ubuntu boot loader is not enabled.

 

Trying to reboot: goes directly to Windows.

Windows still remembers the bcdedit config and applies it.

So when I reboot Windows and land again in grub.

 

I then tried different tricks:

 

1/

Reboot in Windows (which activates ubuntu)

Reboot into BIOS : ubuntu appears as first boot priority.

Reboot into BIOS : ubuntu is gone.

Reboot : goes straight back to Windows.

 

2/

Boot into Ubuntu (through Windows)

Install refind (custom graphical EFI boot loader)

Checking with bootctl shows what will happen at the next reboot:
 

root@s940:~# efibootmgr

BootCurrent: 0000

Timeout: 0 seconds

BootOrder: 0000,0000,002E,0030,0031,0032,0035

Boot0000* rEFInd Boot Manager

 

Reboot: refind loads and lets me choose between Windows, Grub, UEFI setup or boot straight into Ubuntu.

I don't choose anything and just Reboot (ctl-alt-del) : refind is gone, boot goes to Windows.

Rebooting in Ubuntu: bootctl shows that refind is indeed gone.

 

 

So all in all the new BIOS doesn't let us permanently change the boot order.

It works once and on the next reboot any change is lost.

 

Trying to disable Secure Boot or any other security settings in the BIOS doesn't change anything.

 

This leaves us with rolling back the BIOS firmware.

But as it looks we can't download the previous firmware version on Lenonvo's support site.

 

 

Reply
Options

9 Posts

09-19-2020

CH

10 Signins

95 Page Views

  • Posts: 9
  • Registered: ‎09-19-2020
  • Location: CH
  • Views: 95
  • Message 3 of 6

Re:Dual-booting issues after latest BIOS update

2020-09-22, 21:49 PM
Hi, Just letting you know that I was able to rollback my BIOS firmware to version AKCN37WW Which fixed the UEFI boot persistence issue. I have opened a ticket for this with Lenovo's support. Please do the same and ask for a fixed BIOS. Good luck! PS. At the same time I also have my touchpad that broke apparently following the BIOS upgrade. But the downgrade didn't fix this issue.
Reply
Options

3 Posts

09-23-2020

TR

2 Signins

30 Page Views

  • Posts: 3
  • Registered: ‎09-23-2020
  • Location: TR
  • Views: 30
  • Message 4 of 6

Dual-booting issues after latest BIOS update

2020-09-23, 6:39 AM
try Boot Repair application on Linux live from usb.
Reply
Options

9 Posts

09-19-2020

CH

10 Signins

95 Page Views

  • Posts: 9
  • Registered: ‎09-19-2020
  • Location: CH
  • Views: 95
  • Message 5 of 6

Dual-booting issues after latest BIOS update

2020-09-23, 7:41 AM
that's not helping. With the AKCN38WW firmware the UEFI boot order doesn't persist. You can change it once (from Windows with bcdedit or Linux with efitbootmgr/refind/boot-repair) But at the next reboot your change is gone. The only fix for this at the moment is rollback your firmware to AKCN37WW
Reply
Options

2 Posts

08-22-2020

CH

6 Signins

35 Page Views

  • Posts: 2
  • Registered: ‎08-22-2020
  • Location: CH
  • Views: 35
  • Message 6 of 6

Re:Dual-booting issues after latest BIOS update

2020-10-10, 16:44 PM

Thanks very much @moustik and sorry for the late reply, missed the new message notifications.

 

What you describe in your first post is exactly what I'm still experiencing. Now that I know that the issue isn't due to a mistake I made I'll also open a ticket with Lenovo support. And a rollback to the previous bios version is now my next step.

 

Regarding the touchpad issue ("i2c_designware controller timed out" and such), I've had it since the beginning with 5.x kernels. Tried different grub kernel parameters and modules blacklists but haven't found the perfect mix. FYI never had the issue with 4.19.x kernels. That's another problem entirely I know (but please do let me know if you find a fix) :)

 

@seydunaroj thanks for the suggestion but unfortunately that doesn't work, as moustik pointed out.

Reply
Forum Home

Community Guidelines

Please review our Guidelines before posting.

Learn More

Check out current deals!

Go Shop
X

Save

X

Delete