How do I troubleshoot hardware problems in a Linux system? (1)

in the Linux system, the troubleshooting of hardware problems may be the most difficult task in the field of Computer Management, even if the experienced users sometimes encounter their own situation, this article share some practical skills and processing methods, hope to help readers understand, identify and finally solve the hardware problems. AD:2014WOT Global Software Technology Summit Beijing Station course video release "51CTO selected translation" This tutorial is very tangled in the birth process. I've been thinking about writing this for a long time, the main reason is that troubleshooting hardware-related issues can be the toughest task in Computer Management. Even the most experienced users sometimes encounter their own situation, and in trying to solve the subtle, erratic, elusive, or even uncertain hardware and software conflict difficulties encountered nails. Want to find answers on the web? What we find is likely to be tens of thousands of irrelevant themes, eventually wandering around the empty forums and running out of life. Personally, however, I think I am a conceited geek with considerable confidence in technical problems and writing skills. Today I intend to share with you some practical skills and methods to help readers understand, identify and finally solve the hardware problems-Whether you're using a Linux device or any other platform. This tutorial does not guarantee 100%effective, some of these methods may not be easy to grasp, but it can still play some role. Please follow me to explore the mysteries of hardware failure. Hardware failure types before you begin to diagnose hardware problems, it is important that we first need to adjust the expectations to fully understand the types of hardware failures that you may encounter in your work. Finally, we must also master the actual manifestation of hardware failure. Hardware does not work the most common failure occurs when a part of the electronic device is damaged, but the exception happens. If everyone's power supply is out of the question, the equipment of course no way to start, the truth is very simple. In addition, graphics cards, sound cards, and even memory sticks can be hung up at critical moments, and bring a variety of strange performances. In this case, the system may still be able to self-test through the BIOS and into the operating system, and even allow users to a certain degree of normal operation. In some cases, we may feel the device malfunction, for example, the screen resolution suddenly becomes very low--this must be because the graphics card driver does not work, or listen to music without sound, that is the problem of the sound card. In some cases, the operating system may also eject the error message directly. The instability of the hardware instability is one of the most difficult and not easy to diagnose fault types we face. If there is only one part of your hardware that is damaged, the overall device may still work, and only occasionally the problem occurs in certain situations. This often makes the user feel puzzled, unable to connect the abnormal condition with the corresponding equipment, thus draw the correct conclusion. In addition, even if the same fault may have a variety of manifestations, they seem to be unrelated to each other, but enough to torture the user. Some types of errors do not even affect the normal functionality of the device, but they may secretly cause data corruption or overall device performance degradation. This kind of problem is quite sinister, because we are often used to blaming it for operating system corruption or software conflicts. For example, if there are a few corrupted units in our memory stick that make a segment error when accessing and using these storage spaces, what are you going to do? Again, we may be able to crash the system kernel with some software hooked, but its real source may be memory failure or bus error, you think of it? Another good example is the wireless that I experienced three years ago on my old T61 device ./notebook problems. The audiophile-grade desktops I used to play games also encountered faults caused by ground wires. Firmware/driver failure driver failure often behaves like a hardware problem, but the difference is that the attack condition is stable and not as good as hardware. Typically, software problems result in a more consistent and reproducible situation. In some cases, our drivers are not even able to communicate with the hardware, while in other cases, a driver with bugs can cause the device to function unexpectedly. Sometimes such problems can also be translated into global function deletions, such as kernel crashes, black screens, white screen, and other strange faults. Other considerations You must also be aware that some systems may lock the BIOS to prevent us from using certain hardware components or features, or to disable them for some purpose. In a later article we will discuss the BIOS topic further. Finally, you may inadvertently work with hardware components that are designed to conflict. Some vendors may produce hardware that is specific to a particular operating system, so we are not able to get driver support from any other system platform from the official. However, some hardware can use the same public version of the driver as other products, such as Lexmark printers, to perfectly accept the PCL driver. 

How do I troubleshoot hardware problems in a Linux system? (1)