Boot time
So I just reinstalled Bazzite to change from Gnome to KDE. With gnome it took a few seconds to boot. KDE is taking like a minute. What have I done wrong? Or is this normal?
Thanks
Solution:Jump to solution
Fixed! KDE, boot time like 5 seconds.
After telling chatgpt everything and going back and forward for a while, it came up with these as the most liekly issues.
`GRUB or EFI files might be on a slightly different location or partition, and the motherboard is pausing before it finds the bootloader.
...
27 Replies
Send
systemd-analyze blameLike this?
1min 3.766s sys-module-fuse.device
1min 3.679s sys-devices-LNXSYSTM:00-LNXSYBUS:00-MSFT0101:00-tpm-tpm0.device
1min 3.679s dev-tpm0.device
1min 3.643s dev-ttyS1.device
1min 3.643s sys-devices-platform-serial8250-serial8250:0-serial8250:0.1-tty-ttyS1.device
1min 3.642s sys-devices-platform-serial8250-serial8250:0-serial8250:0.2-tty-ttyS2.device
1min 3.642s dev-ttyS2.device
1min 3.642s sys-devices-LNXSYSTM:00-LNXSYBUS:00-MSFT0101:00-tpmrm-tpmrm0.device
1min 3.642s dev-tpmrm0.device
1min 3.639s sys-devices-pnp0-00:04-00:04:0-00:04:0.0-tty-ttyS0.device
1min 3.639s dev-ttyS0.device
1min 3.638s sys-devices-platform-serial8250-serial8250:0-serial8250:0.3-tty-ttyS3.device
1min 3.638s dev-ttyS3.device
1min 3.631s dev-disk-by\x2did-ata\x2dST1000DM010\x2d2EP102_W9AGD4PF.device
1min 3.631s dev-disk-by\x2dpath-pci\x2d0000:0f:00.0\x2data\x2d2.0.device
1min 3.631s dev-sda.device
1min 3.631s dev-disk-by\x2ddiskseq-1.device
1min 3.631s dev-disk-by\x2did-wwn\x2d0x5000c500cc1fcfe6.device
1min 3.631s dev-disk-by\x2dpath-pci\x2d0000:0f:00.0\x2data\x2d2.device
1min 3.631s sys-devices-pci0000:00-0000:00:02.1-0000:03:00.0-0000:04:0d.0-0000:0f:00.0-ata2-host1-target1:0:0->
1min 3.611s dev-disk-by\x2dpath-pci\x2d0000:0f:00.0\x2data\x2d2.0\x2dpart-by\x2dpartnum-1.device
1min 3.611s dev-disk-by\x2ddiskseq-1\x2dpart1.device
1min 3.611s dev-disk-by\x2dpath-pci\x2d0000:0f:00.0\x2data\x2d2.0\x2dpart1.device
Yes but I don't see any outlier🤔
Run
systemd-analyze plot > boot.svg . This will create a boot.svg file in the directory you run the command. You can upload here and also take a look yourself
dracut-initqueue.service (1min 2.048s)this service is taking a long time to finish. Did you add or remove any drives recently?
Nothing like that. All I did was make a USB boot drive for KDE version and installed it exactly the same as I did Gnome a few days ago
I'm getting similar times but it's definitely a recent thing, used to be like 35 seconds before
Should I just try another reinstall maybe?
I noticed after rebooting that the automounting was still running when I did systemctl list-jobs, since I couldn't run systemd-analyze lol
instead of reinstall you can try a downgrade, if it's recent like @Reactive said a downgrade can solve the issue. type
brh and follow the prompts, choose a ~7 days old imageBut it's a fresh install from like an hour ago. Don't think I have anything to downgrade to
they meant that it could be related to the latest stable release, perhaps an older release doesn't have this issue
IF that is the cause
I'm not too bothered by it currently, I just boot it up once per day
I gave up and went back to gnome, but it's happening with that now as well 🙁
systemd-analyze blame
will tell you what services are takng the most timeuploaded that above
But I have no idea what anything in that means
One thing I have noticed, when I restart before it loads the bios it show this screen with an underscore for 10 seconds first. Never did that before
Solution
Fixed! KDE, boot time like 5 seconds.
After telling chatgpt everything and going back and forward for a while, it came up with these as the most liekly issues.
GRUB or EFI files might be on a slightly different location or partition, and the motherboard is pausing before it finds the bootloader.
NVRAM boot entries might be pointing to a “wrong” or “extra” EFI file first, causing a delay.
Less likely, but possible: partition alignment or filesystem differences in the EFI system partition that the firmware doesn’t like.
I had the idea to do a full clean of the ssd from my windows install, and it worked. Reinstalling and wiping everything with the bazzite installer was missing things....
don't use llms to debug your computer
meh, it worked. Wasn't able to get the help needed here.
so its just another reinstall, but wiped with an external tool
in the end, yep
wiped with diskpart
Was a simple fix, but took a long time to find it
might be an anaconda moment but if fixable with a fresh install its probably not a big deal
plus it is going to get replaced soon in f43
What is?
anaconda
the current installer
ohh
Didn't get the anaconda reference but just went with it xD
Yeah, but not just a fresh install ontop of the old one. Wiped in windows first. But in anaconda is going bye bye soon, doesn't really matter 🙂