coreboot

coreboot@coreboot.org

1 participants
39247 discussions

Planned maintenance on ticket.coreboot.org on July 1st
by Felix Singer 01 Jun '23

01 Jun '23

I will do some maintenance work on our ticket system on July 1st, which is the upcoming Thursday. The maintenance will * start at 9:00 am UTC+0 * end at 11:00 am UTC+0 (estimated, probably at latest) During this time, the ticket system will be down and/or unusable. I will announce as soon as the work is finished. The maintenance will cover: * Updating the system to the newest stable release * Updating the ticket system to the newest stable release Felix

1 4

[coreboot - Other #492] (New) Evaluate changes need to be made to support Intel's X86S ISA changes
by Martin Roth 28 May '23

28 May '23

Issue #492 has been reported by Martin Roth. ---------------------------------------- Other #492: Evaluate changes need to be made to support Intel's X86S ISA changes https://ticket.coreboot.org/issues/492 * Author: Martin Roth * Status: New * Priority: Normal * Category: coreboot common code * Target version: none * Start date: 2023-05-28 ---------------------------------------- This past week, Intel announced a plan to boot directly to 64-bit mode[1]. While the timeline released with the announcement does't have any dates for the implementation, due to the huge impact this will have on coreboot, it seems appropriate to start looking at what changes will need to be made to support these changes to the ISA. Changes currently listed: Changes in X86-S ISA consist of: - restricting the CPU to be always in paged mode - removing 32-bit ring 0, as well as vm86 mode. - removing ring 1 and ring 2 - removing 16-bit real and protected modes - removing 16-bit addressing - removing fixed MTRRs - removing user-level I/O and string I/O - removing CR0 Write-Through mode - removing legacy FPU control bits in CR0 - removing ring 3 interrupt flag control - removing obsolete CR access instruction - rearchitecting INIT/SIPI - adding a new mechanism to switch between 4- and 5-level page tables - removing XAPIC and only supporting x2APIC - removing APIC support for 8529 - removing the disabling of NX or SYSCALL or long mode in the EFER MSR - removing the #SS and #NP exceptions - supporting a subset of segmentation architecture, with the following conditions: o restricted to a subset of IDT event delivery o base only for FS, GS o base and limit for GDT, IDT, and TSS o no limit on data or code fetches in 32-bit mode (similar to 64-bit) o no AR or unusable selector checking on CS, DS, ES, FS, and GS on data or code fetches in any mode o restricted support for far call, far return, far jump, and IRET (like FRED). 1: https://web.archive.org/web/20230526070811/https://www.intel.com/content/ww… -- 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 1

Looking to get Coreboot working on Jasper Lake / N5105 mini PC with 4x Intel 2.5Gbit NICs
by Marcos Scriven 25 May '23

25 May '23

Hello all I'd like to get Coreboot working on a new target device, so I'll follow the 6 steps in the https://www.coreboot.org/FAQ section entitled "Will coreboot work on my machine?" It looks like someone emailed the mailing list about this back in November '22 https://mail.coreboot.org/hyperkitty/list/coreboot@coreboot.org/thread/I5HF…, but if I'm reading the archive correctly, didn't get any responses. Step 1: A very brief description of your system: board vendor, board name, CPU, northbridge, southbridge, and optionally other important details. Board Vendor: Board is branded Topton, but the board is from CWWK. CWWK mentions this board on one of their firmware update pages https://www.changwang.com/down/74.html Board Name: MW-JSL2.5G4L CPU: N5105 North Bridge Intel Jasper Lake Host Bridge rev 00 South Bridge Intel Jasper Lake PCH rev 01 • Step 2: Linux "*lspci -tvnn*" output for your system, generated by booting Linux via the original BIOS and runnning lspci. -[0000:00]-+-00.0 Intel Corporation Device [8086:4e24] +-02.0 Intel Corporation Device [8086:4e61] +-04.0 Intel Corporation Device [8086:4e03] +-14.0 Intel Corporation Device [8086:4ded] +-14.2 Intel Corporation Device [8086:4def] +-15.0 Intel Corporation Device [8086:4de8] +-15.2 Intel Corporation Device [8086:4dea] +-16.0 Intel Corporation Device [8086:4de0] +-17.0 Intel Corporation Device [8086:4dd3] +-19.0 Intel Corporation Device [8086:4dc5] +-19.1 Intel Corporation Device [8086:4dc6] +-1c.0-[01]----00.0 Phison Electronics Corporation E12 NVMe Controller [1987:5012] +-1c.4-[02]----00.0 Intel Corporation Ethernet Controller I225-V [8086:15f3] +-1c.5-[03]----00.0 Intel Corporation Ethernet Controller I225-V [8086:15f3] +-1c.6-[04]----00.0 Intel Corporation Ethernet Controller I225-V [8086:15f3] +-1c.7-[05]----00.0 Intel Corporation Ethernet Controller I225-V [8086:15f3] +-1e.0 Intel Corporation Device [8086:4da8] +-1e.3 Intel Corporation Device [8086:4dab] +-1f.0 Intel Corporation Device [8086:4d87] +-1f.3 Intel Corporation Device [8086:4dc8] +-1f.4 Intel Corporation Device [8086:4da3] \-1f.5 Intel Corporation Device [8086:4da4] • Step 3: Super I/O chip on the mainboard (report the model numbers on the actual chip, for example "Winbond W83627HF" and/or run "*superiotool <https://www.coreboot.org/Superiotool> -dV*"). Output of superiotool -dV (minus all the probing/failed): Found ITE IT8613E (id=0x8613, rev=0xc) at 0x2e Register dump: idx 20 21 22 23 24 2b val 86 13 0c 40 00 48 def 86 13 05 40 00 48 LDN 0x01 (COM1) idx 30 60 61 70 f0 val 01 03 f8 04 01 def 00 03 f8 04 00 LDN 0x04 (Environment controller) idx 30 60 61 62 63 70 f0 f1 f2 f3 f4 f5 f6 fa fb fc val 01 0a 30 0a 20 00 80 00 00 00 20 00 f0 00 00 00 def 00 02 90 02 30 09 00 00 00 00 00 NA NA 00 00 00 LDN 0x05 (Keyboard) idx 30 60 61 62 63 70 71 f0 val 00 00 60 00 64 01 02 48 def 01 00 60 00 64 01 02 48 LDN 0x06 (Mouse) idx 30 70 71 f0 val 00 0c 02 00 def 00 0c 02 00 LDN 0x07 (GPIO) idx 25 26 27 28 29 2a 2c 2d 60 61 62 63 70 71 72 73 74 b0 b1 b2 b3 b4 b8 ba bb bc bd c0 c1 c2 c3 c4 c8 c9 ca cb cc cd da db e0 e1 e2 e3 e4 ec f0 f1 f2 f3 f4 f5 f6 f7 f8 f9 fa fb val 00 f7 80 08 d1 00 41 02 0a 10 0a 00 00 01 00 00 00 00 00 00 00 00 00 00 00 c0 03 01 06 80 48 90 00 00 00 00 00 00 b0 44 00 00 00 00 00 00 00 00 00 00 00 00 0e 00 00 00 00 00 def 00 f3 00 00 00 01 01 00 00 00 00 00 00 00 20 38 00 00 00 00 00 00 00 00 00 00 00 01 00 00 40 00 01 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 NA NA 00 00 0e 00 00 00 00 00 LDN 0x0a (Consumer IR) idx 30 60 61 70 f0 val 00 03 10 0b 06 def 00 03 10 0b 06 • Step 4: Type of BIOS device (see the question "How do I identify the BIOS chip on my mainboard?" below). Please send us the output of "*flashrom <http://flashrom.org/> -p internal -V*" Direct inspection shows 8-pin 16MB w25q128jv, however, flashrom doesn't seem to include that in the list of Winbond chips it probes for. dmidecode says it's an 8MB ROM, so not sure why the discrepancy • Step 5: URL to the mainboard specifications page (optional). Topton (branded) https://www.aliexpress.com/item/1005004374464011.html Can't find official specs, but there's a pho • Step 6: Any other relevant information you can provide. There's a photo of the board on the left of this BIOS update page https://www-changwang-com.translate.goog/down/74.html?_x_tr_sl=zh-CN&_x_tr_… I've been Googling both "Jasperlake coreboot" and "n5105 coreboot". I see there was news of starting to support this back in January 2020 https://www.phoronix.com/news/Coreboot-JSP-TGL-Razer-ICL Looking at some Coreboot commits, I see a "jasperlake-rvp" target was added, so I simply tried it out. It seems to build fine, but with two warnings: ** WARNING ** ADD_FSP_BINARIES isn't selected even though this SoC relies on the FSP. The resulting image won't contain the FSP binaries and will not boot unless they are added later. ** WARNING ** coreboot has been built without an Intel Firmware Descriptor. Never write a complete coreboot.rom without an IFD to your board's flash chip! You can use flashrom's IFD or layout parameters to flash only to the BIOS region. The first warning seems to suggest I can't ignore is (as it won't boot). I thus went looking for an FSP bin for this chip. Unfortunately it doesn't seem to be in the official Intel Github repo, and there's an unanswered issue there looking for it https://github.com/intel/FSP/issues/74 I hope that provides the necessary info to make a start! Thanks Marcos

2 3

Looking to get Coreboot working on Jasper Lake / N5105 mini PC with 4x Intel 2.5Gbit NICs
by Marcos Scriven 23 May '23

23 May '23

(This is a second attempt at posting - not heard back from mods, but so far as I can tell I'm a subscribe of this mail group) Hello all I'd like to get Coreboot working on a new target device, so I'll follow the 6 steps in the https://www.coreboot.org/FAQ section entitled "Will coreboot work on my machine?" It looks like someone emailed the mailing list about this back in November '22: https://mail.coreboot.org/hyperkitty/list/coreboot@coreboot.org/thread/I5HF…, but if I'm reading the archive correctly, didn't get any responses. Step 1: A very brief description of your system: board vendor, board name, CPU, northbridge, southbridge, and optionally other important details. Board Vendor: Board is branded Topton, but the board is from CWWK. CWWK mentions this board on one of their firmware update pages https://www.changwang.com/down/74.html Board Name: MW-JSL2.5G4L CPU: N5105 North Bridge Intel Jasper Lake Host Bridge rev 00 South Bridge Intel Jasper Lake PCH rev 01 • Step 2: Linux "*lspci -tvnn*" output for your system, generated by booting Linux via the original BIOS and runnning lspci. -[0000:00]-+-00.0 Intel Corporation Device [8086:4e24] +-02.0 Intel Corporation Device [8086:4e61] +-04.0 Intel Corporation Device [8086:4e03] +-14.0 Intel Corporation Device [8086:4ded] +-14.2 Intel Corporation Device [8086:4def] +-15.0 Intel Corporation Device [8086:4de8] +-15.2 Intel Corporation Device [8086:4dea] +-16.0 Intel Corporation Device [8086:4de0] +-17.0 Intel Corporation Device [8086:4dd3] +-19.0 Intel Corporation Device [8086:4dc5] +-19.1 Intel Corporation Device [8086:4dc6] +-1c.0-[01]----00.0 Phison Electronics Corporation E12 NVMe Controller [1987:5012] +-1c.4-[02]----00.0 Intel Corporation Ethernet Controller I225-V [8086:15f3] +-1c.5-[03]----00.0 Intel Corporation Ethernet Controller I225-V [8086:15f3] +-1c.6-[04]----00.0 Intel Corporation Ethernet Controller I225-V [8086:15f3] +-1c.7-[05]----00.0 Intel Corporation Ethernet Controller I225-V [8086:15f3] +-1e.0 Intel Corporation Device [8086:4da8] +-1e.3 Intel Corporation Device [8086:4dab] +-1f.0 Intel Corporation Device [8086:4d87] +-1f.3 Intel Corporation Device [8086:4dc8] +-1f.4 Intel Corporation Device [8086:4da3] \-1f.5 Intel Corporation Device [8086:4da4] • Step 3: Super I/O chip on the mainboard (report the model numbers on the actual chip, for example "Winbond W83627HF" and/or run "*superiotool <https://www.coreboot.org/Superiotool> -dV*"). Output of superiotool -dV (minus all the probing/failed): Found ITE IT8613E (id=0x8613, rev=0xc) at 0x2e Register dump: idx 20 21 22 23 24 2b val 86 13 0c 40 00 48 def 86 13 05 40 00 48 LDN 0x01 (COM1) idx 30 60 61 70 f0 val 01 03 f8 04 01 def 00 03 f8 04 00 LDN 0x04 (Environment controller) idx 30 60 61 62 63 70 f0 f1 f2 f3 f4 f5 f6 fa fb fc val 01 0a 30 0a 20 00 80 00 00 00 20 00 f0 00 00 00 def 00 02 90 02 30 09 00 00 00 00 00 NA NA 00 00 00 LDN 0x05 (Keyboard) idx 30 60 61 62 63 70 71 f0 val 00 00 60 00 64 01 02 48 def 01 00 60 00 64 01 02 48 LDN 0x06 (Mouse) idx 30 70 71 f0 val 00 0c 02 00 def 00 0c 02 00 LDN 0x07 (GPIO) idx 25 26 27 28 29 2a 2c 2d 60 61 62 63 70 71 72 73 74 b0 b1 b2 b3 b4 b8 ba bb bc bd c0 c1 c2 c3 c4 c8 c9 ca cb cc cd da db e0 e1 e2 e3 e4 ec f0 f1 f2 f3 f4 f5 f6 f7 f8 f9 fa fb val 00 f7 80 08 d1 00 41 02 0a 10 0a 00 00 01 00 00 00 00 00 00 00 00 00 00 00 c0 03 01 06 80 48 90 00 00 00 00 00 00 b0 44 00 00 00 00 00 00 00 00 00 00 00 00 0e 00 00 00 00 00 def 00 f3 00 00 00 01 01 00 00 00 00 00 00 00 20 38 00 00 00 00 00 00 00 00 00 00 00 01 00 00 40 00 01 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 NA NA 00 00 0e 00 00 00 00 00 LDN 0x0a (Consumer IR) idx 30 60 61 70 f0 val 00 03 10 0b 06 def 00 03 10 0b 06 • Step 4: Type of BIOS device (see the question "How do I identify the BIOS chip on my mainboard?" below). Please send us the output of "*flashrom <http://flashrom.org/> -p internal -V*" Direct inspection shows 8-pin 16MB w25q128jv, however, flashrom doesn't seem to include that in the list of Winbond chips it probes for. dmidecode says it's an 8MB ROM, so not sure why the discrepancy • Step 5: URL to the mainboard specifications page (optional). Topton (branded) https://www.aliexpress.com/item/1005004374464011.html Can't find official specs, but there's a pho • Step 6: Any other relevant information you can provide. There's a photo of the board on the left of this BIOS update page https://www-changwang-com.translate.goog/down/74.html?_x_tr_sl=zh-CN&_x_tr_… I've been Googling both "Jasperlake coreboot" and "n5105 coreboot". I see there was news of starting to support this back in January 2020 https://www.phoronix.com/news/Coreboot-JSP-TGL-Razer-ICL Looking at some Coreboot commits, I see a "jasperlake-rvp" target was added, so I simply tried it out. It seems to build fine, but with two warnings: ** WARNING ** ADD_FSP_BINARIES isn't selected even though this SoC relies on the FSP. The resulting image won't contain the FSP binaries and will not boot unless they are added later. ** WARNING ** coreboot has been built without an Intel Firmware Descriptor. Never write a complete coreboot.rom without an IFD to your board's flash chip! You can use flashrom's IFD or layout parameters to flash only to the BIOS region. The first warning seems to suggest I can't ignore is (as it won't boot). I thus went looking for an FSP bin for this chip. Unfortunately it doesn't seem to be in the official Intel Github repo, and there's an unanswered issue there looking for it https://github.com/intel/FSP/issues/74 I hope that provides the necessary info to make a start! Thanks Marcos

1 0

[coreboot - Bug #446] Optiplex 9010 No Post
by Aaron Burton 23 May '23

23 May '23

Issue #446 has been updated by Aaron Burton. Martin Roth wrote in #note-6: > Hi Aaron, any update on this bug? Apologies on the delay, building with APICX2 instead of APIC is what was giving me trouble. Unrelated but I bought a Xeon for it a while back as well but it doesn't post with coreboot, Core i-series chips boot fine. ---------------------------------------- Bug #446: Optiplex 9010 No Post https://ticket.coreboot.org/issues/446#change-1536 * Author: Aaron Burton * Status: New * Priority: Normal * Category: board support * Target version: 4.19 * Start date: 2023-01-09 ---------------------------------------- Working with an Optiplex 9010 SFF, configured and built coreboot as usual against the Optiplex 9010 SFF platform in menuconfig. Left every other setting alone in terms of configuration. Included EC firmware, ME, GBE, IFD blobs from stock firmware into my build. Turns on with fans at normal speed (not full blast), but no keyboard illumination or display output. Using SeaBIOS 1.16.1. Any suggestions as to what may be going on? Thanks. -- 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 #446] Optiplex 9010 No Post
by nolan p 22 May '23

22 May '23

Issue #446 has been updated by nolan p. I also have this issue with my 7010 DT when building from `master` with blobs from my stock firmware (SMSC, GBE, ME, IFD). Both `SeaBIOS 1.16.2` and `edk2` from MrChromebox and tianocore do not POST, though it seems like the fans will spin. My config is mostly default otherwise. ---------------------------------------- Bug #446: Optiplex 9010 No Post https://ticket.coreboot.org/issues/446#change-1535 * Author: Aaron Burton * Status: New * Priority: Normal * Category: board support * Target version: 4.19 * Start date: 2023-01-09 ---------------------------------------- Working with an Optiplex 9010 SFF, configured and built coreboot as usual against the Optiplex 9010 SFF platform in menuconfig. Left every other setting alone in terms of configuration. Included EC firmware, ME, GBE, IFD blobs from stock firmware into my build. Turns on with fans at normal speed (not full blast), but no keyboard illumination or display output. Using SeaBIOS 1.16.1. Any suggestions as to what may be going on? Thanks. -- 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 - Cleanup #490] (New) Verify copyrights on files with BSD, X11, MIT, HPND, and ISC licenses
by Martin Roth 20 May '23

20 May '23

Issue #490 has been reported by Martin Roth. ---------------------------------------- Cleanup #490: Verify copyrights on files with BSD, X11, MIT, HPND, and ISC licenses https://ticket.coreboot.org/issues/490 * Author: Martin Roth * Status: New * Priority: Normal * Target version: 4.21 * Start date: 2023-05-20 ---------------------------------------- Files with these licenses contain a phrase similar to "provided that the above copyright notice appears in all copies". This requires that the copyrights be left in these files when they are brought into coreboot from other projects, and that they should not have been removed in the copyright cleanup. The coreboot project does not want new copyright notices added to these files going forward, similar to the position on GPL files, however the existing copyright notices need to be grandfathered in for these files. -- 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 - Other #479] (New) [legal] ISC License copyright violation in ubsan
by Jonas Termansen 20 May '23

20 May '23

Issue #479 has been reported by Jonas Termansen. ---------------------------------------- Other #479: [legal] ISC License copyright violation in ubsan https://ticket.coreboot.org/issues/479 * Author: Jonas Termansen * Status: New * Priority: Normal * Target version: none * Start date: 2023-04-09 ---------------------------------------- Hi :) coreboot has removed my copyright statement from the ubsan implementation, which violates my copyright as licensed to you under the terms of the ISC License: ``` * Copyright (c) 2014, 2015 Jonas 'Sortie' Termansen. * * Permission to use, copy, modify, and distribute this software for any * purpose with or without fee is hereby granted, provided that the above * copyright notice and this permission notice appear in all copies. * * ... ``` The file in question is: https://github.com/coreboot/coreboot/blob/master/src/lib/ubsan.c The file does clearly state it's forked from my original ubsan implementation: https://gitlab.com/sortix/sortix/-/blob/master/libc/ubsan/ubsan.c However, the coreboot copy has removed my copyright notice, which is one of only two terms of the license. It's fine that the permission notice has been changed to `SPDX-License-Identifier: ISC` which is unambiguously information preserving, but removing my copyright notice is a loss of information. The copyright notice was removed in https://github.com/coreboot/coreboot/commit/16849bbe0c8a79277e1a682dcb42eaf… which moved my name to AUTHORS. Although a mention in AUTHORS is appreciated, it removes the association between the file's contents and my identity and my moral rights to my work. Although the full information is available in the git history, that's not good enough. I'm concerned that further copies of the file in other projects may lose the authorship information entirely. Please restore my copyright notice at the top of the file :) Jonas 'Sortie' Termansen -- 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 3

[coreboot - Bug #141] GRUB payload hangs in HP Elitebooks
by Riku Viitanen 18 May '23

18 May '23

Issue #141 has been updated by Riku Viitanen. Patch has now been merged to GRUB upstream. https://git.savannah.gnu.org/cgit/grub.git/commit/?id=830456a6e3b6ac92d10f9… ---------------------------------------- Bug #141: GRUB payload hangs in HP Elitebooks https://ticket.coreboot.org/issues/141#change-1531 * Author: Iru Cai * Status: New * Priority: Normal * Assignee: Iru Cai * Start date: 2017-09-19 ---------------------------------------- There may be some problem when initializing the keyboard controller, but SeaBIOS payload works fine. Using GRUB payload directly or chainload GRUB payload with SeaBIOS will both hang the system. I modified GRUB and find it hangs in set_scancodes(void), when calling the first write_mode. After ``grub_outb (mode, KEYBOARD_REG_DATA);``, the ``keyboard_controller_wait_until_ready()`` function goes to an infinite loop. ~~~ write_mode (int mode) { unsigned i; for (i = 0; i < GRUB_AT_TRIES; i++) { grub_uint8_t ack; keyboard_controller_wait_until_ready (); grub_outb (0xf0, KEYBOARD_REG_DATA); keyboard_controller_wait_until_ready (); grub_outb (mode, KEYBOARD_REG_DATA); keyboard_controller_wait_until_ready (); ack = wait_ack (); if (ack == GRUB_AT_NACK) continue; if (ack == GRUB_AT_ACK) break; return 0; } return (i != GRUB_AT_TRIES); } ~~~ ---Files-------------------------------- seabios.log (31.5 KB) 0005-at-keyboard-timeout.patch (1.09 KB) -- 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

Tree maintenance and build nodes
by Kyösti Mälkki 17 May '23

17 May '23

Hi A couple of questions, less technical than usual. Do we have any sample cases of bringing boards back from older branches? I would like to have a branch set up for bringing back some selected AGESA from 4.18 branch. My plan would be to backport features from ToT into said new branch and resolve issues there. Once considered clean enough, it should be a three commit drop (vendorcode, platform, boards) to land on master? Is there someone (corporate) currently funding or hiring personnel with reviews and tree maintenance as a priority? Is there currently anyone actually assigning from their existing resources to put attention to frameworks, while customers' board ports and resolving their issues have tight schedules? Regards, Kyösti Mälkki

6 7

Jump to page:

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

2003

2002

coreboot