The following describes my first Linux installation experience and how to handle it. I hope it will help you. If you do not like it, you can skip it. The following describes the basic knowledge of Hardware Management in Linux.
Analyze What devices are available on this machine. Check whether the devices are applicable to our applications;
. 0 VGA compatible controller: Intel Corporation 82852/855 GM Integrated Graphics Device (rev 02)
. 1 Display controller: Intel Corporation 82852/855 GM Integrated Graphics Device (rev 02) Note: This is a Display card;
USB Controller indicates the USB interface. We can see three of these devices. My laptop has exactly three USB interfaces;
Multimedia audio controller: Intel Corporation 82801DB/DBL/DBM (ICH4/ICH4-L/ICH4-M) ac'97 Audio Controller (rev 03) Note: This is a sound card;
Modem: Intel Corporation 82801DB/DBL/DBM (ICH4/ICH4-L/ICH4-M) ac'97 Modem Controller (rev 03) Note: This is a cat;
Ethernet controller: Realtek semiconduco., Ltd. RTL-8139/8139C/8139C + (rev 10) Note: This is the NIC, the chip is 8139;
FireWire (IEEE 1394): Texas Instruments OHCI Compliant IEEE 1394 Host Controller note: this is information about the 1394 Interface. In fact, my notebook also has this interface;
So what is the use of this information? If some devices on the machine do not support this function well, we can search for this information on Google. For example, I feel that my sound card is faulty, you can search for the solution based on the sound card information. Based on the information, you can go to the hardware chipset official website to find the answer or driver;
If you want to know more about the hardware, you can use lspci-v to view it;
[Root @ localhost beinan] # lspci-v
For example, we can use lspci-v to check the irq interruption of the hardware. For example, if the NIC is not easy to use, is there a conflict with the irq? If you do not know how to solve the hardware driver problem, you need to paste the entire segment of the lspci-v hardware information, which is the only solution to the problem; therefore, it is extremely important to learn to ask questions;
Some system releases and lsusb tools. Please try them yourself;
2. Storage Device viewing and operation tools;
We can see that the main tools for storage devices are fdisk, parted, and cfdisk. fdisk is the most commonly used and convenient tool. parted should be a supplement. This tool is not very mature at present;
See:
Introduction to Linux commands for viewing disk partitions, file systems, usage, and related tools
How to Use fdisk for instance explanation
3. view the corresponding files in the/proc directory to obtain some hardware information;
We will notice this line when viewing/etc/fstab;
/Dev/proc defaults 0 0
Proc looks like a file system. In fact, it is not a real file system. It is "proc-process information pseudo-filesystem ", the process information disguising the file system;
"The proc filesystem is a pseudo-filesystem which is used as an interface to kernel data
Structures. It is commonly mounted at/proc. Most of it is read-only, but some files allow
Kernel variables to be changed ."
I will try to translate it and then understand it based on/proc. As an interface for kernel data structure, the proc file system refers to some kernel information, such as hardware information, including CPU, Nic, display card, memory, file system, and SCSI device ....) in the proc file system, the proc is written to the/proc directory by the mont; in the/proc directory, most of the big data files are read-only, but some data changes according to kernel changes; the data in the/proc directory is subject to frequent changes. Each process in the system has a PID, which can be found in/proc; we can also view the process through ps-aux | more;
We can use the cat command to read files in the/proc directory, such as cpu information;
[Root @ localhost beinan] # cat/proc/cpuinfo
You need to check the details. It is also necessary to understand/proc;
Click basic knowledge of Hardware Management in Linux.