coreboot May 2024

coreboot@coreboot.org

9 participants
29 discussions

[coreboot - Bug #121] T520: Hangs in OS
by Anastasios Koutian 31 May '24

31 May '24

Issue #121 has been updated by Anastasios Koutian. I tried booting with kernel command line parameter idle=nomwait. There were no freezes for 1 week, 5 days and 16 hours, which was not possible previously. After this, I powered down and removed the parameter to see what happens. The system froze after 15 hours and 7 minutes. Intel PCM is showing no negative impact on idle power consumption with idle=nomwait. I recommend to people following this bug to try this out and confirm if it works for them. ---------------------------------------- Bug #121: T520: Hangs in OS https://ticket.coreboot.org/issues/121#change-1856 * 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-05-29 - coreboot Leadership Meeting Canceled
by mina＠coreboot.org 30 May '24

30 May '24

Dear community, Kindly be informed that the coreboot leadership meeting scheduled for Wednesday, May 29, 2024, has been canceled due to the absence of agenda items.[1] We apologize for any inconvenience this may cause and appreciate your understanding. Best Regards, Mina Asante. [1](https://docs.google.com/document/d/1NRXqXcLBp5pFkHiJbrLdv3Spqh1Hu086HYkK… g=h.ual5qamha2xi)

3 2

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

24 May '24

Dear community, Kindly note that we have an upcoming coreboot leadership meeting scheduled for Wednesday, May 29, 2024.[1] We encourage that you please take a moment to update the current agenda items with matters you wish to see discussed during the meeting.[2] Thank you for your continued commitment to the coreboot project. Best regards, Mina Asante. [1](https://www.coreboot.org/calendar.html) [2](https://docs.google.com/document/d/1NRXqXcLBp5pFkHiJbrLdv3Spqh1Hu086HYkK…

1 0

[coreboot - Feature #461] (In Progress) Replacing Haswell mrc.bin blob with free software
by Angel Pons 23 May '24

23 May '24

Issue #461 has been updated by Angel Pons. Category changed from board support to chipset configuration Status changed from New to In Progress Start date changed from 02/16/2023 to 04/01/2020 % Done changed from 0 to 30 Related links updated Affected hardware changed from T440p and other to All Haswell mainboards # Current state of the meme magic (Haswell NRI) ## Done - Native non-raminit stuff (already submitted): needed for 9-series boards with Broadwell MRC.bin e.g. https://review.coreboot.org/68188 - Bare minimum memory initialisation (just enough meme magic to be able to boot): patch train up until https://review.coreboot.org/64198 - S3 suspend/resume and fast boot support: https://review.coreboot.org/81897 - Sense amplifier offset training: https://review.coreboot.org/81948 ## Implemented internally in the giant bowl of spaghetti, but in need to clean up the code before publishing - 1D margin centering algorithms (used for various training steps) - Setting non-training command rate (to 1N or 2N, we currently remain at 3T) and LCT (Late Command Training) - 2D margin centering algorithms (used for various training steps) - Power training (optimisation meme magic to reduce power consumption) - TAT (Turnaround Training, a performance improvement) - The raminit console (a half-arsed thing that allows playing around with settings over UART/usbdebug) ## Not implemented or not working yet - Broadwell support (I once got a Broadwell ULT system to boot without MRC, but I had to commit unspeakable horrors to the already messy codebase) - Properly programming some registers about DIMM energy (doesn't seem to be required, but the logic to program these is horribly convoluted and I haven't felt like figuring out how it works) - Automatic overclocking support (will require redesigning how the MPLL handling works, because it currently stinks) # TL;DR - With what's currently submitted, choosing Haswell NRI in menuconfig **WILL NOT BOOT**. It says "NOT WORKING" in the prompt. - Current top of tree (what you should use if you want to try Haswell NRI) is https://review.coreboot.org/81948 - With the aforementioned changes from Gerrit, booting should work. S3 resume should also work, but please test in advance. - **BACK UP YOUR STUFF!** I will NOT be held responsible by any data losses arising from the use of the current state of Haswell NRI. - Because not all training steps are ready yet, performance and power consumption are not optimal. Fix is to finish upstreaming them. - Also, do NOT try to overclock the RAM under any circumstances. You will only make your system much more unstable for no reason. ---------------------------------------- Feature #461: Replacing Haswell mrc.bin blob with free software https://ticket.coreboot.org/issues/461#change-1854 * Author: akjuxr3 akjuxr3 * Status: In Progress * Priority: Normal * Assignee: Angel Pons * Category: chipset configuration * Target version: none * Start date: 2020-04-01 * Related links: https://review.coreboot.org/q/topic:haswell-nri * Affected hardware: All Haswell mainboards ---------------------------------------- Currently in case of the ability to run as less amount of closed source software as possible and still have Microcode updates the reduced Intel ME with disabled bit in IFD and the lga1155 or the mobile versions of those cpus are the only option for x86_64 out there. The next cpu generation (Haswell) inside for example T440p and W541 require the binary blob mrc.bin Are there any plans of replacing the Haswell mrc.bin with free software? Or have the x86_64 platform be given up when the goal is to run just free software and the people should move to aarch64 or risc-v? -- 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 - Feature #540] (New) Support for Lenovo ThinkPad X250 - the competitor to the shortly added HP EliteBook 820 G2
by akjuxr3 akjuxr3 23 May '24

23 May '24

Issue #540 has been reported by akjuxr3 akjuxr3. ---------------------------------------- Feature #540: Support for Lenovo ThinkPad X250 - the competitor to the shortly added HP EliteBook 820 G2 https://ticket.coreboot.org/issues/540 * Author: akjuxr3 akjuxr3 * Status: New * Priority: Normal * Category: board support * Target version: none * Start date: 2024-05-22 * Affected hardware: Lenovo Thinkpad X250 ---------------------------------------- Coreboot now have support for the HP EliteBook 820 G2. This is great, but sadly the keyboard is for a person using Thinkpad keyboards forever not usable. The Thinkpad X250 is the competitor to the HP EliteBook 820 G2. https://www.notebookcheck.net/Face-Off-HP-EliteBook-820-G2-vs-Lenovo-ThinkP… The X250 also have a Full-HD IPS screen. This would also fix the problems many people have with the X230 and spend much time and effort to get a Full-HD IPS screen running in the X230. Nico Huber have(had?) such a X250: https://review.coreboot.org/c/coreboot/+/23820/7#message-04cf9f804c1292f457… Other coreboot developer also seem to have a X250: https://review.coreboot.org/c/coreboot/+/51179 Have someone taken a deeper look into the Thinkpad X250? Is there something special why suddenly the HP EliteBook 820 G2 got supported instead of a typical Thinkpad like it was the case for years at coreboot? -- 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 2

[coreboot - Feature #461] Replacing Haswell mrc.bin blob with free software
by akjuxr3 akjuxr3 22 May '24

22 May '24

Issue #461 has been updated by akjuxr3 akjuxr3. Category set to board support Assignee set to Angel Pons Affected hardware set to T440p and other > Already being worked on, refer to https://review.coreboot.org/q/topic:haswell-nri Great to see active work on this. Lets hope it get merged soon. There are many great features planed like for example: "One of my future plans (automatic RAM overclocking) would try the highest possible frequency and, if training cannot succeed, slow down the MPLL to the next available frequency." ---------------------------------------- Feature #461: Replacing Haswell mrc.bin blob with free software https://ticket.coreboot.org/issues/461#change-1851 * Author: akjuxr3 akjuxr3 * Status: New * Priority: Normal * Assignee: Angel Pons * Category: board support * Target version: none * Start date: 2023-02-16 * Related links: https://review.coreboot.org/c/coreboot/+/52659 * Affected hardware: T440p and other ---------------------------------------- Currently in case of the ability to run as less amount of closed source software as possible and still have Microcode updates the reduced Intel ME with disabled bit in IFD and the lga1155 or the mobile versions of those cpus are the only option for x86_64 out there. The next cpu generation (Haswell) inside for example T440p and W541 require the binary blob mrc.bin Are there any plans of replacing the Haswell mrc.bin with free software? Or have the x86_64 platform be given up when the goal is to run just free software and the people should move to aarch64 or risc-v? -- 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

Add support to Fujitsu Esprimo P2760
by Noob Team 22 May '24

22 May '24

Hello This desktop build doesn't have coreboot support. I want to know if it'd be possible to add support to it. Motherboard details in the attached. I'm willing to do all the tests necessary to make it work. Thank you. Regards

1 0

[coreboot - Other #539] (New) Add support to motherboard
by User Nick 22 May '24

22 May '24

Issue #539 has been reported by User Nick. ---------------------------------------- Other #539: Add support to motherboard https://ticket.coreboot.org/issues/539 * Author: User Nick * Status: New * Priority: Normal * Category: board support * Target version: none * Start date: 2024-05-22 ---------------------------------------- Hi I'd like to get coreboot running in a motherboard that currently doesn't have support. If some developer likes to get this done, I'm willing to provide the flashrom dumps gather the necessary data and do all the required testing. Thank you all. -- 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 #538] (New) [Soft Brick] x230 Dock Causes Internal Display to "Permanently" Malfunction
by Brian L 22 May '24

22 May '24

Issue #538 has been reported by Brian L. ---------------------------------------- Bug #538: [Soft Brick] x230 Dock Causes Internal Display to "Permanently" Malfunction https://ticket.coreboot.org/issues/538 * Author: Brian L * Status: New * Priority: High * Target version: none * Start date: 2024-05-14 * Affected hardware: Lenovo x230 ---------------------------------------- Environment: - Lenovo x230 - Stock screen replaced with Pixel Qi (not sure if relevant) (plug & play LVDS) - Coreboot using Heads (coreboot + linuxboot) - Official lenovo docking station connected to external monitor via DisplayPort Bug Trigger: Using Heads/coreboot fine for years with my Pixel Qi screen modded x230. I then bought a Lenovo docking station. Booted up, everything worked fine. Disconnected from dock, booted up, and there was no bios screen. Screen did not turn on until taken over by Linux Kernel. Once in userspace, wayland could no longer identify the monitor as a Pixel Qi or its proper resolution. EDID is blank. Booting with docking station allows bios to show on external display. Restarting did *not* fix the issue, reflashing heads did *not* fix the issue, flashing skulls (coreboot + seabios) did *not* fix the issue. Flashing stock bios *did fix* the issue. I can now see BIOS screen and get proper EDID in userspace whether on the dock or not. *However* reflashing coreboot again, even coming from stock bios working state, and I immediately now no longer get a BIOS screen or EDID, even without ever introducing the dock again. Essentially now bricked with anything but stock bios. -- 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 19

Micron e.MMC Memory(MTFC64GAPALBH-IT) is not detected
by Murali Ayyappan 21 May '24

21 May '24

Hi, Our custom board is designed based on Denverton SOC. The used boot loader is coreboot-4.13 version and Linux kernel 5.10.30 version. In our design, the eMMC interface is used, and connected Micron e.MMC memory(MTFC64GAPALBH-IT) to it. The eMMC is enabled in coreboot device tree file. Here's the snippet from ./src/mainboard/intel/harcuvar/devicetree.cb file. device pci 1a.2 on end # UART 2 device pci 1c.0 on end # eMMC device pci 1f.0 on end # LPC bridge device pci 1f.2 on end # PMC/ACPI and, in linux kernel following kernel modules are enabled for host controller, # MMC/SD/SDIO Host Controller Drivers # # CONFIG_MMC_DEBUG is not set CONFIG_MMC_SDHCI=y CONFIG_MMC_SDHCI_IO_ACCESSORS=y CONFIG_MMC_SDHCI_PCI=y CONFIG_MMC_RICOH_MMC=y CONFIG_MMC_SDHCI_ACPI=y # CONFIG_MMC_SDHCI_PLTFM is not set # CONFIG_MMC_WBSD is not set # CONFIG_MMC_TIFM_SD is not set # CONFIG_MMC_SPI is not set # CONFIG_MMC_CB710 is not set # CONFIG_MMC_VIA_SDMMC is not set # CONFIG_MMC_VUB300 is not set # CONFIG_MMC_USHC is not set # CONFIG_MMC_USDHI6ROL0 is not set CONFIG_MMC_CQHCI=y and for memory device enabled following kernel modules, CONFIG_MMC=y CONFIG_PWRSEQ_EMMC=y CONFIG_PWRSEQ_SIMPLE=y CONFIG_MMC_BLOCK=y CONFIG_MMC_BLOCK_MINORS=8 Per SOC datasheet the host controller is seen in Bus 0, Device 28 and Function 0 in PCI bus, but the connected memory is not detected under this controller. when added debug prints in linux kernel driver source files, found that the mmc_rescan( ) function is failing due to mmc_attach failing with errno -110. Thanks, Murali

1 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

2003

2002

coreboot May 2024