coreboot

coreboot@coreboot.org

3 participants
39681 discussions

2024_11_20 coreboot Group Review Sesssion
by mina＠coreboot.org 18 Nov '24

18 Nov '24

Hello coreboot! Please note that we have an upcoming review session scheduled for Wednesday, November 20, 2024: https://meet.google.com/kpu-yozw-gtt Check the coreboot calendar for the time in your timezone: https://coreboot.org/calendar.html As usual, we'll begin by reviewing a few patches together, then switch to individual reviews. However, everyone will still be available if you have questions about the patch you're reviewing. Here’s the link to the list of patches to be reviewed this week: (https://docs.google.com/spreadsheets/d/1io-tewVlkX3PAkhR9ttCKjJXiXR9Emy6qsY… 80#gid=594572880) Kindly add any specific patches you'd like the group to review to the top of the sheet. Given the limited time for our session, any reviews completed beforehand would be greatly appreciated. Thank you. Best regards, Mina.

1 0

[coreboot - Bug #121] T520: Hangs in OS
by Nemanja Z 15 Nov '24

15 Nov '24

Issue #121 has been updated by Nemanja Z. I also finally updated my T520 i7-3740QM to 24.08-631-gf8d4283e78d2. (from 4.14-2082-gee760b4be8) No kernel options, C7 working now, no crashes in Debian 12, Windows 10 also seems fine. ---------------------------------------- Bug #121: T520: Hangs in OS https://ticket.coreboot.org/issues/121#change-1974 * Author: Firstname Lastname * Status: In Progress * Priority: Normal * Category: chipset configuration * Start date: 2017-06-09 * Affected hardware: SNB, IVY * Affected OS: - ---------------------------------------- I have been running coreboot since 2017.04.15 and have experienced hangs ever since then. It was suggested by folk on the IRC that I run memtest to check for incorrect raminit causing errors, however I have run memtest for 12 hours straight with no errors. Due to the ambiguous nature of the hangs (immediate freeze with no warning signs, audio gets stuck repeating the last 50ms or so of noise, not sure what this effect is called) I don't have much useful information other than the .config and dmesg. However one thing I can say with high confidence is that the hangs occur significantly more frequently in Linux (*buntu distros) than Windows 10. Within an hour of launching Linux a hang is likely, whereas Windows typically runs for many hours before a hang occurs. I considered this an insignificant anecdotal anomaly at first but over the course of the nearly 2 months I have been running coreboot it seems to be a solid trend. The hangs occur anywhere, typically during mere desktop usage or basic web browsing. Additionally there is another form of hang I experience where the screen goes black except for some sort of graphical corruption down the left side (http://i.imgur.com/4zWrlpX.jpg), whether this is related to the more common total freeze hangs I don't know but I figured I should include it nonetheless. These hangs only occur about 1:20 compared to the regular hangs. ---Files-------------------------------- config (20.7 KB) dmesg.txt (57.3 KB) cbmem-raminit.txt (62 KB) lspci.txt (29.6 KB) cpuinfo.txt (3.94 KB) defconfig (1023 Bytes) defconfig (699 Bytes) -- 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

2024-11-13 - coreboot Leadership Meeting Minutes
by mina＠coreboot.org 14 Nov '24

14 Nov '24

# 2024-11-13 - coreboot Leadership Meeting ## Attendees Andre, Felix Held, Jay Talbott, Felix Singer, Julius Werner, Werner Zeh, Alicja Michalska, Mina Asante, Jon Murphy, Matt DeVillier, Maximilian Brune, Ron Minnich, Karthik R. ## Open Action Items * 2024-10-30 * Add clarification to docs, “do not use gerrit change-id or CB: format in reference to already-merged patches”. * 2024-10-16 * Matt: Set up a meeting to discuss board status alternatives and send out invites. * 2024-09-18 * Jon: Schedule a dedicated meeting to discuss the Coverity defects and action plan. * Werner: Send out an invite for the meeting. Sent out a poll to find a time slot:https://rallly.co/invite/1c8J3azXAcje * 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 ### [Elyes] Any update on OpenSBI case …. ? (See 2024-07-24 - coreboot Leadership Meeting and (https://review.coreboot.org/c/coreboot/+/84979) ). * [Mat]: It was planned to replace the submodule by a binary blob (see patch from Max: https://review.coreboot.org/c/coreboot/+/83284). This patch is ready to be merged, we do not need the 3rdparty git repo anymore for OpenSBI. * Matt will rebase Max’ patch and merge it in. * [Julius]: Shall we keep the old 3rdparty openSBI submodule in the tree or shall we get rid of it after Max’s patch was merged? * [Max]: A lot of users have their own OpenSBI port, so having this submodule in the tree does not bring us that much benefits. It is hard to update OpenSBI submodule currently (can’t build it with our toolchain, there might be a missing linker (PIE: *Makefile:193: *** Your linker does not support creating PIEs, opensbi requires this.. Stop.*) feature). Not clear currently why our linker is missing. * [Julius]: Looks like it's not actually querying the linker for that, you just need to set an option?(https://github.com/riscv-software-src/opensbi/blob/master/Makefile#… * FelixS will give it a try! * If we are going to remove it from 3rdparty, we need to document the dependency to the users to make them aware of the change. * Conclusion: Keep it as long in the tree as somebody is going to fix the issue. ### [Karthik] Is it ok to enable FW_CONFIG in SMM stage (https://review.coreboot.org/c/coreboot/+/85107/11/src/lib/Makefile.mk) * Are there any security concerns? * FW_CONFIG can use either EC or CBFS * [Julius]: Is the EC communication driver linked to SMM? –> Yes * [Karthik]: Since EC code is linked to SMM there is no issue to add fw_config to SMM from Google’s point of view. * [Matt]:Isn’t fw_config cached on the first read? → Yes, but per stage only. * [Mat, FelixH]: Why not toggle the GPIOs even if the WWAN module is not equipped on the board? The pins should be configured as GPIOs anyway, switching them unconditionally should not harm and will enable us to not link fw_config into SMM. → Karthik will propose that to the ODMs, looks doable. # Next Leadership Meeting November 27, 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 https://docs.google.com/document/d/1NRXqXcLBp5pFkHiJbrLdv3Spqh1Hu086HYkKrgK…

1 0

[coreboot - Bug #569] (New) coreinfo: i386-elf-gcc-ar: Cannot find binary 'i386-elf-ar'
by Matthias Brugger 14 Nov '24

14 Nov '24

Issue #569 has been reported by Matthias Brugger. ---------------------------------------- Bug #569: coreinfo: i386-elf-gcc-ar: Cannot find binary 'i386-elf-ar' https://ticket.coreboot.org/issues/569 * Author: Matthias Brugger * Status: New * Priority: Normal * Target version: none * Start date: 2024-11-14 * Affected versions: master * Related links: https://doc.coreboot.org/tutorial/part1.html ---------------------------------------- Hi, when trying to compile the qemu example with latest branch, I get the following error: ``` ~/src/coreboot/$ make -C payloads/coreinfo/ Makefile:358: warning: overriding recipe for target '/home/mbrugger/src/coreboot/payloads/coreinfo/libpayload/arch/x86/exec.libc.o' Makefile:358: warning: ignoring old recipe for target '/home/mbrugger/src/coreboot/payloads/coreinfo/libpayload/arch/x86/exec.libc.o' AR /home/mbrugger/src/coreboot/payloads/coreinfo/libpayload/libpci.a /home/mbrugger/src/coreboot/payloads/libpayload/../../util/crossgcc/xgcc/bin/i386-elf-gcc-ar: Cannot find binary 'i386-elf-ar' make[1]: *** [Makefile.mk:116: /home/mbrugger/src/coreboot/payloads/coreinfo/libpayload/libpci.a] Error 1 make: *** [../libpayload/Makefile.payload:153: /home/mbrugger/src/coreboot/payloads/coreinfo/libpayload/libpayload.a] Error 2 ``` I double checked and ./util/crossgcc/xgcc/bin/i386-elf-ar exists. I suppose it's a problem in the cross compilation of i386-elf-gcc-ar -- 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 2

[coreboot - Support #567] (New) How init git repository for avoiding date error?
by nymous ano 12 Nov '24

12 Nov '24

Issue #567 has been reported by nymous ano. ---------------------------------------- Support #567: How init git repository for avoiding date error? https://ticket.coreboot.org/issues/567 * Author: nymous ano * Status: New * Priority: Normal * Category: build system * Target version: none * Start date: 2024-11-05 * Affected versions: master * Affected hardware: config.emulation_qemu_aarch64_fit_support_timestamps * Affected OS: Ubuntu Noble Numbat, 24.04, LTS ---------------------------------------- With compiling for 'config.emulation_qemu_aarch64_fit_support_timestamps' following this tutorial 'https://doc.coreboot.org/tutorial/part1.html' for origin/main branch on Linux Ubuntu Noble Numbat, 24.04, LTS, for a aarch64 emulation target, there's this error: > fatal: bad object HEAD > fatal: bad object HEAD > fatal: HEAD is neither a commit nor blob > date: invalid date '@' > date: invalid date '@' > date: invalid date '@' > date: invalid date '@' > date: invalid date '@' > date: invalid date '@' > date: invalid date '@' > date: invalid date '@' > fatal: bad object HEAD > fatal: HEAD is neither a commit nor blob > Updating git submodules. > CC romstage/lib/version.o > CC romstage/southbridge/intel/common/rtc.o > CC romstage/southbridge/intel/common/smbus.o > CC romstage/southbridge/intel/i82371eb/early_pm.o > src/lib/version.c:24:75: error: expected expression before ';' token > 24 | const unsigned int coreboot_version_timestamp = COREBOOT_VERSION_TIMESTAMP; > | ^ > In file included from src/lib/version.c:4: > build/build.h:13:33: error: invalid suffix "x" on integer constant > 13 | #define COREBOOT_BUILD_YEAR_BCD 0x > | ^~ > src/lib/version.c:33:17: note: in expansion of macro 'COREBOOT_BUILD_YEAR_BCD' > 33 | .year = COREBOOT_BUILD_YEAR_BCD, > | ^~~~~~~~~~~~~~~~~~~~~~~ > build/build.h:14:34: error: invalid suffix "x" on integer constant > 14 | #define COREBOOT_BUILD_MONTH_BCD 0x > | ^~ > src/lib/version.c:34:18: note: in expansion of macro 'COREBOOT_BUILD_MONTH_BCD' > 34 | .month = COREBOOT_BUILD_MONTH_BCD, > | ^~~~~~~~~~~~~~~~~~~~~~~~ > build/build.h:15:32: error: invalid suffix "x" on integer constant > 15 | #define COREBOOT_BUILD_DAY_BCD 0x > | ^~ > src/lib/version.c:35:16: note: in expansion of macro 'COREBOOT_BUILD_DAY_BCD' > 35 | .day = COREBOOT_BUILD_DAY_BCD, > | ^~~~~~~~~~~~~~~~~~~~~~ > build/build.h:16:36: error: invalid suffix "x" on integer constant > 16 | #define COREBOOT_BUILD_WEEKDAY_BCD 0x > | ^~ > src/lib/version.c:36:20: note: in expansion of macro 'COREBOOT_BUILD_WEEKDAY_BCD' > 36 | .weekday = COREBOOT_BUILD_WEEKDAY_BCD, > | ^~~~~~~~~~~~~~~~~~~~~~~~~~ > make: *** [Makefile:430: build/romstage/lib/version.o] Error 1 > make: *** Waiting for unfinished jobs.... There seems to be no hint within tutorial documentation for to avoid this missing date and version from/for the repository? ( Thanks for Your time and engagement. ) -- 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 11

coreboot Meetings Announcement And Agenda Call
by mina＠coreboot.org 11 Nov '24

11 Nov '24

Dear coreboot community, Please be reminded that we have an upcoming leadership meeting scheduled for Wednesday, November 13, 2024.[1] Kindly take a moment to review the current agenda and share your thoughts, or suggest any additional items you would like to discuss during the meeting.[2] Thank you. ## Current Agenda Items ### [Elyes] Any update on OpenSBI case …. ? (See 2024-07-24 - coreboot Leadership Meeting and https://review.coreboot.org/c/coreboot/+/84979. [1](https://coreboot.org/calendar.html) [2](https://docs.google.com/document/d/1NRXqXcLBp5pFkHiJbrLdv3Spqh1Hu086HYkK…

1 0

coreboot Meetings Announcement And Agenda Call
by mina＠coreboot.org 08 Nov '24

08 Nov '24

Dear coreboot community, Kindly note that our next leadership meeting is scheduled for Wednesday, November 13, 2024.[1] Please update the current agenda with matters you wish to discuss 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

H610DA V41 supporting
by Valeriy Simakov 04 Nov '24

04 Nov '24

Hello! I’m an embedded developer, and I’m interested in your ‘coreboot’ project. I want to run it on my motherboard(H610DA ). Could you please help me with that, is there any document that describes porting to a new motherboard? As I understand, I should know how the bios binary file organize on my motherboard and other specific information that I could get only from manufacture. -- Best regards, Valeriy Simakov

1 0

2024_11_06 coreboot Group Review Sesssion
by mina＠coreboot.org 04 Nov '24

04 Nov '24

Hello coreboot! Please note that our next review session is scheduled for Wednesday, November 6, 2024: https://meet.google.com/kpu-yozw-gtt Check the coreboot calendar for the time in your timezone: https://coreboot.org/calendar.html As usual, we'll begin by reviewing a few patches together, then switch to individual reviews. However, everyone will still be available if you have questions about the patch you're reviewing. Here’s the link to the list of patches to be reviewed this week: (https://docs.google.com/spreadsheets/d/1io-tewVlkX3PAkhR9ttCKjJXiXR9Emy6qsY… 055#gid=1519768055). Kindly add any specific patches you'd like the group to review to the top of the sheet. Thank you. Best regards, Mina.

1 0

2024-10-30 - coreboot Leadership Meeting Minutes
by mina＠coreboot.org 31 Oct '24

31 Oct '24

# 2024-10-30 - coreboot Leadership Meeting ## Attendees Felix Held, Felix Singer, Marshall Dawson, Matt DeVillier, Jeremy Compostella, Alicja Michalska, Maximilian Brune, Pono, Mina Asante, David Hendricks, Jay Talbott, Julius Werner, Ron Minnich. ## Open Action Items * 2024-10-30 * Add clarification to docs, “do not use gerrit change-id or CB: format in reference to already-merged patches”. * 2024-10-16 * Matt: Set up a meeting to discuss board status alternatives and send out invites. * 2024-09-18 * Jon: Schedule a dedicated meeting to discuss the Coverity defects and action plan. * Werner: Send out an invite for the meeting. Sent out a poll to find a time slot:https://rallly.co/invite/1c8J3azXAcje * 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 ### [Elyes] How to know when we should follow Linux rules and when those of coreboot ? Please make it clear. * I’m asking because of Felix’s comment here : https://review.coreboot.org/c/coreboot/+/84074 about “`Commit <first 12 chars of commit> ("<commit title>")"` * [Matt] coreboot’s checkpatch should detect and enforce this: ![alt_text](images/image1.png "image_tooltip") * [Matt] looks like we don’t explicitly state this in the coding style or documentation, and probably should just for clarity * AI: add clarification to docs, do not use gerrit change-id or CB: format in reference to already-merged patches. ### [David] Follow-up on discussion with SFC regarding use of LLM-generated code * It's a new thing that doesn't have a good policy yet. SFC is getting a lot of questions regarding this, and there seems to be widespread adoption in various companies but with various restrictions surrounding how they are used. It's unclear how this applies to the world of free software. * We need to gather data at this time to figure out how many people are using LLMs and how. This will help SFC craft appropriate policy. * How do we do this? Ask people to annotate commit messages if they used an LLM? This would be voluntary (we have no good way to enforce it). * We don't necessarily know who is using it now, and we don't have a good way of tracking it. So we treat patches the way we currently do, regardless of whether an LLM was involved in their creation or not. ### [David] Is anything needed with regard to Russian maintainers/contributors? * We asked the SFC back in April '23, but did not get a response. Given the recent drama in Linux it seems we need to revisit this topic and avoid running amok of sanctions. * [Pono] This is a confusing issue.Continuing as normal for now is OK, but SFC will let us know if this changes. * How could this be enforced? IP address scanning? Is there some retention period for logs? * Pono will follow-up with Karen about this. * Does this only apply to people working at sanctioned companies, or everyone living in the country? * [Alicja & others] - It may only apply to sanctioned companies. * How does this apply to certain community members? We believe there is at least one who may be impacted. # Next Leadership Meeting * November 13, 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 https://docs.google.com/document/d/1NRXqXcLBp5pFkHiJbrLdv3Spqh1Hu086HYkKrgK…

1 0

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