coreboot April 2020

coreboot@coreboot.org

39 participants
36 discussions

Re: Some problems with graphic display when using coreboot + seabios.
by Dalao 19 Apr '20

19 Apr '20

> SeaBIOS is a legacy BIOS implementation, so no it can't boot UEFI boot media. Likewise, Tianocore is a pure UEFI implementation, and doesn't boot legacy boot media / legacy installed OSes. There should be a way to use SeaBIOS as a CSM for Tianocore, but currently it's not working / not implemented (I tried briefly awhile back but didn't have any luck). I tried to follow the steps to build tianocore for SeaBIOS https://www.coreboot.org/TianoCore But I get these errors. It says it can't found nmake.exe... Is this should be build on Windows? How to setup the environment? [dalao@pc tianocore2018]$ git clone --branch UDK2018 https://github.com/tianocore/edk2 Cloning into 'edk2'... remote: Enumerating objects: 66, done. remote: Counting objects: 100% (66/66), done. remote: Compressing objects: 100% (43/43), done. remote: Total 342725 (delta 35), reused 31 (delta 23), pack-reused 342659 Receiving objects: 100% (342725/342725), 286.48 MiB | 436.00 KiB/s, done. Resolving deltas: 100% (247240/247240), done. Updating files: 100% (15636/15636), done. [dalao@pc tianocore2018]$ cd edk2/ [dalao@pc edk2]$ cd BaseTools [dalao@pc BaseTools]$ export EDK_TOOLS_PATH=$(pwd) [dalao@pc BaseTools]$ cd ../ [dalao@pc edk2]$ . ./edksetup.sh BaseTools WORKSPACE: /home/dalao/T440pCorebooting/tianocoreAsSeabiosPayload/tianocore2018/edk2 EDK_TOOLS_PATH: /home/dalao/T440pCorebooting/tianocoreAsSeabiosPayload/tianocore2018/edk2/BaseTools CONF_PATH: /home/dalao/T440pCorebooting/tianocoreAsSeabiosPayload/tianocore2018/edk2/Conf Copying $EDK_TOOLS_PATH/Conf/build_rule.template to /home/dalao/T440pCorebooting/tianocoreAsSeabiosPayload/tianocore2018/edk2/Conf/build_rule.txt Copying $EDK_TOOLS_PATH/Conf/tools_def.template to /home/dalao/T440pCorebooting/tianocoreAsSeabiosPayload/tianocore2018/edk2/Conf/tools_def.txt Copying $EDK_TOOLS_PATH/Conf/target.template to /home/dalao/T440pCorebooting/tianocoreAsSeabiosPayload/tianocore2018/edk2/Conf/target.txt [dalao@pc edk2]$ build -p DuetPkg/DuetPkgIa32.dsc Build environment: Linux-5.4.22-1-MANJARO-x86_64-with-glibc2.2.5 Build start time: 11:48:18, Mar.15 2020 WORKSPACE = /home/dalao/T440pCorebooting/tianocoreAsSeabiosPayload/tianocore2018/edk2 ECP_SOURCE = /home/dalao/T440pCorebooting/tianocoreAsSeabiosPayload/tianocore2018/edk2/EdkCompatibilityPkg EDK_SOURCE = /home/dalao/T440pCorebooting/tianocoreAsSeabiosPayload/tianocore2018/edk2/EdkCompatibilityPkg EFI_SOURCE = /home/dalao/T440pCorebooting/tianocoreAsSeabiosPayload/tianocore2018/edk2/EdkCompatibilityPkg EDK_TOOLS_PATH = /home/dalao/T440pCorebooting/tianocoreAsSeabiosPayload/tianocore2018/edk2/BaseTools CONF_PATH = /home/dalao/T440pCorebooting/tianocoreAsSeabiosPayload/tianocore2018/edk2/Conf POSTBUILD = /home/dalao/T440pCorebooting/tianocoreAsSeabiosPayload/tianocore2018/edk2/DuetPkg/PostBuild.bat -p DuetPkg/DuetPkgIa32.dsc -b DEBUG -a IA32 -t MYTOOLS --conf=/home/dalao/T440pCorebooting/tianocoreAsSeabiosPayload/tianocore2018/edk2/Conf all Architecture(s) = IA32 Build target = DEBUG Toolchain = MYTOOLS Active Platform = /home/dalao/T440pCorebooting/tianocoreAsSeabiosPayload/tianocore2018/edk2/DuetPkg/DuetPkgIa32.dsc Flash Image Definition = /home/dalao/T440pCorebooting/tianocoreAsSeabiosPayload/tianocore2018/edk2/DuetPkg/DuetPkg.fdf Processing meta-data ......... done! Building ... /home/dalao/T440pCorebooting/tianocoreAsSeabiosPayload/tianocore2018/edk2/MdePkg/Library/BasePcdLibNull/BasePcdLibNull.inf [IA32] Building ... /home/dalao/T440pCorebooting/tianocoreAsSeabiosPayload/tianocore2018/edk2/MdePkg/Library/BaseDebugLibNull/BaseDebugLibNull.inf [IA32] Building ... /home/dalao/T440pCorebooting/tianocoreAsSeabiosPayload/tianocore2018/edk2/MdePkg/Library/BaseMemoryLib/BaseMemoryLib.inf [IA32] /bin/sh: Vcbinnmake.exe: command not found build.py... : error 7000: Failed to execute command Vc\bin\nmake.exe /nologo tbuild [/home/dalao/T440pCorebooting/tianocoreAsSeabiosPayload/tianocore2018/edk2/Build/DuetPkgIA32/DEBUG_MYTOOLS/IA32/MdePkg/Library/BasePcdLibNull/BasePcdLibNull] build.py... : error 7000: Failed to execute command Vc\bin\nmake.exe /nologo tbuild [/home/dalao/T440pCorebooting/tianocoreAsSeabiosPayload/tianocore2018/edk2/Build/DuetPkgIA32/DEBUG_MYTOOLS/IA32/MdePkg/Library/BaseDebugLibNull/BaseDebugLibNull] build.py... : error 7000: Failed to execute command Vc\bin\nmake.exe /nologo tbuild [/home/dalao/T440pCorebooting/tianocoreAsSeabiosPayload/tianocore2018/edk2/Build/DuetPkgIA32/DEBUG_MYTOOLS/IA32/MdePkg/Library/BaseMemoryLib/BaseMemoryLib] build.py... : error F002: Failed to build module /home/dalao/T440pCorebooting/tianocoreAsSeabiosPayload/tianocore2018/edk2/MdePkg/Library/BasePcdLibNull/BasePcdLibNull.inf [IA32, MYTOOLS, DEBUG] - Failed - Build end time: 11:48:28, Mar.15 2020 Build total time: 00:00:10 [dalao@pc edk2]$ > Personally, given that it's 2020, I'd not bother with legacy-installed OSes (or SeaBIOS) outside of use with emulation or if a special use case demands it. Esp given that it's easy enough to migrate Windows from legacy to UEFI. I tried the tianocore payload by selecting it and using all default settings. But I can't see anything like the SeaBIOS for me to select the boot media. But it does boot the archlinux in UEFI mode. I'm wondering is this the problem with my display (I have tried both "Use libgfxinit" and "Run VGA Option ROMs" with tianocore) or the tianocore has nothing to display to select boot media? Mar 15, 2020, 10:08 by matt.devillier(a)gmail.com: > On Sat, Mar 14, 2020 at 8:33 PM Dalao via coreboot > <coreboot(a)coreboot.org> wrote: > >> >> >> I have just corebooted T440p. Then I noticed some graphic display problems... >> >> Firstly I "Use libgfxinit" with "Legacy VGA text mode", insert a usb disk with archlinux's latest install image iso. I can see a text mode of archlinux's start screen. >> >> https://imgur.com/0QqQgJn >> >> But when I hit enter, it shows some log till "Triggering uevents" and then there is no display... >> >> https://imgur.com/CHI9jeE >> >> Then I tried "Use libgfxinit" with "Linear "high-resolution" framebuffer". I can see the graphic mode of archlinux's start screen, but again after I hit enter and see some logs, there is no display... Also, the display is not ideal, just at the top left corner not full screen. >> >> https://imgur.com/dvYLERu >> >> Also, under this setting, the nvramcui's display becomes bad. >> >> https://imgur.com/7YG0kOX >> > > unfortunately, many legacy bootloaders seem to assume a full array of > VESA video modes will be available, and fail less than gracefully when > that's not the case. With libgfxinit there is no ability to change > video modes -- all that's available is either the native panel > resolution (high resolution framebuffer) or VGA text mode. > >> Next I included pci8086,0416.rom vbios and tried "Run VGA Option ROMs" with "Legacy VGA text mode". This time, I can't see the archlinux start screen as shown above, there is no display at the beginning. But I can hit the enter blindly. Then after a while I can see archlinux is booting and the first line I can see is "Probing EDD (edd=off to disable)...ok" the archlinux starts ok. >> >> Lastly I also tried "Run VGA Option ROMs" with "Set framebuffer graphics resolution" with the default "framebuffer graphics resolution (1024x768 16.8M-color (8:8:8))" (although my T440p's resolution is 1920x1080). Also the Framebuffer mode is changed to "VESA framebuffer". I still can't see archlinux's start screen... >> >> >> How to make everything work like the vendor BIOS? i.e., I can see both the archlinux's start screen and it's booting. >> > > add the VGA BIOS. set the PCI IDs correctly. Set coreboot display init > to none, and let SeaBIOS run the VBIOS. > >> How to fix the nvramcui under "high-resolution" framebuffer"? >> > > will work properly with above settings > >> Also, as for now it appears seabios can't boot UEFI media. Tianocore by default can't boot Linux/Windows installed by legacy method (installed when using seabios). my goal is to add UEFI support through tianocore as seabios payload (or through tianocore's CSM compatibility support module? ). So that it can boot both UEFI installed Windows or legacy installed Windows like the vendor bios can do. How to achieve this? >> > > SeaBIOS is a legacy BIOS implementation, so no it can't boot UEFI boot > media. Likewise, Tianocore is a pure UEFI implementation, and doesn't > boot legacy boot media / legacy installed OSes. There should be a way > to use SeaBIOS as a CSM for Tianocore, but currently it's not working > / not implemented (I tried briefly awhile back but didn't have any > luck). > > Personally, given that it's 2020, I'd not bother with legacy-installed > OSes (or SeaBIOS) outside of use with emulation or if a special use > case demands it. Esp given that it's easy enough to migrate Windows > from legacy to UEFI. > >> >> _______________________________________________ >> coreboot mailing list -- coreboot(a)coreboot.org >> To unsubscribe send an email to coreboot-leave(a)coreboot.org >> > _______________________________________________ > coreboot mailing list -- coreboot(a)coreboot.org > To unsubscribe send an email to coreboot-leave(a)coreboot.org >

5 10

[gerrit] Impossible to delete some of the ancient changes
by Mike Banon 17 Apr '20

17 Apr '20

i.e. would like to remove the worthless & abandoned 17439 , 17505 , 17506 , 17507 changes I have done at 2016 year (this work has been eventually merged, so nothing of a value will be lost) - but a Delete button for them is not available. Best regards, Mike Banon

1 0

OCP blog for coreboot on server
by Jonathan Zhang 16 Apr '20

16 Apr '20

Thanks for the coreboot community for providing a strong technology foundation and continuous support, coreboot support for servers powered by Intel Xeon-SP processors is becoming a reality: https://www.opencompute.org/blog/linux-firmware-boots-up-server-powered-by-… . We look forward to further collaboration with you! "For my ally is the Force, and a powerful ally it is." Thank you, Jonathan

1 0

T530 with discrete GPU
by David Hobach 13 Apr '20

13 Apr '20

Hi all, did anyone get the discrete GPU working on a T530 with coreboot? All I got so far was a blank screen when trying to switch to "Discrete Only" with nvramtool. With "Integrated Only" it doesn't even show up in lspci. Interestingly, both showed up on the first reboot after the "Discrete Only" change, but the blank screen happened after the first full shutdown. Hardware... The main problem there: Without dGPU support, the external display port on a T530 docking station is not driven at all - it is hardwired to the GPU, if present. So when buying one of those, it actually hurts to have a dGPU. Best Regards David

1 0

OpenBSD won't install on an x220 Thinkpad with Coreboot
by Robert Milton 12 Apr '20

12 Apr '20

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 OpenBSD.

4 4

Re: OpenBSD won't install on an x220 Thinkpad with Coreboot
by Moises Simon 11 Apr '20

11 Apr '20

Hi, I'm runinng coreboot 4.7 without any problems on OpenBSD. I have compiled 4.9 and master and both have the same problem for the hci devices. On GNU/Linux I have experience inestability and lock ups. I'm running with full ME. Something must have be broken between 4.7 and 4.9 (I haven't been able to build 4.8.1, still trying). Hope someone has any solution or knowns what is happening. regards

1 0

Quick Boot: A Guide for Embedded Firmware Developers, 2nd Edition
by Ivan Ivanov 10 Apr '20

10 Apr '20

Finally we found this great rare book after many hours of searching, and would like to share it with you friends. Hope you would find it interesting. Enjoy! https://github.com/informer2016/Quick_Boot-_A_Guide_for_Embedded_Firmware_D… Wish you all the best, and thank you so much for your kind help

1 0

Re: DRI_PRIME on G505s with enabled dGPU?
by Mike Banon 10 Apr '20

10 Apr '20

On Sun, Mar 15, 2020 at 8:46 AM Matt B <matthewwbradley6(a)gmail.com> wrote: > > Hi, > > Thanks for the info on DRI_PRIME. I'm looking at doing a motherboard+cooler swap. > > Have you run battery life tests with/without the dGPU hidden? > Isn't NVRAM the "correct" way to do it? > > -Matt > > On Wed, Mar 11, 2020 at 11:24 AM Mike Banon <mikebdp2(a)gmail.com> wrote: >> >> On Sun, Mar 8, 2020 at 6:56 PM Matt B <matthewwbradley6(a)gmail.com> wrote: >> > >> > To those who have a dual-GPU G505s and have enabled the recent support for the dGPU, does DRI_PRIME GPU offloading work? >> > >> >> Yes, DRI_PRIME GPU offloading works on G505S - and actually I think >> it's the only possible way of using a discrete GPU on this coreboot'ed >> laptop at the moment. However, it's usefulness really depends on your >> software and how fast is the integrated GPU's RAM: you may have >> 1600MHz CL9 RAM modules installed, while a discrete GPU's own soldered >> chips are i.e. 1333MHz CL9 only. I recommend testing them side by side >> in all the programs you care about and remember which one is better in >> what cases. >> >> > >> > Could here be an option created to enable/disable the dGPU at boot time without recompiling? >> > >> >> If there could be a real benefit from doing so (does it consume less >> power if you "hide it" from your system by disabling a PCI bus?), such >> a way could be implemented - however, I don't know how to do it >> without using NVRAM (which I would like to avoid for various reasons) Ideally I prefer a laptop as stateless as possible at least regarding the BIOS - and also, at least some G505S laptops seem to have a broken NVRAM (strong freeze on a write attempt to NVRAM and laptop doesn't turn on until a full motherboard discharge). A10-5750M TDP is 35W, after looking at the similar CPUs from this table - https://www.eteknix.com/amd-kaveri-a10-7850k-overclocking-analysis/7/ , it seems that: Idle | GPU load | CPU+GPU load 15.6W | 23.66W | 35W 44.5% | 67.6% | 100% And "where the ACPI VFCT Table is missing, Power States may not work properly" - so a constant iGPU load, caused by the missing ACPI VFCT for iGPU in our case, adds about 8W to power consumption ~ about 12% less battery life. HD 8570M or R5 M230 might be 20W TDP at max load (hard to find exact info), but its' ACPI VFCT table is loaded by coreboot, so a power consumption difference shouldn't be as big. Currently I'm trying to add the XMP profiles support ( see https://review.coreboot.org/c/coreboot/+/40291 ) so it could take me a while to return to this research.

1 0

sb/intel/bd82x6x/ remapping oddities (was Re: ThinkPad T420 and FireWire chip on Linux)
by Nico Huber 10 Apr '20

10 Apr '20

On 09.04.20 02:04, Peter Stuge wrote: > I found something that might be relevant in https://del.dog/raw/cbmemlog > however, search it for Remap: > > --8<-- https://del.dog/raw/cbmemlog#149 > PCI: 00:1c.0: Disabling device > PCI: 00:1c.0: check set enabled > PCH: Remap PCIe function 1 to 0 That's a weird puzzle. I've looked into the code, it's not mapping _to_ a specific number but swapping _with_ what was there last. So if the mapping was: idx 0 1 2 3 4 5 6 7 fn 0 1 2 3 4 5 6 7 this swaps what is at 0 with what is at 1: idx 0 1 2 3 4 5 6 7 fn 1 0 2 3 4 5 6 7 > PCI: 00:1c.1 [8086/1c12] enabled > PCI: 00:1c.2: Disabling device > PCH: Remap PCIe function 3 to 0 Swaps what is at 3 with what is at 0: idx 0 1 2 3 4 5 6 7 fn 3 0 2 1 4 5 6 7 > PCI: 00:1c.3 [8086/1c16] enabled > PCH: Remap PCIe function 4 to 0 Swaps what is at 4 with what is at 0: idx 0 1 2 3 4 5 6 7 fn 4 0 2 1 3 5 6 7 idx 1, 3 and 4 are on in the devicetree. So final relevant state: idx 0 1 2 3 4 5 6 7 fn 0 1 3 This is not wrong. But the algorithm is that complex because it's supposed to leave no gaps. And it fails at that in this case :-/ > --8<-- https://del.dog/raw/cbmemlog#175 > PCI: Leftover static devices: > PCI: 00:01.0 > PCI: 00:16.1 > PCI: 00:16.2 > PCI: 00:16.3 > PCI: 00:1c.4 > PCI: 00:1c.2 > PCI: 00:1c.5 > PCI: 00:1c.7 > PCI: Check your devicetree.cb. > -->8-- Partially my fault, when we added these messages, we didn't consider devices that were hidden on purpose. I guess we should not complain about devices on bus 0 with !dev->enabled (i.e. `off` in the device- tree). But here seems also something fishy wrt. the remapping: What about 1c.6? Nico

1 0

TPM in QEMU
by Matt Judell 10 Apr '20

10 Apr '20

Hi all, It looks like QEMU supports TPM emulation via swtpm. The KConfig menu for the QEMU "boards" doesn't allow us to toggle TPM support as it does for say, the Chell board. Are there any blockers that would prevent the use of emulated TPM for QEMU "boards"? My apologies if this is a silly question, I'm a little out of my depth here. Best, Matt

2 1

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

2003

2002

coreboot April 2020