I am still using the Thinkpad X230 Tablet I first mentioned in 2012.
 Now we have pretty decent support for Thinkpad X230, but it seems
to be for the regular variant, with only a passiing mention of
digitizer working on X230T.
Mine is now set up for UEFI booting.
So, where do we stand on support for UEFI (Tianocore?) and coreboot
x230? Can I use the same build for both X230 and X230T? What else
would I miss?
Except the wifi whitelist, my X230T has been better than all my
previous laptops. I know I need to find a SOIC8 test clip and a SPI
programmer (I think I'll try an Arduino solution first, with a Mega
2560 lying around) and most of what I need to do to build a working
Appreciate any insights.
I tried the acpi patches again, and this time it worked properly. I
don't know if I had just missed running make clean, ended up flashing
the wrong rom with aflash, or messed something else up.
As for flashrom, I'd posted logs from my attempts at running it on its
I have a running T420 with coreboot running from an msata ssd. Works like a charm.
However, I have grub as payload. Do you intend to run windows, or why do you want seabios?
Hope that helps.
I see on the wiki that mSATA works on the T420.
I am wondering has anyone tried booting from an msata drive? was seaBIOS
able to detect the mSATA drive?
Also how would I go about changing the default boot order for coreboot?
Hello Guys !
I apologize with you if my question seems silly:
can you tell me if Coreboot stores a log of the POST phase in its EPROM
If so, is it possible to retrive the log by the Operative System and
read it ?
Thanks in advance.
/* Style Definitions */
mso-padding-alt:0cm 5.4pt 0cm 5.4pt;
mso-fareast-font-family:"Times New Roman";
mso-bidi-font-family:"Times New Roman";
Tribunale di Lecce
Studio: Strada di Garibaldi - Contrada Paradisi
73010 Lequile (LE)
從 Windows 10 的郵件傳送
I use qemu and tianocore payload to research coreboot but I found qemu can not show vga message in bios post phase. I found tianocore function named“gST->ConOut->OutputString( )”can not show any string on qemu screen under bios post phase, I already add vbios named“vgabios-cirrus.bin”by“make menuconfig”, anyone can tell me how to bring up qemu vga so that show gST->ConOut->OutputString( )”message on qemu screen under post time, my qemu setting as below :
qemu-system-x86_64 -machine accel=kvm:tcg -bios build/coreboot.rom -vga cirrus -m 2048 -drive file=/dev/sdb,index=0,media=disk,format=raw
P.S. My virtualbox does not install kvm
Since there are many releases of Intel's cpu microcode since 2015-01, I
was wondering if
there's a reason why coreboot, if at all, uses this one.
I know very little about it really. It may well be potentially bad to
simply use the latest version,
but in case it's really only because nobody did it, I might prepare a
patch to use
I testing it on my device).
Am 21.11.2017 12:42 schrieb Zoran Stojsavljevic:
>> I know very little about it really. It may well be potentially bad
> to simply use the latest version,
>> but in case it's really only because nobody did it, I might prepare
> a patch to use
>> downloadmirror.intel.com/27337/eng/microcode-20171117.tgz 
> instead (someday, after
>> I testing it on my device).
> To understand what is really going on, I did the following
> investigation on my only coreboot clone version,
> I have on my current SSD the following: WIN10, using VMware®
> Workstation 12 Player, version 12.5.8 build-7098237
> with Fedora 26 VM, where the coreboot is located.
> CLI transcript follows:
> _[user@localhost coreboot]$ pwd_
> _[user@localhost coreboot]$ git describe_
> _[user@localhost coreboot]$ grep -r 20150121 *_
> _[user@localhost coreboot]$ cd 3rdparty/blobs/cpu/intel/microcode_
> _[user@localhost microcode]$ ls -al_
> _total 24_
> _drwxrwxr-x. 2 user user 12288 Nov 21 12:27 ._
> _drwxrwxr-x. 24 user user 4096 Feb 18 2017 .._
> _-rwxrwxr-x. 1 user user 1782 Feb 18 2017 microcode2bin.sh_
> _-rwxrwxr-x. 1 user user 2989 Nov 21 12:27 update-microcodes.sh_
> _[user@localhost microcode]$ tail -10 update-microcodes.sh _
> _DUMP_CPUIDS <<=========================== I ADDED THIS LINE OF CODE
> TO SEE WHICH CPUIDS'S MCUS ARE ADDED HERe: _
> _rm -f $MICROCODE_ARCHIVE_
> _rm -f $MICROCODE_FILE_
> _[user@localhost microcode]$ _
> Now, you can substitute 20150121.tgz with 20171117 .tgz in bash
> shell script update-microcodes.sh and see what will happen?!
That's not enough. The integers in the url of
change aswell, not just MICROCODE_VERSION.
So if you're suggesting that a download fails, that's not the issue.
But maybe I got you wrong. Anyways, I haven't tried to change and run
it. I might. so...
I'm not sure that I'm setting up the acpi patches correctly then. I
had just ran:
git fetch https://review.coreboot.org/coreboot refs/changes/73/22473/1
&& git checkout FETCH_HEAD
originally. I think I had run make clean as well.
I tried doing:
git fetch https://review.coreboot.org/coreboot refs/changes/71/21671/2
&& git fetch https://review.coreboot.org/coreboot
refs/changes/73/22473/1 && git checkout FETCH_HEAD
but I don't know if that's how it's supposed to work.
My experience with git is just using it to pull trunk versions of
software and that's about it. I finally started to read Pro Git
though, to try to actually learn how git works.
The release will be happening, but I haven't had time to get it done.
Mainly we need to find someone to do the release notes.
If we have any volunteers to wade through the 2000+ changes and write
something up, I'd be glad to walk you through the process of what
needs to be done.
On Mon, Nov 20, 2017 at 2:42 PM, Youness Alaoui
> What happened with the plan for the 4.7 release? I thought it was
> supposed to be out at the end of October, now we're approaching the
> end of November.
> Was it forgotten, delayed or cancelled ? If delayed, what's the
> blocking issue ?
> On Wed, Oct 4, 2017 at 11:24 AM, Martin Roth <gaumless(a)gmail.com> wrote:
>> The release will happen towards the end of the month. Generally I
>> try to have the release scheduled a bit before the month ends so
>> there's a little room to slip. I'll sit down this weekend and start
>> sorting out where we are and send out another email with release
>> If there are any bugs in the bug tracker that people would
>> specifically like help with getting fixed before the next release,
>> please reply here.
>> If developers could take a look at coverity and see if there are any
>> issues there that they can fix, that would be great.
>> Please start testing any boards that you have and uploading the
>> results to the board-status repo so we know what's working. If you
>> have boards that don't boot, please reply here, and try to bisect the
>> issue to find where it stopped working.
>> On Tue, Oct 3, 2017 at 9:33 AM, Paul Menzel
>> <paulepanter(a)users.sourceforge.net> wrote:
>>> Dear coreboot folks,
>>> It’s October and coreboot 4.7 is supposed to be tagged in this month.
>>> Are there more specific plans already, when the release will happen?
>>> coreboot mailing list: coreboot(a)coreboot.org
>> coreboot mailing list: coreboot(a)coreboot.org