Librem Mini v2 with dual monitors often freezes on boot

[sienks]

Qubes OS release

4.1.2
4.1.2 - also tried with kernel 6.4.7-1.qubes.fc32.x86_64
4.2.0-rc2

Brief summary

When booting with a Librem Mini v2 PC, with 2 monitors connected both monitors will freeze on the initial boot screen approx 80% of the time.

I can always pass the initial boot screen with 1 monitor connected (although the freeze has occurred once with only one monitor connected), so currently I boot with one screen connected then plug in the other screen once I see the LUKS prompt.

Steps to reproduce

• Using a Librem Mini v2, specs: https://shop.puri.sm/shop/librem-mini/
• Connect two monitors
• Issue will occur approx 80% of the time

Expected behavior

Boot and display LUKS prompt

Actual behavior

I initially thought this was a Pureboot issue: https://forums.puri.sm/t/pureboot-problem-librem-mini-v2/20828
The response seems to indicate the issue is occurring as initrd is initializing the i915 driver.

[sienks]

This issue is still present in the current stable release of Qubes 4.2.0

What logs could I provide that would give the additional context needed to diagnose this issue?

[DemiMarie]

@m-sienk Can you try kernel-latest and see if the problem goes away?

[sienks]

@DemiMarie thanks for your response.

The same issue continues to occur using kernel: 6.6.2-1.qubes.fc37.x86_64

Additional info - this issue will also sometimes occur when only 1 monitor is connected (about 5% of the time).

What else should I check?

[sienks]

@DemiMarie
Issue is still occurring on 6.6.9-1.f37 (kernel-latest)

Is there anything else I can do in the meantime or any other info I can provide?
This issue is driving me nuts as I need to unplug my display just to boot in Qubes.

[DemiMarie]

@m-sienk can you try booting with debug?

[sienks]

@DemiMarie
How do I do that?
I checked my boot options and didn't see any 'debug' just the different installed kernels.
Do I need to enable something first?

[DemiMarie]

@m-sienk You will need to add debug to the kernel command line.

[sienks]

@DemiMarie
Also note I am using a fresh install of 4.2.1 and the issue is still occurring.

This was my original grub:

GRUB_TIMEOUT=5
GRUB_DISTRIBUTOR="$(sed 's, release .*$,,g' /etc/system-release)"
GRUB_DEFAULT=saved
GRUB_DISABLE_SUBMENU=false
GRUB_TERMINAL_OUTPUT="console"
GRUB_CMDLINE_LINUX="rd.luks.uuid=luks-d1ab3523-ce8e-43e8-869d-dc0a54985a6f rd.lvm.lv=qubes_dom0/root rd.lvm.lv=qubes_dom0/swap plymouth.ignore-serial-consoles intel_iommu=igfx_off 6.6.21-1.qubes.fc37.x86_64 x86_64 rhgb quiet"
GRUB_DISABLE_RECOVERY="true"
GRUB_THEME="/boot/grub2/themes/qubes/theme.txt"
GRUB_CMDLINE_XEN_DEFAULT="console=none dom0_mem=min:1024M dom0_mem=max:4096M ucode=scan smt=off gnttab_max_frames=2048 gnttab_max_maptrack_frames=4096"
GRUB_DISABLE_OS_PROBER="true"
GRUB_CMDLINE_LINUX="$GRUB_CMDLINE_LINUX usbcore.authorized_default=0"

I added 'debug verbose loglevel=7' at the end of GRUB_CMDLINE_LINUX

GRUB_TIMEOUT=5
GRUB_DISTRIBUTOR="$(sed 's, release .*$,,g' /etc/system-release)"
GRUB_DEFAULT=saved
GRUB_DISABLE_SUBMENU=false
GRUB_TERMINAL_OUTPUT="console"
GRUB_CMDLINE_LINUX="rd.luks.uuid=luks-d1ab3523-ce8e-43e8-869d-dc0a54985a6f rd.lvm.lv=qubes_dom0/root rd.lvm.lv=qubes_dom0/swap plymouth.ignore-serial-consoles intel_iommu=igfx_off 6.6.21-1.qubes.fc37.x86_64 x86_64 rhgb quiet debug verbose loglevel=7"
GRUB_DISABLE_RECOVERY="true"
GRUB_THEME="/boot/grub2/themes/qubes/theme.txt"
GRUB_CMDLINE_XEN_DEFAULT="console=none dom0_mem=min:1024M dom0_mem=max:4096M ucode=scan smt=off gnttab_max_frames=2048 gnttab_max_maptrack_frames=4096"
GRUB_DISABLE_OS_PROBER="true"
GRUB_CMDLINE_LINUX="$GRUB_CMDLINE_LINUX usbcore.authorized_default=0"

Then I updated grub with:

sudo grub2-mkconfig -o /boot/grub2/grub.cfg

Did I add debug mode correctly?

These are my boot options (I am using Pureboot), assuming I enabled debug correctly as outlined above I'm guessing booting with any of these options would mean I am booting with debug mode?

How can I access the more verbose logfiles?