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.
A pair of 1866MHz CL9 RAM modules* runs only as 1333MHz CL9 on 16h
AM1I-A with coreboot is installed, but worked faster when a
proprietary UEFI was installed. To fix this "turtle RAM" coreboot
problem I tried to play with buildOpts.c -
https://review.coreboot.org/c/coreboot/+/33920 , but the things like
"#define BLDCFG_MEMORY_CLOCK_SELECT DDR1866_FREQUENCY" sadly did not
help.
Any ideas how to improve the RAM speeds? How I can force this RAM to run faster?
Best regards,
Mike Banon
[*] Crucial Ballistix Tactical Series DDR3 1866MHz CL9 (PC3-14900
9-9-9-24) UDIMM 240-Pin modules, part number BLT8G3D1869DT1TX0
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
It's patch cleanup time again. This cleanup was last done almost 2
years ago, so there are a lot of old patches that haven't been touched
in a while.
Next week I'm going to abandon all of the open patches that haven't
been touched in over 18 months.
The list of roughly 250 patches to be abandoned is here:
https://review.coreboot.org/q/status:open+before:2018-02-1+project:coreboot
If anyone wants to take over any of these patches, just mention it in
the patch and if the author doesn't respond in a day or two, feel free
to let them know that you've adopted the patch.
As always, if there's anything that is still useful and shouldn't be
abandoned, a comment in the patch is enough to keep it alive in
gerrit.
Martin
Hi everybody,
you might notice a new column in the Gerrit UI: ACR for All-Comments-Resolved.
For a while, Gerrit allows to "resolve" comments made to changes, and this
field automatically determines if all comments are marked that way.
Another change to our Gerrit install is that changes can only be submitted
when there are no more open comments.
For this reason, please ensure to close comments you consider done.
Thanks,
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