coreboot

Also, FWIW, On a Very Similiar Mainboard - Gigabyte GA-G41M-ES2L ( w/ The Same Chipset (Intel G41 + ICH7) ), Coreboot F/W ( Coreboot 4.10-455-g44449192ab from 27/08/2019 ), Does Enable a Windows 10 x64 1909 OS To Boot.

Please try to transcribe the full error next time – I removed some zeros from the parameters.

0xD, 0xFFFFFA8004753360, 0x000000003353505F,0x0

Here is the error description.

(0x0000000D, Parameter2, Parameter3, Parameter4):

There are many objects that must be defined in the ACPI namespace, and one or more of these was not found. This error generally occurs if either the _HID or _ADR object is missing. An _ADR is used to define the address of a device on its parent bus. The _ADR is a static address that defines slot numbers for devices that reside on any number of bus types, including EISA, floppy, IDE controller, IDE channel, PCI, PCMCIA, and CardBus. The _HID contains objects that supply the operating system with Plug and Play hardware ID for a device. Technically, these objects are optional, but they absolutely must be present to describe any device that is enumerated by an ACPI driver.

Please do the following:

1. Please attach defconfig created by make savedefconfig.
2. Please attach the coreboot logs, for example retrieved by cbmem -1 or from the serial console.
3. Please start GNU/Linux (some latest version), and attach the Linux kernel console.
4. In GNU/Linux, please install FWTS (https://wiki.ubuntu.com/FirmwareTestSuite), and run it, and look out for errors.

PS: Unrelated, it’d be nice if you uploaded the Linux logs to the board status repository. See util/board_status/README.

Parameter3 0x3353505F is ASCII and translates to "_PS3". That's a power-state function which seems to be missing for the Super-I/O chip (which is one of the major differences between these boards).

Please try this patch, maybe we are lucky:
https://review.coreboot.org/c/coreboot/+/39746

I was too tired last night to grep properly, there were many more occurences of the same problem. I've updated the patch, hopefully caught all cases now.

Patch Rev. # 3 Tested & Working - Both on OS Setup & an Installed OS ! You're Like Magicians: a Major Thank You ! :)

Great that Nico was able to come up with a fix so quickly.

In the board status archive, I saw, that you select the unneeded DRIVERS_PS2_KEYBOARD=y in coreboot. GRUB, SeaBIOS and TianoCore have their own drivers for that, so you do not need that.

Additionally, the archive misses the logs from coreboot and Linux. If the fix is in the master branch, it’d be great if you could do another run of board_status.sh.