How to get the GPU info?How do I find out the model of my graphics card?How do I check if Ubuntu is using my...
Calculating the number of days between 2 dates in Excel
How can a jailer prevent the Forge Cleric's Artisan's Blessing from being used?
Simple image editor tool to draw a simple box/rectangle in an existing image
A workplace installs custom certificates on personal devices, can this be used to decrypt HTTPS traffic?
Invariance of results when scaling explanatory variables in logistic regression, is there a proof?
What if somebody invests in my application?
How will losing mobility of one hand affect my career as a programmer?
Are taller landing gear bad for aircraft, particulary large airliners?
Books on the History of math research at European universities
Hostile work environment after whistle-blowing on coworker and our boss. What do I do?
What is the opposite of 'gravitas'?
Should my PhD thesis be submitted under my legal name?
How can I successfully establish a nationwide combat training program for a large country?
Can a malicious addon access internet history and such in chrome/firefox?
Teaching indefinite integrals that require special-casing
Stereotypical names
I2C signal and power over long range (10meter cable)
The One-Electron Universe postulate is true - what simple change can I make to change the whole universe?
Science Fiction story where a man invents a machine that can help him watch history unfold
"lassen" in meaning "sich fassen"
Bob has never been a M before
Visiting the UK as unmarried couple
Golf game boilerplate
Why are on-board computers allowed to change controls without notifying the pilots?
How to get the GPU info?
How do I find out the model of my graphics card?How do I check if Ubuntu is using my NVIDIA graphics card?Terminal splash screen with Weather, Calendar, Time & Sysinfo?How to see what technologies a video card supportsHow to get second and third GPU working on 18.04How can I find the memory usage on my GPU?Switching on and off integrated GPUIntel GPU Monitor and OverclockingHow to find out which NVIDIA GPU I haveWhat is the best way of monitoring GPU temperature in Xubuntu 14.04 when using the OpenSource driver?Where can I find the right GPU driver for a MSI M670 notebook runnig Ubuntu 14.04.2?Dual GPU NVIDIA 940m + Intel Sky LakeVM Gaming via GPU Passthrough without a dedicated monitor?Is a remote X session GPU accelerated? Separate VMs for session and GPU renderingNvidia-smi low GPU Utilization
I'm looking for a command that would give me the same info as:
cat /proc/cpuinfo
Except for the GPU (type of the chip and memory, frequency).
command-line graphics gpu
add a comment |
I'm looking for a command that would give me the same info as:
cat /proc/cpuinfo
Except for the GPU (type of the chip and memory, frequency).
command-line graphics gpu
what does:cat /proc/cpuinfo
do? what info are you looking for?
– Charlie Parker
Mar 5 '18 at 17:00
add a comment |
I'm looking for a command that would give me the same info as:
cat /proc/cpuinfo
Except for the GPU (type of the chip and memory, frequency).
command-line graphics gpu
I'm looking for a command that would give me the same info as:
cat /proc/cpuinfo
Except for the GPU (type of the chip and memory, frequency).
command-line graphics gpu
command-line graphics gpu
edited Dec 15 '17 at 1:36
muru
1
1
asked Oct 9 '10 at 17:14
user2413user2413
4,071133962
4,071133962
what does:cat /proc/cpuinfo
do? what info are you looking for?
– Charlie Parker
Mar 5 '18 at 17:00
add a comment |
what does:cat /proc/cpuinfo
do? what info are you looking for?
– Charlie Parker
Mar 5 '18 at 17:00
what does:
cat /proc/cpuinfo
do? what info are you looking for?– Charlie Parker
Mar 5 '18 at 17:00
what does:
cat /proc/cpuinfo
do? what info are you looking for?– Charlie Parker
Mar 5 '18 at 17:00
add a comment |
18 Answers
18
active
oldest
votes
That type of information is non-standard, and the tools you will use to gather it vary widely.
The command glxinfo
will give you all available OpenGL information for the graphics processor, including its vendor name, if the drivers are correctly installed.
To get clock speed information, there is no standard tool.
- For ATI/AMD GPUs,
aticonfig --odgc
will fetch the clock rates, andaticonfig --odgt
will fetch the temperature data. - For NVIDIA GPUs, the
nvclock
program will fetch the same information.
I am not aware of an equivalent tool for the open source drivers or for Intel or other GPUs.
Other information on the hardware can be fetched from the lspci
and lshw
tools.
1
How to install glxinfo?
– stiv
Mar 13 '15 at 13:40
5
@stiv: It's part of the Mesa library, and comes with the packagemesa-utils
on Ubuntu.
– greyfade
Mar 13 '15 at 18:20
2
aticonfig
doesn't appear to be available since the retirement of fglrx.nvclock
also appears to have been abandoned since the last version was for trusty. Do you have any updated solutions? Here's what I have so far..
– Elder Geek
Dec 14 '17 at 23:16
2
glxinfo | grep "Device"
worked well enough for me on an Intel GPU
– John Hamilton
May 26 '18 at 14:10
I use:glxinfo | egrep -i 'device|memory'
– danger89
Jan 2 at 20:37
|
show 2 more comments
I do not know of a direct equivalent, but lshw should give you the info you want, try:
sudo lshw -C display
(it also works without sudo
but the info may be less complete/accurate)
You can also install the package lshw-gtk
to get a GUI.
3
Had to put gksu before the command in the menu to get lshw-gtk to work.
– robin0800
Feb 15 '11 at 10:55
Any updates? I'm a fan of the command but the only clock rate (frequency) it seems to provide for me is the base bus clock 33MHz. I'm attempting to bring this Q&A up to date. Thank you!
– Elder Geek
Dec 14 '17 at 23:31
Apologies, new to Deep Learning. What should it say if I have a GPU? It saysproduct: 2nd Generation Core Processor Family Integrated Graphics Controller
– frank
Apr 17 '18 at 2:13
add a comment |
A blog post focussing on work done on the command-line is here:
http://www.cyberciti.biz/faq/howto-find-linux-vga-video-card-ram/
Find out the device ID:
lspci | grep ' VGA ' | cut -d" " -f 1
03:00.0
You can then use this output with lspci
again, forming two nested commands
lspci -v -s $(lspci | grep ' VGA ' | cut -d" " -f 1)
If you have more than 1 GPU card, try this equivalent command instead:
lspci | grep ' VGA ' | cut -d" " -f 1 | xargs -i lspci -v -s {}
Output from my system:
03:00.0 VGA compatible controller: NVIDIA Corporation G98 [Quadro NVS 295] (rev a1) (prog-if 00 [VGA controller])
Subsystem: NVIDIA Corporation Device 062e
Flags: bus master, fast devsel, latency 0, IRQ 24
Memory at f6000000 (32-bit, non-prefetchable) [size=16M]
Memory at ec000000 (64-bit, prefetchable) [size=64M]
Memory at f4000000 (64-bit, non-prefetchable) [size=32M]
I/O ports at dc80 [size=128]
[virtual] Expansion ROM at f7e00000 [disabled] [size=128K]
Capabilities: <access denied>
Kernel driver in use: nvidia
EDIT: You can avoid the <access denied>
by launching with sudo
So, (prefetchable) [size=64M)
indicates that I have a 64-MB NVIDIA card. However, I don't, it's rather 256 MB. Why? see below.
To see how to get the most info+performance out of it, read an extremely comprehensive article on the Arch-Linux Wiki
https://wiki.archlinux.org/index.php/NVIDIA
For nvidia users, start with
nvidia-smi
(This works with the Nvidia drivers installed,but not with systems running the open-source 'nouveau' driver).
Output
Thu Dec 19 10:54:18 2013
+------------------------------------------------------+
| NVIDIA-SMI 5.319.60 Driver Version: 319.60 |
|-------------------------------+----------------------+----------------------+
| GPU Name Persistence-M| Bus-Id Disp.A | Volatile Uncorr. ECC |
| Fan Temp Perf Pwr:Usage/Cap| Memory-Usage | GPU-Util Compute M. |
|===============================+======================+======================|
| 0 Quadro NVS 295 Off | 0000:03:00.0 N/A | N/A |
| N/A 73C N/A N/A / N/A | 252MB / 255MB | N/A Default |
+-------------------------------+----------------------+----------------------+
+-----------------------------------------------------------------------------+
| Compute processes: GPU Memory |
| GPU PID Process name Usage |
|=============================================================================|
| 0 Not Supported |
+-----------------------------------------------------------------------------+
This indicates that I have a 256 MB GDDR3 Graphics card.
At this time, I don't know how to get this for Intel and AMD/ATI GPUs.
12
+1 fornvidia-smi
(that should be highlighted a bit in my opinion)
– Martin Thoma
Sep 7 '14 at 15:23
If anyone have any idea: nvidia-smi hangs indefinitely: what could be the issue?
– Franck Dernoncourt
Aug 9 '16 at 15:50
2
This should really be the accepted answer!
– INElutTabile
Mar 27 '18 at 11:26
nvidia-smi
not showing me full GPU name.
– mrgloom
Nov 24 '18 at 15:15
add a comment |
Run google-chrome
and navigate to the URL about:gpu
.
If chrome has figured out how to use OpenGL, you will get extremely detailing information about your GPU.
1
This also works in Chromium (chromium-browser
).
– Eliah Kagan
Jul 2 '17 at 13:02
Clever. Along these lines I additionally went to chromeexperiments.com to see the performance there. Smooth as butter - I'm definitely on gpu
– Jacksonkr
Jul 29 '18 at 17:49
add a comment |
For Nvidia cards.
1st GPU
> cat /proc/driver/nvidia/gpus/0/information
Model: GeForce GTX 680
IRQ: 24
GPU UUID: GPU-71541068-cded-8a1b-1d7e-a093a09e9842
Video BIOS: 80.04.09.00.01
Bus Type: PCIe
DMA Size: 40 bits
DMA Mask: 0xffffffffff
Bus Location: 0000:01.00.0
2nd GPU
> cat /proc/driver/nvidia/gpus/1/information
Model: GeForce GTX 580
IRQ: 33
GPU UUID: GPU-64b1235c-51fc-d6f1-0f0e-fa70320f7a47
Video BIOS: 70.10.20.00.01
Bus Type: PCIe
DMA Size: 40 bits
DMA Mask: 0xffffffffff
Bus Location: 0000:08.00.0
6
Thanks! (thoughcat /proc/driver/nvidia/gpus/0000:01:00.0/information
for me)
– matt wilkie
Nov 24 '15 at 3:54
This is the only correct answer in on-demand cloud/HPC cluster environment on which glxinfo or lspci both fail (the former because there's no OpenGL and display, the latter because the nVidia graphics card is abstracted by a graphics controller like Matrox G200eW3). The folder name under gpus is0000:3b:00.0
or0000:d8:00.0
for me, so we should type:cat /proc/driver/nvidia/gpus/0000:3b:00.0/information
. The lovelyTesla V100-PCIE-16GB
model shows that theqsub
job limit is satisfied as desired.
– user5280911
Oct 6 '18 at 7:40
add a comment |
clinfo
sudo apt-get install clinfo
clinfo
is the analogue of glxinfo
but for OpenCL.
nvidia-settings
Mixes runtime with some static info.
More details: How do I check if Ubuntu is using my NVIDIA graphics card?
add a comment |
For Nvidia cards, type
nvidia-smi -q
add a comment |
I do believe the best option for this is neofetch.
# Get neofetch
sudo add-apt-repository ppa:dawidd0811/neofetch
sudo apt update
sudo apt get neofetch
# Run neofetch
neofetch
This gives an output like this:
3
I'm not seeing the video card frequency and memory in this answer. There are far simpler methods to obtain the model of GPU which appears to be all you are giving us. I'm not sure what this adds to the existing answers.
– Elder Geek
Dec 10 '17 at 17:16
Thescreenfetch
program does the same thing and doesn't require a PPA to install.
– Braden Best
Jan 30 '18 at 19:31
It's a shell script. Plus I linked to its github as well so you can just use it as a script.
– HaoZeke
Jan 30 '18 at 19:36
Here's screenfetch: github.com/KittyKatt/screenFetch
– Camille Goudeseune
Feb 7 '18 at 21:31
add a comment |
Just to find the basics, according to https://wiki.debian.org/NvidiaGraphicsDrivers#NVIDIA_Proprietary_Driver,
lspci | grep VGA
If you need more detail than that, see @knb's answer to this same question.
add a comment |
This is really not that complex For model and memory, here's a 1 liner that works for every video card I've tested it on regardless of manufacturer (Intel, AMD, NVIDIA):
GPU=$(lspci | grep VGA | cut -d ":" -f3);RAM=$(cardid=$(lspci | grep VGA |cut -d " " -f1);lspci -v -s $cardid | grep " prefetchable"| cut -d "=" -f2);echo $GPU $RAM
GPU= All this bit does is grab the 3rd field from 'lspci' output filtered via 'grep' for VGA which corresponds to the video chip.
RAM= All this bit does is set variable cardid
equal to the first field of output from lspci
matching "VGA" and feeds that as a request for -v
verbose output from lspci
for that specific -s
device, further filtering the output by grep
for the string " prefetchable" as this contains the memory on the card itself (note the preceding space as we don't want to match "non-prefetchable" in our output.
For clock rate on Intel integrated graphics (Tested on I3 and I5)
execute the command sudo find /sys -type f -name gt_cur* -print0 | xargs -0 cat
This dives into the /sys tree to locate the gt_cur_freq_mhz
file which on my I3 is /sys/devices/pci0000:00/0000:00:02.0/drm/card0/gt_cur_freq_mhz
and prints the content. which in my case under extremely light load is 350
as in 350 MHz which corresponds to the minimum frequency found in /sys/devices/pci0000:00/0000:00:02.0/drm/card0/gt_min_freq_mhz
and when running glxgears
and glmark2
results in
1050
as in 1050 MHz which corresponds to the maximum frequency found in /sys/devices/pci0000:00/0000:00:02.0/drm/card0/gt_max_freq_mhz
For clock rates on nvidia cards:
nvidia-smi -stats -d procClk
corresponds to the GPU clock
nvidia-smi -stats -d memClk
corresponds to the memory clock.
Note: I am unable to test the above as my trusty GeForce 210 isn't supported and this works only on Kepler or newer GPUs as indicated by
`nvidia-smi -stats --help'
I do not currently have any solutions for clock rate on AMD cards and do not have the hardware available for testing. I will however say that to the best of my knowledge the aticonfig
mentioned in the accepted answer no longer exists and it appears that nvclock
isn't available for anything since trusty.
add a comment |
In addition to neofetch
answered previously, there is screenfetch
which looks a lot nicer (IMO). Plus another answer mentions he doesn't know how to get iGPU listed and this does it:
For details on setup see: How can I get this terminal splash screen?
In summary just for the bottom section with Ubuntu display containing GPU information (second last line) use:
sudo apt install screenfetch
screenfetch
You'll want to put the screenfetch
command an the bottom of your ~/.bashrc
file to have it appear every time you open the terminal.
add a comment |
If you're running Ubuntu on a Chromebook with crouton, the only one of the answers that will work is going to chrome://gpu
in the Chrome browser.
add a comment |
For the Intel GMA950 (comes with EeePC in particular) you can run:
setpci -s 00:02.0 f0.b
which will return '00' for 200MHz, '01' for 250MHz or '03' for 400MHz. You may be able to apply the same principle to other Intel cards.
add a comment |
If you would like to have simple information, you could try gpustat. It is very good and simple.
add a comment |
If you have a AMD Radeon Card, you may want to run the following commands
sudo update-pciids #optional command, requires internet
lspci -nn | grep -E 'VGA|Display'
It should report something like this
00:01.0 VGA compatible controller [0300]: Advanced Micro Devices, Inc. [AMD/ATI] Wani [Radeon R5/R6/R7 Graphics] [1002:9874] (rev c5)
03:00.0 Display controller [0380]: Advanced Micro Devices, Inc. [AMD/ATI] Sun XT [Radeon HD 8670A/8670M/8690M / R5 M330 / M430 / R7 M520] [1002:6660] (rev ff)
add a comment |
For nvidia GPUs, nvidia-smi
command is your friend.
See man nvidia-smi
if you like to.
For listing GPUs use nvidia-smi -L
(nvidia-smi --list-gpus
),
nvidia-smi -q
give information about the gpu and the running processes.
add a comment |
Use lspci
, lspci -v
to get basic info see here.
In my case for ex once I run lspci
and I have got :
dina@dina-X450LA:~$ lspci
00:02.0 VGA compatible controller: Intel Corporation Haswell-ULT Integrated Graphics Controller (rev 0b)
00:03.0 Audio device: Intel Corporation Haswell-ULT HD Audio Controller (rev 0b)
00:14.0 USB controller: Intel Corporation 8 Series USB xHCI HC (rev 04)
00:16.0 Communication controller: Intel Corporation 8 Series HECI #0 (rev 04)
00:1b.0 Audio device: Intel Corporation 8 Series HD Audio Controller (rev 04)
00:1c.0 PCI bridge: Intel Corporation 8 Series PCI Express Root Port 1 (rev e4)
00:1c.2 PCI bridge: Intel Corporation 8 Series PCI Express Root Port 3 (rev e4)
00:1c.3 PCI bridge: Intel Corporation 8 Series PCI Express Root Port 4 (rev e4)
00:1d.0 USB controller: Intel Corporation 8 Series USB EHCI #1 (rev 04)
00:1f.0 ISA bridge: Intel Corporation 8 Series LPC Controller (rev 04)
00:1f.2 SATA controller: Intel Corporation 8 Series SATA Controller 1 [AHCI mode] (rev 04)
00:1f.3 SMBus: Intel Corporation 8 Series SMBus Controller (rev 04)
02:00.0 Ethernet controller: Qualcomm Atheros QCA8171 Gigabit Ethernet (rev 10)
03:00.0 Network controller: Ralink corp. RT3290 Wireless 802.11n 1T/1R PCIe
03:00.1 Bluetooth: Ralink corp. RT3290 Bluetooth
add a comment |
In order to get all the information about the graphics processor, you can use the following command as specified by @greyfade.
> glxinfo
However, if the program glxinfo
is currently not installed, you can install it by typing:
> sudo apt install mesa-utils
You will also have to enable the component called universe
. Once this is done, glxinfo
will list all the specifications related to the graphics processor in that environment.
add a comment |
Your Answer
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "89"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});
function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2faskubuntu.com%2fquestions%2f5417%2fhow-to-get-the-gpu-info%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
18 Answers
18
active
oldest
votes
18 Answers
18
active
oldest
votes
active
oldest
votes
active
oldest
votes
That type of information is non-standard, and the tools you will use to gather it vary widely.
The command glxinfo
will give you all available OpenGL information for the graphics processor, including its vendor name, if the drivers are correctly installed.
To get clock speed information, there is no standard tool.
- For ATI/AMD GPUs,
aticonfig --odgc
will fetch the clock rates, andaticonfig --odgt
will fetch the temperature data. - For NVIDIA GPUs, the
nvclock
program will fetch the same information.
I am not aware of an equivalent tool for the open source drivers or for Intel or other GPUs.
Other information on the hardware can be fetched from the lspci
and lshw
tools.
1
How to install glxinfo?
– stiv
Mar 13 '15 at 13:40
5
@stiv: It's part of the Mesa library, and comes with the packagemesa-utils
on Ubuntu.
– greyfade
Mar 13 '15 at 18:20
2
aticonfig
doesn't appear to be available since the retirement of fglrx.nvclock
also appears to have been abandoned since the last version was for trusty. Do you have any updated solutions? Here's what I have so far..
– Elder Geek
Dec 14 '17 at 23:16
2
glxinfo | grep "Device"
worked well enough for me on an Intel GPU
– John Hamilton
May 26 '18 at 14:10
I use:glxinfo | egrep -i 'device|memory'
– danger89
Jan 2 at 20:37
|
show 2 more comments
That type of information is non-standard, and the tools you will use to gather it vary widely.
The command glxinfo
will give you all available OpenGL information for the graphics processor, including its vendor name, if the drivers are correctly installed.
To get clock speed information, there is no standard tool.
- For ATI/AMD GPUs,
aticonfig --odgc
will fetch the clock rates, andaticonfig --odgt
will fetch the temperature data. - For NVIDIA GPUs, the
nvclock
program will fetch the same information.
I am not aware of an equivalent tool for the open source drivers or for Intel or other GPUs.
Other information on the hardware can be fetched from the lspci
and lshw
tools.
1
How to install glxinfo?
– stiv
Mar 13 '15 at 13:40
5
@stiv: It's part of the Mesa library, and comes with the packagemesa-utils
on Ubuntu.
– greyfade
Mar 13 '15 at 18:20
2
aticonfig
doesn't appear to be available since the retirement of fglrx.nvclock
also appears to have been abandoned since the last version was for trusty. Do you have any updated solutions? Here's what I have so far..
– Elder Geek
Dec 14 '17 at 23:16
2
glxinfo | grep "Device"
worked well enough for me on an Intel GPU
– John Hamilton
May 26 '18 at 14:10
I use:glxinfo | egrep -i 'device|memory'
– danger89
Jan 2 at 20:37
|
show 2 more comments
That type of information is non-standard, and the tools you will use to gather it vary widely.
The command glxinfo
will give you all available OpenGL information for the graphics processor, including its vendor name, if the drivers are correctly installed.
To get clock speed information, there is no standard tool.
- For ATI/AMD GPUs,
aticonfig --odgc
will fetch the clock rates, andaticonfig --odgt
will fetch the temperature data. - For NVIDIA GPUs, the
nvclock
program will fetch the same information.
I am not aware of an equivalent tool for the open source drivers or for Intel or other GPUs.
Other information on the hardware can be fetched from the lspci
and lshw
tools.
That type of information is non-standard, and the tools you will use to gather it vary widely.
The command glxinfo
will give you all available OpenGL information for the graphics processor, including its vendor name, if the drivers are correctly installed.
To get clock speed information, there is no standard tool.
- For ATI/AMD GPUs,
aticonfig --odgc
will fetch the clock rates, andaticonfig --odgt
will fetch the temperature data. - For NVIDIA GPUs, the
nvclock
program will fetch the same information.
I am not aware of an equivalent tool for the open source drivers or for Intel or other GPUs.
Other information on the hardware can be fetched from the lspci
and lshw
tools.
answered Oct 9 '10 at 17:30
greyfadegreyfade
1,2611106
1,2611106
1
How to install glxinfo?
– stiv
Mar 13 '15 at 13:40
5
@stiv: It's part of the Mesa library, and comes with the packagemesa-utils
on Ubuntu.
– greyfade
Mar 13 '15 at 18:20
2
aticonfig
doesn't appear to be available since the retirement of fglrx.nvclock
also appears to have been abandoned since the last version was for trusty. Do you have any updated solutions? Here's what I have so far..
– Elder Geek
Dec 14 '17 at 23:16
2
glxinfo | grep "Device"
worked well enough for me on an Intel GPU
– John Hamilton
May 26 '18 at 14:10
I use:glxinfo | egrep -i 'device|memory'
– danger89
Jan 2 at 20:37
|
show 2 more comments
1
How to install glxinfo?
– stiv
Mar 13 '15 at 13:40
5
@stiv: It's part of the Mesa library, and comes with the packagemesa-utils
on Ubuntu.
– greyfade
Mar 13 '15 at 18:20
2
aticonfig
doesn't appear to be available since the retirement of fglrx.nvclock
also appears to have been abandoned since the last version was for trusty. Do you have any updated solutions? Here's what I have so far..
– Elder Geek
Dec 14 '17 at 23:16
2
glxinfo | grep "Device"
worked well enough for me on an Intel GPU
– John Hamilton
May 26 '18 at 14:10
I use:glxinfo | egrep -i 'device|memory'
– danger89
Jan 2 at 20:37
1
1
How to install glxinfo?
– stiv
Mar 13 '15 at 13:40
How to install glxinfo?
– stiv
Mar 13 '15 at 13:40
5
5
@stiv: It's part of the Mesa library, and comes with the package
mesa-utils
on Ubuntu.– greyfade
Mar 13 '15 at 18:20
@stiv: It's part of the Mesa library, and comes with the package
mesa-utils
on Ubuntu.– greyfade
Mar 13 '15 at 18:20
2
2
aticonfig
doesn't appear to be available since the retirement of fglrx. nvclock
also appears to have been abandoned since the last version was for trusty. Do you have any updated solutions? Here's what I have so far..– Elder Geek
Dec 14 '17 at 23:16
aticonfig
doesn't appear to be available since the retirement of fglrx. nvclock
also appears to have been abandoned since the last version was for trusty. Do you have any updated solutions? Here's what I have so far..– Elder Geek
Dec 14 '17 at 23:16
2
2
glxinfo | grep "Device"
worked well enough for me on an Intel GPU– John Hamilton
May 26 '18 at 14:10
glxinfo | grep "Device"
worked well enough for me on an Intel GPU– John Hamilton
May 26 '18 at 14:10
I use:
glxinfo | egrep -i 'device|memory'
– danger89
Jan 2 at 20:37
I use:
glxinfo | egrep -i 'device|memory'
– danger89
Jan 2 at 20:37
|
show 2 more comments
I do not know of a direct equivalent, but lshw should give you the info you want, try:
sudo lshw -C display
(it also works without sudo
but the info may be less complete/accurate)
You can also install the package lshw-gtk
to get a GUI.
3
Had to put gksu before the command in the menu to get lshw-gtk to work.
– robin0800
Feb 15 '11 at 10:55
Any updates? I'm a fan of the command but the only clock rate (frequency) it seems to provide for me is the base bus clock 33MHz. I'm attempting to bring this Q&A up to date. Thank you!
– Elder Geek
Dec 14 '17 at 23:31
Apologies, new to Deep Learning. What should it say if I have a GPU? It saysproduct: 2nd Generation Core Processor Family Integrated Graphics Controller
– frank
Apr 17 '18 at 2:13
add a comment |
I do not know of a direct equivalent, but lshw should give you the info you want, try:
sudo lshw -C display
(it also works without sudo
but the info may be less complete/accurate)
You can also install the package lshw-gtk
to get a GUI.
3
Had to put gksu before the command in the menu to get lshw-gtk to work.
– robin0800
Feb 15 '11 at 10:55
Any updates? I'm a fan of the command but the only clock rate (frequency) it seems to provide for me is the base bus clock 33MHz. I'm attempting to bring this Q&A up to date. Thank you!
– Elder Geek
Dec 14 '17 at 23:31
Apologies, new to Deep Learning. What should it say if I have a GPU? It saysproduct: 2nd Generation Core Processor Family Integrated Graphics Controller
– frank
Apr 17 '18 at 2:13
add a comment |
I do not know of a direct equivalent, but lshw should give you the info you want, try:
sudo lshw -C display
(it also works without sudo
but the info may be less complete/accurate)
You can also install the package lshw-gtk
to get a GUI.
I do not know of a direct equivalent, but lshw should give you the info you want, try:
sudo lshw -C display
(it also works without sudo
but the info may be less complete/accurate)
You can also install the package lshw-gtk
to get a GUI.
answered Oct 9 '10 at 17:31
Marcel StimbergMarcel Stimberg
26.6k73944
26.6k73944
3
Had to put gksu before the command in the menu to get lshw-gtk to work.
– robin0800
Feb 15 '11 at 10:55
Any updates? I'm a fan of the command but the only clock rate (frequency) it seems to provide for me is the base bus clock 33MHz. I'm attempting to bring this Q&A up to date. Thank you!
– Elder Geek
Dec 14 '17 at 23:31
Apologies, new to Deep Learning. What should it say if I have a GPU? It saysproduct: 2nd Generation Core Processor Family Integrated Graphics Controller
– frank
Apr 17 '18 at 2:13
add a comment |
3
Had to put gksu before the command in the menu to get lshw-gtk to work.
– robin0800
Feb 15 '11 at 10:55
Any updates? I'm a fan of the command but the only clock rate (frequency) it seems to provide for me is the base bus clock 33MHz. I'm attempting to bring this Q&A up to date. Thank you!
– Elder Geek
Dec 14 '17 at 23:31
Apologies, new to Deep Learning. What should it say if I have a GPU? It saysproduct: 2nd Generation Core Processor Family Integrated Graphics Controller
– frank
Apr 17 '18 at 2:13
3
3
Had to put gksu before the command in the menu to get lshw-gtk to work.
– robin0800
Feb 15 '11 at 10:55
Had to put gksu before the command in the menu to get lshw-gtk to work.
– robin0800
Feb 15 '11 at 10:55
Any updates? I'm a fan of the command but the only clock rate (frequency) it seems to provide for me is the base bus clock 33MHz. I'm attempting to bring this Q&A up to date. Thank you!
– Elder Geek
Dec 14 '17 at 23:31
Any updates? I'm a fan of the command but the only clock rate (frequency) it seems to provide for me is the base bus clock 33MHz. I'm attempting to bring this Q&A up to date. Thank you!
– Elder Geek
Dec 14 '17 at 23:31
Apologies, new to Deep Learning. What should it say if I have a GPU? It says
product: 2nd Generation Core Processor Family Integrated Graphics Controller
– frank
Apr 17 '18 at 2:13
Apologies, new to Deep Learning. What should it say if I have a GPU? It says
product: 2nd Generation Core Processor Family Integrated Graphics Controller
– frank
Apr 17 '18 at 2:13
add a comment |
A blog post focussing on work done on the command-line is here:
http://www.cyberciti.biz/faq/howto-find-linux-vga-video-card-ram/
Find out the device ID:
lspci | grep ' VGA ' | cut -d" " -f 1
03:00.0
You can then use this output with lspci
again, forming two nested commands
lspci -v -s $(lspci | grep ' VGA ' | cut -d" " -f 1)
If you have more than 1 GPU card, try this equivalent command instead:
lspci | grep ' VGA ' | cut -d" " -f 1 | xargs -i lspci -v -s {}
Output from my system:
03:00.0 VGA compatible controller: NVIDIA Corporation G98 [Quadro NVS 295] (rev a1) (prog-if 00 [VGA controller])
Subsystem: NVIDIA Corporation Device 062e
Flags: bus master, fast devsel, latency 0, IRQ 24
Memory at f6000000 (32-bit, non-prefetchable) [size=16M]
Memory at ec000000 (64-bit, prefetchable) [size=64M]
Memory at f4000000 (64-bit, non-prefetchable) [size=32M]
I/O ports at dc80 [size=128]
[virtual] Expansion ROM at f7e00000 [disabled] [size=128K]
Capabilities: <access denied>
Kernel driver in use: nvidia
EDIT: You can avoid the <access denied>
by launching with sudo
So, (prefetchable) [size=64M)
indicates that I have a 64-MB NVIDIA card. However, I don't, it's rather 256 MB. Why? see below.
To see how to get the most info+performance out of it, read an extremely comprehensive article on the Arch-Linux Wiki
https://wiki.archlinux.org/index.php/NVIDIA
For nvidia users, start with
nvidia-smi
(This works with the Nvidia drivers installed,but not with systems running the open-source 'nouveau' driver).
Output
Thu Dec 19 10:54:18 2013
+------------------------------------------------------+
| NVIDIA-SMI 5.319.60 Driver Version: 319.60 |
|-------------------------------+----------------------+----------------------+
| GPU Name Persistence-M| Bus-Id Disp.A | Volatile Uncorr. ECC |
| Fan Temp Perf Pwr:Usage/Cap| Memory-Usage | GPU-Util Compute M. |
|===============================+======================+======================|
| 0 Quadro NVS 295 Off | 0000:03:00.0 N/A | N/A |
| N/A 73C N/A N/A / N/A | 252MB / 255MB | N/A Default |
+-------------------------------+----------------------+----------------------+
+-----------------------------------------------------------------------------+
| Compute processes: GPU Memory |
| GPU PID Process name Usage |
|=============================================================================|
| 0 Not Supported |
+-----------------------------------------------------------------------------+
This indicates that I have a 256 MB GDDR3 Graphics card.
At this time, I don't know how to get this for Intel and AMD/ATI GPUs.
12
+1 fornvidia-smi
(that should be highlighted a bit in my opinion)
– Martin Thoma
Sep 7 '14 at 15:23
If anyone have any idea: nvidia-smi hangs indefinitely: what could be the issue?
– Franck Dernoncourt
Aug 9 '16 at 15:50
2
This should really be the accepted answer!
– INElutTabile
Mar 27 '18 at 11:26
nvidia-smi
not showing me full GPU name.
– mrgloom
Nov 24 '18 at 15:15
add a comment |
A blog post focussing on work done on the command-line is here:
http://www.cyberciti.biz/faq/howto-find-linux-vga-video-card-ram/
Find out the device ID:
lspci | grep ' VGA ' | cut -d" " -f 1
03:00.0
You can then use this output with lspci
again, forming two nested commands
lspci -v -s $(lspci | grep ' VGA ' | cut -d" " -f 1)
If you have more than 1 GPU card, try this equivalent command instead:
lspci | grep ' VGA ' | cut -d" " -f 1 | xargs -i lspci -v -s {}
Output from my system:
03:00.0 VGA compatible controller: NVIDIA Corporation G98 [Quadro NVS 295] (rev a1) (prog-if 00 [VGA controller])
Subsystem: NVIDIA Corporation Device 062e
Flags: bus master, fast devsel, latency 0, IRQ 24
Memory at f6000000 (32-bit, non-prefetchable) [size=16M]
Memory at ec000000 (64-bit, prefetchable) [size=64M]
Memory at f4000000 (64-bit, non-prefetchable) [size=32M]
I/O ports at dc80 [size=128]
[virtual] Expansion ROM at f7e00000 [disabled] [size=128K]
Capabilities: <access denied>
Kernel driver in use: nvidia
EDIT: You can avoid the <access denied>
by launching with sudo
So, (prefetchable) [size=64M)
indicates that I have a 64-MB NVIDIA card. However, I don't, it's rather 256 MB. Why? see below.
To see how to get the most info+performance out of it, read an extremely comprehensive article on the Arch-Linux Wiki
https://wiki.archlinux.org/index.php/NVIDIA
For nvidia users, start with
nvidia-smi
(This works with the Nvidia drivers installed,but not with systems running the open-source 'nouveau' driver).
Output
Thu Dec 19 10:54:18 2013
+------------------------------------------------------+
| NVIDIA-SMI 5.319.60 Driver Version: 319.60 |
|-------------------------------+----------------------+----------------------+
| GPU Name Persistence-M| Bus-Id Disp.A | Volatile Uncorr. ECC |
| Fan Temp Perf Pwr:Usage/Cap| Memory-Usage | GPU-Util Compute M. |
|===============================+======================+======================|
| 0 Quadro NVS 295 Off | 0000:03:00.0 N/A | N/A |
| N/A 73C N/A N/A / N/A | 252MB / 255MB | N/A Default |
+-------------------------------+----------------------+----------------------+
+-----------------------------------------------------------------------------+
| Compute processes: GPU Memory |
| GPU PID Process name Usage |
|=============================================================================|
| 0 Not Supported |
+-----------------------------------------------------------------------------+
This indicates that I have a 256 MB GDDR3 Graphics card.
At this time, I don't know how to get this for Intel and AMD/ATI GPUs.
12
+1 fornvidia-smi
(that should be highlighted a bit in my opinion)
– Martin Thoma
Sep 7 '14 at 15:23
If anyone have any idea: nvidia-smi hangs indefinitely: what could be the issue?
– Franck Dernoncourt
Aug 9 '16 at 15:50
2
This should really be the accepted answer!
– INElutTabile
Mar 27 '18 at 11:26
nvidia-smi
not showing me full GPU name.
– mrgloom
Nov 24 '18 at 15:15
add a comment |
A blog post focussing on work done on the command-line is here:
http://www.cyberciti.biz/faq/howto-find-linux-vga-video-card-ram/
Find out the device ID:
lspci | grep ' VGA ' | cut -d" " -f 1
03:00.0
You can then use this output with lspci
again, forming two nested commands
lspci -v -s $(lspci | grep ' VGA ' | cut -d" " -f 1)
If you have more than 1 GPU card, try this equivalent command instead:
lspci | grep ' VGA ' | cut -d" " -f 1 | xargs -i lspci -v -s {}
Output from my system:
03:00.0 VGA compatible controller: NVIDIA Corporation G98 [Quadro NVS 295] (rev a1) (prog-if 00 [VGA controller])
Subsystem: NVIDIA Corporation Device 062e
Flags: bus master, fast devsel, latency 0, IRQ 24
Memory at f6000000 (32-bit, non-prefetchable) [size=16M]
Memory at ec000000 (64-bit, prefetchable) [size=64M]
Memory at f4000000 (64-bit, non-prefetchable) [size=32M]
I/O ports at dc80 [size=128]
[virtual] Expansion ROM at f7e00000 [disabled] [size=128K]
Capabilities: <access denied>
Kernel driver in use: nvidia
EDIT: You can avoid the <access denied>
by launching with sudo
So, (prefetchable) [size=64M)
indicates that I have a 64-MB NVIDIA card. However, I don't, it's rather 256 MB. Why? see below.
To see how to get the most info+performance out of it, read an extremely comprehensive article on the Arch-Linux Wiki
https://wiki.archlinux.org/index.php/NVIDIA
For nvidia users, start with
nvidia-smi
(This works with the Nvidia drivers installed,but not with systems running the open-source 'nouveau' driver).
Output
Thu Dec 19 10:54:18 2013
+------------------------------------------------------+
| NVIDIA-SMI 5.319.60 Driver Version: 319.60 |
|-------------------------------+----------------------+----------------------+
| GPU Name Persistence-M| Bus-Id Disp.A | Volatile Uncorr. ECC |
| Fan Temp Perf Pwr:Usage/Cap| Memory-Usage | GPU-Util Compute M. |
|===============================+======================+======================|
| 0 Quadro NVS 295 Off | 0000:03:00.0 N/A | N/A |
| N/A 73C N/A N/A / N/A | 252MB / 255MB | N/A Default |
+-------------------------------+----------------------+----------------------+
+-----------------------------------------------------------------------------+
| Compute processes: GPU Memory |
| GPU PID Process name Usage |
|=============================================================================|
| 0 Not Supported |
+-----------------------------------------------------------------------------+
This indicates that I have a 256 MB GDDR3 Graphics card.
At this time, I don't know how to get this for Intel and AMD/ATI GPUs.
A blog post focussing on work done on the command-line is here:
http://www.cyberciti.biz/faq/howto-find-linux-vga-video-card-ram/
Find out the device ID:
lspci | grep ' VGA ' | cut -d" " -f 1
03:00.0
You can then use this output with lspci
again, forming two nested commands
lspci -v -s $(lspci | grep ' VGA ' | cut -d" " -f 1)
If you have more than 1 GPU card, try this equivalent command instead:
lspci | grep ' VGA ' | cut -d" " -f 1 | xargs -i lspci -v -s {}
Output from my system:
03:00.0 VGA compatible controller: NVIDIA Corporation G98 [Quadro NVS 295] (rev a1) (prog-if 00 [VGA controller])
Subsystem: NVIDIA Corporation Device 062e
Flags: bus master, fast devsel, latency 0, IRQ 24
Memory at f6000000 (32-bit, non-prefetchable) [size=16M]
Memory at ec000000 (64-bit, prefetchable) [size=64M]
Memory at f4000000 (64-bit, non-prefetchable) [size=32M]
I/O ports at dc80 [size=128]
[virtual] Expansion ROM at f7e00000 [disabled] [size=128K]
Capabilities: <access denied>
Kernel driver in use: nvidia
EDIT: You can avoid the <access denied>
by launching with sudo
So, (prefetchable) [size=64M)
indicates that I have a 64-MB NVIDIA card. However, I don't, it's rather 256 MB. Why? see below.
To see how to get the most info+performance out of it, read an extremely comprehensive article on the Arch-Linux Wiki
https://wiki.archlinux.org/index.php/NVIDIA
For nvidia users, start with
nvidia-smi
(This works with the Nvidia drivers installed,but not with systems running the open-source 'nouveau' driver).
Output
Thu Dec 19 10:54:18 2013
+------------------------------------------------------+
| NVIDIA-SMI 5.319.60 Driver Version: 319.60 |
|-------------------------------+----------------------+----------------------+
| GPU Name Persistence-M| Bus-Id Disp.A | Volatile Uncorr. ECC |
| Fan Temp Perf Pwr:Usage/Cap| Memory-Usage | GPU-Util Compute M. |
|===============================+======================+======================|
| 0 Quadro NVS 295 Off | 0000:03:00.0 N/A | N/A |
| N/A 73C N/A N/A / N/A | 252MB / 255MB | N/A Default |
+-------------------------------+----------------------+----------------------+
+-----------------------------------------------------------------------------+
| Compute processes: GPU Memory |
| GPU PID Process name Usage |
|=============================================================================|
| 0 Not Supported |
+-----------------------------------------------------------------------------+
This indicates that I have a 256 MB GDDR3 Graphics card.
At this time, I don't know how to get this for Intel and AMD/ATI GPUs.
edited Feb 15 '18 at 9:04
answered Dec 19 '13 at 9:50
knbknb
1,95922131
1,95922131
12
+1 fornvidia-smi
(that should be highlighted a bit in my opinion)
– Martin Thoma
Sep 7 '14 at 15:23
If anyone have any idea: nvidia-smi hangs indefinitely: what could be the issue?
– Franck Dernoncourt
Aug 9 '16 at 15:50
2
This should really be the accepted answer!
– INElutTabile
Mar 27 '18 at 11:26
nvidia-smi
not showing me full GPU name.
– mrgloom
Nov 24 '18 at 15:15
add a comment |
12
+1 fornvidia-smi
(that should be highlighted a bit in my opinion)
– Martin Thoma
Sep 7 '14 at 15:23
If anyone have any idea: nvidia-smi hangs indefinitely: what could be the issue?
– Franck Dernoncourt
Aug 9 '16 at 15:50
2
This should really be the accepted answer!
– INElutTabile
Mar 27 '18 at 11:26
nvidia-smi
not showing me full GPU name.
– mrgloom
Nov 24 '18 at 15:15
12
12
+1 for
nvidia-smi
(that should be highlighted a bit in my opinion)– Martin Thoma
Sep 7 '14 at 15:23
+1 for
nvidia-smi
(that should be highlighted a bit in my opinion)– Martin Thoma
Sep 7 '14 at 15:23
If anyone have any idea: nvidia-smi hangs indefinitely: what could be the issue?
– Franck Dernoncourt
Aug 9 '16 at 15:50
If anyone have any idea: nvidia-smi hangs indefinitely: what could be the issue?
– Franck Dernoncourt
Aug 9 '16 at 15:50
2
2
This should really be the accepted answer!
– INElutTabile
Mar 27 '18 at 11:26
This should really be the accepted answer!
– INElutTabile
Mar 27 '18 at 11:26
nvidia-smi
not showing me full GPU name.– mrgloom
Nov 24 '18 at 15:15
nvidia-smi
not showing me full GPU name.– mrgloom
Nov 24 '18 at 15:15
add a comment |
Run google-chrome
and navigate to the URL about:gpu
.
If chrome has figured out how to use OpenGL, you will get extremely detailing information about your GPU.
1
This also works in Chromium (chromium-browser
).
– Eliah Kagan
Jul 2 '17 at 13:02
Clever. Along these lines I additionally went to chromeexperiments.com to see the performance there. Smooth as butter - I'm definitely on gpu
– Jacksonkr
Jul 29 '18 at 17:49
add a comment |
Run google-chrome
and navigate to the URL about:gpu
.
If chrome has figured out how to use OpenGL, you will get extremely detailing information about your GPU.
1
This also works in Chromium (chromium-browser
).
– Eliah Kagan
Jul 2 '17 at 13:02
Clever. Along these lines I additionally went to chromeexperiments.com to see the performance there. Smooth as butter - I'm definitely on gpu
– Jacksonkr
Jul 29 '18 at 17:49
add a comment |
Run google-chrome
and navigate to the URL about:gpu
.
If chrome has figured out how to use OpenGL, you will get extremely detailing information about your GPU.
Run google-chrome
and navigate to the URL about:gpu
.
If chrome has figured out how to use OpenGL, you will get extremely detailing information about your GPU.
edited Aug 25 '15 at 19:19
David Foerster
28.5k1367113
28.5k1367113
answered Nov 15 '12 at 7:35
Chris UhlikChris Uhlik
42142
42142
1
This also works in Chromium (chromium-browser
).
– Eliah Kagan
Jul 2 '17 at 13:02
Clever. Along these lines I additionally went to chromeexperiments.com to see the performance there. Smooth as butter - I'm definitely on gpu
– Jacksonkr
Jul 29 '18 at 17:49
add a comment |
1
This also works in Chromium (chromium-browser
).
– Eliah Kagan
Jul 2 '17 at 13:02
Clever. Along these lines I additionally went to chromeexperiments.com to see the performance there. Smooth as butter - I'm definitely on gpu
– Jacksonkr
Jul 29 '18 at 17:49
1
1
This also works in Chromium (
chromium-browser
).– Eliah Kagan
Jul 2 '17 at 13:02
This also works in Chromium (
chromium-browser
).– Eliah Kagan
Jul 2 '17 at 13:02
Clever. Along these lines I additionally went to chromeexperiments.com to see the performance there. Smooth as butter - I'm definitely on gpu
– Jacksonkr
Jul 29 '18 at 17:49
Clever. Along these lines I additionally went to chromeexperiments.com to see the performance there. Smooth as butter - I'm definitely on gpu
– Jacksonkr
Jul 29 '18 at 17:49
add a comment |
For Nvidia cards.
1st GPU
> cat /proc/driver/nvidia/gpus/0/information
Model: GeForce GTX 680
IRQ: 24
GPU UUID: GPU-71541068-cded-8a1b-1d7e-a093a09e9842
Video BIOS: 80.04.09.00.01
Bus Type: PCIe
DMA Size: 40 bits
DMA Mask: 0xffffffffff
Bus Location: 0000:01.00.0
2nd GPU
> cat /proc/driver/nvidia/gpus/1/information
Model: GeForce GTX 580
IRQ: 33
GPU UUID: GPU-64b1235c-51fc-d6f1-0f0e-fa70320f7a47
Video BIOS: 70.10.20.00.01
Bus Type: PCIe
DMA Size: 40 bits
DMA Mask: 0xffffffffff
Bus Location: 0000:08.00.0
6
Thanks! (thoughcat /proc/driver/nvidia/gpus/0000:01:00.0/information
for me)
– matt wilkie
Nov 24 '15 at 3:54
This is the only correct answer in on-demand cloud/HPC cluster environment on which glxinfo or lspci both fail (the former because there's no OpenGL and display, the latter because the nVidia graphics card is abstracted by a graphics controller like Matrox G200eW3). The folder name under gpus is0000:3b:00.0
or0000:d8:00.0
for me, so we should type:cat /proc/driver/nvidia/gpus/0000:3b:00.0/information
. The lovelyTesla V100-PCIE-16GB
model shows that theqsub
job limit is satisfied as desired.
– user5280911
Oct 6 '18 at 7:40
add a comment |
For Nvidia cards.
1st GPU
> cat /proc/driver/nvidia/gpus/0/information
Model: GeForce GTX 680
IRQ: 24
GPU UUID: GPU-71541068-cded-8a1b-1d7e-a093a09e9842
Video BIOS: 80.04.09.00.01
Bus Type: PCIe
DMA Size: 40 bits
DMA Mask: 0xffffffffff
Bus Location: 0000:01.00.0
2nd GPU
> cat /proc/driver/nvidia/gpus/1/information
Model: GeForce GTX 580
IRQ: 33
GPU UUID: GPU-64b1235c-51fc-d6f1-0f0e-fa70320f7a47
Video BIOS: 70.10.20.00.01
Bus Type: PCIe
DMA Size: 40 bits
DMA Mask: 0xffffffffff
Bus Location: 0000:08.00.0
6
Thanks! (thoughcat /proc/driver/nvidia/gpus/0000:01:00.0/information
for me)
– matt wilkie
Nov 24 '15 at 3:54
This is the only correct answer in on-demand cloud/HPC cluster environment on which glxinfo or lspci both fail (the former because there's no OpenGL and display, the latter because the nVidia graphics card is abstracted by a graphics controller like Matrox G200eW3). The folder name under gpus is0000:3b:00.0
or0000:d8:00.0
for me, so we should type:cat /proc/driver/nvidia/gpus/0000:3b:00.0/information
. The lovelyTesla V100-PCIE-16GB
model shows that theqsub
job limit is satisfied as desired.
– user5280911
Oct 6 '18 at 7:40
add a comment |
For Nvidia cards.
1st GPU
> cat /proc/driver/nvidia/gpus/0/information
Model: GeForce GTX 680
IRQ: 24
GPU UUID: GPU-71541068-cded-8a1b-1d7e-a093a09e9842
Video BIOS: 80.04.09.00.01
Bus Type: PCIe
DMA Size: 40 bits
DMA Mask: 0xffffffffff
Bus Location: 0000:01.00.0
2nd GPU
> cat /proc/driver/nvidia/gpus/1/information
Model: GeForce GTX 580
IRQ: 33
GPU UUID: GPU-64b1235c-51fc-d6f1-0f0e-fa70320f7a47
Video BIOS: 70.10.20.00.01
Bus Type: PCIe
DMA Size: 40 bits
DMA Mask: 0xffffffffff
Bus Location: 0000:08.00.0
For Nvidia cards.
1st GPU
> cat /proc/driver/nvidia/gpus/0/information
Model: GeForce GTX 680
IRQ: 24
GPU UUID: GPU-71541068-cded-8a1b-1d7e-a093a09e9842
Video BIOS: 80.04.09.00.01
Bus Type: PCIe
DMA Size: 40 bits
DMA Mask: 0xffffffffff
Bus Location: 0000:01.00.0
2nd GPU
> cat /proc/driver/nvidia/gpus/1/information
Model: GeForce GTX 580
IRQ: 33
GPU UUID: GPU-64b1235c-51fc-d6f1-0f0e-fa70320f7a47
Video BIOS: 70.10.20.00.01
Bus Type: PCIe
DMA Size: 40 bits
DMA Mask: 0xffffffffff
Bus Location: 0000:08.00.0
answered Apr 1 '15 at 21:22
Matt HMatt H
1,52952033
1,52952033
6
Thanks! (thoughcat /proc/driver/nvidia/gpus/0000:01:00.0/information
for me)
– matt wilkie
Nov 24 '15 at 3:54
This is the only correct answer in on-demand cloud/HPC cluster environment on which glxinfo or lspci both fail (the former because there's no OpenGL and display, the latter because the nVidia graphics card is abstracted by a graphics controller like Matrox G200eW3). The folder name under gpus is0000:3b:00.0
or0000:d8:00.0
for me, so we should type:cat /proc/driver/nvidia/gpus/0000:3b:00.0/information
. The lovelyTesla V100-PCIE-16GB
model shows that theqsub
job limit is satisfied as desired.
– user5280911
Oct 6 '18 at 7:40
add a comment |
6
Thanks! (thoughcat /proc/driver/nvidia/gpus/0000:01:00.0/information
for me)
– matt wilkie
Nov 24 '15 at 3:54
This is the only correct answer in on-demand cloud/HPC cluster environment on which glxinfo or lspci both fail (the former because there's no OpenGL and display, the latter because the nVidia graphics card is abstracted by a graphics controller like Matrox G200eW3). The folder name under gpus is0000:3b:00.0
or0000:d8:00.0
for me, so we should type:cat /proc/driver/nvidia/gpus/0000:3b:00.0/information
. The lovelyTesla V100-PCIE-16GB
model shows that theqsub
job limit is satisfied as desired.
– user5280911
Oct 6 '18 at 7:40
6
6
Thanks! (though
cat /proc/driver/nvidia/gpus/0000:01:00.0/information
for me)– matt wilkie
Nov 24 '15 at 3:54
Thanks! (though
cat /proc/driver/nvidia/gpus/0000:01:00.0/information
for me)– matt wilkie
Nov 24 '15 at 3:54
This is the only correct answer in on-demand cloud/HPC cluster environment on which glxinfo or lspci both fail (the former because there's no OpenGL and display, the latter because the nVidia graphics card is abstracted by a graphics controller like Matrox G200eW3). The folder name under gpus is
0000:3b:00.0
or 0000:d8:00.0
for me, so we should type: cat /proc/driver/nvidia/gpus/0000:3b:00.0/information
. The lovely Tesla V100-PCIE-16GB
model shows that the qsub
job limit is satisfied as desired.– user5280911
Oct 6 '18 at 7:40
This is the only correct answer in on-demand cloud/HPC cluster environment on which glxinfo or lspci both fail (the former because there's no OpenGL and display, the latter because the nVidia graphics card is abstracted by a graphics controller like Matrox G200eW3). The folder name under gpus is
0000:3b:00.0
or 0000:d8:00.0
for me, so we should type: cat /proc/driver/nvidia/gpus/0000:3b:00.0/information
. The lovely Tesla V100-PCIE-16GB
model shows that the qsub
job limit is satisfied as desired.– user5280911
Oct 6 '18 at 7:40
add a comment |
clinfo
sudo apt-get install clinfo
clinfo
is the analogue of glxinfo
but for OpenCL.
nvidia-settings
Mixes runtime with some static info.
More details: How do I check if Ubuntu is using my NVIDIA graphics card?
add a comment |
clinfo
sudo apt-get install clinfo
clinfo
is the analogue of glxinfo
but for OpenCL.
nvidia-settings
Mixes runtime with some static info.
More details: How do I check if Ubuntu is using my NVIDIA graphics card?
add a comment |
clinfo
sudo apt-get install clinfo
clinfo
is the analogue of glxinfo
but for OpenCL.
nvidia-settings
Mixes runtime with some static info.
More details: How do I check if Ubuntu is using my NVIDIA graphics card?
clinfo
sudo apt-get install clinfo
clinfo
is the analogue of glxinfo
but for OpenCL.
nvidia-settings
Mixes runtime with some static info.
More details: How do I check if Ubuntu is using my NVIDIA graphics card?
edited Oct 29 '17 at 20:57
answered Nov 2 '15 at 10:14
Ciro Santilli 新疆改造中心 六四事件 法轮功Ciro Santilli 新疆改造中心 六四事件 法轮功
10.3k44751
10.3k44751
add a comment |
add a comment |
For Nvidia cards, type
nvidia-smi -q
add a comment |
For Nvidia cards, type
nvidia-smi -q
add a comment |
For Nvidia cards, type
nvidia-smi -q
For Nvidia cards, type
nvidia-smi -q
answered Jun 26 '17 at 5:48
QuanlongQuanlong
22124
22124
add a comment |
add a comment |
I do believe the best option for this is neofetch.
# Get neofetch
sudo add-apt-repository ppa:dawidd0811/neofetch
sudo apt update
sudo apt get neofetch
# Run neofetch
neofetch
This gives an output like this:
3
I'm not seeing the video card frequency and memory in this answer. There are far simpler methods to obtain the model of GPU which appears to be all you are giving us. I'm not sure what this adds to the existing answers.
– Elder Geek
Dec 10 '17 at 17:16
Thescreenfetch
program does the same thing and doesn't require a PPA to install.
– Braden Best
Jan 30 '18 at 19:31
It's a shell script. Plus I linked to its github as well so you can just use it as a script.
– HaoZeke
Jan 30 '18 at 19:36
Here's screenfetch: github.com/KittyKatt/screenFetch
– Camille Goudeseune
Feb 7 '18 at 21:31
add a comment |
I do believe the best option for this is neofetch.
# Get neofetch
sudo add-apt-repository ppa:dawidd0811/neofetch
sudo apt update
sudo apt get neofetch
# Run neofetch
neofetch
This gives an output like this:
3
I'm not seeing the video card frequency and memory in this answer. There are far simpler methods to obtain the model of GPU which appears to be all you are giving us. I'm not sure what this adds to the existing answers.
– Elder Geek
Dec 10 '17 at 17:16
Thescreenfetch
program does the same thing and doesn't require a PPA to install.
– Braden Best
Jan 30 '18 at 19:31
It's a shell script. Plus I linked to its github as well so you can just use it as a script.
– HaoZeke
Jan 30 '18 at 19:36
Here's screenfetch: github.com/KittyKatt/screenFetch
– Camille Goudeseune
Feb 7 '18 at 21:31
add a comment |
I do believe the best option for this is neofetch.
# Get neofetch
sudo add-apt-repository ppa:dawidd0811/neofetch
sudo apt update
sudo apt get neofetch
# Run neofetch
neofetch
This gives an output like this:
I do believe the best option for this is neofetch.
# Get neofetch
sudo add-apt-repository ppa:dawidd0811/neofetch
sudo apt update
sudo apt get neofetch
# Run neofetch
neofetch
This gives an output like this:
edited Dec 10 '17 at 17:14
Kevin Bowen
14.7k155970
14.7k155970
answered Dec 10 '17 at 16:37
HaoZekeHaoZeke
14113
14113
3
I'm not seeing the video card frequency and memory in this answer. There are far simpler methods to obtain the model of GPU which appears to be all you are giving us. I'm not sure what this adds to the existing answers.
– Elder Geek
Dec 10 '17 at 17:16
Thescreenfetch
program does the same thing and doesn't require a PPA to install.
– Braden Best
Jan 30 '18 at 19:31
It's a shell script. Plus I linked to its github as well so you can just use it as a script.
– HaoZeke
Jan 30 '18 at 19:36
Here's screenfetch: github.com/KittyKatt/screenFetch
– Camille Goudeseune
Feb 7 '18 at 21:31
add a comment |
3
I'm not seeing the video card frequency and memory in this answer. There are far simpler methods to obtain the model of GPU which appears to be all you are giving us. I'm not sure what this adds to the existing answers.
– Elder Geek
Dec 10 '17 at 17:16
Thescreenfetch
program does the same thing and doesn't require a PPA to install.
– Braden Best
Jan 30 '18 at 19:31
It's a shell script. Plus I linked to its github as well so you can just use it as a script.
– HaoZeke
Jan 30 '18 at 19:36
Here's screenfetch: github.com/KittyKatt/screenFetch
– Camille Goudeseune
Feb 7 '18 at 21:31
3
3
I'm not seeing the video card frequency and memory in this answer. There are far simpler methods to obtain the model of GPU which appears to be all you are giving us. I'm not sure what this adds to the existing answers.
– Elder Geek
Dec 10 '17 at 17:16
I'm not seeing the video card frequency and memory in this answer. There are far simpler methods to obtain the model of GPU which appears to be all you are giving us. I'm not sure what this adds to the existing answers.
– Elder Geek
Dec 10 '17 at 17:16
The
screenfetch
program does the same thing and doesn't require a PPA to install.– Braden Best
Jan 30 '18 at 19:31
The
screenfetch
program does the same thing and doesn't require a PPA to install.– Braden Best
Jan 30 '18 at 19:31
It's a shell script. Plus I linked to its github as well so you can just use it as a script.
– HaoZeke
Jan 30 '18 at 19:36
It's a shell script. Plus I linked to its github as well so you can just use it as a script.
– HaoZeke
Jan 30 '18 at 19:36
Here's screenfetch: github.com/KittyKatt/screenFetch
– Camille Goudeseune
Feb 7 '18 at 21:31
Here's screenfetch: github.com/KittyKatt/screenFetch
– Camille Goudeseune
Feb 7 '18 at 21:31
add a comment |
Just to find the basics, according to https://wiki.debian.org/NvidiaGraphicsDrivers#NVIDIA_Proprietary_Driver,
lspci | grep VGA
If you need more detail than that, see @knb's answer to this same question.
add a comment |
Just to find the basics, according to https://wiki.debian.org/NvidiaGraphicsDrivers#NVIDIA_Proprietary_Driver,
lspci | grep VGA
If you need more detail than that, see @knb's answer to this same question.
add a comment |
Just to find the basics, according to https://wiki.debian.org/NvidiaGraphicsDrivers#NVIDIA_Proprietary_Driver,
lspci | grep VGA
If you need more detail than that, see @knb's answer to this same question.
Just to find the basics, according to https://wiki.debian.org/NvidiaGraphicsDrivers#NVIDIA_Proprietary_Driver,
lspci | grep VGA
If you need more detail than that, see @knb's answer to this same question.
edited Sep 22 '17 at 20:50
answered May 4 '17 at 21:11
mightypilemightypile
440169
440169
add a comment |
add a comment |
This is really not that complex For model and memory, here's a 1 liner that works for every video card I've tested it on regardless of manufacturer (Intel, AMD, NVIDIA):
GPU=$(lspci | grep VGA | cut -d ":" -f3);RAM=$(cardid=$(lspci | grep VGA |cut -d " " -f1);lspci -v -s $cardid | grep " prefetchable"| cut -d "=" -f2);echo $GPU $RAM
GPU= All this bit does is grab the 3rd field from 'lspci' output filtered via 'grep' for VGA which corresponds to the video chip.
RAM= All this bit does is set variable cardid
equal to the first field of output from lspci
matching "VGA" and feeds that as a request for -v
verbose output from lspci
for that specific -s
device, further filtering the output by grep
for the string " prefetchable" as this contains the memory on the card itself (note the preceding space as we don't want to match "non-prefetchable" in our output.
For clock rate on Intel integrated graphics (Tested on I3 and I5)
execute the command sudo find /sys -type f -name gt_cur* -print0 | xargs -0 cat
This dives into the /sys tree to locate the gt_cur_freq_mhz
file which on my I3 is /sys/devices/pci0000:00/0000:00:02.0/drm/card0/gt_cur_freq_mhz
and prints the content. which in my case under extremely light load is 350
as in 350 MHz which corresponds to the minimum frequency found in /sys/devices/pci0000:00/0000:00:02.0/drm/card0/gt_min_freq_mhz
and when running glxgears
and glmark2
results in
1050
as in 1050 MHz which corresponds to the maximum frequency found in /sys/devices/pci0000:00/0000:00:02.0/drm/card0/gt_max_freq_mhz
For clock rates on nvidia cards:
nvidia-smi -stats -d procClk
corresponds to the GPU clock
nvidia-smi -stats -d memClk
corresponds to the memory clock.
Note: I am unable to test the above as my trusty GeForce 210 isn't supported and this works only on Kepler or newer GPUs as indicated by
`nvidia-smi -stats --help'
I do not currently have any solutions for clock rate on AMD cards and do not have the hardware available for testing. I will however say that to the best of my knowledge the aticonfig
mentioned in the accepted answer no longer exists and it appears that nvclock
isn't available for anything since trusty.
add a comment |
This is really not that complex For model and memory, here's a 1 liner that works for every video card I've tested it on regardless of manufacturer (Intel, AMD, NVIDIA):
GPU=$(lspci | grep VGA | cut -d ":" -f3);RAM=$(cardid=$(lspci | grep VGA |cut -d " " -f1);lspci -v -s $cardid | grep " prefetchable"| cut -d "=" -f2);echo $GPU $RAM
GPU= All this bit does is grab the 3rd field from 'lspci' output filtered via 'grep' for VGA which corresponds to the video chip.
RAM= All this bit does is set variable cardid
equal to the first field of output from lspci
matching "VGA" and feeds that as a request for -v
verbose output from lspci
for that specific -s
device, further filtering the output by grep
for the string " prefetchable" as this contains the memory on the card itself (note the preceding space as we don't want to match "non-prefetchable" in our output.
For clock rate on Intel integrated graphics (Tested on I3 and I5)
execute the command sudo find /sys -type f -name gt_cur* -print0 | xargs -0 cat
This dives into the /sys tree to locate the gt_cur_freq_mhz
file which on my I3 is /sys/devices/pci0000:00/0000:00:02.0/drm/card0/gt_cur_freq_mhz
and prints the content. which in my case under extremely light load is 350
as in 350 MHz which corresponds to the minimum frequency found in /sys/devices/pci0000:00/0000:00:02.0/drm/card0/gt_min_freq_mhz
and when running glxgears
and glmark2
results in
1050
as in 1050 MHz which corresponds to the maximum frequency found in /sys/devices/pci0000:00/0000:00:02.0/drm/card0/gt_max_freq_mhz
For clock rates on nvidia cards:
nvidia-smi -stats -d procClk
corresponds to the GPU clock
nvidia-smi -stats -d memClk
corresponds to the memory clock.
Note: I am unable to test the above as my trusty GeForce 210 isn't supported and this works only on Kepler or newer GPUs as indicated by
`nvidia-smi -stats --help'
I do not currently have any solutions for clock rate on AMD cards and do not have the hardware available for testing. I will however say that to the best of my knowledge the aticonfig
mentioned in the accepted answer no longer exists and it appears that nvclock
isn't available for anything since trusty.
add a comment |
This is really not that complex For model and memory, here's a 1 liner that works for every video card I've tested it on regardless of manufacturer (Intel, AMD, NVIDIA):
GPU=$(lspci | grep VGA | cut -d ":" -f3);RAM=$(cardid=$(lspci | grep VGA |cut -d " " -f1);lspci -v -s $cardid | grep " prefetchable"| cut -d "=" -f2);echo $GPU $RAM
GPU= All this bit does is grab the 3rd field from 'lspci' output filtered via 'grep' for VGA which corresponds to the video chip.
RAM= All this bit does is set variable cardid
equal to the first field of output from lspci
matching "VGA" and feeds that as a request for -v
verbose output from lspci
for that specific -s
device, further filtering the output by grep
for the string " prefetchable" as this contains the memory on the card itself (note the preceding space as we don't want to match "non-prefetchable" in our output.
For clock rate on Intel integrated graphics (Tested on I3 and I5)
execute the command sudo find /sys -type f -name gt_cur* -print0 | xargs -0 cat
This dives into the /sys tree to locate the gt_cur_freq_mhz
file which on my I3 is /sys/devices/pci0000:00/0000:00:02.0/drm/card0/gt_cur_freq_mhz
and prints the content. which in my case under extremely light load is 350
as in 350 MHz which corresponds to the minimum frequency found in /sys/devices/pci0000:00/0000:00:02.0/drm/card0/gt_min_freq_mhz
and when running glxgears
and glmark2
results in
1050
as in 1050 MHz which corresponds to the maximum frequency found in /sys/devices/pci0000:00/0000:00:02.0/drm/card0/gt_max_freq_mhz
For clock rates on nvidia cards:
nvidia-smi -stats -d procClk
corresponds to the GPU clock
nvidia-smi -stats -d memClk
corresponds to the memory clock.
Note: I am unable to test the above as my trusty GeForce 210 isn't supported and this works only on Kepler or newer GPUs as indicated by
`nvidia-smi -stats --help'
I do not currently have any solutions for clock rate on AMD cards and do not have the hardware available for testing. I will however say that to the best of my knowledge the aticonfig
mentioned in the accepted answer no longer exists and it appears that nvclock
isn't available for anything since trusty.
This is really not that complex For model and memory, here's a 1 liner that works for every video card I've tested it on regardless of manufacturer (Intel, AMD, NVIDIA):
GPU=$(lspci | grep VGA | cut -d ":" -f3);RAM=$(cardid=$(lspci | grep VGA |cut -d " " -f1);lspci -v -s $cardid | grep " prefetchable"| cut -d "=" -f2);echo $GPU $RAM
GPU= All this bit does is grab the 3rd field from 'lspci' output filtered via 'grep' for VGA which corresponds to the video chip.
RAM= All this bit does is set variable cardid
equal to the first field of output from lspci
matching "VGA" and feeds that as a request for -v
verbose output from lspci
for that specific -s
device, further filtering the output by grep
for the string " prefetchable" as this contains the memory on the card itself (note the preceding space as we don't want to match "non-prefetchable" in our output.
For clock rate on Intel integrated graphics (Tested on I3 and I5)
execute the command sudo find /sys -type f -name gt_cur* -print0 | xargs -0 cat
This dives into the /sys tree to locate the gt_cur_freq_mhz
file which on my I3 is /sys/devices/pci0000:00/0000:00:02.0/drm/card0/gt_cur_freq_mhz
and prints the content. which in my case under extremely light load is 350
as in 350 MHz which corresponds to the minimum frequency found in /sys/devices/pci0000:00/0000:00:02.0/drm/card0/gt_min_freq_mhz
and when running glxgears
and glmark2
results in
1050
as in 1050 MHz which corresponds to the maximum frequency found in /sys/devices/pci0000:00/0000:00:02.0/drm/card0/gt_max_freq_mhz
For clock rates on nvidia cards:
nvidia-smi -stats -d procClk
corresponds to the GPU clock
nvidia-smi -stats -d memClk
corresponds to the memory clock.
Note: I am unable to test the above as my trusty GeForce 210 isn't supported and this works only on Kepler or newer GPUs as indicated by
`nvidia-smi -stats --help'
I do not currently have any solutions for clock rate on AMD cards and do not have the hardware available for testing. I will however say that to the best of my knowledge the aticonfig
mentioned in the accepted answer no longer exists and it appears that nvclock
isn't available for anything since trusty.
edited Dec 14 '17 at 23:17
answered Dec 11 '17 at 13:52
Elder GeekElder Geek
27.4k955130
27.4k955130
add a comment |
add a comment |
In addition to neofetch
answered previously, there is screenfetch
which looks a lot nicer (IMO). Plus another answer mentions he doesn't know how to get iGPU listed and this does it:
For details on setup see: How can I get this terminal splash screen?
In summary just for the bottom section with Ubuntu display containing GPU information (second last line) use:
sudo apt install screenfetch
screenfetch
You'll want to put the screenfetch
command an the bottom of your ~/.bashrc
file to have it appear every time you open the terminal.
add a comment |
In addition to neofetch
answered previously, there is screenfetch
which looks a lot nicer (IMO). Plus another answer mentions he doesn't know how to get iGPU listed and this does it:
For details on setup see: How can I get this terminal splash screen?
In summary just for the bottom section with Ubuntu display containing GPU information (second last line) use:
sudo apt install screenfetch
screenfetch
You'll want to put the screenfetch
command an the bottom of your ~/.bashrc
file to have it appear every time you open the terminal.
add a comment |
In addition to neofetch
answered previously, there is screenfetch
which looks a lot nicer (IMO). Plus another answer mentions he doesn't know how to get iGPU listed and this does it:
For details on setup see: How can I get this terminal splash screen?
In summary just for the bottom section with Ubuntu display containing GPU information (second last line) use:
sudo apt install screenfetch
screenfetch
You'll want to put the screenfetch
command an the bottom of your ~/.bashrc
file to have it appear every time you open the terminal.
In addition to neofetch
answered previously, there is screenfetch
which looks a lot nicer (IMO). Plus another answer mentions he doesn't know how to get iGPU listed and this does it:
For details on setup see: How can I get this terminal splash screen?
In summary just for the bottom section with Ubuntu display containing GPU information (second last line) use:
sudo apt install screenfetch
screenfetch
You'll want to put the screenfetch
command an the bottom of your ~/.bashrc
file to have it appear every time you open the terminal.
edited Apr 18 '18 at 23:21
answered Apr 18 '18 at 23:05
WinEunuuchs2UnixWinEunuuchs2Unix
47.1k1190183
47.1k1190183
add a comment |
add a comment |
If you're running Ubuntu on a Chromebook with crouton, the only one of the answers that will work is going to chrome://gpu
in the Chrome browser.
add a comment |
If you're running Ubuntu on a Chromebook with crouton, the only one of the answers that will work is going to chrome://gpu
in the Chrome browser.
add a comment |
If you're running Ubuntu on a Chromebook with crouton, the only one of the answers that will work is going to chrome://gpu
in the Chrome browser.
If you're running Ubuntu on a Chromebook with crouton, the only one of the answers that will work is going to chrome://gpu
in the Chrome browser.
edited Aug 25 '15 at 19:19
David Foerster
28.5k1367113
28.5k1367113
answered Aug 25 '15 at 17:55
k26drk26dr
14115
14115
add a comment |
add a comment |
For the Intel GMA950 (comes with EeePC in particular) you can run:
setpci -s 00:02.0 f0.b
which will return '00' for 200MHz, '01' for 250MHz or '03' for 400MHz. You may be able to apply the same principle to other Intel cards.
add a comment |
For the Intel GMA950 (comes with EeePC in particular) you can run:
setpci -s 00:02.0 f0.b
which will return '00' for 200MHz, '01' for 250MHz or '03' for 400MHz. You may be able to apply the same principle to other Intel cards.
add a comment |
For the Intel GMA950 (comes with EeePC in particular) you can run:
setpci -s 00:02.0 f0.b
which will return '00' for 200MHz, '01' for 250MHz or '03' for 400MHz. You may be able to apply the same principle to other Intel cards.
For the Intel GMA950 (comes with EeePC in particular) you can run:
setpci -s 00:02.0 f0.b
which will return '00' for 200MHz, '01' for 250MHz or '03' for 400MHz. You may be able to apply the same principle to other Intel cards.
answered Feb 15 '11 at 9:24
user10872
add a comment |
add a comment |
If you would like to have simple information, you could try gpustat. It is very good and simple.
add a comment |
If you would like to have simple information, you could try gpustat. It is very good and simple.
add a comment |
If you would like to have simple information, you could try gpustat. It is very good and simple.
If you would like to have simple information, you could try gpustat. It is very good and simple.
answered Apr 24 '18 at 1:43
NufaNufa
113
113
add a comment |
add a comment |
If you have a AMD Radeon Card, you may want to run the following commands
sudo update-pciids #optional command, requires internet
lspci -nn | grep -E 'VGA|Display'
It should report something like this
00:01.0 VGA compatible controller [0300]: Advanced Micro Devices, Inc. [AMD/ATI] Wani [Radeon R5/R6/R7 Graphics] [1002:9874] (rev c5)
03:00.0 Display controller [0380]: Advanced Micro Devices, Inc. [AMD/ATI] Sun XT [Radeon HD 8670A/8670M/8690M / R5 M330 / M430 / R7 M520] [1002:6660] (rev ff)
add a comment |
If you have a AMD Radeon Card, you may want to run the following commands
sudo update-pciids #optional command, requires internet
lspci -nn | grep -E 'VGA|Display'
It should report something like this
00:01.0 VGA compatible controller [0300]: Advanced Micro Devices, Inc. [AMD/ATI] Wani [Radeon R5/R6/R7 Graphics] [1002:9874] (rev c5)
03:00.0 Display controller [0380]: Advanced Micro Devices, Inc. [AMD/ATI] Sun XT [Radeon HD 8670A/8670M/8690M / R5 M330 / M430 / R7 M520] [1002:6660] (rev ff)
add a comment |
If you have a AMD Radeon Card, you may want to run the following commands
sudo update-pciids #optional command, requires internet
lspci -nn | grep -E 'VGA|Display'
It should report something like this
00:01.0 VGA compatible controller [0300]: Advanced Micro Devices, Inc. [AMD/ATI] Wani [Radeon R5/R6/R7 Graphics] [1002:9874] (rev c5)
03:00.0 Display controller [0380]: Advanced Micro Devices, Inc. [AMD/ATI] Sun XT [Radeon HD 8670A/8670M/8690M / R5 M330 / M430 / R7 M520] [1002:6660] (rev ff)
If you have a AMD Radeon Card, you may want to run the following commands
sudo update-pciids #optional command, requires internet
lspci -nn | grep -E 'VGA|Display'
It should report something like this
00:01.0 VGA compatible controller [0300]: Advanced Micro Devices, Inc. [AMD/ATI] Wani [Radeon R5/R6/R7 Graphics] [1002:9874] (rev c5)
03:00.0 Display controller [0380]: Advanced Micro Devices, Inc. [AMD/ATI] Sun XT [Radeon HD 8670A/8670M/8690M / R5 M330 / M430 / R7 M520] [1002:6660] (rev ff)
answered May 27 '18 at 11:04
NerrveNerrve
296139
296139
add a comment |
add a comment |
For nvidia GPUs, nvidia-smi
command is your friend.
See man nvidia-smi
if you like to.
For listing GPUs use nvidia-smi -L
(nvidia-smi --list-gpus
),
nvidia-smi -q
give information about the gpu and the running processes.
add a comment |
For nvidia GPUs, nvidia-smi
command is your friend.
See man nvidia-smi
if you like to.
For listing GPUs use nvidia-smi -L
(nvidia-smi --list-gpus
),
nvidia-smi -q
give information about the gpu and the running processes.
add a comment |
For nvidia GPUs, nvidia-smi
command is your friend.
See man nvidia-smi
if you like to.
For listing GPUs use nvidia-smi -L
(nvidia-smi --list-gpus
),
nvidia-smi -q
give information about the gpu and the running processes.
For nvidia GPUs, nvidia-smi
command is your friend.
See man nvidia-smi
if you like to.
For listing GPUs use nvidia-smi -L
(nvidia-smi --list-gpus
),
nvidia-smi -q
give information about the gpu and the running processes.
answered Jan 21 at 15:19
MeminMemin
1112
1112
add a comment |
add a comment |
Use lspci
, lspci -v
to get basic info see here.
In my case for ex once I run lspci
and I have got :
dina@dina-X450LA:~$ lspci
00:02.0 VGA compatible controller: Intel Corporation Haswell-ULT Integrated Graphics Controller (rev 0b)
00:03.0 Audio device: Intel Corporation Haswell-ULT HD Audio Controller (rev 0b)
00:14.0 USB controller: Intel Corporation 8 Series USB xHCI HC (rev 04)
00:16.0 Communication controller: Intel Corporation 8 Series HECI #0 (rev 04)
00:1b.0 Audio device: Intel Corporation 8 Series HD Audio Controller (rev 04)
00:1c.0 PCI bridge: Intel Corporation 8 Series PCI Express Root Port 1 (rev e4)
00:1c.2 PCI bridge: Intel Corporation 8 Series PCI Express Root Port 3 (rev e4)
00:1c.3 PCI bridge: Intel Corporation 8 Series PCI Express Root Port 4 (rev e4)
00:1d.0 USB controller: Intel Corporation 8 Series USB EHCI #1 (rev 04)
00:1f.0 ISA bridge: Intel Corporation 8 Series LPC Controller (rev 04)
00:1f.2 SATA controller: Intel Corporation 8 Series SATA Controller 1 [AHCI mode] (rev 04)
00:1f.3 SMBus: Intel Corporation 8 Series SMBus Controller (rev 04)
02:00.0 Ethernet controller: Qualcomm Atheros QCA8171 Gigabit Ethernet (rev 10)
03:00.0 Network controller: Ralink corp. RT3290 Wireless 802.11n 1T/1R PCIe
03:00.1 Bluetooth: Ralink corp. RT3290 Bluetooth
add a comment |
Use lspci
, lspci -v
to get basic info see here.
In my case for ex once I run lspci
and I have got :
dina@dina-X450LA:~$ lspci
00:02.0 VGA compatible controller: Intel Corporation Haswell-ULT Integrated Graphics Controller (rev 0b)
00:03.0 Audio device: Intel Corporation Haswell-ULT HD Audio Controller (rev 0b)
00:14.0 USB controller: Intel Corporation 8 Series USB xHCI HC (rev 04)
00:16.0 Communication controller: Intel Corporation 8 Series HECI #0 (rev 04)
00:1b.0 Audio device: Intel Corporation 8 Series HD Audio Controller (rev 04)
00:1c.0 PCI bridge: Intel Corporation 8 Series PCI Express Root Port 1 (rev e4)
00:1c.2 PCI bridge: Intel Corporation 8 Series PCI Express Root Port 3 (rev e4)
00:1c.3 PCI bridge: Intel Corporation 8 Series PCI Express Root Port 4 (rev e4)
00:1d.0 USB controller: Intel Corporation 8 Series USB EHCI #1 (rev 04)
00:1f.0 ISA bridge: Intel Corporation 8 Series LPC Controller (rev 04)
00:1f.2 SATA controller: Intel Corporation 8 Series SATA Controller 1 [AHCI mode] (rev 04)
00:1f.3 SMBus: Intel Corporation 8 Series SMBus Controller (rev 04)
02:00.0 Ethernet controller: Qualcomm Atheros QCA8171 Gigabit Ethernet (rev 10)
03:00.0 Network controller: Ralink corp. RT3290 Wireless 802.11n 1T/1R PCIe
03:00.1 Bluetooth: Ralink corp. RT3290 Bluetooth
add a comment |
Use lspci
, lspci -v
to get basic info see here.
In my case for ex once I run lspci
and I have got :
dina@dina-X450LA:~$ lspci
00:02.0 VGA compatible controller: Intel Corporation Haswell-ULT Integrated Graphics Controller (rev 0b)
00:03.0 Audio device: Intel Corporation Haswell-ULT HD Audio Controller (rev 0b)
00:14.0 USB controller: Intel Corporation 8 Series USB xHCI HC (rev 04)
00:16.0 Communication controller: Intel Corporation 8 Series HECI #0 (rev 04)
00:1b.0 Audio device: Intel Corporation 8 Series HD Audio Controller (rev 04)
00:1c.0 PCI bridge: Intel Corporation 8 Series PCI Express Root Port 1 (rev e4)
00:1c.2 PCI bridge: Intel Corporation 8 Series PCI Express Root Port 3 (rev e4)
00:1c.3 PCI bridge: Intel Corporation 8 Series PCI Express Root Port 4 (rev e4)
00:1d.0 USB controller: Intel Corporation 8 Series USB EHCI #1 (rev 04)
00:1f.0 ISA bridge: Intel Corporation 8 Series LPC Controller (rev 04)
00:1f.2 SATA controller: Intel Corporation 8 Series SATA Controller 1 [AHCI mode] (rev 04)
00:1f.3 SMBus: Intel Corporation 8 Series SMBus Controller (rev 04)
02:00.0 Ethernet controller: Qualcomm Atheros QCA8171 Gigabit Ethernet (rev 10)
03:00.0 Network controller: Ralink corp. RT3290 Wireless 802.11n 1T/1R PCIe
03:00.1 Bluetooth: Ralink corp. RT3290 Bluetooth
Use lspci
, lspci -v
to get basic info see here.
In my case for ex once I run lspci
and I have got :
dina@dina-X450LA:~$ lspci
00:02.0 VGA compatible controller: Intel Corporation Haswell-ULT Integrated Graphics Controller (rev 0b)
00:03.0 Audio device: Intel Corporation Haswell-ULT HD Audio Controller (rev 0b)
00:14.0 USB controller: Intel Corporation 8 Series USB xHCI HC (rev 04)
00:16.0 Communication controller: Intel Corporation 8 Series HECI #0 (rev 04)
00:1b.0 Audio device: Intel Corporation 8 Series HD Audio Controller (rev 04)
00:1c.0 PCI bridge: Intel Corporation 8 Series PCI Express Root Port 1 (rev e4)
00:1c.2 PCI bridge: Intel Corporation 8 Series PCI Express Root Port 3 (rev e4)
00:1c.3 PCI bridge: Intel Corporation 8 Series PCI Express Root Port 4 (rev e4)
00:1d.0 USB controller: Intel Corporation 8 Series USB EHCI #1 (rev 04)
00:1f.0 ISA bridge: Intel Corporation 8 Series LPC Controller (rev 04)
00:1f.2 SATA controller: Intel Corporation 8 Series SATA Controller 1 [AHCI mode] (rev 04)
00:1f.3 SMBus: Intel Corporation 8 Series SMBus Controller (rev 04)
02:00.0 Ethernet controller: Qualcomm Atheros QCA8171 Gigabit Ethernet (rev 10)
03:00.0 Network controller: Ralink corp. RT3290 Wireless 802.11n 1T/1R PCIe
03:00.1 Bluetooth: Ralink corp. RT3290 Bluetooth
answered Feb 9 at 18:49
DINA TAKLITDINA TAKLIT
1034
1034
add a comment |
add a comment |
In order to get all the information about the graphics processor, you can use the following command as specified by @greyfade.
> glxinfo
However, if the program glxinfo
is currently not installed, you can install it by typing:
> sudo apt install mesa-utils
You will also have to enable the component called universe
. Once this is done, glxinfo
will list all the specifications related to the graphics processor in that environment.
add a comment |
In order to get all the information about the graphics processor, you can use the following command as specified by @greyfade.
> glxinfo
However, if the program glxinfo
is currently not installed, you can install it by typing:
> sudo apt install mesa-utils
You will also have to enable the component called universe
. Once this is done, glxinfo
will list all the specifications related to the graphics processor in that environment.
add a comment |
In order to get all the information about the graphics processor, you can use the following command as specified by @greyfade.
> glxinfo
However, if the program glxinfo
is currently not installed, you can install it by typing:
> sudo apt install mesa-utils
You will also have to enable the component called universe
. Once this is done, glxinfo
will list all the specifications related to the graphics processor in that environment.
In order to get all the information about the graphics processor, you can use the following command as specified by @greyfade.
> glxinfo
However, if the program glxinfo
is currently not installed, you can install it by typing:
> sudo apt install mesa-utils
You will also have to enable the component called universe
. Once this is done, glxinfo
will list all the specifications related to the graphics processor in that environment.
answered 2 mins ago
Nayantara JeyarajNayantara Jeyaraj
1114
1114
add a comment |
add a comment |
Thanks for contributing an answer to Ask Ubuntu!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2faskubuntu.com%2fquestions%2f5417%2fhow-to-get-the-gpu-info%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
what does:
cat /proc/cpuinfo
do? what info are you looking for?– Charlie Parker
Mar 5 '18 at 17:00