February 2019 - coreboot - mail.coreboot.org

Optiplex 790 now has preliminary support by coreboot

by Taiidan＠gmx.com

https://review.coreboot.org/21774 In case anyone else didn't notice - It is a sandy/ivy system with IOMMU. This is great and should help get coreboot in to the corporate user world.

1 week, 5 days

2
1
0 0

Coreboot doesn't POST on ASUS KCMA-D8

by espionage724＠posteo.net

I have a KCMA-D8 motherboard with two Opteron 4226s, and 6x4GB (24GB) Hynix HMT151R7BFR4C-H9 RAM sticks. All my attempts of getting Coreboot to POST with this board so far haven't worked. I'm compiling Coreboot from Git (master branch), and can build it without issue. A pre-built Libreboot ROM (20160907) POSTs and boots fine. For Coreboot's config, I've tried including/excluding CPU microcode updates, along with some less important-sounding options. For hardware, I've tried unplugging everything external (KB/mouse), my GPU (RX 580), and only had a single RAM stick in (slot A1). I've also tried a single CPU being powered (kept the 2nd CPU in but only had a single 4-pin CPU going to the 1st CPU). Can anyone else confirm Git builds of Coreboot booting on this board, or provide any tips as to anything I could be missing? I see this issue https://ticket.coreboot.org/issues/151 but there's a board status months after that that looks like it boots: https://review.coreboot.org/cgit/board-status.git/tree/asus/kcma-d8/4.7-7...

10 months

8
8
0 0

Intel sVID controller and SVID bus.

by dponamorev＠gmail.com

On the motherboard developed by our company (intel atom denverton 3538), there is a low performance of the processor and memory. When trying to monitor the exchange of the SVID bus lines with the oscilloscope (SVID_CLK, SVID_DATA and SVID_ALERT), no activity was noticed. Circuit design is correct (passed Intel review). Could this be the reason for the slow speed of the processor and memory? Do I need to activate this technology in coreboot or FSP? Is there any way to check the operation of the sVID controller from Linux?

10 months, 1 week

3
3
0 0

Atom Denverton processor and memory are very slow.

by Дмитрий Понаморев

The processor and memory are very slow. Compiling the ixgbe network card driver takes 10 minutes. The maximum read speed of DDR4 2133 SODIMM is 742 MB / sec. Custom motherboard with Atom Denverton C3538 processor, quad cores 2.1 GHz. SODIMM module: Crucial DDR4 8Gb 2400MHz CT8G4SFS824A. BIOS: coreboot 4.9 + intel FSP + seabios. WD Blue WDS250G2B0B 250GB, M.2 2280, SATA III Hard Drive. Debian 7 (Linux version 3.2.0-4-amd64 ( debian-kernel(a)lists.debian.org) (gcc version 4.6.3 (Debian 4.6.3-14) ) #1 SMP Debian 3.2.96-2). Why the slow operation of the processor and memory is possible? What settings can be changed in Intel FSP and coreboot to speed up the processor and memory? Full boot log in attached file: putty_com5_coreboot_seabios_debian.zip Bandwidth64 memory test: This is bandwidth version 1.5.1. Copyright (C) 2005-2017 by Zack T Smith. This software is covered by the GNU Public License. It is provided AS-IS, use at your own risk. See the file COPYING for more information. CPU family: GenuineIntel CPU features: MMX SSE SSE2 SSE3 SSSE3 SSE4.1 SSE4.2 AES XD Intel64 Cache 0: L1 data cache, line size 64, 6-ways, 64 sets, size 24k Cache 1: L1 instruction cache, line size 64, 8-ways, 64 sets, size 32k Cache 2: L2 unified cache, line size 64, 16-ways, 2048 sets, size 2048k Notation: B = byte, kB = 1024 B, MB = 1048576 B. CPU speed is 2099.99 MHz. Sequential read (64-bit), size = 128 B, loops = 30408704, 741.4 MB/s Sequential read (64-bit), size = 256 B, loops = 15204352, 741.2 MB/s Sequential read (64-bit), size = 384 B, loops = 10136196, 741.4 MB/s Sequential read (64-bit), size = 512 B, loops = 7602176, 740.9 MB/s Sequential read (64-bit), size = 640 B, loops = 6186563, 742.6 MB/s Sequential read (64-bit), size = 768 B, loops = 5155479, 742.7 MB/s Sequential read (64-bit), size = 896 B, loops = 4418982, 742.7 MB/s Sequential read (64-bit), size = 1024 B, loops = 3866624, 742.7 MB/s Sequential read (64-bit), size = 1280 B, loops = 3040824, 742.3 MB/s Sequential read (64-bit), size = 2 kB, loops = 1933312, 742.7 MB/s Sequential read (64-bit), size = 3 kB, loops = 1288855, 742.5 MB/s Sequential read (64-bit), size = 4 kB, loops = 966656, 742.6 MB/s Sequential read (64-bit), size = 6 kB, loops = 644398, 742.6 MB/s Sequential read (64-bit), size = 8 kB, loops = 475136, 742.4 MB/s Sequential read (64-bit), size = 12 kB, loops = 316738, 735.7 MB/s Sequential read (64-bit), size = 16 kB, loops = 237568, 736.2 MB/s Sequential read (64-bit), size = 20 kB, loops = 190008, 734.7 MB/s Sequential read (64-bit), size = 24 kB, loops = 152880, 708.7 MB/s Sequential read (64-bit), size = 28 kB, loops = 70200, 374.0 MB/s Sequential read (64-bit), size = 32 kB, loops = 61440, 371.4 MB/s Sequential read (64-bit), size = 34 kB, loops = 57810, 371.2 MB/s Sequential read (64-bit), size = 36 kB, loops = 52780, 371.1 MB/s Sequential read (64-bit), size = 40 kB, loops = 49140, 371.2 MB/s Sequential read (64-bit), size = 48 kB, loops = 40950, 371.3 MB/s Sequential read (64-bit), size = 64 kB, loops = 30720, 371.3 MB/s Sequential read (64-bit), size = 128 kB, loops = 14848, 368.6 MB/s Sequential read (64-bit), size = 192 kB, loops = 9889, 368.9 MB/s Sequential read (64-bit), size = 256 kB, loops = 7424, 368.9 MB/s Sequential read (64-bit), size = 320 kB, loops = 5916, 369.6 MB/s Sequential read (64-bit), size = 384 kB, loops = 4930, 369.6 MB/s Sequential read (64-bit), size = 512 kB, loops = 3712, 369.6 MB/s Sequential read (64-bit), size = 768 kB, loops = 2465, 369.6 MB/s Sequential read (64-bit), size = 1 MB, loops = 1856, 369.6 MB/s Sequential read (64-bit), size = 1.25 MB, loops = 1479, 369.5 MB/s Sequential read (64-bit), size = 1.5 MB, loops = 1260, 369.4 MB/s Sequential read (64-bit), size = 1.75 MB, loops = 1080, 366.9 MB/s Sequential read (64-bit), size = 2 MB, loops = 896, 356.9 MB/s Sequential read (64-bit), size = 2.25 MB, loops = 784, 350.9 MB/s Sequential read (64-bit), size = 2.5 MB, loops = 725, 351.2 MB/s Sequential read (64-bit), size = 2.75 MB, loops = 644, 351.0 MB/s Sequential read (64-bit), size = 3 MB, loops = 588, 351.3 MB/s Sequential read (64-bit), size = 3.25 MB, loops = 551, 351.1 MB/s Sequential read (64-bit), size = 3.5 MB, loops = 504, 351.2 MB/s Sequential read (64-bit), size = 4 MB, loops = 448, 351.3 MB/s Sequential read (64-bit), size = 5 MB, loops = 360, 351.4 MB/s Sequential read (64-bit), size = 6 MB, loops = 300, 351.4 MB/s Sequential read (64-bit), size = 7 MB, loops = 252, 351.5 MB/s Sequential read (64-bit), size = 8 MB, loops = 224, 351.4 MB/s Random read (64-bit), size = 256 B, loops = 13893632, 678.4 MB/s Random read (64-bit), size = 512 B, loops = 6946816, 677.2 MB/s Random read (64-bit), size = 768 B, loops = 4631193, 677.1 MB/s Random read (64-bit), size = 1024 B, loops = 3473408, 677.2 MB/s Random read (64-bit), size = 1280 B, loops = 2778684, 677.7 MB/s Random read (64-bit), size = 2 kB, loops = 1769472, 678.6 MB/s Random read (64-bit), size = 3 kB, loops = 1179630, 678.6 MB/s Random read (64-bit), size = 4 kB, loops = 868352, 677.1 MB/s Random read (64-bit), size = 6 kB, loops = 578866, 677.5 MB/s Random read (64-bit), size = 8 kB, loops = 442368, 679.0 MB/s Random read (64-bit), size = 12 kB, loops = 289433, 672.9 MB/s Random read (64-bit), size = 16 kB, loops = 217088, 673.4 MB/s Random read (64-bit), size = 20 kB, loops = 173628, 673.1 MB/s Random read (64-bit), size = 24 kB, loops = 128310, 596.1 MB/s Random read (64-bit), size = 28 kB, loops = 79560, 434.8 MB/s Random read (64-bit), size = 32 kB, loops = 69632, 430.8 MB/s Random read (64-bit), size = 34 kB, loops = 65518, 431.5 MB/s Random read (64-bit), size = 36 kB, loops = 61880, 432.0 MB/s Random read (64-bit), size = 40 kB, loops = 55692, 431.7 MB/s Random read (64-bit), size = 48 kB, loops = 46410, 430.6 MB/s Random read (64-bit), size = 64 kB, loops = 34816, 430.5 MB/s Random read (64-bit), size = 128 kB, loops = 16896, 420.3 MB/s Random read (64-bit), size = 192 kB, loops = 11253, 412.6 MB/s Random read (64-bit), size = 256 kB, loops = 8192, 405.5 MB/s Random read (64-bit), size = 320 kB, loops = 6528, 402.1 MB/s Random read (64-bit), size = 384 kB, loops = 5440, 398.5 MB/s Random read (64-bit), size = 512 kB, loops = 3968, 395.5 MB/s Random read (64-bit), size = 768 kB, loops = 2635, 392.6 MB/s Random read (64-bit), size = 1 MB, loops = 1984, 390.9 MB/s Random read (64-bit), size = 1.25 MB, loops = 1581, 389.6 MB/s Random read (64-bit), size = 1.5 MB, loops = 1302, 388.2 MB/s Random read (64-bit), size = 1.75 MB, loops = 1008, 347.2 MB/s Random read (64-bit), size = 2 MB, loops = 768, 297.0 MB/s Random read (64-bit), size = 2.25 MB, loops = 560, 248.7 MB/s Random read (64-bit), size = 2.5 MB, loops = 450, 221.8 MB/s Random read (64-bit), size = 2.75 MB, loops = 391, 207.7 MB/s Random read (64-bit), size = 3 MB, loops = 336, 198.0 MB/s Random read (64-bit), size = 3.25 MB, loops = 304, 192.9 MB/s Random read (64-bit), size = 3.5 MB, loops = 270, 188.8 MB/s Random read (64-bit), size = 4 MB, loops = 240, 183.5 MB/s Random read (64-bit), size = 5 MB, loops = 180, 176.1 MB/s Random read (64-bit), size = 6 MB, loops = 150, 171.7 MB/s Random read (64-bit), size = 7 MB, loops = 126, 168.5 MB/s Random read (64-bit), size = 8 MB, loops = 104, 166.1 MB/s

10 months, 1 week

3
2
0 0

G505S - slightly different Voltages at integrated HD 8650G iGPU AtomBIOS ?

by Ivan Ivanov

Interesting discovery about the AtomBIOS files at " g505s-atombios " repository - https://github.com/g505s-opensource-researcher/g505s-atombios : While there was the same "clean" proprietary UEFI image flashed both to "G505S with HD 8570M" and to "G505S with R5 M230" before the AtomBIOS extraction, their AtomBIOSes for _ integrated HD 8650G _ turned out as slightly different! (see sha256) So I made their full disassembly with this AtomDis tool - https://cgit.freedesktop.org/~mhopf/AtomDis/ , and compared, diff results here - https://pastebin.com/eewzswnD . As you could see from these diff results, for some reason "G505S R5 version" sets a slightly higher voltages for its' integrated GPU : compared to "G505S HD version" it is 1.8% - 3.2% higher if these 0x3e / 0x40 / 0x6e / 0x70 values are linear and 0x0 = 0 volts. (usNBP0Voltage / usNBP1Voltage / usVoltageID ) What do you think: would it be okay to use the integrated VGA BIOS obtained from "G505S R5 version" for "G505S HD version" ? This voltage difference seems small enough and the integrated GPU is the same part after all ---> I think that it should be fine.

10 months, 2 weeks

2
1
0 0

Microcode in ROM is not loaded with X60s

by Masanori Ogino

Dear Coreboot developers, I installed Coreboot with ThinkPad X60s and Debian 9 and they run successfully, but I observe a weird behavior. Even though I had enabled blob for microcode update, the system seems to run without it. I saw the following message in dmesg: (I think this is not fatal since this is related to temperature monitoring, though.) > coretemp: Errata AE18 not fixed, update BIOS or microcode of the CPU! For comparison, I had installed `intel-microcode` package to the system and then the message disappeared. Is this intended behavior, misconfiguration, or a real bug? For reference, I uploaded the content of /proc/cpuinfo before and after the installation of `intel-microcode` package: https://gist.github.com/omasanori/4a1316bd78d95069f287431f5bd3a176 Also, I uploaded a report to board-status: https://review.coreboot.org/cgit/board-status.git/commit/?id=af91ae4946fe... (I had also tried to install FreeBSD 12.0 and OpenBSD 6.4 but both of their installers failed to boot just after the kernel is loaded and located. I am not sure if this is related to this or not.) Best regards, Masanori -- Masanori Ogino

10 months, 4 weeks

2
3
0 0

Intel Braswell uploads

by Frans Hendriks

Hi, I'm working on Intel Braswell implementation and uploaded several patches. It seems that the maintainer of the Intel Braswell is not active for review/merge/reply of the uploads. Is the maintainer in MAINTAINERS document correct and still active? Met vriendelijke groet / Best regards, Frans Hendriks Eltan B.V.

11 months

7
13
0 0

Intel Xeon D-1577 (16-core)

by aurelio＠platinasystems.com

Hello, I got a daughter-card (DC) based on the Intel's Camelback Mountain CRB. Coreboot won't boot when a DC is populated with a 16-core Xeon D-1577 processor. Nothing is printed in the boot process, so it doesn't seem to be getting very far. However, if i load/program the boot SPI with AMI BIOS instead of coreboot, then everything is hunky-dory. It boots up all the way into linux (see below for the platform information when AMI is loaded). In addition, if DC is populated with a 4-core D-1527 or 2-core D-1508 then coreboot has no issues (see below for info). Is there any configuration that i need to change in coreboot to support the D-1577? thanks! ## AMI BIOS ## @unassigned:~$ inxi -F System: Host: unassigned Kernel: 4.13-platina-mk1 x86_64 (64 bit) Console: tty 0 Distro: Debian GNU/Linux 8 Machine: Mobo: Default string model: Default string v: Default string Bios: American Megatrends v: 5.11 date: 05/31/2017 CPU: Octa core Intel Xeon D-1577 (-HT-MCP-) cache: 24576 KB Clock Speeds: 1: 1300 MHz 2: 1300 MHz 3: 1300 MHz 4: 1300 MHz 5: 1300 MHz 6: 1300 MHz 7: 1300 MHz 8: 1300 MHz Graphics: Card: Failed to Detect Video Card! Display Server: N/A driver: N/A tty size: 80x24 Advanced Data: N/A out of X Network: Card-1: Broadcom Device b960 IF: N/A state: N/A speed: N/A duplex: N/A mac: N/A Card-2: Broadcom Device b960 IF: N/A state: N/A speed: N/A duplex: N/A mac: N/A Card-3: Intel Device 15ab driver: ixgbe IF: eth1 state: down mac: 00:a0:c9:00:00:00 Card-4: Intel Device 15ab driver: ixgbe IF: eth2 state: down mac: 34:12:78:56:01:00 Card-5: Intel I210 Gigabit Network Connection driver: igb IF: eth0 state: up speed: 1000 Mbps duplex: full mac: 50:18:4c:00:16:a1 Drives: HDD Total Size: 520.1GB (4.0% used) ID-1: /dev/sda model: TS512ZBTDM1500T size: 512.1GB ID-2: USB /dev/sdb model: Echo size: 8.0GB Partition: ID-1: / size: 451G used: 942M (1%) fs: ext4 dev: /dev/sda1 ID-2: swap-1 size: 20.75GB used: 0.00GB (0%) fs: swap dev: /dev/sda5 RAID: No RAID devices: /proc/mdstat, md_mod kernel module present Sensors: System Temperatures: cpu: 56.0C mobo: N/A Fan Speeds (in rpm): cpu: N/A Info: Processes: 118 Uptime: 17:49 Memory: 110.9/32087.7MB Init: systemd runlevel: 5 Client: Shell (bash) inxi: 2.1.28 ## Coreboot on 4-core D-1527: ## root@invader0:~# POST: 0x4a romstage_main_continue status: 0 hob_list_ptr: 7f100000 FSP Status: 0x0 POST: 0x4b POST: 0x4c POST: 0x4d CBMEM: IMD: root @ 7efff000 254 entries. IMD: root @ 7effec00 62 entries. POST: 0x4e CBFS: 'Master Header Locator' located CBFS at [800100:ffffc0) CBFS: Locating 'fallback/ramstage' CBFS: Found @ offset 33b80 size d857 coreboot-v0.4-5-g0e4829a5b5 Wed Jun 20 18:38:46 UTC 2018 ramstage starting... POST: 0x39 Moving GDT to 7effe9e0...ok POST: 0x80 ## root@invader0:~# inxi -F System: Host: invader0 Kernel: 4.13-platina-mk1 x86_64 (64 bit) Console: tty 0 Distro: Debian GNU/Linux 8 Machine: Mobo: Intel model: Camelback Mountain Platina DC v: 1.0 serial: 123456789 Bios: coreboot v: v0.4-5-g0e4829a5b5 date: 06/20/2018 CPU: Quad core Intel Xeon D-1527 (-HT-MCP-) cache: 6144 KB Clock Speeds: 1: 2194 MHz 2: 2194 MHz 3: 2194 MHz 4: 2194 MHz 5: 2194 MHz 6: 2194 MHz 7: 2194 MHz 8: 2194 MHz Graphics: Card: Failed to Detect Video Card! Display Server: N/A driver: N/A tty size: 80x24 Advanced Data: N/A for root out of X Network: Card-1: Broadcom Device b960 driver: vfio-pci IF: N/A state: N/A speed: N/A duplex: N/A mac: N/A Card-2: Broadcom Device b960 driver: vfio-pci IF: N/A state: N/A speed: N/A duplex: N/A mac: N/A Card-3: Intel Device 15ab driver: ixgbe IF: eth1 state: down mac: 50:18:4c:00:16:a2 Card-4: Intel Device 15ab driver: ixgbe IF: eth2 state: down mac: 50:18:4c:00:16:a3 Card-5: Intel I210 Gigabit Network Connection driver: igb IF: eth0 state: up speed: 1000 Mbps duplex: full mac: 50:18:4c:00:16:a1 Drives: HDD Total Size: 136.1GB (5.0% used) ID-1: /dev/sda model: SanDisk_SD8SMAT1 size: 128.0GB ID-2: USB /dev/sdb model: Echo size: 8.0GB Partition: ID-1: / size: 98G used: 1.4G (2%) fs: ext4 dev: /dev/sda6 ID-2: swap-1 size: 5.70GB used: 0.00GB (0%) fs: swap dev: /dev/sda5 RAID: No RAID devices: /proc/mdstat, md_mod kernel module present Sensors: System Temperatures: cpu: 56.0C mobo: N/A Fan Speeds (in rpm): cpu: N/A Info: Processes: 133 Uptime: 1 min Memory: 149.1/16078.1MB Init: systemd runlevel: 5 Client: Shell (bash) inxi: 2.1.28 root@invader0:~#

11 months

3
3
0 0

New API to clear DRAM at boot

by Patrick Rudolph

Hi coreboot folks, in order to support TEE like Intel TXT it is necessary to be able to clear all DRAM at boot on request. As all of the x86 coreboot code is x86_32, it is necessary to make use of PAE to clear memory. Please find the attached patch series which proposes an architecure independed API, PAE enabled memset on x86, and helper functions to clear all DRAM on Broadwell DE: https://review.coreboot.org/#/q/project:coreboot+branch:master+topic:secu... The code can be easily extended to other platforms. Please comment, test and improve the patchset. Regards, -- Patrick Rudolph 9elements Agency GmbH, Kortumstraße 19-21, 44787 Bochum, Germany Email: patrick.rudolph(a)9elements.com Phone: +49 234 68 94 188 Sitz der Gesellschaft: Bochum Handelsregister: Amtsgericht Bochum, HRB 17519 Geschäftsführung: Sebastian Deutsch, Daniel Hoelzgen

11 months

5
8
0 0

Re: Microcode in ROM is not loaded with X60s

by Masanori Ogino

Dear Lance, Thank you for your reply. On Mon, Feb 25, 2019 at 4:27 AM Lance Zhao <lance.zhao(a)gmail.com> wrote: > Current coreboot should have same level of microcode compare to intel-microcode for Linux. Indeed. I saw a commit updating Intel microcode in last December, so I am sure the microcode is not so ancient that it does not contain the fix for a known errata. Best regards, Masanori

11 months

3
4
0 0

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

2003

2002

coreboot February 2019