Dell PCs (and other systems) with UEFI Secure Boot show grub prompt #48
Comments
|
Thanks for opening this issue. It's unclear what circumstances cause this behavior: Are you saying that when the system boots with Secure Boot enabled it works as expected, but that it does not work as expected with Secure Boot disabled? Also, are you seeing this behavior on other machines also, or only this particular hardware? |
It boots to GRUB prompt when secure boot enabled/UEFI enabled. MBR boot seems to be OK. It should load Linux but shows GRUB shell. Device is already in secure boot mode, I use OpenSUSE TW and Windows 10. Grub is already working on this machine. |
|
I also have a Mac Mini 2009 (Intel based, EFI) here. It also boots to GRUB prompt. This eliminates the "secure boot" issue since they aren't secure boot enabled (or even implemented). |
|
I downloaded the file again to make sure, it is the exact same file. sha256sum follows: I also used "dd" command this time, same GRUB prompt on both machines. |
|
I have the same here on my Dell XPS 8910 computer. In the UEFI bootmenu I get the option to boot from the USB stick with the iso. But when I do, I only get a grub prompt. Nothing else. System runs Windows 10 only. |
|
Yes, its UEFI related because I can boot off cd with no problem if I don't use uefi. |
|
For a quick test, I grabbed the latest Debian 10 install image (netboot) from https://cdimage.debian.org/debian-cd/current/amd64/iso-cd/debian-10.6.0-amd64-netinst.iso |
|
Tested on my Dell Laptop - same result. Just ending with grub prompt, same as on desktop. |
|
Please check the file name in the boot device. If there is a dot, delete it and try again
…---Original---
From: "RobertHulsebos"<notifications@github.com>
Date: Mon, Oct 19, 2020 02:27 AM
To: "redorescue/redorescue"<redorescue@noreply.github.com>;
Cc: "Subscribed"<subscribed@noreply.github.com>;
Subject: Re: [redorescue/redorescue] HP Pavillon x360 a200nt UEFI secure boot grub prompt (#48)
Tested on my Dell Laptop - same result. Just ending with grub prompt, same as on desktop.
See attached photo for bootmenu...
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub, or unsubscribe.
|
I do not understand what you mean ... you mean the name of the USB device? |
|
No,The file in USB device. (vmlinuz initrd) I'm write the iso file to usb use Ultraiso . When I check the filename in device,initrd and vmlinuz has a dot .Then boot failed . Remove the dot in filename(initrd vmlinuz) boot succee |
|
Whatever the problem is, its located in filesystem.squashfs. When I replaced it with 2.0.7 everything worked again. |
Don't see any dot here
|
And how do I do that? ('linux newbie') |
|
Use either 2.0.7 in place of 3.0. I only replace the file to figure out the culprit. I have reported it, if ignored then I'll stick with 2.0.7 because 3.0 is useless. |
|
Odd, we have yet to see a machine fail to boot, both with and without Secure Boot enabled, including on virtual hardware. Still searching for more answers as to why this is happening for these particular systems. Please continue to post any information you are able to provide and as soon as we determine a fix for this we'll push a new release. |
|
Maybe it's a bug in the debian version. I'm not going to keep trying to figure it out. 2.0.7 does a good enough job, I'll stick with it. |
|
I have both a desktop and a laptop that show this problem. Both are Dell. I you want me something to test for you, then let me know... |
You mean you replaced only the filesystem.squashfs file in the ISO? Where can I get the 2.0.7 version of this file? So I can do the same test here... |
|
Yes....My laptop is a dell too. Downgrade to 2.0.7. I remove 3.0 completely because it doesn't work. Rebuild your usb with 2.0.7. Until these guys figure it out. Whatever they added to filesystem.squashfs is the problem for me and maybe you. |
Ok. I'll test tonight with 2.0.7. Just to see if I have the same results. Did not try that version before.... |
|
Looks like something with grub cfg or kernel boot parameters... I too have a dell laptop and hp desktop, didn't have the chance yet to try v3, will try tomorrow. |
I tried USB stick with 2.0.7. Somehow my laptop does not see it as a bootable device. Does version 2.0.7 support UEFI + Secure Boot ? |
|
Ok. That explains it.... |
|
For others finding this thread, please note that 2.0.7 offers neither Secure Boot nor UEFI, and is strictly MBR. This is by design, and for those users who cannot make use of the UEFI ISO (either due to Redo-specific issues or less-than-ideal EFI implementations with their hardware), it is always possible to use the 2.0 series release instead until a workaround for UEFI on these specific machines can be found. Edit: Release 3.0.1 is now available now, in case it has any impact on this issue. |
zebradots
changed the title
|
(Note: We realize that this issue might affect more than just Dell systems, but this title may help narrow it down more quickly.) Could the EFI implementation on affected systems be looking in a case-sensitive directory name at boot time? In other words, could it somehow make a difference whether the directories are named If anyone with an affected machine can execute GRUB commands to help determine what may be different about these systems, it would be greatly appreciated, as we are unable to reproduce this error on any hardware so far. |
zebradots
changed the title
|
Things are working in 3.0.1. Thanks |
Version 3.0.1 still not working on my Dell Inspiron 17 laptop. I can execute grub commands. Let me know how I can be of assistance... |
|
@RobertHulsebos: As you may already know, Rescuezilla is a fork of a much older version of Redo from 2012. However, the developer recently implemented UEFI support for that project. Out of curiosity, does the latest release of Rescuezilla boot properly in UEFI Secure Boot mode on your hardware? Also, you mentioned in a previous post that you have both a desktop and laptop that were not booting. Does the desktop boot properly on 3.0.1 now? |
On my Dell XPS8190 desktop I have the same result with 3.0.1 as on my laptop - still ending up in grub. So no improvement... |
|
I also tried Rescuezilla 2.0 iso. Booting from same USB stick, same desktop. This seems to work OK for as far as booting is concerned. (I did not test the actual making of a backup) |
|
Based on the fact that GRUB does in fact load, and that Secure Boot appears to at least get to this stage without any complaint, it seems that the problem lies in GRUB's ability to take the next step to boot. We suspect that this may have something to do with the following: Previously, the |
|
#51 Hardware/test report can be submitted here if anyone wishes. |
Thank you @agnivo007 for creating that thread to track different outcomes. Those with an affected system may try entering the above two lines manually into the GRUB prompt to see if it provides any helpful output or error messages. |
|
@zebradots , you may consult and take this issue with the ventoy developers at https://github.com/ventoy with the boot/uefi/grub issue. They are the boot specialists as far as I've seen and have developed a great product. |
I tried the two lines, but they did not give any response at all... |
|
How about: |
|
Anyone encountering this issue: Please download and try This test release image includes a configuration change that may correct the GRUB boot prompt issue. If it appears to work, we will push these changes to the repo and finalize a new release for 3.0.2. Unfortunately, we cannot reproduce this error because all our systems boot properly, so this one is difficult to troubleshoot. |
|
Best of luck for the fix... However, did the insmod normal, normal additions to grub prompt work? Eager to know... |
Yes. They did work! After entering the 'normal' command the Redo application is started automatically and I get this ...
|
|
Great! Hope @zebradots noted it... |
Our understanding is that the
However, invoking the If the 3.0.2-BETA ISO boots properly, we will prepare a final 3.0.2 release immediately. |
It works! I tested both "non secure boot" and "secure boot" options. Thanks for your time. HP Pavilion x360 here (I am the original bug reporter) |
|
Excellent! We will push the commits and prepare a new release. Thank you so much for taking time to report this issue and confirm that it has been fixed. Edit: Fixed with commit df0a00f. Release 3.0.2 coming soon. |
zebradots
added
bug
|
My comment might be too naive, but if any other volume has a "REDO" directory or file entry on it, will not grub be confused with the commit you posted? |
|
@agnivo007, you are correct. If another file named "REDO" exists on the boot media, GRUB could mistakenly assume that it was the root location. While this is theoretically possible, we suspect the likelihood is rather slim. Also, this is the same method used since UEFI was introduced, and was already present before the most recent commit referenced above (see https://github.com/redorescue/redorescue/blob/master/overlay/image/boot/grub/grub.cfg, where these lines also appear). |
Congratulations for 3.0!
I have written the image to a USB2 drive. Secure boot enabled, it works perfectly on supported Linuxes (Fedora, SUSE). When it boots I am greeted by a Grub shell.
I can give any info or do tests.
I believe it is properly signed otherwise Grub wouldn't appear.
The text was updated successfully, but these errors were encountered: