Results 1 to 6 of 6

Thread: Multi-boot Menu: "Now You See It; now You Don't"

  1. #1

    Default Multi-boot Menu: "Now You See It; now You Don't"

    This has been going on now for a year. A Tumbleweed update with a new kernel wipes out the other OS listings in the boot menu - Win 10, Linux Mint. But not always. Sometimes the boot menu is intact after a kernel update.

    When the boot menu is erased (of the other OS's) I reboot into Tumbleweed and rerun YAST Bootloader.

    Can someone explain this phenomenon?

  2. #2
    Join Date
    Aug 2010
    Location
    Chicago suburbs
    Posts
    15,673
    Blog Entries
    3

    Default Re: Multi-boot Menu: "Now You See It; now You Don't"

    You haven't explained what you are doing.

    My boot menu is intact after Tumbleweed updates.
    openSUSE Leap 15.3; KDE Plasma 5.18.6;

  3. #3

    Default Re: Multi-boot Menu: "Now You See It; now You Don't"

    I'm running the updater when it displays updates are available.
    I've gotten used to running YAST bootloader after every update that installs a new kernel. But sometimes the multi-boot options are preserved after a kernel update.There is a text file in /boot/grub2 that mentions how a kernel update can wipe out the boot menu.

  4. #4
    Join Date
    Aug 2010
    Location
    Chicago suburbs
    Posts
    15,673
    Blog Entries
    3

    Default Re: Multi-boot Menu: "Now You See It; now You Don't"

    As far as I know, after a kernel update the program "/sbin/update-bootloader" is run. And that should run
    Code:
    grub2-mkconfig -o /boot/grub2/grub.cfg
    That completely regenerates the boot menu. It should be finding other linux systems by running "os-prober".

    If some of your other systems are encrypted, then "os-prober" may not find them.

    If you want to manually add entries to the menu, it's best to do that with "/etc/grub.d/40_custom"
    openSUSE Leap 15.3; KDE Plasma 5.18.6;

  5. #5

    Default Re: Multi-boot Menu: "Now You See It; now You Don't"

    Quote Originally Posted by nrickert View Post
    As far as I know, after a kernel update the program "/sbin/update-bootloader" is run. And that should run
    Code:
    grub2-mkconfig -o /boot/grub2/grub.cfg
    That completely regenerates the boot menu. It should be finding other linux systems by running "os-prober".

    If some of your other systems are encrypted, then "os-prober" may not find them.

    If you want to manually add entries to the menu, it's best to do that with "/etc/grub.d/40_custom"
    None of my other OS's are encrypted. Evidently, on both of my systems running Tumbleweed, the automatic running of grub2mkconfig is not happening after each kernel update, just sometimes. I know how to deal with this, but it is puzzling why this behavior is inconsistent.

  6. #6
    Join Date
    Jun 2008
    Location
    Groningen, Netherlands
    Posts
    20,925
    Blog Entries
    14

    Default Re: Multi-boot Menu: "Now You See It; now You Don't"

    Quote Originally Posted by Metapsych View Post
    I'm running the updater when it displays updates are available.
    I've gotten used to running YAST bootloader after every update that installs a new kernel. But sometimes the multi-boot options are preserved after a kernel update.There is a text file in /boot/grub2 that mentions how a kernel update can wipe out the boot menu.
    Using the updater? Don't. As per documentation,
    Code:
    zypper dup
    is the only way for TW,
    ° Appreciate my reply? Click the star and let me know why.

    ° Perfection is not gonna happen. No way.

    http://en.opensuse.org/User:Knurpht
    http://nl.opensuse.org/Gebruiker:Knurpht

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •