HDMI output usually not available after cold boot

[marmarek]

Please identify some basic details to help process the report

A. Provide Hardware Details

1. What board are you using (see list of boards here)?

x230

2. Does your computer have a dGPU or is it iGPU-only?

• dGPU
• iGPU-only

3. Who installed Heads on this computer?

• Insurgo
• Nitrokey
• Purism
• Other provider
• Self-installed

4. What PGP key is being used?

• Librem Key
• Nitrokey Pro 2
• Nitrokey Storage
• Yubikey
• Other

5. Are you using the PGP key to provide HOTP verification?

• Yes
• No
• I don't know

B. Identify how the board was flashed

1. Is this problem related to updating heads or flashing it for the first time?

• First-time flash
• Updating heads

2. If the problem is related to an update, how did you attempt to apply the update?

• Using the Heads GUI
• Flashrom via the Recovery Shell
• External flashing

3. How was Heads initially flashed

• External flashing
• Internal-only / 1vyrain
• Don't know

4. Was the board flashed with a maximized or non-maximized/legacy rom?

• Maximized
• Non-maximized / legacy
• I don't know

5. If Heads was externally flashed, was IFD unlocked?

• Yes
• No
• Don't know

C. Identify the rom related to this bug report

1. Did you download or build the rom at issue in this bug report?

• I downloaded it
• I built it

2. If you downloaded your rom, where did you get it from?

• Heads CircleCi
• Purism
• Nitrokey
• Somewhere else (please identify)

Please provide the release number or otherwise identify the rom downloaded

https://circleci.com/gh/linuxboot/heads/14178 ( x230-hotp-maximized_usb-kb of 4a57c61)

Please describe the problem

Describe the bug

HDMI output is not available on cold boot (no signal). Pressing ctrl+alt+delete usually fixes it.

To Reproduce
Steps to reproduce the behavior:

1. Connect HDMI output to the laptop (via miniDP->HDMI converter)
2. Press power button

Expected behavior

Heads output on both internal screen and the external one.

Additional context

It wasn't a problem on a (much) older version - the one used for initial x230 Qubes OS certification.

I've tested also commit just before merging #1522 and the issue happens there too.

[tlaurion]

@marmarek Do you see cbmem -1/dmesg differences between coldboot/warmboot?

You can easy export with usb thumb drive connected and

• mount-usb --mode rw
• cbmem -1 > /media/cbmem_coldboot.log
• dmesg > /media/dmesg_coldboot.log
• reboot #(sysrq magic triggers remount of all fs in ro)
• mount-usb --mode rw
• cbmem -1 > /media/cbmem_warmboot.log
• dmesg > /media/dmesg_warmboot.log
• reboot
• post logs here

Definitely a coreboot issue here but if we can see something different there then a proper upstream linked bug report might lead to resolving the issue here (again coreboot upstream is 4.22 and version used here 4.19 because fhd patchset not merged upstream and used downstream... but that is different story)

[tlaurion]

@marmarek ping

[marmarek]

Logs here.

cbmem-cold.txt
cbmem-warm.txt
dmesg-cold.txt
dmesg-warm.txt

I don't see much difference besides indeed coreboot log says HDMI is disabled on cold boot. BTW, after warm reboot Linux says input: AT Translated Set 2, while after cold boot it's input: AT Raw Set 2 keyboard - related to #958 ? Note, I stopped at Heads here (collected logs from recovery shell), Qubes (or any other OS) was not started between reboots.