coreboot

coreboot@coreboot.org

6 participants
39686 discussions

Working X11SSH-F config
by Martin Kjær Jørgensen 20 Apr '23

20 Apr '23

Hello, I have recently started experimenting with coreboot so please forgive my ignorance :-) I can make it boot using edk2 payload and only flashing "bios" region and I am able to make an ordinary linux distro boot. Using OEM BIOS from supermicro everything seems to work as expected, but using my coreboot image I run into the following issues: 1. I also get PCI related errors and warnings during coreboot boot. 2. Microcode update errors during coreboot boot, although it claims microcode to be updated afterwards. 3. My mainboard have 2 Intel NICs but Linux kernel claims only 1 exists, and lspci only shows 1. The "first" one :-) . 4. Coreboot does not show up, or work, if BMC is not enabled using the jumper. 5. When Linux issues system reset, machine freeze and needs to be manually powered off. If issuing "power off" the machine powers off as normal. Have anyone got a fully "working"/"stable" config for their X11SSH-* board I can use as reference? I got the feeling I'm missing something obvious or needed tweaks ... /Martin

1 0

Is my PC compatible with the Coreboot bios?
by Cédric LACHAUD 18 Apr '23

18 Apr '23

Hello, I am contacting you because a year and a few months ago, I bought a PC assembled by the company NovaCustom (model NH77) and I would like to know if I can install Coreboot as a BIOS without risk for my PC. I specify that I did not find the "official" name of my motherboard (which is, according to my current BIOS - InsydeH20 - NH5x_7xDPx). When I go to my Windows 11 (in the msinfo32 tool), the manufacturer of my motherboard would be "Notebook". Here is the result of the commands you wanted to be addressed for any such questions: * lspci -tvnn -[0000:00]-+-00.0 Intel Corporation 10th Gen Core Processor Host Bridge/DRAM Registers [8086:9b54] +-01.0-[01-05]--+-00.0 NVIDIA Corporation GA106M [GeForce RTX 3060 Mobile / Max-Q] [10de:2520] | \-00.1 NVIDIA Corporation Device [10de:228e] +-02.0 Intel Corporation CometLake-H GT2 [UHD Graphics] [8086:9bc4] +-12.0 Intel Corporation Comet Lake PCH Thermal Controller [8086:06f9] +-14.0 Intel Corporation Comet Lake USB 3.1 xHCI Host Controller [8086:06ed] +-14.2 Intel Corporation Comet Lake PCH Shared SRAM [8086:06ef] +-15.0 Intel Corporation Comet Lake PCH Serial IO I2C Controller #0 [8086:06e8] +-15.1 Intel Corporation Comet Lake PCH Serial IO I2C Controller #1 [8086:06e9] +-16.0 Intel Corporation Comet Lake HECI Controller [8086:06e0] +-17.0 Intel Corporation Device [8086:06d3] +-1b.0-[06]----00.0 Samsung Electronics Co Ltd NVMe SSD Controller SM981/PM981/PM983 [144d:a808] +-1d.0-[07]----00.0 Samsung Electronics Co Ltd NVMe SSD Controller SM981/PM981/PM983 [144d:a808] +-1d.5-[08]----00.0 Intel Corporation Wi-Fi 6 AX200 [8086:2723] +-1d.6-[09]--+-00.0 Realtek Semiconductor Co., Ltd. RTL8411B PCI Express Card Reader [10ec:5287] | \-00.1 Realtek Semiconductor Co., Ltd. RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller [10ec:8168] +-1f.0 Intel Corporation Comet Lake LPC Controller [8086:068d] +-1f.3 Intel Corporation Comet Lake PCH cAVS [8086:06c8] +-1f.4 Intel Corporation Comet Lake PCH SMBus Controller [8086:06a3] \-1f.5 Intel Corporation Comet Lake PCH SPI Controller [8086:06a4] * superiotool -dV superiotool r4.19-1262-g03232e93d3 Probing for ALi Super I/O at 0x3f0... Failed. Returned data: id=0xffff, rev=0xff Probing for ALi Super I/O at 0x370... Failed. Returned data: id=0xffff, rev=0xff Probing for Aspeed Super I/O at 0x2e... Found Aspeed AST2400 (id=0x00) at 0x2e Register dump: idx 20 21 22 23 24 25 26 27 28 29 2a 2b 2c 2d 2e 2f val 55 70 02 01 00 00 00 00 00 00 00 00 01 00 12 03 def 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 LDN 0x02 (SUART1) idx 30 60 61 70 71 f0 val 00 02 f8 03 02 00 def 00 03 f8 04 02 RR LDN 0x03 (SUART2) idx 30 60 61 70 71 f0 val 00 00 00 00 00 00 def 00 02 f8 03 02 00 LDN 0x04 (SWC) idx 30 60 61 62 63 64 65 66 67 70 71 val 00 00 00 00 00 00 00 00 00 00 01 def 00 08 e6 08 e0 08 e4 08 e8 09 01 LDN 0x05 (Keyboard config (KBC)) idx 30 60 61 62 63 70 71 72 73 f0 val 01 00 00 00 00 0c 01 00 00 00 def 00 00 60 00 64 01 02 0c 02 83 LDN 0x07 (GPIO) idx 30 38 70 71 val 00 00 00 00 def 00 00 0b 01 LDN 0x0b (SUART3) idx 30 60 61 70 71 f0 val 00 00 00 00 00 00 def 00 03 e8 06 02 00 LDN 0x0c (SUART4) idx 30 60 61 70 71 f0 val 00 00 00 00 00 00 def 00 02 e8 05 02 00 LDN 0x0d (iLPC2AHB) idx 30 70 71 f0 f1 f2 f3 f4 f5 f6 f7 f8 fe val 00 00 00 00 00 00 00 00 00 00 00 00 00 def 00 09 01 NA NA NA NA NA NA NA NA 00 00 LDN 0x0e (Mailbox) idx 30 60 61 70 71 val 00 00 00 00 00 def 00 08 c0 09 01 Probing for Aspeed Super I/O at 0x4e... Failed. Returned data: scratch registers all read as 0xff Probing for Exar Super I/O at 0x2e... Failed. Returned data: vid=0x0001, id=0x7055 Probing for Exar Super I/O at 0x4e... Failed. Returned data: vid=0xffff, id=0xffff Probing for Fintek Super I/O at 0x2e... Failed. Returned data: vid=0x0001, id=0x7055 Probing for Fintek Super I/O at 0x4e... Failed. Returned data: vid=0xffff, id=0xffff Probing for Fintek Super I/O at 0x2e... Failed. Returned data: vid=0x0001, id=0x7055 Probing for Fintek Super I/O at 0x4e... Failed. Returned data: vid=0xffff, id=0xffff Probing for ITE Super I/O (init=standard) at 0x20e... Failed. Returned data: id=0xffff, rev=0xf Probing for ITE Super I/O (init=it8502e) at 0x20e... Failed. Returned data: id=0xffff, rev=0xf Probing for ITE Super I/O (init=it8761e) at 0x20e... Failed. Returned data: id=0xffff, rev=0xf Probing for ITE Super I/O (init=it8228e) at 0x20e... Failed. Returned data: id=0xffff, rev=0xf Probing for ITE Super I/O (init=it8987e) at 0x20e... Failed. Returned data: id=0xffff, rev=0xf Probing for ITE Super I/O (init=0x87,0x87) at 0x20e... Failed. Returned data: id=0xffff, rev=0xf Probing for ITE Super I/O (init=standard) at 0x25e... Failed. Returned data: id=0xffff, rev=0xf Probing for ITE Super I/O (init=it8502e) at 0x25e... Failed. Returned data: id=0xffff, rev=0xf Probing for ITE Super I/O (init=it8761e) at 0x25e... Failed. Returned data: id=0xffff, rev=0xf Probing for ITE Super I/O (init=it8228e) at 0x25e... Failed. Returned data: id=0xffff, rev=0xf Probing for ITE Super I/O (init=it8987e) at 0x25e... Failed. Returned data: id=0xffff, rev=0xf Probing for ITE Super I/O (init=0x87,0x87) at 0x25e... Failed. Returned data: id=0xffff, rev=0xf Probing for ITE Super I/O (init=standard) at 0x2e... Found ITE IT5570E (id=0x5570, rev=0x2) at 0x2e Register dump: idx 20 21 22 23 24 25 26 27 28 29 2a 2b 2d val 55 70 02 01 00 00 00 00 00 00 00 00 00 def 55 70 NA 01 RR 00 00 RR RR RR RR RR 00 LDN 0x01 (Serial Port 1 (UART1)) idx 30 60 61 62 63 70 71 f0 val 00 03 f8 00 00 04 02 00 def 00 02 f8 00 00 03 02 00 LDN 0x02 (Serial Port 2 (UART2)) idx 30 60 61 62 63 70 71 f0 val 00 02 f8 00 00 03 02 00 def 00 02 f8 00 00 03 02 00 LDN 0x04 (System Wake-Up Control (SWUC)) idx 30 60 61 70 71 val 00 00 00 00 01 def 00 00 00 00 01 LDN 0x05 (KBC Mouse) idx 30 70 71 val 01 0c 01 def 00 0c 01 LDN 0x06 (KBC Keyboard) idx 30 60 61 62 63 70 71 val 01 00 60 00 64 01 01 def 00 00 60 00 64 01 01 LDN 0x0a (Consumer IR) idx 30 60 61 70 71 val 00 03 10 00 02 def 00 03 10 00 02 LDN 0x0f (Shared Memory/Flash Interface (SMFI)) idx 30 60 61 70 71 f0 f1 f2 f3 f4 f5 f6 f9 fa fb fc val 01 00 00 00 02 fe 70 00 00 09 00 70 00 00 00 00 def 00 00 00 00 02 00 00 00 00 00 00 00 00 00 00 01 LDN 0x10 (RTC-like Timer (RTC)) idx 30 60 61 62 63 64 65 66 67 68 69 70 71 f0 f1 f2 f3 f4 f5 val 01 00 94 05 00 00 00 00 00 00 00 00 01 00 49 4a 00 3f 3f def 00 00 70 02 72 00 00 00 00 00 00 08 01 00 49 4a 00 00 00 LDN 0x11 (Power Management Interface Channel 1 (PMC1)) idx 30 60 61 62 63 70 71 val 01 00 62 00 66 00 01 def 00 00 62 00 66 01 01 LDN 0x12 (Power Management Interface Channel 2 (PMC2)) idx 30 60 61 62 63 64 65 70 71 f0 val 00 00 68 00 6c 00 00 00 01 00 def 00 00 68 00 6c 00 00 01 01 NA LDN 0x13 (Serial Peripheral Interface (SSPI)) idx 30 60 61 70 71 val 00 03 00 00 02 def 00 03 00 00 02 LDN 0x14 (Platform Environment Control Interface (PECI)) idx 30 60 61 val 00 00 00 def 00 00 00 LDN 0x17 (Power Management Interface Channel 3 (PMC3)) idx 30 60 61 62 63 70 71 val 00 00 6a 00 6e 01 01 def 00 00 6a 00 6e 01 01 LDN 0x18 (Power Management Interface Channel 4 (PMC4)) idx 30 60 61 62 63 70 71 val 00 00 74 00 78 01 01 def 00 00 74 00 78 01 01 LDN 0x19 (Power Management Interface Channel 5 (PMC5)) idx 30 60 61 62 63 70 71 val 00 00 7a 00 7c 01 01 def 00 00 7a 00 7c 01 01 Probing for ITE Super I/O (init=standard) at 0x4e... Failed. Returned data: id=0xffff, rev=0xf Probing for ITE Super I/O (init=it8502e) at 0x4e... Failed. Returned data: id=0xffff, rev=0xf Probing for ITE Super I/O (init=it8761e) at 0x4e... Failed. Returned data: id=0xffff, rev=0xf Probing for ITE Super I/O (init=it8228e) at 0x4e... Failed. Returned data: id=0xffff, rev=0xf Probing for ITE Super I/O (init=it8987e) at 0x4e... Failed. Returned data: id=0xffff, rev=0xf Probing for ITE Super I/O (init=0x87,0x87) at 0x4e... Failed. Returned data: id=0xffff, rev=0xf Probing for ITE Super I/O (init=legacy/it8661f) at 0x370... Failed. Returned data: id=0xffff, rev=0xf Probing for ITE Super I/O (init=legacy/it8671f) at 0x370... Failed. Returned data: id=0xffff, rev=0xf Probing for ITE Super I/O (init=standard) at 0x6e... Failed. Returned data: id=0xffff, rev=0xf Probing for ITE Super I/O (init=it8502e) at 0x6e... Failed. Returned data: id=0xffff, rev=0xf Probing for ITE Super I/O (init=it8761e) at 0x6e... Failed. Returned data: id=0xffff, rev=0xf Probing for ITE Super I/O (init=it8228e) at 0x6e... Failed. Returned data: id=0xffff, rev=0xf Probing for ITE Super I/O (init=it8987e) at 0x6e... Failed. Returned data: id=0xffff, rev=0xf Probing for ITE Super I/O (init=0x87,0x87) at 0x6e... Failed. Returned data: id=0xffff, rev=0xf Probing for NSC Super I/O at 0x2e... Failed. Returned data: sid=0x55, srid=0x00 Probing for NSC Super I/O at 0x4e... Failed. Returned data: port=0xff, port+1=0xff Probing for NSC Super I/O at 0x15c... Failed. Returned data: port=0xff, port+1=0xff Probing for NSC Super I/O at 0x164e... Failed. Returned data: port=0xff, port+1=0xff Probing for Nuvoton Super I/O at 0x164e... Failed. Returned data: chip_id=0xffff Probing for Nuvoton Super I/O (sid=0xfc) at 0x164e... Failed. Returned data: sid=0xff, id=0xffff, rev=0x00 Probing for Nuvoton Super I/O at 0x2e... Failed. Returned data: chip_id=0x5570 Probing for Nuvoton Super I/O (sid=0xfc) at 0x2e... Failed. Returned data: sid=0x55, id=0x5570, rev=0x00 Probing for Nuvoton Super I/O at 0x4e... Failed. Returned data: chip_id=0xffff Probing for Nuvoton Super I/O (sid=0xfc) at 0x4e... Failed. Returned data: sid=0xff, id=0xffff, rev=0x00 Probing for SMSC Super I/O (idregs=0x20/0x21) at 0x2e... Failed. Returned data: id=0x55, rev=0x70 Probing for SMSC Super I/O (idregs=0x0d/0x0e) at 0x2e... Failed. Returned data: id=0x00, rev=0x00 Probing for SMSC Super I/O (idregs=0x20/0x21) at 0x4e... Failed. Returned data: id=0xff, rev=0xff Probing for SMSC Super I/O (idregs=0x0d/0x0e) at 0x4e... Failed. Returned data: id=0xff, rev=0xff Probing for SMSC Super I/O (idregs=0x20/0x21) at 0x162e... Failed. Returned data: id=0xff, rev=0xff Probing for SMSC Super I/O (idregs=0x0d/0x0e) at 0x162e... Failed. Returned data: id=0xff, rev=0xff Probing for SMSC Super I/O (idregs=0x20/0x21) at 0x164e... Failed. Returned data: id=0xff, rev=0xff Probing for SMSC Super I/O (idregs=0x0d/0x0e) at 0x164e... Failed. Returned data: id=0xff, rev=0xff Probing for SMSC Super I/O (idregs=0x20/0x21) at 0x3f0... Failed. Returned data: id=0xff, rev=0xff Probing for SMSC Super I/O (idregs=0x0d/0x0e) at 0x3f0... Failed. Returned data: id=0xff, rev=0xff Probing for SMSC Super I/O (idregs=0x20/0x21) at 0x370... Failed. Returned data: id=0xff, rev=0xff Probing for SMSC Super I/O (idregs=0x0d/0x0e) at 0x370... Failed. Returned data: id=0xff, rev=0xff Probing for Winbond Super I/O (init=0x88) at 0x2e... Failed. Returned data: id/oldid=0x55/0x00, rev=0x70 Probing for Winbond Super I/O (init=0x89) at 0x2e... Failed. Returned data: id/oldid=0x55/0x00, rev=0x70 Probing for Winbond Super I/O (init=0x86,0x86) at 0x2e... Failed. Returned data: id/oldid=0x55/0x00, rev=0x70 Probing for Winbond Super I/O (init=0x87,0x87) at 0x2e... Failed. Returned data: id/oldid=0x55/0x00, rev=0x70 Probing for Winbond Super I/O (init=0x88) at 0x4e... Failed. Returned data: id/oldid=0xff/0x0f, rev=0xff Probing for Winbond Super I/O (init=0x89) at 0x4e... Failed. Returned data: id/oldid=0xff/0x0f, rev=0xff Probing for Winbond Super I/O (init=0x86,0x86) at 0x4e... Failed. Returned data: id/oldid=0xff/0x0f, rev=0xff Probing for Winbond Super I/O (init=0x87,0x87) at 0x4e... Failed. Returned data: id/oldid=0xff/0x0f, rev=0xff Probing for Winbond Super I/O (init=0x88) at 0x3f0... Failed. Returned data: id/oldid=0xff/0x0f, rev=0xff Probing for Winbond Super I/O (init=0x89) at 0x3f0... Failed. Returned data: id/oldid=0xff/0x0f, rev=0xff Probing for Winbond Super I/O (init=0x86,0x86) at 0x3f0... Failed. Returned data: id/oldid=0xff/0x0f, rev=0xff Probing for Winbond Super I/O (init=0x87,0x87) at 0x3f0... Failed. Returned data: id/oldid=0xff/0x0f, rev=0xff Probing for Winbond Super I/O (init=0x88) at 0x370... Failed. Returned data: id/oldid=0xff/0x0f, rev=0xff Probing for Winbond Super I/O (init=0x89) at 0x370... Failed. Returned data: id/oldid=0xff/0x0f, rev=0xff Probing for Winbond Super I/O (init=0x86,0x86) at 0x370... Failed. Returned data: id/oldid=0xff/0x0f, rev=0xff Probing for Winbond Super I/O (init=0x87,0x87) at 0x370... Failed. Returned data: id/oldid=0xff/0x0f, rev=0xff Probing for Winbond Super I/O (init=0x88) at 0x250... Failed. Returned data: id/oldid=0xff/0x0f, rev=0xff Probing for Winbond Super I/O (init=0x89) at 0x250... Failed. Returned data: id/oldid=0xff/0x0f, rev=0xff Probing for Winbond Super I/O (init=0x86,0x86) at 0x250... Failed. Returned data: id/oldid=0xff/0x0f, rev=0xff Probing for Winbond Super I/O (init=0x87,0x87) at 0x250... Failed. Returned data: id/oldid=0xff/0x0f, rev=0xff Probing for VIA Super I/O (init=0x87,0x87) at 0x2e... Failed. Returned data: id=0x55, rev=0x70 Probing for VIA Super I/O (init=0x87,0x87) at 0x4e... Failed. Returned data: id=0xff, rev=0xff Probing for VIA Super I/O (init=vt82c686) at 0x3f0... PCI device 1106:0686 not found. Probing for AMD EC Super I/O at 0xaa... Probing for Server Engines Super I/O at 0x2e... Failed. Returned data: id=0x5570, rev=0x00 Probing for Infineon Super I/O at 0x2e... Failed. Returned data: id=0x55, rev=0x70 Probing for Infineon Super I/O at 0x4e... Failed. Returned data: id=0xff, rev=0xff * flashrom -p internal -V flashrom v1.2 on Linux 6.2.6-76060206-generic (x86_64) flashrom is free software, get the source code at https://flashrom.org flashrom was built with libpci 3.7.0, GCC 11.2.0, little endian Command line (3 args): flashrom -p internal -V Using clock_gettime for delay loops (clk_id: 1, resolution: 1ns). Initializing internal programmer get_mtd_info: device_name: "BIOS", is_writeable: 0, numeraseregions: 0, total_size: 16777216, erasesize: 4096 Cannot open file stream for /dev/mtd0 No coreboot table found. Using Internal DMI decoder. No DMI table found. W836xx enter config mode worked or we were already in config mode. W836xx leave config mode had no effect. Active config mode, unknown reg 0x20 ID: 55. WARNING: No chipset found. Flash detection will most likely fail. ======================================================================== You may be running flashrom on an unknown laptop. We could not detect this for sure because your vendor has not set up the SMBIOS tables correctly. Some internal buses have been disabled for safety reasons. You can enforce using all buses by adding -p internal:laptop=this_is_not_a_laptop to the command line, but please read the following warning if you are not sure. Laptops, notebooks and netbooks are difficult to support and we recommend to use the vendor flashing utility. The embedded controller (EC) in these machines often interacts badly with flashing. See the manpage and https://flashrom.org/Laptops for details. If flash is shared with the EC, erase is guaranteed to brick your laptop and write may brick your laptop. Read and probe may irritate your EC and cause fan failure, backlight failure and sudden poweroff. You have been warned. ======================================================================== The following protocols are supported: None. No EEPROM/flash device found. Note: flashrom can never write if the flash chip isn't found automatically. My PC has an Intel i7-10750H processor, an NVidia GeForce RTX 3060 graphics card, 64 GB of RAM: Getting SMBIOS data from sysfs. SMBIOS 3.2.0 present. Handle 0x001C, DMI type 16, 23 bytes Physical Memory Array Location: System Board Or Motherboard Use: System Memory Error Correction Type: None Maximum Capacity: 32 GB Error Information Handle: No Error Number Of Devices: 2 Handle 0x001D, DMI type 17, 84 bytes Memory Device Array Handle: 0x001C Error Information Handle: No Error Total Width: 64 bits Data Width: 64 bits Size: 32 GB Form Factor: SODIMM Set: None Locator: ChannelA-DIMM0 Bank Locator: BANK 0 Type: DDR4 Type Detail: Synchronous Speed: 2933 MT/s Manufacturer: Kingston Serial Number: B5766329 Asset Tag: 9876543210 Part Number: 9905744-066.A00G Rank: 2 Configured Memory Speed: 2933 MT/s Minimum Voltage: 1.25 V Maximum Voltage: 1.5 V Configured Voltage: 1.2 V Memory Technology: DRAM Memory Operating Mode Capability: Volatile memory Firmware Version: Not Specified Module Manufacturer ID: Bank 2, Hex 0x98 Module Product ID: Unknown Memory Subsystem Controller Manufacturer ID: Unknown Memory Subsystem Controller Product ID: Unknown Non-Volatile Size: None Volatile Size: 32 GB Cache Size: None Logical Size: None Handle 0x001E, DMI type 17, 84 bytes Memory Device Array Handle: 0x001C Error Information Handle: No Error Total Width: 64 bits Data Width: 64 bits Size: 32 GB Form Factor: SODIMM Set: None Locator: ChannelB-DIMM0 Bank Locator: BANK 2 Type: DDR4 Type Detail: Synchronous Speed: 2933 MT/s Manufacturer: Kingston Serial Number: C8B67CA0 Asset Tag: 9876543210 Part Number: 9905744-066.A00G Rank: 2 Configured Memory Speed: 2933 MT/s Minimum Voltage: 1.25 V Maximum Voltage: 1.5 V Configured Voltage: 1.2 V Memory Technology: DRAM Memory Operating Mode Capability: Volatile memory Firmware Version: Not Specified Module Manufacturer ID: Bank 2, Hex 0x98 Module Product ID: Unknown Memory Subsystem Controller Manufacturer ID: Unknown Memory Subsystem Controller Product ID: Unknown Non-Volatile Size: None Volatile Size: 32 GB Cache Size: None Logical Size: None Thank you in advance for your attention to my message. Yours sincerely, LACHAUD Cédric

1 0

New on blogs.coreboot.org: Embracing a New Era: 9elements and AMD Collaborate to Bring Open-Source Firmware to 4th Gen EPYC Server Systems
by blogs.coreboot.org 18 Apr '23

18 Apr '23

1 0

Re: Supermicro X11SSH-LN4F PCI-e bifurcation?
by Kyösti Mälkki 16 Apr '23

16 Apr '23

On Sun, Apr 16, 2023 at 12:33 AM Tomas <tomas(a)fritiofson.se> wrote: > > Hi > Thank you. > I flashed the OEM firmware back on to the chip, tried the bifurcation card with two NVMe drives, and dumped lspci oputput to file. > There is a setting in the UEFI setup where you can set PCI-e SLOT5 Bifurcation to "Auto" or x4x4. > Hi, please reply to mailing list too. I left out the complete lspci you sent, but attached here is the relevant section. It is PCI 0:1.1 and 0:1.2 that require different configuration from what stock coreboot now does. I think the patch I sent previously has a fair likelihood of working. Auto-detection or a choice in menuconfig is something that can come later. Kyösti

2 1

SMSC- EMC2300 driver
by Ahmet Fenerci 14 Apr '23

14 Apr '23

Hello, We have an Intel (Denverton, cpu:C3758) Harcuvar custom board. We use SMSC-EMC2300 fan controller in the board. It works on i2c bus but driver not available. Is it possible to add SMSC-EMC2300 driver in coreboot? Kind regards, Ahmet FENERCİ

1 0

X200 GPU slowdown that needs to be cured by S3
by Artem Mazurov 13 Apr '23

13 Apr '23

Hello. Whenever I try to run any program that uses 3D acceleration (like glmark2), after a short while performance drops significantly (From 14 FPS running terrain benchmark to 3 FPS) and persists until S3. What could be the problem and how can I troubleshoot this? Since S3 fixes it, maybe it's something with coreboot? cbmem.log attached.

1 0

Supermicro X11SSH-LN4F PCI-e bifurcation?
by Tomas 13 Apr '23

13 Apr '23

Hi, I installed Coreboot with SeaBIOS on a Supermicro X11SSH-LN4F. The stock BIOS can read two NVMe drives in a Dual m.2 splitter card inserted in the middle slot 5 on the motherboard. But coreboot can not. In the coreboot nconfig menu there is no setting that will enable bifurcation of the x8 slot to x4x4. Is this something that is configurable in any way? /Tomas

2 1

request for support new hardware from coreboot
by Artem 12 Apr '23

12 Apr '23

Hello Im Artem from Khadas https://www.khadas.com/ We developing new product our hardware based on: Alder Lake ULT 12th Gen Intel Core i7-1280P We have plans to use coreboot as alternative bootloader for our new product We need some information about: 1) coreboot possibilities for current hardware 2) estimated time to create some initial workable prototype 3) what information we need provide for your side at this moment we use BIOS from AMI: Vendor: Amerian Megatrends Core Verion: 5.27 Compiancy: UEFI 2.8; PI 1.7 etc... About us We are Shenzhen Wesion Technology Co., Ltd is the company that owns the brand "Khadas", our company was founded on 5 November 2014. We focus on developing, manufacturing and marketing single board computers (SBCs) ... more info https://www.khadas.com/about Best regards Artem

2 1

proposal for cross compilation: add Rust support
by ron minnich 07 Apr '23

07 Apr '23

https://review.coreboot.org/c/coreboot/+/74124 First step, which I almost certainly did incorrectly, is to add Rust toolchain support to the Makefile. Next, adding a rust payload was suggested. I'll look into that, probably rewriting linuxcheck in rust (since I'm the only user anyway :-)

2 2

[coreboot - Bug #121] T520: Hangs in OS
by Evgeny Zinoviev 07 Apr '23

07 Apr '23

Issue #121 has been updated by Evgeny Zinoviev. On my x230 with gentoo, with recent kernel the situation has worsened significally. If on 5.x kernels it worked somewhat stable (I had crashes maybe once in a month or so and maybe it wasn't even coreboot related), now I after upgrade to 6.1.12-gentoo and it freezes like twice a day. This might be completely bug-121-unrelated, but limiting max cstate to c3 seems to fix the issue, so I decided to report here anyway... can anybody confirm the same? I mean that the newer kernel == more freezes/crashes ---------------------------------------- Bug #121: T520: Hangs in OS https://ticket.coreboot.org/issues/121#change-1466 * Author: Julz Buckton * Status: New * Priority: Normal * Start date: 2017-06-09 ---------------------------------------- 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) -- 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

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