PhoenixMiner 6.2c: fastest Ethereum/Ethash miner with lowest devfee (Win/Linux)

[cikusa]

Anyone tried 19.9.3 AMD drivers? Miner supports it?

Checked by myself... Driver 19.9.3 is not supported! Miner needs update to support new drivers.

Not only that, but there was also changes how opencl work with kernels that we have right now, better stay on 19.9.2 at this moment.

just curious, are you sure of that? so they started immediately fucking with people, releasing more backward incompatible (maybe driver API changes) shit... nice...
and people prove the point downloading new shit because they hope for the best:)))

Well that opencl thing that was going around here, fake higher hashrate, it is not working anymore. and it was linked to wave32 i suppose, now even if u change it on new drivers, it does nothing.

what is this "fake hashrate" are you talking about? and what is wave32 is it suppose to be an opencl function? I'm confused now was I paid by the pool that was fooled by my fake hashrate as well? or did they just made me feel I was underpaid constantly?

Well let's say this
"
There are architectural changes which affect how code is scheduled:

Single cycle instruction issue:
GCN issued one instruction per wave once every 4 cycles.
RDNA issues instructions every cycle.
Wave32:
GCN used a wavefront size of 64 threads (work items).
RDNA supports both wavefront sizes of 32 and 64 threads.
Workgroup Processors:
GCN grouped the shader hardware into "compute units" (CUs) which contained scalar ALUs and vector ALUs, LDS and memory access. One CU contains 4 SIMD16s which share one path to memory.
RDNA introduced the "workgroup processor" ("WGP"). The WGP replaces the compute unit as the basic unit of shader computation hardware/computing. One WGP encompasses 2 CUs. This allows significantly more compute power and memory bandwidth to be directed at a single workgroup. In RDNA 1 CU is one half of a WGP.
"

So as u can see most of old GCN gpu works in wavefronts of 64 threads in 4 cycles, and new RDNA is doing instruction every cycle. So what i my guess is that that on driver 19.9.2 u could force driver to give 5700xt  64 threads to deal with and then cards were showing hashrates up to 58mh even more but it was also giving incorrect shares so effective hashrate was acaually lower than it was showing on miner console. Now once again my guess is that via wavefront of 64 on Navi u were just giving too much instructions to gpu that gpu just could not handle, since on GCN they were done in 4 cycles and here they need to be done in one cycle. So i suppose later on there will be some new kernels optimized for Navi architecture that will be able to get that hashrate without any incorrect share. Take this with grain of salt, i am far from expert on this field, this is just my understand of it.

Interesting, I lost you at the end, keep thinking how is it known that "gpu cant handle", because if you see bad shares you can actually understand it's not working, so your rate is shit. but now if its about Navi then I don't have any ... yet (is it the 7nm one? like in two flavors 5700 and 5700xl or something?)

Yes i am talking about 5700 and 5700xt, incorrect share does not mean that gpu is not working, it means it is giving shares that are not valid. U can compare it in fact with incorrect share that happen if memory if overclocked too much and it is giving too many errors.

[1713945901]

1713945901

[1713945901]

1713945901

[1713945901]

1713945901

[1713945901]

1713945901

[Ursul0]

Yes i am talking about 5700 and 5700xt, incorrect share does not mean that gpu is not working, it means it is giving shares that are not valid. U can compare it in fact with incorrect share that happen if memory if overclocked too much and it is giving too many errors.

yes also if we are on ethhash, which is memory intensive and it is intensive in the read part mostly (you need only to pass the dag generation phase gracefully. and avoid getting bad shares over the limit

[Ursul0]

no bad shares for me. and I do tREF at 10ms on the bulk of plolarises with amdmemtweak (here I found it for myself - https://bitcointalk.org/index.php?topic=5123724.msg52515352#msg52515352) - my standard safe voltage is 875, cards do not need that much - they take about 868 or lower on these frequencies. and I always use all stages, somehow it feels better. step eround 5-6 mv on freq over 1000 to 1180 - and never go higher 1180(definetely not on ethash) - only very rarely lower. rx4 were natively lower clock as it seems also:) and drivers as you can see can be even older. its 18.2.2 running very smooth on phoenix 4,2c. the restarts were due to maintenance reasons, including smart plugs with wattage from the wall, so now I know the exact total all the time:))



and ohh and is it now WHQL from 19.9.1?

[cikusa]

Yes i am talking about 5700 and 5700xt, incorrect share does not mean that gpu is not working, it means it is giving shares that are not valid. U can compare it in fact with incorrect share that happen if memory if overclocked too much and it is giving too many errors.

yes also if we are on ethhash, which is memory intensive and it is intensive in the read part mostly (you need only to pass the dag generation phase gracefully. and avoid getting bad shares over the limit

I just wanted to let u know what i was thinking, i was not trying to be rude or attack anyone

[Ursul0]

@cikusa

Yes i am talking about 5700 and 5700xt, incorrect share does not mean that gpu is not working, it means it is giving shares that are not valid. U can compare it in fact with incorrect share that happen if memory if overclocked too much and it is giving too many errors.

and here i have an issue with semi-permanent exclusively bad shares production on some of my polarises with Hynix:  
https://bitcointalk.org/index.php?topic=5123724.msg52574444#msg52574444

EDIT: surely no offence, why, I agree with you:)

[Ursul0]

Anyone tried 19.9.3 AMD drivers? Miner supports it?

Checked by myself... Driver 19.9.3 is not supported! Miner needs update to support new drivers.

I told you 19.9.2 is the one to try - it gives slightly lower hashrate on polaris with my configs, but works well.
I think 19.9.2 is the improved one over the previous where they fixed 5700 dag(which is a must for support) bug... if I'm not mistaken or is it 7500... lol)

My Polaris cards works fine with 19.9.2 with full speed as on any other driver.

@UnclWish no seriously have you tried using amdmemtweak? also I'm very much interested if and who's paying whom for not releasing the Nvidia timings to the public and what's up with Claymore's implementation for nvidia

[cikusa]

@cikusa

Yes i am talking about 5700 and 5700xt, incorrect share does not mean that gpu is not working, it means it is giving shares that are not valid. U can compare it in fact with incorrect share that happen if memory if overclocked too much and it is giving too many errors.

and here i have an issue with semi-permanent exclusively bad shares production on some of my polarises with Hynix:  
https://bitcointalk.org/index.php?topic=5123724.msg52574444#msg52574444

EDIT: surely no offence, why, I agree with you:)

It is just that RDNA(Navi) is really different than every GCN card before(7790,R9s R9 fury, any of Polaris cards) that wave32 is just have so much room to grow on this architecture, and i am sure that full potential of 5700 series is not yet unlocked, even on side of core based algorithms.

[Ursul0]

@cikusa

Yes i am talking about 5700 and 5700xt, incorrect share does not mean that gpu is not working, it means it is giving shares that are not valid. U can compare it in fact with incorrect share that happen if memory if overclocked too much and it is giving too many errors.

and here i have an issue with semi-permanent exclusively bad shares production on some of my polarises with Hynix:  
https://bitcointalk.org/index.php?topic=5123724.msg52574444#msg52574444

EDIT: surely no offence, why, I agree with you:)

It is just that RDNA(Navi) is really different than every GCN card before(7790,R9s R9 fury, any of Polaris cards) that wave32 is just have so much room to grow on this architecture, and i am sure that full potential of 5700 series is not yet unlocked, even on side of core based algorithms.

yes I think its a very good card. my partner is setting up some of those now:) so we'll see how it goes. also 7nm is crazy low. we are about to go nutz. no atoms left in the walls no more. new fab process needed. and btw there're some people supposedly doing a single chip on the whole waffer. just think about it, instead of doing small doing actually good. lol

P.S. and I've read the rules about merit growth and I see it stuck on 259 and according to my calculation it should already start growing, maybe rules do not make sense? )

[UnclWish]

Anyone tried 19.9.3 AMD drivers? Miner supports it?

Checked by myself... Driver 19.9.3 is not supported! Miner needs update to support new drivers.

I told you 19.9.2 is the one to try - it gives slightly lower hashrate on polaris with my configs, but works well.
I think 19.9.2 is the improved one over the previous where they fixed 5700 dag(which is a must for support) bug... if I'm not mistaken or is it 7500... lol)

My Polaris cards works fine with 19.9.2 with full speed as on any other driver.

@UnclWish no seriously have you tried using amdmemtweak? also I'm very much interested if and who's paying whom for not releasing the Nvidia timings to the public and what's up with Claymore's implementation for nvidia

Yes, of cause I'm using AMD MemTweak Tool, but not XL variant. Old one, that works with secure boot. I'm use it only for setting REF.

[Ursul0]

Yes, of cause I'm using AMD MemTweak Tool, but not XL variant. Old one, that works with secure boot. I'm use it only for setting REF.

secure boot what is it? you mean you have outside access to each separate worker? or you dont have vegas then? or all in ppts? sorry a bit hectic here:)
I'm using cli version dunno which, just works. ooh I think secure boot is windows related shit for unsigned driver modes or something is that so?

EDIT: I once took anniversary winx used gpedit.msc, just fucking went through it all and read and killed all the stupid crap MS marketing(no cartana and no charbana) you with and then made acronis deployment footprint size below 10gb. and I give no fuck about spectre and whatever shit them may invented. just put it out of fire reach or make burnable:)

[UnclWish]

Yes, of cause I'm using AMD MemTweak Tool, but not XL variant. Old one, that works with secure boot. I'm use it only for setting REF.

secure boot what is it? you mean you have outside access to each separate worker? or you dont have vegas then? or all in ppts? sorry a bit hectic here:)
I'm using cli version dunno which, just works. ooh I think secure boot is windows related shit for unsigned driver modes or something is that so?

EDIT: I once took anniversary winx used gpedit.msc, just fucking went through it all and read and killed all the stupid crap MS marketing(no cartana and no charbana) you with and then made acronis deployment footprint size below 10gb. and I give no fuck about spectre and whatever shit them may invented. just put it out of fire reach or make burnable:)

Yes, secure boot is what didn't allows to load unsigned drivers. So I don't use XL tool version. I'm use pre XL AMD Memtweal GUI tool. I don't have vegas, only Polarises.

[Neurolicious]

Because of the GTX1050Ti (and other 4 GB Nvidia cards) problems under Windows, here is a special release that will solve the issue for a few more weeks. That's the best that can be done, because Nvidia drivers just won't allow to allocate enough VRAM even when it is available. Note that if you don't have 4 GB Nvidia cards, there is no point to use the 4.7a - there are only some small fixes for rare bugs. You can download PhoenixMiner 4.7a from here:

https://mega.nz/#F!fVUGRK4C!CRF040jyvAgr-DJDBn-gTQ  (MEGA)

If you want to check the integrity of the downloaded file, please use the following hashes (you need the last file PhoenixMiner_NVRTC_Windows.zip only if you want to mine BCI with Nvdia cards under Windows):

Code:

    File: PhoenixMiner_4.7a_Windows.zip
    ===================================
   SHA-1: c4448eef92538ff9745a8cd6a79e9f1dbd9d3f20
 SHA-256: 18077c9e18b66a43add6f65eceaad5c56359dffec3e5a0b2bdf609fb8cbb1340
 SHA-512: 45b87fa6f6e80b616bbf97ef02d572fac499660d4b8e854bc3624df6682276aae4341dfe24c04d460d5a44f1c986f6df54ad909ff03861fb4c656d21e716d324


    File: PhoenixMiner_NVRTC_Windows.zip
    ====================================
   SHA-1: ff6fa5e018adbd52caf631c42b7c2fac7ce48a51
 SHA-256: 8087757169405d51ea8ba818347fb05d0450aef985c29272165070346eb5a54a
 SHA-512: 7b2d832f7f40578bb1f501d5174467f5ae06612e601dab769fd56d39da48a471b18c6373435a485155f70fec4017d8378797bf1e1dfe5d62fee30fa6a1d992c4

Here are the new features for this release:

• Reduced VRAM usage for Nvidia cards on Windows to allow slightly longer operation of 4 GB cards under Windows 10 (few weeks to a month, then the problem will appear again)
• Other small improvements and fixes.

Remember to add -rvram -1 -eres 0 to your command-line or config.txt file in order to lower the memory usage as much as possible.

Thank you for this.. I just upgraded to Win10 from Win7 and BOOM the problem begun... Screw Win10 I'm going back to 7.

[ManDoneKTM]

Because of the GTX1050Ti (and other 4 GB Nvidia cards) problems under Windows, here is a special release that will solve the issue for a few more weeks. That's the best that can be done, because Nvidia drivers just won't allow to allocate enough VRAM even when it is available. Note that if you don't have 4 GB Nvidia cards, there is no point to use the 4.7a - there are only some small fixes for rare bugs. You can download PhoenixMiner 4.7a from here:

https://mega.nz/#F!fVUGRK4C!CRF040jyvAgr-DJDBn-gTQ  (MEGA)

If you want to check the integrity of the downloaded file, please use the following hashes (you need the last file PhoenixMiner_NVRTC_Windows.zip only if you want to mine BCI with Nvdia cards under Windows):

Code:

    File: PhoenixMiner_4.7a_Windows.zip
    ===================================
   SHA-1: c4448eef92538ff9745a8cd6a79e9f1dbd9d3f20
 SHA-256: 18077c9e18b66a43add6f65eceaad5c56359dffec3e5a0b2bdf609fb8cbb1340
 SHA-512: 45b87fa6f6e80b616bbf97ef02d572fac499660d4b8e854bc3624df6682276aae4341dfe24c04d460d5a44f1c986f6df54ad909ff03861fb4c656d21e716d324


    File: PhoenixMiner_NVRTC_Windows.zip
    ====================================
   SHA-1: ff6fa5e018adbd52caf631c42b7c2fac7ce48a51
 SHA-256: 8087757169405d51ea8ba818347fb05d0450aef985c29272165070346eb5a54a
 SHA-512: 7b2d832f7f40578bb1f501d5174467f5ae06612e601dab769fd56d39da48a471b18c6373435a485155f70fec4017d8378797bf1e1dfe5d62fee30fa6a1d992c4

Here are the new features for this release:

• Reduced VRAM usage for Nvidia cards on Windows to allow slightly longer operation of 4 GB cards under Windows 10 (few weeks to a month, then the problem will appear again)
• Other small improvements and fixes.

Remember to add -rvram -1 -eres 0 to your command-line or config.txt file in order to lower the memory usage as much as possible.

Thank you for this.. I just upgraded to Win10 from Win7 and BOOM the problem begun... Screw Win10 I'm going back to 7.

Installed w10 ( custom build ) and boom ! All rigs runs flawesly since 2018 

[ContionMig]

Currently using AMD Vega 64, however, cant manage to get above 34.9MH, not even earning profit, any advice?

[Branko]

Currently using AMD Vega 64, however, cant manage to get above 34.9MH, not even earning profit, any advice?

Try to add -acm to command line?

[alexmpa]

Currently using AMD Vega 64, however, cant manage to get above 34.9MH, not even earning profit, any advice?

I'm getting 42,3-42,4 from my 2 Vega 56 cards with quite low power consumption and heat, running this:

switch-radeon-gpu -G 0,1 --admin --hbcc off --largepages on --compute=on restart

WinAMDTweak.exe --CL 17 --RAS 27 --RCDRD 13 --RCDWR 7 --REF 31200

Core clocks are set to 850, memory - to 940.

Theese numbers might be specific for my cards.

[ContionMig]

Currently using AMD Vega 64, however, cant manage to get above 34.9MH, not even earning profit, any advice?

Try to add -acm to command line?

@alexmpa

No Luck
https://i.imgur.com/aGKKdDG.png

[Bael]

Hi

I have an asrock H110 pro btc +, integrated graphic use for monitor and 12 gpus rx570 / 580 mining.

I am having many incorrect shares, before I had 11 gpus without problem, when I put the 12 gpus this problem started.

Do you know if it has to do with the motherboard? I discard the gpus because I have tried to change them and it still happens the same, when connecting 12 fails, with 11 all good.

Attached screenshots

Apologies for writing bad english


https://imgur.com/MFvaP3m

https://imgur.com/it5JwsW

Regards!

[darkneorus]

Hi

I have an asrock H110 pro btc +, integrated graphic use for monitor and 12 gpus rx570 / 580 mining.

I am having many incorrect shares, before I had 11 gpus without problem, when I put the 12 gpus this problem started.

Do you know if it has to do with the motherboard? I discard the gpus because I have tried to change them and it still happens the same, when connecting 12 fails, with 11 all good.

Attached screenshots

Apologies for writing bad english


https://imgur.com/MFvaP3m

https://imgur.com/it5JwsW

Regards!

enter UEFI Setup,
disable unused onboard devices - integrated audio, serial port, ..
set PCIe Link Speed to Gen1.
should work fine then.

[bokel1]

Does Phoenixminer suppport AMD RX5700 (NAVI) under Linux?