5 ms·
That explains the issues with the C2000 family. Various Linux distros crash randomly, and not just crash sometimes really just stop opening applications or stop
by frik 10y ago
That explains the issues with the C2000 family. Various Linux distros crash randomly, and not just crash sometimes really just stop opening applications or stop processing e.g. apt-get.
The BIOS is a piece of shit. It's buggy, the legacy-BIOS support is unstable, the Win7-EFI and Win8-EFI modes are not good either. I patched a Win7 DVD with Win8 files, so that I could install Win7. Now Win7 runs great and stable - but only after I installed various Intel drivers that fixed the hardware flaws.
I am seriously looking forward to the upcoming new AMD CPU - Intel dod barely anything the last five years, a 2011 highend CPU is almost as fast as Intel 2017 flagship, and costed a lot less back then, had less DRM or other shit that is broken. Intel needs a proper competitor, so a comeback of AMD on the one side, and Apple notebooks with ARM CPU are very welcome to stop Intel from siting on their quasi monopoly chair.
- yuhong 10y agoWhich motherboard?
- wang_li 10y ago>That explains the issues with the C2000 family. Various Linux distros crash randomly, and not just crash sometimes really just stop opening applications or stop processing e.g. apt-get. No it doesn't. Did you read the errata? It completely stops. There's no weirdness. It's just dead.
- AstralStorm 10y agoRandom crashes are often sign of memory corruption. Sometimes broken power supply or major interference. Not of such CPU problems.
- nowaynohow 10y agoMeh, for C2000, it can be also a sign of outdated firmware. We don't get microcode updates for SoCs in the general distribution: either your system vendor does a good job of keeping up with firmware updates, or you are screwed.