Hi,
I saw very similar symptoms myself while porting coreboot to the ASUS AM1I-A board.
I'm not sure about the reasons but this is likely caused by corrupted NVRAM data. Make sure your board has a valid cmos.layout and a cmos.default file (the latter one is optional) then build a fresh copy of coreboot and flash it. Power off, remove the power cord and clear the CMOS memory using a jumper on the mainboard. This ensures coreboot rewrites the CMOS memory with defaults on next boot.
I did the same and it helped, the issue disappeared and never came back later.
Hope it helps you, too!
Regards, Gergely
On 24 January 2018 at 16:35, Аладышев Константин aladyshev@nicevt.ru wrote:
Hello!
I'm trying to include CMOS variables use to my Coreboot, but when I enable "CONFIG_USE_OPTION_TABLE" option strange things happen.
Windows stucks at boot logo and coreinfo payload displays very strange NVRAM RTC data (completely incorrect time with year and second that increment every second).
I checked this with upstream code on Google/Panther motherboard. This motherboard uses "mc146818rtc" driver for RTC.
Without "CONFIG_USE_OPTION_TABLE" option coreinfo displays time correctly. What can be the source of such thing?
Best Regards, Aladyshev Konstantin
-- coreboot mailing list: coreboot@coreboot.org https://mail.coreboot.org/mailman/listinfo/coreboot