Issue #611 has been updated by Matt DeVillier.
Walter Sonius wrote in #note-3: > Related patch: [CB:89464](https://review.coreboot.org/c/coreboot/+/89464) > device/Kconfig: Disable top-down resource allocation for pre-FSP 2.0 > > Is using the option `CONFIG_EDK2_CBMEM_LOGGING` the correct way to log EDK2 > and is there a way to increase the CBMEM size or should I decrease coreboot > its own logging from SPEW to EMERGENCY to keep more space available for EDK2 > log? I would use: ``` CONFIG_EDK2_CBMEM_LOGGING=y CONFIG_CONSOLE_CBMEM_BUFFER_SIZE=0x80000 ``` reducing coreboot's logging level will not free up a meaningful amount of space. edk2 uses 10x what coreboot does, the cbmem allocation must be increased. ---------------------------------------- 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-2154 * Author: Matt DeVillier * Status: New * 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]
