I'm freaking done trying to get Linux on my machine. I've tried every distro with many different versions of the kernel and I always run into the same problem on my desktop.

The computer super stutters for 2 seconds ish than freezes.

I've spent DAYS looking into this issue trying to find something. The worst part is that it can happen 5 minutes when I boot or 5 hours. At first I thought it was Compton. Then I thought I installed arch wrong. Maybe an update to the BIOS? How about downloading updated microcode? Maybe this obscure bug with AMD processors and setting power idle to typical? Nothing. I'm now behind on my school work because of the massive amount of time ive spent getting this fixed. It works just fine on my laptop, but it doesn't work on the machine I built to code with. I'm done. Give me Force Lightning, a red lightsaber, and call me a Sith baby because I'm joining the dark side. Here I come Windows.

For those who are wondering my setup:
Ryzen 7 1700
Rx 480
Asus x-370 prime
16 gb Corsair RAM

And no, Windows has never had this bug.

So,
Acer has a corrupt BIOS,
Lenovo is a bug fest,
HP supposedly also sucks.

So which brand of laptop does not suck?

Soo insyde BIOS got a big bug via 17.10 ubuntu iso
- Settings not getting saved in bios
- USB booting is a no-go.
- suspend never wakes up without battery removal
Infected systems mostly include acer, LENoVO and hp mainly

I am surprised it took them this long to notice the bug.

Lately programs have been crashing a lot on my pc, I've tried different things like disabling SWAP for a sec, BIOS changes, remove firefox and use Google Chrome, try different commands, it kept happening.

Obviously along the way I started investigating what was causing these crashes, looking through bug reports and my syslog. There was no consistency, except for 1 thing: SIGENV. Everything that crashed had a segmentation fault, now I'm not an expect and I don't know what this means or how to fix it, so I went to Google to ask for answers.

Then I downloaded memtest and ran a memory test, error palooza. Then I went to Windows and ran memory check, error palooza.

This is week 3 of this high-end gaming pc which was a huge investment AND IT HAS BEEN FUCKING WITH ME BECAUSE OF BAD MEMORY HOW THE FUCK DOES THIS HAPPEN I ALMOST STARTED TO DOUBT UBUNTU BUT IT WAS A FUCKING FAULT IN BRAND NEW MEMORY MODULES WHAT THE FUCK.

Obviously I'm pissed off. Today I'm gonna call the store that assembled it to voice my complaints.

Thank you for listening to my TedTalk.

Is that me or Lenovo cannot figure out the bios issue I am having with my ideapad-100. The Linux kernel says that the bios has a bug in it and then Windows can't update because the bios has a bug, the bios updater tells me the bios is perfectly fine. This is weird because the laptop is unstable whatever the Os and yeah it did that since I bought it and sent it to be repaired and still the issues goes on

Windows 11 is here. And there is a bug that prevents it from being installed 🐞

I got "incompatible" error so I downloaded MS compat. checker and it says: need TPM

I go to BIOS and enable TPM. The tool now says YES, compatible. But the Windows update panel still says NO, not compatible.

Bottom line, Microsoft does NOT want people to install Windows 11. If they did, then they would not have silly bugs, such as this one. All they had to do is to clear the compat. flag cache after restart

Piggy backing off an earlier rant about Linux. Let's talk about time wasted fixing Linux.

One time for me was I couldn't get Ubuntu to boot. Whenever it booted through UEFI it would go straight to the EFI bash like command line boot screen, not allowing me to access Ubuntu.

I tried for almost a full day to fix it, Googling solutions, resetting my BIOS and fixing Boot using a Ubuntu Live USB.

In the end I found it was an issue with setting my filesystem as XFS. I reinstalled using EXT4 and it booted right up. Must've been some sort of bug. Strange because XFS boot worked with Fedora. A day wasted trying to set up Ubuntu.

spent a few days trying to track down the cause of a thermal shutdown in my workstation. intel 4790k with no overclock would spike to 95C on one core (core1) whenever maxing out all 8 threads, be it real work, mprime, anything with 100% cpu being used. I quadrupled my RAM from 8gb to 32, because its cheap and id like to have all data in memory sometimes, not because I thought that was the problem. I reseated my watercooling block. I checked out the PSU. I unplugged all unnecessary peripherals, drives, etc. It turned out to be a bug in Gigabyte MOBO BIOS (causing temps to be read incorrectly i think, still not exactly sure...) updated from version 5 to 10 and poof now temps are back in the high 50's at full load. it only took 2 days to figure out and i think i learned something