How do I troubleshoot hardware problems in a Linux system? (4) 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
LSPCI command
There is also an easier way to scan all the hardware components that are connected and their corresponding drivers. The system command LSPCI can list all devices that access the PCI bus, but even legacy hardware will be displayed.
The question now is, where did LSPCI get this information? Well, if you really want to know, then we'll combine LSPCI with Strace to see. There is no doubt that LSPCI is scanning the/sys directory for access to device information, including connection ports, vendor IDs, device types, and configurations.
Finally, LSPCI will refer to the hardware vendor static list contained in the/usr/share/hwdata/pci.ids file. This list translates the Supplier ID numbers into natural language names, allowing us to directly read the results of the scan that the LSPCI outputs.
Some Linux distributions also have a graphical front end for the LSPCI command so that we can read the System information from the window as it did on the Windows platform. However, it is necessary to remind you that the command output is more convenient to query, especially when doing debugging work.
/var/log/messages
Last but not least, we can also get the answers we want by querying the system log. Again, focus on the hardware on which the problem occurs, and don't be guided by insignificant errors. As a demonstration, we insert a USB flash drive into the device and see what information the system will give us feedback. In order to query the information in real time, we need to use the tail command.
Be aware of what is listed in the system. In this example, we will see that the system correctly identifies the newly-accessed drive. But this does not mean that we can directly start to use, we must have found that the system does not automatically install the driver for it, we do not have sufficient access to the right, and so on. Even the USB flash drive itself may be faulty. However, the device has been correctly identified by the contents of the system, so we can eliminate this possibility.
How do I troubleshoot hardware problems in a Linux system? (4)