Closed eHerbaciarz closed 10 months ago
We have an identical setup - WIN10 amd SteamOS 3.5
Boot SteamOS and then go to desktop mode.
Open konsole terminal and type this command -
systemd-analyze time
It will show a breakdown of how long it takes to boot. My output is this -
5.50 - firmware
4.87 - loader
1.84 - kernel
5.95 - userspace
Add all of that and you get your boot time. Mine is 18.06seconds.
With that said i find the boot times inconsistent. Even without Clover sometimes SteamOS takes a while to load getting stuck on a blank screen. I don't think this is caused by the Clover script itself. The Clover script that runs automatically at startup only takes milliseconds to run.
I have a similar issue on Steam OS 3.5, Bios 118.
Steps to reproduce for me:
Fix:
I'm not sure what's causing it, if I was using Steam OS before the shutdown and use Steam OS again, the long boot doesn't happen.
Maybe important:
Where can I find the sanity check systemd script? I'll try to code review it and comment here if I find something that could possibly be related
@hartojodylan Please check my previous reply and use systemd-analyze time and compare the output.
The systemd script is located here -
/etc/systemd/system/clover-bootmanager.sh
havent heard back so i'll be closing this issue.
I use Clover for dual-boot (SteamOS 3.5 and Windows 10) - https://github.com/ryanrudolfoba/SteamDeck-Clover-dualboot (release 15.10.2023) And I noticed that SteamOS loads much slower due to Clover - ~30 seconds to even over one minute. Windows 10 starts immediately. If I boot SteamOS directly from UEFI (Vol - + power button), the system starts almost immediately.
What could be causing the long startup time?