Linux Commands for Hardware Info - lshw, lspci, lsdev, lscpu, lsblk, lsusb

-
In this post, we will discuss some of the Linux commands for retrieving hardware information. I am using Ubuntu 14.04 as my development machine.

1. lshw -> lshw stands for list hardware. It generates detailed information about various hardware devices present on the system by reading the /proc filesystem.

Running lshw without any commands will generate full information report about all detected hardware.

Note: It should run as root user to get full information

Running "lshw -short" will produce brief information


For more lshw commands, look at this article: https://www.binarytides.com/linux-lshw-command/

2. lspci -> Displays information about the PCI buses in the system and devices connected to them.

Simply run the lspci command to get the PCI information.


Running "lspci -vvv" command will generate verbose output, which also contains the name of the driver for that PCI Device.



Running "lspci -tree" will display the output in tree format,


3. lsdev -> Displays information about installed hardware by gathering information from interrupts, ioports, and dma files in the /proc directory. This command is not present by default, you need to install it by running "sudo apt-get install procinfo"



4. lscpu -> Displays information on CPU Architecture


5. lsblk -> List information about all block devices. Run "lsblk --all"


6. lsusb -> List all usb devices


Comments

Post a Comment

Popular posts from this blog

bb.utils.contains yocto

-
Image
bb.utils.contains  is most commonly used function in Yocto. grep in poky directory returned with 696 count. $ grep -nr 'bb.utils.contains' poky/ | wc -l 696 It's definition is present in 'poky/bitbake/lib/bb/utils.py' file This function returns third argument if the second argument is subset of the first argument else returns fourth argument Let's take an example to understand this. You can see from the above screenshot, when the second argument is a subset of first argument, "present" was returned, else "notpresent" was returned We can also use bb.utils.contains inside if loop. This we can use inside a recipe. if ${@bb.utils.contains('SOMEFLAG','NEWVALUE3','true','false',d)}; then     FOO = 'HELLO' fi
Read more

Difference between RDEPENDS and DEPENDS in Yocto

-
We normally observe these two (RDEPENDS and DEPENDS) whenever we open any recipe. What should we choose when we write our own recipe. DEPENDS -> Build Time Dependency RDEPENDS -> Run Time Dependency DEPENDS: When a recipe 'A' is DEPENDS on recipe 'B'. In this case, Bitbake first builds recipe 'B' and then recipe 'A' E.g. You need 'dbus' to be built before 'wpa_supplicant'. RDEPENDS: When a recipe 'A' is RDEPENDS on recipe 'B'. In this case, Bitbake deploys 'B' on the target system when it deploys 'A'.  E.g. 'perf' RDEPENDS on 'bash' In other words, DEPENDS are those set of packages that should be available while building package, whereas RDEPENDS are set of packages that should be available during execution of the program.
Read more

PR, PN and PV Variable in Yocto

-
PN : Represents the name of the recipe. The name is usually extracted from the recipe file name. PR:  Represents the revision of the recipe. Default value for this revision is "r0". Subsequent revisions of the recipe conventionally will have "r1", "r2" and so on. PV:  Represents the version of the recipe. Normally extracted from the recipe file name. For example: ffmpeg_3.4.2.bb recipe. ${PN} : ffmpeg ${PV} : 3.4.2
Read more