Topic: PhoenixMiner 6.2c: fastest Ethereum/Ethash miner with lowest devfee (Win/Linux) - page 141. (Read 784965 times)
January 13, 2021, 01:18:55 PM
@Mr.Phoenix thanks for update. what about add strap option for polaris cards?
January 13, 2021, 12:35:04 PM
Radeon 7 hashrate decreased and fluctuating since epoch 384. From 89mhs down to 82mhs. It was fine before epoch 384. My 5700 on the same rig is not affected. Tried other versions of the miner but still the same problem. Anybody have the same issue. Im on driver 20.8.1. GT on autotune
January 13, 2021, 11:47:41 AM
The new beta version is ready. You can download PhoenixMiner 5.5b
Hello, do you have plans to fix ethash performance under win7 for Nvidia 10 series GPUs? January 13, 2021, 09:36:26 AM
- 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
Do we need to reset -GT settings ?
January 13, 2021, 06:30:33 AM
Hi, new user and player here and this is my first post 
First of all thank you for all your work guys so far.
Have tried the 5.5.b driver for 20-30 mins on my modded 5700xt , so far i see no difference on hash rate power consumption ( still 54-55 MH/s with 108-113w ).
Shall test it later and if i see difference i will post again.
edit: Windows 10 with latest stable amd drivers 20.11.1
First of all thank you for all your work guys so far.
Have tried the 5.5.b driver for 20-30 mins on my modded 5700xt , so far i see no difference on hash rate power consumption ( still 54-55 MH/s with 108-113w ).
Shall test it later and if i see difference i will post again.
edit: Windows 10 with latest stable amd drivers 20.11.1
January 13, 2021, 04:42:46 AM
The new beta version is ready. You can download PhoenixMiner 5.5b
Hello, do you have plans to fix ethash performance under win7 for Nvidia 10 series GPUs? January 13, 2021, 04:37:22 AM
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):
The new features in this release are:
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.
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):
Code:
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.
What about RTX 3000 series get insane amount of invalid shares after every epoch change, and you have to reset everything to stock everything until epoch is fully loaded on every card then you can re-overclock again?
January 13, 2021, 04:05:22 AM
- 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
Do we need to reset -GT settings ?
January 13, 2021, 03:06:19 AM
The new beta version is ready. You can download PhoenixMiner 5.5b 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):
The new features in this release are:
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.
(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):
Code:
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.
January 12, 2021, 09:42:07 PM
A GTX 980TI HAS GDDR5X VRAM--
But there was no "Pill" for this Maxwell chip GPU. It mined ETH at 26MH/s at best and used more energy than a GTX 1080ti mining at 35-50MH/s (depending on tuning and pill-taking).
It will mine ETH with the right miner. If the miner is not compiled to include Maxwell-chip compatibility, it won't work. If you compile the stock Ethereum miner (no fee, free, open-source), it will mine ETH. You will need to set the compile options to include Maxwell chips.
--scryptr
EDIT: I have a couple 980ti cards, but I don't feel like plugging them in. Try setting options for CUDA kernels and "nvmem"? Good luck!
--scryptr
But there was no "Pill" for this Maxwell chip GPU. It mined ETH at 26MH/s at best and used more energy than a GTX 1080ti mining at 35-50MH/s (depending on tuning and pill-taking).
It will mine ETH with the right miner. If the miner is not compiled to include Maxwell-chip compatibility, it won't work. If you compile the stock Ethereum miner (no fee, free, open-source), it will mine ETH. You will need to set the compile options to include Maxwell chips.
--scryptr
EDIT: I have a couple 980ti cards, but I don't feel like plugging them in. Try setting options for CUDA kernels and "nvmem"? Good luck!
--scryptr
January 12, 2021, 09:00:44 PM
Im showing a gtx980ti is cuda 6.0. ... and you are using cuda 11.0
Thats all i notice right away....besides the fail near the bottom
Thats all i notice right away....besides the fail near the bottom
January 12, 2021, 08:25:01 PM
I ask you a question, I am new.
Can you mine with a Geforce GTX 980 TI
start_miner.bat:
REM
REM Example bat file for starting PhoenixMiner.exe to mine ETH
REM
setx GPU_FORCE_64BIT_PTR 0
setx GPU_MAX_HEAP_SIZE 100
setx GPU_USE_SYNC_OBJECTS 1
setx GPU_MAX_ALLOC_PERCENT 100
setx GPU_SINGLE_ALLOC_PERCENT 90
REM IMPORTANT: Replace the ETH address with your own ETH wallet address in the -wal option (Rig001 is the name of the rig)
PhoenixMiner.exe -pool ssl://us1.ethermine.org:5555 -pool2 ssl://us1.ethermine.org:5555 -wal 0x07dc04bc7c9ab4fc9bdf3a1ccf9b6b8b53df622a.Rig001
pause
...
And on the other hand when I execute start_miner.bat and the DAC reaches 97%, then the screen goes black, and it throws me the following error:
CUDA version: 11.0, CUDA runtime: 8.0
No OpenCL platforms found
Available GPUs for mining:
GPU1: GeForce GTX 980 Ti (pcie
, CUDA cap. 5.2, 6 GB VRAM, 22 CUs
Nvidia driver version: 461.09
Eth: the pool list contains 2 pools (2 from command-line)
Eth: primary pool: ssl://us1.ethermine.org:5555
Starting GPU mining
Eth: Connecting to ethash pool ssl://us1.ethermine.org:5555 (proto: EthProxy)
GPU1: 51C 0% 18W
GPUs power: 18.0 W
Eth: Connected to SSL ethash pool us1.ethermine.org:5555 (172.65.218.238)
Listening for CDM remote manager at port 3333 in read-only mode
Eth: New job #a64bac20 from ssl://us1.ethermine.org:5555; diff: 4000MH
GPU1: Starting up... (0)
GPU1: Generating ethash light cache for epoch #388
Light cache generated in 1.9 s (34.2 MB/s)
GPU1: Allocating DAG (4.05) GB; good for epoch up to #390
GPU1: Generating DAG for epoch #388
Eth: New job #a3185cbe from ssl://us1.ethermine.org:5555; diff: 4000MH
GPU1: DAG 13%
Eth speed: 0.000 MH/s, shares: 0/0/0, time: 0:00
GPU1: DAG 27%
GPU1: DAG 41%
Eth: New job #2c75af58 from ssl://us1.ethermine.org:5555; diff: 4000MH
Eth: New job #ccddc397 from ssl://us1.ethermine.org:5555; diff: 4000MH
Eth: New job #aadfef96 from ssl://us1.ethermine.org:5555; diff: 4000MH
GPU1: DAG 55%
GPU1: DAG 69%
Eth speed: 0.000 MH/s, shares: 0/0/0, time: 0:00
GPU1: DAG 83%
Eth: New job #4f8511a3 from ssl://us1.ethermine.org:5555; diff: 4000MH
GPU1: DAG 97%
GPU1: DAG generated in 10.8 s (382.1 MB/s)
GPU1: Using v2 Ethash CUDA kernels (GeForce GTX 980 Ti)
Eth speed: 0.000 MH/s, shares: 0/0/0, time: 0:00
Eth: New job #7d2f9679 from ssl://us1.ethermine.org:5555; diff: 4000MH
CUDA error in CudaProgram.cu:465 : unknown error (999)
GPU1 search error: unknown error
Fatal error detected. Restarting.
Eth: New job #593be957 from ssl://us1.ethermine.org:5555; diff: 4000MH
can this be fixed?
Can you mine with a Geforce GTX 980 TI
start_miner.bat:
REM
REM Example bat file for starting PhoenixMiner.exe to mine ETH
REM
setx GPU_FORCE_64BIT_PTR 0
setx GPU_MAX_HEAP_SIZE 100
setx GPU_USE_SYNC_OBJECTS 1
setx GPU_MAX_ALLOC_PERCENT 100
setx GPU_SINGLE_ALLOC_PERCENT 90
REM IMPORTANT: Replace the ETH address with your own ETH wallet address in the -wal option (Rig001 is the name of the rig)
PhoenixMiner.exe -pool ssl://us1.ethermine.org:5555 -pool2 ssl://us1.ethermine.org:5555 -wal 0x07dc04bc7c9ab4fc9bdf3a1ccf9b6b8b53df622a.Rig001
pause
...
And on the other hand when I execute start_miner.bat and the DAC reaches 97%, then the screen goes black, and it throws me the following error:
CUDA version: 11.0, CUDA runtime: 8.0
No OpenCL platforms found
Available GPUs for mining:
GPU1: GeForce GTX 980 Ti (pcie
, CUDA cap. 5.2, 6 GB VRAM, 22 CUsNvidia driver version: 461.09
Eth: the pool list contains 2 pools (2 from command-line)
Eth: primary pool: ssl://us1.ethermine.org:5555
Starting GPU mining
Eth: Connecting to ethash pool ssl://us1.ethermine.org:5555 (proto: EthProxy)
GPU1: 51C 0% 18W
GPUs power: 18.0 W
Eth: Connected to SSL ethash pool us1.ethermine.org:5555 (172.65.218.238)
Listening for CDM remote manager at port 3333 in read-only mode
Eth: New job #a64bac20 from ssl://us1.ethermine.org:5555; diff: 4000MH
GPU1: Starting up... (0)
GPU1: Generating ethash light cache for epoch #388
Light cache generated in 1.9 s (34.2 MB/s)
GPU1: Allocating DAG (4.05) GB; good for epoch up to #390
GPU1: Generating DAG for epoch #388
Eth: New job #a3185cbe from ssl://us1.ethermine.org:5555; diff: 4000MH
GPU1: DAG 13%
Eth speed: 0.000 MH/s, shares: 0/0/0, time: 0:00
GPU1: DAG 27%
GPU1: DAG 41%
Eth: New job #2c75af58 from ssl://us1.ethermine.org:5555; diff: 4000MH
Eth: New job #ccddc397 from ssl://us1.ethermine.org:5555; diff: 4000MH
Eth: New job #aadfef96 from ssl://us1.ethermine.org:5555; diff: 4000MH
GPU1: DAG 55%
GPU1: DAG 69%
Eth speed: 0.000 MH/s, shares: 0/0/0, time: 0:00
GPU1: DAG 83%
Eth: New job #4f8511a3 from ssl://us1.ethermine.org:5555; diff: 4000MH
GPU1: DAG 97%
GPU1: DAG generated in 10.8 s (382.1 MB/s)
GPU1: Using v2 Ethash CUDA kernels (GeForce GTX 980 Ti)
Eth speed: 0.000 MH/s, shares: 0/0/0, time: 0:00
Eth: New job #7d2f9679 from ssl://us1.ethermine.org:5555; diff: 4000MH
CUDA error in CudaProgram.cu:465 : unknown error (999)
GPU1 search error: unknown error
Fatal error detected. Restarting.
Eth: New job #593be957 from ssl://us1.ethermine.org:5555; diff: 4000MH
can this be fixed?
January 12, 2021, 03:21:20 PM
Hi all,
I have 13 x RTX580 4GB cards, I can still have 5.4c version running, but the hashrate is no more than 9.3MHs per card. Is there any way to still use them or are they condemned to die?
Last year I was mining @ 31 per card, now is less than 1/3, is the power consumption also reduced towards 31MHs or it's still consuming the same but the result is 1/3 (9.3MHs) ?
I have 13 x RTX580 4GB cards, I can still have 5.4c version running, but the hashrate is no more than 9.3MHs per card. Is there any way to still use them or are they condemned to die?
Last year I was mining @ 31 per card, now is less than 1/3, is the power consumption also reduced towards 31MHs or it's still consuming the same but the result is 1/3 (9.3MHs) ?
580 with 4GB is done on the ETH.
You can try to mine ETC with full speed.
If You switch to Linux You will get around 20 MHs om ETH. Far better than 30 on ETC.
Performance on ETH will sink on each New epic though.
January 12, 2021, 03:16:48 PM
Hi all,
I have 13 x RTX580 4GB cards, I can still have 5.4c version running, but the hashrate is no more than 9.3MHs per card. Is there any way to still use them or are they condemned to die?
Last year I was mining @ 31 per card, now is less than 1/3, is the power consumption also reduced towards 31MHs or it's still consuming the same but the result is 1/3 (9.3MHs) ?
I have 13 x RTX580 4GB cards, I can still have 5.4c version running, but the hashrate is no more than 9.3MHs per card. Is there any way to still use them or are they condemned to die?
Last year I was mining @ 31 per card, now is less than 1/3, is the power consumption also reduced towards 31MHs or it's still consuming the same but the result is 1/3 (9.3MHs) ?
580 with 4GB is done on the ETH.
You can try to mine ETC with full speed.
If You switch to Linux You will get around 20 MHs om ETH. Far better than 30 on ETC.
Performance on ETH will sink on each New epoc though.
January 12, 2021, 01:33:40 PM
Hi all,
I have 13 x RTX580 4GB cards, I can still have 5.4c version running, but the hashrate is no more than 9.3MHs per card. Is there any way to still use them or are they condemned to die?
Last year I was mining @ 31 per card, now is less than 1/3, is the power consumption also reduced towards 31MHs or it's still consuming the same but the result is 1/3 (9.3MHs) ?
I have 13 x RTX580 4GB cards, I can still have 5.4c version running, but the hashrate is no more than 9.3MHs per card. Is there any way to still use them or are they condemned to die?
Last year I was mining @ 31 per card, now is less than 1/3, is the power consumption also reduced towards 31MHs or it's still consuming the same but the result is 1/3 (9.3MHs) ?
580 with 4GB is done on the ETH.
You can try to mine ETC with full speed.
January 12, 2021, 01:26:07 PM
Hi all,
I have 13 x RTX580 4GB cards, I can still have 5.4c version running, but the hashrate is no more than 9.3MHs per card. Is there any way to still use them or are they condemned to die?
Last year I was mining @ 31 per card, now is less than 1/3, is the power consumption also reduced towards 31MHs or it's still consuming the same but the result is 1/3 (9.3MHs) ?
I have 13 x RTX580 4GB cards, I can still have 5.4c version running, but the hashrate is no more than 9.3MHs per card. Is there any way to still use them or are they condemned to die?
Last year I was mining @ 31 per card, now is less than 1/3, is the power consumption also reduced towards 31MHs or it's still consuming the same but the result is 1/3 (9.3MHs) ?
Just let it die. DAG is over 4GB now so it's pretty surprising that they still are running at all.
January 12, 2021, 08:14:35 AM
A little feedback:
-dagrestart Restart the miner when allocating buffer for a new DAG epoch. The
possible values are: 0 - never, 1 - always, 2 - auto (the miner decides depending on the driver version).
This is relevant for 4 GB AMD cards, which may have problems with new DAG epochs after epoch 350.
This is good, but what we need is a -dagRunScript. Which of course, runs a script when a new DAG begins to build. Right now the 30 series works OK with the HiveOS "OC Delay" but we need to restart the miner when the new DAG hits to let HiveOS use it's OC Delay feature.
-dagrestart
possible values are: 0 - never, 1 - always, 2 - auto (the miner decides depending on the driver version).
This is relevant for 4 GB AMD cards, which may have problems with new DAG epochs after epoch 350.
This is good, but what we need is a -dagRunScript. Which of course, runs a script when a new DAG begins to build. Right now the 30 series works OK with the HiveOS "OC Delay" but we need to restart the miner when the new DAG hits to let HiveOS use it's OC Delay feature.
+1
January 12, 2021, 07:14:24 AM
Hello,
I use a Rig with Windows 10 update 20H2. 2 x AMD and 2x Nvidia Cards.
The AMD RX 570/580 with 8gb VRAM. But Phoenix Miner shows only 6,4gb VRAM.
Any idea?
Thanks.
I use a Rig with Windows 10 update 20H2. 2 x AMD and 2x Nvidia Cards.
The AMD RX 570/580 with 8gb VRAM. But Phoenix Miner shows only 6,4gb VRAM.
Quote
2021.01.10:11:56:39.114: main Phoenix Miner 5.3b Windows/msvc - Release build
2021.01.10:11:56:39.194: main CUDA version: 11.0, CUDA runtime: 8.0
2021.01.10:11:56:40.970: main OpenCL driver version: 19.12.x/20.1-3.x
2021.01.10:11:56:41.014: main Available GPUs for mining:
2021.01.10:11:56:41.014: main GPU1: Radeon RX 580 Series (pcie 1), OpenCL 2.0, 6.4 GB VRAM, 36 CUs
2021.01.10:11:56:41.014: main GPU2: GeForce GTX 1070 (pcie 3), CUDA cap. 6.1, 8 GB VRAM, 15 CUs
2021.01.10:11:56:41.014: main GPU3: GeForce GTX 1070 (pcie 4), CUDA cap. 6.1, 8 GB VRAM, 15 CUs
2021.01.10:11:56:41.014: main GPU4: Radeon RX 570 Series (pcie 5), OpenCL 2.0, 6.4 GB VRAM, 32 CUs
2021.01.10:11:56:41.014: main ADL library initialized
2021.01.10:11:56:41.024: main NVML library initialized
2021.01.10:11:56:41.059: main Nvidia driver version: 451.67
2021.01.10:11:56:43.320: main Eth: the pool list contains 1 pool (1 from command-line)
2021.01.10:11:56:43.320: main Eth: primary pool: eu2.ethermine.org:4444
2021.01.10:11:56:43.320: main Starting GPU mining
2021.01.10:11:56:43.320: main Matched GPU1 to ADL adapter index 8 (method 1)
2021.01.10:11:56:43.347: main GPU1: AMD driver 20.1.3
2021.01.10:11:56:43.347: main GPU1: Created ADL monitor for adapter 8; overdrive version: 7 (7)
2021.01.10:11:56:43.347: main GPU1: using AMD driver ver 20.1.3
2021.01.10:11:56:43.348: main Matched GPU4 to ADL adapter index 0 (method 1)
2021.01.10:11:56:43.381: main GPU4: AMD driver 20.1.3
2021.01.10:11:56:43.381: main GPU4: Created ADL monitor for adapter 0; overdrive version: 7 (7)
2021.01.10:11:56:43.381: main GPU4: using AMD driver ver 20.1.3
2021.01.10:11:56:43.516: wdog Starting watchdog thread
2021.01.10:11:56:43.517: main Eth: Connecting to ethash pool eu2.ethermine.org:4444 (proto: EthProxy)
2021.01.10:11:56:43.518: main GPU1: 37C 30% 6W, GPU2: 25C 30% 8W, GPU3: 27C 30% 8W, GPU4: 27C 30% 6W
2021.01.10:11:56:39.194: main CUDA version: 11.0, CUDA runtime: 8.0
2021.01.10:11:56:40.970: main OpenCL driver version: 19.12.x/20.1-3.x
2021.01.10:11:56:41.014: main Available GPUs for mining:
2021.01.10:11:56:41.014: main GPU1: Radeon RX 580 Series (pcie 1), OpenCL 2.0, 6.4 GB VRAM, 36 CUs
2021.01.10:11:56:41.014: main GPU2: GeForce GTX 1070 (pcie 3), CUDA cap. 6.1, 8 GB VRAM, 15 CUs
2021.01.10:11:56:41.014: main GPU3: GeForce GTX 1070 (pcie 4), CUDA cap. 6.1, 8 GB VRAM, 15 CUs
2021.01.10:11:56:41.014: main GPU4: Radeon RX 570 Series (pcie 5), OpenCL 2.0, 6.4 GB VRAM, 32 CUs
2021.01.10:11:56:41.014: main ADL library initialized
2021.01.10:11:56:41.024: main NVML library initialized
2021.01.10:11:56:41.059: main Nvidia driver version: 451.67
2021.01.10:11:56:43.320: main Eth: the pool list contains 1 pool (1 from command-line)
2021.01.10:11:56:43.320: main Eth: primary pool: eu2.ethermine.org:4444
2021.01.10:11:56:43.320: main Starting GPU mining
2021.01.10:11:56:43.320: main Matched GPU1 to ADL adapter index 8 (method 1)
2021.01.10:11:56:43.347: main GPU1: AMD driver 20.1.3
2021.01.10:11:56:43.347: main GPU1: Created ADL monitor for adapter 8; overdrive version: 7 (7)
2021.01.10:11:56:43.347: main GPU1: using AMD driver ver 20.1.3
2021.01.10:11:56:43.348: main Matched GPU4 to ADL adapter index 0 (method 1)
2021.01.10:11:56:43.381: main GPU4: AMD driver 20.1.3
2021.01.10:11:56:43.381: main GPU4: Created ADL monitor for adapter 0; overdrive version: 7 (7)
2021.01.10:11:56:43.381: main GPU4: using AMD driver ver 20.1.3
2021.01.10:11:56:43.516: wdog Starting watchdog thread
2021.01.10:11:56:43.517: main Eth: Connecting to ethash pool eu2.ethermine.org:4444 (proto: EthProxy)
2021.01.10:11:56:43.518: main GPU1: 37C 30% 6W, GPU2: 25C 30% 8W, GPU3: 27C 30% 8W, GPU4: 27C 30% 6W
Any idea?
Thanks.
update your amd driver to 20.11.2. I am on the same version of windows and that driver version works fine. Also update your miner to 5.4.c. Try the miner update first and then the driver next.
2021.01.12:01:07:03.890: main Phoenix Miner 5.4c Windows/msvc - Release build
2021.01.12:01:07:03.890: main Cmd line:
2021.01.12:01:07:03.890: main config.txt: -proto 3 -fret 5 -ftimeout 120 -ptimeout 5 -amd -gpus 123456 -gswin 30 -gsi 30 -tstop 80 -tstart 75 -gt 38,32,76,69,69,76 -vmr 25 -straps 1
2021.01.12:01:07:06.447: main OpenCL driver version: 20.11.2
2021.01.12:01:07:06.504: main Available GPUs for mining:
2021.01.12:01:07:06.504: main GPU1: Radeon RX 580 Series (pcie 1), OpenCL 2.0, 8 GB VRAM, 36 CUs
2021.01.12:01:07:06.504: main GPU2: Radeon RX 580 Series (pcie 2), OpenCL 2.0, 8 GB VRAM, 36 CUs
2021.01.12:01:07:06.504: main GPU3: Radeon RX 580 Series (pcie 4), OpenCL 2.0, 8 GB VRAM, 36 CUs
2021.01.12:01:07:06.504: main GPU4: Radeon RX 580 Series (pcie 6), OpenCL 2.0, 8 GB VRAM, 36 CUs
2021.01.12:01:07:06.504: main GPU5: Radeon RX 580 Series (pcie
, OpenCL 2.0, 8 GB VRAM, 36 CUs2021.01.12:01:07:06.504: main GPU6: Radeon RX 580 Series (pcie 9), OpenCL 2.0, 8 GB VRAM, 36 CUs
January 12, 2021, 07:09:18 AM
Where are download links ?
January 12, 2021, 02:07:00 AM
THANKS--
But that does not answer my question. I use Miner-Manager often, but it does not do anything to launch a miner. It will update a miner or add a new miner to the system.
It may take a system mod to do what I want. I want to launch and run PhoenixMiner as root. --scryptr
But that does not answer my question. I use Miner-Manager often, but it does not do anything to launch a miner. It will update a miner or add a new miner to the system.
It may take a system mod to do what I want. I want to launch and run PhoenixMiner as root. --scryptr
This might sound stupid but have you tried sudo and the start_miner.sh? or su and start_miner.sh?
DO YOU USE ETHOS? --
The ethOS system uses a "local.conf" file to configure the launch. Flags and OC options may be specified there. However, the system launches the miner and maintains statistics and logs. The super-user commands won't be recognized if placed in local.conf.
I could launch the miner with a "start.sh", but the system would not track the miner. I am hoping to find out how to modify the system launch in order to run the miner as root.
Thanks for answering. --scryptr
Jump to: