Bitcoin Forum
June 25, 2024, 06:50:47 PM *
News: Latest Bitcoin Core release: 27.0 [Torrent]
 
   Home   Help Search Login Register More  
Pages: « 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 [44] 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 »
  Print  
Author Topic: [ANN] Kryptohash | Brand new PoW algo | 320bit hash | ed25519 | PID algo for dif  (Read 149396 times)
jox
Hero Member
*****
Offline Offline

Activity: 681
Merit: 500


View Profile
January 03, 2015, 06:54:46 PM
 #861

catalyst 14.12, underclocked/undervolted R9 280x ~234Kh/s
wr104 (OP)
Sr. Member
****
Offline Offline

Activity: 329
Merit: 250


View Profile WWW
January 03, 2015, 08:12:23 PM
 #862

About the Intensity feature:

The implementation is different from the traditional one found in cgminer with scrypt support.  

In the cgminer-khc case, the Minimum Intensity is always 2 and the Maximum Intensity depends on what GPU you have.  The Max is calculated as the number of Stream Processors divided by the Work Size (default: 256).

Examples of Max Intensity using 256 for work size:


R9 290x:  2816 / 256 = 11
R9 290 :  2560 / 256 = 10
R9 280x:  2048 / 256 = 8
HD7970 :  2048 / 256 = 8
HD6970 :  1536 / 256 = 6


Using a number for Intensity higher than the values shown above will have no effect on these GPUs.

Finally, the Dynamic Intensity feature is disabled by default.  It doesn't work as expected.
bitman008
Full Member
***
Offline Offline

Activity: 140
Merit: 100


View Profile
January 03, 2015, 08:32:35 PM
 #863

Power of my 6*R270 mining rig increase from 620watt to 850 watt,hashrate from 90kh/s to 133kh/s.

bitman008
Full Member
***
Offline Offline

Activity: 140
Merit: 100


View Profile
January 03, 2015, 08:36:04 PM
 #864

I've switched to beta2,I am worried about my power supply. Angry

antonio8
Legendary
*
Offline Offline

Activity: 1386
Merit: 1000


View Profile
January 03, 2015, 08:54:07 PM
Last edit: January 03, 2015, 09:28:42 PM by antonio8
 #865

@wr104

I am also getting the HW errors again with the Nvidia cards.  Was there something besides the .bin files that needed to be deleted?

EDIT: It works fine for my 750ti's. Getting around 80 kh/s. Up from about 50 kh/s. The 970 gets HW errors though. Not sure what is going on with tat yet.

If you are going to leave your BTC on an exchange please send it to this address instead 1GH3ub3UUHbU5qDJW5u3E9jZ96ZEmzaXtG, I will at least use the money better than someone who steals it from the exchange. Thanks Wink
bitman008
Full Member
***
Offline Offline

Activity: 140
Merit: 100


View Profile
January 03, 2015, 09:15:15 PM
 #866

cgminer is dead on my R280x after mining for half an hour.

wr104 (OP)
Sr. Member
****
Offline Offline

Activity: 329
Merit: 250


View Profile WWW
January 03, 2015, 09:59:55 PM
Last edit: January 03, 2015, 10:13:03 PM by wr104
 #867

I've switched to beta2,I am worried about my power supply. Angry

There is no need to go back to beta2. The Kernel is the same.

You can remove the '--cl-opt-disable' option, delete the 'kshake320-546-uint2{GPUNAME}v1w256i4.bin' file and cgminer beta3 should run just like the beta2.  
 
Or, you can take advantage of the Intensity setting.  For your R270, you can use intensity 3 or 4 on each card.  Try specifying:  -I 3  or -I 4


@wr104

I am also getting the HW errors again with the Nvidia cards.  Was there something besides the .bin files that needed to be deleted?

EDIT: It works fine for my 750ti's. Getting around 80 kh/s. Up from about 50 kh/s. The 970 gets HW errors though. Not sure what is going on with tat yet.

As I said, the Kernel hasn't changed.  If the '--cl-opt-disable' option isn't helping on the 970, just remove it and cgminer should pretty much work as before.  Don't forget to delete 'kshake320-546-uint2{GPUNAME}v1w256i4.bin' every time you make a change so, cgminer is forced to re-compile the Kernel next time it is executed.

Also, try changing the Work Size using the '--worksize' option on your 970.  The default is now 256 and your nVidia GPU might not like that value.

 
antonio8
Legendary
*
Offline Offline

Activity: 1386
Merit: 1000


View Profile
January 03, 2015, 10:36:09 PM
 #868

@wr104

I am also getting the HW errors again with the Nvidia cards.  Was there something besides the .bin files that needed to be deleted?

EDIT: It works fine for my 750ti's. Getting around 80 kh/s. Up from about 50 kh/s. The 970 gets HW errors though. Not sure what is going on with tat yet.

As I said, the Kernel hasn't changed.  If the '--cl-opt-disable' option isn't helping on the 970, just remove it and cgminer should pretty much work as before.  Don't forget to delete 'kshake320-546-uint2{GPUNAME}v1w256i4.bin' every time you make a change so, cgminer is forced to re-compile the Kernel next time it is executed.

Also, try changing the Work Size using the '--worksize' option on your 970.  The default is now 256 and your nVidia GPU might not like that value.

 


Tried changing the --worksize to 128 and 512 same issue with HW error. I am not sure if there are other multiples to try with it.

I have also been deleting the .bin files everytime I run the bat.

If you are going to leave your BTC on an exchange please send it to this address instead 1GH3ub3UUHbU5qDJW5u3E9jZ96ZEmzaXtG, I will at least use the money better than someone who steals it from the exchange. Thanks Wink
wr104 (OP)
Sr. Member
****
Offline Offline

Activity: 329
Merit: 250


View Profile WWW
January 03, 2015, 10:53:26 PM
 #869

@wr104

I am also getting the HW errors again with the Nvidia cards.  Was there something besides the .bin files that needed to be deleted?

EDIT: It works fine for my 750ti's. Getting around 80 kh/s. Up from about 50 kh/s. The 970 gets HW errors though. Not sure what is going on with tat yet.

As I said, the Kernel hasn't changed.  If the '--cl-opt-disable' option isn't helping on the 970, just remove it and cgminer should pretty much work as before.  Don't forget to delete 'kshake320-546-uint2{GPUNAME}v1w256i4.bin' every time you make a change so, cgminer is forced to re-compile the Kernel next time it is executed.

Also, try changing the Work Size using the '--worksize' option on your 970.  The default is now 256 and your nVidia GPU might not like that value.

 


Tried changing the --worksize to 128 and 512 same issue with HW error. I am not sure if there are other multiples to try with it.

I have also been deleting the .bin files everytime I run the bat.

Add these two paramters to the command line:   --debug  2>log.txt

And look inside log.txt  what is the Preferred Work Size for the 970.
antonio8
Legendary
*
Offline Offline

Activity: 1386
Merit: 1000


View Profile
January 03, 2015, 11:06:28 PM
 #870

@wr104

I am also getting the HW errors again with the Nvidia cards.  Was there something besides the .bin files that needed to be deleted?

EDIT: It works fine for my 750ti's. Getting around 80 kh/s. Up from about 50 kh/s. The 970 gets HW errors though. Not sure what is going on with tat yet.

As I said, the Kernel hasn't changed.  If the '--cl-opt-disable' option isn't helping on the 970, just remove it and cgminer should pretty much work as before.  Don't forget to delete 'kshake320-546-uint2{GPUNAME}v1w256i4.bin' every time you make a change so, cgminer is forced to re-compile the Kernel next time it is executed.

Also, try changing the Work Size using the '--worksize' option on your 970.  The default is now 256 and your nVidia GPU might not like that value.

 


Tried changing the --worksize to 128 and 512 same issue with HW error. I am not sure if there are other multiples to try with it.

I have also been deleting the .bin files everytime I run the bat.

Add these two paramters to the command line:   --debug  2>log.txt

And look inside log.txt  what is the Preferred Work Size for the 970.

I see Preferred vector but not worksize, I do see max work size reported though:

[2015-01-03 17:55:10] CL Platform vendor: NVIDIA Corporation
 [2015-01-03 17:55:10] CL Platform name: NVIDIA CUDA
 [2015-01-03 17:55:10] CL Platform version: OpenCL 1.1 CUDA 6.5.30
 [2015-01-03 17:55:10] List of devices:
 [2015-01-03 17:55:10]    0   GeForce GTX 970
 [2015-01-03 17:55:10]    1   GeForce GTX 750 Ti
 [2015-01-03 17:55:10]    2   GeForce GTX 750 Ti
 [2015-01-03 17:55:10]    3   GeForce GTX 750 Ti
 [2015-01-03 17:55:10] Selected 0: GeForce GTX 970
 [2015-01-03 17:55:18] Preferred vector width reported 1
 [2015-01-03 17:55:18] Max work group size reported 1024
 [2015-01-03 17:55:18] Max mem alloc size is 1073741824
 [2015-01-03 17:55:18] GPU 0: No Dynamic Interval was set. Disabling Dynamic Intensity
 [2015-01-03 17:55:18] GPU 0: No Intensity value was set. Disabling Intensity
 [2015-01-03 17:55:18] No binary found, generating from source
 [2015-01-03 17:55:18] Setting worksize to 256
 [2015-01-03 17:55:18] cl_amd_media_ops not found, will not set BITALIGN
 [2015-01-03 17:55:18] BFI_INT patch requiring device not found, will not BFI_INT patch
 [2015-01-03 17:55:18] CompilerOptions: -D WORKSIZE=256
 [2015-01-03 17:55:18] Binary size for gpu 0 found in binary slot 0: 423533
 [2015-01-03 17:55:18] Initialising kernel kshake320-546-uint2.cl without bitalign, 1 vectors and worksize 256
 [2015-01-03 17:55:18] Creating kryptohash buffer size 872415232
 [2015-01-03 17:55:18] initCl() finished. Found GeForce GTX 970
 [2015-01-03 17:55:18] Pushing sem post to thread 0
 [2015-01-03 17:55:18] Init GPU thread 1 GPU 1 virtual GPU 1
 [2015-01-03 17:55:18] CL Platform vendor: NVIDIA Corporation
 [2015-01-03 17:55:18] CL Platform name: NVIDIA CUDA
 [2015-01-03 17:55:18] CL Platform version: OpenCL 1.1 CUDA 6.5.30
 [2015-01-03 17:55:18] List of devices:
 [2015-01-03 17:55:18] opencl_thread_init: thread id=0 using kshake320v2
 [2015-01-03 17:55:18]    0   GeForce GTX 970
 [2015-01-03 17:55:18] Waiting on sem in miner thread
 [2015-01-03 17:55:18] Popping work from get queue to get work
 [2015-01-03 17:55:18] Got work from get queue to get work for thread 0

If you are going to leave your BTC on an exchange please send it to this address instead 1GH3ub3UUHbU5qDJW5u3E9jZ96ZEmzaXtG, I will at least use the money better than someone who steals it from the exchange. Thanks Wink
wr104 (OP)
Sr. Member
****
Offline Offline

Activity: 329
Merit: 250


View Profile WWW
January 03, 2015, 11:09:10 PM
 #871

I meant to say max group work size.  Sorry.

Delete the .bin and try --worksize 1024 and see what happens.


Also, if you want your 750s with a different worksize value, you can use for example: --worksize 1024,256,256,256
antonio8
Legendary
*
Offline Offline

Activity: 1386
Merit: 1000


View Profile
January 03, 2015, 11:27:51 PM
 #872

I meant to say max group work size.  Sorry.

Delete the .bin and try --worksize 1024 and see what happens.


Also, if you want your 750s with a different worksize value, you can use for example: --worksize 1024,256,256,256

Still get the HW error but that is ok, my 750ti's owrk. Even if the --worksize 1024 worked the speed went from over 200 kh/s down to 40 kh/s.

I must need something else, file, for the 970 to work. Like maybe an updated open cl file or something or this Nvidia driver is holding it back.

If you are going to leave your BTC on an exchange please send it to this address instead 1GH3ub3UUHbU5qDJW5u3E9jZ96ZEmzaXtG, I will at least use the money better than someone who steals it from the exchange. Thanks Wink
PeaMine
Hero Member
*****
Offline Offline

Activity: 979
Merit: 510



View Profile
January 03, 2015, 11:33:08 PM
 #873

@wr104

I am also getting the HW errors again with the Nvidia cards.  Was there something besides the .bin files that needed to be deleted?

EDIT: It works fine for my 750ti's. Getting around 80 kh/s. Up from about 50 kh/s. The 970 gets HW errors though. Not sure what is going on with tat yet.

What build instructions or wget and command line did you use to get it working with your 750ti ?
I've been trying for days, I must be missing something.
I'm on Linux 64bit Ubuntu 14.

Datacenter Technician and Electrician.  If you have any questions feel free to ask me as I am generally bored looking at logs and happy to help during free time.
WORE
Sr. Member
****
Offline Offline

Activity: 350
Merit: 250


View Profile
January 03, 2015, 11:47:24 PM
 #874

I've switched to beta2,I am worried about my power supply. Angry

There is no need to go back to beta2. The Kernel is the same.

You can remove the '--cl-opt-disable' option, delete the 'kshake320-546-uint2{GPUNAME}v1w256i4.bin' file and cgminer beta3 should run just like the beta2.  
 
Or, you can take advantage of the Intensity setting.  For your R270, you can use intensity 3 or 4 on each card.  Try specifying:  -I 3  or -I 4


@wr104

I am also getting the HW errors again with the Nvidia cards.  Was there something besides the .bin files that needed to be deleted?

EDIT: It works fine for my 750ti's. Getting around 80 kh/s. Up from about 50 kh/s. The 970 gets HW errors though. Not sure what is going on with tat yet.

As I said, the Kernel hasn't changed.  If the '--cl-opt-disable' option isn't helping on the 970, just remove it and cgminer should pretty much work as before.  Don't forget to delete 'kshake320-546-uint2{GPUNAME}v1w256i4.bin' every time you make a change so, cgminer is forced to re-compile the Kernel next time it is executed.

Also, try changing the Work Size using the '--worksize' option on your 970.  The default is now 256 and your nVidia GPU might not like that value.

 


A request for increased value range of 'gpu-engine'.  Presently it will not accept a value below 1Ghz, default it tries to run at 1.1Ghz.

Presently if using he "cl-opt-disable" : true, with "Intensity" : "8" on an R9 280x DD, I am getting a fair hash rate of about 235KH/s but the driver is locking up, but not until card reaches around 90C which puts the VRM's near max tolerance of 120C with the increased wattage draw under the new kernel.

Would it be possible to allow input for gpu-engine to run down to around 850Mhz on the tahiti to maintain full utilization of memory while providing the ability to lower running temps across all the hardware in the card?
antonio8
Legendary
*
Offline Offline

Activity: 1386
Merit: 1000


View Profile
January 04, 2015, 12:31:13 AM
 #875

@wr104

I am also getting the HW errors again with the Nvidia cards.  Was there something besides the .bin files that needed to be deleted?

EDIT: It works fine for my 750ti's. Getting around 80 kh/s. Up from about 50 kh/s. The 970 gets HW errors though. Not sure what is going on with tat yet.

What build instructions or wget and command line did you use to get it working with your 750ti ?
I've been trying for days, I must be missing something.
I'm on Linux 64bit Ubuntu 14.

I did not compile or build at all.

Just downloaded and ran the miner from the github. I am on Windows 7 64 bit.

Did you try just running the miner that he already has built for Linux? https://github.com/kryptohash/cgminer-khc/releases/tag/v3.7.6-Beta3

EDIT: Here is my bat that I use: cgminer.exe --kryptohash --kernel kshake320v2 -d 1,2,3 -I 14 -o http://khc.nonce-pool.com:4300 -u YOUR_USER_NAME_HERE -p YOUR_PASSWORD_HERE --shaders 640 --shaders-mul 8
I probably should be using Nonce Pools stratum though.

If you are going to leave your BTC on an exchange please send it to this address instead 1GH3ub3UUHbU5qDJW5u3E9jZ96ZEmzaXtG, I will at least use the money better than someone who steals it from the exchange. Thanks Wink
wr104 (OP)
Sr. Member
****
Offline Offline

Activity: 329
Merit: 250


View Profile WWW
January 04, 2015, 01:17:51 AM
 #876

I've switched to beta2,I am worried about my power supply. Angry

There is no need to go back to beta2. The Kernel is the same.

You can remove the '--cl-opt-disable' option, delete the 'kshake320-546-uint2{GPUNAME}v1w256i4.bin' file and cgminer beta3 should run just like the beta2.  
 
Or, you can take advantage of the Intensity setting.  For your R270, you can use intensity 3 or 4 on each card.  Try specifying:  -I 3  or -I 4


@wr104

I am also getting the HW errors again with the Nvidia cards.  Was there something besides the .bin files that needed to be deleted?

EDIT: It works fine for my 750ti's. Getting around 80 kh/s. Up from about 50 kh/s. The 970 gets HW errors though. Not sure what is going on with tat yet.

As I said, the Kernel hasn't changed.  If the '--cl-opt-disable' option isn't helping on the 970, just remove it and cgminer should pretty much work as before.  Don't forget to delete 'kshake320-546-uint2{GPUNAME}v1w256i4.bin' every time you make a change so, cgminer is forced to re-compile the Kernel next time it is executed.

Also, try changing the Work Size using the '--worksize' option on your 970.  The default is now 256 and your nVidia GPU might not like that value.

 


A request for increased value range of 'gpu-engine'.  Presently it will not accept a value below 1Ghz, default it tries to run at 1.1Ghz.

Presently if using he "cl-opt-disable" : true, with "Intensity" : "8" on an R9 280x DD, I am getting a fair hash rate of about 235KH/s but the driver is locking up, but not until card reaches around 90C which puts the VRM's near max tolerance of 120C with the increased wattage draw under the new kernel.

Would it be possible to allow input for gpu-engine to run down to around 850Mhz on the tahiti to maintain full utilization of memory while providing the ability to lower running temps across all the hardware in the card?

I'll look into the 'gpu-engine' parameter but for the mean time, try lowering the Intensity for GPU0.  For some reason, GPU0 always seems to be the one getting hotter. The R9 280x has 2048 Stream Engines, meaning that Intensity 8 is the max value you can use on it.
 
Also, beware that on systems with more than one GPU, cgminer may incorrectly show the temperature of a secondary cards as the GPU0's temp.  I realized this after I put my second 290x on my rig that has the HD7970 and I kept the HD7970 disabled.  To correct this, use the '--gpu-map' option to correctly map the GPU number seen by OpenCL with the GPU number seen by ADL.  
In my case, since I only have 2 GPUs, the mapping was simple:  --gpu-map 0:1,1:0

bitcurrenty
Full Member
***
Offline Offline

Activity: 129
Merit: 100


View Profile
January 04, 2015, 01:45:56 AM
 #877

The new cgminer is almost killing my power supply.I think I need to adjust intensity lower.

wr104 (OP)
Sr. Member
****
Offline Offline

Activity: 329
Merit: 250


View Profile WWW
January 04, 2015, 02:15:55 AM
 #878

I've switched to beta2,I am worried about my power supply. Angry

There is no need to go back to beta2. The Kernel is the same.

You can remove the '--cl-opt-disable' option, delete the 'kshake320-546-uint2{GPUNAME}v1w256i4.bin' file and cgminer beta3 should run just like the beta2.  
 
Or, you can take advantage of the Intensity setting.  For your R270, you can use intensity 3 or 4 on each card.  Try specifying:  -I 3  or -I 4


@wr104

I am also getting the HW errors again with the Nvidia cards.  Was there something besides the .bin files that needed to be deleted?

EDIT: It works fine for my 750ti's. Getting around 80 kh/s. Up from about 50 kh/s. The 970 gets HW errors though. Not sure what is going on with tat yet.

As I said, the Kernel hasn't changed.  If the '--cl-opt-disable' option isn't helping on the 970, just remove it and cgminer should pretty much work as before.  Don't forget to delete 'kshake320-546-uint2{GPUNAME}v1w256i4.bin' every time you make a change so, cgminer is forced to re-compile the Kernel next time it is executed.

Also, try changing the Work Size using the '--worksize' option on your 970.  The default is now 256 and your nVidia GPU might not like that value.

 


A request for increased value range of 'gpu-engine'.  Presently it will not accept a value below 1Ghz, default it tries to run at 1.1Ghz.

Presently if using he "cl-opt-disable" : true, with "Intensity" : "8" on an R9 280x DD, I am getting a fair hash rate of about 235KH/s but the driver is locking up, but not until card reaches around 90C which puts the VRM's near max tolerance of 120C with the increased wattage draw under the new kernel.

Would it be possible to allow input for gpu-engine to run down to around 850Mhz on the tahiti to maintain full utilization of memory while providing the ability to lower running temps across all the hardware in the card?

I've been playing with all the GPU settings (Manual Engine clock, Autotune, Powertune, etc) on all my cards and this seems to be an issue with the drivers or with the ADL SDK.

On my R9 290x, only reducing Powertune reduces the GPU clock.  
On my HD7970, nothing makes the GPU clock change.
On my HD6950, everything works fine.
rigging
Jr. Member
*
Offline Offline

Activity: 59
Merit: 10


View Profile
January 04, 2015, 03:13:21 AM
 #879

I guess when beta4 comes out,it will consume as much power as scrypt algo. Angry

██████    ... ANTSHARES, DIGITAL ASSETS FOR EVERYONE  ...    ██████
████    ... ANTSHARES ICO STARTS AUGUST 8th  ...     ████
▀▀▀▀▀▀▀▀▀▀▀▀▀▀     ANTSHARES     ▀▀▀▀▀▀▀▀▀▀▀▀▀▀ (https://antshares.com/?ref=rigging)
WORE
Sr. Member
****
Offline Offline

Activity: 350
Merit: 250


View Profile
January 04, 2015, 03:51:44 AM
Last edit: January 04, 2015, 08:13:59 AM by WORE
 #880

I've switched to beta2,I am worried about my power supply. Angry

There is no need to go back to beta2. The Kernel is the same.

You can remove the '--cl-opt-disable' option, delete the 'kshake320-546-uint2{GPUNAME}v1w256i4.bin' file and cgminer beta3 should run just like the beta2.  
 
Or, you can take advantage of the Intensity setting.  For your R270, you can use intensity 3 or 4 on each card.  Try specifying:  -I 3  or -I 4


@wr104

I am also getting the HW errors again with the Nvidia cards.  Was there something besides the .bin files that needed to be deleted?

EDIT: It works fine for my 750ti's. Getting around 80 kh/s. Up from about 50 kh/s. The 970 gets HW errors though. Not sure what is going on with tat yet.

As I said, the Kernel hasn't changed.  If the '--cl-opt-disable' option isn't helping on the 970, just remove it and cgminer should pretty much work as before.  Don't forget to delete 'kshake320-546-uint2{GPUNAME}v1w256i4.bin' every time you make a change so, cgminer is forced to re-compile the Kernel next time it is executed.

Also, try changing the Work Size using the '--worksize' option on your 970.  The default is now 256 and your nVidia GPU might not like that value.

 


A request for increased value range of 'gpu-engine'.  Presently it will not accept a value below 1Ghz, default it tries to run at 1.1Ghz.

Presently if using he "cl-opt-disable" : true, with "Intensity" : "8" on an R9 280x DD, I am getting a fair hash rate of about 235KH/s but the driver is locking up, but not until card reaches around 90C which puts the VRM's near max tolerance of 120C with the increased wattage draw under the new kernel.

Would it be possible to allow input for gpu-engine to run down to around 850Mhz on the tahiti to maintain full utilization of memory while providing the ability to lower running temps across all the hardware in the card?

I've been playing with all the GPU settings (Manual Engine clock, Autotune, Powertune, etc) on all my cards and this seems to be an issue with the drivers or with the ADL SDK.

On my R9 290x, only reducing Powertune reduces the GPU clock.  
On my HD7970, nothing makes the GPU clock change.
On my HD6950, everything works fine.


On a 280x I can directly specify the clock setting or give it a range 1000-1100+ which cgminer is supposed to dynamically adjust based on the temp-overheat+temp-hysteresis and was observed doing such on beta 2.  It just won't go below 1Ghz even if told to.

Is a bummer that one cannot do the same based on VRM temps as this would have saved a lot of cards throughout the history of BTC.  No biggy for me though, I'd just swap out burned VRM's with new ones as I have to do a lot of component level board repairs on my day gig.  Could be another interesting implementation of PID in there as well.   Smiley

I don't have the GPU temp swap thing going on unless it has GPU-Z spoofed, funny though, GPU0 does run hotter that GPU1, but VRM on GPU1 runs hotter than GPU0.  But this has been observed mining under other algo's so may be a problem with that card.  Whacky, the temp-overheat+temp-hysteresis that is triggering clock down seems to clock down the cooler GPU1 running card.  But realistically, the '"cl-opt-disable" : true' option is for water cooled rigs, I was running the clock at 1Ghz WS256 I6 and still hit 90C and caught the VRM at 120C and only saw 24Kh/s gain, not worth it to me unless I can has less Mhz on the clock and avoid having to unbrick my card.
Pages: « 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 [44] 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 »
  Print  
 
Jump to:  

Powered by MySQL Powered by PHP Powered by SMF 1.1.19 | SMF © 2006-2009, Simple Machines Valid XHTML 1.0! Valid CSS!