this post was submitted on 28 Jan 2024
135 points (98.6% liked)
Asklemmy
43947 readers
638 users here now
A loosely moderated place to ask open-ended questions
If your post meets the following criteria, it's welcome here!
- Open-ended question
- Not offensive: at this point, we do not have the bandwidth to moderate overtly political discussions. Assume best intent and be excellent to each other.
- Not regarding using or support for Lemmy: context, see the list of support communities and tools for finding communities below
- Not ad nauseam inducing: please make sure it is a question that would be new to most members
- An actual topic of discussion
Looking for support?
Looking for a community?
- Lemmyverse: community search
- sub.rehab: maps old subreddits to fediverse options, marks official as such
- !lemmy411@lemmy.ca: a community for finding communities
~Icon~ ~by~ ~@Double_A@discuss.tchncs.de~
founded 5 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
Check inside your BIOS if you can add a delay to the startup or disable skips for a faster boot. Sounds like the drive need some time to wake up.
Naaah it’s fine, it’s either the CPU not making contact or I scratched the MB with a SATA cable. The boot drive is m.2 so it’s not the cable. Cos it’s started happening after I changed the CPU, and while doing that a SATA cable got stuck behind the MB and I pull it out with force instead of unscrewing the MB :) I just can’t be bothered figure it out anymore lol