Topic: PhoenixMiner 6.2c: fastest Ethereum/Ethash miner with lowest devfee (Win/Linux) - page 349. (Read 784857 times)
March 12, 2019, 10:52:20 PM
Fans are controlled with overdriventool. Should I do anything in phoenix?
March 12, 2019, 03:19:40 PM
PhoenixMiner 4.2a added to https://www.minermonitoring.com/
Join our discord https://discord.gg/aGGaeqq
also, you can check the speed of the miner on different rigs using the benchmark page: https://minermonitoring.com/benchmark
Join our discord https://discord.gg/aGGaeqq
also, you can check the speed of the miner on different rigs using the benchmark page: https://minermonitoring.com/benchmark
March 12, 2019, 11:45:35 AM
Please take our apologies about the lack of forum activity in the last month. We have our plates full when the new version enters "pre-release limbo" and is time to squeeze out the bugs, so our policy is generally to "block out" the outside world for a few weeks and concentrate on our main job - making PhoenixMiner better.
With that being said - the first beta of the 4.2 is ready. You can download PhoenixMiner 4.2a from here:
With that being said - the first beta of the 4.2 is ready. You can download PhoenixMiner 4.2a from here:
Understood, that makes sense, no worries.
Great to see the new beta, and trying it out right now. It still has the problem that I and a couple of others have reported about solo mode with GetWork - it still dumps out saying that a Stratum thread is not responding. This version is still not usable for solo mining using geth client. Version 4.0b works fine.
Code:
~# ~/phoenixminer/PhoenixMiner -gwtime 50 -rate 0 -pool http://10.69.1.10:8547 -coin clo -mi 14 -cdm 0 -amd -gpus 1 -acm -clKernel 0 -gpureset 1 -rmode 0 -log 0
Phoenix Miner 4.2a Linux/gcc - Release build
--------------------------------------------
Unknown OpenCL driver version! Hashrate and stale shares may suffer
OpenCL platform: OpenCL 2.1 AMD-APP (2766.4)
Available GPUs for mining:
GPU1: Vega 10 XTX [Radeon Vega Frontier Edition] (pcie 3), OpenCL 1.2, 16 GB VRAM, 64 CUs
Eth: the pool list contains 1 pool (1 from command-line)
Eth: primary pool: http://10.69.1.10:8547
Starting GPU mining
Eth: Connecting to http://10.69.1.10:8547 (GetWork/Solo)
Eth: New job #db436429 from http://10.69.1.10:8547; diff: 14057125MH
GPU1: Starting up... (0)
GPU1: Generating ethash light cache for epoch #73
Eth: Connected to ethash pool http://10.69.1.10:8547
GPU1: 44C 46%
Eth: New job #3f23092f from http://10.69.1.10:8547; diff: 14057125MH
Light cache generated in 1.0 s (24.5 MB/s)
GPU1: Using generic OpenCL kernels
GPU1: Allocating DAG for epoch #73 (1.57) GB
GPU1: Generating DAG for epoch #73
GPU1: DAG 39%
GPU1: DAG 78%
Eth speed: 0.000 MH/s, shares: 0/0/0, time: 0:00
GPU1: DAG generated in 3.8 s (419.4 MB/s)
Eth: New job #1e921adf from http://10.69.1.10:8547; diff: 14063984MH
Eth speed: 35.978 MH/s, shares: 0/0/0, time: 0:00
Eth: New job #ca64d685 from http://10.69.1.10:8547; diff: 14063984MH
Eth: New job #30a7b50e from http://10.69.1.10:8547; diff: 14070850MH
Eth speed: 36.000 MH/s, shares: 0/0/0, time: 0:00
Eth: New job #c1c2944c from http://10.69.1.10:8547; diff: 14070850MH
Eth: New job #68e9b9a2 from http://10.69.1.10:8547; diff: 14070850MH
Eth speed: 36.006 MH/s, shares: 0/0/0, time: 0:00
Eth: New job #905adf93 from http://10.69.1.10:8547; diff: 14077722MH
Eth: New job #da4b152d from http://10.69.1.10:8547; diff: 14077722MH
Eth speed: 42.021 MH/s, shares: 0/0/0, time: 0:00
Eth: New job #593c043d from http://10.69.1.10:8547; diff: 14077722MH
GPU1: 56C 75%
Eth: New job #c9a1abfe from http://10.69.1.10:8547; diff: 14077722MH
Eth: New job #a3a841f9 from http://10.69.1.10:8547; diff: 14077722MH
Eth speed: 42.021 MH/s, shares: 0/0/0, time: 0:00
Eth: New job #d541fa9f from http://10.69.1.10:8547; diff: 14084601MH
Eth: New job #2326c892 from http://10.69.1.10:8547; diff: 14084601MH
Eth speed: 42.021 MH/s, shares: 0/0/0, time: 0:00
Eth: New job #b95e9046 from http://10.69.1.10:8547; diff: 14084601MH
Eth: New job #e5503f0e from http://10.69.1.10:8547; diff: 14084601MH
Eth speed: 42.023 MH/s, shares: 0/0/0, time: 0:00
Eth: New job #3616fc00 from http://10.69.1.10:8547; diff: 14084601MH
*** 0:00 *** 3/12 11:42 **************************************
Eth: Mining CLO on http://10.69.1.10:8547 for 0:00
Eth speed: 42.021 MH/s, shares: 0/0/0, time: 0:00
Eth: Accepted shares 0 (0 stales), rejected shares 0 (0 stales)
Eth: Incorrect shares 0 (0.00%), est. stales percentage 0.00%
Eth: Average speed (5 min): 36.015 MH/s
Eth: New job #7c5650d1 from http://10.69.1.10:8547; diff: 14084601MH
Eth: New job #06b785bd from http://10.69.1.10:8547; diff: 14084601MH
Eth speed: 42.018 MH/s, shares: 0/0/0, time: 0:00
Stratum thread not responsive for 51 s
Thread(s) not responding. Restarting.
March 12, 2019, 09:51:35 AM
I'm very interested to se the Radeon VII supported by Phoenixminer. Wating for reports !
Note for the Radeon VII owners, it seems the card works better with a core voltage set from 950mV to 995mV, at least while gaming.
Note for the Radeon VII owners, it seems the card works better with a core voltage set from 950mV to 995mV, at least while gaming.
March 12, 2019, 09:22:25 AM
Is there any chance to see Hawaii(gfx7) kernels for amdgpu-pro linux driver?
Thanks.
Thanks.
March 12, 2019, 09:19:46 AM
good to see that the new PhoenixMiner 4.2a version is out
I've just started with PhoenixMiner yesterday and got ~5% more reported hash on pool, compared to Clay
Will test this new version too
I've just started with PhoenixMiner yesterday and got ~5% more reported hash on pool, compared to Clay
Will test this new version too
March 12, 2019, 09:08:51 AM
Please take our apologies about the lack of forum activity in the last month. We have our plates full when the new version enters "pre-release limbo" and is time to squeeze out the bugs, so our policy is generally to "block out" the outside world for a few weeks and concentrate on our main job - making PhoenixMiner better.
With that being said - the first beta of the 4.2 is ready. You can download PhoenixMiner 4.2a from here:
(MEGA links are no longer active)
If you want to check the integrity of the downloaded file, please use the following hashes:
Here are the changes for this release:
Here is an example command-line for mining BCI (ProgPOW) - be sure to change YourBciWalletAddress with your actual BCI wallet address:
With that being said - the first beta of the 4.2 is ready. You can download PhoenixMiner 4.2a from here:
(MEGA links are no longer active)
If you want to check the integrity of the downloaded file, please use the following hashes:
Code:
File: PhoenixMiner_4.2a_Windows.zip
===================================
SHA-1: 79196d8316093630c8e929bac494ab432811b7eb
SHA-256: 27be501456b40b06a96bbe1f765d693da6cc5c19849fd5f808aabfdd363263ed
SHA-512: 452b5fec50a83f4f8f8c888223f16a340087b8befefd0e7fff643627ea7e23a7c24de2ad0fbec0aff9fc58b98c4b60e25d506d5d23f33e3aaba19f8f4e4c32e4
File: PhoenixMiner_4.2a_Linux.tar.gz
====================================
SHA-1: 417f6457315c01ecadffc803ae604293f8616169
SHA-256: a82c5c13be0a1cb516daa09fc57b97a43630b9fb789bdc9e6b2e3a9b33a49c97
SHA-512: 6fb1337d5b97c5720754aa795b883d1bd7b455d96b33d9df5fe380ca53d432b8f51eecd3c840632f2ee05cc54c03979005e628ddf8eeab5a1733aff7923648d7
Here are the changes for this release:
- Added support for dual mining Ethash and Blake2s on Nvidia GPUs
- Added experimental support for ProgPOW mining of Bitcoin Interest (BCI). Note that the kernels are not optimized and only work on AMD. You must add -coin bci to the command line (or COIN: bci to your epools.txt file) in order to mine BCI.
- Added support for EthereumStratum/2.0.0 protocol (use -proto 5 if the pool requires it).
- AMD hardware control code was rewritten, now should be more stable and work on older cards too
- Added command-line option -fcm to set the way fans are controlled (AMD/Windows only). The possible values are 0 (auto; the default behavior), 1 (use VBIOS/driver), 2 (force custom control of the fans regardless of VBIOS/drivers fan curves, etc). Use -fcm 2 if the fans are not controlled properly or at all
- Added support for Radeon VII
- Added support for AMD drivers up to 19.3.1
- Added new command-line option -nvkernel to select the old (v1) or new (v2) CUDA kernels. The possible values are 0 (auto; the default), 1 (use the old v1 CUDA kernels from PhoenixMiner 3.5), 2 (use the new v2 kernels, which were introduced with PhoenixMiner 4.0). This was added because there were some complains that the new kernels are running slower on some Nvidia cards. Note that v1 CUDA kernels doesn't support dual mining.
- Increased the maximum supported DAG epoch to 329. This should be fine for at least a year or so.
- Added support for direct mining without DAG switching of Yocoin (YOC), Bitcoiin2Gen (B2G), Ethersocial (ESN), Atheios (ATH), and REOSC. See the -coin parameter in Readme.txt for more information.
- Other small improvements and fixes.
Here is an example command-line for mining BCI (ProgPOW) - be sure to change YourBciWalletAddress with your actual BCI wallet address:
Code:
PhoenixMiner.exe -pool eu-1.pool.bci-server.com:3869 -wal YourBciWalletAddress.Rig1 -coin bci -proto 1
March 12, 2019, 03:28:26 AM
[/quote]
last active on 11th february...strange indeed
March 11, 2019, 06:03:59 PM
I'm having the same issue. I'm mining Callisto (CLO). I had been using Parity with its built-in stratum support, but since they have not updated their Parity client (rust-callisto) for last week's hard fork, I tried to switch to Geth, which doesn't have stratum - thus needing to switch to the RPC interface for get_work. This is where the issue comes in.
I am setting the coin on the commandline.
I tried setting a "password' in commandline as suggested above, but that doesn't make a difference. Over the past few days, I've also tried as many other options as I can. It appears that the issue is it's connecting on RPC for get_work, but there's still a watchdog for a Stratum thread - but since we're not using Stratum, it sees no activity and bombs out.
See here - you can see that the coin is properly set, has connected to geth successfully, and has started mining, but at 51s, it kills itself because of the stratum thread.
I am setting the coin on the commandline.
I tried setting a "password' in commandline as suggested above, but that doesn't make a difference. Over the past few days, I've also tried as many other options as I can. It appears that the issue is it's connecting on RPC for get_work, but there's still a watchdog for a Stratum thread - but since we're not using Stratum, it sees no activity and bombs out.
See here - you can see that the coin is properly set, has connected to geth successfully, and has started mining, but at 51s, it kills itself because of the stratum thread.
Code:
*** 0:00 *** 3/3 08:18 **************************************
Eth: Mining CLO on http://10.69.1.10:8547 for 0:00
Eth speed: 41.982 MH/s, shares: 0/0/0, time: 0:00
Eth: Accepted shares 0 (0 stales), rejected shares 0 (0 stales)
Eth: Incorrect shares 0 (0.00%), est. stales percentage 0.00%
Eth: Average speed (5 min): 36.004 MH/s
Eth: New job #fec49625 from http://10.69.1.10:8547; diff: 14108624MH
Eth: New job #585617fa from http://10.69.1.10:8547; diff: 14115512MH
Eth speed: 41.946 MH/s, shares: 0/0/0, time: 0:00
Eth: New job #e9d5c9cf from http://10.69.1.10:8547; diff: 14115512MH
Stratum thread not responsive for 51 s
Thread(s) not responding. Restarting.
@PhoenixMiner are you out there?
March 10, 2019, 01:35:01 PM
I'm having the same issue. I'm mining Callisto (CLO). I had been using Parity with its built-in stratum support, but since they have not updated their Parity client (rust-callisto) for last week's hard fork, I tried to switch to Geth, which doesn't have stratum - thus needing to switch to the RPC interface for get_work. This is where the issue comes in.
I am setting the coin on the commandline.
I tried setting a "password' in commandline as suggested above, but that doesn't make a difference. Over the past few days, I've also tried as many other options as I can. It appears that the issue is it's connecting on RPC for get_work, but there's still a watchdog for a Stratum thread - but since we're not using Stratum, it sees no activity and bombs out.
See here - you can see that the coin is properly set, has connected to geth successfully, and has started mining, but at 51s, it kills itself because of the stratum thread.
I am setting the coin on the commandline.
I tried setting a "password' in commandline as suggested above, but that doesn't make a difference. Over the past few days, I've also tried as many other options as I can. It appears that the issue is it's connecting on RPC for get_work, but there's still a watchdog for a Stratum thread - but since we're not using Stratum, it sees no activity and bombs out.
See here - you can see that the coin is properly set, has connected to geth successfully, and has started mining, but at 51s, it kills itself because of the stratum thread.
Code:
*** 0:00 *** 3/3 08:18 **************************************
Eth: Mining CLO on http://10.69.1.10:8547 for 0:00
Eth speed: 41.982 MH/s, shares: 0/0/0, time: 0:00
Eth: Accepted shares 0 (0 stales), rejected shares 0 (0 stales)
Eth: Incorrect shares 0 (0.00%), est. stales percentage 0.00%
Eth: Average speed (5 min): 36.004 MH/s
Eth: New job #fec49625 from http://10.69.1.10:8547; diff: 14108624MH
Eth: New job #585617fa from http://10.69.1.10:8547; diff: 14115512MH
Eth speed: 41.946 MH/s, shares: 0/0/0, time: 0:00
Eth: New job #e9d5c9cf from http://10.69.1.10:8547; diff: 14115512MH
Stratum thread not responsive for 51 s
Thread(s) not responding. Restarting.
@PhoenixMiner are you out there?
March 08, 2019, 11:38:23 PM
Im running MSOS (ubuntu 16.04, 4.15.0 kernel, 17.5 amd driver) and ever since the ETH upgrade I have had 10 times the amount of stale and invalid shares at the pool. I tried everything including dialing back the OC/UV settings and nothing could get my previous stability back. No mater what I tried it was always 5% stales and 1% invalid shares (normal was 0.5% or less stales and a random invalid every so often). I switched to claymore and while its running at a slower hash Im getting a way higher overall usable hashrate and little to no stales/ invalid. this is only at the pool side the miner side shows way less stales and invalids than what the pool shows. Im thinking this is a linux only issue as my windows rig running 4.1c is fine no unusual stales or invalids, and the linux/MSOS rig running claymore is fine but phoenix on linux/MSOS is just trash on stability now.... If you got any tricks to fix it let me know if not maybe its something you guys can look into on the next release?
thanks for any help
thanks for any help
March 08, 2019, 02:59:36 PM
6 x RX480 bc drivers. Miner crashes: "phoenix miner debugger detected" while claymore works well((( Could someone point me to the decisions? Thanks in advance)
Are you running windows? Do you have the window defender running? if so, you either have to disable defender or create an exceptions folder and place phoenix miner in it.
Thanks, but it doesn't help(
Sorry did you may have to disable defender thru registry, delete the current version of PhxM you have and download a new version of PhxM before this may work.
I've done all as you sad but with no results( Thanks any way. Next step - upgrade GPU drivers or going on with Claymore
March 08, 2019, 07:49:28 AM
What is the best AMD drivers for windows 10. Since new Phoenix Miner, I get all sort of issues. My rigs used to never reboot, even after 40days+ stable. And now they reboot every 7 hours. Sometime a card is also disconnected
Can we use same BIOSes for mining ETH with RX (polaris) cards?
Can we use same BIOSes for mining ETH with RX (polaris) cards?
I don't if they are the best but I have absolutely no issue on 3 RIGs with 18.3.4
March 07, 2019, 06:00:59 PM
What is the best AMD drivers for windows 10. Since new Phoenix Miner, I get all sort of issues. My rigs used to never reboot, even after 40days+ stable. And now they reboot every 7 hours. Sometime a card is also disconnected
Can we use same BIOSes for mining ETH with RX (polaris) cards?
Can we use same BIOSes for mining ETH with RX (polaris) cards?
March 07, 2019, 10:27:30 AM
6 x RX480 bc drivers. Miner crashes: "phoenix miner debugger detected" while claymore works well((( Could someone point me to the decisions? Thanks in advance)
Are you running windows? Do you have the window defender running? if so, you either have to disable defender or create an exceptions folder and place phoenix miner in it.
Thanks, but it doesn't help(
Sorry did you may have to disable defender thru registry, delete the current version of PhxM you have and download a new version of PhxM before this may work.
March 07, 2019, 04:02:24 AM
6 x RX480 bc drivers. Miner crashes: "phoenix miner debugger detected" while claymore works well((( Could someone point me to the decisions? Thanks in advance)
Are you running windows? Do you have the window defender running? if so, you either have to disable defender or create an exceptions folder and place phoenix miner in it.
Thanks, but it doesn't help(
March 07, 2019, 02:57:02 AM
6 x RX480 bc drivers. Miner crashes: "phoenix miner debugger detected" while claymore works well((( Could someone point me to the decisions? Thanks in advance)
Are you running windows? Do you have the window defender running? if so, you either have to disable defender or create an exceptions folder and place phoenix miner in it.
March 07, 2019, 02:17:10 AM
6 x RX480 bc drivers. Miner crashes: "phoenix miner debugger detected" while claymore works well((( Could someone point me to the decisions? Thanks in advance)
March 06, 2019, 11:59:38 AM
What about ZIL support for dual mine (switching when time is come) ?
March 06, 2019, 12:43:24 AM
Phoenix, allready 19.2.3 driver realeased and I sure AMD release 19.3.1 version soon. When we can use new version of your miner with support of new drivers versions?
why you would use pm with newest drivers ? you will have the same results in hashrate ... ffsJump to: