It runs an impressively large suite of checks and can help identify areas of platform insanity, such as regions of ACPI tables that are wholesale missing or otherwise don't make sense per the specs. Ideally while your laptop is under a premium support care package, you can relay this report output to the vendor and keep after them to fix things. If you do not have support or the device is older, you may have some success with back-porting sections of ACPI tables from similar platforms (e.g. the XPS and Precision lines are very similar).
In some cases the Intel ACPI Source Language (`iasl` ) compiler used in Firmware Test Suite will have false-positives/negatives if the ACPI table was initially compiled by Microsoft tooling. You'll see mention of `MSFT` in the ACPI table dump during boot (via dmesg).
Back when I managed to get OSX running on VMWare Player I recall having to edit some of the DSDT stuff to get the battery indicator to show on the desktop!
It still boggles my mind that there's a virtual machine interpreter running in kernel mode.
It runs an impressively large suite of checks and can help identify areas of platform insanity, such as regions of ACPI tables that are wholesale missing or otherwise don't make sense per the specs. Ideally while your laptop is under a premium support care package, you can relay this report output to the vendor and keep after them to fix things. If you do not have support or the device is older, you may have some success with back-porting sections of ACPI tables from similar platforms (e.g. the XPS and Precision lines are very similar).
In some cases the Intel ACPI Source Language (`iasl` ) compiler used in Firmware Test Suite will have false-positives/negatives if the ACPI table was initially compiled by Microsoft tooling. You'll see mention of `MSFT` in the ACPI table dump during boot (via dmesg).