ATI Catalyst 9.2 is out!

[Singulus]

Get it here:
http://game.amd.com/us-en/drivers_catalyst.aspx

Any folding improvements for us ? I´m going to test with F@H now.
I observed one bug so far, which sucks (but is not related to F@H): After booting windows and before starting a 3D app, the second GPU of my HD4870 X2 is in 3D mode 750 / 900 MHz and not at 507 / 500 MHz. Seems that the driver guys reintroduced a bug that nagged me until 8.12 ... *argh*.

Update 1: Still no 3D clocks while folding on GPU2 (not related to the bug mentioned above, but related to clock management, too)!
Update 2: Even with aticalrt.dll (6.14.10.186) renamed to amdcalrt.dll, there still is that GPU2 clock issue (only 2D clock folding).
Update 3: Newest CAL DLL still causes a client crash, if I press Ctrl-C to exit the GPU client.

official Info 1: CAL DLL naming change in Cat 9.2, read here: viewtopic.php?f=51&t=8533#p84423

Dia

[Ivoshiee]

ATI Catalyst™> 9.2 Folding@Home Multi-GPU support
Multi-GPU configurations using the ATI Radeon™ HD 4000 Series, ATI Radeon™ HD 3000 Series, and ATI Radeon™ HD 2000 Series of graphics accelerators will be able to use run a separate Folding@Home client on each GPU to further increase their Folding@Home performance.

What is that? Is it indeed a new feature?

[Singulus]

ATI Catalyst™> 9.2 Folding@Home Multi-GPU support
Multi-GPU configurations using the ATI Radeon™ HD 4000 Series, ATI Radeon™ HD 3000 Series, and ATI Radeon™ HD 2000 Series of graphics accelerators will be able to use run a separate Folding@Home client on each GPU to further increase their Folding@Home performance.

What is that? Is it indeed a new feature?

Where did you get that info from? But what´s new about that? It (one client for each GPU) worked with Vista x64 since 9.1 and for other Win-OSes even before 9.1.

Dia

[Ivoshiee]

ATI Catalyst™> 9.2 Folding@Home Multi-GPU support
Multi-GPU configurations using the ATI Radeon™ HD 4000 Series, ATI Radeon™ HD 3000 Series, and ATI Radeon™ HD 2000 Series of graphics accelerators will be able to use run a separate Folding@Home client on each GPU to further increase their Folding@Home performance.

What is that? Is it indeed a new feature?

Where did you get that info from? But what´s new about that? It (one client for each GPU) worked with Vista x64 since 9.1 and for other Win-OSes even before 9.1.

Dia

http://www.amdzone.com/index.php/news/drivers/11181-catalyst-92-drivers-released

[opti2k4]

I am using 2 clients on 4870x2 and Cat 9.1 vista x64 atm. Is there a big performance increase in these drivers?

[Singulus]

I am using 2 clients on 4870x2 and Cat 9.1 vista x64 atm. Is there a big performance increase in these drivers?

I only did a few percent on a 5XXX WU and did not observe any performance increase.

Dia

[Singulus]

http://www.amdzone.com/index.php/news/drivers/11181-catalyst-92-drivers-released

That part is missing in my Releasenotes PDF .

Dia

[mhouston]

There is a CAL dll rename, so if you want to use the dlls provided by this driver, you need to copy aticalcl.dll to amdcalcl.dll and aticalrt.dll to amdcalrt.dll. There is an upcoming core that can internally handle the name change.

[Singulus]

There is a CAL dll rename, so if you want to use the dlls provided by this driver, you need to copy aticalcl.dll to amdcalcl.dll and aticalrt.dll to amdcalrt.dll. There is an upcoming core that can internally handle the name change.

-Mike

Is it intended, that a driver update doesn´t remove the amdcal*.dll files from the SysWOW64 folder? The amdcal*64.dll files are gone.

Currently these versions are on my system:
aticalrt.dll - 6.14.10.186
amdcalrt.dll - 6.14.10.158

Will try that rename thing, thanks for that update Mike .

Dia

[mhouston]

We didn't quite get the driver release and the new core up in sync. Yes, the driver update will remove the amdcal*.dll files. This was one of the reasons why we still supply dlls with the client as we knew this change was coming and couldn't be certain the new core would be fully tested in time. However, copying across the dlls and renaming, or creating a copy in the system folder and changing the name to ati* should suffice.

[Singulus]

We didn't quite get the driver release and the new core up in sync. Yes, the driver update will remove the amdcal*.dll files. This was one of the reasons why we still supply dlls with the client as we knew this change was coming and couldn't be certain the new core would be fully tested in time. However, copying across the dlls and renaming, or creating a copy in the system folder and changing the name to ati* should suffice.

Mike, please read , is it intended, that a driver update does NOT remove the amdcal*.dll files from the SysWOW64 folder (mine were still there, I deleted them for myself)?
I now copied the needed atical*.dll from SysWOW64 to the F@H app directory and renamed them to amdcal*.dll, which seems to work, thanks again.

Dia

[mhouston]

Interesting... Sorry I misread that. I'll need have our driver guys double check that in the installer. The second ASIC should be clocking up now, so I'll need to try to reproduce. Vista64 SP1 4870X2?

[TheCrazyCanuck]

I use the console client so I can just make a copy of the new DLLs and rename them in the syswow64 folder right?

[Singulus]

Interesting... Sorry I misread that. I'll need have our driver guys double check that in the installer. The second ASIC should be clocking up now, so I'll need to try to reproduce. Vista64 SP1 4870X2?

Like I said, amdcal*64.dll files are removed, but not the 32 Bit versions in my case, which are stored in the SysWOW64 folder in Vista x64.

my System:
Vista x64 SP1
Sapphire HD4870 X2 (both GPUs overdrived to 800 / 935 via CCC)
Catalyst 9.2 installed right on top of 9.1
Console Client 6.23 / Core 1.22
Core 1 has this comand line: -verbosity 9 -gpu 0
Core 2 has this comand line: -verbosity 9 -gpu 1 -forcegpu ati_r700

I will re-check that clock issue tomorrow, but I´m currently folding on both GPUs and it doesn´t work. On WU 5736 GPU1 gets 2700 PPD and GPU2 gets 1800 PPD.

Dia

[Singulus]

I use the console client so I can just make a copy of the new DLLs and rename them in the syswow64 folder right?

That should work, or have a local copy in every F@H GPU client folder and rename the 2 files there .

Dia