Re: [coreboot] ISP header for x60, fallback: indicating normal boot from grub2
On 19.07.2014 07:42, Charles Devereaux wrote:
Hello,
On Wed, Jul 9, 2014 at 2:15 AM, Denis 'GNUtoo' Carikli
gnu...@no-log.org mailto:gnu...@no-log.org wrote:
My pomona clip had issues with its contact pins(the ones in contact
with the flash chip) over time, so I unmounted it and repaired it.
I tried pushing the pins down - it looks better but it didn't help. Mine
only work with a lot of duct tape to keep it firmly pressed to the
motherboard. Otherwise, it slides up just a bit, enough to avoid making
contact. It seems more like a problem with the plastic
Example in grub.cfg:
menuentry 'Normal' {
cmosclean 0x30:0
cmosclean 0x30:1
cmosclean 0x30:2
cmosclean 0x30:3
cmosclean 0x30:4
cmosclean 0x30:5
halt
}
Interesting. Is there a reason why different values are used on gluglug
halt? cf http://samnoble.org/thinkpad/grub/gluglug.grub.custom.cfg:
The values are exactly the same. Search for hex.
There is only cbmemc, cbls and cbtime. They could be good menu options
but the output is displayed without a pager (so you can't see them as it
goes back to the menu - you have to enter a command line)
pager=1
Of all of these, cbtime would be especially interesting to add a title
to grub menu, to show if the boot was in normal or fallback and how long
it took.
I'll see if it's possible to add the result of a command to grub menu
signature.asc
Description: OpenPGP digital signature
--
coreboot mailing list: coreboot@coreboot.org
http://www.coreboot.org/mailman/listinfo/coreboot
Re: [coreboot] BayleyBay FSP booting
Tuan, Sorry - I've been on vacation and missed this thread until now. What Wang Fei suggested is exactly right - you need to start with a different BIOS flashed on the board.. The problem is the Descriptor/TXE that is being used. Intel has said that they would update the build instructions included with the FSP to highlight this issue, but I don't know if this has been done. I'm thinking I'll put in a check for this condition and print out a message stating what needs to be done. I'll try to get that added shortly. Martin On 07/17/2014 03:55 PM, WANG FEI wrote: Tuan, Your platform's northbirdge and GFX device ID is 0x0 and 0x0031? It's definitely wrong, I would suggest you to download the Bayley Bay platform's official UEFI BIOS from Intel IBL and flash it to you Bayley Bay platform, then see what's the correct ID. On Fri, Jul 11, 2014 at 4:36 AM, Patrick Georgi patr...@georgi-clan.de mailto:patr...@georgi-clan.de wrote: Am 01.07.2014 17:55, schrieb Tuan Vu: Typically, what creates the memory ranges? To a large degree the memory init code, which is closed source in the FSP model and thus unavailable to us. When it comes to memory issues with FSP, it might be better to ask Intel directly. Regards, Patrick -- coreboot mailing list: coreboot@coreboot.org mailto:coreboot@coreboot.org http://www.coreboot.org/mailman/listinfo/coreboot -- coreboot mailing list: coreboot@coreboot.org http://www.coreboot.org/mailman/listinfo/coreboot
