Tried to use phoenix miner for the first time today, got 0,00 MHS for some reason
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 -amdany 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:5555Phoenix 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).
