Ubuntu更新后启动黑屏（联想ThinkBook）的排查求助

看起来你在Ubuntu更新后碰到了挺闹心的启动黑屏问题，左上角那个不闪的下划线确实让人头疼。先给你梳理下目前的情况，再分享几个针对性的排查方向：

你的问题背景与已尝试操作 #

我的联想ThinkBook安装Ubuntu更新后，启动时会停在黑屏界面，左上角有个不闪烁的下划线。目前能进入Recovery模式、获取root权限查看日志，但不知道该从哪里着手修复，也摸不清问题根源。

你已经尝试过这些操作：

• 切换到旧内核启动，结果依旧黑屏
• 尝试禁用X服务以文本模式启动，但没成功
• 启动过程中能看到系统消息，直到某一阶段突然黑屏冻结

你提供的启动日志关键信息 #

以下是你截取的内核与启动日志（整理后）：

[  0.223581] ACPI Error: AE_ALREADY_EXISTS, During name lookup/catalog (20220331/psobject-220)
[  0.223586] ACPI BIOS Error (bug): Failure creating named object [_SB.PCI0.XHC.RHUB.SS05._UPC], AE_ALREADY_EXISTS (20220331/dswload2-326)
[  0.223589] ACPI Error: AE_ALREADY_EXISTS, During name lookup/catalog (20220331/psobject-220)
[  0.223593] ACPI BIOS Error (bug): Failure creating named object [_SB.PCI0.XHC.RHUB.SS05._PLD], AE_ALREADY_EXISTS (20220331/dswload2-326)
[  0.223596] ACPI Error: AE_ALREADY_EXISTS, During name lookup/catalog (20220331/psobject-220)
[  0.223601] ACPI BIOS Error (bug): Failure creating named object [_SB.PCI0.XHC.RHUB.SS06._UPC], AE_ALREADY_EXISTS (20220331/dswload2-326)
[  0.223604] ACPI Error: AE_ALREADY_EXISTS, During name lookup/catalog (20220331/psobject-220)
[  0.223608] ACPI BIOS Error (bug): Failure creating named object [_SB.PCI0.XHC.RHUB.SS06._PLD], AE_ALREADY_EXISTS (20220331/dswload2-326)
[  0.223611] ACPI Error: AE_ALREADY_EXISTS, During name lookup/catalog (20220331/psobject-220)
[  0.251319] ACPI BIOS Error (bug): Could not resolve symbol [_SB.UBTC.CR04._PLD], AE_NOT_FOUND (20220331/psargs-330)
[  0.251339] ACPI Error: Aborting method _SB.UBTC.RUCC due to previous error (AE_NOT_FOUND) (20220331/psparse-529)
[  0.251345] ACPI Error: Aborting method _SB.PCI0.XHC.RHUB.HS07._PLD due to previous error (AE_NOT_FOUND) (20220331/psparse-529)
[  8.063631] ACPI BIOS Error (bug): Could not resolve symbol [_SB.UBTC.CR04._PLD], AE_NOT_FOUND (20220331/psargs-330)
[  8.063679] ACPI Error: Aborting method _SB.UBTC.RUCC due to previous error (AE_NOT_FOUND) (20220331/psparse-529)
[  8.063754] ACPI Error: Aborting method _SB.PCI0.XHC.RHUB.HS07._PLD due to previous error (AE_NOT_FOUND) (20220331/psparse-529)
[  8.063877] ACPI BIOS Error (bug): Could not resolve symbol [_SB.UBTC.CR04._PLD], AE_NOT_FOUND (20220331/psargs-330)
[  8.063910] ACPI Error: Aborting method _SB.UBTC.RUCC due to previous error (AE_NOT_FOUND) (20220331/psparse-529)
[  8.063957] ACPI Error: Aborting method _SB.PCI0.XHC.RHUB.HS07._PLD due to previous error (AE_NOT_FOUND) (20220331/psparse-529)
/dev/nvme0n1p5: clean, 1337885/6406144 files, 24803739/25600256 blocks
Starting User Login Management...
Starting Thermal Daemon Service...
Starting Fix touchpad issue by binding correct driver...
Starting Disk Manager...
Starting LSB: This service stops the USB Arbitrator....
Starting WPA supplicant...
[  OK  ] Started Atop process accounting daemon.
[  OK  ] Started System Logging Service.
[FAILED] Failed to start Fix touchpad issue by binding correct driver.
See 'systemctl status touchpadfix.service' for details.
[  OK  ] Finished Initialize hardware monitoring sensors.
Starting Atop advanced performance monitor...
Starting Process error automatic reporting is enabled...
[  OK  ] Finished Record successful boot for GRUB.
Starting GRUB failed boot detection...
[  OK  ] Started LSB: automatic crash report generation.
[  OK  ] Started WPA supplicant.
[  OK  ] Started Thermal Daemon Service.
[  OK  ] Started Avahi mDNS/DNS-SD Stack.
[  OK  ] Started Atop advanced performance monitor.
[  OK  ] Finished Detect the available deals with any system changes.
[  OK  ] Finished GRUB failed boot detection.
[  OK  ] Started Switcheroo Control Proxy service.
[  OK  ] Started Authorization Manager.
Starting Modem Manager...
[  OK  ] Started Network Manager.
[  OK  ] Reached target Network.
Starting Network Manager Wait Online...
Starting containerd container runtime...
Starting CUPS Scheduler...
Starting OpenVPN service...
Starting OpenBSD Secure Shell server...
Starting Permit User Sessions...
[  OK  ] Finished OpenVPN service.
Starting Host...

从日志里能看到几个关键点：

1. 一堆ACPI BIOS错误：这类错误大多是BIOS层面的命名冲突或符号缺失，虽然看起来吓人，但很多时候不会直接导致黑屏，不过后续可以考虑更新BIOS试试。
2. 触摸板修复服务启动失败：[FAILED] Failed to start Fix touchpad issue by binding correct driver.，这个可能和硬件驱动有关，但暂时不确定是否是黑屏的直接原因。
3. 启动卡在Starting Host...：说明系统在启动用户会话或图形相关服务时卡住了，大概率是图形界面的问题。

具体排查步骤 #

1. 先确认卡住的服务细节 #

进入Recovery模式的root shell，先启用网络（选择Recovery菜单里的network选项），然后执行命令查看上一次启动的完整日志，找到卡住的具体服务：

journalctl -b -1

或者直接看启动日志：

cat /var/log/boot.log

重点看最后几行的服务状态，比如gdm3（Ubuntu默认显示管理器）是否启动失败。

2. 强制以文本模式启动（修正之前的尝试） #

之前你尝试禁用X没成功，可能是方法不对，试试这个：

• 启动时按住Shift键进入GRUB菜单
• 选中要启动的内核，按e进入编辑模式
• 找到以linux开头的行，在末尾添加systemd.unit=multi-user.target
• 按Ctrl+X启动，这样会直接进入文本登录界面
  如果能成功进入，说明问题肯定出在图形界面驱动或显示管理器上。

3. 修复图形界面相关问题 #

如果进入了文本模式，先试试重新安装显示管理器：

sudo apt update && sudo apt install --reinstall gdm3

然后切换回图形模式并重启：

sudo systemctl set-default graphical.target
sudo reboot

如果还是不行，检查显卡驱动：

• 先查看显卡型号：lspci | grep VGA
• 如果你是Intel核显，重新安装核显驱动：

sudo apt install --reinstall xserver-xorg-core xserver-xorg-video-intel

• 如果是NVIDIA独显，先卸载旧驱动再重装：

sudo apt purge nvidia*
sudo apt install nvidia-driver-535  # 替换成适合你显卡的版本，比如525、540等

4. 处理失败的触摸板服务 #

虽然不一定是黑屏原因，但先禁用它避免干扰：

sudo systemctl stop touchpadfix.service
sudo systemctl disable touchpadfix.service

然后查看这个服务的具体错误：

systemctl status touchpadfix.service

5. 检查磁盘与BIOS设置 #

• 磁盘检查：虽然日志显示分区是干净的，但可以在Recovery模式下执行fsck /dev/nvme0n1p5再次确认（执行前确保分区是只读挂载）。
• BIOS设置：重启进入BIOS，检查是否开启了Secure Boot，尝试关闭它；另外可以去联想官网下载对应型号的最新BIOS更新试试。

备注：内容来源于stack exchange，提问作者Dan123