avirdoz
Legendary
 Offline
Activity: 1191
Merit: 1001
|
 |
March 18, 2019, 04:18:17 PM |
|
H/r has decreased after with CN4 on my old 470x, 950 vs 850 h/s. Is it normal?
|
|
|
|
|
|
|
|
"Governments are good at cutting off the heads of a centrally
controlled
networks like Napster, but pure P2P networks like Gnutella and Tor seem
to be holding their own." -- Satoshi
|
|
|
Advertised sites are not endorsed by the Bitcoin Forum. They may be unsafe, untrustworthy, or illegal in your jurisdiction.
|
Kaezar
Newbie
Offline
Activity: 73
Merit: 0
|
|
March 18, 2019, 04:19:48 PM |
|
Pool prohashing.com, v4 algo. 18.6.1, rx570.
[2019-03-18 19:12:19] Connected to prohashing.com:3347
[2019-03-18 19:12:19] User logged in
[2019-03-18 19:12:19] Pool difficulty: 50000
[2019-03-18 19:12:19] Pool sent a new job [ID: 1985c64]
[2019-03-18 19:12:19] Block height = 0 for V4 job - DeviceID 0 (Thread 0) [report to pool]
[2019-03-18 19:12:19] Block height = 0 for V4 job - DeviceID 0 (Thread 1) [report to pool]
[2019-03-18 19:12:30] Pool accepted result 0x00007624 for job[1] [124ms]
[2019-03-18 19:12:52] GPU0 : 994 H/s [T: 52c, RPM: 1800, CC: 1250 MHz, MC: 2265 MHz][BUS:1]
[2019-03-18 19:12:52] Total: 994 H/s
[2019-03-18 19:13:13] Pool sent a new job [ID: 1986970]
[2019-03-18 19:13:14] Block height = 0 for V4 job - DeviceID 0 (Thread 0) [report to pool]
[2019-03-18 19:13:15] Block height = 0 for V4 job - DeviceID 0 (Thread 1) [report to pool]
[2019-03-18 19:13:15] Pool sent a new job [ID: 1986989]
[2019-03-18 19:13:16] Block height = 0 for V4 job - DeviceID 0 (Thread 0) [report to pool]
[2019-03-18 19:13:16] ERROR : PARSE error: Malformed data received!
[2019-03-18 19:13:16] Pool accepted result 0x000027C9 for job[3] [130ms]
[2019-03-18 19:13:16] Reconnecting to prohashing.com:3347 in 10 seconds
[2019-03-18 19:13:17] Block height = 0 for V4 job - DeviceID 0 (Thread 1) [report to pool]
[2019-03-18 19:13:27] Connected to prohashing.com:3347
[2019-03-18 19:13:28] User logged in
[2019-03-18 19:13:28] Pool difficulty: 50000
[2019-03-18 19:13:28] Pool sent a new job [ID: 1986efa]
[2019-03-18 19:13:28] Block height = 0 for V4 job - DeviceID 0 (Thread 1) [report to pool]
[2019-03-18 19:13:28] Block height = 0 for V4 job - DeviceID 0 (Thread 0) [report to pool]
[2019-03-18 19:13:43] GPU0 : 990 H/s [T: 50c, RPM: 1960, CC: 1250 MHz, MC: 2265 MHz][BUS:1]
[2019-03-18 19:13:43] Total: 990 H/s
[2019-03-18 19:13:49] Pool accepted result 0x00001E27 for job[4] [130ms]
|
|
|
|
|
|
doktor83 (OP)
|
|
March 18, 2019, 04:29:41 PM |
|
Pool prohashing.com, v4 algo. 18.6.1, rx570.
[2019-03-18 19:12:19] Connected to prohashing.com:3347
[2019-03-18 19:12:19] User logged in
[2019-03-18 19:12:19] Pool difficulty: 50000
[2019-03-18 19:12:19] Pool sent a new job [ID: 1985c64]
[2019-03-18 19:12:19] Block height = 0 for V4 job - DeviceID 0 (Thread 0) [report to pool]
[2019-03-18 19:12:19] Block height = 0 for V4 job - DeviceID 0 (Thread 1) [report to pool]
[2019-03-18 19:12:30] Pool accepted result 0x00007624 for job[1] [124ms]
[2019-03-18 19:12:52] GPU0 : 994 H/s [T: 52c, RPM: 1800, CC: 1250 MHz, MC: 2265 MHz][BUS:1]
[2019-03-18 19:12:52] Total: 994 H/s
[2019-03-18 19:13:13] Pool sent a new job [ID: 1986970]
[2019-03-18 19:13:14] Block height = 0 for V4 job - DeviceID 0 (Thread 0) [report to pool]
[2019-03-18 19:13:15] Block height = 0 for V4 job - DeviceID 0 (Thread 1) [report to pool]
[2019-03-18 19:13:15] Pool sent a new job [ID: 1986989]
[2019-03-18 19:13:16] Block height = 0 for V4 job - DeviceID 0 (Thread 0) [report to pool]
[2019-03-18 19:13:16] ERROR : PARSE error: Malformed data received!
[2019-03-18 19:13:16] Pool accepted result 0x000027C9 for job[3] [130ms]
[2019-03-18 19:13:16] Reconnecting to prohashing.com:3347 in 10 seconds
[2019-03-18 19:13:17] Block height = 0 for V4 job - DeviceID 0 (Thread 1) [report to pool]
[2019-03-18 19:13:27] Connected to prohashing.com:3347
[2019-03-18 19:13:28] User logged in
[2019-03-18 19:13:28] Pool difficulty: 50000
[2019-03-18 19:13:28] Pool sent a new job [ID: 1986efa]
[2019-03-18 19:13:28] Block height = 0 for V4 job - DeviceID 0 (Thread 1) [report to pool]
[2019-03-18 19:13:28] Block height = 0 for V4 job - DeviceID 0 (Thread 0) [report to pool]
[2019-03-18 19:13:43] GPU0 : 990 H/s [T: 50c, RPM: 1960, CC: 1250 MHz, MC: 2265 MHz][BUS:1]
[2019-03-18 19:13:43] Total: 990 H/s
[2019-03-18 19:13:49] Pool accepted result 0x00001E27 for job[4] [130ms]
That is not a CN V4/R pool or if it is, it's not working good. The accepted messages are false. |
|
|
|
Kaezar
Newbie
Offline
Activity: 73
Merit: 0
|
|
March 18, 2019, 04:32:48 PM |
|
That is not a CN V4/R pool or if it is, it's not working good. The accepted messages are false.
No. It's also CN V4/R pool. TMR working well. Hashing withouts errors. |
|
|
|
|
|
doktor83 (OP)
|
|
March 18, 2019, 04:47:37 PM |
|
That is not a CN V4/R pool or if it is, it's not working good. The accepted messages are false.
No. It's also CN V4/R pool. TMR working well. Hashing withouts errors. It cant work when the pool does not send block height, you can see in the log in the json if the pool sent block height or not can you paste a part of the log where this error is? |
|
|
|
Kaezar
Newbie
Offline
Activity: 73
Merit: 0
|
|
March 18, 2019, 05:15:58 PM |
|
That is not a CN V4/R pool or if it is, it's not working good. The accepted messages are false.
No. It's also CN V4/R pool. TMR working well. Hashing withouts errors. It cant work when the pool does not send block height, you can see in the log in the json if the pool sent block height or not can you paste a part of the log where this error is? [2019-03-18 20:09:11] json_send[160]: {"id":1,"jsonrpc": "2.0","method":"login","params":{"login":"me","pass":"d=50000 n=rx570-2","agent":"SRBMiner Cryptonight AMD GPU miner/1.8.1","rigid":""}}
[2019-03-18 20:09:11] json_receive[304]: {"id": 1, "result": {"id": "me", "job": {"blob": "0707abd8d8dd05163e813771fb7483305927dade29b0fa724081141a3406c5d9fa9eb52df484e3000000007d808a953ce6747a97ef273356bc917759a763b78c28251c6fc63334b39019db07", "job_id": "initial_job", "target": "10000000", "id": "me"}, "status": "OK"}, "error": null}
[2019-03-18 20:09:11] json_receive[264]: {"id": null, "method": "job", "params": {"id": "me", "blob": "0b0bd69fbfe4054b8a11a88c0c438a9e53e3c6e87ca6de209472a24369e9d979db7822fb5031c7000000009c5312c8a671b9dc57c233c0e5d3d1f78a27741f8c933a4068f03f16231d949f02", "job_id": "19c2f88", "target": "8b4f0100"}}
[2019-03-18 20:09:11] Connected to prohashing.com:3347
[2019-03-18 20:09:11] sock_ready: User logged in
[2019-03-18 20:09:11] pool_have_job: Pool sent a new job [ID: 19c2f88]
[2019-03-18 20:09:12] Block height = 0 for V4 job - DeviceID 0 (Thread 0) [report to pool]
[2019-03-18 20:09:12] Block height = 0 for V4 job - DeviceID 0 (Thread 1) [report to pool]
[2019-03-18 20:09:43] hashrate: GPU0: 992 H/s [T:51c][BUS:1]
[2019-03-18 20:09:43] hashrate: Total: 992 H/s
[2019-03-18 20:10:06] json_receive[264]: {"id": null, "method": "job", "params": {"id": "me", "blob": "0b0bd69fbfe4054b8a11a88c0c438a9e53e3c6e87ca6de209472a24369e9d979db7822fb5031c700000000ea1c0b4a4a934288f7f07510c86747108ee956ebd769968ee9c91421ad68828b02", "job_id": "19c3a3e", "target": "8b4f0100"}}
[2019-03-18 20:10:06] pool_have_job: Pool sent a new job [ID: 19c3a3e]
[2019-03-18 20:10:06] Block height = 0 for V4 job - DeviceID 0 (Thread 1) [report to pool]
[2019-03-18 20:10:07] Block height = 0 for V4 job - DeviceID 0 (Thread 0) [report to pool]
[2019-03-18 20:10:08] pool_ping: Sent keepalive message to pool
[2019-03-18 20:10:08] json_receive[52]: {"id": 1, "result": {"status": "OK"}, "error": null}
[2019-03-18 20:10:17] hashrate: GPU0: 991 H/s [T:52c][BUS:1]
[2019-03-18 20:10:17] hashrate: Total: 991 H/s
[2019-03-18 20:10:17] stats: Algo: normalv4
[2019-03-18 20:10:17] stats: Mining time: 0 days, 0 hours, 1 minutes, 7 seconds
[2019-03-18 20:10:17] stats: Pool: prohashing.com:3347
[2019-03-18 20:10:17] stats: Connected since: 2019-03-18 20:09:11
[2019-03-18 20:10:17] stats: Last job received : 11 seconds ago
[2019-03-18 20:10:51] miner_result: Sending user result to pool
[2019-03-18 20:10:51] json_send[183]: {"id":1,"jsonrpc": "2.0","method":"submit","params":{"id":"me","job_id":"19c3a3e","nonce":"74520000","result":"f9083efa07dba9e102c03af04ee762ff88a84db7999c337bc398cbb793ba0000"}}
[2019-03-18 20:10:51] json_receive[52]: {"id": 1, "result": {"status": "OK"}, "error": null}
[2019-03-18 20:10:51] miner_result: Pool accepted result 0x0000BA93 for job[2] [125ms]
[2019-03-18 20:10:56] json_receive[264]: {"id": null, "method": "job", "params": {"id": "me", "blob": "0b0bd69fbfe4054b8a11a88c0c438a9e53e3c6e87ca6de209472a24369e9d979db7822fb5031c70000000024b1e0da2381f3400d9f1ee2bfeb54884eea0e1209270f9d2b772b0429aaf5ae02", "job_id": "19c4b03", "target": "8b4f0100"}}
[2019-03-18 20:10:56] pool_have_job: Pool sent a new job [ID: 19c4b03]
|
|
|
|
|
|
doktor83 (OP)
|
|
March 18, 2019, 05:26:12 PM |
|
That is not a CN V4/R pool or if it is, it's not working good. The accepted messages are false.
No. It's also CN V4/R pool. TMR working well. Hashing withouts errors. It cant work when the pool does not send block height, you can see in the log in the json if the pool sent block height or not can you paste a part of the log where this error is? [2019-03-18 20:09:11] json_send[160]: {"id":1,"jsonrpc": "2.0","method":"login","params":{"login":"me","pass":"d=50000 n=rx570-2","agent":"SRBMiner Cryptonight AMD GPU miner/1.8.1","rigid":""}}
[2019-03-18 20:09:11] json_receive[304]: {"id": 1, "result": {"id": "me", "job": {"blob": "0707abd8d8dd05163e813771fb7483305927dade29b0fa724081141a3406c5d9fa9eb52df484e3000000007d808a953ce6747a97ef273356bc917759a763b78c28251c6fc63334b39019db07", "job_id": "initial_job", "target": "10000000", "id": "me"}, "status": "OK"}, "error": null}
[2019-03-18 20:09:11] json_receive[264]: {"id": null, "method": "job", "params": {"id": "me", "blob": "0b0bd69fbfe4054b8a11a88c0c438a9e53e3c6e87ca6de209472a24369e9d979db7822fb5031c7000000009c5312c8a671b9dc57c233c0e5d3d1f78a27741f8c933a4068f03f16231d949f02", "job_id": "19c2f88", "target": "8b4f0100"}}
[2019-03-18 20:09:11] Connected to prohashing.com:3347
[2019-03-18 20:09:11] sock_ready: User logged in
[2019-03-18 20:09:11] pool_have_job: Pool sent a new job [ID: 19c2f88]
[2019-03-18 20:09:12] Block height = 0 for V4 job - DeviceID 0 (Thread 0) [report to pool]
[2019-03-18 20:09:12] Block height = 0 for V4 job - DeviceID 0 (Thread 1) [report to pool]
[2019-03-18 20:09:43] hashrate: GPU0: 992 H/s [T:51c][BUS:1]
[2019-03-18 20:09:43] hashrate: Total: 992 H/s
[2019-03-18 20:10:06] json_receive[264]: {"id": null, "method": "job", "params": {"id": "me", "blob": "0b0bd69fbfe4054b8a11a88c0c438a9e53e3c6e87ca6de209472a24369e9d979db7822fb5031c700000000ea1c0b4a4a934288f7f07510c86747108ee956ebd769968ee9c91421ad68828b02", "job_id": "19c3a3e", "target": "8b4f0100"}}
[2019-03-18 20:10:06] pool_have_job: Pool sent a new job [ID: 19c3a3e]
[2019-03-18 20:10:06] Block height = 0 for V4 job - DeviceID 0 (Thread 1) [report to pool]
[2019-03-18 20:10:07] Block height = 0 for V4 job - DeviceID 0 (Thread 0) [report to pool]
[2019-03-18 20:10:08] pool_ping: Sent keepalive message to pool
[2019-03-18 20:10:08] json_receive[52]: {"id": 1, "result": {"status": "OK"}, "error": null}
[2019-03-18 20:10:17] hashrate: GPU0: 991 H/s [T:52c][BUS:1]
[2019-03-18 20:10:17] hashrate: Total: 991 H/s
[2019-03-18 20:10:17] stats: Algo: normalv4
[2019-03-18 20:10:17] stats: Mining time: 0 days, 0 hours, 1 minutes, 7 seconds
[2019-03-18 20:10:17] stats: Pool: prohashing.com:3347
[2019-03-18 20:10:17] stats: Connected since: 2019-03-18 20:09:11
[2019-03-18 20:10:17] stats: Last job received : 11 seconds ago
[2019-03-18 20:10:51] miner_result: Sending user result to pool
[2019-03-18 20:10:51] json_send[183]: {"id":1,"jsonrpc": "2.0","method":"submit","params":{"id":"me","job_id":"19c3a3e","nonce":"74520000","result":"f9083efa07dba9e102c03af04ee762ff88a84db7999c337bc398cbb793ba0000"}}
[2019-03-18 20:10:51] json_receive[52]: {"id": 1, "result": {"status": "OK"}, "error": null}
[2019-03-18 20:10:51] miner_result: Pool accepted result 0x0000BA93 for job[2] [125ms]
[2019-03-18 20:10:56] json_receive[264]: {"id": null, "method": "job", "params": {"id": "me", "blob": "0b0bd69fbfe4054b8a11a88c0c438a9e53e3c6e87ca6de209472a24369e9d979db7822fb5031c70000000024b1e0da2381f3400d9f1ee2bfeb54884eea0e1209270f9d2b772b0429aaf5ae02", "job_id": "19c4b03", "target": "8b4f0100"}}
[2019-03-18 20:10:56] pool_have_job: Pool sent a new job [ID: 19c4b03]
Just as i thought, jobs don't have the needed height parameter : json_receive[264]: {"id": null, "method": "job", "params": {"id": "me", "blob": "0b0bd69fbfe4054b8a11a88c0c438a9e53e3c6e87ca6de209472a24369e9d979db7822fb5031c700000000ea1c0b4a4a934288f7f07510c86747108ee956ebd769968ee9c91421ad68828b02", "job_id": "19c3a3e", "target": "8b4f0100"}}json_receive[264]: {"id": null, "method": "job", "params": {"id": "me", "blob": "0b0bd69fbfe4054b8a11a88c0c438a9e53e3c6e87ca6de209472a24369e9d979db7822fb5031c70000000024b1e0da2381f3400d9f1ee2bfeb54884eea0e1209270f9d2b772b0429aaf5ae02", "job_id": "19c4b03", "target": "8b4f0100"}}
But that pool is crazy, when no block height is sent SRB uses block height 0, and pool accepted that result, which shouldn't happen. this is how a good job should look : json_receive[259]: {"jsonrpc":"2.0","method":"job","params":{"blob":"0b0bf1a5bfe405a17745ceba1ac56db8353be64c3ac900b042217bd528c0a8fd4859b9f25ae7d3000000006b67bdffaf379ef71a75d2fe532b646742a92e3d77f0f2ca774cfdc1053b295612","job_id":"15551","target":"cf8b0000","height":1793523}}
See the "height":1793523 at the end |
|
|
|
Kaezar
Newbie
Offline
Activity: 73
Merit: 0
|
|
March 18, 2019, 05:32:36 PM |
|
json_receive[264]: {"id": null, "method": "job", "params": {"id": "me", "blob": "0b0bd69fbfe4054b8a11a88c0c438a9e53e3c6e87ca6de209472a24369e9d979db7822fb5031c70000000024b1e0da2381f3400d9f1ee2bfeb54884eea0e1209270f9d2b772b0429aaf5ae02", "job_id": "19c4b03", "target": "8b4f0100"}}
But that pool is crazy, when no block height is sent SRB uses block height 0, and pool accepted that result, which shouldn't happen. this is how a good job should look : json_receive[259]: {"jsonrpc":"2.0","method":"job","params":{"blob":"0b0bf1a5bfe405a17745ceba1ac56db8353be64c3ac900b042217bd528c0a8fd4859b9f25ae7d3000000006b67bdffaf379ef71a75d2fe532b646742a92e3d77f0f2ca774cfdc1053b295612","job_id":"15551","target":"cf8b0000","height":1793523}}
See the "height":1793523 at the end Yeah, is a crazy pool. But all winking fine? no need re-programming?) |
|
|
|
|
|
doktor83 (OP)
|
|
March 18, 2019, 05:46:37 PM |
|
json_receive[264]: {"id": null, "method": "job", "params": {"id": "me", "blob": "0b0bd69fbfe4054b8a11a88c0c438a9e53e3c6e87ca6de209472a24369e9d979db7822fb5031c70000000024b1e0da2381f3400d9f1ee2bfeb54884eea0e1209270f9d2b772b0429aaf5ae02", "job_id": "19c4b03", "target": "8b4f0100"}}
But that pool is crazy, when no block height is sent SRB uses block height 0, and pool accepted that result, which shouldn't happen. this is how a good job should look : json_receive[259]: {"jsonrpc":"2.0","method":"job","params":{"blob":"0b0bf1a5bfe405a17745ceba1ac56db8353be64c3ac900b042217bd528c0a8fd4859b9f25ae7d3000000006b67bdffaf379ef71a75d2fe532b646742a92e3d77f0f2ca774cfdc1053b295612","job_id":"15551","target":"cf8b0000","height":1793523}}
See the "height":1793523 at the end Yeah, is a crazy pool. But all winking fine? no need re-programming?) Well if you get hashrate poolside and accepted shares, yeah it's ok  |
|
|
|
eduardooaz
Newbie
Offline
Activity: 24
Merit: 0
|
|
March 18, 2019, 06:11:23 PM |
|
Sup guys.
Long time i dont mine cryptonight, i used SRB to mine heavy algo good time ago and stoped.
Now i am gonna help a friend of myne to mine Monero with SRB miner, monero uses V4 right?
Can some1 tell me what is the intensity that is normaly used in a RX 580 in v4?
|
|
|
|
|
|
doktor83 (OP)
|
|
March 18, 2019, 06:40:44 PM |
|
Sup guys.
Long time i dont mine cryptonight, i used SRB to mine heavy algo good time ago and stoped.
Now i am gonna help a friend of myne to mine Monero with SRB miner, monero uses V4 right?
Can some1 tell me what is the intensity that is normaly used in a RX 580 in v4?
You could try out the auto setup , just leave intensity at 0  |
|
|
|
|
UnclWish
|
|
March 18, 2019, 06:56:04 PM |
|
Sup guys.
Long time i dont mine cryptonight, i used SRB to mine heavy algo good time ago and stoped.
Now i am gonna help a friend of myne to mine Monero with SRB miner, monero uses V4 right?
Can some1 tell me what is the intensity that is normaly used in a RX 580 in v4?
If 8Gb card - try this variants - 71, 72, 90, 104, 108, 112, 116, 118 |
|
|
|
|
RuMiner
Member
Offline
Activity: 168
Merit: 15
|
|
March 18, 2019, 07:12:40 PM |
|
anybody tuned intensity param for CNv4 on Vegas?
|
|
|
|
|
|
doktor83 (OP)
|
|
March 18, 2019, 07:16:51 PM |
|
anybody tuned intensity param for CNv4 on Vegas?
112 for vega56, 123 for vega64, also try playing with the thread delay parameter |
|
|
|
ntshb
Newbie
Offline
Activity: 95
Merit: 0
|
|
March 19, 2019, 01:33:25 AM
Last edit: March 19, 2019, 03:18:07 AM by ntshb |
|
what intensity should I set?
vega 64
|
|
|
|
|
|
UnclWish
|
|
March 19, 2019, 04:53:12 AM |
|
anybody tuned intensity param for CNv4 on Vegas?
112 for vega56, 123 for vega64, also try playing with the thread delay parameter doctor, I have 2 RX 588. On 1st all right, but on 2nd speed max can i get on SRB miner is 1001-1002 h/s on cnr. But on TeamRed miner on this card i have 1045 h/s. Tried different intensities, tried to change thread delay, but can't increase max speed. Windows 10, Drivers is last 19.3.2. |
|
|
|
|
chimaeraa
Newbie
Offline
Activity: 49
Merit: 0
|
|
March 19, 2019, 05:47:16 AM |
|
hi doc. i got this before stop again. [2019-03-19 06:35:04] json_send[200]: {"id":1,"jsonrpc": "2.0","method":"submit","params":{"id":"384626154776718","job_id":"379878018372315","nonce":"63d96f57","result":"30663415f3114aa9e8a801cf612f83ebc252d60e3ccdc77a37a82791bb190000"}}
[2019-03-19 06:35:04] json_receive[62]: {"id":1,"jsonrpc":"2.0","error":null,"result":{"status":"OK"}}
[2019-03-19 06:35:04] miner_result: Pool accepted result 0x000019BB for job[143] [171ms]
[2019-03-19 06:35:28] DevFee pool NOT SET!
[2019-03-19 06:35:28] DevFee pool NOT SET! i use V 1.8.0. |
|
|
|
|
|
doktor83 (OP)
|
|
March 19, 2019, 06:40:54 AM
Last edit: March 19, 2019, 07:01:57 AM by doktor83 |
|
anybody tuned intensity param for CNv4 on Vegas?
112 for vega56, 123 for vega64, also try playing with the thread delay parameter doctor, I have 2 RX 588. On 1st all right, but on 2nd speed max can i get on SRB miner is 1001-1002 h/s on cnr. But on TeamRed miner on this card i have 1045 h/s. Tried different intensities, tried to change thread delay, but can't increase max speed. Windows 10, Drivers is last 19.3.2. Yes you wrote this already, how can i help you ? You are in this a long time ago, you know same cards with same straps & settings won't always give same hashrate.. Someone told me that if he compiles the kernel on 18.6.1 and uses it on 19.2.3, he got better hashrate. Maybe try that. |
|
|
|
|
doktor83 (OP)
|
|
March 19, 2019, 07:05:13 AM |
|
hi doc. i got this before stop again. [2019-03-19 06:35:04] json_send[200]: {"id":1,"jsonrpc": "2.0","method":"submit","params":{"id":"384626154776718","job_id":"379878018372315","nonce":"63d96f57","result":"30663415f3114aa9e8a801cf612f83ebc252d60e3ccdc77a37a82791bb190000"}}
[2019-03-19 06:35:04] json_receive[62]: {"id":1,"jsonrpc":"2.0","error":null,"result":{"status":"OK"}}
[2019-03-19 06:35:04] miner_result: Pool accepted result 0x000019BB for job[143] [171ms]
[2019-03-19 06:35:28] DevFee pool NOT SET!
[2019-03-19 06:35:28] DevFee pool NOT SET! i use V 1.8.0. Miner won't stop if devfee pool can't be set/connected ONCE, it will do something only after few hours of trying. Also why still using 1.8.0 ? |
|
|
|
chimaeraa
Newbie
Offline
Activity: 49
Merit: 0
|
|
March 19, 2019, 07:27:25 AM |
|
hi doc. i got this before stop again. [2019-03-19 06:35:04] json_send[200]: {"id":1,"jsonrpc": "2.0","method":"submit","params":{"id":"384626154776718","job_id":"379878018372315","nonce":"63d96f57","result":"30663415f3114aa9e8a801cf612f83ebc252d60e3ccdc77a37a82791bb190000"}}
[2019-03-19 06:35:04] json_receive[62]: {"id":1,"jsonrpc":"2.0","error":null,"result":{"status":"OK"}}
[2019-03-19 06:35:04] miner_result: Pool accepted result 0x000019BB for job[143] [171ms]
[2019-03-19 06:35:28] DevFee pool NOT SET!
[2019-03-19 06:35:28] DevFee pool NOT SET! i use V 1.8.0. Miner won't stop if devfee pool can't be set/connected ONCE, it will do something only after few hours of trying. Also why still using 1.8.0 ? i don't know why half of my gpu not working and get 0 hash. i think it's about gpu driver. |
|
|
|
|
|
