coreboot October 2019

coreboot@coreboot.org

67 participants
59 discussions

Postcodes to IO port 80
by Jorge Fernandez Monteagudo 17 Oct '19

17 Oct '19

Hi all, Sorry for my noob question but, how can I know where the IO port 80 is physically mapped in my hardware? I have a custom board with an AMD Prairie Falcon SOC and I'm still trying to get it work. I've read the AGESA blob could post error codes to this IO port and I would like to get this info, but I don't complete understand the magic behind the postcodes and the IO port. Anybody could bring some light? Regards Jorge

4 4

GRUB2 payload build error
by Naveen Chaudhary 17 Oct '19

17 Oct '19

I am able to successfully build with SeaBIOS as payload and also able to boot it on MinnowBoard Max. But when I change the payload to GRUB2, it fails with the following build error : Copying file m4/time_h.m4 Copying file m4/unistd-safer.m4 Copying file m4/unistd_h.m4 Copying file m4/vasnprintf.m4 Copying file m4/vsnprintf.m4 Copying file m4/warn-on-use.m4 Copying file m4/wchar_h.m4 Replacing file m4/wchar_t.m4 (non-gnulib code backed up in m4/wchar_t.m4~) !! Copying file m4/wcrtomb.m4 Copying file m4/wctype_h.m4 Copying file m4/wcwidth.m4 Replacing file m4/wint_t.m4 (non-gnulib code backed up in m4/wint_t.m4~) !! Replacing file m4/xsize.m4 (non-gnulib code backed up in m4/xsize.m4~) !! Creating grub-core/lib/gnulib/Makefile.am Creating m4/gnulib-cache.m4 Creating m4/gnulib-comp.m4 Finished. You may need to add #include directives for the following .h files. #include <fnmatch.h> #include <regex.h> #include <stdio.h> #include <stdlib.h> #include "argp.h" #include "error.h" #include "gettext.h" #include "mbswidth.h" #include "progname.h" #include "save-cwd.h" You may need to use the following Makefile variables when linking. Use them in <program>_LDADD when linking a program, or in <library>_a_LDFLAGS or <library>_la_LDFLAGS when linking a library. $(LTLIBINTL) when linking with libtool, $(LIBINTL) otherwise $(LTLIBTHREAD) when linking with libtool, $(LIBTHREAD) otherwise Don't forget to - add "grub-core/lib/gnulib/Makefile" to AC_CONFIG_FILES in ./configure.ac, - mention "gnulib" in SUBDIRS in grub-core/lib/Makefile.am, - mention "-I m4" in ACLOCAL_AMFLAGS in Makefile.am, - mention "m4/gnulib-cache.m4" in EXTRA_DIST in Makefile.am, - invoke gl_EARLY in ./configure.ac, right after AC_PROG_CC, - invoke gl_INIT in ./configure.ac. patching file argp-parse.c patching file argp-fmtstream.c patching file argp-help.c patching file mbswidth.c patching file mbswidth.h patching file regcomp.c Importing unicode... Importing libgcrypt... Generating Automake input... Saving timestamps... running: AUTOPOINT=true LIBTOOLIZE=true autoreconf --verbose --install --force -I m4 --no-recursive autoreconf: Entering directory `.' autoreconf: running: true --force autoreconf: running: aclocal -I m4 --force -I m4 autoreconf: configure.ac: tracing autoreconf: configure.ac: not using Libtool autoreconf: running: /usr/bin/autoconf --include=m4 --force configure.ac:414: error: possibly undefined macro: AC_CHECK_HEADERS If this token and others are legitimate, please use m4_pattern_allow. See the Autoconf documentation. configure.ac:505: error: possibly undefined macro: AC_LINK_IFELSE configure.ac:1550: error: possibly undefined macro: AC_LANG_CALL autoreconf: /usr/bin/autoconf failed with exit status: 1 ./bootstrap: autoreconf failed Importing unicode... Importing libgcrypt... WARNING: grub-core/lib/libgcrypt-grub already exists WARNING: grub-core/lib/libgcrypt-grub/cipher already exists WARNING: grub-core/lib/libgcrypt-grub/mpi already exists WARNING: grub-core/lib/libgcrypt-grub/src already exists Generating Automake input... Saving timestamps... Running autoreconf... autoreconf: Entering directory `.' autoreconf: running: autopoint --force Copying file build-aux/config.rpath Copying file m4/extern-inline.m4 autoreconf: running: aclocal --force -I m4 autoreconf: configure.ac: tracing autoreconf: configure.ac: not using Libtool autoreconf: running: /usr/bin/autoconf --force configure.ac:414: error: possibly undefined macro: AC_CHECK_HEADERS If this token and others are legitimate, please use m4_pattern_allow. See the Autoconf documentation. configure.ac:505: error: possibly undefined macro: AC_LINK_IFELSE configure.ac:1550: error: possibly undefined macro: AC_LANG_CALL autoreconf: /usr/bin/autoconf failed with exit status: 1 Makefile:28: recipe for target 'grub2/build/config.h' failed make[1]: *** [grub2/build/config.h] Error 1 payloads/external/Makefile.inc:171: recipe for target 'grub2' failed make: *** [grub2] Error 2 Has anyone seen this error? I tried searching on google and few related but different posts suggested that it maybe related to incorrect automake files/headers being picked up, but I couldn't make it working. While I am still searching on it, has anyone seen and fixed this earlier before?

3 2

AMD AGESA maintenance and/or deprecation
by Patrick Georgi 16 Oct '19

16 Oct '19

Hi everybody, coreboot is shipping AMD's open sourced AGESA for a few generations as part of its tree. Some people advocate dropping the code due to its quality and lack of maintenance while others are happy with using the code. So: to help keep this code alive, we'd need maintainers - people willing to work through issues, improve the code quality and generally act as a point of contact if any questions arise. One item to start with could be to work through Coverity issues, where the largest proportion is now AGESA based after Jacob cleaned up most of the rest of the tree. See https://scan.coverity.com/projects/coreboot Drivers needs support to not get in the way of later development, and AGESA is sorely lacking in that department. If you see value in that code, please step up now, not only when we're looking into removing that code for good. Regards, Patrick -- Google Germany GmbH, ABC-Str. 19, 20354 Hamburg Registergericht und -nummer: Hamburg, HRB 86891, Sitz der Gesellschaft: Hamburg Geschäftsführer: Paul Manicle, Halimah DeLaine Prado

9 20

IPMI driver in romstage
by johnny_lin＠wiwynn.com 15 Oct '19

15 Oct '19

Hi everyone, In the current implementation, IPMI driver is initialized and ready for use in ramstage, but there are some scenarios that would be better to have IPMI ready earlier in romstage. For example, setting and starting a BMC watchdog timer via IPMI in romstage, or adding a SEL record right after memory is ready., etc. Appreciate your thoughts on this, please advice. Thanks.

1 0

ifdtool --layout switch in HEAD
by Simon Newton 15 Oct '19

15 Oct '19

Hi Folks, When using current HEAD, ifdtool exits with the error 'You may not specify more than one mode' when using the -f / --layout switch. to reproduce: git clone https://review.coreboot.org/coreboot.git cd coreboot/ cd util/ifdtool/ make ./ifdtool --layout me.txt ~/coreboot.rom You may not specify more than one mode. usage: ./ifdtool [-vhdix?] <filename> -d | --dump: dump intel firmware descriptor -f | --layout <filename> dump regions into a flashrom layout file -- SNIP If I run the same against a previous copy of ifdtool from coreboot 4.9, I do not get the error and the layout file is created correctly. Is this expected? I cant seem to find anything in docs or release notes that indicate a change in ifdtool behavior regarding the -f / --layout switch -- Kind Regards, Simon Newton E: Simon.newton(a)gmail.com

2 1

mailing list rejecting
by Simon Newton 15 Oct '19

15 Oct '19

Can anyone point me in the direction of who is best to talk to about the rejection of mails from my other email address? /var/log/exim_mainlog:2019-10-14 22:38:31 1iK76s-0003yR-W7 SMTP connection outbound 1571085511 1iK76s-0003yR-W7 simonnewton.com coreboot(a)coreboot.org /var/log/exim_mainlog:2019-10-14 22:38:37 1iK76s-0003yR-W7 H= mail.coreboot.org [78.46.105.101]: SMTP error from remote mail server after end of data: 451 4.7.1 Try again later /var/log/exim_mainlog:2019-10-14 22:38:37 1iK76s-0003yR-W7 == coreboot(a)coreboot.org R=dkim_lookuphost T=dkim_remote_smtp defer (-46) H= mail.coreboot.org [78.46.105.101]: SMTP error from remote mail server after end of data: 451 4.7.1 Try again later All messages seem to have bounced under error 451 : 4.7.1 which is normally some form of spam protection. I have verified my sending IP appears in no RBL so im perplexed as to why its doing this. My only guess is that another server in my hosts ASN or on my /24 has been naughty any pointers? -- Kind Regards, Simon Newton E: Simon.newton(a)gmail.com

1 0

How to configure ECC memory through FSP 1.0 (Baytrail)
by Alexey Borovikov 14 Oct '19

14 Oct '19

I have is board on Soc Baytrail processor with ECC memory. After setting the correct memory parameters through the FSP, the board started. But when I try to set the “BakerSport Platform (ECC) Type” parameter, the board stops booting with post code 2a. There are no more parameters in FSP for ECC memory. What other options can I try? What am I doing wrong?

1 0

Any DUET experts here?
by Rafael Send 14 Oct '19

14 Oct '19

Hi, Some of you might have picked up on my somewhat disjointed line of questions from the IRC, I'm putting this into an email so it's searchable better. Quick background, I'm trying to find a way to boot both UEFI and Legacy disks; turns out it's not so straightforward for someone who doesn't code at all. I'm still a bit surprised there's no way to do this out-of-the-box since most machines these days support both via CSMs, right? More specifically, I'm investigating using SeaBIOS + DUET; as this seems easier than modifying Tianocore to accept a CSM and seems to "almost" work if you squint at it. I'm starting with trying to get DUET working off of a flash drive, for which I've tried all three flavors given here <https://www.win-raid.com/t3286f50-Guide-NVMe-boot-for-systems-with-legacy-B…>. All of them will boot my desired UEFI disk on an old Thinkpad X61 (C2D!) as well as my current work machine (Lenovo P50 - i7-6820HQ). However, this USB will NOT boot the machine I actually want to use (X210 - i7-8650u). It gets as far as the memory test (supposedly successfully), but then I get a solid cursor forever, not even a shell. On the X61, it "waits" here for several minutes as well and ultimately continues booting, but on the X210 it never continues. So this tells me DUET as a concept does work, but I have no idea what is causing the freeze. Does anyone have some suggestions what I might look for / how I might debug this / different versions to try? Cheers, Rafael

1 0

OpenBMC on KGPE-D16, somebody has it working?
by Kinky Nekoboi 14 Oct '19

14 Oct '19

Due to lib depenency hell i am not able to build openbmc myself atm. Does somebody has openbmc working for there kgpe-d16 system and can maybe send me a rom ? Can i flash the module with a Programmer and testclip or only internally?

3 6

Alix2d13
by Karim El Chenawi 13 Oct '19

13 Oct '19

Hi guys, I was wondering if anyone has a working build of coreboot for PC Engines Alix2d13. I know that this board is old and retired but I still would like to have coreboot on it. There are some messages from a few years back from Reto Rayen but I’m not able to reproduce his work. Thanks, Karim

2 3

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

2003

2002

coreboot October 2019