You are not logged in.

#1 2015-05-14 11:55:59

aligator
Member
Registered: 2013-10-07
Posts: 75

[solved] nvidia-settings -q --> segmentation fault

Hi

I used this command for a long time to get the GPU RAM:

nvidia-settings -q UsedDedicatedGPUMemory

I use it with conky. A few weeks ago ist stopped working and produced segmentation faults:

nvidia-settings -q UsedDedicatedGPUMemory                                                                                                                                                                  :(

  Attribute 'UsedDedicatedGPUMemory' (arch:0[gpu:0]): 148.
    'UsedDedicatedGPUMemory' is an integer attribute.
    'UsedDedicatedGPUMemory' is a read-only attribute.
    'UsedDedicatedGPUMemory' can use the following target types: GPU.

[1]    7409 segmentation fault (core dumped)  nvidia-settings -q UsedDedicatedGPUMemory

I get this segmentation fault always regardless of the property, I want to read:

nvidia-settings -q gpucoretemp                                                                                                                                                                                                                                                                     :(

  Attribute 'GPUCoreTemp' (arch:0.0): 35.
    'GPUCoreTemp' is an integer attribute.
    'GPUCoreTemp' is a read-only attribute.
    'GPUCoreTemp' can use the following target types: X Screen, GPU.
  Attribute 'GPUCoreTemp' (arch:0[gpu:0]): 35.
    'GPUCoreTemp' is an integer attribute.
    'GPUCoreTemp' is a read-only attribute.
    'GPUCoreTemp' can use the following target types: X Screen, GPU.

[1]    8067 segmentation fault (core dumped)  nvidia-settings -q gpucoretemp
nvidia-settings -q all
.
.
.
.
    'RandROutputID' is a read-only attribute.
    'RandROutputID' is display device specific.
    'RandROutputID' can use the following target types: Display Device.

  Attribute 'RandROutputID' (arch:0[dpy:5]): 661.
    'RandROutputID' is an integer attribute.
    'RandROutputID' is a read-only attribute.
    'RandROutputID' is display device specific.
    'RandROutputID' can use the following target types: Display Device.

  Attribute 'RandROutputID' (arch:0[dpy:5]): 661.
    'RandROutputID' is an integer attribute.
    'RandROutputID' is a read-only attribute.
    'RandROutputID' is display device specific.
    'RandROutputID' can use the following target types: Display Device.

  Attribute 'RandROutputID' (arch:0[dpy:5]): 661.
    'RandROutputID' is an integer attribute.
    'RandROutputID' is a read-only attribute.
    'RandROutputID' is display device specific.
    'RandROutputID' can use the following target types: Display Device.

[1]    7755 segmentation fault (core dumped)  nvidia-settings -q all

Any idea?

Last edited by aligator (2015-05-14 15:10:38)

Offline

#2 2015-05-14 14:39:03

Malkymder
Member
Registered: 2015-05-13
Posts: 258

Re: [solved] nvidia-settings -q --> segmentation fault

I would start by verifiying the installed version with

 cat /proc/driver/nvidia/version 

to check your current Driver and

nvidia-settings --v

for the settings version

Offline

#3 2015-05-14 14:48:59

Scimmia
Fellow
Registered: 2012-09-01
Posts: 11,593

Re: [solved] nvidia-settings -q --> segmentation fault

If you have an Intel CPU (Haswell or early Broadwell), make sure your microcode is updated.

Offline

#4 2015-05-14 15:02:45

NoSavvy
Member
From: Dorchester, Dorset, UK
Registered: 2013-01-23
Posts: 97

Re: [solved] nvidia-settings -q --> segmentation fault

Don't see "nvidia-settings" under listed repository packages anymore. Is it the the right version ie. matching the driver.??

Offline

#5 2015-05-14 15:07:30

Malkymder
Member
Registered: 2015-05-13
Posts: 258

Re: [solved] nvidia-settings -q --> segmentation fault

nvidia-settings is from the nvidia-utils package smile

Offline

#6 2015-05-14 15:10:12

aligator
Member
Registered: 2013-10-07
Posts: 75

Re: [solved] nvidia-settings -q --> segmentation fault

@ Scimmia:

Thank you, that fixed it!

Offline

Board footer

Powered by FluxBB