[opensuse-factory] Howto debug grub.efi ?
Problem: Trying to boot Opensuse installation media on a laptop results in a black screen with a non blinking cursor on the left top edge. I think that this problem is caused by an incompatility between Opensuses grub.efi and the UEFI/BIOS of that laptop due to the following reasons: 1. All versions of Opensuses Installation media I've tried ( openSUSE- Leap-15.0-DVD-x86_64, openSUSE-Tumbleweed-DVD-x86_64- Snapshot20181107,openSUSE-Tumbleweed-DVD-x86_64-Snapshot20181122, openSUSE- Leap-15.1-DVD-x86_64-Build352.1) show that problem. But they boot on other systems. 2. Other linux installation/live media like Fedora-Workstation-Live- x86_64-29-1.2, manjaro-kde-18.0-stable-x86_64,ubuntu-18.10-desktop-amd64. don't have a problem to boot on that system. 3. The UEFI of that system allows to specify a path to an EFI executable to be booted. If I replace the default bootx64.efi with grub.efi I get the described problem , if I choose mokmanager.efi, the UI of mokmanager is started. 4. If I replace the grub.efi on the Opensuse installation media with grubx64.efi ( renamed to grub.efi) from the fedora installation system , I'am able to boot and to run the installation. But, as you can expect, the installed grub also shows the problem . And in this case replacing grub.efi with the fedora one results in a complaint about missing symbols. Howto get more information about the problem to be able to write a useful bugreport ? Is there a debugger or strace/ltrace like tool for EFI executables ? -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
25.11.2018 20:47, Markus Koßmann пишет:
Problem: Trying to boot Opensuse installation media on a laptop results in a black screen with a non blinking cursor on the left top edge. I think that this problem is caused by an incompatility between Opensuses grub.efi and the UEFI/BIOS of that laptop due to the following reasons:
1. All versions of Opensuses Installation media I've tried ( openSUSE- Leap-15.0-DVD-x86_64, openSUSE-Tumbleweed-DVD-x86_64- Snapshot20181107,openSUSE-Tumbleweed-DVD-x86_64-Snapshot20181122, openSUSE- Leap-15.1-DVD-x86_64-Build352.1) show that problem. But they boot on other systems.
Did you test earlier versions (Leap 42.x, openSUSE 13.x)? If they work this would give at least some starting point.
2. Other linux installation/live media like Fedora-Workstation-Live- x86_64-29-1.2, manjaro-kde-18.0-stable-x86_64,ubuntu-18.10-desktop-amd64. don't have a problem to boot on that system.
3. The UEFI of that system allows to specify a path to an EFI executable to be booted. If I replace the default bootx64.efi with grub.efi I get the described problem , if I choose mokmanager.efi, the UI of mokmanager is started.
What happens if you chose grub.efi manually from within EFI UI?
4. If I replace the grub.efi on the Opensuse installation media with grubx64.efi ( renamed to grub.efi) from the fedora installation system , I'am able to boot and to run the installation. But, as you can expect, the installed grub also shows the problem . And in this case replacing grub.efi with the fedora one results in a complaint about missing symbols.
Howto get more information about the problem to be able to write a useful bugreport ? Is there a debugger or strace/ltrace like tool for EFI executables ?
grub.efi is signed. Do you use (need, want) Secure Boot? If you can switch SB off, the first thing to test is normal grub2 generated by grub2-install. This should be used if you disable Secure Boot in YaST2 Bootloader (or you can manually run grub2-install and then select \EFI\opensuse\grubx64.efi from your EFI UI). In any case this requires bug report so it can be followed. -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
Am Sonntag, 25. November 2018, 21:18:46 schrieb Andrei Borzenkov:
Did you test earlier versions (Leap 42.x, openSUSE 13.x)? If they work this would give at least some starting point. Just tested Leap 42.3. It fails, too. For 13.x I still need to find an iso.
3. The UEFI of that system allows to specify a path to an EFI executable to be booted. If I replace the default bootx64.efi with grub.efi I get the described problem , if I choose mokmanager.efi, the UI of mokmanager is started. What happens if you chose grub.efi manually from within EFI UI? As written, trying to start grub.efi directly fails with black screen
grub.efi is signed. Do you use (need, want) Secure Boot?
Secure boot was disabled for all installations.
In any case this requires bug report so it can be followed. It looks for me that <https://bugzilla.opensuse.org/show_bug.cgi?id=1114754> is the same problem. So I attached there.
-- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
On Sonntag, 25. November 2018 21:23:05 Markus Koßmann wrote: Cannot help you with the problem in question, but..
Am Sonntag, 25. November 2018, 21:18:46 schrieb Andrei Borzenkov:
Did you test earlier versions (Leap 42.x, openSUSE 13.x)? If they work this would give at least some starting point.
Just tested Leap 42.3. It fails, too. For 13.x I still need to find an iso.
http://ftp.gwdg.de/pub/linux/suse/opensuse/discontinued/distribution/13.2/ -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
participants (3)
-
Andrei Borzenkov -
Hans-Peter Jansen -
Markus Koßmann