coreboot May 2017

coreboot@coreboot.org

70 participants
202 discussions

IBB and Coreboot
by Melvin Walker 18 May '17

18 May '17

I am looking to use coreboot on a project, but I am confused about Boot Guard, FSP, Coreboot, and the IBB. Let's say I purchase a mainboard without Boot Guard enabled that supports coreboot. I build coreboot and put it in flash. I enable Boot Guard with the FIT Tool. When I boot, Boot Guard will authenticate the IBB. But, where does the IBB come from? Does it come from the FSP or is there a ".c" file in the coreboot source repository that reflects what will end up in the IBB? Melvin

1 0

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

17 May '17

The ASUS KGPE-D16 fails verification for branch master as of commit c7ccb6b29fb138b1d5f6ac6f702e9e378f71e2d7 The following tests failed: BOOT_FAILURE Commits since last successful test: c7ccb6b siemens/mc_apl1: Program eMMC DLL settings ae10ec6 siemens/mc_apl1: Select external 8250 UART 9e9cf27 soc/intel/apollolake: Enable decoding for ComA and ComB on LPC 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

Port80 isn't working (ASUS P8B75-V)
by Константин 17 May '17

17 May '17

Hello, Coreboot community! I work ASUS P8B75-V port with Nuvoton 6779d Super I/O. I have a problem: after the first call of post_code(...) function I get post-code x80 on PCI Port80 regardless which post-code I send. In debug console I see that all postcodes are correct, but only x80 is at all three PCI buses. I think that the problem may occur because the register, which saves last postcode value, isn't connected (or connected incorrectly) with PCI/Port80, but I am not sure. Could you help me with my problem, please?

1 0

Re: [coreboot] Intel me problems
by Haleigh Novak 17 May '17

17 May '17

(Just to clarify) if your asking about increasing the console log level displayed in cbmem: do 'make menuconfig' in your coreboot folder go to the 'Console' section (the following relate to the CBMEM buffer) [*] Send console output to a CBMEM buffer (0x40000) Room allocated for console output in CBMEM Default console log level (8: SPEW) ---> Just change the 'Default console log level' [though I think '8 SPEW' is supposed to show everything], you might need to increase the 'Room allocated for console output in cbmem' as well to accommodate. H From: coreboot <coreboot-bounces(a)coreboot.org> on behalf of Alejandro Flores <af49880(a)gmail.com> Sent: Tuesday, May 16, 2017 10:38 AM To: Nico Huber Cc: coreboot(a)coreboot.org Subject: Re: [coreboot] Intel me problems Thanks Nico. I do see 2 me related events. ME: Power Management Event: Clean Moff > Mx wake intel_me_path: mbp is not ready! How would I increase the log level? On May 16, 2017 9:48 AM, "Nico Huber" <nico.h(a)gmx.de> wrote: On 16.05.2017 16:22, Alejandro Flores wrote: > I have a new acer chromebook I have flashed with coreboot + seabios > payload. It boots to linux ok, but then powers off suddenly after 30 min > regardless of whether I am using it. > > I disabled hibernation and have been leaving it plugged in, but this > changes nothing. I suspect a faulty intel me since there is nothing else I > can think of. The strange thing is I did not use me cleaner but used the > full me extracted from the original bios. Later I downloaded the stock > chrombook bios for my model from google and extracted the me module from > that. > > At this point I have built several variations of roms using the me module > from the original bios, the google bios, and "cleaned" versions of both but > always with the same problem of power off after 30 min. > > I am confused as to what the problem may be. I used the intelmetool bundled > with coreboot but when I run it with the -s flag it seg faults. > > In order to extract the me rom I used ifdtool that is included with > coreboot. > ./ifdtool -x bios.bin > The intel me module is found at offset 00001000 - 001fffff and is 2 mb in > size. Is that the correct way to do it? > > Any suggestions would be appreciated. The ME state is logged in the coreboot console. You can read it with `cbmem -c` (see util/cbmem/ in the coreboot source tree). If you set the default log level high enough, you should find some lines starting with "ME:". Hope that helps, Nico

2 1

soc/amd/stoneyridge
by Marc Jones 17 May '17

17 May '17

Greetings! We want to bring to your attention the following patches, which are the start of an experiment to move AMD coreboot SOCs to the same structure as other vendor SOCs. https://review.coreboot.org/#/q/topic:soc_stoneyridge The goals of the experiments are: - to correct interfaces for each coreboot stage - to leverage common coreboot drivers (which require the common soc structure) - to correct nagging issues in current implementations (cruft, bit-rot, etc) - to provide an example for AMD silicon and mainboards moving forward We recognize that these changes may may not be compatible with the current binaryPI API (AGESA2008 a.k.a. v5), so the separation allows current AGESA and binaryPI solutions to be maintained and developed independently. Once stable, we expect that changes may be back-ported or older silicon brought up to the new soc structure. Feel free to comment on the specifics of the patches or discuss general concerns or issues in this thread. Regards, Marc -- http://marcjonesconsulting.com

1 0

Re: [coreboot] Intel me problems
by Nico Huber 16 May '17

16 May '17

On 16.05.2017 16:22, Alejandro Flores wrote: > I have a new acer chromebook I have flashed with coreboot + seabios > payload. It boots to linux ok, but then powers off suddenly after 30 min > regardless of whether I am using it. > > I disabled hibernation and have been leaving it plugged in, but this > changes nothing. I suspect a faulty intel me since there is nothing else I > can think of. The strange thing is I did not use me cleaner but used the > full me extracted from the original bios. Later I downloaded the stock > chrombook bios for my model from google and extracted the me module from > that. > > At this point I have built several variations of roms using the me module > from the original bios, the google bios, and "cleaned" versions of both but > always with the same problem of power off after 30 min. > > I am confused as to what the problem may be. I used the intelmetool bundled > with coreboot but when I run it with the -s flag it seg faults. > > In order to extract the me rom I used ifdtool that is included with > coreboot. > ./ifdtool -x bios.bin > The intel me module is found at offset 00001000 - 001fffff and is 2 mb in > size. Is that the correct way to do it? > > Any suggestions would be appreciated. The ME state is logged in the coreboot console. You can read it with `cbmem -c` (see util/cbmem/ in the coreboot source tree). If you set the default log level high enough, you should find some lines starting with "ME:". Hope that helps, Nico

2 1

Invitation european coreboot conference 2017 // Bochum // 26.-29.10.2017
by Zaolin 16 May '17

16 May '17

Hi guys, on behalf of the 9elements GmbH I would like to invite you to the coreboot conference and developer meeting on October 26-29 2017 in Bochum. This conference and developer meeting is geared towards manufacturers of hardware (processors, chipsets, mainboards and servers/ laptops/ tablets/ desktops/ appliances) as well as developers of firmware with an interest in coreboot and the possibilities it offers as well as (potential) coreboot users. Both professionals and hobbyists are invited. The conference will be four days long. The first two days (business days) will take place at the convention centre at the Ruhr-University Bochum. During the following two Barcamp days, the conference will take place at Das Labor e.V. in Bochum downtown. Workshops are designed to give a first insight into coreboot development. Further, the participants are given space for the realization of own projects (hackathon) as well as time to discuss the findings and results of the previous days. Tickets& further information: https://ecc2017.coreboot.org/ Call For Paper: 25.05.2017 - 26.08.2017 Thank you, Zaolin

1 0

Re: [coreboot] Intel me problems
by John Lewis 16 May '17

16 May '17

Well, that sounds like the right one, but could you post the model number from the underside of the device in full please? For instance, mine starts off with "CB5-571". I've also uploaded a copy of mine to https://johnlewis.ie/auron_me.bin if that helps - I used it to build a ROM yesterday (and used me_cleaner), and it works a treat as far as I can tell. On 16/05/17 16:14, Alejandro Flores wrote: > Ok sure. Its an acer c910. The image I downloaded from google is > coreboot-Google_Auron_yuna.6301.59.8.bin. > > I got it by running the crosfirmware.sh script in utils/chromos/ > included with coreboot.

1 0

Re: [coreboot] Intel me problems
by John Lewis 16 May '17

16 May '17

Well, it definitely is the ME that's the problem if it switches off after exactly 30 mins. That *should* be the correct way, yes, assuming you have the right image for the right Chromebook model (which it's possible you don't considering what's happening). With Acer Chromebook's (and sometimes other makes, HP springs to mind) there can be several different versions of the same Chromebook model, which might ostensibly look the same, but are actually running a different chipset (Broadwell vs Baytrail vs Skylake vs Braswell). I would suggest you post the exact model number and image name you downloaded so this can be verified. On 16/05/17 15:22, Alejandro Flores wrote: > I have a new acer chromebook I have flashed with coreboot + seabios > payload. It boots to linux ok, but then powers off suddenly after 30 > min regardless of whether I am using it. > > I disabled hibernation and have been leaving it plugged in, but this > changes nothing. I suspect a faulty intel me since there is nothing > else I can think of. The strange thing is I did not use me cleaner but > used the full me extracted from the original bios. Later I downloaded > the stock chrombook bios for my model from google and extracted the me > module from that. > > At this point I have built several variations of roms using the me > module from the original bios, the google bios, and "cleaned" versions > of both but always with the same problem of power off after 30 min. > > I am confused as to what the problem may be. I used the intelmetool > bundled with coreboot but when I run it with the -s flag it seg faults. > > In order to extract the me rom I used ifdtool that is included with > coreboot. > ./ifdtool -x bios.bin > The intel me module is found at offset 00001000 - 001fffff and is 2 mb > in size. Is that the correct way to do it? > > Any suggestions would be appreciated. > >

2 1

Intel me problems
by Alejandro Flores 16 May '17

16 May '17

I have a new acer chromebook I have flashed with coreboot + seabios payload. It boots to linux ok, but then powers off suddenly after 30 min regardless of whether I am using it. I disabled hibernation and have been leaving it plugged in, but this changes nothing. I suspect a faulty intel me since there is nothing else I can think of. The strange thing is I did not use me cleaner but used the full me extracted from the original bios. Later I downloaded the stock chrombook bios for my model from google and extracted the me module from that. At this point I have built several variations of roms using the me module from the original bios, the google bios, and "cleaned" versions of both but always with the same problem of power off after 30 min. I am confused as to what the problem may be. I used the intelmetool bundled with coreboot but when I run it with the -s flag it seg faults. In order to extract the me rom I used ifdtool that is included with coreboot. ./ifdtool -x bios.bin The intel me module is found at offset 00001000 - 001fffff and is 2 mb in size. Is that the correct way to do it? Any suggestions would be appreciated.

1 0

← Newer
1
...
5
6
7
8
9
10
11
...
21
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 May 2017