Hi, Renato Bispo wrote: > * Under BIOS at least
More we cannot expect from this setup. The next experiment would be to create a new partition of type 0xef (1MiB, with no filesystem on it, should be ok) and to copy the file /boot/grub/efi.img, which is actually a FAT filesystem image. Then one would try with an EFI system where legacy BIOS emulation is disabled or by a qemu with OVMF as firmware qemu-system-x86_64 -enable-kvm -bios /usr/share/ovmf/OVMF.fd -hda /dev/sdc > PS - I'm curious about this: when I opened the images with an archive > manager (more specifically with the one that comes with the MATE desktop), I > saw a directory named "[BOOT]" that contained files with a name along the > lines of "...no-emulation...". The date of creation was 1969. Pretty weird, > haha. Do you have any idea about what it is? Probably a synthetic directory which represents the El Torito boot images. "...no-emulation..." applies to both, the binary /isolinux/isolinux.bin, and the FAT image /boot/grub/efi.img. The boot catalog does not contain file names but only some info fields like intended firmware platform, bootability, floppy-or-disk emulation, x86 load address, size, block address. Compare the sizes of /isolinux/isolinux.bin and /boot/grub/efi.img with the ones reported by the archive manager in the [BOOT] directory. 1969 is a strange date for a Unix-ly system. The lowest possible file date is supposed to be 1 Jan 1970. Well, if my theory about synthetic files is true, then the date is purely synthetic, too. Have a nice day :) Thomas
