1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
|
NVClock 0.5 - FAQ
=================
This FAQ offers answers to some common questions about NVClock. If your question is not addressed herein, please e-mail the author so it can be added.
Why does NVClock only work as root when I don't use Nvidia's accelerated 3d drivers?
NVClock requires read/write access to /dev/mem and only root has that. You can let non-root users use NVClock if you set NVClock setuid* or setguid**. However, this setup is not very secure!!! If you really wish to have NVClock available to all users, setguid is the more secure of the two options.
* If a program has setuid permission, anyone who has permission to run the program
is treated as if they are the program's owner.
chmod 4755 nvclock
** If a program has setguid permission, anyone who has permission to run the program
is treated as if they belong to the program's group.
chmod 2755 nvclock
Why does NVClock tell me that my card is not supported?
This is most likely due to NVClock not yet including your card's PCI id. If this is the problem, you need to use NVClock with the -f option. (Any PCI id's that are e-mailed to the author will be included in upcoming releases)
Why does NVClock not support NVIDIA's onboard/integrated graphics chipsets?
NVClock is, quite simply, not designed for use with these graphics subsystem configurations. While it may work for adjusting the graphics chipset's core speed, there are obviously issues with overclocking the memory as it is system memory being used in this case. As it is the adjustment of memory speed that offers the best performance improvement when overclocking graphics components the author sees no need to support these configurations.
When I overclock my card the screen moves a few pixels to the left. How can I fix this?
It is possible that your NVClock has been compiled with the option -O2. Remove that option from the makefiles and it should work properly.
When I overclock my card before I start X, my custom speeds are gone when X is launched. What can I do about this?
The problem is that the NVIDIA kernel module (NVdriver) resets the speeds of some cards when it starts. Most of the time NVdriver isn't loaded at the startup of Linux. NVdriver is loaded on X startup and resets the speeds of some (newer) cards. Possibly the only thing what you can do is to make sure that NVdriver is loaded at system startup as opposed to X launch.
|
