[arch-releng] [DRAFT][RFC][PATCH][archiso] Add UEFI boot support via Linux >= 3.3 EFI boot stub.

Gerardo Exequiel Pozzi

20 Mar 2012 20 Mar '12

3:59 p.m.

Support is only added to x86_64. This only works via (U)EFI shell. Boot with: fs0:\EFI\linux\vmlinuz.efi archisolabel=ARCH_201203 initrd=\EFI\linux\archiso.img There are plans to support command line options via a config file (not yet in linux-3.3), in such case vmlinuz.efi can be renamed to bootia64.efi and placed to \EFI\boot to automatic boot. --- archiso/mkarchiso | 11 ++++++++++- configs/releng/build.sh | 25 +++++++++++++++++++++++++ 2 files changed, 35 insertions(+), 1 deletion(-) diff --git a/archiso/mkarchiso b/archiso/mkarchiso index ad88b0b..208f7b6 100755 --- a/archiso/mkarchiso +++ b/archiso/mkarchiso @@ -380,6 +380,8 @@ command_checksum () { # Create an ISO9660 filesystem from "iso" directory. command_iso () { + local _iso_efi_boot_args + if [[ ! -f "${work_dir}/iso/isolinux/isolinux.bin" ]]; then _msg_error "The file '${work_dir}/iso/isolinux/isolinux.bin' does not exist." 1 fi @@ -387,6 +389,12 @@ command_iso () { _msg_error "The file '${work_dir}/iso/isolinux/isohdpfx.bin' does not exist." 1 fi + if [[ -d "${work_dir}/iso/EFI" ]]; then + _iso_efi_boot_args="-eltorito-alt-boot --efi-boot EFI/archiso/archiso.fat -no-emul-boot" + else + _iso_efi_boot_args="" + fi + _show_config iso if _is_directory_changed "${work_dir}/iso" "${out_dir}/${img_name}"; then @@ -398,9 +406,10 @@ command_iso () { fi xorriso -as mkisofs ${_qflag} -r -l \ -b isolinux/isolinux.bin -c isolinux/boot.cat \ - -iso-level 3 \ -no-emul-boot -boot-load-size 4 -boot-info-table \ + ${_iso_efi_boot_args} \ -isohybrid-mbr ${work_dir}/iso/isolinux/isohdpfx.bin \ + -iso-level 3 \ -p "prepared by mkarchiso" \ -publisher "${iso_publisher}" \ -A "${iso_application}" \ diff --git a/configs/releng/build.sh b/configs/releng/build.sh index 2faf210..f4ca11e 100755 --- a/configs/releng/build.sh +++ b/configs/releng/build.sh @@ -58,6 +58,29 @@ make_boot() { fi } +# Prepare /EFI (using linux EFI boot stub) +make_boot_efi() { + if [[ ! -e ${work_dir}/build.${FUNCNAME} ]]; then + if [[ ${arch} == "x86_64" ]]; then + mkdir -p ${work_dir}/iso/EFI/linux + cp ${work_dir}/iso/${install_dir}/boot/x86_64/vmlinuz ${work_dir}/iso/EFI/linux/vmlinuz.efi + cp ${work_dir}/iso/${install_dir}/boot/x86_64/archiso.img ${work_dir}/iso/EFI/linux/archiso.img + # There are plans to support command line options via a config file (not yet in linux-3.3) + # echo "archisolabel=${iso_label} initrd=\EFI\linux\archiso.img" | iconv -f ascii -t ucs2 > ${work_dir}/iso/EFI/linux/vmlinuz.conf + mkdir -p ${work_dir}/iso/EFI/archiso + mkdir -p ${work_dir}/fat + dd of=${work_dir}/iso/EFI/archiso/archiso.fat bs=1 seek=32M count=0 + mkfs.vfat ${work_dir}/iso/EFI/archiso/archiso.fat + mount ${work_dir}/iso/EFI/archiso/archiso.fat ${work_dir}/fat/ + mkdir -p ${work_dir}/fat/EFI/linux + cp ${work_dir}/iso/EFI/linux/vmlinuz.efi ${work_dir}/fat/EFI/linux + cp ${work_dir}/iso/EFI/linux/archiso.img ${work_dir}/fat/EFI/linux + # cp ${work_dir}/iso/EFI/linux/vmlinuz.conf ${work_dir}/fat/EFI/linux + umount ${work_dir}/fat/ + fi + fi +} + # Prepare /${install_dir}/boot/syslinux make_syslinux() { if [[ ! -e ${work_dir}/build.${FUNCNAME} ]]; then @@ -155,6 +178,7 @@ make_core_repo() { fi } + # Process aitab # args: $1 (core | netinstall) make_aitab() { @@ -259,6 +283,7 @@ make_common_single() { make_packages make_setup_mkinitcpio make_boot + make_boot_efi make_syslinux make_isolinux make_customize_root_image -- 1.7.9.4

Show replies by date

Keshav P R

20 Mar 20 Mar

4:03 p.m.

New subject: [arch-releng] [DRAFT][RFC][PATCH][archiso] Add UEFI boot support via Linux >= 3.3 EFI boot stub.

On Tue, Mar 20, 2012 at 21:29, Gerardo Exequiel Pozzi wrote:

...

Support is only added to x86_64. This only works via (U)EFI shell. Boot with:

fs0:\EFI\linux\vmlinuz.efi archisolabel=ARCH_201203 initrd=\EFI\linux\archiso.img

There are plans to support command line options via a config file (not yet in linux-3.3), in such case vmlinuz.efi can be renamed to bootia64.efi and placed to \EFI\boot to automatic boot.

Should be bootx64.efi

...

--- archiso/mkarchiso | 11 ++++++++++- configs/releng/build.sh | 25 +++++++++++++++++++++++++ 2 files changed, 35 insertions(+), 1 deletion(-)

diff --git a/archiso/mkarchiso b/archiso/mkarchiso index ad88b0b..208f7b6 100755 --- a/archiso/mkarchiso +++ b/archiso/mkarchiso @@ -380,6 +380,8 @@ command_checksum () {

# Create an ISO9660 filesystem from "iso" directory. command_iso () { + local _iso_efi_boot_args + if [[ ! -f "${work_dir}/iso/isolinux/isolinux.bin" ]]; then _msg_error "The file '${work_dir}/iso/isolinux/isolinux.bin' does not exist." 1 fi @@ -387,6 +389,12 @@ command_iso () { _msg_error "The file '${work_dir}/iso/isolinux/isohdpfx.bin' does not exist." 1 fi

+ if [[ -d "${work_dir}/iso/EFI" ]]; then + _iso_efi_boot_args="-eltorito-alt-boot --efi-boot EFI/archiso/archiso.fat -no-emul-boot" + else + _iso_efi_boot_args="" + fi + _show_config iso

if _is_directory_changed "${work_dir}/iso" "${out_dir}/${img_name}"; then @@ -398,9 +406,10 @@ command_iso () { fi xorriso -as mkisofs ${_qflag} -r -l \ -b isolinux/isolinux.bin -c isolinux/boot.cat \ - -iso-level 3 \ -no-emul-boot -boot-load-size 4 -boot-info-table \ + ${_iso_efi_boot_args} \ -isohybrid-mbr ${work_dir}/iso/isolinux/isohdpfx.bin \ + -iso-level 3 \ -p "prepared by mkarchiso" \ -publisher "${iso_publisher}" \ -A "${iso_application}" \ diff --git a/configs/releng/build.sh b/configs/releng/build.sh index 2faf210..f4ca11e 100755 --- a/configs/releng/build.sh +++ b/configs/releng/build.sh @@ -58,6 +58,29 @@ make_boot() { fi }

+# Prepare /EFI (using linux EFI boot stub) +make_boot_efi() { + if [[ ! -e ${work_dir}/build.${FUNCNAME} ]]; then + if [[ ${arch} == "x86_64" ]]; then + mkdir -p ${work_dir}/iso/EFI/linux + cp ${work_dir}/iso/${install_dir}/boot/x86_64/vmlinuz ${work_dir}/iso/EFI/linux/vmlinuz.efi + cp ${work_dir}/iso/${install_dir}/boot/x86_64/archiso.img ${work_dir}/iso/EFI/linux/archiso.img + # There are plans to support command line options via a config file (not yet in linux-3.3) + # echo "archisolabel=${iso_label} initrd=\EFI\linux\archiso.img" | iconv -f ascii -t ucs2 > ${work_dir}/iso/EFI/linux/vmlinuz.conf + mkdir -p ${work_dir}/iso/EFI/archiso + mkdir -p ${work_dir}/fat + dd of=${work_dir}/iso/EFI/archiso/archiso.fat bs=1 seek=32M count=0 + mkfs.vfat ${work_dir}/iso/EFI/archiso/archiso.fat + mount ${work_dir}/iso/EFI/archiso/archiso.fat ${work_dir}/fat/ + mkdir -p ${work_dir}/fat/EFI/linux + cp ${work_dir}/iso/EFI/linux/vmlinuz.efi ${work_dir}/fat/EFI/linux + cp ${work_dir}/iso/EFI/linux/archiso.img ${work_dir}/fat/EFI/linux + # cp ${work_dir}/iso/EFI/linux/vmlinuz.conf ${work_dir}/fat/EFI/linux + umount ${work_dir}/fat/ + fi + fi +} + # Prepare /${install_dir}/boot/syslinux make_syslinux() { if [[ ! -e ${work_dir}/build.${FUNCNAME} ]]; then @@ -155,6 +178,7 @@ make_core_repo() { fi }

+ # Process aitab # args: $1 (core | netinstall) make_aitab() { @@ -259,6 +283,7 @@ make_common_single() { make_packages make_setup_mkinitcpio make_boot + make_boot_efi make_syslinux make_isolinux make_customize_root_image -- 1.7.9.4

Gerardo Exequiel Pozzi

5:45 p.m.

New subject: [arch-releng] [DRAFT][RFC][PATCH][archiso] Add UEFI boot support via Linux >= 3.3 EFI boot stub.

----- Mensaje original -----

...

De: Keshav P R Para: Arch Linux Release Engineering CC: Enviado: martes, 20 de marzo de 2012 13:03 Asunto: Re: [arch-releng] [DRAFT][RFC][PATCH][archiso] Add UEFI boot support via Linux >= 3.3 EFI boot stub.

On Tue, Mar 20, 2012 at 21:29, Gerardo Exequiel Pozzi wrote:

...
Support is only added to x86_64. This only works via (U)EFI shell. Boot with:

fs0:\EFI\linux\vmlinuz.efi archisolabel=ARCH_201203 initrd=\EFI\linux\archiso.img

There are plans to support command line options via a config file (not yet in linux-3.3), in such case vmlinuz.efi can be renamed to bootia64.efi and placed to \EFI\boot to automatic boot.

Should be bootx64.efi

oops, true. Thanks.

...

...
--- archiso/mkarchiso | 11 ++++++++++- configs/releng/build.sh | 25 +++++++++++++++++++++++++ 2 files changed, 35 insertions(+), 1 deletion(-)

diff --git a/archiso/mkarchiso b/archiso/mkarchiso index ad88b0b..208f7b6 100755 --- a/archiso/mkarchiso +++ b/archiso/mkarchiso @@ -380,6 +380,8 @@ command_checksum () {

# Create an ISO9660 filesystem from "iso" directory. command_iso () { + local _iso_efi_boot_args + if [[ ! -f "${work_dir}/iso/isolinux/isolinux.bin" ]]; then _msg_error "The file

'${work_dir}/iso/isolinux/isolinux.bin' does not exist." 1

...
fi @@ -387,6 +389,12 @@ command_iso () { _msg_error "The file '${work_dir}/iso/isolinux/isohdpfx.bin' does not exist." 1 fi

+ if [[ -d "${work_dir}/iso/EFI" ]]; then + _iso_efi_boot_args="-eltorito-alt-boot --efi-boot EFI/archiso/archiso.fat -no-emul-boot" + else + _iso_efi_boot_args="" + fi + _show_config iso

if _is_directory_changed "${work_dir}/iso" "${out_dir}/${img_name}"; then @@ -398,9 +406,10 @@ command_iso () { fi xorriso -as mkisofs ${_qflag} -r -l \ -b isolinux/isolinux.bin -c isolinux/boot.cat \ - -iso-level 3 \ -no-emul-boot -boot-load-size 4 -boot-info-table \ + ${_iso_efi_boot_args} \ -isohybrid-mbr ${work_dir}/iso/isolinux/isohdpfx.bin \ + -iso-level 3 \ -p "prepared by mkarchiso" \ -publisher "${iso_publisher}" \ -A "${iso_application}" \ diff --git a/configs/releng/build.sh b/configs/releng/build.sh index 2faf210..f4ca11e 100755 --- a/configs/releng/build.sh +++ b/configs/releng/build.sh @@ -58,6 +58,29 @@ make_boot() { fi }

+# Prepare /EFI (using linux EFI boot stub) +make_boot_efi() { + if [[ ! -e ${work_dir}/build.${FUNCNAME} ]]; then + if [[ ${arch} == "x86_64" ]]; then + mkdir -p ${work_dir}/iso/EFI/linux + cp ${work_dir}/iso/${install_dir}/boot/x86_64/vmlinuz ${work_dir}/iso/EFI/linux/vmlinuz.efi + cp ${work_dir}/iso/${install_dir}/boot/x86_64/archiso.img ${work_dir}/iso/EFI/linux/archiso.img + # There are plans to support command line options via a config file (not yet in linux-3.3) + # echo "archisolabel=${iso_label} initrd=\EFI\linux\archiso.img" | iconv -f ascii -t ucs2 > ${work_dir}/iso/EFI/linux/vmlinuz.conf + mkdir -p ${work_dir}/iso/EFI/archiso + mkdir -p ${work_dir}/fat + dd of=${work_dir}/iso/EFI/archiso/archiso.fat bs=1 seek=32M count=0 + mkfs.vfat ${work_dir}/iso/EFI/archiso/archiso.fat + mount ${work_dir}/iso/EFI/archiso/archiso.fat ${work_dir}/fat/ + mkdir -p ${work_dir}/fat/EFI/linux + cp ${work_dir}/iso/EFI/linux/vmlinuz.efi ${work_dir}/fat/EFI/linux + cp ${work_dir}/iso/EFI/linux/archiso.img ${work_dir}/fat/EFI/linux + # cp ${work_dir}/iso/EFI/linux/vmlinuz.conf ${work_dir}/fat/EFI/linux + umount ${work_dir}/fat/ + fi + fi +} + # Prepare /${install_dir}/boot/syslinux make_syslinux() { if [[ ! -e ${work_dir}/build.${FUNCNAME} ]]; then @@ -155,6 +178,7 @@ make_core_repo() { fi }

+ # Process aitab # args: $1 (core | netinstall) make_aitab() { @@ -259,6 +283,7 @@ make_common_single() { make_packages make_setup_mkinitcpio make_boot + make_boot_efi make_syslinux make_isolinux make_customize_root_image -- 1.7.9.4

Keshav P R

4:13 p.m.

New subject: [arch-releng] [DRAFT][RFC][PATCH][archiso] Add UEFI boot support via Linux >= 3.3 EFI boot stub.

On Tue, Mar 20, 2012 at 21:29, Gerardo Exequiel Pozzi wrote:

...

Support is only added to x86_64. This only works via (U)EFI shell. Boot with:

fs0:\EFI\linux\vmlinuz.efi archisolabel=ARCH_201203 initrd=\EFI\linux\archiso.img

There are plans to support command line options via a config file (not yet in linux-3.3), in such case vmlinuz.efi can be renamed to bootia64.efi and placed to \EFI\boot to automatic boot.

--- archiso/mkarchiso | 11 ++++++++++- configs/releng/build.sh | 25 +++++++++++++++++++++++++ 2 files changed, 35 insertions(+), 1 deletion(-)

diff --git a/archiso/mkarchiso b/archiso/mkarchiso index ad88b0b..208f7b6 100755 --- a/archiso/mkarchiso +++ b/archiso/mkarchiso @@ -380,6 +380,8 @@ command_checksum () {

# Create an ISO9660 filesystem from "iso" directory. command_iso () { + local _iso_efi_boot_args + if [[ ! -f "${work_dir}/iso/isolinux/isolinux.bin" ]]; then _msg_error "The file '${work_dir}/iso/isolinux/isolinux.bin' does not exist." 1 fi @@ -387,6 +389,12 @@ command_iso () { _msg_error "The file '${work_dir}/iso/isolinux/isohdpfx.bin' does not exist." 1 fi

+ if [[ -d "${work_dir}/iso/EFI" ]]; then + _iso_efi_boot_args="-eltorito-alt-boot --efi-boot EFI/archiso/archiso.fat -no-emul-boot" + else + _iso_efi_boot_args="" + fi + _show_config iso

if _is_directory_changed "${work_dir}/iso" "${out_dir}/${img_name}"; then @@ -398,9 +406,10 @@ command_iso () { fi xorriso -as mkisofs ${_qflag} -r -l \ -b isolinux/isolinux.bin -c isolinux/boot.cat \ - -iso-level 3 \ -no-emul-boot -boot-load-size 4 -boot-info-table \ + ${_iso_efi_boot_args} \ -isohybrid-mbr ${work_dir}/iso/isolinux/isohdpfx.bin \ + -iso-level 3 \ -p "prepared by mkarchiso" \ -publisher "${iso_publisher}" \ -A "${iso_application}" \ diff --git a/configs/releng/build.sh b/configs/releng/build.sh index 2faf210..f4ca11e 100755 --- a/configs/releng/build.sh +++ b/configs/releng/build.sh @@ -58,6 +58,29 @@ make_boot() { fi }

+# Prepare /EFI (using linux EFI boot stub) +make_boot_efi() { + if [[ ! -e ${work_dir}/build.${FUNCNAME} ]]; then + if [[ ${arch} == "x86_64" ]]; then + mkdir -p ${work_dir}/iso/EFI/linux + cp ${work_dir}/iso/${install_dir}/boot/x86_64/vmlinuz ${work_dir}/iso/EFI/linux/vmlinuz.efi + cp ${work_dir}/iso/${install_dir}/boot/x86_64/archiso.img ${work_dir}/iso/EFI/linux/archiso.img

Why duplicate the files? /EFI/linux/archiso.img in this case. You can always use fs0:\EFI\linux\vmlinuz.efi archisolabel=ARCH_201203 initrd=\boot\x86_64\archiso.img

...

+ # There are plans to support command line options via a config file (not yet in linux-3.3) + # echo "archisolabel=${iso_label} initrd=\EFI\linux\archiso.img" | iconv -f ascii -t ucs2 > ${work_dir}/iso/EFI/linux/vmlinuz.conf + mkdir -p ${work_dir}/iso/EFI/archiso + mkdir -p ${work_dir}/fat + dd of=${work_dir}/iso/EFI/archiso/archiso.fat bs=1 seek=32M count=0 + mkfs.vfat ${work_dir}/iso/EFI/archiso/archiso.fat + mount ${work_dir}/iso/EFI/archiso/archiso.fat ${work_dir}/fat/ + mkdir -p ${work_dir}/fat/EFI/linux + cp ${work_dir}/iso/EFI/linux/vmlinuz.efi ${work_dir}/fat/EFI/linux + cp ${work_dir}/iso/EFI/linux/archiso.img ${work_dir}/fat/EFI/linux + # cp ${work_dir}/iso/EFI/linux/vmlinuz.conf ${work_dir}/fat/EFI/linux + umount ${work_dir}/fat/ + fi + fi +} +

This is going to increase the iso size like hell. Having the kernel and initrd files within a FAT image inside the iso is not a good idea. A 32 MB fat image, come on. I know this is required for CD booting, but this is not a good idea with efistub efilinux or elilo etc. For USB booting you can just have the files in the iso itself, wherein the user simply extract the iso in a FAT32 USB and boots from it. I say drop support for iso booting via this fat fs image and support uefi boot only in case of USBs. Regards. Keshav

Gerardo Exequiel Pozzi

5:45 p.m.

New subject: [arch-releng] [DRAFT][RFC][PATCH][archiso] Add UEFI boot support via Linux >= 3.3 EFI boot stub.

----- Mensaje original -----

...

De: Keshav P R Para: Arch Linux Release Engineering CC: Enviado: martes, 20 de marzo de 2012 13:13 Asunto: Re: [arch-releng] [DRAFT][RFC][PATCH][archiso] Add UEFI boot support via Linux >= 3.3 EFI boot stub.

On Tue, Mar 20, 2012 at 21:29, Gerardo Exequiel Pozzi wrote:

...
Support is only added to x86_64. This only works via (U)EFI shell. Boot with:

fs0:\EFI\linux\vmlinuz.efi archisolabel=ARCH_201203 initrd=\EFI\linux\archiso.img

There are plans to support command line options via a config file (not yet in linux-3.3), in such case vmlinuz.efi can be renamed to bootia64.efi and placed to \EFI\boot to automatic boot.

--- archiso/mkarchiso | 11 ++++++++++- configs/releng/build.sh | 25 +++++++++++++++++++++++++ 2 files changed, 35 insertions(+), 1 deletion(-)

diff --git a/archiso/mkarchiso b/archiso/mkarchiso index ad88b0b..208f7b6 100755 --- a/archiso/mkarchiso +++ b/archiso/mkarchiso @@ -380,6 +380,8 @@ command_checksum () {

# Create an ISO9660 filesystem from "iso" directory. command_iso () { + local _iso_efi_boot_args + if [[ ! -f "${work_dir}/iso/isolinux/isolinux.bin" ]]; then _msg_error "The file '${work_dir}/iso/isolinux/isolinux.bin' does not exist." 1 fi @@ -387,6 +389,12 @@ command_iso () { _msg_error "The file '${work_dir}/iso/isolinux/isohdpfx.bin' does not exist." 1 fi

+ if [[ -d "${work_dir}/iso/EFI" ]]; then + _iso_efi_boot_args="-eltorito-alt-boot --efi-boot EFI/archiso/archiso.fat -no-emul-boot" + else + _iso_efi_boot_args="" + fi + _show_config iso

if _is_directory_changed "${work_dir}/iso" "${out_dir}/${img_name}"; then @@ -398,9 +406,10 @@ command_iso () { fi xorriso -as mkisofs ${_qflag} -r -l \ -b isolinux/isolinux.bin -c isolinux/boot.cat \ - -iso-level 3 \ -no-emul-boot -boot-load-size 4 -boot-info-table \ + ${_iso_efi_boot_args} \ -isohybrid-mbr ${work_dir}/iso/isolinux/isohdpfx.bin \ + -iso-level 3 \ -p "prepared by mkarchiso" \ -publisher "${iso_publisher}" \ -A "${iso_application}" \ diff --git a/configs/releng/build.sh b/configs/releng/build.sh index 2faf210..f4ca11e 100755 --- a/configs/releng/build.sh +++ b/configs/releng/build.sh @@ -58,6 +58,29 @@ make_boot() { fi }

+# Prepare /EFI (using linux EFI boot stub) +make_boot_efi() { + if [[ ! -e ${work_dir}/build.${FUNCNAME} ]]; then + if [[ ${arch} == "x86_64" ]]; then + mkdir -p ${work_dir}/iso/EFI/linux + cp ${work_dir}/iso/${install_dir}/boot/x86_64/vmlinuz ${work_dir}/iso/EFI/linux/vmlinuz.efi + cp ${work_dir}/iso/${install_dir}/boot/x86_64/archiso.img ${work_dir}/iso/EFI/linux/archiso.img

Why duplicate the files? /EFI/linux/archiso.img in this case. You can always use

fs0:\EFI\linux\vmlinuz.efi archisolabel=ARCH_201203 initrd=\boot\x86_64\archiso.img

True, I am just testing this stuff just now. initrd=\arch\boot\x86_64\archiso.img

...

...
+ # There are plans to support command line options via a config file (not yet in linux-3.3) + # echo "archisolabel=${iso_label} initrd=\EFI\linux\archiso.img" | iconv -f ascii -t ucs2 > ${work_dir}/iso/EFI/linux/vmlinuz.conf + mkdir -p ${work_dir}/iso/EFI/archiso + mkdir -p ${work_dir}/fat + dd of=${work_dir}/iso/EFI/archiso/archiso.fat bs=1 seek=32M count=0 + mkfs.vfat ${work_dir}/iso/EFI/archiso/archiso.fat + mount ${work_dir}/iso/EFI/archiso/archiso.fat ${work_dir}/fat/ + mkdir -p ${work_dir}/fat/EFI/linux + cp ${work_dir}/iso/EFI/linux/vmlinuz.efi ${work_dir}/fat/EFI/linux + cp ${work_dir}/iso/EFI/linux/archiso.img ${work_dir}/fat/EFI/linux + # cp ${work_dir}/iso/EFI/linux/vmlinuz.conf ${work_dir}/fat/EFI/linux + umount ${work_dir}/fat/ + fi + fi +} +

This is going to increase the iso size like hell. Having the kernel and initrd files within a FAT image inside the iso is not a good idea. A 32 MB fat image, come on. I know this is required for CD booting, but this is not a good idea with efistub efilinux or elilo etc. For USB booting you can just have the files in the iso itself, wherein the user simply extract the iso in a FAT32 USB and boots from it. I say drop support for iso booting via this fat fs image and support uefi boot only in case of USBs.

Regards.

Keshav

OK, so just ignore this draft patch. UEFI boot support can be made manually by the user, just doing a copy of vmlinuz to the right place and optionally installing a boot manager. A documentation on the wiki is sufficient.

Keshav P R

26 Mar 26 Mar

2:16 p.m.

New subject: [arch-releng] [DRAFT][RFC][PATCH][archiso] Add UEFI boot support via Linux >= 3.3 EFI boot stub.

On Tue, Mar 20, 2012 at 23:15, Gerardo Exequiel Pozzi wrote:

...

...
This is going to increase the iso size like hell. Having the kernel and initrd files within a FAT image inside the iso is not a good idea. A 32 MB fat image, come on. I know this is required for CD booting, but this is not a good idea with efistub efilinux or elilo etc. For USB booting you can just have the files in the iso itself, wherein the user simply extract the iso in a FAT32 USB and boots from it. I say drop support for iso booting via this fat fs image and support uefi boot only in case of USBs.

Regards.

Keshav

OK, so just ignore this draft patch. UEFI boot support can be made manually by the user, just doing a copy of vmlinuz to the right place and optionally installing a boot manager.

A documentation on the wiki is sufficient.

You might be interested in rEFInd-x86_64 https://aur.archlinux.org/packages.php?ID=57632 which provides a nice menu for EFISTUB kernels. Related info : http://www.rodsbooks.com/refind/linux.html http://www.rodsbooks.com/efi-bootloaders/efistub.html [QUOTE from http://www.rodsbooks.com/refind/linux.html] rEFInd looks for a file called linux.conf in the same directory as the kernel file. This file is a practical requirement for booting from an auto-detected kernel. It consists of a series of lines, each of which consists of a label followed by a series of kernel options. The first line sets default options, and subsequent lines set options that are accessible from the main menu tag's submenu screen. The intent of this system is that distribution maintainers can place their kernels, initial RAM disks, and a linux.conf file in their own subdirectory on the ESP. rEFInd will detect their kernels and create one main menu entry for each kernel. Each entry will implement as many options as there are lines in the linux.conf file. In this way, two or more distributions can each maintain their boot loader entries, without being too concerned for who maintains rEFInd as a whole. [/QUOTE] The filename has been changed to refind_linux.conf in the upstream git repo so that it does not conflict with the proposed efistub config file by kernel devs (http://sourceforge.net/p/refind/code/ci/c09200e2220b05bbade961bdc35f7da90d31...). This should be pretty straightforward to implement in Archiso. For non-EFISTUB kernels like LTS ones, you can use efilinux-x86_64 https://aur.archlinux.org/packages.php?ID=57972 (Usage instructions - http://thread.gmane.org/gmane.linux.kernel/1172645 and http://article.gmane.org/gmane.linux.kernel/1175060). This might be a good alternative for grub2 uefi boot, although booting i686 kernels in x86_64 UEFI will not be supported by EFISTUB (which can be done using grub2). Support for mixed arch booting seems to have been merged for 3.4-rc1 . Regards. Keshav

Gerardo Exequiel Pozzi

27 Mar 27 Mar

1:34 a.m.

New subject: [arch-releng] [DRAFT][RFC][PATCH][archiso] Add UEFI boot support via Linux >= 3.3 EFI boot stub.

On 03/26/2012 11:16 AM, Keshav P R wrote:

...

...
...
This is going to increase the iso size like hell. Having the kernel and initrd files within a FAT image inside the iso is not a good idea. A 32 MB fat image, come on. I know this is required for CD booting, but this is not a good idea with efistub efilinux or elilo etc. For USB booting you can just have the files in the iso itself, wherein the user simply extract the iso in a FAT32 USB and boots from it. I say drop support for iso booting via this fat fs image and support uefi boot only in case of USBs.

Regards.

Keshav

OK, so just ignore this draft patch. UEFI boot support can be made manually by the user, just doing a copy of vmlinuz to the right place and optionally installing a boot manager.

A documentation on the wiki is sufficient. You might be interested in rEFInd-x86_64 https://aur.archlinux.org/packages.php?ID=57632 which provides a nice

On Tue, Mar 20, 2012 at 23:15, Gerardo Exequiel Pozzi wrote: menu for EFISTUB kernels.

Related info : http://www.rodsbooks.com/refind/linux.html http://www.rodsbooks.com/efi-bootloaders/efistub.html

[QUOTE from http://www.rodsbooks.com/refind/linux.html] rEFInd looks for a file called linux.conf in the same directory as the kernel file. This file is a practical requirement for booting from an auto-detected kernel. It consists of a series of lines, each of which consists of a label followed by a series of kernel options. The first line sets default options, and subsequent lines set options that are accessible from the main menu tag's submenu screen.

The intent of this system is that distribution maintainers can place their kernels, initial RAM disks, and a linux.conf file in their own subdirectory on the ESP. rEFInd will detect their kernels and create one main menu entry for each kernel. Each entry will implement as many options as there are lines in the linux.conf file. In this way, two or more distributions can each maintain their boot loader entries, without being too concerned for who maintains rEFInd as a whole. [/QUOTE]

The filename has been changed to refind_linux.conf in the upstream git repo so that it does not conflict with the proposed efistub config file by kernel devs (http://sourceforge.net/p/refind/code/ci/c09200e2220b05bbade961bdc35f7da90d31...).

This should be pretty straightforward to implement in Archiso. For non-EFISTUB kernels like LTS ones, you can use efilinux-x86_64 https://aur.archlinux.org/packages.php?ID=57972 (Usage instructions - http://thread.gmane.org/gmane.linux.kernel/1172645 and http://article.gmane.org/gmane.linux.kernel/1175060). This might be a good alternative for grub2 uefi boot, although booting i686 kernels in x86_64 UEFI will not be supported by EFISTUB (which can be done using grub2). Support for mixed arch booting seems to have been merged for 3.4-rc1 .

Regards.

Keshav

Thanks for the work. But this only added the advantage of passing command line options to the kernel. We still need a "FAT image" with bootx64.efi (rEFInd) + vmlinuz.efi + archiso.img (initramfs) + refind*.conf (for El Torito) that was the main dissapointed issue. Otherwise rEFInd can not find what file to load. -- Gerardo Exequiel Pozzi \cos^2\alpha + \sin^2\alpha = 1

Keshav P R

5:31 a.m.

New subject: [arch-releng] [DRAFT][RFC][PATCH][archiso] Add UEFI boot support via Linux >= 3.3 EFI boot stub.

On Tue, Mar 27, 2012 at 07:04, Gerardo Exequiel Pozzi wrote:

...

On 03/26/2012 11:16 AM, Keshav P R wrote:

...
On Tue, Mar 20, 2012 at 23:15, Gerardo Exequiel Pozzi wrote:

...
...
This is going to increase the iso size like hell. Having the kernel and initrd files within a FAT image inside the iso is not a good idea. A 32 MB fat image, come on. I know this is required for CD booting, but this is not a good idea with efistub efilinux or elilo etc. For USB booting you can just have the files in the iso itself, wherein the user simply extract the iso in a FAT32 USB and boots from it. I say drop support for iso booting via this fat fs image and support uefi boot only in case of USBs.

Regards.

Keshav

OK, so just ignore this draft patch. UEFI boot support can be made manually by the user, just doing a copy of vmlinuz to the right place and optionally installing a boot manager.

A documentation on the wiki is sufficient.

You might be interested in rEFInd-x86_64 https://aur.archlinux.org/packages.php?ID=57632 which provides a nice menu for EFISTUB kernels.

Related info : http://www.rodsbooks.com/refind/linux.html http://www.rodsbooks.com/efi-bootloaders/efistub.html

[QUOTE from http://www.rodsbooks.com/refind/linux.html] rEFInd looks for a file called linux.conf in the same directory as the kernel file. This file is a practical requirement for booting from an auto-detected kernel. It consists of a series of lines, each of which consists of a label followed by a series of kernel options. The first line sets default options, and subsequent lines set options that are accessible from the main menu tag's submenu screen.

The intent of this system is that distribution maintainers can place their kernels, initial RAM disks, and a linux.conf file in their own subdirectory on the ESP. rEFInd will detect their kernels and create one main menu entry for each kernel. Each entry will implement as many options as there are lines in the linux.conf file. In this way, two or more distributions can each maintain their boot loader entries, without being too concerned for who maintains rEFInd as a whole. [/QUOTE]

The filename has been changed to refind_linux.conf in the upstream git repo so that it does not conflict with the proposed efistub config file by kernel devs

(http://sourceforge.net/p/refind/code/ci/c09200e2220b05bbade961bdc35f7da90d31...).

This should be pretty straightforward to implement in Archiso. For non-EFISTUB kernels like LTS ones, you can use efilinux-x86_64 https://aur.archlinux.org/packages.php?ID=57972 (Usage instructions - http://thread.gmane.org/gmane.linux.kernel/1172645 and http://article.gmane.org/gmane.linux.kernel/1175060). This might be a good alternative for grub2 uefi boot, although booting i686 kernels in x86_64 UEFI will not be supported by EFISTUB (which can be done using grub2). Support for mixed arch booting seems to have been merged for 3.4-rc1 .

Regards.

Keshav

Thanks for the work.

But this only added the advantage of passing command line options to the kernel. We still need a "FAT image" with bootx64.efi (rEFInd) + vmlinuz.efi + archiso.img (initramfs) + refind*.conf (for El Torito) that was the main dissapointed issue. Otherwise rEFInd can not find what file to load.

No. In this case just rEFInd (and the required icons - not all of them) needs to be in the FAT image. The kernels and initramfs can be in (ISO)/efi/(SUBDIR)/ along with (ISO)/efi/(SUBDIR)/refind_linux.conf containing the kernel parameters. If the (SUBDIR) is "arch" , ie. (ISO)/efi/arch/ , then refind will even display Archlinux icon making it easy for the user to differentiate the iso kernels from other kernels. All the answers are at http://www.rodsbooks.com/refind/ . Regards. Keshav

Gerardo Exequiel Pozzi

1:26 p.m.

New subject: [arch-releng] [DRAFT][RFC][PATCH][archiso] Add UEFI boot support via Linux >= 3.3 EFI boot stub.

On 03/27/2012 02:31 AM, Keshav P R wrote:

...

On Tue, Mar 27, 2012 at 07:04, Gerardo Exequiel Pozzi wrote:

...
On 03/26/2012 11:16 AM, Keshav P R wrote:

...
...
...
This is going to increase the iso size like hell. Having the kernel and initrd files within a FAT image inside the iso is not a good idea. A 32 MB fat image, come on. I know this is required for CD booting, but this is not a good idea with efistub efilinux or elilo etc. For USB booting you can just have the files in the iso itself, wherein the user simply extract the iso in a FAT32 USB and boots from it. I say drop support for iso booting via this fat fs image and support uefi boot only in case of USBs.

Regards.

Keshav

OK, so just ignore this draft patch. UEFI boot support can be made manually by the user, just doing a copy of vmlinuz to the right place and optionally installing a boot manager.

A documentation on the wiki is sufficient. You might be interested in rEFInd-x86_64 https://aur.archlinux.org/packages.php?ID=57632 which provides a nice

On Tue, Mar 20, 2012 at 23:15, Gerardo Exequiel Pozzi wrote: menu for EFISTUB kernels.

Related info : http://www.rodsbooks.com/refind/linux.html http://www.rodsbooks.com/efi-bootloaders/efistub.html

[QUOTE from http://www.rodsbooks.com/refind/linux.html] rEFInd looks for a file called linux.conf in the same directory as the kernel file. This file is a practical requirement for booting from an auto-detected kernel. It consists of a series of lines, each of which consists of a label followed by a series of kernel options. The first line sets default options, and subsequent lines set options that are accessible from the main menu tag's submenu screen.

The intent of this system is that distribution maintainers can place their kernels, initial RAM disks, and a linux.conf file in their own subdirectory on the ESP. rEFInd will detect their kernels and create one main menu entry for each kernel. Each entry will implement as many options as there are lines in the linux.conf file. In this way, two or more distributions can each maintain their boot loader entries, without being too concerned for who maintains rEFInd as a whole. [/QUOTE]

The filename has been changed to refind_linux.conf in the upstream git repo so that it does not conflict with the proposed efistub config file by kernel devs

(http://sourceforge.net/p/refind/code/ci/c09200e2220b05bbade961bdc35f7da90d31...).

This should be pretty straightforward to implement in Archiso. For non-EFISTUB kernels like LTS ones, you can use efilinux-x86_64 https://aur.archlinux.org/packages.php?ID=57972 (Usage instructions - http://thread.gmane.org/gmane.linux.kernel/1172645 and http://article.gmane.org/gmane.linux.kernel/1175060). This might be a good alternative for grub2 uefi boot, although booting i686 kernels in x86_64 UEFI will not be supported by EFISTUB (which can be done using grub2). Support for mixed arch booting seems to have been merged for 3.4-rc1 .

Regards.

Keshav

Thanks for the work.

But this only added the advantage of passing command line options to the kernel. We still need a "FAT image" with bootx64.efi (rEFInd) + vmlinuz.efi + archiso.img (initramfs) + refind*.conf (for El Torito) that was the main dissapointed issue. Otherwise rEFInd can not find what file to load.

No. In this case just rEFInd (and the required icons - not all of them) needs to be in the FAT image. The kernels and initramfs can be in (ISO)/efi/(SUBDIR)/ along with (ISO)/efi/(SUBDIR)/refind_linux.conf containing the kernel parameters. If the (SUBDIR) is "arch" , ie. (ISO)/efi/arch/ , then refind will even display Archlinux icon making it easy for the user to differentiate the iso kernels from other kernels.

All the answers are at http://www.rodsbooks.com/refind/ .

Regards.

Keshav

Are you sure? The only thing that can do rEFInd is launch EFI apps from drives listed by EFI firmware. A filesystem ISO9660 is not listed as a drive with filesystem by EFI, and rEFInd does not understand about ISO9660. Thanks. -- Gerardo Exequiel Pozzi \cos^2\alpha + \sin^2\alpha = 1

Keshav P R

29 Mar 29 Mar

5:20 p.m.

New subject: [arch-releng] [DRAFT][RFC][PATCH][archiso] Add UEFI boot support via Linux >= 3.3 EFI boot stub.

On Tue, Mar 27, 2012 at 18:56, Gerardo Exequiel Pozzi wrote:

...

On 03/27/2012 02:31 AM, Keshav P R wrote:

...
On Tue, Mar 27, 2012 at 07:04, Gerardo Exequiel Pozzi wrote:

...
On 03/26/2012 11:16 AM, Keshav P R wrote:

...
On Tue, Mar 20, 2012 at 23:15, Gerardo Exequiel Pozzi wrote:

...
...
This is going to increase the iso size like hell. Having the kernel and initrd files within a FAT image inside the iso is not a good idea. A 32 MB fat image, come on. I know this is required for CD booting, but this is not a good idea with efistub efilinux or elilo etc. For USB booting you can just have the files in the iso itself, wherein the user simply extract the iso in a FAT32 USB and boots from it. I say drop support for iso booting via this fat fs image and support uefi boot only in case of USBs.

Regards.

Keshav

OK, so just ignore this draft patch. UEFI boot support can be made manually by the user, just doing a copy of vmlinuz to the right place and optionally installing a boot manager.

A documentation on the wiki is sufficient.

You might be interested in rEFInd-x86_64 https://aur.archlinux.org/packages.php?ID=57632 which provides a nice menu for EFISTUB kernels.

Related info : http://www.rodsbooks.com/refind/linux.html http://www.rodsbooks.com/efi-bootloaders/efistub.html

[QUOTE from http://www.rodsbooks.com/refind/linux.html] rEFInd looks for a file called linux.conf in the same directory as the kernel file. This file is a practical requirement for booting from an auto-detected kernel. It consists of a series of lines, each of which consists of a label followed by a series of kernel options. The first line sets default options, and subsequent lines set options that are accessible from the main menu tag's submenu screen.

The intent of this system is that distribution maintainers can place their kernels, initial RAM disks, and a linux.conf file in their own subdirectory on the ESP. rEFInd will detect their kernels and create one main menu entry for each kernel. Each entry will implement as many options as there are lines in the linux.conf file. In this way, two or more distributions can each maintain their boot loader entries, without being too concerned for who maintains rEFInd as a whole. [/QUOTE]

The filename has been changed to refind_linux.conf in the upstream git repo so that it does not conflict with the proposed efistub config file by kernel devs

(http://sourceforge.net/p/refind/code/ci/c09200e2220b05bbade961bdc35f7da90d31...).

This should be pretty straightforward to implement in Archiso. For non-EFISTUB kernels like LTS ones, you can use efilinux-x86_64 https://aur.archlinux.org/packages.php?ID=57972 (Usage instructions - http://thread.gmane.org/gmane.linux.kernel/1172645 and http://article.gmane.org/gmane.linux.kernel/1175060). This might be a good alternative for grub2 uefi boot, although booting i686 kernels in x86_64 UEFI will not be supported by EFISTUB (which can be done using grub2). Support for mixed arch booting seems to have been merged for 3.4-rc1 .

Regards.

Keshav

Thanks for the work.

But this only added the advantage of passing command line options to the kernel. We still need a "FAT image" with bootx64.efi (rEFInd) + vmlinuz.efi + archiso.img (initramfs) + refind*.conf (for El Torito) that was the main dissapointed issue. Otherwise rEFInd can not find what file to load.

No. In this case just rEFInd (and the required icons - not all of them) needs to be in the FAT image. The kernels and initramfs can be in (ISO)/efi/(SUBDIR)/ along with (ISO)/efi/(SUBDIR)/refind_linux.conf containing the kernel parameters. If the (SUBDIR) is "arch" , ie. (ISO)/efi/arch/ , then refind will even display Archlinux icon making it easy for the user to differentiate the iso kernels from other kernels.

All the answers are at http://www.rodsbooks.com/refind/ .

Regards.

Keshav

Are you sure?

The only thing that can do rEFInd is launch EFI apps from drives listed by EFI firmware. A filesystem ISO9660 is not listed as a drive with filesystem by EFI, and rEFInd does not understand about ISO9660.

Thanks.

-- Gerardo Exequiel Pozzi \cos^2\alpha + \sin^2\alpha = 1

Rod? - Keshav

Gerardo Exequiel Pozzi

1 Apr 1 Apr

5:48 p.m.

New subject: [arch-releng] [DRAFT][RFC][PATCH][archiso] Add UEFI boot support via Linux >= 3.3 EFI boot stub.

On 03/20/2012 12:59 PM, Gerardo Exequiel Pozzi wrote:

...

Support is only added to x86_64. This only works via (U)EFI shell. Boot with:

fs0:\EFI\linux\vmlinuz.efi archisolabel=ARCH_201203 initrd=\EFI\linux\archiso.img

There are plans to support command line options via a config file (not yet in linux-3.3), in such case vmlinuz.efi can be renamed to bootia64.efi and placed to \EFI\boot to automatic boot.

I only pushed to master the mkarchiso part (is optionally): + # If exists, add an EFI "El Torito" boot image (FAT filesystem) to ISO-9660 image. + if [[ -f "${work_dir}/iso/EFI/archiso/efiboot.img" ]]; then + _iso_efi_boot_args="--efi-boot EFI/archiso/efiboot.img" + fi Such .img acts as ESP (EFI System Partition), so you can push anything inside for EFI boot. (PENDING) Now remains decision about what will go to "efiboot.img" and what of x86_64 isos will be EFI enabled (configs/releng/build.sh) +# Prepare EFI "El Torito" boot image (using Linux >= 3.3 EFI boot stub) +make_boot_efi() { + if [[ ! -e ${work_dir}/build.${FUNCNAME} ]]; then + if [[ ${arch} == "x86_64" ]]; then + mkdir -p ${work_dir}/iso/EFI/archiso + dd of=${work_dir}/iso/EFI/archiso/efiboot.img bs=1 seek=20M count=0 + mkfs.vfat ${work_dir}/iso/EFI/archiso/efiboot.img + mkdir -p ${work_dir}/efiboot + mount ${work_dir}/iso/EFI/archiso/efiboot.img ${work_dir}/efiboot + mkdir -p ${work_dir}/efiboot/EFI/archiso + cp ${work_dir}/iso/${install_dir}/boot/x86_64/vmlinuz ${work_dir}/efiboot/EFI/archiso/vmlinuz.efi + cp ${work_dir}/iso/${install_dir}/boot/x86_64/archiso.img ${work_dir}/efiboot/EFI/archiso/archiso.img + # There are plans to support command line options via a config file (not yet in Linux-3.3) + # echo "archisolabel=${iso_label} initrd=\EFI\archiso\archiso.img" | iconv -f ascii -t ucs2 > ${work_dir}/efiboot/EFI/archiso/vmlinuz.conf + umount ${work_dir}/efiboot + fi + : > ${work_dir}/build.${FUNCNAME} + fi +} This increment final ISO in 20MiB. -- Gerardo Exequiel Pozzi \cos^2\alpha + \sin^2\alpha = 1

4407

Age (days ago)

4419

Last active (days ago)

List overview

Download

10 comments

2 participants

participants (2)

Gerardo Exequiel Pozzi
Keshav P R