{"id":109153,"date":"2026-01-04T22:47:14","date_gmt":"2026-01-04T22:47:14","guid":{"rendered":"https:\/\/mailinvest.blog\/index.php\/2026\/01\/04\/6-practical-uses-for-the-lspci-command-on-linux\/"},"modified":"2026-01-04T22:48:34","modified_gmt":"2026-01-04T22:48:34","slug":"6-practical-uses-for-the-lspci-command-on-linux","status":"publish","type":"post","link":"https:\/\/mailinvest.blog\/index.php\/2026\/01\/04\/6-practical-uses-for-the-lspci-command-on-linux\/","title":{"rendered":"6 practical uses for the lspci command on Linux"},"content":{"rendered":"

<\/a>\n<\/p>\n

\n

Are you experiencing {hardware} points in your Linux machine? Or perhaps you are simply interested by what data you may collect utilizing terminal instructions? You must attempt these lspci<\/code> command examples.<\/p>\n

<\/p>\n

The lspci<\/code> command line software offers you details about PCI (Peripheral Part Interconnect) bus techniques and gadgets linked to your PC’s motherboard. This contains gadgets reminiscent of your GPU, your Ethernet port, and your Wi-Fi card. In the event you’re acquainted with the ls<\/code> command<\/a>, then you may perceive the command’s identify: “record PCI”. Details about your machine’s inner techniques is just a few keystrokes away with lspci<\/code>. <\/p>\n

<\/p>\n

\n Test all PCI gadgets
\n <\/h2>\n

Essentially the most primary use-case for lspci is getting a printout of all PCI gadgets linked to your system. You possibly can simply run lspci<\/code> by itself to get a quick overview.<\/p>\n

\n
\n \"A\n <\/picture>\n<\/p><\/div>\n<\/p><\/div>\n

You may see each entry seem first with the slot handle, a set of numbers and typically letters distinctive to the machine. There’s additionally a category listed, the seller identify, and the machine identify. You may additionally see subsystem vendor and machine names when subsystems exist. You would possibly see a revision quantity (like “rev 04”) and an related programming language on the finish too.<\/p>\n

Take into account that the gadgets listed below are PCI gadgets. Whereas that features USB controllers, it doesn’t embody USB-connected peripherals. If you wish to see what USB gadgets are plugged into these controllers, then you definitely need the lsusb<\/code> command.<\/p>\n

Equally, in the event you’re attempting to work instantly together with your linked storage gadgets, then it is best to look into the lsblk<\/code> command.<\/p>\n

<\/p>\n

\n Seek for particular gadgets
\n <\/h2>\n

OK, lspci’s output generally is a little overwhelming to eyeball if you’re attempting to determine one thing particular. With an help from the tried and true grep<\/code> command<\/a>, you may search for particular gadgets by search time period.<\/p>\n

For instance, as an example you need to see all USB controllers. Simply run this command:<\/p>\n

lspci | grep \"USB\"<\/code><\/pre>\n
\n
\n                                                                                            \"A\n        <\/picture>\n<\/p><\/div>\n<\/p><\/div>\n
It will filter out all outcomes that do not point out USB within the primary data.<\/p>\n
Search phrases may be difficult although. For instance, your graphics card could or could not point out the phrase “graphics” or “GPU” anyplace in its machine identify. Nevertheless, I do know that the built-in GPU in use on my laptop computer has the phrase Iris in its identify, so I can run this command:<\/p>\n
lspci | grep \"Iris\"<\/code><\/pre>\n
\n
\n                                                                                            \"A\n        <\/picture>\n<\/p><\/div>\n<\/p><\/div>\n
As you may see, I efficiently discovered the iGPU on my laptop computer. It’d take some trial and error to filter appropriately in your Linux system. Strive completely different phrases that you understand could also be related together with your machine.<\/p>\n
\n\"An\n        <\/picture>\n
                    
\n
\n
\t\t
\n\t\t\tHow to List Your Computer’s Devices From the Linux Terminal
\n\t\t<\/a>
\n\t<\/h5>\n
Simpler than ripping it aside. <\/p>\n<\/p><\/div>\n<\/p><\/div>\n
<\/p>\n
\n                        Get detailed data about gadgets
\n               <\/h2>\n
As an example you’ve got recognized an necessary machine. You may use different instructions to get additional data, however lspci<\/code> is able to telling you fairly a bit about them itself in the event you use the verbose choice. This may be helpful particularly when somebody helps you troubleshoot your Linux system, a case the place realizing as a lot as attainable concerning the gadgets in play is at all times useful.<\/p>\n
To get an in depth studying of all gadgets, run lspci<\/code> with the -v<\/code> flag, quick for “verbose”:<\/p>\n
lspci -v<\/code><\/pre>\n
\n
\n                                                                                            \"A\n        <\/picture>\n<\/p><\/div>\n<\/p><\/div>\n
Some data requires root to be viewable, so that you would possibly need to attempt sudo lspci -v<\/code> you probably have permission. In any other case you may see entry denied<\/code> in sure readouts.<\/p>\n
The lspci<\/code> command really has two extra ranges of verbosity you may entry by typing -vv<\/code> or -vvv<\/code>. You may find yourself with a ton of textual content to parse, although. Except you are a developer, you most likely will not achieve something helpful with these printouts.<\/p>\n
    <\/p>\n
If you wish to understand how the gadgets in lspci<\/code>‘s output are associated to one another, you may run the -t<\/code> choice to get every little thing organized right into a “tree.” By default, it can solely present you machine slots, however in the event you enhance verbosity, you may see names too.<\/p>\n
lspci -tv<\/code><\/pre>\n
\n
\n                                                                                            \"A\n        <\/picture>\n<\/p><\/div>\n<\/p><\/div>\n
<\/p>\n
\n                        See which driver your machine is utilizing
\n               <\/h2>\n
Typically it is helpful to know which driver your PCI machine is utilizing. Graphics drivers specifically are a topic of quite a lot of dialogue within the Linux world as a result of the one you’ve gotten put in typically is not the perfect one obtainable.<\/p>\n
Fortuitously, the motive force being utilized by your GPU, or some other machine, is included in lspci<\/code>‘s output. even with out root. For instance, we already recognized the iGPU on my laptop computer earlier at handle 00:02.0<\/code>. I can examine which driver it is utilizing by operating this command:<\/p>\n
lspci -ks 00:02.0<\/code><\/pre>\n
\n
\n                                                                                            \"A\n        <\/picture>\n<\/p><\/div>\n<\/p><\/div>\n
The -k<\/code> flag will get us kernel data whereas, once more, the -s<\/code> flag tells lspci<\/code> you need simply the particular machine situated on the slot that follows.<\/p>\n
\n\"Linux\n        <\/picture>\n
                    
\n
\n
\t\t
\n\t\t\t11 Overlooked Linux Commands You Really Should Be Using
\n\t\t<\/a>
\n\t<\/h5>\n
These instructions might considerably improve your workflow!<\/p>\n<\/p><\/div>\n<\/p><\/div>\n
<\/p>\n
\n                        Get distinctive machine codes
\n               <\/h2>\n
Typically you might want to discover extra details about particular gadgets. lspci<\/code> is ready to provide you with distinctive vendor and machine codes\u2014extra distinctive than simply the machine identify\u2014that you may then lookup on-line or give to the seller if you want specialised help with it.<\/p>\n
All you might want to do is use the -nn<\/code> flag, which will get you vendor and machine names and codes. For instance, I can get that data for my iGPU with this command:<\/p>\n
lspci -nns 00:02.0<\/code><\/pre>\n
\n
\n                                                                                            \"A\n        <\/picture>\n<\/p><\/div>\n<\/p><\/div>\n
You possibly can see the output I get exhibits a set of codes on the finish: 8086:a7a0<\/code>. 8086 is Intel’s vendor code, and a7a0 is the distinctive code for the built-in graphics machine put in in my PC. In the event you do an online seek for these codes, you may discover detailed data about it.<\/p>\n\n
There are quite a lot of instructions for the Linux terminal which can be surprisingly helpful. The traceroute<\/code> command<\/a> could assist you to troubleshoot your web connection, and mastering the systemctl<\/code> command <\/a>will assist you to higher handle the providers operating in your machine.<\/p>\n<\/p><\/div>\n