[coreboot - Bug #611] (In Progress) I2C Controllers fail to initialize under Win11 with top-down allocation on pre-FSP 2.0 platforms
Matt DeVillier <[email protected]>
| Newsgroups | gmane.linux.bios |
|---|---|
| Message-ID | <[email protected]> |
Issue #611 has been updated by Matt DeVillier. Status changed from New to In Progress issue was coreboot's missing ACPI MMIO windows for a few platforms. patches pushed to resolve the issue: https://review.coreboot.org/c/coreboot/+/89588 https://review.coreboot.org/c/coreboot/+/89589 https://review.coreboot.org/c/coreboot/+/89590 Haswell itself was not affected as initially suspected, nor any earlier platforms. ---------------------------------------- Bug #611: I2C Controllers fail to initialize under Win11 with top-down allocation on pre-FSP 2.0 platforms https://ticket.coreboot.org/issues/611#change-2158 * Author: Matt DeVillier * Status: In Progress * Priority: Normal * Category: coreboot common code * Target version: none * Start date: 2025-10-12 * Affected versions: main ---------------------------------------- When booting Win11 using edk2 payload and top-down resource allocation (which is now the default), pre-FSP 2.0 platforms all seem to have issues with the I2C controllers failing to initialize. Windows Device Manager reports a Code 35 error: Your computer's system firmware does not include enough information to properly configure and use this device. To use this device, contact your computer manufacturer to obtain a firmware or BIOS update. Microsoft's support pages provide the following: > Full Error Message > > Your computer's system firmware does not include enough information to properly configure and use this device. To use this device, contact your computer manufacturer to obtain a firmware or BIOS update. (Code 35) > > Cause > > The Multiprocessor System (MPS) table, which stores the resource assignments for the BIOS, is missing an entry for your device and must be updated. > > Recommended Resolution > > Contact the manufacturer of your computer to update the BIOS. compiling with `RESOURCE_ALLOCATION_TOP_DOWN=n` resolves the issue Tested on: google/slippy (HSW) google/auron (BSW) google/rambi (BYT) google/cyan (BSW) -- You have received this notification because you have either subscribed to it, or are involved in it. To change your notification preferences, please click here: https://ticket.coreboot.org/my/account _______________________________________________ coreboot mailing list -- [email protected] To unsubscribe send an email to [email protected]