Show Posts
|
Pages: [1]
|
Dok, hi. What is default value for "giveup_limit" ? And what is the max?
Best regards.
|
|
|
I have all my rigs working on fairpool, all working fine. What version of SRB are you using?
All Did not try to calculate how much idle your devices are, trying to cope with the difficulties .... And how many blocks do you miss .... Accepted shares 99-100%...
|
|
|
https://bitcointalk.org/index.php?topic=2079202.new#newSet the static complexity, the cards are simply idle at a complexity of 1200 000
Will repost my reply from the sumo thread. Are you using SRBMiner, right?
I monitored the network traffic for a while and i'm sure your problem is caused by the bug in the mining software and is not related to the FairPool somehow. FairPool's stratum code utilizes sophisticated variable diff algorithm and it actually does its job quite well.
Just use opensource xmr-stak or xmrig.
Как-то прокомментируете? Somehow comment? i don't really understand what we are talking about here? Is the problem that the pool sets too high diff ? I myself am mining sumo at https://pool.sumokoin.com and it works great . sumo.fairpool.cloud (here all the powers) A person, to talk about not working, was not, he automatically raises the difficulty up to, say, 1200 000, and the cards are beaten empty or nothing until the pool changes complexity, much is lost !!!!! And in the post above, the creators of the pool say that the SRBMiner-CN error and it is necessary to use the other software !!!! I have all my rigs working on fairpool, all working fine. What version of SRB are you using?
|
|
|
V1.4.9- Possibly fixed bug some were having when switching pool from user to devfee - Removed location parameter from config file as it just confused people - Added resources cleanup on miner shutdown Please everyone having issues with miner crashing and stuck on change to devfee mining, download this version, it should fix these issues. Hi, Dok. 16 rigs, 9+ hours, all ok so far... Not so much time to test, but looking promissing. Thanks.
|
|
|
Dok,
I am having an unusual problem. One of my win 10 rigs with 4 Vega56s had to have win10 reinstalled due to OS software screwup, so I thought I'd try your software without AMD Blockchain drivers using win10-64bit-radeon-software-adrenalin-edition-18.3.4-march23 drivers.
No matter what I do your miner will only hash on GPU 0 and 3, GPU 1 and 2 do not hash, they are recognized, but no hashing, I have tried very low intensity, but with no effect.
Any ideas?
Stupid question, but did you turn on computing mode on adrenalin drivers?
|
|
|
Dok, hi. Can send only 2 private messages per day. Testing what you asked in last message. I'll write you ASAP.
Thank you, i hope this is it now Started it on 16 rigs, to increase efficiency.
|
|
|
Dok, hi. Can send only 2 private messages per day. Testing what you asked in last message. I'll write you ASAP.
|
|
|
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
|
|
|
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.
|
|
|
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?
|
|
|
|