initrd slowing down boot
Hi everyone,
I installed Bazzite a couple of weeks ago on a brand new desktop computer (I have a dualboot with Windows installed on another disk, but Bazzite is my primary boot OS).
I noticed about a week ago that it was suddenly being fairly slow to boot (more than 1 minute whereas it took barely 20 seconds before).
I ran the analyze time command (you'll see the results in the first picture) .
I ran the analyze blame command as well and was able to locate where the boot takes too much time (you'll see the results in the second picture).
Has anyone had this issue ? I saw on a forum that someone updated their BIOS and it fixed the issue, but I just did it and it doesn't seem to have fixed anything.
Here is the log to the last journalctl for dracut :
Aug 25 19:13:09 bazzite systemd[1]: Starting dracut-initqueue.service - dracut initqueue hook...
Aug 25 19:14:14 bazzite systemd[1]: Finished dracut-initqueue.service - dracut initqueue hook.
Aug 25 19:14:14 bazzite systemd[1]: dracut-initqueue.service: Deactivated successfully.
Aug 25 19:14:14 bazzite systemd[1]: Stopped dracut-initqueue.service - dracut initqueue hook.
I updated Bazzite but only after this issue started, as I thought the update might solve my issue.
The only thing I noticed which occurred at the same time as my current issue, is my bluetooth receiver (integrated to my motherboard) stopped working. It had been acting weird with one of my devices as it would connect/disconnect/reconnect/redisconnect several times per second. The device is now connected through 2.4 and works fine, but according to the system, my computer doesn't have a Bluetooth receiver anymore (at least not on Bazzite).
As for some other info :
I installed Bazzite a couple of weeks ago on a brand new desktop computer (I have a dualboot with Windows installed on another disk, but Bazzite is my primary boot OS).
I noticed about a week ago that it was suddenly being fairly slow to boot (more than 1 minute whereas it took barely 20 seconds before).
I ran the analyze time command (you'll see the results in the first picture) .
I ran the analyze blame command as well and was able to locate where the boot takes too much time (you'll see the results in the second picture).
Has anyone had this issue ? I saw on a forum that someone updated their BIOS and it fixed the issue, but I just did it and it doesn't seem to have fixed anything.
Here is the log to the last journalctl for dracut :
Aug 25 19:13:09 bazzite systemd[1]: Starting dracut-initqueue.service - dracut initqueue hook...
Aug 25 19:14:14 bazzite systemd[1]: Finished dracut-initqueue.service - dracut initqueue hook.
Aug 25 19:14:14 bazzite systemd[1]: dracut-initqueue.service: Deactivated successfully.
Aug 25 19:14:14 bazzite systemd[1]: Stopped dracut-initqueue.service - dracut initqueue hook.
I updated Bazzite but only after this issue started, as I thought the update might solve my issue.
The only thing I noticed which occurred at the same time as my current issue, is my bluetooth receiver (integrated to my motherboard) stopped working. It had been acting weird with one of my devices as it would connect/disconnect/reconnect/redisconnect several times per second. The device is now connected through 2.4 and works fine, but according to the system, my computer doesn't have a Bluetooth receiver anymore (at least not on Bazzite).
As for some other info :
- I'm currently using Bazzite 42 Desktop Edition; KDE Plasma Edition 6.4.4, KDE Frameworks Version 6.17.0, Qt Version: 6.9.1; Kernel version: 6.15.9-106.bazzite.fc42.x86_64 (64-bit)
- The loading time stays the same on both the rurrent and the rollback version
- There are 2 disks, both NVMe, one used by Windows and one used by Bazzite. They are both 2TB.
- The Windows OS is not encrypted (I made sure to disable bitdefender), not sure about Bazzite although I haven't encrypted anything manually
- Fastboot is enabled
Solution
Yes ! It was my computer housing’s usb ports that weren’t working properly, once I plugged everything on the motherboard it solved my issue :) I was also having an issue with my built-in Bluetooth adapter on the motherboard, which also seemed to slow down the process and wouldn’t work but I unplugged the power cord, replugged it and now it all works perfectly again
