Linux Command To Find the System Configuration And Hardware Information

最新推荐文章于 2025-12-07 12:18:51 发布
转载 最新推荐文章于 2025-12-07 12:18:51 发布 · 1.4k 阅读 · 0
文章标签：

#linux

本文详细介绍了在Linux系统中使用命令行方式获取硬件配置信息的方法，包括CPU、内存、磁盘、BIOS版本、操作系统版本等。通过运行特定命令，用户可以轻松了解系统硬件的详细情况。

Linux Command To Find the System Configuration And Hardware Information

by  VIVEK GITE  on  AUGUST 2, 2007
in  BASH SHELL,  CENTOS,  DEBIAN / UBUNTU,  LINUX,  SUSE

What is the command to find the system configuration on Linux operating system using command line (text) mode?


On Linux based system most of the hardware information can be extracted from /proc file system, for example display CPU and Memory information, enter:

Tutorial details  
Difficulty Intermediate (rss)
Root privileges Yes
Requirements None
Estimated completion time 10 minutes
cat /proc/meminfo
cat /proc/cpuinfo

The following list summarizes commands to get various hardware from the system:

Linux cpu/hardware information

Use any one of the following command:
# less /proc/cpuinfo
OR
# lscpu
Sample outputs:

Architecture:          x86_64
CPU op-mode(s):        32-bit, 64-bit
Byte Order:            Little Endian
CPU(s):                32
On-line CPU(s) list:   0-31
Thread(s) per core:    2
Core(s) per socket:    8
Socket(s):             2
NUMA node(s):          2
Vendor ID:             GenuineIntel
CPU family:            6
Model:                 45
Stepping:              7
CPU MHz:               1999.874
BogoMIPS:              4000.99
Virtualization:        VT-x
L1d cache:             32K
L1i cache:             32K
L2 cache:              256K
L3 cache:              20480K
NUMA node0 CPU(s):     0-7,16-23
NUMA node1 CPU(s):     8-15,24-31

Linux show free and used memory in the system

Use any one of the following command:
# cat /proc/meminfo
OR
# free
# free -m
# free -mt
# free -gt
Sample outputs:

             total       used       free     shared    buffers     cached
Mem:      32911564   32665848     245716     168592     294192   29324484
-/+ buffers/cache:    3047172   29864392
Swap:       999420      81832     917588

You can also run top/htop/atop commands to see used and free memory and cpu usage and more:
# top
# htop
# atop

Find ram speed and max supported ram by the server

# dmidecode --type 17
# lshw -short -C memory
# perl memconf.v3.06.pl -v
Sample outputs:

memconf:  V3.06 17-Feb-2015 http://sourceforge.net/projects/memconf/
hostname: server1
manufacturer: Supermicro
model:    X9DRi-LN4+/X9DR3-LN4+ (2 X Eight-Core Hyper-Threaded Intel(R) Xeon(R) E5-2650 0 @ 2.00GHz)
BusyBox v1.21.1
is, Ubuntu 14.04.2 LTS, 64-bit kernel, Linux 3.13.0-46-generic
CPU 1: Intel(R) Xeon(R) E5-2650 0 @ 2.00GHz cpu, system freq: 100MHz
CPU 2: Intel(R) Xeon(R) E5-2650 0 @ 2.00GHz cpu, system freq: 100MHz
Memory Error Correction: Multi-bit ECC
Maximum Memory: 786432MB (768GB)
P1-DIMMA1 P0_Node0_Channel0_Dimm0: 4096MB 1600MHz Registered (Buffered) DDR3 DIMM, Kingston SL4D316R11D8HE
P1-DIMMB1 P0_Node0_Channel1_Dimm0: 4096MB 1600MHz Registered (Buffered) DDR3 DIMM, Kingston SL4D316R11D8HE
P1-DIMMC1 P0_Node0_Channel2_Dimm0: 4096MB 1600MHz Registered (Buffered) DDR3 DIMM, Kingston SL4D316R11D8HE
P1-DIMMD1 P0_Node0_Channel3_Dimm0: 4096MB 1600MHz Registered (Buffered) DDR3 DIMM, Kingston SL4D316R11D8HE
P2-DIMME1 P1_Node1_Channel0_Dimm0: 4096MB 1600MHz Registered (Buffered) DDR3 DIMM, Kingston SL4D316R11D8HE
P2-DIMMF1 P1_Node1_Channel1_Dimm0: 4096MB 1600MHz Registered (Buffered) DDR3 DIMM, Kingston SL4D316R11D8HE
P2-DIMMG1 P1_Node1_Channel2_Dimm0: 4096MB 1600MHz Registered (Buffered) DDR3 DIMM, Kingston SL4D316R11D8HE
P2-DIMMH1 P1_Node1_Channel3_Dimm0: 4096MB 1600MHz Registered (Buffered) DDR3 DIMM, Kingston SL4D316R11D8HE

Linux find out the current running kernel version

Type the following command:
# cat /proc/version
Sample outputs:

Linux version 3.2.0-43-generic (buildd@batsu) (gcc version 4.6.3 (Ubuntu/Linaro 4.6.3-1ubuntu5) ) #68-Ubuntu SMP Wed May 15 03:33:33 UTC 2013

OR use the following command:
# uname -mrs
# uname -a

Find out information about the Linux distribution and version

# lsb_release -a
Sample outputs:

No LSB modules are available.
Distributor ID:	Ubuntu
Description:	Ubuntu 12.04.2 LTS
Release:	12.04
Codename:	precise

OR use the following command:
$ cat /etc/*release*
Sample outputs:

Red Hat Enterprise Linux Server release 6.4 (Santiago)

List all PCI devices

# lspci
Sample outputs:

00:00.0 Host bridge: Intel Corporation Xeon E5/Core i7 DMI2 (rev 07)
00:01.0 PCI bridge: Intel Corporation Xeon E5/Core i7 IIO PCI Express Root Port 1a (rev 07)
00:01.1 PCI bridge: Intel Corporation Xeon E5/Core i7 IIO PCI Express Root Port 1b (rev 07)
00:02.0 PCI bridge: Intel Corporation Xeon E5/Core i7 IIO PCI Express Root Port 2a (rev 07)
00:03.0 PCI bridge: Intel Corporation Xeon E5/Core i7 IIO PCI Express Root Port 3a in PCI Express Mode (rev 07)
00:04.0 System peripheral: Intel Corporation Xeon E5/Core i7 DMA Channel 0 (rev 07)
00:04.1 System peripheral: Intel Corporation Xeon E5/Core i7 DMA Channel 1 (rev 07)
00:04.2 System peripheral: Intel Corporation Xeon E5/Core i7 DMA Channel 2 (rev 07)
00:04.3 System peripheral: Intel Corporation Xeon E5/Core i7 DMA Channel 3 (rev 07)
00:04.4 System peripheral: Intel Corporation Xeon E5/Core i7 DMA Channel 4 (rev 07)
00:04.5 System peripheral: Intel Corporation Xeon E5/Core i7 DMA Channel 5 (rev 07)
00:04.6 System peripheral: Intel Corporation Xeon E5/Core i7 DMA Channel 6 (rev 07)
00:04.7 System peripheral: Intel Corporation Xeon E5/Core i7 DMA Channel 7 (rev 07)
00:05.0 System peripheral: Intel Corporation Xeon E5/Core i7 Address Map, VTd_Misc, System Management (rev 07)
00:05.2 System peripheral: Intel Corporation Xeon E5/Core i7 Control Status and Global Errors (rev 07)
00:05.4 PIC: Intel Corporation Xeon E5/Core i7 I/O APIC (rev 07)
00:11.0 PCI bridge: Intel Corporation C600/X79 series chipset PCI Express Virtual Root Port (rev 06)
00:16.0 Communication controller: Intel Corporation C600/X79 series chipset MEI Controller #1 (rev 05)
00:16.1 Communication controller: Intel Corporation C600/X79 series chipset MEI Controller #2 (rev 05)
00:1a.0 USB controller: Intel Corporation C600/X79 series chipset USB2 Enhanced Host Controller #2 (rev 06)
00:1c.0 PCI bridge: Intel Corporation C600/X79 series chipset PCI Express Root Port 1 (rev b6)
00:1d.0 USB controller: Intel Corporation C600/X79 series chipset USB2 Enhanced Host Controller #1 (rev 06)
00:1e.0 PCI bridge: Intel Corporation 82801 PCI Bridge (rev a6)
00:1f.0 ISA bridge: Intel Corporation C600/X79 series chipset LPC Controller (rev 06)
00:1f.2 SATA controller: Intel Corporation C600/X79 series chipset 6-Port SATA AHCI Controller (rev 06)
00:1f.3 SMBus: Intel Corporation C600/X79 series chipset SMBus Host Controller (rev 06)
00:1f.6 Signal processing controller: Intel Corporation C600/X79 series chipset Thermal Management Controller (rev 06)
06:00.0 Ethernet controller: Intel Corporation I350 Gigabit Network Connection (rev 01)
06:00.1 Ethernet controller: Intel Corporation I350 Gigabit Network Connection (rev 01)
06:00.2 Ethernet controller: Intel Corporation I350 Gigabit Network Connection (rev 01)
06:00.3 Ethernet controller: Intel Corporation I350 Gigabit Network Connection (rev 01)
08:01.0 VGA compatible controller: Matrox Electronics Systems Ltd. MGA G200eW WPCM450 (rev 0a)
7f:08.0 System peripheral: Intel Corporation Xeon E5/Core i7 QPI Link 0 (rev 07)
7f:08.3 System peripheral: Intel Corporation Xeon E5/Core i7 QPI Link Reut 0 (rev 07)
7f:08.4 System peripheral: Intel Corporation Xeon E5/Core i7 QPI Link Reut 0 (rev 07)
7f:09.0 System peripheral: Intel Corporation Xeon E5/Core i7 QPI Link 1 (rev 07)
7f:09.3 System peripheral: Intel Corporation Xeon E5/Core i7 QPI Link Reut 1 (rev 07)
7f:09.4 System peripheral: Intel Corporation Xeon E5/Core i7 QPI Link Reut 1 (rev 07)
7f:0a.0 System peripheral: Intel Corporation Xeon E5/Core i7 Power Control Unit 0 (rev 07)
7f:0a.1 System peripheral: Intel Corporation Xeon E5/Core i7 Power Control Unit 1 (rev 07)
7f:0a.2 System peripheral: Intel Corporation Xeon E5/Core i7 Power Control Unit 2 (rev 07)
7f:0a.3 System peripheral: Intel Corporation Xeon E5/Core i7 Power Control Unit 3 (rev 07)
7f:0b.0 System peripheral: Intel Corporation Xeon E5/Core i7 Interrupt Control Registers (rev 07)
7f:0b.3 System peripheral: Intel Corporation Xeon E5/Core i7 Semaphore and Scratchpad Configuration Registers (rev 07)
7f:0c.0 System peripheral: Intel Corporation Xeon E5/Core i7 Unicast Register 0 (rev 07)
7f:0c.1 System peripheral: Intel Corporation Xeon E5/Core i7 Unicast Register 0 (rev 07)
7f:0c.2 System peripheral: Intel Corporation Xeon E5/Core i7 Unicast Register 0 (rev 07)
7f:0c.3 System peripheral: Intel Corporation Xeon E5/Core i7 Unicast Register 0 (rev 07)
7f:0c.6 System peripheral: Intel Corporation Xeon E5/Core i7 Integrated Memory Controller System Address Decoder 0 (rev 07)
7f:0c.7 System peripheral: Intel Corporation Xeon E5/Core i7 System Address Decoder (rev 07)
7f:0d.0 System peripheral: Intel Corporation Xeon E5/Core i7 Unicast Register 0 (rev 07)
7f:0d.1 System peripheral: Intel Corporation Xeon E5/Core i7 Unicast Register 0 (rev 07)
7f:0d.2 System peripheral: Intel Corporation Xeon E5/Core i7 Unicast Register 0 (rev 07)
7f:0d.3 System peripheral: Intel Corporation Xeon E5/Core i7 Unicast Register 0 (rev 07)
7f:0d.6 System peripheral: Intel Corporation Xeon E5/Core i7 Integrated Memory Controller System Address Decoder 1 (rev 07)
7f:0e.0 System peripheral: Intel Corporation Xeon E5/Core i7 Processor Home Agent (rev 07)
7f:0e.1 Performance counters: Intel Corporation Xeon E5/Core i7 Processor Home Agent Performance Monitoring (rev 07)
7f:0f.0 System peripheral: Intel Corporation Xeon E5/Core i7 Integrated Memory Controller Registers (rev 07)
7f:0f.1 System peripheral: Intel Corporation Xeon E5/Core i7 Integrated Memory Controller RAS Registers (rev 07)
7f:0f.2 System peripheral: Intel Corporation Xeon E5/Core i7 Integrated Memory Controller Target Address Decoder 0 (rev 07)
7f:0f.3 System peripheral: Intel Corporation Xeon E5/Core i7 Integrated Memory Controller Target Address Decoder 1 (rev 07)
7f:0f.4 System peripheral: Intel Corporation Xeon E5/Core i7 Integrated Memory Controller Target Address Decoder 2 (rev 07)
7f:0f.5 System peripheral: Intel Corporation Xeon E5/Core i7 Integrated Memory Controller Target Address Decoder 3 (rev 07)
7f:0f.6 System peripheral: Intel Corporation Xeon E5/Core i7 Integrated Memory Controller Target Address Decoder 4 (rev 07)
7f:10.0 System peripheral: Intel Corporation Xeon E5/Core i7 Integrated Memory Controller Channel 0-3 Thermal Control 0 (rev 07)
7f:10.1 System peripheral: Intel Corporation Xeon E5/Core i7 Integrated Memory Controller Channel 0-3 Thermal Control 1 (rev 07)
7f:10.2 System peripheral: Intel Corporation Xeon E5/Core i7 Integrated Memory Controller ERROR Registers 0 (rev 07)
7f:10.3 System peripheral: Intel Corporation Xeon E5/Core i7 Integrated Memory Controller ERROR Registers 1 (rev 07)
7f:10.4 System peripheral: Intel Corporation Xeon E5/Core i7 Integrated Memory Controller Channel 0-3 Thermal Control 2 (rev 07)
7f:10.5 System peripheral: Intel Corporation Xeon E5/Core i7 Integrated Memory Controller Channel 0-3 Thermal Control 3 (rev 07)
7f:10.6 System peripheral: Intel Corporation Xeon E5/Core i7 Integrated Memory Controller ERROR Registers 2 (rev 07)
7f:10.7 System peripheral: Intel Corporation Xeon E5/Core i7 Integrated Memory Controller ERROR Registers 3 (rev 07)
7f:11.0 System peripheral: Intel Corporation Xeon E5/Core i7 DDRIO (rev 07)
7f:13.0 System peripheral: Intel Corporation Xeon E5/Core i7 R2PCIe (rev 07)
7f:13.1 Performance counters: Intel Corporation Xeon E5/Core i7 Ring to PCI Express Performance Monitor (rev 07)
7f:13.4 Performance counters: Intel Corporation Xeon E5/Core i7 QuickPath Interconnect Agent Ring Registers (rev 07)
7f:13.5 Performance counters: Intel Corporation Xeon E5/Core i7 Ring to QuickPath Interconnect Link 0 Performance Monitor (rev 07)
7f:13.6 System peripheral: Intel Corporation Xeon E5/Core i7 Ring to QuickPath Interconnect Link 1 Performance Monitor (rev 07)
80:01.0 PCI bridge: Intel Corporation Xeon E5/Core i7 IIO PCI Express Root Port 1a (rev 07)
80:02.0 PCI bridge: Intel Corporation Xeon E5/Core i7 IIO PCI Express Root Port 2a (rev 07)
80:03.0 PCI bridge: Intel Corporation Xeon E5/Core i7 IIO PCI Express Root Port 3a in PCI Express Mode (rev 07)
80:04.0 System peripheral: Intel Corporation Xeon E5/Core i7 DMA Channel 0 (rev 07)
80:04.1 System peripheral: Intel Corporation Xeon E5/Core i7 DMA Channel 1 (rev 07)
80:04.2 System peripheral: Intel Corporation Xeon E5/Core i7 DMA Channel 2 (rev 07)
80:04.3 System peripheral: Intel Corporation Xeon E5/Core i7 DMA Channel 3 (rev 07)
80:04.4 System peripheral: Intel Corporation Xeon E5/Core i7 DMA Channel 4 (rev 07)
80:04.5 System peripheral: Intel Corporation Xeon E5/Core i7 DMA Channel 5 (rev 07)
80:04.6 System peripheral: Intel Corporation Xeon E5/Core i7 DMA Channel 6 (rev 07)
80:04.7 System peripheral: Intel Corporation Xeon E5/Core i7 DMA Channel 7 (rev 07)
80:05.0 System peripheral: Intel Corporation Xeon E5/Core i7 Address Map, VTd_Misc, System Management (rev 07)
80:05.2 System peripheral: Intel Corporation Xeon E5/Core i7 Control Status and Global Errors (rev 07)
80:05.4 PIC: Intel Corporation Xeon E5/Core i7 I/O APIC (rev 07)
81:00.0 RAID bus controller: Adaptec AAC-RAID (rev 09)
ff:08.0 System peripheral: Intel Corporation Xeon E5/Core i7 QPI Link 0 (rev 07)
ff:08.3 System peripheral: Intel Corporation Xeon E5/Core i7 QPI Link Reut 0 (rev 07)
ff:08.4 System peripheral: Intel Corporation Xeon E5/Core i7 QPI Link Reut 0 (rev 07)
ff:09.0 System peripheral: Intel Corporation Xeon E5/Core i7 QPI Link 1 (rev 07)
ff:09.3 System peripheral: Intel Corporation Xeon E5/Core i7 QPI Link Reut 1 (rev 07)
ff:09.4 System peripheral: Intel Corporation Xeon E5/Core i7 QPI Link Reut 1 (rev 07)
ff:0a.0 System peripheral: Intel Corporation Xeon E5/Core i7 Power Control Unit 0 (rev 07)
ff:0a.1 System peripheral: Intel Corporation Xeon E5/Core i7 Power Control Unit 1 (rev 07)
ff:0a.2 System peripheral: Intel Corporation Xeon E5/Core i7 Power Control Unit 2 (rev 07)
ff:0a.3 System peripheral: Intel Corporation Xeon E5/Core i7 Power Control Unit 3 (rev 07)
ff:0b.0 System peripheral: Intel Corporation Xeon E5/Core i7 Interrupt Control Registers (rev 07)
ff:0b.3 System peripheral: Intel Corporation Xeon E5/Core i7 Semaphore and Scratchpad Configuration Registers (rev 07)
ff:0c.0 System peripheral: Intel Corporation Xeon E5/Core i7 Unicast Register 0 (rev 07)
ff:0c.1 System peripheral: Intel Corporation Xeon E5/Core i7 Unicast Register 0 (rev 07)
ff:0c.2 System peripheral: Intel Corporation Xeon E5/Core i7 Unicast Register 0 (rev 07)
ff:0c.3 System peripheral: Intel Corporation Xeon E5/Core i7 Unicast Register 0 (rev 07)
ff:0c.6 System peripheral: Intel Corporation Xeon E5/Core i7 Integrated Memory Controller System Address Decoder 0 (rev 07)
ff:0c.7 System peripheral: Intel Corporation Xeon E5/Core i7 System Address Decoder (rev 07)
ff:0d.0 System peripheral: Intel Corporation Xeon E5/Core i7 Unicast Register 0 (rev 07)
ff:0d.1 System peripheral: Intel Corporation Xeon E5/Core i7 Unicast Register 0 (rev 07)
ff:0d.2 System peripheral: Intel Corporation Xeon E5/Core i7 Unicast Register 0 (rev 07)
ff:0d.3 System peripheral: Intel Corporation Xeon E5/Core i7 Unicast Register 0 (rev 07)
ff:0d.6 System peripheral: Intel Corporation Xeon E5/Core i7 Integrated Memory Controller System Address Decoder 1 (rev 07)
ff:0e.0 System peripheral: Intel Corporation Xeon E5/Core i7 Processor Home Agent (rev 07)
ff:0e.1 Performance counters: Intel Corporation Xeon E5/Core i7 Processor Home Agent Performance Monitoring (rev 07)
ff:0f.0 System peripheral: Intel Corporation Xeon E5/Core i7 Integrated Memory Controller Registers (rev 07)
ff:0f.1 System peripheral: Intel Corporation Xeon E5/Core i7 Integrated Memory Controller RAS Registers (rev 07)
ff:0f.2 System peripheral: Intel Corporation Xeon E5/Core i7 Integrated Memory Controller Target Address Decoder 0 (rev 07)
ff:0f.3 System peripheral: Intel Corporation Xeon E5/Core i7 Integrated Memory Controller Target Address Decoder 1 (rev 07)
ff:0f.4 System peripheral: Intel Corporation Xeon E5/Core i7 Integrated Memory Controller Target Address Decoder 2 (rev 07)
ff:0f.5 System peripheral: Intel Corporation Xeon E5/Core i7 Integrated Memory Controller Target Address Decoder 3 (rev 07)
ff:0f.6 System peripheral: Intel Corporation Xeon E5/Core i7 Integrated Memory Controller Target Address Decoder 4 (rev 07)
ff:10.0 System peripheral: Intel Corporation Xeon E5/Core i7 Integrated Memory Controller Channel 0-3 Thermal Control 0 (rev 07)
ff:10.1 System peripheral: Intel Corporation Xeon E5/Core i7 Integrated Memory Controller Channel 0-3 Thermal Control 1 (rev 07)
ff:10.2 System peripheral: Intel Corporation Xeon E5/Core i7 Integrated Memory Controller ERROR Registers 0 (rev 07)
ff:10.3 System peripheral: Intel Corporation Xeon E5/Core i7 Integrated Memory Controller ERROR Registers 1 (rev 07)
ff:10.4 System peripheral: Intel Corporation Xeon E5/Core i7 Integrated Memory Controller Channel 0-3 Thermal Control 2 (rev 07)
ff:10.5 System peripheral: Intel Corporation Xeon E5/Core i7 Integrated Memory Controller Channel 0-3 Thermal Control 3 (rev 07)
ff:10.6 System peripheral: Intel Corporation Xeon E5/Core i7 Integrated Memory Controller ERROR Registers 2 (rev 07)
ff:10.7 System peripheral: Intel Corporation Xeon E5/Core i7 Integrated Memory Controller ERROR Registers 3 (rev 07)
ff:11.0 System peripheral: Intel Corporation Xeon E5/Core i7 DDRIO (rev 07)
ff:13.0 System peripheral: Intel Corporation Xeon E5/Core i7 R2PCIe (rev 07)
ff:13.1 Performance counters: Intel Corporation Xeon E5/Core i7 Ring to PCI Express Performance Monitor (rev 07)
ff:13.4 Performance counters: Intel Corporation Xeon E5/Core i7 QuickPath Interconnect Agent Ring Registers (rev 07)
ff:13.5 Performance counters: Intel Corporation Xeon E5/Core i7 Ring to QuickPath Interconnect Link 0 Performance Monitor (rev 07)
ff:13.6 System peripheral: Intel Corporation Xeon E5/Core i7 Ring to QuickPath Interconnect Link 1 Performance Monitor (rev 07)

List all USB devices

# lsusb
Sample outputs:

Bus 002 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 001 Device 003: ID 0557:2221 ATEN International Co., Ltd Winbond Hermon
Bus 001 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

List all block devices (hard disks, cdrom, and others)

# lsblk
Sample outputs:

sda      8:0    1 372.3G  0 disk
|-sda1   8:1    1   243M  0 part /boot
|-sda2   8:2    1     1K  0 part
|-sda5   8:5    1   976M  0 part [SWAP]
`-sda6   8:6    1 371.1G  0 part /
sr0     11:0    1  1024M  0 rom
loop0    7:0    0     4G  0 loop /jails/tmp

Display installed hard disk and size

# fdisk -l | grep '^Disk /dev/'
Sample outputs:

Disk /dev/sda: 399.7 GB, 399717171200 bytes

Display information about hardware RAID

See info about Adaptec hardware RAID:
# arcconf getconfig DEV
# /usr/StorMan/arcconf getconfig 1
See info about 3ware hardware RAID:
# tw_cli /dev show
# tw_cli /c0 show

Say hello to lshw

The lshw is a small command line tool to extract detailed information on the hardware configuration of the machine. It can report exact memory configuration, firmware version, mainboard configuration, CPU version and speed, cache configuration, bus speed, etc. on DMI-capable x86 or IA-64 systems and on some PowerPC machines (PowerMac G4 is known to work):
# lshw | more
# lshw -html > output.htmlq
# lshw -short | less
Sample outputs:

H/W path          Device      Class          Description
========================================================
                              system         X9DRi-LN4+/X9DR3-LN4+ (To be filled by O.E.M.)
/0                            bus            X9DRi-LN4+/X9DR3-LN4+
/0/0                          memory         64KiB BIOS
/0/4                          processor      Intel(R) Xeon(R) CPU E5-2650 0 @ 2.00GHz
/0/4/5                        memory         512KiB L1 cache
/0/4/6                        memory         2MiB L2 cache
/0/4/7                        memory         20MiB L3 cache
/0/6                          processor      Intel(R) Xeon(R) CPU E5-2650 0 @ 2.00GHz
/0/6/9                        memory         512KiB L1 cache
/0/6/a                        memory         2MiB L2 cache
/0/6/b                        memory         20MiB L3 cache
/0/2f                         memory         System Memory
/0/2f/0                       memory         4GiB DIMM DDR3 1600 MHz (0.6 ns)
/0/2f/1                       memory         DIMM Synchronous [empty]
/0/2f/2                       memory         DIMM Synchronous [empty]
/0/2f/3                       memory         4GiB DIMM DDR3 1600 MHz (0.6 ns)
/0/2f/4                       memory         DIMM Synchronous [empty]
/0/2f/5                       memory         DIMM Synchronous [empty]
/0/2f/6                       memory         4GiB DIMM DDR3 1600 MHz (0.6 ns)
....
...
..
/0/1                          bridge         Xeon E5/Core i7 IIO PCI Express Root Port 1a
/0/1/0            scsi0       storage        AAC-RAID
/0/1/0/0.0.0      /dev/sda    disk           399GB SCSI Disk
/0/1/0/0.0.0/1    /dev/sda1   volume         243MiB Linux filesystem partition
/0/1/0/0.0.0/2    /dev/sda2   volume         372GiB Extended partition
/0/1/0/0.0.0/2/5  /dev/sda5   volume         976MiB Linux swap / Solaris partition
/0/1/0/0.0.0/2/6  /dev/sda6   volume         371GiB Linux filesystem partition
/0/1/0/1.0.0                  disk           SCSI Disk
/0/1/0/1.1.0                  disk           SCSI Disk
/0/1/0/1.2.0                  disk           SCSI Disk
/0/1/0/1.3.0                  disk           SCSI Disk
...
..
...
/0/68             scsi5       storage
/0/68/0.0.0       /dev/cdrom  disk           DV-28S-W
/1                            power          PWS-605P-1H
/2                vethWKP76N  network        Ethernet interface
/3                veth1N2SWB  network        Ethernet interface
/4                veth8L2A3F  network        Ethernet interface
/5                bond0       network        Ethernet interface
 

Dump all hardware information

Type the following command to see your motherboard, cpu, vendor, serial-numbers, RAM, disks, and other information directly from the system BIOS:
# dmidecode | less
Sample outputs:

# dmidecode 2.12
SMBIOS 2.7 present.
155 structures occupying 7700 bytes.
Table at 0x000EC440.
 
Handle 0x0000, DMI type 0, 24 bytes
BIOS Information
        Vendor: American Megatrends Inc.
        Version: 3.0b
        Release Date: 05/27/2014
        Address: 0xF0000
        Runtime Size: 64 kB
        ROM Size: 12288 kB
        Characteristics:
                PCI is supported
                BIOS is upgradeable
                BIOS shadowing is allowed
                Boot from CD is supported
                Selectable boot is supported
                BIOS ROM is socketed
                EDD is supported
                Print screen service is supported (int 5h)
                8042 keyboard services are supported (int 9h)
                Serial services are supported (int 14h)
                Printer services are supported (int 17h)
                ACPI is supported
                USB legacy is supported
                BIOS boot specification is supported
                Function key-initiated network boot is supported
                Targeted content distribution is supported
                UEFI is supported
        BIOS Revision: 3.11
 
Handle 0x0001, DMI type 1, 27 bytes
System Information
        Manufacturer: Supermicro
        Product Name: X9DRi-LN4+/X9DR3-LN4+
        Version: 0123456789
        Serial Number: 0123456789
        UUID: 00000000-0000-0000-0000-0025902E1590
        Wake-up Type: Power Switch
        SKU Number: To be filled by O.E.M.
        Family: To be filled by O.E.M.
 
Handle 0x0002, DMI type 2, 15 bytes
Base Board Information
        Manufacturer: Supermicro
....
..
...
 
Handle 0x00AB, DMI type 13, 22 bytes
BIOS Language Information
        Language Description Format: Long
        Installable Languages: 1
                en|US|iso8859-1
        Currently Installed Language: en|US|iso8859-1
 
Handle 0x00AE, DMI type 127, 4 bytes
End Of Table
 
Could not find a package configuration file provided by “***“ with any of the following，找不到cmake文件
pvmsmfchcs的博客
01-06 1万+
1，可以使用下面的方法，我们将cmake设置到工作环境中，一般情况下它有一个启动的setup.sh文件，配置到bashrc文件中。然后就可以了，就说明这个cmake文件在系统环境了，就可以调用了。2.还有一种方法，就是将came复制出来，然后直接用findpackage方法，就可以，推荐使用第一种方法。
Porting Linux to a new processor architecture, part 2: The early code
mounter625的专栏
05-13 1080
本文是系列文章的第二部分，继续探讨将Linux移植到新处理器架构的过程，重点介绍了启动代码的实现。文章首先讨论了架构相关头文件的作用，这些头文件分为内核接口和用户接口两部分，通常涉及上百个文件，是移植过程中工作量较大的部分。幸运的是，许多处理器架构共享相似代码，这些代码已被汇总到通用头文件层中，减少了定制需求。接着，文章详细描述了启动流程，从手动编写的汇编函数开始，逐步执行一系列架构相关函数，如设置架构、初始化陷阱、内存管理等，最终创建第一个内核线程。这一过程帮助开发者理解必须实现的最小架构相关函数集合及其
Error Detection And Correction (EDAC)
一棹春风一叶舟，一纶茧缕一轻钩
12-17 6048
COPIED FROM: http://fibrevillage.com/sysadmin/243-edac-error-detection-and-correction https://01.org/linuxgraphics/gfx-docs/drm/driver-api/edac.html 1. Error Detection And Correction (EDAC) D...
成功解决MemoryError
m0_66793065的博客
10-25 2万+
成功解决MemoryError。
服务器内存故障预测居然可以这样做！
vivo互联网技术
07-26 3800
。本文主要介绍EDAC（Error Detection And Correction）框架在内存预测方面的应用。首先介绍了EDAC应用的背景，接着是EDAC的原理介绍，然后通过EDAC安装——配置——测试过程详细的介绍了EDAC在vivo服务器上的应用，最后提出了内存预测使用EDAC的方案总结以及服务器RAS（Reliability, Availability and Serviceability）应用减小硬件故障对系统的影响的展望。...
Linux中压缩zip和解压unzip(转载至尤灯塔)
qq_41612527的博客
10-19 539
作者：尤灯塔 出处：https://www.cnblogs.com/30go/ 本文版权归作者和博客园共有，欢迎转载，但未经作者同意必须保留此段声明，且在文章页面明显位置给出原文连接，否则保留追究法律责任的权利. 1、把/home目录下面的mydata目录压缩为mydata.zip 　　zip -r mydata.zip mydata #压缩mydata目录 2、把/home目录下面的mydata.zip解压到mydatabak目录里面 　　unzip mydata.zip -d mydatabak 3、把
33、Linux Framebuffer Device Driver Installation and DB-to-File Utility Guide
最新发布
ansible6ops的博客
12-07 8
本文介绍了如何在Linux系统中安装和配置Framebuffer设备驱动，包括处理vesafb驱动冲突、选择合适的视频模式以及使用硬件特定驱动的方法。同时，文章还详细讲解了tbl2filed守护进程的使用，该工具通过数据库接口实现对传统配置文件的读写管理，支持SELECT查询、UPDATE更新、原子化写入和脚本触发等操作，提升了系统配置的统一性和可维护性。
MATLAB Version and Hardware Requirements: Understanding Configuration Needs for Smooth Operation
# Overview of MATLAB Versions and Hardware Requirements: Understanding Configuration Needs for Smooth Operation ## 1. Overview of MATLAB Versions MATLAB is a powerful technical computing software ...
The Indispensable PC Hardware Book - rar - part1. (1/7)
09-03
l Extensive glossary which explains most of the terms and concepts related to personal computer hardware. l Appendices brimming with practical advice, especially for programmers. -------------------...
ZooKeeper Administrator‘s Guide：A Guide to Deployment and Administration是一本关于ZooKeeper部署和管理的指南
BLOG域名:programb.blog.youkuaiyun.com
04-28 1994
它涵盖了部署系统的要求、支持的平台、所需的软件、集群设置、单服务器和开发人员设置，以及一些需要考虑的事项，如ZooKeeper的优点和局限性。总之，ZooKeeper管理员指南是一本全面而实用的参考书，对于需要部署和管理ZooKeeper的读者来说非常有价值。这包括如何识别和解决常见问题，如何设计和实施备份和恢复策略，以及如何利用ZooKeeper提供的各种工具进行故障排查。此外，该指南还提供了关于如何监控ZooKeeper的性能和可用性，以及如何处理故障转移和恢复的信息。
超微X9DRi_3-LN4F+说明书
04-15
超微服务器主板X9DRi_3-LN4F+说明书，X9DR3-LN4F+和X9DRi-LN4F+通用，USER’SMANUAL Revision 1.0b，
超微X9DRI-LN4F+最新BIOS
04-15
超微服务器主板X9DRI-LN4F+最新原版BIOS，3.3版本，更新的功能包括：Updated SATA RAID/SCU OPROM/EFI driver to RSTe PreOS v4.6.0.1018 (RSTe SATA 4.6.0.1091 and NVMe 4.6.0.2127)
【问题解决】 Could not find a package configuration file provided by “OpenCV“ with any of the following n
Xjsdhwdma的博客
01-09 3501
Could not find a package configuration file provided by "OpenCV" with any of the following names:
ubuontu16.04安装Opencv库引发的find_package()错误信息处理及其简单使用
weixin_30832143的博客
01-27 537
　　在安装完Opencv库之后，打算测试一下Opencv库是否成功安装。下面是用的例子对应的.cpp代码以及对应的CMakeLists.txt代码: .cpp文件： 1 #include <stdio.h> 2 #include <opencv2/opencv.hpp> 3 using namespace cv; 4 int main(int argc...
19.2 MEMORY CONTROLLER
weixin_30508309的博客
02-27 281
在存储控制器的BANKCONTROLREGISTER(BANKCONn: GCS6-nGCS7)表中：中文翻译各个寄存器的位出现错误： 原文中正确的表述见下图： 转载于:https://www.cnblogs.com/baixu/p/10441437.html...
系统异常重启检测-mcelog
小陌成长之路
01-11 1万+
mcelog 是Linux 系统上用来检查硬件错误，特别是内存和CPU错误的工具。 比如服务器隔一段时间莫名的重启一次，而message和syslog又检测不到有价值的信息。 通常发生MCE报错的原因有如下： 1、内存报错或者ECC问题 2、处理器过热 3、系统总线错误 4、CPU或者硬件缓存错误 一般来说当有错误提示时，需要优先注意内存问题，但由于现在内存控制器是集成在cpu里，所
Linux服务器EDAC CE memory read error
LittleMagic's Blog
03-10 7460
之前在大数据集群中，有一台服务器的CPU占用总是莫名其妙飙高，就算执行简单任务也会耗费很长时间，且reboot不能解决问题。检查了各种可能的问题之后，最终在查看dmesg命令的设备信息时，发现大量如下的日志： ...... [1180532.573917] EDAC MC1: 128 CE memory read error on CPU_SrcID#1_Ha#0_Chan#1_D...
Memory Error问题的解决方法
weixin_42547085的博客
09-20 1万+
Memory Error 问题 在用Python读取数据的时候，遇到Memory Error 问题，数据大小约为4G 解决方法 扩大虚拟内存，操作方法为 1、打开 控制面板； 2、打开 系统； 3、打开 高级系统设置； 4、点击 性能----设置； 5、点击 高级----虚拟内存----更改； 6、取消选中“自动管理所有驱动器的分页文件大小”，选择D盘（其他盘应该也可以）； 7、选择 系统管理的大小； 8、点击 设置----确定----重启电脑。 ...
内存MCE错误导致系统崩溃的问题分析
热门推荐
xuyaqun的专栏
10-31 3万+
今天服务器因为内存问题而崩溃，通过mcelog工具分析是在读内存的时候Error overflow（虽然是ECC内存，但也无奈错误太多），估计是内存硬件故障，如果再次出现的话就得考虑更换内存。 # more /var/log/messages Oct 31 14:19:36 pingu_fd kernel: sbridge: HANDLING MCE MEMORY ERROR Oct 3
Streaming MAVLink Messages This tutorial demonstrates how to stream a uORB message as a MAVLink message, and applies to both standard and custom messages. Overview MAVLink messages are streamed using a streaming class, derived from MavlinkStream, that has been added to the PX4 stream list. The class has framework methods that you implement so PX4 can get information it needs from the generated MAVLink message definition. It also has a send() method that is called each time the message needs to be sent — you override this to copy information from a uORB subscription to the MAVLink message object that is to be sent. Once you have created a streaming class the corresponding message can be streamed on request. You can also configure PX4 to stream the message by default, depending on the MAVLink configuration. Preconditions Generally you will already have a uORB message that contains information you'd like to stream and a definition of a MAVLink message that you'd like to stream it with. For this example we're going to assume that you want to stream the (existing) BatteryStatus uORB message to a new MAVLink battery status message, which we will name BATTERY_STATUS_DEMO. Copy this BATTERY_STATUS_DEMO message into the message section of development.xml in your PX4 source code, which will be located at: \src\modules\mavlink\mavlink\message_definitions\v1.0\development.xml. <message id="11514" name="BATTERY_STATUS_DEMO"> <description>Simple demo battery.</description> <field type="uint8_t" name="id" instance="true">Battery ID</field> <field type="int16_t" name="temperature" units="cdegC" invalid="INT16_MAX">Temperature of the whole battery pack (not internal electronics). INT16_MAX field not provided.</field> <field type="uint8_t" name="percent_remaining" units="%" invalid="UINT8_MAX">Remaining battery energy. Values: [0-100], UINT8_MAX: field not provided.</field> </message> INFO Note that this is a cut-down version of the not-yet-implemented BATTERY_STATUS_V2 message with randomly chosen unused id of 11514. Here we've put the message in development.xml, which is fine for testing and if the message is intended to eventually be part of the standard message set, but you might also put a custom message in its own dialect file. Build PX4 for SITL and confirm that the associated message is generated in /build/px4_sitl_default/mavlink/development/mavlink_msg_battery_status_demo.h. Because BatteryStatus already exists you will not need to do anything to create or build it. Define the Streaming Class First create a file named BATTERY_STATUS_DEMO.hpp for your streaming class (named after the message to stream) inside the /src/modules/mavlink/streams directory. Add the headers for the uORB message(s) to the top of the file (the required MAVLink headers should already be available): #include <uORB/topics/battery_status.h> INFO The uORB topic's snake-case header file is generated from the CamelCase uORB filename at build time. Then copy the streaming class definition below into the file: class MavlinkStreamBatteryStatusDemo : public MavlinkStream { public: static MavlinkStream *new_instance(Mavlink *mavlink) { return new MavlinkStreamBatteryStatusDemo(mavlink); } const char *get_name() const { return MavlinkStreamBatteryStatusDemo::get_name_static(); } static const char *get_name_static() { return "BATTERY_STATUS_DEMO"; } static uint16_t get_id_static() { return MAVLINK_MSG_ID_BATTERY_STATUS_DEMO; } uint16_t get_id() { return get_id_static(); } unsigned get_size() { return MAVLINK_MSG_ID_BATTERY_STATUS_DEMO_LEN + MAVLINK_NUM_NON_PAYLOAD_BYTES; } private: //Subscription to array of uORB battery status instances uORB::SubscriptionMultiArray<battery_status_s, battery_status_s::MAX_INSTANCES> _battery_status_subs{ORB_ID::battery_status}; // SubscriptionMultiArray subscription is needed because battery has multiple instances. // uORB::Subscription is used to subscribe to a single-instance topic /* do not allow top copying this class */ MavlinkStreamBatteryStatusDemo(MavlinkStreamBatteryStatusDemo &); MavlinkStreamBatteryStatusDemo& operator = (const MavlinkStreamBatteryStatusDemo &); protected: explicit MavlinkStreamBatteryStatusDemo(Mavlink *mavlink) : MavlinkStream(mavlink) {} bool send() override { bool updated = false; // Loop through _battery_status_subs (subscription to array of BatteryStatus instances) for (auto &battery_sub : _battery_status_subs) { // battery_status_s is a struct that can hold the battery object topic battery_status_s battery_status; // Update battery_status and publish only if the status has changed if (battery_sub.update(&battery_status)) { // mavlink_battery_status_demo_t is the MAVLink message object mavlink_battery_status_demo_t bat_msg{}; bat_msg.id = battery_status.id - 1; bat_msg.percent_remaining = (battery_status.connected) ? roundf(battery_status.remaining * 100.f) : -1; // check if temperature valid if (battery_status.connected && PX4_ISFINITE(battery_status.temperature)) { bat_msg.temperature = battery_status.temperature * 100.f; } else { bat_msg.temperature = INT16_MAX; } //Send the message mavlink_msg_battery_status_demo_send_struct(_mavlink->get_channel(), &bat_msg); updated = true; } } return updated; } }; Most streaming classes are very similar (see examples in /src/modules/mavlink/streams): The streaming class derives from MavlinkStream and is named using the pattern MavlinkStream<CamelCaseMessageName>. The public definitions are "near-boilerplate", allowing PX4 to get an instance of the class (new_instance()), and then to use it to fetch the name, id, and size of the message from the MAVLink headers (get_name(), get_name_static(), get_id_static(), get_id(), get_size()). For your own streaming classes these can just be copied and modified to match the values for your MAVLink message. The private definitions subscribe to the uORB topics that need to be published. In this case the uORB topic has multiple instances: one for each battery. We use uORB::SubscriptionMultiArray to get an array of battery status subscriptions. Here we also define constructors to prevent the definition being copied. The protected section is where the important work takes place! Here we override the send() method, copying values from the subscribed uORB topic(s) into appropriate fields in the MAVLink message, and then send the message. In this particular example we have an array of uORB instances _battery_status_subs (because we have multiple batteries). We iterate the array and use update() on each subscription to check if the associated battery instance has changed (and update a structure with the current data). This allows us to send the MAVLink message only if the associated battery uORB topic has changed: // Struct to hold current topic data. battery_status_s battery_status; // update() populates battery_status and returns true if the status has changed if (battery_sub.update(&battery_status)) { // Use battery_status to populate message and send } If wanted to send a MAVLink message whether or not the data changed, we could instead use copy() as shown: battery_status_s battery_status; battery_sub.copy(&battery_status); INFO For a single-instance topic like VehicleStatus we would subscribe like this: // Create subscription _vehicle_status_sub uORB::Subscription _vehicle_status_sub{ORB_ID(vehicle_status)}; And we could use the resulting subscription in the same way with update or copy. vehicle_status_s vehicle_status{}; // vehicle_status_s is the definition of the uORB topic if (_vehicle_status_sub.update(&vehicle_status)) { // Use the vehicle_status as it has been updated. } Next we include our new class in mavlink_messages.cpp. Add the line below to the part of the file where all the other streams are included: #include "streams/BATTERY_STATUS_DEMO.hpp" Finally append the stream class to the streams_list at the bottom of mavlink_messages.cpp StreamListItem *streams_list[] = { ... #if defined(BATTERY_STATUS_DEMO_HPP) create_stream_list_item<MavlinkStreamBatteryStatusDemo>(), #endif // BATTERY_STATUS_DEMO_HPP ... } The class is now available for streaming, but won't be streamed by default. We cover that in the next sections. Streaming by Default The easiest way to stream your messages by default (as part of a build) is to add them to mavlink_main.cpp in the appropriate message group. If you search in the file you'll find groups of messages defined in a switch statement: MAVLINK_MODE_NORMAL: Streamed to a GCS. MAVLINK_MODE_ONBOARD: Streamed to a companion computer on a fast link, such as Ethernet MAVLINK_MODE_ONBOARD_LOW_BANDWIDTH: Streamed to a companion computer for re-routing to a reduced-traffic link, such as a GCS. MAVLINK_MODE_GIMBAL: Streamed to a gimbal MAVLINK_MODE_EXTVISION: Streamed to an external vision system MAVLINK_MODE_EXTVISIONMIN: Streamed to an external vision system on a slower link MAVLINK_MODE_OSD: Streamed to an OSD, such as an FPV headset. MAVLINK_MODE_CUSTOM: Stream nothing by default. Used when configuring streaming using MAVLink. MAVLINK_MODE_MAGIC: Same as MAVLINK_MODE_CUSTOM MAVLINK_MODE_CONFIG: Streaming over USB with higher rates than MAVLINK_MODE_NORMAL. MAVLINK_MODE_MINIMAL: Stream a minimal set of messages. Normally used for poor telemetry links. MAVLINK_MODE_IRIDIUM: Streamed to an iridium satellite phone Normally you'll be testing on a GCS, so you could just add the message to the MAVLINK_MODE_NORMAL case using the configure_stream_local() method. For example, to stream CA_TRAJECTORY at 5 Hz: case MAVLINK_MODE_CONFIG: // USB // Note: streams requiring low latency come first ... configure_stream_local("BATTERY_STATUS_DEMO", 5.0f); ... It is also possible to add a stream by calling the mavlink module with the stream argument in a startup script. For example, you might add the following line to /ROMFS/px4fmu_common/init.d-posix/px4-rc.mavlink in order to stream BATTERY_STATUS_DEMO at 50Hz on UDP port 14556 (-r configures the streaming rate and -u identifies the MAVLink channel on UDP port 14556). mavlink stream -r 50 -s BATTERY_STATUS_DEMO -u 14556 Streaming on Request Some messages are only needed once, when particular hardware is connected, or under other circumstances. In order to avoid clogging communications links with messages that aren't needed you may not stream all messages by default, even at low rate. If you needed, a GCS or other MAVLink API can request that particular messages are streamed at a particular rate using MAV_CMD_SET_MESSAGE_INTERVAL. A particular message can be requested just once using MAV_CMD_REQUEST_MESSAGE.
09-15
<field type="uint64_t" name="timestamp">Timestamp (microseconds since system boot) <field type="int32_t" name="lat">Latitude (WGS84), in degrees * 1E7 <field type="int32_t" name="lon">Longitude ...
评论
添加红包

请填写红包祝福语或标题

个

红包个数最小为10个

元

红包金额最低5元

当前余额3.43元 前往充值 >
需支付：10.00元
成就一亿技术人!
领取后你会自动成为博主和红包主的粉丝 规则
hope_wisdom
发出的红包
实付元
使用余额支付
点击重新获取
扫码支付
钱包余额 0

抵扣说明：

1.余额是钱包充值的虚拟货币，按照1:1的比例进行支付金额的抵扣。
2.余额无法直接购买下载，可以购买VIP、付费专栏及课程。

余额充值