-
This is prob more of a Debian vs openSUSE question but since the creator of both Spiral and Gecko has expertise in both distros, thought I'd see if I can get some insight here. I have installs of both Tumbleweed and Spiral (builder w/ sway) on my laptop. They are both fantastic and to be honest, I'm really impressed with Spiral and likely will be staying here. There's a nice calmness that comes with Debian which I can appreciate. The one area Tumbleweed seems to excel in however is boot times, reboot times, shut down times etc Everything is quick in this department. With Debian so far, things have been much slower to startup, much slower to reboot, and much slower to shutdown. I guess I'm wondering a) if anyone who has run both distros has noticed the same, and b) if any config options can be done on Debian to bring it up to speed with openSUSE? And if Sam sees or responds to this, just want to say thanks for all the great work on both projects! |
Beta Was this translation helpful? Give feedback.
Replies: 3 comments 4 replies
-
On my system (SpiralLinux with Budgie DM) I have boot- and shutdown times within a few seconds. |
Beta Was this translation helpful? Give feedback.
-
Hi there, thanks to @chaibronz for the kind words. I haven't really noticed any difference between the boot time of the two systems. Pretty much all distros with systemd these days take about the same time to boot, which is usually not notably fast or slow. There's probably some specific service that is hanging during startup on your SpiralLinux installation. First try to hit If nothing stands out there then trying running |
Beta Was this translation helpful? Give feedback.
-
My laptop shuts down straight away. I don't have to hold down the power button. |
Beta Was this translation helpful? Give feedback.
Solved!
You got me looking in the right direction. BIOS was up-to-date but there was a setting I had to change.
For any future dummies like myself (Lenovo Thinkpad w/ Intel):
Enter BIOS --> Security --> Security Chip --> Security Chip Selection --> Discrete TPM
I must have changed it to "Intel PTT" at some point, or it's just never come up as an issue before.
Either way, we're shutting down properly now.