Well the good news is that I have now got this board to work with Coreboot v4.6 with the CMOS options and SeaBIOS! :-)
The bad news is that this obviously means a bug has crept in on the way up to 4.8 that prevents this board from working properly whenever the CMOS options are enabled. :-(
Thanks to everyone who provided help and suggestions during this journey (especially Taiidan!), it is a relief to finally have my new system up and working.
Kind regards,
Pete
‐‐‐‐‐‐‐ Original Message ‐‐‐‐‐‐‐ On Saturday, December 8, 2018 5:52 AM, Taiidan@gmx.com Taiidan@gmx.com wrote:
On 12/07/2018 02:14 PM, petecb via coreboot wrote:
Hi Taiidan, Thanks for your message.
I am using v4.6 on my system FYI (no reason for me to update) and the only options I have changed are the ones I told you about before...all I can figure is perhaps I have a different version of the SP5100 that doesn't have the erratum or something to that effect.
Is it possible for me to build v4.6 in case something has changed since then that causes my issues? When I look at the branches available on git there is no 4.6 available.
Get it from the coreboot website + check signature.
FYI I saw you select build nvramcui as a secondary payload so you can mess with cmos options without recompiling as long as next time you shut off "Load default configuration values into CMOS on each boot" Since your menuconfig options look fine...shot in the dark but try using grub instead of SeaBIOS as I use grub.
I will try building it with Grub. There is an option to include a GRUB2 runtime config file into ROM image. Should I select this? If so, what options should be in this file?
I would set it to load your disk .cfg file otherwise you would have to do so via configfile (ahci0,msdos1)/grub2/grub.cfg or what not when it boots to the rescue shell.
Kind regards, Pete
--
coreboot mailing list: coreboot@coreboot.org https://mail.coreboot.org/mailman/listinfo/coreboot