{"id":322,"date":"2018-08-12T10:27:03","date_gmt":"2018-08-12T07:27:03","guid":{"rendered":"http:\/\/kifarunix.com\/?p=322"},"modified":"2024-03-11T08:18:06","modified_gmt":"2024-03-11T05:18:06","slug":"how-to-check-hardware-information-on-linux","status":"publish","type":"post","link":"https:\/\/kifarunix.com\/how-to-check-hardware-information-on-linux\/","title":{"rendered":"How to Check Hardware information on Linux System"},"content":{"rendered":"\n<figure class=\"wp-block-image size-full\"><img loading=\"lazy\" decoding=\"async\" width=\"1054\" height=\"592\" src=\"https:\/\/kifarunix.com\/wp-content\/uploads\/2018\/08\/check-linux-hardware-information.png\" alt=\"check hardware information on Linux system\" class=\"wp-image-16534\" title=\"\" srcset=\"https:\/\/kifarunix.com\/wp-content\/uploads\/2018\/08\/check-linux-hardware-information.png?v=1683817072 1054w, https:\/\/kifarunix.com\/wp-content\/uploads\/2018\/08\/check-linux-hardware-information-768x431.png?v=1683817072 768w\" sizes=\"(max-width: 1054px) 100vw, 1054px\" \/><\/figure>\n\n\n\n<p>In this tutorial, we will learn how to check hardware information on Linux system. Many a time as we interact with the Linux system in our day to day administrative activities, there may arise a need to check on the mounted filesystems, available block devices, disk space usage, system hardware information or even file space usage. Well, in this tutorial we are going to explore some of the tools that will come in handy while performing such activities.<\/p>\n\n\n\n<p>You may also want to check our previous article on <a href=\"https:\/\/kifarunix.com\/viewing-system-processes-using-ps-and-top-commands\/\" target=\"_blank\" rel=\"noreferrer noopener\">Viewing System Processes using ps and top commands<\/a>.<\/p>\n\n\n\n<div class=\"wp-block-rank-math-toc-block\" id=\"rank-math-toc\"><h2>Table of Contents<\/h2><nav><ul><li><a href=\"#checking-hardware-information-on-linux-system\">Checking Hardware Information on Linux System<\/a><ul><li><a href=\"#lscpu-command\">lscpu Command<\/a><\/li><li><a href=\"#lsusb-command\">lsusb Command<\/a><\/li><li><a href=\"#lshw-command\">lshw Command<\/a><\/li><li><a href=\"#lspci-command\">lspci Command<\/a><\/li><li><a href=\"#lsblk-command\">lsblk Command<\/a><\/li><li><a href=\"#free-command\">free Command<\/a><\/li><li><a href=\"#df-command\">df Command<\/a><\/li><li><a href=\"#hwinfo-command\">hwinfo Command<\/a><\/li><li><a href=\"#dmidecode-command\">dmidecode Command<\/a><\/li><li><a href=\"#hdparm-command\">hdparm Command<\/a><\/li><li><a href=\"#blkid-command\">blkid Command<\/a><\/li><li><a href=\"#ethool-command\">ethool Command<\/a><\/li><li><a href=\"#du-command\">du Command<\/a><\/li><li><a href=\"#findmnt-command\">findmnt Command<\/a><\/li><\/ul><\/li><\/ul><\/nav><\/div>\n\n\n\n<h2 class=\"wp-block-heading\" id=\"checking-hardware-information-on-linux-system\">Checking Hardware Information on Linux System<\/h2>\n\n\n\n<p>There are multiple commands that you can use as a Linux system administrator to check hardware information.<\/p>\n\n\n\n<p>Some of these commands include;<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>lscpu<\/li>\n\n\n\n<li>lsusb<\/li>\n\n\n\n<li>lshw<\/li>\n\n\n\n<li>lspci<\/li>\n\n\n\n<li>lsblk<\/li>\n\n\n\n<li>free<\/li>\n\n\n\n<li>df<\/li>\n\n\n\n<li>hwinfo<\/li>\n\n\n\n<li>dmidecode<\/li>\n\n\n\n<li>hdparm<\/li>\n\n\n\n<li>blkid<\/li>\n\n\n\n<li>ethool<\/li>\n\n\n\n<li>du<\/li>\n\n\n\n<li>findmnt<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\" id=\"lscpu-command\">lscpu Command<\/h3>\n\n\n\n<p><strong>lscpu<\/strong> utility displays information about the CPU cores in the system including their;<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>CPU architecture,<\/li>\n\n\n\n<li>model,<\/li>\n\n\n\n<li>number of cores,<\/li>\n\n\n\n<li>Threads per core<\/li>\n\n\n\n<li>vendor ID, etc.<\/li>\n<\/ul>\n\n\n\n<p>To display this information, just run the command, <strong><code>lscpu<\/code><\/strong>.<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>lscpu<\/code><\/pre>\n\n\n\n<pre class=\"scroll-box\"><code>\nArchitecture:            x86_64\n  CPU op-mode(s):        32-bit, 64-bit\n  Address sizes:         39 bits physical, 48 bits virtual\n  Byte Order:            Little Endian\nCPU(s):                  2\n  On-line CPU(s) list:   0,1\nVendor ID:               GenuineIntel\n  Model name:            Intel(R) Core(TM) i7-10510U CPU @ 1.80GHz\n    CPU family:          6\n    Model:               142\n    Thread(s) per core:  1\n    Core(s) per socket:  2\n    Socket(s):           1\n    Stepping:            12\n    BogoMIPS:            4607.95\n    Flags:               fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush mmx fxsr sse sse2 ht syscall nx rdtscp lm constant_tsc rep_good nop\n                         l xtopology nonstop_tsc cpuid tsc_known_freq pni pclmulqdq ssse3 cx16 pcid sse4_1 sse4_2 x2apic movbe popcnt aes xsave avx rdrand hypervisor lahf_l\n                         m abm 3dnowprefetch invpcid_single pti fsgsbase bmi1 avx2 bmi2 invpcid rdseed clflushopt md_clear flush_l1d arch_capabilities\nVirtualization features: \n  Hypervisor vendor:     KVM\n  Virtualization type:   full\nCaches (sum of all):     \n  L1d:                   64 KiB (2 instances)\n  L1i:                   64 KiB (2 instances)\n  L2:                    512 KiB (2 instances)\n  L3:                    16 MiB (2 instances)\nNUMA:                    \n  NUMA node(s):          1\n  NUMA node0 CPU(s):     0,1\nVulnerabilities:         \n  Itlb multihit:         KVM: Mitigation: VMX unsupported\n  L1tf:                  Mitigation; PTE Inversion\n  Mds:                   Mitigation; Clear CPU buffers; SMT Host state unknown\n  Meltdown:              Mitigation; PTI\n  Mmio stale data:       Mitigation; Clear CPU buffers; SMT Host state unknown\n  Retbleed:              Vulnerable\n  Spec store bypass:     Vulnerable\n  Spectre v1:            Mitigation; usercopy\/swapgs barriers and __user pointer sanitization\n  Spectre v2:            Mitigation; Retpolines, STIBP disabled, RSB filling, PBRSB-eIBRS Not affected\n  Srbds:                 Unknown: Dependent on hypervisor status\n  Tsx async abort:       Not affected\n<\/code><\/pre>\n\n\n\n<p>For more information, check lscpu manual page, <code>lscpu(1)<\/code>.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\" id=\"lsusb-command\">lsusb Command<\/h3>\n\n\n\n<p><strong>lsusb<\/strong> utility is used to display information about USB buses in the system and the devices connected to them.<\/p>\n\n\n\n<p>If used without options, it will display basic information about USB devices and attached devices.<\/p>\n\n\n\n<pre class=\"scroll-box\"><code>\nBus 002 Device 003: ID 5986:0294 Acer, Inc \nBus 002 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub\nBus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub\nBus 001 Device 004: ID 0bda:0129 Realtek Semiconductor Corp. RTS5129 Card Reader Controller\nBus 001 Device 005: ID 0cf3:3005 Qualcomm Atheros Communications AR3011 Bluetooth\nBus 001 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub\nBus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub\nBus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub\nBus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub\n<\/code><\/pre>\n\n\n\n<p>To display additional information, various options can be passed to the lsusb command.<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>-v, &#8211; -verbose<\/strong> \u2013 Display detailed information about the devices shown.<\/li>\n\n\n\n<li><strong>-s [[bus]:][devnum]<\/strong> \u2013 Show only devices in specified bus and\/or device number.<\/li>\n\n\n\n<li><strong>-d [vendor]:[product]<\/strong> \u2013 Show only devices with the specified vendor and product ID.<\/li>\n\n\n\n<li><strong>-D<\/strong> <em>device<\/em> \u2013 Do not scan the \/dev\/bus\/usb directory, instead display only information about the device whose device file is given.<\/li>\n\n\n\n<li><strong>-t<\/strong> \u2013 Dump the physical USB device hierarchy as a tree.<\/li>\n\n\n\n<li><strong>-V, &#8211;version<\/strong> \u2013 Print version information on standard output, then exit successfully.<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\" id=\"lshw-command\">lshw Command<\/h3>\n\n\n\n<p>The command is used to list hardware information in Linux. This command displays detailed information about all the hardware components on the system, including CPU, memory, disks, network interfaces, and more.<\/p>\n\n\n\n<p>It requires to be ran as privileged user to print all details;<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>sudo lshw<\/code><\/pre>\n\n\n\n<pre class=\"scroll-box\"><code>\njellyfish                   \n    description: Computer\n    product: VirtualBox\n    vendor: innotek GmbH\n    version: 1.2\n    serial: 0\n    width: 64 bits\n    capabilities: smbios-2.5 dmi-2.5 smp vsyscall32\n    configuration: family=Virtual Machine uuid=c819f24c-9cf9-4f55-8604-bcdbe2e4289f\n  *-core\n       description: Motherboard\n       product: VirtualBox\n       vendor: Oracle Corporation\n       physical id: 0\n       version: 1.2\n       serial: 0\n     *-firmware\n          description: BIOS\n          vendor: innotek GmbH\n          physical id: 0\n          version: VirtualBox\n          date: 12\/01\/2006\n          size: 128KiB\n          capacity: 128KiB\n          capabilities: isa pci cdboot bootselect int9keyboard int10video acpi\n     *-memory\n          description: System memory\n          physical id: 1\n          size: 2GiB\n<\/code><\/pre>\n\n\n\n<h3 class=\"wp-block-heading\" id=\"lspci-command\">lspci Command<\/h3>\n\n\n\n<p>It is used to display all the information about PCI buses in the system and devices connected to them. If run without options, it will display a brief list of devices.<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>lspci<\/code><\/pre>\n\n\n\n<pre class=\"scroll-box\"><code>\n00:00.0 Host bridge: Intel Corporation 440FX - 82441FX PMC [Natoma] (rev 02)\n00:01.0 ISA bridge: Intel Corporation 82371SB PIIX3 ISA [Natoma\/Triton II]\n00:01.1 IDE interface: Intel Corporation 82371AB\/EB\/MB PIIX4 IDE (rev 01)\n00:02.0 VGA compatible controller: VMware SVGA II Adapter\n00:03.0 Ethernet controller: Intel Corporation 82540EM Gigabit Ethernet Controller (rev 02)\n00:04.0 System peripheral: InnoTek Systemberatung GmbH VirtualBox Guest Service\n00:05.0 Multimedia audio controller: Intel Corporation 82801AA AC'97 Audio Controller (rev 01)\n00:06.0 USB controller: Apple Inc. KeyLargo\/Intrepid USB\n00:07.0 Bridge: Intel Corporation 82371AB\/EB\/MB PIIX4 ACPI (rev 08)\n00:08.0 Ethernet controller: Intel Corporation 82540EM Gigabit Ethernet Controller (rev 02)\n00:0b.0 USB controller: Intel Corporation 82801FB\/FBM\/FR\/FW\/FRW (ICH6 Family) USB2 EHCI Controller\n00:0d.0 SATA controller: Intel Corporation 82801HM\/HEM (ICH8M\/ICH8M-E) SATA Controller [AHCI mode] (rev 02)\n<\/code><\/pre>\n\n\n\n<p>However, there are several options that can be used to tweak the output of the program.<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>-v<\/strong> \u2013 Display detailed information about all devices; can be doubled or tripled (-vv\/-vvv) for more verbosity.<\/li>\n\n\n\n<li><strong>-m<\/strong> \u2013 Dump PCI device data in a backward-compatible machine readable form.<\/li>\n\n\n\n<li><strong>-mm<\/strong> \u2013 Dump PCI device data in a machine readable form for easy parsing by scripts.<\/li>\n\n\n\n<li><strong>-t<\/strong> \u2013 Show a tree-like view of all buses, bridges, devices and connections between them.<\/li>\n\n\n\n<li><strong>-n<\/strong> \u2013 Show PCI vendor and device codes as numbers rather than manufacturer and device names.<\/li>\n\n\n\n<li><strong>-nn<\/strong> \u2013 Show PCI both vendor and device names as well their numeric codes.<\/li>\n\n\n\n<li><strong><code>--version<\/code><\/strong> \u2013 Shows lspci version.<\/li>\n<\/ul>\n\n\n\n<p>For more options, refer to lspci man pages: <code>lspci(8)<\/code><\/p>\n\n\n\n<h3 class=\"wp-block-heading\" id=\"lsblk-command\">lsblk Command<\/h3>\n\n\n\n<p>The <strong><code>lsblk<\/code><\/strong> command is used to list all available block devices, including hard drives, SSDs, and USB drives, on the system. This command displays information about the size, type, and mount point of each device.<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>lsblk<\/code><\/pre>\n\n\n\n<pre class=\"scroll-box\"><code>\nNAME                      MAJ:MIN RM   SIZE RO TYPE MOUNTPOINTS\nloop0                       7:0    0 111.9M  1 loop \/snap\/lxd\/24322\nloop1                       7:1    0  63.3M  1 loop \/snap\/core20\/1778\nloop2                       7:2    0   103M  1 loop \/snap\/lxd\/23541\nloop4                       7:4    0  63.3M  1 loop \/snap\/core20\/1879\nloop5                       7:5    0  49.8M  1 loop \/snap\/snapd\/17950\nloop6                       7:6    0  53.2M  1 loop \/snap\/snapd\/19122\nsda                         8:0    0  39.1G  0 disk \n\u251c\u2500sda1                      8:1    0     1M  0 part \n\u251c\u2500sda2                      8:2    0   1.8G  0 part \/boot\n\u2514\u2500sda3                      8:3    0  37.3G  0 part \n  \u2514\u2500ubuntu--vg-ubuntu--lv 253:0    0  37.3G  0 lvm  \/\nsr0                        11:0    1  1024M  0 rom\n<\/code><\/pre>\n\n\n\n<p>What does each header field mean?<\/p>\n\n\n\n<ol class=\"wp-block-list\">\n<li><code>NAME<\/code>: The name of the block device.<\/li>\n\n\n\n<li><code>MAJ:MIN<\/code>: The major and minor device number of the block device.<\/li>\n\n\n\n<li><code>RM<\/code>: Whether the device is removable or not (0 = not removable, 1 = removable).<\/li>\n\n\n\n<li><code>SIZE<\/code>: The size of the block device in bytes.<\/li>\n\n\n\n<li><code>RO<\/code>: Whether the device is read-only or not (0 = not read-only, 1 = read-only).<\/li>\n\n\n\n<li><code>TYPE<\/code>: The type of the block device (disk, partition, loop etc.).<\/li>\n\n\n\n<li><code>MOUNTPOINT<\/code>: The mount point of the block device, if it is currently mounted.<\/li>\n<\/ol>\n\n\n\n<h3 class=\"wp-block-heading\" id=\"free-command\">free Command<\/h3>\n\n\n\n<p><strong>free<\/strong> command can be used to check memory usage. It displays the total amount of physical and swap memory in the system as well as amount of used, free, shared, cached or in kernel buffers.<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>free<\/code><\/pre>\n\n\n\n<pre class=\"wp-block-code\"><code>               total        used        free      shared  buff\/cache   available\nMem:         2023204     1503376       67860        3692      451968      347500\nSwap:        1914876      114848     1800028<\/code><\/pre>\n\n\n\n<p>The memory information is gathered by parsing \/proc\/meminfo. The displayed columns are:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>total<\/strong>: Total installed memory (MemTotal and SwapTotal in \/proc\/meminfo)<\/li>\n\n\n\n<li><strong>used<\/strong>: Used memory (calculated as total &#8211; free &#8211; buffers &#8211; cache)<\/li>\n\n\n\n<li><strong>free<\/strong>: Unused memory (MemFree and SwapFree in \/proc\/meminfo)<\/li>\n\n\n\n<li><strong>shared<\/strong>: Memory used (mostly) by tmpfs (Shmem in \/proc\/meminfo)<\/li>\n\n\n\n<li><strong>buffers<\/strong>: Memory used by kernel buffers (Buffers in \/proc\/meminfo)<\/li>\n\n\n\n<li><strong>cache<\/strong>: Memory used by the page cache and slabs (Cached and SReclaimable in \/proc\/meminfo)<\/li>\n\n\n\n<li><strong>buff\/cache<\/strong>: Sum of buffers and cache<\/li>\n\n\n\n<li><strong>available<\/strong>: Estimation of how much memory is available for starting new applications, without swapping. Unlike the data provided by the cache or free fields, this field takes into account page cache and also that not all reclaimable memory slabs will be reclaimed due to items being in use (MemAvailable in \/proc\/meminfo, available on kernels 3.14, emulated on kernels 2.6.27+, otherwise the same as free).<\/li>\n<\/ul>\n\n\n\n<p>You can pass the <strong><code>-h, --human<\/code><\/strong> to show all output fields automatically scaled to shortest three digit unit and display the units of print out. Following units are used;<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>B = bytes<\/li>\n\n\n\n<li>Ki = kibibyte<\/li>\n\n\n\n<li>Mi = mebibyte<\/li>\n\n\n\n<li>Gi = gibibyte<\/li>\n\n\n\n<li>Ti = tebibyte<\/li>\n\n\n\n<li>Pi = pebibyte<\/li>\n<\/ul>\n\n\n\n<pre class=\"wp-block-code\"><code>free -h<\/code><\/pre>\n\n\n\n<h3 class=\"wp-block-heading\" id=\"df-command\">df Command<\/h3>\n\n\n\n<p><strong>df<\/strong> utility displays the amount of disk space available on the file system i.e summarizes disk usage on a partition-by-partition basis.<\/p>\n\n\n\n<p>Its syntax is: <code>df [options] [files]<\/code><\/p>\n\n\n\n<p>If run without optons, it can display <strong>filsystems, type of filesystem, their sizes, used space, available space, percentage space usage, mount point<\/strong> of a filesystem.<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>df<\/code><\/pre>\n\n\n\n<pre class=\"scroll-box\"><code>\nFilesystem                        1K-blocks    Used Available Use% Mounted on\ntmpfs                                202324    1152    201172   1% \/run\n\/dev\/mapper\/ubuntu--vg-ubuntu--lv  38366744 8573768  28086940  24% \/\ntmpfs                               1011600       0   1011600   0% \/dev\/shm\ntmpfs                                  5120       0      5120   0% \/run\/lock\n\/dev\/sda2                           1790136  256856   1424020  16% \/boot\ntmpfs                                202320       4    202316   1% \/run\/user\/1000\n<\/code><\/pre>\n\n\n\n<p>Some of the options that can be used to fine-tune the output of the df command include but no limited to:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong><code>-h, --human-readable<\/code><\/strong> \u2013 Print sizes in powers of 1024 (e.g., 1023M).<\/li>\n\n\n\n<li><strong><code>-H, --si<\/code><\/strong> \u2013 Print sizes in powers of 1000 (e.g., 1.1G).<\/li>\n\n\n\n<li><strong><code>-i, --inodes<\/code><\/strong> \u2013 List inode information instead of block usage.<\/li>\n\n\n\n<li><strong><code>-l, --local<\/code><\/strong> \u2013 Limit listing to local file systems.<\/li>\n\n\n\n<li><strong><code>-T, --print-type<\/code><\/strong> \u2013 Print file system type.<\/li>\n\n\n\n<li><strong><code>--help<\/code><\/strong> \u2013 Display help and exit.<\/li>\n\n\n\n<li><strong><code>--version<\/code><\/strong> \u2013 Displays version information and exit.<\/li>\n<\/ul>\n\n\n\n<p>Consult man page, <code>df(1)<\/code>, for more options that can be used.<\/p>\n\n\n\n<p>An Example to display filesystem types in human readable form i.e display sizes in either megabytes or gigabytes instead of blocks;<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>df -hT<\/code><\/pre>\n\n\n\n<pre class=\"scroll-box\"><code>\nFilesystem                        Type   Size  Used Avail Use% Mounted on\ntmpfs                             tmpfs  198M  1.2M  197M   1% \/run\n\/dev\/mapper\/ubuntu--vg-ubuntu--lv ext4    37G  8.2G   27G  24% \/\ntmpfs                             tmpfs  988M     0  988M   0% \/dev\/shm\ntmpfs                             tmpfs  5.0M     0  5.0M   0% \/run\/lock\n\/dev\/sda2                         ext4   1.8G  251M  1.4G  16% \/boot\ntmpfs                             tmpfs  198M  4.0K  198M   1% \/run\/user\/1000\n<\/code><\/pre>\n\n\n\n<h3 class=\"wp-block-heading\" id=\"hwinfo-command\">hwinfo Command<\/h3>\n\n\n\n<p><code><strong>hwinfo<\/strong><\/code> command provides a detailed hardware information about various components of Linux system, such as CPU, memory, hard drives, network cards, and more.<\/p>\n\n\n\n<p>However, it may not be installed by default on all systems and may require root privileges to run.<\/p>\n\n\n\n<p>To install <code>hwinfo<\/code> on Ubuntu or Debian, you can run the following command:<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>sudo apt install hwinfo<\/code><\/pre>\n\n\n\n<p>To install it on CentOS or RHEL, you can use the following command:<\/p>\n\n\n\n<pre class=\"wp-block-preformatted\"><code><code>sudo yum install hwinfo<\/code><\/pre>\n\n\n\n<p>To get a summary of the system's hardware;<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>hwinfo --short<\/code><\/pre>\n\n\n\n<pre class=\"scroll-box\"><code>\ncpu:                                                            \n                       Intel(R) Core(TM) i7-10510U CPU @ 1.80GHz, 2303 MHz\n                       Intel(R) Core(TM) i7-10510U CPU @ 1.80GHz, 2303 MHz\nkeyboard:\n  \/dev\/input\/event2    AT Translated Set 2 keyboard\nmouse:\n  \/dev\/input\/mice      VirtualBox USB Tablet\n  \/dev\/input\/mice      ImExPS\/2 Generic Explorer Mouse\n  \/dev\/input\/mice      VirtualBox mouse integration\ngraphics card:\n                       VMware VMWARE0405\nsound:\n                       Intel 82801AA AC'97 Audio Controller\nstorage:\n                       Intel 82801HM\/HEM (ICH8M\/ICH8M-E) SATA Controller [AHCI mode]\n                       Intel 82371AB\/EB\/MB PIIX4 IDE\nnetwork:\n  enp0s8               Intel PRO\/1000 MT Desktop Adapter\n  enp0s3               Intel PRO\/1000 MT Desktop Adapter\nnetwork interface:\n  enp0s3               Ethernet network interface\n  enp0s8               Ethernet network interface\n  lo                   Loopback network interface\ndisk:\n  \/dev\/sda             VBOX HARDDISK\npartition:\n  \/dev\/sda1            Partition\n  \/dev\/sda2            Partition\n  \/dev\/sda3            Partition\ncdrom:\n  \/dev\/sr0             VBOX CD-ROM\nusb controller:\n                       Apple KeyLargo\/Intrepid USB\n                       Intel 82801FB\/FBM\/FR\/FW\/FRW (ICH6 Family) USB2 EHCI Controller\nbios:\n                       BIOS\nbridge:\n                       Intel 82371SB PIIX3 ISA [Natoma\/Triton II]\n                       Intel 82371AB\/EB\/MB PIIX4 ACPI\n                       Intel 440FX - 82441FX PMC [Natoma]\nhub:\n                       Linux Foundation 2.0 root hub\n                       Linux Foundation 1.1 root hub\nmemory:\n                       Main Memory\nunknown:\n                       FPU\n                       DMA controller\n                       PIC\n                       Keyboard controller\n  \/dev\/input\/mice      InnoTek Systemberatung VirtualBox Guest Service\n<\/code><\/pre>\n\n\n\n<p>You can also get detailed information about a specific hardware component such as cpu, memory, storage, etc;<\/p>\n\n\n\n<p>To show CPU information;<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>hwinfo --cpu<\/code><\/pre>\n\n\n\n<p>Memory;<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>hwinfo --memory<\/code><\/pre>\n\n\n\n<p>Storage;<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>hwinfo --storage<\/code><\/pre>\n\n\n\n<p>USB;<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>hwinfo --usb<\/code><\/pre>\n\n\n\n<p>Sound;<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>hwinfo --sound<\/code><\/pre>\n\n\n\n<p>e.t.c<\/p>\n\n\n\n<h3 class=\"wp-block-heading\" id=\"dmidecode-command\">dmidecode Command<\/h3>\n\n\n\n<p><code>dmidecode<\/code> is a tool for dumping a computer's DMI table contents in a human-readable format. This table contains a description of the system's hardware components, as well as other useful pieces of information such as serial numbers and BIOS revision.<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>To display system's hardware information in brief:<\/li>\n<\/ul>\n\n\n\n<pre class=\"wp-block-preformatted\"><code>sudo dmidecode -t system<\/code><\/pre>\n\n\n\n<ul class=\"wp-block-list\" start=\"2\">\n<li>To display BIOS information:<\/li>\n<\/ul>\n\n\n\n<pre class=\"wp-block-preformatted\"><code>sudo dmidecode -t bios<\/code><\/pre>\n\n\n\n<ul class=\"wp-block-list\" start=\"3\">\n<li>To display processor information:<\/li>\n<\/ul>\n\n\n\n<pre class=\"wp-block-preformatted\"><code>sudo dmidecode -t processor<\/code><\/pre>\n\n\n\n<ul class=\"wp-block-list\" start=\"4\">\n<li>To display memory information:<\/li>\n<\/ul>\n\n\n\n<pre class=\"wp-block-preformatted\"><code>sudo dmidecode -t memory<\/code><\/pre>\n\n\n\n<ul class=\"wp-block-list\" start=\"5\">\n<li>To display information about the system's cache:<\/li>\n<\/ul>\n\n\n\n<pre class=\"wp-block-preformatted\"><code>sudo dmidecode -t cache<\/code><\/pre>\n\n\n\n<ul class=\"wp-block-list\" start=\"6\">\n<li>To display information about the system's baseboard (motherboard):<\/li>\n<\/ul>\n\n\n\n<pre class=\"wp-block-preformatted\"><code>sudo dmidecode -t baseboard<\/code><\/pre>\n\n\n\n<ul class=\"wp-block-list\" start=\"7\">\n<li>To display information about the system's chassis:<\/li>\n<\/ul>\n\n\n\n<pre class=\"wp-block-preformatted\"><code>sudo dmidecode -t chassis<\/code><\/pre>\n\n\n\n<ul class=\"wp-block-list\" start=\"8\">\n<li>To display information about the system's power supply:<\/li>\n<\/ul>\n\n\n\n<pre class=\"wp-block-preformatted\"><code>sudo dmidecode -t power<\/code><\/pre>\n\n\n\n<p>DMI types can also be mapped to number. Check table below;<\/p>\n\n\n\n<figure class=\"wp-block-table\"><table><thead><tr><th>Number<\/th><th>Type<\/th><th>Description<\/th><\/tr><\/thead><tbody><tr><td>0<\/td><td>BIOS<\/td><td>BIOS information<\/td><\/tr><tr><td>1<\/td><td>System<\/td><td>System information<\/td><\/tr><tr><td>2<\/td><td>Base Board<\/td><td>Base board or motherboard information<\/td><\/tr><tr><td>3<\/td><td>Chassis<\/td><td>Chassis information<\/td><\/tr><tr><td>4<\/td><td>Processor<\/td><td>Processor information<\/td><\/tr><tr><td>5<\/td><td>Memory Controller<\/td><td>Memory controller information<\/td><\/tr><tr><td>6<\/td><td>Memory Module<\/td><td>Memory module information<\/td><\/tr><tr><td>7<\/td><td>Cache<\/td><td>Cache information<\/td><\/tr><tr><td>8<\/td><td>Port Connector<\/td><td>Port connector information<\/td><\/tr><tr><td>9<\/td><td>System Slots<\/td><td>Slot information for add-in devices<\/td><\/tr><tr><td>10<\/td><td>On Board Devices<\/td><td>Information about devices integrated into the motherboard<\/td><\/tr><tr><td>11<\/td><td>OEM Strings<\/td><td>OEM-specific information<\/td><\/tr><tr><td>12<\/td><td>System Configuration<\/td><td>System configuration information<\/td><\/tr><tr><td>13<\/td><td>BIOS Language<\/td><td>BIOS language information<\/td><\/tr><tr><td>14<\/td><td>Group Associations<\/td><td>Information about groups of related objects<\/td><\/tr><tr><td>15<\/td><td>System Event Log<\/td><td>System event log information<\/td><\/tr><tr><td>16<\/td><td>Physical Memory Array<\/td><td>Physical memory array information<\/td><\/tr><tr><td>17<\/td><td>Memory Device<\/td><td>Information about a specific memory device<\/td><\/tr><tr><td>18<\/td><td>32-bit Memory Error<\/td><td>Information about 32-bit memory errors<\/td><\/tr><tr><td>19<\/td><td>Memory Array Mapped Address<\/td><td>Mapped address information for a physical memory array<\/td><\/tr><tr><td>20<\/td><td>Memory Device Mapped Address<\/td><td>Mapped address information for a memory device<\/td><\/tr><tr><td>21<\/td><td>Built-in Pointing Device<\/td><td>Information about the built-in pointing device<\/td><\/tr><tr><td>22<\/td><td>Portable Battery<\/td><td>Information about the portable battery<\/td><\/tr><tr><td>23<\/td><td>System Reset<\/td><td>System reset information<\/td><\/tr><tr><td>24<\/td><td>Hardware Security<\/td><td>Hardware security information<\/td><\/tr><tr><td>25<\/td><td>System Power Controls<\/td><td>Information about system power controls<\/td><\/tr><tr><td>26<\/td><td>Voltage Probe<\/td><td>Voltage probe information<\/td><\/tr><tr><td>27<\/td><td>Cooling Device<\/td><td>Cooling device information<\/td><\/tr><tr><td>28<\/td><td>Temperature Probe<\/td><td>Temperature probe information<\/td><\/tr><tr><td>29<\/td><td>Electrical Current Probe<\/td><td>Electrical current probe information<\/td><\/tr><tr><td>30<\/td><td>Out-of-Band Remote Access<\/td><td>Information about out-of-band remote access to the system<\/td><\/tr><tr><td>31<\/td><td>Boot Integrity Services (BIS)<\/td><td>Information about the boot integrity services (BIS)<\/td><\/tr><tr><td>32<\/td><td>System Boot<\/td><td>Information about the system boot process<\/td><\/tr><tr><td>33<\/td><td>Memory Error<\/td><td>Information about memory errors<\/td><\/tr><tr><td>34<\/td><td>Management Device<\/td><td>Management controller information<\/td><\/tr><tr><td>35<\/td><td>Management Device Component<\/td><td>Component information for the management controller<\/td><\/tr><tr><td>36<\/td><td>Management Device Threshold Data<\/td><td>Threshold information for the management controller<\/td><\/tr><tr><td>37<\/td><td>Memory Channel<\/td><td>Information about memory channel<\/td><\/tr><tr><td>38<\/td><td>IPMI Device<\/td><td>IPMI device information<\/td><\/tr><tr><td>39<\/td><td>Power Supply<\/td><td>Power supply information<\/td><\/tr><tr><td>40<\/td><td>Additional Information<\/td><td>Additional system information<\/td><\/tr><tr><td>41<\/td><td>Onboard Device<\/td><td>Onboard device information<\/td><\/tr><tr><td>42<\/td><td>OEM-specific Type<\/td><td>OEM-specific information<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n<p>You can replace the type with a number e.g;<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>sudo dmidecode -t 1<\/code><\/pre>\n\n\n\n<pre class=\"scroll-box\"><code>\n# dmidecode 3.3\nGetting SMBIOS data from sysfs.\nSMBIOS 2.5 present.\n\nHandle 0x0001, DMI type 1, 27 bytes\nSystem Information\n\tManufacturer: innotek GmbH\n\tProduct Name: VirtualBox\n\tVersion: 1.2\n\tSerial Number: 0\n\tUUID: 4cf219c8-f99c-554f-8604-bcdbe2e4289f\n\tWake-up Type: Power Switch\n\tSKU Number: Not Specified\n\tFamily: Virtual Machine\n<\/code><\/pre>\n\n\n\n<h3 class=\"wp-block-heading\" id=\"hdparm-command\">hdparm Command<\/h3>\n\n\n\n<p><code>hdparm<\/code> is a command-line utility in Linux used to view and configure various hard disk drive (HDD) parameters such as reading\/writing speed, power management, security, and more;<\/p>\n\n\n\n<p>View hard disk drive information:<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>sudo hdparm -i \/dev\/sda<\/code><\/pre>\n\n\n\n<pre class=\"scroll-box\"><code>\n\/dev\/sda:\n\n Model=VBOX HARDDISK, FwRev=1.0, SerialNo=VB00c718f1-fb070a44\n Config={ Fixed }\n RawCHS=16383\/16\/63, TrkSize=0, SectSize=512, ECCbytes=0\n BuffType=DualPortCache, BuffSize=256kB, MaxMultSect=128, MultSect=128\n CurCHS=16383\/16\/63, CurSects=16514064, LBA=yes, LBAsects=81920000\n IORDY=yes, tPIO={min:120,w\/IORDY:120}, tDMA={min:120,rec:120}\n PIO modes:  pio0 pio3 pio4 \n DMA modes:  mdma0 mdma1 mdma2 \n UDMA modes: udma0 udma1 udma2 udma3 udma4 udma5 *udma6 \n AdvancedPM=no WriteCache=enabled\n Drive conforms to: unknown:  ATA\/ATAPI-1,2,3,4,5,6\n\n * signifies the current active mode\n<\/code><\/pre>\n\n\n\n<p>Check hard disk read speed:<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>sudo hdparm -t \/dev\/sda<\/code><\/pre>\n\n\n\n<p>Read more on <strong><code>man hdparm<\/code><\/strong>.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\" id=\"blkid-command\">blkid Command<\/h3>\n\n\n\n<p><strong>blkid<\/strong> command displays information such as UUID, filesystem type, volume label about available block devices. For example:<\/p>\n\n\n\n<p>(Remember, you must run blkid with root privileges to view all devices).<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>sudo blkid<\/code><\/pre>\n\n\n\n<pre class=\"scroll-box\"><code>\n\/dev\/mapper\/ubuntu--vg-ubuntu--lv: UUID=\"26b3d004-a446-4510-b0a7-be001dc566ff\" BLOCK_SIZE=\"4096\" TYPE=\"ext4\"\n\/dev\/sda2: UUID=\"d0108361-8ba6-4f1c-bd2b-2729493274b8\" BLOCK_SIZE=\"4096\" TYPE=\"ext4\" PARTUUID=\"31f3e534-b4cc-4231-98cf-8e46f233a7ed\"\n\/dev\/sda3: UUID=\"2l4lAf-vXju-afXg-LfeQ-jcl2-Q3mR-99iXpg\" TYPE=\"LVM2_member\" PARTUUID=\"7cf8f230-4a68-49d6-b0d0-f8117be770cc\"\n\/dev\/loop1: TYPE=\"squashfs\"\n\/dev\/loop6: TYPE=\"squashfs\"\n\/dev\/loop4: TYPE=\"squashfs\"\n\/dev\/loop2: TYPE=\"squashfs\"\n\/dev\/loop0: TYPE=\"squashfs\"\n\/dev\/sda1: PARTUUID=\"03ae84e9-6865-4000-a13d-4ae7923fcffb\"\n\/dev\/loop5: TYPE=\"squashfs\"\n<\/code><\/pre>\n\n\n\n<p>To display specific information about specific block device, pass the device name to blkid. For example, to display information about \/dev\/sda2.<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>sudo blkid \/dev\/sda2<\/code><\/pre>\n\n\n\n<p>To see the options that can be used with blkid, check its man page.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\" id=\"ethool-command\">ethool Command<\/h3>\n\n\n\n<p>ethtool is a command-line utility in Linux that allows users to view and modify network interface controller (NIC) settings. It can be used to check the link status, speed, duplex, and other settings of Ethernet devices.<\/p>\n\n\n\n<p>To check the status of eth0 interface;<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>sudo ethtool enp0s3<\/code><\/pre>\n\n\n\n<pre class=\"scroll-box\"><code>\nSettings for enp0s3:\n\tSupported ports: [ TP ]\n\tSupported link modes:   10baseT\/Half 10baseT\/Full\n\t                        100baseT\/Half 100baseT\/Full\n\t                        1000baseT\/Full\n\tSupported pause frame use: No\n\tSupports auto-negotiation: Yes\n\tSupported FEC modes: Not reported\n\tAdvertised link modes:  10baseT\/Half 10baseT\/Full\n\t                        100baseT\/Half 100baseT\/Full\n\t                        1000baseT\/Full\n\tAdvertised pause frame use: No\n\tAdvertised auto-negotiation: Yes\n\tAdvertised FEC modes: Not reported\n\tSpeed: 1000Mb\/s\n\tDuplex: Full\n\tAuto-negotiation: on\n\tPort: Twisted Pair\n\tPHYAD: 0\n\tTransceiver: internal\n\tMDI-X: off (auto)\n\tSupports Wake-on: umbg\n\tWake-on: d\n        Current message level: 0x00000007 (7)\n                               drv probe link\n\tLink detected: yes\n<\/code><\/pre>\n\n\n\n<p>To change the speed and duplex settings of eth0 to 100Mbps full-duplex;<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>sudo ethtool -s enp0s3 speed 100 duplex full autoneg off<\/code><\/pre>\n\n\n\n<p>To check the driver information and firmware version;<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>sudo ethtool -i enp0s3<\/code><\/pre>\n\n\n\n<p>Read more on <code>man ethool<\/code>.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\" id=\"du-command\">du Command<\/h3>\n\n\n\n<p>Summarize disk usage of the set of FILEs, recursively for directories. It searches the specified directories recursively and reports how much disk space each is consuming.<\/p>\n\n\n\n<p>The basic syntax is: <code>du [options] [directories]<\/code><\/p>\n\n\n\n<p>To display the disk usage for each of the subdirectories in the current working directory, run the command with no option:<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>du<\/code><\/pre>\n\n\n\n<pre class=\"wp-block-code\"><code>40  .\/man\n136 .\/src\n28  .\/src.drivers\/freebsd\n28  .\/src.drivers\n16  .\/<span class=\"hljs-built_in\">test<\/span>\n228 .<\/code><\/pre>\n\n\n\n<p>Some of the options used include:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong><code>-a, --all<\/code><\/strong> \u2013 Write counts for all files, not just directories<\/li>\n\n\n\n<li><strong><code>-c, --total<\/code><\/strong> \u2013 Produce a grand total at the end of its output.<\/li>\n\n\n\n<li><strong><code>-h, --human-readable<\/code><\/strong> \u2013 Print sizes in human readable format (e.g., 2K 110M 34G)<\/li>\n\n\n\n<li><strong><code>--help<\/code><\/strong> \u2013 Display this help and exit<\/li>\n\n\n\n<li><strong><code>--version<\/code><\/strong> \u2013 Displays version information and exit<\/li>\n<\/ul>\n\n\n\n<p>For more options, consult du man page, <code>du(1)<\/code>.<\/p>\n\n\n\n<p>To display grand total in human readable form, pass option -h and -c;<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>du -hc<\/code><\/pre>\n\n\n\n<h3 class=\"wp-block-heading\" id=\"findmnt-command\">findmnt Command<\/h3>\n\n\n\n<p><strong>findmnt<\/strong> command is used to list all mounted filesystems or search for a filesystem along with the information such as target mount point, source device, filesystem type and relevant mount options. If device or mountpoint is not given, all filesystems are shown in the tree-like format.<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>findmnt <\/code><\/pre>\n\n\n\n<pre class=\"scroll-box\"><code>\nTARGET                                        SOURCE                    FSTYPE      OPTIONS\n\/                                             \/dev\/mapper\/ubuntu--vg-ubuntu--lv\n\u2502                                                                       ext4        rw,relatime\n\u251c\u2500\/sys                                        sysfs                     sysfs       rw,nosuid,nodev,noexec,relatime\n\u2502 \u251c\u2500\/sys\/kernel\/security                      securityfs                securityfs  rw,nosuid,nodev,noexec,relatime\n\u2502 \u251c\u2500\/sys\/fs\/cgroup                            cgroup2                   cgroup2     rw,nosuid,nodev,noexec,relatime,nsdelegate,memory_recursiveprot\n\u2502 \u251c\u2500\/sys\/fs\/pstore                            pstore                    pstore      rw,nosuid,nodev,noexec,relatime\n\u2502 \u251c\u2500\/sys\/fs\/bpf                               bpf                       bpf         rw,nosuid,nodev,noexec,relatime,mode=700\n\u2502 \u251c\u2500\/sys\/kernel\/debug                         debugfs                   debugfs     rw,nosuid,nodev,noexec,relatime\n\u2502 \u251c\u2500\/sys\/kernel\/tracing                       tracefs                   tracefs     rw,nosuid,nodev,noexec,relatime\n\u2502 \u251c\u2500\/sys\/fs\/fuse\/connections                  fusectl                   fusectl     rw,nosuid,nodev,noexec,relatime\n\u2502 \u2514\u2500\/sys\/kernel\/config                        configfs                  configfs    rw,nosuid,nodev,noexec,relatime\n\u251c\u2500\/proc                                       proc                      proc        rw,nosuid,nodev,noexec,relatime\n\u2502 \u2514\u2500\/proc\/sys\/fs\/binfmt_misc                  systemd-1                 autofs      rw,relatime,fd=29,pgrp=1,timeout=0,minproto=5,maxproto=5,direct,pipe_ino=18763\n\u2502   \u2514\u2500\/proc\/sys\/fs\/binfmt_misc                binfmt_misc               binfmt_misc rw,nosuid,nodev,noexec,relatime\n\u251c\u2500\/dev                                        udev                      devtmpfs    rw,nosuid,relatime,size=953340k,nr_inodes=238335,mode=755,inode64\n\u2502 \u251c\u2500\/dev\/pts                                  devpts                    devpts      rw,nosuid,noexec,relatime,gid=5,mode=620,ptmxmode=000\n\u2502 \u251c\u2500\/dev\/shm                                  tmpfs                     tmpfs       rw,nosuid,nodev,inode64\n\u2502 \u251c\u2500\/dev\/hugepages                            hugetlbfs                 hugetlbfs   rw,relatime,pagesize=2M\n\u2502 \u2514\u2500\/dev\/mqueue                               mqueue                    mqueue      rw,nosuid,nodev,noexec,relatime\n\u251c\u2500\/run                                        tmpfs                     tmpfs       rw,nosuid,nodev,noexec,relatime,size=202324k,mode=755,inode64\n\u2502 \u251c\u2500\/run\/lock                                 tmpfs                     tmpfs       rw,nosuid,nodev,noexec,relatime,size=5120k,inode64\n\u2502 \u251c\u2500\/run\/credentials\/systemd-sysusers.service none                      ramfs       ro,nosuid,nodev,noexec,relatime,mode=700\n\u2502 \u251c\u2500\/run\/snapd\/ns                             tmpfs[\/snapd\/ns]          tmpfs       rw,nosuid,nodev,noexec,relatime,size=202324k,mode=755,inode64\n\u2502 \u2502 \u2514\u2500\/run\/snapd\/ns\/lxd.mnt                   nsfs[mnt:[4026532273]]    nsfs        rw\n\u2502 \u2514\u2500\/run\/user\/1000                            tmpfs                     tmpfs       rw,nosuid,nodev,relatime,size=202320k,nr_inodes=50580,mode=700,uid=1000,gid=1000,inode64\n\u251c\u2500\/snap\/lxd\/24322                             \/dev\/loop0                squashfs    ro,nodev,relatime,errors=continue\n\u251c\u2500\/snap\/core20\/1778                           \/dev\/loop1                squashfs    ro,nodev,relatime,errors=continue\n\u251c\u2500\/snap\/lxd\/23541                             \/dev\/loop2                squashfs    ro,nodev,relatime,errors=continue\n\u251c\u2500\/snap\/core20\/1879                           \/dev\/loop4                squashfs    ro,nodev,relatime,errors=continue\n\u251c\u2500\/snap\/snapd\/17950                           \/dev\/loop5                squashfs    ro,nodev,relatime,errors=continue\n\u251c\u2500\/boot                                       \/dev\/sda2                 ext4        rw,relatime\n\u2514\u2500\/snap\/snapd\/19122                           \/dev\/loop6                squashfs    ro,nodev,relatime,errors=continue\n<\/code><\/pre>\n\n\n\n<p>Read more on <strong><code>man findmnt<\/code><\/strong>.<\/p>\n\n\n\n<p>That concludes our guide on checking hardware information on Linux system.<\/p>\n","protected":false},"excerpt":{"rendered":"<p>In this tutorial, we will learn how to check hardware information on Linux system. Many a time as we interact with the Linux system in<\/p>\n","protected":false},"author":1,"featured_media":16534,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"rank_math_lock_modified_date":false,"footnotes":""},"categories":[49],"tags":[56,6649,54,53,59,58,6650,60,57,55,61],"class_list":["post-322","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-command-cheatsheets","tag-blkid","tag-check-linux-hardware-information","tag-df","tag-du","tag-findmnt","tag-free","tag-linux-hardware-information","tag-lsblk","tag-lscpu","tag-lspci","tag-lsusb","generate-columns","tablet-grid-50","mobile-grid-100","grid-parent","grid-50","resize-featured-image"],"_links":{"self":[{"href":"https:\/\/kifarunix.com\/wp-json\/wp\/v2\/posts\/322"}],"collection":[{"href":"https:\/\/kifarunix.com\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/kifarunix.com\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/kifarunix.com\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/kifarunix.com\/wp-json\/wp\/v2\/comments?post=322"}],"version-history":[{"count":8,"href":"https:\/\/kifarunix.com\/wp-json\/wp\/v2\/posts\/322\/revisions"}],"predecessor-version":[{"id":20963,"href":"https:\/\/kifarunix.com\/wp-json\/wp\/v2\/posts\/322\/revisions\/20963"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/kifarunix.com\/wp-json\/wp\/v2\/media\/16534"}],"wp:attachment":[{"href":"https:\/\/kifarunix.com\/wp-json\/wp\/v2\/media?parent=322"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/kifarunix.com\/wp-json\/wp\/v2\/categories?post=322"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/kifarunix.com\/wp-json\/wp\/v2\/tags?post=322"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}