[ipxe-devel] Regression with commit fc87adb46c1395b09302085e9d15fcd8ab3c31fe - [efi] Expose downloaded images via EFI_SIMPLE_FILE_SYSTEM_PROTOCOL on IMAGE_EFI

Jarrod Johnson jarrod.b.johnson at gmail.com
Wed Apr 10 18:27:40 UTC 2013

Ok, don't know if someone could clarify, but it *looks* like it requires
that a candidate device be put into efi_pci_devices list, but I don't see
the relevant function being called when running as snponly, meaning no
'pci' devices are listed at all, nothing is considered to be snp, etc etc...

On Wed, Apr 10, 2013 at 1:33 PM, Jarrod Johnson
<jarrod.b.johnson at gmail.com>wrote:

> So prior to the commit, snponly latched onto the device as provided from
> loaded image.  The switch to last_opened_snpdev() seems to not be
> working.....
> On Wed, Apr 10, 2013 at 1:21 PM, Jarrod Johnson <
> jarrod.b.johnson at gmail.com> wrote:
>> This was working for me, but broke as of
>> fc87adb commit...  If I back that one out, chain loading efi images from
>> snponly.efi works again...
>>  On Tue, Apr 9, 2013 at 11:42 AM, James A. Peltier <jpeltier at sfu.ca>wrote:
>>>  ------------------------------
>>> 2013/4/6 Michael Brown <mbrown at fensystems.co.uk>
>>>> This will give you an iPXE EFI ROM; you'll see it show up as "EFI
>>>> Network" in the EFI boot device selection screen, and it should thereafter
>>>> look and feel similar to normal iPXE.
>>>> There is no such thing as a non-EFI (aka BIOS or "legacy") ROM which is
>>>> capable of loading an EFI image.  Such a thing simply does not and can not
>>>> exist.
>>>> Michael
>>> I didn't know this. Up to know I've been using a modified version of
>>> ipxe that gives me a shell after initilizing the devices (just a modified
>>> main() function), so that I can load and boot any image over a network.
>>> I've always had all image types enabled in general.h and never had an
>>> issues when starting ipxe. Right now my system just reboots regardless of
>>> the not supported IMAGE_EFI. From my point of view this is a regression,
>>> because befor this commit ipxe started without glitches regardless if an
>>> image is supported or not. So even if the image is not supported then ipxe
>>> should gracefully continue initilization and not reboot the mashine....
>>> From the shell I can point to and download any efi image over the
>>> network, but why it cannot boot the system?
>>> Joshua
>>> I have iPXE working with both legacy BIOS and EFI machines right now,
>>> except that I can't get it to chainload to an EFI bootloader such as
>>> CentOS's BOOTX64.efi.  I always end up with "Could not boot: No such
>>> device", although considering this is my first time trying to do this I'm
>>> probably not doing it right.  I'm just trying with
>>>   chain
>>> http://mirror.its.sfu.ca/mirror/CentOS/6/os/x86_64/EFI/BOOT/BOOTX64.efi
>>> which is probably not right.  Any ideas?
>>> --
>>> James A. Peltier
>>> Manager, IT Services - Research Computing Group
>>> Simon Fraser University - Burnaby Campus
>>> Phone   : 778-782-6573
>>> Fax     : 778-782-3045
>>> E-Mail  : jpeltier at sfu.ca
>>> Website : http://www.sfu.ca/itservices
>>> “A successful person is one who can lay a solid foundation from the
>>> bricks others have thrown at them.” -David Brinkley via Luke Shaw
>>> _______________________________________________
>>> ipxe-devel mailing list
>>> ipxe-devel at lists.ipxe.org
>>> https://lists.ipxe.org/mailman/listinfo.cgi/ipxe-devel
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.ipxe.org/pipermail/ipxe-devel/attachments/20130410/5d6b84c0/attachment.htm>

More information about the ipxe-devel mailing list