coreboot March 2017

coreboot@coreboot.org

79 participants
267 discussions

Re: [coreboot] Lenovo Thinkpad X201: cannot boot encrypted Debian w/Coreboot & GRUB2
by Nico Huber 22 Mar '17

22 Mar '17

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

2 1

Re: [coreboot] Maintain boot order for multiple EFI based OS
by Nico Huber 22 Mar '17

22 Mar '17

Hi Sibi, On 22.03.2017 14:20, Sibi.Rajasekaran(a)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

1 0

Lenovo Thinkpad X201: cannot boot encrypted Debian w/Coreboot & GRUB2
by Sam Kuper 22 Mar '17

22 Mar '17

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!

1 0

Re: [coreboot] Maintain boot order for multiple EFI based OS
by Zoran Stojsavljevic 22 Mar '17

22 Mar '17

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, <Sibi.Rajasekaran(a)dell.com> 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(a)coreboot.org > https://www.coreboot.org/mailman/listinfo/coreboot >

1 0

Re: [coreboot] Add me_cleaner to automated tests?
by Zoran Stojsavljevic 22 Mar '17

22 Mar '17

BTW, Martin, > https://www.coreboot.org/User:MartinRoth#Platforms_supported_by_coreboo <https://www.coreboot.org/User:MartinRoth#Platforms_supported_by_coreboot>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 <sam.kuper(a)uclmail.net> wrote: > On 22/03/2017, Martin Roth <gaumless(a)gmail.com> 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(a)coreboot.org > https://www.coreboot.org/mailman/listinfo/coreboot >

1 0

Maintain boot order for multiple EFI based OS
by Sibi.Rajasekaran＠dell.com 22 Mar '17

22 Mar '17

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

1 0

Re: [coreboot] Add me_cleaner to automated tests?
by Sam Kuper 22 Mar '17

22 Mar '17

On 22/03/2017, Martin Roth <gaumless(a)gmail.com> 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? ;)

1 0

Rowhammer DRAM Refresh
by Philipp Stanner 22 Mar '17

22 Mar '17

Hi, where (which code file) does coreboot set the DRAM-refresh-rate and how easy is it for me to change it? A higher refresh rate will decrease the performance but increase the protection against Rowhammer. // Philipp

2 2

Re: [coreboot] PS/2 Mouse on KGPE-D16
by Paul Menzel 22 Mar '17

22 Mar '17

Dear cb, Am Montag, den 20.03.2017, 21:15 +0000 schrieb cb(a)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

1 0

Re: [coreboot] PS/2 Mouse on KGPE-D16
by Paul Menzel 22 Mar '17

22 Mar '17

Dear cb, Am Montag, den 20.03.2017, 21:43 +0000 schrieb cb(a)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

1 0

← Newer
1
...
9
10
11
12
13
14
15
...
27
Older →

Jump to page:

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

2003

2002

coreboot March 2017