Stuck in EFI shell
Posted: Wed Nov 23, 2022 3:10 am
What does this mean?
Discussion, talk and tips
https://forum.puppylinux.com/
What does this mean?
This looks like an internal shell for dealing with the EFI setup for UEFI boot. What were you doing to enter this shell?
rockedge wrote: Wed Nov 23, 2022 2:01 pmThis looks like an internal shell for dealing with the EFI setup for UEFI boot. What were you doing to enter this shell?
I just configured Fatdog64, rebooted and it gave me this screen when selecting the first option in the bootloader, keeps giving me this everytime I try to boot Fatdog64 from UEFI, even if it's a fresh ISO. I didn't do anything advanced just configured things from the applications it comes with mostly.
LLe wrote: Thu Nov 24, 2022 10:32 pmjust configured things from the applications it comes with mostly.
You need to be more specific. Is this a hard drive install?
When UEFI firmware boots, it scans the available drives for an EFI System Partition (ESP). This is a fat32 partition with an EFI folder containing a file like bootx64.efi. If it cannot find any such partition, it may default to running the EFI shell.
If possible, boot the machine with a different OS and check to see what is on the drive.
Not an install, I flashed to a USB drive and later tried burning to a DVD-R, so I don't think it's a problem with the ISO, I downloaded the ISO number of times as well and checked md5, so it is unlikely it was corrupted. I think it the UEFI bootloader utility that is used with this that has some kind of trouble with my laptop, think I had a similar problem with Ventoy and some other puppy in the past. non-UEFI boot still works. maybe the Dog is just too fat to fit into my laptop.
Here's what's on it
https://i.imgur.com/QS50DnI.png
There are many variations of UEFI firmware, so it's hard to know what's going wrong. Have you turned Secure Boot OFF?
FWIW, I can boot the Fatdog ISO on UEFI machines using ISObooter.
Since you just need a UEFI-bootable flash drive. see the instructions here.
Yeah, secure boot is disabled.
I've had good experience with grub2config, that likely would work well in this case as well.
