coreboot February 2014

coreboot@coreboot.org

52 participants
148 discussions

Re: [coreboot] Unable to start correctly coreboot on Asus f2a85-m REV 1.02
by David Hubbard 06 Feb '14

06 Feb '14

On Thu, Feb 6, 2014 at 12:28 AM, HacKurx <hackurx(a)gmail.com> wrote: > > OK. Please can you enable AGESA debug stuff. It should produce more > > output. > > > > You can do that by uncommenting #define IDSOPT_IDS_ENABLED in mainboard > > directory OptionsIds.h file. > > > > We dont have a menuconfig for that yet. > > I made it. There is in my file: > grep "#define IDSOPT_IDS_ENABLED" > coreboot/src/mainboard/asus/f2a85-m/OptionsIds.h > #define IDSOPT_IDS_ENABLED TRUE > > I get exactly the same result with this option... > > I also tested the following options without success. : > CONFIG_DEBUG_CBFS > CONFIG_DEBUG_MALLOC > CONFIG_DEBUG_ACPI > CONFIG_DEBUG_SPI_FLASH > > What can I do now? Thanks. > > Please double check IDSOPT_IDS_ENABLED. I have first-hand experience with Rudolf's suggestion to use that #define, I have an F2A85-M as well. With IDSOPT_IDS_ENABLED, the serial output is significantly longer. I suspect the build system does not catch the change since it's not in menuconfig. Perhaps try 'make clean' followed by all the normal build steps? David

1 0

Re: [coreboot] UNTIN casting errors
by Patrick Georgi 06 Feb '14

06 Feb '14

Am Donnerstag, den 06.02.2014, 12:49 +0530 schrieb Anthony Ross: > errors on X64 architectures. But some like the casting errors > contained in the PlatformPie/Memdect.c have not been fixed yet. Part of the issue is that these errors vary between GCC versions. The code is tested with their mingw based toolchain and with GCC47. I think you used GCC45, which naturally shows different behaviour. > I hope so someone on this mailing list would pay heed and do the > needful. I had mailed the author directly concerning the changes but > nothing has been reflected. As Peter noted, "patches accepted". Patrick

1 0

Re: [coreboot] UNTIN casting errors
by Peter Stuge 06 Feb '14

06 Feb '14

Anthony Ross wrote: > I had mailed the author directly concerning the changes but nothing has > been reflected. I think you may have better success if you mail patches which fix the issue. //Peter

1 0

UNTIN casting errors
by Anthony Ross 06 Feb '14

06 Feb '14

Hello all Well the corebootPkg has been one of the best to be incorporated in the edk2 source code. For those who contain large EEPROMs would actually be lucky to try it out on real hardware. Well coming to the point the corebootpkg had some fixes done last time like the toolchain errors on X64 architectures. But some like the casting errors contained in the PlatformPie/Memdect.c have not been fixed yet. Suggestions were last time given of UNTIN cast prior to casting to a pointer but the edk2 corebootpkg gitrepo contains no changes pushed. I hope so someone on this mailing list would pay heed and do the needful. I had mailed the author directly concerning the changes but nothing has been reflected. Neo

1 0

Re: [coreboot] Motherboard Not on Support MB List -> Specs
by Peter Stuge 05 Feb '14

05 Feb '14

ron minnich wrote: > So I'm continuing my discussion with intel, they are being quite > responsive. Peter, thanks for pushing on this, we need the answer! I'm looking forward to the outcome of the discussion! //Peter

1 0

Re: [coreboot] Motherboard Not on Support MB List -> Specs
by Peter Stuge 05 Feb '14

05 Feb '14

ron minnich wrote: > On Wed, Feb 5, 2014 at 7:53 AM, Peter Stuge <peter(a)stuge.se> wrote: > > I read a little about the quark soc and it seems to have some pretty > > tight signature checks on firmware. I got the impression that it was > > unpossible to use any other firmware than the UEFI it comes with. > > Word from Intel: "hook up a dediprog and reprogram." https://communities.intel.com/servlet/JiveServlet/downloadBody/21828-102-2-… https://communities.intel.com/docs/DOC-21828 The top of page 38 (1.2 Component Overview) reads: "To enable secure applications, the SoC features an on-die Boot ROM that is used to establish a hardware Root of Trust (RoT). The immutable code located within the Boot ROM is used to initiate an iterative firmware authentication process ensuring only trusted code is executed when taking the platform out of reset." > Sounds like a documentation clarification is needed on release notes." Sounds like it.. //Peter

3 2

Re: [coreboot] Acer c720p: seabios is gone after enabling write protection
by Yannick 05 Feb '14

05 Feb '14

Le mercredi 05 février 2014 à 12:41 -0600, Aaron Durbin a écrit : > On Wed, Feb 5, 2014 at 12:08 PM, Yannick <sevmek(a)free.fr> wrote: > > Le mercredi 05 février 2014 à 09:36 -0600, Aaron Durbin a écrit : > >> On Wed, Feb 5, 2014 at 3:04 AM, Yannick <sevmek(a)free.fr> wrote: > >> > Hi, > >> > > >> > I'm the one who tried to help Carmelo. Unfortunately, after I opened > >> > this machine (Acer c720p, french keyboard) and removed the screw to > >> > enable writing on coreboot, it now refuses to access to seabios if I > >> > press CTRL + L has I did before so many times. It just emits a sound "bip" when doing so. > >> > I've put the screw back in, it's still the same. > >> > > >> > Thus the fedora 20 I installed is now out of reach. > >> > > >> > If I wait ~30 seconds, I've a second white screen proposing to reinstall > >> > ChromeOS using USB or SD. I hope I someone here can save me the trouble > >> > of reinstalling ChromeOS, then wipe it again, then reinstall Fedora 20 > >> > and reconfigure it... > >> > > >> > Process I'm trying to get it working back: > >> > 1- using a distro (ubuntu 12.04 in my case) prepare an USB stick with chromeos recovery using this script : > >> > https://support.google.com/chromebook/answer/1080595 > >> > -> https://dl.google.com/dl/edgedl/chromeos/recovery/linux_recovery.sh > >> > 2- turn on os verification in coreboot > >> > 3- reboot and at the warning screen telling you chromeos is missing insert the USB stick. > >> > 4- I've a "unexpected error" during recovery process. :/ > >> > > >> > I'm stuck... > >> > > >> > > >> > >> You need access to the chromeos-firmwareupdate script and flashrom as > >> documented here: > >> > >> http://www.coreboot.org/pipermail/coreboot/2014-February/077158.html > >> > >> You could ask your friend to copy chromeos-firmwareupdate as well as > >> flashrom to your machine. The script is self hosting and flashrom is > >> statically linked: > >> > >> # ldd /usr/sbin/flashrom > >> not a dynamic executable > > > > The current issue is I only have access to the white screen from > > coreboot, there is no seabios available. > > > > Thus I'm trying to reinstall Chrome OS. > > > > I find out there is a log on the USB flash drive I'm using for the > > Chrome OS recovery which might explain the failure and maybe solve my > > issue at the same time. > > > > In recovery.log, before running some diagnostics at the end of the file, > > there is this error: > > > > "Touch(/mnt/stateful_partition/.install_completed) FAILED > > Starting firmware updater > > (/tmp/install-mount-point/usr/sbin/chromeos-firmwareupdate > > --mode=recovery) > > Command: /tmp/install-mount-point/usr/sbin/chromeos-firmwareupdate > > --mode=recovery > > Starting Peppy firmware updater v4 (recovery)... > > - Updater package: [Google_Peppy.4389.81.0 / peppy_v1.5.114-5d52788] > > - Current system: [RO:Google_Peppy.4389.78.0 , > > ACT:Google_Peppy.4389.78.0 / peppy_v1.5.113-2d79820] > > - Write protection: Hardware: ON, Software: Main=off EC=ON > > Upgrading from early-MP firmware. > > > > RW firmware update is not compatible with current RO firmware. > > Starting full update... > > > > ERROR: You need to first disable hardware write protection. > > ERROR: Execution failed: ./updater4.sh (error code = 4) > > Finished after 2 seconds. > > Failed > > Command: /tmp/install-mount-point/usr/sbin/chromeos-firmwareupdate > > --mode=recovery - Exit Code 4 > > RO Firmware needs update, but is really marked RO. (error code: 4) > > Rolling back update due to failure installing required firmware. > > Successfully updated GPT with all settings to rollback. > > PostInstall Failed" > > > > Do you guys think the recovery fails because I do have the screw > > protecting coreboot in? > > Yes. Can't you just get the two files from your friend. You wouldn't > need to recover ChromeOS. > > > Should I remove this screw and try again? > > You can. It will re-write the entire SPI. I'd go with the above first. Removing the screw allowed the recovery process to fully completed. Chrome OS is now reinstalled. Thank you for your help. > > -Aaron

1 0

Re: [coreboot] Motherboard Not on Support MB List -> Specs
by mrnuke 05 Feb '14

05 Feb '14

On Tuesday, February 04, 2014 09:16:31 PM ron minnich wrote: > you can shoot for a board with an FSP-supported chipset, or you could Please avoid FSP like the plague. Programatically, it will be the worst pain you will have ever dealt with. > do the Quark, which would be truly wonderful to have. > Quark comes with firmware source code IIRC. Shouldn't be hard to integrate that under vendorcode/ and do a proper coreboot port. Alex

3 4

Re: [coreboot] Researching the SMM mode
by Patrick Georgi 05 Feb '14

05 Feb '14

Am Mittwoch, den 05.02.2014, 11:44 -0700 schrieb David Hubbard: > It is a no-frills approach to what the SMI handler must do, Yes. We don't do crazy stuff like writing to flash from SMM. > and does not include any extras (D_LOCK and D_OPEN are extras). No. Locking down SMM would provide a trivial way to undermine system integrity. Look for D_LCK in src/southbridge/intel (various southbridges) to see what we do in that regard. I think the handling on AMD and Via is similar. > Linux probably doesn't interact with the SMI handler at all. We don't just support Linux, but also real operating systems. Patrick

1 0

Re: [coreboot] Acer c720p: seabios is gone after enabling write protection
by Aaron Durbin 05 Feb '14

05 Feb '14

On Wed, Feb 5, 2014 at 12:51 PM, Yannick <sevmek(a)free.fr> wrote: > Le mercredi 05 février 2014 à 12:41 -0600, Aaron Durbin a écrit : >> > Do you guys think the recovery fails because I do have the screw >> > protecting coreboot in? >> >> Yes. Can't you just get the two files from your friend. You wouldn't >> need to recover ChromeOS. > > There is something I do not understand here: I can't run any software on > the machine except chrome OS recovery, which fails. How am I supposed to > run this script? Duh. My apologies. Try removing the WP screw and recover. -Aaron

1 0

← Newer
1
...
9
10
11
12
13
14
15
Older →

Jump to page:

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

2003

2002

coreboot February 2014