Issue #620 has been updated by Teej Tj.

Tj here (identified the problem commit). I've been working with hustlerone in 
#coreboot:matrix.org for a few days on this and other issues.

Rudolf: your comment in commit 97dbfd309 "TODO: Test on platforms that have 
FSRM (Ivy Bridge and newer)." cued me in as this possibly being the cause of 
the Lenovo X230 regression.

I'm currently writing a patch for hustlerone to figure out the cause that 
conditionally reverts parts of the commit. The most obvious changes are:

1. MTRR
2. splitting of cache fill/clear
3. possibly the rep stosl using ERSM in Ivy Bridge influenced by the 64-byte 
stride for the modification loop

----------------------------------------
Bug #620: X230(t) does not work since commit 
97dbfd3098ae12ef3f51e5f95cd6d66c25214205 was merged
https://ticket.coreboot.org/issues/620#change-2204

* Author: Hustler One
* Status: New
* Priority: High
* Category: coreboot common code
* Target version: main
* Start date: 2025-12-31
* Affected versions: main
* Related links: 
https://www.reddit.com/r/coreboot/comments/1pu5vlp/x230t_does_not_get_past_postcar/
https://www.reddit.com/r/coreboot/comments/1pyzcvf/no_video_output_with_updated_coreboot_x230_4132512/
* Affected hardware: x230t
----------------------------------------
Releases 25.09, 25.12 are affected. 25.06 works.

The commit 97dbfd3098ae12ef3f51e5f95cd6d66c25214205 prevents the x230t from 
going past the `postcar` stage, hence it being inoperable since it won't load 
into the main payload.

I have attempted to debug using flashconsole but the trail runs cold after 
`postcar`.


Credit to iam_tj for finding the commit.

Also, Libreboot is somehow unaffected by this. I don't know if lbmk undoes this 
commit or not at this time.



-- 
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]

Reply via email to