NOTE: please upgrade to v15.0 as soon as possible, old versions support up to #299 epoch only, they will fail then! v15.0 supports up to #384 epoch (4GB DAG size).
|
|
|
I don't mind the honestly won millions but I don't understand people that accept to be lied: you have been charged 1.3% when it is clearly stated that you should be charged 1%.
Oh, another newbie states that I'm a thief. I don't care when you get crazy numbers like 39 or 19M$, you can even call me the richest person of this planet, I don't mind. But if you call me a thief and state that I lie about devfee rate, show some proofs. Oops, Sorry. I am in mistake. Your devfee is honest but your hashrate is fake with about 1.5% higher. Everybody can see that by subtracting the pool hash rate from your hashrate doesn't gives 1% (devfee) difference but gives about 2.5% which means that your real hashrate is about 1.5% lower. So you were talking about fake devfee rate 1.3%, now it's fine but there is fake hashrate 1.5%, right? Where do you take these numbers? Ok, probably you have own good source of them. From my experience, I always see a couple of percents fluctuations in hashrate on pool side, and usually it's a bit less than miner shows because miner shows raw hashrate, i.e. it ignores devfee, stale and invalid shares, startup time, dag creation file and other minor things. But pool has to calculate miner's speed from shares only so there is some small error rate there, always. And hashrate that you see on the pool is "final" hashrate, it's always a bit lower. Anyway, if you don't like hashrate that you see, or don't believe it - just use some other miner that shows better numbers or numbers that you believe. I even saw reports like "I tried miner X and now I see +10% shares on pool", so some people think that they get a lot more than 1.5% after changing miner You can try this way too and find the best miner for you, no one forces you to use my miner if you don't like it. PS. I assume that you don't use "devfee cut" tools or cracks, in this case miner really may show some fake hashrate, read Readme for details. Forget the network connections and pools. I really have my own great source of data - it's called common sense. Just take all the shares (accepted + incorrect + rejected) from your log and the averaged stated speed (this needs some elementary programming skills - not applicable to 99.5% of the people who will read this) also from your log for a statistically long enough period (a week, a month or more). Use some basic math (I am not gonna give free math lessons here) having in mind the difficulty of the pool and if you have applied the math properly you will easily find that the stated hashrate is about 1.5% higher than the real one. As easy as pie. You are correct, everybody can examine the logfile and find some better miner if don't like the results. As easy as pie.
|
|
|
I don't mind the honestly won millions but I don't understand people that accept to be lied: you have been charged 1.3% when it is clearly stated that you should be charged 1%.
Oh, another newbie states that I'm a thief. I don't care when you get crazy numbers like 39 or 19M$, you can even call me the richest person of this planet, I don't mind. But if you call me a thief and state that I lie about devfee rate, show some proofs. Oops, Sorry. I am in mistake. Your devfee is honest but your hashrate is fake with about 1.5% higher. Everybody can see that by subtracting the pool hash rate from your hashrate doesn't gives 1% (devfee) difference but gives about 2.5% which means that your real hashrate is about 1.5% lower. So you were talking about fake devfee rate 1.3%, now it's fine but there is fake hashrate 1.5%, right? Where do you take these numbers? Ok, probably you have own good source of them. From my experience, I always see a couple of percents fluctuations in hashrate on pool side, and usually it's a bit less than miner shows because miner shows raw hashrate, i.e. it ignores devfee, stale and invalid shares, startup time, dag creation file and other minor things. But pool has to calculate miner's speed from shares only so there is some small error rate there, always. And hashrate that you see on the pool is "final" hashrate, it's always a bit lower. Anyway, if you don't like hashrate that you see, or don't believe it - just use some other miner that shows better numbers or numbers that you believe. I even saw reports like "I tried miner X and now I see +10% shares on pool", so some people think that they get a lot more than 1.5% after changing miner You can try this way too and find the best miner for you, no one forces you to use my miner if you don't like it. PS. I assume that you don't use "devfee cut" tools or cracks, in this case miner really may show some fake hashrate, read Readme for details.
|
|
|
@big_daddy: thanks! Is it possible to add the block number each time this line appears ?
Unfortunately, pools don't send block number, they only send seedhash so miner can detect epoch number only, not the block number.
|
|
|
I don't mind the honestly won millions but I don't understand people that accept to be lied: you have been charged 1.3% when it is clearly stated that you should be charged 1%.
Oh, another newbie states that I'm a thief. I don't care when you get crazy numbers like 39 or 19M$, you can even call me the richest person of this planet, I don't mind. But if you call me a thief and state that I lie about devfee rate, show some proofs.
|
|
|
I would expect the Non XT to run at around 48MHs (36 CU vs 40 CU), don't know much about power usage in that case.
Nah I’m running plain 5700...extra cores don’t do anything for eth, and it will matter even less when miners are running wave32 code. Yes, both 5700XT and 5700 have the same hashrate.
|
|
|
Currently running 54 MH, haven't started messing with timings yet Also claymore is still running this as old GCN code, he hasn't updated to Wave32 which should significantly reduce core load needed and reduce power to under 100 watts. I do use wave32 mode. During tests I tried wave64 as well, both showed same speed.
|
|
|
Does anyone use claymore 15.0? I got problem with setting up obviously, Bat script is running properly and it is showing increase in mhs but when I want to monitor through nanopool web site it is showing 0 mhs, anyone with same issue?
When I first started using Claymore years ago, I had the same issue as you. Basically it connected to the right pool but after 5, 15,30, 60 minutes of checking my pools stats it showed 0 MH/s and no shares submitted. The issue was that you need to manually change the epool.txt file with your info. Because by default it mines to Claymore's account. It was confusing because it was my pool but apparently the default Claymore pool was also the same one as mine. Eventually after 60 minutes of mining for Claymore it worked on my ETH address. Most likely this is your issue. Incorrect, default epools.txt does not contain any pools, all lines are disabled with "#".
|
|
|
v15.0:
- now miner supports up to #384 epoch (4GB DAG size). Note that previous versions support up to #299 epoch, you will not be able to use old versions after #299 epoch. - added support for Navi cards (ETH-only mode). - now miner sets environment variables automatically (required for 4GB AMD cards). - a few minor bug fixes and improvements.
PS. AMD still has no public Navi drivers with DAG-fix, so currently 5700XT shows a very bad hashrate. But AMD already solved this issue and they promise to release public drivers soon...
|
|
|
@claymore Man i can't wait for you to update something on the XT. On the edge of our seats man!
New version with Navi cards support is ready, I will release it when AMD releases DAG-fix drivers, it will be soon.
|
|
|
Any progress with RX 5700 XT cards ?
I can create ASM binaries for Navi now. But AMD must fix their drivers, they have same problem as old drivers for Polaris, drivers with dag fix are required. AMD knows about this problem, hope they will fix it.
|
|
|
trouble in beta witn rx550 card
21:03:12:322 480 Error loading C:\Claymore's Dual Ethereum+Decred_Siacoin AMD+NVIDIA GPU Miner v6.3\Data1k1.bin 21:03:12:323 480 Cannot build OpenCL program for GPU 0
This bug is due to internal Navi tests, incorrect binary was used. Fixed, please try b748: https://mega.nz/#!D0pFHQSL!K0tlq7j2Huupo-PDK2SMuIovDCuXehcm5YZSQfmNEww
|
|
|
This build 747 sets environment variables automatically, that's the only difference. So if it works for you and previous versions don't work, it means that you cannot correctly set system environment variables in Windows. I will release v14.8 within a few days, it will set environment variables automatically too, right now you can use b747 if you have problems with DAG on 4GB AMD cards.
|
|
|
sure. But two of three rigs just hangs at this same moment (Rx 470 & Rx 480), it happens when ETC touch epoch 280. Below is my config.txt content (they nearly just the same on both machines)
Try "-eres 0".
|
|
|
Any update friend? We are sitting on the edge of our seats! Is there anything anybody can contribute to help you out with this process? Did you try the washer fix for cooling on your card if you have one?
I'm working on it, just need a couple of days more. AMD even did not release official ISA docs for RDNA yet... any news about ETC dag 281+ mining? use phoenix now. this miner dont work
What's wrong with dag 281 epoch? It works fine in my tests. If you want to get some support, it's a good idea to post your config.txt file and some hardware info (or log file).
|
|
|
Claymore is a thief.
I write miners since 2014 and I have some good reputation and earnings in this area, so I don't have any reasons to write viruses and I don't need your coins, I already have enough of them. Hey Claymore any input or any sort of work going on to get the new rx 5700xt mining on your platform? Thanks!
Yes I'm checking this card, but I need a few days to see what hashrate it can achieve.
|
|
|
Wrong power consumption for AMD RX560
Miner just shows values that are returned by video driver. If video driver reports wrong value, you will see wrong value. BTW, you must see same values in GPU-Z.
|
|
|
|