Dear Ladies and Gentlemen,
We invite you to the Open Source Firmware Conference 2018
( www.osfc.io ) which takes place
at the 12th - 15th September in Erlangen, Germany.
The OSFC 2018 is the first conference focusing exclusively on Open
Therefore, our mission is to provide an appropriate platform to bring
together as many Open Source projects,
hardware manufacturers and developers as possible.
In order to collaborate, share knowledge and push the Open Source
Get in touch with community of coreboot, LinuxBoot, Tianocore, u-boot
and be part of our amazing firmware conference!
Tickets are available: https://osfc.io/tickets
CFP is available: https://easychair.org/cfp/osfc2018
Follow us on Twitter: osfc_io
Best Regards, Philipp
I am trying to make a series of scripts with configs to help simplify
the Coreboot build process for the Lenovo X230, and soon the X220, using
the Coreboot-sdk Docker image. The one issue I am having is creating
consistent builds. This was confusing after heading the news that
Coreboot was reproducible and finding that the x230 was one of the many
models confirmed here:
doing some digging through the Coreboot git repo and searching gerrit, I
found the config used,
does not include payloads and that the IFD, ME and GBE binaries were
sourced from "./site-local/" but I cannot find these files in any public
repo. If these are not available, then the generated hashes cannot be
confirmed outside of the reproducible-builds Jenkins environments.
My question ultimately comes down to how much of Coreboot is
reproducible and can a complete binary with payloads be built
consistently given the same build enviroment? The more specific
question is, if the downloading the Coreboot 4.8.1 release using this
why would the SHA256 hashes never match and, at times, cbfstool
partition sizes vary?
maybe this is not really coreboot-related, but I am experiencing an issue with the KGPE-D16 that there seems to be no working constellation how the following three cards can be put into service:
- nvidia GPU (PCIe 3 x16, takes 1 slot but occupies two)
- ASUS hypercard (PCIe 3 x16, takes 1 slot, has four M.2 slot with PCIe x4 each), see 
- USB3 controller card (PCIe x4, takes 1 slot)
No matter what I try, the hypercard is unable to detect more than two M.2 ssds. And only in the following config:
1 (MIO): empty
When I put the USB3 card in 5, only one of the M.2 ssds on the hypercard is recognized. Therefore, I also tried swapping stuff in many combinations such as the following:
But no matter what I do, there seems to be now way to get all three cards working simulaneously. Even with JUST the hypercard and nothing else it will only detect two of the three M.2 cards inserted. :/
Seems like the vendor bios has the same issue. My plan now is to get a GPU that occupies only 1 slot and put the USB3 card next to it.
Any help and clarifying explanations on this topic are warmly welcome.
I also have a coreboot KGPE-D16 but am using different accessory cards. I
took a look at the specs on your Hyper card and compared it to KGPE specs
and I think one or more of the following might be the issue:
* It looks like the Hyper card is a PCIE 3.0 device and the KGPE-D16 has
PCIE 2.0 slots.
* The Hyper card uses Intel VROC technology and I don't see that AMD cpus
have an equivalent/compatible technology.