Claymore's Dual Ethereum AMD+NVIDIA GPU Miner v15.0 (Windows/Linux)

[Claymore]

Something wrong, on two mashines, miner crash (not freezz, but process crash):

Confirmed, probably this issue is related to Linux version only. I just saw this on my test linux rig. Since it works for several hours before crashing, it will take some time to fix it.

[1713580618]

1713580618

[1713580618]

1713580618

[1713580618]

1713580618

[1713580618]

1713580618

[Claymore]

@claymore: Do you plan any output from the miner itself maybe in json format ? This would be killer feature for miner with more then just a few rigs to build central monitoring

Miner sends stats in json format, use wireshark or similar tool to see format. So you can write own monitoring utility if you want.

[DDSZ]

So far, I know:
Request:
{"id":0,"jsonrpc":"2.0","method":"miner_getstat1"}
Response:
{"id": 0, "error": null, "result": ["<App_version>", "<Uptime(minutes)>", "<Eth_Mhs>;<Eth_accepts>;<Eth_rejects>", "<Eth_Mhs>", "<Dcr_Mhs>;<Dcr_accepts>;<Dcr_rejects>", "<Dcr_Mhs>", "<GPU_temp>;<GPU_fan_%>", "<Pool>"]}
But I dunno how to make that request...
Claymore, can you please tell us more info about it?

[Claymore]

So far, I know:
Request:
{"id":0,"jsonrpc":"2.0","method":"miner_getstat1"}
Response:
{"id": 0, "error": null, "result": ["<App_version>", "<Uptime(minutes)>", "<Eth_Mhs>;<Eth_accepts>;<Eth_rejects>", "<Eth_Mhs>", "<Dcr_Mhs>;<Dcr_accepts>;<Dcr_rejects>", "<Dcr_Mhs>", "<GPU_temp>;<GPU_fan_%>", "<Pool>"]}
But I dunno how to make that request...
Claymore, can you please tell us more info about it?

It's usual tcp/ip connection - create socket, connect, send the string "{"id":0,"jsonrpc":"2.0","method":"miner_getstat1"}" and read response, disconnect, that is all.

[Claymore]

complete log-file

Finally I got it. Issue confirmed and fixed, re-download v4.3, log must show "b142" now (means build 142).

-erate:

Check OP or readme for sample how to specify worker name for dwarf. Hint:  -ewal YourWallet/YourWorkerName.
Don't use -erate option because it is already "1" by default.

[Flexystar]

Something wrong, on two mashines, miner crash (not freezz, but process crash):

Confirmed, probably this issue is related to Linux version only. I just saw this on my test linux rig. Since it works for several hours before crashing, it will take some time to fix it.

Yup, one little rig i have on windows. Working stable.
Trouble on linux ver.

I try to add -tt 0 (for disable T and Fans watch - but this option does not work oO)

[DDSZ]

So far, I know:
Request:
{"id":0,"jsonrpc":"2.0","method":"miner_getstat1"}
Response:
{"id": 0, "error": null, "result": ["<App_version>", "<Uptime(minutes)>", "<Eth_Mhs>;<Eth_accepts>;<Eth_rejects>", "<Eth_Mhs>", "<Dcr_Mhs>;<Dcr_accepts>;<Dcr_rejects>", "<Dcr_Mhs>", "<GPU_temp>;<GPU_fan_%>", "<Pool>"]}
But I dunno how to make that request...
Claymore, can you please tell us more info about it?

It's usual tcp/ip connection - create socket, connect, send the string "{"id":0,"jsonrpc":"2.0","method":"miner_getstat1"}" and read response, disconnect, that is all.

Got it. Thank you
Actually, I was thinking so, but guess what? Miner just crashed, and thats why connect timed out...

[zyzzyva]

port 8000 also doesn't return anything. Seems like Miner manager does the web part not the miner itself.

Right. You have to be running the Remote Manager, and then you can point your browser at port 8000 on the machine that's running the Remote Manager.

[ekrem]

Hi Claymore how to run the remote menager by XP

[peoples]

So far, I know:
Request:
{"id":0,"jsonrpc":"2.0","method":"miner_getstat1"}
Response:
{"id": 0, "error": null, "result": ["<App_version>", "<Uptime(minutes)>", "<Eth_Mhs>;<Eth_accepts>;<Eth_rejects>", "<Eth_Mhs>", "<Dcr_Mhs>;<Dcr_accepts>;<Dcr_rejects>", "<Dcr_Mhs>", "<GPU_temp>;<GPU_fan_%>", "<Pool>"]}
But I dunno how to make that request...
Claymore, can you please tell us more info about it?

It's usual tcp/ip connection - create socket, connect, send the string "{"id":0,"jsonrpc":"2.0","method":"miner_getstat1"}" and read response, disconnect, that is all.

Got it. Thank you
Actually, I was thinking so, but guess what? Miner just crashed, and thats why connect timed out...

socket to remoteminerip:3333 ? Don't get it ... always timeout

[qqqq]

Claymore, thank you for remote feature, don't tried yet. Btw solomine is ok and finding blocks.

[MinerDudeRigs]

This miner is pretty amazing, thanks a lot Claymore!

[GenTarkin]

Just a heads up too anyone daring and wanting to try:

I spent all afternoon bios modding my 7870 xt's which are normally voltage locked in utils such as MSI Afterburner.
I remember long ago, I had custom bios for higher clocks @ lower voltages on these cards.
But now, for some reason ... whenever I was changing the voltage in bios for these cards.... in windows, they would just go into limp mode when mining ... whereas on default voltage at bios level...the cards didnt have the problem.

So, I thought back to when I was using these cards a couple years ago for gaming.... what was different back then vs now.
The answer:
Crimson vs Catalyst

So, I installed latest catalyst 15.7.1

BAM!!!! Now my voltage mod in BIOS for the cards works great and is no longer in limp mode.

As a bonus, this driver version is actually a BIT FASTER then the recommended Crimson 15.12 (according to the local mining hashrate).

Another bonus I just found out....
Previously -dcri 30-35 would cause ETH mining to slowdown on these cards.
With this driver version I can cruise all the way to -dcri 62 before ETH mining STARTS to slowdown. Meanwhile, DCR nearly doubles in speed.

[WhyMe]

Just a heads up too anyone daring and wanting to try:

I spent all afternoon bios modding my 7870 xt's which are normally voltage locked in utils such as MSI Afterburner.
I remember long ago, I had custom bios for higher clocks @ lower voltages on these cards.
But now, for some reason ... whenever I was changing the voltage in bios for these cards.... in windows, they would just go into limp mode when mining ... whereas on default voltage at bios level...the cards didnt have the problem.

So, I thought back to when I was using these cards a couple years ago for gaming.... what was different back then vs now.
The answer:
Crimson vs Catalyst

So, I installed latest catalyst 15.7.1

BAM!!!! Now my voltage mod in BIOS for the cards works great and is no longer in limp mode.

As a bonus, this driver version is actually a BIT FASTER then the recommended Crimson 15.12 (according to the local mining hashrate).

Another bonus I just found out....
Previously -dcri 30-35 would cause ETH mining to slowdown on these cards.
With this driver version I can cruise all the way to -dcri 62 before ETH mining STARTS to slowdown. Meanwhile, DCR nearly doubles in speed.

Interesting, will test this version.

[GenTarkin]

Just a heads up too anyone daring and wanting to try:

I spent all afternoon bios modding my 7870 xt's which are normally voltage locked in utils such as MSI Afterburner.
I remember long ago, I had custom bios for higher clocks @ lower voltages on these cards.
But now, for some reason ... whenever I was changing the voltage in bios for these cards.... in windows, they would just go into limp mode when mining ... whereas on default voltage at bios level...the cards didnt have the problem.

So, I thought back to when I was using these cards a couple years ago for gaming.... what was different back then vs now.
The answer:
Crimson vs Catalyst

So, I installed latest catalyst 15.7.1

BAM!!!! Now my voltage mod in BIOS for the cards works great and is no longer in limp mode.

As a bonus, this driver version is actually a BIT FASTER then the recommended Crimson 15.12 (according to the local mining hashrate).

Another bonus I just found out....
Previously -dcri 30-35 would cause ETH mining to slowdown on these cards.
With this driver version I can cruise all the way to -dcri 62 before ETH mining STARTS to slowdown. Meanwhile, DCR nearly doubles in speed.

Interesting, will test this version.

Just tried on a 4x 7970 rig ... no ETH speedup , no slowdown either. Was able to increase DCR only a tad.

So, I suspect this wont work for all cards =) ... but anyone needing voltage mod via BIOS on their gpu's to work right, then running Crimson is not an option.

[dingyangangel]

Can't work in https://eth.bw.com/pool/i
port:ether.bw.com:8080

run.bat:
setx GPU_FORCE_64BIT_PTR 0
setx GPU_MAX_HEAP_SIZE 100
setx GPU_USE_SYNC_OBJECTS 1
setx GPU_MAX_ALLOC_PERCENT 100
setx GPU_SINGLE_ALLOC_PERCENT 100
EthDcrMiner64.exe -epool ether.bw.com:8080 -ewal dingyangangel.1 -eworker 1 -epsw x -dpool stratum+tcp://yiimp.ccminer.org:4252 -dwal DsafdmEcgRvkz9EkyRcMwqJQhAtd8hKXnDz -dpsw j70


log:
14:43:17:598   15cc   This pool (ether.bw.com) does not support Ethereum addresses as login (or requires worker name in "Login.Worker" format) and cannot be used for devfee mining, therefore it is not supported.
14:43:17:601   15cc   However, you can mine on this pool if you specify "-allpools 1" option, default pools (different from this pool) will be used for devfee.
14:43:17:601   15cc   Please read "Readme" file for details
14:43:17:605   15cc   This pool (ether.bw.com) does not support Ethereum addresses as login (or requires worker name in "Login.Worker" format) and cannot be used for devfee mining, therefore it is not supported.
14:43:17:608   15cc   However, you can mine on this pool if you specify "-allpools 1" option, default pools (different from this pool) will be used for devfee.
14:43:17:609   15cc   Please read "Readme" file for details
14:43:17:610   15cc   Pool ether.bw.com removed from the list
14:43:17:613   15cc   ETH: No pools specified! Specify at least one valid pool in "-epool" parameter.

[osnwt]

Anybody has issues with 4.3 monitoring on Linux?

@Claymore:

Tried few 4.3 beta (as soon as they were updated). One of them dumped some error and segfaulted. Updated to the latest, the same issue. Restarted - it worked some time with monitoring utility, then turned red and no more updates. The miner itself worked. Restart helped to recover, worked few seconds and gave me the same error:

Code:

ETH - Total Speed: 39.123 Mh/s, Total Shares: 0, Rejected: 0, Time: 00:00
ETH: GPU0 19.556 Mh/s, GPU1 19.567 Mh/s
 DCR - Total Speed: 782.459 Mh/s, Total Shares: 1, Rejected: 0
 DCR: GPU0 391.114 Mh/s, GPU1 391.345 Mh/s
GPU0 t=64C fan=26%, GPU1 t=70C fan=95%
 DCR: 05/19/16-11:26:09 - SHARE FOUND - (GPU 0)
 DCR: Share accepted (82 ms)!
 DCR: 05/19/16-11:26:10 - SHARE FOUND - (GPU 1)
 DCR: Share accepted (83 ms)!
[xcb] Unknown request in queue while dequeuing
[xcb] Most likely this is a multi-threaded client and XInitThreads has not been called
[xcb] Aborting, sorry about that.
ethdcrminer64: ../../src/xcb_io.c:179: dequeue_pending_request: Assertion `!xcb_xlib_unknown_req_in_deq' failed.
./EthDcrMiner.sh: line 71:  2366 Aborted

I think that is some problem with monitoring in the miner, found on Linux only.

[Claymore]

Anybody has issues with 4.3 monitoring on Linux?

@Claymore:

Tried few 4.3 beta (as soon as they were updated). One of them dumped some error and segfaulted. Updated to the latest, the same issue. Restarted - it worked some time with monitoring utility, then turned red and no more updates. The miner itself worked. Restart helped to recover, worked few seconds and gave me the same error:

I'm working on this issue, I will upload an update for Linux today.

[GenTarkin]

Hey claymore...
I noticed the epools.txt & dpools.txt  ... the commas are used as delimiters for parsing.

This caused a problem w/ the PSW setting, one of the pools I mine on takes commas as worker config parameters.
Any chance they can be escaped in the epools/dpools file somehow?

[osnwt]

Great. I hope someone writes a nice webapp for mobiles that uses the same API to (only) get stats. ATM I use internal server but it is Windows only, and I wish to go Linux completely.