Re: [coreboot] Maintain boot order for multiple EFI based OS

[Ma, Maurice]

Hi, Sibi，

Yes,  UEFI payload follows the same way as standard UEFI FW on boot order 
handling.   You will have to enable a NVRAM variable driver in order to 
maintain the boot options and order.

Current UEFI payload uses an generic emulated variable driver provided in EDK2 
MdeModulePkg.   With this driver, the variable will be lost after reboot since 
it is stored in memory.
To  store it in NVRAM,  you will then need to develop or port a flash based 
variable driver, and then replace the emulated variable driver.  This part is 
very platform and silicon specific.

Thanks
Maurice
From: Leahy, Leroy P
Sent: Wednesday, March 22, 2017 4:51 PM
To: sibi.rajaseka...@dell.com; coreboot@coreboot.org; Ma, Maurice 
; Agyeman, Prince 
Subject: RE: Maintain boot order for multiple EFI based OS

Hi Maurice and Prince,

Would you please help answer the question below?

Hi Sibi,

The maintainers for the various EDK-II packages can be found in 
payloads/external/tianocore/tianocore/Maintainers.txt.  In your case, search 
for CorebootPayloadPkg.

Lee Leahy

From: coreboot [mailto:coreboot-boun...@coreboot.org] On Behalf Of 
sibi.rajaseka...@dell.com
Sent: Wednesday, March 22, 2017 6:20 AM
To: coreboot@coreboot.org
Subject: [coreboot] Maintain boot order for multiple EFI based OS

Dell - Internal Use - Confidential
Hi,

We are using the coreboot project with Intel fsp to boot the Intel Rangeley 
based Mohonpeak CPU. We have built the Tianocore EDK2 project and used it as 
the payload to bring UEFI services to this bootloader. With this payload, we 
are able to boot a EFI based OS successfully.

As a next step, we are looking at installing multiple EFI OS and maintaining 
boot order among the OS.
How is boot order maintained with UEFI payload?
Is it through EFI NVRAM variables? If so, does coreboot support NVRAM variables?

Can you please point us in the right direction.

Thanks,
Sibi
-- 
coreboot mailing list: coreboot@coreboot.org
https://www.coreboot.org/mailman/listinfo/coreboot

Re: [coreboot] Where to buy the KCMA-D8? *brand new*

[taii...@gmx.com]

On 03/22/2017 07:07 PM, Daniel Kulesz wrote:


Does anyone know? I have checked everywhere
I can't find the accessories for the board family either (TPM etc)

There is shop in Germany that sells it (according to the website, they have 6 
pcs left in stock):

https://direkt.jacob.de/Mainboards/divers/ASUS-KCMA-D8-90-MSVD91-G0UAY00Z-artnr-851627.html?ref=103

It was easy to find using a price comparison machine:

https://geizhals.de/asus-kcma-d8-90-msvd91-g0uay00z-a592717.html

If you are looking for a cheap board for a "high-end" router without the need 
for IOMMU I would recommend trying the Supermicro H8DME (it doesn't have a recent 
board_status though). You can find them pretty cheap on Ebay (used as well as new), 
however, you need to get DDR2 memory for them (which is even cheaper than DDR2 nowadays).

Cheers, Daniel

Thanks, but germany is quite far away for me I am preferably looking for 
a US, canadian, mexican etc seller to save on shipping (and that 
jacob.de site sells them for way above the $300 MSRP)



I already have an AM1ML as my router, but it has no IOMMU functional and 
that is a big issue.
Biostar didn't make it work in the vendor bios, they said that "AMD 
didn't implement it in hw" whereas AMD says it is in-fact present and 
accounted for. I am going to try to add it in coreboot for this and 
another agesa board when I have the time.


--
coreboot mailing list: coreboot@coreboot.org
https://www.coreboot.org/mailman/listinfo/coreboot

Re: [coreboot] Maintain boot order for multiple EFI based OS

[Leahy, Leroy P]

Hi Maurice and Prince,

Would you please help answer the question below?

Hi Sibi,

The maintainers for the various EDK-II packages can be found in 
payloads/external/tianocore/tianocore/Maintainers.txt.  In your case, search 
for CorebootPayloadPkg.

Lee Leahy

From: coreboot [mailto:coreboot-boun...@coreboot.org] On Behalf Of 
sibi.rajaseka...@dell.com
Sent: Wednesday, March 22, 2017 6:20 AM
To: coreboot@coreboot.org
Subject: [coreboot] Maintain boot order for multiple EFI based OS

Dell - Internal Use - Confidential
Hi,

We are using the coreboot project with Intel fsp to boot the Intel Rangeley 
based Mohonpeak CPU. We have built the Tianocore EDK2 project and used it as 
the payload to bring UEFI services to this bootloader. With this payload, we 
are able to boot a EFI based OS successfully.

As a next step, we are looking at installing multiple EFI OS and maintaining 
boot order among the OS.
How is boot order maintained with UEFI payload?
Is it through EFI NVRAM variables? If so, does coreboot support NVRAM variables?

Can you please point us in the right direction.

Thanks,
Sibi
-- 
coreboot mailing list: coreboot@coreboot.org
https://www.coreboot.org/mailman/listinfo/coreboot

[coreboot] Where to buy the KCMA-D8? *brand new*

[Daniel Kulesz via coreboot]

>Does anyone know? I have checked everywhere
>I can't find the accessories for the board family either (TPM etc)

There is shop in Germany that sells it (according to the website, they have 6 
pcs left in stock):

https://direkt.jacob.de/Mainboards/divers/ASUS-KCMA-D8-90-MSVD91-G0UAY00Z-artnr-851627.html?ref=103

It was easy to find using a price comparison machine:

https://geizhals.de/asus-kcma-d8-90-msvd91-g0uay00z-a592717.html

If you are looking for a cheap board for a "high-end" router without the need 
for IOMMU I would recommend trying the Supermicro H8DME (it doesn't have a 
recent board_status though). You can find them pretty cheap on Ebay (used as 
well as new), however, you need to get DDR2 memory for them (which is even 
cheaper than DDR2 nowadays).

Cheers, Daniel

-- 
coreboot mailing list: coreboot@coreboot.org
https://www.coreboot.org/mailman/listinfo/coreboot

Re: [coreboot] Lenovo Thinkpad X201: cannot boot encrypted Debian w/Coreboot & GRUB2

[Sam Kuper]

On 22/03/2017, Sam Kuper  wrote:
> On 22/03/2017, Nico Huber  wrote:
>> On 22.03.2017 17:03, Sam Kuper wrote:
>> The GRUB payload, by default, doesn't have any configuration file and
>> will wait at the prompt (no matter if the disk is encrypted or not).
>
> Good to have this confirmed. From a GRUB prompt, I hope I will be able
> to find and boot the Debian installation.
>
>>> In any case, how would more
>>> experienced Corebooters suggest I proceed?
>>
>> Easiest option seems to be to select CONFIG_MAINBOARD_DO_NATIVE_VGA_INIT
>
> [Will] try it ASAP. Thank you!

Thanks again for this suggestion. I do feel it's getting me closer to
having Coreboot boot to Debian with FDE on the X201. However, there's
still a way to go...

Based on your suggestion above, I kept everything as described in my
first email in this thread, except that to build Coreboot, I also
selected "Use native graphics initialization" under "Devices" within
`make nconfig`. (This sets CONFIG_MAINBOARD_DO_NATIVE_VGA_INIT=y in
the .config .)

Unfortunately, my results were exactly the same as before, except that
this time the backlight came on. In particular, no GRUB2 prompt
appeared.

Is this expected? From your email, it sounds as though it isn't what
you expected.

I would be grateful for additional suggestions from you or other
experienced Corebooters :)

Thanks again!

-- 
coreboot mailing list: coreboot@coreboot.org
https://www.coreboot.org/mailman/listinfo/coreboot

[coreboot] Where to buy the KCMA-D8? *brand new*

[taii...@gmx.com]

Does anyone know? I have checked everywhere
I can't find the accessories for the board family either (TPM etc)

I would just get another KGPE-D16 but I want to make a router with one 
of the 35W C32 "EE" opterons and the retail price is a little cheaper.



And does anyone know how much longer they are making the KGPE-D16? I 
wanna buy more before they stop (I could get arm or power, but I still 
need x86 to play video games) I suppose it is possible to port to 
another better available similar board like something from supermicro 
(H8DGI-way, way better specs, first released 2014) but I have no idea 
how complex that is.



--
coreboot mailing list: coreboot@coreboot.org
https://www.coreboot.org/mailman/listinfo/coreboot

Re: [coreboot] Maintain boot order for multiple EFI based OS

[Zoran Stojsavljevic]

> I think you miss the point here. Sibi was asking how to store settings,
> where UEFI should look for the next-stage bootloader (e.g. GRUB), and
> not how to relay the decision which OS to boot.

I am old, a bit numb/dumb (reason INTEL ousted me, good reasoning, don't
you think?), so this is why I did reply to this email in the first place...
To learn something tangible. I am looking forward for people to couch/teach
me.

Besides, seems that you, Nico, missing something important in your personal
integration: reading/listening skills. You even did not bother to read my
entire email (typical FLMs and SLMs behavior in INTEL). ;-)

What about my question #1: *[1: For general Coreboot population] After
having Tiano Core payload executed, how Tiano Core is linked with the next
booting phase: GRUB2?*

So your answer/question is kinda perfect, I should say. I am also looking
forward to the answer you did formulate (since you did not bother to read
mine).

In other words, I am also after this question: How Tiano Core should
look/what is the mechanism to get to the GRUB2?

(I need to learn Chinese, really I do, maybe I'll make/express myself more
clear) :-))

Thank you,
Zoran

On Wed, Mar 22, 2017 at 8:02 PM, Nico Huber  wrote:

> Hi Zoran,
>
> On 22.03.2017 14:51, Zoran Stojsavljevic wrote:
> > Hello Sibi,
> >
> > The answer to your question lies outside of Coreboot domain. After
> bringing
> > Tiano Core, you need to bring the next phase of booting: OS boot loader.
> > The best for you is to use GRUB2. Then, from GRUB2 menu
> > (/boot/efi/EFI/.../grub.cfg) you can choose your OS (either WIN8+, either
> > any modern Linux distro). You can have up to 128 of them, as my best
> > understanding is.
>
> I think you miss the point here. Sibi was asking how to store settings,
> where UEFI should look for the next-stage bootloader (e.g. GRUB), and
> not how to relay the decision which OS to boot.
>
> Nico
>
>
-- 
coreboot mailing list: coreboot@coreboot.org
https://www.coreboot.org/mailman/listinfo/coreboot

Re: [coreboot] Lenovo Thinkpad X201: cannot boot encrypted Debian w/Coreboot & GRUB2

[Sam Kuper]

On 22/03/2017, Nico Huber  wrote:
> On 22.03.2017 17:03, Sam Kuper wrote:
>> -- Choose "GRUB2" as payload.
> You didn't select any option to initialize the display.
[...]
>> - After about 10 minutes, the fan spins up for a few seconds, then
>> spins back down. This repeats roughly every 10 minutes.
> I guess, you are at the GRUB console here, just without display.
[...]
> The only thing that is skipped is the display initialization. SeaBIOS
> does a legacy boot and detects the installed GRUB, runs it etc...
[...]

Interesting. A few days ago, I tried running Coreboot on the X201 with
a SeaBIOS payload and no SSD installed. IIRC, SeaBIOS did provide a
display at that point. But maybe I am misremembering, and the SeaBIOS
display was actually something I only saw in QEMU.

That aside (which on reflection probably *was* in QEMU), your
explanation makes perfect sense :) I hadn't realised that Coreboot's
default would be *not* to initialise a display.

> The GRUB payload, by default, doesn't have any configuration file and
> will wait at the prompt (no matter if the disk is encrypted or not).

Good to have this confirmed. From a GRUB prompt, I hope I will be able
to find and boot the Debian installation.

>> In any case, how would more
>> experienced Corebooters suggest I proceed?
>
> Easiest option seems to be to select CONFIG_MAINBOARD_DO_NATIVE_VGA_INIT
>
> Hope that helps,

Very much so; will try it ASAP. Thank you!

-- 
coreboot mailing list: coreboot@coreboot.org
https://www.coreboot.org/mailman/listinfo/coreboot

Re: [coreboot] Lenovo Thinkpad X201: cannot boot encrypted Debian w/Coreboot & GRUB2

[Nico Huber]

Hi Sam,

On 22.03.2017 17:03, Sam Kuper wrote:
> Steps followed:
> 
> ...
> 
> - On spare PC, in Coreboot directory:
> 
> -- make distclean && make nconfig
> 
> -- Choose "Lenovo" as mainboard vendor.
> 
> -- Choose "ThinkPad X201 / X201s / X201t" as mainboard.
> 
> -- Choose "Add Intel descriptor.bin file".
> 
> -- Choose "Add Intel ME/TXE firmware".
> 
> -- Choose "GRUB2" as payload.

You didn't select any option to initialize the display.

> 
> - After about 10 minutes, the fan spins up for a few seconds, then
> spins back down. This repeats roughly every 10 minutes.

I guess, you are at the GRUB console here, just without display.

> 
> N.B. with the same X201, a day or two ago, I was able to use a
> Coreboot build with a SeaBIOS payload to boot a non-encrypted Debian
> installation from the SSD. Oddly, when I did that, there was no
> SeaBIOS menu displayed, nor any GRUB2 menu displayed, even though the
> unencrypted Debian install had placed a GRUB2 instance on the SSD: it
> was as though Coreboot skipped both its own SeaBIOS payload in the
> flash chip, AND the Debian-installed GRUB2 on the SSD, and somehow
> went straight to the Debian login prompt.

The only thing that is skipped is the display initialization. SeaBIOS
does a legacy boot and detects the installed GRUB, runs it etc...

> 
> Anyhow, I didn't want a non-encrypted Debian installation, I wanted an
> encrypted one: hence the attempt above. I guess maybe what's happening
> is that Coreboot is somehow this time skipping its GRUB2 payload much
> as it previously seemed to skip its SeaBIOS payload, and likewise
> skipping the Debian-installed GRUB2 instance on the SSD as it did
> previously. Only this time, instead of finding an unencrypted drive
> with a Debian kernel that it knows how to boot, Coreboot is instead
> finding an encrypted partition that it doesn't know how to do anything
> with.

The GRUB payload, by default, doesn't have any configuration file and
will wait at the prompt (no matter if the disk is encrypted or not).

> 
> Is my interpretation plausible? In any case, how would more
> experienced Corebooters suggest I proceed?

Easiest option seems to be to select CONFIG_MAINBOARD_DO_NATIVE_VGA_INIT

Hope that helps,
Nico

-- 
coreboot mailing list: coreboot@coreboot.org
https://www.coreboot.org/mailman/listinfo/coreboot

Re: [coreboot] Maintain boot order for multiple EFI based OS

[Nico Huber]

Hi Zoran,

On 22.03.2017 14:51, Zoran Stojsavljevic wrote:
> Hello Sibi,
> 
> The answer to your question lies outside of Coreboot domain. After bringing
> Tiano Core, you need to bring the next phase of booting: OS boot loader.
> The best for you is to use GRUB2. Then, from GRUB2 menu
> (/boot/efi/EFI/.../grub.cfg) you can choose your OS (either WIN8+, either
> any modern Linux distro). You can have up to 128 of them, as my best
> understanding is.

I think you miss the point here. Sibi was asking how to store settings,
where UEFI should look for the next-stage bootloader (e.g. GRUB), and
not how to relay the decision which OS to boot.

Nico


-- 
coreboot mailing list: coreboot@coreboot.org
https://www.coreboot.org/mailman/listinfo/coreboot

Re: [coreboot] Maintain boot order for multiple EFI based OS

[Nico Huber]

Hi Sibi,

On 22.03.2017 14:20, sibi.rajaseka...@dell.com wrote:
> Dell - Internal Use - Confidential
please skip such folly when you write to a public mailing list.

> 
> Hi,
> 
> We are using the coreboot project with Intel fsp to boot the Intel
> Rangeley based Mohonpeak CPU. We have built the Tianocore EDK2 project
> and used it as the payload to bring UEFI services to this bootloader.
> With this payload, we are able to boot a EFI based OS successfully.

Nice.

> 
> As a next step, we are looking at installing multiple EFI OS and
> maintaining boot order among the OS.  How is boot order maintained with
> UEFI payload?  Is it through EFI NVRAM variables? If so, does coreboot
> support NVRAM variables?

IIRC, CorebootPayloadPkg doesn't support NVRAM. I'll CC some people who
might know the details.

Nico

-- 
coreboot mailing list: coreboot@coreboot.org
https://www.coreboot.org/mailman/listinfo/coreboot

[coreboot] Lenovo Thinkpad X201: cannot boot encrypted Debian w/Coreboot & GRUB2

[Sam Kuper]

Steps followed:

- Switch off X201; disconnect X201 PSU and battery.

- Flash X201 using Bus Pirate, with OEM BIOS that has had its ME
neutralised with me_cleaner, noting that Flashrom reported "VERIFIED".

- Disconnect Bus Pirate from X201.

- Reconnect X201 PSU.

- Press power button, then F12 to select CD-ROM as boot media.

- Boot Debian Jessie AMD64 NetInstall CD-ROM.

- Install Debian Jessie to X201's SSD, using guided install (full disk
with encrypted LVM, and GRUB2 on the SSD).

- Eject CD.

- Boot X201 from SSD; everything works as expected.

- Boot X201 from SSD again; again, everything works as expected.

- Switch off X201 and disconnect X201 PSU.

- On spare PC, in Coreboot directory:

-- make distclean && make nconfig

-- Choose "Lenovo" as mainboard vendor.

-- Choose "ThinkPad X201 / X201s / X201t" as mainboard.

-- Choose "Add Intel descriptor.bin file".

-- Choose "Add Intel ME/TXE firmware".

-- Choose "GRUB2" as payload.

-- make

- Flash resulting build/coreboot.rom to X201 with Bus Pirate, noting
that Flashrom reported "VERIFIED".

- Disconnect Bus Pirate from X201.

- Reconnect X201 PSU, confirming that "plugged in" LED indicator turns
on, just beneath the X201's display.

- Press power switch on X201.

- The X201's fan spins up, and the following LED indicators light up,
in addition to the power "plugged in" indicator: NumLock, CapsLock,
On, and Sleep.

- After about 1 second, the NumLock and Sleep LEDs turn off, and the
fan starts to spin down.

- After about 1 more second, the CapsLock LED turns off, leaving just
the "on" and "plugged in" LEDs lit.

- Nothing further happens for some time. The backlight doesn't turn
on, and the screen stays blank.

- After about 10 minutes, the fan spins up for a few seconds, then
spins back down. This repeats roughly every 10 minutes.

N.B. with the same X201, a day or two ago, I was able to use a
Coreboot build with a SeaBIOS payload to boot a non-encrypted Debian
installation from the SSD. Oddly, when I did that, there was no
SeaBIOS menu displayed, nor any GRUB2 menu displayed, even though the
unencrypted Debian install had placed a GRUB2 instance on the SSD: it
was as though Coreboot skipped both its own SeaBIOS payload in the
flash chip, AND the Debian-installed GRUB2 on the SSD, and somehow
went straight to the Debian login prompt.

Anyhow, I didn't want a non-encrypted Debian installation, I wanted an
encrypted one: hence the attempt above. I guess maybe what's happening
is that Coreboot is somehow this time skipping its GRUB2 payload much
as it previously seemed to skip its SeaBIOS payload, and likewise
skipping the Debian-installed GRUB2 instance on the SSD as it did
previously. Only this time, instead of finding an unencrypted drive
with a Debian kernel that it knows how to boot, Coreboot is instead
finding an encrypted partition that it doesn't know how to do anything
with.

Is my interpretation plausible? In any case, how would more
experienced Corebooters suggest I proceed?

I certainly would have expected, based on the Coreboot wiki's GRUB2
page,[1] at least a GRUB2 console.

In case it is useful, I have attached my .config file.

Many thanks in advance!


.config
Description: Binary data
-- 
coreboot mailing list: coreboot@coreboot.org
https://www.coreboot.org/mailman/listinfo/coreboot

Re: [coreboot] Power supply and X220

[Albin]

Thank you John Lewis and, again, Persmule.

I've now successfully flashed coreboot onto the machine with a disabled
ME and just booted into GNU/Linux.

I connected 3.3v to pin 3 on the BBB (instead of an ATX) and reapplied
the Pomona clip a few times. Then, finally, the chip was recognized. \o/


Happy hacking!

Albin

Den 2017-03-21 kl. 16:47, skrev John Lewis:
> Dear Albin,
> 
> 
> As for Persmule, I've never had the need to use an ATX power supply, or
> anything beyond the external BBB power supply and the two 3.3v
> pins/holes on the BBB itself when flashing Chromebooks externally.
> 
> 
> If the chip isn't being recognised, the most likely culprits are:
> 
> 
> 1. That you attached the clip the wrong way round.
> 
> 2. The pins on the clip aren't making proper contact with the legs on
> the chip.
> 
> 3. You've mis-wired the setup to begin with.
> 
> 
> Regards,
> 
> 
> John.
> 
> 
> On 21/03/17 11:59, Persmule wrote:
> 
>> Dear Albin,
>>
>> You should only power your BBB with an external 5V power supplier, and
>> connect its usb peripheral port to your controlling computer. I have
>> never used any ATX power supplier for this, just the configuration I
>> just described is enough.
>>
>> Best regards,
>>
>> Persmule
>>
>> 在 2017年03月21日 18:55, Albin 写道:
>>> Dear Persmule,
>>>
>>> First, thank you for your work on free software. I'm following your
>>> guide[1] to replace Bios on my Thinkpad X220 with a neutralized
>>> coreboot using a BBB rev. C and an ATX power supply for the v3.3 pin,
>>> but flashrom is unable to recognize the chip. Did you have any
>>> problems recognizing the chip on your device and do you have any
>>> ideas of what to try?
>>>
>>> "image" at #coreboot suggested that I should connect the power cable
>>> to the machine instead of using an external power supply but I
>>> haven't read anywhere that this should work or even be safe.
>>>
>>> My current setup worked for reflashing a macbook2,1 but not for this
>>> x220.
>>>
>>> Again, any advice would be highly appreciated.
>>>
>>> Best,
>>>
>>> Albin
>>>
>>> 1.
>>> https://hardenedlinux.github.io/firmware/2016/11/17/neutralize_ME_firmware_on_sandybridge_and_ivybridge.html
>>
>>
>>
> 
> 

-- 
coreboot mailing list: coreboot@coreboot.org
https://www.coreboot.org/mailman/listinfo/coreboot

Re: [coreboot] Maintain boot order for multiple EFI based OS

[Zoran Stojsavljevic]

Hello Sibi,

The answer to your question lies outside of Coreboot domain. After bringing
Tiano Core, you need to bring the next phase of booting: OS boot loader.
The best for you is to use GRUB2. Then, from GRUB2 menu
(/boot/efi/EFI/.../grub.cfg) you can choose your OS (either WIN8+, either
any modern Linux distro). You can have up to 128 of them, as my best
understanding is.

So: Coreboot intermingled with FSP -> Coreboot -> Tiano Core -> GRUB2 ->
Any UEFI compliant OS.

I have here two questions:
[1: For general Coreboot population] After having Tiano Core payload
executed, how Tiano Core is linked with the next booting phase: GRUB2?
[2: for Sibi] What are the fastest and average booting times from board
Power On till post executing Tiano Core?

Thank you,
Zoran

On Wed, Mar 22, 2017 at 2:20 PM,  wrote:

>
>
> *Dell - Internal Use - Confidential *
>
> Hi,
>
>
>
> We are using the coreboot project with Intel fsp to boot the Intel
> Rangeley based Mohonpeak CPU. We have built the Tianocore EDK2 project and
> used it as the payload to bring UEFI services to this bootloader. With this
> payload, we are able to boot a EFI based OS successfully.
>
>
>
> As a next step, we are looking at installing multiple EFI OS and
> maintaining boot order among the OS.
>
> How is boot order maintained with UEFI payload?
>
> Is it through EFI NVRAM variables? If so, does coreboot support NVRAM
> variables?
>
>
>
> Can you please point us in the right direction.
>
>
>
> Thanks,
>
> Sibi
>
> --
> coreboot mailing list: coreboot@coreboot.org
> https://www.coreboot.org/mailman/listinfo/coreboot
>
-- 
coreboot mailing list: coreboot@coreboot.org
https://www.coreboot.org/mailman/listinfo/coreboot

Re: [coreboot] Add me_cleaner to automated tests?

[Zoran Stojsavljevic]

BTW, Martin,

> https://www.coreboot.org/User:MartinRoth#Platforms_supported_by_coreboo
t

All boards here, which I took from your list are actually INTEL Customer
Reference Boards (CRBs), not laptop/notebook platforms/boards!
Intel Bakersport Intel Bay Trail I 1 ECC DDR-3 SODIMM 1 No
Intel Bayley Bay Intel Bay Trail I 2 DDR-3 SODIMM 1 No
Intel Camelback Mountain Broadwell DE 2 DDR-4 UDIMMs 1 No
Intel Cougar Canyon Intel Ivybridge 1 No







Intel Galileo 2 Yes
Intel Galileo Gen 2 1 Yes
Intel/Circuitco Minnowboard Max Intel Bay Trail I 1 No
Intel/ADI Minnowboard Turbot Intel Bay Trail I 1 No
Intel Mohon Peak Intel Rangeley 1 NoThis would be as your wife got some
outdated shoes from outlet mall almost for free (which I doubt, I know that
women do care about Fashion). ;-)

You need more INTEL based ASUS and GigaByte platforms/boards... Definitely!

Zoran

On Wed, Mar 22, 2017 at 1:42 PM, Sam Kuper  wrote:

> On 22/03/2017, Martin Roth  wrote:
> > Here's the list of boards I've got for coreboot testing.
> >
> > https://www.coreboot.org/User:MartinRoth#Platforms_supported_by_coreboot
> >
> > My plan is to get as many of these as I can set up for automated testing.
> >
> > When new boards are added to the tree, I try to buy them if possible,
> > but that's a lot of boards.  I've told my wife that every time she
> > buys a pair of shoes, I get to buy a new computer.  It works out well
> > for both of us, but she's still winning.  :)
>
> Thanks :)
>
> Interesting to see that there are no X-series laptops on your list,
> given how much attention they receive from the Coreboot community. Did
> you say your wife is a few pairs of shoes ahead of your board
> collection? ;)
>
> --
> coreboot mailing list: coreboot@coreboot.org
> https://www.coreboot.org/mailman/listinfo/coreboot
>
-- 
coreboot mailing list: coreboot@coreboot.org
https://www.coreboot.org/mailman/listinfo/coreboot

[coreboot] Maintain boot order for multiple EFI based OS

[Sibi.Rajasekaran]

Dell - Internal Use - Confidential

Hi,

We are using the coreboot project with Intel fsp to boot the Intel Rangeley 
based Mohonpeak CPU. We have built the Tianocore EDK2 project and used it as 
the payload to bring UEFI services to this bootloader. With this payload, we 
are able to boot a EFI based OS successfully.

As a next step, we are looking at installing multiple EFI OS and maintaining 
boot order among the OS.
How is boot order maintained with UEFI payload?
Is it through EFI NVRAM variables? If so, does coreboot support NVRAM variables?

Can you please point us in the right direction.

Thanks,
Sibi
-- 
coreboot mailing list: coreboot@coreboot.org
https://www.coreboot.org/mailman/listinfo/coreboot

Re: [coreboot] Add me_cleaner to automated tests?

[Sam Kuper]

On 22/03/2017, Martin Roth  wrote:
> Here's the list of boards I've got for coreboot testing.
>
> https://www.coreboot.org/User:MartinRoth#Platforms_supported_by_coreboot
>
> My plan is to get as many of these as I can set up for automated testing.
>
> When new boards are added to the tree, I try to buy them if possible,
> but that's a lot of boards.  I've told my wife that every time she
> buys a pair of shoes, I get to buy a new computer.  It works out well
> for both of us, but she's still winning.  :)

Thanks :)

Interesting to see that there are no X-series laptops on your list,
given how much attention they receive from the Coreboot community. Did
you say your wife is a few pairs of shoes ahead of your board
collection? ;)

-- 
coreboot mailing list: coreboot@coreboot.org
https://www.coreboot.org/mailman/listinfo/coreboot

Re: [coreboot] Rowhammer DRAM Refresh

[Philipp Stanner]

K, thank you so far! I hoped there was an easier solution like a #define 
in a header somewhere.


However it's the code I've gone through so far is already interesting as 
coreboot often seems to use a refresh rate of ~16ms what's 4x of the 
rate some vendors use.


// P.


On 20.03.2017 13:34, Arthur Heymans wrote:

Philipp Stanner  writes:


Hi,

where (which code file) does coreboot set the DRAM-refresh-rate and
how easy is it for me to change it?

That would be in raminit, which is platform specific. So it depends on
readability of that code whether it's easy to find or not.

Not sure of this is possible with raminits like FSP or MRC.bin provided
in binary only.


A higher refresh rate will decrease the performance but increase the
protection against Rowhammer.

// Philipp


Some example of how to achieve this on Intel 945 northbridge:

diff --git a/src/northbridge/intel/i945/raminit.c 
b/src/northbridge/intel/i945/raminit.c
index b5cce9c429..36dd601fb2 100644
--- a/src/northbridge/intel/i945/raminit.c
+++ b/src/northbridge/intel/i945/raminit.c
@@ -811,32 +811,8 @@ static void sdram_detect_smallest_refresh(struct sys_info 
* sysinfo)
  {
int i;
  
-	sysinfo->refresh = 0;

+   sysinfo->refresh = 1;
  
-	for (i = 0; i < 2*DIMM_SOCKETS; i++) {

-   int refresh;
-
-   if (sysinfo->dimm[i] == SYSINFO_DIMM_NOT_POPULATED)
-   continue;
-
-   refresh = spd_read_byte(get_dimm_spd_address(sysinfo, i),
-   SPD_REFRESH) & ~(1 << 7);
-
-   /* 15.6us */
-   if (!refresh)
-   continue;
-
-   /* Refresh is slower than 15.6us, use 15.6us */
-   if (refresh > 2)
-   continue;
-
-   if (refresh == 2) {
-   sysinfo->refresh = 1;
-   break;
-   }
-
-   die("DDR-II module has unsupported refresh value\n");
-   }
printk(BIOS_DEBUG, "Refresh: %s\n", sysinfo->refresh?"7.8us":"15.6us");
  }
  
  




--
coreboot mailing list: coreboot@coreboot.org
https://www.coreboot.org/mailman/listinfo/coreboot

Re: [coreboot] PS/2 Mouse on KGPE-D16

[Paul Menzel via coreboot]

Dear cb,


Am Montag, den 20.03.2017, 21:15 + schrieb c...@imap.cc:
> Has anybody had any success using a PS/2 mouse on the KGPE-D16?
> 
> I tried a few PS/2 compatible USB mice, along with an adaptor, without
> success and thought that the mice might be to blame but I've just
> confirmed a native PS/2 mouse doesn't seem to work either.
> 
> I've tried booting directly from SeaBIOS and also with GRUB2 as a
> secondary and no combination I try seems to work.

1.  Please attach all the relevant logs from coreboot, SeaBIOS, and the
Linux Kernel. Please also send us the configuration files of coreboot
and SeaBIOS.

2.  Could you please try passing `i8042.nopnp` to Linux on its command
line, and see if that changes anything?

3.  Lastly, could you please try another payload, which doesn’t rely on
ACPI. I think FreeDOS supports PS/2 mice, but I am not sure.


Thanks,

Paul

signature.asc
Description: This is a digitally signed message part
-- 
coreboot mailing list: coreboot@coreboot.org
https://www.coreboot.org/mailman/listinfo/coreboot

Re: [coreboot] PS/2 Mouse on KGPE-D16

[Paul Menzel via coreboot]

Dear cb,


Am Montag, den 20.03.2017, 21:43 + schrieb c...@imap.cc:
> Not a silly question:
> 
> # CONFIG_DRIVERS_PS2_KEYBOARD is not set
> 
> but the PS/2 keyboard works. Is that setting essential for a mouse to
> function?

No, as SeaBIOS, Linux, and soon libpayload based payloads should be
able to initialize the mouse themselves, if I am not mistaken.


Thanks,

Paul


PS: cb, Taiidan replied using interleaved style [1]. I think, it’d be
good netiquette if you did the same, when you receive such a message.


[1] https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

signature.asc
Description: This is a digitally signed message part
-- 
coreboot mailing list: coreboot@coreboot.org
https://www.coreboot.org/mailman/listinfo/coreboot

[coreboot] HTML messages and list archive (was: Power supply and X220)

[Paul Menzel via coreboot]

Dear persmule,


Am Mittwoch, den 22.03.2017, 00:32 +0800 schrieb persmule:

[…]

You sent just an HTML message. Currently, it’s hard to read such a
message in the archive [1].

So, please send at least a plain/text part in your message. That also
benefits people using an email client (MUA) on the command line.

In my personal opinion, plain text messages (no HTML) is the least
intrusive way, as almost all messages, sent to the list, just contain
text.


Thanks,

Paul


[1] https://www.coreboot.org/pipermail/coreboot/2017-March/083705.html

signature.asc
Description: This is a digitally signed message part
-- 
coreboot mailing list: coreboot@coreboot.org
https://www.coreboot.org/mailman/listinfo/coreboot

Re: [coreboot] Add me_cleaner to automated tests?

[Zoran Stojsavljevic]

> I've told my wife that every time she buys a pair of shoes, I get to buy
a new computer.
>  It works out well for both of us, but she's still winning.  :)

You should change the rule. You should buy a sport car for each pair of
shoes. ;-)

Zoran

On Wed, Mar 22, 2017 at 2:45 AM, Martin Roth  wrote:

> Here's the list of boards I've got for coreboot testing.
>
> https://www.coreboot.org/User:MartinRoth#Platforms_supported_by_coreboot
>
> My plan is to get as many of these as I can set up for automated testing.
>
> When new boards are added to the tree, I try to buy them if possible,
> but that's a lot of boards.  I've told my wife that every time she
> buys a pair of shoes, I get to buy a new computer.  It works out well
> for both of us, but she's still winning.  :)
>
> Martin
>
> On Tue, Mar 21, 2017 at 6:07 PM, Sam Kuper  wrote:
> > Good to hear :)
> >
> > Does the Coreboot project already have an actual physical board for
> > every board listed at https://www.coreboot.org/Supported_Motherboards
> > ? If not, is there a list of which physical boards the project has
> > (or, conversely, is lacking)?
> >
> > Thank you for answering all these questions!
> >
> > P.S. I notice you replied to me individually rather than to the list.
> > If that was not intentional, please feel free to CC the list in your
> > reply :)
> >
> >
> > On 21/03/2017, Martin Roth  wrote:
> >> Well, ultimately, we'd like to have every board in the coreboot tree
> >> tested automatically, if not for every commit, at least daily.  So in
> >> that respect, It's on the roadmap.  It's just slow going.  Currently
> >> only a single configuration is tested, so that's something that would
> >> need to be updated as well.  Once that happens, I don't have any
> >> problem with testing a cut-down ME.
> >>
> >> Martin
> >>
> >> On Tue, Mar 21, 2017 at 2:49 PM, Sam Kuper 
> wrote:
> >>> On 21/03/2017, Martin Roth  wrote:
>  Most of our current automated testing is just build testing, although
>  we're working to expand that.  The boot testing we DO have doesn't
>  currently include any boards with an ME - they're currently all boards
>  that don't require any blobs.
> >>>
> >>> Thanks for the info :)
> >>>
> >>> Is it on Coreboot's roadmap to do automated boot testing of boards
> >>> that have a Management Engine? If so, is my suggestion to also test
> >>> for incompatibilities with me_cleaner a feasible one?
> >>>
> >>> Thanks again :)
> >>
>
> --
> coreboot mailing list: coreboot@coreboot.org
> https://www.coreboot.org/mailman/listinfo/coreboot
>
-- 
coreboot mailing list: coreboot@coreboot.org
https://www.coreboot.org/mailman/listinfo/coreboot