I'm looking for an option to configure my Intel IvyBridge CPU (enable /
disable Hyperthreading, TurboBoost, set configurable TDP level etc.)
using coreboot / nvramcui. My board is a Lenovo Thinkpad T430. So far,
"only virtualization" is configurable and can not be enabled / disabled
"in flight" but requires a rebuild of coreboot.
Is anyone currently working on something similar?
Is anything planned in that regard?
Dear coreboot folks,
On the Lenovo T60 (with AMD/ATI graphics) the Linux kernel (4.9, 4.19,
5.3, 5.4) hangs after starting user space. As SeaBIOS, GRUB, payloads
and FreeDOS work, I tried to limit the number of CPUs, and booting Linux
with `nosmp` gave me a booting system. It worked with older coreboot
versions, so I think it’s a regression. I am able to reproduce this with
coreboot 4.11 and 4.11-422-g1a5c3bb7fa.
Is somebody else seeing this issue? Maybe on some i945 desktop board, so
it would be easier to bisect?
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
I own an Acer Aspire VN7-572G and have not been impressed with its OEM
firmware. After discovering that it does not utilise Intel's Boot Guard
technology, that several Skylake and Kabylake laptops (it has a Skylake
chip, but I read that the platforms are similar) have received successful
coreboot ports and reading the porting guide on the wiki, I figured that I
could give porting coreboot to my laptop a shot.
When I was done, I figured that I had an image that might boot so I flashed
it to my laptop with a Raspberry Pi and a SOIC clip. However, here's what
a) It powers on quietly, as expected;
b) The backlight and power LED light up;
c) The fans spin up to high and then it stays that way. It does nothing
else. The display is dark too.
After 15 minutes and a second attempt, I figured that I could no longer
blame anything on a long first boot-up and gave up and flashed back to
Now, in all honesty I should have tried first without cleaning Intel ME but
I find it so much more likely that I did something wrong than that cleaning
ME was the sole problem.
Can anyone advise me on how to continue? My code is here:
I know a couple folks here are active on Thinkpads.com / familiar with the
X210 port by Matthew.
The stock BIOS doesn't appear to support non-NVME devices in the M.2 slot;
I'm attempting to get a Sunix UPD2018 card working to add USB-C.
With stock BIOS, the card works just fine in the WiFi slot, and an NVME
drive works just fine in the M.2 slot so nothing appears physically broken.
However, so far nothing I've done lets me detect the Sunix card if I try to
put it in the NVME slot using this adapter
<https://www.adt.link/product/R42.html>. I would think it should just show
up under "lspci" like it does in the WiFi slot, but it does not.
I have not tried the latest Coreboot / port yet, but I figured I might as
well get some opinions on the subject.
What do you guys think, can this be done with Coreboot?
For the past month or two (I'm not actually sure WHEN it stopped working) I
haven't been able to successfully boot (any) Windows installations using
Mid-October I had created some builds that worked, but I'm not sure they
were using master or something else at that point (only kept the binaries
The symptom is that when I select the Windows boot manager from Grub, I get
a very regular-looking, TV-static like screen, then black. From the HDD
activity, I can tell the boot is continuing but the graphics don't recover.
Interestingly, if I then force-powercycle the machine, the Windows
bootloader does successfully enter its "Recovery Environment" or whatever
that is. I can try to choose an OS to boot, but after that the same thing
Is this a known bug / issue?
I'm building the latest master for the X210 using mgj59's port.
In the spirit of board report coverage, I pulled out the (used, but new to
me) AM1I-A I have and spent a day or two trying to install the latest
coreboot on it.
The board boots fine under the stock bios, and returns to working order if
flashed with my backup, but shows little signs of life with coreboot.
Along the way I extracted and included the vgabios rom, as well as tried
with a nivida card, so I'm pretty sure that's not it.
I tried having it save the console output to flash, but that made the build
Yesterday evening I noticed it was configured by default to use open-source
init (and for some reason the build finishes without error), but as far as
I know that doesn't exist for family 16h. Switching to BinaryPI causes the
build to fail.  3rd party blobs are cloned and enabled.
I'm running an Athlon 5250, or something of that nature, with a couple of
gigs of ram on one dimm. My current .config is .
Could a Coreboot Coverity admin please re-run the scan against master?
Looks like the last analyzed version was from Sep 24, 2019. I would like
to see what AGESA issues remain.
- don't top post
Mailing list etiquette:
- trim quoted reply to only relevant portions
- when possible, copy and paste text instead of screenshots
I'm trying to boot camelback mountain with coreboot image. I selected the seabios as primary payload. I attached USB keyboard.
In the boot log, I'm able to see "USB is initialised", "1 device found on USB port". So I think USB is initialised properly.
But when I press escape key continuously while booting, the boot menu is not displayed at all. Even on pressing num lock, the num lock led doesn't glow. It looks like keyboard is not even powered on.
Please let me know how to resolve this issue.
Thanks in advance,
L&T Technology Services Ltd