coreboot February 2022

coreboot@coreboot.org

19 participants
43 discussions

[coreboot - Bug #302] (Closed) You need to be root
by Felix Singer 11 Feb '22

11 Feb '22

Issue #302 has been updated by Felix Singer. Status changed from New to Closed No response after 11 months. Closing. ---------------------------------------- Bug #302: You need to be root https://ticket.coreboot.org/issues/302#change-881 * Author: Tim L * Status: Closed * Priority: Normal * Start date: 2021-03-29 ---------------------------------------- ~~~ # ./intelmetool -m iopl: Operation not permitted You need to be root. # id uid=0(root) gid=0(root) groups=0(root) ~~~ -- 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 #48] (Closed) Linux fails to boot with embedded GRUB payload but works with embedded SeaBIOS payload
by Felix Singer 11 Feb '22

11 Feb '22

Issue #48 has been updated by Felix Singer. Status changed from New to Closed ---------------------------------------- Bug #48: Linux fails to boot with embedded GRUB payload but works with embedded SeaBIOS payload https://ticket.coreboot.org/issues/48#change-880 * Author: Timothy Pearson * Status: Closed * Priority: Normal * Category: os_handoff * Start date: 2016-04-28 ---------------------------------------- When booting an ASUS KGPE-D16 with the embedded GRUB payload Linux fails to acquire the ACPI IRQ and/or tables; booting the same board and OS image with the embedded SeaBIOS payload works fine. Log of failed kernel boot from GRUB attached; logs of the successful kernel boot under SeaBIOS are forthcoming. ---Files-------------------------------- kgpe-d16-grub-linux-acpi-failure.log (21.2 KB) kgpe-d16-seabios-linux-success.log (376 KB) kgpe-d16-grub-linux-4.5-failure.log (366 KB) kgpe-d16-seabios-linux-4.5-success.log (379 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

[coreboot - Bug #93] (Closed) Romstage messages missing on Asus KGPE-D16
by Felix Singer 11 Feb '22

11 Feb '22

Issue #93 has been updated by Felix Singer. Status changed from New to Closed ---------------------------------------- Bug #93: Romstage messages missing on Asus KGPE-D16 https://ticket.coreboot.org/issues/93#change-879 * Author: Paul Menzel * Status: Closed * Priority: Normal * Start date: 2017-01-31 ---------------------------------------- With no CMOS battery (not tested with one yet), and using the user option table (CMOS/NVRAM) nothing is shown on the serial console until 40 s right before ramstage starts. ``` # This image was built using coreboot 4.5-917-g545edca CONFIG_ANY_TOOLCHAIN=y CONFIG_USE_OPTION_TABLE=y CONFIG_COLLECT_TIMESTAMPS=y CONFIG_USE_BLOBS=y CONFIG_BOOTBLOCK_NORMAL=y CONFIG_VENDOR_ASUS=y CONFIG_BOARD_ASUS_KGPE_D16=y CONFIG_NO_POST=y CONFIG_COREBOOT_ROMSIZE_KB_16384=y CONFIG_SOUTHBRIDGE_AMD_SB700_33MHZ_SPI=y CONFIG_CONSOLE_CBMEM_BUFFER_SIZE=0x40000 CONFIG_DEFAULT_CONSOLE_LOGLEVEL_3=y CONFIG_PAYLOAD_GRUB2=y CONFIG_GRUB2_EXTRA_MODULES="boottime" CONFIG_GRUB2_INCLUDE_RUNTIME_CONFIG_FILE=y CONFIG_COREINFO_SECONDARY_PAYLOAD=y CONFIG_MEMTEST_SECONDARY_PAYLOAD=y CONFIG_MEMTEST_MASTER=y CONFIG_NVRAMCUI_SECONDARY_PAYLOAD=y CONFIG_TINT_SECONDARY_PAYLOAD=y ``` Please find the log from CBMEM console attached. ---Files-------------------------------- 20170131–coreboot–asus_kgpe-d16–cbmem-c.txt (84.5 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

[coreboot - Bug #321] (Resolved) NVME in X16 port issue
by Felix Singer 11 Feb '22

11 Feb '22

Issue #321 has been updated by Felix Singer. Status changed from New to Resolved ---------------------------------------- Bug #321: NVME in X16 port issue https://ticket.coreboot.org/issues/321#change-878 * Author: Francois Ollonois * Status: Resolved * Priority: Normal * Start date: 2021-09-07 ---------------------------------------- I have used latest git version of coreboot to build a rom for my ASUS P5QL-EM. I have some strange behavior: I use a **X16 nvme** Adapter in the X16 graphic card slot. I also want to use an add-on gpu card (nvidia GT710 **PCIe X1**) to be able to use higher resolution displays. With the bare board without any card everything works fine, but when I plug in the nvme adapter card with ssd, only the VGA output is working, but it is shiftet one character to the left. HDMI and DVI output are dead. It is possible to boot from the nvme ssd in this configuration. When the GT710 is pluged in, it is no longer possible to boot from the nvme ssd. (Read Error) ---Files-------------------------------- p5ql-em.config (17 KB) coreboot_p5ql_with_nvme_hdmi (40.7 KB) lspci_vendor.txt (61.9 KB) lspci_coreboot_root2.txt (64.3 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

[coreboot - Bug #249] (Closed) Clean up jasperlake_rvp devictree
by Felix Singer 11 Feb '22

11 Feb '22

Issue #249 has been updated by Felix Singer. Status changed from New to Closed ---------------------------------------- Bug #249: Clean up jasperlake_rvp devictree https://ticket.coreboot.org/issues/249#change-877 * Author: Aamir Bohra * Status: Closed * Priority: Normal * Assignee: Aamir Bohra * Start date: 2019-12-27 ---------------------------------------- Current jasperlake_rvp mainboard CL: https://review.coreboot.org/c/coreboot/+/37557 is based on copy from icelake_rvp . Once this is merged, devicetree needs to be cleaned up as per JSL SOC. This bug tracks further jasperlake_rvp mainboard devicetree cleanup -- 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 #22] (Resolved) X230 native raminit failed
by Felix Singer 11 Feb '22

11 Feb '22

Issue #22 has been updated by Felix Singer. Status changed from Needs Testing to Resolved ---------------------------------------- Bug #22: X230 native raminit failed https://ticket.coreboot.org/issues/22#change-876 * Author: Patrick Rudolph * Status: Resolved * Priority: Normal * Assignee: Patrick Rudolph * Start date: 2016-01-10 ---------------------------------------- Native raminit failed with: "edge write discovery failed". It's failing on channel 1 with two DIMMs installed, while it has no problems booting with a single DIMM. The test fails on lane 1. These are the Cvals of channel 1: Cval: 1, 1, 0, 26 Cval: 1, 1, 1, 21 Cval: 1, 1, 2, 41 Cval: 1, 1, 3, 4d Cval: 1, 1, 4, 4e Cval: 1, 1, 5, 52 Cval: 1, 1, 6, 2c Cval: 1, 1, 7, 5e Cval: 1, 0, 0, 22 Cval: 1, 0, 1, 5e Cval: 1, 0, 2, 3b Cval: 1, 0, 3, 4a Cval: 1, 0, 4, 4a Cval: 1, 0, 5, 4c Cval: 1, 0, 6, 29 Cval: 1, 0, 7, 5b Values for the same lane are about the same (+- 6units), but only lane 1 shows a huge offset of 61. ---Files-------------------------------- x230_edge_write_discovery_failed.log (911 KB) debugboot1.txt (61.7 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

[coreboot - Bug #45] (Closed) F2A85-M fails to detect 24-32GB of RAM properly
by Felix Singer 11 Feb '22

11 Feb '22

Issue #45 has been updated by Felix Singer. Status changed from Response Needed to Closed Closed. No response since 5 years. ---------------------------------------- Bug #45: F2A85-M fails to detect 24-32GB of RAM properly https://ticket.coreboot.org/issues/45#change-875 * Author: Daniel Kulesz * Status: Closed * Priority: Normal * Assignee: Kyösti Mälkki * Start date: 2016-04-25 ---------------------------------------- Hi, I am running Coreboot 4.3 release on the Asus F2a85-M with 16GB of Crucial Ballistix Sport DDR-1600 DIMMs at 1,5V (2 sticks). When I populate the remaining RAM slots with another 2 sticks of the same type, the system does not boot to the Payload. When I put only 1 of the additional sticks in (so in total I should have 24GB), the system boots fine but I am seeing 78GB (!!) of memory detected on the operating system - see the attached output. I don't have the coreboot config at hand, but I am just running basically 4.3 release configured for this board together with the vgabios blob. Is it safe to try the 4.4 prerelease to see if the bug can be reproduced there as well? I am just asking because I have no separate chip as backup nor the proper clip for hardware flashing this device. ---Files-------------------------------- memtotal.txt (1.21 KB) coreboot.rom.bz2 (446 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

[coreboot - Bug #37] (Closed) x220/native graphics: after some time the display shows only a one color blur image.
by Felix Singer 11 Feb '22

11 Feb '22

Issue #37 has been updated by Felix Singer. Status changed from Response Needed to Closed Closed. No response since 5 years. ---------------------------------------- Bug #37: x220/native graphics: after some time the display shows only a one color blur image. https://ticket.coreboot.org/issues/37#change-874 * Author: Alexander Couzens * Status: Closed * Priority: Normal * Start date: 2016-03-12 ---------------------------------------- After some time the display goes into a one color blur mode. Everything but the display continues to work. Changing to another tty doesn't help. Workaround: suspend/resume <pre> [22770.401257] [drm:intel_set_pch_fifo_underrun_reporting [i915]] *ERROR* uncleared pch fifo underrun on pch transcoder A </pre> ---Files-------------------------------- config (349 Bytes) dmesg_with_resume_with_native_graphics_with_failure (154 KB) dmesg_with_resume_with_native_graphics_without_failure (126 KB) dmesg_vgabios (126 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

[coreboot - Bug #47] (Closed) Wsxga+ screens display Grub incorrectly
by Felix Singer 11 Feb '22

11 Feb '22

Issue #47 has been updated by Felix Singer. Status changed from Response Needed to Closed Closed. No response since 5 years. ---------------------------------------- Bug #47: Wsxga+ screens display Grub incorrectly https://ticket.coreboot.org/issues/47#change-873 * Author: Kete Foy * Status: Closed * Priority: Normal * Start date: 2016-04-27 ---------------------------------------- Wsxga+ screens partition Grub output into a few sections, and one of the sections is blank; so it's hard to use the Grub commandline. -- 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 #147] (Closed) Backlight level setting is not restored when the display wakes up from sleep on ThinkPad X230
by Felix Singer 11 Feb '22

11 Feb '22

Issue #147 has been updated by Felix Singer. Status changed from Feedback to Closed Closed. No response since 3 years. ---------------------------------------- Bug #147: Backlight level setting is not restored when the display wakes up from sleep on ThinkPad X230 https://ticket.coreboot.org/issues/147#change-872 * Author: Tobis Greer * Status: Closed * Priority: Normal * Start date: 2017-11-03 ---------------------------------------- I am using Ubuntu 17.10, it also occurred on 17.04. Whenever the display is sleeping (the laptop is still awake, just the display is off), and when it wakes up again (by moving the mouse, or issuing a keypress); then the backlight setting is at 100% regardless of what it was set at before the display went to sleep. If I press the Fn+F8 key to set it again, one press is enough for the backlight level to go down several increments; back to where it was before the display turned off. This didn't happen with the same Ubuntu install but running the stock BIOS. For context, here is an excerpt from the mailing list: ~~~ this is a known issue. It actually was there all the time but only got more visible with the introduction of ACPI/OpRegion for the inte- grated GFX. Here is what I found out so far (on my ArchLinux): w/o OpRegion: 1. `acpi_video` driver gets loaded, systemd restores brightness from last shutdown. 2. `i915` driver gets loaded, reads the current brightness. 3. `i915` exposes backlight as `intel_backlight`, systemd restores brightness from last shutdown here as well. Every time `i915` power cycles the backlight, it restores the value it has seen when it was loaded. w/ Opregion the order somehow changes to 2. 1. 3., now `i915` always restores to 100% that it read before systemd restored the brightness. A sane solution would be to extend XBCM in `src/drivers/intel/gma/acpi/ configure_brightness_levels.asl` to always notify `i915` when we change the backlight through OpRegion mailbox 3. ~~~ Happy to provide more logs or details as required. 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

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

2003

2002

coreboot February 2022