UEFI Payload from EDK2 2017 seems to be pretty old.
toggle quoted messageShow quoted text
Below are some of my recommendations:
- Enable serial debug console in UEFI payload so that you don't depend on USB KB for input. Once you booted to Shell using serial console, further info can be collected to root cause USB issue.
- If you saw the hang at "[Bds]BdsWait(3)..Zzzz...", it could be timer related issue. I saw some instances where the ACPI timer base was reported incorrectly to UEFI payload and ACPI timer base was wrong. That would cause the dead loop in delay function.
- Try out the latest UefiPayload in EDK2 to see if it works for you.
From: Laszlo Ersek <email@example.com>
Sent: Thursday, February 4, 2021 1:58
To: firstname.lastname@example.org; email@example.com
Cc: Ma, Maurice <firstname.lastname@example.org>; Dong, Guo
<email@example.com>; You, Benjamin <firstname.lastname@example.org>
Subject: Re: [edk2-discuss] UEFI Payload Issue
On 02/02/21 13:16, email@example.com wrote:
got struck after the below message. The keyboard is not detecting so i can't
I have generated a payload from edk2 2017. When i booting with payload i
press any key. Mouse got powered up. Even i exchanged the usb ports but
still keyboard not detecting. I am using coreboot and edk2 payload. I am
using Coffeelake processor. If i use the uefi payload binary from Intel.
Everything is working and able to select device in the boot manager and load
LastBlock : 4FFFFF
F2 or Down to enter Boot Manager Menu.
ENTER to boot directly.
[Bds]=============Begin Load Options Dumping ...=============
Boot0000: UiApp 0x0109
Boot0001: UEFI SM659GXC CDZ A0519022617060000001 0x0001
Boot0002: UEFI Shell 0x0001
PlatformRecovery0000: Default PlatformRecovery 0x0001
[Bds]=============End Load Options Dumping=============
...Zzzzzzzzzzzz...Adding the UefiPayloadPkg folks to the CC list.