coreboot August 2021

coreboot@coreboot.org

27 participants
26 discussions

[RFC] Intel split stack IIO design support in coreboot - new multidomain approach
by Szafranski, MariuszX 20 Aug '21

20 Aug '21

Hi, RFC/initial proposal how to implement split IIO in coreboot: [RFC] Intel IIO split stack - multidomain approach (I38ac830e) * Gerrit Code Review (coreboot.org)<https://review.coreboot.org/c/coreboot/+/56263> thx for all comments, suggestions BR, Mariusz -------------------------------------------------------------- Intel Research and Development Ireland Limited Registered in Ireland Registered Office: Collinstown Industrial Park, Leixlip, County Kildare Registered Number: 308263 This e-mail and any attachments may contain confidential material for the sole use of the intended recipient(s). Any review or distribution by others is strictly prohibited. If you are not the intended recipient, please contact the sender and delete all copies.

1 0

denverton_ns: failed to write RW_MRC_CACHE
by Sumo 20 Aug '21

20 Aug '21

Hi, I'm stuck in a problem where coreboot fails to write the MRC cache in the SPI Flash. Below is the log output: FMAP: area RW_MRC_CACHE found @ 810000 (65536 bytes) MRC: Checking cached data update for 'RW_MRC_CACHE'. SF: Detected 00 0000 with sector size 0x1000, total 0x1000000 MRC: no data in 'RW_MRC_CACHE' MRC: cache data 'RW_MRC_CACHE' needs update. SPI Transaction Error at Flash Offset 810000 HSFSTS = 0x01046003 REGF metadata allocation failed: 1949 data blocks 4096 total blocks MRC: failed to update 'RW_MRC_CACHE'. Any clues? Thanks, Sumo

3 5

coreboot Wiki contribution workflow, old Wiki and how to increase the contributions
by Mike Banon 20 Aug '21

20 Aug '21

On Fri, Aug 20, 2021 at 10:07 AM Keith Emery <k.emery.nbn(a)internode.on.net> wrote: > Guy's if the WiKi is unmaintained can we just get rid of it. Google loves > directing people to it, and it's incredibly confusing / misleading. Before getting rid of the old Wiki, the community should look through it page-by-page and move all the important still-valid stuff to the new Wiki. To avoid losing anything of value! Of course, if the contribution process to the new Wiki would've been a real-time WYSIWYG write&publish process just like at so many established successful Wikis - and without requiring the upvotes from other people to commit each contribution! - there'd be a lot more activity and this would have already happened. I believe that the current process of contributing to the coreboot documentation is inefficient, and not just me. On one of 3mdeb's past vBeers, Alexey Vazhnov described how tricky could it be to get merged the coreboot docs and shared his experiences at this post: https://www.reddit.com/r/coreboot/comments/lm7jh8/my_pain_with_documentatio… Old wiki died because the people willing to contribute were prevented from doing so by a closed registration roadblock and had to go elsewhere with their manuals - which now are scattered all over the Internet, i.e. stuff like this could've been on a coreboot wiki - http://dangerousprototypes.com/docs/Flashing_KB9012_with_Bus_Pirate#Craftin… . But, if the simplification of Wiki contribution process isn't done out of fear of bots/spammers, you can always set up an advanced math captcha like _____||| 3*x^7 + x^6 + 2*x^5 + 4*x^4 + 4*x^3 lim ------------------------------------------ x->0 ||| 5*x^5 + 4*x^4 + 3*x^3 which takes a minute to learn how to solve even if you don't know how at the moment.

1 0

Re: Firmware another laptop
by Keith Emery 20 Aug '21

20 Aug '21

The list of supported hardware, and other information is available here: https://doc.coreboot.org/mainboard/index.html Of course with enough information you can always be able to run core-boot, the caveat being you have to write the code for it. On the off chance that you do, and it is working, please remember to push the changes. It's incredibly frustrating to have a report that says: 'yeah this works, just use this git commit that doesn't exist'. I wound up buying two F2A85-M main-boards only to find the code has mysteriously disappeared. PS: Guy's if the WiKi is unmaintained can we just get rid of it. Google loves directing people to it, and it's incredibly confusing / misleading. .On 20/8/21 8:30 am, Stefano wrote: > Thank you for the answer. > This is my machine: > https://termbin.com/yiyx <https://termbin.com/yiyx> > > System: Kernel: 5.4.0-81-generic x86_64 bits: 64 compiler: gcc v: 9.3.0 Desktop: Cinnamon 5.0.5 > wm: muffin dm: LightDM Distro: Linux Mint 20.2 Uma base: Ubuntu 20.04 focal > Machine: Type: Portable System: Alienware product: Alienware 17 v: A17 serial: <filter> Chassis: > type: 8 v: A17 serial: <filter> > Mobo: Alienware model: 04WT2G v: A00 serial: <filter> UEFI: Alienware v: A17 > date: 07/22/2019 > Battery: ID-1: BAT1 charge: 70.9 Wh condition: 70.9/88.8 Wh (80%) volts: 17.0/14.8 > model: Simplo PABAS0241231 serial: <filter> status: Full > CPU: Topology: Quad Core model: Intel Core i7-4910MQ bits: 64 type: MT MCP arch: Haswell > rev: 3 L2 cache: 8192 KiB > flags: avx avx2 lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx bogomips: 46296 > Speed: 873 MHz min/max: 800/4100 MHz Core speeds (MHz): 1: 798 2: 798 3: 798 4: 798 > 5: 798 6: 799 7: 798 8: 802 > Graphics: Device-1: NVIDIA GK104M [GeForce GTX 880M] vendor: Dell driver: nvidia v: 460.91.03 > bus ID: 01:00.0 chip ID: 10de:1198 > Display: x11 server: X.Org 1.20.11 driver: nvidia > unloaded: fbdev,modesetting,nouveau,vesa resolution: 1920x1080~60Hz > OpenGL: renderer: GeForce GTX 880M/PCIe/SSE2 v: 4.6.0 NVIDIA 460.91.03 > direct render: Yes > Audio: Device-1: Intel 8 Series/C220 Series High Definition Audio vendor: Dell > driver: snd_hda_intel v: kernel bus ID: 00:1b.0 chip ID: 8086:8c20 > Device-2: NVIDIA GK104 HDMI Audio vendor: Dell driver: snd_hda_intel v: kernel > bus ID: 01:00.1 chip ID: 10de:0e0a > Sound Server: ALSA v: k5.4.0-81-generic > Network: Device-1: Qualcomm Atheros Killer E220x Gigabit Ethernet vendor: Dell driver: alx > v: kernel port: 3000 bus ID: 08:00.0 chip ID: 1969:e091 > IF: enp8s0 state: down mac: <filter> > Device-2: Intel Wireless 7260 driver: iwlwifi v: kernel port: 3000 bus ID: 0a:00.0 > chip ID: 8086:08b1 > IF: wlp10s0 state: up mac: <filter> > Drives: Local Storage: total: 1.14 TiB used: 32.96 GiB (2.8%) > ID-1: /dev/sda vendor: Toshiba model: MQ01ABD100 size: 931.51 GiB speed: 6.0 Gb/s > serial: <filter> > ID-2: /dev/sdb vendor: LITE-ON IT model: LMT-256M6M mSATA 256GB size: 238.47 GiB > speed: 6.0 Gb/s serial: <filter> > RAID: Hardware-1: Intel 82801 Mobile SATA Controller [RAID mode] driver: ahci v: 3.0 > bus ID: 00:1f.2 chip ID: 8086.282a > Partition: ID-1: / size: 231.54 GiB used: 16.28 GiB (7.0%) fs: ext4 dev: /dev/dm-1 > ID-2: /boot size: 704.5 MiB used: 407.9 MiB (57.9%) fs: ext4 dev: /dev/sdb2 > ID-3: swap-1 size: 976.0 MiB used: 0 KiB (0.0%) fs: swap dev: /dev/dm-2 > Sensors: System Temperatures: cpu: 50.0 C mobo: N/A gpu: nvidia temp: 50 C > Fan Speeds (RPM): N/A > Repos: No active apt repos in: /etc/apt/sources.list > Active apt repos in: /etc/apt/sources.list.d/freedownloadmanager.list > 1: deb [arch=amd64] https: //debrepo.freedownloadmanager.org/ bionic main > Active apt repos in: /etc/apt/sources.list.d/official-package-repositories.list > 1: deb http: //packages.linuxmint.com uma main upstream import backport > 2: deb http: //archive.ubuntu.com/ubuntu <http://archive.ubuntu.com/ubuntu> focal main restricted universe multiverse > 3: deb http: //archive.ubuntu.com/ubuntu <http://archive.ubuntu.com/ubuntu> focal-updates main restricted universe multiverse > 4: deb http: //archive.ubuntu.com/ubuntu <http://archive.ubuntu.com/ubuntu> focal-backports main restricted universe multiverse > 5: deb http: //security.ubuntu.com/ubuntu/ <http://security.ubuntu.com/ubuntu/> focal-security main restricted universe multiverse > 6: deb http: //archive.canonical.com/ubuntu/ <http://archive.canonical.com/ubuntu/> focal partner > Active apt repos in: /etc/apt/sources.list.d/spotify.list > 1: deb http: //repository.spotify.com stable non-free > Info: Processes: 293 Uptime: 4h 42m Memory: 15.56 GiB used: 1.82 GiB (11.7%) Init: systemd > v: 245 runlevel: 5 Compilers: gcc: 9.3.0 alt: 9 Client: Unknown python3.8 client > inxi: 3.0.38 > > > Sent with ProtonMail <https://protonmail.com/> Secure Email. > > ‐‐‐‐‐‐‐ Original Message ‐‐‐‐‐‐‐ > Il venerdì 20 agosto 2021 00:11, Keith Emery > <k.emery.nbn(a)internode.on.net> ha scritto: >> >> I think you meant to ask if it's possible to do. That can't be >> answered without more information about the hardware... A lot more. >> >> At a minimum the precise model of mainboard, or a precise model number. >> >> >> On 20/8/21 12:02 am, Stefano via coreboot wrote: >>> Good morning I can install the coreboot firmware on my dell >>> alienware 17 with Linux mint (updated to the latest version)? >>> >>> Best regards >>> Stefano >>> >>> >>> Sent with ProtonMail <https://protonmail.com/> Secure Email. >>> >>> >>> _______________________________________________ >>> coreboot mailing list --coreboot(a)coreboot.org <mailto:coreboot@coreboot.org> >>> To unsubscribe send an email tocoreboot-leave(a)coreboot.org <mailto:coreboot-leave@coreboot.org> >

1 0

Firmware another laptop
by Stefano 20 Aug '21

20 Aug '21

Good morning I can install the coreboot firmware on my dell alienware 17 with Linux mint (updated to the latest version)? Best regards Stefano Sent with [ProtonMail](https://protonmail.com/) Secure Email.

3 2

Re: Build for F2A85-M Foobared, any ideas?
by Paul Menzel 17 Aug '21

17 Aug '21

Dear Keith, Am 16.08.21 um 12:39 schrieb Keith Emery: > I went one further and just deleted the whole working directory, > re-cloned coreboot and built using that exact configuration. All to > little avail. Please do not leave the other questions/requests unanswered. > How do I go about finding the exact commit that was used in the log? It’s in the path name or logs in the directory I referenced: 4.13-917-g192177d34d refers to commit hash 192177d34d. Kind regards, Paul PS: It’s common to interleaved style when replying (on mailing lists).

3 3

SPI Flash console output
by Keith Emery 17 Aug '21

17 Aug '21

Does anybody happen to know when or why SPI Flash console output broke? I kind of need it. The build only fails when I enable said option. The error is as follows, name of home directory redacted: coreboot/util/crossgcc/xgcc/bin/i386-elf-ld.bfd: build/bootblock/drivers/spi/spi-generic.o: in function `spi_setup_slave': coreboot/src/drivers/spi/spi-generic.c:118: undefined reference to `spi_ctrlr_bus_map_count' coreboot/util/crossgcc/xgcc/bin/i386-elf-ld.bfd: coreboot/src/drivers/spi/spi-generic.c:119: undefined reference to `spi_ctrlr_bus_map' coreboot/util/crossgcc/xgcc/bin/i386-elf-ld.bfd: coreboot/src/drivers/spi/spi-generic.c:119: undefined reference to `spi_ctrlr_bus_map' coreboot/util/crossgcc/xgcc/bin/i386-elf-ld.bfd: coreboot/src/drivers/spi/spi-generic.c:121: undefined reference to `spi_ctrlr_bus_map' make: *** [src/arch/x86/Makefile.inc:90: build/cbfs/fallback/bootblock.debug] Error 1

1 0

Denverton: NVMe not detected when serial console logs are disabled
by Sumo 16 Aug '21

16 Aug '21

Hi, The NVMe is not detected when serial console logs are disabled, I mean by setting both Coreboot log_level=Error (or less) and FSP PcdFspDebugPrintErrorLevel=NoDebug. Looks like the enumeration fails then further on the device is not listed in the UEFI FW (same issue shown in either CorebootPayloadPkg or UefiPayloadPkg). When Linux boots the device appears normally. The problem is fixed by adding a small delay inside dev_enumerate() - a 20ms delay at the very beginning of the function is enough. I'm wondering if there is a better solution for this, the device is already defined in the devicetree.cb (set as on). Maybe coreboot is too fast and the NVMe is still booting up - or the PCIe link is still training, not sure. Coreboot doesn't retry if the device is not detected right away? Kind regards, Sumo

2 1

Stuck on Coreboot logo
by Leo Roberts 16 Aug '21

16 Aug '21

I don't know if you offer any support but I have inherited a HP G4 chromebook stuck on the Coreboot logo. The escape key does not work even with an external keyboard. Can you point me in the right direction? Thank you, Dr. Leo Roberts

1 0

Build for F2A85-M Foobared, any ideas?
by Keith Emery 16 Aug '21

16 Aug '21

coreboot-4.14-1405-gad08265740-dirty Sun Aug 15 07:12:41 UTC 2021 bootblock starting (log level: 7)... CBFS: Found 'fallback/romstage' @0x30e00 size 0x4c910 in mcache @0x00034f7c BS: bootblock times (exec / console): total (unknown) / 12 ms coreboot-4.14-1405-gad08265740-dirty Sun Aug 15 07:12:41 UTC 2021 romstage starting (log level: 7)... APIC 00: CPU Family_Model = 00000663 APIC 00: ** Enter AmdInitReset [00020007] ASSERTION ERROR: file 'src/drivers/amd/agesa/state_machine.c', line 256 ASSERTION ERROR: file 'src/vendorcode/amd/agesa/f15tn/Proc/CPU/heapManager.c', line 332 ASSERTION ERROR: file 'src/vendorcode/amd/agesa/f15tn/Proc/Fch/Interface/InitResetDef.c', line 70 ASSERTION ERROR: file 'src/vendorcode/amd/agesa/f15tn/Proc/Fch/Interface/InitResetDef.c', line 73 Fch OEM config in INIT RESET ASSERTION ERROR: file 'src/vendorcode/amd/agesa/common/amdlib.c', line 768 ASSERTION ERROR: file 'src/vendorcode/amd/agesa/common/amdlib.c', line 926 ASSERTION ERROR: file 'src/vendorcode/amd/agesa/common/amdlib.c', line 817 ASSERTION ERROR: file 'src/vendorcode/amd/agesa/common/amdlib.c', line 926 ASSERTION ERROR: file 'src/vendorcode/amd/agesa/common/amdlib.c', line 768 ASSERTION ERROR: file 'src/vendorcode/amd/agesa/common/amdlib.c', line 926 ASSERTION ERROR: file 'src/vendorcode/amd/agesa/common/amdlib.c', line 817 ASSERTION ERROR: file 'src/vendorcode/amd/agesa/common/amdlib.c', line 926 ASSERTION ERROR: file 'src/vendorcode/amd/agesa/common/amdlib.c', line 768 ASSERTION ERROR: file 'src/vendorcode/amd/agesa/common/amdlib.c', line 926 ASSERTION ERROR: file 'src/vendorcode/amd/agesa/common/amdlib.c', line 817 ASSERTION ERROR: file 'src/vendorcode/amd/agesa/common/amdlib.c', line 926 ASSERTION ERROR: file 'src/vendorcode/amd/agesa/common/amdlib.c', line 768 ASSERTION ERROR: file 'src/vendorcode/amd/agesa/common/amdlib.c', line 926 ASSERTION ERROR: file 'src/vendorcode/amd/agesa/common/amdlib.c', line 817 ASSERTION ERROR: file 'src/vendorcode/amd/agesa/common/amdlib.c', line 926 AmdInitReset() returned AGESA_SUCCESS APIC 00: Heap in LocalCache (2) at 0x00400000 APIC 00: ** Exit AmdInitReset [00020007] APIC 00: ** Enter AmdInitEarly [00020002] ASSERTION ERROR: file 'src/vendorcode/amd/agesa/f15tn/Proc/CPU/heapManager.c', line 332 ASSERTION ERROR: file 'src/vendorcode/amd/agesa/f15tn/Proc/Common/CreateStruct.c', line 205 ASSERTION ERROR: file 'src/vendorcode/amd/agesa/f15tn/Proc/Common/AmdInitEarly.c', line 169 ASSERTION ERROR: file 'src/drivers/amd/agesa/state_machine.c', line 256 ASSERTION ERROR: file 'src/vendorcode/amd/agesa/f15tn/Proc/CPU/heapManager.c', line 332 ASSERTION ERROR: file 'src/vendorcode/amd/agesa/f15tn/Proc/CPU/heapManager.c', line 332 ASSERTION ERROR: file 'src/vendorcode/amd/agesa/f15tn/Proc/CPU/heapManager.c', line 332 ASSERTION ERROR: file 'src/vendorcode/amd/agesa/f15tn/Proc/HT/htMain.c', line 562 ASSERTION ERROR: file 'src/vendorcode/amd/agesa/f15tn/Proc/CPU/heapManager.c', line 606 ASSERTION ERROR: file 'src/vendorcode/amd/agesa/f15tn/Proc/CPU/cpuGeneralServices.c', line 483 ASSERTION ERROR: file 'src/vendorcode/amd/agesa/f15tn/Proc/CPU/heapManager.c', line 606 ASSERTION ERROR: file 'src/vendorcode/amd/agesa/f15tn/Proc/CPU/cpuGeneralServices.c', line 872 ASSERTION ERROR: file 'src/vendorcode/amd/agesa/f15tn/Proc/CPU/heapManager.c', line 606 ASSERTION ERROR: file 'src/vendorcode/amd/agesa/f15tn/Proc/CPU/cpuGeneralServices.c', line 483 ASSERTION ERROR: file 'src/vendorcode/amd/agesa/f15tn/Proc/CPU/heapManager.c', line 606 ASSERTION ERROR: file 'src/vendorcode/amd/agesa/f15tn/Proc/CPU/cpuGeneralServices.c', line 872 ASSERTION ERROR: file 'src/vendorcode/amd/agesa/f15tn/Proc/CPU/heapManager.c', line 606 ASSERTION ERROR: file 'src/vendorcode/amd/agesa/f15tn/Proc/CPU/cpuGeneralServices.c', line 735 ASSERTION ERROR: file 'src/vendorcode/amd/agesa/f15tn/Proc/CPU/heapManager.c', line 606 ASSERTION ERROR: file 'src/vendorcode/amd/agesa/f15tn/Proc/CPU/cpuGeneralServices.c', line 483 ASSERTION ERROR: file 'src/vendorcode/amd/agesa/f15tn/Proc/CPU/cpuGeneralServices.c', line 261 ASSERTION ERROR: file 'src/vendorcode/amd/agesa/f15tn/Proc/CPU/heapManager.c', line 606 ASSERTION ERROR: file 'src/vendorcode/amd/agesa/f15tn/Proc/CPU/cpuGeneralServices.c', line 872 ASSERTION ERROR: file 'src/vendorcode/amd/agesa/f15tn/Proc/CPU/cpuGeneralServices.c', line 727 ASSERTION ERROR: file 'src/vendorcode/amd/agesa/f15tn/Proc/CPU/cpuGeneralServices.c', line 728 ASSERTION ERROR: file 'src/vendorcode/amd/agesa/f15tn/Proc/CPU/heapManager.c', line 606 ASSERTION ERROR: file 'src/vendorcode/amd/agesa/f15tn/Proc/CPU/cpuGeneralServices.c', line 735 ASSERTION ERROR: file 'src/vendorcode/amd/agesa/f15tn/Proc/CPU/heapManager.c', line 606 ASSERTION ERROR: file 'src/vendorcode/amd/agesa/f15tn/Proc/CPU/cpuGeneralServices.c', line 483 ASSERTION ERROR: file 'src/vendorcode/amd/agesa/f15tn/Proc/CPU/cpuGeneralServices.c', line 261 ASSERTION ERROR: file 'src/vendorcode/amd/agesa/f15tn/Proc/CPU/heapManager.c', line 606 ASSERTION ERROR: file 'src/vendorcode/amd/agesa/f15tn/Proc/CPU/cpuGeneralServices.c', line 872 ASSERTION ERROR: file 'src/vendorcode/amd/agesa/f15tn/Proc/CPU/cpuGeneralServices.c', line 727 ASSERTION ERROR: file 'src/vendorcode/amd/agesa/f15tn/Proc/CPU/cpuGeneralServices.c', line 728 ASSERTION ERROR: file 'src/vendorcode/amd/agesa/f15tn/Proc/CPU/heapManager.c', line 606 ASSERTION ERROR: file 'src/vendorcode/amd/agesa/f15tn/Proc/CPU/cpuGeneralServices.c', line 735 ASSERTION ERROR: file 'src/vendorcode/amd/agesa/f15tn/Proc/CPU/heapManager.c', line 606 ASSERTION ERROR: file 'src/vendorcode/amd/agesa/f15tn/Proc/CPU/cpuGeneralServices.c', line 483 ASSERTION ERROR: file 'src/vendorcode/amd/agesa/f15tn/Proc/CPU/cpuGeneralServices.c', line 261 ASSERTION ERROR: file 'src/vendorcode/amd/agesa/f15tn/Proc/CPU/heapManager.c', line 606 ASSERTION ERROR: file 'src/vendorcode/amd/agesa/f15tn/Proc/CPU/cpuGeneralServices.c', line 872 ASSERTION ERROR: file 'src/vendorcode/amd/agesa/f15tn/Proc/CPU/cpuGeneralServices.c', line 727 ASSERTION ERROR: file 'src/vendorcode/amd/agesa/f15tn/Proc/CPU/cpuGeneralServices.c', line 728 ASSERTION ERROR: file 'src/vendorcode/amd/agesa/f15tn/Proc/CPU/heapManager.c', line 606 ASSERTION ERROR: file 'src/vendorcode/amd/agesa/f15tn/Proc/CPU/cpuGeneralServices.c', line 735

2 1

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

2003

2002

coreboot August 2021