 Show Posts
|
|
Pages: [1] 2 3 »
|
Some notes on the best (or at least some of the better) drivers for AMD cards: - If you have 6GB or 8GB card that is at least Polaris (i.e. 470/480/570/580, Vega, Radeon VII, Navi), you should run at least driver 20.5.1 under Windows 10, or driver 20.10.x under Linux.
Is there any way to patch drivers version higher that 20.5.1 for BIOS modified cards? I had no luck with PhoenixMiner detecting any GPUs for mining with 20.5.1 and as far as I know you can't patch newer drivers with AMD-ATI-Pixel-Clock-Patcher. Regards, zeezoo |
|
|
|
Hello guys... I need some help here. I switched my gpus (gtx 1070 8gb) to ETH after a long time, and what I see is some strange behavior. It seems that hashrate is low, and memory overclock doesn't have any effect. What I was able to google out is that apparently when there is more than 50% of 1070's gpu memory utilized it starts to behave strangely. When I try mining ETC everything is normal (sure ETC have DAG size much lower, after fork). So mining ETC I am able to get 33 MHs at 90W with underclock and undervolt core and overclocked memory as much as possible, while mining ETH I get 28 MHs at 115W (overclocked nd undervolted core, little overclock on memory) ... you see my despair  ... also mining ETH overclockin core have positive effect on hashrate, while overclocking memory doesn't have any impact - which is not normal for ethash. It happens the same on windows or linux (hive os), the same on all miners (lol miner, phoenix miner, t-rex miner ...) I was not able to find any solution to this. So is there any workaround this issue? Thanks for your help Wink Cheers It is, unfortunately, normal behaviour for Nvidia 10x0 series. Growing DAG is significantly reducing hashrate. Nothing to be done here, except increasing core frequency/voltage until it's unstable or too hot... Good hashrates are basically gone on these cards. Even 1080 Ti was doing 57 MH/s with eth pill and now it's down to 45-47. What I did was reducing memory OC but increased core clocks a little (1920) to find sweet spot between hashrate/temps/power comsumption. Coming back to lower DAG size will bring hashrates back to normal, hence if you want to see numbers higher the only solution is to mine ETC or other ethash coins with small DAG. |
|
|
|
Hi,
I try to mine with my old R9 290 with 4GB but the result it's so poor:
my .bat file:
PhoenixMiner.exe -epool xxxxxxxxxxxxx -wal xxxxxxxxxxxxxxxx -proto 3 -daglim 3820 -amd -gpus 2
2020.12.04:13:25:41.047: main 1 GPU(s) are auto-tuning. Hashrate may be low until they are ready.
2020.12.04:13:25:41.047: main Eth: Accepted shares 0 (0 stales), rejected shares 0 (0 stales)
2020.12.04:13:25:41.047: main Eth: Incorrect shares 0 (0.00%), est. stales percentage 0.00%
2020.12.04:13:25:41.047: main Eth: Average speed (5 min): 0.362 MH/s
2020.12.04:13:25:41.047: main Eth: Effective speed: 0.00 MH/s; at pool: 0.00 MH/s
I have also a RX 580 thats works correctly but i'm not capable to share his DAG file for the R9 290 so i try to do in 2 shells so separately.
Can you help me please?
Sorry for mi english level xD
I guess the best solution for you would be to mine another coin or switch to linux but there are more less 2 weeks left for mining ETH with 4GB cards and as far as I remember the hashrate on 290s was low even with 3.8GB DAG. |
|
|
|
hi, pls help, how to use PhoenixMiner command in ethOS  i try "-daglim 3990" on ethos local config, but not working, my rx 570 4GB still not mining ... There's no need to do anything in Linux. I use hiveOS for my 4GB cards and they mine at full speed. Even better than before due to rxboost... |
|
|
|
Hi there,
I have 4 GPUS (1x RX 570, 3x RX 580). I'm using AMD Radeon drivers (non-whql-win10-64bit-radeon-software-crimson-relive-17.10.2-oct23).
Do you recommend me to update it to the last version (20.4.x) or don't touch anything?
Thanks in advance!!!!
If it works and you're happy with your hashrates just keep it. If anything is wrong, you're facing hashrate drops or miner is not stable then update. I'm using v20.4.2 myself on all rigs and they work fine. Regards, zeezoo Thanks, I've got around 124MH/s. Is it right or I can obtain more MH/s ? With Claymore's I've got around 127 MH/s.  Newer drivers are usually working better than the old ones. 124/4 = 31, so I guess it's pretty nice score for 570/580s. I think rxboost is not supported with the drivers that you use in PhoenixMiner... Thx !! I'm going to try with the last stable drivers. If I can get more MH/s... why not? hehe Thanks again !! Let us know the results. You can always revert to previos drivers if it's worse than now. Good luck! |
|
|
|
Hi there,
I have 4 GPUS (1x RX 570, 3x RX 580). I'm using AMD Radeon drivers (non-whql-win10-64bit-radeon-software-crimson-relive-17.10.2-oct23).
Do you recommend me to update it to the last version (20.4.x) or don't touch anything?
Thanks in advance!!!!
If it works and you're happy with your hashrates just keep it. If anything is wrong, you're facing hashrate drops or miner is not stable then update. I'm using v20.4.2 myself on all rigs and they work fine. Regards, zeezoo Thanks, I've got around 124MH/s. Is it right or I can obtain more MH/s ? With Claymore's I've got around 127 MH/s. Newer drivers are usually working better than the old ones. 124/4 = 31, so I guess it's pretty nice score for 570/580s. I think rxboost is not supported with the drivers that you use in PhoenixMiner... |
|
|
|
Hi there,
I have 4 GPUS (1x RX 570, 3x RX 580). I'm using AMD Radeon drivers (non-whql-win10-64bit-radeon-software-crimson-relive-17.10.2-oct23).
Do you recommend me to update it to the last version (20.4.x) or don't touch anything?
Thanks in advance!!!!
If it works and you're happy with your hashrates just keep it. If anything is wrong, you're facing hashrate drops or miner is not stable then update. I'm using v20.4.2 myself on all rigs and they work fine. Regards, zeezoo |
|
|
|
Nice to see new version but my question still not answered not only me many people interested as well.
Will be there new version for new coming ETC fork with reduced dag size? there is only 6-8days left to fork, thanks
Your question was already adressed shortly after 5.2a release. Peace Edit: It would be really fantastic if we could select cards 0,1,2 to mine ETH and 3,4,5 for ETC under the same instance of PhoenixMiner... @Phoenixminer: the 5.2a will compatible with the ETCHASH?
We will add support for the new ETC variant of ethash (with reduced DAG size after epoch 390) in the stable version of 5.2, it is not included in 5.2a yet, but there is still at least three weeks before ETC reaches epoch 390. |
|
|
|
Hy people!
I have a problem running more than 9 RX580 at my ashrock H110. It run with 12 cards till december 19, than I stopped mining. Now I startet again, but get always error in claymore and with phoenix is the same. The mainboard found more than 9 cards, but get errors when I try to run more than 9 cards. I have old blockchain drivers for the amd rx580 cards. So, do you think after upgrading will it be posible to run more than 9 cards, or will it be the same?
I did not upgrade now, because I don´t know if the system runs stable after upgrading? Last update was maybe 2018, after installing the system.
I have two riggs with the same components - both are running only 9 cards, more than 9 - error.
thank you for your replay
Anon
use 20.4.2 drivers, it works fine with 10 gpu rigs Hi! Thx for the answer! I did upgrade to this driver 20.4.2, but it is the same. The miner crashes, error something in phoenix. At Claymore error at gpu x, gpu y... The system finds 12 gpu´s, but not posible to mine more than 9 gpu´s. I can mix the 9 gpu´s at all 12 slots with also mixing the risers to know if the gpu´s are ok, the risers are ok and the gpu-slots at the mainboard are ok, no idea at the moment.... I tryed also with a brand new ashrock h110 btc plus, with also the driver 20.4.2, but phonix and claymore are not willing to mine... Maybe motherboard bios update?? thank you Anon It is possible to mine even with 19 gpus under Windows. Just make sure you're running latest Win10 version as well as recommended drivers. |
|
|
|
PhoenixMiner 5.2d is ready with another speed improvement for AMD 4 GB cards. You can download PhoenixMiner 5.2d from here (both Windows and Linux versions): https://mega.nz/folder/OYcgVZJD#jC_7RaccVXhi0TGov5JupA (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.2d_Windows.zip
===================================
SHA-1: c0046d07d915c030c5486536a29c49e044943b4f
SHA-256: 8093946d46acf3609d61a8ba8e2c7b71b0920e3cf8cef2732db320d8eeed30b8
SHA-512: 70fa65657aac7b0a34f7e847dec60c859536af840be919316a619501d22cec83315bda0df2736d6e37c8af8bff00af99d92a0d23f655b17edd7c308439bc7c2c
File: PhoenixMiner_5.2d_Linux.tar.gz
====================================
SHA-1: 9ba41efc5c54ff4682e216976c6f44d3dc6dc6e8
SHA-256: 714af07c14e960c1fb8782e91c4add3aa292a26ef820cf797f452fdf411677d7
SHA-512: 7c13305660736d62d3de2b82875afaa18d2cbbd518a4a9b368763827a89834a38034d91fcfd5bb29ca0c21120738a03aff36d982f685336212ece868f4ceaf4c
File: PhoenixMiner_NVRTC_Windows.zip
====================================
SHA-1: ff6fa5e018adbd52caf631c42b7c2fac7ce48a51
SHA-256: 8087757169405d51ea8ba818347fb05d0450aef985c29272165070346eb5a54a
SHA-512: 7b2d832f7f40578bb1f501d5174467f5ae06612e601dab769fd56d39da48a471b18c6373435a485155f70fec4017d8378797bf1e1dfe5d62fee30fa6a1d992c4
The changes in this release (since 5.2c) include the following: - Added support for -daglim for AMD Fiji, Tonga, and Baffin cards with 4GB VRAM, so you will be able to use them some time beyond epoch 373 (Windows), or 381 (Linux)
- New kernels for 4GB AMD cards with higher hashrate when -daglim is in effect
- Added -daglim and -rxboost support in Linux. The default -daglim value in Linux is 4064 for older drivers (before 19.50), and 4076 for the newer drivers
- Added support for the AMD Linux drivers 20.20, and 20.30
- Added support for the latest AMD Linux drivers 20.40-1147286 (however they seem to have hardware control problems with some cards, so no need to upgrade for now)
The changes of the previous beta (5.2c) since the last version (5.1c) are: - The kernels are modified to allow bigger DAG limit of 4023 MB under Windows. This allows higher hashrate when the DAG is bigger than the available VRAM.
- The -daglim parameter is now on "auto" (1) by default and it sets the DAG limit to 4023, so you don't need to set -daglim 1 or -daglim 4023 if the default value is working fine.
- AMD cards with more than 4 GB RAM will now work without issues until DAG epoch 450
- Added new -daglim parameter to allow a few more weeks of work for 4 GB AMD Polaris cards. Use -daglim 1 for automatic operation, or specify a concrete value for the maximum DAG size (example: -daglim 4000 will set max DAG size 4000 MB)
- Added -rxboost parameter (also accessible via -vmr) to boost the performance of GDDR5 based AMD cards (Polaris or earlier)
- Added memory straps support for AMD Vega cards. Use the -straps command-line option to activate it (example: -straps 1 will activate the lowest strap level)
- The Nvidia memory timing (straps) option is improved and now is turned off during DAG generation to avoid any possible instability issues
- Many other small improvements and fixes
Here are some additional notes: - The -daglim option works on Polaris (RX470, RX480, RX570, RX580, RX590), Baffin (RX560, RX550), Tonga, and Fiji cards. It limits the DAG size to <n> MB to allow mining on 4 GB cards a few weeks after epoch 374 on Windows (or after 381 on Linux). The possible values are the exact DAG limit in MB, or 0 (turn off the DAG limit), or 1 (automatic DAG limit size, usually around 4023 MB under Windows; this is the default option). Note that the hashrate will drop significantly with each epoch after the DAG limit is in effect. If the hashrate drops too much (e.g. from 28 MH/s to just 2-3 MH/s, you need to use lower value, for example -daglim 3990
- (Windows) With PhoenixMiner 5.2d either remove the -daglim option entirely (it is set to auto by default), or set it to -daglim 4023, which should work on all 470/480/570/580/590 cards with "good" drivers (see bellow)
- (Windows) If you cards doesn't work with the default DAG limit of 4023 and require substantial decrease to 4006 or 3990, you need to update to one of the "good" AMD drivers for Windows: from 18.12.1.1 to 19.7.5 (inclusive), and from 19.12.2 to 20.11.1 (inclusive)
- (Linux) With PhoenixMiner 5.2d either remove the -daglim option entirely (it is set to auto by default), or set it to -daglim 4064 on older drivers (before 19.50), or -daglim 4076 on newer drivers.
- (Linux) When the -daglim option is in effect (i.e. if you are mining ETH or ETC with 4GB cards), the miner will restart on each new DAG epoch, and will force serial (one-by-one) generation of the DAG buffers. To allow more stable operation under these conditions, it is best to use -rmode 0 and to use a script to restart the miner when it exits. Two such scripts are provided with the miner: start_amd_4g_old_drv.sh for older drivers (before 19.50, note that when using -rmode 0, the -daglim for these older drivers can be increased to 4068), and start_amd_4g_new_drv.sh for newer drivers. Make sure to change the pools and the wallet in these scripts with your own before using them for mining.
- It is also important to use auto-tune (do not specify -gt values in the command line) because the optimal -gt value may change with each new epoch, and will definitely be different than before.
- Using -rxboost, -vmr, or -straps on AMD cards requires running as administrator (or as root under Linux), so you need to run PhoenixMiner as administrator for the VRAM timing options to work. Note that the -mt option will still work without running as administrator.
- The -rxboost option is only supported on GDDR5 cards (RX4xx/RX5xx or older).
- The VRAM timing options can be quite different between the GPUs, even when the GPUs are the same model. Therefore, you can (and probably should) specify the VRAM timing options separately for each GPU.
Please let us know if you have any problems or questions related to PhoenixMiner 5.2d. PROBLEM! Claymore OK, lolminer OK, TeamRedMiner OK ale PM 5.2d KO... Please do something from the SW to be able to benefit on the RX 570 8GB. How come other SWs go? 2020.11.18:10:21:03.440: main Phoenix Miner 5.2d Windows/msvc - Release build 2020.11.18:10:21:03.440: main Cmd line: -pool ssl://eu1.ethermine.org:5555 -pool2 ssl://us1.ethermine.org:5555 -wal adresa.Miner16 -rmode 2 -tstop 85 -cdmport 2222 2020.11.18:10:21:03.440: main No CUDA driver found 2020.11.18:10:21:04.955: main OpenCL driver version: 17.8-BETA 2020.11.18:10:21:04.989: main Available GPUs for mining: 2020.11.18:10:21:04.989: main GPU1: Radeon RX 570 Series (pcie 1), OpenCL 2.0, 8 GB VRAM, 32 CUs 2020.11.18:10:21:04.989: main GPU2: Radeon RX 570 Series (pcie 2), OpenCL 2.0, 8 GB VRAM, 32 CUs 2020.11.18:10:21:04.989: main GPU3: Radeon RX 570 Series (pcie 3), OpenCL 2.0, 8 GB VRAM, 32 CUs 2020.11.18:10:21:04.989: main GPU4: Radeon RX 570 Series (pcie 4), OpenCL 2.0, 8 GB VRAM, 32 CUs 2020.11.18:10:21:04.989: main GPU5: Radeon RX 570 Series (pcie 5), OpenCL 2.0, 8 GB VRAM, 32 CUs 2020.11.18:10:21:04.989: main GPU6: Radeon RX 570 Series (pcie 6), OpenCL 2.0, 8 GB VRAM, 32 CUs 2020.11.18:10:21:04.989: main Increase the Windows page file size to at least 29 GB to avoid out of memory errors and unexpected crashes. 2020.11.18:10:21:04.989: main ADL library initialized 2020.11.18:10:21:06.300: main Eth: the pool list contains 2 pools (2 from command-line) 2020.11.18:10:21:06.300: main Eth: primary pool: ssl://eu1.ethermine.org:5555 2020.11.18:10:21:06.300: main Starting GPU mining 2020.11.18:10:21:06.300: main Matched GPU1 to ADL adapter index 24 (method 1) 2020.11.18:10:21:06.321: main GPU1: AMD driver BETA 2020.11.18:10:21:06.321: main GPU1: Created ADL monitor for adapter 24; overdrive version: 7 (7) 2020.11.18:10:21:06.321: main GPU1: using the blockchain beta driver 2020.11.18:10:21:06.321: main Matched GPU2 to ADL adapter index 0 (method 1) 2020.11.18:10:21:06.342: main GPU2: AMD driver BETA 2020.11.18:10:21:06.342: main GPU2: Created ADL monitor for adapter 0; overdrive version: 7 (7) 2020.11.18:10:21:06.342: main GPU2: using the blockchain beta driver 2020.11.18:10:21:06.342: main Matched GPU3 to ADL adapter index 12 (method 1) 2020.11.18:10:21:06.365: main GPU3: AMD driver BETA 2020.11.18:10:21:06.365: main GPU3: Created ADL monitor for adapter 12; overdrive version: 7 (7) 2020.11.18:10:21:06.365: main GPU3: using the blockchain beta driver 2020.11.18:10:21:06.365: main Matched GPU4 to ADL adapter index 18 (method 1) 2020.11.18:10:21:06.390: main GPU4: AMD driver BETA 2020.11.18:10:21:06.390: main GPU4: Created ADL monitor for adapter 18; overdrive version: 7 (7) 2020.11.18:10:21:06.390: main GPU4: using the blockchain beta driver 2020.11.18:10:21:06.390: main Matched GPU5 to ADL adapter index 6 (method 1) 2020.11.18:10:21:06.410: main GPU5: AMD driver BETA 2020.11.18:10:21:06.410: main GPU5: Created ADL monitor for adapter 6; overdrive version: 7 (7) 2020.11.18:10:21:06.411: main GPU5: using the blockchain beta driver 2020.11.18:10:21:06.411: main Matched GPU6 to ADL adapter index 30 (method 1) 2020.11.18:10:21:06.436: main GPU6: AMD driver BETA 2020.11.18:10:21:06.436: main GPU6: Created ADL monitor for adapter 30; overdrive version: 7 (7) 2020.11.18:10:21:06.436: main GPU6: using the blockchain beta driver 2020.11.18:10:21:06.539: wdog Starting watchdog thread 2020.11.18:10:21:06.820: main Eth: Connecting to ethash pool ssl://eu1.ethermine.org:5555 (proto: EthProxy) 2020.11.18:10:21:06.821: main GPU1: 40C 22% 36W, GPU2: 44C 25% 32W, GPU3: 43C 25% 32W, GPU4: 45C 27% 32W, GPU5: 43C 24% 34W, GPU6: 43C 25% 32W GPUs power: 196.6 W 2020.11.18:10:21:07.023: main Listening for CDM remote manager at port 2222 in read-only mode 2020.11.18:10:21:07.061: eths Eth: Connected to SSL ethash pool eu1.ethermine.org:5555 (172.65.207.106) 2020.11.18:10:21:07.144: eths Eth: Send: {"id":1,"jsonrpc":"2.0","method":"eth_submitLogin","worker":"eth1.0","params":["0xAc6C6D400644eF9861373514266899F891e7e130.Miner16"]} 2020.11.18:10:21:07.182: eths Eth: Received: {"id":1,"jsonrpc":"2.0","result":true} 2020.11.18:10:21:07.182: eths Eth: Send: {"id":5,"jsonrpc":"2.0","method":"eth_getWork","params":[]} 2020.11.18:10:21:07.199: eths Eth: Received: {"id":0,"jsonrpc":"2.0","result":["0xa69bf44a20854d836f582aafd03c0f9051fa569e9e36c4b80de5a88f9be1c8c9","0x731f490a019481affba0aff3c5e52cd6b808378f19a46c40c2157465420f1404","0x0000000112e0be826d694b2e62d01511f12a6061fbaec8bc02357593e70e52ba","0xac22bb"]} 2020.11.18:10:21:07.199: eths Eth: New job #a69bf44a from ssl://eu1.ethermine.org:5555; diff: 4000MH 2020.11.18:10:21:07.205: GPU1 GPU1: Starting up... (0) 2020.11.18:10:21:07.205: GPU1 GPU1: Generating ethash light cache for epoch #376 2020.11.18:10:21:07.209: GPU2 GPU2: Starting up... (0) 2020.11.18:10:21:07.213: GPU3 GPU3: Starting up... (0) 2020.11.18:10:21:07.215: GPU4 GPU4: Starting up... (0) 2020.11.18:10:21:07.218: GPU5 GPU5: Starting up... (0) 2020.11.18:10:21:07.220: GPU6 GPU6: Starting up... (0) 2020.11.18:10:21:08.823: eths Eth: Received: {"id":0,"jsonrpc":"2.0","result":["0x9b9ef2712ee05d68cb52143b9d8259bd169ccb7cf25e2f165d9a2c36a1fba7b2","0x731f490a019481affba0aff3c5e52cd6b808378f19a46c40c2157465420f1404","0x0000000112e0be826d694b2e62d01511f12a6061fbaec8bc02357593e70e52ba","0xac22bb"]} 2020.11.18:10:21:08.823: eths Eth: New job #9b9ef271 from ssl://eu1.ethermine.org:5555; diff: 4000MH 2020.11.18:10:21:11.522: GPU1 Light cache generated in 4.3 s (14.6 MB/s) 2020.11.18:10:21:11.885: main Eth speed: 0.000 MH/s, shares: 0/0/0, time: 0:00 2020.11.18:10:21:11.885: main 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) I have the same problems with 8 GB Cards ... they do not work at all with the new version ! Drivers! I won't play drivers when it works in Claymore and BETA. It is a problem only SW from PM. He has to solve this :-( Then use Claymore. It's clearly mentioned in the first post that "these are recommended drivers that work best with our software" and BETA drivers are no longer recommended. By the way - These drivers are from which year? 2018?... If it works good with the other mining software there's no need to use PhoenixMiner, right? I'm using 20.4.2 myself on 4 different rigs and have no issues at all with 5.2d and 4GB/8 GB cards... except 1-2 MH/s loss with RX574 and RX474 ... Peace. |
|
|
|
PhoenixMiner 5.2d is ready with another speed improvement for AMD 4 GB cards. You can download PhoenixMiner 5.2d from here (both Windows and Linux versions): https://mega.nz/folder/OYcgVZJD#jC_7RaccVXhi0TGov5JupA (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.2d_Windows.zip
===================================
SHA-1: c0046d07d915c030c5486536a29c49e044943b4f
SHA-256: 8093946d46acf3609d61a8ba8e2c7b71b0920e3cf8cef2732db320d8eeed30b8
SHA-512: 70fa65657aac7b0a34f7e847dec60c859536af840be919316a619501d22cec83315bda0df2736d6e37c8af8bff00af99d92a0d23f655b17edd7c308439bc7c2c
File: PhoenixMiner_5.2d_Linux.tar.gz
====================================
SHA-1: 9ba41efc5c54ff4682e216976c6f44d3dc6dc6e8
SHA-256: 714af07c14e960c1fb8782e91c4add3aa292a26ef820cf797f452fdf411677d7
SHA-512: 7c13305660736d62d3de2b82875afaa18d2cbbd518a4a9b368763827a89834a38034d91fcfd5bb29ca0c21120738a03aff36d982f685336212ece868f4ceaf4c
File: PhoenixMiner_NVRTC_Windows.zip
====================================
SHA-1: ff6fa5e018adbd52caf631c42b7c2fac7ce48a51
SHA-256: 8087757169405d51ea8ba818347fb05d0450aef985c29272165070346eb5a54a
SHA-512: 7b2d832f7f40578bb1f501d5174467f5ae06612e601dab769fd56d39da48a471b18c6373435a485155f70fec4017d8378797bf1e1dfe5d62fee30fa6a1d992c4
The changes in this release (since 5.2c) include the following: - Added support for -daglim for AMD Fiji, Tonga, and Baffin cards with 4GB VRAM, so you will be able to use them some time beyond epoch 373 (Windows), or 381 (Linux)
- New kernels for 4GB AMD cards with higher hashrate when -daglim is in effect
- Added -daglim and -rxboost support in Linux. The default -daglim value in Linux is 4064 for older drivers (before 19.50), and 4076 for the newer drivers
- Added support for the AMD Linux drivers 20.20, and 20.30
- Added support for the latest AMD Linux drivers 20.40-1147286 (however they seem to have hardware control problems with some cards, so no need to upgrade for now)
The changes of the previous beta (5.2c) since the last version (5.1c) are: - The kernels are modified to allow bigger DAG limit of 4023 MB under Windows. This allows higher hashrate when the DAG is bigger than the available VRAM.
- The -daglim parameter is now on "auto" (1) by default and it sets the DAG limit to 4023, so you don't need to set -daglim 1 or -daglim 4023 if the default value is working fine.
- AMD cards with more than 4 GB RAM will now work without issues until DAG epoch 450
- Added new -daglim parameter to allow a few more weeks of work for 4 GB AMD Polaris cards. Use -daglim 1 for automatic operation, or specify a concrete value for the maximum DAG size (example: -daglim 4000 will set max DAG size 4000 MB)
- Added -rxboost parameter (also accessible via -vmr) to boost the performance of GDDR5 based AMD cards (Polaris or earlier)
- Added memory straps support for AMD Vega cards. Use the -straps command-line option to activate it (example: -straps 1 will activate the lowest strap level)
- The Nvidia memory timing (straps) option is improved and now is turned off during DAG generation to avoid any possible instability issues
- Many other small improvements and fixes
Here are some additional notes: - The -daglim option works on Polaris (RX470, RX480, RX570, RX580, RX590), Baffin (RX560, RX550), Tonga, and Fiji cards. It limits the DAG size to <n> MB to allow mining on 4 GB cards a few weeks after epoch 374 on Windows (or after 381 on Linux). The possible values are the exact DAG limit in MB, or 0 (turn off the DAG limit), or 1 (automatic DAG limit size, usually around 4023 MB under Windows; this is the default option). Note that the hashrate will drop significantly with each epoch after the DAG limit is in effect. If the hashrate drops too much (e.g. from 28 MH/s to just 2-3 MH/s, you need to use lower value, for example -daglim 3990
- (Windows) With PhoenixMiner 5.2d either remove the -daglim option entirely (it is set to auto by default), or set it to -daglim 4023, which should work on all 470/480/570/580/590 cards with "good" drivers (see bellow)
- (Windows) If you cards doesn't work with the default DAG limit of 4023 and require substantial decrease to 4006 or 3990, you need to update to one of the "good" AMD drivers for Windows: from 18.12.1.1 to 19.7.5 (inclusive), and from 19.12.2 to 20.11.1 (inclusive)
- (Linux) With PhoenixMiner 5.2d either remove the -daglim option entirely (it is set to auto by default), or set it to -daglim 4064 on older drivers (before 19.50), or -daglim 4076 on newer drivers.
- (Linux) When the -daglim option is in effect (i.e. if you are mining ETH or ETC with 4GB cards), the miner will restart on each new DAG epoch, and will force serial (one-by-one) generation of the DAG buffers. To allow more stable operation under these conditions, it is best to use -rmode 0 and to use a script to restart the miner when it exits. Two such scripts are provided with the miner: start_amd_4g_old_drv.sh for older drivers (before 19.50, note that when using -rmode 0, the -daglim for these older drivers can be increased to 4068), and start_amd_4g_new_drv.sh for newer drivers. Make sure to change the pools and the wallet in these scripts with your own before using them for mining.
- It is also important to use auto-tune (do not specify -gt values in the command line) because the optimal -gt value may change with each new epoch, and will definitely be different than before.
- Using -rxboost, -vmr, or -straps on AMD cards requires running as administrator (or as root under Linux), so you need to run PhoenixMiner as administrator for the VRAM timing options to work. Note that the -mt option will still work without running as administrator.
- The -rxboost option is only supported on GDDR5 cards (RX4xx/RX5xx or older).
- The VRAM timing options can be quite different between the GPUs, even when the GPUs are the same model. Therefore, you can (and probably should) specify the VRAM timing options separately for each GPU.
Please let us know if you have any problems or questions related to PhoenixMiner 5.2d. PROBLEM! Claymore OK, lolminer OK, TeamRedMiner OK ale PM 5.2d KO... Please do something from the SW to be able to benefit on the RX 570 8GB. How come other SWs go? 2020.11.18:10:21:03.440: main Phoenix Miner 5.2d Windows/msvc - Release build 2020.11.18:10:21:03.440: main Cmd line: -pool ssl://eu1.ethermine.org:5555 -pool2 ssl://us1.ethermine.org:5555 -wal adresa.Miner16 -rmode 2 -tstop 85 -cdmport 2222 2020.11.18:10:21:03.440: main No CUDA driver found 2020.11.18:10:21:04.955: main OpenCL driver version: 17.8-BETA 2020.11.18:10:21:04.989: main Available GPUs for mining: 2020.11.18:10:21:04.989: main GPU1: Radeon RX 570 Series (pcie 1), OpenCL 2.0, 8 GB VRAM, 32 CUs 2020.11.18:10:21:04.989: main GPU2: Radeon RX 570 Series (pcie 2), OpenCL 2.0, 8 GB VRAM, 32 CUs 2020.11.18:10:21:04.989: main GPU3: Radeon RX 570 Series (pcie 3), OpenCL 2.0, 8 GB VRAM, 32 CUs 2020.11.18:10:21:04.989: main GPU4: Radeon RX 570 Series (pcie 4), OpenCL 2.0, 8 GB VRAM, 32 CUs 2020.11.18:10:21:04.989: main GPU5: Radeon RX 570 Series (pcie 5), OpenCL 2.0, 8 GB VRAM, 32 CUs 2020.11.18:10:21:04.989: main GPU6: Radeon RX 570 Series (pcie 6), OpenCL 2.0, 8 GB VRAM, 32 CUs 2020.11.18:10:21:04.989: main Increase the Windows page file size to at least 29 GB to avoid out of memory errors and unexpected crashes. 2020.11.18:10:21:04.989: main ADL library initialized 2020.11.18:10:21:06.300: main Eth: the pool list contains 2 pools (2 from command-line) 2020.11.18:10:21:06.300: main Eth: primary pool: ssl://eu1.ethermine.org:5555 2020.11.18:10:21:06.300: main Starting GPU mining 2020.11.18:10:21:06.300: main Matched GPU1 to ADL adapter index 24 (method 1) 2020.11.18:10:21:06.321: main GPU1: AMD driver BETA 2020.11.18:10:21:06.321: main GPU1: Created ADL monitor for adapter 24; overdrive version: 7 (7) 2020.11.18:10:21:06.321: main GPU1: using the blockchain beta driver 2020.11.18:10:21:06.321: main Matched GPU2 to ADL adapter index 0 (method 1) 2020.11.18:10:21:06.342: main GPU2: AMD driver BETA 2020.11.18:10:21:06.342: main GPU2: Created ADL monitor for adapter 0; overdrive version: 7 (7) 2020.11.18:10:21:06.342: main GPU2: using the blockchain beta driver 2020.11.18:10:21:06.342: main Matched GPU3 to ADL adapter index 12 (method 1) 2020.11.18:10:21:06.365: main GPU3: AMD driver BETA 2020.11.18:10:21:06.365: main GPU3: Created ADL monitor for adapter 12; overdrive version: 7 (7) 2020.11.18:10:21:06.365: main GPU3: using the blockchain beta driver 2020.11.18:10:21:06.365: main Matched GPU4 to ADL adapter index 18 (method 1) 2020.11.18:10:21:06.390: main GPU4: AMD driver BETA 2020.11.18:10:21:06.390: main GPU4: Created ADL monitor for adapter 18; overdrive version: 7 (7) 2020.11.18:10:21:06.390: main GPU4: using the blockchain beta driver 2020.11.18:10:21:06.390: main Matched GPU5 to ADL adapter index 6 (method 1) 2020.11.18:10:21:06.410: main GPU5: AMD driver BETA 2020.11.18:10:21:06.410: main GPU5: Created ADL monitor for adapter 6; overdrive version: 7 (7) 2020.11.18:10:21:06.411: main GPU5: using the blockchain beta driver 2020.11.18:10:21:06.411: main Matched GPU6 to ADL adapter index 30 (method 1) 2020.11.18:10:21:06.436: main GPU6: AMD driver BETA 2020.11.18:10:21:06.436: main GPU6: Created ADL monitor for adapter 30; overdrive version: 7 (7) 2020.11.18:10:21:06.436: main GPU6: using the blockchain beta driver 2020.11.18:10:21:06.539: wdog Starting watchdog thread 2020.11.18:10:21:06.820: main Eth: Connecting to ethash pool ssl://eu1.ethermine.org:5555 (proto: EthProxy) 2020.11.18:10:21:06.821: main GPU1: 40C 22% 36W, GPU2: 44C 25% 32W, GPU3: 43C 25% 32W, GPU4: 45C 27% 32W, GPU5: 43C 24% 34W, GPU6: 43C 25% 32W GPUs power: 196.6 W 2020.11.18:10:21:07.023: main Listening for CDM remote manager at port 2222 in read-only mode 2020.11.18:10:21:07.061: eths Eth: Connected to SSL ethash pool eu1.ethermine.org:5555 (172.65.207.106) 2020.11.18:10:21:07.144: eths Eth: Send: {"id":1,"jsonrpc":"2.0","method":"eth_submitLogin","worker":"eth1.0","params":["0xAc6C6D400644eF9861373514266899F891e7e130.Miner16"]} 2020.11.18:10:21:07.182: eths Eth: Received: {"id":1,"jsonrpc":"2.0","result":true} 2020.11.18:10:21:07.182: eths Eth: Send: {"id":5,"jsonrpc":"2.0","method":"eth_getWork","params":[]} 2020.11.18:10:21:07.199: eths Eth: Received: {"id":0,"jsonrpc":"2.0","result":["0xa69bf44a20854d836f582aafd03c0f9051fa569e9e36c4b80de5a88f9be1c8c9","0x731f490a019481affba0aff3c5e52cd6b808378f19a46c40c2157465420f1404","0x0000000112e0be826d694b2e62d01511f12a6061fbaec8bc02357593e70e52ba","0xac22bb"]} 2020.11.18:10:21:07.199: eths Eth: New job #a69bf44a from ssl://eu1.ethermine.org:5555; diff: 4000MH 2020.11.18:10:21:07.205: GPU1 GPU1: Starting up... (0) 2020.11.18:10:21:07.205: GPU1 GPU1: Generating ethash light cache for epoch #376 2020.11.18:10:21:07.209: GPU2 GPU2: Starting up... (0) 2020.11.18:10:21:07.213: GPU3 GPU3: Starting up... (0) 2020.11.18:10:21:07.215: GPU4 GPU4: Starting up... (0) 2020.11.18:10:21:07.218: GPU5 GPU5: Starting up... (0) 2020.11.18:10:21:07.220: GPU6 GPU6: Starting up... (0) 2020.11.18:10:21:08.823: eths Eth: Received: {"id":0,"jsonrpc":"2.0","result":["0x9b9ef2712ee05d68cb52143b9d8259bd169ccb7cf25e2f165d9a2c36a1fba7b2","0x731f490a019481affba0aff3c5e52cd6b808378f19a46c40c2157465420f1404","0x0000000112e0be826d694b2e62d01511f12a6061fbaec8bc02357593e70e52ba","0xac22bb"]} 2020.11.18:10:21:08.823: eths Eth: New job #9b9ef271 from ssl://eu1.ethermine.org:5555; diff: 4000MH 2020.11.18:10:21:11.522: GPU1 Light cache generated in 4.3 s (14.6 MB/s) 2020.11.18:10:21:11.885: main Eth speed: 0.000 MH/s, shares: 0/0/0, time: 0:00 2020.11.18:10:21:11.885: main 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) I have the same problems with 8 GB Cards ... they do not work at all with the new version ! Drivers! |
|
|
|
PhoenixMiner 5.2c (still beta) is ready with speed improvement for AMD 4 GB cards. You can download PhoenixMiner 5.2c from here (this is only the Windows version, the Linux version will be ready in a few days): https://mega.nz/folder/HJVTkYjD#5CConQEPniyjCeluCpeDZA (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.2c_Windows.zip
===================================
SHA-1: 7d4cdb429522caa5244f05bd58bb42e21c1d94fb
SHA-256: cfb4b6a48dc15667e17dca3906cae8ef6668d4d741f692541a9cf8feda630b68
SHA-512: 01dc553015c2553353a3af5c6bdf811c9084b37bfb157f963898def1bb9b8b6e6f847a78b01ad36baada413213eab34a0a5e91333636a6adf2728b1cf42f32ba
File: PhoenixMiner_NVRTC_Windows.zip
====================================
SHA-1: ff6fa5e018adbd52caf631c42b7c2fac7ce48a51
SHA-256: 8087757169405d51ea8ba818347fb05d0450aef985c29272165070346eb5a54a
SHA-512: 7b2d832f7f40578bb1f501d5174467f5ae06612e601dab769fd56d39da48a471b18c6373435a485155f70fec4017d8378797bf1e1dfe5d62fee30fa6a1d992c4
The fixes in this release (since 5.1) include the following: - The kernels are modified to allow bigger DAG limit of 4023 MB under Windows. This will get the hashrate back to 100% on current epoch, and the next epoch will only lose about 2-3% of the hashrate.
- The -daglim parameter is now on "auto" (1) by default and it sets the DAG limit to 4023, so you don't need to set -daglim 1 or -daglim 4023 if the default value is working fine.
- AMD cards with more than 4 GB RAM will now work without issues until DAG epoch 450
- Added new -daglim parameter to allow a few more weeks of work for 4 GB AMD Polaris cards. Use -daglim 1 for automatic operation, or specify a concrete value for the maximum DAG size (example: -daglim 4000 will set max DAG size 4000 MB)
- Added -rxboost parameter (also accessible via -vmr) to boost the performance of GDDR5 based AMD cards (Polaris or earlier)
- Added memory straps support for AMD Vega cards. Use the -straps command-line option to activate it (example: -straps 1 will activate the lowest strap level)
- The Nvidia memory timing (straps) option is improved and now is turned off during DAG generation to avoid any possible instability issues
- Many other small improvements and fixes
Here are some additional notes: - With PhoenixMiner 5.2c either remove the -daglim option entirely, or set it to -daglim 4023, which should work on all 470/480/570/580/590 cards with "good" drivers (see bellow)
- The -daglim option works only on Polaris cards (RX470, RX480, RX570, RX580, RX590). It limits the DAG size to <n> MB to allow mining on 4 GB cards a few weeks after epoch 374 on Windows (or after 380-383 on Linux). The possible values are the exact DAG limit in MB, or 0 (turn off the DAG limit), or 1 (automatic DAG limit size, usually around 4023 MB under Windows; this is the default option). Note that the hashrate will drop significantly with each epoch after the DAG limit is in effect. If the hashrate drops too much (e.g. from 28 MH/s to just 2-3 MH/s, you need to use lower value, for example -daglim 3990
- It is also important to use auto-tune (do not specify -gt values in the command line) because the optimal -gt value may change with each new epoch, and will definitely be different than before.
- If you cards doesn't work with the default DAG limit of 4023 and require substantial decrease to 4006 or 3990, you need to update to one of the "good" AMD drivers for Windows: from 18.12.1.1 to 19.7.5 (inclusive), and from 19.12.2 to 20.11.1 (inclusive)
- Using -rxboost, -vmr, or -straps on AMD cards requires running as administrator (or as root under Linux), so you need to run PhoenixMiner as administrator for the VRAM timing options to work. Note that the -mt option will still work without running as administrator/root.
- The -rxboost option is only supported on GDDR5 cards (RX4xx/RX5xx or older).
- The VRAM timing options can be quite different between the GPUs, even when the GPUs are the same model. Therefore, you can (and probably should) specify the VRAM timing options separately for each GPU.
Please let us know if you have any problems or questions related to PhoenixMiner 5.2c. 4GB cards are back in the game and with rxboost working faster than pre 5.2 version... XFX 570 @ 27,5 instead of 26,6 and XFX 470 @ 26.9 instead of 25,6... Thank you for your hard work guys. Awesome. |
|
|
|
Does Phoenixminer plan the same as the Lolminer? So mining will be possible with a reduced speed until February 2021? Btw, WHEN is ETC going to cut the DAG size? Is there any supposed date for this? Thanks!
Around 2nd December 2020, so I guess soon (2-3 epochs from now) 4GB card's owners will need to find another ethash coin to mine until we can mine ETC again. Any recommendations guys? Maybe if we switch together into one coin we can bump up the price a bit 1050ti 4G out of mining( cuda memory error
My 470s and 570s 4GB still mining at the same speeds with current epoch 370. I guess I'm lucky Regards, zeezoo |
|
|
|
hi
my rx580 8gb stop mining ETC at #379 epoch (4GB DAG size) in win10 & PhoenixMiner 5.1c
but still work ETH at #368 epoch.
my driver is Crimson Beta for Blockchain.
i dont have any problem in linux but some rigs work in win10.
any suggestion?
Good drivers. These are versions from 18.12.1.1 to 19.7.5 (inclusive), and from 19.12.2 to 20.8.1 (inclusive). These will allow you to mine until DAG epoch 372-373 and won't need restart of PhoenixMiner on each DAG epoch change.
Not so good drivers. These are versions 18.1.1 to 18.10.1 (inclusive), and from 19.8.1 to 19.12.1 (inclusive). This will allow you to mine until DAG epoch 365-366 and will require restart of PhoenixMiner on each DAG epoch change (for these drivers this will be preformed automatically unless you have added -dagrestart 0 command-line option to explicitly disable the auto-restart).
Your 8GB RX580 should be able to mine ETC without issues though, even with Blockchain drivers. |
|
|
|
I have a few rigs with 9GPU AMD 4GB and all of them have the same problem. Only 8 GPU's are working, GPU 1 hashrate is 0.0MHS and after some time miner restarts because GPU "is not working". Any tips for that error? Tried latest windows, different drivers....etc If I try to mine different coin they are all wrking at full speed, and no issue with GPU1....
You can also use integrated GPU if your CPU/Mobo supports it. Just connect hdmi to motherboard and check it out. Windows will use iGPU to display desktop and Phoenix will be able to use full GPU memory. |
|
|
|
hi all,
4gb cards stopped mining ETH, or have some fix for it ?
Use "good drivers" as described in 1st post and latest phoenixminer 5.1c. I have still no issues mining on 470 4G and 570 4G. Speeds are the same for almost 3 years. |
|
|
|
Anyone else's rx570s(4gig) just drop in hashrate under windows 10? if not what driver's are you using or how are you doing it?
Thanks
I had the same problem, but then I updated to 20.4.2 It was mentioned in an earlier post and now I’m running again. It’s pretty volatile right now for my 4 GB cards, but it is working I upgraded to 20.8.1 before you posted and one rig is running fine however the other is running but locking up strangely. The screen totally freezes but nanopool is still accepting a reported hashrate just no work so I do not know the miner is down. so.... 1: Should I downgrade driver to 20.4.2? 2: Should I be using DDU on the driver switch(I did not) Thanks 1. I'm using 20.4.2 with 470, 570 4GB without any issues so far. 2. Definitely. Each time you update/downgrade drivers you should use DDU. |
|
|
|
Anyone else's rx570s(4gig) just drop in hashrate under windows 10? if not what driver's are you using or how are you doing it?
Thanks
No hashrate drops for both 470 4G and 570 4G... Just use recommended drivers from 1st page and you'll be fine until DAG 372ish. |
|
|
|
I have NVIDIA MSI GeForce GT 1030 OC 2GH and information in phoenix
GPU1: Allocating DAG for epoch #366 (3.86) GB
CUDA error in CudaProgram.cu:373 : out of memory (2)
my card have 2GB. What to do ?
Choose a coin with dag size less than 2GB https://investoon.com/tools/dag_sizeis this necessary for only graphic card ? For ryzen too ? Which is more profitable card NVIDIA MSI GeForce GT 1030 OC 2GH or slow ryzen ? You can mine Monero with Ryzen or some other cpu-mineable coins. Check cpu-pool.com . I used to mine XMR, YTN and MBC with CPUs but profitability is very, very low. Unless you get some coins today and price goes 10-20x in few months/years. Same for your 1030. You will not get any significant amount of crypto using that card these days and will probably pay more for power. Better to buy crypto for cash IMHO. |
|
|
|
|
