If this is your first visit, be sure to
check out the FAQ by clicking the
link above. You may have to register
before you can post: click the register link above to proceed. To start viewing messages,
select the forum that you want to visit from the selection below.

Are you using an IGP like the RS690 or RS48x ? If so, it relies on the CPU's memory controller to feed the display, and if the CPU clocks down too far you could get corruption. If you are using an integrated graphics part please check your CPU clock speeds; if not then please provide more info.

Are you using an IGP like the RS690 or RS48x ? If so, it relies on the CPU's memory controller to feed the display, and if the CPU clocks down too far you could get corruption. If you are using an integrated graphics part please check your CPU clock speeds; if not then please provide more info.

Hi,

I'm using a HP6910p laptop, which is using the Mobility Radeon x2300 card, which I believe is a discrete video card on this model of laptop. It is a derivative of the Mobility Radeon x1300 and I believe it is based on the R515/520 series.

How would I determine whether or not my "laptop-mode" is affecting my GPU? Just turn it off? How can I then use laptop-mode to spin down my HDD?

POWERplay Options:
Following options will not change the config file.
These options will be effective immediately. Other options on
the same command line will be ignored.
--lsp, --list-powerstates
Print information about power states and exit.
--set-powerstate=NUMBER
Set a power state listed by --list-powerstates.
--auto-powerstates=on|off
Enable/disable automatic transitions between battery and performance
modes on AC/DC transitions. This automatic mode is enabled by default,
and may compete with atieventsd style power management.

Should I try

Code:

$sudo aticonfig --auto-powerstates=off

Any problems/downside to this other than using the battery much faster?

yep, that was it...BUT can't be changed from xorg.conf as Option PowerState # has been depreciated and now atieventsd runs this dynamically. Catalyst driver 9.1 & 9.2 don't have this bug - SO this is a regression in 9.3, which of course means that it will NEVER be fixed.