Diff of /nouveau-pm/README [d1bba6] .. [131335]  Maximize  Restore

Switch to side-by-side view

--- a/nouveau-pm/README
+++ b/nouveau-pm/README
@@ -2,6 +2,7 @@
 
 
 Pre-requirements
+--------------
 ----------------
 
 - any single setup NVIDIA videocard of the following generations - nv50, nv8x, nv9x.
@@ -13,25 +14,22 @@
 - linux kernel with CONFIG_MMIOTRACE built-in
 - the normal build-essentials, such as gcc, make etc.
 - xorg-dev packages provided by your distribution
+- timeout - a small program that kills a program after a specified amount of time
 - compressing programs like - xz-utils, tar and gzip
-- git-core - used to get the source
-- timeout - a small program that kills a program after a specified amount of time
 
 
 
 How to
 ------
 
-1. Download the relevant files
-$ git clone git://nouveau.git.sourceforge.net/gitroot/nouveau/nouveau nouveau
+1. Disable all of the fancy window effects that comes with "eye candy" window
+managers, like compiz, KWin etc.
+  
+2. Download the relevant files
+$ cvs -z3 -d:pserver:anonymous@nouveau.cvs.sourceforge.net:/cvsroot/nouveau co -P nouveau-pm
 
-2. Compile the program
-$ cd nouveau/nouveau-pm
+3. Compile the program
 $ make
-
-3. Disable all of the fancy window effects that comes with "eye candy" window
-managers, like compiz, KWin etc. and make sure that they will not start again
-upon the next X session
 
 4. Exit to a virtual terminal and kill X
 
@@ -40,23 +38,42 @@
 
 6. Startup X
 
-7. Once everything is up and running fire up you favorite terminal emulator
- and the following script as root
+7. Once everything is up and running run the following script as root :
 $ sudo ./run-trace.sh
 
-Retain yourself from running anything else as it may alter the clocks and/or
+Retain yourself from running anything else as it may alther the clocks and/or
 increase the dump size.
 
 Within two-three minutes you should see the message "Dumping done. Stopping
 tracer" but the script will continue running (compressing the data and
 collecting other information).
 
-If any ERROR occurs during the above mentioned process please consult yourself with the FAQ
+If the above message does not appear, stop the script manually and do NOT send the dump.
+This means that the driver did not decrease the clocks to
+NV_CTRL_GPU_DEFAULT_2D_CLOCK_FREQS, which can be caused by several reasons :
 
-If by any chance you interrupt the run-trace.sh script, note that there may be two new
-folders in the current working directory - nouveau-pm.XXXXXXXXXX and nvXX-0xYYYYYYYY-ZZZZ.
-Feel free to delete those folders (you will need root access) and repeat the procedure from
-step 3 onwards. A system reboot is recommended but not essential.
+ A. You are using a videocard without "dedicated video memory", i.e. the card is
+ using the system memory / the card is a integrated within the motherboard
+
+ B. The test is being run while something is connected to the HDMI/DP output
+ (please send me a email if it happens with other outputs)
+
+ Possible workarounds :
+ A. Use gdb to find the lowest frequency the "integrated" videocard reaches in a stable 2D state.
+ Within 3-4 minutes look at the value returned by NV_CTRL_GPU_CURRENT_CLOCK_FREQS.
+ Set def_2d to the same value and repeat the procedure from step 3 onwards.
+
+Example of monitor_downclocking.c (around line 170)
+	check_bus_type(dpy);
+	check_fans(dpy);
++	def_2d = 0x008b0078; // example of 139MHz core, and 120MHz mem
+// Where def_2d is a packed integer. The upper 16bits are the core freq and the mem
+// freq is the lower 16bits. All the values are in MHz
+	do
+	{
+		XNVCTRLQueryTargetAttribute (dpy, NV_CTRL_TARGET_TYPE_X_SCREEN, 0,
+
+ B. Use alternative output such as VGA/DVI
 
 8. In the end there should be a file created in your current directory called
 nvXX-0xYYYYYYYY-ZZZZ.tar.gz