Slow boot yesterday and today

Loving bazzite so far! Please be patient as I'm very much a novice (and currently posting this before heading in to work, so sorry i i dont reply for a few hours). I updated my bazzite night before last (on the 13th of oct here in aus) using "ujust update" in terminal. Then when i booted it up yesterday it took much longer than normal. I was able to press the power button, feed the cat, empty her litter tray and still have about 30s to spare before reaching the login screen. Then this morning it also took a long while too. Anyone have the same issue, or know whats happening? I saw some other posts from a while back that it was services-related for those people, but i dont know how to diagnose what service it could be. If that is recommended please walk me through the process of checking that stuff. - Im on a desktop PC. - Using the KDE version of bazzite. - Processor: Intel core ultra 7... 265kf... i think? (Ill have to check tonight at home) - RAM: 32GB of ram (kingston fury beast ddr5) - GPU: nvidia 5080 - Mobo: ASUS TUF PRO-WIFI (whichever one is compatible with the ultra 7 processor, cant remember the number) Let me know if there is other info you need. It is worth noting that once I'm actually in there are no issues, its just the boot time.
Solution:
I ended up figuring it out, I have a "Deepcool Morpheus" PC case and it comes with a little CPU/GPU temperature monitor. That little device was all of a sudden causing a huge increase in time on the "initrd" stage of boot when the attempt was made to identify it. unplugging it from the motherboard and plugging it back in seems to have fixed it...
Jump to solution
1 Reply
Solution
FozzieOscar
FozzieOscar2mo ago
I ended up figuring it out, I have a "Deepcool Morpheus" PC case and it comes with a little CPU/GPU temperature monitor. That little device was all of a sudden causing a huge increase in time on the "initrd" stage of boot when the attempt was made to identify it. unplugging it from the motherboard and plugging it back in seems to have fixed it

Did you find this page helpful?