How to check hardware information under Linux?
During the development process of linux, we sometimes need to know the current hardware information, such as: cpu core? Usage? Memory size and usage? Is the usb device recognized? etc. The following are some commonly used hardware check commands.

lshw
lshw This command is a relatively general tool that can list the hardware information of the machine in detail. But this command is not available in all distributions. For example, Fedora does not have it by default and you need to install it yourself.
lshw can extract hardware information from each /proc file, such as: CPU, memory, USB controller, hard disk, etc. Without options, the information listed will be very long. With the -short
option, only summary information will be listed.
[alvin@VM_0_16_centos ~]$ sudo lshw -short #篇幅关系,以下结果有删减 H/W path Device Class Description ========================================================== system Bochs /0 bus Motherboard /0/0 memory 96KiB BIOS /0/401 processor Intel(R) Xeon(R) CPU E5-26xx v4 /0/1000 memory 2GiB System Memory /0/1000/0 memory 2GiB DIMM RAM /0/100 bridge 440FX - 82441FX PMC [Natoma] /0/100/1 bridge 82371SB PIIX3 ISA [Natoma/Triton II] /0/100/1.1/0.1.0 /dev/cdrom disk QEMU DVD-ROM /0/100/1.2/1 usb1 bus UHCI Host Controller /0/100/1.3 bridge 82371AB/EB/MB PIIX4 ACPI /0/100/4/0/1 /dev/vda1 volume 49GiB EXT3 volume /0/100/5 generic Virtio memory balloon /0/100/5/0 generic Virtual I/O device /0/1 system PnP device PNP0b00 /0/2 input PnP device PNP0303
lscpu
lscpu can list the CPU related information of this machine. This command does not have any options or parameters.
[alvin@VM_0_16_centos ~]$ lscpu Architecture: x86_64 CPU op-mode(s): 32-bit, 64-bit Byte Order: Little Endian CPU(s): 1 On-line CPU(s) list: 0 Thread(s) per core: 1 Core(s) per socket: 1 Socket(s): 1 NUMA node(s): 1 Vendor ID: GenuineIntel CPU family: 6 Model: 79 Model name: Intel(R) Xeon(R) CPU E5-26xx v4 Stepping: 1 CPU MHz: 2399.988 BogoMIPS: 4799.97 Hypervisor vendor: KVM Virtualization type: full L1d cache: 32K L1i cache: 32K L2 cache: 4096K NUMA node0 CPU(s): 0
lsusb
lsusb Lists the information of all USB devices connected to this machine. By default, only summary information is listed. Use the -v
option to list detailed information for each USB port.
[alvin@VM_0_16_centos ~]$ lsusb Bus 001 Device 003: ID 0424:ec00 Standard Microsystems Corp. SMSC9512/9514 Fast Ethernet Adapter Bus 001 Device 002: ID 0424:9514 Standard Microsystems Corp. SMC9514 Hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
lsscsi
lsscsi can list SCSI/SATA device information such as hard disk/optical drive.
[alvin@VM_0_16_centos ~]$ lsscsi [0:0:1:0] cd/dvd QEMU QEMU DVD-ROM 1.2. /dev/sr0
lspci
lspci lists all PCI buses, and details of all devices connected to the PCI bus, such as VGA adapters, graphics cards, network adapters, USB ports, SATA controllers, etc.
[alvin@VM_0_16_centos ~]$ lspci 00:00.0 Host bridge: Intel Corporation 440FX - 82441FX PMC [Natoma] (rev 02) 00:01.0 ISA bridge: Intel Corporation 82371SB PIIX3 ISA [Natoma/Triton II] 00:01.1 IDE interface: Intel Corporation 82371SB PIIX3 IDE [Natoma/Triton II] 00:01.2 USB controller: Intel Corporation 82371SB PIIX3 USB [Natoma/Triton II] (rev 01) 00:01.3 Bridge: Intel Corporation 82371AB/EB/MB PIIX4 ACPI (rev 03) 00:02.0 VGA compatible controller: Cirrus Logic GD 5446 00:03.0 Ethernet controller: Red Hat, Inc Virtio network device 00:04.0 SCSI storage controller: Red Hat, Inc Virtio block device 00:05.0 Unclassified device [00ff]: Red Hat, Inc Virtio memory balloon
df
df command can list the size, usage, usage, mount point and other information of different partitions. With the -h
option, the size can be expressed in units of k, M, G, etc., otherwise it defaults to It's bytes, not easy to read.
[alvin@VM_0_16_centos ~]$ df -h Filesystem Size Used Avail Use% Mounted on /dev/vda1 50G 7.5G 40G 16% / devtmpfs 911M 0 911M 0% /dev tmpfs 920M 68K 920M 1% /dev/shm tmpfs 920M 364K 920M 1% /run tmpfs 920M 0 920M 0% /sys/fs/cgroup tmpfs 184M 0 184M 0% /run/user/0 tmpfs 184M 0 184M 0% /run/user/1001 tmpfs 184M 0 184M 0% /run/user/1000
free
Thefree command can view the total amount of used, idle and RAM in the system, usually with the -m
parameter.
[alvin@VM_0_16_centos ~]$ free -m total used free shared buff/cache available Mem: 1839 221 156 0 1461 1400 Swap: 0 0 0
The above is the detailed content of How to check hardware information under Linux?. For more information, please follow other related articles on the PHP Chinese website!

Hot AI Tools

Undresser.AI Undress
AI-powered app for creating realistic nude photos

AI Clothes Remover
Online AI tool for removing clothes from photos.

Undress AI Tool
Undress images for free

Clothoff.io
AI clothes remover

Video Face Swap
Swap faces in any video effortlessly with our completely free AI face swap tool!

Hot Article

Hot Tools

Notepad++7.3.1
Easy-to-use and free code editor

SublimeText3 Chinese version
Chinese version, very easy to use

Zend Studio 13.0.1
Powerful PHP integrated development environment

Dreamweaver CS6
Visual web development tools

SublimeText3 Mac version
God-level code editing software (SublimeText3)

Hot Topics



How to use Docker Desktop? Docker Desktop is a tool for running Docker containers on local machines. The steps to use include: 1. Install Docker Desktop; 2. Start Docker Desktop; 3. Create Docker image (using Dockerfile); 4. Build Docker image (using docker build); 5. Run Docker container (using docker run).

Docker process viewing method: 1. Docker CLI command: docker ps; 2. Systemd CLI command: systemctl status docker; 3. Docker Compose CLI command: docker-compose ps; 4. Process Explorer (Windows); 5. /proc directory (Linux).

Troubleshooting steps for failed Docker image build: Check Dockerfile syntax and dependency version. Check if the build context contains the required source code and dependencies. View the build log for error details. Use the --target option to build a hierarchical phase to identify failure points. Make sure to use the latest version of Docker engine. Build the image with --t [image-name]:debug mode to debug the problem. Check disk space and make sure it is sufficient. Disable SELinux to prevent interference with the build process. Ask community platforms for help, provide Dockerfiles and build log descriptions for more specific suggestions.

VS Code system requirements: Operating system: Windows 10 and above, macOS 10.12 and above, Linux distribution processor: minimum 1.6 GHz, recommended 2.0 GHz and above memory: minimum 512 MB, recommended 4 GB and above storage space: minimum 250 MB, recommended 1 GB and above other requirements: stable network connection, Xorg/Wayland (Linux)

The reasons for the installation of VS Code extensions may be: network instability, insufficient permissions, system compatibility issues, VS Code version is too old, antivirus software or firewall interference. By checking network connections, permissions, log files, updating VS Code, disabling security software, and restarting VS Code or computers, you can gradually troubleshoot and resolve issues.

VS Code is available on Mac. It has powerful extensions, Git integration, terminal and debugger, and also offers a wealth of setup options. However, for particularly large projects or highly professional development, VS Code may have performance or functional limitations.

VS Code is the full name Visual Studio Code, which is a free and open source cross-platform code editor and development environment developed by Microsoft. It supports a wide range of programming languages and provides syntax highlighting, code automatic completion, code snippets and smart prompts to improve development efficiency. Through a rich extension ecosystem, users can add extensions to specific needs and languages, such as debuggers, code formatting tools, and Git integrations. VS Code also includes an intuitive debugger that helps quickly find and resolve bugs in your code.

How to back up VS Code configurations and extensions? Manually backup the settings file: Copy the key JSON files (settings.json, keybindings.json, extensions.json) to a safe location. Take advantage of VS Code synchronization: enable synchronization with your GitHub account to automatically back up all relevant settings and extensions. Use third-party tools: Back up configurations with reliable tools and provide richer features such as version control and incremental backups.
