Linux
Welcome to c/linux!
Welcome to our thriving Linux community! Whether you're a seasoned Linux enthusiast or just starting your journey, we're excited to have you here. Explore, learn, and collaborate with like-minded individuals who share a passion for open-source software and the endless possibilities it offers. Together, let's dive into the world of Linux and embrace the power of freedom, customization, and innovation. Enjoy your stay and feel free to join the vibrant discussions that await you!
Rules:
-
Stay on topic: Posts and discussions should be related to Linux, open source software, and related technologies.
-
Be respectful: Treat fellow community members with respect and courtesy.
-
Quality over quantity: Share informative and thought-provoking content.
-
No spam or self-promotion: Avoid excessive self-promotion or spamming.
-
No NSFW adult content
-
Follow general lemmy guidelines.
view the rest of the comments
On my last computer I found that the boot process was looking for things that weren't there but that the motherboard had rudimentary functionality for like a floppy drive. It didn't even have a connector for one.
For whatever reason, that caused a 10-30 second delay while the kernel tried to determine if there was a floppy drive connected. Pretty sure I had everything disabled via the BIOS but apparently it wasn't disabled enough and the kernel could still see it.
That required throwing something into the system config, probably somewhere in /etc/modprobe.d, to blacklist that particular kernel module.
There was another problematic module as well; I can't remember what that was, but I'm pretty sure it was the same fix. Got the boot time to login screen down to less than 10 seconds.
But all that said, even on this computer where the boot time is pretty quick, I usually put the computer into suspend mode to keep times down.