this post was submitted on 20 Oct 2025
443 points (97.0% liked)
Technology
76299 readers
4133 users here now
This is a most excellent place for technology news and articles.
Our Rules
- Follow the lemmy.world rules.
- Only tech related news or articles.
- Be excellent to each other!
- Mod approved content bots can post up to 10 articles per day.
- Threads asking for personal tech support may be deleted.
- Politics threads may be removed.
- No memes allowed as posts, OK to post as comments.
- Only approved bots from the list below, this includes using AI responses and summaries. To ask if your bot can be added please contact a mod.
- Check for duplicates before posting, duplicates may be removed
- Accounts 7 days and younger will have their posts automatically removed.
Approved Bots
founded 2 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
The only reason I have a windows box is for gaming, specifically sims (racing and flying)
Ever more reason to test and see if the wheel and flight stick work under Proton.
Bazzite my dude. Check it out, super easy and setup for easy dual boot so you can give it a shot without clearing windows (if shits partitioned right)
I want to use this last year of win 10 updates to slowly get onto Bazzite but I have heard horror stories of dualbooting Linux and Windows. Windows tends to overwrite the boot preferences and caps the system.i have only booted into Linux from an external drive in the past, so what is the tried and true dual boot method?
I installed endeavouros on my windows laptop.
The installer guided me through the partitioning, setting up systemd-boot, and it was all great.
I had to disable bitlocker in windows (not that bothered about) and secure boot in bios (also not that bothered about).
Ran smoothly dual booting both for about 4 months.
Then a windows update hit, and fucked the boot.
Thankfully, this is a common enough thing that there are plenty of tutorials out there.
A liveUSB of endeavouros, some tinkering, and I was back up and running.
The cause seems to be FastBoot, where windows keeps the boot partition mounted. What I think happens is that bios tries to read the boot partition, which is configured/loaded for windows (because it never cleaned up after itself due to FastBoot being on) and boots into windows.
Since turning off FastBoot, I haven't had any issues in the past 8 months.