Diff of /nouveau-pm/FAQ [c4b4f4] .. [d1bba6]  Maximize  Restore

Switch to side-by-side view

--- a/nouveau-pm/FAQ
+++ b/nouveau-pm/FAQ
@@ -28,4 +28,41 @@
 	- Take a look in nvidia-settings and set the current Clock state to Adaptive
 6. "The PowerMizer mode is not Adaptive"
-	- Use nvidia-setting to change the mode+	- Use nvidia-setting to change the mode
+7. "Timeout while waiting for the driver to reach default 2D frequencies"
+	There is a number of reasons for this message to happen please take a look
+	section "II. "ERROR - Timeout..." and what does it mean"
+II. "ERROR - Timeout..." and what does it mean
+	By default the program monitor_downclocking check for how long it has been
+	run in order to prevent unwanted endless loop. It may occur if the ddx/driver
+	does not go to the lowest frequencies - the ones returned by
+1. The card is integrated/built into the motherboard
+	For some reason the driver (NV-Control) does not return always return
+	the correct value of NV_CTRL_GPU_DEFAULT_2D_CLOCK_FREQS
+	(The memory returned by the function is often zero)
+- Use gdb to find the correct value and "hardcode it into monitor_downclocking.c
+XXX: Add instructions how to do it exactly, step by step
+2. There is more than one display connected/There is a HDMI/DP display connected
+From NVIDIA's forum
+		"PowerMizer often needs to keep the performance level high when there
+		are two screens connected to make sure there is enough internal bandwidth
+		in the chip to drive both displays..." [1]
+- Use a single display for that session, preferably only a VGA (the LVDS if the system is a laptop). DVI should work as well
+3. None of the above
+	The card does reach NV_CTRL_GPU_CURRENT_CLOCK_FREQS but it takes more than
+	the currently coded timeout.
+- Edit monitor_downclocking.c by changing NOUVEAU_TIME_WAIT to a more
+appropriate value. Follow the steps in README from 2 onwards
+XXX: Add instructions how to check/confirm the above statement
+[1] http://www.nvnews.net/vbulletin/showpost.php?p=2260205&postcount=2