我想在我的系统上重新启用 IPv6，该系统当前已直接在 GRUB 中禁用。但如果我删除ipv6.disable=1，我就会得到一个空白（背光）屏幕。
今晚我才发现我有timeshift操作系统 (Linux Mint 21.3) 的备份，然后我就能够恢复到 20 天前的状态。
e我在引导期间通过 dit 测试了 GRUB cmdline 的各种组合。似乎与引导过程的某些部分冲突的唯一更改是删除ipv6.disable=1从 grub 命令行，同样的结果适用于ipv6.disable=0.我不知道会发生什么冲突，真的不知道。
这是更改前的 grub 配置文件（我的目标是重新启用 IPv6）：
GRUB_DEFAULT=saved
GRUB_SAVEDEFAULT=true
GRUB_TIMEOUT_STYLE=countdown
GRUB_TIMEOUT=3
GRUB_DISTRIBUTOR=`lsb_release -i -s 2> /dev/null || echo Debian`
GRUB_CMDLINE_LINUX_DEFAULT="fsck.mode=force fsck.repair=yes rootflags=data=journal ipv6.disable=1"
# GPU-related wakeup from suspend issue FIX
GRUB_CMDLINE_LINUX="nouveau.modeset=0"
非常感谢任何帮助。
重大更新，改变一切
实际上，大约 2 分 30 秒后，它确实显示了我的桌面。 （在我的秒表上）
一些可能有用的信息：
$ systemd-analyze blame
5.842s NetworkManager-wait-online.service
1.638s fwupd.service
1.415s [email protected]
1.294s vboxdrv.service
1.118s dev-loop11.device
1.117s dev-loop10.device
1.114s dev-loop17.device
1.113s dev-loop16.device
1.105s dev-loop18.device
1.105s dev-loop15.device
1.105s dev-loop14.device
1.104s dev-loop13.device
1.098s dev-loop12.device
1.056s snapd.service
940ms dev-loop4.device
940ms dev-loop2.device
939ms dev-loop1.device
938ms dev-loop3.device
937ms dev-loop0.device
937ms dev-loop7.device
934ms dev-loop6.device
934ms dev-loop5.device
863ms dev-nvme0n1p2.device
766ms dev-loop9.device
539ms snapd.seeded.service
460ms networking.service
367ms loadcpufreq.service
363ms accounts-daemon.service
338ms avahi-daemon.service
316ms bluetooth.service
308ms binfmt-support.service
308ms NetworkManager.service
308ms apport.service
307ms cups.service
304ms mnt-5tb.mount
304ms apparmor.service
298ms netfilter-persistent.service
281ms dev-loop8.device
277ms systemd-udev-trigger.service
271ms networkd-dispatcher.service
257ms udisks2.service
249ms polkit.service
238ms mono-xsp4.service
218ms systemd-binfmt.service
214ms lm-sensors.service
205ms grub-common.service
202ms systemd-resolved.service
189ms systemd-logind.service
185ms systemd-journal-flush.service
182ms switcheroo-control.service
181ms rsyslog.service
176ms e2scrub_reap.service
176ms gpu-manager.service
164ms secureboot-db.service
156ms [email protected]
152ms blueman-mechanism.service
143ms wpa_supplicant.service
142ms thermald.service
138ms nvidia-persistenced.service
129ms [email protected]
124ms snap-bare-5.mount
124ms ModemManager.service
122ms systemd-timesyncd.service
122ms snap-core-16202.mount
120ms snap-core-16574.mount
120ms dns-clean.service
117ms snap-core18-2796.mount
114ms snap-core18-2812.mount
113ms upower.service
112ms snap-core20-2105.mount
112ms snap-core20-2182.mount
111ms mnt-windows.mount
110ms snap-gimp-418.mount
108ms snap-gimp-428.mount
106ms snap-gnome\x2d3\x2d28\x2d1804-194.mount
106ms snap-gnome\x2d3\x2d28\x2d1804-198.mount
104ms systemd-fsck@dev-disk-by\x2duuid-4966\x2dE925.service
104ms ubuntu-system-adjustments.service
103ms snap-gnome\x2d3\x2d38\x2d2004-140.mount
103ms lightdm.service
101ms snap-gnome\x2d3\x2d38\x2d2004-143.mount
98ms snap-gtk2\x2dcommon\x2dthemes-13.mount
98ms mnt-qvo.mount
97ms console-setup.service
96ms keyboard-setup.service
95ms snap-gtk2\x2dcommon\x2dthemes-9.mount
92ms snap-gtk\x2dcommon\x2dthemes-1534.mount
89ms snap-gtk\x2dcommon\x2dthemes-1535.mount
86ms snap-kde\x2dframeworks\x2d5\x2dcore18-32.mount
86ms systemd-udevd.service
85ms update-notifier-download.service
84ms finalrd.service
84ms systemd-remount-fs.service
84ms snap-kde\x2dframeworks\x2d5\x2dcore18-35.mount
81ms systemd-modules-load.service
80ms [email protected]
80ms proc-sys-fs-binfmt_misc.mount
77ms [email protected]
76ms alsa-restore.service
75ms [email protected]
72ms systemd-journald.service
70ms colord.service
69ms smartmontools.service
68ms phpsessionclean.service
64ms kmod-static-nodes.service
61ms sys-kernel-tracing.mount
55ms sys-kernel-debug.mount
55ms grub-initrd-fallback.service
52ms cpufrequtils.service
51ms dev-mqueue.mount
46ms dev-hugepages.mount
45ms ssh.service
44ms snapd.apparmor.service
41ms boot-efi.mount
38ms openvpn.service
35ms plymouth-read-write.service
30ms systemd-update-utmp.service
30ms sys-kernel-config.mount
29ms packagekit.service
28ms sys-fs-fuse-connections.mount
27ms systemd-random-seed.service
26ms systemd-tmpfiles-setup.service
25ms systemd-sysusers.service
24ms systemd-sysctl.service
21ms systemd-user-sessions.service
17ms systemd-backlight@leds:dell::kbd_backlight.service
17ms kerneloops.service
16ms modprobe@efi_pstore.service
16ms systemd-backlight@backlight:intel_backlight.service
11ms [email protected]
9ms systemd-rfkill.service
9ms ifupdown-pre.service
9ms nvmf-autoconnect.service
9ms snapd.socket
8ms systemd-tmpfiles-setup-dev.service
7ms [email protected]
5ms systemd-update-utmp-runlevel.service
5ms plymouth-quit-wait.service
4ms vboxweb-service.service
4ms setvtrgb.service
3ms vboxautostart-service.service
3ms rtkit-daemon.service
3ms vboxballoonctrl-service.service
1ms postfix.service
答案1
终于，今天早上我腾出了时间来做这件事。从第二台计算机通过 SSH 连接到我的机器时，它看起来工作正常，没有错误踪迹dmesg或syslog直接出现。
update-grub启动两次就足够了。第一次需要相当长的时间才能显示桌面，但第二次可以正常启动。