[ipxe-devel] Generating a BIOS/UEFI hybrid ISO image

[Dean Westhead]

Hi,

The directory tree's for each ISO :

New ( non working ) ISO :

/new_iso/
├── boot.catalog
├── esp.img
├── ipxe.lkrn
├── isolinux.bin
└── isolinux.cfg

0 directories, 5 files

And the esp.img file on the non working ISO :

/new_esp.img/
└── EFI
    └── BOOT
        ├── BOOTIA32.EFI
        └── BOOTX64.EFI

2 directories, 2 files

The old ( working ) ISO :

/old_iso/
├── boot.cat
├── efiboot.img
├── ipxe.krn
├── isolinux.bin
└── isolinux.cfg

0 directories, 5 files

And the efiboot.img file on the working ISO :

/old_efiboot.img/
└── EFI
    └── BOOT
        ├── BOOTIA32.EFI
        └── BOOTX64.EFI

2 directories, 2 files

When the ISO file is loaded into RUFUS to write to a USB I get :

New ( non working ) ISO :

RUFUS "sees" the ISO as only being for a target system of "BIOS (or UEFI-CSM)"

Old ( working ) ISO :

RUFUS "sees" the ISO as being for a target system of "BIOS or UEFI"

Dean.



----- Original Message -----
From: "Geert Stappers" <stappers at stappers.nl>
To: "ipxe-devel" <ipxe-devel at lists.ipxe.org>
Sent: Thursday, 7 October, 2021 20:07:38
Subject: Re: [ipxe-devel] Generating a BIOS/UEFI hybrid ISO image

On Thu, Oct 07, 2021 at 03:03:06PM +0100, Michael Brown wrote:
> On 07/10/2021 14:52, Dean Westhead wrote:
> > Sorry ... I didnt want to take lots of your time if it is only me
> > having this issue and everyone else is working fine.

It is not important how much "works for me" exists.
Interesting is exploring what can be improved.
 
> > In the old "working" ISO, there is the following files :
> > 
> > boot.cat
> > efiboot.img
> > ipxe.krn
> > isolinux.bin
> > isolinux.cfg
> > 
> > The new one that isnt seen as a EFI bootable disk has :
> > 
> > boot.catalog
> > esp.img
> > ipxe.lkrn
> > isolinux.big
> > isolinux.cfg
> > 
> > I will open the EFI image too and see what is in that as soon as i
> > can and let you know about that too.
> 
> Thanks!  Most of those files are for BIOS booting: the relevant ones for
> UEFI are efiboot.img/esp.img, which should both be FAT filesystem images
> containing a file \EFI\Boot\BootX64.efi (which should be the ipxe.efi
> binary).

I think a "directory tree" will help.  As happy user of netbooting
systems can't I provide a "directory tree" of a known good.

An attempt to illustrate "directory tree" by using `tree /boot`
(Warning: non-ASCII characters ahead)

| $ tree /boot | wc
|     344    1346   12736
| $ tree /boot | grep -v -e .mo$ -e .mod$
| /boot
| ├── config-5.10.0-4-amd64
| ├── config-5.10.0-5-amd64
| ├── grub
| │   ├── fonts
| │   │   └── unicode.pf2
| │   ├── grub.cfg
| │   ├── grubenv
| │   ├── i386-pc
| │   │   ├── boot.img
| │   │   ├── command.lst
| │   │   ├── core.img
| │   │   ├── crypto.lst
| │   │   ├── efiemu32.o
| │   │   ├── efiemu64.o
| │   │   ├── fs.lst
| │   │   ├── moddep.lst
| │   │   ├── modinfo.sh
| │   │   ├── partmap.lst
| │   │   ├── parttool.lst
| │   │   ├── terminal.lst
| │   │   ├── video.lst
| │   ├── locale
| │   └── unicode.pf2
| ├── initrd.img-5.10.0-4-amd64
| ├── initrd.img-5.10.0-5-amd64
| ├── lost+found [error opening dir]
| ├── System.map-5.10.0-4-amd64
| ├── System.map-5.10.0-5-amd64
| ├── vmlinuz-5.10.0-4-amd64
| └── vmlinuz-5.10.0-5-amd64
| 


Regards
Geert Stappers
-- 
Silence is hard to parse
_______________________________________________
ipxe-devel mailing list
ipxe-devel at lists.ipxe.org
https://lists.ipxe.org/mailman/listinfo/ipxe-devel