This does make sense. Do you have a suggestion how I would go about
finding/creating a unique identifier for the system during preboot?
Cheers,
Tom
On 18/05/17 16:11, [email protected] wrote:
Not a helpful comment, but I wanted to air my feelings on the topic:
I view SMBIOS as data strictly for OS-level consumption and not for
any pre-boot code. I'm sure I'm in the minority, however.
One of the problems is that the BIOS needs to have scanned all
devices/resources and perhaps executed a connect all before the
tables can be generated (or at least completed).
Regards,
Jim
-----Original Message-----
From: edk2-devel [mailto:[email protected]] On Behalf Of Tomas
Pilar (tpilar)
Sent: Thursday, May 18, 2017 10:01 AM
To: [email protected]
Subject: [edk2] SMBios configuration table not present until late stage of boot
Hi,
I am trying to read the system UUID from the System Table (Type 1) in
the SMBios set of tables. I am doing this during DriverBinding.Start()
part of the UEFI_DRIVER initialisation. Unfortunately the
gST->ConfigurationTable only contains 6 tables and SMBios is not one of
them.
Once I boot into UEFI shell or start a PXE booting process, the
gST->ConfigurationTable now contains 8 tables and SMBios is one of the
two new tables. If I however only boot to a HDD, this never seems to
happen.
Can someone offer some insight why this might be so and how would I go
about forcing the platform to provide the SMBios in
gST->ConfigurationTable at a sensible point?
Incidentally it seems ExitBootServices is not signaled on this platform
if the boot goes through to HDD either, which is another strange thing ...
Cheers,
Tom
_______________________________________________
edk2-devel mailing list
[email protected]
https://lists.01.org/mailman/listinfo/edk2-devel
_______________________________________________
edk2-devel mailing list
[email protected]
https://lists.01.org/mailman/listinfo/edk2-devel
