在 HP HP ProBook 450 上运行 Ubuntu 22.04。通常在启动时，系统会在显示 fsck 输出后立即出现问题。会显示不闪烁的光标，并且系统没有响应，只有硬重启才能清除此问题。会显示错误消息 - 不同时间显示不同的消息。
然而，在检查系统日志时，发现系统似乎继续运行。我在下面列出了我看到的一些挂起消息。
# journalctl --since today
kernel: tpm tpm0: [Firmware Bug]: TPM interrupt not working, polling instead
===
kernel: iwlwifi 0000:00:14.3: BIOS contains WGDS but no WRDS
===
kernel: Bluetooth: hci0: Malformed MSFT vendor event: 0x02
===
[drm:nv_drm_load [nvidia_drm]] *ERROR* [nvidia-drm] [GPU ID 0x00000100] Failed to allocate NvKmsKapiDevice
[drm:nv_drm_probe_devices [nvidia_drm]] *ERROR* [nvidia-drm] [GPU ID 0x00000100] Failed to register device
BUG: kernel NULL pointer dereference, address: 0000000000000040
#PF: supervisor read access in kernel mode
#PF: error_code(0x0000) - not-present page
--
Failed to start Detect the available GPUs and deal with any system changes.
--
thermald[1964]: Unsupported condition 9 (Aggregate_power_percentage)
thermald[1964]: Unsupported condition 9 (Aggregate_power_percentage)
thermald[1964]: Unsupported conditions are present
thermald[1964]: Polling mode is enabled: 4
kernel: ACPI BIOS Error (bug): Could not resolve symbol [\_TZ.ETMD], AE_NOT_FOUND (20220331/psargs-330)
--
kernel: ACPI Error: Aborting method \_SB.IETM._OSC due to previous error (AE_NOT_FOUND) (20220331/psparse-529)
--
gdm-launch-environment][3113]: GLib-GObject: g_object_unref: assertion 'G_IS_OBJECT (object)' failed
大多数这些问题似乎不太可能导致系统挂起，而且正如我所说，即使我没有看到控制台的响应，日志也会记录正在进行的活动。
我越来越怀疑系统无法启动窗口系统，因为我看到如下日志条目
Apr 17 06:41:23 tigger /usr/libexec/gdm-x-session[3137]: (EE) open /dev/fb0: No such file or directory
Apr 17 06:41:23 tigger /usr/libexec/gdm-x-session[3137]: vesa: Ignoring device with a bound kernel driver
Apr 17 06:41:23 tigger /usr/libexec/gdm-x-session[3137]: (EE) Screen 0 deleted because of no matching config section.
Apr 17 06:41:23 tigger /usr/libexec/gdm-x-session[3137]: (II) UnloadModule: "modesetting"
Apr 17 06:41:23 tigger /usr/libexec/gdm-x-session[3137]: (EE) Screen 0 deleted because of no matching config section.
Apr 17 06:41:23 tigger /usr/libexec/gdm-x-session[3137]: (II) UnloadModule: "fbdev"
Apr 17 06:41:23 tigger /usr/libexec/gdm-x-session[3137]: (II) UnloadSubModule: "fbdevhw"
Apr 17 06:41:23 tigger /usr/libexec/gdm-x-session[3137]: (II) UnloadSubModule: "fbdevhw"
Apr 17 06:41:23 tigger /usr/libexec/gdm-x-session[3137]: (II) UnloadSubModule: "fbdevhw"
Apr 17 06:41:23 tigger /usr/libexec/gdm-x-session[3137]: (EE) Screen 0 deleted because of no matching config section.
Apr 17 06:41:23 tigger /usr/libexec/gdm-x-session[3137]: (II) UnloadModule: "vesa"
Apr 17 06:41:23 tigger /usr/libexec/gdm-x-session[3137]: (EE) Device(s) detected, but none match those in the config file.
Apr 17 06:41:23 tigger /usr/libexec/gdm-x-session[3137]: (EE)
Apr 17 06:41:23 tigger /usr/libexec/gdm-x-session[3137]: Fatal server error:
Apr 17 06:41:23 tigger /usr/libexec/gdm-x-session[3137]: (EE) no screens found(EE)
Apr 17 06:41:23 tigger /usr/libexec/gdm-x-session[3137]: (EE)
Apr 17 06:41:23 tigger /usr/libexec/gdm-x-session[3137]: Please consult the The X.Org Foundation support
Apr 17 06:41:23 tigger /usr/libexec/gdm-x-session[3137]: at http://wiki.x.org
Apr 17 06:41:23 tigger /usr/libexec/gdm-x-session[3137]: for help.
Apr 17 06:41:23 tigger /usr/libexec/gdm-x-session[3137]: (EE) Please also check the log file at "/var/log/Xorg.0.log" for additional information.
Apr 17 06:41:23 tigger /usr/libexec/gdm-x-session[3137]: (EE)
如今，开机需要 4 到 5 次启动才能成功启动，有时是通过恢复模式和启动修复实用程序。
如能就如何排除故障并修复此问题提供任何建议，我们将不胜感激。
在使用 Nvidia 驱动程序和 nouveau 驱动程序运行时都会发生这种情况