**** with Claymore's Dual Miner
2016-08-15 10:25:09 TRACE rpc Request: {"method": "eth_getWork", "params": [], "id":0}
2016-08-15 10:25:09 DEBUG rpc Response: Some("{\"jsonrpc\":\"2.0\",\"error\":{\"code\":-32600,\"message\":\"Invalid request\",\"data\":null},\"id\":null}")
2016-08-15 10:25:10 TRACE rpc Request: {"method": "eth_getWork", "params": [], "id":0}
2016-08-15 10:25:10 DEBUG rpc Response: Some("{\"jsonrpc\":\"2.0\",\"error\":{\"code\":-32600,\"message\":\"Invalid request\",\"data\":null},\"id\":null}")
**** with Ethminer
2016-08-15 10:25:30 TRACE rpc Request: {"id":1,"jsonrpc":"2.0","method":"eth_getWork"}
2016-08-15 10:25:30 DEBUG rpc Response: Some("{\"jsonrpc\":\"2.0\",\"result\":[\"0xcc906703772e5e65d85abb672dc363bc91f866d7b01b61c0877c40d2edc92b49\",\"0x46862965466b5f8011ebefb35a0d1a0b7290c3ba38c11e916c74c347e00ed903\",\"0x00000000001c72ad64007a6db5d3515a0db95a130c9293553de655fde6328914\",\"0x1fa7e4\"],\"id\":1}")
2016-08-15 10:25:32 TRACE rpc Request: {"id":1,"jsonrpc":"2.0","method":"eth_getWork"}
2016-08-15 10:25:32 DEBUG rpc Response: Some("{\"jsonrpc\":\"2.0\",\"result\":[\"0xcc906703772e5e65d85abb672dc363bc91f866d7b01b61c0877c40d2edc92b49\",\"0x46862965466b5f8011ebefb35a0d1a0b7290c3ba38c11e916c74c347e00ed903\",\"0x00000000001c72ad64007a6db5d3515a0db95a130c9293553de655fde6328914\",\"0x1fa7e4\"],\"id\":1}")
2016-08-15 10:25:33 TRACE rpc Request: {"id":1,"jsonrpc":"2.0","method":"eth_submitHashrate","params":["0x62f2","0x0d2d291fe73cba1bfc69c5605a3d3e0af93a2f8c7d210d53cb4c1c263cd3d525"]}
Technically, RPC command in Claymore's Dual Miner is not an issue. Actually, I have tested with RPC command windows in the parity UI, this command is working well. but, with Miner, it shows as the error. I feel as some kind of line termination code error ? or something, strange error has been happening, Headers are not displayed here.. The Content-Type needs to be set, as already mentioned before Thank you for your comment, I have missed your post which has made before, Thank you. Ok, I changed requests a bit, please test this build: https://mega.nz/#!6kJ0lLrD!OVklt9Rxq4ernAMi39CrzPEck_OmngItQVdzKb-067k |
|
|
|
The "simple stratum protocol" lacks a lots of simple features for basic share spoofing / exploit protection so it's a lot of more work todo on my side for validating shares, duplicates, difficulty etc which makes it rather a big risk instead of an advantage if implemented, but I guess if it takes another 1-2 weeks I'll have a look at it again.. I agree, if you don't support HTTP for Sia, proably it will take you more time to implement my stratum. But if you support HTTP it will be very easy because my stratum is just a wrapper around HTTP. |
|
|
|
|
Again, for people who don't have any experience with this miner:
You can change second coin intensity with "+" and "-" keys and see current hashrates with "s" key. This way you can select best value for "-dcri" option.
|
|
|
|
Hi! Claymore.. is siamining stratum supported in the new version?
Thank you!
peace
SiaMining.com [PPS] has added support for Claymore's Stratum on port 7777. See https://siamining.com/help for more info! EthDcrMiner64.exe -epool us1.ethpool.org:3333 -ewal YourEthAddress.YourWorkerName -epsw x -dpool stratum+tcp://siamining.com:7777 -dwal YourSiacoinAddress.YourWorkerName -dcoin sia authentification failed tryed 5.3 and 6 version This works for me: EthDcrMiner64.exe -epool us1.ethpool.org:3333 -ewal 0xD69af2A796A737A103F12d2f0BCC563a13900E6F -epsw x -dpool stratum+tcp://siamining.com:7777 -dwal 3be0304dee313515cf401b8593a0c1df905ed13f0adaee89a8d7337d2ba8209e5ca9f297bbc2 -dcoin sia |
|
|
|
On win 8.1 64 with the 368.81 drivers, a gtx 1070 and a regular batch (it needs to work, I've got experience with it) it hangs. You cannot mine ETH on 368.81 drivers, thanks to buggy nvidia drivers. So, firstly install 369.05 or later and then start miner.hmm, but there is no 369 driver release for win7,8.1 yet , at least i cant find it. only in anniversary upgrade for win10 , provided by M$ NOT WANTING TO CONTRADICT THE MASTER-- But my MAXWELL (GTX9xx) cards run fine on Win 7 x64, nVidia Driver 368.81. It is too soon for me to update either my AMD or nVidia cards, the hardware has not been fully tweaked, and the drivers are the source of many complaints. Red Team or Green Team, the bugs are eating the latest products alive. --scryptr @scryptr - You can't mine on 368.81 drivers WITH a 1070. Of course you can do it for GTX9xx cards, but the op was asking about Win 8.1 and GTX1070. I believe Claymores response wasn't specific because the OP was asking about Win8.1 & GTX1070 working specifically and not all Nvidia cards. @mo35 - You will have to upgrade to Win10 for now if you want to use the GTX1070 at full hashing speeds under Windows. I've been mining under Linux while waiting for the drivers to be fixed, so about to make the switch now myself. You are correct - to be more precise, you cannot mine ETH on 368.81 drivers on latest 10xx cards. You can mine ETH on 368.81 drivers on previous cards like 970 or 980. |
|
|
|
On win 8.1 64 with the 368.81 drivers, a gtx 1070 and a regular batch (it needs to work, I've got experience with it) it hangs. You cannot mine ETH on 368.81 drivers, thanks to buggy nvidia drivers. So, firstly install 369.05 or later and then start miner. |
|
|
|
|
1. Found a bug in multi-GPU config, please redownload v6.0.
2. You can change second coin intensity with "+" and "-" keys and see current hashrates with "s" key.
|
|
|
|
|
v6.0:
- added nVidia support. Tested on 970, 980 and 1070 cards, both single and dual modes are supported. Mixed AMD+nVidia cards are supported too.
- added temperature management for latest AMD 4xx cards.
- added "-ttli" option.
- fixed possible issues with fan management when "-di detect" is used.
NOTE: Linux version will be available in 1-2 days.
|
|
|
|
To all requests: I will check them a bit later, don't want to postpone new version again and again.
Within 24 hours I will release v6.0 with nvidia support, temp/fan management for amd 4xx cards and "-ttli" option to reduce overall mining intensity when GPU is overheated.
Please, support solo mining with Parity v1.3.0 No problem, as soon as someone can explain me how to make it work. Step by step: download link, how to start/configure, etc. Because I spent a lot of time and still don't have any ideas why it does not download blockchain though Mist wallet works on same system. I think, JSONRPC command packet which request the work from the wallet(parity), is not compatible with Parity and it just return Invalid Message Error, I am not sure the how packet has configured from this miner (if there is any option to see the message, let me try with Parity manually), or Could you show me the message in solo mining mode such as ' http://127.0.0.1:8584'; Note: after fully synced with parity 1.3.0; I have tried with ethminer.exe from CPP-Ethereum; I feel the packet from this miner has recognized by parity successfully Thank you for the good support always, Download WireShark and see what packets miner sends, especially packets with "eth_getWork". You can compare my miner and ethminer and see the difference. If you can see it, I can fix it and send you an update for tests. @Claymore you have to sent correct headers to parity (Content-Type: application/json) otherwise it'll refuse to give work. Will you implement suprnova's stratum type for Sia ? I still have some requests asking for it ... 1. It worked for 0.x geth, but fails in Parity. I doubt that I broke something, but it is possible. Anyway I could fix it in a minute if I could make new geth work. Weird situation. 2. Well, it seems you are the only Stratum pool that does not support my simple Stratum version. Again, I'm going to add your Stratum, but I need time for it because I don't use code from sgminer. I've been busy with nvidia for a few weeks and I still see some other important things to do. So if you cannot implement my Stratum, we need to wait some more time, may be 1-2 weeks or so. |
|
|
|
To all requests: I will check them a bit later, don't want to postpone new version again and again.
Within 24 hours I will release v6.0 with nvidia support, temp/fan management for amd 4xx cards and "-ttli" option to reduce overall mining intensity when GPU is overheated.
Please, support solo mining with Parity v1.3.0 No problem, as soon as someone can explain me how to make it work. Step by step: download link, how to start/configure, etc. Because I spent a lot of time and still don't have any ideas why it does not download blockchain though Mist wallet works on same system. I think, JSONRPC command packet which request the work from the wallet(parity), is not compatible with Parity and it just return Invalid Message Error, I am not sure the how packet has configured from this miner (if there is any option to see the message, let me try with Parity manually), or Could you show me the message in solo mining mode such as ' http://127.0.0.1:8584'; Note: after fully synced with parity 1.3.0; I have tried with ethminer.exe from CPP-Ethereum; I feel the packet from this miner has recognized by parity successfully Thank you for the good support always, Download WireShark and see what packets miner sends, especially packets with "eth_getWork". You can compare my miner and ethminer and see the difference. If you can see it, I can fix it and send you an update for tests. |
|
|
|
To all requests: I will check them a bit later, don't want to postpone new version again and again.
Within 24 hours I will release v6.0 with nvidia support, temp/fan management for amd 4xx cards and "-ttli" option to reduce overall mining intensity when GPU is overheated.
Please, support solo mining with Parity v1.3.0 No problem, as soon as someone can explain me how to make it work. Step by step: download link, how to start/configure, etc. Because I spent a lot of time and still don't have any ideas why it does not download blockchain though Mist wallet works on same system. |
|
|
|
|
To all requests: I will check them a bit later, don't want to postpone new version again and again.
Within 24 hours I will release v6.0 with nvidia support, temp/fan management for amd 4xx cards and "-ttli" option to reduce overall mining intensity when GPU is overheated.
|
|
|
|
Hey Claymore,
Will the Nvidia support be a seperate .exe or will the new miner be able to mine with Nvidia and AMD in the same system and claymore instance? Also will it Support Kepler and Maxwell or just newer Pascal stuff?
v6.0 will support amd or nvidia or mixed amd+nvidia in same system. I test it on 970, 980 and 1070 cards on recent drivers. Nvidia 980 works a bit worse in dual mode than AMD 290/390, did not try 1070 yet. |
|
|
|
Some news:
- Finally AMD released ADL10, so I can add temperature/clocks management for Radeon 4xx cards.
- I almost finished NVIDIA support.
I will release new version in 2-4 days.
PS. Still no good nvidia driver for 1070 card for Windows 7/10 for ETH mining? Right now I see ridiculous 1MH/s speed.
There is a driver that works. You need the latest Windows 10 update (anniversary edition 1607) and then you need to update the driver through windows (weird I know, nvidia hasn't published it yet). You can find the details here: https://forum.ethereum.org/discussion/2227/cuda-miner/p64Then the 10xx series will work with Win 10. I'd like to test it on Win7 firstly, I don't like Win10 with its paranoid defender, updates, two control panels, etc. Anyway, I will try to make it work in Win7, if it fails I'll try Win10. |
|
|
|
|
Some news:
- Finally AMD released ADL10, so I can add temperature/clocks management for Radeon 4xx cards.
- I almost finished NVIDIA support.
I will release new version in 2-4 days.
PS. Still no good nvidia driver for 1070 card for Windows 7/10 for ETH mining? Right now I see ridiculous 1MH/s speed.
|
|
|
|
pool nicehash
OS Linux Debian 8.5 amd64
fglrx-driver 15.12
Claymore Miner v5.3
GPU0 -> HD 7850 cclock =1000 mclock = 1250 ethi= 32
CPU1 -> HD 7950 cclock = 1000 mclock =1250 ethi = 48
See "Setting DAG" message between your selections. Nicehash switched to ETH (epoch #68) from some other coin (may be EXP?) with less epoch number (afaik about #10-15 for EXP). Bigger epoch number - less speed. |
|
|
|
|
v2.2:
- Compiled for Catalyst 15.12.
- Repacked to improve Windows 10 support.
|
|
|
|
|
v13.2:
- Repacked to improve Windows 10 support.
|
|
|
|
Claymore, when I edit my configs through remote manager, some digits are added to the end. Since I have dcri at the bottom it looks something like this
-dcri 404
0
9
and the miner starts with 404. I'm on 5.1 beta 2.
Fixed in 5.3, check OP: ..... Latest version v5.3: - added experimental "-di detect" option value to detect correct GPU order for temperatures management. - improved Nicehash pool support (mining.extranonce.subscribe). - fixed issue with sending config.txt to EthMan. - fixed issue in EthMan (possible garbage during remote editing config.txt). |
|
|
|
@Claymore with new AMDGPU-PRO (16.30.3) and ubuntu 16.04 (also on 14.04 LTS) following error every second while mining. is this something you can fix in your miner ? Cause genoils ethminer ( https://github.com/Genoil/cpp-ethereum/tree/110 ) adressed this issue in his miner. thanks regards I don't like Linux. If you know how Genoil fixed it, let me know and I will do the same. But I will not install "AMDGPU-PRO (16.30.3) and ubuntu 16.04 (also on 14.04 LTS)" to try to reproduce it and then try to find the reason, sorry. When trying to use CDM solo with the Parity client (version 1.2.3), I am getting a JSON error when it calls eth_GetWork. Below is the log. Anyone have any ideas what could be going wrong? I've tried -esm settings but they did not help.
Probably, solo with Parity is not supported currently. I tried to install latest client, but it even does not want to download blockchain for some reason (spent a couple of hours with no success), so I cannot check the reason. |
|
|
|
|
Show Posts
