 Show Posts
|
|
Pages: « 1 [2] 3 4 5 »
|
AMD released 20.8.2 driver. I checked it - PM support it. OpenCL still from 20.7.1.
So 20.8.2 can be installed without any difference with 20.7.1 drivers.
i would stick to 20.4.2 drivers for a while.. (very very very stable) |
|
|
|
hi guys, need help here with P104 gpus Unable to set -straps  "Added new parameter -nvmem to force using straps even on unsupported Nvidia GPUs (use -nvmem 1 for GDDR5 cards, or -nvmem 2 for GDDR5X cards)" It works ! however any idea for -vmt1,2,3 setting? |
|
|
|
hi guys, need help here with P104 gpus Unable to set -straps |
|
|
|
msiafterburner dont work with amd new drivers for win10?how can overclock them?
same here... |
|
|
|
can you mix nvidia and amd cards with this miner?
yes |
|
|
|
Yes ,my P106 doing good with Claymore, But if DAG reaches 384, we still have to give up claymore, So i tried to use Phoenix Miner  It depends, if your p106 is 4gb and you are on windows then it should have stopped mining already on claymore. I have a feeling your p106-100 are all 6gb, i might be wrong. I think in china there was a 4gb version. mine all 6GB  |
|
|
|
When initializing, i noticed the following errors. Using P106-100 6GB Card, Using NVIDIA drivers 399.24,Using Phoenix Miner 5.1c Windows 10 GPU0:unable to set straps - unsupported GPU 00000000 GPU1:unable to set straps - unsupported GPU 00000000 GPU2:unable to set straps - unsupported GPU 00000000 GPU3:unable to set straps - unsupported GPU 00000000 GPU4:unable to set straps - unsupported GPU 00000000 GPU5:unable to set straps - unsupported GPU 00000000 GPU6:unable to set straps - unsupported GPU 00000000 GPU7:unable to set straps - unsupported GPU 00000000 It seems that straps does not support P106-100 6GB Card  Hi. my P106 still doing good with Claymore. So I remain .. Straps all working fine |
|
|
|
AMD driver 20.8.1 is supported by PM. I just installed it. PM recognized it like 20.7.1 and works.
One issue is MSI Afterburner voltage adjustment won't work after setting the display to onboard intel display... also the MSI Afterburner Fan Target Temp won't work... It's not driver issue, it's Afterburner problem... hope we will see an update |
|
|
|
AMD driver 20.8.1 is supported by PM. I just installed it. PM recognized it like 20.7.1 and works.
One issue is MSI Afterburner voltage adjustment won't work after setting the display to onboard intel display... also the MSI Afterburner Fan Target Temp won't work... |
|
|
|
20.4.2 i confirm is good ! Thanks !
I'm about epoch, that you asked. 372-373. so you mean we can mine ETH at full speed till EPOCH 372-373 ? however, I saw this at Phoenix Miner start up 2020.08.05:20:44:19.538: GPU1 Light cache generated in 3.8 s (15.7 MB/s) 2020.08.05:20:44:20.646: GPU1 GPU1: Free VRAM: 3.948 GB; used: 0.052 GB 2020.08.05:20:44:20.646: GPU1 GPU1: Allocating DAG (3.77) GB; good for epoch up to # 3552020.08.05:20:44:20.726: GPU1 GPU1: Generating DAG for epoch #353 It's not maximum. It's miner reserve 3.77Gb vmem and this used mem can be used up to 355 epoch just in this session. so you mean I still have lots of room for ETH till November ? hahah ! See Free VRAM: 3.948 GB; used: 0.052 GB message above Sure. 3.948GB - 3.77GB = 178MB headroom left..good  |
|
|
|
20.4.2 i confirm is good ! Thanks !
I'm about epoch, that you asked. 372-373. so you mean we can mine ETH at full speed till EPOCH 372-373 ? however, I saw this at Phoenix Miner start up 2020.08.05:20:44:19.538: GPU1 Light cache generated in 3.8 s (15.7 MB/s) 2020.08.05:20:44:20.646: GPU1 GPU1: Free VRAM: 3.948 GB; used: 0.052 GB 2020.08.05:20:44:20.646: GPU1 GPU1: Allocating DAG (3.77) GB; good for epoch up to # 3552020.08.05:20:44:20.726: GPU1 GPU1: Generating DAG for epoch #353 It's not maximum. It's miner reserve 3.77Gb vmem and this used mem can be used up to 355 epoch just in this session. so you mean I still have lots of room for ETH till November ? hahah ! See Free VRAM: 3.948 GB; used: 0.052 GB message above |
|
|
|
20.4.2 i confirm is good ! Thanks !
I'm about epoch, that you asked. 372-373. so you mean we can mine ETH at full speed till EPOCH 372-373 ? however, I saw this at Phoenix Miner start up 2020.08.05:20:44:19.538: GPU1 Light cache generated in 3.8 s (15.7 MB/s) 2020.08.05:20:44:20.646: GPU1 GPU1: Free VRAM: 3.948 GB; used: 0.052 GB 2020.08.05:20:44:20.646: GPU1 GPU1: Allocating DAG (3.77) GB; good for epoch up to # 3552020.08.05:20:44:20.726: GPU1 GPU1: Generating DAG for epoch #353 |
|
|
|
which driver is best for phoenix and give hashrate more than claymore in win10?
Hashrate is the same on Win10 at any drivers. You can use f.e. 20.4.2. More than Claymore you can recieve only if you use PM with AMD Memory tweak tool to set REF parameter, cause PM didn't have -rxboost parameter. Hi ! my issue with slowest hashrate for the last gpu fixed using 20.4.2 ! however, i would like to know how much longer can we mine ETH using 4GB cards ? I am using Sapphire RX470 4GB hashrate looks ok for now.. But the Phoenix miner say "good for EPOCH up to 355"  Read carefully "Good drivers". Let us reprint the important message from the first post about the mining after DAG epoch 350: IMPORTANT! All owners of AMD cards with 4 GB RAM must upgrade to PhoenixMiner 5.0e or later version to continue mining after DAG epoch 350 (both ETH and ETC has already passed DAG epoch 350). Additionally, here are some important tips for longest possible usage of 4 GB AMD cards with PhoenixMiner 5.0e and later: - If your rig is using Intel CPU, use the integrated graphics as primary display adapter. To do this, go to motherboard's BIOS setup and change the "Primary display adapter" to iGPU (or integrated GPU). Also, if you are using actual monitor or HDMI plug, put it in the motherboard video output.
- If you can't use integrated GPU, replace the primary GPU with one with 6 or 8 GB VRAM.
- Do not upgrade to a new AMD driver unless it is explicitly supported by PhoenixMiner. With 4 GB AMD cards, this will not only lower your hashrate but it will make impossible to mine when the DAG epoch is above 350.
- After the DAG epoch becomes more than 350, the optimal -gt value for the 4 GB AMD cards may change. So, we recommend to run auto-tune again after DAG epoch 350 to find the best GT values for the cards.
After extensive testing of AMD Windows drivers for the last two years or so, we identified two broad groups of drivers: - Good drivers. These are versions from 18.12.1.1 to 19.7.5 (inclusive), and from 19.12.2 to 20.4.2 (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).
- If you are using a pool with automatic switching between the coins (like nicehash for example), you should use one of the good drivers above, and shouldn't use the -dagrestart option.
- Drivers older than 18.1.1 were not tested for 4 GB DAG operation. Specifically, there are multiple reports that the old blockchain drivers from 2017 doesn't work with 4 GB cards beyond epoch 350. If you are still using the blockchain drivers, you must upgrade to newer drivers if you have 4 GB AMD cards. After that, do not forget to turn on the Compute mode for all cards in AMD control center.
Under Linux all relatively recent drivers (i.e. last 24-36 months) allow mining until epoch 378-380 but there are much more driver bugs, so if you are happy with your current driver version, do not change it. Please note that the usage of 4 GB AMD cards on Windows 7 is problematic, because the blockchain driver from 2017 doesn't seem to work properly with big DAGs, and the newer drivers do not support turning on the compute mode. There are some possible workarounds with patched/hacked drivers but we haven't tested them and can't tell you how to do it. 20.4.2 i confirm is good ! Thanks ! |
|
|
|
which driver is best for phoenix and give hashrate more than claymore in win10?
Hashrate is the same on Win10 at any drivers. You can use f.e. 20.4.2. More than Claymore you can recieve only if you use PM with AMD Memory tweak tool to set REF parameter, cause PM didn't have -rxboost parameter. Hi ! my issue with slowest hashrate for the last gpu fixed using 20.4.2 ! however, i would like to know how much longer can we mine ETH using 4GB cards ? I am using Sapphire RX470 4GB hashrate looks ok for now.. But the Phoenix miner say "good for EPOCH up to 355" |
|
|
|
Hey guys. My two miners crashed at night with error:
POSIX win threads for windows stopped working
KAwpow WIN10 470 cards
How to fix?
Same here !!!!!!! |
|
|
|
 guys, wonder what causes this ? |
|
|
|
Set to -mt 0 now all cards are same hashrate !!!! however the speed is slower ...  All cards drawing the same power Looks like drivers bug. mt parameter set timings for memory: 0 - default VBIOS values; 1 - faster timings; 2 - fastest timings. These timings provided by drivers as i know. Try to install other drivers. F.e. 20.4.2. ok i will try 20.4.2 (hopefully this is the most stable driver for Phoenix Miner) |
|
|
|
Set to -mt 0 now all cards are same hashrate !!!! however the speed is slower ... All cards drawing the same power |
|
|
|
now running only the last GPU.. still same issue !  What operating system? Drivers version? What are the full launch options? Hi, I am using Windows 10 64bit, Driver 19.4.3
timeout 5
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 100
PhoenixMiner.exe -pool asia1.ethermine.org:4444 -pool2 us1.ethermine.org:4444 -wal wallet.rig -proto 3 -acm -pass x -lidag 1 -wdog 0 -hstats 2 -tt 75 -mt 1 -cvddc 875 -mvddc 875 -cclock 1025 -mclock 2025
Cards identical? Have the same video memory manufacter? Yes, All the same cards & memory... It just always happen at the last gpu.. Other miners have the same speed drop on last card? Before this, I tried Claymore V15.. all good !  |
|
|
|
now running only the last GPU.. still same issue ! What operating system? Drivers version? What are the full launch options? Hi, I am using Windows 10 64bit, Driver 19.4.3
timeout 5
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 100
PhoenixMiner.exe -pool asia1.ethermine.org:4444 -pool2 us1.ethermine.org:4444 -wal wallet.rig -proto 3 -acm -pass x -lidag 1 -wdog 0 -hstats 2 -tt 75 -mt 1 -cvddc 875 -mvddc 875 -cclock 1025 -mclock 2025
Cards identical? Have the same video memory manufacter? Yes, All the same cards & memory... It just always happen at the last gpu.. |
|
|
|
|
