coreboot

coreboot@coreboot.org

6 participants
39686 discussions

Trouble booting with mt8183
by Jared Baur 15 Aug '23

15 Aug '23

I am looking for some advice for configuring coreboot with a uImage fit payload for an mt8183 chromebook (Kukui Fennel)? I have said fitimage, I've modified the memlayout for the mt8183 board similar to https://github.com/coreboot/coreboot/commit/22e605c2c06f553b98131a87b634709… so that the fitimage fits in the cbfs and has space to load, and coreboot successfully builds. I've also enabled a bunch of debug settings for coreboot printing to serial. When flashing the ROM and rebooting, the serial console doesn't show anything past bootrom messages like so: ``` [DL] 00000000 00000000 010701 F0: 102B 0000 F3: 1006 0033 [0200] F3: 4001 00E0 [0200] F3: 0000 0000 V0: 0000 0000 [0001] 00: 1027 0002 01: 0000 0000 BP: 0C00 0251 [0000] G0: 1182 0000 EC: 0004 0000 [0001] S7: 0000 0000 [0000] CC: 0000 0000 [0001] T0: 0000 00DB [000F] Jump to BL ``` I am happy to post any configuration that would be helpful. I am hoping to just get some serial output from coreboot at this point in time, regardless of the payload.

3 2

Haswell-E 2011-3 support
by Sid_key 14 Aug '23

14 Aug '23

Can someone help to implement 2011-3 support in coreboot? There are quite many 2011-3 chinese boards with broken bios, would be good to run coreboot on them to fix most problems. For example: Huananzhi X99 QD4 (Haswell-E/Broadwell-E 2011-3 CPU, B85/Q87/Z87 chipset) Huananzhi X99 BD4 (Haswell-E/Broadwell-E 2011-3 CPU, B85/Q87/Z87 chipset) I tried to make coreboot dt and to try booting Haswell-E over Haswell drivers, but faced FF postcode: dt: https://github.com/MrArtemSid/coreboot_huananzhi_x99-series/tree/staging1 haswell-e changes: https://github.com/MrArtemSid/coreboot/tree/haswell-e

1 0

The coreboot 4.21 release tag in 1 week
by coreboot org 14 Aug '23

14 Aug '23

Hello coreboot, This is the notification that we're one week away from doing the coreboot 4.21 release tag on August 21st. As mentioned previously, we will have a 1 week delay after the new version is tagged to allow for testing after the release. This will give us a chance to fix any issues that are found during the release process before making the release public. The 4.21 announcement is scheduled for August 28th. If you have any questions or concerns, please let the coreboot release team know. We're using the IRC channel #coreboot_release to coordinate our activities. Martin

1 0

[coreboot - Bug #495] (Response Needed) Stoney not booting PSPSecureOS -- Graphics driver takes 30 minutes to start
by CoolStar Organization 14 Aug '23

14 Aug '23

Issue #495 has been reported by CoolStar Organization. ---------------------------------------- Bug #495: Stoney not booting PSPSecureOS -- Graphics driver takes 30 minutes to start https://ticket.coreboot.org/issues/495 * Author: CoolStar Organization * Status: Response Needed * Priority: High * Category: chipset configuration * Target version: none * Start date: 2023-06-14 * Affected versions: 4.21, 4.15, 4.16, 4.17, 4.18, 4.19, master * Affected hardware: stoney * Affected OS: Windows 10, Windows 11 ---------------------------------------- Windows 11 Graphics driver takes 30 minutes to start on Stoney due to missing PSPSecureOS. Windows 10 20H2 and newer hangs on boot (potentially from the same thing) -- 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

4 3

[coreboot - Bug #496] (New) Missing malloc check in libpayload
by Keith Makan 14 Aug '23

14 Aug '23

Issue #496 has been reported by Keith Makan. ---------------------------------------- Bug #496: Missing malloc check in libpayload https://ticket.coreboot.org/issues/496 * Author: Keith Makan * Status: New * Priority: Normal * Target version: none * Start date: 2023-06-27 * Affected versions: 4.21 * Affected hardware: ALL * Affected OS: ALL ---------------------------------------- libpayload in payload/libpayload/drivers/options.c::get_option_as_string does not issue a NULL check against malloc's return code. Should there be a NOMEM error this may result in a NULL pointer deref or crash. The following code extract illustrates the mentioned issue: ` int get_option_as_string(const struct nvram_accessor *nvram, struct cb_cmos_option_table *option_table, char **dest, const char *name) { ... /* extra byte to ensure 0-terminated strings */ raw = malloc(cmos_length+1); memset(raw, 0, cmos_length+1); <--- no check against malloc's return code ` -- 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

2 1

[PATCH v2 1/2] x86: coreboot: Update cbmem table
by Simon Glass 14 Aug '23

14 Aug '23

This changed a few years ago to include an overflow flag. Bring in the new structure. This comes from coreboot commit: 6f5ead14b4 ("mb/google/nissa/var/joxer: Update eMMC DLL settings") Note: There are several implementations of this in coreboot. I have chosen to follow the one in src/lib/cbmem_console.c Signed-off-by: Simon Glass <sjg(a)chromium.org> --- (no changes since v1) arch/x86/include/asm/coreboot_tables.h | 19 ++++++++++++++++--- 1 file changed, 16 insertions(+), 3 deletions(-) diff --git a/arch/x86/include/asm/coreboot_tables.h b/arch/x86/include/asm/coreboot_tables.h index 4de137fbab9d..8db7c189b474 100644 --- a/arch/x86/include/asm/coreboot_tables.h +++ b/arch/x86/include/asm/coreboot_tables.h @@ -299,11 +299,24 @@ struct cb_vdat { #define CB_TAG_TIMESTAMPS 0x0016 #define CB_TAG_CBMEM_CONSOLE 0x0017 -struct cbmem_console { +#define CBMC_CURSOR_MASK ((1 << 28) - 1) +#define CBMC_OVERFLOW BIT(31) + +/* + * struct cbmem_console - In-memory console buffer for coreboot + * + * Structure describing console buffer. It is overlaid on a flat memory area, + * with body covering the extent of the memory. Once the buffer is full, + * output will wrap back around to the start of the buffer. The high bit of the + * cursor field gets set to indicate that this happened. If the underlying + * storage allows this, the buffer will persist across multiple boots and append + * to the previous log. + */ +struct __packed cbmem_console { u32 size; u32 cursor; - char body[0]; -} __packed; + u8 body[0]; +}; #define CB_TAG_MRC_CACHE 0x0018 -- 2.41.0.640.ga95def55d0-goog

1 1

New Defects reported by Coverity Scan for coreboot
by scan-admin＠coverity.com 11 Aug '23

11 Aug '23

Hi, Please find the latest report on new defect(s) introduced to coreboot found with Coverity Scan. 2 new defect(s) introduced to coreboot found with Coverity Scan. New defect(s) Reported-by: Coverity Scan Showing 2 of 2 defect(s) ** CID 1518442: Resource leaks (RESOURCE_LEAK) /3rdparty/vboot/futility/file_type_bios.c: 215 in ft_show_bios() ________________________________________________________________________________________________________ *** CID 1518442: Resource leaks (RESOURCE_LEAK) /3rdparty/vboot/futility/file_type_bios.c: 215 in ft_show_bios() 209 if (fmap_find_by_name(buf, len, fmap, fmap_name[c], &ah)) { 210 /* But the file might be truncated */ 211 fmap_limit_area(ah, len); 212 if (asprintf((char **)&ft_print_header, "bios::%s", 213 fmap_name[c]) <= 0) { 214 ERROR("Failed to allocate buffer for FT_PRINT"); >>> CID 1518442: Resource leaks (RESOURCE_LEAK) >>> Variable "buf" going out of scope leaks the storage it points to. 215 return 1; 216 } 217 218 /* Update the state we're passing around */ 219 state.c = c; 220 state.area[c].offset = ah->area_offset; ** CID 1518441: Resource leaks (RESOURCE_LEAK) /3rdparty/vboot/futility/file_type_bios.c: 215 in ft_show_bios() ________________________________________________________________________________________________________ *** CID 1518441: Resource leaks (RESOURCE_LEAK) /3rdparty/vboot/futility/file_type_bios.c: 215 in ft_show_bios() 209 if (fmap_find_by_name(buf, len, fmap, fmap_name[c], &ah)) { 210 /* But the file might be truncated */ 211 fmap_limit_area(ah, len); 212 if (asprintf((char **)&ft_print_header, "bios::%s", 213 fmap_name[c]) <= 0) { 214 ERROR("Failed to allocate buffer for FT_PRINT"); >>> CID 1518441: Resource leaks (RESOURCE_LEAK) >>> Handle variable "fd" going out of scope leaks the handle. 215 return 1; 216 } 217 218 /* Update the state we're passing around */ 219 state.c = c; 220 state.area[c].offset = ah->area_offset; ________________________________________________________________________________________________________ To view the defects in Coverity Scan visit, https://u15810271.ct.sendgrid.net/ls/click?upn=HRESupC-2F2Czv4BOaCWWCy7my0P…

1 0

Custom Splash Screen
by Ahamed Husni 09 Aug '23

09 Aug '23

Hi all, I want to display a custom logo in the splash screen for a specified amount of time (SeaBIOS as payload). How do I configure the logo and give a timeout when building coreboot? Any pointers will be really helpful. Regards, Husni.

3 3

Termin mit Hinweis abgesagt: coreboot Leadership Meeting - Mi 9. Aug. 2023 19:00 - 20:00 (MESZ) (coreboot@coreboot.org)
by Patrick Georgi 09 Aug '23

09 Aug '23

Dieser Termin wurde mit folgendem Hinweis abgesagt: "The entire leadership team can't make it today, so let's take the rare decision to cancel the meeting." coreboot Leadership Meeting Mittwoch 9. Aug. 2023 ⋅ 19:00 – 20:00 Mitteleuropäische Zeit - Berlin Mit Google Meet teilnehmen https://meet.google.com/pyt-newq-rbb?hs=224 Per Telefon teilnehmen (US) +1 608-618-4744 PIN: 143813170 Weitere Telefonnummern https://tel.meet/pyt-newq-rbb?pin=6680344120895&hs=0 Anhänge Notes - coreboot Leadership Meeting https://docs.google.com/document/d/1FdgO-uLMmdRzBiOYJmzwaf8MSTVNpn6lHbQk7H8… Meeting Minutes - If you don't have edit access and want it, please ask Patrick G. Organisator Patrick Georgi pgeorgi(a)google.com Gäste Patrick Georgi - Organisator gaumless(a)gmail.com Stefan Reinauer Werner Zeh David Hendricks Noga Smith sheng.tan(a)9elements.com subratabanik(a)google.com kapilporwal(a)google.com hughsient(a)gmail.com taruntuli(a)google.com maximilian.brune(a)9elements.com rangasai.v.chaganty(a)intel.com vincent.zimmer(a)intel.com Simon Glass Andreas Huber mattpapa(a)amazon.com WIM - Optional Dossym Nurmukhanov - Optional christian.walter(a)9elements.com - Optional marshalldawson3rd(a)gmail.com - Optional patrick.rudolph(a)9elements.com - Optional matt.devillier(a)gmail.com - Optional jeremy(a)system76.com - Optional Ron Minnich - Optional jaytalbott(a)sysproconsulting.com - Optional jonzhang(a)fb.com - Optional zaolin.daisuki(a)googlemail.com - Optional rminnich(a)gmail.com - Optional Julius Werner - Optional epeers(a)google.com - Optional felix.held(a)amd.corp-partner.google.com - Optional tcrawford(a)system76.com - Optional Rocky Phagura - Optional Desimone, Nathaniel L - Optional arthur(a)aheymans.xyz - Optional felix.singer12(a)gmail.com - Optional stefank.reinauer(a)gmail.com - Optional Shelley Chen - Optional kramasub(a)google.com - Optional nico.h(a)gmx.de - Optional jason.glenesk(a)amd.com - Optional Held, Felix - Optional felix-coreboot(a)felixheld.de - Optional felix(a)felixheld.de - Optional gduynisveld(a)eltan.com - Optional coreboot(a)coreboot.org - Optional ~~//~~ Einladung von Google Kalender: https://calendar.google.com/calendar/ Sie erhalten diese E-Mail, weil Sie ein Gast des Termins sind. Wenn Sie keine weiteren Informationen zu diesem Termin erhalten möchten, lehnen Sie die Einladung ab. Wenn Sie diese Einladung weiterleiten, kann jeder Empfänger eine Antwort an den Organisator senden und zur Gästeliste hinzugefügt werden. Außerdem könnte er weitere Nutzer einladen und Ihre Antwort ändern. Weitere Informationen https://support.google.com/calendar/answer/37135#forwarding

1 0

The coreboot 4.21 release is scheduled for 2023_08_21
by coreboot org 07 Aug '23

07 Aug '23

Hi everyone, This is the notification that we're planning on tagging the coreboot 4.21 release in 2 weeks on August 21st. Please let us know if there are any patches that need to make it into the release by setting the topic to “coreboot_release_4.21". This does not guarantee that the patch will be merged before then, but an effort will be made to get those patches merged. As always, we'd appreciate any platform testing that can be done now before the release is done. Starting with the 4.19 release we have a 1 week delay after the new version is tagged to allow for testing after the release. This will give us a chance to fix any issues that are found during the release process before making the release public. The 4.21 announcement is scheduled for August 28th. If you have any questions, please let the coreboot release team know. We're using the IRC channel #coreboot_release to coordinate our activities. Martin

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