Hey guys,

how do you manage to mine using the new 17.12.2 AMD drivers?
I currently use the driver from July (if I'm not wrong), the one someone published on this or another forum with the tag "dag_fix_beta" and which you have to install via device manager.

I was looking for informations about new AMD drivers and how they perform with mining.
Here I read that people have 30+ MH/s using the new release and that you need Claymore 10.3, so I got both, installed 17.12.2 and applied the atikmdag-patcher 1.4.6.
I've edited the BIOS of each of my mining RX580 cards, which probably many miners here did.

After rebooting and starting Clay 10.3 (downloaded it on Thursday), the 1st thing I noticed: the video card numbering is different to Clay 10.0 and 10.2.
I have 4 cards in the mining PC and use 3 of them for mining. Using the same batch file to start Claymore, it suddenly wants to mine with the 4th card, so I guess the clock and voltage values are applied to the wrong cards, too.
With older Claymore releases it works as it should and uses the correct cards.

the 2nd thing I saw: the temperature and fan information is still missing, though Claymore 10.3 was said to be updated to fix this
I mine using Win7 x64.

But the main problem I have is: The cards only mine with about 18 MH/s and with too much power, core temperature also is too high. Wattman shows options for voltage and core frequency settings which don't appear using the older Claymore versions, so I guess 10.3 does not apply the correct values to the cards? I think it doesn't apply ANY values to the cards because the clock/voltage values I use don't differ that much from card to card.

Having 17.12.2 installed I can't use older Claymore releases and 18 MH/s are no option for me, so I went back to the manually installed mentioned dag_fix_beta driver above. I cannot start Wattman anymore because it crashes with this driver installed, but I can mine again at 30+ MH/s and older Claymore miner.

How did you manage to use the new AMD driver and mine at 30+ with undervolting (and edited BIOS)?

BTW: I also see no option to set the cards to compute/mining mode in the AMD Radeon settings, so I added the KMD_EnableInternalLargePage(2) line to every card in the registry which had no effect at all.

maybe another try to get some informations out of people here ...

how does clay 9.7 or 9.8 "react" to nodevfee?
I saw someone write 9.8 notices it.
beside missing fan speed and temperature, I see no difference between 9.7 and 9.8
the only thing I notice is, using ethermine, in the chart the avg hashrate is more below the reported hashrate line than above it, but IMO this could have a different reason because -without changing anything- the avg was a little better a few weeks ago.
any opinion?

so can anyone actually tell something?

what's your clay 9.8 doing if you use it with nodevfee?
I tested and I see no difference (except 9.8 showing correct temp and fan speed)

curious

and this one here installed like a charm (Win7 x64)
I think the temperature rised a bit (compared to 4 weeks ago with no DAG related speed degradation), but also the rate increased by around 2-2.5MH/s
Radeon Settings also load fine from 17.7.2

good stuff

I'd also like to try these out
I see no dag speed degradation on my R9 Nano, but I see it on the RX580. AMD's new driver does not work here -_-

sgminer crashes  or doesn't start working with the R9 Nano.

Ethminer + patches, I just don't know where to find the correct informations and usually people just ignore questions about these things ... not for the 1st time on bitcointalk.org

so you guys suggest installing robinhood's driver?

I had major troubles with recent Radeon driver releases.
RX580 with patched Bios, no ati patch was needed so far

yesterday I tried to install 17.7.2, tried it several times, it always ended with error 1603 (mostly AMD settings failed, but after AMD DDU I was able to finish installing the driver with error 1603 still there, but no more error installing AMD settings)

today I tried to install the older but "better" blockchain beta driver without success. Again 1603 (again with no specific errors listed)
Windows Aero was gone (tastbar looked very plain)
"Radeon settings" did not start. Well it did, but the window was not visible, just a button in taskbar, but no window anywhere
Claymore 9.8 crashed immediately

so I went back to 17.7.2 (with error 1603) but at least Win7 looks normal, no flickering while mining and mining is possible.

I did not find any clear info if the amd/ati patcher is needed with this "new" beta driver. Do you rather suggest robinhood's driver in combination with a Bios patched RX580 (and if so: can you please direct me to it's install how-to?)
many thanks

it's like running in a circle ...

-> "it will steal shares" -> "patch it, then it won't" -> "it will steal shares" -> "patch it, then it won't"  ->

 

I wish I could test versus / compare with the SGminer thing ...

mmh, I wanted to try sgminer-gm 5.5.5 to see how it compares
but it won't even start working ...

[19:29:08] Initialising kernel ethash.cl with nfactor 10, n 1024
[19:29:15] Error -4: Setting args for the DAG kernel and/or executing it.
[19:29:15] Error: clSetKernelArg of all params failed.
[19:29:15] GPU 0 failure, disabling!

(R9 Nano / Fiji)

so if I understand the latest posts right, even the people who wiresharked the traffic are fakes and lied when they wrote that everything looks right?

@all: how important is the effective hash rate value?
Isn't the reported by miner value the one to look at?

C0inZ: yeah, it shows only the past hour values, nanopool shows the ones of each past hour, it makes it easier to compare IMO (for example: start at 9:00 and compare the accepted shares with the number after 1 hour (between 9:00 and 10:00)
for me (while using nanopool) it was the exact number

the default worker is the one with the redirected devfee share(s) and it usually disappears if nothing was found after the next devfee round 1 hour later.

C0inZ, the 2nd worker is called default or x?
if so, that's the redirected share worker

I wish ethermine would show the submitted shares as nanopool does ... would make it a little bit easier so see the number of shares/h for each worker

right now I see no decrease in MH/s
a moment ago claymore went into devfee mining and found 4 shares. 4 at once XDD (single GPU)

btw, I switched pool again and somehow the found shares are higher on ethermine, but I see a few stale shares now and then (between 1 to 3)

pomak, I guess you talk about wireshark and watching the program's traffic?

I'm kinda new to mining and still figuring out the best way, so I try to gain every bit of information I can get
google isn't always helpful
after reading some forum threads and mining websites, I decided to go to nanopool (and tested ethermine once only for a short time)

tesar, you're right, it's under 7.0 and I had to read twice until I saw it XD *so tired*

I currently try it using 9.7, no visible error messages yet

by the way, how do I notice stale shares with nanopool? If the number of shared mentioned there is the same as claymore reports, does it mean that there was no stale share?

it would be nice to add a workername (or if nodevfee it would use the same as the one set on claymore), but oh well

since you tested this nodevfee program it's safe to use, I guess?
I'm always a bit scared about included keylogger and such things, claymore's miner also is closed source (and I always thought stuff on github is open source haha XD)

the readme is a bit puzzling. in the video they suggest to add the port in the batch file (along with the wallet address)
the moment I started nodevfee with the port added to the command line it tried to add the bat file to the autostart folder ... this didn't happen when I 1st started it without the port

if I understand borox right, the 182 shares/h are ETH and DCR shares added together

I don't mine a long time and I like to try out stuff, that's why I'm here and test that python proxy thing

I calculated the dev fee on my 2 PCs was around 10%
I don't know yet how the pool or miner comes up with the found shares. For me it looks like the shares come from the pool, calculated with the rig's hashrate, because here I can see that in every 60 minutes there's a moment where I have like 8 shares in just a few minutes
then for 15-20 minutes not a single share, then again several in another few minutes.
I noticed that the dev fee mining fell into these few minutes. So at the end I have around 20 shares per hour and another 2 that happened in the dev fee mining time period

so I guess dev fee mining basically is like 1% of 60 minutes but if it catches 1 or 2 shares/hr and 20 left for me, it's more than 1%, isn't it? And I've noticed 2 found shares during the dev fee period more than a few times, even if it's just luck :/

does this post make any sense? XD

hey guys
I'm reading here for some time but now I finally registered.

and I've got a question:

I have about 56 MH/s and the shares are between 28 and 45 per hour ...


@b080180d: the readme should tell you everything
just install python 2.7, add the python folder to the Windows path (reboot)
then follow the readme on the github page