Commands using lspci sorted by votes

Commands using lspci (11)

sorted by

list your device drivers

great for running off a bootable cd to identify hardware other os's can't detect
This is sample output - yours may be different.
5

lspci -vv

kumara · 2009-02-05 13:01:41 25
Show number of NIC's, ports per nic and PCI address
This is sample output - yours may be different.
3

lspci | grep Ether | awk '{ VAR=$1; split(VAR,ARR,"."); count[ARR[1]]++; LINE=$0; split(LINE,LINEARR,":"); LINECOUNT[ARR[1]]=LINEARR[3]; } END { for(i in count) { printf("PCI address: %s\nPorts: %d\nCard Type: %s\n", i, count[i], LINECOUNT[i]) } }'

bpfx · 2009-02-05 14:24:59 84

Get information on your graphics card on linux (such as graphics memory size)

probably only works if you have one graphics card. used this: http://www.cyberciti.biz/faq/howto-find-linux-vga-video-card-ram/ as reference can be expanded, for example: lspci -v -s `lspci | awk '/VGA/{print $1}'` | sed -n '/Memory.*, prefetchable/s/.*\[size=$[^]]\+$\]/\1/p' will just get the amount of prefetchable memory compare to: lshw -C display which does not give the size (it does give byte ranges and you could calculate the size from that, but that's a pain) Also uses a command which is not standard on linux; wheras lspci is a core utility provided by most systems Show Sample Output

lspci -v -s `lspci | awk '/VGA/{print $1}'`

infinull · 2010-10-26 17:45:14 10

Find your graphics chipset

Displays only the VGA adapter/chipset being used for the graphics. In this case, it gave me the "M22" and "Mobility Radeon x300" that I needed to research a graphics issue I was having. Show Sample Output
This is sample output - yours may be different.
```
~$ lspci |grep VGA
01:00.0 VGA compatible controller: ATI Technologies Inc M22 [Mobility Radeon X300]
```
1

lspci |grep VGA

CafeNinja · 2009-04-28 08:34:42 9
Show display adapter, available drivers, and driver in use
This is sample output - yours may be different.
1

lspci -v | perl -ne '/VGA/../^$/ and /VGA|Kern/ and print'

unixmonkey5248 · 2009-09-05 11:26:26 3
Get block device mapped parent PCI controller

Maps block devices to the PCIe nodes
This is sample output - yours may be different.
0

udevadm info -q all -n /dev/sdb | grep ID_PATH | cut -d'-' -f 2 | xargs -n 1 lspci -s

bp · 2014-02-18 06:23:39 8
Remap Nic aliases from PCI location

for redhat systems works sometimes :S tested on dell poweredge r7+ systems
This is sample output - yours may be different.
0

lspci -vv | grep 'Ethernet\|Serial' | awk 'NR == 1{ printf $1 } NR == 2 { print " mac " $7 }' | sed ?e 's/-/:/g' -e 's/:f[ef]:f[ef]//g' -e 's/01:00.0/eth0/g' -e 's/01:00.1/eth1/g' -e 's/01:00.2/eth2/g' -e 's/01:00.3/eth3/g' > /etc/iftab && ifrename

PROJAK_SX · 2014-03-01 20:07:18 7
Find which fibre HBA a disk is connected to

Useful for big systems with lots of cards. (Update: does not work with USB disks)
This is sample output - yours may be different.
0

udevadm info -q all -n /dev/sdc | grep ID_PATH | cut -d'-' -f 2 | xargs -n 1 lspci -s

mhs · 2015-01-27 15:34:02 9
lspci | grep -i pci

Get information pci All
This is sample output - yours may be different.
-1

lspci | grep -i pci

fekrhdesigns · 2012-04-14 15:14:41 19
get basic information out of your computer
This is sample output - yours may be different.
-3

lspci

theIndianMaiden · 2009-08-16 02:01:58 3
Find out how much ram memory has your video (graphic) card

One liner is based on this article: https://www.computerhope.com/issues/ch001307.htm Show Sample Output
This is sample output - yours may be different.
```
$ lspci|grep -i "VGA Compatible Controller"|cut -d' ' -f1|xargs lspci -v -s|grep ' prefetchable'
        Memory at e0000000 (64-bit, prefetchable) [size=256M]
```
-4

lspci|grep -i "VGA Compatible Controller"|cut -d' ' -f1|xargs lspci -v -s|grep ' prefetchable'

knoppix5 · 2020-09-11 14:04:10 297

What's this?

commandlinefu.com is the place to record those command-line gems that you return to again and again. That way others can gain from your CLI wisdom and you from theirs too. All commands can be commented on, discussed and voted up or down.

Share Your Commands

Check These Out

set your screensaver as your desktop background MAC OSX

Grep syslog today last hour

Uses date to grep de logfile for today and uses it to get the last hour logs. Can be used to get last minute logs or today's logs.

Check if *hardware* is 32bit or 64bit

This command tell you if your hardware is 32 or 64 bits even if you install a 32bits OS on a 64 bits hardware. If your distro don't support the -q switch, try doing : $ grep &>/dev/null '\' /proc/cpuinfo && echo 64 bits || echo 32 bits

Print the current time on the whole screen, updated every second

http://www.joachim-breitner.de/projects#screen-message now also supports reading stdin continuously to update what it shows, different ?slides? separated by a form feed character. Here, we feed the current time into it each second to create a large clock.

Get the size of all the directories in current directory

OSX's BSD version of the du command uses the -d argument instead of --max-depth.

view the system memory in clear text

see what's in your memory right now... sometimes you find passwords, account numbers and url's that were recently used. Anyone have a safe command to clear the memory without rebooting?

Check if port is open on remote machine

Check if port is open, if you don't have ncat on your machine.

Get the Nth argument of the last command (handling spaces correctly)

Bash's history expansion character, "!", has many features, including "!:" for choosing a specific argument (or range of arguments) from the history. The gist is any number after !: is the number of the argument you want, with !:1 being the first argument and !:0 being the command. See the sample output for a few examples. For full details search for "^HISTORY EXPANSION" in the bash(1) man page. Note that this version improves on the previous function in that it handles arguments that include whitespace correctly.

Monitor incoming connections of proxies and balancers.

Maybe this will help you to monitor your load balancers or reverse proxies if you happen to use them. This is useful to discover TIME OUTS and this will let you know if one or more of your application servers is not connected by checking.

Check command history, but avoid running it

!whatever will search your command history and execute the first command that matches 'whatever'. If you don't feel safe doing this put :p on the end to print without executing. Recommended when running as superuser.

Stay in the loop…

Follow the Tweets.

Every new command is wrapped in a tweet and posted to Twitter. Following the stream is a great way of staying abreast of the latest commands. For the more discerning, there are Twitter accounts for commands that get a minimum of 3 and 10 votes - that way only the great commands get tweeted.

» http://twitter.com/commandlinefu
» http://twitter.com/commandlinefu3
» http://twitter.com/commandlinefu10

Subscribe to the feeds.

Use your favourite RSS aggregator to stay in touch with the latest commands. There are feeds mirroring the 3 Twitter streams as well as for virtually every other subset (users, tags, functions,…):

Subscribe to the feed for:

» all commands
» commands with 3 up-votes (commandlinefu3)
» commands with 10 up-votes (commandlinefu10)
» commands using lspci

Commands using lspci (11) the last day the last week the last month all time sorted by date votes

What's this?

Check These Out

Stay in the loop…

Commands using lspci (11)

sorted by