Porteus on UEFI-ONLY: rock solid boot!

Here you can post about your various experiences with PC hardware. You can also post about hardware that is not compatible with the linux kernel or not recommended for use with Porteus.
panama2005
Ronin
Ronin
Posts: 1
Joined: 07 Apr 2024, 16:18
Distribution: Porteus-v5.01 CINNAMON x86-X64

Porteus on UEFI-ONLY: rock solid boot!

Post#31 by panama2005 » 07 Apr 2024, 16:25

raja wrote:
01 Jul 2021, 08:34
BIOS in any modern PC can handle, both legacy bios and uefi.

So, I think, porteus syslinux bootloader uses only "legacy BIOS" mode.

For Syslinux to boot EFI only bios, a separate procedure is given in wiki.

Code: Select all

UEFI
For UEFI systems, the bootloader files included in the official Syslinux distribution archives are originally named syslinux.efi:

efi32/efi/syslinux.efi
UEFI bootloader for EFI IA32 (x86) firmware.
efi64/efi/syslinux.efi
UEFI bootloader for EFI X64 (x86_64) firmware.
The UEFI bootloader files can be renamed, usually maintaining the ".efi" filename extension.

In UEFI systems, a GPT scheme usually replaces the traditional MBR Partition Table for storage media. The GPT standard is part of the UEFI specification, and it can also be used with BIOS firmware (Syslinux includes "gptmbr*.bin" files for the latter).

For storage media, UEFI bootloaders are expected to be found in a so-called EFI SYSTEM PARTITION.

The EFI SYSTEM PARTITION (see UEFI and EFI System partition) is frequently known as "$ESP". The most commonly supported filesystem format for $ESP is FAT32, although the UEFI specs allow for others too. Each firmware might recognize additional / different / several filesystems for $ESP (e.g. other FAT variants, UDF, HPF+, NTFS,...).

According to the UEFI specs, the default location and naming conventions for storage media are:

EFI_SYSTEM_PARTITION/EFI/BOOT/BOOTIA32.EFI
for EFI IA32 firmware.
EFI_SYSTEM_PARTITION/EFI/BOOT/BOOTX64.EFI
for EFI X64 firmware.
The UEFI specs allow for additional alternative locations and names for UEFI binaries; the aforementioned are just the default location and naming conventions according to the UEFI specs, depending on the relevant firmware/architecture type.

Some firmware might use a different default location and naming for its default UEFI executable(s).

Note: According to the UEFI specs, the firmware uses backslash ("\") instead of slash ("/") characters as path separator.


The syslinux.efi bootloader files need at least a corresponding core module. Inside the official Syslinux distribution archives, the core modules for respective UEFI architectures are located as:

efi32/com32/elflink/ldlinux/ldlinux.e32
for EFI IA32.
efi64/com32/elflink/ldlinux/ldlinux.e64
for EFI X64.
There are no "installers" for syslinux.efi. Copy the relevant syslinux.efi file to an appropriate location, and rename it if necessary or desired. Additionally, copy the necessary core module file (either "ldlinux.e32" or "ldlinux.e64", according to the architecture of the firmware) to the same directory.
syslinux-6.04 xzm module is uploaded for reference and usage.
hi I think your post is what Im looking , can you share the exact link for complete steps and I really need only UEFI boot , or ISO full install ready, the live usb works fine straight UEFI but after install goes Legacy, thanks

User avatar
Ed_P
Contributor
Contributor
Posts: 8397
Joined: 06 Feb 2013, 22:12
Distribution: Cinnamon 5.01 ISO
Location: Western NY, USA

Porteus on UEFI-ONLY: rock solid boot!

Post#32 by Ed_P » 07 Apr 2024, 17:20

Have you disabled EFI's Secure Boot option on the machine? Did you copy the Porteus files to a FAT32 drive?
Ed

Post Reply