10.2: Ultra Low Power State Confusion & Crossfire Eyefinity

When AMD was first briefing us on the 10.2 drivers, one of the first things they discussed was Ultra Low Power State (ULPS) support – this was probably a mistake. In our initial Radeon HD 5870 article covering the whole Evergreen architecture we discussed ULPS, albeit not under that name. ULPS was one of the many features AMD had briefed us about in September when they introduced the 5000 series, where ULPS allows AMD to power down the slave card(s) in a Crossfire configuration to a state even lower than idle. For the 5870/5970, this meant being able to reduce the slave(s) from 27W at idle to 20W under ULPS. This is only a 7W difference, but combined with other idle-efficient hardware it can become a notable difference. At the time it had been our understanding that this feature was enabled right out of the gate.

So imagine our confusion when at CES AMD is telling us that they are just enabling that feature for the entire 5000 series. Until that moment as far as we knew this feature was already enabled.

This started an almost immediate chain of confusion between ourselves and AMD. Terry Makedon – AMD’s Manager of Software Product Management – was giving the presentation and found himself at the end of an odd stare from us rather quickly. When we asked for clarification on this, he said that this feature was just finally going to be enabled in the mainstream Catalyst drivers, and that previously it had only been enabled for the 5970 in the launch drivers for that card. After expressing our displeasure on the issue, we quickly moved on due to time constraints.


The Radeon HD 5970: The card ULPS was practically made for

This brings us to February, where we started work on this article after wrapping up the Radeon HTPC investigation last week. Seeking further clarification on the issue and to once again express our displeasure with how this was handled, we sent an email to our favorite PR contact over at AMD, Evan Groenke. Evan has only been AMD’s PR frontman for hardware editors since the start of the year, and he’s been the guy largely responsible for helping us nail down all the issues we were seeing with the new Radeon 5000 series cards in HTPC use.

After sending that email early Friday morning, we got a phone call from Evan later that day… from the ski slopes. What was supposed to be a long weekend for him turned out to be a bit of a working weekend as he did what he could to dig in to the issue and to find a better explanation for us. Thanks to him we have a solid explanation on what’s going on and why our earlier tests were not as compromised as we once thought they were.

The key issue for AMD is that they did not consider the software side of ULPS to be ready for public use when the 5000 series launched, so it was not enabled in the Catalyst drivers at the time. ULPS was then enabled for the 5970 launch, where AMD was confident it was going to work correctly under the very limited conditions encountered by a single-card dual-GPU setup. But this was only enabled for the launch driver for the 5970 – it was never enabled in the mainline Catalyst drivers.

The issue for us, and why we were initially so displeased, was that it had never been communicated to us that ULPS wasn’t enabled from the beginning. We thought that it was enabled, AMD thought we knew that it wasn’t. So when we did our testing of the 5700, 5800, and 5900 series, we based all of our data on the idea that this feature was enabled, when in retrospect it wasn’t. Worse, it was enabled on the drivers we used to test the 5970 but not the 5870/5850, so our results would have the 5970 consuming less power at idle than what a real user would get if they used the mainline Catalyst drivers. This makes the results invalid, and was the source of our concerns.


Our original 5970 results

All of this was finally clarified when Evan was able to tell us two things: that the driver set we used to test the 5970 had been posted as a hotfix driver for the 5970 launch, and that it wasn’t the only driver with ULPS enabled. The former is of particular importance since coming from CES our interpretation had been that ULPS was not enabled on any public driver build, when in fact it just hadn’t been enabled on any mainline driver build – it had in fact been available in public hotfixes such as the 5970 launch driver. The latter is important because it was an undocumented feature of the 9.12 hotfix, which as we explained earlier is the precursor to much of what’s in the 10.2 driver being released today. So if you used the 9.12 hotfix, then you’ve already been enjoying ULPS on your 5000-series Crossfire setups.

With that in mind, here’s what the issue ultimately boils down to: Unless you were using the 5970 launch driver or the 9.12 hotfix, you have not been enjoying the benefit of ULPS. Specifically, unless you have used those drivers your idle power usage on the 5970 would have been around 7W higher than what we found in our initial 5970 review. It’s only now with today’s 10.2 driver that this is finally being enabled for customers using the mainline driver. If that’s you, then the 10.2 drivers should reduce your idle power usage some.

To settle this point, here we have a re-test of the 5970 using the 10.1 Catalyst drivers, and the 10.3 beta drivers AMD has provided us.


Our new 5970 results. Note: This is a different test setup than for our original results

The end result: a difference of 8W, out of 170W, meaning enabling it reduces idle power usage by around 5% on our overclocked Core i7 920 setup.

Moving on from ULPS, we have Crossfire Eyefinity, one of the other features that was previously exposed in the 9.12 hotfix driver. Much like ULPS, this feature was originally only enabled for the 5970 while AMD worked out the kinks in the technology. Since the 5970’s launch this feature has made a great deal of progress – it’s no longer a whitelist feature that only works on certain games, but rather it’s a blacklist feature where AMD only disables it on games where there are known issues.

We strongly suspect that anyone that had a vested interest in a Crossfire Eyefinity setup with a pair of 5800/5700 series cards already is on the 9.12 hotfix, but nevertheless this brings Crossfire Eyefinity in to the mainline drivers for everyone else.

Index 10.2: Crossfire Profiles, DisplayPort Audio, & Crossfire Rearchitecture
Comments Locked

75 Comments

View All Comments

  • iamezza - Thursday, February 18, 2010 - link

    Ever since Vista DPI scaling works on ALL applications, it works completely differently to the way it did in XP, which had lots of compatibility problems with programs.
    It is much more preferable to use the DPI scaling and run the monitor at it's native res.
  • BernardP - Friday, February 19, 2010 - link

    Nice to know. I'll give it a try when I move to Windows 8 (?), as I intend to stay with XP for another 2 years.
  • mariush - Wednesday, February 17, 2010 - link

    That's just crazy. You should always you the native resolution of the LCD screen.

    Otherwise, the LCD screen just resizes the image to its native resolution causing blurriness.

    LCD doesn't work like CRTs work, they have fixed pixel sizes.
  • Roland00 - Wednesday, February 17, 2010 - link

    Correct, BernardP should instead increase the DPI under windows to 125%. Same "effective resolution" for everything becomes 25% bigger but the graphics will be much sharper.
  • chizow - Wednesday, February 17, 2010 - link

    Good to see AMD trying hard to address some of their deficiencies in relation to Nvidia's drivers. Please keep on them about the CrossFireX profiles though...it makes no sense for them to encrypt their profile xml and not expose CrossFire/AA compatibility bits to the end user, especially since they love to claim they're the "open standards" and "community friendly" company.....

    Crossing this hurdle would make CrossFire a much more appealing option for high-end users as CrossFire Performance, buying new games, and expectations for AA support go hand-in-hand for most enthusiasts.
  • poohbear - Wednesday, February 17, 2010 - link

    I just switched from an nvidia 8800gt to an ATI 5770, and the biggest pet peeve is how CCC doesnt have game specific profiles for us so we can choose which AA setting we want and the type of AA. I dont want transparent AA on any of my strat games because its useless, but would like it in my FPS games. What on earth is so hard for AMD to include a tool so simple like Nvidia has for years????? They already have a clumsy "profile" feauture that we can setup, but its far from convenient and easy to use, unlike Nvidias which is so simple and straight to the point.

    Get w/ the program AMD, your hardware rocks but your drivers are not very convenient or user friendly. If u want the masses to switch from Nvidia to your products atleast give them a user friendly CCC in this regards. It's looooong overdue.
  • Tanclearas - Wednesday, February 17, 2010 - link

    While ATI has this OCD issue of releasing monthly drivers for some products, others are left out in the cold.

    http://support.amd.com/us/kbarticles/Pages/GPU39_A...">http://support.amd.com/us/kbarticles/Pages/GPU39_A...

    There are no drivers for a Windows OS that has been for sale for MONTHS, for a currently shipping product.

  • papapapapapapapababy - Wednesday, February 17, 2010 - link

    WHAT ABOUT THE REST OF THE WORLD? THE HD 4xxxUSERS? LETS THINK ABOUT 1% OF THE MARKET AND GTFO THE REST. ARG. GREAT. EYEFINITY? CROSSFIRE? WHO GIVES ASHT! I HATE ATI DRIVERS. HATE. GIVE ME A CLEAN, FAST, FUNCTIONAL CONTROL PANEL YOU SILLY MONKEY INSIDE A SUIT ( LIKE NVIDIA DOES) NO MORE Microsoft .NET Framework !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
  • Zstream - Wednesday, February 17, 2010 - link

    I really have to wonder about half you people. Are you seriously complaining about using .net? Are you going to tell me that installing the CCC pannel is going to ruin a machine? It has all the options as most 3rd party programs do. What exactly are you referring to when saying the panel is not fast?

    What world do you live in... I had 2x3870 and use 2x4850. What exactly are you doing to the card that requires a rant like this?
  • papapapapapapapababy - Wednesday, February 17, 2010 - link

    let me explain, the 4850 is the perfect card for the sill user. Why? excessive heat. To much power power consumption. (that's why i waited for the better option >4770) Now if you are a 2x4850 user that beyond silly. thats stupid. Why? there are better options. Now about the net part. Yes. I dont need that bloatware. LIL BACK STORY: ATI DITCHED THE OLD CONTROL PANEL, INTRODUCED A SLOW, BROKEN, BLOATED, INFERIOR CCC PANEL, AND REMOVED THE OPTION OF USING THE OLD ONE, GREAT BUT THE BEST PART THEY HAVE THE FKN BRAINFART OF ASKING ME TO USE .NET? MORE GARBAGE? Nvidia doESNT DO THAT. ID DOESNT FORCE ANY KIND OF bloatware. NO EXTRA SERVICES. NO .NET UPDATES. NOTHING. EXCEPT THIS: FAST AND VERSATILE CONTROL PANEL

Log in

Don't have an account? Sign up now