Recurring Boot menu After reboot from Windows?

Hey guys I just freshly installed EOS alongside Win11 23H2. I chose windows existing /boot/efi as my boot partition. And i checked for double grub menus and can confirm there is none. There is no chainloading in grub config as well.

The recurring grub only occurs when trying to boot Linux (both latest and LTS kernels). Its the same grub with my custom configurations on /etc/default/grub. Windows booting happens without any problems.

What I’m experiencing is…

  • If I boot into windows and reboot - Then If i select linux the kernel starts to load (with mounting partitions starting services etc) Then the laptop reboots the grub again And then I have to chose linux again to successfully log in.
  • If I boot into windows then Power off completely then no prob. Upon next power on of laptop I only get one grub for linux.
  • If I reboot from windows once no matter how many time I boot into Linux and restart too, the issue persists until a shutdown.
  • I have set the previous booted entry as default as well. This works after rebooting from Linux but after rebooting from Windows it does not point to the last booted entry (windows)

Something I have noticed is every time this happens at the first kernel loading I get a message “A start job for network manager is running” for like a 1 second. Then it reboots to the 2nd grub. (Or else at the start of network services there is a very slight noticeable hang). I have turned off Both Hibernation and Fast startup as well. It seemed like the failed load suddenly stops at network services I dont see the Account Authorize services starts at failed boot attempts. But I do see them at the 2nd successful attempt.

**One other thing to consider is: The windows 11 as well as my firmware does not support s3 sleep. And I have to use modern standby which maintains network connection while laptop is sleep. I thought this might cause that network manager start delay. Maybe that’s why when Rebooting I encounter this issue.

I appreciate your thought and any help regarding this issue. thanks!

Is there any other Linux system except this new EnOS, or was ever any Linux system installed on this workstation?

You should provide some technical info, as your description is not helping clearly identify the problem.

For example:

inxi -Faz
journalctl -b -p3
sudo fdisk -l
lsblk -f

Oh sorry my bad. Here are the Outputs

inxi -Faz
fdisk -l
lsblk -f
journalctl -b -p3
efibootmgr -v

And no I have not installed nor tried to install any other OS other than EOS apart from windows (which came preinstalled). EOS installation was one time too there were no unsuccessful attempts as well.

Also i have observed that it does not go into another grub it actually restarts right at the start of network manager service start.

Thank you for the reply

When multi-booting with WinOS, sometimes, with some laptops, network devices are not released from Windows. This is a known issue. When this happens, and Linux manages to boot successfully, some network features (ethernet, wifi, bluetooth, etc.) may not function (being hard-blocked).

Your case looks very similar, with the difference that the second (re)boot manages to finally release the network hardware. I believe that in case you had booted in EnOS with one reboot, you would have issues with some network feature.

All this aligns with your report about s3 sleep. It might be the source of the problem (vendor’s firmware).
I would suggest you look into any available settings in the BIOS for sleep modes, network/hardware options, or ask your vendor’s support. Lenovo is generally Linux-friendly, and they might welcome feedback about this inconveniency.

Nevertheless, for now it seems an easy fix to just use the successful method to boot Linux. :point_down:

I see, i thought that might be the caee too… Thank you for the details you provided. I didn’t know the cause and from my observations and your reply I think not releasing the network indeed might be the problem.

I did check in BIOS for such settings and I could not find them too.

Thank you for your time! at least now I’m confident of the reason for this.

1 Like

This topic was automatically closed 2 days after the last reply. New replies are no longer allowed.