Bitcoin Forum
June 20, 2021, 02:02:44 AM *
News: Latest Bitcoin Core release: 0.21.1 [Torrent]
 
   Home   Help Search Login Register More  
Pages: « 1 ... 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 [55] 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99 100 101 102 103 104 105 ... 458 »
  Print  
Author Topic: PhoenixMiner 5.6d: fastest Ethereum/Ethash miner with lowest devfee (Win/Linux)  (Read 663526 times)
john1010
Hero Member
*****
Offline Offline

Activity: 1722
Merit: 555



View Profile
March 15, 2018, 04:23:24 AM
 #1081

Can I mine other eth base coin, coz i tried to mine DBIX but it says that disconnecting to server... Am I missing something in my configuration?

My sample bat config..

PhoenixMiner.exe -pool stratum+tcp://beta-dbix.pool.sexy:10032 -wal 0xabc0419ec201fdccf5********* -epsw x -tt 65 -fanmin 55 -fanmax 90 -cclock 1130,1167,1130,1130,1130,1167,1167,1167,1167,1167,1167,1130 -mclock 2050,2100,2050,2050,2050,2100,2100,2100,2100,2100,2100,2050 -cvddc 850,820,850,850,850,820,820,820,820,820,820,850 -mvddc 850,820,850,850,850,820,820,820,820,820,820,850

1624154564
Hero Member
*
Offline Offline

Posts: 1624154564

View Profile Personal Message (Offline)

Ignore
1624154564
Reply with quote  #2

1624154564
Report to moderator
1624154564
Hero Member
*
Offline Offline

Posts: 1624154564

View Profile Personal Message (Offline)

Ignore
1624154564
Reply with quote  #2

1624154564
Report to moderator
1624154564
Hero Member
*
Offline Offline

Posts: 1624154564

View Profile Personal Message (Offline)

Ignore
1624154564
Reply with quote  #2

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

Posts: 1624154564

View Profile Personal Message (Offline)

Ignore
1624154564
Reply with quote  #2

1624154564
Report to moderator
1624154564
Hero Member
*
Offline Offline

Posts: 1624154564

View Profile Personal Message (Offline)

Ignore
1624154564
Reply with quote  #2

1624154564
Report to moderator
khafan11
Newbie
*
Offline Offline

Activity: 16
Merit: 0


View Profile
March 15, 2018, 06:15:12 AM
 #1082

perfect , good job
switch claymore v11.4 to PhoenixMiner 2.7c  Kiss
smallbitmoney
Newbie
*
Offline Offline

Activity: 12
Merit: 1


View Profile
March 15, 2018, 06:37:58 AM
 #1083

Hi there,

Being using Claymore and had a steady hash rate at 243.5 Mh/s. Switched to PhoenixMiner 2.7c but hash rate fluctuates between 239+ to 248+ Mh/s; pool report an average of 242.4 M/hs. Does anyone hash rate fluctuates or it is just me?
peeshypow
Newbie
*
Offline Offline

Activity: 5
Merit: 0


View Profile
March 15, 2018, 07:54:37 AM
 #1084

So far so good...

I have double digit rigs with different card setups, I have not tried Phoenix Miner on any of those yet.  However I did try it on my test single GPU test machine.  It is right now a solo GTX 1070.  It was getting 29 to 30 mhs consistently at 62C on Claymore 11.2, rarely get stale shares with this card.

I started testing Phoenix Miner an hour ago.  I am getting 30 to 31 mhs.  It seems stable, same 62C.  However it seems my Effective speed is lower with Phoenix Miner at ethmine.   Then I noticed that in the short DEVFEE transition, it found 2 shares for the Devs while in the first 30 minutes it found just 6 for me.  So my effective rate(the actual rate measured by how many shares I find) at the pool is still 22.71 mh/s, but after a couple hours I will see if it catches up.  With Claymore my effective hash rate is pretty close and sometimes more than reported hash rate at the actual pool.

Overall it seems stable and if this small 0.5 mhs difference in speed on this one card is legit AND the dev fee is really legit then this looks like a possible better alternative to Claymore.
kkanoee
Newbie
*
Offline Offline

Activity: 10
Merit: 0


View Profile
March 15, 2018, 09:13:25 AM
 #1085


@kkanoee which card is it?  Most likely you've some settings messed up

RX580 8G Armor. some settings in the bat file you mean ?
human75
Newbie
*
Offline Offline

Activity: 51
Merit: 0


View Profile
March 15, 2018, 01:29:13 PM
 #1086

Hi Guys.
i am very happy with Phoenix Miner so far but i am having strange issue with Afterburner...i have Rx570 and 580 in my rig and in total 8 cards installed.Afterburner works perfect with old blockchain driver but when i installed latest adrenalin driver afterburner wont recognize my cards at all.all cards are good in windows device manager.Any advise?
gsrcrxsi314
Member
**
Offline Offline

Activity: 367
Merit: 34


View Profile
March 15, 2018, 02:14:05 PM
 #1087

Hi Guys.
i am very happy with Phoenix Miner so far but i am having strange issue with Afterburner...i have Rx570 and 580 in my rig and in total 8 cards installed.Afterburner works perfect with old blockchain driver but when i installed latest adrenalin driver afterburner wont recognize my cards at all.all cards are good in windows device manager.Any advise?

It’s been my experience that afterburner doesn’t work very well with RX cards in general. My advice is to use a different method of overclocking. Use the built in commands of Pheonix instead.
aurus33
Newbie
*
Offline Offline

Activity: 20
Merit: 0


View Profile
March 15, 2018, 04:42:48 PM
 #1088

Hi Guys.
i am very happy with Phoenix Miner so far but i am having strange issue with Afterburner...i have Rx570 and 580 in my rig and in total 8 cards installed.Afterburner works perfect with old blockchain driver but when i installed latest adrenalin driver afterburner wont recognize my cards at all.all cards are good in windows device manager.Any advise?

It’s been my experience that afterburner doesn’t work very well with RX cards in general. My advice is to use a different method of overclocking. Use the built in commands of Pheonix instead.

Agree, I just use afterburner with nvidia cards, for amd I use OverdriveNTool, it works very nice!!


@PhoenixMiner
DevRequest: Forget about Dual mining on any other coin but XVG!!!!! PLEASE! Implement one of the multiple algoritms that Verge supports (Scrypt, X17, Lyra2rev2, myr-groestl, blake2s), you got options! Pretty please!!!
janding
Newbie
*
Offline Offline

Activity: 140
Merit: 0


View Profile
March 15, 2018, 07:46:26 PM
 #1089

would it be possible to get a fresh compiled version straight from the owen, or is it possible to get the source code so i can compile myself?

i need a fresh version because i allways get problems with precompiled binaries and AV.



Maybe I missed something.
Are you asking Phoenix to give you their source code so you can compile it ?
nars28
Newbie
*
Offline Offline

Activity: 25
Merit: 0


View Profile
March 15, 2018, 07:58:41 PM
 #1090

Phoenix team can you make ASM kernel for rx 560 (baffin) ? Miner is considerably slower than claymore...

thanks
mayers8851
Newbie
*
Offline Offline

Activity: 45
Merit: 0


View Profile
March 15, 2018, 08:00:56 PM
 #1091

would it be possible to get a fresh compiled version straight from the owen, or is it possible to get the source code so i can compile myself?
i need a fresh version because i allways get problems with precompiled binaries and AV.
Maybe I missed something.
Are you asking Phoenix to give you their source code so you can compile it ?

Grin Grin Grin
PhoenixMiner
Member
**
Offline Offline

Activity: 338
Merit: 68


View Profile
March 16, 2018, 07:03:56 AM
 #1092

Tried to use phoenix miner for the first time today, got 0,00 MHS for some reason

Code:
17604:04:37:03.269: main Phoneix Miner 2.7c Windows/msvc - Release
17604:04:37:03.269: main Cmd line: -pool stratum+tcp://daggerhashimoto.eu.nicehash.com:3353 -wal nicehashwallet -pass x -proto 4 -stales 0 -amd
17604:04:37:03.950: main Available GPUs for mining:
17604:04:37:03.950: main GPU1: Radeon (TM) RX 480 Graphics (pcie 1), OpenCL 2.0, 8 GB VRAM, 36 CUs
17604:04:37:03.950: main GPU2: Radeon (TM) RX 480 Graphics (pcie 3), OpenCL 2.0, 8 GB VRAM, 36 CUs
17604:04:37:03.950: main GPU3: Radeon (TM) RX 480 Graphics (pcie 5), OpenCL 2.0, 8 GB VRAM, 36 CUs
17604:04:37:03.950: main GPU4: Radeon (TM) RX 480 Graphics (pcie 6), OpenCL 2.0, 8 GB VRAM, 36 CUs
17604:04:37:03.950: main GPU5: Radeon (TM) RX 480 Graphics (pcie 7), OpenCL 2.0, 8 GB VRAM, 36 CUs
17604:04:37:03.950: main GPU6: Radeon (TM) RX 480 Graphics (pcie 8), OpenCL 2.0, 8 GB VRAM, 36 CUs
17604:04:37:03.979: main ADL library initialized
17604:04:37:04.269: main Listening for CDM remote manager at port 3333 in read-only mode
17604:04:37:04.269: main Eth: the pool list contains 2 pools
17604:04:37:04.269: main Eth: primary pool: daggerhashimoto.eu.nicehash.com:3353
17604:04:37:04.269: main Starting GPU mining
17604:04:37:04.269: main Matched GPU1 to ADL adapter index 24 (method 1)
17604:04:37:04.299: main GPU1: Using the X2 ODN API
17604:04:37:04.299: main GPU1: Created ADL monitor for adapter 24; overdrive version: 7
17604:04:37:04.299: main Matched GPU2 to ADL adapter index 12 (method 1)
17604:04:37:04.329: main GPU2: Using the X2 ODN API
17604:04:37:04.329: main GPU2: Created ADL monitor for adapter 12; overdrive version: 7
17604:04:37:04.330: main Matched GPU3 to ADL adapter index 30 (method 1)
17604:04:37:04.360: main GPU3: Using the X2 ODN API
17604:04:37:04.360: main GPU3: Created ADL monitor for adapter 30; overdrive version: 7
17604:04:37:04.360: main Matched GPU4 to ADL adapter index 0 (method 1)
17604:04:37:04.390: main GPU4: Using the X2 ODN API
17604:04:37:04.390: main GPU4: Created ADL monitor for adapter 0; overdrive version: 7
17604:04:37:04.390: main Matched GPU5 to ADL adapter index 18 (method 1)
17604:04:37:04.421: main GPU5: Using the X2 ODN API
17604:04:37:04.421: main GPU5: Created ADL monitor for adapter 18; overdrive version: 7
17604:04:37:04.421: main Matched GPU6 to ADL adapter index 6 (method 1)
17604:04:37:04.454: main GPU6: Using the X2 ODN API
17604:04:37:04.454: main GPU6: Created ADL monitor for adapter 6; overdrive version: 7
17604:04:37:04.454: wdog Starting watchdog thread
17604:04:37:04.454: main Eth: Connecting to ethash pool daggerhashimoto.eu.nicehash.com:3353 (proto: Nicehash)
17604:04:37:04.495: eths Eth: Connected to ethash pool daggerhashimoto.eu.nicehash.com:3353 (159.122.29.199)
17604:04:37:04.495: eths Eth: Send: {"id":1,"method":"mining.subscribe","params":["PhoenixMiner/2.7c","EthereumStratum/1.0.0"]}

17604:04:37:04.566: eths Eth: Received: {"id":1,"error":null,"result":[["mining.notify","1b823da44765203241b8224983007c12","EthereumStratum/1.0.0"],"4b61a2"]}
17604:04:37:04.566: eths Eth: Extranonce set to 4b61a2
17604:04:37:04.566: eths Eth: Subscribed to ethash pool
17604:04:37:04.566: eths Eth: Send: {"id":2,"method":"mining.extranonce.subscribe","params":[]}
{"id":3,"method":"mining.authorize","params":["3C6VmPEhFSM7cj4aw89NhpZGmSovKffKVH","x"]}

17604:04:37:04.613: eths Eth: Received: {"id":3,"result":true,"error":null}
17604:04:37:04.613: eths Eth: Worker 3C6VmPEhFSM7cj4aw89NhpZGmSovKffKVH authorized
17604:04:37:04.631: eths Eth: Received: {"id":null,"method":"mining.set_difficulty","params":[0.5]}
17604:04:37:04.631: eths Eth: Difficulty set to 0.5
17604:04:37:04.631: eths Eth: Received: {"params":["000000251564b3f1","08e704bf06ac983d776d734cacf1f611802b802efb5a5f5cb8086d6a0d966ac5","ead2f865f18fd460b8938e49795e17d876b1cec5cda5ebc65b5381c46645ef18",true],"id":null,"method":"mining.notify"}
17604:04:37:04.631: eths Eth: New job #ead2f865 from daggerhashimoto.eu.nicehash.com:3353; diff: 2147MH
17604:04:37:04.631: GPU1 GPU1: Starting up... (0)
17604:04:37:04.631: GPU1 Eth: Generating light cache for epoch #175
17604:04:37:04.631: GPU2 GPU2: Starting up... (0)
17604:04:37:04.633: GPU3 GPU3: Starting up... (0)
17604:04:37:04.635: GPU4 GPU4: Starting up... (0)
17604:04:37:04.637: GPU5 GPU5: Starting up... (0)
17604:04:37:04.639: GPU6 GPU6: Starting up... (0)
17604:04:37:04.641: eths Eth: Received: {"id":2,"result":true,"error":null}
17604:04:37:04.659: main GPU1: 32C 0%, GPU2: 24C 70%, GPU3: 23C 75%, GPU4: 20C 75%, GPU5: 26C 95%, GPU6: 36C 60%
17604:04:37:07.205: GPU2 GPU2: Using optimized OpenCL kernels (device name 'Ellesmere')
17604:04:37:09.590: main Eth speed: 0.000 MH/s, shares: 0/0/0, time: 0:00
[b]17604:04:37:09.590: 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)
17604:04:37:14.714: main Eth speed: 0.000 MH/s, shares: 0/0/0, time: 0:00
17604:04:37:14.714: 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)
17604:04:37:19.862: main Eth speed: 0.000 MH/s, shares: 0/0/0, time: 0:00
17604:04:37:19.862: 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)
17604:04:37:25.029: main Eth speed: 0.000 MH/s, shares: 0/0/0, time: 0:00
17604:04:37:25.029: 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)
17604:04:37:30.157: main Eth speed: 0.000 MH/s, shares: 0/0/0, time: 0:00
17604:04:37:30.157: 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)[/b]
17604:04:37:32.720: main GPU1: 32C 0%, GPU2: 25C 70%, GPU3: 23C 75%, GPU4: 21C 75%, GPU5: 26C 95%, GPU6: 37C 60%

BAT: -pool stratum+tcp://daggerhashimoto.eu.nicehash.com:3353 -wal nicehashwallet -pass x -proto 4 -stales 0 -amd

any ideas appreciated!
The light cache generation on your rig is rather slow - it starts on 04:37:04.631 but it is still going on at 04:37:32, which is almost 30 seconds. Even on quite slow CPU (Athlon II X2, Celereon, etc.), this shouldn't take more than 10-15 seconds. Note that the light cache must be generated first before the DAGs are generated and then the mining will start. Check with Task Manager what is your CPU load, it is probably 100% for some reason. Even so, the light cache will be generated eventually but it may take a long time (e.g. minutes) if your CPU is 100% loaded with other higher-priority tasks.

I Just switched to Phoenix. Performance is roughly the same as Claymore's, lower dev fee, it's a no brainer.

Dual mining is overrated as usual, unless you have free electricity.

Just one question: I had to set mining intensity to 12 to get same performance as Claymore's 11.4, no problem, power consumption is the same and all seems stable. But how about -dcri? C's 11.4 actually improved performance a bit by auto setting dcri in Eth only mode. I got -dcri 110,44,110.

Tried to use those values with -gt parameter in Phoenix bat file, but performance was much lower.
  The -gt parameter is quite similar but not the same as -dcri. Replace -gt 110,44,110 with -dcri 110,44,110, which will force PhoenixMiner to try and approximate the GT values from the supplied -dcri values.


a few hours back pool shows that rig went offline but the miner still submit shares.
i've restarted the miner and still submit shares as usual but pool still doesn't show that.
been in touch with ethermine support but they insist that it wasn't a server side fault. still not sure if it was a pool or miner issue but till then, i'll continue using claymore.
  This sounds like the infamous MITM attack. Check the difficulty which is displayed each time when the miner receives a new job. On ethermine it is 4000MH but if your connection was hijacked it would be 10000MH. To prevent such attacks, use the SSL ports on ethermine and don't forget to add the ssl:// prefix too, like this: -pool ssl://eu1.ethermine.org:5555 -pool2 ssl://us1.ethermine.org:5555


Phoenix 2.7c crashes with the settings I have and with so many GPU's it will take lot of time to re-tune the clocks to match this program

Similar problem with claymore 11.2 to 11.4 but now Claymore has just released v11.5 with -oldkernel option which can be used in cases where they have problems with latest versions because they use hard OC and/or custom bioses created for old versions

any chance we can get a similar one for Phoenix so that there will not be need to change clock settings/bios mod
   We haven't changed the kernels significantly in the last release but when we do in the future, we will most likely provide a way to use the older kernels if there are similar problems.


Tried even a bit more than -20 on memory.
Getting this error:
wdog Hardware manager thread not responding
wdog Thread(s) not responding. Restarting.
    In our experience, once you get the NVML 999 error, the only thing than helps is to restart the rig. So, if you get 999 error, first restart Windows, and then lower the OC.


I have a weird thing, when mining PIRL I have 29mh/s but when I try to mine ETH Im getting 18mh/s. I tried ethermine and nanopool but nothing changed. Anyone got an idea ? I should get the same speed since its the same algorithm right ?
    If you have an AMD GPU(s), most probably you have old drivers or haven't switched the driver in compute mode. PIRL has a low DAG epoch (less than 40), while ETH is at 175 already. The driver must be in compute mode in order to avoid losing hasrate with higher DAG epochs.


would it be possible to get a fresh compiled version straight from the owen, or is it possible to get the source code so i can compile myself?

i need a fresh version because i allways get problems with precompiled binaries and AV.
   PhoenixMiner is not open-source. To solve the AV problems, add the executable (PhoenixMiner.exe) as an exception in your AV. The false positives can't be avoided as most AV interpret the anti-debugging code in the program as suspicious. If you want to be extra safe, compare the hashes of the downloaded package with these that are listed in the first post of this thread - they must be identical.


Can I mine other eth base coin, coz i tried to mine DBIX but it says that disconnecting to server... Am I missing something in my configuration?

My sample bat config..

PhoenixMiner.exe -pool stratum+tcp://beta-dbix.pool.sexy:10032 -wal 0xabc0419ec201fdccf5********* -epsw x -tt 65 -fanmin 55 -fanmax 90 -cclock 1130,1167,1130,1130,1130,1167,1167,1167,1167,1167,1167,1130 -mclock 2050,2100,2050,2050,2050,2100,2100,2100,2100,2100,2100,2050 -cvddc 850,820,850,850,850,820,820,820,820,820,820,850 -mvddc 850,820,850,850,850,820,820,820,820,820,820,850
   We tried exactly the same command line but with valid wallet address and it works without any problems.


Hi there,

Being using Claymore and had a steady hash rate at 243.5 Mh/s. Switched to PhoenixMiner 2.7c but hash rate fluctuates between 239+ to 248+ Mh/s; pool report an average of 242.4 M/hs. Does anyone hash rate fluctuates or it is just me?
    We report the hashrate as (almost) unfiltered momentary value, which is exactly what the GPUs are giving at this time. You can also see the 5 minute average hashrate every 30 seconds or when you press the 's' key - this is much more stable and consistent value. As some people prefer more smoothed out values, we will probably add an option to set the amount of filtering.


Hi Guys.
i am very happy with Phoenix Miner so far but i am having strange issue with Afterburner...i have Rx570 and 580 in my rig and in total 8 cards installed.Afterburner works perfect with old blockchain driver but when i installed latest adrenalin driver afterburner wont recognize my cards at all.all cards are good in windows device manager.Any advise?
  Try to upgrade the Afterburner to the latest version (or use slightly older drivers but still from the 18.x.x generation, don't downgrade to 17.x.x as these have a lot of issues).


Agree, I just use afterburner with nvidia cards, for amd I use OverdriveNTool, it works very nice!!

@PhoenixMiner
DevRequest: Forget about Dual mining on any other coin but XVG!!!!! PLEASE! Implement one of the multiple algoritms that Verge supports (Scrypt, X17, Lyra2rev2, myr-groestl, blake2s), you got options! Pretty please!!!
    Will take this under consideration but the situation with these coins changes so fast that probably we will have to implement more than one and see which survives in the long run.


Phoenix team can you make ASM kernel for rx 560 (baffin) ? Miner is considerably slower than claymore...

thanks
   Hmm, PhoenixMiner does contain an optimized kernel for Baffin GPUs but perhaps it is not working well on your system. Could you please send us the first few pages of your log file and also tell us the driver version and overclocking settings of your card(s) to check what is causing these problems?
   Note that depending on your OC settings, the hashrate on RX560 could take a minute or so to pick up (you can play with -mi and -gt values to get more stable hashrate but make sure that the average speed isn't getting lower).

murgorx
Member
**
Offline Offline

Activity: 434
Merit: 13


View Profile
March 16, 2018, 07:31:28 AM
 #1093

@PhoenixMiner, bro I have been with the newest version 2.7c for a week now and I see the following tendency - every 12 hours or so the rig freezes and stops mining, the cards go in idle state and I have to make a hard reset in order to restart the machine.
For the last 5 days this has happened around 5 times. What may be causing this issue? Anyone else with the same problem?
kkanoee
Newbie
*
Offline Offline

Activity: 10
Merit: 0


View Profile
March 16, 2018, 11:57:53 AM
 #1094



I have a weird thing, when mining PIRL I have 29mh/s but when I try to mine ETH Im getting 18mh/s. I tried ethermine and nanopool but nothing changed. Anyone got an idea ? I should get the same speed since its the same algorithm right ?
    If you have an AMD GPU(s), most probably you have old drivers or haven't switched the driver in compute mode. PIRL has a low DAG epoch (less than 40), while ETH is at 175 already. The driver must be in compute mode in order to avoid losing hasrate with higher DAG epochs.



I have the blockchain drivers from august, I will try the latest ones with compute mode thanks.
smallbitmoney
Newbie
*
Offline Offline

Activity: 12
Merit: 1


View Profile
March 16, 2018, 07:34:05 PM
 #1095

Hi there,

Being using Claymore and had a steady hash rate at 243.5 Mh/s. Switched to PhoenixMiner 2.7c but hash rate fluctuates between 239+ to 248+ Mh/s; pool report an average of 242.4 M/hs. Does anyone hash rate fluctuates or it is just me?
    We report the hashrate as (almost) unfiltered momentary value, which is exactly what the GPUs are giving at this time. You can also see the 5 minute average hashrate every 30 seconds or when you press the 's' key - this is much more stable and consistent value. As some people prefer more smoothed out values, we will probably add an option to set the amount of filtering.


Thank you for your explanation. Now I understand and I like the way it was implemented. Great job PhoenixMiner developers!
EthCiN
Newbie
*
Offline Offline

Activity: 4
Merit: 0


View Profile
March 16, 2018, 09:59:17 PM
 #1096

When new version available? What are the best NVidia drivers/settings for the 1070 GPUs?
Regards
theodrim
Newbie
*
Offline Offline

Activity: 81
Merit: 0


View Profile
March 18, 2018, 04:36:42 AM
 #1097

The -gt parameter is quite similar but not the same as -dcri. Replace -gt 110,44,110 with -dcri 110,44,110, which will force PhoenixMiner to try and approximate the GT values from the supplied -dcri values.
Any reason this isn't mentioned in readme? Why hide such beneficial (albeit experimental) thing?
smallbitmoney
Newbie
*
Offline Offline

Activity: 12
Merit: 1


View Profile
March 18, 2018, 05:00:31 AM
 #1098

Hi there,

Being using Claymore and had a steady hash rate at 243.5 Mh/s. Switched to PhoenixMiner 2.7c but hash rate fluctuates between 239+ to 248+ Mh/s; pool report an average of 242.4 M/hs. Does anyone hash rate fluctuates or it is just me?
    We report the hashrate as (almost) unfiltered momentary value, which is exactly what the GPUs are giving at this time. You can also see the 5 minute average hashrate every 30 seconds or when you press the 's' key - this is much more stable and consistent value. As some people prefer more smoothed out values, we will probably add an option to set the amount of filtering.


Thank you for your explanation. Now I understand and I like the way it was implemented. Great job PhoenixMiner developers!
In the end you should consider what the pool reports as your hashrate and earnings. It's easy for any mining developer to obfuscate or in other ways present wrong numbers.

--ypsi

Yes, I did that and the result was PhoenixMiner does a little more shares. Initially I'm not sure why the fluctuation therefore curious to find out.
sjyi
Jr. Member
*
Offline Offline

Activity: 196
Merit: 1


View Profile
March 18, 2018, 05:35:44 AM
 #1099

...Quadro K2100M..... with 2GB VRAM ...


.... However i have not yet run any Ethash based miner. I thought your's would be the first .... but no luck.

...

You can't mine ethereum with 2GB of RAM.  Current DAG already passed 2GB.  You can still mine newer coins with smaller DAG sizes though.
PhoenixMiner
Member
**
Offline Offline

Activity: 338
Merit: 68


View Profile
March 18, 2018, 05:55:25 AM
 #1100

@PhoenixMiner, bro I have been with the newest version 2.7c for a week now and I see the following tendency - every 12 hours or so the rig freezes and stops mining, the cards go in idle state and I have to make a hard reset in order to restart the machine.
For the last 5 days this has happened around 5 times. What may be causing this issue? Anyone else with the same problem?
    Obviously this is not DAG generation related as it happens too often, so we will need some logs to make any suggestions.

When new version available? What are the best NVidia drivers/settings for the 1070 GPUs?
Regards
   The first beta of 2.8 should be released tomorrow. We found some regressions during the internal testing and we had to delay the release.

The -gt parameter is quite similar but not the same as -dcri. Replace -gt 110,44,110 with -dcri 110,44,110, which will force PhoenixMiner to try and approximate the GT values from the supplied -dcri values.
Any reason this isn't mentioned in readme? Why hide such beneficial (albeit experimental) thing?
    Well, we print a warning for each Claymore command-line argument that is not implemented by us, and we assume that if anyone is switching over from Claymore, they would try first with the same command-line options as they used before. However, for the new users it is best to use directly the -gt parameter as the approximation of -dcri is not ideal and may give some strange results in certain cases.
Pages: « 1 ... 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 [55] 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99 100 101 102 103 104 105 ... 458 »
  Print  
 
Jump to:  

Powered by MySQL Powered by PHP Powered by SMF 1.1.19 | SMF © 2006-2009, Simple Machines Valid XHTML 1.0! Valid CSS!