Bitcoin Forum
June 02, 2020, 12:28:13 PM *
News: Latest Bitcoin Core release: 0.19.1 [Torrent]
 
   Home   Help Search Login Register More  
Pages: « 1 ... 178 179 180 181 182 183 184 185 186 187 188 189 190 191 192 193 194 195 196 197 198 199 200 201 202 203 204 205 206 207 208 209 210 211 212 213 214 215 216 217 218 219 220 221 222 223 224 225 226 227 [228]
  Print  
Author Topic: PhoenixMiner 5.0b: fastest Ethereum/Ethash miner with lowest devfee (Win/Linux)  (Read 236386 times)
j2james
Newbie
*
Offline Offline

Activity: 65
Merit: 0


View Profile
May 29, 2020, 06:36:00 PM
 #4541

Hi @PhoenixMiner,

Which driver version you are recommend to use for GTX1080 on Windows 7?
1591100893
Hero Member
*
Offline Offline

Posts: 1591100893

View Profile Personal Message (Offline)

Ignore
1591100893
Reply with quote  #2

1591100893
Report to moderator
1591100893
Hero Member
*
Offline Offline

Posts: 1591100893

View Profile Personal Message (Offline)

Ignore
1591100893
Reply with quote  #2

1591100893
Report to moderator
Advertised sites are not endorsed by the Bitcoin Forum. They may be unsafe, untrustworthy, or illegal in your jurisdiction. Advertise here.
1591100893
Hero Member
*
Offline Offline

Posts: 1591100893

View Profile Personal Message (Offline)

Ignore
1591100893
Reply with quote  #2

1591100893
Report to moderator
1591100893
Hero Member
*
Offline Offline

Posts: 1591100893

View Profile Personal Message (Offline)

Ignore
1591100893
Reply with quote  #2

1591100893
Report to moderator
zhihao4456
Newbie
*
Offline Offline

Activity: 15
Merit: 1


View Profile
May 30, 2020, 04:52:46 AM
 #4542

Is there a way to apply custom timing like in Claymore, with "-strap" ?
I'm looking to switch from Claymore and this strap thing is the only thing that's holding me.
You should use AMD Memory Tweak (https://github.com/Eliovp/amdmemorytweak binaries are here compiled by me: https://drive.google.com/open?id=1sgYugFgFq5Ja89DexDvwgvP1dtRO2d7A) and you will 100% sure get 1.0%-1.5% more hashrate than Claymore.

Unzip WinAMDTweak.zip to some folder XXX. Run Claymore with your best settings. After that run a command prompt window with Administrative privileges, navigate to WinAMDTweak.zip unzipped folder XXX using 'cd XXX' command and after that run:

WinAMDTweak.exe --current



You will see the current setting of Claymore. Something like this:
https://www.cryptoprofi.info/wp-content/uploads/2019/04/word-image-49.png

Copy/Paste them down in text file.
After that stop Claymore. Run WinAMDTweak.exe --...  with these settings and run Phoenixminer.exe after that with the  same -cclock -mclock -cvddc -mvddc parameters like Claymore.

If you have NVidia GPUs using -strap option leave them with Claymore using Claymore's -di option, and run Phoenix miner with all other AMD GPUs using PhoenixMiner's -gpus option. For example: 'PhoenixMiner.exe -gpus 135' will run PM on your first, third and fifth GPU. The GPU index starts from 1 not from 0 in PM and from zero not from 1 in Claymore.


Another more simple way (that works on Nvidia too) without WinAMDTweak.exe is to run Claymore (don't stop during mining) with your best settings, pause all the GPUs (by pressing the number keys from '0' to '9' or 'p' for all) and run Phoenixminer.

wow, thanks for the tips on opening Claymore and then Phoenix. Now i can use the strap and run PhoenixMiner on my nvidia cards

if this method works, i think in the future Phoenix miner can implement the strap too for nvidia cards
PhoenixMiner
Member
**
Offline Offline

Activity: 245
Merit: 18


View Profile
May 30, 2020, 05:41:04 AM
 #4543

Miner didn't support new AMD 20.5.1 driver.
  We are testing with the new driver and will release 5.0c soon that will support it. So far it seems that it behaves as the "good" drivers - i.e. allows mining until DAG epoch 373 on 4 GB cards.


20.4.2 had mem clock problems with navi.Pls someone recommend driver for both navi and polaris cards without anybug.19.11.3 no problems but not recommend PM devs.
  Please note that in the latest drivers the memory clocks of Navi cards are shown as double the value from the previous drivers. If you have used -mclock 950 in the older drivers, in the latest driver you must use -mclock 1900. In order to check if this is the case, run the miner without -mclock but with -hstats 2 and see the nominal memory clocks then use the appropriate -mclock value.

Hi @PhoenixMiner,

Which driver version you are recommend to use for GTX1080 on Windows 7?
   We don't test on Windows 7 anymore but probably older driver will be better as neither 1080 nor Windows 7 are spring chickens Wink One thing to be aware of is that some users have reported low speed (like 50% lower than normal) with Nvidia cards on Windows 7, which can only be fixed by increasing the physical RAM (i.e. the DIMM module(s) on the motherboard!) to at least 8 GB. Strangely enough, increasing the page file size does not help - apparently some kind of driver bug. There is no such problem on Windows 10.
UnclWish
Sr. Member
****
Offline Offline

Activity: 1120
Merit: 253


View Profile
May 30, 2020, 06:59:05 AM
 #4544

Miner didn't support new AMD 20.5.1 driver.
  We are testing with the new driver and will release 5.0c soon that will support it. So far it seems that it behaves as the "good" drivers - i.e. allows mining until DAG epoch 373 on 4 GB cards.
Thanks for info! Will waiting update.
bategojko74
Jr. Member
*
Offline Offline

Activity: 138
Merit: 4


View Profile
May 30, 2020, 09:47:24 AM
Last edit: May 30, 2020, 10:56:02 AM by bategojko74
 #4545

Miner didn't support new AMD 20.5.1 driver.
  We are testing with the new driver and will release 5.0c soon that will support it. So far it seems that it behaves as the "good" drivers - i.e. allows mining until DAG epoch 373 on 4 GB cards.


20.4.2 had mem clock problems with navi.Pls someone recommend driver for both navi and polaris cards without anybug.19.11.3 no problems but not recommend PM devs.
  Please note that in the latest drivers the memory clocks of Navi cards are shown as double the value from the previous drivers. If you have used -mclock 950 in the older drivers, in the latest driver you must use -mclock 1900. In order to check if this is the case, run the miner without -mclock but with -hstats 2 and see the nominal memory clocks then use the appropriate -mclock value.
Upgraded -mclock 900 (19.8.2 drivers) to -mclock 1800 (20.5.1 drivers) and my Navi cards work like a charm.
bategojko74
Jr. Member
*
Offline Offline

Activity: 138
Merit: 4


View Profile
May 30, 2020, 10:49:49 AM
 #4546

Miner didn't support new AMD 20.5.1 driver.
  We are testing with the new driver and will release 5.0c soon that will support it. So far it seems that it behaves as the "good" drivers - i.e. allows mining until DAG epoch 373 on 4 GB cards.
Thanks for info! Will waiting update.
If you put 4GB AMD card on PCI-E X 16 slot with 20.4.2 and older drivers it can even mine after 373 epoch having the hashrate gradually falling (25 MH/S for epoch 380, 22MH/S for epoch 400, 15.7 MH/s for epoch 410, 12 MH/s for epoch 420) as opposed to Claymore who stops at epoch 353 and advises me to go mining another coin.
nikqz
Newbie
*
Offline Offline

Activity: 12
Merit: 0


View Profile
May 30, 2020, 01:29:40 PM
 #4547

hi
How to make sure that when reaching for example 62 degrees, the mining intensity decreases so as not to exceed the temperature threshold. What commands to put in a batch file. Driver version 19.7.5 mining 5.0b (my current settings, but on them the temperature continues to rise and above 62 degrees without reducing the intensity of mining -tt 61 -tstop 67 -tstart 50 -tmax 62 -fcm (0 or 2) -fanmin 50)
Permonik
Member
**
Offline Offline

Activity: 198
Merit: 10


View Profile
May 31, 2020, 02:31:52 PM
 #4548

Hello,
Which driver is recomanded for Radeon VII?
THX
jgonzi
Newbie
*
Offline Offline

Activity: 20
Merit: 0


View Profile
May 31, 2020, 04:03:26 PM
 #4549

Hi @PhoenixMiner,

Which driver version you are recommend to use for GTX1080 on Windows 7?

442.59 WHQL
mollov
Newbie
*
Offline Offline

Activity: 3
Merit: 0


View Profile
June 01, 2020, 10:15:18 AM
 #4550

I'm having problem with dag350 and generating it... used -dagrestart 2 (and 1) but if the miner starts to generate this dag, the phoenix miner crashes... 4GB RX580, Win 10, 8 card rig, using the onboard video for windows 2D...

I'm using the Blockchain drivers (working no problems until now)... could the problem be with the driver?
soldat9011
Newbie
*
Offline Offline

Activity: 2
Merit: 0


View Profile
June 01, 2020, 10:26:27 AM
 #4551

I'm having problem with dag350 and generating it... used -dagrestart 2 (and 1) but if the miner starts to generate this dag, the phoenix miner crashes... 4GB RX580, Win 10, 8 card rig, using the onboard video for windows 2D...

I'm using the Blockchain drivers (working no problems until now)... could the problem be with the driver?
I have the same problem! Stops working on AMD 4GB!
PhoenixMiner
Member
**
Offline Offline

Activity: 245
Merit: 18


View Profile
June 01, 2020, 11:28:42 AM
 #4552

I'm having problem with dag350 and generating it... used -dagrestart 2 (and 1) but if the miner starts to generate this dag, the phoenix miner crashes... 4GB RX580, Win 10, 8 card rig, using the onboard video for windows 2D...

I'm using the Blockchain drivers (working no problems until now)... could the problem be with the driver?
   Blockchain drivers are too old - we haven't tested with them but it is likely that the problem is caused by them. See this post for the recommended driver versions for 4 GB AMD cards: https://bitcointalk.org/index.php?topic=2647654.msg54502449#msg54502449


hi
How to make sure that when reaching for example 62 degrees, the mining intensity decreases so as not to exceed the temperature threshold. What commands to put in a batch file. Driver version 19.7.5 mining 5.0b (my current settings, but on them the temperature continues to rise and above 62 degrees without reducing the intensity of mining -tt 61 -tstop 67 -tstart 50 -tmax 62 -fcm (0 or 2) -fanmin 50)
  There is no such feature (reducing mining intensity to keep the temperature in check). You should use -tmax, which lowers the GPU core clocks when it reaches the target temperature. If it doesn't work, try a newer driver version (e.g. 2.4.2) and if still doesn't work, let us know what cards you are using.
PhoenixMiner
Member
**
Offline Offline

Activity: 245
Merit: 18


View Profile
June 01, 2020, 11:31:47 AM
 #4553

IMPORTANT!  ETC is already at DAG epoch 350, so you must use PhoenixMiner 5.0b or later if you have 4 GB AMD cards. Additionally, here are some important tips for longest possible usage of 4 GB AMD cards with PhoenixMiner 5.0b:

  • 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).
  • Drivers older than 18.1.1 were not tested for 4 GB DAG operation.

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.
j2james
Newbie
*
Offline Offline

Activity: 65
Merit: 0


View Profile
June 01, 2020, 11:38:20 AM
 #4554

Hi @PhoenixMiner,

Which driver version you are recommend to use for GTX1080 on Windows 7?
   We don't test on Windows 7 anymore but probably older driver will be better as neither 1080 nor Windows 7 are spring chickens Wink One thing to be aware of is that some users have reported low speed (like 50% lower than normal) with Nvidia cards on Windows 7, which can only be fixed by increasing the physical RAM (i.e. the DIMM module(s) on the motherboard!) to at least 8 GB. Strangely enough, increasing the page file size does not help - apparently some kind of driver bug. There is no such problem on Windows 10.

Thanks and I'm sorry. I wanted to as about drivers for GTX1070 on Win 7. I have 8GB physical RAM (2 * 4GB DIMM). But basing on your answer I think it does not matter in acase of Win 7 if I use 1070 or 1080. I have problem that my mining speed decreased and decreased each time. Only power limit increasing fixes it, but it costs additional electricity. If I will use win 10 I will not have these problems? Or may be it will be better to use HIVE OS (If in any case I should install other OS instead of Win 7)?
soldat9011
Newbie
*
Offline Offline

Activity: 2
Merit: 0


View Profile
June 01, 2020, 02:48:27 PM
 #4555

IMPORTANT!  ETC is already at DAG epoch 350, so you must use PhoenixMiner 5.0b or later if you have 4 GB AMD cards. Additionally, here are some important tips for longest possible usage of 4 GB AMD cards with PhoenixMiner 5.0b:

  • 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).
  • Drivers older than 18.1.1 were not tested for 4 GB DAG operation.

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.
Thanks for the clarification! Installed the latest driver and it worked!
PhoenixMiner
Member
**
Offline Offline

Activity: 245
Merit: 18


View Profile
Today at 06:12:07 AM
 #4556

Thanks and I'm sorry. I wanted to as about drivers for GTX1070 on Win 7. I have 8GB physical RAM (2 * 4GB DIMM). But basing on your answer I think it does not matter in acase of Win 7 if I use 1070 or 1080. I have problem that my mining speed decreased and decreased each time. Only power limit increasing fixes it, but it costs additional electricity. If I will use win 10 I will not have these problems? Or may be it will be better to use HIVE OS (If in any case I should install other OS instead of Win 7)?

   No, unfortunately the same problem is present in Windows 10 and Linux. Unless Nvidia solves it at driver level (e.g. increase the size of memory pages like AMD did with Polaris), which is highly unlikely, there is no fix for this problem.


Thanks for the clarification! Installed the latest driver and it worked!
   
   Note that you can use the latest supported by PhoenixMiner Windows driver, which is 20.4.2 for PhoenixMiner 5.0b. The new driver 20.5.1 won't work with PhoenixMiner 5.0b and 4 GB AMD card.

PhoenixMiner
Member
**
Offline Offline

Activity: 245
Merit: 18


View Profile
Today at 06:16:51 AM
 #4557

There is a new version, which is a minor update with support for the latest AMD Windows driver. You can download PhoenixMiner 5.0c from here:

https://mega.nz/folder/qJsRCByR#ddQWqxm4Re6UC1Zdp-ncTg  (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.0c_Windows.zip
    ===================================
   SHA-1: ef3158ffb1071abbbde0091fc18e03eec5823d8e
 SHA-256: b95bd34653877f1b664ba897369ee5663298dbdd837377528201966371b03c6f
 SHA-512: be775ef9dd552f82b07f74ebceaa6804f3f7f16f32fed21a6971a24b8e6534d6ec82cedf17d3433936e6f69ef0887014a5cfb6fd9869adaeeaf9ed7505c6e14c

    File: PhoenixMiner_5.0c_Linux.tar.gz
    ====================================
   SHA-1: e41b6eb9da7e5bdb68eb153dbe846ac7ab765395
 SHA-256: 1f21303b2d7f0e939c3867067a9daeacec9157efec7c4362d0a433481f489b5d
 SHA-512: 994069ccec68fda53e1c04e6ac4133b0d5f31719ec359d271dc3ce03b156217ba0522126a35bf8d46b3317a2be1cdb256e30a569056df37718c0639645c3a8cc

    File: PhoenixMiner_NVRTC_Windows.zip
    ====================================
   SHA-1: ff6fa5e018adbd52caf631c42b7c2fac7ce48a51
 SHA-256: 8087757169405d51ea8ba818347fb05d0450aef985c29272165070346eb5a54a
 SHA-512: 7b2d832f7f40578bb1f501d5174467f5ae06612e601dab769fd56d39da48a471b18c6373435a485155f70fec4017d8378797bf1e1dfe5d62fee30fa6a1d992c4

The new features in this release are:

  • Added support for latest AMD Windows driver 20.5.1
  • Added SO_REUSEPORT option on the remote control port (default 3333) under Linux to prevent problems when the miner is restarting

There is no need to update to 5.0c unless you want to run AMD Windows drivers 20.5.1, or need the small improvement for the Linux version. Please let us know if you have any problems or questions related to PhoenixMiner 5.0c.
djzmei
Newbie
*
Offline Offline

Activity: 17
Merit: 0


View Profile
Today at 07:03:30 AM
 #4558

Hi, I have the following problem.
I put Phoenix Miner 5.0b, I run the bat file which is ready inside and it leaves without a problem.
I replace it with my data and when I release it when it reaches the moment to generate the cache miner crash.
Broomey
Newbie
*
Offline Offline

Activity: 4
Merit: 0


View Profile
Today at 09:57:22 AM
 #4559

I just hope Phoenix Miner can keep up the good work and keep finding ways to mine with our 4gb cards.. big thumbs up to Phoenix Miner and an even bigger thumbs up to the team at PiMP (www.getpimp.org) for getting the latest 5.0b version into their mining OS literally minutes after it's release! Definitely keep PiMP'in !! Smiley  Was a totally hassle-free and simple update from a miners point of view. Just lovin PiMP! (and Phoenix Miner Wink )
Match made for hashing.
Thanks.
Pages: « 1 ... 178 179 180 181 182 183 184 185 186 187 188 189 190 191 192 193 194 195 196 197 198 199 200 201 202 203 204 205 206 207 208 209 210 211 212 213 214 215 216 217 218 219 220 221 222 223 224 225 226 227 [228]
  Print  
 
Jump to:  

Sponsored by , a Bitcoin-accepting VPN.
Powered by MySQL Powered by PHP Powered by SMF 1.1.19 | SMF © 2006-2009, Simple Machines Valid XHTML 1.0! Valid CSS!