我在 Fedora 37 上安装了 Nvidia GeForce GTX 1060 驱动程序指导一切似乎都正常。我遇到的问题是当我插入显示端口时。我的屏幕会变黑，系统需要大约 10 分钟或更长时间才能完全启动到桌面环境。奇怪的是，使用 HDMI 连接时不会出现此问题。系统启动大约需要1-2分钟。我到处寻找这种症状，人们往往指出是电缆有问题。我从一家信誉良好的公司购买了一条新电缆，但没有任何区别。我还查看了发布在https://ask.fedoraproject.org/t/black-screen-after-updating-to-6-1-5-200-fc37-w-nvidia-drivers/30759和https://ask.fedoraproject.org/t/multiple-displayport-displays-slow-boot-flickering/10132。如果我使用DP线，我的问题似乎是一样的；否则不适用。
此外，连接 DP 线时我无法看到或进入 BIOS 屏幕，但可以使用 HDMI 线访问 BIOS。 Nvidia 已修复，https://www.nvidia.com/en-us/drivers/nv-uefi-update-x64/，幸运的是我有一个旧的 Windows 驱动器安装在我的系统上。我能够启动它来进行更新。之后，我断开了 Windows 驱动器的连接，并使用 Fedora 37 启动了我的 M2 NVME Sata 驱动器。
我当前的连接是一根 DP 电缆从显卡连接到我的显示器，并以菊花链方式从一台显示器连接到另一台显示器，并在第三台显示器处终止。
以下是 HDMI 启动过程的结果：
systemd-analyze
Startup finished in 13.680s (firmware) + 7.079s (loader) + 1.798s (kernel) + 12.596s (initrd) + 9.190s (userspace) = 44.346s
graphical.target reached after 9.162s in userspace.
systemd-analyze blame | head -n 20
1min 58.150s fstrim.service
18.898s dnf-makecache.service
13.071s sys-module-fuse.device
13.036s sys-devices-platform-serial8250-tty-ttyS1.device
13.036s dev-ttyS1.device
13.035s dev-ttyS18.device
13.035s sys-devices-platform-serial8250-tty-ttyS18.device
13.034s sys-devices-platform-serial8250-tty-ttyS12.device
13.034s dev-ttyS12.device
13.033s sys-devices-platform-serial8250-tty-ttyS13.device
13.033s dev-ttyS13.device
13.033s sys-devices-platform-serial8250-tty-ttyS11.device
13.033s dev-ttyS11.device
13.033s sys-devices-platform-serial8250-tty-ttyS10.device
13.033s dev-ttyS10.device
13.033s sys-devices-platform-serial8250-tty-ttyS14.device
13.033s dev-ttyS14.device
13.032s sys-devices-platform-serial8250-tty-ttyS0.device
13.032s dev-ttyS0.device
13.031s sys-devices-platform-serial8250-tty-ttyS15.device
systemd-analyze critical-chain
The time when unit became active or started is printed after the "@" character.
The time the unit took to start is printed after the "+" character.
graphical.target @9.162s
└─multi-user.target @9.162s
└─plymouth-quit-wait.service @6.550s +2.602s
└─systemd-user-sessions.service @6.514s +23ms
└─remote-fs.target @6.501s
└─remote-fs-pre.target @6.501s
└─nfs-client.target @2.964s
└─gssproxy.service @2.945s +18ms
└─network.target @2.941s
└─wpa_supplicant.service @8.286s +10ms
└─dbus-broker.service @2.248s +19ms
└─dbus.socket @2.150s
└─sysinit.target @2.147s
└─systemd-resolved.service @2.045s +101ms
└─systemd-tmpfiles-setup.service @1.973s +54ms
└─import-state.service @1.915s +30ms
└─local-fs.target @1.914s
└─boot-efi.mount @1.902s +11ms
└─boot.mount @1.569s +11ms
└─systemd-fsck@dev-disk-by\x2duuid-49e7acd7\x2d0f9e\x2d4eea\x2d905a\x>
└─local-fs-pre.target @1.497s
└─lvm2-monitor.service @839ms +655ms
└─dm-event.socket @820ms
└─system.slice
└─-.slice
这是 DP 连接的结果。差异在于启动时间为 7 分钟。是什么赋予了？
systemd-analyze
Startup finished in 2min 2.252s (firmware) + 7.057s (loader) + 1.749s (kernel) + 2min 58.356s (initrd) + 2min 50.312s (userspace) = 7min 59.728s
graphical.target reached after 2min 50.281s in userspace.
systemd-analyze blame | head -n 20
2min 58.726s dev-disk-by\x2ddiskseq-2.device
2min 58.726s dev-disk-by\x2dpath-pci\x2d0000:00:1f.2\x2data\x2d1.device
2min 58.726s sys-devices-pci0000:00-0000:00:1f.2-ata1-host0-target0:0:0-0:0:0:0-block-sr0.device
2min 58.726s dev-sr0.device
2min 58.726s dev-disk-by\x2dpath-pci\x2d0000:00:1f.2\x2data\x2d1.0.device
2min 58.726s dev-cdrom.device
2min 58.726s dev-disk-by\x2did-ata\x2dASUS_BW\x2d12B1ST_a_K9PF4GH0434.device
2min 58.716s sys-module-fuse.device
2min 58.692s dev-disk-by\x2dpath-pci\x2d0000:00:1f.2\x2data\x2d2.0.device
2min 58.692s sys-devices-pci0000:00-0000:00:1f.2-ata2-host1-target1:0:0-1:0:0:0-block-sr1.device
2min 58.692s dev-sr1.device
2min 58.692s dev-disk-by\x2did-ata\x2dHL\x2dDT\x2dST_BD\x2dRE_WH16NS40_K93F23H1928.device
2min 58.692s dev-disk-by\x2ddiskseq-4.device
2min 58.692s dev-disk-by\x2dpath-pci\x2d0000:00:1f.2\x2data\x2d2.device
2min 58.675s sys-devices-platform-serial8250-tty-ttyS11.device
2min 58.675s dev-ttyS11.device
2min 58.675s dev-ttyS10.device
2min 58.675s sys-devices-platform-serial8250-tty-ttyS10.device
2min 58.674s sys-devices-platform-serial8250-tty-ttyS1.device
2min 58.674s dev-ttyS1.device
systemd-analyze critical-chain
The time when unit became active or started is printed after the "@" character.
The time the unit took to start is printed after the "+" character.
graphical.target @2min 50.281s
└─multi-user.target @2min 50.281s
└─plymouth-quit-wait.service @5.694s +2min 44.576s
└─systemd-user-sessions.service @5.661s +21ms
└─remote-fs.target @5.649s
└─remote-fs-pre.target @5.649s
└─nfs-client.target @2.618s
└─gssproxy.service @2.591s +26ms
└─network.target @2.581s
└─wpa_supplicant.service @2min 49.191s +9ms
└─dbus-broker.service @2.148s +26ms
└─dbus.socket @2.043s
└─sysinit.target @2.040s
└─systemd-resolved.service @1.936s +104ms
└─systemd-tmpfiles-setup.service @1.870s +48ms
└─import-state.service @1.794s +34ms
└─local-fs.target @1.793s
└─boot-efi.mount @1.778s +14ms
└─boot.mount @1.446s +8ms
└─systemd-fsck@dev-disk-by\x2duuid-49e7acd7\x2d0f9e\x2d4eea\x2d905a\x2d224a26ff22e9.service @1.395s +28ms
└─local-fs-pre.target @1.391s
└─lvm2-monitor.service @723ms +666ms
└─dm-event.socket @704ms
└─system.slice
└─-.slice
我没有主意，希望有人能提供帮助。我将不胜感激！