Hello !
I have some issues with my Acer Swift Go 14 (model 72)
First time using Fedora, seems really great ! 
First one is the having no sound, but was solved using [BUG] Acer Swift Go 14 - No sound card detected - "No SoundWire machine driver found" · Issue #4923 · thesofproject/linux · GitHub (how to ask for a new alsa-conf version is a side question for this topic)
But the second one is related to boot times, nearly 2 minutes. I struggle reading and understanding all the boot time analysis.
Note that I added a second NVME SSD to my laptop on which Fedora is installed.
Note that sometimes, not always, udisk service does not start…
Here is what I tried
vincent@fedora:~$ systemd-analyze blame
1min 1.819s sys-module-fuse.device
1min 1.779s dev-tpm0.device
1min 1.779s sys-devices-LNXSYSTM:00-LNXSYBUS:00-INTC7001:00-tpm-tpm0.device
1min 1.771s dev-ttyS3.device
1min 1.771s sys-devices-platform-serial8250-serial8250:0-serial8250:0.3-tty-tty>
1min 1.770s dev-ttyS2.device
1min 1.770s sys-devices-platform-serial8250-serial8250:0-serial8250:0.2-tty-tty>
1min 1.767s sys-devices-platform-serial8250-serial8250:0-serial8250:0.0-tty-tty>
1min 1.767s dev-ttyS0.device
1min 1.766s sys-devices-platform-serial8250-serial8250:0-serial8250:0.1-tty-tty>
1min 1.766s dev-ttyS1.device
1min 1.758s dev-tpmrm0.device
1min 1.758s sys-devices-LNXSYSTM:00-LNXSYBUS:00-INTC7001:00-tpmrm-tpmrm0.device
1min 1.750s sys-module-configfs.device
38.237s fwupd.service
6.368s NetworkManager-wait-online.service
1.916s plymouth-quit-wait.service
1.134s dev-disk-by\x2did-nvme\x2dHFS512GEJ9X110N_5YC9N032511709O1J_1\x2dpa>
1.134s dev-disk-by\x2dpath-pci\x2d0000:00:0e.0\x2dpci\x2d10000:e1:00.0\x2d>
1.134s dev-nvme1n1p3.device
vincent@fedora:~$ 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 @1min 5.262s
└─multi-user.target @11.784s
└─plymouth-quit-wait.service @9.866s +1.916s
└─systemd-user-sessions.service @9.848s +16ms
└─remote-fs.target @9.846s
└─remote-fs-pre.target @3.524s
└─nfs-client.target @3.524s
└─gssproxy.service @3.504s +20ms
└─network.target @3.501s
└─wpa_supplicant.service @3.478s +22ms
└─basic.target @2.535s
└─dbus-broker.service @2.503s +30ms
└─dbus.socket @2.496s
└─sysinit.target @2.493s
└─systemd-resolved.service @1.563s +929ms
└─run-credentials-systemd\x2dresolved.service.mount>
Some things I saw in dmesg
[ 2.408583] fbcon: Deferring console take-over
[ 2.408584] i915 0000:00:02.0: [drm] fb0: i915drmfb frame buffer device
[ 2.525972] i915 0000:00:02.0: [drm] GT1: Loaded GSC firmware i915/mtl_gsc_1.bin (cv1.0, r102.0.10.1878, svn 1)
[ 2.546019] i915 0000:00:02.0: [drm] GT1: HuC: authenticated for all workloads
[ 9.840145] fbcon: Taking over console
[ 9.857618] Console: switching to colour frame buffer device 360x112
[ 22.546610] i915 0000:00:02.0: [drm] *ERROR* GT1: GSC proxy component didn't bind within the expected timeout
[ 22.546624] i915 0000:00:02.0: [drm] *ERROR* GT1: GSC proxy handler failed to init
[ 62.533401] nvme nvme0: I/O tag 20 (2014) QID 0 timeout, completion polled
[ 62.538036] nvme nvme0: 8/0/0 default/read/poll queues
[ 62.541366] nvme0n1: p1 p2 p3
[ 62.631692] BTRFS: device label fedora devid 1 transid 141 /dev/nvme0n1p3 (259:8) scanned by mount (687)
[ 62.684385] BTRFS info (device nvme0n1p3): first mount of filesystem 0a14acb6-d4fc-443d-be2f-bc943781a1a4
[ 62.684410] BTRFS info (device nvme0n1p3): using crc32c (crc32c-intel) checksum algorithm
[ 62.684417] BTRFS info (device nvme0n1p3): using free-space-tree
[ 62.819676] systemd-journald[403]: Received SIGTERM from PID 1 (systemd).
[ 62.859478] audit: type=1404 audit(1728826326.311:5): enforcing=1 old_enforcing=0 auid=4294967295 ses=4294967295 enabled=1 old-enabled=1 lsm=selinux res=1
First is the ‘ERROR GT1: GSC proxy handler failed to init’ which seems to take 20 seconds and then nvme timeout on which Fedora is installed.
Can someone help troubleshooting ? Thanks
