September 2024 - coreboot - mail.coreboot.org

Re: Could not find a bounce buffer... Payload not loaded. Intel 440BX/LX Board
by Branden Waldner Sept. 22, 2024

Sept. 22, 2024

Hi Christian, Both Keith Hei and I [Branden] have 440BX boards that still run up-to-date/recent coreboot (though they do need a bit of work). I also have an Intel 440LX board [Trigem Florida-TG (COGNAC)] that I was intending on trying to get coreboot to run on yet, but I wanted to get it reworked at the local maker/hackerspace to socket the flash chip which I haven't been able to get done. From old messages on the mailing list, it looked like the 440BX code did run on the 440LX and I have had it run at 66MHz fsb speed on the 440BX. Though maybe the memory settings could be an issue if the ram is rated for faster than the [older] chipset can handle (I'm not sure about the details of it)? I probably can't help much though and Keith has been working on a Haswell board recently, so I'm not sure how much time he has had to work on the older boards. I just figured I make sure to mention it at least. Branden PS Necroware on Youtube / scorp on Vogons forum has the same board as you [in the video: Too nice to be true? Intel i440LX was upset about my plans] and has expressed interest in open source works, so maybe he might be interested as well? I haven't tried messaging him about it.

2 1

Gerrit Gitiles is back - for now
by Felix Singer Sept. 20, 2024

Sept. 20, 2024

I've just enabled Gitiles again. We will observe which effect this has on Gerrit now. Fingers crossing that it won't cause a high load anymore :) Felix

3 4

2024-09-18 - coreboot Leadership Meeting Minutes
by mina＠coreboot.org Sept. 19, 2024

Sept. 19, 2024

# 2024-09-18 - coreboot Leadership Meeting ## Attendees Ron Minnich, Felix Singer, Julius Werner, Felix Held, Matt DeVillier, Nico Huber,Jon Murphy, Werner Zeh, David Hendricks, Mina Asante. ## Announcements & Events * OCP Global Summit: San Jose, California on October 15–17, 2024 https://www.opencompute.org/summit/global-summit ## Open Action Items * 2024-09-18 * Jon: Schedule a dedicated meeting to discuss the Coverity defects and action plan. * Werner: Send out invitations for this meeting. * 2024-05-01 * Nick Van Der Harst volunteered for Dutch. "gogo gogo" would like to translate to Russian (?) * 2024-01-10 * Nico:(https://review.coreboot.org/q/topic:enforce_region_api) * Daniel: Look at how we want to localize (non console) strings for coreboot. Long term project. ## Minutes ### [Martin] How do we want to handle code written with copilot or other AI tools. * We don’t currently have a policy, and it seems like we should. * [Matt] Code generated by AI is not copyrightable. Submitters should stay responsible for their code, regardless how it was created. * [David] Would be polite if the author mentions in the commit message that AI was used to create (parts) of the code. Still DCO should cover the legal parts of this discussion. Therefore, we do not need a dedicated policy for that. * [David] We should try to leverage AI possibilities in our project. As Bryan @ Oxide observed, open source code are by nature documented better than proprietary firmware (as far as LLM training goes) and this can be an advantage of coreboot. * [Nico] Can this make it easier to violate the DCO using AI? Should we try to improve the awareness in the community? * [Matt] The AI can spit out license-incompatible code and this way could make it into coreboot’s code base. * [Matt] Update the DCO to include that the comitter has to ensure that the added code from AI is compliant to our license. * [David] Are there filters available at the AI side to ensure output is license compatible? * [Julius] We could ask the SFC for help from the legal standpoint →[David](mailto:david.hendricks@gmail.com) will ask ### [jpmurphy] What are the coreboot projects goals? * Individuals and companies have their own goals. Do we have wider goals from the project’s point of view? * [David] This is a huge topic. Should we start a doc and just collect things there? * [Ron] Initial goals of linuxbios were: maintainability, security reliability * Goal was to have computers shipped with coreboot, not to retrofit machines like buying a Wintel PC and installing Linux on it. * [Werner] Get adoption by big vendors earlier, the rest will fall into it. * [Nico] For an early vendor adoption, we need to be able to boot into Windows as a first class citizen * [FelixH] UEFI way of booting an OS is de facto standard in the client space. We could counter this with EDK 2 but somebody should take the time to work on this. * [David] There are a number of different solutions to boot Windows (Universal Payload, EDK 2, Yabits and Rust Hypervisor (Akira's projects)), has somebody had a closer look? If the goal is to boot into EDK2, why bother with coreboot at all? * [David] Multiple architectures and boards in a single codebase - LinuxBIOS started with PPC, Alpha, and x86. Support for ARM helped get Intel to support coreboot. EDK2 is a fork-per-product sort of deal. * [Werner] We should continue the task of re-building coreboot’s webpage. Gather all the requirements and reach out to some company that can do the work based on our requirements. Preserve a section in this webpage where real uses-cases can be added to to make coreboot’s use cases popular. * [FelixH] Simplified architecture, not bloated like EDK2 with its dispatcher, dynamic module loading, etc. ### [jpmurphy] How do we want to manage a roadmap? * Can we start a draft of a roadmap to at least start gathering a list of features/tech debt and their priorities? * [FelixH] Writing up a roadmap does not mean the features will be implemented. Who will make sure that we stick to the planned roadmap? * [Jon] We should have at least a list gathered so that we can plan * [FelixS] We have too many communication channels, keeping track can be quite challenging. * [Werner] Use a kanban board to publish and track progress of features? * Better look/feel than tickets. * [Werner] The coreboot project has a few different communication channels around (mailing list, Slack, Matrix, IRC, Google docs, Discord) All our discussions happen spreaded among those and there is no central place (accepted by all community members) where decisions are written down. * Mailing list seems suitable as it has an archive but some people opted out due to heated discussions and other issue we had in the past. * Google docs could be one place but unfortunately not every community member likes them. In addition, despite the meeting minutes, there is no “official” document where centric decisions are written down, one has to search in the archive to find things. * Slack/Matrix are not used by everyone. * IRC is not suitable for such things as well. * Would a kanban-style board be something we like to have a look into for such things? I know, ranting about too many communication channels and then adding another one isn’t the best move. But still, let us at least discuss. * Possible open source boards we can have a look at: (https://kanboard.org/) and (https://wekan.github.io/) It might be easier to maintain a feature roadmap this way, IMHO. And we can host it on coreboot.org to have full control over it. * [FelixS] I suggest using [forgejo for kanban boards](https://forgejo.org/docs/latest/user/project/) instead, since I’ve suggested it as an issue tracker before and it got positive feedback. Both, issues and kanban, are very well integrated. So we reduce the number of services. ### [jpmurphy] We get coverity results for free from synopsis. At the time of writing, there are 705 outstanding defects. Do we have a plan for burning these down? * (https://scan.coverity.com/projects/coreboot)? * Can we set a bar to burn these down by a certain date, and then moving forward we require that the defect count is 0 prior to releases? * [FelixH] Can we export the coverity results and show them in a coreboot-driven dashboard so that everybody can have access? * [Jon] Set up a dedicated meeting to discuss this? * [Werner] I can send out an invite to discuss this. ### [jpmurphy] I opened a bug within Google to update our best practices on bugs being used with coreboot. There are at least two options, asking for feedback/alternatives: * 1. Use a public component that everyone can see accessible at <code>(https://issuetracker.google.com/)</code> * Some bugs will still need to stay private to protect business needs and may create the need for secondary bugs. For this reason, some Googlers prefer we not use this approach. * 2. Instead of using BUG=b: fields within commit messages, googlers could use a different ID to make it more clear it’s a Google bug. Felix S had suggested ChromeOS-Bug-Id. # Next Leadership Meeting * October 2,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.

1 0

Announcement: Introducing UEFI Capsule Update Integration for coreboot with EDK II
by Beata Skierka Sept. 18, 2024

Sept. 18, 2024

Hello, We are pleased to announce the launch of a project by 3mdeb aimed at integrating UEFI Capsule Update for coreboot with EDK II as a payload. This initiative aims to bring the capsule-based update method, providing an alternative to the traditional flashrom-based method, which becomes more and more difficult to implement, due to the restricted OS-level access to the firmware storage. One of the main goals is also to ease the integration and firmware update deployments via the fwupd for devices running open-source firmware (based on coreboot + EDK II). For a detailed project outline, please visit our Dasharo documentation [1]. We are looking for feedback through comments on this thread or via the built-in discussion module on the website. Although the project plan has been already accepted by the NLnet Foundation, there may be still some room for justified changes. You can track project's progress via the GitHub Project [2]. Your feedback and participation would be much appreciated. We welcome your involvement in discussions, reviewing, and testing. You might already have seen some first patches as a results of this project getting started, such us: - https://review.coreboot.org/c/coreboot/+/82247 - https://review.coreboot.org/c/coreboot/+/82248 - https://review.coreboot.org/c/coreboot/+/82249 - https://review.coreboot.org/c/coreboot/+/82610 We acknowledge and appreciate the funding support from the NLnet Foundation. [1] https://docs.dasharo.com/projects/capsule-updates/ [2] https://github.com/orgs/Dasharo/projects/7/views/1 Best regards, Beata Skierka Project Manager https://3mdeb.com | @3mdeb_com

8 18

coreboot Meetings Announcement And Agenda Call
by mina＠coreboot.org Sept. 16, 2024

Sept. 16, 2024

Dear coreboot community, Please be reminded that our leadership meeting is scheduled for Wednesday, September 18, 2024.[1] Kindly review the current agenda and share your thoughts or suggest additional items you would like to see discussed during the meeting.[2] Thank you. ## Current Agenda ### [Martin] How do we want to handle code written with copilot or other AI tools. * We don’t currently have a policy, and it seems like we should. * [jpmurphy] What are the coreboot projects goals? * [jpmurphy] How do we want to manage a roadmap? * Can we start a draft of a roadmap to at least start gathering a list of features/tech debt and their priorities? * [jpmurphy] Have we solicited or received feedback on why organizations choose not to use coreboot? * Have we solicited or performed technical analysis of how we compare to other solutions or what features may be missing? * [jpmurphy] How do we utilize the OSFF to obtain NDA’s with SoC vendors and provide early silicon support? * [jpmurphy] I opened a bug within Google to update our best practices on bugs being used with coreboot. There are at least two options, asking for feedback/alternatives: * 1. Use a public component that everyone can see accessible at <code>(https://issuetracker.google.com/)</code> * <code>Some bugs will still need to stay private to protect business needs and may create the need for secondary bugs. For this reason, some Googlers prefer we not use this approach.</code> * <code>2. Instead of using BUG=b: fields within commit messages, googlers could use a different ID to make it more clear it's a Google bug. Felix S had suggested ChromeOS-Bug-Id</code> * <code>[jpmurphy] We get coverity results for free from synopsis. At the time of writing, there are 705 outstanding defects. Do we have a plan for burning these down?</code> * <code>(https://scan.coverity.com/projects/coreboot)?</code> * <code>Can we set a bar to burn these down by a certain date, and then moving forward we require that the defect count is 0 prior to releases?</code> ### [Werner] The coreboot project has a few different communication channels around (mailing list, Slack, Matrix, IRC, Google docs) All our discussions happen spreaded among those and there is no central place (accepted by all community members) where decisions are written down. * Mailing list seems suitable as it has an archive but some people opted out due to heated discussions and other issue we had in the past * Google docs could be one place but unfortunately not every community member likes them. In addition, despite the meeting minutes, there is no “official” document where centric decisions are written down, one has to search in the archive to find things * Slack/Matrix are not used by everyone * IRC is not suitable for such things as well In addition, I agree with jmurphy’s points above, we do not have a plan for a roadmap. Would a kanban-style board be something we like to have a look into for such things? I know, ranting about too many communication channels and then adding another one isn’t the best move. But still, let us at least discuss. Possible open source boards we can have a look at:(https://kanboard.org/) and (https://wekan.github.io/) It might be easier to maintain a feature roadmap this way, IMHO. And we can host it on coreboot.org to have full control over it. ## Announcements & Events * OCP Global Summit: San Jose, California on October 15–17, 2024 https://www.opencompute.org/summit/global-summit

1 0

[coreboot - Bug #563] (New) tty doesn't show on external display using edk2 on W530
by Simon Dominic Sept. 16, 2024

Sept. 16, 2024

Issue #563 has been reported by Simon Dominic. ---------------------------------------- Bug #563: tty doesn't show on external display using edk2 on W530 https://ticket.coreboot.org/issues/563 * Author: Simon Dominic * Status: New * Priority: Normal * Target version: none * Start date: 2024-09-16 * Affected hardware: Lenovo ThinkPad W530 * Affected OS: Debian 12 ---------------------------------------- I use the w530 (with Debian 12 + edk2), but this may also be happening with other thinkpads. When I connect to external displays and turn on, while the graphical environment shows as normal, the tty or anything not graphical doesn't show. This includes anything prior to the graphical display manager (such as lightdm). For example, when LUKS asks for the password for my encrypted drive. (The GRUB screen also doesn't show, but I can't recall if this was already the case with the stock bios. It also never showed with SeaBIOS, so maybe so). With SeaBIOS, the tty etc. *does* show, but only with nouveau open-source graphics drivers. The nouveau driver suffers from screen tearing on this system, so I switched to proprietary nvidia drivers (Tesla 470 for w530) to resolve this. While it did cure screen tearing, I got the same problem as with edk2. -- 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 0

[coreboot - Bug #562] (New) Issues regarding HP Elitebook 8470p
by Kristof Horvath Sept. 14, 2024

Sept. 14, 2024

Issue #562 has been reported by Kristof Horvath. ---------------------------------------- Bug #562: Issues regarding HP Elitebook 8470p https://ticket.coreboot.org/issues/562 * Author: Kristof Horvath * Status: New * Priority: Normal * Target version: none * Start date: 2024-09-14 * Affected versions: 4.21 ---------------------------------------- Hi all! I have a HP Elitebook 8470p with Libreboot 20240612 installed, but I've also tried compiling from scratch using the git head of coreboot. I have been using it with Ubuntu 24.04, but there are some issues: 1.) Screen brightness can not be changed. 2.) After returning from sleep, the WWAN module (MC7710) is not accessible. 3.) Bluetooth is not recognized, as if the BT module was absent. It may not be related, but Windows 10 fails to boot with "ACPI BIOS error" BSOD message. I have actually found out the third problem: the device tree override (/src/mainboard/hp/snb_ivb_laptops/variants/8470p/overridetree.cb) contains incorrect values for usb_port_config. Enabling all USB ports fixes that issue, but I'm not sure if this is the correct fix. -- 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 0

coreboot Meetings Announcement And Agenda Call
by mina＠coreboot.org Sept. 13, 2024

Sept. 13, 2024

Dear coreboot community, Please note that our upcoming leadership meeting is scheduled for Wednesday,September 18, 2024.[1] Kindly take a moment to update the current agenda with matters you wish to see discussed during the meeting.[2] Thank you. Best regards, Mina Asante. [1](https://coreboot.org/calendar.html) [2](https://docs.google.com/document/d/1NRXqXcLBp5pFkHiJbrLdv3Spqh1Hu086HYkK…

1 0

DUG #7 & vPub 0xC - an open-source online party! September 12th at 4 PM UTC
by Mike Banon Sept. 11, 2024

Sept. 11, 2024

Dear friends, I invite you to a joint DUG #7 + vPub 0xC event that starts Tomorrow at 4 PM UTC ! ;-) Would you like to: * see an exciting demo of a new Dasharo firmware for ODROID H4+ single board computer? (could be installed in a mini-ITX case thanks to a kit) * get updates about the NovaCustom privacy-focused laptops (coreboot-supported & QubesOS-certified) ? * learn some cool tricks on how to successfully hunt for firmware vulnerabilities? and also * find out about new open hardware / opensource firmware-supporting devices that you haven't heard about before? Then this upcoming event - is an excellent opportunity for you to have a great time in the company of fellow firmware enthusiasts. The 1st part of our event - DUG #7 - is dedicated to Dasharo distribution of coreboot opensource firmware with advanced features like GUI & FLASHBIOS and the ecosystem around it. DUG will take place between 4-6 PM UTC - and then around 6 PM UTC will switch to vPub. The past events have been highly successful, and I'm sure you will find this time interesting as well ;-) Both sound/video and text chats will be available for your convenience More details and Join links are available here - https://vpub.dasharo.com/e/14/dasharo-user-group-7 -- Best regards, Mike Banon Open Source Community Manager of 3mdeb - https://3mdeb.com/

1 0

Could not find a bounce buffer... Payload not loaded. Intel 440BX/LX Board
by Christian Sühs Sept. 10, 2024

Sept. 10, 2024

2 2