Hi Josh,
Thanks for getting back to me.
Thats good news, hopefully that means that I shouldn't run into too many
more difficulties moving forward :). I only brought up the question
about native EFI support because I've heard that Apple butchered the
spec for their firmware.
I'll work on getting write permissions to the wiki this afternoon so I
can start helping out with documenting the EFI build process.
Like I said before, I haven't really put much time into debugging this
myself, so I certainly don't expect you to. But, since you asked, here
is the output so far:
fs0:\> e1000e.efi
InstallProtocolInterface: 5B1B31A1-9562-11D2-8E3F-00A0C969723B 3588DA40
InstallProtocolInterface: 4C8A2451-C207-405B-9694-99EA13251341 358279A8
Loading driver at 0x357BC000 EntryPoint=0x357C62D8 e1000e.efi
InstallProtocolInterface: 47C7B223-C42A-11D2-8E57-00A0C969723B 37425A60
gPXE initialising devices...
gPXE 1.0.0+ -- Open Source Boot Firmware -- http://etherboot.org
Features: HTTP DNS TFTP EFI
net0: 00:17:3c:00:85:fc on PCI05:00.0 (open)
[Link:up, TX:0 TXE:0 RX:0 RXE:0]
DHCP (net0 00:17:3c:00:85:fc)!!!! X64 Exception Type -
0000000000000006 CPU Apic ID - 00000000!!!!
RIP - 00000000357BC241, CS - 0000000000000038, RFLAGS - 0000000000010287
RAX - 00000000357BC07F, RCX - 000000003581A018, RDX - 00000000FFFFFFFF
RBX - 00000000357D6508, RSP - 0000000037425628, RBP - 00000000357D5590
RSI - 00000000357D6508, RDI - 00000000357D5594
R8 - 0000000000000000, R9 - 000000004008F5C0, R10 - 00000000357D1C9D
R11 - 00000000374252E0, R12 - 00000000357D6508, R13 - 000000003588DC18
R14 - 0000000035B40018, R15 - 000000003763EF18
DS - 0000000000000030, ES - 0000000000000030, FS - 0000000000000018
GS - 0000000000000018, SS - 0000000000000030
GDTR - 000037496E600047 00000000357C0000, LDTR - 0000000000000000
IDTR - 0000374979900FFF 00000000357D0000, TR - 0000000000000000
CR0 - 0000000080000013, CR2 - 0000000000000000, CR3 - 0000000036DFB000
CR4 - 0000000000000628, CR8 - 0000000000000000
DR0 - 0000000000000000, DR1 - 0000000000000000, DR2 - 0000000000000000
DR3 - 0000000000000000, DR6 - 00000000FFFF0FF0, DR7 - 0000000000000400
ERROR: C90000002:V3050006 I C9DCF469-A7C4-11D5-87DA-00062945C3B9 37497150
ERROR_UNRECOVERED:SOFTWARE_DXE_BS_DRIVER:ABORTED:0
As you can see I built with the shiny new e1000e driver (Thank you Marty
and NGC :) )
The extra debug you see is a result of having the debug output enabled
in the system firmware. Hitting Ctrl-B when prompted also causes the
exception.
Thanks,
Mike
Joshua Oreman wrote:
On Fri, Apr 2, 2010 at 10:53 AM, Mike Bishton <[email protected]> wrote:
Hi Guys,
I've been experimenting with gPXE on our EFI platform. I finally got it
to build after applying Piotr Jaroszyński's patch and installing
gcc-4.4.3. I'm now running into a runtime exception. I'll spare you the
details until I get a chance to take a stab at debugging it myself.
My question is: Has anyone out there tried using gPXE on a native EFI
firmware (not Apple's)? I got the impression from the documentation on
the gPXE wiki that EFI support was added for, and only tested on,
Apple's EFI firmware.
EFI support was certainly added for native EFI firmware, and tested
under such; gPXE didn't even compile under OS X until some patches
around this time last year. There just isn't any native EFI
documentation on the wiki, because nobody has contributed any. (You
could rectify this :-)
We'd be very interested in hearing the details of the runtime error.
-- Josh
Thanks,
Mike
--
Mike Bishton
[email protected]
Extreme Engineering Solutions, Inc.
608-833-1155 x127
www.xes-inc.com
_______________________________________________
gPXE mailing list
[email protected]
http://etherboot.org/mailman/listinfo/gpxe
_______________________________________________
gPXE mailing list
[email protected]
http://etherboot.org/mailman/listinfo/gpxe
