Pages:
Author

Topic: PhoenixMiner 6.2c: fastest Ethereum/Ethash miner with lowest devfee (Win/Linux) - page 45. (Read 784965 times)

jr. member
Activity: 33
Merit: 1
Upgraded to 5.7b, kept all the same settings and flags but got a crash within an hour of using it.  Using latest Win 10 and June AMD drivers.  Nothing interesting coming from the logfiles.

I'm using 7 x RX 6800's.  

Will try again using July AMD driver.  

I have the Rx 6800 XT which are almost the same and they are really one of the most problematic cards for mining at least in Windows,as I haven't tried them in Linux.The only option I used and kept them running for a few days with Phoenix miner 5.6d was to use a larger -eres option usually -eres 6-8 which can not be affected by DAG recreation as this is the main issue with Rx 6800 cards,they have 16 GB of memory so with this I have been able to run stable for a week at max.

You're right, the issues happen on DAG recreation.  I'll try your tip with the -eres flag as I haven't gotten anything stable for more than a day or so.
staff
Activity: 3472
Merit: 4111
Crypto Swap Exchange
I had a 1070ti running in a Windows Server 2016 box.  It was actually the most stable of my mining boxes. I managed to get my hands on a 3060ti and swapped them out, and now I can't install any NVidia drivers. They all say the driver isn't compatible with this version of windows.

Has anyone else run into this? And found a way around it?

Thanks,
Try to upgrade your Windows Server 2016 to 2019 version. If I understand truly, Nvidia does not build the latest drivers for old Windows server editions. https://linustechtips.com/topic/1080569-solvedget-rtx-2080-ti-working-on-windows-server-2016/?__cf_chl_jschl_tk__=pmd_7851ee2f4e6840fc53af8a67e4f2a0a4245ecd49-1628418682-0-gqNtZGzNAmKjcnBszQhi
legendary
Activity: 3318
Merit: 1247
Bitcoin Casino Est. 2013
Upgraded to 5.7b, kept all the same settings and flags but got a crash within an hour of using it.  Using latest Win 10 and June AMD drivers.  Nothing interesting coming from the logfiles.

I'm using 7 x RX 6800's.  

Will try again using July AMD driver.  

I have the Rx 6800 XT which are almost the same and they are really one of the most problematic cards for mining at least in Windows,as I haven't tried them in Linux.The only option I used and kept them running for a few days with Phoenix miner 5.6d was to use a larger -eres option usually -eres 6-8 which can not be affected by DAG recreation as this is the main issue with Rx 6800 cards,they have 16 GB of memory so with this I have been able to run stable for a week at max.

The real problem with such cards is that even AMD itself does not really produce that good drivers for them,at least this is what I see because every driver I try it is always the same problem.
newbie
Activity: 28
Merit: 0

  • Implemented new "turbo" kernels (-clkernel 3) for AMD Polaris cards that can work with the current DAG sizes over 4 GB. Note that -clkernel 3 uses double the VRAM and will provide slightly faster hashrate with slightly higher power consumption. You can use the -rvram command-line parameter to specify how much VRAM to be left unused

Please let us know if you have any problems or questions related to PhoenixMiner 5.7b.

Tried the -clkernel 3 on my RX 480 8GB and got lower hashrates than -clkernel 2.
I'm on windows 10 20H2, Radeon Software version 21.6.1
I'm only using the -vmr 25 parameter and -gt 69 as per benchmark suggestion.
Everything else is default.
Your current gt value 69 is not the optimal for -clkernel 3. Put -gt 0 in your settings to find the new best gt value for -clkernel 3. After that you can put -gt NEW_BEST_GT_FOUND_VALUE in your settings.

Thank you very much. I will look into that.

Aaaand nothing changed.
If you have amd rx470/480/570/580 GPUs you will get +0.1mh/s per GPU with -clkernel 3. You will not get increase with Vega, Navi or Nvidia GPUs.
The option -clKernel 3 is ignored for all GPU, when i use -clKernel 3. nitro+ rx570 8g samsung, stock bios.
jr. member
Activity: 33
Merit: 1
Upgraded to 5.7b, kept all the same settings and flags but got a crash within an hour of using it.  Using latest Win 10 and June AMD drivers.  Nothing interesting coming from the logfiles.

I'm using 7 x RX 6800's. 

Will try again using July AMD driver. 
member
Activity: 220
Merit: 12

  • Implemented new "turbo" kernels (-clkernel 3) for AMD Polaris cards that can work with the current DAG sizes over 4 GB. Note that -clkernel 3 uses double the VRAM and will provide slightly faster hashrate with slightly higher power consumption. You can use the -rvram command-line parameter to specify how much VRAM to be left unused

Please let us know if you have any problems or questions related to PhoenixMiner 5.7b.

Tried the -clkernel 3 on my RX 480 8GB and got lower hashrates than -clkernel 2.
I'm on windows 10 20H2, Radeon Software version 21.6.1
I'm only using the -vmr 25 parameter and -gt 69 as per benchmark suggestion.
Everything else is default.
Your current gt value 69 is not the optimal for -clkernel 3. Put -gt 0 in your settings to find the new best gt value for -clkernel 3. After that you can put -gt NEW_BEST_GT_FOUND_VALUE in your settings.

Thank you very much. I will look into that.

Aaaand nothing changed.
If you have amd rx470/480/570/580 GPUs you will get +0.1mh/s per GPU with -clkernel 3. You will not get increase with Vega, Navi or Nvidia GPUs.
jr. member
Activity: 45
Merit: 6

  • Implemented new "turbo" kernels (-clkernel 3) for AMD Polaris cards that can work with the current DAG sizes over 4 GB. Note that -clkernel 3 uses double the VRAM and will provide slightly faster hashrate with slightly higher power consumption. You can use the -rvram command-line parameter to specify how much VRAM to be left unused

Please let us know if you have any problems or questions related to PhoenixMiner 5.7b.

Tried the -clkernel 3 on my RX 480 8GB and got lower hashrates than -clkernel 2.
I'm on windows 10 20H2, Radeon Software version 21.6.1
I'm only using the -vmr 25 parameter and -gt 69 as per benchmark suggestion.
Everything else is default.
Your current gt value 69 is not the optimal for -clkernel 3. Put -gt 0 in your settings to find the new best gt value for -clkernel 3. After that you can put -gt NEW_BEST_GT_FOUND_VALUE in your settings.

Thank you very much. I will look into that.

Aaaand nothing changed.
jr. member
Activity: 45
Merit: 6

  • Implemented new "turbo" kernels (-clkernel 3) for AMD Polaris cards that can work with the current DAG sizes over 4 GB. Note that -clkernel 3 uses double the VRAM and will provide slightly faster hashrate with slightly higher power consumption. You can use the -rvram command-line parameter to specify how much VRAM to be left unused

Please let us know if you have any problems or questions related to PhoenixMiner 5.7b.

Tried the -clkernel 3 on my RX 480 8GB and got lower hashrates than -clkernel 2.
I'm on windows 10 20H2, Radeon Software version 21.6.1
I'm only using the -vmr 25 parameter and -gt 69 as per benchmark suggestion.
Everything else is default.
Your current gt value 69 is not the optimal for -clkernel 3. Put -gt 0 in your settings to find the new best gt value for -clkernel 3. After that you can put -gt NEW_BEST_GT_FOUND_VALUE in your settings.

Thank you very much. I will look into that.
member
Activity: 220
Merit: 12

  • Implemented new "turbo" kernels (-clkernel 3) for AMD Polaris cards that can work with the current DAG sizes over 4 GB. Note that -clkernel 3 uses double the VRAM and will provide slightly faster hashrate with slightly higher power consumption. You can use the -rvram command-line parameter to specify how much VRAM to be left unused

Please let us know if you have any problems or questions related to PhoenixMiner 5.7b.

Tried the -clkernel 3 on my RX 480 8GB and got lower hashrates than -clkernel 2.
I'm on windows 10 20H2, Radeon Software version 21.6.1
I'm only using the -vmr 25 parameter and -gt 69 as per benchmark suggestion.
Everything else is default.
Your current gt value 69 is not the optimal for -clkernel 3. Put -gt 0 in your settings to find the new best gt value for -clkernel 3. After that you can put -gt NEW_BEST_GT_FOUND_VALUE in your settings.
jr. member
Activity: 63
Merit: 1
Hello i download this new version but windows defender give trojan warning:  Program:Win32/Uwamson.A!ml
Computer is work ok.

Anybody have issue with new PhoenixMiner 5.7b?



this is typical for reverse engineering protected software. All developers of malware are using similar protection mechanisms to prevent debugging and reverse-engineering of their software, so Phoenix developers are using the same packer, hence signature matching.
newbie
Activity: 1
Merit: 0
Hello i download this new version but windows defender give trojan warning:  Program:Win32/Uwamson.A!ml
Computer is work ok.

Anybody have issue with new PhoenixMiner 5.7b?



The new beta version is ready. You can download PhoenixMiner 5.7b from here:

PhoenixMiner_5.7b_Windows.zip
PhoenixMiner_5.7b_Linux.tar.gz

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_5.7b_Windows.zip
    ===================================
   SHA-1: 6d55e616ea06896b6d6afde60c6cdfbac67260f0
 SHA-256: febcc9abbbf5426c6caf7004167fb86a1d384dfd14966ca67b4eb55bdcfeb97e
 SHA-512: 5d7a1899efae0e79963cdc6cbf2117283704a0e85539fc353b7ea291a028ba70b6df60422bcb3b97f1b7636133dc16c30cb075a2cfa95f3f4e06e8d35309db28

    File: PhoenixMiner_5.7b_Linux.tar.gz
    ====================================
   SHA-1: 6fb818bd8d96321cd5881557994755c3a9021426
 SHA-256: b56da6d413b6c91716c8d97ddf75dab1b1bbd2ca3183486286097e8349019917
 SHA-512: ea477315f74424489cf1048c4e1927ff8e50c177d9f14258f62ef0db5a893d96392bbfdd5d8326ed7d952593fafa8be390329f21672d76ae679762ac26b15989

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

The new features in this release are:

  • Implemented new "turbo" kernels (-clkernel 3) for AMD Polaris cards that can work with the current DAG sizes over 4 GB. Note that -clkernel 3 uses double the VRAM and will provide slightly faster hashrate with slightly higher power consumption. You can use the -rvram command-line parameter to specify how much VRAM to be left unused
  • Increased the maximum supported DAG epoch to 600 (i.e. until about Sep 2023)
  • Implemented full hardware control for AMD RX6900/6800/6700 cards under Linux. Note that with these cards under Linux you need to specify relative core voltage: e.g. -cclock -50 will set the core voltage to be 50 mV under the default value
  • Added ROCr kernels for Vega, Radeon VII and Navi cards. With these kernels you will be able to run these cards with Linux drivers 20.45 and later but the performance will be lower than with the older PAL drivers and kernels. We recommend using AMD Linux driver 20.30 for all cards except RX6900/6800/6700
  • Fixed an issue causing crashing with some RX6900/6800/6700 cards under Linux (there is no need to run these cards with -clkernel 0 anymore)
  • Added support for AMD Windows drivers up to 21.7.2. Note that Radeon VII cards will not work with drivers 21.6.1 or higher - you need to use older drivers for proper operation of these cards
  • Added support for AMD Linux drivers up to 21.20 (use older drivers for Vega or Radeon VII cards as they will not work with 21.20)
  • Numerous other fixes and small improvements

For more robust integrity check, you can use our GPG public key, which was verifyed with ETH transaction from our main devfee account as explained here: https://bitcointalksearch.org/topic/m.56755869. Here are the signatures for the files in this release:


Please let us know if you have any problems or questions related to PhoenixMiner 5.7b.
R30
newbie
Activity: 19
Merit: 0
Have you a plan to implement "DAG cache" feature for dual mining?
Thank you.

The new beta version is ready. You can download PhoenixMiner 5.7b from here:

PhoenixMiner_5.7b_Windows.zip
PhoenixMiner_5.7b_Linux.tar.gz

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_5.7b_Windows.zip
    ===================================
   SHA-1: 6d55e616ea06896b6d6afde60c6cdfbac67260f0
 SHA-256: febcc9abbbf5426c6caf7004167fb86a1d384dfd14966ca67b4eb55bdcfeb97e
 SHA-512: 5d7a1899efae0e79963cdc6cbf2117283704a0e85539fc353b7ea291a028ba70b6df60422bcb3b97f1b7636133dc16c30cb075a2cfa95f3f4e06e8d35309db28

    File: PhoenixMiner_5.7b_Linux.tar.gz
    ====================================
   SHA-1: 6fb818bd8d96321cd5881557994755c3a9021426
 SHA-256: b56da6d413b6c91716c8d97ddf75dab1b1bbd2ca3183486286097e8349019917
 SHA-512: ea477315f74424489cf1048c4e1927ff8e50c177d9f14258f62ef0db5a893d96392bbfdd5d8326ed7d952593fafa8be390329f21672d76ae679762ac26b15989

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

The new features in this release are:

  • Implemented new "turbo" kernels (-clkernel 3) for AMD Polaris cards that can work with the current DAG sizes over 4 GB. Note that -clkernel 3 uses double the VRAM and will provide slightly faster hashrate with slightly higher power consumption. You can use the -rvram command-line parameter to specify how much VRAM to be left unused
  • Increased the maximum supported DAG epoch to 600 (i.e. until about Sep 2023)
  • Implemented full hardware control for AMD RX6900/6800/6700 cards under Linux. Note that with these cards under Linux you need to specify relative core voltage: e.g. -cclock -50 will set the core voltage to be 50 mV under the default value
  • Added ROCr kernels for Vega, Radeon VII and Navi cards. With these kernels you will be able to run these cards with Linux drivers 20.45 and later but the performance will be lower than with the older PAL drivers and kernels. We recommend using AMD Linux driver 20.30 for all cards except RX6900/6800/6700
  • Fixed an issue causing crashing with some RX6900/6800/6700 cards under Linux (there is no need to run these cards with -clkernel 0 anymore)
  • Added support for AMD Windows drivers up to 21.7.2. Note that Radeon VII cards will not work with drivers 21.6.1 or higher - you need to use older drivers for proper operation of these cards
  • Added support for AMD Linux drivers up to 21.20 (use older drivers for Vega or Radeon VII cards as they will not work with 21.20)
  • Numerous other fixes and small improvements

For more robust integrity check, you can use our GPG public key, which was verifyed with ETH transaction from our main devfee account as explained here: https://bitcointalksearch.org/topic/m.56755869. Here are the signatures for the files in this release:


Please let us know if you have any problems or questions related to PhoenixMiner 5.7b.
member
Activity: 89
Merit: 12
edit: looks like i fixed it with
/etc/modprobe.d/amdgpu.conf

blacklist radeon
blacklist fglrx
options amdgpu si_support=1 cik_support=1 vm_fragment_size=9 audio=0 dc=0 aspm=0 ppfeaturemask=0xffffffff

Quote
need help please

fresh install of ubuntu 20.04 with driver 21.10

i´m unable to set voltage and core/mem clocks
it say: GPU1: Unable to reset core clocks and voltages - error 13
  This requires running PhoenixMiner as root

but i run it as root (also sudo does not help)
i have added "amdgpu.ppfeaturemask=0xffffffff" to grub config

any help is much welcome
newbie
Activity: 3
Merit: 0
I had a 1070ti running in a Windows Server 2016 box.  It was actually the most stable of my mining boxes. I managed to get my hands on a 3060ti and swapped them out, and now I can't install any NVidia drivers. They all say the driver isn't compatible with this version of windows.

Has anyone else run into this? And found a way around it?

Thanks,
jr. member
Activity: 200
Merit: 3
Config:

Windows 10 / AMD Driver 2021.3.3

Command line used:
Code:
PhoenixMiner.exe -amd -eres 1 -coin ETH -dcoin blake2s -pool DAGGERHASHIMOTO.eu-west.nicehash.com:3353 -wal ###########################.########### -pass x -proto 4 -dpool blake2s.eu.mine.zpool.ca:5766 -dwal ################# -dpass ########,c=BTC -log 0 -wdog 0 -cdmport 4002 -gpus 2

Error:
Code:
...
GPU1: DAG generated in 10.9 s (412.3 MB/s)
GPU1 doesn't support Blake2s dual mining
GPU1: Using Ethash OCL kernels (Ellesmere; -clkernel 1)
GPU1: no -gt value specified, switching to auto-tune
GPU1: starting auto-tune process
Eth: New job #cb4e3547 from DAGGERHASHIMOTO.eu-west.nicehash.com:3353; diff: 979MH
...

Surprisingly dual mining ETC & blake2s works.
Command line used:

Code:
PhoenixMiner.exe -amd -eres 1 -coin ETC -dcoin blake2s -pool etchash.eu.mine.zergpool.com:9997 -wal ############################ -pass ##############,c=BTC,mc=ETC,pl=0 -dpool blake2s.eu.mine.zpool.ca:5766 -dwal ################## -dpass ############,c=BTC -log 0 -wdog 0 -cdmport 4002 -gpus 2


jr. member
Activity: 63
Merit: 1
We, users, need update something in PhoenixMiner near EIP1559 fork?  
no, it's full node software to be upgraded, not miner clinet.

@PhoenixMiner BTW a question: Is it possible to use phoenix for solo mining with geth?
newbie
Activity: 10
Merit: 0
We, users, need update something in PhoenixMiner near EIP1559 fork? 
newbie
Activity: 1
Merit: 0

  • Implemented new "turbo" kernels (-clkernel 3) for AMD Polaris cards that can work with the current DAG sizes over 4 GB. Note that -clkernel 3 uses double the VRAM and will provide slightly faster hashrate with slightly higher power consumption. You can use the -rvram command-line parameter to specify how much VRAM to be left unused

Please let us know if you have any problems or questions related to PhoenixMiner 5.7b.

Tried the -clkernel 3 on my RX 480 8GB and got lower hashrates than -clkernel 2.
I'm on windows 10 20H2, Radeon Software version 21.6.1
I'm only using the -vmr 25 parameter and -gt 69 as per benchmark suggestion.
Everything else is default.

I am a lurker and just registered to say that I have the same experience. -clkernel 1 gives me better hashrate than the turbo kernels.

Either way, thanks for the update! I needed to upgrade the drivers and now I can because of it Smiley


jr. member
Activity: 45
Merit: 6

  • Implemented new "turbo" kernels (-clkernel 3) for AMD Polaris cards that can work with the current DAG sizes over 4 GB. Note that -clkernel 3 uses double the VRAM and will provide slightly faster hashrate with slightly higher power consumption. You can use the -rvram command-line parameter to specify how much VRAM to be left unused

Please let us know if you have any problems or questions related to PhoenixMiner 5.7b.

Tried the -clkernel 3 on my RX 480 8GB and got lower hashrates than -clkernel 2.
I'm on windows 10 20H2, Radeon Software version 21.6.1
I'm only using the -vmr 25 parameter and -gt 69 as per benchmark suggestion.
Everything else is default.
jr. member
Activity: 56
Merit: 6
@PhoenixMiner
Is there anything useful with the new version for Nvidia GPUs?
Or those with Nvidia GPUs no need to update to this new 5.7b version?
Pages:
Jump to: