Page 3 of 5 FirstFirst 12345 LastLast
Results 21 to 30 of 42

Thread: Today's TW zypper dup -l wipes grub and boots to white screen????

  1. #21

    Default Re: Today's TW zypper dup -l wipes grub and boots to white screen????

    Quote Originally Posted by nrickert View Post
    I don't really know what is the actual problem. So this is a workaround rather than a fix. And yes, doing it that way from the command line might be easier.
    @nrickert:

    OK, thanks for the reply . . . yes, I don't know what the problem is either . . . but, there is a problem . . . and from the bug reporting I don't think I'm alone on it.

    @karlmistelberger:

    And thanks to you for stopping by, glad your multi-boot set up is working well . . . I'm away from those two computers that did have a problem with the only whiteness issue for awhile, I'll try out your suggestions, both of you gents, when I get back to them.

  2. #22

    Default Re: Today's TW zypper dup -l wipes grub and boots to white screen????

    Folks:

    Still trying to get a handle on the "Why is this happening to me?" question, before I start running commands. Tried several attempts at "os-prober" and chrooting over into TW to run os-prober, which has worked in the past when grub items got wiped, so far nothing is working. I took a look at "man efibootmgr" and tried to delete dups . . . not sure if I want to set "Boot current" to one of the grub choices listed?? Right now the only choice when cold booting is Linux Mint, which I had tried to run another "grub2-mkconfig" from my Gecko partition where I wound up when I used SG2 disk to boot into a "vmlinuz" option . . . . Previous to the recent zypper dup I could boot the machine and the grub menu would appear and it would . . . work to select any of the linux distros, now only system to boot is Linux Mint, which I don't think was the last install to go into the machine????

    Code:
    sudo efibootmgr -D
    [sudo] password:            
    BootCurrent: 0010
    BootOrder: 0010,0008,0000,000F,000A,0006,0005,0004,0007,000E,000C,000B,0009,0080,000D,0003,0001,0002
    Boot0000* ubuntu
    Boot0001* opensusetw
    Boot0002* grub
    Boot0003* lubuntu1910
    Boot0004* grub-secureboot
    Boot0005* opensuse-secureboot
    Boot0006* tumbleweed-secureboot
    Boot0007* opensusetw-secureboot
    Boot0008* ubuntu
    Boot0009* ubuntu
    Boot000A* opensusetw-secureboot
    Boot000B* opensuse-secureboot
    Boot000C* tumbleweed-secureboot
    Boot000D* Debian
    Boot000E* debian
    Boot000F* ubuntu
    Boot0010* ubuntu
    Boot0080* Mac OS X
    Boot0081* Mac OS X
    Boot0082* 
    BootFFFF*

  3. #23
    Join Date
    Jun 2008
    Location
    Podunk
    Posts
    31,295
    Blog Entries
    15

    Default Re: Today's TW zypper dup -l wipes grub and boots to white screen????

    Quote Originally Posted by non_space View Post
    Folks:

    Still trying to get a handle on the "Why is this happening to me?" question, before I start running commands. Tried several attempts at "os-prober" and chrooting over into TW to run os-prober, which has worked in the past when grub items got wiped, so far nothing is working. I took a look at "man efibootmgr" and tried to delete dups . . . not sure if I want to set "Boot current" to one of the grub choices listed?? Right now the only choice when cold booting is Linux Mint, which I had tried to run another "grub2-mkconfig" from my Gecko partition where I wound up when I used SG2 disk to boot into a "vmlinuz" option . . . . Previous to the recent zypper dup I could boot the machine and the grub menu would appear and it would . . . work to select any of the linux distros, now only system to boot is Linux Mint, which I don't think was the last install to go into the machine????

    Code:
    sudo efibootmgr -D
    [sudo] password:            
    BootCurrent: 0010
    BootOrder: 0010,0008,0000,000F,000A,0006,0005,0004,0007,000E,000C,000B,0009,0080,000D,0003,0001,0002
    Boot0000* ubuntu
    Boot0001* opensusetw
    Boot0002* grub
    Boot0003* lubuntu1910
    Boot0004* grub-secureboot
    Boot0005* opensuse-secureboot
    Boot0006* tumbleweed-secureboot
    Boot0007* opensusetw-secureboot
    Boot0008* ubuntu
    Boot0009* ubuntu
    Boot000A* opensusetw-secureboot
    Boot000B* opensuse-secureboot
    Boot000C* tumbleweed-secureboot
    Boot000D* Debian
    Boot000E* debian
    Boot000F* ubuntu
    Boot0010* ubuntu
    Boot0080* Mac OS X
    Boot0081* Mac OS X
    Boot0082* 
    BootFFFF*
    Hi
    You need to show the verbose output
    Cheers Malcolm °¿° SUSE Knowledge Partner (Linux Counter #276890)
    SUSE SLE, openSUSE Leap/Tumbleweed (x86_64) | GNOME DE
    If you find this post helpful and are logged into the web interface,
    please show your appreciation and click on the star below... Thanks!

  4. #24

    Default Re: Today's TW zypper dup -l wipes grub and boots to white screen????

    Quote Originally Posted by malcolmlewis View Post
    Hi
    You need to show the verbose output
    @malcolmlewis:

    Thanks for the reply, managed to get back into TW and running the suggested command shows:

    Code:
    BootCurrent: 0000
    BootOrder: 0010,0008,0000,000F,000A,0006,0005,0004,0007,000E,000C,000B,0009,0080,000D,0003,0001,0002
    Boot0000* ubuntu    HD(1,GPT,7f39c61b-b9d1-4378-8478-a5e99ae6079d,0x28,0x64000)/File(\EFI\ubuntu\shimx64.efi)
    Boot0001* opensusetw    HD(1,GPT,0d8470db-279c-4890-8cdb-8af7d48ab8c4,0x28,0x64000)/File(\EFI\opensusetw\grubx64.efi)
    Boot0002* grub    HD(1,GPT,7f39c61b-b9d1-4378-8478-a5e99ae6079d,0x28,0x64000)/File(\EFI\grub\grubx64.efi)
    Boot0003* lubuntu1910    HD(1,GPT,916b2a9f-8722-4501-a243-815ec3f629c6,0x28,0x64000)/File(\EFI\lubuntu1910\shimx64.efi)
    Boot0004* grub-secureboot    HD(1,GPT,7f39c61b-b9d1-4378-8478-a5e99ae6079d,0x28,0x64000)/File(\EFI\grub\shim.efi)
    Boot0005* opensuse-secureboot    HD(1,GPT,7f39c61b-b9d1-4378-8478-a5e99ae6079d,0x28,0x64000)/File(\EFI\opensuse\shim.efi)
    Boot0006* tumbleweed-secureboot    HD(1,GPT,7f39c61b-b9d1-4378-8478-a5e99ae6079d,0x28,0x64000)/File(\EFI\tumbleweed\shim.efi)
    Boot0007* opensusetw-secureboot    HD(1,GPT,0d8470db-279c-4890-8cdb-8af7d48ab8c4,0x28,0x64000)/File(\EFI\opensusetw\shim.efi)
    Boot0008* ubuntu    HD(1,GPT,916b2a9f-8722-4501-a243-815ec3f629c6,0x28,0x64000)/File(\EFI\ubuntu\shimx64.efi)
    Boot0009* ubuntu    HD(1,GPT,0d8470db-279c-4890-8cdb-8af7d48ab8c4,0x28,0x64000)/File(\EFI\ubuntu\shimx64.efi)
    Boot000A* opensusetw-secureboot    HD(1,GPT,7f39c61b-b9d1-4378-8478-a5e99ae6079d,0x28,0x64000)/File(\EFI\opensusetw\shim.efi)
    Boot000B* opensuse-secureboot    HD(1,GPT,0d8470db-279c-4890-8cdb-8af7d48ab8c4,0x28,0x64000)/File(\EFI\opensuse\shim.efi)
    Boot000C* tumbleweed-secureboot    HD(1,GPT,0d8470db-279c-4890-8cdb-8af7d48ab8c4,0x28,0x64000)/File(\EFI\tumbleweed\shim.efi)
    Boot000D* Debian    HD(1,GPT,0d8470db-279c-4890-8cdb-8af7d48ab8c4,0x28,0x64000)/File(\EFI\Debian\shimx64.efi)
    Boot000E* debian    HD(1,GPT,0d8470db-279c-4890-8cdb-8af7d48ab8c4,0x28,0x64000)/File(\EFI\Debian\shimx64.efi)
    Boot000F* ubuntu    HD(1,GPT,7f39c61b-b9d1-4378-8478-a5e99ae6079d,0x28,0x64000)/File(\EFI\lubuntu1910\shimx64.efi)
    Boot0010* ubuntu    HD(1,GPT,916b2a9f-8722-4501-a243-815ec3f629c6,0x28,0x64000)/File(\EFI\lubuntu1910\shimx64.efi)
    Boot0080* Mac OS X    PciRoot(0x0)/Pci(0x1f,0x2)/Sata(2,0,0)/HD(2,GPT,961fdd8f-5b94-4e90-a090-6a1d9836fb58,0x64028,0x26bd5aa8)
    Boot0081* Mac OS X    PciRoot(0x0)/Pci(0x1f,0x2)/Sata(3,0,0)/HD(2,GPT,3447e9e0-204a-414f-a226-9f19fa88ef29,0x64028,0x1d40ffb8)
    Boot0082*     PciRoot(0x0)/Pci(0x1f,0x2)/Sata(2,0,0)/HD(2,GPT,961fdd8f-5b94-4e90-a090-6a1d9836fb58,0x64028,0x26bd5aa8)/File(\System\Library\CoreServices\boot.efi)
    BootFFFF*     PciRoot(0x0)/Pci(0x1f,0x2)/Sata(0,0,0)/HD(3,0,00000000000000000000000000000000,0x5d5,0xf79)/File(\System\Library\CoreServices\boot.efi)

  5. #25
    Join Date
    Jun 2008
    Location
    Podunk
    Posts
    31,295
    Blog Entries
    15

    Default Re: Today's TW zypper dup -l wipes grub and boots to white screen????

    Hi
    I see 3 and 10 are duplicates, can you show the disk structure for the EFI directory...

    Code:
    tree /boot/efi/EFI
    Cheers Malcolm °¿° SUSE Knowledge Partner (Linux Counter #276890)
    SUSE SLE, openSUSE Leap/Tumbleweed (x86_64) | GNOME DE
    If you find this post helpful and are logged into the web interface,
    please show your appreciation and click on the star below... Thanks!

  6. #26

    Default Re: Today's TW zypper dup -l wipes grub and boots to white screen????

    Quote Originally Posted by malcolmlewis View Post
    Hi
    I see 3 and 10 are duplicates, can you show the disk structure for the EFI directory...

    Code:
    tree /boot/efi/EFI
    Code:
    tree /boot/efi/EFI
    /boot/efi/EFI
    ├── APPLE
    │   └── EXTENSIONS
    │       └── Firmware.scap
    ├── BOOT
    │   ├── BOOTX64.EFI
    │   ├── fallback.efi
    │   ├── fbx64.efi
    │   ├── grub.cfg
    │   ├── grub.efi
    │   ├── mmx64.efi
    │   └── MokManager.efi
    ├── Debian
    │   ├── BOOTX64.CSV
    │   ├── fbx64.efi
    │   ├── grub.cfg
    │   ├── grubx64.efi
    │   ├── mmx64.efi
    │   └── shimx64.efi
    ├── opensuse
    │   ├── boot.csv
    │   ├── grub.cfg
    │   ├── grub.efi
    │   ├── grubx64.efi
    │   ├── MokManager.efi
    │   └── shim.efi
    ├── opensusetw
    │   ├── boot.csv
    │   ├── grub.cfg
    │   ├── grub.efi
    │   ├── grubx64.efi
    │   ├── MokManager.efi
    │   └── shim.efi
    ├── tumbleweed
    │   ├── boot.csv
    │   ├── grub.cfg
    │   ├── grub.efi
    │   ├── grubx64.efi
    │   ├── MokManager.efi
    │   └── shim.efi
    └── ubuntu
        ├── BOOTX64.CSV
        ├── grub.cfg
        ├── grubx64.efi
        ├── mmx64.efi
        └── shimx64.efi
    
    8 directories, 37 files

  7. #27
    Join Date
    Jun 2008
    Location
    Podunk
    Posts
    31,295
    Blog Entries
    15

    Default Re: Today's TW zypper dup -l wipes grub and boots to white screen????

    Hi
    I suspect it's just conflicts when efi entries created... two different disk ID's A and 7 for the same thing...

    Code:
    Boot0005* opensuse-secureboot    HD(1,GPT,7f39c61b-b9d1-4378-8478-a5e99ae6079d,0x28,0x64000)/File(\EFI\opensuse\shim.efi)
    Boot0006* tumbleweed-secureboot  HD(1,GPT,7f39c61b-b9d1-4378-8478-a5e99ae6079d,0x28,0x64000)/File(\EFI\tumbleweed\shim.efi)
    Boot000A* opensusetw-secureboot  HD(1,GPT,7f39c61b-b9d1-4378-8478-a5e99ae6079d,0x28,0x64000)/File(\EFI\opensusetw\shim.efi)
    
    Boot0001* opensusetw             HD(1,GPT,0d8470db-279c-4890-8cdb-8af7d48ab8c4,0x28,0x64000)/File(\EFI\opensusetw\grubx64.efi)
    Boot0007* opensusetw-secureboot  HD(1,GPT,0d8470db-279c-4890-8cdb-8af7d48ab8c4,0x28,0x64000)/File(\EFI\opensusetw\shim.efi)
    Boot000B* opensuse-secureboot    HD(1,GPT,0d8470db-279c-4890-8cdb-8af7d48ab8c4,0x28,0x64000)/File(\EFI\opensuse\shim.efi)
    Boot000C* tumbleweed-secureboot  HD(1,GPT,0d8470db-279c-4890-8cdb-8af7d48ab8c4,0x28,0x64000)/File(\EFI\tumbleweed\shim.efi)
    To be honest, I would delete them all and recreate with efibootmgr create command and I think it will come right as per your directory structure.
    Cheers Malcolm °¿° SUSE Knowledge Partner (Linux Counter #276890)
    SUSE SLE, openSUSE Leap/Tumbleweed (x86_64) | GNOME DE
    If you find this post helpful and are logged into the web interface,
    please show your appreciation and click on the star below... Thanks!

  8. #28

    Default Re: Today's TW zypper dup -l wipes grub and boots to white screen????

    Quote Originally Posted by malcolmlewis View Post
    Hi
    I suspect it's just conflicts when efi entries created... two different disk ID's A and 7 for the same thing...

    Code:
    Boot0005* opensuse-secureboot    HD(1,GPT,7f39c61b-b9d1-4378-8478-a5e99ae6079d,0x28,0x64000)/File(\EFI\opensuse\shim.efi)
    Boot0006* tumbleweed-secureboot  HD(1,GPT,7f39c61b-b9d1-4378-8478-a5e99ae6079d,0x28,0x64000)/File(\EFI\tumbleweed\shim.efi)
    Boot000A* opensusetw-secureboot  HD(1,GPT,7f39c61b-b9d1-4378-8478-a5e99ae6079d,0x28,0x64000)/File(\EFI\opensusetw\shim.efi)
    
    Boot0001* opensusetw             HD(1,GPT,0d8470db-279c-4890-8cdb-8af7d48ab8c4,0x28,0x64000)/File(\EFI\opensusetw\grubx64.efi)
    Boot0007* opensusetw-secureboot  HD(1,GPT,0d8470db-279c-4890-8cdb-8af7d48ab8c4,0x28,0x64000)/File(\EFI\opensusetw\shim.efi)
    Boot000B* opensuse-secureboot    HD(1,GPT,0d8470db-279c-4890-8cdb-8af7d48ab8c4,0x28,0x64000)/File(\EFI\opensuse\shim.efi)
    Boot000C* tumbleweed-secureboot  HD(1,GPT,0d8470db-279c-4890-8cdb-8af7d48ab8c4,0x28,0x64000)/File(\EFI\tumbleweed\shim.efi)
    To be honest, I would delete them all and recreate with efibootmgr create command and I think it will come right as per your directory structure.
    @malcolmlewis:

    OK, well at this point, nothing has worked that in the past has worked. In the meanwhile from today I used SG2 to get into TW and ran another zypper dup and it found 246 packages to upgrade, which included a "shim-15.4-2" package, but after running that update it went back into booting into whiteness, rather than the "default" of Linux Mint as the only non-SG2 disk distro that would boot. It's again back to none of them.

    So. I looked at the "man efibootmgr" but, as far as understanding how I would "delete them all and then recreate them" . . . ??? I don't know, is there a basic command that will erase and delete the efibootmgr listings?? Or, this is a delete each line item one at a time by number listing thing?

    The item that is missing is for the GUI-ish Grub menu to appear that shows me my various choices of distro to log into . . . rather than looking at whiteness in which there is only more whiteness to look at . . . .

  9. #29
    Join Date
    Jun 2008
    Location
    Podunk
    Posts
    31,295
    Blog Entries
    15

    Default Re: Today's TW zypper dup -l wipes grub and boots to white screen????

    Quote Originally Posted by non_space View Post
    @malcolmlewis:

    OK, well at this point, nothing has worked that in the past has worked. In the meanwhile from today I used SG2 to get into TW and ran another zypper dup and it found 246 packages to upgrade, which included a "shim-15.4-2" package, but after running that update it went back into booting into whiteness, rather than the "default" of Linux Mint as the only non-SG2 disk distro that would boot. It's again back to none of them.

    So. I looked at the "man efibootmgr" but, as far as understanding how I would "delete them all and then recreate them" . . . ??? I don't know, is there a basic command that will erase and delete the efibootmgr listings?? Or, this is a delete each line item one at a time by number listing thing?

    The item that is missing is for the GUI-ish Grub menu to appear that shows me my various choices of distro to log into . . . rather than looking at whiteness in which there is only more whiteness to look at . . . .
    Hi
    I use the following to delete entries;

    Code:
    efibootmgr -B N -b N
    
    e.g.
    efibootmgr -B C -b C
    Use the following to recreate that entry;

    Code:
    efibootmgr -c -L "tumbleweed-secureboot" -l "\\EFI\\tumbleweed\\shim.efi"
    Cheers Malcolm °¿° SUSE Knowledge Partner (Linux Counter #276890)
    SUSE SLE, openSUSE Leap/Tumbleweed (x86_64) | GNOME DE
    If you find this post helpful and are logged into the web interface,
    please show your appreciation and click on the star below... Thanks!

  10. #30

    Default Re: Today's TW zypper dup -l wipes grub and boots to white screen????

    @malcolmlewis:

    OK, well that looks a bit technical . . . as far as it seems like items are being removed one at a time and then added back in, also one at a time, and some have "shim" mentioned and some don't??

    My problem, among others is that the Grub menu isn't showing up, to then select which system I would like to use that day. It's not so much of a concern as to which of them "boots first" via efibootmgr, but getting the 5 or 6 options to show up listed in grub on cold boot, rather than . . . now, none of them, just whiteness.

    One of the freedesk bug reports that had Dell laptops going to black or blank screen, may have found a fix in the 5.12 kernel . . . that may or may not relate to my problem, as "whiteness" is different than "blackness" as the Dell folks report, but "blankness" is open to the realm of possibility, if "blankness" would be similar to what I'm calling "whiteness" there might be a fix coming in the nearing future???

Page 3 of 5 FirstFirst 12345 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
  •