coreboot March 2017

coreboot@coreboot.org

79 participants
267 discussions

Re: [coreboot] USB Support on Apollo Lake
by Gailu Singh 23 Mar '17

23 Mar '17

Hi Zoran, Thanks for the detailed inputs. You are right we were using EHCI in BYT and we used it with grub2 without any issue. If I understood it correctly the usb 2.0 card I was planning to use over pcie is not going to work as we can't mix with usb3.0 root hub, so not worth even trying that option. Would you mind sharing the product details of xHCI 3.0 passive Belkin USB 2.0 bridge so that I can buy and try that. Tried to find on Amazon and Google but couldn't locate a product matching to this criteria (probably my poor keywords) Regarding UARTs, yes there are driver in Linux but not in Grub, so can not use grub console, linux console works fine. USB to UART converter could be an option but USB itself is not working. All my problems end up at USB, (keyboard, uart, mass storage) Thanks again for your help and support On Mon, Mar 20, 2017 at 6:41 PM, Zoran Stojsavljevic < zoran.stojsavljevic(a)gmail.com> wrote: > Hello Gaily, > > Several time here, on Coreboot threads, I wrote the following (regarding > BYT and post ATOM families skus): > > There are two root hub controllers in BYT: USB 3.0 - xHCI and USB 2.0 > (legacy one) - EHCI. The trick here is that you/nobody could not have them > both working at the same time. Either you set/select one, or another. Why? > They are on the different clocking domains. In other words all your USBs > will hang out either of USB 3.0 root hub, either of USB 2.0 root hub. You > could NOT mix outside USB ports (to have them hanging out from both root > hubs mixed). > > To enhance/fix this further, past BYT time, INTEL totally removed from > ATOM silicon (not only) EHCI legacy USB 2.0 root hub, because of that bug. > So, since BSW (including APL-I, former BXT-I), there is ONLY USB 3.0 xHCI > root hub. The (maybe) efficient method is to put on xHCI 3.0 passive Belkin > USB 2.0 bridge as bypass, maybe this can make this transition smooth. Helps > with my HSW notebook, since mine notebook USB 3.0 root hub ports do not > work with my printer USB 2.0 eHCI port, connected straight (with Belkin > does, but on WIN10 OS). > > About IO mapped UART I have no idea, but I think there should be some > (virtual?!) UARTs available. Not sure how this design plays out (certainly, > you should have SW drivers for these for Linux). Have no clue about > GRUB/GRUB2 implementation. > > You might also try USB to UART physical converter, and see if it is > recognized by GRUB2. Does work for Linux. > > Zoran > > On Mon, Mar 20, 2017 at 1:01 PM, Gailu Singh <gailu96(a)gmail.com> wrote: > >> Hi Werner, >> >> Thanks for your detailed clarification. Looks like Intel removing various >> legacy interfaces and support for alternatives is yet to be developed in >> grub. No only they removed USB2.0 altogether, they also removed IO mapped >> UART and we can't get serial console working on this board either with grub. >> >> For USB I am making a last attempt to use PCIE USB2.0 card and ordered >> following from Aliexpress but I have serious doubts if this will work in >> Grub2. Will post the results once I get the cards delivered. >> >> https://www.aliexpress.com/item/Hot-New-Mini-PCI-E-Card-Slot >> -Expansion-to-USB-2-0-Interface-Adapter-Riser-Card/325315080 >> 95.html?spm=2114.13010608.0.0.KTeUNS >> >> >> Thank you very much once again. >> >> On Mon, Mar 20, 2017 at 5:18 PM, Zeh, Werner <werner.zeh(a)siemens.com> >> wrote: >> >>> Hi Gailu. >>> >>> I don't think that one can configure the xHCI to behave like an EHCI so >>> that GRUB2 can natively support it. >>> xHCI has different version number in the PCI space which will prevent >>> the EHCI driver in GRUB2 to use this controller at all. >>> Not speaking about the complete different register set and operational >>> model. >>> >>> What in turn should work is that "some of the BIOS" (which in >>> coreboot-context is the payload like SeaBIOS) will handle all the >>> xHCI stuff and provide a legacy interface to the OS (and here GRUB acts >>> as an OS) to just read mass storage devices using interrupts. >>> >>> Beside that you are lost with GRUB2 and xHCI, sorry! >>> >>> Werner >>> >>> >Hi Experts, >>> > >>> >Does coreboot support USB port initialization in legacy mode on Apollo >>> Lake as some of the BIOS does so that grub or other payloads can use it as >>> USB2.0? >>> > >>> >There is no USB2.0 port on this board and Grub2 doesn't support xhci so >>> we seems to be reaching to a dead end. >>> > >>> >I am trying to see if the dual role USB ports can be initialized in >>> coreboot/fsp so that they can act as USB2.0 for payloads. >>> > >>> >Thanks >>> >> >> >> -- >> coreboot mailing list: coreboot(a)coreboot.org >> https://www.coreboot.org/mailman/listinfo/coreboot >> > >

1 0

Re: [coreboot] Lenovo Thinkpad X201: cannot boot encrypted Debian w/Coreboot & GRUB2
by Sam Kuper 23 Mar '17

23 Mar '17

On 22/03/2017, Sam Kuper <sam.kuper(a)uclmail.net> wrote: > On 22/03/2017, Sam Kuper <sam.kuper(a)uclmail.net> wrote: >> On 22/03/2017, Nico Huber <nico.h(a)gmx.de> wrote: >>> Easiest option seems to be to select CONFIG_MAINBOARD_DO_NATIVE_VGA_INIT >> > 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. I tried again, this time with SeaBIOS instead of GRUB2 as the primary payload, and with CoreInfo as a secondary payload. As above, I selected "Use native graphics initialization" under "Devices" within `make nconfig`. (See attached .config .) The result was the same as above: the backlight came on, but there was nothing displayed on the screen. I do think you are probably right about this issue (i.e. nothing being displayed on the screen) being due to a failure to initialise the graphics properly, and I am open to further attempts to overcome the issue, as my time allows. Is there anyone on the list who has Coreboot working on an X201 who would be willing to share their .config file, so that I might see how they succeeded where I am failing? Thanks!

1 0

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

23 Mar '17

> Current UEFI payload uses an generic emulated variable driver provided in EDK2 MdeModulePkg. Thank you for that info, Maurice. Was looking for this (right entry point) for very long time! :-) Zoran On Thu, Mar 23, 2017 at 1:56 AM, Ma, Maurice <maurice.ma(a)intel.com> wrote: > 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.Rajasekaran(a)dell.com; coreboot(a)coreboot.org; Ma, Maurice < > maurice.ma(a)intel.com>; Agyeman, Prince <prince.agyeman(a)intel.com> > *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-bounces@coreboot.org > <coreboot-bounces(a)coreboot.org>] *On Behalf Of *Sibi.Rajasekaran(a)dell.com > *Sent:* Wednesday, March 22, 2017 6:20 AM > *To:* coreboot(a)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(a)coreboot.org > https://www.coreboot.org/mailman/listinfo/coreboot >

1 0

Re: [coreboot] Maintain boot order for multiple EFI based OS
by Patrick Georgi 23 Mar '17

23 Mar '17

Am 23.03.2017 08:10 schrieb "Matt DeVillier" <matt.devillier(a)gmail.com>: that seems like the kind of functionality it would make sense to handle in an abstracted way (perhaps using libpayload?) How about importing flashrom for this purpose? It has drivers for pretty much everything under the sun as long as it's flash. Patrick

1 0

Re: [coreboot] Maintain boot order for multiple EFI based OS
by Matt DeVillier 23 Mar '17

23 Mar '17

Maurice, that seems like the kind of functionality it would make sense to handle in an abstracted way (perhaps using libpayload?) and let coreboot handle the board-specific flash interface. Has anyone looked into that kind of approach? This is something that's actually been on my to-do list for some time, as the UEFI firmware I build/distribute for ChromeOS devices suffers from the same limitations, which I'd love to eliminate cheers, Matt On Thu, Mar 23, 2017 at 11:26 AM, Ma, Maurice <maurice.ma(a)intel.com> wrote: > 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.Rajasekaran(a)dell.com; coreboot(a)coreboot.org; Ma, Maurice < > maurice.ma(a)intel.com>; Agyeman, Prince <prince.agyeman(a)intel.com> > *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-bounces@coreboot.org > <coreboot-bounces(a)coreboot.org>] *On Behalf Of *Sibi.Rajasekaran(a)dell.com > *Sent:* Wednesday, March 22, 2017 6:20 AM > *To:* coreboot(a)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(a)coreboot.org > https://www.coreboot.org/mailman/listinfo/coreboot >

1 0

Where to buy the KCMA-D8? *brand new*
by Daniel Kulesz 23 Mar '17

23 Mar '17

>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-a… 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

2 1

Re: [coreboot] Maintain boot order for multiple EFI based OS
by Ma, Maurice 23 Mar '17

23 Mar '17

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.Rajasekaran(a)dell.com; coreboot(a)coreboot.org; Ma, Maurice <maurice.ma(a)intel.com>; Agyeman, Prince <prince.agyeman(a)intel.com> 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-bounces@coreboot.org] On Behalf Of Sibi.Rajasekaran(a)dell.com<mailto:Sibi.Rajasekaran@dell.com> Sent: Wednesday, March 22, 2017 6:20 AM To: coreboot(a)coreboot.org<mailto: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

1 0

Re: [coreboot] Maintain boot order for multiple EFI based OS
by Leahy, Leroy P 22 Mar '17

22 Mar '17

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-bounces@coreboot.org] On Behalf Of Sibi.Rajasekaran(a)dell.com Sent: Wednesday, March 22, 2017 6:20 AM To: coreboot(a)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

1 0

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

22 Mar '17

On 22/03/2017, Sam Kuper <sam.kuper(a)uclmail.net> wrote: > On 22/03/2017, Nico Huber <nico.h(a)gmx.de> 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!

1 0

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

22 Mar '17

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

2 1

← Newer
1
...
8
9
10
11
12
13
14
...
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