coreboot February 2017

coreboot@coreboot.org

66 participants
212 discussions

ASUS KGPE-D16 Automated Test Failure [master]
by Raptor Engineering Automated Coreboot Test Stand 03 Feb '17

03 Feb '17

The ASUS KGPE-D16 fails verification for branch master as of commit 4a282b84192d4b8ba62521c0dc87db1872853ab0 The following tests failed: BOOT_FAILURE Commits since last successful test: 4a282b8 mainboard/google/snappy: Set PL2 override to 15000mW 84e6881 mb/lenovo/x60,t60: Move EC CMOS parameters in checksummed space 31db6f5 asus/f2a85-m_le: Activate IOMMU support 3236f7b ectool: Support OpenBSD See attached log for details This message was automatically generated from Raptor Engineering's ASUS KGPE-D16 test stand Want to test on your own equipment? Check out https://www.raptorengineering.com/content/REACTS/intro.html Raptor Engineering also offers coreboot consulting services! Please visit https://www.raptorengineering.com for more information Please contact Timothy Pearson at Raptor Engineering <tpearson(a)raptorengineering.com> regarding any issues stemming from this notification

1 0

Re: [coreboot] Back to original BIOS
by Peter Stuge 03 Feb '17

03 Feb '17

Michal Widlok wrote: > Peter: Is that really the case with old T400? I don't have experience with T400, but on older models still it was very much the case that the BIOS image had some information in it, which was compared with the actual hardware at runtime, and in case of mismatch the platform did not boot. I always assumed that it's a handshake between BIOS and the AT24RF EEPROM which includes some extra special functionality. On platforms with ME it wouldn't surprise me too much if all that moved into the ME, or even disappeared completely, but I *have* had the problem in the past. I didn't research exactly what information it is, or exactly what the handshake is, I always worked around the problem by flashing the backup. //Peter

2 1

Re: [coreboot] Back to original BIOS
by Arthur Heymans 03 Feb '17

03 Feb '17

ron minnich <rminnich(a)gmail.com> writes: > We really need to start warning people when the flash a thinkpad that > it is very important to save the old flash image. It is somewhat thinkpad specific whether the bios extracted from the update tool will work. On X60 I have had no success with it. On X200 it sort of works to flash the vendor bios extracted from update .exe. You can even just flash bios region and leave ifd, gbe (and me) alone. (Though I have had it not being able to boot and complain about some pxe stuff) Note: on x200 there exists a modified (whitelist removed) bios which does not write protect its bootblock. With this it is possible to flash the vendor bios without having to rely on an external programmer to re-flash coreboot. Backup are essential! -- Arthur Heymans

2 1

EHCI wakeup on Haswell+Lynxpoint motherboards
by Аладышев Константин 03 Feb '17

03 Feb '17

I have Haswell+LynxpointLP motherboard and Linux doesn't wakeup from USB devices from S3. EHCI controller is listed in "/proc/acpi/wakeup" as "enabled" and GPE number is seemed to be configured correctly in ACPI to PME_B0, but it doesn't work. What is need to be done to enable USB wakeup? Does USB wakeup work on Haswell+Lynxpoint motherboards?

2 1

T420i compatibility
by ilker 03 Feb '17

03 Feb '17

Is thinkpad T420i (4178CWG) compatible with Coreboot? Differences between the T420i and the T420 https://www.ifixit.com/Device/ThinkPad_T420

1 0

T420i compatibility
by ilker 03 Feb '17

03 Feb '17

Is thinkpad T420i (4178CWG) compatible with Coreboot? Differences between the T420i and the T420 https://www.ifixit.com/Device/ThinkPad_T420

1 0

Back to original BIOS
by enrico pallazzo 03 Feb '17

03 Feb '17

Hi Michael, If t400 stock bios structure is similar, you might try restoring it using this procedure: http://thinkwiki.de/UEFI_BIOS_T420_BIOS_Structure It worked for me to revert to stock bios from coreboot on a t420. As you write only bios region, you don' t need the old backup of your chip. In fact, I flashed a version of the stock bios that was different from the one I had before coreboot. Regards, Florian

1 0

Re: [coreboot] Passing CFLAGS to coreboot make (and reproducible builds)
by Trammell Hudson 03 Feb '17

03 Feb '17

On Thu, Feb 02, 2017 at 09:10:09PM +0100, Patrick Georgi via coreboot wrote: > coreboot is normally reproducible: > https://tests.reproducible-builds.org/coreboot/coreboot.html Hmm. I must have messed up someting in my earlier tests (maybe they ran without BUILD_TIMELESS=1?). You're right; the resulting firmware images do not depend on the build path, so the extra CFLAGS are not necessary. -- Trammell

2 1

Re: [coreboot] Back to original BIOS
by ron minnich 02 Feb '17

02 Feb '17

peter is not talking about CMOS. He's talking about saving data in the flash ROM that is tied to an individual motherboard. Those are very different things. Here's a simple example from older systems. They would save the ethernet MAC in flash. When you did an upgrade, you had to use the existing flash as input, else your MAC would be lost or appear as all zeros. You can imagine how tricky this can be if the exist flash rom has, e.g., GPIO settings that must be transferred to the new flash image before flashing. Hence, just a raw factory image may not work. We really need to start warning people when the flash a thinkpad that it is very important to save the old flash image. ron On Thu, Feb 2, 2017 at 11:52 AM Zoran Stojsavljevic < zoran.stojsavljevic(a)gmail.com> wrote: > > I think that will be a problem. Lenovo BIOSes save some machine-specific > > information in the flash ROM across updates, and I've so far not seen > > a single Lenovo mainboard which does not require this information for > > the vendor BIOS to work. > > Let say, you are right/correct, Peter. Then I need explanation for this > text: > > http://www.howtogeek.com/131623/how-to-clear-your-computers-cmos-to-reset-b… > > *Reseat the CMOS Battery* > > *If your motherboard does not have a CLEAR CMOS jumper, you can often > clear its CMOS settings by removing the CMOS battery and replacing it. The > CMOS battery provides power used to save the BIOS settings – this is how > your computer knows how much time has passed even when it’s been > powered-off for a while – so removing the battery will remove the source of > power and clear the settings.* > > *Important Note: Not all motherboards have removable CMOS batteries. If > the battery won’t come loose, don’t force it.* > > *First, ensure the computer is powered off and you’re grounded so you > won’t damage the motherboard with static electricity. Locate the round, > flat, silver battery on the motherboard and carefully remove it. Wait five > minutes before reseating the battery.* > > Since I am kind of *naive*, and do not understand what these people are > talking about (you are opposing them, am I correct, or maybe not)? > > > It's a kind offer, but not useful in my experience, for the above reasons. > All Lenovo BIOS updates require a Lenovo BIOS. > > Two questions/conclusions: did you ever try what I proposed here? If NOT, > it is worth trying. If YES, total valid observation. Then DEDIPROG flash > programmer or similar of kind is a must, unfortunately?! > > Zoran > > On Thu, Feb 2, 2017 at 8:53 PM, Peter Stuge <peter(a)stuge.se> wrote: > > Michal Widlok wrote: > > Ron - I've lost original bios, my mistake. > > I think that will be a problem. Lenovo BIOSes save some machine-specific > information in the flash ROM across updates, and I've so far not seen > a single Lenovo mainboard which does not require this information for > the vendor BIOS to work. > > > > On Wed, Feb 1, 2017 at 9:20 PM, Zoran Stojsavljevic < > zoran.stojsavljevic(a)gmail.com> wrote: > > > I'll try to find the original BIOS for Michael > > It's a kind offer, but not useful in my experience, for the above > reasons. All Lenovo BIOS updates I've seen so far require a Lenovo BIOS. > > > //Peter > > -- > coreboot mailing list: coreboot(a)coreboot.org > https://www.coreboot.org/mailman/listinfo/coreboot > > > -- > coreboot mailing list: coreboot(a)coreboot.org > https://www.coreboot.org/mailman/listinfo/coreboot

1 0

Re: [coreboot] Passing CFLAGS to coreboot make (and reproducible builds)
by Patrick Georgi 02 Feb '17

02 Feb '17

Am 02.02.2017 8:39 nachm. schrieb "Trammell Hudson" <hudson(a)trmm.net>: Is there a right way to pass additional compiler flags to the coreboot makefiles? Please add them as a test to util/xcompile/xcompile. We've been working on making the Heads firmware reproducible coreboot is normally reproducible: https://tests.reproducible-builds.org/coreboot/coreboot.html Patrick

1 0

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 2017