PhoenixMiner 2.6 is officially released. In addition to what was included in 2.6b, we have added monitoring of the main thread by the watchdog to catch some rare cases when the main thread freezes but the GPU threads continue.
We are switching our attention to 2.7, which should include the initial support for hardware control, direct support for mining some new coins (Akroma, VIC, and Whalecoin), as well as some other new features. We are also working on a completely new share processing code path that aims to lower the probability for stale shares even more but as it uses completely different approach than the current code, it may not be stable enough to be included in 2.7.
Topic: PhoenixMiner 6.2c: fastest Ethereum/Ethash miner with lowest devfee (Win/Linux) - page 482. (Read 784985 times)
February 04, 2018, 10:23:26 AM
February 04, 2018, 08:52:45 AM
when i am opening .bat file the miner starts and closes automatically, i have read readme.txt and all miner options are set as mentioned.here is my .bat file
can anyone help me what is the problem about?
can anyone help me what is the problem about?
If you arent seeing an error, dont turn logging off and look in the log file .. it will be hard for anyone to help if you have no error or warnings.
February 04, 2018, 07:23:00 AM
Running 2.6 with no issues on two RX570 rigs. All default settings with 18.x drivers. I get 2-4% stales (closer to 2 most the time). I think that is pretty normal.
February 04, 2018, 07:04:31 AM
Please try using the command line option -mi with different values (for example 8, or 9 instead of the default value of 10). You can change it only for the RX560s by using it like this:
In the above example the first two cards will run with mining intensity 8, and the other three - with mining intensity 10. This assumes that the RX560s are the first and the second card and you have five cards in the rig. The order of the cards must be the same that is listed by PhoenixMiner when starting up.
Didn't change much, still dropping hashrate. Code:
-mi 8,8,10,10,10
Running on Windows 10 Pro 1709 with AMD Drivers 17.12.2 (18.x+ is unstable right now).
February 04, 2018, 06:05:48 AM
40 hours straight up! No disruptions, no downtime, runs flawlessly!!! Avg pool speed 157mh/s for 5x rx580s! Thats insane!
February 04, 2018, 04:36:50 AM
Great miner!!!! I'm using it for a week and not a single problem! Keep up the good work!! THX!
February 04, 2018, 03:30:44 AM
when i am opening .bat file the miner starts and closes automatically, i have read readme.txt and all miner options are set as mentioned.here is my .bat file
timeout 10
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
timeout 5
PhoenixMiner.exe -pool eu1-etc.ethermine.org:4444 -wal 1d4feb6e2e33913a461889fe9391b2b1ca08d55f.7X570 -coin etc -amd -wdog 1 -minRigSpeed 195 -rmode 2 -log 0 -v -cdm 0
i am using amd latest driver and latest windows 10 os and amd rx570 4gb gpuX7
i have no problem with claymore 10.6.i am getting problem with phoenix 2.5d miner.
can anyone help me what is the problem about?
thankyou.
timeout 10
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
timeout 5
PhoenixMiner.exe -pool eu1-etc.ethermine.org:4444 -wal 1d4feb6e2e33913a461889fe9391b2b1ca08d55f.7X570 -coin etc -amd -wdog 1 -minRigSpeed 195 -rmode 2 -log 0 -v -cdm 0
i am using amd latest driver and latest windows 10 os and amd rx570 4gb gpuX7
i have no problem with claymore 10.6.i am getting problem with phoenix 2.5d miner.
can anyone help me what is the problem about?
thankyou.
Is bat in same folder? I don't see a cd\ line to change directory.
Lot of commands there. Going from memory and maybe wrong but isn't it -minspeed?
Also, -v with no argument. I maybe wrong again as I'm on phone but shouldn't v have a value?
Overall, go to last line, blank line and type in pause. Then cmd won't close on you and you can read what the issue is.
You can remove the timeouts, no reason to slow it down. Pause is priceless though. Hope this helps.
February 03, 2018, 10:48:01 PM
10hrs isnt enough.
i get no devfee errors. been running about 3 days straight at this point. on an 8GPU rig making 228MH/s
try adding "-coin eth" to your startup bat file
i get no devfee errors. been running about 3 days straight at this point. on an 8GPU rig making 228MH/s
try adding "-coin eth" to your startup bat file
is there any power difference in your previous miner and phoenix miner?
February 03, 2018, 10:45:14 PM
when i am opening .bat file the miner starts and closes automatically, i have read readme.txt and all miner options are set as mentioned.here is my .bat file
timeout 10
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
timeout 5
PhoenixMiner.exe -pool eu1-etc.ethermine.org:4444 -wal 1d4feb6e2e33913a461889fe9391b2b1ca08d55f.7X570 -coin etc -amd -wdog 1 -minRigSpeed 195 -rmode 2 -log 0 -v -cdm 0
i am using amd latest driver and latest windows 10 os and amd rx570 4gb gpuX7
i have no problem with claymore 10.6.i am getting problem with phoenix 2.5d miner.
can anyone help me what is the problem about?
thankyou.
timeout 10
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
timeout 5
PhoenixMiner.exe -pool eu1-etc.ethermine.org:4444 -wal 1d4feb6e2e33913a461889fe9391b2b1ca08d55f.7X570 -coin etc -amd -wdog 1 -minRigSpeed 195 -rmode 2 -log 0 -v -cdm 0
i am using amd latest driver and latest windows 10 os and amd rx570 4gb gpuX7
i have no problem with claymore 10.6.i am getting problem with phoenix 2.5d miner.
can anyone help me what is the problem about?
thankyou.
February 03, 2018, 07:31:11 PM
phoenix crashed at 10.5 hrs so that why I used that mark LOL
What happens is a GPU hangs and drops to 0 in DEVFEE then when it trys to go back to regular it doesn't recognize it needs to restart and it will get stuck in DEVFEE and issue incorrect shares by all GPUs. Its happened at 10.5 hrs, its happened at 1.5 hrs and even at like 4 hours. Otherwise I haven't had any issues with phoenix it's been stable if I didn't have the DEVFEE issue.
What happens is a GPU hangs and drops to 0 in DEVFEE then when it trys to go back to regular it doesn't recognize it needs to restart and it will get stuck in DEVFEE and issue incorrect shares by all GPUs. Its happened at 10.5 hrs, its happened at 1.5 hrs and even at like 4 hours. Otherwise I haven't had any issues with phoenix it's been stable if I didn't have the DEVFEE issue.
I forgot to ask- what version are you running? I tried 2.4, 2.5 and 2.6B. I was having the best luck on 2.4 but all 3 do the DEVFEE issue for me unfortunately. I tried 2.6 today thinking it might not happen but it did
February 03, 2018, 07:17:40 PM
phoenix crashed at 10.5 hrs so that why I used that mark LOL
What happens is a GPU hangs and drops to 0 in DEVFEE then when it trys to go back to regular it doesn't recognize it needs to restart and it will get stuck in DEVFEE and issue incorrect shares by all GPUs. Its happened at 10.5 hrs, its happened at 1.5 hrs and even at like 4 hours. Otherwise I haven't had any issues with phoenix it's been stable if I didn't have the DEVFEE issue.
What happens is a GPU hangs and drops to 0 in DEVFEE then when it trys to go back to regular it doesn't recognize it needs to restart and it will get stuck in DEVFEE and issue incorrect shares by all GPUs. Its happened at 10.5 hrs, its happened at 1.5 hrs and even at like 4 hours. Otherwise I haven't had any issues with phoenix it's been stable if I didn't have the DEVFEE issue.
February 03, 2018, 05:55:07 PM
10hrs isnt enough.
i get no devfee errors. been running about 3 days straight at this point. on an 8GPU rig making 228MH/s
try adding "-coin eth" to your startup bat file
i get no devfee errors. been running about 3 days straight at this point. on an 8GPU rig making 228MH/s
try adding "-coin eth" to your startup bat file
February 03, 2018, 05:50:38 PM
pool average fluctuates a lot but overall average is about 1-2% better on phoenix than running claymore, hashrate doesnt matter, accepted shares do, which is why i based my comparison on that number.
other differences are that phoenix doesnt have any fan control or clock/voltage modification where claymore does, and on my rig, even though i see more hashrate with pheonix, i see 10-20W more power consumption as well.
Over a 10 hour period I had 100 more shares on Phoenix. Granted that can be luck or it can be the program. I get about 5 more hash then claymore. Claymores reported is also 2 m/hs lower at the pool then what is reported in the program. Phoenix follows the reported on the miner right through to the pool. However I keep getting devfee errors and have to resort back to claymore until it's resolved. It keeps hanging up after a couple of ETH shares are found on Phoenix.
February 03, 2018, 05:29:19 PM
im also a little confused about the counts of shares submitted.
for about 225MH/s
claymore/phoenix reports submitting shares at a rate of about 78-80 shares/hr
but nanopool is seeing about 2x that number of shares at about 170 shares/hr
yet still seeing and calculating the same hashrate. can anyone explain this discrepancy?
for about 225MH/s
claymore/phoenix reports submitting shares at a rate of about 78-80 shares/hr
but nanopool is seeing about 2x that number of shares at about 170 shares/hr
yet still seeing and calculating the same hashrate. can anyone explain this discrepancy?
What did the pool report during your test and were there any significant differences between Claymore and Phoenix?
pool average fluctuates a lot but overall average is about 1-2% better on phoenix than running claymore, hashrate doesnt matter, accepted shares do, which is why i based my comparison on that number.
other differences are that phoenix doesnt have any fan control or clock/voltage modification where claymore does, and on my rig, even though i see more hashrate with pheonix, i see 10-20W more power consumption as well.
February 03, 2018, 04:11:05 PM
im also a little confused about the counts of shares submitted.
for about 225MH/s
claymore/phoenix reports submitting shares at a rate of about 78-80 shares/hr
but nanopool is seeing about 2x that number of shares at about 170 shares/hr
yet still seeing and calculating the same hashrate. can anyone explain this discrepancy?
for about 225MH/s
claymore/phoenix reports submitting shares at a rate of about 78-80 shares/hr
but nanopool is seeing about 2x that number of shares at about 170 shares/hr
yet still seeing and calculating the same hashrate. can anyone explain this discrepancy?
What did the pool report during your test and were there any significant differences between Claymore and Phoenix?
February 03, 2018, 03:58:20 PM
The dev is working those feature into the program but for now, use overdriveNtool by the guy on guru3d
Works great for all overclocking, undervolting and fan control. I mod all my bios with Polaris 1.6 but if I need to tweak anything after I use overdriveNtool
Works great for all overclocking, undervolting and fan control. I mod all my bios with Polaris 1.6 but if I need to tweak anything after I use overdriveNtool
Could you please share a simple guide on how to undervolt with this tool mate? I don't want to mess up my cards
I don't know if I should even do it, since for the first two weeks my rig is finally stable *fingers crossed* and I don't know if that would cause any instability, that's why I'm asking. It just much simple with those commands to do it and not go in-depth, that's why I asked, I don't mind waiting tho. Electricity is 0.06usd, so 100-150w won't cause me to lose much of the profit. It just bugs me, that the cards are getting hot and the fans, therefore, are working at 60%, producing a lot of noise.You want to focus on P6 and P7 (this is your core clock and core voltage) and then P3 (memory clock and voltage). You need to make P6 voltage slightly higher then P7. You can carry the P6 voltage all the way back to P2 for the core. I don't adjust the memory voltage only the memory clock in the middle of the program under p3 (p1 to p3 columns). I believe it helps maintain stability and you'd only save a couple watts at most by undervolting the memory voltage. Most of your savings will be the core clock and core voltage in p6 and p7 on the left side of the tool. Since the gpu runs 100% almost all of the time for utilization the most relevant field is p7 core clock and p7 voltage.
February 03, 2018, 03:48:37 PM
61hr tests on each claymore and Phoenix. on nanopool mining ETH
Claymore v10.0
4744 shares accepted
0 rejected
Phoenix 2.5d
4815 shares accepted
0 rejected
1.2% stales
this shows that over these two 61hr periods, Phoenix submitted 1.5% more shares. but phoenix also had 1.2% stales. I'm not sure how to compare this with claymore since claymore's program doesnt report stales.
Claymore v10.0
4744 shares accepted
0 rejected
Phoenix 2.5d
4815 shares accepted
0 rejected
1.2% stales
this shows that over these two 61hr periods, Phoenix submitted 1.5% more shares. but phoenix also had 1.2% stales. I'm not sure how to compare this with claymore since claymore's program doesnt report stales.
Set up one machine to ethermine and one to nanopool and see what stale shares are reported? I'm only familiar with ethermine and they report stale shares which are usually slightly higher then whats reported by phoenix because phoenix is a calculated number.
February 03, 2018, 03:40:41 PM
The Program itself its pretty simple, load the GUI, enter your settings onto one card, click to save that as a profile, that will create a config file right in the same folder, you can go in there and make other profiles with copy and paste and edit them faster then in the GUI, but either way woek, edit config file or GUI. That's how you make any number of profiles you want to call with the -pX function. You can have a profile for each card in your rig if you want.
These are my two profiles in this one rig, the voltages need a little touchup, kind of high:
Code:
[Profile_0]
Name=570
GPU_P0=300;750
GPU_P1=588;765
GPU_P2=976;956
GPU_P3=1065;950
GPU_P4=1130;950
GPU_P5=1192;950
GPU_P6=1233;950
GPU_P7=1268;950
Mem_P0=300;750
Mem_P1=1000;800
Mem_P2=2200;900
Fan_Min=750
Fan_Max=3000
Fan_Target=70
Fan_Acoustic=910
Power_Temp=90
Power_Target=0
[Profile_1]
Name=580
GPU_P0=300;750
GPU_P1=600;769
GPU_P2=918;893
GPU_P3=1167;1050
GPU_P4=1239;1050
GPU_P5=1282;1050
GPU_P6=1326;1050
GPU_P7=1366;1050
Mem_P0=300;750
Mem_P1=1000;800
Mem_P2=2250;900
Fan_Min=1125
Fan_Max=3500
Fan_Target=75
Fan_Acoustic=918
Power_Temp=90
Power_Target=0
And I have found that these 'hold' better then using watt man, afterburner, claymore command line, sapphire, any of them. Really rock solid.
If I could use Phoenix Miner with geth I would be getting 32 and 34.5 MHS on the 570s and 580s respectively but nope, I am suffering with Claymore still. haha.
I haven't put overdriveNtool into the BAT file but it appears pretty simple. I should... Occasionally the unit will blink and then I have to check the profiles. I do need to rename them because I have tried to be specific so I know which card is which in my profile but it would be a much longer bat file. I guess that doesn't matter?
February 03, 2018, 03:32:21 PM
im also a little confused about the counts of shares submitted.
for about 225MH/s
claymore/phoenix reports submitting shares at a rate of about 78-80 shares/hr
but nanopool is seeing about 2x that number of shares at about 170 shares/hr
yet still seeing and calculating the same hashrate. can anyone explain this discrepancy?
for about 225MH/s
claymore/phoenix reports submitting shares at a rate of about 78-80 shares/hr
but nanopool is seeing about 2x that number of shares at about 170 shares/hr
yet still seeing and calculating the same hashrate. can anyone explain this discrepancy?
Nanopool ETH share difficulty temporary increased x2. So each submitted share is now worth about double.
February 03, 2018, 11:34:26 AM
im also a little confused about the counts of shares submitted.
for about 225MH/s
claymore/phoenix reports submitting shares at a rate of about 78-80 shares/hr
but nanopool is seeing about 2x that number of shares at about 170 shares/hr
yet still seeing and calculating the same hashrate. can anyone explain this discrepancy?
for about 225MH/s
claymore/phoenix reports submitting shares at a rate of about 78-80 shares/hr
but nanopool is seeing about 2x that number of shares at about 170 shares/hr
yet still seeing and calculating the same hashrate. can anyone explain this discrepancy?
Jump to: