1. Disable Compiz and use your system for a while; by doing so, you should prevent PowerMizer from having to switch the power supply by ensuring the load on your GFX card never passes a certain level. If it’s still flickering, something else is the culprit.
2. Run Compiz with the –loose-binding option but not with –indirect-rendering. If you’re using fusion-icon, which I heavily recommend, you can right-click it and toggle these under “Compiz Options”. If you’re manually starting it, you’ll need to add/remove these switches to whatever process you use to start it.
3. Open CompizConfig Settings Manager, and in the Workarounds settings, under Utility, enable Force Synchronization between X and GLX.
4. If steps 2 or 3 worked, play around with those three settings until you find something that works for you. I personally enable loose binding due to the performance increase it gives me, but your mileage may vary.

If all else fails, read on.

Since you’re reading this, you must be encountering the PowerMizer bug, and it’s time to mess around with PowerMizer. This will involve editing your xorg.conf file a bit, so I (HIGHLY, HIGHLY) recommend you make a backup by running

beforehand. Note the capitalization of the X in X11. In case this somehow royally messes up your system and/or config file (which it shouldn’t; it just involves adding one line) you can just copy the backup over the modified version.

With that out of the way, open /etc/X11/xorg.conf for editing. You’ll need to do so as root, so run

(or whatever editor you want to use if you don’t like gedit). Now, find the section that starts with

. It should have the line

nearby; if it doesn’t, something’s wrong. Start a new line somewhere between

and the

that should come a few lines later, and add

to the beginning of that line. What you put after that determines the settings PowerMizer will apply. There are four ‘parameters’ you can put in the configuration string, each of which has a hexadecimal value; you specify them in the form “parameter1=value1; parameter2=value2; parameter3=value3…”. Since the values are all hexadecimal, you need to include a 0x before each of the values.

• PerfLevelSrc tells PowerMizer what ‘strategies’ to use on AC and battery power. The two strategies are ‘fixed’ and ‘adaptive’; ‘fixed’ tells PowerMizer to always use the same clock frequency, and ‘adaptive’ tells it to dynamically select one. The value for PerfLevelSrc is of the form xxyy, where xx specifies the battery power strategy and yy specifies the AC power strategy. Fixed is 22, and adaptive is 33.
• PowerMizerDefault corresponds to the default clock frequency for battery power. 1 corresponds to maximum performance, 3 is maximum battery life, and 2 is an intermediate. Yes, I know it’s backwards.
• PowerMizerDefaultAC is the same as PowerMizerDefault, but for AC power.
• PowerMizerEnable enables PowerMizer, obviously. Set this to 1.

So for example, if I wanted mycard to run at maximum frequency on AC power, but adaptive frequency on battery, I would use the line

If I wanted it to always run on minimum power on battery and maximum power on AC, the line would be

You get the picture. By way of example, the relevant setting of my xorg.conf file currently reads:

Once you’re done, save and close, and reboot and/or restart X. You can find more information about power settings and such at this site, which is where I got the information on the parameters for RegistryDwords.