 Show Posts
|
|
Pages: [1] 2 3 »
|
Compare to Gminer, how many percent can be increased at hashrate?
yes, it's pretty much the same. And with teamred? |
|
|
|
|
Compare to Gminer, how many percent can be increased at hashrate?
|
|
|
|
And we are all waiting for NiceHash to apologize ...  |
|
|
|
|
For my concern, if you noticed my GPU2 is usually running at 31-32MH/s, it seems that in the middle of the mining it crashed and was able to mine at 16-17 MH/s
|
|
|
|
|
id like to know this too.. can someone post some result of their 3080 cards?
|
|
|
|
In any war, both lose. However, PhoenixMiner will lose a large audience from this conflict, unlike NiceHash, because they have a large media resource. What to do? We need to spread good information about PhoenixMiner on blogs, on youtube, in chats. In every way to promote the PhoenixMiner project in media. Because it is the most convenient and fastest miner.NiceHash, obviously, will continue to play dark and throw mud at PhoenixMiner, trying to ruin his reputation so that he will be forgotten. But we will not allow this to be done. We'll win the media war if need be, because Phoenix is so much better, safer, and more reliable than NiceHash  . I have acquaintances in crypto media (websites, twitter, reddit, discrod, youtube). At least for my part, I will tell them the whole situation so that they do not believe in the tales from NiceHash and so that PhoenixMiner does not lose its audience. |
|
|
|
We have added some additional files that were hosted on MEGA previously, as well as some older versions of PhoenixMiner here: https://github.com/PhoenixMinerDevTeam/files/If a lot of people are using even older versions of PhoenixMiner, let us know and we will add them. However we advise against using older versions because most of them won't even work with the current DAG epoch, and we will not offer any support for anything older than the last two releases (5.4c, and 5.5c). Please add more DAG epoch in new version! |
|
|
|
|
NiceHash still hasn't apologized even though they promised.
Will there be an apology?
|
|
|
|
|
I think NiceHash themselves complained about the Mega.nz accounts of Claymore, Phoenix and other closed source programs. And then they blame Phoenix for the link being removed. And they backed it up the next day with a huge fast, accusing Phoenix of all mortal sins. At the same time, they did not forget to advertise their new program.
I think the discussions can be closed. Everyone thinks atk as he wants in the current situation.
Those who are constantly spreading 5.5d on mega here will not be able to blame phoenixminer, because he has a different checksums and has nothing to do with it!
I will only download Phoenix from its GitHub and always watch checksums of the .exe file.
|
|
|
|
Mega blocked all phoenix downloads, could someone reupload the original zipped 5.5c version for windows somewhere (going to crc check anyway) Thanks !! 🙌
+1 Since all other links can't be trusted, I'm waiting for a message of the original author. I'll send him a message. It makes no sense to write in a personal message. Because he has nothing to do with it, but MEGA is to blame. Write directly to MEGA and attach the link.Write: You deleted the file [https://mega.nz/#F!2VskDJrI!lsQsz1CdDe8x5cH3L8QaBw] by mistake. This is a cryptocurrency mining program, not a virus. Please restore it. Thank. support@mega.nzabuse@mega.nzbug@mega.nz |
|
|
|
|
Can I control memory clock and core clocks from the bat files...? I m using rx580 armor oc edition..
|
|
|
|
|
Don't download PhoenixMiner 5.5d - hotfix available from this spam posts! - it's malware!!! there is no such official version. He creates an account over and over and uploads viruses here.
|
|
|
|
PhoenixMiner 5.5c (release candidate) is ready. You can download PhoenixMiner 5.5c from here (both Windows and Linux versions): https://mega.nz/folder/HQ9EyYBD#qIGApl7-ZB1mLq3rjM1XOg (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 Nvidia cards under Windows): File: PhoenixMiner_5.5c_Windows.zip
===================================
SHA-1: 9a3efe6130ba21ab2ade9df38ff9d52a539d9693
SHA-256: 0bb20989cd107c6b65d08da30f014df0b3cb94f8124253e2caee1dfa99431c2d
SHA-512: 2e1aa259f6519d6759ccf679bf1b989c36fe504c9066cc3ba79537bf34129fb168b2956e385a4cf593e45c3a22e89590319870fb502ff13a371932aad441b250
File: PhoenixMiner_5.5c_Linux.tar.gz
====================================
SHA-1: 43bc9221582c8e90188fb1b416df14a8259d5b4e
SHA-256: 66914e1b5011c35cf6af3f0d3e7540f5fa1bbe1563105fd242a67a96437b8e69
SHA-512: 1088fcfd06b1bf63a3ab0d92089504b37e634bc138290c432797594ed25d37f8e5a658cf4124b6bb4495592b2b90f89bf0a68d03f51ce97e61b69efbe0667943
File: PhoenixMiner_NVRTC_Windows.zip
====================================
SHA-1: ff6fa5e018adbd52caf631c42b7c2fac7ce48a51
SHA-256: 8087757169405d51ea8ba818347fb05d0450aef985c29272165070346eb5a54a
SHA-512: 7b2d832f7f40578bb1f501d5174467f5ae06612e601dab769fd56d39da48a471b18c6373435a485155f70fec4017d8378797bf1e1dfe5d62fee30fa6a1d992c4
The changes in this release (since 5.5b) include the following: - Added support for the latest AMD Windows driver 21.1.1 (still, we don't recommend using the 21.1.1 driver yet - we had some instability issues with it even when just idling on the desktop!)
- Added new -mcdag parameter to reset the memory overclock on Nvidia cards during DAG generation. This may allow you to set higher memory overclock on your Nvidia cards without risking corrupt DAG buffer, which can lead to excessive number of incorrect shares. Use -mcdag 1 (by default the value is 0, which means turned off) to use this new feature.
Under Linux -mcdag 1 will execute a shell script named daggen.sh (if present in the current directory) for each Nvidia GPU, passing the GPU index as the first argument, and PCIE bus ID as second argument. The miner will then wait for about 7 seconds before starting DAG generation to allow the script enough time to reset the memory overclock.
- The -tt parameter is now strictly for controlling the fan behavior. E.g. -tt 60 sets auto-fan speed with target temperature 60C; -tt -70 sets fixed fan speed 70%; and -tt 0 turns off the fan control. All these can be specified per GPU.
- There is a new -hwm parameter that allows controlling the frequency of the hardware monitoring, which was also done by -tt in the previous versions of PhoenixMiner
- Other small improvements and fixes
The changes of the previous beta (5.5b) since the last version (5.4c) are: - Added native kernels for AMD RX6800 and RX6900 GPUs. These are faster than the generic kernels and produce a lot less stale shares
- Updated kernels for AMD Polaris, Vega and Navi GPUs that are slightly faster and use less power than before when mining ETH. To use these updated kernels, you need to use drivers 20.5.1 or later under Win10, or 20.10.x or later under Linux
- The Nvidia mining cards (P106, P104, etc.) can now use straps and hardware control options (power limit, memory overclock, max temperature, etc.) under Windows
- Added support for AMD Linux drivers 20.45-1164792 and 20.45-1188099. Use this drivers only if you have RX6800 or RX6900 GPU. WARNING: Vega and Navi GPUs won't work with these drivers!
- Automatically set -ttli instead of -tmax when the later is not supported by the driver. This will throttle down the GPUs when they reach the specified temperature to avoid overheating
Please let us know if you have any problems or questions related to PhoenixMiner 5.4c Should I upgrade if I have an Nvidia 3060 TI? |
|
|
|
The new beta version is ready. You can download PhoenixMiner 5.5b from here: https://mega.nz/folder/jUdTiQhS#vVz_39HlXUK--Leql280iQ (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): File: PhoenixMiner_5.5b_Windows.zip
===================================
SHA-1: 52ac75b2c8d5432aeb88900f034045d2bf023395
SHA-256: 10e022d95514a682d749a593042f02b6f6a8adea112c470c68a3ae7b7b1cb187
SHA-512: 84dbc3df53c38cd0d1956f92c4eb0226341e3230102d0214661bd795455d4995b9ceeb1c19aa98d46b98d710f0790ed1804029899ef9e1b6c85f77696e25e957
File: PhoenixMiner_5.5b_Linux.tar.gz
====================================
SHA-1: d64c126fb31d53ab367288bd69021ffe9d26e974
SHA-256: a870d7c2427e005a502f728ea3d9711a36b126e0a1f91bcfbe5dfb23c5700ed1
SHA-512: b86269cf3985dfbd45779226ff4b15f01ee36dd332af3f4a42396dfa9cdcc0e012172c622f55f16b9a49c5d8e5aff0d757b95ae7d8fc58fd322e6c2b758d007d
File: PhoenixMiner_NVRTC_Windows.zip
====================================
SHA-1: ff6fa5e018adbd52caf631c42b7c2fac7ce48a51
SHA-256: 8087757169405d51ea8ba818347fb05d0450aef985c29272165070346eb5a54a
SHA-512: 7b2d832f7f40578bb1f501d5174467f5ae06612e601dab769fd56d39da48a471b18c6373435a485155f70fec4017d8378797bf1e1dfe5d62fee30fa6a1d992c4
The new features in this release are: - Added native kernels for AMD RX6800 and RX6900 GPUs. These are faster than the generic kernels and produce a lot less stale shares
- Updated kernels for AMD Polaris, Vega and Navi GPUs that are slightly faster and use less power than before when mining ETH. To use these updated kernels, you need to use drivers 20.5.1 or later under Win10, or 20.10.x or later under Linux
- The Nvidia mining cards (P106, P104, etc.) can now use straps and hardware control options (power limit, memory overclock, max temperature, etc.) under Windows
- Added support for AMD Linux drivers 20.45-1164792 and 20.45-1188099. Use this drivers only if you have RX6800 or RX6900 GPU. WARNING: Vega and Navi GPUs wont' work with these drivers!
- Automatically set -ttli instead of -tmax when the later is not supported by the driver. This will throttle down the GPUs when they reach the specified temperature to avoid overheating
If you have RX6800 or RX6900 card, do not use the PhoenixMiner hardware control options (-cclock, -mclock, etc.) because there is yet another undocumented change in OverDrive and some of them will work, but some won't with weird results - we will implement them properly in the next version. Instead use the AMD control panel to set the card parameters. Good starting point are the following options: core clock 1500 MHz, mem clock 2050 MHz, core voltage 800 mV, set faster memory timings, and a custom fan curve to keep the temperature below 65-66 C. Please let us know if you have any problems or questions related to PhoenixMiner 5.5b. This version looks stable |
|
|
|
The new beta version is ready. You can download PhoenixMiner 5.5b from here: https://mega.nz/folder/jUdTiQhS#vVz_39HlXUK--Leql280iQ (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): File: PhoenixMiner_5.5b_Windows.zip
===================================
SHA-1: 52ac75b2c8d5432aeb88900f034045d2bf023395
SHA-256: 10e022d95514a682d749a593042f02b6f6a8adea112c470c68a3ae7b7b1cb187
SHA-512: 84dbc3df53c38cd0d1956f92c4eb0226341e3230102d0214661bd795455d4995b9ceeb1c19aa98d46b98d710f0790ed1804029899ef9e1b6c85f77696e25e957
File: PhoenixMiner_5.5b_Linux.tar.gz
====================================
SHA-1: d64c126fb31d53ab367288bd69021ffe9d26e974
SHA-256: a870d7c2427e005a502f728ea3d9711a36b126e0a1f91bcfbe5dfb23c5700ed1
SHA-512: b86269cf3985dfbd45779226ff4b15f01ee36dd332af3f4a42396dfa9cdcc0e012172c622f55f16b9a49c5d8e5aff0d757b95ae7d8fc58fd322e6c2b758d007d
File: PhoenixMiner_NVRTC_Windows.zip
====================================
SHA-1: ff6fa5e018adbd52caf631c42b7c2fac7ce48a51
SHA-256: 8087757169405d51ea8ba818347fb05d0450aef985c29272165070346eb5a54a
SHA-512: 7b2d832f7f40578bb1f501d5174467f5ae06612e601dab769fd56d39da48a471b18c6373435a485155f70fec4017d8378797bf1e1dfe5d62fee30fa6a1d992c4
The new features in this release are: - Added native kernels for AMD RX6800 and RX6900 GPUs. These are faster than the generic kernels and produce a lot less stale shares
- Updated kernels for AMD Polaris, Vega and Navi GPUs that are slightly faster and use less power than before when mining ETH. To use these updated kernels, you need to use drivers 20.5.1 or later under Win10, or 20.10.x or later under Linux
- The Nvidia mining cards (P106, P104, etc.) can now use straps and hardware control options (power limit, memory overclock, max temperature, etc.) under Windows
- Added support for AMD Linux drivers 20.45-1164792 and 20.45-1188099. Use this drivers only if you have RX6800 or RX6900 GPU. WARNING: Vega and Navi GPUs wont' work with these drivers!
- Automatically set -ttli instead of -tmax when the later is not supported by the driver. This will throttle down the GPUs when they reach the specified temperature to avoid overheating
If you have RX6800 or RX6900 card, do not use the PhoenixMiner hardware control options (-cclock, -mclock, etc.) because there is yet another undocumented change in OverDrive and some of them will work, but some won't with weird results - we will implement them properly in the next version. Instead use the AMD control panel to set the card parameters. Good starting point are the following options: core clock 1500 MHz, mem clock 2050 MHz, core voltage 800 mV, set faster memory timings, and a custom fan curve to keep the temperature below 65-66 C. Please let us know if you have any problems or questions related to PhoenixMiner 5.5b. 5.5b works stably on my old RX 580 |
|
|
|
GPU6: Generating DAG for epoch #387
Eth: New job #06735b75 from asia.ethash-hub.miningpoolhub.com:20535; diff: 8589MH
GPU2: DAG 65%
GPU5: DAG 21%
GPU4: DAG 42%
GPU7: Free VRAM: 7.948 GB; used: 0.052 GB
GPU7: Disabling DAG pre-allocation (not enough VRAM)
GPU7: Allocating DAG for epoch #387 (4.02) GB
GPU7: Generating DAG for epoch #387
GPU3: DAG 63%
GPU2: DAG 81%
GPU6: DAG 21%
Eth: New job #7cc46469 from asia.ethash-hub.miningpoolhub.com:20535; diff: 8589MH
GPU5: DAG 41%
GPU1: Free VRAM: 7.948 GB; used: 0.052 GB
GPU1: Disabling DAG pre-allocation (not enough VRAM)
GPU1: Allocating DAG for epoch #387 (4.02) GB
GPU1: Generating DAG for epoch #387
Eth: New job #a67920b6 from asia.ethash-hub.miningpoolhub.com:20535; diff: 8589MH
GPU4: DAG 63%
GPU3: DAG 80%
GPU7: DAG 21%
GPU2: DAG generated in 8.0 s (515.6 MB/s)
GPU2: Using Ethash OCL kernels (Ellesmere; -clkernel 1 -clnew 0)
GPU2: clSetKernelArg (-48)
Fatal error detected. Restarting.
Eth: New job #7482ee9b from asia.ethash-hub.miningpoolhub.com:20535; diff: 8589MH
Eth: New job #9bc3aa8e from asia.ethash-hub.miningpoolhub.com:20535; diff: 8589MH
Eth: New job #b84dedd8 from asia.ethash-hub.miningpoolhub.com:20535; diff: 8589MH
I have that problem, virtual memory in 40.000.
Try to add -gser 2 SAME BRO, same problem you need to find the optimal value for the -gser command for your gpus. Example: PhoenixMiner.exe -pool eth-eu2.nanopool.org:9999 -wal wallet.rig -gser 2 or Perhaps your drivers have been automatically updated. You need to roll back the drivers to the version on which the program works stably. In config.txt add: -rvram -1 And add more virtual memory in windows 16 to 32Go, Me for 6 * RX580 i have 65635Mo virtual memory for no problem Same but i saw this: GPU4: DAG 22% Eth: New job #4b0e9be5 from asia.ethash-hub.miningpoolhub.com:20535; diff: 8589MH GPU3: DAG 65% GPU2: DAG generated in 8.0 s (517.9 MB/s) GPU2: Using Ethash OCL kernels (Ellesmere; -clkernel 1 -clnew 0) GPU2: clSetKernelArg (-48)
Fatal error detected. Restarting.Eth speed: 0.000 MH/s, shares: 0/0/0, time: 0:00 GPUs: 1: 0.000 MH/s (0) 2: 0.000 MH/s (0) 3: 0.000 MH/s (0) 4: 0.000 MH/s (0) 5: 0.000 MH/s (0) 6: 0.000 MH/s (0) 7: 0.000 MH/s (0) GPU5: Free VRAM: 7.948 GB; used: 0.052 GB try to add this: PhoenixMiner.exe -pool eth-eu2.nanopool.org:9999 -wal wallet.rx580 -gser 10 -rvram -1 |
|
|
|
GPU6: Generating DAG for epoch #387
Eth: New job #06735b75 from asia.ethash-hub.miningpoolhub.com:20535; diff: 8589MH
GPU2: DAG 65%
GPU5: DAG 21%
GPU4: DAG 42%
GPU7: Free VRAM: 7.948 GB; used: 0.052 GB
GPU7: Disabling DAG pre-allocation (not enough VRAM)
GPU7: Allocating DAG for epoch #387 (4.02) GB
GPU7: Generating DAG for epoch #387
GPU3: DAG 63%
GPU2: DAG 81%
GPU6: DAG 21%
Eth: New job #7cc46469 from asia.ethash-hub.miningpoolhub.com:20535; diff: 8589MH
GPU5: DAG 41%
GPU1: Free VRAM: 7.948 GB; used: 0.052 GB
GPU1: Disabling DAG pre-allocation (not enough VRAM)
GPU1: Allocating DAG for epoch #387 (4.02) GB
GPU1: Generating DAG for epoch #387
Eth: New job #a67920b6 from asia.ethash-hub.miningpoolhub.com:20535; diff: 8589MH
GPU4: DAG 63%
GPU3: DAG 80%
GPU7: DAG 21%
GPU2: DAG generated in 8.0 s (515.6 MB/s)
GPU2: Using Ethash OCL kernels (Ellesmere; -clkernel 1 -clnew 0)
GPU2: clSetKernelArg (-48)
Fatal error detected. Restarting.
Eth: New job #7482ee9b from asia.ethash-hub.miningpoolhub.com:20535; diff: 8589MH
Eth: New job #9bc3aa8e from asia.ethash-hub.miningpoolhub.com:20535; diff: 8589MH
Eth: New job #b84dedd8 from asia.ethash-hub.miningpoolhub.com:20535; diff: 8589MH
I have that problem, virtual memory in 40.000.
Try to add -gser 2 SAME BRO, same problem you need to find the optimal value for the -gser command for your gpus. Example: PhoenixMiner.exe -pool eth-eu2.nanopool.org:9999 -wal wallet.rig -gser 2 or Perhaps your drivers have been automatically updated. You need to roll back the drivers to the version on which the program works stably. |
|
|
|
anyone tried to compare hashrate on GTX 1080 vs claymore?
About the same. |
|
|
|
How much increment in hashrate people getting with current version for other cards?
Almost not. |
|
|
|
GPU1: Free VRAM: 7.948 GB; used: 0.052 GB
GPU1: Disabling DAG pre-allocation (not enough VRAM)
GPU1: Allocating DAG for epoch #382 (3.98) GB
GPU1: Generating DAG for epoch #382
error=Disabling DAG pre-allocation (not enough VRAM)
in 7xRx-580 8Gb
You can try adding -eres 0 -rvram -1 |
|
|
|
|
