Skip to content

PC boots into boot-manager with a 90s timeout, even if timeout is set to 0 #9

Description

@gweeeeeeeeeen

Describe the bug
At startup, the computer boots into the boot manager with a 90 seconds timeout. Typing sudo clr-boot-manager set-timeout 0 doesn't make it disappear. Trying to change the timeout to 5 seconds doesn't change the 90 seconds timeout either, even after sudo clr-boot-manager update. I also tried sudo clr-boot-manager set-kernel com.solus-project.current.6.14.4-318 without any change.

To Reproduce
Steps to reproduce the behavior:

  1. Boot the computer
  2. The computer boots into the boot-manager
  3. Type commands sudo clr-boot-manager set timeout 0 or sudo clr-boot-manager set timeout 5 in a terminal
  4. Reboot

Expected behavior
If timeout is set at 0, PC should boot in the desktop environment directly. if set at 5, there should be a 5 seconds timeout.

Environment (please complete the following information):

  • Solus Solus 4.7 Endurance
  • Kernel: com.solus-project.current.6.14.4-318
  • clr-boot-manager Version: 3.6.0

Additional context

Command

eopkg li | grep linux-lts
sudo clr-boot-manager list-kernels
cat /boot/loader/loader.conf
ls /boot/EFI/com.solus-project/

gives

* com.solus-project.current.6.14.4-318
default Solus-current-6.14.4-318.conf
bootloaderx64.efi  initrd-com.solus-project.current.6.14.4-318
BOOTX64.CSV        kernel-com.solus-project.current.6.14.4-318
grubx64.efi        mmx64.efi

More info could be found here, on Solus forum: https://discuss.getsol.us/d/11365-how-to-open-solus-directly-in-my-de/11

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    Projects

    • Status
      Ready

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions