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.

If you use fc11 that makes things pretty complicated and I'd leave my fingers from it. AFAIK fc11 already uses snapshots of a radeon git-branch (radeon-gem-cs3 I'd guess) in order to enable kms and dri2.
Apparently the new power options haven't made it in that branch, and quite possibly wont until the branch is merged into master again.
So building from git-master right now will most likely give you a not working X-Server... or if you're lucky "just" kms and dri2 will stop working.

Comment

One of the features that the Overdrive program offers on Windows is control of the memory voltage. Are the docs for programming this available so we can implement this on Linux as well? In particular, I want to try using these new 1.6V DDR2 SODIMMs in my HP dv5z notebook to try to reduce heat and power consumption.

Since I don't run Windows on this laptop, just using Overdrive isn't an option.

I've read the Family 11H BKDG but the memory controller registers described there only control the memory timing, not the voltage. This appears to be more a function of the 780 chipset, and I haven't found any docs on that yet. (And like most notebooks, the BIOS is too heavily lobotomized to provide this control there.)

edit: while we're on the subject of lobotomized notebook BIOSes, it would be nice to see CoreBoot supported on AMD Puma notebooks. It looks like right now the only issues are legal, not technical:

I dunno about anyone else, but I find the closed-source stranglehold on BIOSes to be pretty aggravating. You can never get updates from your vendors on a timely basis (or at all), particularly if your board is more than several months old, and some bugs simply never get fixed. (E.g., my HP dv5z came with BIOS F.08, which had a buggy ACPI DSDT that didn't return valid results for the Thermal Zone module. As such, the Linux kernel refused to use this module, so you couldn't get temperature monitoring from ACPI. That was around 8 months ago it was released; today they're up to BIOS F.32 and it's still not fixed. I emailed various people at HP and got no response; I've been running with my own fixed DSDT since then.) With AMD's strong support of open source development, it would be a good idea to use a pure open source BIOS in all your motherboard reference designs from now on. The OEMs may not care about fixing their damn bugs, but we do.

Comment

Nothing at all? Mostly concentrating modesetting and memory management in kernelspace led/will lead to better (read: one that has access to both modesetting and acceleration and can do power management at the right time and in the right place without the risk of hangs or such ) power management after power management gets ported to kernel too. (and this moving/porting power management to DRM is the thing bridgman talked about)

Comment

Do power-saving options still work with KMS, DRI2 and xorg 1.7? I ask because that is the current standard configuration in Arch Linux now and with it power saving options seem not be working anymore, and without KMS X hangs. I have these messages in Xorg.log:

(WW) RADEON(0): Option "DynamicPM" is not used
(WW) RADEON(0): Option "ForceLowPowerMode" is not used
(WW) RADEON(0): Option "ClockGating" is not used

What is the status here?

BTW, the limitation that OpenGL wouldn't output to a portion of my second monitor at all is gone! Also most other things seem to work fine, only Radeon xv is not working on the second monitor, I get a black screen there, which is no problem since I can use OpenGL or X11 outputs in mplayer.

Thanks for any info, signorRossi.

Comment

Do power-saving options still work with KMS, DRI2 and xorg 1.7? I ask because that is the current standard configuration in Arch Linux now and with it power saving options seem not be working anymore, and without KMS X hangs. I have these messages in Xorg.log:

(WW) RADEON(0): Option "DynamicPM" is not used
(WW) RADEON(0): Option "ForceLowPowerMode" is not used
(WW) RADEON(0): Option "ClockGating" is not used

BTW, the limitation that OpenGL wouldn't output to a portion of my second monitor at all is gone! Also most other things seem to work fine, only Radeon xv is not working on the second monitor, I get a black screen there, which is no problem since I can use OpenGL or X11 outputs in mplayer.

You may need a newer radeon drm kernel modules and/or ddx depending on what versions you are currently using.