Pages:
Author

Topic: [ANN] sgminer v5 - optimized X11/X13/NeoScrypt/Lyra2RE/etc. kernel-switch miner - page 48. (Read 877859 times)

newbie
Activity: 4
Merit: 0
It's possibly seeing the iGPU on the Intel CPU as another GPU so try --gpu-platform -1 in your .bat

Hi, thanks for the response.  Gave it a go, and it seems that --gpu-platform 0 is the one which yields results (1 or 2 crashes the miner).  Using --gpu-platform 0 by itself mines on the 7950, one core of the 7990, and the cpu.  Setting the devices to -d 1,2 mines on one core of the 7990 and the cpu (the latter is OFF by default when --remove-disabled is not set).  
full member
Activity: 212
Merit: 100
Hello, all.  Sorry to post what appears to be one of many --gpu-map questions, but unfortunately I haven't found anything which has worked over the past 10 days or so that I've been wrestling with this off and on.  Any assistance would be appreciated.

I combined two single-gpu mining rigs into a single machine for easier watercooling, and have accordingly run into a problem with OpenCL recognizing the devices.  I am running an Intel 4790k cpu, a 7950, and 7990 on Windows 10.  I've upgraded Catalyst to 15.7.1, the latest at time of writing, and to sgminer_v5.1_2015-03-09-win32 as provided by NiceHash.  

The full output of sgminer -n is below:

Code:
[14:17:30] CL Platform vendor: Advanced Micro Devices, Inc.
[14:17:30] CL Platform name: AMD Accelerated Parallel Processing
[14:17:30] CL Platform version: OpenCL 2.0 AMD-APP (1800.8)
[14:17:30] Platform devices: 3
[14:17:30] 0 Tahiti
[14:17:30] 1 Tahiti
[14:17:30] 2 Tahiti
[14:17:30] Number of ADL devices: 3
[14:17:30] ATI ADL Overdrive5 API found.
[14:17:30] ATI ADL Overdrive6 API found.
[14:17:30] Found 16 logical ADL adapters
[14:17:30] ADL index 0, id 169197120 - BIOS partno.: 113-C3810100-103, version: 015.017.000.001, date: 2012/04/11 02:08
[14:17:30] GPU 0 assigned: iAdapterIndex:0 iPresent:1 strUDID:PCI_VEN_1002&DEV_679A&SUBSYS_27601462&REV_00_4&1286464&0&0008A iBusNumber:1 iDeviceNumber:0 iFunctionNumber:0 iVendorID:1002 name:AMD Radeon HD 7900 Series
[14:17:30] ADL index 1, id 169197120 - BIOS partno.: 113-C3810100-103, version: 015.017.000.001, date: 2012/04/11 02:08
[14:17:30] ADL index 2, id 169197120 - BIOS partno.: 113-C3810100-103, version: 015.017.000.001, date: 2012/04/11 02:08
[14:17:30] ADL index 3, id 169197120 - BIOS partno.: 113-C3810100-103, version: 015.017.000.001, date: 2012/04/11 02:08
[14:17:30] ADL index 4, id 169197120 - BIOS partno.: 113-C3810100-103, version: 015.017.000.001, date: 2012/04/11 02:08
[14:17:30] ADL index 5, id 169197120 - BIOS partno.: 113-C3810100-103, version: 015.017.000.001, date: 2012/04/11 02:08
[14:17:30] ADL index 6, id 178252608 - BIOS partno.: 113-C47601M0-101, version: 015.032.000.004, date: 2013/05/03 15:54
[14:17:30] GPU 1 assigned: iAdapterIndex:6 iPresent:1 strUDID:PCI_VEN_1002&DEV_679B&SUBSYS_0B2A1002&REV_00_6&13A8AB83&0&00400009A iBusNumber:4 iDeviceNumber:0 iFunctionNumber:0 iVendorID:1002 name:AMD Radeon HD 7900 Series
[14:17:30] ADL index 7, id 178252608 - BIOS partno.: 113-C47601M0-101, version: 015.032.000.004, date: 2013/05/03 15:54
[14:17:30] ADL index 8, id 178252608 - BIOS partno.: 113-C47601M0-101, version: 015.032.000.004, date: 2013/05/03 15:54
[14:17:30] ADL index 9, id 178252608 - BIOS partno.: 113-C47601M0-101, version: 015.032.000.004, date: 2013/05/03 15:54
[14:17:30] ADL index 10, id 178252608 - BIOS partno.: 113-C47601M0-101, version: 015.032.000.004, date: 2013/05/03 15:54
[14:17:30] ADL index 11, id 178252608 - BIOS partno.: 113-C47601M0-101, version: 015.032.000.004, date: 2013/05/03 15:54
[14:17:30] ADL index 12, id 173347584 - BIOS partno.: 113-C47601S0-101, version: 015.032.000.004, date: 2013/05/03 15:56
[14:17:30] GPU 2 assigned: iAdapterIndex:12 iPresent:0 strUDID:PCI_VEN_1002&DEV_679B&SUBSYS_0B2A1002&REV_00_6&2EC6759&0&00800009A iBusNumber:5 iDeviceNumber:0 iFunctionNumber:0 iVendorID:1002 name:AMD Radeon HD 7900 Series
[14:17:30] ADL index 13, id 173347584 - FAILED to get BIOS info
[14:17:30] Failed to ADL_Adapter_ID_Get. Error -1
[14:17:30] ADL index 14, id 173347584 - FAILED to get BIOS info
[14:17:30] Failed to ADL_Adapter_ID_Get. Error -1
[14:17:30] ADL index 15, id 173347584 - FAILED to get BIOS info
[14:17:30] Failed to ADL_Adapter_ID_Get. Error -1
[14:17:30] GPU 0 AMD Radeon HD 7900 Series hardware monitoring enabled
[14:17:30] ADL GPU 0 is Adapter index 0 and maps to adapter id 169197120
[14:17:30] GPU 0 BIOS partno.: 113-C3810100-103, version: 015.017.000.001, date: 2012/04/11 02:08
[14:17:30] Failed to ADL_Overdrive5_FanSpeed_Get for default value
[14:17:30] GPU 1 AMD Radeon HD 7900 Series hardware monitoring enabled
[14:17:30] ADL GPU 1 is Adapter index 6 and maps to adapter id 178252608
[14:17:30] GPU 1 BIOS partno.: 113-C47601M0-101, version: 015.032.000.004, date: 2013/05/03 15:54
[14:17:30] Failed to ADL_Overdrive5_FanSpeed_Get for default value
[14:17:30] GPU 2 AMD Radeon HD 7900 Series hardware monitoring enabled
[14:17:30] ADL GPU 2 is Adapter index 12 and maps to adapter id 173347584
[14:17:30] GPU 2 BIOS partno.: 113-C47601S0-101, version: 015.032.000.004, date: 2013/05/03 15:56
[14:17:30] Failed to ADL_Overdrive5_FanSpeed_Get for default value
[14:17:30] 3 GPU devices max detected

It looks to me that device 0 (the 7950) has been assigned to ADL 0 and devices 1 and 2 (the 7990) have been assigned to ADL 6 and 12 respectively.

I have had limited success with the -d command, and am able to run the 7950 by setting the -d 0 flag.  However, attempting to runt the 7990 with -d 1,2 provides one core of the 7990 and what appears to be the cpu based upon the hashrate.  I have tried adding "-d 1,2 --gpu-map 1:6,2:12 --remove-disabled" and similar the 7990 batch file without success.  

I may well be missing something obvious.  Thanks in advance for any advice.

It's possibly seeing the iGPU on the Intel CPU as another GPU so try --gpu-platform -1 in your .bat
newbie
Activity: 4
Merit: 0
Hello, all.  Sorry to post what appears to be one of many --gpu-map questions, but unfortunately I haven't found anything which has worked over the past 10 days or so that I've been wrestling with this off and on.  Any assistance would be appreciated.

I combined two single-gpu mining rigs into a single machine for easier watercooling, and have accordingly run into a problem with OpenCL recognizing the devices.  I am running an Intel 4790k cpu, a 7950, and 7990 on Windows 10.  I've upgraded Catalyst to 15.7.1, the latest at time of writing, and to sgminer_v5.1_2015-03-09-win32 as provided by NiceHash.  

The full output of sgminer -n is below:

Code:
[14:17:30] CL Platform vendor: Advanced Micro Devices, Inc.
[14:17:30] CL Platform name: AMD Accelerated Parallel Processing
[14:17:30] CL Platform version: OpenCL 2.0 AMD-APP (1800.8)
[14:17:30] Platform devices: 3
[14:17:30] 0 Tahiti
[14:17:30] 1 Tahiti
[14:17:30] 2 Tahiti
[14:17:30] Number of ADL devices: 3
[14:17:30] ATI ADL Overdrive5 API found.
[14:17:30] ATI ADL Overdrive6 API found.
[14:17:30] Found 16 logical ADL adapters
[14:17:30] ADL index 0, id 169197120 - BIOS partno.: 113-C3810100-103, version: 015.017.000.001, date: 2012/04/11 02:08
[14:17:30] GPU 0 assigned: iAdapterIndex:0 iPresent:1 strUDID:PCI_VEN_1002&DEV_679A&SUBSYS_27601462&REV_00_4&1286464&0&0008A iBusNumber:1 iDeviceNumber:0 iFunctionNumber:0 iVendorID:1002 name:AMD Radeon HD 7900 Series
[14:17:30] ADL index 1, id 169197120 - BIOS partno.: 113-C3810100-103, version: 015.017.000.001, date: 2012/04/11 02:08
[14:17:30] ADL index 2, id 169197120 - BIOS partno.: 113-C3810100-103, version: 015.017.000.001, date: 2012/04/11 02:08
[14:17:30] ADL index 3, id 169197120 - BIOS partno.: 113-C3810100-103, version: 015.017.000.001, date: 2012/04/11 02:08
[14:17:30] ADL index 4, id 169197120 - BIOS partno.: 113-C3810100-103, version: 015.017.000.001, date: 2012/04/11 02:08
[14:17:30] ADL index 5, id 169197120 - BIOS partno.: 113-C3810100-103, version: 015.017.000.001, date: 2012/04/11 02:08
[14:17:30] ADL index 6, id 178252608 - BIOS partno.: 113-C47601M0-101, version: 015.032.000.004, date: 2013/05/03 15:54
[14:17:30] GPU 1 assigned: iAdapterIndex:6 iPresent:1 strUDID:PCI_VEN_1002&DEV_679B&SUBSYS_0B2A1002&REV_00_6&13A8AB83&0&00400009A iBusNumber:4 iDeviceNumber:0 iFunctionNumber:0 iVendorID:1002 name:AMD Radeon HD 7900 Series
[14:17:30] ADL index 7, id 178252608 - BIOS partno.: 113-C47601M0-101, version: 015.032.000.004, date: 2013/05/03 15:54
[14:17:30] ADL index 8, id 178252608 - BIOS partno.: 113-C47601M0-101, version: 015.032.000.004, date: 2013/05/03 15:54
[14:17:30] ADL index 9, id 178252608 - BIOS partno.: 113-C47601M0-101, version: 015.032.000.004, date: 2013/05/03 15:54
[14:17:30] ADL index 10, id 178252608 - BIOS partno.: 113-C47601M0-101, version: 015.032.000.004, date: 2013/05/03 15:54
[14:17:30] ADL index 11, id 178252608 - BIOS partno.: 113-C47601M0-101, version: 015.032.000.004, date: 2013/05/03 15:54
[14:17:30] ADL index 12, id 173347584 - BIOS partno.: 113-C47601S0-101, version: 015.032.000.004, date: 2013/05/03 15:56
[14:17:30] GPU 2 assigned: iAdapterIndex:12 iPresent:0 strUDID:PCI_VEN_1002&DEV_679B&SUBSYS_0B2A1002&REV_00_6&2EC6759&0&00800009A iBusNumber:5 iDeviceNumber:0 iFunctionNumber:0 iVendorID:1002 name:AMD Radeon HD 7900 Series
[14:17:30] ADL index 13, id 173347584 - FAILED to get BIOS info
[14:17:30] Failed to ADL_Adapter_ID_Get. Error -1
[14:17:30] ADL index 14, id 173347584 - FAILED to get BIOS info
[14:17:30] Failed to ADL_Adapter_ID_Get. Error -1
[14:17:30] ADL index 15, id 173347584 - FAILED to get BIOS info
[14:17:30] Failed to ADL_Adapter_ID_Get. Error -1
[14:17:30] GPU 0 AMD Radeon HD 7900 Series hardware monitoring enabled
[14:17:30] ADL GPU 0 is Adapter index 0 and maps to adapter id 169197120
[14:17:30] GPU 0 BIOS partno.: 113-C3810100-103, version: 015.017.000.001, date: 2012/04/11 02:08
[14:17:30] Failed to ADL_Overdrive5_FanSpeed_Get for default value
[14:17:30] GPU 1 AMD Radeon HD 7900 Series hardware monitoring enabled
[14:17:30] ADL GPU 1 is Adapter index 6 and maps to adapter id 178252608
[14:17:30] GPU 1 BIOS partno.: 113-C47601M0-101, version: 015.032.000.004, date: 2013/05/03 15:54
[14:17:30] Failed to ADL_Overdrive5_FanSpeed_Get for default value
[14:17:30] GPU 2 AMD Radeon HD 7900 Series hardware monitoring enabled
[14:17:30] ADL GPU 2 is Adapter index 12 and maps to adapter id 173347584
[14:17:30] GPU 2 BIOS partno.: 113-C47601S0-101, version: 015.032.000.004, date: 2013/05/03 15:56
[14:17:30] Failed to ADL_Overdrive5_FanSpeed_Get for default value
[14:17:30] 3 GPU devices max detected

It looks to me that device 0 (the 7950) has been assigned to ADL 0 and devices 1 and 2 (the 7990) have been assigned to ADL 6 and 12 respectively.

I have had limited success with the -d command, and am able to run the 7950 by setting the -d 0 flag.  However, attempting to runt the 7990 with -d 1,2 provides one core of the 7990 and what appears to be the cpu based upon the hashrate.  I have tried adding "-d 1,2 --gpu-map 1:6,2:12 --remove-disabled" and similar the 7990 batch file without success.  

I may well be missing something obvious.  Thanks in advance for any advice.
hero member
Activity: 1088
Merit: 531
Free Crypto in Stake.com Telegram t.me/StakeCasino
I'm trying to use this miner with x11 algo, but no luck.I'm getting this error: Rejected 1287f082(-> this number changes) Diff 13/0.020 GPU 0  (Share above target.)

My GPU is MSI R9 270 (2GB), I'm using Windows 10 Pro 64-bit and latest AMD drivers..

Anyone knows a solution?
legendary
Activity: 2912
Merit: 1091
--- ChainWorks Industries ---
windows 32bit by the looks of things also ...
is that correct? ...
and 1172 ... thats a nice push Smiley ... i cant get mine that far ...
#crysx

Works on win64 as well. If you use linux, you need a 32 bit installation.

i have tried it sp ...

did an install today of windows 7 x64 with x32 miner and bins ... the increase was nice - but nothing to write home about Smiley ...

i will try fedora 21 x32 tomorrow i think ... see how much we can push ...

but to be honest - this is too much a headache for a full install to 'downgrade' to a x32 installation on the whole farm ...

its just not worth my time and effort ...

its easier to pay someone like you or wolf to rewrite the bins and do it privately ... and that of course is only IF you were interested and had the time to be bothered doing it ...

for me though - its too much effort on my part ...

we are not talking just one machine here - which is why i can afford the small drop in hashrate across the whole farm ...

are you looking at increasing the hashrate for x11 on your fork of ccminer? ...

#crysx
sp_
legendary
Activity: 2926
Merit: 1087
Team Black developer
windows 32bit by the looks of things also ...
is that correct? ...
and 1172 ... thats a nice push Smiley ... i cant get mine that far ...
#crysx

Works on win64 as well but you need a sgminer compiled for win32. If you use linux, you need a 32 bit installation.
newbie
Activity: 10
Merit: 0
What power settings and intensity are people using the the AMD 280 @ 1100/1500.  I find intensity 17 throttles with anything under +11%

my settings for the miner below ...

./sgminer -o stratum+tcp://mining-ace.granitecoin.com:7009/ -u chrysophylax.amd125 -p x -k x11mod -w 64 --xintensity 512 -g 2 --thread-concurrency 8192 --lookup-gap 2 --gpu-engine 1100 --gpu-memclock 1500 --gpu-fan 97

DO NOT use these 'pool' settings when you mine - as you will be mining for ME then ... change them to your own settings ... im using an exact paste of what i use to mine the amd part of teh farm for posteritys sake only ...

this is the test system that i use to hammer the gigabyte 280x oc cards ...

i did away with --intensity parameter and started using the --xintensity ... apparently it has something to do with the way it calculates hashes in teh card memory - so xintensity works better ... the devs know better though - so im not going into the technical side of it ... 'it just works' - thats how i like the machines ...

with a little tweaking - you could probably do a bit more ... but using wolfs x11 bins and the latest sgminer-dev compile ( 5.1.1-19-g8bf1 ) - each card is running hashing at about 6.5MH under fedora 19 x64 ( catalyst driver - kmod-catalyst-3.14.27-100.fc19.x86_64-14.4-1.fc19.21.x86_64 ) ...

as sp mentioned earlier - if you use a 32bit system and run the russian bins - you can get at least another 1MH more on each card ... but from what i understand - its no where near as stable as wolfs bins ... and i like my machines to be working flat out Wink ...

hope this helps ...

#crysx


I'm using russian bin and x11 mining is stable with latest windows sgminer downloaded from nicehash (7.7 Mh/s on 280x)

      "xintensity": "128",
      "worksize": "64",
      "gpu-engine": "1172",
      "gpu-memclock": "1500",
      "gpu-threads": "2",
      "gpu-powertune": "20"




windows 32bit by the looks of things also ...

is that correct? ...

and 1172 ... thats a nice push Smiley ... i cant get mine that far ...

#crysx

I'm using windows 8.1 x64 with Catalyst 15.7.1 with 2xAsus R9280XDC2T3GD5 (no monitor attached).
On my desktop with only one of those cards, Windows 10 and same Catalyst version I have to lower gpu-engine to 1170. Iin order to see videos while mining the xintensity must be lowered to 64.

One thing I noticed is that gpu-memclock is fixed to 1600 and I'm unable to change that either with sgminer or asus tweak
legendary
Activity: 2912
Merit: 1091
--- ChainWorks Industries ---
What power settings and intensity are people using the the AMD 280 @ 1100/1500.  I find intensity 17 throttles with anything under +11%

my settings for the miner below ...

./sgminer -o stratum+tcp://mining-ace.granitecoin.com:7009/ -u chrysophylax.amd125 -p x -k x11mod -w 64 --xintensity 512 -g 2 --thread-concurrency 8192 --lookup-gap 2 --gpu-engine 1100 --gpu-memclock 1500 --gpu-fan 97

DO NOT use these 'pool' settings when you mine - as you will be mining for ME then ... change them to your own settings ... im using an exact paste of what i use to mine the amd part of teh farm for posteritys sake only ...

this is the test system that i use to hammer the gigabyte 280x oc cards ...

i did away with --intensity parameter and started using the --xintensity ... apparently it has something to do with the way it calculates hashes in teh card memory - so xintensity works better ... the devs know better though - so im not going into the technical side of it ... 'it just works' - thats how i like the machines ...

with a little tweaking - you could probably do a bit more ... but using wolfs x11 bins and the latest sgminer-dev compile ( 5.1.1-19-g8bf1 ) - each card is running hashing at about 6.5MH under fedora 19 x64 ( catalyst driver - kmod-catalyst-3.14.27-100.fc19.x86_64-14.4-1.fc19.21.x86_64 ) ...

as sp mentioned earlier - if you use a 32bit system and run the russian bins - you can get at least another 1MH more on each card ... but from what i understand - its no where near as stable as wolfs bins ... and i like my machines to be working flat out Wink ...

hope this helps ...

#crysx


I'm using russian bin and x11 mining is stable with latest windows sgminer downloaded from nicehash (7.7 Mh/s on 280x)

      "xintensity": "128",
      "worksize": "64",
      "gpu-engine": "1172",
      "gpu-memclock": "1500",
      "gpu-threads": "2",
      "gpu-powertune": "20"




windows 32bit by the looks of things also ...

is that correct? ...

and 1172 ... thats a nice push Smiley ... i cant get mine that far ...

#crysx
newbie
Activity: 10
Merit: 0
What power settings and intensity are people using the the AMD 280 @ 1100/1500.  I find intensity 17 throttles with anything under +11%

my settings for the miner below ...

./sgminer -o stratum+tcp://mining-ace.granitecoin.com:7009/ -u chrysophylax.amd125 -p x -k x11mod -w 64 --xintensity 512 -g 2 --thread-concurrency 8192 --lookup-gap 2 --gpu-engine 1100 --gpu-memclock 1500 --gpu-fan 97

DO NOT use these 'pool' settings when you mine - as you will be mining for ME then ... change them to your own settings ... im using an exact paste of what i use to mine the amd part of teh farm for posteritys sake only ...

this is the test system that i use to hammer the gigabyte 280x oc cards ...

i did away with --intensity parameter and started using the --xintensity ... apparently it has something to do with the way it calculates hashes in teh card memory - so xintensity works better ... the devs know better though - so im not going into the technical side of it ... 'it just works' - thats how i like the machines ...

with a little tweaking - you could probably do a bit more ... but using wolfs x11 bins and the latest sgminer-dev compile ( 5.1.1-19-g8bf1 ) - each card is running hashing at about 6.5MH under fedora 19 x64 ( catalyst driver - kmod-catalyst-3.14.27-100.fc19.x86_64-14.4-1.fc19.21.x86_64 ) ...

as sp mentioned earlier - if you use a 32bit system and run the russian bins - you can get at least another 1MH more on each card ... but from what i understand - its no where near as stable as wolfs bins ... and i like my machines to be working flat out Wink ...

hope this helps ...

#crysx


I'm using russian bin and x11 mining is stable with latest windows sgminer downloaded from nicehash (7.7 Mh/s on 280x)

      "xintensity": "128",
      "worksize": "64",
      "gpu-engine": "1172",
      "gpu-memclock": "1500",
      "gpu-threads": "2",
      "gpu-powertune": "20"


newbie
Activity: 34
Merit: 0

what kernel are you using MehZhure ??

I believe it is Wolf0's.  So far, it has been stable for 16 hours and counting.
legendary
Activity: 2912
Merit: 1091
--- ChainWorks Industries ---
What power settings and intensity are people using the the AMD 280 @ 1100/1500.  I find intensity 17 throttles with anything under +11%

my settings for the miner below ...

./sgminer -o stratum+tcp://mining-ace.granitecoin.com:7009/ -u chrysophylax.amd125 -p x -k x11mod -w 64 --xintensity 512 -g 2 --thread-concurrency 8192 --lookup-gap 2 --gpu-engine 1100 --gpu-memclock 1500 --gpu-fan 97

DO NOT use these 'pool' settings when you mine - as you will be mining for ME then ... change them to your own settings ... im using an exact paste of what i use to mine the amd part of teh farm for posteritys sake only ...

this is the test system that i use to hammer the gigabyte 280x oc cards ...

i did away with --intensity parameter and started using the --xintensity ... apparently it has something to do with the way it calculates hashes in teh card memory - so xintensity works better ... the devs know better though - so im not going into the technical side of it ... 'it just works' - thats how i like the machines ...

with a little tweaking - you could probably do a bit more ... but using wolfs x11 bins and the latest sgminer-dev compile ( 5.1.1-19-g8bf1 ) - each card is running hashing at about 6.5MH under fedora 19 x64 ( catalyst driver - kmod-catalyst-3.14.27-100.fc19.x86_64-14.4-1.fc19.21.x86_64 ) ...

as sp mentioned earlier - if you use a 32bit system and run the russian bins - you can get at least another 1MH more on each card ... but from what i understand - its no where near as stable as wolfs bins ... and i like my machines to be working flat out Wink ...

hope this helps ...

#crysx
hero member
Activity: 547
Merit: 502
What power settings and intensity are people using the the AMD 280 @ 1100/1500.  I find intensity 17 throttles with anything under +11%
hero member
Activity: 528
Merit: 500

appreciate that ...

i no longer hold any 290 or 290x cards - only gigabyte 280x oc cards now in the farm ... so it really is purely for the 'how' ... for me anyway ...

-g 3 can work well with sgminer - but i have found that ( at least with the 280x ) that a higher clock rate and a lower thread count ( -g 2 in the 280x - at 1100 gpuclock / 1500 memclock ) it worked the best ... some cards work really well at 1125 / 1500 ( or even 1125 / 1490 ) but the gigabyte ones i have cant be pushed that far - and are restricted to the driver version contained in the repo for fedora 19 x64 ...

im just too damned lazy to do implicit installs on each and every machine contained in the farm ...

as for the power usage ... you will find that with EVERY card used today ... and it all boils down to the heat ...

no matter how good your heat dissipation may be - the rule of thumb is simple ... the higher the clocks - the higher the heat generation - the higher the power ...

thefarm is a perfect example of that ... when its freezing cold ( not that i could get it that cold - but humor me and just flow ) - thefarm uses the least power yet hashes the same if not better than when its warm or hot ... adversely - the hotter thefarm - the more power it uses for about the same hashrate ...

so its got to work harder the hotter it is - which uses more power ...

anyway - bed for me ... im stuffed and babbling now ...

#crysx

That is has been my experience with electronics in general.  In this case, the temperature is remaining constant, but the power usage keeps rising.  Matter of fact, as of right now, the power usage has continued to creep up, and is currently sitting at 171.0W.  The voltage has ticked up another notch, and the amperage has increased by about 1 amp since I last posted.

 I pulled this guy up  here:-   https://bitcointalksearch.org/topic/m.12020302

what kernel are you using MehZhure ??
legendary
Activity: 1274
Merit: 1006
wolf0 since you probably don't answer on messages, I'll ask here: are you mining ethereum yet?
newbie
Activity: 34
Merit: 0

same worksize and xintensity that you use for 2 threads?  I use 64 for each.

That is correct.  64 on both.
full member
Activity: 169
Merit: 100
Not sure the settings are going to be stable just yet.  There is one weird quirk I have observed, and it is making me a bit suspicious. 

I have noticed it happening on three different restarts so far.  The first was several hours ago, when I first ran across the settings.  The power usage started out at about 150W.  Over about an hour, it had crept up to about 160W.  I wanted to try some different settings, so I changed the conf and restarted.  This time it started at about 166W.  Over about 4 hours, it crept up to about 175W.

Just to see if I was losing my mind, I decided to shut down and let the system cool all the way down.  Once it was sitting at 38C, I restarted.  Power usage was about 166W on startup.  It has been running for 36 minutes, and the power usage is now up to 169.4W.  And now it is 169.5W.  I just noticed both the amperage and the voltage increased by the minimum increment.  And now it is 169.6W.

I don't know.  Something just doesn't feel quite right about it. 

Oh, as for the "magic number".... and this to your conf file
Code:
"gpu-threads": "3"

Maybe it doesn't work for everyone, but my gpu really likes running 3 threads.

same worksize and xintensity that you use for 2 threads?  I use 64 for each.
newbie
Activity: 34
Merit: 0

appreciate that ...

i no longer hold any 290 or 290x cards - only gigabyte 280x oc cards now in the farm ... so it really is purely for the 'how' ... for me anyway ...

-g 3 can work well with sgminer - but i have found that ( at least with the 280x ) that a higher clock rate and a lower thread count ( -g 2 in the 280x - at 1100 gpuclock / 1500 memclock ) it worked the best ... some cards work really well at 1125 / 1500 ( or even 1125 / 1490 ) but the gigabyte ones i have cant be pushed that far - and are restricted to the driver version contained in the repo for fedora 19 x64 ...

im just too damned lazy to do implicit installs on each and every machine contained in the farm ...

as for the power usage ... you will find that with EVERY card used today ... and it all boils down to the heat ...

no matter how good your heat dissipation may be - the rule of thumb is simple ... the higher the clocks - the higher the heat generation - the higher the power ...

thefarm is a perfect example of that ... when its freezing cold ( not that i could get it that cold - but humor me and just flow ) - thefarm uses the least power yet hashes the same if not better than when its warm or hot ... adversely - the hotter thefarm - the more power it uses for about the same hashrate ...

so its got to work harder the hotter it is - which uses more power ...

anyway - bed for me ... im stuffed and babbling now ...

#crysx

That is has been my experience with electronics in general.  In this case, the temperature is remaining constant, but the power usage keeps rising.  Matter of fact, as of right now, the power usage has continued to creep up, and is currently sitting at 171.0W.  The voltage has ticked up another notch, and the amperage has increased by about 1 amp since I last posted.
legendary
Activity: 2912
Merit: 1091
--- ChainWorks Industries ---
Not sure the settings are going to be stable just yet.  There is one weird quirk I have observed, and it is making me a bit suspicious.  

I have noticed it happening on three different restarts so far.  The first was several hours ago, when I first ran across the settings.  The power usage started out at about 150W.  Over about an hour, it had crept up to about 160W.  I wanted to try some different settings, so I changed the conf and restarted.  This time it started at about 166W.  Over about 4 hours, it crept up to about 175W.

Just to see if I was losing my mind, I decided to shut down and let the system cool all the way down.  Once it was sitting at 38C, I restarted.  Power usage was about 166W on startup.  It has been running for 36 minutes, and the power usage is now up to 169.4W.  And now it is 169.5W.  I just noticed both the amperage and the voltage increased by the minimum increment.  And now it is 169.6W.

I don't know.  Something just doesn't feel quite right about it.  

Oh, as for the "magic number".... and this to your conf file
Code:
"gpu-threads": "3"

Maybe it doesn't work for everyone, but my gpu really likes running 3 threads.

appreciate that ...

i no longer hold any 290 or 290x cards - only gigabyte 280x oc cards now in the farm ... so it really is purely for the 'how' ... for me anyway ...

-g 3 can work well with sgminer - but i have found that ( at least with the 280x ) that a higher clock rate and a lower thread count ( -g 2 in the 280x - at 1100 gpuclock / 1500 memclock ) it worked the best ... some cards work really well at 1125 / 1500 ( or even 1125 / 1490 ) but the gigabyte ones i have cant be pushed that far - and are restricted to the driver version contained in the repo for fedora 19 x64 ...

im just too damned lazy to do implicit installs on each and every machine contained in the farm ...

as for the power usage ... you will find that with EVERY card used today ... and it all boils down to the heat ...

no matter how good your heat dissipation may be - the rule of thumb is simple ... the higher the clocks - the higher the heat generation - the higher the power ...

thefarm is a perfect example of that ... when its freezing cold ( not that i could get it that cold - but humor me and just flow ) - thefarm uses the least power yet hashes the same if not better than when its warm or hot ... adversely - the hotter thefarm - the more power it uses for about the same hashrate ...

so its got to work harder the hotter it is - which uses more power ...

anyway - bed for me ... im stuffed and babbling now ...

#crysx
newbie
Activity: 34
Merit: 0
Not sure the settings are going to be stable just yet.  There is one weird quirk I have observed, and it is making me a bit suspicious. 

I have noticed it happening on three different restarts so far.  The first was several hours ago, when I first ran across the settings.  The power usage started out at about 150W.  Over about an hour, it had crept up to about 160W.  I wanted to try some different settings, so I changed the conf and restarted.  This time it started at about 166W.  Over about 4 hours, it crept up to about 175W.

Just to see if I was losing my mind, I decided to shut down and let the system cool all the way down.  Once it was sitting at 38C, I restarted.  Power usage was about 166W on startup.  It has been running for 36 minutes, and the power usage is now up to 169.4W.  And now it is 169.5W.  I just noticed both the amperage and the voltage increased by the minimum increment.  And now it is 169.6W.

I don't know.  Something just doesn't feel quite right about it. 

Oh, as for the "magic number".... and this to your conf file
Code:
"gpu-threads": "3"

Maybe it doesn't work for everyone, but my gpu really likes running 3 threads.
legendary
Activity: 924
Merit: 1000
Tweak the settings, and tweak some more.  Try different bins.  Tweak settings again. And again.  And again.  Finally, I think I found the sweet spot.  My r9 290 has been stable for 4.5 hours now.  The temp has stayed under 65C.  The power consumption has stayed about 175W.  Sgminer is reporting a hash rate > 9.6 Mh/s and my mining pool has continuously been reporting my accepted hash rate is at, or greater, than 10 Mh/s.

Wow if you dont mind sharing your findings I would greatly appreciate it. I just flashed my unlocked 290 to 290x and getting 10.4MH but if your getting >9.6 on a 290 I would love to know how.
Pages:
Jump to: