Tiny Core Extensions > TCE Tips & Tricks
How to make a legacy bios/uefi dual boot usb stick with syslinux
coreplayer2:
--- Quote from: Rich on January 09, 2019, 12:45:13 PM ---It seems his Acer laptop has a list of "acceptable" paths hardcoded into it it:
http://forum.tinycorelinux.net/index.php/topic,22410.msg140356.html#msg140356
--- End quote ---
Hello Rich
This is what's troubling me.. In the OP's questions it's never very clear if the list within this notebook's firmware contains both the Standard
"/EFI/BOOT/BOOTX64.EFI", and manufacturer specific
"/EFI/Linux/BOOTX64.EFI"
pathways?
Rich:
Hi coreplayer2
The notebook did not contain /EFI/BOOT/ which was why I suggested he try polikuos tutorial using /EFI/Linux/ instead.
coreplayer2:
--- Quote from: Rich on January 09, 2019, 03:46:11 PM ---Hi coreplayer2
The notebook did not contain /EFI/BOOT/ which was why I suggested he try polikuo's tutorial using /EFI/Linux/ instead.
--- End quote ---
Ok but I believe that this troubleshooting step occurred earlier and was not confirmed to have fixed the problem. It was my understanding that this was the cause;
http://forum.tinycorelinux.net/index.php/topic,22410.msg140439.html#msg140439
After this fix was performed the OP reinstalled to /EFI/Linux/ which worked. Yet it's not clear that /EFI/BOOT/ wouldn't have worked after the fix was applied.
Only reason I'm curious, is because I have a hard time believing a manufacturer would not include the default UEFI path in it's firmware.
:)
Rich:
Hi coreplayer2
--- Quote from: coreplayer2 on January 09, 2019, 04:58:06 PM ---
--- Quote from: Rich on January 09, 2019, 03:46:11 PM ---Hi coreplayer2
The notebook did not contain /EFI/BOOT/ which was why I suggested he try polikuo's tutorial using /EFI/Linux/ instead.
--- End quote ---
Ok but I believe that this troubleshooting step occurred earlier and was not confirmed to have fixed the problem. ...
--- End quote ---
It eventually got him to a grub prompt after some additional prompting by polikuo and yourself.
--- Quote ---It was my understanding that this was the cause;
http://forum.tinycorelinux.net/index.php/topic,22410.msg140439.html#msg140439
--- End quote ---
That fixed a syslinux problem.
--- Quote ---Only reason I'm curious, is because I have a hard time believing a manufacturer would not include the default UEFI path in it's firmware.
--- End quote ---
I think you're not giving manufacturers enough credit for thinking they know what you need better than you do. :D Someone
decided paths for Windows, several Linux flavors, and a generic Linux entry were all that was needed.
coreplayer2:
--- Quote from: Rich on January 09, 2019, 08:22:09 PM ---Hi coreplayer2
--- Quote ---Only reason I'm curious, is because I have a hard time believing a manufacturer would not include the default UEFI path in it's firmware.
--- End quote ---
I think you're not giving manufacturers enough credit for thinking they know what you need better than you do. :D Someone
decided paths for Windows, several Linux flavors, and a generic Linux entry were all that was needed.
--- End quote ---
Hello Rich, Yes that's right, It extremely frustrating when they know better what we want than we do.. :P It's for this reason I waste time with constant reboot cycles attempting to select my desired OS boot loader and that's ASUS whose engineers I have a lot of respect. Yet they forgot to include the only boot option that's important, to me; Load the EFI bootloader menu switchable to default, instead the time limited special key usage.
In this case it appears that ACER neglected to conform with the UEFI spec's. to include the default path for removable drives and generic fallback path ( EFI/BOOT/bootx64.efi ). Maybe they thought it was enough to support Windows and Ubuntu? maybe this was neglect, or maybe they thought it was a security risk allowing someone to boot their hardware without knowing the super secret path and handshake...
:P
I quote from https://www.rodsbooks.com/efi-bootloaders/principles.html which is easier reading than the UEFI specifications
--- Quote ---One other boot loader directory requires mention: EFI/BOOT. This directory holds a boot loader file, bootx64.efi, which serves as the fallback boot loader if none is specified in the firmware's flash storage. The filename varies depending on the architecture—the filename is bootia32.efi on IA-32 (x86) computers and bootaa64.efi on ARM64 computers. The vast majority of EFI-based x86-64 computers use 64-bit EFIs and therefore use a bootx64.efi default boot loader file
...
The fallback boot loader mentioned earlier (EFI/BOOT/bootx64.efi, or variants of that, depending on the architecture) is something of a special case. This filename was originally intended for use only on removable media, so that they could be booted to install an OS. (If not for that fixed filename, a factory-fresh computer wouldn't be able to boot anything!) This filename was quickly adopted as a fallback filename for hard disk installations, as well. This way, if a duplicate of the normal boot loader is installed to the fallback filename, the computer will remain bootable if the NVRAM-based boot manager list is damaged.
--- End quote ---
ref: http://www.uefi.org/specifications v2.7 (Errata A)
/EFI/BOOT/bootx64.efi is listed as the only path for multiple architectures on removable devices In the latest UEFI spec's chapter "13.3.1.3 Directory Structure"
--- Quote ---For removable media devices there must be only one UEFI-compliant system partition, and that partition must contain an UEFI-defined directory in the root directory. The directory will be named EFI. All OS loaders and applications will be stored in a subdirectory below EFI called BOOT. There must only be one executable EFI image for each supported processor architecture in the BOOT directory.
--- End quote ---
/EFI/Linux/ is not listed as an approved none conflicting path
Just saying,..
:)
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version