Hi all,
I’m currently trying to resolve an issue with my QubesOS install.
Presently when I boot my Librem Mini v2 with 2 monitors connected I get a freeze in the boot process about 90% of the time. I initially thought this issue was related to the bootloader, however it was later pointed out to me that the corruption seen on the screen occurs as Qubes is initializing i915.
Here is a link to my Github issue, which includes an image of the issue: https://github.com/QubesOS/qubes-issues/issues/8467
I now find myself trying to find the issue in logs, however that is turning out to be difficult.
As suggested I enabled debug verbose loglevel=7
in my grub at the end of GRUB_CMDLINE_LINUX
, here is what my grub now looks like:
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"
I’m now trying to produce a log using journalctl, however this is where I am encountering another issue.
Assume i boot the computer 3 times:
- Boot 1: This boot is fine with no issues
- Boot 2: the issue occurs which forces me to have to restart the computer by holding down the power button until it turns off, then pressing the power button again to turn it on
- Boot 3: This boot is fine with no issues (this is my current session)
I produce logs for this session for comparison:
journalctl -b > good_boot.txt
Then I want to produce logs for the bad boot for analysis:
journalctl -b -1 > bad_boot.txt
However journalctl -b -1
produces logs of Boot 1, I’m guessing because I do a hard shutoff via the power button it doesn’t persist the logs.
I then assumed the issue could be to do with persistent logging, therefore I enabled persistent logging by adding Storage=persistent
to /etc/systemd/journald.conf
, my journald.conf now is as follows:
[Journal]
Storage=persistent
#Compress=yes
#Seal=yes
#SplitMode=uid
#SyncIntervalSec=5m
#RateLimitIntervalSec=30s
#RateLimitBurst=10000
#SystemMaxUse=
#SystemKeepFree=
#SystemMaxFileSize=
#SystemMaxFiles=100
#RuntimeMaxUse=
#RuntimeKeepFree=
#RuntimeMaxFileSize=
#RuntimeMaxFiles=100
#MaxRetentionSec=
#MaxFileSec=1month
#ForwardToSyslog=no
#ForwardToKMsg=no
#ForwardToConsole=no
#ForwardToWall=yes
#TTYPath=/dev/console
#MaxLevelStore=debug
#MaxLevelSyslog=debug
#MaxLevelKMsg=notice
#MaxLevelConsole=info
#MaxLevelWall=emerg
#LineMax=48K
#ReadKMsg=yes
#Audit=yes
However the issue still persists and I am unable to produce the logs of the ‘bad boot’ to diagnose the issue. Could someone please point me in the right direction as I am very stuck.
Is there a way to persist the journald logs?
Or is there another set of logs that I’m unaware of that would have captured the issue?
Thanks.