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

How do I troubleshoot hardware problems in a Linux system? (2) 2013-03-27 10:32 51cto.com of nuclear coke translationfont Size:T | T

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

Hardware analysis

As there are hundreds of solutions to tracking hardware problems and trying to solve them, it is extremely normal to be confused in practice or overwhelmed by the countless cases of the Internet-the greatest sorrow in life. My advice to you is to minimize miscalculation and interference, despite the systematic approach to every hardware failure.

Well, let's just assume that we've already met a hardware failure. In reality some of the faults are real, some are just our miscalculation or occasional phenomena, but here we are only discussing the real problems for the time being.

Backup and update

The first and most critical step is to make a backup of your data. Once the equipment starts to disrupt, our bottom line is to never lose any valuable information, a step that is indispensable in the repair plan.

The second step is a full update of the device. In the Linux domain, this means downloading all available system updates, which may contain firmware and driver fixes that are critical to resolving hardware issues. Even without these targeted content, the new kernel is often better able to support hardware on the device. For example, the SSD trim command can only take effect in the 2.6.33 kernel. Similarly, Sandy Bridge only supports the latest releases of several systems. Nvidia's 290. The XX driver may contain additional features or important repair codes that were not available in previous versions.

Start log

If there are hardware in our equipment that is completely damaged, partially damaged, or has serious problems, the first thing to think about is to see if the startup process is recording and feedback. To do this, you need to query the startup log in the system. In most cases, the Linux system's boot log is stored under the/var/log path, and the file name is usually Boot.log or boot.msg. As shown in the following:

Do not see the error message on the attention!

From there, you can see a few red failure messages and yellow warning messages. Put them aside for the time being, they may or may not be related to a malfunction, in fact we do not interfere with the normal inspection process due to interference factors. Again, what you have to do now is to identify some kind of hardware problem, and for the moment, we should focus only on what's exactly relevant to the hardware of the problem. If it doesn't matter, just skip it. In fact, in many cases we can predict the scope of the problem and go directly to the corresponding section to check it.

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