I'm trying to get OpenBSD to install on an x220 Thinkpad with
Coreboot/SeaBIOS but I'm running into two problems: the ethernet device
doesn't work and OpenBSD doesn't detect my HDD. dmesg said em0 wouldn't
load because the EEPROM had an invalid signature. I have no idea why
OpenBSD doesn't see my HDD though. It's strange because everything works
fine under Linux. And I cannot seem to mount a usb drive under the
OpenBSD installer to attach dmesg errors.
I originally posted this as a bug report to bug report mailing list but
Theo said it would be better suited for Coreboot's and wasn't a bug in
OpenBSD.
https://review.coreboot.org/21774
In case anyone else didn't notice - It is a sandy/ivy system with IOMMU.
This is great and should help get coreboot in to the corporate user world.
Greetings,
From what I can find, Linux can only chainload another linux kernel. (via
kexec) Does this mean that a Linux payload like LinuxBoot cannot be used to
boot Windows or another OS, either directly or by chainloading another
payload from CBFS?
It's nice that a Linux payload can provide superior flexibility and
configurability than UEFI with the added benefit of a battle-hardened
environment, but the ability to only boot a Linux OS seems like a pretty
significant limitation (if this is indeed the case).
Sincerely,
-Matt
Hi,
maybe some of you have already seen it in common Linux online media.
We are currently looking for Coreboot developers.
You should bring along:
- Knowledge of C and C++
- Already experience with the development of kernel modules
- Enjoy testing new hardware
- Experience in driver development
- Knowledge of LVFS and fwupd advantageous
- Ideally already busy with Coreboot, EFI or similar.
More about this also at:
https://www.tuxedocomputers.com/en/Infos/Jobs/Software-Developers-for-Coreb…
So if someone is interested or knows someone here, please contact us!
If you have any questions, please contact me directly!
--
Mit freundlichen Grüßen / Kind regards
Vinzenz Vietzke
Produktmanagement
--
TUXEDO Computers GmbH
Zeppelinstr. 3 ~ D-86343 Königsbrunn
--
Tel: +49 (0) 8231 / 99 19 000
Fax: +49 (0) 8231 / 99 19 009
E-Mail: vv(a)tuxedocomputers.com
--
www.TuxedoComputers.com ~ www.Linux-Onlineshop.de
--
Amtsgericht Augsburg: HRB 27755 ~ USt-IdNr.: DE815420876
Geschäftsführer: Herbert Feiler
Hi all,
I've been able to implement the 'AGESA_HOOKBEFORE_DRAM_INIT' to try to see what AGESA blob is doing and it's call 10 time before
resetting the board. Any with AGESA experience could confirm this is a normal behavior?
Anybody knows if there are any board using the IDS (Integrated Debug Services) of the AGESA? I would like to activate it to try to get more info
about what's going on...
Regards,
Jorge
________________________________
De: Jorge Fernandez Monteagudo <jorgefm(a)cirsa.com>
Enviado: martes, 25 de junio de 2019 8:42:57
Para: coreboot(a)coreboot.org
Asunto: [coreboot] Debugging AGESA black box
Hi all,
I'm trying to use coreboot on a custom board based on the stoneyridge AMD SOC. I'm
reusing the mainboard/amd/gardenia code. We have serial console and I've been able
to trace down to 'AmdInitPost(PostParams);' called from 'src/soc/amd/common/block/pi/agesawrapper.c'
to the responsible to make the board reset. Maybe we have some hardware problem related
to the DIMM area.
Then, there is some way to get some callback, trace, etc from the AGESA blackbox code? Any
chance to use the Integrated Debug Services (IDS)? Any recommendation to solve this?
Thanks!
A quick look on the mailing list doesn't show this issue for anybody
else so I have to assume something with my setup.
For past year + I have been working with coreboot in Chromium chroot
environment.
Yesterday I had to go back to the standalone build environment. This is
happening from tip of upstream master.
It is consistent with i386, arm and aarch64 toolchain. This output is
following Lesson 1 so it is from i386 with QEMU configuration.
Using git blame, all of the code (cbfstool & commonlib headers) was last
modified 2015 and 2017, so figure it is toolchain and/or my host, which
is Ubuntu 16.04.
I will add that there is an issue with chrome-ec repo access, but doubt
that is contributory to this build error, but here are the messages from
chrome-ec first:
Cloning into '3rdparty/chromeec'...
X11 forwarding request failed on channel 0
fatal: Project not found: coreboot/chrome-ec
fatal: Could not read from remote repository.
Please make sure you have the correct access rights
and the repository exists.
Clone of
'ssh://review-android.quicinc.com:29418/coreboot/chrome-ec.git' into
submodule path '3rdparty/chromeec' failed
And here is tail-end of coreboot build that fails:
CC postcar/southbridge/intel/common/reset.o
CC postcar/southbridge/intel/common/rtc.o
LINK cbfs/fallback/postcar.debug
IASL build/dsdt.aml
Intel ACPI Component Architecture
ASL+ Optimizing Compiler/Disassembler version 20190509
Copyright (c) 2000 - 2019 Intel Corporation
coreboot toolchain vc15e600 2019-05-10
ASL Input: dsdt.asl - 15113 bytes 245 keywords 399 source
lines
AML Output: dsdt.aml - 4021 bytes 99 opcodes 146 named
objects
Compilation successful. 0 Errors, 0 Warnings, 0 Remarks, 234
Optimizations
IASL build/dsdt.aml disassembled correctly.
HOSTCC cbfstool/cbfstool.o
In file included from <command-line>:0:0:
/local/mnt/workspace/mturney/gitrepos/qualcomm/chromebook/cbdc-meta/standalone/coreboot/util/cbfstool/cbfstool.c:
In function 'cbfs_add_component':
/local/mnt/workspace/mturney/gitrepos/qualcomm/chromebook/cbdc-meta/standalone/coreboot/src/commonlib/include/commonlib/compiler.h:59:2:
error: first argument to '__builtin_choose_expr' not a constant
__builtin_choose_expr(__builtin_constant_p(expr), fallback_expr,
expr))
^
/local/mnt/workspace/mturney/gitrepos/qualcomm/chromebook/cbdc-meta/standalone/coreboot/src/commonlib/include/commonlib/helpers.h:39:2:
note: in expansion of macro '__TYPEOF_UNLESS_CONST'
__TYPEOF_UNLESS_CONST(a, b) var_a = (a); \
^
/local/mnt/workspace/mturney/gitrepos/qualcomm/chromebook/cbdc-meta/standalone/coreboot/src/commonlib/include/commonlib/helpers.h:49:26:
note: in expansion of macro '__CMP_SAFE'
__CMP_UNSAFE(a, b, op), __CMP_SAFE(a, b, op, __TMPNAME, __TMPNAME))
^
/local/mnt/workspace/mturney/gitrepos/qualcomm/chromebook/cbdc-meta/standalone/coreboot/src/commonlib/include/commonlib/helpers.h:56:19:
note: in expansion of macro '__CMP'
#define MAX(a, b) __CMP(a, b, >)
^
/local/mnt/workspace/mturney/gitrepos/qualcomm/chromebook/cbdc-meta/standalone/coreboot/util/cbfstool/cbfstool.c:546:19:
note: in expansion of macro 'MAX'
uint32_t size = MAX(hs, param.padding);
^
/local/mnt/workspace/mturney/gitrepos/qualcomm/chromebook/cbdc-meta/standalone/coreboot/src/commonlib/include/commonlib/compiler.h:59:2:
error: first argument to '__builtin_choose_expr' not a constant
__builtin_choose_expr(__builtin_constant_p(expr), fallback_expr,
expr))
^
/local/mnt/workspace/mturney/gitrepos/qualcomm/chromebook/cbdc-meta/standalone/coreboot/src/commonlib/include/commonlib/helpers.h:40:2:
note: in expansion of macro '__TYPEOF_UNLESS_CONST'
__TYPEOF_UNLESS_CONST(b, a) var_b = (b); \
^
/local/mnt/workspace/mturney/gitrepos/qualcomm/chromebook/cbdc-meta/standalone/coreboot/src/commonlib/include/commonlib/helpers.h:49:26:
note: in expansion of macro '__CMP_SAFE'
__CMP_UNSAFE(a, b, op), __CMP_SAFE(a, b, op, __TMPNAME, __TMPNAME))
^
/local/mnt/workspace/mturney/gitrepos/qualcomm/chromebook/cbdc-meta/standalone/coreboot/src/commonlib/include/commonlib/helpers.h:56:19:
note: in expansion of macro '__CMP'
#define MAX(a, b) __CMP(a, b, >)
^
/local/mnt/workspace/mturney/gitrepos/qualcomm/chromebook/cbdc-meta/standalone/coreboot/util/cbfstool/cbfstool.c:546:19:
note: in expansion of macro 'MAX'
uint32_t size = MAX(hs, param.padding);
^
In file included from
/local/mnt/workspace/mturney/gitrepos/qualcomm/chromebook/cbdc-meta/standalone/coreboot/util/cbfstool/common.h:25:0,
from
/local/mnt/workspace/mturney/gitrepos/qualcomm/chromebook/cbdc-meta/standalone/coreboot/util/cbfstool/cbfstool.c:26:
/local/mnt/workspace/mturney/gitrepos/qualcomm/chromebook/cbdc-meta/standalone/coreboot/src/commonlib/include/commonlib/helpers.h:47:25:
error: first argument to '__builtin_choose_expr' not a constant
#define __CMP(a, b, op) __builtin_choose_expr( \
^
/local/mnt/workspace/mturney/gitrepos/qualcomm/chromebook/cbdc-meta/standalone/coreboot/src/commonlib/include/commonlib/helpers.h:56:19:
note: in expansion of macro '__CMP'
#define MAX(a, b) __CMP(a, b, >)
^
/local/mnt/workspace/mturney/gitrepos/qualcomm/chromebook/cbdc-meta/standalone/coreboot/util/cbfstool/cbfstool.c:546:19:
note: in expansion of macro 'MAX'
uint32_t size = MAX(hs, param.padding);
^
In file included from <command-line>:0:0:
/local/mnt/workspace/mturney/gitrepos/qualcomm/chromebook/cbdc-meta/standalone/coreboot/util/cbfstool/cbfstool.c:
In function 'cbfs_create':
/local/mnt/workspace/mturney/gitrepos/qualcomm/chromebook/cbdc-meta/standalone/coreboot/src/commonlib/include/commonlib/compiler.h:59:2:
error: first argument to '__builtin_choose_expr' not a constant
__builtin_choose_expr(__builtin_constant_p(expr), fallback_expr,
expr))
^
/local/mnt/workspace/mturney/gitrepos/qualcomm/chromebook/cbdc-meta/standalone/coreboot/src/commonlib/include/commonlib/helpers.h:39:2:
note: in expansion of macro '__TYPEOF_UNLESS_CONST'
__TYPEOF_UNLESS_CONST(a, b) var_a = (a); \
^
/local/mnt/workspace/mturney/gitrepos/qualcomm/chromebook/cbdc-meta/standalone/coreboot/src/commonlib/include/commonlib/helpers.h:49:26:
note: in expansion of macro '__CMP_SAFE'
__CMP_UNSAFE(a, b, op), __CMP_SAFE(a, b, op, __TMPNAME, __TMPNAME))
^
/local/mnt/workspace/mturney/gitrepos/qualcomm/chromebook/cbdc-meta/standalone/coreboot/src/commonlib/include/commonlib/helpers.h:56:19:
note: in expansion of macro '__CMP'
#define MAX(a, b) __CMP(a, b, >)
^
/local/mnt/workspace/mturney/gitrepos/qualcomm/chromebook/cbdc-meta/standalone/coreboot/util/cbfstool/cbfstool.c:957:6:
note: in expansion of macro 'MAX'
MAX(bootblock.size, sizeof(int32_t));
^
In file included from
/local/mnt/workspace/mturney/gitrepos/qualcomm/chromebook/cbdc-meta/standalone/coreboot/util/cbfstool/common.h:25:0,
from
/local/mnt/workspace/mturney/gitrepos/qualcomm/chromebook/cbdc-meta/standalone/coreboot/util/cbfstool/cbfstool.c:26:
/local/mnt/workspace/mturney/gitrepos/qualcomm/chromebook/cbdc-meta/standalone/coreboot/src/commonlib/include/commonlib/helpers.h:47:25:
error: first argument to '__builtin_choose_expr' not a constant
#define __CMP(a, b, op) __builtin_choose_expr( \
^
/local/mnt/workspace/mturney/gitrepos/qualcomm/chromebook/cbdc-meta/standalone/coreboot/src/commonlib/include/commonlib/helpers.h:56:19:
note: in expansion of macro '__CMP'
#define MAX(a, b) __CMP(a, b, >)
^
/local/mnt/workspace/mturney/gitrepos/qualcomm/chromebook/cbdc-meta/standalone/coreboot/util/cbfstool/cbfstool.c:957:6:
note: in expansion of macro 'MAX'
MAX(bootblock.size, sizeof(int32_t));
^
make: *** [build/util/cbfstool/cbfstool.o] Error 1
mturney@mturney-linux:/local/mnt/workspace/mturney/gitrepos/qualcomm/chromebook/cbdc-meta/standalone/coreboot$
Hey everybody,
in today's leadership meeting, the question was brought up if we want
to normalize the coding style in coreboot to _always_ use braces in
if, else and for statements, even if it's just one statement they're
wrapping.
The arguments made in favor were:
1. it's more consistent
2. it's safer: you won't accidentally add a statement that is outside
the context it's supposed to run in (or even move a statement out
into the parent context by inserting another statement)
So instead of:
if (foo)
bar();
else {
baz();
quux();
}
we'd do:
if (foo) {
bar();
} else {
baz();
quux();
}
The attendees were generally in favor, but wanted to ask the wider
community. The idea of putting it up for a vote was brought up, but
we decided to discuss it first (and vote if there's disagreement,
after the arguments were exchanged. makes for clearer arguments for
all positions on the ballot, too)
Patrick
