Topic: SRBMiner Cryptonight AMD GPU Miner V1.9.3 - native algo switching - page 286. (Read 237247 times)
May 03, 2018, 09:24:10 AM
So, what's new in 1.5.1?
May 03, 2018, 08:48:55 AM
So i had to make my own script to restart the miner because it was still hanging with 10 vegas, i woke up and machine hanged. sometimes only miner hangs. I made a bat file that runs every 4 hours to kill the process, and re run it. Seems to be working fine up to now, 10 hours mining.
Script for those who want it.
@echo off
:: clears the screen
cls
:: Enter your process name below
taskkill /im SRBMiner-CN.exe /F
:: clears the screen again
cls
:: echos the following
echo The requested program and service has been restarted. Press any key to exit.
You can even do other crazy stuff in here...
Script for those who want it.
@echo off
:: clears the screen
cls
:: Enter your process name below
taskkill /im SRBMiner-CN.exe /F
:: clears the screen again
cls
:: echos the following
echo The requested program and service has been restarted. Press any key to exit.
You can even do other crazy stuff in here...
May 03, 2018, 08:10:13 AM
Hi all,
does somebody has a good memory strap for an RX 480 elpida?
I get 720 H/s only on it (cryptonight heavy) vs 1060 H/s for my rx 580 hynix...
(alternative question: is it an issue to flash the BIOS many times ?)
does somebody has a good memory strap for an RX 480 elpida?
I get 720 H/s only on it (cryptonight heavy) vs 1060 H/s for my rx 580 hynix...
(alternative question: is it an issue to flash the BIOS many times ?)
May 03, 2018, 05:00:24 AM
Hi guys.
Mind helping out maximising my hashrates?
Think I could burst to 1k?
I'll share my config.
Running 18.3.4 latest Driver.
My config file. The rest I did not touch. Should I mess with the kernels?
And what parameters are safe to play around the intensity with for RX580 8GB ?
Appreciate the help here
Mind helping out maximising my hashrates?
Think I could burst to 1k?
I'll share my config.
Running 18.3.4 latest Driver.
Code:
[font=Verdana][color=green][/color][/font][2018-05-03 07:12:44] GPU0: 981.0 H/S [T: 86c, RPM: 2988, CC: 1411 MHz, MC: 2000 MHz]
[2018-05-03 07:12:44] GPU1: 896.0 H/S [T: 80c, RPM: 2382, CC: 1411 MHz, MC: 2000 MHz]
[2018-05-03 07:12:44] GPU2: 897.0 H/S [T: 79c, RPM: 1846, CC: 1411 MHz, MC: 2000 MHz]
[2018-05-03 07:12:44] GPU3: 666.0 H/S [T: 78c, RPM: 1933, CC: 1411 MHz, MC: 2000 MHz]
[2018-05-03 07:12:44] GPU4: 880.0 H/S [T: 82c, RPM: 3086, CC: 1411 MHz, MC: 2000 MHz]
[2018-05-03 07:12:44] GPU5: 917.0 H/S [T: 52c, RPM: 1258, CC: 1360 MHz, MC: 2000 MHz]
[2018-05-03 07:12:44] GPU6: 818.0 H/S [T: 81c, RPM: 1555, CC: 1411 MHz, MC: 2000 MHz]
[2018-05-03 07:12:44] GPU7: 986.0 H/S [T: 86c, RPM: 2925, CC: 1411 MHz, MC: 2000 MHz]
[2018-05-03 07:12:44] GPU8: 820.0 H/S [T: 78c, RPM: 1939, CC: 1411 MHz, MC: 2000 MHz]
[2018-05-03 07:12:44] GPU9: 841.0 H/S [T: 63c, RPM: 1352, CC: 1360 MHz, MC: 2000 MHz]
[2018-05-03 07:12:44] GPU10: 849.0 H/S [T: 71c, RPM: 2103, CC: 1360 MHz, MC: 2000 MHz]
[2018-05-03 07:12:44] GPU11: 929.0 H/S [T: 65c, RPM: 1883, CC: 1360 MHz, MC: 2000 MHz]
[2018-05-03 07:12:44] GPU12: 731.0 H/S [T: 64c, RPM: 1374, CC: 1360 MHz, MC: 2000 MHz]
[2018-05-03 07:12:44] Total: 11211.0 H/S
[2018-05-03 07:12:44] GPU1: 896.0 H/S [T: 80c, RPM: 2382, CC: 1411 MHz, MC: 2000 MHz]
[2018-05-03 07:12:44] GPU2: 897.0 H/S [T: 79c, RPM: 1846, CC: 1411 MHz, MC: 2000 MHz]
[2018-05-03 07:12:44] GPU3: 666.0 H/S [T: 78c, RPM: 1933, CC: 1411 MHz, MC: 2000 MHz]
[2018-05-03 07:12:44] GPU4: 880.0 H/S [T: 82c, RPM: 3086, CC: 1411 MHz, MC: 2000 MHz]
[2018-05-03 07:12:44] GPU5: 917.0 H/S [T: 52c, RPM: 1258, CC: 1360 MHz, MC: 2000 MHz]
[2018-05-03 07:12:44] GPU6: 818.0 H/S [T: 81c, RPM: 1555, CC: 1411 MHz, MC: 2000 MHz]
[2018-05-03 07:12:44] GPU7: 986.0 H/S [T: 86c, RPM: 2925, CC: 1411 MHz, MC: 2000 MHz]
[2018-05-03 07:12:44] GPU8: 820.0 H/S [T: 78c, RPM: 1939, CC: 1411 MHz, MC: 2000 MHz]
[2018-05-03 07:12:44] GPU9: 841.0 H/S [T: 63c, RPM: 1352, CC: 1360 MHz, MC: 2000 MHz]
[2018-05-03 07:12:44] GPU10: 849.0 H/S [T: 71c, RPM: 2103, CC: 1360 MHz, MC: 2000 MHz]
[2018-05-03 07:12:44] GPU11: 929.0 H/S [T: 65c, RPM: 1883, CC: 1360 MHz, MC: 2000 MHz]
[2018-05-03 07:12:44] GPU12: 731.0 H/S [T: 64c, RPM: 1374, CC: 1360 MHz, MC: 2000 MHz]
[2018-05-03 07:12:44] Total: 11211.0 H/S
My config file. The rest I did not touch. Should I mess with the kernels?
Code:
[color=brown]"cryptonight_type" : "heavy", "double_threads" : true,
[/color]
[/color]
And what parameters are safe to play around the intensity with for RX580 8GB ?
Appreciate the help here
RX580 8GB best for me intensity 52 worksize 8, you need to flash your bios with doktor83 strap if your chipset is hynix. set your core clock 1200-1250 and memory clock 2100-2150 depend on how good your GPU.
May 03, 2018, 03:28:10 AM
Is it possible to automatically switch between pools after a specific time interval? So, for instance each 30 minutes it switches to the next pool?
Why would you do that?
Most of pools are PPLNS , you would waste hashing power
May 03, 2018, 02:24:12 AM
Is it possible to automatically switch between pools after a specific time interval? So, for instance each 30 minutes it switches to the next pool?
Why would you do that?
Most of pools are PPLNS , you would waste hashing power
May 03, 2018, 01:58:16 AM
Hello, is there any plan add overclock settings in SRBminer. I dont wanna use Afterburner etc.
May 03, 2018, 01:32:56 AM
Is it possible to automatically switch between pools after a specific time interval? So, for instance each 30 minutes it switches to the next pool?
May 02, 2018, 07:16:26 PM
Hi guys.
Mind helping out maximising my hashrates?
Think I could burst to 1k?
I'll share my config.
Running 18.3.4 latest Driver.
My config file. The rest I did not touch. Should I mess with the kernels?
And what parameters are safe to play around the intensity with for RX580 8GB ?
Appreciate the help here
Mind helping out maximising my hashrates?
Think I could burst to 1k?
I'll share my config.
Running 18.3.4 latest Driver.
Code:
[font=Verdana][color=green][/color][/font][2018-05-03 07:12:44] GPU0: 981.0 H/S [T: 86c, RPM: 2988, CC: 1411 MHz, MC: 2000 MHz]
[2018-05-03 07:12:44] GPU1: 896.0 H/S [T: 80c, RPM: 2382, CC: 1411 MHz, MC: 2000 MHz]
[2018-05-03 07:12:44] GPU2: 897.0 H/S [T: 79c, RPM: 1846, CC: 1411 MHz, MC: 2000 MHz]
[2018-05-03 07:12:44] GPU3: 666.0 H/S [T: 78c, RPM: 1933, CC: 1411 MHz, MC: 2000 MHz]
[2018-05-03 07:12:44] GPU4: 880.0 H/S [T: 82c, RPM: 3086, CC: 1411 MHz, MC: 2000 MHz]
[2018-05-03 07:12:44] GPU5: 917.0 H/S [T: 52c, RPM: 1258, CC: 1360 MHz, MC: 2000 MHz]
[2018-05-03 07:12:44] GPU6: 818.0 H/S [T: 81c, RPM: 1555, CC: 1411 MHz, MC: 2000 MHz]
[2018-05-03 07:12:44] GPU7: 986.0 H/S [T: 86c, RPM: 2925, CC: 1411 MHz, MC: 2000 MHz]
[2018-05-03 07:12:44] GPU8: 820.0 H/S [T: 78c, RPM: 1939, CC: 1411 MHz, MC: 2000 MHz]
[2018-05-03 07:12:44] GPU9: 841.0 H/S [T: 63c, RPM: 1352, CC: 1360 MHz, MC: 2000 MHz]
[2018-05-03 07:12:44] GPU10: 849.0 H/S [T: 71c, RPM: 2103, CC: 1360 MHz, MC: 2000 MHz]
[2018-05-03 07:12:44] GPU11: 929.0 H/S [T: 65c, RPM: 1883, CC: 1360 MHz, MC: 2000 MHz]
[2018-05-03 07:12:44] GPU12: 731.0 H/S [T: 64c, RPM: 1374, CC: 1360 MHz, MC: 2000 MHz]
[2018-05-03 07:12:44] Total: 11211.0 H/S
[2018-05-03 07:12:44] GPU1: 896.0 H/S [T: 80c, RPM: 2382, CC: 1411 MHz, MC: 2000 MHz]
[2018-05-03 07:12:44] GPU2: 897.0 H/S [T: 79c, RPM: 1846, CC: 1411 MHz, MC: 2000 MHz]
[2018-05-03 07:12:44] GPU3: 666.0 H/S [T: 78c, RPM: 1933, CC: 1411 MHz, MC: 2000 MHz]
[2018-05-03 07:12:44] GPU4: 880.0 H/S [T: 82c, RPM: 3086, CC: 1411 MHz, MC: 2000 MHz]
[2018-05-03 07:12:44] GPU5: 917.0 H/S [T: 52c, RPM: 1258, CC: 1360 MHz, MC: 2000 MHz]
[2018-05-03 07:12:44] GPU6: 818.0 H/S [T: 81c, RPM: 1555, CC: 1411 MHz, MC: 2000 MHz]
[2018-05-03 07:12:44] GPU7: 986.0 H/S [T: 86c, RPM: 2925, CC: 1411 MHz, MC: 2000 MHz]
[2018-05-03 07:12:44] GPU8: 820.0 H/S [T: 78c, RPM: 1939, CC: 1411 MHz, MC: 2000 MHz]
[2018-05-03 07:12:44] GPU9: 841.0 H/S [T: 63c, RPM: 1352, CC: 1360 MHz, MC: 2000 MHz]
[2018-05-03 07:12:44] GPU10: 849.0 H/S [T: 71c, RPM: 2103, CC: 1360 MHz, MC: 2000 MHz]
[2018-05-03 07:12:44] GPU11: 929.0 H/S [T: 65c, RPM: 1883, CC: 1360 MHz, MC: 2000 MHz]
[2018-05-03 07:12:44] GPU12: 731.0 H/S [T: 64c, RPM: 1374, CC: 1360 MHz, MC: 2000 MHz]
[2018-05-03 07:12:44] Total: 11211.0 H/S
My config file. The rest I did not touch. Should I mess with the kernels?
Code:
[color=brown]"cryptonight_type" : "heavy", "double_threads" : true,
[/color]
[/color]
And what parameters are safe to play around the intensity with for RX580 8GB ?
Appreciate the help here
May 02, 2018, 04:54:07 PM
I am using AMD software version 18.3.4, you dont need to restart the vegas with this software version after each restart, it will auto detect. There is no special setting, I just had to reduce the OC on all cards, so running 900 on memory and 1300 on core. 950mV on core and 900mV on mem. 18kh/s, using SRBminer, tried cast too, same results. However, I have disabled the ADL reporting and I am using openhardwaremonitor to check temps and fan speed and I have also disabled the gpuwatchdog. That's it. Screens:
Can you share your full hardware specs? PSU, Mobo, memory, SO, etc...
May 02, 2018, 03:15:31 PM
INFO - TEST VEGA 56 PowerColor
3*Vega56 flashed to 64
Crimson-ReLive-Beta-Blockchain driver
SRBminer 1.4.9
GPU - 1442/1437/1407mhz 905-907mv
MEM - 1095/1100mhz 900mv
Cryptonight V7(monero)
"intensity" : 120 HR=6000 - 560W
https://image.prntscr.com/image/rK5kLVCPQQS89xDEIYhHgQ.jpg
Cryptonight lite(aeon)
"intensity" : 235 HR=12900 - 570W
https://image.prntscr.com/image/23TkvCkvRMCvC9p2YhxiCQ.jpg
Cryptonight liteV7(trtl)
"intensity" : 235 HR=12900 - 570W
https://image.prntscr.com/image/Xb6WiZ1EQaS5UMmWq3KHuw.jpg
Cryptonight ultraheavy-lightv3(ipbc)
"intensity" : 239 HR=11100 - 550W
https://image.prntscr.com/image/PeiajoLsTJO3Zwc1ZX8f8A.jpg
Cryptonight heavy(sumo)
"intensity" : 56 HR=4550 - 530W
https://image.prntscr.com/image/2xW89wB8SxaZeSWX1n6zjQ.jpg
Cryptonight artocache(arto)
"intensity" : 118 HR=5400 - 550W
https://image.prntscr.com/image/AopDRnW8R0m9EDnqyB8-aw.jpg
3*Vega56 flashed to 64
Crimson-ReLive-Beta-Blockchain driver
SRBminer 1.4.9
GPU - 1442/1437/1407mhz 905-907mv
MEM - 1095/1100mhz 900mv
Cryptonight V7(monero)
"intensity" : 120 HR=6000 - 560W
https://image.prntscr.com/image/rK5kLVCPQQS89xDEIYhHgQ.jpg
Cryptonight lite(aeon)
"intensity" : 235 HR=12900 - 570W
https://image.prntscr.com/image/23TkvCkvRMCvC9p2YhxiCQ.jpg
Cryptonight liteV7(trtl)
"intensity" : 235 HR=12900 - 570W
https://image.prntscr.com/image/Xb6WiZ1EQaS5UMmWq3KHuw.jpg
Cryptonight ultraheavy-lightv3(ipbc)
"intensity" : 239 HR=11100 - 550W
https://image.prntscr.com/image/PeiajoLsTJO3Zwc1ZX8f8A.jpg
Cryptonight heavy(sumo)
"intensity" : 56 HR=4550 - 530W
https://image.prntscr.com/image/2xW89wB8SxaZeSWX1n6zjQ.jpg
Cryptonight artocache(arto)
"intensity" : 118 HR=5400 - 550W
https://image.prntscr.com/image/AopDRnW8R0m9EDnqyB8-aw.jpg
May 02, 2018, 03:12:36 PM
1250W at the wall, 6x Vega56@64, Onda D1800
That is too much. my 3*vega56 flashed to 64 = 530-570W at the wall .
v7= 6000hr 555-560W
ok. My rig without minig spend 105W- 555W with mining-
3*vega spend 450w = 150w per card ...
May 02, 2018, 01:45:01 PM
@dok
do you know of any reason the miner would just hang without any results being sent to pool. Basically the log says new job received and then the console keeps displaying full hashrate but none of the hashes but none are submitted. This has happened with v7 pools couple of times now for me. So from 04:19 and later the mining stopped but hashrates still get displayed out on console with no GPU hang until I shutdown the miner manually at 08:43. This was on support.xmr pool. Has happened with stellite pool too.
do you know of any reason the miner would just hang without any results being sent to pool. Basically the log says new job received and then the console keeps displaying full hashrate but none of the hashes but none are submitted. This has happened with v7 pools couple of times now for me. So from 04:19 and later the mining stopped but hashrates still get displayed out on console with no GPU hang until I shutdown the miner manually at 08:43. This was on support.xmr pool. Has happened with stellite pool too.
Code:
[2018-05-02 04:19:52] pool_have_job: Switching user to new job
[2018-05-02 04:19:52] pool_have_job: Pool sent a new job (ID: Xit8I/aR3mpvT5HBbrehA8O3I1uC)
[2018-05-02 08:42:47] stats: Mining time: 0 days, 10 hours, 19 minutes, 49 seconds
[2018-05-02 08:42:47] stats: Accepted/Total shares: 734/734
[2018-05-02 08:42:52] Stopping miner process
[2018-05-02 08:43:02] AMD Platform ID: 2
Which version ? I worked on this kind of issue in 1.4.9, is the version you are using before 1.4.9 ?
I think it's 1.4.5. I'll update the miner and monitor.
May 02, 2018, 12:11:41 PM
I give some benchmark:
Only cryptonight heavy,blockchain driver, 1300core/2100mem, uber mix 3,1 (srb miner is much bether then cast or else):
rx470 4gb hynix 800 h/r,
rx470 4gb samsung 790 h/r,
rx580 4gb Powercolor samsung/hynix 817 h/r
only problem is primary card (attached dong on) with up to 4% low h/r (ON CAST AND CRYPTONIGHT HEAVY PRIMARI CARD IS 0 H/R)
https://imgur.com/a/GYwl8uy
Only cryptonight heavy,blockchain driver, 1300core/2100mem, uber mix 3,1 (srb miner is much bether then cast or else):
rx470 4gb hynix 800 h/r,
rx470 4gb samsung 790 h/r,
rx580 4gb Powercolor samsung/hynix 817 h/r
only problem is primary card (attached dong on) with up to 4% low h/r (ON CAST AND CRYPTONIGHT HEAVY PRIMARI CARD IS 0 H/R)
https://imgur.com/a/GYwl8uy
WTF?
let me see if I understood, you have made UberMix-MOD for samsung memory to a card with Hynix memory?
How can this be possible?
May 02, 2018, 10:32:00 AM
How to get 370-400 H/s for RX460 2G on cryptonight heavy ? With Srb 1.1.4 i can mine sumo on fairpool with hash 460 H/s per card (not work on another pool, shares rejected), but when use a newest SRB, only get 320 H/s per card
May 02, 2018, 09:26:22 AM
@dok
do you know of any reason the miner would just hang without any results being sent to pool. Basically the log says new job received and then the console keeps displaying full hashrate but none of the hashes but none are submitted. This has happened with v7 pools couple of times now for me. So from 04:19 and later the mining stopped but hashrates still get displayed out on console with no GPU hang until I shutdown the miner manually at 08:43. This was on support.xmr pool. Has happened with stellite pool too.
do you know of any reason the miner would just hang without any results being sent to pool. Basically the log says new job received and then the console keeps displaying full hashrate but none of the hashes but none are submitted. This has happened with v7 pools couple of times now for me. So from 04:19 and later the mining stopped but hashrates still get displayed out on console with no GPU hang until I shutdown the miner manually at 08:43. This was on support.xmr pool. Has happened with stellite pool too.
Code:
[2018-05-02 04:19:52] pool_have_job: Switching user to new job
[2018-05-02 04:19:52] pool_have_job: Pool sent a new job (ID: Xit8I/aR3mpvT5HBbrehA8O3I1uC)
[2018-05-02 08:42:47] stats: Mining time: 0 days, 10 hours, 19 minutes, 49 seconds
[2018-05-02 08:42:47] stats: Accepted/Total shares: 734/734
[2018-05-02 08:42:52] Stopping miner process
[2018-05-02 08:43:02] AMD Platform ID: 2
Which version ? I worked on this kind of issue in 1.4.9, is the version you are using before 1.4.9 ?
May 02, 2018, 09:22:01 AM
@dok
do you know of any reason the miner would just hang without any results being sent to pool. Basically the log says new job received and then the console keeps displaying full hashrate but none of the hashes but none are submitted. This has happened with v7 pools couple of times now for me. So from 04:19 and later the mining stopped but hashrates still get displayed out on console with no GPU hang until I shutdown the miner manually at 08:43. This was on support.xmr pool. Has happened with stellite pool too.
do you know of any reason the miner would just hang without any results being sent to pool. Basically the log says new job received and then the console keeps displaying full hashrate but none of the hashes but none are submitted. This has happened with v7 pools couple of times now for me. So from 04:19 and later the mining stopped but hashrates still get displayed out on console with no GPU hang until I shutdown the miner manually at 08:43. This was on support.xmr pool. Has happened with stellite pool too.
Code:
[2018-05-02 04:19:52] pool_have_job: Switching user to new job
[2018-05-02 04:19:52] pool_have_job: Pool sent a new job (ID: Xit8I/aR3mpvT5HBbrehA8O3I1uC)
[2018-05-02 08:42:47] stats: Mining time: 0 days, 10 hours, 19 minutes, 49 seconds
[2018-05-02 08:42:47] stats: Accepted/Total shares: 734/734
[2018-05-02 08:42:52] Stopping miner process
[2018-05-02 08:43:02] AMD Platform ID: 2
May 02, 2018, 09:00:20 AM
Driver Amd Adrenalin 18.3.1
Intel integrated GPU Hd530 on Cpu
8xAmd Rx550
FIX IT
"platform_index" : 1, in config.txt change Platform !!
(in readmy.txt not comment this parameter )
Now new problem))
{ "id" : 0, "intensity" : 21, "worksize" : 8, "threads" : 2},
Intensity not change ! ( auto intensity =22
id ?
Intel integrated GPU Hd530 on Cpu
8xAmd Rx550
FIX IT
"platform_index" : 1, in config.txt change Platform !!
(in readmy.txt not comment this parameter )
Now new problem))
{ "id" : 0, "intensity" : 21, "worksize" : 8, "threads" : 2},
Intensity not change ! ( auto intensity =22
id ?
There is no platform_index parameter in SRBMiner. So i don't know what are you doing and on which miner
"platform_index" : 1,
"intensity" : 0,
"double_threads" : true,
"target_temperature" : 75,
this config WORK
"cryptonight_type" : "normalv7",
"intensity" : 0,
"double_threads" : true,
"target_temperature" : 75,
This not WORK !
Try it yourself
I don't have to, im developing the damn thing
Are you using the latest v1.5.0 ? Did you download it from the link on first page or some other site ?
Also make sure you uncomment the gpu_conf settings so :
Like this:
"gpu_conf" :
[
{ "id" : 0, "intensity" : 0, "worksize" : 8, "threads" : 2, "target_temperature" : 55}
]
Not this:
/*"gpu_conf" :
[
{ "id" : 0, "intensity" : 0, "worksize" : 8, "threads" : 2, "target_temperature" : 55}
]*/
/* Im sorry, my mistake!
Re install AMD driver and all OK ))
May 02, 2018, 06:16:34 AM
Driver Amd Adrenalin 18.3.1
Intel integrated GPU Hd530 on Cpu
8xAmd Rx550
FIX IT
"platform_index" : 1, in config.txt change Platform !!
(in readmy.txt not comment this parameter )
Now new problem))
{ "id" : 0, "intensity" : 21, "worksize" : 8, "threads" : 2},
Intensity not change ! ( auto intensity =22
id ?
Intel integrated GPU Hd530 on Cpu
8xAmd Rx550
FIX IT
"platform_index" : 1, in config.txt change Platform !!
(in readmy.txt not comment this parameter )
Now new problem))
{ "id" : 0, "intensity" : 21, "worksize" : 8, "threads" : 2},
Intensity not change ! ( auto intensity =22
id ?
There is no platform_index parameter in SRBMiner. So i don't know what are you doing and on which miner
"platform_index" : 1,
"intensity" : 0,
"double_threads" : true,
"target_temperature" : 75,
this config WORK
"cryptonight_type" : "normalv7",
"intensity" : 0,
"double_threads" : true,
"target_temperature" : 75,
This not WORK !
Try it yourself
I don't have to, im developing the damn thing
Are you using the latest v1.5.0 ? Did you download it from the link on first page or some other site ?
Also make sure you uncomment the gpu_conf settings so :
Like this:
"gpu_conf" :
[
{ "id" : 0, "intensity" : 0, "worksize" : 8, "threads" : 2, "target_temperature" : 55}
]
Not this:
/*"gpu_conf" :
[
{ "id" : 0, "intensity" : 0, "worksize" : 8, "threads" : 2, "target_temperature" : 55}
]*/
May 02, 2018, 06:13:36 AM
Doc,
Ive just tested the 1.5.0 with 6x Vega 64. Same good hash. I was still using 1.4.1 cuz it was working fine.
Ive tested the disable/enable feature.
After i press 2, took more than a min to disable the card. I have started to wait for the card come back and nothing. lol after 5 min ive decided to press 2 again and voila.
It may be good to add a message "card disable" 3 seconds after the event to be sure.
About JJ script, the script became more conservator and it added a separated disable and enable process with tempo to each card. ive always used the first version doing to all 6 at same time. It never hanged to me IF 5 seconds interval is respected. I mean, after disable all cards, if i hit a key to start the enable process in 3 seconds, the rig will BSOD. This is to all cards of course.
About the "restart_devices_on_startup" : option,
Can i place this anywhere in the config file?
Ive just tested the 1.5.0 with 6x Vega 64. Same good hash. I was still using 1.4.1 cuz it was working fine.
Ive tested the disable/enable feature.
After i press 2, took more than a min to disable the card. I have started to wait for the card come back and nothing. lol after 5 min ive decided to press 2 again and voila.
It may be good to add a message "card disable" 3 seconds after the event to be sure.
About JJ script, the script became more conservator and it added a separated disable and enable process with tempo to each card. ive always used the first version doing to all 6 at same time. It never hanged to me IF 5 seconds interval is respected. I mean, after disable all cards, if i hit a key to start the enable process in 3 seconds, the rig will BSOD. This is to all cards of course.
About the "restart_devices_on_startup" : option,
Can i place this anywhere in the config file?
Added possibility to disable/enable GPU's while mining. To maximize efficiency, when a device is disabled it won't get disabled right at that moment, it will first finish the round it is working on, and then it will stop working.
This is good for you because if some shares are found, they will be sent to the pool, and only after that the device will get disabled. This can sometimes take even 15-30 sec.
For GPU id's from 0-9 just press the corresponding key, for 10, 11, 12 ..etc use SHIFT+NUMBER, so if you want to disable GPU13, press SHIFT+3 on the keyboard.
This is for pausing specifig GPU in the mining process, not for driver restarting with devcon
You misunderstood this option.
And yes, you put that option in the config.txt : "restart_devices_on_startup" : true.
This disables/enables every AMD gpu in the system. Altough i set a 2 sec timeout between those operations, but i will increase it to 5 sec if you say that much is needed.
Jump to: