* Enabling boot menu via serial & PXE boot in CorebootPayloadPkg
@ 2017-11-24 9:15 Cameron Craig
2017-11-25 15:25 ` You, Benjamin
0 siblings, 1 reply; 9+ messages in thread
From: Cameron Craig @ 2017-11-24 9:15 UTC (permalink / raw)
To: 'edk2-devel@lists.01.org'
Hi all,
I'm new to this list and new to edk2 integration.
Currently I'm working on an Intel Leaf Hill CRB, attempting to produce a coreboot payload consisting of a Tianocore EDKII UDK 2017 UEFI boot manager.
I have basic functionality, but a few useful features are currently missing from my build:
1. User interface via serial.
We will not have the luxury of a video output so need to be able to navigate the boot menu etc. via serial.
In an ideal world I would be looking for a Boolean value to toggle :) But I imagine there might be a little more to it.
2. PXE Boot.
So far I have sources and built an UNDI driver and pinged a local network device.
I have also attempted to enable the necessary features for PXE boot [1].
But I get an error message:
```
$ ipconfig
MAC Address: <valid MAC addr>
Broadcast MAC: FF FF FF FF FF FF
ipconfig: Locate protocol error: 'PXE base code protocol'
```
So I'm thinking some drivers are not being loaded?
Any suggestions for enabling these features would be greatly appreciated.
[1] https://github.com/tianocore/tianocore.github.io/wiki/NetworkPkg-Getting-Started-Guide -> FEATURES ENABLING
Cheers,
Cameron
Cameron Craig | Graduate Software Engineer | Exterity Limited
tel: +44 1383 828 250 | fax: | mobile:
e: Cameron.Craig@exterity.com | w: www.exterity.com
Exterity is a leading provider of IP Video and Digital Signage solutions that helps organizations to harness the power of video to communicate, educate and entertain. Our end-to-end solutions enable you to take TV and video content directly from any source and manage its delivery, live or on demand, to any connected device via your existing network. For more information or to schedule a product demonstration, contact Exterity on +44(0)1383 828 250 or visit www.exterity.com
Legal Notice
Unless expressly stated otherwise, this message is confidential and may be privileged. It is intended for the addressee(s) only. Access to this e-mail by anyone else is unauthorized. If you are not an addressee, any disclosure or copying of the contents of this e-mail or any action taken (or not taken) in reliance on it is unauthorized and may be unlawful. If you are not an addressee, please inform the sender immediately.
Exterity Limited is registered in Scotland under No. 225313 with its registered office at Ridge Way, Hillend Industrial Park, Dalgety Bay, KY11 9JD.
______________________________________________________________________
This email has been scanned by the Symantec Email Security.cloud service.
For more information please visit http://www.symanteccloud.com
______________________________________________________________________
^ permalink raw reply [flat|nested] 9+ messages in thread
* Re: Enabling boot menu via serial & PXE boot in CorebootPayloadPkg
2017-11-24 9:15 Enabling boot menu via serial & PXE boot in CorebootPayloadPkg Cameron Craig
@ 2017-11-25 15:25 ` You, Benjamin
2017-11-25 16:21 ` You, Benjamin
0 siblings, 1 reply; 9+ messages in thread
From: You, Benjamin @ 2017-11-25 15:25 UTC (permalink / raw)
To: Cameron Craig, 'edk2-devel@lists.01.org'
Hi Cameron,
CorebootPayloadPkg does support serial output as user interface. To enable
serial, the CorebootPayloadPkg retrieves serial information from Coreboot
through CorebootModulePkg\Library\CbParseLib\CbParseLib.c =>
CbParseSerialInfo(), which is called by CorebootPayloadPkg\Library\
PlatformHookLib\PlatformHookLib.c => PlatformHookSerialPortInitialize(),
which is in turn called by CorebootModulePkg\Library\BaseSerialPortLib16550
\BaseSerialPortLib16550.c ==> SerialPortInitialize().
Have you seen serial output info during Coreboot? If the answer is no, then
Coreboot should be tweaked. If the answer is yes, but you cannot see serial
output in Coreboot Payload, then probably the above call sequence needs to
be checked. If you do not have a debugger, one way to trace code flow is to
insert raw serial outputs in the code flow. This should be doable since
Coreboot already does serial output. Once the serial output functions
correctly in the Coreboot Payload, Boot Menu / UI through serial should be
automatically supported.
On networking, you might refer to the Minnow Board v3 source tree, at
https://github.com/tianocore/edk2-platforms/tree/devel-MinnowBoard3-UDK2017
Minnow Board v3 uses the same SOC as Leaf Hill. You might look at
Platform/BroxtonPlatformPkg/PlatformPkg.fdf file for a reference on which
components are used for network / PXE.
Thanks,
- ben
> -----Original Message-----
> From: edk2-devel [mailto:edk2-devel-bounces@lists.01.org] On Behalf Of
> Cameron Craig
> Sent: Friday, November 24, 2017 5:16 PM
> To: 'edk2-devel@lists.01.org' <edk2-devel@lists.01.org>
> Subject: [edk2] Enabling boot menu via serial & PXE boot in CorebootPayloadPkg
>
> Hi all,
>
> I'm new to this list and new to edk2 integration.
> Currently I'm working on an Intel Leaf Hill CRB, attempting to produce a
> coreboot payload consisting of a Tianocore EDKII UDK 2017 UEFI boot manager.
>
> I have basic functionality, but a few useful features are currently missing from
> my build:
>
> 1. User interface via serial.
> We will not have the luxury of a video output so need to be able to navigate the
> boot menu etc. via serial.
> In an ideal world I would be looking for a Boolean value to toggle :) But I
> imagine there might be a little more to it.
>
> 2. PXE Boot.
> So far I have sources and built an UNDI driver and pinged a local network device.
> I have also attempted to enable the necessary features for PXE boot [1].
> But I get an error message:
> ```
> $ ipconfig
> MAC Address: <valid MAC addr>
> Broadcast MAC: FF FF FF FF FF FF
> ipconfig: Locate protocol error: 'PXE base code protocol'
> ```
> So I'm thinking some drivers are not being loaded?
>
> Any suggestions for enabling these features would be greatly appreciated.
>
> [1] https://github.com/tianocore/tianocore.github.io/wiki/NetworkPkg-
> Getting-Started-Guide -> FEATURES ENABLING
>
> Cheers,
> Cameron
>
>
> Cameron Craig | Graduate Software Engineer | Exterity Limited
> tel: +44 1383 828 250 | fax: | mobile:
> e: Cameron.Craig@exterity.com | w: www.exterity.com
>
> Exterity is a leading provider of IP Video and Digital Signage solutions that helps
> organizations to harness the power of video to communicate, educate and
> entertain. Our end-to-end solutions enable you to take TV and video content
> directly from any source and manage its delivery, live or on demand, to any
> connected device via your existing network. For more information or to
> schedule a product demonstration, contact Exterity on +44(0)1383 828 250 or
> visit www.exterity.com
>
> Legal Notice
> Unless expressly stated otherwise, this message is confidential and may be
> privileged. It is intended for the addressee(s) only. Access to this e-mail by
> anyone else is unauthorized. If you are not an addressee, any disclosure or
> copying of the contents of this e-mail or any action taken (or not taken) in
> reliance on it is unauthorized and may be unlawful. If you are not an addressee,
> please inform the sender immediately.
>
> Exterity Limited is registered in Scotland under No. 225313 with its registered
> office at Ridge Way, Hillend Industrial Park, Dalgety Bay, KY11 9JD.
>
>
> _________________________________________________________________
> _____
> This email has been scanned by the Symantec Email Security.cloud service.
> For more information please visit http://www.symanteccloud.com
> _________________________________________________________________
> _____
> _______________________________________________
> edk2-devel mailing list
> edk2-devel@lists.01.org
> https://lists.01.org/mailman/listinfo/edk2-devel
^ permalink raw reply [flat|nested] 9+ messages in thread
* Re: Enabling boot menu via serial & PXE boot in CorebootPayloadPkg
2017-11-25 15:25 ` You, Benjamin
@ 2017-11-25 16:21 ` You, Benjamin
2017-11-30 14:11 ` Cameron Craig
0 siblings, 1 reply; 9+ messages in thread
From: You, Benjamin @ 2017-11-25 16:21 UTC (permalink / raw)
To: You, Benjamin, Cameron Craig, 'edk2-devel@lists.01.org'
Hi Cameron,
BTW, please use debug build for Coreboot Payload, such that debug
information can be shown in serial console from the very early stage in the
Payload's execution. This would help validating the functioning of serial.
Thanks,
- ben
> -----Original Message-----
> From: edk2-devel [mailto:edk2-devel-bounces@lists.01.org] On Behalf Of You,
> Benjamin
> Sent: Saturday, November 25, 2017 11:25 PM
> To: Cameron Craig <Cameron.Craig@exterity.com>; 'edk2-devel@lists.01.org'
> <edk2-devel@lists.01.org>
> Subject: Re: [edk2] Enabling boot menu via serial & PXE boot in
> CorebootPayloadPkg
>
> Hi Cameron,
>
> CorebootPayloadPkg does support serial output as user interface. To enable
> serial, the CorebootPayloadPkg retrieves serial information from Coreboot
> through CorebootModulePkg\Library\CbParseLib\CbParseLib.c =>
> CbParseSerialInfo(), which is called by CorebootPayloadPkg\Library\
> PlatformHookLib\PlatformHookLib.c => PlatformHookSerialPortInitialize(),
> which is in turn called by CorebootModulePkg\Library\BaseSerialPortLib16550
> \BaseSerialPortLib16550.c ==> SerialPortInitialize().
>
> Have you seen serial output info during Coreboot? If the answer is no, then
> Coreboot should be tweaked. If the answer is yes, but you cannot see serial
> output in Coreboot Payload, then probably the above call sequence needs to
> be checked. If you do not have a debugger, one way to trace code flow is to
> insert raw serial outputs in the code flow. This should be doable since
> Coreboot already does serial output. Once the serial output functions
> correctly in the Coreboot Payload, Boot Menu / UI through serial should be
> automatically supported.
>
> On networking, you might refer to the Minnow Board v3 source tree, at
> https://github.com/tianocore/edk2-platforms/tree/devel-MinnowBoard3-
> UDK2017
>
> Minnow Board v3 uses the same SOC as Leaf Hill. You might look at
> Platform/BroxtonPlatformPkg/PlatformPkg.fdf file for a reference on which
> components are used for network / PXE.
>
> Thanks,
>
> - ben
>
> > -----Original Message-----
> > From: edk2-devel [mailto:edk2-devel-bounces@lists.01.org] On Behalf Of
> > Cameron Craig
> > Sent: Friday, November 24, 2017 5:16 PM
> > To: 'edk2-devel@lists.01.org' <edk2-devel@lists.01.org>
> > Subject: [edk2] Enabling boot menu via serial & PXE boot in
> CorebootPayloadPkg
> >
> > Hi all,
> >
> > I'm new to this list and new to edk2 integration.
> > Currently I'm working on an Intel Leaf Hill CRB, attempting to produce a
> > coreboot payload consisting of a Tianocore EDKII UDK 2017 UEFI boot
> manager.
> >
> > I have basic functionality, but a few useful features are currently missing from
> > my build:
> >
> > 1. User interface via serial.
> > We will not have the luxury of a video output so need to be able to navigate
> the
> > boot menu etc. via serial.
> > In an ideal world I would be looking for a Boolean value to toggle :) But I
> > imagine there might be a little more to it.
> >
> > 2. PXE Boot.
> > So far I have sources and built an UNDI driver and pinged a local network
> device.
> > I have also attempted to enable the necessary features for PXE boot [1].
> > But I get an error message:
> > ```
> > $ ipconfig
> > MAC Address: <valid MAC addr>
> > Broadcast MAC: FF FF FF FF FF FF
> > ipconfig: Locate protocol error: 'PXE base code protocol'
> > ```
> > So I'm thinking some drivers are not being loaded?
> >
> > Any suggestions for enabling these features would be greatly appreciated.
> >
> > [1] https://github.com/tianocore/tianocore.github.io/wiki/NetworkPkg-
> > Getting-Started-Guide -> FEATURES ENABLING
> >
> > Cheers,
> > Cameron
> >
> >
> > Cameron Craig | Graduate Software Engineer | Exterity Limited
> > tel: +44 1383 828 250 | fax: | mobile:
> > e: Cameron.Craig@exterity.com | w: www.exterity.com
> >
> > Exterity is a leading provider of IP Video and Digital Signage solutions that
> helps
> > organizations to harness the power of video to communicate, educate and
> > entertain. Our end-to-end solutions enable you to take TV and video content
> > directly from any source and manage its delivery, live or on demand, to any
> > connected device via your existing network. For more information or to
> > schedule a product demonstration, contact Exterity on +44(0)1383 828 250 or
> > visit www.exterity.com
> >
> > Legal Notice
> > Unless expressly stated otherwise, this message is confidential and may be
> > privileged. It is intended for the addressee(s) only. Access to this e-mail by
> > anyone else is unauthorized. If you are not an addressee, any disclosure or
> > copying of the contents of this e-mail or any action taken (or not taken) in
> > reliance on it is unauthorized and may be unlawful. If you are not an addressee,
> > please inform the sender immediately.
> >
> > Exterity Limited is registered in Scotland under No. 225313 with its registered
> > office at Ridge Way, Hillend Industrial Park, Dalgety Bay, KY11 9JD.
> >
> >
> >
> _________________________________________________________________
> > _____
> > This email has been scanned by the Symantec Email Security.cloud service.
> > For more information please visit http://www.symanteccloud.com
> >
> _________________________________________________________________
> > _____
> > _______________________________________________
> > edk2-devel mailing list
> > edk2-devel@lists.01.org
> > https://lists.01.org/mailman/listinfo/edk2-devel
> _______________________________________________
> edk2-devel mailing list
> edk2-devel@lists.01.org
> https://lists.01.org/mailman/listinfo/edk2-devel
^ permalink raw reply [flat|nested] 9+ messages in thread
* Re: Enabling boot menu via serial & PXE boot in CorebootPayloadPkg
2017-11-25 16:21 ` You, Benjamin
@ 2017-11-30 14:11 ` Cameron Craig
2017-12-01 0:31 ` You, Benjamin
0 siblings, 1 reply; 9+ messages in thread
From: Cameron Craig @ 2017-11-30 14:11 UTC (permalink / raw)
To: 'You, Benjamin', 'edk2-devel@lists.01.org'
Hi Benjamin,
Thanks for the pointers.
>> On networking, you might refer to the Minnow Board v3 source tree, at
>> https://github.com/tianocore/edk2-platforms/tree/devel-MinnowBoard3-
>> UDK2017
>>
>> Minnow Board v3 uses the same SOC as Leaf Hill. You might look at
>> Platform/BroxtonPlatformPkg/PlatformPkg.fdf file for a reference on
>> which components are used for network / PXE.
Network boot/PXE is now functioning, I just had to link in the UNDI driver in edk2 rather than loading via USB.
It's just the serial boot menu I'm trying to get working now.
>BTW, please use debug build for Coreboot Payload, such that debug
>information can be shown in serial console from the very early stage in the
>Payload's execution. This would help validating the functioning of serial.
Interestingly, my debug build was complaining that it ran out of room when attempting to fit everything in the UEFIPAYLOAD.
When I strip out the network additions and keep DEBUG on, Tianocore builds but errors at runtime:
```
Failed to add memory space :0xFEE00000 0x100000
```
I'm guessing I can increase the size of a region somewhere to avoid this issue?
>> Have you seen serial output info during Coreboot? If the answer is no,
>> then Coreboot should be tweaked. If the answer is yes, but you cannot
>> see serial output in Coreboot Payload, then probably the above call
>> sequence needs to be checked. If you do not have a debugger, one way
>> to trace code flow is to insert raw serial outputs in the code flow.
I get serial output from coreboot and edk2, just not the boot menu.
>> This should be doable since Coreboot already does serial output. Once
>> the serial output functions correctly in the Coreboot Payload, Boot
>> Menu / UI through serial should be automatically supported.
That's not happening in my case. I'm currently trying to get the debug build to run.
Cheers,
Cameron
Cameron Craig | Graduate Software Engineer | Exterity Limited
tel: +44 1383 828 250 | fax: | mobile:
e: Cameron.Craig@exterity.com | w: www.exterity.com
______________________________________________________________________
This email has been scanned by the Symantec Email Security.cloud service.
For more information please visit http://www.symanteccloud.com
______________________________________________________________________
^ permalink raw reply [flat|nested] 9+ messages in thread
* Re: Enabling boot menu via serial & PXE boot in CorebootPayloadPkg
2017-11-30 14:11 ` Cameron Craig
@ 2017-12-01 0:31 ` You, Benjamin
2017-12-01 10:23 ` Cameron Craig
0 siblings, 1 reply; 9+ messages in thread
From: You, Benjamin @ 2017-12-01 0:31 UTC (permalink / raw)
To: Cameron Craig, 'edk2-devel@lists.01.org'
Hi, Cameron,
> Interestingly, my debug build was complaining that it ran out of room when
> attempting to fit everything in the UEFIPAYLOAD.
> When I strip out the network additions and keep DEBUG on, Tianocore builds but
> errors at runtime:
> ```
> Failed to add memory space :0xFEE00000 0x100000
> ```
> I'm guessing I can increase the size of a region somewhere to avoid this issue?
There has been a recent fix for this issue by commit e2ef8b9a68. Could you
please have a try?
> I get serial output from coreboot and edk2, just not the boot menu.
I will double check whether there is an issue with enabling serial with release
build.
Thanks,
- ben
^ permalink raw reply [flat|nested] 9+ messages in thread
* Re: Enabling boot menu via serial & PXE boot in CorebootPayloadPkg
2017-12-01 0:31 ` You, Benjamin
@ 2017-12-01 10:23 ` Cameron Craig
2017-12-01 10:26 ` Cameron Craig
0 siblings, 1 reply; 9+ messages in thread
From: Cameron Craig @ 2017-12-01 10:23 UTC (permalink / raw)
To: 'You, Benjamin', 'edk2-devel@lists.01.org'
Hi Benjamin,
>> Interestingly, my debug build was complaining that it ran out of room
>> when attempting to fit everything in the UEFIPAYLOAD.
>> When I strip out the network additions and keep DEBUG on, Tianocore
>> builds but errors at runtime:
>> ```
>> Failed to add memory space :0xFEE00000 0x100000 ``` I'm guessing I can
>> increase the size of a region somewhere to avoid this issue?
>
>There has been a recent fix for this issue by commit e2ef8b9a68. Could you
>please have a try?
Nice! I tried that fix and can now run the debug build.
>> I get serial output from coreboot and edk2, just not the boot menu.
>
>I will double check whether there is an issue with enabling serial with release
>build.
I get serial output from edk2 with the release build and the debug build.
However this serial output does not include the boot menu, I just get progress and error codes (and debug messages in debug mode).
I have attached a runtime log of a recent debug build.
Given that I do get serial output I'm hoping that getting a boot menu via serial is not far away.
Thanks for the help so far!
Cheers,
Cameron
Cameron Craig | Graduate Software Engineer | Exterity Limited
tel: +44 1383 828 250 | fax: | mobile:
e: Cameron.Craig@exterity.com | w: www.exterity.com
______________________________________________________________________
This email has been scanned by the Symantec Email Security.cloud service.
For more information please visit http://www.symanteccloud.com
______________________________________________________________________
^ permalink raw reply [flat|nested] 9+ messages in thread
* Re: Enabling boot menu via serial & PXE boot in CorebootPayloadPkg
2017-12-01 10:23 ` Cameron Craig
@ 2017-12-01 10:26 ` Cameron Craig
2017-12-02 3:02 ` You, Benjamin
0 siblings, 1 reply; 9+ messages in thread
From: Cameron Craig @ 2017-12-01 10:26 UTC (permalink / raw)
To: 'You, Benjamin', 'edk2-devel@lists.01.org'
[-- Attachment #1: Type: text/plain, Size: 1825 bytes --]
Added log as attachment.
>
Cameron Craig | Graduate Software Engineer | Exterity Limited
tel: +44 1383 828 250 | fax: | mobile:
e: Cameron.Craig@exterity.com | w: www.exterity.com
-----Original Message-----
>From: Cameron Craig
>Sent: 01 December 2017 10:23
>To: 'You, Benjamin'; 'edk2-devel@lists.01.org'
>Subject: RE: [edk2] Enabling boot menu via serial & PXE boot in
>CorebootPayloadPkg
>
>Hi Benjamin,
>
>>> Interestingly, my debug build was complaining that it ran out of room
>>> when attempting to fit everything in the UEFIPAYLOAD.
>>> When I strip out the network additions and keep DEBUG on, Tianocore
>>> builds but errors at runtime:
>>> ```
>>> Failed to add memory space :0xFEE00000 0x100000 ``` I'm guessing I
>>> can increase the size of a region somewhere to avoid this issue?
>>
>>There has been a recent fix for this issue by commit e2ef8b9a68. Could
>>you please have a try?
>
>Nice! I tried that fix and can now run the debug build.
>
>>> I get serial output from coreboot and edk2, just not the boot menu.
>>
>>I will double check whether there is an issue with enabling serial with
>>release build.
>
>I get serial output from edk2 with the release build and the debug build.
>However this serial output does not include the boot menu, I just get progress
>and error codes (and debug messages in debug mode).
>I have attached a runtime log of a recent debug build.
>Given that I do get serial output I'm hoping that getting a boot menu via serial
>is not far away.
>
>Thanks for the help so far!
>
>Cheers,
>Cameron
______________________________________________________________________
This email has been scanned by the Symantec Email Security.cloud service.
For more information please visit http://www.symanteccloud.com
______________________________________________________________________
[-- Attachment #2: edk2_no_serial_boot_menu.txt --]
[-- Type: text/plain, Size: 70284 bytes --]
PROGRESS CODE: V03020003 I0
Loading PEIM at 0x000008143C0 EntryPoint=0x00000814600 CbSupportPeim.efi
PROGRESS CODE: V03020002 I0
0. 0000000000000000 - 0000000000000FFF [10]
1. 0000000000001000 - 000000000009FFFF [01]
2. 00000000000A0000 - 00000000000FFFFF [02]
3. 0000000000100000 - 000000000FFFFFFF [01]
4. 0000000010000000 - 0000000012150FFF [02]
5. 0000000012151000 - 000000007AB25FFF [01]
6. 000000007AB26000 - 000000007AFFFFFF [10]
7. 000000007B000000 - 000000007FFFFFFF [02]
8. 00000000D0000000 - 00000000D0FFFFFF [02]
9. 00000000E0000000 - 00000000EFFFFFFF [02]
10. 00000000FED10000 - 00000000FED17FFF [02]
Low memory 0x7AB26000
SystemLowMemTop 0x80000000
PeiMemBase: 0x76B20000.
PeiMemSize: 0x4000000.
PeiInstallPeiMemory MemoryBegin 0x76B20000, MemoryLength 0x4000000
Found one valid fv : 0x3E000000830000.
Install PPI: 49EDB1C1-BF21-4761-BB12-EB0031AABB39
Notify: PPI Guid: 49EDB1C1-BF21-4761-BB12-EB0031AABB39, Peim notify entry point: 807D48
The 1th FV start address is 0x00000830000, size is 0x003E0000, handle is 0x830000
Install PPI: 7408D748-FC8C-4EE6-9288-C4BEC092A410
Actual Coreboot header: 7AB5B000.
Find CbMemTable Id 0x41435049, base 7AB37000, size 0x24000
Find CbMemTable Id 0x534D4254, base 7AB26000, size 0x800
Detected Acpi Table at 0x7AB37000, length 0x24000
Detected Smbios Table at 0x7AB26000, length 0x800
Create system table info guid hob
Find CbMemTable Id 0x41435049, base 7AB37000, size 0x24000
Find Rsdp at 7AB37000
Find Rsdt 0x7AB37030, Xsdt 0x7AB370E0
PmCtrl Reg 0x404
PmTimer Reg 0x408
Reset Reg 0xCF9
Reset Value 0x6
PmEvt Reg 0x400
PmGpeEn Reg 0x430
Create acpi board info guid hob
Found coreboot video frame buffer information
physical_address: 0xB0000000
x_resolution: 0x400
y_resolution: 0x300
bits_per_pixel: 0x20
bytes_per_line: 0x1000
red_mask_size: 0x8
red_mask_pos: 0x10
green_mask_size: 0x8
green_mask_pos: 0x8
blue_mask_size: 0x8
blue_mask_pos: 0x0
reserved_mask_size: 0x18
reserved_mask_pos: 0x18
Create frame buffer info guid hob
PROGRESS CODE: V03020003 I0
Temp Stack : BaseAddress=0x88000 Length=0x8000
Temp Heap : BaseAddress=0x80000 Length=0x8000
Total temporary memory: 65536 bytes.
temporary memory stack ever used: 32768 bytes.
temporary memory heap used: 3880 bytes.
Old Stack size 32768, New stack size 131072
Stack Hob: BaseAddress=0x76B20000 Length=0x20000
Heap Offset = 0x76AC0000 Stack Offset = 0x76AB0000
Loading PEIM at 0x0007AB14000 EntryPoint=0x0007AB1BE10 PeiCore.efi
Reinstall PPI: 8C8CE578-8A3D-4F1C-9935-896185C32DD3
Reinstall PPI: 5473C07A-3DCB-4DCA-BD6F-1E9689E7349A
Reinstall PPI: B9E0ABFE-5979-4914-977F-6DEE78C278A6
Install PPI: F894643D-C449-42D1-8EA8-85BDD8C65BDE
Loading PEIM at 0x0007AB0F000 EntryPoint=0x0007AB10103 DxeIpl.efi
PROGRESS CODE: V03020002 I0
PROGRESS CODE: V03020003 I0
Install PPI: 1A36E4E7-FAB6-476A-8E75-695A0576FDD7
Install PPI: 0AE8CE5D-E448-4437-A8D7-EBF5F194F731
DXE IPL Entry
Loading PEIM at 0x0007AAE7000 EntryPoint=0x0007AAE7240 DxeCore.efi
PROGRESS CODE: V03021001 I0
Loading DXE CORE at 0x0007AAE7000 EntryPoint=0x0007AAE7240
Install PPI: 605EA650-C65C-42E1-BA80-91A52AB618C6
HandOffToDxeCore() Stack Base: 0x7AAC7000, Stack Size: 0x20000
PROGRESS CODE: V03040003 I0
Loading driver F80697E9-7FD6-4665-8646-88E33EF71DFC
InstallProtocolInterface: 5B1B31A1-9562-11D2-8E3F-00A0C969723B 7A7A0840
Loading driver at 0x0007A788000 EntryPoint=0x0007A788D0D SecurityStubDxe.efi
InstallProtocolInterface: BC62157E-3E33-4FEC-9920-2D3B36D750DF 7A7A0198
ProtectUefiImageCommon - 0x7A7A0840
- 0x000000007A788000 - 0x0000000000007800
PROGRESS CODE: V03040002 I0
InstallProtocolInterface: 94AB2F58-1438-4EF1-9152-18941A3A0E68 7A78EF78
InstallProtocolInterface: A46423E3-4617-49F1-B9FF-D1BFA9115839 7A78EF70
InstallProtocolInterface: 15853D7C-3DDF-43E0-A1CB-EBF85B8F872C 7A78EF50
PROGRESS CODE: V03040003 I0
Loading driver 1A1E4886-9517-440E-9FDE-3BE44CEE2136
InstallProtocolInterface: 5B1B31A1-9562-11D2-8E3F-00A0C969723B 7A7A3CC0
Loading driver at 0x0007A76A000 EntryPoint=0x0007A76A240 CpuDxe.efi
InstallProtocolInterface: BC62157E-3E33-4FEC-9920-2D3B36D750DF 7A7A3118
ProtectUefiImageCommon - 0x7A7A3CC0
- 0x000000007A76A000 - 0x000000000000E0C0
PROGRESS CODE: V03040002 I0
CurrentPagingContext:
MachineType - 0x8664
PageTableBase - 0x7AAC5000
Attributes - 0x40000006
InstallProtocolInterface: 26BACCB1-6F42-11D4-BCE7-0080C73C8881 7A777A00
MemoryProtectionCpuArchProtocolNotify:
ProtectUefiImageCommon - 0x7AB0A608
- 0x000000007AAE7000 - 0x0000000000028000
ProtectUefiImageCommon - 0x7A79F040
- 0x000000007A798000 - 0x0000000000006A80
ProtectUefiImageCommon - 0x7A7A6B40
- 0x000000007A9EF000 - 0x0000000000003080
ProtectUefiImageCommon - 0x7A7A63C0
- 0x000000007A9EA000 - 0x0000000000004200
ProtectUefiImageCommon - 0x7A7A0840
- 0x000000007A788000 - 0x0000000000007800
ProtectUefiImageCommon - 0x7A7A3CC0
- 0x000000007A76A000 - 0x000000000000E0C0
Flushing GCD
Flushing GCD
Flushing GCD
Flushing GCD
Flushing GCD
Flushing GCD
Flushing GCD
Flushing GCD
Flushing GCD
Flushing GCD
Flushing GCD
Flushing GCD
AP Loop Mode is 1
APIC MODE is 1
MpInitLib: Find 4 processors in system.
Detect CPU count: 4
Does not find any HOB stored CPU BIST information!
InstallProtocolInterface: 3FDDA605-A76E-4F46-AD29-12F4531B3D08 7A7779A0
PROGRESS CODE: V03040003 I0
Loading driver C8339973-A563-4561-B858-D8476F9DEFC4
InstallProtocolInterface: 5B1B31A1-9562-11D2-8E3F-00A0C969723B 7A787CC0
Loading driver at 0x0007A783000 EntryPoint=0x0007A783E85 Metronome.efi
InstallProtocolInterface: BC62157E-3E33-4FEC-9920-2D3B36D750DF 7A787C18
ProtectUefiImageCommon - 0x7A787CC0
- 0x000000007A783000 - 0x0000000000001D80
PROGRESS CODE: V03040002 I0
InstallProtocolInterface: 26BACCB2-6F42-11D4-BCE7-0080C73C8881 7A784B40
PROGRESS CODE: V03040003 I0
Loading driver B601F8C4-43B7-4784-95B1-F4226CB40CEE
InstallProtocolInterface: 5B1B31A1-9562-11D2-8E3F-00A0C969723B 7A787240
!!!!!!!! InsertImageRecord - Section Alignment(0x40) is not 4K !!!!!!!!
!!!!!!!! Image - /home/ccraig/git/coreboot-leafhill-mario/payloads/external/tianocore/tianocore/Build/CorebootPayloadPkgX64/DEBUG_COREBOOT/X64/MdeModulePkg/Core/RuntimeDxe/RuntimeDxe/DEBUG/RuntimeDxe.dll !!!!!!!!
Loading driver at 0x0007A9E7000 EntryPoint=0x0007A9E7C5C RuntimeDxe.efi
InstallProtocolInterface: BC62157E-3E33-4FEC-9920-2D3B36D750DF 7A787498
ProtectUefiImageCommon - 0x7A787240
- 0x000000007A9E7000 - 0x0000000000002C40
PROGRESS CODE: V03040002 I0
InstallProtocolInterface: B7DFB4E1-052F-449F-87BE-9818FC91B733 7A9E95C0
PROGRESS CODE: V03040003 I0
Loading driver 4B28E4C7-FF36-4E10-93CF-A82159E777C5
InstallProtocolInterface: 5B1B31A1-9562-11D2-8E3F-00A0C969723B 7A786140
!!!!!!!! InsertImageRecord - Section Alignment(0x40) is not 4K !!!!!!!!
!!!!!!!! Image - /home/ccraig/git/coreboot-leafhill-mario/payloads/external/tianocore/tianocore/Build/CorebootPayloadPkgX64/DEBUG_COREBOOT/X64/MdeModulePkg/Universal/ResetSystemRuntimeDxe/ResetSystemRuntimeDxe/DEBUG/ResetSystemRuntimeDxe.dll !!!!!!!!
Loading driver at 0x0007A9E4000 EntryPoint=0x0007A9E4B0C ResetSystemRuntimeDxe.efi
InstallProtocolInterface: BC62157E-3E33-4FEC-9920-2D3B36D750DF 7A786A18
ProtectUefiImageCommon - 0x7A786140
- 0x000000007A9E4000 - 0x00000000000026C0
PROGRESS CODE: V03040002 I0
InstallProtocolInterface: 27CFAC88-46CC-11D4-9A38-0090273FC14D 0
PROGRESS CODE: V03040003 I0
Loading driver 02B01AD5-7E59-43E8-A6D8-238180613A5A
InstallProtocolInterface: 5B1B31A1-9562-11D2-8E3F-00A0C969723B 7A785040
!!!!!!!! InsertImageRecord - Section Alignment(0x40) is not 4K !!!!!!!!
!!!!!!!! Image - /home/ccraig/git/coreboot-leafhill-mario/payloads/external/tianocore/tianocore/Build/CorebootPayloadPkgX64/DEBUG_COREBOOT/X64/MdeModulePkg/Universal/Variable/EmuRuntimeDxe/EmuVariableRuntimeDxe/DEBUG/EmuVariableRuntimeDxe.dll !!!!!!!!
Loading driver at 0x0007A9DF000 EntryPoint=0x0007A9DFAF6 EmuVariableRuntimeDxe.efi
InstallProtocolInterface: BC62157E-3E33-4FEC-9920-2D3B36D750DF 7A786418
ProtectUefiImageCommon - 0x7A785040
- 0x000000007A9DF000 - 0x0000000000004B80
PROGRESS CODE: V03040002 I0
InstallProtocolInterface: 1E5668E2-8481-11D4-BCF1-0080C73C8881 0
InstallProtocolInterface: 6441F818-6362-4E44-B570-7DBA31DD2453 0
PROGRESS CODE: V03040003 I0
Loading driver A19B1FE7-C1BC-49F8-875F-54A5D542443F
InstallProtocolInterface: 5B1B31A1-9562-11D2-8E3F-00A0C969723B 7A7853C0
Loading driver at 0x0007A77E000 EntryPoint=0x0007A77F34C CpuIo2Dxe.efi
InstallProtocolInterface: BC62157E-3E33-4FEC-9920-2D3B36D750DF 7A785E98
ProtectUefiImageCommon - 0x7A7853C0
- 0x000000007A77E000 - 0x0000000000002000
PROGRESS CODE: V03040002 I0
InstallProtocolInterface: AD61F191-AE5F-4C0E-B9FA-E869D288C64F 7A77FE00
PROGRESS CODE: V03040003 I0
Loading driver 9B680FCE-AD6B-4F3A-B60B-F59899003443
InstallProtocolInterface: 5B1B31A1-9562-11D2-8E3F-00A0C969723B 7A782B40
Loading driver at 0x0007A54C000 EntryPoint=0x0007A554565 DevicePathDxe.efi
InstallProtocolInterface: BC62157E-3E33-4FEC-9920-2D3B36D750DF 7A782D98
ProtectUefiImageCommon - 0x7A782B40
- 0x000000007A54C000 - 0x000000000000C640
PROGRESS CODE: V03040002 I0
InstallProtocolInterface: 0379BE4E-D706-437D-B037-EDB82FB772A4 7A557F00
InstallProtocolInterface: 8B843E20-8132-4852-90CC-551A4E4A7F1C 7A557EE0
InstallProtocolInterface: 05C99A21-C70F-4AD2-8A5F-35DF3343F51E 7A557EC0
PROGRESS CODE: V03040003 I0
Loading driver 96B5C032-DF4C-4B6E-8232-438DCF448D0E
InstallProtocolInterface: 5B1B31A1-9562-11D2-8E3F-00A0C969723B 7A7822C0
Loading driver at 0x0007A77C000 EntryPoint=0x0007A77CCBB NullMemoryTestDxe.efi
InstallProtocolInterface: BC62157E-3E33-4FEC-9920-2D3B36D750DF 7A782518
ProtectUefiImageCommon - 0x7A7822C0
- 0x000000007A77C000 - 0x0000000000001BC0
PROGRESS CODE: V03040002 I0
InstallProtocolInterface: 309DE7F1-7F5E-4ACE-B49C-531BE5AA95EF 7A77D980
PROGRESS CODE: V03040003 I0
Loading driver 79CA4208-BBA1-4A9A-8456-E1E66A81484E
InstallProtocolInterface: 5B1B31A1-9562-11D2-8E3F-00A0C969723B 7A77B0C0
Loading driver at 0x0007A779000 EntryPoint=0x0007A77A083 Legacy8259.efi
InstallProtocolInterface: BC62157E-3E33-4FEC-9920-2D3B36D750DF 7A77BE18
ProtectUefiImageCommon - 0x7A77B0C0
- 0x000000007A779000 - 0x0000000000001B40
PROGRESS CODE: V03040002 I0
InstallProtocolInterface: 38321DBA-4FE0-4E17-8AEC-413055EAEDC1 7A77A920
PROGRESS CODE: V03040003 I0
Loading driver 348C4D62-BFBD-4882-9ECE-C80BB1C4783B
InstallProtocolInterface: 5B1B31A1-9562-11D2-8E3F-00A0C969723B 7A77B540
Loading driver at 0x0007A50C000 EntryPoint=0x0007A50F0BD HiiDatabase.efi
InstallProtocolInterface: BC62157E-3E33-4FEC-9920-2D3B36D750DF 7A781018
ProtectUefiImageCommon - 0x7A77B540
- 0x000000007A50C000 - 0x000000000001F680
PROGRESS CODE: V03040002 I0
InstallProtocolInterface: E9CA4775-8657-47FC-97E7-7ED65A084324 7A52B248
InstallProtocolInterface: 0FD96974-23AA-4CDC-B9CB-98D17750322A 7A52B2C0
InstallProtocolInterface: EF9FC172-A1B2-4693-B327-6D32FC416042 7A52B2E8
InstallProtocolInterface: 587E72D7-CC50-4F79-8209-CA291FC1A10F 7A52B340
InstallProtocolInterface: 0A8BADD5-03B8-4D19-B128-7B8F0EDAA596 7A52B370
InstallProtocolInterface: 31A6406A-6BDF-4E46-B2A2-EBAA89C40920 7A52B268
InstallProtocolInterface: 1A1241E6-8F19-41A9-BC0E-E8EF39E06546 7A52B290
PROGRESS CODE: V03040003 I0
Loading driver C68DAA4E-7AB5-41E8-A91D-5954421053F3
InstallProtocolInterface: 5B1B31A1-9562-11D2-8E3F-00A0C969723B 7A781340
Loading driver at 0x0007A560000 EntryPoint=0x0007A560A60 CbSupportDxe.efi
InstallProtocolInterface: BC62157E-3E33-4FEC-9920-2D3B36D750DF 7A780F18
ProtectUefiImageCommon - 0x7A781340
- 0x000000007A560000 - 0x0000000000002640
PROGRESS CODE: V03040002 I0
Install Acpi Table at 0x7AB37000, length 0x24000
Install Smbios Table at 0x7AB26000, length 0x800
PmCtrlReg at 0x404
PROGRESS CODE: V03040003 I0
Loading driver F9D88642-0737-49BC-81B5-6889CD57D9EA
InstallProtocolInterface: 5B1B31A1-9562-11D2-8E3F-00A0C969723B 7A780140
Loading driver at 0x0007A548000 EntryPoint=0x0007A5494AE SmbiosDxe.efi
InstallProtocolInterface: BC62157E-3E33-4FEC-9920-2D3B36D750DF 7A780C98
ProtectUefiImageCommon - 0x7A780140
- 0x000000007A548000 - 0x0000000000003A80
PROGRESS CODE: V03040002 I0
InstallProtocolInterface: 03583FF6-CB36-4940-947E-B9B39F4AFAF7 7A54B8F0
PROGRESS CODE: V03040003 I0
Loading driver D3987D4B-971A-435F-8CAF-4967EB627241
InstallProtocolInterface: 5B1B31A1-9562-11D2-8E3F-00A0C969723B 7A55F040
Loading driver at 0x0007A55C000 EntryPoint=0x0007A55CF8C SerialDxe.efi
InstallProtocolInterface: BC62157E-3E33-4FEC-9920-2D3B36D750DF 7A780518
ProtectUefiImageCommon - 0x7A55F040
- 0x000000007A55C000 - 0x0000000000002AC0
PROGRESS CODE: V03040002 I0
InstallProtocolInterface: BB25CF6F-F1D4-11D2-9A0C-0090273FC1FD 7A55E7C0
InstallProtocolInterface: 09576E91-6D3F-11D2-8E39-00A0C969723B 7A55E860
PROGRESS CODE: V03040003 I0
Loading driver FC5C7020-1A48-4198-9BE2-EAD5ABC8CF2F
InstallProtocolInterface: 5B1B31A1-9562-11D2-8E3F-00A0C969723B 7A55F440
Loading driver at 0x0007A4AC000 EntryPoint=0x0007A4CBB06 BdsDxe.efi
InstallProtocolInterface: BC62157E-3E33-4FEC-9920-2D3B36D750DF 7A55F698
ProtectUefiImageCommon - 0x7A55F440
- 0x000000007A4AC000 - 0x000000000002F840
PROGRESS CODE: V03040002 I0
InstallProtocolInterface: 665E3FF6-46CC-11D4-9A38-0090273FC14D 7A4DA1A0
PROGRESS CODE: V03040003 I0
Loading driver F2765DEC-6B41-11D5-8E71-00902707B35E
InstallProtocolInterface: 5B1B31A1-9562-11D2-8E3F-00A0C969723B 7A565040
Loading driver at 0x0007A55A000 EntryPoint=0x0007A55ACE9 Timer.efi
InstallProtocolInterface: BC62157E-3E33-4FEC-9920-2D3B36D750DF 7A55F918
ProtectUefiImageCommon - 0x7A565040
- 0x000000007A55A000 - 0x0000000000001A40
PROGRESS CODE: V03040002 I0
InstallProtocolInterface: 26BACCB3-6F42-11D4-BCE7-0080C73C8881 7A55B800
PROGRESS CODE: V03040003 I0
Loading driver 42857F0A-13F2-4B21-8A23-53D3F714B840
InstallProtocolInterface: 5B1B31A1-9562-11D2-8E3F-00A0C969723B 7A564B40
!!!!!!!! InsertImageRecord - Section Alignment(0x40) is not 4K !!!!!!!!
!!!!!!!! Image - /home/ccraig/git/coreboot-leafhill-mario/payloads/external/tianocore/tianocore/Build/CorebootPayloadPkgX64/DEBUG_COREBOOT/X64/MdeModulePkg/Universal/CapsuleRuntimeDxe/CapsuleRuntimeDxe/DEBUG/CapsuleRuntimeDxe.dll !!!!!!!!
Loading driver at 0x0007A9DC000 EntryPoint=0x0007A9DCA1A CapsuleRuntimeDxe.efi
InstallProtocolInterface: BC62157E-3E33-4FEC-9920-2D3B36D750DF 7A564E98
ProtectUefiImageCommon - 0x7A564B40
- 0x000000007A9DC000 - 0x0000000000002100
PROGRESS CODE: V03040002 I0
InstallProtocolInterface: 5053697E-2CBC-4819-90D9-0580DEEE5754 0
PROGRESS CODE: V03040003 I0
Loading driver AD608272-D07F-4964-801E-7BD3B7888652
InstallProtocolInterface: 5B1B31A1-9562-11D2-8E3F-00A0C969723B 7A5642C0
!!!!!!!! InsertImageRecord - Section Alignment(0x40) is not 4K !!!!!!!!
!!!!!!!! Image - /home/ccraig/git/coreboot-leafhill-mario/payloads/external/tianocore/tianocore/Build/CorebootPayloadPkgX64/DEBUG_COREBOOT/X64/MdeModulePkg/Universal/MonotonicCounterRuntimeDxe/MonotonicCounterRuntimeDxe/DEBUG/MonotonicCounterRuntimeDxe.dLoading driver at 0x0007A9DA000 EntryPoint=0x0007A9DADA2 MonotonicCounterRuntimeDxe.efi
InstallProtocolInterface: BC62157E-3E33-4FEC-9920-2D3B36D750DF 7A564618
ProtectUefiImageCommon - 0x7A5642C0
- 0x000000007A9DA000 - 0x0000000000001F00
PROGRESS CODE: V03040002 I0
InstallProtocolInterface: 1DA97072-BDDC-4B30-99F1-72A0B56FFF2A 0
PROGRESS CODE: V03040003 I0
Loading driver 378D7B65-8DA9-4773-B6E4-A47826A833E1
InstallProtocolInterface: 5B1B31A1-9562-11D2-8E3F-00A0C969723B 7A5631C0
!!!!!!!! InsertImageRecord - Section Alignment(0x40) is not 4K !!!!!!!!
!!!!!!!! Image - /home/ccraig/git/coreboot-leafhill-mario/payloads/external/tianocore/tianocore/Build/CorebootPayloadPkgX64/DEBUG_COREBOOT/X64/PcAtChipsetPkg/PcatRealTimeClockRuntimeDxe/PcatRealTimeClockRuntimeDxe/DEBUG/PcRtc.dll !!!!!!!!
Loading driver at 0x0007A9D6000 EntryPoint=0x0007A9D6A8E PcRtc.efi
InstallProtocolInterface: BC62157E-3E33-4FEC-9920-2D3B36D750DF 7A563918
ProtectUefiImageCommon - 0x7A5631C0
- 0x000000007A9D6000 - 0x0000000000003F00
PROGRESS CODE: V03040002 I0
InstallProtocolInterface: 27CFAC87-46CC-11D4-9A38-0090273FC14D 0
PROGRESS CODE: V03040003 I0
Loading driver EBF342FE-B1D3-4EF8-957C-8048606FF671
InstallProtocolInterface: 5B1B31A1-9562-11D2-8E3F-00A0C969723B 7A559140
Loading driver at 0x0007A4F0000 EntryPoint=0x0007A500E33 SetupBrowser.efi
InstallProtocolInterface: BC62157E-3E33-4FEC-9920-2D3B36D750DF 7A559A18
ProtectUefiImageCommon - 0x7A559140
- 0x000000007A4F0000 - 0x000000000001B540
PROGRESS CODE: V03040002 I0
InstallProtocolInterface: B9D4C360-BCFB-4F9B-9298-53C136982258 7A50AD70
InstallProtocolInterface: A770C357-B693-4E6D-A6CF-D21C728E550B 7A50ADA0
InstallProtocolInterface: 1F73B18D-4630-43C1-A1DE-6F80855D7DA4 7A50AD80
PROGRESS CODE: V03040003 I0
Loading driver 0F7EC77A-1EE1-400F-A99D-7CBD1FEB181E
InstallProtocolInterface: 5B1B31A1-9562-11D2-8E3F-00A0C969723B 7A547CC0
Loading driver at 0x0007A53B000 EntryPoint=0x0007A53B240 PcatPciRootBridge.efi
InstallProtocolInterface: BC62157E-3E33-4FEC-9920-2D3B36D750DF 7A547C18
ProtectUefiImageCommon - 0x7A547CC0
- 0x000000007A53B000 - 0x0000000000005A80
PROGRESS CODE: V03040002 I0
InstallProtocolInterface: 09576E91-6D3F-11D2-8E39-00A0C969723B 7A547A18
InstallProtocolInterface: 2F707EBB-4A1A-11D4-9A38-0090273FC14D 7A547230
InstallProtocolInterface: AF6AC311-84C3-11D2-8E3C-00A0C969723B 7A547728
PROGRESS CODE: V03040003 I0
Loading driver F099D67F-71AE-4C36-B2A3-DCEB0EB2B7D8
InstallProtocolInterface: 5B1B31A1-9562-11D2-8E3F-00A0C969723B 7A4A2D40
Loading driver at 0x0007A49E000 EntryPoint=0x0007A49ED8A WatchdogTimer.efi
InstallProtocolInterface: BC62157E-3E33-4FEC-9920-2D3B36D750DF 7A4A3B98
ProtectUefiImageCommon - 0x7A4A2D40
- 0x000000007A49E000 - 0x0000000000001A40
PROGRESS CODE: V03040002 I0
InstallProtocolInterface: 665E3FF5-46CC-11D4-9A38-0090273FC14D 7A49F800
PROGRESS CODE: V03040003 I0
Loading driver E660EA85-058E-4B55-A54B-F02F83A24707
InstallProtocolInterface: 5B1B31A1-9562-11D2-8E3F-00A0C969723B 7A4A22C0
Loading driver at 0x0007A476000 EntryPoint=0x0007A47A6DB DisplayEngine.efi
InstallProtocolInterface: BC62157E-3E33-4FEC-9920-2D3B36D750DF 7A4A6C18
ProtectUefiImageCommon - 0x7A4A22C0
- 0x000000007A476000 - 0x0000000000013B40
PROGRESS CODE: V03040002 I0
InstallProtocolInterface: 9BBE29E9-FDA1-41EC-AD52-452213742D2E 7A4877B0
PROGRESS CODE: V03040003 I0
Loading driver 35C0C168-2607-4E51-BB53-448E3ED1A87F
InstallProtocolInterface: 5B1B31A1-9562-11D2-8E3F-00A0C969723B 7A4A0AC0
Loading driver at 0x0007A48B000 EntryPoint=0x0007A48D422 PciBusNoEnumerationDxe.efi
InstallProtocolInterface: BC62157E-3E33-4FEC-9920-2D3B36D750DF 7A4DCC98
ProtectUefiImageCommon - 0x7A4A0AC0
- 0x000000007A48B000 - 0x0000000000007D00
PROGRESS CODE: V03040002 I0
InstallProtocolInterface: 18A031AB-B443-4D1A-A5C0-0C09261E9F71 7A492960
InstallProtocolInterface: 107A772C-D5E1-11D4-9A46-0090273FC14D 7A492AA0
InstallProtocolInterface: 6A7A5CFF-E8D9-4F70-BADA-75AB3025CE14 7A492900
PROGRESS CODE: V03040003 I0
Loading driver 38A0EC22-FBE7-4911-8BC1-176E0D6C1DBD
InstallProtocolInterface: 5B1B31A1-9562-11D2-8E3F-00A0C969723B 7A49D0C0
Loading driver at 0x0007A495000 EntryPoint=0x0007A496410 IsaAcpi.efi
InstallProtocolInterface: BC62157E-3E33-4FEC-9920-2D3B36D750DF 7A49D998
ProtectUefiImageCommon - 0x7A49D0C0
- 0x000000007A495000 - 0x0000000000002340
PROGRESS CODE: V03040002 I0
InstallProtocolInterface: 18A031AB-B443-4D1A-A5C0-0C09261E9F71 7A497000
InstallProtocolInterface: 107A772C-D5E1-11D4-9A46-0090273FC14D 7A4970E0
InstallProtocolInterface: 6A7A5CFF-E8D9-4F70-BADA-75AB3025CE14 7A496FE0
PROGRESS CODE: V03040003 I0
Loading driver 240612B5-A063-11D4-9A3A-0090273FC14D
InstallProtocolInterface: 5B1B31A1-9562-11D2-8E3F-00A0C969723B 7A49C040
Loading driver at 0x0007A46E000 EntryPoint=0x0007A46FB0F IsaBusDxe.efi
InstallProtocolInterface: BC62157E-3E33-4FEC-9920-2D3B36D750DF 7A49D898
ProtectUefiImageCommon - 0x7A49C040
- 0x000000007A46E000 - 0x0000000000003E80
PROGRESS CODE: V03040002 I0
InstallProtocolInterface: 18A031AB-B443-4D1A-A5C0-0C09261E9F71 7A471BE0
InstallProtocolInterface: 107A772C-D5E1-11D4-9A46-0090273FC14D 7A471B60
InstallProtocolInterface: 6A7A5CFF-E8D9-4F70-BADA-75AB3025CE14 7A471BB0
PROGRESS CODE: V03040003 I0
Loading driver 3DC82376-637B-40A6-A8FC-A565417F2C38
InstallProtocolInterface: 5B1B31A1-9562-11D2-8E3F-00A0C969723B 7A49CA40
Loading driver at 0x0007A462000 EntryPoint=0x0007A462E53 Ps2KeyboardDxe.efi
InstallProtocolInterface: BC62157E-3E33-4FEC-9920-2D3B36D750DF 7A49C398
ProtectUefiImageCommon - 0x7A49CA40
- 0x000000007A462000 - 0x0000000000005E00
PROGRESS CODE: V03040002 I0
InstallProtocolInterface: 18A031AB-B443-4D1A-A5C0-0C09261E9F71 7A467BA0
InstallProtocolInterface: 107A772C-D5E1-11D4-9A46-0090273FC14D 7A467B60
InstallProtocolInterface: 6A7A5CFF-E8D9-4F70-BADA-75AB3025CE14 7A467AF0
PROGRESS CODE: V03040003 I0
Loading driver 51CCF399-4FDF-4E55-A45B-E123F84D456A
InstallProtocolInterface: 5B1B31A1-9562-11D2-8E3F-00A0C969723B 7A49A040
Loading driver at 0x0007A45D000 EntryPoint=0x0007A45DB9F ConPlatformDxe.efi
InstallProtocolInterface: BC62157E-3E33-4FEC-9920-2D3B36D750DF 7A49C418
ProtectUefiImageCommon - 0x7A49A040
- 0x000000007A45D000 - 0x00000000000042C0
PROGRESS CODE: V03040002 I0
InstallProtocolInterface: 18A031AB-B443-4D1A-A5C0-0C09261E9F71 7A460EC0
InstallProtocolInterface: 107A772C-D5E1-11D4-9A46-0090273FC14D 7A461060
InstallProtocolInterface: 6A7A5CFF-E8D9-4F70-BADA-75AB3025CE14 7A461040
InstallProtocolInterface: 18A031AB-B443-4D1A-A5C0-0C09261E9F71 7A460E80
InstallProtocolInterface: 107A772C-D5E1-11D4-9A46-0090273FC14D 7A461060
InstallProtocolInterface: 6A7A5CFF-E8D9-4F70-BADA-75AB3025CE14 7A461040
PROGRESS CODE: V03040003 I0
Loading driver 408EDCEC-CF6D-477C-A5A8-B4844E3DE281
InstallProtocolInterface: 5B1B31A1-9562-11D2-8E3F-00A0C969723B 7A49A440
Loading driver at 0x0007A44B000 EntryPoint=0x0007A44C0B2 ConSplitterDxe.efi
InstallProtocolInterface: BC62157E-3E33-4FEC-9920-2D3B36D750DF 7A49A818
ProtectUefiImageCommon - 0x7A49A440
- 0x000000007A44B000 - 0x0000000000008080
PROGRESS CODE: V03040002 I0
InstallProtocolInterface: 18A031AB-B443-4D1A-A5C0-0C09261E9F71 7A452720
InstallProtocolInterface: 107A772C-D5E1-11D4-9A46-0090273FC14D 7A4526E0
InstallProtocolInterface: 6A7A5CFF-E8D9-4F70-BADA-75AB3025CE14 7A452650
InstallProtocolInterface: 18A031AB-B443-4D1A-A5C0-0C09261E9F71 7A4527C0
InstallProtocolInterface: 107A772C-D5E1-11D4-9A46-0090273FC14D 7A452780
InstallProtocolInterface: 6A7A5CFF-E8D9-4F70-BADA-75AB3025CE14 7A452630
InstallProtocolInterface: 18A031AB-B443-4D1A-A5C0-0C09261E9F71 7A452860
InstallProtocolInterface: 107A772C-D5E1-11D4-9A46-0090273FC14D 7A452820
InstallProtocolInterface: 6A7A5CFF-E8D9-4F70-BADA-75AB3025CE14 7A452610
InstallProtocolInterface: 18A031AB-B443-4D1A-A5C0-0C09261E9F71 7A452900
InstallProtocolInterface: 107A772C-D5E1-11D4-9A46-0090273FC14D 7A4528C0
InstallProtocolInterface: 6A7A5CFF-E8D9-4F70-BADA-75AB3025CE14 7A4525F0
InstallProtocolInterface: 18A031AB-B443-4D1A-A5C0-0C09261E9F71 7A4529A0
InstallProtocolInterface: 107A772C-D5E1-11D4-9A46-0090273FC14D 7A452960
InstallProtocolInterface: 6A7A5CFF-E8D9-4F70-BADA-75AB3025CE14 7A4525D0
InstallProtocolInterface: 387477C1-69C7-11D2-8E39-00A0C969723B 7A452A30
InstallProtocolInterface: DD9E7534-7762-4698-8C14-F58517A625AA 7A452A60
InstallProtocolInterface: 31878C87-0B75-11D5-9A4F-0090273FC14D 7A452AC0
InstallProtocolInterface: 8D59D32B-C655-4AE9-9B15-F25904992A43 7A452B18
InstallProtocolInterface: 387477C2-69C7-11D2-8E39-00A0C969723B 7A452D10
InstallProtocolInterface: 387477C2-69C7-11D2-8E39-00A0C969723B 7A452BD0
PROGRESS CODE: V03040003 I0
Loading driver CCCB0C28-4B24-11D5-9A5A-0090273FC14D
InstallProtocolInterface: 5B1B31A1-9562-11D2-8E3F-00A0C969723B 7A493B40
Loading driver at 0x0007A457000 EntryPoint=0x0007A4579F8 GraphicsConsoleDxe.efi
InstallProtocolInterface: BC62157E-3E33-4FEC-9920-2D3B36D750DF 7A493D98
ProtectUefiImageCommon - 0x7A493B40
- 0x000000007A457000 - 0x0000000000005E00
PROGRESS CODE: V03040002 I0
InstallProtocolInterface: 18A031AB-B443-4D1A-A5C0-0C09261E9F71 7A45B460
InstallProtocolInterface: 107A772C-D5E1-11D4-9A46-0090273FC14D 7A45CB60
InstallProtocolInterface: 6A7A5CFF-E8D9-4F70-BADA-75AB3025CE14 7A45B430
PROGRESS CODE: V03040003 I0
Loading driver 9E863906-A40F-4875-977F-5B93FF237FC6
InstallProtocolInterface: 5B1B31A1-9562-11D2-8E3F-00A0C969723B 7A493440
Loading driver at 0x0007A439000 EntryPoint=0x0007A43A7AF TerminalDxe.efi
InstallProtocolInterface: BC62157E-3E33-4FEC-9920-2D3B36D750DF 7A48AF98
ProtectUefiImageCommon - 0x7A493440
- 0x000000007A439000 - 0x0000000000008100
PROGRESS CODE: V03040002 I0
InstallProtocolInterface: 18A031AB-B443-4D1A-A5C0-0C09261E9F71 7A440D40
InstallProtocolInterface: 107A772C-D5E1-11D4-9A46-0090273FC14D 7A440D00
InstallProtocolInterface: 6A7A5CFF-E8D9-4F70-BADA-75AB3025CE14 7A4409F0
PROGRESS CODE: V03040003 I0
Loading driver 6B38F7B4-AD98-40E9-9093-ACA2B5A253C4
InstallProtocolInterface: 5B1B31A1-9562-11D2-8E3F-00A0C969723B 7A48A140
Loading driver at 0x0007A434000 EntryPoint=0x0007A4352F2 DiskIoDxe.efi
InstallProtocolInterface: BC62157E-3E33-4FEC-9920-2D3B36D750DF 7A48A398
ProtectUefiImageCommon - 0x7A48A140
- 0x000000007A434000 - 0x0000000000004B00
PROGRESS CODE: V03040002 I0
InstallProtocolInterface: 18A031AB-B443-4D1A-A5C0-0C09261E9F71 7A4387E0
InstallProtocolInterface: 107A772C-D5E1-11D4-9A46-0090273FC14D 7A438920
InstallProtocolInterface: 6A7A5CFF-E8D9-4F70-BADA-75AB3025CE14 7A4387B0
PROGRESS CODE: V03040003 I0
Loading driver 1FA1F39E-FEFF-4AAE-BD7B-38A070A3B609
InstallProtocolInterface: 5B1B31A1-9562-11D2-8E3F-00A0C969723B 7A475040
Loading driver at 0x0007A42D000 EntryPoint=0x0007A430053 PartitionDxe.efi
InstallProtocolInterface: BC62157E-3E33-4FEC-9920-2D3B36D750DF 7A48A698
ProtectUefiImageCommon - 0x7A475040
- 0x000000007A42D000 - 0x0000000000006140
PROGRESS CODE: V03040002 I0
InstallProtocolInterface: 18A031AB-B443-4D1A-A5C0-0C09261E9F71 7A432EE0
InstallProtocolInterface: 107A772C-D5E1-11D4-9A46-0090273FC14D 7A432E60
InstallProtocolInterface: 6A7A5CFF-E8D9-4F70-BADA-75AB3025CE14 7A432EC0
PROGRESS CODE: V03040003 I0
Loading driver CD3BAFB6-50FB-4FE8-8E4E-AB74D2C1A600
InstallProtocolInterface: 5B1B31A1-9562-11D2-8E3F-00A0C969723B 7A475A40
Loading driver at 0x0007A46A000 EntryPoint=0x0007A46AE09 EnglishDxe.efi
InstallProtocolInterface: BC62157E-3E33-4FEC-9920-2D3B36D750DF 7A475D98
ProtectUefiImageCommon - 0x7A475A40
- 0x000000007A46A000 - 0x0000000000001D40
PROGRESS CODE: V03040002 I0
InstallProtocolInterface: 1D85CD7F-F43D-11D2-9A0C-0090273FC14D 7A46B7E0
InstallProtocolInterface: A4C751FC-23AE-4C3E-92E9-4964CF63F349 7A46B780
PROGRESS CODE: V03040003 I0
Loading driver 8F4CD826-A5A0-4E93-9522-CFB0AB72926C
InstallProtocolInterface: 5B1B31A1-9562-11D2-8E3F-00A0C969723B 7A469040
Loading driver at 0x0007A454000 EntryPoint=0x0007A4554E6 SataController.efi
InstallProtocolInterface: BC62157E-3E33-4FEC-9920-2D3B36D750DF 7A469F18
ProtectUefiImageCommon - 0x7A469040
- 0x000000007A454000 - 0x0000000000002D80
PROGRESS CODE: V03040002 I0
InstallProtocolInterface: 18A031AB-B443-4D1A-A5C0-0C09261E9F71 7A456B60
InstallProtocolInterface: 107A772C-D5E1-11D4-9A46-0090273FC14D 7A456B20
InstallProtocolInterface: 6A7A5CFF-E8D9-4F70-BADA-75AB3025CE14 7A456AB0
PROGRESS CODE: V03040003 I0
Loading driver 19DF145A-B1D4-453F-8507-38816676D7F6
InstallProtocolInterface: 5B1B31A1-9562-11D2-8E3F-00A0C969723B 7A469440
Loading driver at 0x0007A426000 EntryPoint=0x0007A426EDD AtaBusDxe.efi
InstallProtocolInterface: BC62157E-3E33-4FEC-9920-2D3B36D750DF 7A469318
ProtectUefiImageCommon - 0x7A469440
- 0x000000007A426000 - 0x0000000000006D00
PROGRESS CODE: V03040002 I0
InstallProtocolInterface: 18A031AB-B443-4D1A-A5C0-0C09261E9F71 7A42CA80
InstallProtocolInterface: 107A772C-D5E1-11D4-9A46-0090273FC14D 7A42CA40
InstallProtocolInterface: 6A7A5CFF-E8D9-4F70-BADA-75AB3025CE14 7A42C800
PROGRESS CODE: V03040003 I0
Loading driver 5E523CB4-D397-4986-87BD-A6DD8B22F455
InstallProtocolInterface: 5B1B31A1-9562-11D2-8E3F-00A0C969723B 7A474040
Loading driver at 0x0007A410000 EntryPoint=0x0007A412AE3 AtaAtapiPassThruDxe.efi
InstallProtocolInterface: BC62157E-3E33-4FEC-9920-2D3B36D750DF 7A474E18
ProtectUefiImageCommon - 0x7A474040
- 0x000000007A410000 - 0x000000000000A440
PROGRESS CODE: V03040002 I0
InstallProtocolInterface: 18A031AB-B443-4D1A-A5C0-0C09261E9F71 7A41A200
InstallProtocolInterface: 107A772C-D5E1-11D4-9A46-0090273FC14D 7A41A1C0
InstallProtocolInterface: 6A7A5CFF-E8D9-4F70-BADA-75AB3025CE14 7A419EF0
PROGRESS CODE: V03040003 I0
Loading driver 0167CCC4-D0F7-4F21-A3EF-9E64B7CDCE8B
InstallProtocolInterface: 5B1B31A1-9562-11D2-8E3F-00A0C969723B 7A474440
Loading driver at 0x0007A443000 EntryPoint=0x0007A44403C ScsiBus.efi
InstallProtocolInterface: BC62157E-3E33-4FEC-9920-2D3B36D750DF 7A474318
ProtectUefiImageCommon - 0x7A474440
- 0x000000007A443000 - 0x0000000000003B00
PROGRESS CODE: V03040002 I0
InstallProtocolInterface: 18A031AB-B443-4D1A-A5C0-0C09261E9F71 7A4468A0
InstallProtocolInterface: 107A772C-D5E1-11D4-9A46-0090273FC14D 7A446940
InstallProtocolInterface: 6A7A5CFF-E8D9-4F70-BADA-75AB3025CE14 7A446870
PROGRESS CODE: V03040003 I0
Loading driver 0A66E322-3740-4CCE-AD62-BD172CECCA35
InstallProtocolInterface: 5B1B31A1-9562-11D2-8E3F-00A0C969723B 7A473B40
Loading driver at 0x0007A406000 EntryPoint=0x0007A407191 ScsiDisk.efi
InstallProtocolInterface: BC62157E-3E33-4FEC-9920-2D3B36D750DF 7A474918
ProtectUefiImageCommon - 0x7A473B40
- 0x000000007A406000 - 0x0000000000009AC0
PROGRESS CODE: V03040002 I0
InstallProtocolInterface: 18A031AB-B443-4D1A-A5C0-0C09261E9F71 7A40F8A0
InstallProtocolInterface: 107A772C-D5E1-11D4-9A46-0090273FC14D 7A40F860
InstallProtocolInterface: 6A7A5CFF-E8D9-4F70-BADA-75AB3025CE14 7A40F7B0
PROGRESS CODE: V03040003 I0
Loading driver 961578FE-B6B7-44C3-AF35-6BC705CD2B1F
InstallProtocolInterface: 5B1B31A1-9562-11D2-8E3F-00A0C969723B 7A4732C0
Loading driver at 0x0007A3FB000 EntryPoint=0x0007A3FC150 Fat.efi
InstallProtocolInterface: BC62157E-3E33-4FEC-9920-2D3B36D750DF 7A473618
ProtectUefiImageCommon - 0x7A4732C0
- 0x000000007A3FB000 - 0x000000000000ACC0
PROGRESS CODE: V03040002 I0
InstallProtocolInterface: 18A031AB-B443-4D1A-A5C0-0C09261E9F71 7A4059C0
InstallProtocolInterface: 107A772C-D5E1-11D4-9A46-0090273FC14D 7A4059A0
InstallProtocolInterface: 6A7A5CFF-E8D9-4F70-BADA-75AB3025CE14 7A4058B0
PROGRESS CODE: V03040003 I0
Loading driver 8E325979-3FE1-4927-AAE2-8F5C4BD2AF0D
InstallProtocolInterface: 5B1B31A1-9562-11D2-8E3F-00A0C969723B 7A472D40
Loading driver at 0x0007A3F1000 EntryPoint=0x0007A3F7451 SdMmcPciHcDxe.efi
InstallProtocolInterface: BC62157E-3E33-4FEC-9920-2D3B36D750DF 7A472098
ProtectUefiImageCommon - 0x7A472D40
- 0x000000007A3F1000 - 0x0000000000009540
PROGRESS CODE: V03040002 I0
InstallProtocolInterface: 18A031AB-B443-4D1A-A5C0-0C09261E9F71 7A3FA2A0
InstallProtocolInterface: 107A772C-D5E1-11D4-9A46-0090273FC14D 7A3FA260
InstallProtocolInterface: 6A7A5CFF-E8D9-4F70-BADA-75AB3025CE14 7A3FA380
PROGRESS CODE: V03040003 I0
Loading driver 2145F72F-E6F1-4440-A828-59DC9AAB5F89
InstallProtocolInterface: 5B1B31A1-9562-11D2-8E3F-00A0C969723B 7A4723C0
Loading driver at 0x0007A3E8000 EntryPoint=0x0007A3EDBD2 EmmcDxe.efi
InstallProtocolInterface: BC62157E-3E33-4FEC-9920-2D3B36D750DF 7A472A18
ProtectUefiImageCommon - 0x7A4723C0
- 0x000000007A3E8000 - 0x0000000000008680
PROGRESS CODE: V03040002 I0
InstallProtocolInterface: 18A031AB-B443-4D1A-A5C0-0C09261E9F71 7A3F0400
InstallProtocolInterface: 107A772C-D5E1-11D4-9A46-0090273FC14D 7A3F03C0
InstallProtocolInterface: 6A7A5CFF-E8D9-4F70-BADA-75AB3025CE14 7A3F0510
PROGRESS CODE: V03040003 I0
Loading driver 430AC2F7-EEC6-4093-94F7-9F825A7C1C40
InstallProtocolInterface: 5B1B31A1-9562-11D2-8E3F-00A0C969723B 7A4681C0
Loading driver at 0x0007A3E2000 EntryPoint=0x0007A3E31B4 SdDxe.efi
InstallProtocolInterface: BC62157E-3E33-4FEC-9920-2D3B36D750DF 7A468B98
ProtectUefiImageCommon - 0x7A4681C0
- 0x000000007A3E2000 - 0x0000000000005F80
PROGRESS CODE: V03040002 I0
InstallProtocolInterface: 18A031AB-B443-4D1A-A5C0-0C09261E9F71 7A3E7DE0
InstallProtocolInterface: 107A772C-D5E1-11D4-9A46-0090273FC14D 7A3E7DA0
InstallProtocolInterface: 6A7A5CFF-E8D9-4F70-BADA-75AB3025CE14 7A3E7B70
PROGRESS CODE: V03040003 I0
Loading driver 2FB92EFA-2EE0-4BAE-9EB6-7464125E1EF7
InstallProtocolInterface: 5B1B31A1-9562-11D2-8E3F-00A0C969723B 7A4685C0
Loading driver at 0x0007A3DA000 EntryPoint=0x0007A3DEDBC UhciDxe.efi
InstallProtocolInterface: BC62157E-3E33-4FEC-9920-2D3B36D750DF 7A468498
ProtectUefiImageCommon - 0x7A4685C0
- 0x000000007A3DA000 - 0x0000000000007940
PROGRESS CODE: V03040002 I0
InstallProtocolInterface: 18A031AB-B443-4D1A-A5C0-0C09261E9F71 7A3E1720
InstallProtocolInterface: 107A772C-D5E1-11D4-9A46-0090273FC14D 7A3E16E0
InstallProtocolInterface: 6A7A5CFF-E8D9-4F70-BADA-75AB3025CE14 7A3E1680
PROGRESS CODE: V03040003 I0
Loading driver BDFE430E-8F2A-4DB0-9991-6F856594777E
InstallProtocolInterface: 5B1B31A1-9562-11D2-8E3F-00A0C969723B 7A44A140
Loading driver at 0x0007A3D0000 EntryPoint=0x0007A3D1920 EhciDxe.efi
InstallProtocolInterface: BC62157E-3E33-4FEC-9920-2D3B36D750DF 7A44AB98
ProtectUefiImageCommon - 0x7A44A140
- 0x000000007A3D0000 - 0x0000000000009440
PROGRESS CODE: V03040002 I0
InstallProtocolInterface: 18A031AB-B443-4D1A-A5C0-0C09261E9F71 7A3D91E0
InstallProtocolInterface: 107A772C-D5E1-11D4-9A46-0090273FC14D 7A3D91A0
InstallProtocolInterface: 6A7A5CFF-E8D9-4F70-BADA-75AB3025CE14 7A3D9230
PROGRESS CODE: V03040003 I0
Loading driver B7F50E91-A759-412C-ADE4-DCD03E7F7C28
InstallProtocolInterface: 5B1B31A1-9562-11D2-8E3F-00A0C969723B 7A44A640
Loading driver at 0x0007A3B4000 EntryPoint=0x0007A3B66C6 XhciDxe.efi
InstallProtocolInterface: BC62157E-3E33-4FEC-9920-2D3B36D750DF 7A449F98
ProtectUefiImageCommon - 0x7A44A640
- 0x000000007A3B4000 - 0x000000000000DA80
PROGRESS CODE: V03040002 I0
InstallProtocolInterface: 18A031AB-B443-4D1A-A5C0-0C09261E9F71 7A3C17A0
InstallProtocolInterface: 107A772C-D5E1-11D4-9A46-0090273FC14D 7A3C1760
InstallProtocolInterface: 6A7A5CFF-E8D9-4F70-BADA-75AB3025CE14 7A3C18B0
PROGRESS CODE: V03040003 I0
Loading driver 240612B7-A063-11D4-9A3A-0090273FC14D
InstallProtocolInterface: 5B1B31A1-9562-11D2-8E3F-00A0C969723B 7A449140
Loading driver at 0x0007A3C6000 EntryPoint=0x0007A3C7237 UsbBusDxe.efi
InstallProtocolInterface: BC62157E-3E33-4FEC-9920-2D3B36D750DF 7A449398
ProtectUefiImageCommon - 0x7A449140
- 0x000000007A3C6000 - 0x0000000000009C80
PROGRESS CODE: V03040002 I0
InstallProtocolInterface: 18A031AB-B443-4D1A-A5C0-0C09261E9F71 7A3CF9E0
InstallProtocolInterface: 107A772C-D5E1-11D4-9A46-0090273FC14D 7A3CF8C0
InstallProtocolInterface: 6A7A5CFF-E8D9-4F70-BADA-75AB3025CE14 7A3CF870
PROGRESS CODE: V03040003 I0
Loading driver 2D2E62CF-9ECF-43B7-8219-94E7FC713DFE
InstallProtocolInterface: 5B1B31A1-9562-11D2-8E3F-00A0C969723B 7A448040
Loading driver at 0x0007A3AD000 EntryPoint=0x0007A3ADD67 UsbKbDxe.efi
InstallProtocolInterface: BC62157E-3E33-4FEC-9920-2D3B36D750DF 7A448F18
ProtectUefiImageCommon - 0x7A448040
- 0x000000007A3AD000 - 0x0000000000006CC0
PROGRESS CODE: V03040002 I0
InstallProtocolInterface: 18A031AB-B443-4D1A-A5C0-0C09261E9F71 7A3B3A80
InstallProtocolInterface: 107A772C-D5E1-11D4-9A46-0090273FC14D 7A3B3A40
InstallProtocolInterface: 6A7A5CFF-E8D9-4F70-BADA-75AB3025CE14 7A3B39C0
PROGRESS CODE: V03040003 I0
Loading driver 9FB4B4A7-42C0-4BCD-8540-9BCC6711F83E
InstallProtocolInterface: 5B1B31A1-9562-11D2-8E3F-00A0C969723B 7A448A40
Loading driver at 0x0007A3A6000 EntryPoint=0x0007A3A99A9 UsbMassStorageDxe.efi
InstallProtocolInterface: BC62157E-3E33-4FEC-9920-2D3B36D750DF 7A448918
ProtectUefiImageCommon - 0x7A448A40
- 0x000000007A3A6000 - 0x00000000000060C0
PROGRESS CODE: V03040002 I0
InstallProtocolInterface: 18A031AB-B443-4D1A-A5C0-0C09261E9F71 7A3ABEA0
InstallProtocolInterface: 107A772C-D5E1-11D4-9A46-0090273FC14D 7A3ABCE0
InstallProtocolInterface: 6A7A5CFF-E8D9-4F70-BADA-75AB3025CE14 7A3ABE80
PROGRESS CODE: V03040003 I0
Loading driver 4ACA697E-F883-446F-98F7-096416FFFFFF
InstallProtocolInterface: 5B1B31A1-9562-11D2-8E3F-00A0C969723B 7A447040
Loading driver at 0x0007A39D000 EntryPoint=0x0007A39E47B OhciDxe.efi
InstallProtocolInterface: BC62157E-3E33-4FEC-9920-2D3B36D750DF 7A447E98
ProtectUefiImageCommon - 0x7A447040
- 0x000000007A39D000 - 0x0000000000008340
PROGRESS CODE: V03040002 I0
InstallProtocolInterface: 18A031AB-B443-4D1A-A5C0-0C09261E9F71 7A3A5140
InstallProtocolInterface: 107A772C-D5E1-11D4-9A46-0090273FC14D 7A3A5100
InstallProtocolInterface: 6A7A5CFF-E8D9-4F70-BADA-75AB3025CE14 7A3A50B0
PROGRESS CODE: V03040003 I0
Loading driver 0B04B2ED-861C-42CD-A22F-C3AAFACCB896
InstallProtocolInterface: 5B1B31A1-9562-11D2-8E3F-00A0C969723B 7A447440
Loading driver at 0x0007A41C000 EntryPoint=0x0007A41CE97 FbGop.efi
InstallProtocolInterface: BC62157E-3E33-4FEC-9920-2D3B36D750DF 7A447698
ProtectUefiImageCommon - 0x7A447440
- 0x000000007A41C000 - 0x00000000000041C0
PROGRESS CODE: V03040002 I0
InstallProtocolInterface: 18A031AB-B443-4D1A-A5C0-0C09261E9F71 7A41FEE0
InstallProtocolInterface: 107A772C-D5E1-11D4-9A46-0090273FC14D 7A41FFA0
InstallProtocolInterface: 6A7A5CFF-E8D9-4F70-BADA-75AB3025CE14 7A41FEB0
PROGRESS CODE: V03040003 I0
PROGRESS CODE: V03041001 I0
[BdsDxe] Locate Variable Lock protocol - Not Found
PROGRESS CODE: V03051005 I0
Variable Driver Auto Update Lang, Lang:eng, PlatformLang:en
InstallProtocolInterface: 09576E91-6D3F-11D2-8E39-00A0C969723B 7A4D93E0
InstallProtocolInterface: 330D4706-F2A0-4E4F-A369-B66FA8D54385 7A4D9F48
InstallProtocolInterface: 09576E91-6D3F-11D2-8E39-00A0C969723B 7A4D93C0
InstallProtocolInterface: 330D4706-F2A0-4E4F-A369-B66FA8D54385 7A4D9F60
InstallProtocolInterface: 09576E91-6D3F-11D2-8E39-00A0C969723B 7A4D94A0
InstallProtocolInterface: 330D4706-F2A0-4E4F-A369-B66FA8D54385 7A4D9278
InstallProtocolInterface: 09576E91-6D3F-11D2-8E39-00A0C969723B 7A4D9610
InstallProtocolInterface: 330D4706-F2A0-4E4F-A369-B66FA8D54385 7A4D92C0
Fail to get gEfiLdrMemoryDescriptorGuid from GUID HOB LIST!
InstallReadyToLock entering......
All EndOfDxe callbacks have returned successfully
InstallReadyToLock end
Boot Mode:0
Get PciExpress Address from Hob: 0x0
Pci Root bridge handle is 0x7A547618
InstallProtocolInterface: 09576E91-6D3F-11D2-8E39-00A0C969723B 7A41BC98
InstallProtocolInterface: 4CF5B200-68B8-4CA5-9EEC-B23E3F50029A 7A41B0A8
InstallProtocolInterface: 09576E91-6D3F-11D2-8E39-00A0C969723B 7A41B918
InstallProtocolInterface: 4CF5B200-68B8-4CA5-9EEC-B23E3F50029A 7A396128
InstallProtocolInterface: 09576E91-6D3F-11D2-8E39-00A0C969723B 7A41BC18
InstallProtocolInterface: 4CF5B200-68B8-4CA5-9EEC-B23E3F50029A 7A3963A8
InstallProtocolInterface: 09576E91-6D3F-11D2-8E39-00A0C969723B 7A41BF98
InstallProtocolInterface: 4CF5B200-68B8-4CA5-9EEC-B23E3F50029A 7A396628
PciExp - 1 (B-0, D-2, F-0)
InstallProtocolInterface: 09576E91-6D3F-11D2-8E39-00A0C969723B 7A41BA18
InstallProtocolInterface: 4CF5B200-68B8-4CA5-9EEC-B23E3F50029A 7A395028
PciExp - 1 (B-0, D-3, F-0)
InstallProtocolInterface: 09576E91-6D3F-11D2-8E39-00A0C969723B 7A41B018
InstallProtocolInterface: 4CF5B200-68B8-4CA5-9EEC-B23E3F50029A 7A395D28
PciExp - 1 (B-0, D-E, F-0)
InstallProtocolInterface: 09576E91-6D3F-11D2-8E39-00A0C969723B 7A41BD18
InstallProtocolInterface: 4CF5B200-68B8-4CA5-9EEC-B23E3F50029A 7A3952A8
InstallProtocolInterface: 09576E91-6D3F-11D2-8E39-00A0C969723B 7A41B718
InstallProtocolInterface: 4CF5B200-68B8-4CA5-9EEC-B23E3F50029A 7A395528
InstallProtocolInterface: 09576E91-6D3F-11D2-8E39-00A0C969723B 7A41B798
InstallProtocolInterface: 4CF5B200-68B8-4CA5-9EEC-B23E3F50029A 7A3957A8
InstallProtocolInterface: 09576E91-6D3F-11D2-8E39-00A0C969723B 7A395F98
InstallProtocolInterface: 4CF5B200-68B8-4CA5-9EEC-B23E3F50029A 7A394028
PciExp - 1 (B-0, D-13, F-0)
InstallProtocolInterface: 09576E91-6D3F-11D2-8E39-00A0C969723B 7A396C98
InstallProtocolInterface: 4CF5B200-68B8-4CA5-9EEC-B23E3F50029A 7A394D28
PciExp - 1 (B-0, D-13, F-2)
InstallProtocolInterface: 09576E91-6D3F-11D2-8E39-00A0C969723B 7A396D18
InstallProtocolInterface: 4CF5B200-68B8-4CA5-9EEC-B23E3F50029A 7A3942A8
PciExp - 1 (B-2, D-0, F-0)
InstallProtocolInterface: 09576E91-6D3F-11D2-8E39-00A0C969723B 7A394B98
InstallProtocolInterface: 4CF5B200-68B8-4CA5-9EEC-B23E3F50029A 7A394528
PciExp - 1 (B-0, D-13, F-3)
InstallProtocolInterface: 09576E91-6D3F-11D2-8E39-00A0C969723B 7A394C18
InstallProtocolInterface: 4CF5B200-68B8-4CA5-9EEC-B23E3F50029A 7A3947A8
PciExp - 1 (B-0, D-14, F-0)
InstallProtocolInterface: 09576E91-6D3F-11D2-8E39-00A0C969723B 7A394F98
InstallProtocolInterface: 4CF5B200-68B8-4CA5-9EEC-B23E3F50029A 7A393028
PciExp - 1 (B-0, D-14, F-1)
InstallProtocolInterface: 09576E91-6D3F-11D2-8E39-00A0C969723B 7A394C98
InstallProtocolInterface: 4CF5B200-68B8-4CA5-9EEC-B23E3F50029A 7A393D28
InstallProtocolInterface: 09576E91-6D3F-11D2-8E39-00A0C969723B 7A393B98
InstallProtocolInterface: 4CF5B200-68B8-4CA5-9EEC-B23E3F50029A 7A3932A8
InstallProtocolInterface: 09576E91-6D3F-11D2-8E39-00A0C969723B 7A393C18
InstallProtocolInterface: 4CF5B200-68B8-4CA5-9EEC-B23E3F50029A 7A393528
InstallProtocolInterface: 09576E91-6D3F-11D2-8E39-00A0C969723B 7A393C98
InstallProtocolInterface: 4CF5B200-68B8-4CA5-9EEC-B23E3F50029A 7A3937A8
InstallProtocolInterface: 09576E91-6D3F-11D2-8E39-00A0C969723B 7A393F98
InstallProtocolInterface: 4CF5B200-68B8-4CA5-9EEC-B23E3F50029A 7A392028
InstallProtocolInterface: 09576E91-6D3F-11D2-8E39-00A0C969723B 7A393A18
InstallProtocolInterface: 4CF5B200-68B8-4CA5-9EEC-B23E3F50029A 7A392D28
InstallProtocolInterface: 09576E91-6D3F-11D2-8E39-00A0C969723B 7A393A98
InstallProtocolInterface: 4CF5B200-68B8-4CA5-9EEC-B23E3F50029A 7A3922A8
InstallProtocolInterface: 09576E91-6D3F-11D2-8E39-00A0C969723B 7A393B18
InstallProtocolInterface: 4CF5B200-68B8-4CA5-9EEC-B23E3F50029A 7A392528
InstallProtocolInterface: 09576E91-6D3F-11D2-8E39-00A0C969723B 7A392A18
InstallProtocolInterface: 4CF5B200-68B8-4CA5-9EEC-B23E3F50029A 7A3927A8
InstallProtocolInterface: 09576E91-6D3F-11D2-8E39-00A0C969723B 7A392F98
InstallProtocolInterface: 4CF5B200-68B8-4CA5-9EEC-B23E3F50029A 7A391028
InstallProtocolInterface: 09576E91-6D3F-11D2-8E39-00A0C969723B 7A392A98
InstallProtocolInterface: 4CF5B200-68B8-4CA5-9EEC-B23E3F50029A 7A391D28
InstallProtocolInterface: 09576E91-6D3F-11D2-8E39-00A0C969723B 7A392B18
InstallProtocolInterface: 4CF5B200-68B8-4CA5-9EEC-B23E3F50029A 7A3912A8
InstallProtocolInterface: 09576E91-6D3F-11D2-8E39-00A0C969723B 7A391B98
InstallProtocolInterface: 4CF5B200-68B8-4CA5-9EEC-B23E3F50029A 7A391528
InstallProtocolInterface: 09576E91-6D3F-11D2-8E39-00A0C969723B 7A391C18
InstallProtocolInterface: 4CF5B200-68B8-4CA5-9EEC-B23E3F50029A 7A3917A8
InstallProtocolInterface: 09576E91-6D3F-11D2-8E39-00A0C969723B 7A391F98
InstallProtocolInterface: 4CF5B200-68B8-4CA5-9EEC-B23E3F50029A 7A390028
InstallProtocolInterface: 09576E91-6D3F-11D2-8E39-00A0C969723B 7A391C98
InstallProtocolInterface: 4CF5B200-68B8-4CA5-9EEC-B23E3F50029A 7A390D28
InstallProtocolInterface: 09576E91-6D3F-11D2-8E39-00A0C969723B 7A390B98
InstallProtocolInterface: 4CF5B200-68B8-4CA5-9EEC-B23E3F50029A 7A3902A8
InstallProtocolInterface: 09576E91-6D3F-11D2-8E39-00A0C969723B 7A390C18
InstallProtocolInterface: 4CF5B200-68B8-4CA5-9EEC-B23E3F50029A 7A390528
InstallProtocolInterface: 09576E91-6D3F-11D2-8E39-00A0C969723B 7A390C98
InstallProtocolInterface: 4CF5B200-68B8-4CA5-9EEC-B23E3F50029A 7A3907A8
InstallProtocolInterface: 09576E91-6D3F-11D2-8E39-00A0C969723B 7A390F98
InstallProtocolInterface: 4CF5B200-68B8-4CA5-9EEC-B23E3F50029A 7A38F028
InstallProtocolInterface: 09576E91-6D3F-11D2-8E39-00A0C969723B 7A390A18
InstallProtocolInterface: 4CF5B200-68B8-4CA5-9EEC-B23E3F50029A 7A38FD28
InstallProtocolInterface: 09576E91-6D3F-11D2-8E39-00A0C969723B 7A390A98
InstallProtocolInterface: 4CF5B200-68B8-4CA5-9EEC-B23E3F50029A 7A38F2A8
Find the VGA device
GOP START
PROGRESS CODE: V01030004 I0
InstallProtocolInterface: 09576E91-6D3F-11D2-8E39-00A0C969723B 7A389F18
FbGopCheckForVbe - Success
InstallProtocolInterface: 9042A9DE-23DC-4A38-96FB-7ADED080516A 7A38A4B0
InstallProtocolInterface: 1C0C34F6-D380-41FA-A049-8AD06C1A66AA 7A38A4D0
InstallProtocolInterface: BD8C1056-9F36-44EC-92A8-A6337F817986 7A38A4E0
ERROR: C00000002:V03058002 I0 FC5C7020-1A48-4198-9BE2-EAD5ABC8CF2F 7A38A818
Find the LPC Bridge device
GraphicsConsole video resolution 1024 x 768
Graphics - Mode 0, Column = 80, Row = 25
Graphics - Mode 1, Column = 0, Row = 0
Graphics - Mode 2, Column = 100, Row = 31
Graphics - Mode 3, Column = 128, Row = 40
InstallProtocolInterface: 387477C2-69C7-11D2-8E39-00A0C969723B 7A0875B0
InstallProtocolInterface: D3B36F2C-D551-11D4-9A46-0090273FC14D 0
InstallProtocolInterface: 9042A9DE-23DC-4A38-96FB-7ADED080516A 7A452DA0
InstallProtocolInterface: 64A892DC-5561-4536-92C7-799BFC183355 7A07A2A8
PROGRESS CODE: V02060000 I0
PROGRESS CODE: V02060004 I0
InstallProtocolInterface: 09576E91-6D3F-11D2-8E39-00A0C969723B 7A07A398
InstallProtocolInterface: 7EE2BD44-3DA0-11D4-9A38-0090273FC14D 7A07A828
InstallProtocolInterface: 09576E91-6D3F-11D2-8E39-00A0C969723B 7A077018
InstallProtocolInterface: 7EE2BD44-3DA0-11D4-9A38-0090273FC14D 7A07A528
InstallProtocolInterface: 09576E91-6D3F-11D2-8E39-00A0C969723B 7A077C18
InstallProtocolInterface: 7EE2BD44-3DA0-11D4-9A38-0090273FC14D 7A077B28
InstallProtocolInterface: 09576E91-6D3F-11D2-8E39-00A0C969723B 7A077198
InstallProtocolInterface: 7EE2BD44-3DA0-11D4-9A38-0090273FC14D 7A0770A8
InstallProtocolInterface: 09576E91-6D3F-11D2-8E39-00A0C969723B 7A077598
InstallProtocolInterface: 7EE2BD44-3DA0-11D4-9A38-0090273FC14D 7A077428
InstallProtocolInterface: 09576E91-6D3F-11D2-8E39-00A0C969723B 7A076018
InstallProtocolInterface: 7EE2BD44-3DA0-11D4-9A38-0090273FC14D 7A077728
PROGRESS CODE: V01010004 I0
ERROR: C40000002:V01010003 I0 3DC82376-637B-40A6-A8FC-A565417F2C38 7A076098
XhcCreateUsb3Hc: Capability length 0x80
XhcCreateUsb3Hc: HcSParams1 0xF000820
XhcCreateUsb3Hc: HcSParams2 0x94000054
XhcCreateUsb3Hc: HcCParams 0x200077C1
XhcCreateUsb3Hc: DBOff 0x3000
XhcCreateUsb3Hc: RTSOff 0x2000
XhcCreateUsb3Hc: UsbLegSupOffset 0x46C
XhcCreateUsb3Hc: DebugCapSupOffset 0x700
XhcSetBiosOwnership: called to set BIOS ownership
XhcResetHC!
XhcInitSched:DCBAA=0x7A051000
XhcInitSched:XHC_CRCR=0x7A051140
XhcInitSched:XHC_EVENTRING=0x7A052140
InstallProtocolInterface: 3E745226-9818-45B6-A2AC-D7CD0E8BA2BC 7A061038
XhcDriverBindingStart: XHCI started for controller @ 7A38DF98
PROGRESS CODE: V02020000 I0
PROGRESS CODE: V02020004 I0
InstallProtocolInterface: 240612B7-A063-11D4-9A3A-0090273FC14D 7A03C020
PROGRESS CODE: V02020003 I0
XhcGetCapability: 15 ports, 64 bit 1
UsbRootHubInit: root hub 7A03CA98 - max speed 3, 15 ports
XhcClearRootHubPortFeature: status Success
UsbEnumeratePort: port 1 state - 201, change - 01 on 7A03CA98
UsbEnumeratePort: Device Connect/Disconnect Normally
UsbEnumeratePort: new device connected at port 1
XhcUsbPortReset!
XhcSetRootHubPortFeature: status Success
XhcClearRootHubPortFeature: status Success
XhcClearRootHubPortFeature: status Success
Enable Slot Successfully, The Slot ID = 0x1
Address 1 assigned successfully
UsbEnumerateNewDev: hub port 1 is reset
UsbEnumerateNewDev: device is of 1 speed
UsbEnumerateNewDev: device uses translator (0, 0)
UsbEnumerateNewDev: device is now ADDRESSED at 1
UsbEnumerateNewDev: max packet size for EP 0 is 8
Evaluate context
UsbBuildDescTable: device has 1 configures
UsbGetOneConfig: total length is 34
UsbParseConfigDesc: config 1 has 1 interfaces
UsbParseInterfaceDesc: interface 0(setting 0) has 1 endpoints
Configure Endpoint
UsbEnumerateNewDev: device 1 is now in CONFIGED state
UsbSelectConfig: config 1 selected for device 1
UsbSelectSetting: setting 0 selected for interface 0
InstallProtocolInterface: 09576E91-6D3F-11D2-8E39-00A0C969723B 7A03D418
InstallProtocolInterface: 2B2F68D6-0CD2-44CF-8E8B-BBA20B1B5B75 7A03BEC0
UsbConnectDriver: TPL before connect is 8, 7A03D398
PROGRESS CODE: V01010004 I0
PROGRESS CODE: V01010003 I0
PROGRESS CODE: V01010006 I0
InstallProtocolInterface: 387477C1-69C7-11D2-8E39-00A0C969723B 7A03A1B8
InstallProtocolInterface: DD9E7534-7762-4698-8C14-F58517A625AA 7A03A1D0
PROGRESS CODE: V01010001 I0
PROGRESS CODE: V01011001 I0
InstallProtocolInterface: D3B36F2B-D551-11D4-9A46-0090273FC14D 0
UsbConnectDriver: TPL after connect is 8
PROGRESS CODE: V02020006 I0
XhcClearRootHubPortFeature: status Success
UsbEnumeratePort: port 4 state - 01, change - 01 on 7A03CA98
UsbEnumeratePort: Device Connect/Disconnect Normally
UsbEnumeratePort: new device connected at port 4
XhcUsbPortReset!
XhcSetRootHubPortFeature: status Success
XhcClearRootHubPortFeature: status Success
XhcClearRootHubPortFeature: status Success
Enable Slot Successfully, The Slot ID = 0x2
Address 2 assigned successfully
UsbEnumerateNewDev: hub port 4 is reset
UsbEnumerateNewDev: device is of 2 speed
UsbEnumerateNewDev: device uses translator (0, 0)
UsbEnumerateNewDev: device is now ADDRESSED at 2
UsbEnumerateNewDev: max packet size for EP 0 is 64
Evaluate context
UsbBuildDescTable: device has 1 configures
UsbGetOneConfig: total length is 32
UsbParseConfigDesc: config 1 has 1 interfaces
UsbParseInterfaceDesc: interface 0(setting 0) has 2 endpoints
Configure Endpoint
UsbEnumerateNewDev: device 2 is now in CONFIGED state
UsbSelectConfig: config 1 selected for device 2
UsbSelectSetting: setting 0 selected for interface 0
InstallProtocolInterface: 09576E91-6D3F-11D2-8E39-00A0C969723B 7A035E98
InstallProtocolInterface: 2B2F68D6-0CD2-44CF-8E8B-BBA20B1B5B75 7A035F40
PROGRESS CODE: V02020006 I0
UsbBusStart: usb bus started on 7A38DF98, root hub 7A03CA98
Start showing progress bar... Press any key to stop it! ...Zzz....
Showing progress bar...Remaining 5 second!
Showing progress bar...Remaining 4 second!
InstallProtocolInterface: 09576E91-6D3F-11D2-8E39-00A0C969723B 7A4DAD60
InstallProtocolInterface: 330D4706-F2A0-4E4F-A369-B66FA8D54385 7A02F068
InstallProtocolInterface: 09576E91-6D3F-11D2-8E39-00A0C969723B 7A4DAD90
InstallProtocolInterface: 330D4706-F2A0-4E4F-A369-B66FA8D54385 7A030948
PROGRESS CODE: V03050006 I0
InstallProtocolInterface: 348C4D62-BFBD-4882-9ECE-C80BB1C4783B 0
PROGRESS CODE: V03050007 I0
PROGRESS CODE: V01010004 I0
ERROR: C40000002:V01010003 I0 3DC82376-637B-40A6-A8FC-A565417F2C38 7A029D98
PROGRESS CODE: V02020000 I0
Terminal - Mode 0, Column = 80, Row = 25
Terminal - Mode 1, Column = 80, Row = 50
Terminal - Mode 2, Column = 100, Row = 31
PROGRESS CODE: V01040001 I0
InstallProtocolInterface: 387477C1-69C7-11D2-8E39-00A0C969723B 7A030D40
InstallProtocolInterface: DD9E7534-7762-4698-8C14-F58517A625AA 7A030E28
InstallProtocolInterface: 387477C2-69C7-11D2-8E39-00A0C969723B 7A030D58
InstallProtocolInterface: 09576E91-6D3F-11D2-8E39-00A0C969723B 7A029B98
SataControllerStart START
InstallProtocolInterface: A1E37052-80D9-4E65-A317-3E9A55C43EC9 7A02FEA0
SataControllerStart END status = Success
==AtaAtapiPassThru Start== Controller = 7A38F818
InstallProtocolInterface: 1D3DE7F0-0807-424F-AA69-11A54E19A46F 7A02F6C0
InstallProtocolInterface: 143B7632-B81B-4CB7-ABD3-B625A5B9BFFE 7A02F710
PROGRESS CODE: V02080000 I0
InstallProtocolInterface: 19DF145A-B1D4-453F-8507-38816676D7F6 7A399D98
PROGRESS CODE: V02080003 I0
PROGRESS CODE: V02070000 I0
InstallProtocolInterface: 0167CCC4-D0F7-4F21-A3EF-9E64B7CDCE8B 7A3990A0
PROGRESS CODE: V02070003 I0
PROGRESS CODE: V02020000 I0
UsbBusRecursivelyConnectWantedUsbIo: TPL before connect is 4
InstallProtocolInterface: 964E5B21-6459-11D2-8E39-00A0C969723B 7A027038
InstallProtocolInterface: D432A67F-14DC-484B-B3BB-3F0291849327 7A0270B0
InstallProtocolInterface: CE345171-BA0B-11D2-8E4F-00A0C969723B 7A027F20
BlockSize : 512
LastBlock : 77FFFF
PartitionValidMbr: Bad MBR partition size EndingLBA(D9FF09B7) > LastLBA(77FFFF)
InstallProtocolInterface: 964E5B22-6459-11D2-8E39-00A0C969723B 7A026030
Installed Fat filesystem on 7A035B98
UsbBusRecursivelyConnectWantedUsbIo: TPL after connect is 4
SdMmcPciHcDriverBindingStart: Start
== Slot [0] Capability is 0x7A024A70 ==
Timeout Clk Freq 1MHz
Base Clk Freq 200MHz
Max Blk Len 512bytes
8-bit Support FALSE
ADMA2 Support TRUE
HighSpeed Support TRUE
SDMA Support TRUE
Suspend/Resume FALSE
Voltage 3.3 TRUE
Voltage 3.0 FALSE
Voltage 1.8 TRUE
64-bit Sys Bus TRUE
Async Interrupt TRUE
SlotType Embedded Slot
SDR50 Support TRUE
SDR104 Support TRUE
DDR50 Support TRUE
Driver Type A FALSE
Driver Type C FALSE
Driver Type D FALSE
Driver Type 4 FALSE
Retuning TimerCnt 14seconds
SDR50 Tuning TRUE
Retuning Mode Mode 1
Clock Multiplier M = 1
HS 400 FALSE
SdMmcHcCardDetect: No device attached in Slot[0]!!!
InstallProtocolInterface: 716EF0D9-FF83-4F69-81E9-518BD39A8E70 7A0249B0
SdMmcPciHcDriverBindingStart: Success End on 7A38B218
InstallProtocolInterface: 2145F72F-E6F1-4440-A828-59DC9AAB5F89 79A90018
InstallProtocolInterface: 430AC2F7-EEC6-4093-94F7-9F825A7C1C40 7A024698
SdMmcPciHcDriverBindingStart: Start
== Slot [0] Capability is 0x7A023D70 ==
Timeout Clk Freq 1MHz
Base Clk Freq 200MHz
Max Blk Len 2048bytes
8-bit Support TRUE
ADMA2 Support TRUE
HighSpeed Support TRUE
SDMA Support TRUE
Suspend/Resume FALSE
Voltage 3.3 FALSE
Voltage 3.0 FALSE
Voltage 1.8 TRUE
64-bit Sys Bus TRUE
Async Interrupt FALSE
SlotType Embedded Slot
SDR50 Support TRUE
SDR104 Support TRUE
DDR50 Support TRUE
Driver Type A FALSE
Driver Type C FALSE
Driver Type D FALSE
Driver Type 4 FALSE
Retuning TimerCnt 14seconds
SDR50 Tuning FALSE
Retuning Mode Mode 1
Clock Multiplier M = 1
HS 400 TRUE
BaseClkFreq 200MHz Divisor 250 ClockFreq 400Khz
EmmcIdentification: Found a EMMC device at slot [0], RCA [1]
EmmcSetBusMode: HsTiming 3 ClockFreq 200 BusWidth 8 Ddr TRUE
BaseClkFreq 200MHz Divisor 0 ClockFreq 200000Khz
BaseClkFreq 200MHz Divisor 2 ClockFreq 52000Khz
BaseClkFreq 200MHz Divisor 0 ClockFreq 200000Khz
EmmcSetBusMode: Switch to HS400 Success
InstallProtocolInterface: 716EF0D9-FF83-4F69-81E9-518BD39A8E70 7A023CB0
SdMmcPciHcDriverBindingStart: Success End on 7A38B698
InstallProtocolInterface: 2145F72F-E6F1-4440-A828-59DC9AAB5F89 79A90018
== Dump Emmc Csd Register==
CSD structure 0x3
System specification version 0x4
Data read access-time 1 0x27
Data read access-time 2 0x1
Max. bus clock frequency 0x32
Device command classes 0xF5
Max. read data block length 0x9
Partial blocks for read allowed 0x0
Write block misalignment 0x0
Read block misalignment 0x0
DSR implemented 0x0
Device size 0xFFF
Max. read current @ VDD min 0x6
Max. read current @ VDD max 0x6
Max. write current @ VDD min 0x6
Max. write current @ VDD max 0x6
Device size multiplier 0x7
Erase group size 0x1F
Erase group size multiplier 0x1F
Write protect group size 0xF
Write protect group enable 0x1
Manufacturer default ECC 0x0
Write speed factor 0x3
Max. write data block length 0x9
Partial blocks for write allowed 0x0
Content protection application 0x0
File format group 0x0
Copy flag (OTP) 0x1
Permanent write protection 0x0
Temporary write protection 0x0
File format 0x0
ECC code 0x0
==Dump Emmc ExtCsd Register==
Supported Command Sets 0x0
HPI features 0x1
Background operations support 0x1
Background operations status 0x0
Number of correctly programmed sectors 0x0
Initialization time after partitioning 0x1E
TRIM Multiplier 0x2
Secure Feature support 0x55
Secure Erase Multiplier 0x1B
Secure TRIM Multiplier 0x11
Boot information 0x7
Boot partition size 0x20
Access size 0x7
High-capacity erase unit size 0x1
High-capacity erase timeout 0x1
Reliable write sector count 0x1
High-capacity write protect group size 0x10
Sleep/awake timeout 0x11
Sector Count 0x747C000
Partition switching timing 0x1
Out-of-interrupt busy timing 0x5
I/O Driver Strength 0x1F
Device type 0x57
CSD STRUCTURE 0x2
Extended CSD revision 0x7
Command set 0x0
Command set revision 0x0
Power class 0x0
High-speed interface timing 0x3
Bus width mode 0x0
Erased memory content 0x0
Partition configuration 0x0
Boot config protection 0x0
Boot bus Conditions 0x0
High-density erase group definition 0x0
Boot write protection status register 0x0
Boot area write protection register 0x10
User area write protection register 0x0
FW configuration 0x0
RPMB Size 0x20
H/W reset function 0x1
Partitioning Support 0x7
Max Enhanced Area Size 0x000E8F
Partitions attribute 0x0
Partitioning Setting 0x0
General Purpose Partition 1 Size 0x000000
General Purpose Partition 2 Size 0x000000
General Purpose Partition 3 Size 0x000000
General Purpose Partition 4 Size 0x000000
Enhanced User Data Area Size 0x000000
Enhanced User Data Start Address 0x0
Bad Block Management mode 0x0
Native sector size 0x0
Sector size emulation 0x0
Sector size 0x0
InstallProtocolInterface: 09576E91-6D3F-11D2-8E39-00A0C969723B 7A023918
InstallProtocolInterface: 09576E91-6D3F-11D2-8E39-00A0C969723B 7A023198
InstallProtocolInterface: 964E5B21-6459-11D2-8E39-00A0C969723B 79A90070
InstallProtocolInterface: A77B2472-E282-4E9F-A245-C2C0E27BBCC1 79A900A0
InstallProtocolInterface: 95A9A93E-A86E-4926-AAEF-9918E772D987 79A90108
InstallProtocolInterface: 09576E91-6D3F-11D2-8E39-00A0C969723B 7A023498
InstallProtocolInterface: 964E5B21-6459-11D2-8E39-00A0C969723B 79A90158
InstallProtocolInterface: A77B2472-E282-4E9F-A245-C2C0E27BBCC1 79A90188
InstallProtocolInterface: 95A9A93E-A86E-4926-AAEF-9918E772D987 79A901F0
InstallProtocolInterface: 09576E91-6D3F-11D2-8E39-00A0C969723B 7A022198
InstallProtocolInterface: 964E5B21-6459-11D2-8E39-00A0C969723B 79A90240
InstallProtocolInterface: A77B2472-E282-4E9F-A245-C2C0E27BBCC1 79A90270
InstallProtocolInterface: 95A9A93E-A86E-4926-AAEF-9918E772D987 79A902D8
InstallProtocolInterface: CE345171-BA0B-11D2-8E4F-00A0C969723B 7A023B20
InstallProtocolInterface: 151C8EAE-7F2C-472C-9E54-9828194F6A88 7A023B38
BlockSize : 512
LastBlock : 747BFFF
EmmcRead (): Part 0 Lba 0x0 BlkNo 0x1 Event 0 with Success
EmmcRead (): Part 0 Lba 0x1 BlkNo 0x1 Event 0 with Success
EmmcRead (): Part 0 Lba 0x2 BlkNo 0x20 Event 0 with Success
Valid efi partition table header
EmmcRead (): Part 0 Lba 0x747BFFF BlkNo 0x1 Event 0 with Success
EmmcRead (): Part 0 Lba 0x747BFDF BlkNo 0x20 Event 0 with Success
Valid efi partition table header
Valid primary and Valid backup partition table
EmmcRead (): Part 0 Lba 0x2 BlkNo 0x20 Event 0 with Success
Partition entries read block success
Number of partition entries: 128
start check partition entries
End check partition entries
Index : 0
Start LBA : 800
End LBA : 97FF
Partition size: 9000
Start : 100000 End : 12FFE00
InstallProtocolInterface: 09576E91-6D3F-11D2-8E39-00A0C969723B 7A021C98
InstallProtocolInterface: 964E5B21-6459-11D2-8E39-00A0C969723B 7A0214B0
InstallProtocolInterface: A77B2472-E282-4E9F-A245-C2C0E27BBCC1 7A0214E0
InstallProtocolInterface: C12A7328-F81F-11D2-BA4B-00A0C93EC93B 0
Index : 1
Start LBA : 9800
End LBA : 6EA97FF
Partition size: 6EA0000
Start : 1300000 End : DD52FFE00
InstallProtocolInterface: 09576E91-6D3F-11D2-8E39-00A0C969723B 7A021798
InstallProtocolInterface: 964E5B21-6459-11D2-8E39-00A0C969723B 7A021630
InstallProtocolInterface: A77B2472-E282-4E9F-A245-C2C0E27BBCC1 7A021660
Index : 2
Start LBA : 6EA9800
End LBA : 747B7FF
Partition size: 5D2000
Start : DD5300000 End : E8F6FFE00
InstallProtocolInterface: 09576E91-6D3F-11D2-8E39-00A0C969723B 79A82098
InstallProtocolInterface: 964E5B21-6459-11D2-8E39-00A0C969723B 79A82D30
InstallProtocolInterface: A77B2472-E282-4E9F-A245-C2C0E27BBCC1 79A82D60
Prepare to Free Pool
InstallProtocolInterface: CE345171-BA0B-11D2-8E4F-00A0C969723B 79A82BA0
InstallProtocolInterface: 151C8EAE-7F2C-472C-9E54-9828194F6A88 79A82BB8
BlockSize : 512
LastBlock : 8FFF
EmmcRead (): Part 0 Lba 0x800 BlkNo 0x1 Event 0 with Success
EmmcRead (): Part 0 Lba 0x840 BlkNo 0x4 Event 0 with Success
EmmcRead (): Part 0 Lba 0x800 BlkNo 0x1 Event 0 with Success
EmmcRead (): Part 0 Lba 0x800 BlkNo 0x1 Event 0 with Success
EmmcRead (): Part 0 Lba 0x801 BlkNo 0x1 Event 0 with Success
InstallProtocolInterface: 964E5B22-6459-11D2-8E39-00A0C969723B 79A87030
Installed Fat filesystem on 7A021F18
InstallProtocolInterface: CE345171-BA0B-11D2-8E4F-00A0C969723B 79A827A0
InstallProtocolInterface: 151C8EAE-7F2C-472C-9E54-9828194F6A88 79A827B8
BlockSize : 512
LastBlock : 6E9FFFF
EmmcRead (): Part 0 Lba 0x9800 BlkNo 0x1 Event 0 with Success
EmmcRead (): Part 0 Lba 0x9840 BlkNo 0x4 Event 0 with Success
EmmcRead (): Part 0 Lba 0x9800 BlkNo 0x1 Event 0 with Success
EmmcRead (): Part 0 Lba 0x9800 BlkNo 0x1 Event 0 with Success
InstallProtocolInterface: CE345171-BA0B-11D2-8E4F-00A0C969723B 79A82A20
InstallProtocolInterface: 151C8EAE-7F2C-472C-9E54-9828194F6A88 79A82A38
BlockSize : 512
LastBlock : 5D1FFF
EmmcRead (): Part 0 Lba 0x6EA9800 BlkNo 0x1 Event 0 with Success
EmmcRead (): Part 0 Lba 0x6EA9840 BlkNo 0x4 Event 0 with Success
EmmcRead (): Part 0 Lba 0x6EA9800 BlkNo 0x1 Event 0 with Success
EmmcRead (): Part 0 Lba 0x6EA9800 BlkNo 0x1 Event 0 with Success
InstallProtocolInterface: CE345171-BA0B-11D2-8E4F-00A0C969723B 79A86AA0
InstallProtocolInterface: 151C8EAE-7F2C-472C-9E54-9828194F6A88 79A86AB8
BlockSize : 512
LastBlock : 1FFF
EmmcRead (): Part 1 Lba 0x0 BlkNo 0x1 Event 0 with Success
EmmcRead (): Part 1 Lba 0x40 BlkNo 0x4 Event 0 with Success
EmmcRead (): Part 1 Lba 0x0 BlkNo 0x1 Event 0 with Success
EmmcRead (): Part 1 Lba 0x0 BlkNo 0x1 Event 0 with Success
InstallProtocolInterface: CE345171-BA0B-11D2-8E4F-00A0C969723B 79A86020
InstallProtocolInterface: 151C8EAE-7F2C-472C-9E54-9828194F6A88 79A86038
BlockSize : 512
LastBlock : 1FFF
EmmcRead (): Part 2 Lba 0x0 BlkNo 0x1 Event 0 with Success
EmmcRead (): Part 2 Lba 0x40 BlkNo 0x4 Event 0 with Success
EmmcRead (): Part 2 Lba 0x0 BlkNo 0x1 Event 0 with Success
EmmcRead (): Part 2 Lba 0x0 BlkNo 0x1 Event 0 with Success
SdMmcPciHcDriverBindingStart: Start
== Slot [0] Capability is 0x79A850F0 ==
Timeout Clk Freq 1MHz
Base Clk Freq 200MHz
Max Blk Len 2048bytes
8-bit Support FALSE
ADMA2 Support TRUE
HighSpeed Support TRUE
SDMA Support TRUE
Suspend/Resume FALSE
Voltage 3.3 TRUE
Voltage 3.0 FALSE
Voltage 1.8 TRUE
64-bit Sys Bus TRUE
Async Interrupt TRUE
SlotType Embedded Slot
SDR50 Support TRUE
SDR104 Support TRUE
DDR50 Support TRUE
Driver Type A FALSE
Driver Type C FALSE
Driver Type D FALSE
Driver Type 4 FALSE
Retuning TimerCnt 14seconds
SDR50 Tuning FALSE
Retuning Mode Mode 1
Clock Multiplier M = 1
HS 400 FALSE
BaseClkFreq 200MHz Divisor 250 ClockFreq 400Khz
SdCardIdentification: Executing Cmd8 fails with Device Error
InstallProtocolInterface: 716EF0D9-FF83-4F69-81E9-518BD39A8E70 79A85030
SdMmcPciHcDriverBindingStart: Success End on 7A38AF98
InstallProtocolInterface: 2145F72F-E6F1-4440-A828-59DC9AAB5F89 795D5018
InstallProtocolInterface: 430AC2F7-EEC6-4093-94F7-9F825A7C1C40 79A85998
PROGRESS CODE: V02060000 I0
PROGRESS CODE: V02060004 I0
PROGRESS CODE: V01010004 I0
ERROR: C40000002:V01010003 I0 3DC82376-637B-40A6-A8FC-A565417F2C38 79A85C98
PROGRESS CODE: V02080000 I0
PROGRESS CODE: V02080003 I0
SataControllerStart START
SataControllerStart error return status = Already started
PROGRESS CODE: V02070000 I0
PROGRESS CODE: V02070003 I0
PROGRESS CODE: V02020000 I0
InstallProtocolInterface: 2145F72F-E6F1-4440-A828-59DC9AAB5F89 795D5018
InstallProtocolInterface: 430AC2F7-EEC6-4093-94F7-9F825A7C1C40 7A03D818
BlockSize : 512
LastBlock : 747BFFF
EmmcRead (): Part 0 Lba 0x0 BlkNo 0x1 Event 0 with Success
EmmcRead (): Part 0 Lba 0x1 BlkNo 0x1 Event 0 with Success
EmmcRead (): Part 0 Lba 0x2 BlkNo 0x20 Event 0 with Success
Valid efi partition table header
EmmcRead (): Part 0 Lba 0x747BFFF BlkNo 0x1 Event 0 with Success
EmmcRead (): Part 0 Lba 0x747BFDF BlkNo 0x20 Event 0 with Success
Valid efi partition table header
Valid primary and Valid backup partition table
EmmcRead (): Part 0 Lba 0x2 BlkNo 0x20 Event 0 with Success
Partition entries read block success
Number of partition entries: 128
start check partition entries
End check partition entries
Index : 0
Start LBA : 800
End LBA : 97FF
Partition size: 9000
Start : 100000 End : 12FFE00
Index : 1
Start LBA : 9800
End LBA : 6EA97FF
Partition size: 6EA0000
Start : 1300000 End : DD52FFE00
Index : 2
Start LBA : 6EA9800
End LBA : 747B7FF
Partition size: 5D2000
Start : DD5300000 End : E8F6FFE00
Prepare to Free Pool
BlockSize : 512
LastBlock : 6E9FFFF
EmmcRead (): Part 0 Lba 0x9800 BlkNo 0x1 Event 0 with Success
EmmcRead (): Part 0 Lba 0x9840 BlkNo 0x4 Event 0 with Success
EmmcRead (): Part 0 Lba 0x9800 BlkNo 0x1 Event 0 with Success
EmmcRead (): Part 0 Lba 0x9800 BlkNo 0x1 Event 0 with Success
BlockSize : 512
LastBlock : 5D1FFF
EmmcRead (): Part 0 Lba 0x6EA9800 BlkNo 0x1 Event 0 with Success
EmmcRead (): Part 0 Lba 0x6EA9840 BlkNo 0x4 Event 0 with Success
EmmcRead (): Part 0 Lba 0x6EA9800 BlkNo 0x1 Event 0 with Success
EmmcRead (): Part 0 Lba 0x6EA9800 BlkNo 0x1 Event 0 with Success
BlockSize : 512
LastBlock : 1FFF
EmmcRead (): Part 1 Lba 0x0 BlkNo 0x1 Event 0 with Success
EmmcRead (): Part 1 Lba 0x40 BlkNo 0x4 Event 0 with Success
EmmcRead (): Part 1 Lba 0x0 BlkNo 0x1 Event 0 with Success
EmmcRead (): Part 1 Lba 0x0 BlkNo 0x1 Event 0 with Success
BlockSize : 512
LastBlock : 1FFF
EmmcRead (): Part 2 Lba 0x0 BlkNo 0x1 Event 0 with Success
EmmcRead (): Part 2 Lba 0x40 BlkNo 0x4 Event 0 with Success
EmmcRead (): Part 2 Lba 0x0 BlkNo 0x1 Event 0 with Success
EmmcRead (): Part 2 Lba 0x0 BlkNo 0x1 Event 0 with Success
InstallProtocolInterface: 2145F72F-E6F1-4440-A828-59DC9AAB5F89 795D5018
InstallProtocolInterface: 430AC2F7-EEC6-4093-94F7-9F825A7C1C40 79A84118
PROGRESS CODE: V02060000 I0
PROGRESS CODE: V02060004 I0
PROGRESS CODE: V01010004 I0
ERROR: C40000002:V01010003 I0 3DC82376-637B-40A6-A8FC-A565417F2C38 79A84798
PROGRESS CODE: V01010004 I0
ERROR: C40000002:V01010003 I0 3DC82376-637B-40A6-A8FC-A565417F2C38 79A84F98
PROGRESS CODE: V01010004 I0
ERROR: C40000002:V01010003 I0 3DC82376-637B-40A6-A8FC-A565417F2C38 79A84398
PROGRESS CODE: V02020000 I0
Enable SCI bit at 0x404 before boot
PROGRESS CODE: V03051001 I0
Memory Previous Current Next
Type Pages Pages Pages
====== ======== ======== ========
09 00000008 00000000 00000008
0A 00000004 00000000 00000004
00 00000004 00000001 00000004
06 000000C0 00000035 000000C0
05 00000080 0000001D 00000080
Booting EFI USB Device
PROGRESS CODE: V03058000 I0
FSOpen: Open '\EFI\BOOT\BOOTX64.EFI' Success
PROGRESS CODE: V03058000 I0
FSOpen: Open '\EFI\BOOT\BOOTX64.EFI' Success
[Security] 3rd party image[0] can be loaded after EndOfDxe: PciRoot(0x0)/Pci(0x15,0x0)/USB(0x4,0x0)/\EFI\BOOT\BOOTX64.EFI.
InstallProtocolInterface: 5B1B31A1-9562-11D2-8E3F-00A0C969723B 7947C040
Loading driver at 0x000793ED000 EntryPoint=0x000793ED400
InstallProtocolInterface: BC62157E-3E33-4FEC-9920-2D3B36D750DF 79511818
ProtectUefiImageCommon - 0x7947C040
- 0x00000000793ED000 - 0x000000000008EC00
PROGRESS CODE: V03058001 I0
EmmcRead (): Part 0 Lba 0x0 BlkNo 0x40 Event 0 with Success
EmmcRead (): Part 0 Lba 0x800 BlkNo 0x40 Event 0 with Success
EmmcRead (): Part 0 Lba 0x9800 BlkNo 0x40 Event 0 with Success
EmmcRead (): Part 0 Lba 0x6EA9800 BlkNo 0x40 Event 0 with Success
EmmcRead (): Part 1 Lba 0x0 BlkNo 0x40 Event 0 with Success
EmmcRead (): Part 2 Lba 0x0 BlkNo 0x40 Event 0 with Success
XhcClearBiosOwnership: called to clear BIOS ownership
^ permalink raw reply [flat|nested] 9+ messages in thread
* Re: Enabling boot menu via serial & PXE boot in CorebootPayloadPkg
2017-12-01 10:26 ` Cameron Craig
@ 2017-12-02 3:02 ` You, Benjamin
2017-12-04 15:29 ` Cameron Craig
0 siblings, 1 reply; 9+ messages in thread
From: You, Benjamin @ 2017-12-02 3:02 UTC (permalink / raw)
To: Cameron Craig, 'edk2-devel@lists.01.org'
Hi Cameron,
> >I get serial output from edk2 with the release build and the debug build.
> >However this serial output does not include the boot menu, I just get progress
> >and error codes (and debug messages in debug mode).
> >I have attached a runtime log of a recent debug build.
From your log, I cannot see the below prompt message:
"F2 or Down to enter Boot Manager Menu.
ENTER to boot directly."
With my system, there is above message shown in serial. When I press F2
upon the message, the boot manager is shown.
The message is printed in PlatformBootManagerAfterConsole() in
CorebootPayloadPkg\Library\PlatformBootManagerLib\PlatformBootManager.c.
Not sure what went wrong, but you might add some debug message to trace the
execution flow.
Or, have you been able to boot to UEFI Shell? If yes, you may type "exit"
from the Shell prompt, and boot manager should show up.
Thanks,
- ben
^ permalink raw reply [flat|nested] 9+ messages in thread
* Re: Enabling boot menu via serial & PXE boot in CorebootPayloadPkg
2017-12-02 3:02 ` You, Benjamin
@ 2017-12-04 15:29 ` Cameron Craig
0 siblings, 0 replies; 9+ messages in thread
From: Cameron Craig @ 2017-12-04 15:29 UTC (permalink / raw)
To: 'You, Benjamin', 'edk2-devel@lists.01.org'
Hi Benjamin,
>Hi Cameron,
>
>> >I get serial output from edk2 with the release build and the debug build.
>> >However this serial output does not include the boot menu, I just get
>> >progress and error codes (and debug messages in debug mode).
>> >I have attached a runtime log of a recent debug build.
>
>From your log, I cannot see the below prompt message:
>
>"F2 or Down to enter Boot Manager Menu.
>ENTER to boot directly."
>
>With my system, there is above message shown in serial. When I press F2
>upon the message, the boot manager is shown.
>
>The message is printed in PlatformBootManagerAfterConsole() in
>CorebootPayloadPkg\Library\PlatformBootManagerLib\PlatformBootManage
>r.c.
>Not sure what went wrong, but you might add some debug message to trace
>the execution flow.
>
>Or, have you been able to boot to UEFI Shell? If yes, you may type "exit"
>from the Shell prompt, and boot manager should show up.
>
>Thanks,
>
>- ben
I managed to work out the problem.
Coreboot applies patches to the edk2 source after the git fetch, one of these changes the BdsDxe provider from MdeModulePkg to IntelFrameworkModulePkg [1].
Changing it back to MdeModulePkg fixed the issue.
[1] https://github.com/coreboot/coreboot/blob/master/payloads/external/tianocore/patches/02_CorebootPayloadPkg_bds.patch
Thanks again for your help,
Cameron
Cameron Craig | Graduate Software Engineer | Exterity Limited
tel: +44 1383 828 250 | fax: | mobile:
e: Cameron.Craig@exterity.com | w: www.exterity.com
______________________________________________________________________
This email has been scanned by the Symantec Email Security.cloud service.
For more information please visit http://www.symanteccloud.com
______________________________________________________________________
^ permalink raw reply [flat|nested] 9+ messages in thread
end of thread, other threads:[~2017-12-04 15:25 UTC | newest]
Thread overview: 9+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2017-11-24 9:15 Enabling boot menu via serial & PXE boot in CorebootPayloadPkg Cameron Craig
2017-11-25 15:25 ` You, Benjamin
2017-11-25 16:21 ` You, Benjamin
2017-11-30 14:11 ` Cameron Craig
2017-12-01 0:31 ` You, Benjamin
2017-12-01 10:23 ` Cameron Craig
2017-12-01 10:26 ` Cameron Craig
2017-12-02 3:02 ` You, Benjamin
2017-12-04 15:29 ` Cameron Craig
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox