SRBMiner Cryptonight AMD GPU Miner V1.9.3 - native algo switching - page 10.

cas333

newbie

Activity: 52

Merit: 0

One of the most stable versions. Thanks Dok! Wink

Turkish88

full member

Activity: 714

Merit: 104

Quote from: Topcd on July 15, 2019, 09:59:19 AM

Quote from: doktor83 on July 15, 2019, 07:23:51 AM

Quote from: netmebtc on July 14, 2019, 07:56:37 PM

@doktor83, Hello, When will SRBminer support turtle's new algo "chukwa" and loki's new algo "RandmXL"?

I haven't decided yet what to do with the randomx algo family - it will suck on AMD gpus. Chukwa isn't in my plans atm.

RandomX is the good news for CPU miners and bad news for GPU miners, specially for RX Vega Owners like me as i've heard that the hash rate will drop off around 50% for Rx Vega on this new algorithm, but they say they are doing some optimizations to make it more acceptable.
Let's wait and see what happens! Undecided

But its better then switching to asic friendly algo, because on this scenario RX Vega hashrates drops more.
Lets hope to the succes of randomX

sky2018miner

newbie

Activity: 33

Merit: 0

Hello
I can not stop mining Rio
on Cryptonight Gpu
other algorithms work
I bring a log
[2019-07-16 23:26:22] Startup monitor attached
[2019-07-16 23:26:22] Miner version: 1.9.2
[2019-07-16 23:26:22] Windows version: 10.0 build 17763
[2019-07-16 23:26:22] Video driver version: 24.20.11021.1000
[2019-07-16 23:26:22] Please run miner as administrator to enable tweaking
[2019-07-16 23:26:32] AMD Platform ID: 0
[2019-07-16 23:26:32] AMD platform FOUND
[2019-07-16 23:26:32] Found 7 AMD devices
[2019-07-16 23:26:32] CPU AES-NI: FALSE
[2019-07-16 23:26:32] PREPARE DATA: FALSE
[2019-07-16 23:26:32] GPU0: AMD Radeon (TM) R7 370 Series [baffin] [2048 MB][CU: 14][I: 13.0][W: 8][T: 2][F: 0][BUS: 1]
[2019-07-16 23:26:32] GPU1: AMD Radeon (TM) R7 370 Series [baffin] [2048 MB][CU: 14][I: 13.6][W: 8][T: 2][F: 0][BUS: 3]
[2019-07-16 23:26:32] GPU2: AMD Radeon (TM) R7 370 Series [tonga] [2048 MB][CU: 28][I: 27.0][W: 8][T: 2][F: 4][BUS: 4]
[2019-07-16 23:26:32] GPU3: AMD Radeon (TM) R7 370 Series [baffin] [4096 MB][CU: 16][I: 15.5][W: 8][T: 2][F: 0][BUS: 8]
[2019-07-16 23:26:32] GPU4: AMD Radeon (TM) R7 370 Series [pitcairn] [2048 MB][CU: 16][I: 16.0][W: 8][T: 2][F: 0][BUS: 9]
[2019-07-16 23:26:32] GPU5: AMD Radeon (TM) R7 370 Series [pitcairn] [2048 MB][CU: 16][I: 16.0][W: 8][T: 2][F: 0][BUS: 10]
[2019-07-16 23:26:32] GPU6: AMD Radeon (TM) R7 370 Series [pitcairn] [2048 MB][CU: 16][I: 16.0][W: 8][T: 2][F: 0][BUS: 11]
[2019-07-16 23:26:32] ADL is enabled
[2019-07-16 23:26:32] Algorithm: Cryptonight Gpu
[2019-07-16 23:26:32] Algo switching: disabled
[2019-07-16 23:26:32] Coin forking: disabled
[2019-07-16 23:26:32] Gpu watchdog: enabled [normal mode]
[2019-07-16 23:26:32] Startup monitor: enabled
[2019-07-16 23:26:32] Tweaking: disabled
[2019-07-16 23:26:32] Socket initialiasation done
[2019-07-16 23:26:32] Starting init of gpu threads
[2019-07-16 23:26:32] Created OCL context
[2019-07-16 23:26:33] Created OCL input buffer for DeviceID 0 (Thread 0)
[2019-07-16 23:26:33] load_binary: Couldn't load default binary for DeviceID 0 (Thread 0)
[2019-07-16 23:26:33] ctx->headers[0] created for DeviceID 0 (Thread 0)
[2019-07-16 23:26:33] ctx->Program created for DeviceID 0 (Thread 0)
[2019-07-16 23:26:33] Compiling [gpu] kernel for DEVICE BUS_ID[1]
[2019-07-16 23:26:35] Binary kernel for DeviceID 0 (Thread 0) saved to disk
[2019-07-16 23:26:35] Created OCL input buffer for DeviceID 0 (Thread 1)
[2019-07-16 23:26:35] load_binary: Couldn't load default binary for DeviceID 0 (Thread 1)
[2019-07-16 23:26:35] Loading [gpu] kernel for DEVICE BUS_ID[1]
[2019-07-16 23:26:35] ctx->Program for DeviceID 0 (Thread 1) loaded
[2019-07-16 23:26:36] Created OCL input buffer for DeviceID 1 (Thread 2)
[2019-07-16 23:26:36] load_binary: Couldn't load default binary for DeviceID 1 (Thread 2)
[2019-07-16 23:26:36] Loading [gpu] kernel for DEVICE BUS_ID[3]
[2019-07-16 23:26:36] ctx->Program for DeviceID 1 (Thread 2) loaded
[2019-07-16 23:26:36] Created OCL input buffer for DeviceID 1 (Thread 3)
[2019-07-16 23:26:36] load_binary: Couldn't load default binary for DeviceID 1 (Thread 3)
[2019-07-16 23:26:36] Loading [gpu] kernel for DEVICE BUS_ID[3]
[2019-07-16 23:26:36] ctx->Program for DeviceID 1 (Thread 3) loaded
[2019-07-16 23:26:36] Created OCL input buffer for DeviceID 2 (Thread 4)
[2019-07-16 23:26:36] load_binary: Couldn't load default binary for DeviceID 2 (Thread 4)
[2019-07-16 23:26:36] ctx->headers[0] created for DeviceID 2 (Thread 4)
[2019-07-16 23:26:36] Error CL_COMPILE_PROGRAM_FAILURE when calling clCompileProgram [ctx->Program] for DeviceID 2 (Thread 4)
[2019-07-16 23:26:36] Error while creating GPU threads.. Stopping miner process.
[2019-07-16 23:26:36] Socket cleanup done
[2019-07-16 23:26:36] Shutting down miner...

please fix it

GodOfStars

newbie

Activity: 49

Merit: 0

Quote from: doktor83 on July 15, 2019, 01:55:05 PM

Quote from: GodOfStars on July 15, 2019, 01:02:03 PM

Quote from: doktor83 on July 15, 2019, 08:15:23 AM

V1.9.2
- Added parameter '--disablerestartonrejectedshares' to disable auto restart of miner on too many rejected shares
- Added parameter '--maxrejectedshares' to set the number of allowed rejected shares on a pool connection ( min 1, max 100, def. 15)
- Optimisations in OpenCL code, so tiny hashrate increase could be seen on Vegas and Ellesmere cards.
- Minor bug fixes

+ Previous version added a feature that restarts miner when there are too many rejected shares. This version adds a new parameter to disable this feature, '--disablerestartonrejectedshares'

+ Also previous version had a hardcoded number of 5 for the max allowed rejected shares, this is now changed to 15, or you can set your own value with '--maxrejectedshares' value

+ Vegas and Ellesmere cards can see some small hashrate increase on major algorithms

Abut the rejected shares parameter, where do we write this code, in the config file or in the start.bat?

Every parameter that starts with -- is a cmd parameter and goes to start.bat:

Code:

SRBMiner-CN.exe --config Config\config-normalv4.txt --pools pools.txt --maxrejectedshares 20

Thank you Doc, for the update and you response. On another note perhaps an idea about the following update. Won't it be cool if let's say to automatically restart the miner every 2-3 days so at least the miner can insure a 24/7 undisturbed operation. For example if the GPUs are mining more than a week straight they start to become buggy at some point. Like, you won't able to close the miner whiteout a hard rig restart or power off, or one of the gpus will die and the miner wont be able to start it back again. So i was thinking if the miner automatically restarts every 2-3 days, of course optional input from the user, would simply amazing. Thaks ones again!

doktor83

hero member

Activity: 2520

Merit: 626

Quote from: GodOfStars on July 15, 2019, 01:02:03 PM

Quote from: doktor83 on July 15, 2019, 08:15:23 AM

V1.9.2
- Added parameter '--disablerestartonrejectedshares' to disable auto restart of miner on too many rejected shares
- Added parameter '--maxrejectedshares' to set the number of allowed rejected shares on a pool connection ( min 1, max 100, def. 15)
- Optimisations in OpenCL code, so tiny hashrate increase could be seen on Vegas and Ellesmere cards.
- Minor bug fixes

+ Previous version added a feature that restarts miner when there are too many rejected shares. This version adds a new parameter to disable this feature, '--disablerestartonrejectedshares'

+ Also previous version had a hardcoded number of 5 for the max allowed rejected shares, this is now changed to 15, or you can set your own value with '--maxrejectedshares' value

+ Vegas and Ellesmere cards can see some small hashrate increase on major algorithms

Abut the rejected shares parameter, where do we write this code, in the config file or in the start.bat?

Every parameter that starts with -- is a cmd parameter and goes to start.bat:

Code:

SRBMiner-CN.exe --config Config\config-normalv4.txt --pools pools.txt --maxrejectedshares 20

GodOfStars

newbie

Activity: 49

Merit: 0

Quote from: doktor83 on July 15, 2019, 08:15:23 AM

V1.9.2
- Added parameter '--disablerestartonrejectedshares' to disable auto restart of miner on too many rejected shares
- Added parameter '--maxrejectedshares' to set the number of allowed rejected shares on a pool connection ( min 1, max 100, def. 15)
- Optimisations in OpenCL code, so tiny hashrate increase could be seen on Vegas and Ellesmere cards.
- Minor bug fixes

+ Previous version added a feature that restarts miner when there are too many rejected shares. This version adds a new parameter to disable this feature, '--disablerestartonrejectedshares'

+ Also previous version had a hardcoded number of 5 for the max allowed rejected shares, this is now changed to 15, or you can set your own value with '--maxrejectedshares' value

+ Vegas and Ellesmere cards can see some small hashrate increase on major algorithms

Abut the rejected shares parameter, where do we write this code, in the config file or in the start.bat?

Topcd

newbie

Activity: 7

Merit: 0

Quote from: doktor83 on July 15, 2019, 07:23:51 AM

Quote from: netmebtc on July 14, 2019, 07:56:37 PM

@doktor83, Hello, When will SRBminer support turtle's new algo "chukwa" and loki's new algo "RandmXL"?

I haven't decided yet what to do with the randomx algo family - it will suck on AMD gpus. Chukwa isn't in my plans atm.

RandomX is the good news for CPU miners and bad news for GPU miners, specially for RX Vega Owners like me as i've heard that the hash rate will drop off around 50% for Rx Vega on this new algorithm, but they say they are doing some optimizations to make it more acceptable.
Let's wait and see what happens! Undecided

doktor83

hero member

Activity: 2520

Merit: 626

V1.9.2
- Added parameter '--disablerestartonrejectedshares' to disable auto restart of miner on too many rejected shares
- Added parameter '--maxrejectedshares' to set the number of allowed rejected shares on a pool connection ( min 1, max 100, def. 15)
- Optimisations in OpenCL code, so tiny hashrate increase could be seen on Vegas and Ellesmere cards.
- Minor bug fixes

+ Previous version added a feature that restarts miner when there are too many rejected shares. This version adds a new parameter to disable this feature, '--disablerestartonrejectedshares'

+ Also previous version had a hardcoded number of 5 for the max allowed rejected shares, this is now changed to 15, or you can set your own value with '--maxrejectedshares' value

+ Vegas and Ellesmere cards can see some small hashrate increase on major algorithms

doktor83

hero member

Activity: 2520

Merit: 626

Quote from: netmebtc on July 14, 2019, 07:56:37 PM

@doktor83, Hello, When will SRBminer support turtle's new algo "chukwa" and loki's new algo "RandmXL"?

I haven't decided yet what to do with the randomx algo family - it will suck on AMD gpus. Chukwa isn't in my plans atm.

netmebtc

newbie

Activity: 72

Merit: 0

@doktor83, Hello, When will SRBminer support turtle's new algo "chukwa" and loki's new algo "RandmXL"?

Topcd

newbie

Activity: 7

Merit: 0

I've tested V1.9.1 on one of my Rigs with 6 RX VEGAs and it is stable after 1 day and a half of mining.
if it goes without any error for two or three days, then i will start to set it up on all of my Rigs.
proof: https://i.ibb.co/DW4XrYt/Monero-14-July.png

KhorneFlake

newbie

Activity: 27

Merit: 0

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.

GodOfStars

newbie

Activity: 49

Merit: 0

Quote from: doktor83 on July 12, 2019, 10:12:15 AM

Quote from: GodOfStars on July 12, 2019, 07:54:49 AM

Quote from: doktor83 on July 12, 2019, 06:35:34 AM

Quote from: GodOfStars on July 12, 2019, 05: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

Try adding "tweak_profile" : 8 in config.txt, for example :

Code:

{
"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 :

Code:

{
"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 Grin

I will add a parameter that disables this in the next version in a few days.

God Bless, you are amazing!

doktor83

hero member

Activity: 2520

Merit: 626

Quote from: GodOfStars on July 12, 2019, 07:54:49 AM

Quote from: doktor83 on July 12, 2019, 06:35:34 AM

Quote from: GodOfStars on July 12, 2019, 05: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

Try adding "tweak_profile" : 8 in config.txt, for example :

Code:

{
"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 :

Code:

{
"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 Grin

I will add a parameter that disables this in the next version in a few days.

GodOfStars

newbie

Activity: 49

Merit: 0

Quote from: doktor83 on July 12, 2019, 06:35:34 AM

Quote from: GodOfStars on July 12, 2019, 05: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

Try adding "tweak_profile" : 8 in config.txt, for example :

Code:

{
"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

hero member

Activity: 2520

Merit: 626

Quote from: GodOfStars on July 12, 2019, 05: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

Try adding "tweak_profile" : 8 in config.txt, for example :

Code:

{
"cryptonight_type" : "normalv4",
"intensity" : 0,
"double_threads" : true,
"off_temperature" : 80,
"tweak_profile" : 8
}

GodOfStars

newbie

Activity: 49

Merit: 0

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

sky2018miner

newbie

Activity: 33

Merit: 0

everything works fine again
thank you very much
as always, fast response and excellent results

doktor83

hero member

Activity: 2520

Merit: 626

Quote from: sky2018miner on July 11, 2019, 10:03:17 AM

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

doktor83

hero member

Activity: 2520

Merit: 626

Quote from: Vcxz on July 11, 2019, 09:51:04 AM

Quote from: doktor83 on July 11, 2019, 08:45:23 AM

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 Grin

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.

Topic: SRBMiner Cryptonight AMD GPU Miner V1.9.3 - native algo switching - page 10. (Read 237207 times)