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

I don't believe that is a legitimate version or website. Only use the one you see from the Dev PhoenixMiner as is listed above..

Definitely not! All secure links where you can download the miner are posted on the first page of this topic. And for security reasons, you need to remove the link from your post or make it inactive.

Hi guys.

I am total beginner with mining. Just wanted to see how it works and get a smooth start.

Now I installed phonexminer from here https:##phoenixminer.org#download#. In the version 6.6 b. I used it on my windows main pc. I know now that this idea is obviously not the best option, but i have no other option yet.

I got nearly an heart attack because i saw news that phoenixminer is dangerous or maleware, like 10 minutes after that.

Here I see it should be safe.

The question is, is it safe or not ? 
Thank you for your help.

There is some problem with phoenixminer 5.6 both betas and RX6700 cards.
After new epoch kicked in just now, they simply crash or hash 0.
Rest cards are ok.

Reverting to 5.5c-rc kinda works.

Any advice on best command line settings for a 3090?

Is there any way to mine zil and eth on different pools? I.e eth on ethermine and zil on ezil.

5500 5600 win10 20.11.2

show temp only on 470\480\570\580
on 5500\5600 show only power and cooler

Available GPUs for mining:
GPU1: Radeon RX 570 Series (pcie 1), OpenCL 2.0, 8 GB VRAM, 32 CUs
GPU2: Radeon RX 5500 XT (pcie 4), OpenCL 2.0, 8 GB VRAM, 22 CUs
GPU3: Radeon RX 5500 XT (pcie , OpenCL 2.0, 8 GB VRAM, 22 CUs
GPU4: Radeon RX 570 Series (pcie 9), OpenCL 2.0, 8 GB VRAM, 32 CUs
GPU5: Radeon RX 570 Series (pcie 11), OpenCL 2.0, 8 GB VRAM, 32 CUs
GPU6: Radeon RX 580 Series (pcie 12), OpenCL 2.0, 8 GB VRAM, 36 CUs

GPU1: 51C 51% 104W, GPU2: 63% 55W, GPU3: 41% 56W, GPU4: 46C 41% 94W, GPU5: 47C 43% 93W, GPU6: 55C 63% 88W
GPUs power: 490.2 W; 356 kH/J

5600 rig too
Available GPUs for mining:
GPU1: AMD Radeon RX 5600 XT (pcie 3), OpenCL 2.0, 6 GB VRAM, 36 CUs
GPU2: AMD Radeon RX 5600 XT (pcie 6), OpenCL 2.0, 6 GB VRAM, 36 CUs
GPU3: AMD Radeon RX 5600 XT (pcie 9), OpenCL 2.0, 6 GB VRAM, 36 CUs
GPU4: AMD Radeon RX 5600 XT (pcie 12), OpenCL 2.0, 6 GB VRAM, 36 CUs
GPU5: AMD Radeon RX 5600 XT (pcie 15), OpenCL 2.0, 6 GB VRAM, 36 CUs
GPU6: AMD Radeon RX 5600 XT (pcie 19), OpenCL 2.0, 6 GB VRAM, 36 CUs
GPU7: AMD Radeon RX 5600 XT (pcie 22), OpenCL 2.0, 6 GB VRAM, 36 CUs
GPU8: AMD Radeon RX 5600 XT (pcie 25), OpenCL 2.0, 6 GB VRAM, 36 CUs
GPU9: AMD Radeon RX 5600 XT (pcie 28), OpenCL 2.0, 6 GB VRAM, 36 CUs
GPU10: AMD Radeon RX 5600 XT (pcie 31), OpenCL 2.0, 6 GB VRAM, 36 CUs
GPU11: AMD Radeon RX 5600 XT (pcie 34), OpenCL 2.0, 6 GB VRAM, 36 CUs
GPU12: AMD Radeon RX 5600 XT (pcie 37), OpenCL 2.0, 6 GB VRAM, 36 CUs
GPU1: 61% 84W, GPU2: 64% 81W, GPU3: 74% 86W, GPU4: 64% 35W, GPU5: 62% 86W, GPU6: 52% 72W, GPU7: 65% 83W, GPU8: 78% 88W, GPU9: 69% 84W, GPU10: 64% 87W, GPU11: 64% 82W, GPU12: 69% 85W
GPUs power: 953.0 W; 533 kH/J

When using older versions of PhoenixMiner, it makes sense that you need to run within the supported platforms of the version you are running.   5.5c, 5.6a, and now 5.6b will work with newer driver versions that would not work with older versions of the miner.    Just do a proper backup, then update your drivers and then update the miner before you start the process again.   You may be pleasantly surprised when things work better.

Im still using 5.4c

I tested with Linux AMD driver 21.10.1247438 and 6900 XT.
Kernel version is 5.11.16-arch1-1 . With this kernel version, there is no over(under)clock control. Only powercap can be changed.
In the below scenarios, the power cap is set to 150W.

1. 5.5c + 20.45: ETH speed reported ~59 MH/s. Effective at pool ~59 MH/s.
2. 5.6a + 20.50: ETH speed reported ~59 MH/s. Effective at pool ~59 MH/s.
3. 5.6a + 21.10 + clkernel=0: ETH speed reported between 59 to 61 MH/s. Effective at pool ~60 MH/s. Edit: ~30% stale shares
4. 5.6b + 21.10: ETH speed reported ~64 MH/s. Effective at pool ~20 MH/s.

But if i use this driver my kernals are doomed. I need to use kernal 0 and the hashrate is not stable. The incorrect hashrate are still present too.

Starting from 5.5c (because that was the latest version at the time) none of the versions have got along with linux kernel 5.11, including this one. On 5.5c only first GPU was hashing, on this version it seems like everything starts up properly but then within 15-20 seconds, hashrates start going crazy, fluctuating from 8 to 31 (all polaris GPUs) and the whole OS gets slowed down to 0.2 FPS.

Is there maybe something that needs adjusting on my side or is compatibility still in the works?

I'm asking because kernel 5.12 is right around a corner and it seems like at this pace the gap is only going to grow.

The next release candidate is ready. You can download PhoenixMiner 5.6b from here:

PhoenixMiner_5.6b_Windows.zip
PhoenixMiner_5.6b_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):

The new features in this release (since 5.6a) are:

• Added support for showing GPU hotspot (junction), and video memory temperatures for Nvidia GPUs. Note that the video memory temperature is only shown by some GPUs (3080, 3090, possibly 2080Ti)
• The options -ttj, -ttmem, -tmaxj, and -tmaxmem now also work with Nvidia GPUs
• Added support for AMD Windows drivers 21.4.1
• Added support for AMD Linux drivers 21.10-1244864-ubuntu-18.04 and 21.10-1247438-ubuntu-20.04 (use these only with Polaris or older GPUs, or with the latest RX6x00 GPUs, these drivers won't work with Vega, Radeon VII, or Navi GPUs)

The changes of the previous beta (5.6a) since the last version (5.5c) are:

• Added native kernels for AMD RX6700 GPUs. These are faster than the generic kernels and produce a lot less stale shares
• Increase the max supported DAG epoch to 550 (should be enough to about Jan 2023)
• Full support for setting clocks, fan speeds, voltages, and memory timings of AMD RX6900/6800/6700 cards
• The specific hashrate is now shown in the form of kilo hashes per joule (kH/J). Example: if a GPU has hashrate of 30 MH/s with 100W power usage, the specific hashrate is 300 kH/J
• Added new command-line parameters -ttj and -ttmem, allowing automatic fan speed control based on GPU hotspot (junction), and memory temperatures respectively. Example: -ttmem 83 will keep the GPU memory temperature at or bellow 83C by increasing the fan speed as necessary. These parameters can be combined with -tt, as well as with each other. These options are supported only on AMD GPUs that report junction and memory temperatures
• Added new command-line parameters -tmaxj and -tmaxmem, allowing to decrease the GPU usage when the GPU hotspot (junction), or GPU memory temperatures are above the specified thresholds. These options are supported only on AMD GPUs that report junction and memory temperatures
• Added support for AMD Windows drivers 21.3.2, and 21.3.1
• Added support for AMD Linux drivers 20.50.x. Use this drivers only if you have Polaris or older GPUs, or the latest RX6x000 GPUs. WARNING: Vega, Radeon VII, and Navi GPUs won't work with these drivers!
• Turn off the zero fan feature on AMD cards whenever a fixed fan speed is used (e.g. -tt -40), or when an auto fan with min fan speed is used (e.g. -tt 63 -minfan 35). To disable this feature, add -fanstop 1 command-line parameter
• When -mcdag 1 is specified under Linux, the miner will not wait for the daggen.sh script to finish before starting to generate the DAGs. Instead it will for a fixed 7 seconds. This allows you to do all the following in the daggen.sh: turn off the overclocking of Nvidia GPUs, sleep for 30-60 seconds to allow time for DAG generation, and then re-apply the overclocking of the Nvidia GPUs
• Other small improvements and fixes

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:

• PhoenixMiner_5.6b_Windows.zip.asc
• PhoenixMiner_5.6b_Linux.tar.gz.asc
• PhoenixMiner_NVRTC_Windows.zip.asc

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

EDIT: May 12th, 2021 - changed the links from github.com to phoenixminer.info

1st use driver like 20.11.1 with 5.5c. Then try start that gpu with lower memory clocks like 2020-2040-2060 see when it starts give incorrect shares. 1200 is much you can get that with 1150mhz on core.

I'm having a problem with my rig using pheonixminer 5.5c along with driver 20.5.1 (used a later version but kernals didnt work with 580s so i moved back to 20.5.1).
My issue is that my gpu4 (6 gpus on rig) is giving me incorrect shares. rest of the cards are not. windows 10.
OC is done via the miner itself. i tried many OC settings changes to gpu4, still none working as needed. it gives me many incorrect shares.
On other miners i do not have this problem.

OC settings on rest of the cards are 1200 core, 2100 memory , 850 volt for both core and mem.
Any help is appriciate.

It is not it doesn't work, it is just not supported, if you're not facing any problems that is good it means that the miner will need little to no changes on the next release.

Hi,

First of all, thank you for all of your work!
Ive an Ubuntu Rig with an AMD RX 5700 and a RX 570 inside.
Now I ordered a new AMD RX 6700 XT to add this to my rig.
If I see it correctly, AMD GPU PRO 20.45-1188099 is the first version, which is usable with a RX 6700.
Is there any driver fully supported by PhoenixMiner for Linux, which is usable for all of these graphic cards - or is this planed for future?

Thanks

One issue that I may have been hitting is using the Windows Insider program(Dev channel).   If you are not having a problem, then that could be the cause of my issues with 5.6a.

Hello,

I have a rig with a mix of AMD 4x0 and 5x0 cards, and I use ethermine. On the portal he often reports "stale hashes" to me, but on Phoenix Miner I can't understand which GPU can generate them. Is there any way to figure this out without trying one GPU at a time?

Thanks,
Andrea

If you see my MH/s you would know that it is 6800XT.