|
Title: 2x5970 Rig SICK Post by: bjornsni on August 01, 2012, 07:16:40 PM Keep having problems with this rig
Running 11.2 Cgminer 2.2.7 Installed SDK 2.1 and I keep getting this.... Any thoughts? [2012-08-01 14:11:21] Started cgminer 2.2.7 [2012-08-01 14:11:23] AMD OpenCL SDK 2.6 installed giving POOR PERFORMANCE on R5 xxx and R6xxx. [2012-08-01 14:11:23] Downgrade SDK, delete .bin files and restart cgminer to fi [2012-08-01 14:11:21] Started cgminer 2.2.7 [2012-08-01 14:11:23] AMD OpenCL SDK 2.6 installed giving POOR PERFORMANCE on R5 xxx and R6xxx. [2012-08-01 14:11:23] Downgrade SDK, delete .bin files and restart cgminer to fi x this. [2012-08-01 14:11:23] Need to specify at least one pool server. Input server details. URL: Title: Re: 2x5970 Rig SICK Post by: ChanceCoats123 on August 01, 2012, 08:10:58 PM Looks like you had previously been running 2.6 and didn't fully clean that installation before you installed 2.1. The computer will run the newest installed software.
On top of that, you didn't correctly input the pool information... Title: Re: 2x5970 Rig SICK Post by: AndrewBUD on August 01, 2012, 08:12:36 PM keep your cgminer.conf file.... upgrade cgminer.... make sure proper SDK is installed after driver sweep....
Title: Re: 2x5970 Rig SICK Post by: bjornsni on August 01, 2012, 08:17:49 PM Looks like you had previously been running 2.6 and didn't fully clean that installation before you installed 2.1. The computer will run the newest installed software. On top of that, you didn't correctly input the pool information... cgminer runs, but only runs 1 card, the other is SICK...this is just what comes up right away. Title: Re: 2x5970 Rig SICK Post by: AndrewBUD on August 01, 2012, 10:37:40 PM try a different kernel... Try Diablo instead of PhatK or pocblm
Title: Re: 2x5970 Rig SICK Post by: ChanceCoats123 on August 01, 2012, 10:54:23 PM Looks like you had previously been running 2.6 and didn't fully clean that installation before you installed 2.1. The computer will run the newest installed software. On top of that, you didn't correctly input the pool information... cgminer runs, but only runs 1 card, the other is SICK...this is just what comes up right away. It helps if you mention all of that in the OP. ::) Title: Re: 2x5970 Rig SICK Post by: AndrewBUD on August 01, 2012, 11:21:06 PM well it does say it in the title.....
Are you running this card at stock settings? (have you tried hitting it with a hammer?) J/K :) Title: Re: 2x5970 Rig SICK Post by: ChanceCoats123 on August 01, 2012, 11:58:57 PM well it does say it in the title..... Are you running this card at stock settings? (have you tried hitting it with a hammer?) J/K :) I was unaware hardware could contract disease... Title: Re: 2x5970 Rig SICK Post by: bjornsni on August 02, 2012, 02:15:04 PM well it does say it in the title..... Are you running this card at stock settings? (have you tried hitting it with a hammer?) J/K :) Thought about it. I've searched for ways to do a clean sweep of SDK, is there a thread out there I am not seeing on how to do this? Title: Re: 2x5970 Rig SICK Post by: AndrewBUD on August 02, 2012, 07:19:27 PM get "Driver Cleaner" software
Uninstall catalyst.... use driver sweeper..... save your config file from cgminer folder.... delete everythign else....Install Catalyst, install cgminer 2.6.1 replace your config file in cgminer folder... The end :) Title: Re: 2x5970 Rig SICK Post by: -ck on August 03, 2012, 10:40:45 AM Whenever you change drivers or SDK with cgminer, if you are to actually get different performance, you MUST delete any .bin files that cgminer has generated from the previously installed drivers/sdk combo.
Title: Re: 2x5970 Rig SICK Post by: Cablez on August 03, 2012, 12:06:34 PM Also, driver sweeper does not get rid of SDK files that may be left. You need to check the system32 and syswow64 folders in the windows directory for files called atiocl*.dll and amdocl*.dll.
This is especially important when downgrading SDKs, not so much for upgrading. Title: Re: 2x5970 Rig SICK Post by: AndrewBUD on August 03, 2012, 12:09:09 PM ^ you're right..... that's what made me change kernels...... comparing identical rigs I am getting better performance with diablo kernel.....
|