How to get Specific Conky scripts to work?
Forum rules
Before you post read how to get help. Topics in this forum are automatically closed 6 months after creation.
Before you post read how to get help. Topics in this forum are automatically closed 6 months after creation.
-
- Level 3
- Posts: 114
- Joined: Mon Apr 18, 2022 4:08 pm
How to get Specific Conky scripts to work?
This is the conky I'm trying to get to work, but for the life of me can't figure it out
https://www.gnome-look.org/p/1170490/
I got a couple of them to work but they were in French for some reason. I figured out I can just open the files and change the text to English words and that worked.
The ones I got working are CPU Information and Memory. I got Network Device to popup but it doesn't show any of my traffic. And the Graphic Card conky doesn't show up at all
I noticed that if it ends in a .py, then it won't work at all. Not sure what that means but it must be something
You can see which ones end in a .py in the image below
Also, when I put my mouse pointer to the bottom right of the screen to make everything minimise, all the conky's (conkies?) get minimised as well. So that sucks
https://www.gnome-look.org/p/1170490/
I got a couple of them to work but they were in French for some reason. I figured out I can just open the files and change the text to English words and that worked.
The ones I got working are CPU Information and Memory. I got Network Device to popup but it doesn't show any of my traffic. And the Graphic Card conky doesn't show up at all
I noticed that if it ends in a .py, then it won't work at all. Not sure what that means but it must be something
You can see which ones end in a .py in the image below
Also, when I put my mouse pointer to the bottom right of the screen to make everything minimise, all the conky's (conkies?) get minimised as well. So that sucks
Last edited by LockBot on Wed Dec 28, 2022 7:16 am, edited 2 times in total.
Reason: Topic automatically closed 6 months after creation. New replies are no longer allowed.
Reason: Topic automatically closed 6 months after creation. New replies are no longer allowed.
Re: Conky Showoff thread
If you open header.py you can change the
own_window_type
, where this code is using normal
, by default, so it will minimize as you see.From the conky manual:
own_window_type
if own_window is yes, you may specify type normal, desktop,
dock, panel or override (default: normal). Desktop windows are
special windows that have no window decorations; are always vis‐
ible on your desktop; do not appear in your pager or taskbar;
and are sticky across all workspaces. Panel windows reserve
space along a desktop edge, just like panels and taskbars, pre‐
venting maximized windows from overlapping them. The edge is
chosen based on the alignment option. Override windows are not
under the control of the window manager. Hints are ignored. This
type of window can be useful for certain situations.
-
- Level 3
- Posts: 114
- Joined: Mon Apr 18, 2022 4:08 pm
- smurphos
- Level 18
- Posts: 8501
- Joined: Fri Sep 05, 2014 12:18 am
- Location: Irish Brit in Portugal
- Contact:
Re: How to get Specific Conky scripts to work?
They are python scripts - just a hunch but as this conky is unmaintained for over 5 years the scripts may be written in legacy python version.TinMan1325 wrote: ⤴Mon May 23, 2022 9:51 pm I noticed that if it ends in a .py, then it won't work at all. Not sure what that means but it must be something
You can see which ones end in a .py in the image below
Edit to add - the shebangs for the python scripts appear to be pointing to
/usr/bin/python
and others are calling python
directly - this doesn't exist by default in current Mint - only python2 and python3 unless as an end user you install one of the python-is-
packages needed for legacy programs.For custom Nemo actions, useful scripts for the Cinnamon desktop, and Cinnamox themes visit my Github pages.
-
- Level 3
- Posts: 114
- Joined: Mon Apr 18, 2022 4:08 pm
Re: How to get Specific Conky scripts to work?
Oh I see. I guess at this point it would be easier to find a different conkysmurphos wrote: ⤴Tue May 24, 2022 2:19 am They are python scripts - just a hunch but as this conky is unmaintained for over 5 years the scripts may be written in legacy python version.
Edit to add - the shebangs for the python scripts appear to be pointing to/usr/bin/python
and others are callingpython
directly - this doesn't exist by default in current Mint - only python2 and python3 unless as an end user you install one of thepython-is-
packages needed for legacy programs.
Thanks for the help
Re: Conky Showoff thread
You can make these yourself, they are pretty simple. With the lua file i added you can make the bars (included an example). The rest of the info you can get out of /sys/class/* or /sys/devices/* files.TinMan1325 wrote: ⤴Mon May 23, 2022 9:51 pm This is the conky I'm trying to get to work, but for the life of me can't figure it out
https://www.gnome-look.org/p/1170490/
The ones I got working are CPU Information and Memory. I got Network Device to popup but it doesn't show any of my traffic. And the Graphic Card conky doesn't show up at all
This is my second monitor i use as a dashboard. It's all conky. http://www.cobrasoft.nl/pics/conky_mess1.jpg
Last edited by Koentje on Tue May 24, 2022 3:27 pm, edited 1 time in total.
Re: How to get Specific Conky scripts to work?
If i had the info of your graphic card i could have finished it!
Re: How to get Specific Conky scripts to work?
Actually I, reluctantly, dropped it in, and it worked fine, well, maybe clunkily, but that's just my inexperience of dealing with A (single) config that's made up of 15 different files and multiple languages.
That's on a default mint 20.x setup where is there is no python command or python 2 version and only python3.
I saw in the first file that it kills all conky instances so I didn't like that right off the bat, because I was already running one. And after messing with it a bit and rerunning the start.sh I ended up with a bunch of dead conky and python processes. (the amd config was throwing errors because of the python syntax)
I feel like a thing like this should be just broken into the smaller pieces for each "conky". I don't think the overhead of running separate configs is hurting the system, but it's just so convoluted with this setup, and appears there are technical issues as well.
It looks good, but I'm not sure it functions as well as it looks.
That's on a default mint 20.x setup where is there is no python command or python 2 version and only python3.
I saw in the first file that it kills all conky instances so I didn't like that right off the bat, because I was already running one. And after messing with it a bit and rerunning the start.sh I ended up with a bunch of dead conky and python processes. (the amd config was throwing errors because of the python syntax)
I feel like a thing like this should be just broken into the smaller pieces for each "conky". I don't think the overhead of running separate configs is hurting the system, but it's just so convoluted with this setup, and appears there are technical issues as well.
It looks good, but I'm not sure it functions as well as it looks.
Re: How to get Specific Conky scripts to work?
I didn't even try it. I don't use python because i don't know how to code in it. So i rather start with a fresh conky window and try to copy it. And from what i see on the screenshot, these aren't that hard to make.. From what i made so far it uses a lua script to make the bars, and a small bash script to pull the info out of the system (/sys/class and /sys/devices). But i was hoping the TS would react in this tread to give some info about his gpu..
But you're right, try and keep it simple! (says the one who has the most conky scripts running haha)
In the very beginning i had also one conky config doing multiple things. But soon they got split up and even those got split up, and split up again.. because not every conky needs the same update_interval, or combining a ${blink} text statement in a window with a graphbar produces strange behavoir on the graphbar! And my configs grew in complexity and this way i keep every topic in an apart config/setting. You learn what's best while you keep messing around with it! It's addicting!
My conkyscreen exists of 45 conky configs.. and the complete conky system exists out of around 200 files! (more if you include the tmp files and images) Including my homebrew ip camera monitor system
But i still try to keep every script as light as possible and am always trying to improve it with better/simpler/lighter code!
I just recently learned that top is not the best way to find out if some script/program is running! Instead ps -A is way better! And with the new amd gpu i improved that conky window. Before i used radeontop to extract the info, but that was time and cpu consuming! So now it gets all the info from /sys/class and /sys/devices. I only use lspci for the name of the card and bus number.
But I even made a conky usage script that calculates cpu usage and ram usage of every conky/bash/lua script and libs that are called from it. It uses around 25mb of ram and mostly hoovers around 6% cpu usage, sometimes 12% and about 3 times an hour a 25% burst. I guess the latter is because all the update_intervals are coming together and all or most scripts are started at the same time. I try messing around with the intervals to avoid that, but i guess it's at it's best now..
But you're right, try and keep it simple! (says the one who has the most conky scripts running haha)
In the very beginning i had also one conky config doing multiple things. But soon they got split up and even those got split up, and split up again.. because not every conky needs the same update_interval, or combining a ${blink} text statement in a window with a graphbar produces strange behavoir on the graphbar! And my configs grew in complexity and this way i keep every topic in an apart config/setting. You learn what's best while you keep messing around with it! It's addicting!
My conkyscreen exists of 45 conky configs.. and the complete conky system exists out of around 200 files! (more if you include the tmp files and images) Including my homebrew ip camera monitor system
But i still try to keep every script as light as possible and am always trying to improve it with better/simpler/lighter code!
I just recently learned that top is not the best way to find out if some script/program is running! Instead ps -A is way better! And with the new amd gpu i improved that conky window. Before i used radeontop to extract the info, but that was time and cpu consuming! So now it gets all the info from /sys/class and /sys/devices. I only use lspci for the name of the card and bus number.
But I even made a conky usage script that calculates cpu usage and ram usage of every conky/bash/lua script and libs that are called from it. It uses around 25mb of ram and mostly hoovers around 6% cpu usage, sometimes 12% and about 3 times an hour a 25% burst. I guess the latter is because all the update_intervals are coming together and all or most scripts are started at the same time. I try messing around with the intervals to avoid that, but i guess it's at it's best now..
Re: How to get Specific Conky scripts to work?
If this is a python problem, and I'm not sure that is the case here, I wonder if installing the python-is-python3 from the repos if you don't already have it, would help.
I've been using conky for many years now with no difficulties but have nothing python related in my .conkyrc configuration file as far as I can remember, and I'm using an Android tablet to write this so can't check details at the moment.
I've been using conky for many years now with no difficulties but have nothing python related in my .conkyrc configuration file as far as I can remember, and I'm using an Android tablet to write this so can't check details at the moment.
-
- Level 3
- Posts: 114
- Joined: Mon Apr 18, 2022 4:08 pm
Re: Conky Showoff thread
Yeah I have no idea how to do any of that lol. I did however figure out the network one, so that's goodKoentje wrote: ⤴Tue May 24, 2022 5:17 am You can make these yourself, they are pretty simple. With the lua file i added you can make the bars (included an example). The rest of the info you can get out of /sys/class/* or /sys/devices/* files.
This is my second monitor i use as a dashboard. It's all conky. http://www.cobrasoft.nl/pics/conky_mess1.jpg
cpuload.tar.gz
Thanks for sharing
Re: Conky Showoff thread
Let me guess... you had to change the device name?TinMan1325 wrote: ⤴Wed May 25, 2022 4:40 am Yeah I have no idea how to do any of that lol. I did however figure out the network one, so that's good
But what graphic card are you using?
Can you run this in a terminal and post the ouput:
inxi -G
Re: How to get Specific Conky scripts to work?
If you want me to make that gpu conky work for you, you can run the script i attached to this post in a terminal.
When it's finished it will give you a link that you can copy here.
This script will give me all the info i need..
When it's finished it will give you a link that you can copy here.
This script will give me all the info i need..
Last edited by Koentje on Wed May 25, 2022 2:46 pm, edited 1 time in total.
-
- Level 3
- Posts: 114
- Joined: Mon Apr 18, 2022 4:08 pm
Re: Conky Showoff thread
Hah yup, that was it. Took me hours of searching online to realise what the issue wasKoentje wrote: ⤴Wed May 25, 2022 5:12 amLet me guess... you had to change the device name?TinMan1325 wrote: ⤴Wed May 25, 2022 4:40 am Yeah I have no idea how to do any of that lol. I did however figure out the network one, so that's good
But what graphic card are you using?
Can you run this in a terminal and post the ouput:inxi -G
Code: Select all
Graphics:
Device-1: NVIDIA GP106 [GeForce GTX 1060 6GB] driver: nvidia v: 510.73.05
Display: x11 server: X.Org 1.20.13 driver: nvidia
unloaded: fbdev,modesetting,nouveau,vesa resolution: 1920x1080~60Hz
OpenGL: renderer: NVIDIA GeForce GTX 1060 6GB/PCIe/SSE2
v: 4.6.0 NVIDIA 510.73.05
Re: How to get Specific Conky scripts to work?
See my last reply!, post the link please!
-
- Level 3
- Posts: 114
- Joined: Mon Apr 18, 2022 4:08 pm
Re: How to get Specific Conky scripts to work?
Mmmh.. there is not so much info from the sysfs as i hoped to be.
Do you have a tool called
edit:
Try this in the terminal:
Do you have a tool called
nvidia-smi
or any other tool that you can run on the terminal to get clock speeds, memory usage and gpu load from your nvidia card? I do not have a nvidia card, so i can't test it.edit:
Try this in the terminal:
nvidia-settings -q all -t
and post the outcome here.-
- Level 3
- Posts: 114
- Joined: Mon Apr 18, 2022 4:08 pm
Re: How to get Specific Conky scripts to work?
I don't think I have that but here's from the terminalKoentje wrote: ⤴Thu May 26, 2022 7:04 am Mmmh.. there is not so much info from the sysfs as i hoped to be.
Do you have a tool callednvidia-smi
or any other tool that you can run on the terminal to get clock speeds, memory usage and gpu load from your nvidia card? I do not have a nvidia card, so i can't test it.
edit:
Try this in the terminal:nvidia-settings -q all -t
and post the outcome here.
Code: Select all
Attributes queryable via Home:0.0:
OperatingSystem: 0
NvidiaDriverVersion: 510.73.05
NvControlVersion: 1.29
GLXServerVersion: 1.4
GLXClientVersion: 1.4
OpenGLVersion: 4.6.0 NVIDIA 510.73.05
XRandRVersion: 1.6
XF86VidModeVersion: 2.2
XvVersion: 2.2
TwinView: 0
ConnectedDisplays: 0x00000200
EnabledDisplays: 0x00000200
AssociatedDisplays: 0x00001f00
InitialPixmapPlacement: 2
MultiGpuDisplayOwner: 0
GlyphCache: 1
Depth30Allowed: 1
NoScanout: 0
XServerUniqueId: -1054779187
PixmapCache: 1
PixmapCacheRoundSizeKB: 1024
AccelerateTrapezoids: 1
ScreenPosition: x=0, y=0, width=1920, height=1080
SyncToVBlank: 1
LogAniso: 0
FSAA: 0
TextureClamping: 1
FXAA: 0
AllowFlipping: 1
FSAAAppControlled: 1
LogAnisoAppControlled: 1
OpenGLImageSettings: 1
FSAAAppEnhanced: 0
SliMosaicModeAvailable: 0
ShowGraphicsVisualIndicator: 0
BusType: 2
PCIEMaxLinkSpeed: 8000
PCIEMaxLinkWidth: 16
PCIECurrentLinkSpeed: 8000
PCIECurrentLinkWidth: 16
VideoRam: 6291456
Irq: 118
CUDACores: 1280
GPUMemoryInterface: 192
GPUCoreTemp: 37
GPUCurrentClockFreqs: 1177,4006
BusRate: 16
PCIEGen: 3
GPUErrors: 0
GPUPowerSource: 0
GPUCurrentPerfLevel: 3
GPUAdaptiveClockState: 1
ECCConfigurationSupported: 0
GPUCurrentClockFreqsString: nvclock=1177, nvclockmin=189, nvclockmax=1961,
nvclockeditable=218, memclock=4006, memclockmin=4004, memclockmax=4004,
memclockeditable=1, memTransferRate=8012, memTransferRatemin=8008,
memTransferRatemax=8008, memTransferRateeditable=1
GPUPerfModes: perf=0, nvclock=139, nvclockmin=139, nvclockmax=607,
nvclockeditable=1, memclock=405, memclockmin=405, memclockmax=405,
memclockeditable=1, memTransferRate=810, memTransferRatemin=810,
memTransferRatemax=810, memTransferRateeditable=1 ; perf=1, nvclock=139,
nvclockmin=139, nvclockmax=1911, nvclockeditable=149, memclock=810,
memclockmin=810, memclockmax=810, memclockeditable=1, memTransferRate=1620,
memTransferRatemin=1620, memTransferRatemax=1620, memTransferRateeditable=1 ;
perf=2, nvclock=189, nvclockmin=189, nvclockmax=1961, nvclockeditable=42,
memclock=3802, memclockmin=3802, memclockmax=3802, memclockeditable=1,
memTransferRate=7604, memTransferRatemin=7604, memTransferRatemax=7604,
memTransferRateeditable=1 ; perf=3, nvclock=189, nvclockmin=189,
nvclockmax=1961, nvclockeditable=218, memclock=4004, memclockmin=4004,
memclockmax=4004, memclockeditable=1, memTransferRate=8008,
memTransferRatemin=8008, memTransferRatemax=8008, memTransferRateeditable=1
GPUSlowdownTempThreshold: 99
GPUShutdownTempThreshold: 102
FrameLockAvailable: 0
FrameLockFirmwareUnsupported: 0
DigitalVibrance: 0
ImageSharpeningDefault: 127
RefreshRate: 60.00 Hz
RefreshRate3: 60.000 Hz
ColorSpace: 0
ColorRange: 0
CurrentColorSpace: 0
CurrentColorRange: 0
CurrentMetaModeID: 50
CurrentMetaMode: id=50, switchable=yes, source=xconfig :: DPY-1:
nvidia-auto-select @1920x1080 +0+0 {ViewPortIn=1920x1080,
ViewPortOut=1920x1080+0+0}
XineramaInfoOrder: HDMI-0
XVideoSyncToDisplay: 0x00000200
XVideoSyncToDisplayID: -1
CurrentXVideoSyncToDisplayID: 1
Attributes queryable via Home:0[gpu:0]:
OperatingSystem: 0
NvidiaDriverVersion: 510.73.05
ConnectedDisplays: 0x00000200
EnabledDisplays: 0x00000200
Depth30Allowed: 1
NoScanout: 0
SliMosaicModeAvailable: 0
BusType: 2
PCIEMaxLinkSpeed: 8000
PCIEMaxLinkWidth: 16
PCIECurrentLinkSpeed: 8000
PCIECurrentLinkWidth: 16
VideoRam: 6291456
TotalDedicatedGPUMemory: 6070
UsedDedicatedGPUMemory: 1032
Irq: 118
CUDACores: 1280
GPUMemoryInterface: 192
GPUCoreTemp: 38
GPUCurrentClockFreqs: 1556,4006
BusRate: 16
PCIDomain: 0
PCIBus: 8
PCIDevice: 0
PCIFunc: 0
PCIID: 4318,7171
PCIEGen: 3
GPUPowerSource: 0
GPUCurrentPerfLevel: 3
GPUAdaptiveClockState: 1
GPUPowerMizerMode: 2
GPUPowerMizerDefaultMode: 0
ECCSupported: 0
GPULogoBrightness: 100
ECCConfigurationSupported: 0
GPUFanControlState: 1
BaseMosaic: 0
MultiGpuPrimaryPossible: 0
MultiGpuMasterPossible: 0
VideoEncoderUtilization: 0
VideoDecoderUtilization: 0
GPUCurrentClockFreqsString: nvclock=1556, nvclockmin=189, nvclockmax=1961,
nvclockeditable=218, memclock=4006, memclockmin=4004, memclockmax=4004,
memclockeditable=1, memTransferRate=8012, memTransferRatemin=8008,
memTransferRatemax=8008, memTransferRateeditable=1
GPUPerfModes: perf=0, nvclock=139, nvclockmin=139, nvclockmax=607,
nvclockeditable=1, memclock=405, memclockmin=405, memclockmax=405,
memclockeditable=1, memTransferRate=810, memTransferRatemin=810,
memTransferRatemax=810, memTransferRateeditable=1 ; perf=1, nvclock=139,
nvclockmin=139, nvclockmax=1911, nvclockeditable=149, memclock=810,
memclockmin=810, memclockmax=810, memclockeditable=1, memTransferRate=1620,
memTransferRatemin=1620, memTransferRatemax=1620, memTransferRateeditable=1 ;
perf=2, nvclock=189, nvclockmin=189, nvclockmax=1961, nvclockeditable=42,
memclock=3802, memclockmin=3802, memclockmax=3802, memclockeditable=1,
memTransferRate=7604, memTransferRatemin=7604, memTransferRatemax=7604,
memTransferRateeditable=1 ; perf=3, nvclock=189, nvclockmin=189,
nvclockmax=1961, nvclockeditable=218, memclock=4004, memclockmin=4004,
memclockmax=4004, memclockeditable=1, memTransferRate=8008,
memTransferRatemin=8008, memTransferRatemax=8008, memTransferRateeditable=1
GpuUUID: GPU-0f3ec235-a823-bf52-2a32-e5cf80be4f1a
GPUUtilization: graphics=28, memory=3, video=0, PCIe=0
GPUSlowdownTempThreshold: 99
GPUShutdownTempThreshold: 102
FrameLockAvailable: 0
FrameLockFirmwareUnsupported: 0
Dithering: 0
CurrentDithering: 1
DitheringMode: 0
CurrentDitheringMode: 3
DitheringDepth: 0
CurrentDitheringDepth: 2
DigitalVibrance: 0
ImageSharpeningDefault: 127
RefreshRate: 60.00 Hz
RefreshRate3: 60.000 Hz
ColorSpace: 0
ColorRange: 0
CurrentColorSpace: 0
CurrentColorRange: 0
SynchronousPaletteUpdates: 0
Hdmi3D: 0
Attributes queryable via Home:0[fan:0]:
GPUTargetFanSpeed: 40
GPUCurrentFanSpeed: 40
GPUCurrentFanSpeedRPM: 1238
GPUFanControlType: 2
GPUFanTarget: 0x00000007
Attributes queryable via Home:0[thermalsensor:0]:
ThermalSensorReading: 38
ThermalSensorProvider: 1
ThermalSensorTarget: 1
Attributes queryable via Home:0[dpy:0]:
FrameLockAvailable: 0
Dithering: 0
CurrentDithering: 0
DitheringMode: 0
CurrentDitheringMode: 0
DitheringDepth: 0
CurrentDitheringDepth: 0
ColorSpace: 0
ColorRange: 0
CurrentColorSpace: 0
CurrentColorRange: 0
SynchronousPaletteUpdates: 0
RandROutputID: 445
DisplayVRRMode: 0
DisplayVRREnabled: 0
Attributes queryable via Home:0[dpy:1]:
FrameLockAvailable: 0
Dithering: 0
CurrentDithering: 1
DitheringMode: 0
CurrentDitheringMode: 3
DitheringDepth: 0
CurrentDitheringDepth: 2
DigitalVibrance: 0
ImageSharpeningDefault: 127
RefreshRate: 60.00 Hz
RefreshRate3: 60.000 Hz
ColorSpace: 0
ColorRange: 0
CurrentColorSpace: 0
CurrentColorRange: 0
SynchronousPaletteUpdates: 0
RandROutputID: 446
Hdmi3D: 0
DisplayVRRMode: 0
DisplayVRRMinRefreshRate: 0
DisplayVRREnabled: 0
Attributes queryable via Home:0[dpy:2]:
FrameLockAvailable: 0
Dithering: 0
CurrentDithering: 0
DitheringMode: 0
CurrentDitheringMode: 0
DitheringDepth: 0
CurrentDitheringDepth: 0
ColorSpace: 0
ColorRange: 0
CurrentColorSpace: 0
CurrentColorRange: 0
SynchronousPaletteUpdates: 0
RandROutputID: 474
DisplayPortConnectorType: 0
DisplayPortIsMultiStream: 0
DisplayPortSinkIsAudioCapable: 0
DisplayVRRMode: 0
DisplayVRREnabled: 0
Attributes queryable via Home:0[dpy:3]:
FrameLockAvailable: 0
Dithering: 0
CurrentDithering: 0
DitheringMode: 0
CurrentDitheringMode: 0
DitheringDepth: 0
CurrentDitheringDepth: 0
ColorSpace: 0
ColorRange: 0
CurrentColorSpace: 0
CurrentColorRange: 0
SynchronousPaletteUpdates: 0
RandROutputID: 475
DisplayVRRMode: 0
DisplayVRREnabled: 0
Attributes queryable via Home:0[dpy:4]:
FrameLockAvailable: 0
Dithering: 0
CurrentDithering: 0
DitheringMode: 0
CurrentDitheringMode: 0
DitheringDepth: 0
CurrentDitheringDepth: 0
ColorSpace: 0
ColorRange: 0
CurrentColorSpace: 0
CurrentColorRange: 0
SynchronousPaletteUpdates: 0
RandROutputID: 476
DisplayVRRMode: 0
DisplayVRREnabled: 0
Re: How to get Specific Conky scripts to work?
Please be more specific! What command did you run??
nvidia-smi
or did you run nvidia-settings
?-
- Level 3
- Posts: 114
- Joined: Mon Apr 18, 2022 4:08 pm
Re: How to get Specific Conky scripts to work?
Oh sorry, it didn't realise "nvidia-smi" was a command for the terminal. I posted the results for "nvidia-settings -q all -t"
nvidia-smi gives me
Code: Select all
Thu May 26 15:37:51 2022
+-----------------------------------------------------------------------------+
| NVIDIA-SMI 510.73.05 Driver Version: 510.73.05 CUDA Version: 11.6 |
|-------------------------------+----------------------+----------------------+
| GPU Name Persistence-M| Bus-Id Disp.A | Volatile Uncorr. ECC |
| Fan Temp Perf Pwr:Usage/Cap| Memory-Usage | GPU-Util Compute M. |
| | | MIG M. |
|===============================+======================+======================|
| 0 NVIDIA GeForce ... Off | 00000000:08:00.0 On | N/A |
| 40% 33C P8 10W / 120W | 523MiB / 6144MiB | 4% Default |
| | | N/A |
+-------------------------------+----------------------+----------------------+
+-----------------------------------------------------------------------------+
| Processes: |
| GPU GI CI PID Type Process name GPU Memory |
| ID ID Usage |
|=============================================================================|
| 0 N/A N/A 979 G /usr/lib/xorg/Xorg 241MiB |
| 0 N/A N/A 1489 G cinnamon 26MiB |
| 0 N/A N/A 16160 G ...211446204693648980,131072 63MiB |
| 0 N/A N/A 34030 G ...llation/ubuntu12_32/steam 30MiB |
| 0 N/A N/A 34106 G ...ef_log.txt --shared-files 157MiB |
+-----------------------------------------------------------------------------+