Bug #10
closednvramtool fails to extract CMOS layout from CBMEM
0%
Description
On all ASUS KGPE-D16 systems across every supported coreboot revision nvramtool fails to find a valid CBMEM table:
nvramtool: coreboot table not found.  coreboot does not appear to
be installed on this system.  Scanning for the table produced the
following results:
        0 valid signatures were found with bad header checksums.
        1 valid headers were found with bad table checksums.
cbmem -t has a different take on the table validity:
16 entries total:
0:1st timestamp                                     412,121
1:start of rom stage                                412,836 (715)
2:before ram initialization                         1,136,999 (724,162)
3:after ram initialization                          15,498,973 (14,361,974)
4:end of romstage                                   15,624,631 (125,657)
10:start of ramstage                                 15,700,842 (76,211)
30:device enumeration                                15,704,011 (3,168)
40:device configuration                              18,181,771 (2,477,760)
50:device enable                                     18,188,003 (6,232)
60:device initialization                             18,190,394 (2,391)
70:device setup done                                 18,883,332 (692,937)
75:cbmem post                                        18,884,387 (1,055)
80:write tables                                      18,885,443 (1,055)
90:load payload                                      18,903,332 (17,888)
15:starting LZMA decompress (ignore for x86)         18,903,988 (656)
16:finished LZMA decompress (ignore for x86)         18,935,555 (31,566)
99:selfboot jump                                     18,937,670 (2,115)
I suspect the cbmem tool handles the tables differently (more correctly?) than nvramtool, but don't really have time to track this down, considering that nvramtool -y is a functional workaround.
I can provide more debug information if needed, but there is nothing out of the ordinary in either the coreboot console or dmesg, so I would probably need to know which parts of the code to instrument before being able to provide anything useful.
Thanks!