Author

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

hero member
Activity: 2548
Merit: 626
i fu***D up something obviously. Use previous version , im working on a fix.
newbie
Activity: 1
Merit: 0
Yeah, my miners are also getting stuck on the devfee pool.

What's the problem doc?

edit: Using v1.4.8
newbie
Activity: 417
Merit: 0
target_temperature can now be set for every card separately

how i use this? i have 3 card and i wont 1card 60C 2card 58C 3 card 55C

give me example pls.

now i have this:
"cryptonight_type" : "heavy",
"intensity" : 56,
"double_threads" : true,
"target_temperature" : 59,

{ "id" : 0, "intensity" :56, "worksize" : 16, "threads" : 2},
{ "id" : 1, "intensity" : 56, "worksize" : 16, "threads" : 2},
{ "id" : 2, "intensity" : 56, "worksize" : 16, "threads" : 2},
Will be like this:
Code:
"cryptonight_type" : "heavy",
"intensity" : 56,
"double_threads" : true,

{ "id" : 0, "intensity" :56, "worksize" : 16, "threads" : 2, "target_temperature" : 60},
{ "id" : 1, "intensity" : 56, "worksize" : 16, "threads" : 2, "target_temperature" : 58},
{ "id" : 2, "intensity" : 56, "worksize" : 16, "threads" : 2, "target_temperature" : 55},

thx i try.
newbie
Activity: 15
Merit: 0
What pool do you use for dev fee? My miner stuck for 7 hours on this.
https://preview.ibb.co/iLewPH/sbr.png
newbie
Activity: 2
Merit: 0
I want minming SUMO,
SRBMiner selects which algo?
heavy
sumokoin
newbie
Activity: 8
Merit: 0
I want minming SUMO,
SRBMiner selects which algo?
jr. member
Activity: 202
Merit: 2
Hey Doktor

First of all thanks for good work, SRB Miner is the best.

I have a request for pool switch option. While using pool switch option i can switch coins sharing same algorihtms. Can you adjust the miner for pool switch option such as while switching pool, algo switch is also possible. For example while i am mining a coin with normalv7 algo, i can switch a heavy alogrithm coin or lite1 without closing and restarting miner. Is this possible. Thanks in advance.

Sorry but that is not in plan any soon

Sorry to hear that. Its the one feature that everyone is expecting.
I even use MRR to change coins in the same algo but need to stop the miner to change the algo itself.
If the miner change the algo and pool to the dev pool, everyone was thinking it was not that hard to implement.

The Miner is great as it is, thanks!
hero member
Activity: 2548
Merit: 626
Hey Doktor

First of all thanks for good work, SRB Miner is the best.

I have a request for pool switch option. While using pool switch option i can switch coins sharing same algorihtms. Can you adjust the miner for pool switch option such as while switching pool, algo switch is also possible. For example while i am mining a coin with normalv7 algo, i can switch a heavy alogrithm coin or lite1 without closing and restarting miner. Is this possible. Thanks in advance.

Sorry but that is not in plan any soon
hero member
Activity: 2548
Merit: 626
This night I had a problem , can`t connect to pool  for devfee and it has been for 7 hours like this. What could be the issue?

miner version, algo you are mining?
The miner is 1.4.7 mining Heavy algo.  I see others have issue too. Hope it is just a pool problem.

but what error did you get?
It said "Can't connect to devfee pool" ? Or just connected to devfee pool and nothing happens for a long time, or ?
sr. member
Activity: 1484
Merit: 253
target_temperature can now be set for every card separately

how i use this? i have 3 card and i wont 1card 60C 2card 58C 3 card 55C

give me example pls.

now i have this:
"cryptonight_type" : "heavy",
"intensity" : 56,
"double_threads" : true,
"target_temperature" : 59,

{ "id" : 0, "intensity" :56, "worksize" : 16, "threads" : 2},
{ "id" : 1, "intensity" : 56, "worksize" : 16, "threads" : 2},
{ "id" : 2, "intensity" : 56, "worksize" : 16, "threads" : 2},
Will be like this:
Code:
"cryptonight_type" : "heavy",
"intensity" : 56,
"double_threads" : true,

{ "id" : 0, "intensity" :56, "worksize" : 16, "threads" : 2, "target_temperature" : 60},
{ "id" : 1, "intensity" : 56, "worksize" : 16, "threads" : 2, "target_temperature" : 58},
{ "id" : 2, "intensity" : 56, "worksize" : 16, "threads" : 2, "target_temperature" : 55},
hero member
Activity: 1274
Merit: 556
Doktor, I have to say you've built a great miner. Not only is it faster than the competition clock for clock, but it also allows for higher clocks. Amazing stuff.
newbie
Activity: 33
Merit: 0
Hey Doktor

First of all thanks for good work, SRB Miner is the best.

I have a request for pool switch option. While using pool switch option i can switch coins sharing same algorihtms. Can you adjust the miner for pool switch option such as while switching pool, algo switch is also possible. For example while i am mining a coin with normalv7 algo, i can switch a heavy alogrithm coin or lite1 without closing and restarting miner. Is this possible. Thanks in advance.
newbie
Activity: 417
Merit: 0
target_temperature can now be set for every card separately

how i use this? i have 3 card and i wont 1card 60C 2card 58C 3 card 55C

give me example pls.

now i have this:
"cryptonight_type" : "heavy",
"intensity" : 56,
"double_threads" : true,
"target_temperature" : 59,

{ "id" : 0, "intensity" :56, "worksize" : 16, "threads" : 2},
{ "id" : 1, "intensity" : 56, "worksize" : 16, "threads" : 2},
{ "id" : 2, "intensity" : 56, "worksize" : 16, "threads" : 2},
hero member
Activity: 2548
Merit: 626
ok, i will rewrite this the third time...  Huh
newbie
Activity: 10
Merit: 0
Another one...

[2018-04-25 21:52:19] switch_pool: Connected to devfee pool
[2018-04-25 22:22:05] DevFee stops in 18446744073709549896 seconds
[2018-04-25 22:22:06] DevFee stops in 18446744073709549895 seconds
[2018-04-25 22:22:07] DevFee stops in 18446744073709549894 seconds
[2018-04-25 22:22:08] DevFee stops in 18446744073709549893 seconds
[2018-04-25 22:22:09] DevFee stops in 18446744073709549892 seconds
[2018-04-25 22:22:10] DevFee stops in 18446744073709549891 seconds
[2018-04-25 22:22:11] DevFee stops in 18446744073709549890 seconds
[2018-04-25 22:22:12] DevFee stops in 18446744073709549889 seconds
[2018-04-25 22:22:13] DevFee stops in 18446744073709549888 seconds
[2018-04-25 22:22:14] DevFee stops in 18446744073709549887 seconds
[2018-04-25 22:22:15] DevFee stops in 18446744073709549886 seconds
[2018-04-25 22:22:16] DevFee stops in 18446744073709549885 seconds
[2018-04-25 22:22:17] DevFee stops in 18446744073709549884 seconds
[2018-04-25 22:22:18] DevFee stops in 18446744073709549883 seconds
[2018-04-25 22:22:19] DevFee stops in 18446744073709549882 seconds
[2018-04-25 22:22:20] DevFee stops in 18446744073709549881 seconds
[2018-04-25 22:22:21] DevFee stops in 18446744073709549880 seconds
[2018-04-25 22:22:22] DevFee stops in 18446744073709549879 seconds
[2018-04-25 22:22:23] DevFee stops in 18446744073709549878 seconds
[2018-04-25 22:22:24] DevFee stops in 18446744073709549877 seconds
[2018-04-25 22:22:25] DevFee stops in 18446744073709549876 seconds
newbie
Activity: 10
Merit: 0
Hi, doctor.
Still there is a problem with devfee in last version.
My rigs updated to 1.4.8 today, and after connection to devfee pool no reconnection to user pool.
From log:

[2018-04-25 20:21:16] miner_result: Pool accepted result 0x00003805
[2018-04-25 20:21:28] miner_result: Sending user result to pool
[2018-04-25 20:21:28] json_send: {"method":"submit","params":{"id":"2412128013","job_id":"54eb","nonce":"802b56d5","result":"af0ff0380c8bc50cc70f9c9c0fa13124378013c6fa542d8aa6ee1dd3dc680000"},"id":1}
[2018-04-25 20:21:28] json_receive: {"id": 1, "jsonrpc": "2.0", "result": {"status": "OK"}, "error": null}
[2018-04-25 20:21:28] miner_result: Pool accepted result 0x000068DC
[2018-04-25 20:21:28] switch_pool: Connected to devfee  :)pool
[2018-04-25 20:53:52] DevFee stops in 18446744073709549737 seconds

Any ideas?

where is rest of log after devfee started? from 20:21:28

this is insane really

Its copy-paste from log. Nothing else. I dont know where is the rest.
hero member
Activity: 676
Merit: 500
This night I had a problem , can`t connect to pool  for devfee and it has been for 7 hours like this. What could be the issue?

miner version, algo you are mining?
The miner is 1.4.7 mining Heavy algo.  I see others have issue too. Hope it is just a pool problem.
hero member
Activity: 2548
Merit: 626
Hi, doctor.
Still there is a problem with devfee in last version.
My rigs updated to 1.4.8 today, and after connection to devfee pool no reconnection to user pool.
From log:

[2018-04-25 20:21:16] miner_result: Pool accepted result 0x00003805
[2018-04-25 20:21:28] miner_result: Sending user result to pool
[2018-04-25 20:21:28] json_send: {"method":"submit","params":{"id":"2412128013","job_id":"54eb","nonce":"802b56d5","result":"af0ff0380c8bc50cc70f9c9c0fa13124378013c6fa542d8aa6ee1dd3dc680000"},"id":1}
[2018-04-25 20:21:28] json_receive: {"id": 1, "jsonrpc": "2.0", "result": {"status": "OK"}, "error": null}
[2018-04-25 20:21:28] miner_result: Pool accepted result 0x000068DC
[2018-04-25 20:21:28] switch_pool: Connected to devfee  :)pool
[2018-04-25 20:53:52] DevFee stops in 18446744073709549737 seconds

Any ideas?

where is rest of log after devfee started? from 20:21:28

this is insane really
newbie
Activity: 10
Merit: 0
Hi, doctor.
Still there is a problem with devfee in last version.
My rigs updated to 1.4.8 today, and after connection to devfee pool no reconnection to user pool.
From log:

[2018-04-25 20:21:16] miner_result: Pool accepted result 0x00003805
[2018-04-25 20:21:28] miner_result: Sending user result to pool
[2018-04-25 20:21:28] json_send: {"method":"submit","params":{"id":"2412128013","job_id":"54eb","nonce":"802b56d5","result":"af0ff0380c8bc50cc70f9c9c0fa13124378013c6fa542d8aa6ee1dd3dc680000"},"id":1}
[2018-04-25 20:21:28] json_receive: {"id": 1, "jsonrpc": "2.0", "result": {"status": "OK"}, "error": null}
[2018-04-25 20:21:28] miner_result: Pool accepted result 0x000068DC
[2018-04-25 20:21:28] switch_pool: Connected to devfee pool
[2018-04-25 20:53:52] DevFee stops in 18446744073709549737 seconds

Any ideas?
hero member
Activity: 2548
Merit: 626
I get error when miner went for devfees on both my rigs.... anyone else

what kind of error and which version?
Jump to: