The new beta version is ready. You can download PhoenixMiner 5.0b from here: (MEGA links are no longer active) 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.0b_Windows.zip
===================================
SHA-1: 7937a895451c1162716fbf31d5b44567faae6dc5
SHA-256: 9156041628e8498857a74d4035377ad1032533f7c4601445f274c62687bf920b
SHA-512: 0c7329611e1f54af263dd3e426ae808c3081127b17cccfe04ad693ee42caad72b04bb5d89a7708e726e1b227d835a11c70d23decd9b485bb721f38d70d198cc7
File: PhoenixMiner_5.0b_Linux.tar.gz
====================================
SHA-1: 121e9d14547fcf97613805c88782d76d74ccb43a
SHA-256: ced7789d213d729d0efd1a295462549415cd8254091dfbcdbc720aaf13684bbe
SHA-512: 6f115a54101b2f3a95638f7c5ddccf5ae77bd6493f8312c0a81dc58885645f6e56973e9654426bce926605a24218da10fea4c69cf22afb8017fc95061ff5cde9
File: PhoenixMiner_NVRTC_Windows.zip
====================================
SHA-1: ff6fa5e018adbd52caf631c42b7c2fac7ce48a51
SHA-256: 8087757169405d51ea8ba818347fb05d0450aef985c29272165070346eb5a54a
SHA-512: 7b2d832f7f40578bb1f501d5174467f5ae06612e601dab769fd56d39da48a471b18c6373435a485155f70fec4017d8378797bf1e1dfe5d62fee30fa6a1d992c4
The new features in this release are: - Added support for mining with 4 GB AMD cards beyond the DAG epoch 350. Depending on the OS and driver versions, you will be able to use 4 GB AMD cards until epoch 372-373 under Windows, and 380 under Linux.
- Added new -dagrestart command-line option to work around the problems with DAG allocation on 4 GB AMD cards under some driver versions. See Readme.txt for more information.
- Added support for latest AMD drivers 20.4.2 under Windows and 20.10-1048554 under Linux
- Many other small improvements and fixes
Please let us know if you have any problems or questions related to PhoenixMiner 5.0b. |
|
|
|
PhoenixMiner, any chance for miner update to support newest AMD drivers?
Yes, certainly the new version will support the latest drivers. However we have found some issues with the latest Linux drivers so it is not recommended to change the driver version unless you are unhappy with the older driver (e.g. the hardware control doesn't work, etc.). In terms of hash-rate there isn't significant difference between the drivers with rare exceptions. Hi Phoenix,
Im from ClayMore´s miner and want to test the phoenix miner. Smiley
In CM i got 52 MH/s for an vega 64. (155 W on SW miner) and probably 200 from wall.
Here in my tests , using auto-tune or manual or intensity 15 i only got 44 mh/S , if increase intensity to 400 i got 32mh/S
I tested several kernels too, could be my amd drivers : Radeon-Software-Adrenalin-2019-19.5.2 ?
Its a Strange behavior.
Any ideia where should i look?
Thanks
Most probably you are using some options to change the timings and refresh rates of the VRAM, which aren't supported on PhoenixMiner. For similar things, you may use a third-party tool like AMD Memory Tweak tool: https://github.com/Eliovp/amdmemorytweak (note: we are not affiliated with the author(s) of this tool in any way) |
|
|
|
|
Hello again, everybody! We hope you are doing well (as well as possible in these circumstances anyway).
Here are some important updates about PhoenixMiner and the upcoming events:
* All users of 4 GB cards should add the following command line options: -rvram -1 -eres 0 This will allow uninterrupted operation until the next VRAM limit hits, which will be around epoch 350-352 for AMD cards and a bit later for Nvidia cards.
* We are working on a fix for the AMD cards with 4 GB VRAM, which will allow them to work a bit longer after epoch 350, and it will be ready in the next few weeks (certainly before epoch 350 hits), so don't lose hope if you have 4 GB AMD cards yet.
* Do not upgrade to the latest AMD drivers (20.4.x on Windows, or 20.10-1048554 on Linux) as they are not supported by the current PhoenixMiner 4.9c and you will get lower hashrate and higher stale shares as a result.
|
|
|
|
OK, here are some results from one of our test rigs that runs 24/7: - PhoenixMiner 4.9c, Windows 10, Nvidia driver 397.64, common parameters for all cards: -mi 14 -tt 63 -fanmin 20 -fanmax 50 -tmax 66
- 1070: -mclock +440 (4248 MHz final mem clock)
- 1070 Ti: -mclock +440 (4248 MHz final mem clock)
- 1080 Ti: -mclock +756 (5872 MHz final memclock), also using the ETH "pill"
We use power limit in order to optimize the power consumption as using -cclock for Nvidia cards is inferior (doesn't lower the core voltage enough, resulting in higher power consumption than necessary for give clock speed). First, here are the results (both hashrate and the reported power usage) with lower power limit (i.e. with optimized power consumption): | Card | ETH (epoch 310) | ETC (epoch 321) | | 1070 (-powlim -50) | 28.54 (99 W) | 27.93 (99 W) | | 1070 Ti (-powlim -45) | 30.48 (99 W) | 30.48 (99 W) | | 1080 Ti (-powlim -25) | 48.44 (185 W) | 46.42 (188 W) |
Next, we increase the power limits to offset the hashrate drop of the cards with the increase of the DAG size (note that depending on your power cost, maximizing the hashrate regardless of the power consumption may be a losing strategy): | Card | ETH (epoch 310) | ETC (epoch 321) | | 1070 (-powlim -30) | 30.36 (132 W) | 30.36 (132 W) | | 1070 Ti (-powlim -25) | 30.52 (135 W) | 30.52 (135 w) | | 1080 Ti (-powlim -5) | 54.63 (241 W) | 52.01 (238 W) |
As you can see there is hashrate drop with the increase of the DAG size but it is nowhere as dramatic as 50% for ETC. Additionally, with 1070Ti the drop is almost non-existing, so there is definitely something wrong with your setup. We suggest adding the -hstats 2 parameter to see the actual clocks and power consumption, the reason for power cap (pcap) if any, and so on. |
|
|
|
About the AMD Linux drivers 19.50-967956:
These drivers fix the hardware control issues from the previous Linux drivers and support RX5500. However, they reintroduce the Navi TLB problem and the hashrates are about 10-14 MH/s, so you are better off with the previous Linux drivers for Navi cards (or use Windows).
They seem to forgot adding this in 19.50, here is how to fix the problem on Ubuntu or other debian: ... Enjoy mining with newest driver  Nice find! Thank you very much for this information! We have put together the patched files from the driver and here are the slightly easier installation instructions for the patched driver: 1. If you have installed the unpatched driver or any other AMD driver, uninstall it first: and then reboot the rig. 2. Download the driver from AMD web site (it will be named amdgpu-pro-19.50-967956-ubuntu-18.04.tar.xz) 3. Download the patch from here: https://github.com/PhoenixMinerDevTeam/files/blob/main/amdgpu-pro-19.50-967956-patch.tar.gz?raw=true (the file name is amdgpu-pro-19.50-967956-patch.tar.gz) 4. To verify the downloaded patch file, you can use the following checksums: SHA-1: 1f8ca89e98f9cb625ae9ad6194a012a642f4b39d
SHA-256: c969e326971acbaef9a3e20d0aa2459f70ac5b6cd5cbde79614289c99051a9aa
SHA-512: e96652ffac48375b97b756bed02296180ef92a07f9b407db66bf003c58d805e80f15e9c9a2525e2706b0de7e4391e732ae6800adf90c9730fb25546581a1a6a5 Place both files in the same folder and first extract the files of the driver with the following command: tar -Jxvf amdgpu-pro-19.50-967956-ubuntu-18.04.tar.xz Then extract the patched files, which will overwrite some files in the extracted driver: tar -zxvf amdgpu-pro-19.50-967956-patch.tar.gz Finally, go to the extracted driver folder and start the installation with the following commands: cd amdgpu-pro-19.50-967956-ubuntu-18.04
./amdgpu-pro-install -y --opencl=pal,legacy --headless Hi,
The average share difficulty for dev mining is 5 Mhs but regular share difficulty is 20 Ghs . Why such a huge difference ?
The share difficulty is determined by the pool. When the pool used for devfee is different than your pool, the difficulty can also be different. |
|
|
|
Does anyone have a list of the pools that Pheonix uses for its dev fees? I just switched from Claymore to Pheonix and I have firewall rules that block all egress traffic from mining rigs except to certain sites. Claymore was consistent in its preferred pool, Pheonix seems to be a lot of different ones.
Basically we try to use the same pool for devfee as the pool that you are mining on (if it is one of the top 3-4 ones), otherwise it is ethermine or some of the other big pools. |
|
|
|
PhoenixMiner 4.9c is officially released. You can find the download link and the checksums in the first post of this thread. The new features in this release are: - Adding option -rate 2 to use the command name "eth_submitHashRate" instead of "eth_submitHashrate" when solo mining
- Adding support for AMD Linux drivers 19.50-967956
- Other small fixes and improvements
Here are the other features from 4.9b: - Added support for AMD RX5500 cards
- Added support for the latest AMD Windows drivers 19.12.3
- Fixed the problem with loading NVML library with the latest Nvidia drivers
- Fixed a problem that was introduced in 4.8c causing mismatching of the cards when using more than one value in -cclock or any other command-line argument with more than one value (i.e. when using different values for each card)
- Added an HTML version of the documentation for better navigation and readability
About the AMD Linux drivers 19.50-967956:These drivers fix the hardware control issues from the previous Linux drivers and support RX5500. However, they reintroduce the Navi TLB problem and the hashrates are about 10-14 MH/s, so you are better off with the previous Linux drivers for Navi cards (or use Windows).
|
|
|
|
The new beta version is ready. You can download PhoenixMiner 4.9b from here: (MEGA links are no longer active) 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_4.9b_Windows.zip
===================================
SHA-1: 4b8f002bfed687938580a60354ee74ba2b9ed97a
SHA-256: 5ab17ce168d2da17ad49e8cd9a0263abdfc5e9412079458026f1dede64fb15c1
SHA-512: 71d9cf2a65d378900bbb616895f4f4cede8da8fa8ae19352491f82e82e27e9e079e7c879789afb833db2b588527f391acc725d74a638f8b91b9356e0d48add8a
File: PhoenixMiner_4.9b_Linux.tar.gz
====================================
SHA-1: d8dd717c554227da8834880b8d9a93b4e589b8b0
SHA-256: e357ed9fc56e13f627d5a576fff7b6c84d0790a7ce85a1ac6dd2022e30dd5c15
SHA-512: 8829b3d65818a016fa42f57e09d22a7aa26cc50e287f28837ea9cde59626f70f3dcdf9b641744053259e12fc6132e98553b092cf80f676cf329996adce3c6b10
File: PhoenixMiner_NVRTC_Windows.zip
====================================
SHA-1: ff6fa5e018adbd52caf631c42b7c2fac7ce48a51
SHA-256: 8087757169405d51ea8ba818347fb05d0450aef985c29272165070346eb5a54a
SHA-512: 7b2d832f7f40578bb1f501d5174467f5ae06612e601dab769fd56d39da48a471b18c6373435a485155f70fec4017d8378797bf1e1dfe5d62fee30fa6a1d992c4
The new features in this release are: - Added support for AMD RX5500 cards
- Added support for the latest AMD Windows drivers 19.12.3
- Fixed the problem with loading NVML library with the latest Nvidia drivers
- Fixed a problem that was introduced in 4.8c causing mismatching of the cards when using more than one value in -cclock or any other command-line argument with more than one value (i.e. when using different values for each card)
- Added an HTML version of the documentation for better navigation and readability
Please let us know if you have any problems or questions related to PhoenixMiner 4.9b. |
|
|
|
PhoenixMiner 4.8c is officially released. You can find the download link and the checksums in the first post of this thread. The new features in this release are: - Added command-line option -gbase to set 0-base or 1-based GPU indexes (the default is 1). With -gbase 1 (the default), the first GPU is GPU1, then GPU2, etc. With -gbase 0 the first GPU is GPU0, second - GPU1, etc. Note that this also changes the indexes that are used with all command line options that accept GPU indexes (e.g. -gpus) as well as these used with the interactive commands on the miner shell window
Here are the other features from 4.8b: - Added support for the latest AMD drivers under Linux 19.30-934563 and for mining with RX5700 cards under Linux. Note that drivers are quite buggy and most of the overclocking options don't work, as well as most of the hardware monitoring options.
- Added a new flexible way for setting GPU-specific options with selectors. Example: -cclock 1-3:1090,4:1300 -mclock nvidia:+450,amd:2000,*:1900,gtx*1070*ti:+200 See bellow for more information
- Validated support for the latest AMD Windows drivers 19.11.3 (but they already work with 4.7c because there were no significant changes in the OpenCL driver)
About the AMD Linux drivers 19.30-934563:These drivers finally fix the RX5700 TLB problem but they are not perfect: - Most of the hardware monitoring options don't work for RX5700 cards - even the temperature is not reported correctly. Only the power usage, fan speed, and core voltage are reported. - Almost all hardware control options don't work for RX5700 cards either with the notable exception of power limit, so the only way to avoid wasting power is to use -powlim -45 or something like this. The fan control options doesn't work either so you will be relying on auto-fan. About the new selectors for the GPU-specific options:This is best explained by example: -cclock *:1100,1-3:1090,4:1300 - here we are setting core clock to 1100 MHz for all cards, except the cards 1 to 3, on which it is set to 1090 MHz, and card 4 to 1300 MHz. The part before the colon : is the selector, which selects the GPUs for which the value after the colon is applied. The selector can be: - single GPU index: e.g. 5:1000 sets 1000 for the 5th GPU - range of GPU indexes: e.g 2-5:1200 sets 1200 for the GPUs 2,3,4, and 5 - asterisk, which sets the value for all GPUs - label amd or nvidia: e.g. amd:1090 sets the value to 1090 for all AMD cards - arbitrary string that starts with letter and can contain letters, numbers and asterisks, which is matched against the GPU name as listed by PhoenixMiner. Example: gtx*1070:+500 will set value +500 for all cards which contain ' gtx' and ' 1070' in their names with anything between them. This will match ' Nvidia GeForce GTX 1070' but not ' Nvidia GeForce 1070'. Note that if more than one selector matches given card, than only the last one counts. Example: -cclock *:1100,1-4:1090,2:1300 will set card 2 to 1300; cards 1,2, and 4 to 1090; and the rest of the cards to 1100 MHz core clock.
|
|
|
|
Having issue after windows update, miner can no longer restart itself when thread crash or manual restart time. Miner shows restarting waiting 15s but after 15s CMD closes. I also have had random CMD closure after a few days or sometimes less than 12hours of running.
Anyone with the same issues? Or know a fix ? (its getting annoying waking up or coming home to find no errors messages in windows or in the miner log, but the program had just turned off and will not restart.) This seems like Windows Defender issue. Turn off Windows Defender completely (it can be done with gpedit.msc) and see if the issues go away. Dear developers. Do you know why every month the ETH hashrate decreases a bit on 1070-1080Ti video cards? About 2-3 MX per year. On AMD cards and on 1066 - this does not happen, everything is ok there. Thank you in advance!
I also wants to know answer this question. In the first half of this year my 6 1070 have 192Mh. Now they have 183.8Mh. Moreover I decreased MC, because with MC I used before, hashrate is even less. But there is nothing incorrect shares, so looks like hardware works good. This is a long-standing problem with Nvidia 10x0 cards. As it started above certain size of DAG and gradually lowers the hashrate with each new epoch, it seems to be related to the TLB size (yes, TLB strikes again). At this point the only workaround is to increase the power limit (and thus indirectly the core clock) but whether it is worth it depends on your electricity prices. We are testing some theoretical fixes for this problem but the results are not very encouraging. Nvidia could probably fix this with driver update by increasing the page size as AMD did in the past but it is not very likely that they will bother to do it. |
|
|
|
After AMD finally released Linux driver which can be used for Ethash mining with RX5700 cards, the release candidate of 4.8 is ready for download. You can download PhoenixMiner 4.8b from here: (MEGA links are no longer active) 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_4.8b_Windows.zip
===================================
SHA-1: 0064bd0a2523c623f8b7ffd20105a2a901422479
SHA-256: 90f57b65b1f92ae2ef712a2d17b90f1dfdc45db6b6d01b17d7f52fd8106eaf89
SHA-512: 5fdbc109dbf7cb8a6cc51ee75b2139083c90fd1cb51116e4687a896aad2274c42f37b68ca1cd46ac60c885e43c82dfaa5f9823b1588ae55874b17030c73de875
File: PhoenixMiner_4.8b_Linux.tar.gz
====================================
SHA-1: 95aa2754d6a0ed933d42b0380d4b5be076a64298
SHA-256: 1f235d022699acba1470e1f8af5950ff62cae7ac96bdb4eb794af9848e7dae24
SHA-512: df29e3dfff5476fc29823f57725462c8bd021742d7f24e58688e245cdff2e146620cc44b983de1f14b720a6102b50c52c07869854eca4c93e3121cda360bc1fc
File: PhoenixMiner_NVRTC_Windows.zip
====================================
SHA-1: ff6fa5e018adbd52caf631c42b7c2fac7ce48a51
SHA-256: 8087757169405d51ea8ba818347fb05d0450aef985c29272165070346eb5a54a
SHA-512: 7b2d832f7f40578bb1f501d5174467f5ae06612e601dab769fd56d39da48a471b18c6373435a485155f70fec4017d8378797bf1e1dfe5d62fee30fa6a1d992c4
The new features in this release are: - Added support for the latest AMD drivers under Linux 19.30-934563 and for mining with RX5700 cards under Linux. Note that drivers are quite buggy and most of the overclocking options don't work, as well as most of the hardware monitoring options.
- Added a new flexible way for setting GPU-specific options with selectors. Example: -cclock 1-3:1090,4:1300 -mclock nvidia:+450,amd:2000,*:1900,gtx*1070*ti:+200 See bellow for more information
- Validated support for the latest AMD Windows drivers 19.11.1 (but they already work with 4.7c because there were no significant changes in the OpenCL driver)
- Other small improvements and fixes.
If you don't need or want any of these features, there is no need to upgrade yet. About the AMD Linux drivers 19.30-934563:These drivers finally fix the RX5700 TLB problem but they are not perfect: - Most of the hardware monitoring options don't work for RX5700 cards - even the temperature is not reported correctly. Only the power usage, fan speed, and core voltage are reported. - Almost all hardware control options don't work for RX5700 cards either with the notable exception of power limit, so the only way to avoid wasting power is to use -powlim -45 or something like this. The fan control options doesn't work either so you will be relying on auto-fan. About the new selectors for the GPU-specific options:This is best explained by example: -cclock *:1100,1-3:1090,4:1300 - here we are setting core clock to 1100 MHz for all cards, except the cards 1 to 3, on which it is set to 1090 MHz, and card 4 to 1300 MHz. The part before the colon : is the selector, which selects the GPUs for which the value after the colon is applied. The selector can be: - single GPU index: e.g. 5:1000 sets 1000 for the 5th GPU - range of GPU indexes: e.g 2-5:1200 sets 1200 for the GPUs 2,3,4, and 5 - asterisk, which sets the value for all GPUs - label amd or nvidia: e.g. amd:1090 sets the value to 1090 for all AMD cards - arbitrary string that starts with letter and can contain letters, numbers and asterisks, which is matched against the GPU name as listed by PhoenixMiner. Example: gtx*1070:+500 will set value +500 for all cards which contain ' gtx' and ' 1070' in their names with anything between them. This will match ' Nvidia GeForce GTX 1070' but not ' Nvidia GeForce 1070'. Note that if more than one selector matches given card, than only the last one counts. Example: -cclock *:1100,1-4:1090,2:1300 will set card 2 to 1300; cards 1,2, and 4 to 1090; and the rest of the cards to 1100 MHz core clock. |
|
|
|
Reject all progpow shares on rx584 at zergpool. (rx562 work fine)
...
We tested with similar card (RX580 4 GB) on the same pool without any problems. 100% incorrect shares usually indicate that there was an error during the DAG creation, so probably the memory is too overclocked or undervolted. Exit on run at 1080ti
Nvidia cards require several additional files in order to work with ProgPow. These files are in the file file PhoenixMiner_NVRTC_Windows.zip, which you can download from the same folder as PhoenixMiner. Then, you need to extract the files from PhoenixMiner_NVRTC_Windows.zip and put them in the same folder as PhoenixMiner.exe. |
|
|
|
PhoenixMiner 4.7c is the new stable varsion (see the first post for details). You can download PhoenixMiner 4.7c from here: (MEGA links are no longer active) 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_4.7c_Windows.zip
===================================
SHA-1: 444b9bca05692f51cfaf8100c91a2bd6adbb5055
SHA-256: 9a4bd6eba5614f754d5ec5ae78558c4928b502136dccf47702f3df54c0027883
SHA-512: 4bdfedd21d09b8e59cc91a09661fb47ff2ed6b01ad0128185900d427bf96e7035d64d363ca9e11fe70371622f912af96b2f1b253e12f7d2dad4f6163d2caec4f
File: PhoenixMiner_4.7c_Linux.tar.gz
====================================
SHA-1: 56ab80ae3ce1843ba842e837f10d3e0f894539ff
SHA-256: 184e31bf92cd84a5062fa60cf2d2a7db17433681df7d60500f3b70189a79f38d
SHA-512: 04521956dbdccd3dedf8e7d27b0fde0d59bfc92222d8063bced0ac5b67d6c858f3343637f8e45fa3bb483910e3f49cf2fad00c775d5a7923e3519e76b8ac93cf
File: PhoenixMiner_NVRTC_Windows.zip
====================================
SHA-1: ff6fa5e018adbd52caf631c42b7c2fac7ce48a51
SHA-256: 8087757169405d51ea8ba818347fb05d0450aef985c29272165070346eb5a54a
SHA-512: 7b2d832f7f40578bb1f501d5174467f5ae06612e601dab769fd56d39da48a471b18c6373435a485155f70fec4017d8378797bf1e1dfe5d62fee30fa6a1d992c4
The changes since the 4.7b beta version are another small change in Navi kernels and other small improvements. Changes in version 4.7c (since 4.6c):- New kernels for Navi (RX5700) with better stability. Should solve the freezing and restarts that some miners are experiencing with Navi cards
- Reduced VRAM usage for both AMD and Nvidia cards on Windows and Linux
- Added command-line option -config to load a config.txt file. This allows combining command-line options and config.txt file.
- Added support for mining QuarkChain (QKC) without DAG switching on devfee (use -coin qkc)
- Added support for the latest AMD Windows drivers up to 19.10.1
- Other small improvements and fixes.
When using the new -config option, please note the following: - The order of the options is important. For example, if we have a config.txt file that contains -cclock 1000 and we specify command line -cclock 1100 -config config.txt, the option from the config.txt file will take precedence and the resulting -cclock will be 1000. If the order is reversed (-config config.txt -cclock 1100) then the second option takes precedence and the resulting -cclock will be 1100.
- Only one -config option is allowed
- If you reload the config file with 'c' key or with the remote interface, its options will take precedence over whatever you have specified in the command-line.
|
|
|
|
Does Phoenixminer suppport AMD RX5700 (NAVI) under Linux?
Yes, but we haven't released our optimized kernels yet, as AMD Linux drivers are still not usable for ETH mining with Navi. The TLB problem was fixed on Windows with 19.9.1 but it is still present on Linux with the latest drivers. Hopefully AMD will release fixed Linux drivers soon. |
|
|
|
The release candidate of 4.7 is ready for download. You can download PhoenixMiner 4.7b from here: (MEGA links are no longer active) 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_4.7b_Windows.zip
===================================
SHA-1: 6168de64ca680b824fb3f63d2cebd30ee22dc0f2
SHA-256: c7aeb33c3d7a2354da0bb006c6280083239aa79e002185a5e3947811abbe6858
SHA-512: e00f6061cdcf2b20fe15937b9a146bc90bd8c8e653432271e9ada49b3c43970ae8ca0b0fbf275707f01fb13f4b0786bb7bfcaadbcf7d864d733745d2ae82cc19
File: PhoenixMiner_4.7b_Linux.tar.gz
====================================
SHA-1: 0f9e127ba6fab8d62049f45a8799d9b8b9e1da2e
SHA-256: 7e8359ce6322d6001b4f45be4959692d6e83a69b45882e6938f91cd782bf08ed
SHA-512: bc8a47249afa4220e19059c0e3319a268b521fdbfe5b67d4f80a7c64843b1174a0aa13a4cc1a275246e7dec2daed10d236ef7f13d4e9d0cbe9b4aad4be59142c
File: PhoenixMiner_NVRTC_Windows.zip
====================================
SHA-1: ff6fa5e018adbd52caf631c42b7c2fac7ce48a51
SHA-256: 8087757169405d51ea8ba818347fb05d0450aef985c29272165070346eb5a54a
SHA-512: 7b2d832f7f40578bb1f501d5174467f5ae06612e601dab769fd56d39da48a471b18c6373435a485155f70fec4017d8378797bf1e1dfe5d62fee30fa6a1d992c4
Here are the new features for this release: - New kernels for Navi (RX5700) with better stability. Should solve the freezing and restarts that some miners are experiencing with Navi cards
- Reduced VRAM usage for both AMD and Nvidia cards on Windows and Linux
- Added command-line option -config to load a config.txt file. This allows combining command-line options and config.txt file.
- Added support for mining QuarkChain (QKC) without DAG switching on devfee (use -coin qkc)
- Added support for the latest AMD Windows drivers 19.9.3
- Other small improvements and fixes.
When using the new -config option, please note the following: - The order of the options is important. For example, if we have a config.txt file that contains -cclock 1000 and we specify command line -cclock 1100 -config config.txt, the option from the config.txt file will take precedence and the resulting -cclock will be 1000. If the order is reversed (-config config.txt -cclock 1100) then the second option takes precedence and the resulting -cclock will be 1100.
- Only one -config option is allowed
- If you reload the config file with 'c' key or with the remote interface, its options will take precedence over whatever you have specified in the command-line.
|
|
|
|
Here are some notes about the Windows 10 out of memory problems: - While they are present both on AMD and Nvidia GPUs, the problem with Nvidia is much worse. The 4 GB AMD GPUs will work without problems under Windows 10 at least until DAG 350, while the best that can be expected from Nvidia is DAG 293. And this is not entirely Windows 10 fault because even under Linux the 1050Ti won't be able to go beyond DAG 340 or a little higher.
- The first thing to do after encountering out of memory error is 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.
- Again, there is no point to upgrade to PhoenixMiner 4.7a if you don't have 4 GB Nvidia cards and there are no out of memory problems
|
|
|
|
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: (MEGA links are no longer active) 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_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. |
|
|
|
hi,
if i use at least one command line parameter, it completely ignores the config.txt
so i cant use both options together? i have to choose either config or command line ?
Currently there can be only one config.txt file (or command-line options). We will probably add ability to use both config.txt file and command-line options in the next release, as it can be useful in some cases. I own now 2x Sapphire 5700XT. I have used Adrenaline 1.9.2.2 and classic setting posted on this topic; -tt 62 -cclock 1300 -cvddc 800 -mclock 900 -hstats 2 it gives 52,x MH but it fails in minutes. I have tried lower or bigger -cvvdc between 750 and 900mV, even lower/higher -tt, it fails randomly showing 0.00MH. I tried also to keep memory stock (875MHz), it fails randomly, same problem and miner stays locked, mouse too, just hard reset works. When I have removed -hstats 2 command, keeping just -tt 62 -cclock 1300 -cvddc 800 -mclock 900, it worked fine 12 hours but I just tried last sollution: I have deleted all commands -tt 62 -cclock 1300 -cvddc 800 -mclock 900 -hstats 2 from ,bat file and I have used just Msi Afterburner 4.6.2 beta 2 https://www.guru3d.com/files-details/msi-afterburner-beta-download.html wich full controls power limit, voltage and frequency, now I left voltage unattended (1187mV), GPU frequency stock, memory increased at 900MHz and power limit down to -43 or even -44%. Works flawless. It looks as the much commands gived to the miner (tt 62 -cclock 1300 -cvddc 800 -mclock 900 -hstats 2), especially -hstats 2, gives driver error (atimtag.dll) and locks the miner... So, I keept settings as in picture attached and .bat file as simple, without extra commands ex: PhoenixMiner.exe -pool ssl://eu1.ethermine.org:5555 -pool2 ssl://us1.ethermine.org:5555 -wal your wallet adress.rig name, and is rock solid. https://i.postimg.cc/RhtKXjtg/Best-settings.jpg It is important to avoid using both the PhoenixMiner hardware control options and third party programs (e.g. Afterburner) at the same time. While we use the AMD provided API to do most of the hardware control and monitoring, most of these programs use lower-level undocumented access and doing both at the same time can lead to driver lock ups. Note that Afterburner must be completely closed, not only minimized to tray in order to stop interacting with the GPUs. Or, alternatively, you should use only Afterburner (or other third party program) and none of PhoenixMiner hardware control options. |
|
|
|
hi,
some of my cards are rx570 with moded bios so they need the pixel patcher
after update to amd driver 19.9.1 - the patcher doesnt work, just gives the error "File too large"
any solution for this? or do i have to go back to older driver ?
The latest version of the patcher (atikmdag-patcher-1.4.7.zip) works fine with 19.9.1 drivers. It appears that the official thread for it is here: https://www.monitortests.com/forum/Thread-AMD-ATI-Pixel-Clock-Patcher (note that aren't affiliated with its creator in any way, so decide for yourself, we just use it with our modded cards and it works fine). Going back to the older drivers is also an option because RX570 doesn't benefit from the latest drivers. |
|
|
|
We tested on a similar rig (RX570 + RX5700, Windows 10 1709, AMD driver 19.9.1) and we didn't encounter any problems. Does PhoenixMiner 4.5c work on the same rig? What is the version of the drivers? Also, please try to run PhoenixMiner 4.6b only with -list (i.e. Phoenixminer.exe -list) and see if it shows the list of GPUs properly. A possible but unlikely reason - Windows defender may be blocking or even deleting PhoenixMiner.exe.
... Edit3: Turns out Windows Defender was blocking the miner... Haven't seen it block something like that before.... Thank you for finding the cause of the problem on your rig. We were scratching our heads because even with latest Windows updates we couldn't reproduce the problem. Frankly, the behviour of Windows Defender is becoming really idiotic. We are already disabled it permanently on all our test rigs (and even on developer PCs) from the start but we will stop short from recommending this for everyone. Just keep in mind that whenever you see strange behavior or unexplained errors, just try with disabled Windows Defender to be sure that it is not causing problems. |
|
|
|
|
Show Posts
