|
doktor83 (OP)
|
 |
July 08, 2019, 05:08:14 AM |
|
You are using the wrong algorithm, you should use cryptonight_r : config.txt{
"cryptonight_type" : "cryptonight_r",
"intensity" : 0,
"double_threads" : true
}{
"pools" :
[
{
"pool" : "xmr.pool.minergate.com:45700",
"wallet" : "myemail",
"password" : "x",
}
]
}SRBMiner-CN.exe --config config.txt --pools pools.txt Also looks like pool rejects your connection, maybe you got banned because trying with the wrong algo? |
|
|
|
|
|
|
|
|
|
|
|
|
"Bitcoin: mining our own business since 2009" -- Pieter Wuille
|
|
|
Advertised sites are not endorsed by the Bitcoin Forum. They may be unsafe, untrustworthy, or illegal in your jurisdiction.
|
|
|
|
|
lpadua
Newbie
 Offline
Activity: 5
Merit: 0
|
|
July 08, 2019, 07:48:04 AM |
|
Thanks a lot, Dok!
I will try later to see if works and also if I´m not banned.
|
|
|
|
|
lpadua
Newbie
Offline
Activity: 5
Merit: 0
|
|
July 08, 2019, 06:18:38 PM |
|
Unfortunately, it didn't work, connecting to minergate.
Even connecting successfully with other pool, after this error:
Error CL_MEM_OBJECT_ALLOCATION_FAILURE when calling clEnqueueNDRangeKernel for kernel 0 for DeviceID 0 (Thread 0)
it starts to crash everywhere, the application, the system, you name it... I tried several cleans setup, with all type of configs but without success.
Probably some incompatibility with these drivers version.
Recommended driver : Adrenalin 18.6.1
Algorithm : Cryptonight V4 (CN/R)
Algo switching : disabled
Coin forking : disabled
Gpu watchdog : enabled [normal mode]
Startup monitor : enabled
Tweaking : enabled
[2019-07-08 20:03:13] Pools defined -> 1
[2019-07-08 20:03:13] Loading [normalv4] kernel for DEVICE BUS_ID[3]
[2019-07-08 20:03:13] Loading [normalv4] kernel for DEVICE BUS_ID[3]
[2019-07-08 20:03:13] ADL initialised successfully
[2019-07-08 20:03:14] Connected to pool.supportxmr.com:7777
[2019-07-08 20:03:14] Pool difficulty: 40000
[2019-07-08 20:03:14] Job received, block height 1874147 [ID: VRMnppD/yKP9aKoGxuekVnYwxsZh]
[2019-07-08 20:03:14] Precompiling program [BUS_ID: 3]
[2019-07-08 20:03:19] Finished program precompilation [BUS_ID: 3]
[2019-07-08 20:03:22] Error CL_MEM_OBJECT_ALLOCATION_FAILURE when calling clEnqueueNDRangeKernel for kernel 0 for DeviceID 0 (Thread 0)
Is there someone that is mining successfully with Windows 10 and a Radeon VII?
|
|
|
|
|
Topcd
Newbie
Offline
Activity: 7
Merit: 0
|
|
July 08, 2019, 07:20:26 PM |
|
Unfortunately, it didn't work, connecting to minergate.
Even connecting successfully with other pool, after this error:
Error CL_MEM_OBJECT_ALLOCATION_FAILURE when calling clEnqueueNDRangeKernel for kernel 0 for DeviceID 0 (Thread 0)
it starts to crash everywhere, the application, the system, you name it... I tried several cleans setup, with all type of configs but without success.
Probably some incompatibility with these drivers version.
Recommended driver : Adrenalin 18.6.1
Algorithm : Cryptonight V4 (CN/R)
Algo switching : disabled
Coin forking : disabled
Gpu watchdog : enabled [normal mode]
Startup monitor : enabled
Tweaking : enabled
[2019-07-08 20:03:13] Pools defined -> 1
[2019-07-08 20:03:13] Loading [normalv4] kernel for DEVICE BUS_ID[3]
[2019-07-08 20:03:13] Loading [normalv4] kernel for DEVICE BUS_ID[3]
[2019-07-08 20:03:13] ADL initialised successfully
[2019-07-08 20:03:14] Connected to pool.supportxmr.com:7777
[2019-07-08 20:03:14] Pool difficulty: 40000
[2019-07-08 20:03:14] Job received, block height 1874147 [ID: VRMnppD/yKP9aKoGxuekVnYwxsZh]
[2019-07-08 20:03:14] Precompiling program [BUS_ID: 3]
[2019-07-08 20:03:19] Finished program precompilation [BUS_ID: 3]
[2019-07-08 20:03:22] Error CL_MEM_OBJECT_ALLOCATION_FAILURE when calling clEnqueueNDRangeKernel for kernel 0 for DeviceID 0 (Thread 0)
Is there someone that is mining successfully with Windows 10 and a Radeon VII?
This problem comes from your virtual memory options in windows Radeon VII is a 16gb card so you need to set at least 16 GB of virtual memory in windows settings. Right Click on This PC > Properties > in the left, select Advanced system settings > a window pop ups , in the advanced tab and Performance section select settings> go to advanced tab > change memory virtual settings > select Custom and type 16384 (16*1024) in the initial size (min) and something more in the max size , for example 17000, remember that its 16 gb for each card, if you have two cards you should type 32768 for min, and after that click on set ( don't forget this if you don't click on set button it will get back to the previous numbers) and then ok. you are ready! lets start the SRB! |
|
|
|
|
lpadua
Newbie
Offline
Activity: 5
Merit: 0
|
|
July 09, 2019, 05:54:33 PM |
|
Letter by letter! It worked!
Thanks a lot, @Topcd, @doktor83!
|
|
|
|
|
|
doktor83 (OP)
|
|
July 10, 2019, 11:50:02 AM |
|
Letter by letter! It worked!
Thanks a lot, @Topcd, @doktor83!
Now you just need to find the best settings for your VII  |
|
|
|
Baikal miner
Newbie
Offline
Activity: 53
Merit: 0
|
|
July 10, 2019, 05:10:42 PM |
|
Iridium Coin
It is time for VERSION 5! New release is out containing new algorithm (Cn Pico) !
When new version srb?
|
|
|
|
|
|
doktor83 (OP)
|
|
July 10, 2019, 05:49:23 PM |
|
Iridium Coin
It is time for VERSION 5! New release is out containing new algorithm (Cn Pico) !
When new version srb?
CN Pico = turtle, so you can already mine it |
|
|
|
|
doktor83 (OP)
|
|
July 11, 2019, 12:45:23 PM |
|
V1.9.1- Added support for Navi10 (gfx1010) - Arto, conceal, normal, normalv7, marketcash, b2n, fast, hycon, hospital algos have lower power consumption on Vegas with auto settings - Hopefully fixed bug with invalid job id / same job id - If more than 5 'invalid share' messages received from pool within same connection, auto miner restart - Fixed cn-gpu hashrate (it was lower from v.1.8.8 -> my mistake) - CN/R program precompilation process is now only logged, not displayed on screen + Added support for gfx1010 card. Well at least i hope, because i don't own a rx 5700 card, so i couldn't test  It would be good if someone could test it and report back. + On Vega, intensity 0 (auto setting) now uses a little less power on next algorithms : Arto, conceal, normal, normalv7, marketcash, b2n, fast, hycon, hospital + I tried to fix the 'invalid job', 'invalid share' issue, unfortunately i couldn't reproduce it neither earlier neither now, that's why i say i tried .. Anyways if the problem still persists, i also added a 'protection' against this, if within the same pool connection more than 5 invalid share messages received from the pool, miner will auto restart. + I accidentally messed up CN/GPU hashrate from version 1.8.8, now it is fixed and hashing again at full speed
|
|
|
|
Vcxz
Newbie
Offline
Activity: 30
Merit: 0
|
|
July 11, 2019, 01:51:04 PM |
|
V1.9.1- Added support for Navi10 (gfx1010) - Arto, conceal, normal, normalv7, marketcash, b2n, fast, hycon, hospital algos have lower power consumption on Vegas with auto settings - Hopefully fixed bug with invalid job id / same job id - If more than 5 'invalid share' messages received from pool within same connection, auto miner restart - Fixed cn-gpu hashrate (it was lower from v.1.8.8 -> my mistake) - CN/R program precompilation process is now only logged, not displayed on screen + Added support for gfx1010 card. Well at least i hope, because i don't own a rx 5700 card, so i couldn't test It would be good if someone could test it and report back. + On Vega, intensity 0 (auto setting) now uses a little less power on next algorithms : Arto, conceal, normal, normalv7, marketcash, b2n, fast, hycon, hospital + I tried to fix the 'invalid job', 'invalid share' issue, unfortunately i couldn't reproduce it neither earlier neither now, that's why i say i tried .. Anyways if the problem still persists, i also added a 'protection' against this, if within the same pool connection more than 5 invalid share messages received from the pool, miner will auto restart. + I accidentally messed up CN/GPU hashrate from version 1.8.8, now it is fixed and hashing again at full speed tested on 5700xt Algo: normalv4 1 min avg: 231 H/s 5 min avg: 206 H/s Max Speed: 866 H/s |
|
|
|
|
sky2018miner
Newbie
Offline
Activity: 33
Merit: 0
|
|
July 11, 2019, 02:03:17 PM |
|
Hello
please pay attention
something went wrong
I bring a log
[2019-07-11 16:55:18] Startup monitor attached
[2019-07-11 16:55:18] Miner version: 1.9.1
[2019-07-11 16:55:18] Windows version: 10.0 build 17763
[2019-07-11 16:55:18] Video driver version: 26.20.11015.5009
[2019-07-11 16:55:18] Please run miner as administrator to enable tweaking
[2019-07-11 16:55:23] AMD Platform ID: 0
[2019-07-11 16:55:23] AMD platform FOUND
[2019-07-11 16:55:23] Found 7 AMD devices
[2019-07-11 16:55:23] CPU AES-NI: FALSE
[2019-07-11 16:55:23] PREPARE DATA: FALSE
[2019-07-11 16:55:23] GPU0: Radeon(TM) RX 460 Graphics [baffin] [2048 MB][CU: 14][I: 20.0][W: 8][T: 2][F: 8][BUS: 1]
[2019-07-11 16:55:23] GPU1: Radeon(TM) RX 460 Graphics [baffin] [2048 MB][CU: 14][I: 27.0][W: 8][T: 2][F: 8][BUS: 3]
[2019-07-11 16:55:23] GPU2: AMD Radeon R9 200 Series [tonga] [2048 MB][CU: 28][I: 28.0][W: 8][T: 2][F: 8][BUS: 4]
[2019-07-11 16:55:23] GPU3: Radeon RX 560 Series [baffin] [4096 MB][CU: 16][I: 27.0][W: 8][T: 2][F: 8][BUS: 8]
[2019-07-11 16:55:23] GPU4: AMD Radeon (TM) R7 370 Series [pitcairn] [2048 MB][CU: 16][I: 28.0][W: 8][T: 2][F: 8][BUS: 9]
[2019-07-11 16:55:23] GPU5: AMD Radeon R7 200 Series [pitcairn] [2048 MB][CU: 16][I: 28.0][W: 8][T: 2][F: 8][BUS: 10]
[2019-07-11 16:55:23] GPU6: AMD Radeon (TM) R7 370 Series [pitcairn] [2048 MB][CU: 16][I: 28.0][W: 8][T: 2][F: 8][BUS: 11]
[2019-07-11 16:55:23] ADL is enabled
[2019-07-11 16:55:23] Algorithm: Cryptonight Conceal
[2019-07-11 16:55:23] Algo switching: disabled
[2019-07-11 16:55:23] Coin forking: disabled
[2019-07-11 16:55:23] Gpu watchdog: enabled [gpu disable mode]
[2019-07-11 16:55:23] Startup monitor: enabled
[2019-07-11 16:55:23] Tweaking: disabled
[2019-07-11 16:55:23] Socket initialiasation done
[2019-07-11 16:55:23] Starting init of gpu threads
[2019-07-11 16:55:23] Created OCL context
[2019-07-11 16:55:23] Created OCL input buffer for DeviceID 0 (Thread 0)
[2019-07-11 16:55:23] load_binary: Couldn't load default binary for DeviceID 0 (Thread 0)
[2019-07-11 16:55:23] Loading [conceal] kernel for DEVICE BUS_ID[1]
[2019-07-11 16:55:23] ctx->Program for DeviceID 0 (Thread 0) loaded
[2019-07-11 16:55:23] Created OCL input buffer for DeviceID 0 (Thread 1)
[2019-07-11 16:55:23] load_binary: Couldn't load default binary for DeviceID 0 (Thread 1)
[2019-07-11 16:55:24] Loading [conceal] kernel for DEVICE BUS_ID[1]
[2019-07-11 16:55:24] ctx->Program for DeviceID 0 (Thread 1) loaded
[2019-07-11 16:55:24] Created OCL input buffer for DeviceID 1 (Thread 2)
[2019-07-11 16:55:24] load_binary: Couldn't load default binary for DeviceID 1 (Thread 2)
[2019-07-11 16:55:24] Loading [conceal] kernel for DEVICE BUS_ID[3]
[2019-07-11 16:55:24] ctx->Program for DeviceID 1 (Thread 2) loaded
[2019-07-11 16:55:24] Created OCL input buffer for DeviceID 1 (Thread 3)
[2019-07-11 16:55:24] load_binary: Couldn't load default binary for DeviceID 1 (Thread 3)
[2019-07-11 16:55:24] Loading [conceal] kernel for DEVICE BUS_ID[3]
[2019-07-11 16:55:24] ctx->Program for DeviceID 1 (Thread 3) loaded
[2019-07-11 16:55:25] Created OCL input buffer for DeviceID 2 (Thread 4)
[2019-07-11 16:55:25] load_binary: Couldn't load default binary for DeviceID 2 (Thread 4)
[2019-07-11 16:55:25] ctx->headers[0] created for DeviceID 2 (Thread 4)
[2019-07-11 16:55:25] Error CL_COMPILE_PROGRAM_FAILURE when calling clCompileProgram [ctx->Program] for DeviceID 2 (Thread 4)
[2019-07-11 16:55:25] Error while creating GPU threads.. Stopping miner process.
[2019-07-11 16:55:25] Socket cleanup done
[2019-07-11 16:55:25] Shutting down miner...
previous version works fine
|
|
|
|
|
|
doktor83 (OP)
|
|
July 11, 2019, 02:59:44 PM |
|
V1.9.1- Added support for Navi10 (gfx1010) - Arto, conceal, normal, normalv7, marketcash, b2n, fast, hycon, hospital algos have lower power consumption on Vegas with auto settings - Hopefully fixed bug with invalid job id / same job id - If more than 5 'invalid share' messages received from pool within same connection, auto miner restart - Fixed cn-gpu hashrate (it was lower from v.1.8.8 -> my mistake) - CN/R program precompilation process is now only logged, not displayed on screen + Added support for gfx1010 card. Well at least i hope, because i don't own a rx 5700 card, so i couldn't test It would be good if someone could test it and report back. + On Vega, intensity 0 (auto setting) now uses a little less power on next algorithms : Arto, conceal, normal, normalv7, marketcash, b2n, fast, hycon, hospital + I tried to fix the 'invalid job', 'invalid share' issue, unfortunately i couldn't reproduce it neither earlier neither now, that's why i say i tried .. Anyways if the problem still persists, i also added a 'protection' against this, if within the same pool connection more than 5 invalid share messages received from the pool, miner will auto restart. + I accidentally messed up CN/GPU hashrate from version 1.8.8, now it is fixed and hashing again at full speed tested on 5700xt Algo: normalv4 1 min avg: 231 H/s 5 min avg: 206 H/s Max Speed: 866 H/s Thanks for trying it out. You probably tried the auto setup, guess didnt play with manual config yet.. i hope more can be squeezed out from those cards and the right intensity/worksize/fragments. |
|
|
|
|
doktor83 (OP)
|
|
July 11, 2019, 04:20:40 PM
Last edit: July 11, 2019, 05:35:17 PM by doktor83 |
|
Hello
please pay attention
something went wrong
I bring a log
[2019-07-11 16:55:18] Startup monitor attached
[2019-07-11 16:55:18] Miner version: 1.9.1
[2019-07-11 16:55:18] Windows version: 10.0 build 17763
[2019-07-11 16:55:18] Video driver version: 26.20.11015.5009
[2019-07-11 16:55:18] Please run miner as administrator to enable tweaking
[2019-07-11 16:55:23] AMD Platform ID: 0
[2019-07-11 16:55:23] AMD platform FOUND
[2019-07-11 16:55:23] Found 7 AMD devices
[2019-07-11 16:55:23] CPU AES-NI: FALSE
[2019-07-11 16:55:23] PREPARE DATA: FALSE
[2019-07-11 16:55:23] GPU0: Radeon(TM) RX 460 Graphics [baffin] [2048 MB][CU: 14][I: 20.0][W: 8][T: 2][F: 8][BUS: 1]
[2019-07-11 16:55:23] GPU1: Radeon(TM) RX 460 Graphics [baffin] [2048 MB][CU: 14][I: 27.0][W: 8][T: 2][F: 8][BUS: 3]
[2019-07-11 16:55:23] GPU2: AMD Radeon R9 200 Series [tonga] [2048 MB][CU: 28][I: 28.0][W: 8][T: 2][F: 8][BUS: 4]
[2019-07-11 16:55:23] GPU3: Radeon RX 560 Series [baffin] [4096 MB][CU: 16][I: 27.0][W: 8][T: 2][F: 8][BUS: 8]
[2019-07-11 16:55:23] GPU4: AMD Radeon (TM) R7 370 Series [pitcairn] [2048 MB][CU: 16][I: 28.0][W: 8][T: 2][F: 8][BUS: 9]
[2019-07-11 16:55:23] GPU5: AMD Radeon R7 200 Series [pitcairn] [2048 MB][CU: 16][I: 28.0][W: 8][T: 2][F: 8][BUS: 10]
[2019-07-11 16:55:23] GPU6: AMD Radeon (TM) R7 370 Series [pitcairn] [2048 MB][CU: 16][I: 28.0][W: 8][T: 2][F: 8][BUS: 11]
[2019-07-11 16:55:23] ADL is enabled
[2019-07-11 16:55:23] Algorithm: Cryptonight Conceal
[2019-07-11 16:55:23] Algo switching: disabled
[2019-07-11 16:55:23] Coin forking: disabled
[2019-07-11 16:55:23] Gpu watchdog: enabled [gpu disable mode]
[2019-07-11 16:55:23] Startup monitor: enabled
[2019-07-11 16:55:23] Tweaking: disabled
[2019-07-11 16:55:23] Socket initialiasation done
[2019-07-11 16:55:23] Starting init of gpu threads
[2019-07-11 16:55:23] Created OCL context
[2019-07-11 16:55:23] Created OCL input buffer for DeviceID 0 (Thread 0)
[2019-07-11 16:55:23] load_binary: Couldn't load default binary for DeviceID 0 (Thread 0)
[2019-07-11 16:55:23] Loading [conceal] kernel for DEVICE BUS_ID[1]
[2019-07-11 16:55:23] ctx->Program for DeviceID 0 (Thread 0) loaded
[2019-07-11 16:55:23] Created OCL input buffer for DeviceID 0 (Thread 1)
[2019-07-11 16:55:23] load_binary: Couldn't load default binary for DeviceID 0 (Thread 1)
[2019-07-11 16:55:24] Loading [conceal] kernel for DEVICE BUS_ID[1]
[2019-07-11 16:55:24] ctx->Program for DeviceID 0 (Thread 1) loaded
[2019-07-11 16:55:24] Created OCL input buffer for DeviceID 1 (Thread 2)
[2019-07-11 16:55:24] load_binary: Couldn't load default binary for DeviceID 1 (Thread 2)
[2019-07-11 16:55:24] Loading [conceal] kernel for DEVICE BUS_ID[3]
[2019-07-11 16:55:24] ctx->Program for DeviceID 1 (Thread 2) loaded
[2019-07-11 16:55:24] Created OCL input buffer for DeviceID 1 (Thread 3)
[2019-07-11 16:55:24] load_binary: Couldn't load default binary for DeviceID 1 (Thread 3)
[2019-07-11 16:55:24] Loading [conceal] kernel for DEVICE BUS_ID[3]
[2019-07-11 16:55:24] ctx->Program for DeviceID 1 (Thread 3) loaded
[2019-07-11 16:55:25] Created OCL input buffer for DeviceID 2 (Thread 4)
[2019-07-11 16:55:25] load_binary: Couldn't load default binary for DeviceID 2 (Thread 4)
[2019-07-11 16:55:25] ctx->headers[0] created for DeviceID 2 (Thread 4)
[2019-07-11 16:55:25] Error CL_COMPILE_PROGRAM_FAILURE when calling clCompileProgram [ctx->Program] for DeviceID 2 (Thread 4)
[2019-07-11 16:55:25] Error while creating GPU threads.. Stopping miner process.
[2019-07-11 16:55:25] Socket cleanup done
[2019-07-11 16:55:25] Shutting down miner...
previous version works fine
should be fixed. try it, re - download 1.9.1 |
|
|
|
sky2018miner
Newbie
Offline
Activity: 33
Merit: 0
|
|
July 11, 2019, 06:14:34 PM |
|
everything works fine again
thank you very much
as always, fast response and excellent results
|
|
|
|
|
GodOfStars
Newbie
Offline
Activity: 49
Merit: 0
|
|
July 12, 2019, 09:51:21 AM |
|
Hi Doc, I find out that my Vegas 64 are all stable at memory tweak profile 8. How to apply it so it is already at 8 when restarting the miner, instead of manually pressing the + sign. Thank you
|
|
|
|
|
|
doktor83 (OP)
|
|
July 12, 2019, 10:35:34 AM |
|
Hi Doc, I find out that my Vegas 64 are all stable at memory tweak profile 8. How to apply it so it is already at 8 when restarting the miner, instead of manually pressing the + sign. Thank you
Try adding "tweak_profile" : 8 in config.txt, for example : {
"cryptonight_type" : "normalv4",
"intensity" : 0,
"double_threads" : true,
"off_temperature" : 80,
"tweak_profile" : 8
} |
|
|
|
GodOfStars
Newbie
Offline
Activity: 49
Merit: 0
|
|
July 12, 2019, 11:54:49 AM |
|
Hi Doc, I find out that my Vegas 64 are all stable at memory tweak profile 8. How to apply it so it is already at 8 when restarting the miner, instead of manually pressing the + sign. Thank you
Try adding "tweak_profile" : 8 in config.txt, for example : {
"cryptonight_type" : "normalv4",
"intensity" : 0,
"double_threads" : true,
"off_temperature" : 80,
"tweak_profile" : 8
}Thanks Doc, for your fast response, it did work like a charm. But I will have to ask one more question though. Maybe i was thinking to do a fine tuning and isolate the weaker cards and put them one profile 8 and the rest on 9 or 10. How to do that? And last thing after updating to the latest SRB miner 1.9.1 I found out that it restarts the miner after 5 bad shares. One of my Vega VII apparently inst from the silicone lottery. I have memory at 1075 and clock at 1700 to avoid too many bad shares. I still get one bad share from time to time but its not a big deal, because I still get about 99.5%, but my question is how to disable the new option of restarting the miner after 5 bad shares or maybe to increase it to 20, in order down time due to restarts. I think I have 3-9 bad shares per 24 hours from that GPU. Thank you so much! |
|
|
|
|
|
doktor83 (OP)
|
|
July 12, 2019, 02:12:15 PM |
|
Hi Doc, I find out that my Vegas 64 are all stable at memory tweak profile 8. How to apply it so it is already at 8 when restarting the miner, instead of manually pressing the + sign. Thank you
Try adding "tweak_profile" : 8 in config.txt, for example : {
"cryptonight_type" : "normalv4",
"intensity" : 0,
"double_threads" : true,
"off_temperature" : 80,
"tweak_profile" : 8
}Thanks Doc, for your fast response, it did work like a charm. But I will have to ask one more question though. Maybe i was thinking to do a fine tuning and isolate the weaker cards and put them one profile 8 and the rest on 9 or 10. How to do that? And last thing after updating to the latest SRB miner 1.9.1 I found out that it restarts the miner after 5 bad shares. One of my Vega VII apparently inst from the silicone lottery. I have memory at 1075 and clock at 1700 to avoid too many bad shares. I still get one bad share from time to time but its not a big deal, because I still get about 99.5%, but my question is how to disable the new option of restarting the miner after 5 bad shares or maybe to increase it to 20, in order down time due to restarts. I think I have 3-9 bad shares per 24 hours from that GPU. Thank you so much! For per card configuration use gpu_conf array, here is an example : {
"cryptonight_type" : "normalv4",
"intensity" : 0,
"double_threads" : true,
"gpu_conf" :
[
{
"id" : 0,
"intensity" : 112,
"worksize" : 16,
"threads" : 2,
"tweak_profile" : 8
},
{
"id" : 1,
"intensity" : 112,
"worksize" : 16,
"threads" : 2,
"tweak_profile" : 10
}
]
}You get the idea. Also on the first page or in the readme.txt you have more info. Regarding the restart on 5 bad shares, well yes, i don't know myself why i didn't make that one optional I will add a parameter that disables this in the next version in a few days. |
|
|
|
GodOfStars
Newbie
Offline
Activity: 49
Merit: 0
|
|
July 12, 2019, 02:56:45 PM |
|
Hi Doc, I find out that my Vegas 64 are all stable at memory tweak profile 8. How to apply it so it is already at 8 when restarting the miner, instead of manually pressing the + sign. Thank you
Try adding "tweak_profile" : 8 in config.txt, for example : {
"cryptonight_type" : "normalv4",
"intensity" : 0,
"double_threads" : true,
"off_temperature" : 80,
"tweak_profile" : 8
}Thanks Doc, for your fast response, it did work like a charm. But I will have to ask one more question though. Maybe i was thinking to do a fine tuning and isolate the weaker cards and put them one profile 8 and the rest on 9 or 10. How to do that? And last thing after updating to the latest SRB miner 1.9.1 I found out that it restarts the miner after 5 bad shares. One of my Vega VII apparently inst from the silicone lottery. I have memory at 1075 and clock at 1700 to avoid too many bad shares. I still get one bad share from time to time but its not a big deal, because I still get about 99.5%, but my question is how to disable the new option of restarting the miner after 5 bad shares or maybe to increase it to 20, in order down time due to restarts. I think I have 3-9 bad shares per 24 hours from that GPU. Thank you so much! For per card configuration use gpu_conf array, here is an example : {
"cryptonight_type" : "normalv4",
"intensity" : 0,
"double_threads" : true,
"gpu_conf" :
[
{
"id" : 0,
"intensity" : 112,
"worksize" : 16,
"threads" : 2,
"tweak_profile" : 8
},
{
"id" : 1,
"intensity" : 112,
"worksize" : 16,
"threads" : 2,
"tweak_profile" : 10
}
]
}You get the idea. Also on the first page or in the readme.txt you have more info. Regarding the restart on 5 bad shares, well yes, i don't know myself why i didn't make that one optional I will add a parameter that disables this in the next version in a few days. God Bless, you are amazing! |
|
|
|
|
KhorneFlake
Newbie
Offline
Activity: 27
Merit: 0
|
|
July 13, 2019, 09:47:57 AM |
|
Downloaded the latest 1.9.1 version and still the main GPU starts at 1000h/s and drops over time from there. Sniff, shame I cannot use the 1.8.0 anymore.
|
|
|
|
|
|
