Page 1 of 3 123 LastLast
Results 1 to 10 of 21

Thread: GRUB problem after update to Tumbleweed 2019-01-15

  1. #1

    Default GRUB problem after update to Tumbleweed 2019-01-15

    Today I updated Tumbleweed for the first time this year, to 2015-01-15. Standard procedure, sudo zypper ref and zypper dup; used TTY. Tumbleweed had been fine today before the update.

    Now GRUB throws ”symbol grub_efi_allocate_fixed not found“. There is no way anymore for me to get out of GRUB and boot into Tumbleweed. I have Manjaro on the same machine, still booting fine from the same EFI partition and bootloader which Tumbleweed uses.

    I should say that my machine (HP EliteBook 8560w from 2011) has an early UEFI implementation. It requires to have bootx64.efi to be present in the Microsoft default place, /boot/efi/EFI/BOOT/.

    In addition, since an earlier update last year I found a fwupdx64.efi in the openSUSE Directory of the EFI partition. I didn‘t do anything with it.

    I‘m somewhat lost and would like to ask for your help.

  2. #2

    Default Re: GRUB problem after update to Tumbleweed 2019-01-15

    In detail: Booting from GRUB Menü unto Tumbleweed gets to the loading initial ramdisk, then throws the a.m. error and ”hit any key“, then into GRUB command mode.

  3. #3
    Join Date
    Aug 2010
    Location
    Chicago suburbs
    Posts
    12,767
    Blog Entries
    3

    Default Re: GRUB problem after update to Tumbleweed 2019-01-15

    I'm not sure what went wrong. I have not heard any other reports of this problem.

    It seems that you got as far as grub, so this is probably not a UEFI firmware issue.

    Are you using "btrfs"?

    Since you are able to boot manjaro, you should be able to add a boot entry for openSUSE in your manjaro boot menu. Perhaps you will have to add manually.
    openSUSE Leap 15.1; KDE Plasma 5;
    testing Leap 15.2Alpha

  4. #4

    Default Re: GRUB problem after update to Tumbleweed 2019-01-15

    Thanks a lot. Just ext4 for all roots and homes.

    If what you propose is good, then I think I should be able to point my UEFI to boot the original grubx64.efi in the openSUSE subdue of the EFI partition?

    Unfortunately, I have to be patient until Monday at my computer.

    In the meantime: Any other ideas and help? Thanks.

  5. #5
    Join Date
    Aug 2010
    Location
    Chicago suburbs
    Posts
    12,767
    Blog Entries
    3

    Default Re: GRUB problem after update to Tumbleweed 2019-01-15

    With "ext4", you should not have problems booting via manjaro.

    The default for openSUSE is to configure secure-boot support. You appear to not be using that. So I would suggest that you go into Yast bootloader, and uncheck the "secure-boot" support (if it is checked). That will leave one less thing to go wrong during booting.
    openSUSE Leap 15.1; KDE Plasma 5;
    testing Leap 15.2Alpha

  6. #6
    Join Date
    Aug 2010
    Location
    Chicago suburbs
    Posts
    12,767
    Blog Entries
    3

    Default Re: GRUB problem after update to Tumbleweed 2019-01-15

    I forgot to comment on "fwupdx64.efi". As far as I know, that is for updating the UEFI firmware, and should not affect your normal boot setup at all.
    openSUSE Leap 15.1; KDE Plasma 5;
    testing Leap 15.2Alpha

  7. #7
    Join Date
    Sep 2012
    Posts
    5,202

    Default Re: GRUB problem after update to Tumbleweed 2019-01-15

    Quote Originally Posted by 111MilesToGo View Post
    Now GRUB throws ”symbol grub_efi_allocate_fixed not found“.
    This symbol was introduced an 20th of December. Please show output of
    Code:
    efibootmgr -v
    grep -v '^#' /etc/default/gub 
    grep -v '^#' etc/sysconfig/bootloader
    ls -lR /boot/efi/EFI/
    ls -lR /boot/grub2
    As output is long, you may consider uploading to susepaste.org.

  8. #8

    Default Re: GRUB problem after update to Tumbleweed 2019-01-15

    Thanks to both of you! I‘ll be back on Monday.

    Some remarks, though:

    No Secure Boot. That check mark in Yast Create Bootloader was not touched manually, AFAIK.

    No serious error messages during zypper dup today as far as I could see in passing.

    Following your info that the symbol in question was introduced on Dec 20, I have a hypothesis that Tumbleweed with today’s update wrote a new and different grubx64.efi to /boot/efi/EFI/openSUSE/. If that were true, then it would be different from the existing /boot/efi/EFI/BOOT/bootx64.efi, which is the only one my PC can boot from without manual intervention, and which comes from an update before December. Maybe such a scenario causes my current boot failure. It might be solved by booting into Manjaro and copying beE/openSUSE/grubx64.efi over to beE/BOOT/bootx64.efi. For the past two years or so I had been careful enough to always do such copying after a zypper dup whenever Tumbleweed showed a different time stamp for grubx64.efi. Maybe today was my unlucky day - I have neglected to check and copy grubx64.efi, since in the past the various grubx64.efi files had been identical most of the time.

    But maybe this is not true, and another reason would need to be found. Maybe the grub config file would need to recreated. Maybe the initial ramdisk would need to be recreated. Maybe I would have to boot into Manjaro and give its grub menu an entry to boot Tumbleweed.

    I will dig into this on Monday. Hope you both will be available for further help!

  9. #9
    Join Date
    Aug 2010
    Location
    Chicago suburbs
    Posts
    12,767
    Blog Entries
    3

    Default Re: GRUB problem after update to Tumbleweed 2019-01-15

    Quote Originally Posted by 111MilesToGo View Post
    It might be solved by booting into Manjaro and copying beE/openSUSE/grubx64.efi over to beE/BOOT/bootx64.efi.
    Yes, that's worth trying. There's a good chance that it will solve the problem, though you won't know until you try it.
    openSUSE Leap 15.1; KDE Plasma 5;
    testing Leap 15.2Alpha

  10. #10

    Default Re: GRUB problem after update to Tumbleweed 2019-01-15

    Sigh, all solved. The issue was exactly what I figured it to be following your helpful comments,
    Quote Originally Posted by arvidjaar View Post
    This symbol was introduced an 20th of December. Please show output of Code:
    efibootmgr -v
    grep -v '^#' /etc/default/gub
    grep -v '^#' etc/sysconfig/bootloader
    ls -lR /boot/efi/EFI/
    ls -lR /boot/grub2
    As output is long, you may consider uploading to susepaste.org.
    and
    Quote Originally Posted by nrickert View Post
    "It might be solved by booting into Manjaro and copying beE/openSUSE/grubx64.efi over to beE/BOOT/bootx64.efi."
    Yes, that's worth trying. There's a good chance that it will solve the problem, though you won't know until you try it.
    I had missed the one step after updating that is essential with my peculiar UEFI hard and firmware, i.e. copying /boot/efi/EFI/opensuse/grubx64.efi over to /boot/efi/EFI/BOOT/bootx64.efi whenever Tumbleweed changes its /boot/efi/EFI/opensuse/grubx64.efi (check its timestamp).

    Lesson learnt! Always exert utmost diligence to do all steps when updating.


    Now, three questions come to my mind:

    (1) What does
    Quote Originally Posted by arvidjaar View Post
    This symbol was introduced an 20th of December.
    actually mean? Where was it introduced?

    (2) Until now, I thought all grubx64.efi's were created equal (for the same GRUB version, and except for pointing to its OS-specific config file, but having the same executable EFI code), but I seem to be mistaken. So, what's in a grubx64.efi file? What did change in Tumbleweed's grubx64.efi between Dec 20 and Jan 15? Maybe you could give a short explanatory summary; of course I did already dig deeper into the literature, but will have to continue.

    (3) I have a multiboot of two Linux's on my hard disk, Tumbleweed and Manjaro. Tumbleweed is the master, i.e. its /boot/efi/EFI/opensuse/grubx64.efi is copied to /boot/efi/EFI/BOOT/bootx64.efi, and that takes its configuration from Tumbleweed. Therein I have configfile inclusion (cf. here: https://forums.opensuse.org/showthre...erating-system) in order to boot Manjaro. On Tumbleweed, /etc/grub.d/40_custom reads
    Code:
    menuentry "Menüeinträge für Manjaro Linux" {
        set bootdir='hd0,gpt2'
        search --fs-uuid --set=bootdir a1b2c3d4-e5f6-a7b8-c9d0-a1b2d3e4f5g6
        configfile (${bootdir})/boot/grub/grub.cfg
    }
    So there is only one grubx64.efi (aka bootx64.efi) in action, the Tumbleweed one. Manjaro's /boot/efi/EFI/Manjaro/grubx64.efi - as as I understand it - is never used in my case. Correct??? Now, what would happen if Manjaro were to decide some day that its grubx64.efi shall be changed. Would it be possible that Tumbleweed's grubx64.efi turns out to be incompatible with Manjaro's? Would I be unable to boot Manjaro on that potential day? Similar to what happened to me within Tumbleweed between last December and the latest update 20190115.


    Thanks a lot to both of you for your helpful comments, past, present and future!

Page 1 of 3 123 LastLast

Posting Permissions

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