Arch Linux

Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines

Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.

REPEAT: Do NOT report bugs for outdated packages!
Tasklist

FS#16721 - [nvclock] nvclock, nvclock_gtk crash

Attached to Project: Arch Linux
Opened by filippo colombo (ombra85) - Sunday, 18 October 2009, 13:13 GMT
Last edited by Andrea Scarpino (BaSh) - Monday, 19 October 2009, 13:30 GMT
Task Type Bug Report
Category Packages: Extra
Status Closed
Assigned To No-one
Architecture i686
Severity Medium
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

Description:

1) Nvclock segfaults if i use its options.

2) Nvclock_gtk doesn't start.

3) If i put into xorg.conf this line: " Option "Coolbits" "1" "
i have an entry in nvidia-config about overclocking, called clock frequencies.
It works and i can enable overclocking or downclocking, but if i restart gdm the overclocking or downclocking is disabled.

Additional info:
* package version(s)
* config and/or log files etc.

nvidia 185.18.36
nvidia-utils 185.18.36
nvclock 0.8b4

Steps to reproduce:
This task depends upon

Closed by  Andrea Scarpino (BaSh)
Monday, 19 October 2009, 13:30 GMT
Reason for closing:  Upstream
Comment by Gerardo Exequiel Pozzi (djgera) - Monday, 19 October 2009, 00:50 GMT
  • Field changed: Summary (Nvclock,nvlock_gtk and Nvidia-config Overclock → [nvclock] nvclock, nvclock_gtk crash)
About nvclock crash, should report this to upstream.

And about configuration settings should put "nvidia-settings -l" (I guess that you say nvidia-settings and not nvidia-config) at some startup script so can be executed automatically so settings can take effect. Or you can not configured again?
Comment by filippo colombo (ombra85) - Monday, 19 October 2009, 09:02 GMT
I've installed new 190.40 nvidia drivers and reading /usr/share/doc/nvidia/README , i saw that overclocking wasn't saved for security and all can enable it from terminal with this commands:

1) to enable overclocking do: nvidia-settings --assign GPUOverClockingState=1

2) to change frequency : use --assign="GPU3DClockFreqs=" option of nvidia-settings

So for me i use: nvidia-settings --assign GPUOverClockingState=1 --assign="GPU3DClockFreqs=275,200"

So for me this bug it's closed. Maybe i'll correct nvidia archwiki.
Comment by filippo colombo (ombra85) - Monday, 19 October 2009, 09:21 GMT
Because i think that one can do overclocking via nvidia-settings, why keep a bad nvclock in extra?
Nvclock and nvclock_gtk are bugged only for me?
Nvclock do something that nevidia-settings doesn't do?
Nvidia-settings is only for nvidia 8 series?
Comment by filippo colombo (ombra85) - Monday, 19 October 2009, 09:22 GMT
On the last sentence i talk about overclocking ( and downclocking ) in nvidia-settings.

Loading...