@Claymore, few questions:
1) -cclock: you wrote "you can overclock only", but it seems not to be true for, at least, Windows and Polaris. My 470x can be underclocked (GPU set to 1150 for all states).
2) Any chance to support -cclock and -mclock on Linux for amdgpu-pro drivers (for Polaris)? It is not said "unsupported on Linux", but does not work for me (mem can't be set to 1950 using this).
3) Any chance to support -cvddc and -mvddc on Linux for amdgpu-pro drivers?
4) Are older cards like 7950/7970 supported using amdgpu-pro drivers on Linux?
5) There is an issue on Windows when used -*clock commands: they are applied at some init stage, but for my 470x it instantly changes hashrates only for the card with monitor connected. I can stop and resume other cards for changes to take effect (and show correct/new hashrate), but probably makes sense to fix it somehow, so miner shows correct hashrates after applying values. Of course, if you run it for 2+ time, drivers keep settings and there is no that effect. Still, it is surprising when you run minr with some value and it is not reflected in hashrates.
1. AMD disabled underclocking in theri drivers in past. May be it enabled it again in recent drivers, I did not check it. 2. Linux requires root access for it, I remember someone said that even sudo is not working. 3. Did not check if it is possible. 4. I did not check it. 5. So if I take two 4xx cards, start miner with -*clock option and it will change clocks only for one card? |
|
|
|
@Claymore do sell your Miner so that there is no Fee?
No. All my miners are public, I don't sell private miners. |
|
|
|
I use the parity but i don't like it much. It has problem sometimes when DDOS too. This is Msi afterburner icons of GPU temps. I want total hashrate icon from ethman   Tray is noot good place for numbers 100 and higher. Only two digits are good there. So may be set target total hashrate in EthMan and show % of target hashrate in tray. |
|
|
|
Sometimes geth crushed due DDOS, so why i need 1 minute for that. Anyway request flag to reduce time between attempts to connect and ethman tray icon total hashmeter. It's good if you found that the problem is not in miner. Use Parity when possible, it works much better than geth, really. What about tray hashmeter? I have no clue what you mean, sorry. |
|
|
|
I know what screenshot and log is. Just wanted to show the issue.
Finally I see the log. From the log I see you have 3 ETH pools. After every 3 attempts miner switches to new pool. May be all pools have same IP, I don't know it, I have no idea why you cleared IP because 192.168.x.x addresses are not public, they are not routed. Anyway, 3 or 6 attempts mean that miner changed pool 1 or 2 times. To make a "clean" test, try to remove all settings from command line or config.dat and leave one pool in epools.txt as I described in previous message. Also before starting miner it's a good idea that geth is working (and may be test it with some different miner). In my tests miner always starts working at first attempt. I can add option to change the delay between attempts, but I'm not sure if it really necessary, you are the first person who want to have it. hey Claymore, nice miner!
Maybe you can add to EthMan feature to reduce intensity for a particular gpu?
Already done, check Readme or OP for "-li" option. |
|
|
|
So please add flag for choosing time between tries or number tries.
As you can see, this is not a log file. This is a screenshot. From this screenshot I see only that you get error #7, I get this error if geth is not started. So the problem probably is not in miner. My test is easy: empty command line and empty "config.txt" and one line in epools.txt: POOL: http://localhost:8545 |
|
|
|
Reporting fans not adjusting with -tt (reboot set on -tstop) when updating from v6.2 to v7.2 ubuntu. 5x Asus R9 390 Strix 8GB on risers with Asrock BTC Pro.
Great job on -lidag option, although it doesnt really help me personally, my machine frequently reboots when miner suddenly stops (if too overclocked) , ie. with devfee.
-lidag opitoin : default 0, you can show me how we'll put 1 or value ? @claymore please help ? It is very strange question if you have read Readme. Ok, here is a sample: -lidag 1 |
|
|
|
It works with Wallet address and without, but after 6 tries at 20 sec. How i can reduce time between checking or number of tries ?
At least it works, thank you for help.
I need to see log file |
|
|
|
Claymore, do your miner has ability to failover with SOLO ETH wallets ? I see only pool options like ESM, wallet_address.Workername.
The best way is to try, it would take you a minute only to create epools.txt with this line: POOL: http://192.168.0.1:8545Then start miner and see if it works. I've read this "Do not change spacing, spaces between parameters and values are required for parsing." and thought i can't delete any parameters. Ok i will try. No, it's not working or i may got a mistake. POOL: http://192.168.0.1:8545, WALLET: 0x4b670df9fbc586fge356b426361d57911f1da682 POOL: http://192.168.0.2:8544, WALLET: 0xc05ce628f4c37h3c60d531ef26b54c13fb3e6f22 In your readme explanation and examples for pools only with their parameters like ESM, worker name and not any example for solo. When you mine SOLO, you do not specify wallet in the miner. "SAMPLE USAGE" section: Ethereum SOLO mining (assume geth is on 192.168.0.1:8545):
EthDcrMiner64.exe -epool http://192.168.0.1:8545
Please review my previous message and try to create epools.txt with this line (change IP if necessary): POOL: http://192.168.0.1:8545It works for me. What error do you get exactly? You can PM me the log file. |
|
|
|
Hmm.. How can I disable particular card when mining?
In runtime - press number key, for example, "2" to disable card #2. From command line - use "-di" option. Is there a way to run two instanses of the miner? When i try to mine with 3 cards monero and with 3 cards eth, this miner says port is used and connot connect , the other monero miner is working?
Specify "-mport 0" option, read FAQ in readme for details. Claymore, do your miner has ability to failover with SOLO ETH wallets ? I see only pool options like ESM, wallet_address.Workername.
The best way is to try, it would take you a minute only to create epools.txt with this line: POOL: http://192.168.0.1:8545Then start miner and see if it works. |
|
|
|
Recently started using Claymore, and so far its pretty awesome. Way more stable and profitable compared to what I was using before. Has anyone has any experience using the -logfile flag when running Claymore? I like the fact that it logs whats going on, but I am having trouble logging it to a file that I specify. If anyone has a working example that would be awesome.
When Claymore starts, it says -logfile is an unknown option. Is this flag deprecated from an older version? (I am running 7.1) Or am I just using it incorrectly.
Download v7.2, v7.1 has problems with "-logfile" option. Downloaded and implemented 7.2, although its still giving me UNKNOWN OPTION -logfile UNKNOWN OPTION test.txt Does the -logfile option need to be implemented in a certain place or a certain way? Im running Claymore like this... ./ethdcrminer64 -epool http://STRATUM/WORKER -ewal WALLET -epsw x -allpools 1 -di 0 -dpool XXXXXXX -dwal XXXXXX -dpsw x -dcoin sc -dbg 1 -gser 2 -logfile card0_noappend_log.txt -r 1 -mport 0 Thanks for the help! Oh, linux, use v7.0 then. Or wait v7.3, will be available in a few days. |
|
|
|
Recently started using Claymore, and so far its pretty awesome. Way more stable and profitable compared to what I was using before. Has anyone has any experience using the -logfile flag when running Claymore? I like the fact that it logs whats going on, but I am having trouble logging it to a file that I specify. If anyone has a working example that would be awesome.
When Claymore starts, it says -logfile is an unknown option. Is this flag deprecated from an older version? (I am running 7.1) Or am I just using it incorrectly.
Download v7.2, v7.1 has problems with "-logfile" option. |
|
|
|
@Claymore
is it possible to implement GPU error rate messages like in hwinfo? tool?
Miner has no any info about error, it just sees that GPU got incorrect result. |
|
|
|
@Claymore
if I connect to a pool with "ETH: Stratum - Connected" but then receive "ETH: Job timeout, disconnect, retry in 20 sec..." message in the log, does your miner switch to other pool after 3 job timeouts? or what is the logic of switching?
Yes it will switch to other pool after 3 job timeouts. |
|
|
|
Anyone have any idea why it takes 40-80 seconds for claymore to begin generating DAG on my rx 480 rigs with windows 10 ? this delay happens on all of them. have the latest stable driver (not hotfix, which causes a bit lower performance).
Is my answer not enough? Or may be you missed it: https://bitcointalk.org/index.php?topic=1433925.msg16422035#msg16422035 |
|
|
|
BUG: w/ new DAG and claymore miner.
Up until recently ... the following has worked fine:
Mining EXP and SIA or DCR on my rig on 2 7970's
As of the latest DAG .... this now causes a crash when switching to devpool (subsequently having to change epoch to ETH's epoch), the DAG creation takes 2x longer than usual and at the end of it the machine reboots w/ bug check of a hung device thread status.
Ive repeated this across multiple sets of cards - so its not hardware related.
If you use same version and it started to generate DAG slowly - reboot PC, it's not miner issue, drivers or hardware failed. I have several rigs turned on right now and they work fine with latest 7.2 on Win10. What version of the miner do you use? What pool do you use to mine EXP? Using win7 x64, 15.12, have tried miner 5.3 and the latest 7.2 .... same issues. I dont understand how its a hardware problem. No cards on rig exhibit this problem when generating either EXP or ETH DAG on miner start, only while mining and switching to devfeepool has the problem shown up(going from EXP mining to devfeepool mining). Could it be size of larger new dag and exp dag cant coexist on a card? ( I dont know how the ongpu dag creation works - is the old DAG discarded prior to the GPUs generate a new one? ... if not then its easily a DAG size issue) Completely different GPU's on this rig exhibit same problem ... I doubt all the GPU's are failing .. I just tried to mine EXP, it mines it, after a few DAG switches it still works, no rejected/invalid shares. EXP has epoch #13 and ETH has epoch #79, so it takes in about 1.5 times longer to create DAG for ETH. Try to specify "-allcoins -1" option, see readme for details. If it does not help, ask here if someone mines EXP and has same problems, this way we can confirm that the problem is not in your hardware. PS. If you use dwarfpool (or any pool that accepts wallet address directly) you can avoid DAG re-creation at all, miner can mine EXP in devfee too. Though it seems "-allcoins exp" option was broken in v7.x, I fixed it and I can send you an update. |
|
|
|
Hey Claymore, can you integrate usernames instead of only allowing -u WALLET ? I've got a pool up: https://xmr.suprnova.cc and people would like to mine with your miner, but it seems it doesn't support -u suprnova.1 for example I need to change devfee system for this miner to support all pools, it takes some time, also I'm working on Linux version, so be patient please, I think it will be done in a week. |
|
|
|
BUG: w/ new DAG and claymore miner.
Up until recently ... the following has worked fine:
Mining EXP and SIA or DCR on my rig on 2 7970's
As of the latest DAG .... this now causes a crash when switching to devpool (subsequently having to change epoch to ETH's epoch), the DAG creation takes 2x longer than usual and at the end of it the machine reboots w/ bug check of a hung device thread status.
Ive repeated this across multiple sets of cards - so its not hardware related.
If you use same version and it started to generate DAG slowly - reboot PC, it's not miner issue, drivers or hardware failed. I have several rigs turned on right now and they work fine with latest 7.2 on Win10. What version of the miner do you use? What pool do you use to mine EXP? |
|
|
|
dont know what to say.. here is screen with my config... 270 w from wall atm ... same hasrates of 3 heavily overclocked cards but instead they have heavy downclock.....
As I said before, I don't overclock cards, I always use stock clocks. From your screenshots I see that single card shows 103MH/s LBC and 17MH/s ETH (to get average hashrate I added all hashrate lines and divided them by the number of lines). In my miner on stock single 1070 I can get 17MH/s ETH on "-dcri 220", it shows 83MH/s LBC. But you changed clocks for your cards, so these results cannot be compared to your results. You should start my miner and use "+" and "-" keys to get 17MH/s ETH per card, then see LBC hashrate. |
|
|
|
Claymore, how about adding a mirror with direct http links with easy to remember file names ? (for easy downloading with wget on linux)
Could he just make a bit.ly link to the latest linux version? Then keep that one link updated? How can I make this link for a file on google drive or mega? |
|
|
|
|
Show Posts
