April 2024 - coreboot - mail.coreboot.org

Windows XP 0xA5 BSoD at IASL_VERSION Address
by Grayson Guarino April 14, 2024

April 14, 2024

Greetings, I am not the most familiar with how Coreboot, SeaBIOS, BIOSes in general, and ACPI work, so forgive me if I am unclear. I am trying to install Windows XP SP3 on a Thinkpad T420 which has been upgraded with an Intel i7-3632QM. I am running Coreboot (commits c4e68f6080/09eb8d0c9b) and SeaBIOS (v1.16.3/commit d239552). I have listed two versions for both Coreboot and SeaBIOS because the former is a sensible recent build of both, while the latter is an attempt to build Coreboot with ACPI 1.0 support (and the latter SeaBIOS commit was chosen as it was made around the same time as the Coreboot commit). It seems like ACPI 1.0 backwards compatibility was dropped at commit be3979c, which could be incorrect. What I am noticing is that regardless of whether I use the newer or older Coreboot build, Windows XP's installer shows a blue screen of death with the following STOP code: [Newer build] STOP: 0x000000A5 (0x00000011, 0x00000008, 0xF794B280, 0x20230628) [Older build] STOP: 0x000000A5 (0x00000011, 0x00000008, 0xF794B280, 0x20200110) Parameter 4 for each of these STOP codes matches the date of the IASL version in both. Do you have any suggestions for how I can further attempt to debug this? I'm struggling to find the release where ACPI v1.0 compatibility was officially dropped, so if it is not 09eb8d0c9b, let me know and I will attempt to rebuild and flash again. Thank you, Grayson

4 5

coreboot Meetings Announcement And Agenda Call
by mina＠coreboot.org April 12, 2024

April 12, 2024

Dear community, We are happy to announce that the next coreboot leadership meeting is scheduled for Wednesday, April 17, 2024. [1] Kindly take a moment to update the current agenda items with matters you wish to see addressed during the meeting. [2] Thank you for your continued commitment to the coreboot project. Best regards, Mina Asante. [1](https://coreboot.org/calendar.html). [2](https://docs.google.com/document/d/1NRXqXcLBp5pFkHiJbrLdv3Spqh1Hu086HYkK….

1 0

BIOS Flashing
by Orion Brewer April 11, 2024

April 11, 2024

Is there a coreboot BIOS flash available for an unknown motherboard in a customized PC? The motherboard is more than 10 years old. If there is a coreboot BIOS flash for it, will it add secure boot and TPM 2.0? -- Disclaimer The information contained in this communication from the sender is confidential. It is intended solely for use by the recipient and others authorized to receive it. If you are not the recipient, you are hereby notified that any disclosure, copying, distribution or taking action in relation of the contents of this information is strictly prohibited and may be unlawful. This email has been scanned for viruses and malware, and may have been automatically archived by Mimecast, a leader in email security and cyber resilience. Mimecast integrates email defenses with brand protection, security awareness training, web security, compliance and other essential capabilities. Mimecast helps protect large and small organizations from malicious activity, human error and technology failure; and to lead the movement toward building a more resilient world. To find out more, visit our website.

2 1

e1000e ULP issue
by Mr. Gadha April 9, 2024

April 9, 2024

Using Maciej Pijanowski's m920q review, I was able to get coreboot booting on a Lenovo m720q. However, I get a strange error in Linux under coreboot. e1000e 0000:00:1f.6 0000:00:1f.6 (uninitialized): Failed to disable ULP There is also a potentially related ACPI complaint: ACPI Error: AE_NOT_FOUND, While resolving a named reference package element - \_SB_.PCI0.IGBE (20230331/dspkginit-438) The gbe Ethernet controller is built in: 00:1f.6 Ethernet controller: Intel Corporation Ethernet Connection (7) I219-V (rev 10) Several other existing boards seem also have I219 devices but I couldn’t find any special handling for this. I'm not familiar with ULP, but it seems the ME could turned it on. I still have the original ME and GBE sections in the flash. Has anyone seen this issue before? Or should I try to add coreboot code to disable ULP in the Ethernet PHY? (seems a bit strange). Thanks!

3 2

Invalid links on GitHub platform
by Ricky Tigg April 8, 2024

April 8, 2024

Hello. At https://github.com/coreboot/coreboot, links https://review.coreboot.org/plugins/gitiles/coreboot/+/HEAD https://review.coreboot.org/coreboot.git are invalid. Regards.

2 1

Pointers in FSP config?
by mr gadha April 8, 2024

April 8, 2024

I've been poking around a bit more on system I'm attempting to port and started doing a detailed comparison between the FSP settings from the stock BIOS and what Coreboot is using. In going through the FSP settings, I'm noticing there are a few pointers to external tables that aren't very well documented. For example, the CoffeeLake FSP has "ChipsetInitBinPtr" / "ChipsetInitBinLen" fields, but their documentation doesn't seem to say anything beyond the names. Couldn't find any other code referencing these. Anybody know what these are?

2 1

[coreboot - Support #534] (New) Enable Ethernet (LAN) on ADL-P Custom Board
by Mahesh Kilumu April 8, 2024

April 8, 2024

Issue #534 has been reported by Mahesh Kilumu. ---------------------------------------- Support #534: Enable Ethernet (LAN) on ADL-P Custom Board https://ticket.coreboot.org/issues/534 * Author: Mahesh Kilumu * Status: New * Priority: Normal * Category: coreboot common code * Target version: 4.21 * Start date: 2024-03-21 ---------------------------------------- Hi, With respect to the Alderlake-P RVP platform designed Custom Board. i have been trying to implement the Ethernet(LAN) on my Custom Board. on RVP intel team used GBE PHY but on my custom board we have used the External Realtek RTL8111H controller over PCIe Root port7 for Ethernet. Below are the configuration details: 1) Devicetree.cb: device ref pcie_rp7 on end # Enable PCH PCIE RP 7 using CLK 6 register "pch_pcie_rp[PCH_RP(7)]" = "{ .clk_src = 6, .clk_req = 6, .flags = PCIE_CLK_LAN }" 2) gpio.c: /* 19: PCIE SRCCLKREQ6- same as RVP */ PAD_CFG_NF(GPP_F19, NONE, DEEP, NF1), /* 2: GPD_2_LAN_WAKE_N- same as RVP*/ PAD_CFG_NF(GPD2, NONE, DEEP, NF1), /* 21 : LAN_ISOLATE# -New Implementation */ PAD_CFG_GPO(GPP_A21, 1, DEEP), from the logs observed that, Root port got enabled ->> [SPEW ] PCI: 00:00:1c.6: enabled 1 But observed the few Error & warnings in the log with respect to the above configuration [WARN ] Missing root port clock structure definition [ERROR] PCI: 00:00:1c.6 missing read_resources full log details : https://pastebin.com/zWcsEZvL -- You have received this notification because you have either subscribed to it, or are involved in it. To change your notification preferences, please click here: https://ticket.coreboot.org/my/account

1 4

2024-04-03 - coreboot Leadership Meeting Minutes
by coreboot org April 6, 2024

April 6, 2024

# 2024-04-03 - coreboot Leadership Meeting Minutes ## Attendees David Hendricks, Werner Zeh, Felix Held, Felix Singer, Jay Talbott, Jon Murphy, Jonathon Hall, Julius Werner, Martin Roth, Matt DeVillier, Maximilian Brune, Nicholas Chin, Philip Molloy, Mina Asante, Nico Huber, Linus Lackner. ## Announcements & Events * OCP Regional Summit: Lisbon, Portugal on April 24–25, 2024 [https://www.opencompute.org/summit/regional-summit] * FOSSY conference: August 1-4 2024 in Portland, Oregon, USA [https://sfconservancy.org/fossy/] * **[Community track proposals](https://sfconservancy.org/fossy/community-tracks) are open until April 18, 2024** * COSCUP - Taipei, Taiwan on 2024/08/03 ~ 2024/08/04 [https://coscup.org/2024/en/landing] * OSFC will be in Bochum Germany - September 3-5, 2024 [https://www.osfc.io/] * **[Call for participation](https://talks.osfc.io/osfc-2024/cfp) is open until May 31st, 2024** * OCP Global Summit: San Jose, California on October 15–17, 2024 [https://www.opencompute.org/summit/global-summit] ## Open Action Items * 2024-03-20 * [Open] Martin: Add a note to the gerrit guidelines to email the leadership. * 2024-03-06 * [Open] Martin: To update documentation on gerrit contributing guidelines. * https://doc.coreboot.org/contributing/index.html * 2024-01-10 * [Open] Werner: Push patch based on https://ticket.coreboot.org/issues/522 * Nico: https://review.coreboot.org/q/topic:enforce_region_api * [Open] Daniel: Look at how we want to localize (non console) strings for coreboot. Long term project. ## Minutes ### [Martin] Handle GOP drivers * How do we intend to handle GOP driver init going forward? Do we know what graphics card manufacturers are planning? (when) will we lose legacy option rom support on external graphics cards? Currently the option rom is specified by the PCI specification, so maybe we don’t need to worry. I’m thinking we could look at something modular, like yabel or x86emu currently do for the legacy option roms. * Graphics card manufacturers often support both UEFI and legacy option ROM init. They may get rid of legacy option ROMs at some point... * coreboot may need to implement a wrapper for a few calls needed. * Martin has a list of what needs to be supported for the AMD GOP driver. ### [Martin] [CVE-2024-3094](https://nvd.nist.gov/vuln/detail/CVE-2024-3094) liblzma build compromise * The liblzma vulnerability did not impact coreboot source, but it did affect our build server images. Something similar could be done to coreboot to introduce some sort of vulnerability into the codebase. What do we need to do to help protect the coreboot codebase against similar attacks? * Isolate test targets in makefiles from normal builds? * Move all binaries out of the coreboot tree? * Relocating binaries probably won't help. * Julius: liblzma had a few issues that helped obfuscate the problem, such as using autoconf and automake that generate unreadable Makefiles. * Get rid of release tarballs? * [https://coreboot.org/downloads.html] * The vulnerability was injected into the release tarballs. coreboot has reproducible builds, so is there a purpose for having tarballs? * Werner: Having the source tarballs is useful in his case. * Corporate release processes make it difficult to point at a source code repo. Much easier to just point at a release tarball with everything needed. * Tarballs themselves are not reproducible. This can depend on things like the version of `tar` installed. * [reproducible-builds.org] has some suggestions on how to fix this. ### [Martin] Gitiles is still disabled * It was disabled since a web crawler was hitting it with a lot of requests, causing a lot of traffic and CPU utilization, and ultimately DOS'ing Gerrit. * What do we want to do until it’s re-enabled? * Should we just re-enable it now, blocking user-agents for known web-crawlers and see how things go? * Main advantage is that you click on a hash in Gerrit and it brings you to the source code. * We can't block IP addresses, but we can block user-agents. * FelixS has volunteered to work on this. ### [Werner][https://review.coreboot.org/c/coreboot/+/69159] * TPM patch was merged that breaks timeless builds somehow. .text and another section end up overlapping other sections. * This might need a recent patch to increase bootblock size. * [https://review.coreboot.org/c/coreboot/+/80348] <-- only applies to AMD right now. * Why was this not caught by Jenkins? * It depends on the configuration, and only breaks if TPM is enabled # Next meeting * April 17, 2024. * [coreboot Calendar](https://coreboot.org/calendar.html). # Notice * Decisions shown here are not necessarily final, and are based on the current information available. If there are questions or comments about decisions made, or additional information to present, please put it on the leadership meeting agenda and show up if possible to discuss it. Of course items may also be discussed on the mailing list, but as it's difficult to interpret tone over email, controversial topics frequently do not have good progress in those discussions. For particularly difficult issues, it may be best to try to schedule another meeting. # coreboot leadership meeting minutes [2024-04-03](https://docs.google.com/document/d/1NRXqXcLBp5pFkHiJbrLdv3Spqh1….

1 0

[coreboot - Bug #533] (New) T440p audio mute button and fan control not working
by frantic from xboot April 6, 2024

April 6, 2024

Issue #533 has been reported by frantic from xboot. ---------------------------------------- Bug #533: T440p audio mute button and fan control not working https://ticket.coreboot.org/issues/533 * Author: frantic from xboot * Status: New * Priority: Normal * Target version: master * Start date: 2024-03-07 * Affected versions: master * Affected hardware: Lenovo Thinkpad T440p * Affected OS: All Linux distributions ---------------------------------------- In recent coreboot versions, the audio mute button and fan control has stopped working. Whereas you use the same revision from Libreboot, it all works fine and smoothly. This leads me to suspect that someone changed someone without testing, which is real annoying. The audio mute button technically still functions, but the LED no longer turns on/off. Always just off. Fan control no longer works with Thinkfan. /proc/acpi/ibm/fan doesn't exist any more. I've tried "force loading" thinkpad_acpi, but it doesn't work. -- You have received this notification because you have either subscribed to it, or are involved in it. To change your notification preferences, please click here: https://ticket.coreboot.org/my/account

3 14

Coreboot - NY NOW 2024
by Constance Brown April 4, 2024

April 4, 2024

Hello, I trust you're in good health. Are you in the market for an event visitor database. Here's a sneak peek at what we have: NY NOW 2024 : 40714 Contacts If you're interested, I'd be happy to provide you the value & other information. Awaiting your response. Best regards. Constance Brown - Marketing Specialist Unsubscribe<mailto:constance.brown@exposforge.info?subject=Unsubscribe%20588F721D%2DF347%2D40B6%2DAE5F%2DEB5830FB9E2C&body=Please%20don%27t%20change%20the%20email%20content%20and%20send%20this%20email%20to%20unsubscribe.%0D%0A%0D%0Acoreboot@coreboot.org>

1 0