I have never seen/heard of linux breaking any hardware, so I'm very curious about your experience especially since there are protections that prevent breaking hardware like turning off the machine if a component gets to hot, etc... In the worst case, there is no driver available for some specific hardware and it simply doesn't work, that's it.OsDictator wrote: ↑Mon Feb 05, 2018 10:49 amHi.
How do I approach testing Linux on hardware, without killing any hardware-components?
What risks are we to expect?
In rambling text:
I have been running Linux for several years, and would always risk my own system to get it running, cannot live inside windows anymore.
When friends and relatives comes to me for computer support, I now say I am happy to help, but I only do Linux. Their choice! Since they have been relying on me forever, they usually go the Linux route too, or at least tries it out. But on occasions, I have experienced Linux killing graphic-cards or doing very scary stuff to make me back away(latest Solus Os). In the light of the recent incident where ubuntu bricked some uefi's, I would very much like to see prominent people, like Ikey, guide us to the proper approach in testing the hardware and its Linux capabilities.
I am looking for a variant of Linux to master, because my approach have been very lazy since I learned that in contrast to wasting a day or two on installing Windoze, Linux is up and running and fully updated in less than an hour. So I simply to a fresh install when needed. But that is not feasible when you have several people relying on you, over great distances. Through my Linux years I have been running Fedora, various Ubuntu variants, Arch, Manjaro, Suse and probably a lot of other weird exciting stuff, but I am now looking to get better in depth knowledge on how to keep systems up and running so distro-hopping might not be the best approach anymore.
I am about to migrate my mothers 7 year old laptop to Linux, but this very laptop was the first, and brand new, computer on which I experienced Linux killing the graphics. Back then, it was Linux-Mint that left me with a vertical bar of dead pixels. It was handled with a DOA.
I have only been testing Solus, not running it per se. I have been running KDE Neon for more than a year, and it has been the most reliable Linux experience I have ever had, but not without its quirks, so i'm curious to see after all thees years, if it is a rolling release that will take it the rest of the way.
Is this the same problem that affected 17.10? I was under the impression that it was a specific kernel version that caused the issues with bricking some UEFI laptops.kyrios wrote: ↑Mon Feb 05, 2018 1:19 pm
Regarding the recent incident ubuntu had it was caused by the intel microcode and [url=http://www.zdnet.com/article/windo ... ctre-fix/] windows did suffer from the same problem ...
You're right, it was another problem, my mistake!
Or just google linux and the computer models you're planning to buy to see the reviews/test/feedback or comments from other people.geoffrey.A wrote: ↑Mon Feb 05, 2018 9:18 pmWell, I learned a long time ago if one wants a truly smooth, troublefree environment for running (or testing) Linux, do one of these things:
* Buy a PC with Linux already installed . . . now there are at least 50 vendors worldwide to choose from. No surprises, the testing and engineering has already been done by the "Systems Integrator" . . .
* Buy a PC that is "All Intel" . . . . cpu, graphics and wireless
* If want to build or buy off the shelf . . . do your homework FIRST. A reliable brand such as Dell that complies with UEFI standards is always a good bet.