PhoenixMiner 6.2c: fastest Ethereum/Ethash miner with lowest devfee (Win/Linux)

[PhoenixMiner]

There is a new beta for Windows: PhoenixMiner 3.5b, which can be downloaded 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_3.5b_Windows.zip
    ===================================
   SHA-1: 6e7be7b9a12fd2db2cd8c3c37f94a3f4a21397f9
 SHA-256: d8978bfc0c0b11f684528a3fb8b9d89ab1d09d63097c5e23a07a19d6cc5cf195
 SHA-512: 90253e600ff86a3d7b1fa33af19933a84735d04305e16090e085ca33c3a0935844156506b4f80cd1c288f6e7e9a9bbb5564662dcf84bf1d1ce7d62afb46ff8ff

There are only small fixes in 3.5b, hopefully mitigating the problems with some drivers (Fatal error: debugger detected, etc.).

Note that there isn't a new beta for Linux, so 3.5a remains the latest for Linux (it is in the same folder as above, and you can see its checksums in this post: https://bitcointalk.org/index.php?topic=2647654.msg45385531#msg45385531.

A few notes:

• The new -clgreen kernels have completely different optimal GT values, so you have to run auto-tune again to get the optimal hashrate with them
• Unfortunately, the time wasn't enough to implement HW control in Linux, so only the monitoring works there (i.e. showing fan speeds and temperatures but not controlling them). This will be implemented in the next release.

Finally, here are the changes since the 3.0c again:

* Support for Linux (tested on Ubuntu 16.04 LTS and Debian 9.5 stable). Note that we have tested with AMD GPU-Pro drivers (not the open source drivers) and the official Nvidia closed-source drivers. Please note that this is the first version that supports Linux, so some glitches are to be expected. Do not hesitate to write us about any problems.
* With the recent drop in prices of most cryptos, we are trying to come up with ways to increase the profitability. Since the cost of the electric power a major factor now, we worked hard to create new, power-efficient kernels for most widely used AMD cards (RX580/570/560/480/470/460). To use these kernels, you must specify the option -clgreen 1 on the command-line, or in the config.txt file. In our tests the green kernels lower the power consumption by 2-3% on the supported cards. These kernels may also slightly lower the hashrate (by 0.2-0.5%), so you have to check if they are more efficient for you depending on the electricity costs in your area.
* Small improvements in the normal AMD kernels to increase hashrate (RX4xx, RX5xx, Tonga, and Fury)
* Added advanced stats option (you have to turn this on with the command-line option -astats 1) that will try to estimate the daily earnings depending on the current price of the coin you are mining and the current difficulty. Note that this is only an estimation and it uses information from third-party web sites, which may not be accurate.
* Added support for direct mining of DubaiCoin (DBIX)
* Added -leaveoc option to prevent resetting of the HW OC settings to defaults on exit
* Many small fixes

[Marvell2]

  v3.5a detects all devices but then ends with error

Code:

Phoenix Miner 3.5a Windows/msvc - Release build
-----------------------------------------------

Available GPUs for mining:
GPU1: GeForce GTX 1070 (pcie 2), CUDA cap. 6.1, 8 GB VRAM, 15 CUs
GPU2: GeForce GTX 1070 (pcie 3), CUDA cap. 6.1, 8 GB VRAM, 15 CUs
GPU3: GeForce GTX 1070 (pcie 5), CUDA cap. 6.1, 8 GB VRAM, 15 CUs
GPU4: GeForce GTX 1070 (pcie 7), CUDA cap. 6.1, 8 GB VRAM, 15 CUs
GPU5: GeForce GTX 1070 (pcie 8), CUDA cap. 6.1, 8 GB VRAM, 15 CUs
GPU6: GeForce GTX 1070 (pcie 9), CUDA cap. 6.1, 8 GB VRAM, 15 CUs
FATAL ERROR: Debugger detected

  Please try the new 3.5b version, which should fix the problem. Here is how to download and verify it: https://bitcointalk.org/index.php?topic=2647654.msg45442768#msg45442768

don't work
old 3.0c work

Code:

1970.01.04:05:04:49.399: unkn OpenCL driver version: 17.31.0
2018.09.08:20:15:21.223: main Phoenix Miner 3.5a Windows/msvc - Release build
2018.09.08:20:15:21.223: main Cmd line: -amd -coin clo -pool stratum+tcp://moac.bylt.gq:5005 -wal mywalletxxxxxx -worker amd -pass x -log 1 -tstop 70 -cdm 0 -retrydelay 0 -cclock 965 -mclock 1875 -powlim 0 -cvddc 850 -mvddc 900 -clgreen 1
2018.09.08:20:15:21.223: main Available GPUs for mining:
2018.09.08:20:15:21.223: main GPU1: Radeon RX 570 Series (pcie 2), OpenCL 2.0, 4 GB VRAM, 32 CUs
2018.09.08:20:15:21.265: main ADL library initialized

please add moac coin

  Do you have only one GPU? Is the miner just freezes, or crashes? Please try the new 3.5b version, which may fix the problem. Here is how to download and verify it: https://bitcointalk.org/index.php?topic=2647654.msg45442768#msg45442768

Using 3.5a and can not get it to work. I have Gigabyte Vega56 oc gaming with regmod Burnsted editor.

Everytime I launch it connects fine, acts like it is mining but hash rate is 0 then crashes after a while. I can run stable on Fireice currently 1900 h/s. Do you have any recommendations to get stable in Phoenix or even to get any hash rate at all?

    It's possible that your OC settings are not stable for ETH mining. Vega is notoriously power hungry, so we suggest to start with fairly low core clocks (around or under 1000 Mhz) and power limit -10% or even less. If the problem persists, you can try he new 3.5b version, which may fix the problem. Here is how to download and verify it: https://bitcointalk.org/index.php?topic=2647654.msg45442768#msg45442768. If nothing else helps, please send the log from the beginning to see if the DAG is constructed properly, etc.

3.5a won't start at all, 3.0c working perfectly since release

    Please try the new 3.5b version, which may fix the problem. Here is how to download and verify it: https://bitcointalk.org/index.php?topic=2647654.msg45442768#msg45442768. If this doesn't help, please send us the log file to see what exactly goes wrong.

anyone seen this error ? happens right when i launch, happens even after a fresh install wtf ?

Code:

Faulting application name: PhoenixMiner.exe, version: 0.0.0.0, time stamp: 0x5b12b632
Faulting module name: igdrclneo64.dll, version: 0.0.0.0, time stamp: 0x5a96b19b
Exception code: 0xc0000005
Fault offset: 0x0000000000030819
Faulting process id: 0x12e0
Faulting application start time: 0x01d4481ab1bcf677
Faulting application path: C:\Latest PhoenixMiner\PhoenixMiner.exe
Faulting module path: C:\Windows\System32\DriverStore\FileRepository\igdlh64.inf_amd64_250db833a1cd577e\igdrclneo64.dll
Report Id: 032ad2c0-acc2-4048-b285-f7afb3049b2e
Faulting package full name:

    Please try the new 3.5b version, which should fix the problem. Here is how to download and verify it: https://bitcointalk.org/index.php?topic=2647654.msg45442768#msg45442768. If this doesn't help, please send us the log file to see when the error occurs, which may gives us a clue what is causing it.

https://imgur.com/a/kTCssZG    its normal?? Thats -clgreen 1

   Yes, the optimal GT values for the green kernels are completely different from the other kernels (just as the GT values for -clkernel 1 and -clkernel 2 are usually also quite different from each other). So, you are doing the right thing letting auto-tune to find them. Also, please note that even if all GPUs are the same model, there are always differences and not every time the optimal GT values are the same.

3.5 working fine with 14 GPU rig (nvidia), no difference in hashrate, same stable as 3.0

I finally gave it a try now that profitability has tanked and I was shutting my farm down.
Good miner, similar to Claymore, easy to setup and use and lots of information displayed.

Works well on my AMD Rx 570's, with maximum tweaking I am getting about 0.2 mh per care more with Phoenix and consuming 4W power less compared to claymores.
Also this miner has a lower devfee, so theres three title advantages in all - 1% extra hash rate, 4% lower power, and 0.35% lower fee.
If I ever boot up my farm again, I would use this miner going forward. Also appreciate the regular updates to it, which hasn't been the case for claymores.

   Good news! Almost every message after releasing new version is about problems (which is quite normal and alright), so it's quite nice to get a few positive reports. Don't hesitate to write us with any ideas for improvements, etc.

ok ill try the new version

[53nsk]

    Please try the new 3.5b version, which may fix the problem. Here is how to download and verify it: https://bitcointalk.org/index.php?topic=2647654.msg45442768#msg45442768. If this doesn't help, please send us the log file to see what exactly goes wrong.

3.5b same result, log:

1970.01.01:07:15:48.496: unkn OpenCL driver version: 18.5.1
2018.09.09:22:48:59.585: main Phoenix Miner 3.5b Windows/msvc - Release build
2018.09.09:22:48:59.585: main Cmd line:
2018.09.09:22:48:59.585: main config.txt: -pool stratum+tcp://etc.hvpps.net:3333 -wal 0x4afc488F6E42A6502A187A268da302D156B19C79.AwesomeMiner -pass 2.0 -proto 4 -coin etc -stales 1 -fret 5 -ptimeout 5 -ftimeout 180 -rate 1 -cdm 0 -amd -clKernel 1 -clNew 1 -clf 1 -eres 4 -lidag 1 -gser 0 -gpureset 0 -tstop 67 -tstart 50 -gt 12,10,8,12 -mi 14 -clgreen 1
2018.09.09:22:48:59.585: main Available GPUs for mining:
2018.09.09:22:48:59.585: main GPU1: Radeon RX 580 Series (pcie 1), OpenCL 2.0, 8 GB VRAM, 36 CUs
2018.09.09:22:48:59.585: main GPU2: Radeon RX 580 Series (pcie 3), OpenCL 2.0, 4 GB VRAM, 36 CUs
2018.09.09:22:48:59.585: main GPU3: Radeon RX 580 Series (pcie 4), OpenCL 2.0, 4 GB VRAM, 36 CUs
2018.09.09:22:48:59.585: main GPU4: Radeon RX 580 Series (pcie 6), OpenCL 2.0, 8 GB VRAM, 36 CUs
2018.09.09:22:48:59.641: main ADL library initialized

[borox]

I tried the 3.5b. No change:

Code:

Phoenix Miner 3.5b Windows/msvc - Release build
-----------------------------------------------

Available GPUs for mining:
GPU1: GeForce GTX 1070 (pcie 2), CUDA cap. 6.1, 8 GB VRAM, 15 CUs
GPU2: GeForce GTX 1070 (pcie 3), CUDA cap. 6.1, 8 GB VRAM, 15 CUs
GPU3: GeForce GTX 1070 (pcie 5), CUDA cap. 6.1, 8 GB VRAM, 15 CUs
GPU4: GeForce GTX 1070 (pcie 7), CUDA cap. 6.1, 8 GB VRAM, 15 CUs
GPU5: GeForce GTX 1070 (pcie 8), CUDA cap. 6.1, 8 GB VRAM, 15 CUs
GPU6: GeForce GTX 1070 (pcie 9), CUDA cap. 6.1, 8 GB VRAM, 15 CUs
FATAL ERROR: Debugger detected

[haliy-2017]

-clgreen 1   what is this parameter

[sirkorro]

   Good news! Almost every message after releasing new version is about problems (which is quite normal and alright), so it's quite nice to get a few positive reports. Don't hesitate to write us with any ideas for improvements, etc.

Did you see: https://bitcointalk.org/index.php?topic=2647654.msg43145022#msg43145022

[adi1972]

Running Phoenixminer 3.5b now.

No issues starting with 12 gpu mix of 8 RX580, 2 GTX1070 and 1 R9 290. Using Overdriventool for AMD tweaking and NvidiaInspector for Nvidia gpus.

All in a single rig. FYI, I just copy/paste my bat file from version 3.0c.

[miner95]

PhoenixMiner 3.5b works stable for my only 2x Sapphire RX580 Nitro+ rig but I don't see any change on my GPUs power draw when using new green kernels.
I get same hashrate (30.3MH) with same GPU only power draw in GPU-Z sensors tab (90W for every card) when using new kernels.

[Branko]

PhoenixMiner 3.5b works stable for my only 2x Sapphire RX580 Nitro+ rig but I don't see any change on my GPUs power draw when using new green kernels.
I get same hashrate (30.3MH) with same GPU only power draw in GPU-Z sensors tab (90W for every card) when using new kernels.

Never use GPU-Z for power measurements, hardware watt meter is the only sure way. Everything else is just software estimate
that is often pretty wrong

Theyre not expensive, either:

https://www.ebay.com/itm/AC-power-meter-220v-digital-wattmeter-energy-monitor-electricity-consumption-KI/153101520651?hash=item23a58fcf0b:m:mAjCDfztrd1tW9iDnDvS1xw

[simcity4]

miner freeze
here log

1970.01.01:03:45:10.965: unkn OpenCL driver version: 17.31.0
2018.09.10:10:42:07.996: main Phoenix Miner 3.5b Windows/msvc - Release build
2018.09.10:10:42:07.996: main Cmd line: -amd -coin clo -pool stratum+tcp://moac.bylt.gq:5005 -wal mywallet -worker amd -pass x -log 1 -tstop 70 -cdm 0 -retrydelay 0 -cclock 965 -mclock 1875 -powlim 0 -cvddc 850 -mvddc 900
2018.09.10:10:42:07.996: main Available GPUs for mining:
2018.09.10:10:42:07.996: main GPU1: Radeon RX 570 Series (pcie 2), OpenCL 2.0, 4 GB VRAM, 32 CUs
2018.09.10:10:42:08.025: main ADL library initialized

[Digital_Seytan]

miner freeze v3.5b detects all devices but then ends with error !!!!

Code:

Phoenix Miner 3.5b Windows/msvc - Release build
-----------------------------------------------

Available GPUs for mining:
GPU1: GeForce GTX 1060 (pcie 1), CUDA cap. 6.1, 6 GB VRAM, 10 CUs
GPU2: GeForce GTX 1060 (pcie 2), CUDA cap. 6.1, 6 GB VRAM, 10 CUs
GPU3: GeForce GTX 1060 (pcie 3), CUDA cap. 6.1, 6 GB VRAM, 10 CUs
GPU4: GeForce GTX 1060 (pcie 4), CUDA cap. 6.1, 6 GB VRAM, 10 CUs

please HELP

[53nsk]

Tried 3.5b on 2 more amd rigs - same issue. Drivers are 18.5.1 and 18.5.2.

[Risecrypto]

Decided to try Phoenix Miner after Claymore kept giving DAG errors last few days and shutting the Mining Rig off.

Running 10 GPU RX580
roughly Hashrate is 1.5 Mh/s more on each card then Claymore miner.

seems to run a little more stable, and Dag file are currently not causing Dag error after 12hrs mining.
(Claymore gave Dag errors)

Will keep monitoring and update you guys.

[laik2]

BUG report: Linux version PM 3.5a has support for fan/temp only upto 7 devices.
http://prntscr.com/kspvgc
Temperature monitoring will not work on 7+ devices, otherwise it seems the fastest and most efficient ethash miner to me. Good job!
EDIT: Does rmode on linux execs reboot.bat or reboot.bash/sh ?
EDIT2: It does read temp/fan till PCI 0x09, miner marks it as 0x10 but its actually 0x0a.

[ZoomhashLLC]

PhoenixMiner 3.5b works stable for my only 2x Sapphire RX580 Nitro+ rig but I don't see any change on my GPUs power draw when using new green kernels.
I get same hashrate (30.3MH) with same GPU only power draw in GPU-Z sensors tab (90W for every card) when using new kernels.

Never use GPU-Z for power measurements, hardware watt meter is the only sure way. Everything else is just software estimate
that is often pretty wrong

Theyre not expensive, either:

https://www.ebay.com/itm/AC-power-meter-220v-digital-wattmeter-energy-monitor-electricity-consumption-KI/153101520651?hash=item23a58fcf0b:m:mAjCDfztrd1tW9iDnDvS1xw

We have found even some plug-in watt meters are not accurate and can easily become uncalibrated.

Depending on your voltage you can find a cheap metered PDU that will tell you your amperage draw for under $150.

[Soliqesh]

green kernel 1275w 304mh/s, without 308mh/s 1287w on wattmeter. 

[salvo2002]

Hi all, just reporting my results... on:

PhoenixMiner 3.5a -- First release with support for Linux

Code:

4.10.17-hiveos #1 SMP Sun Dec 10 08:48:43 EET 2017 x86_64 x86_64 x86_64 GNU/Linux
DISTRIB_ID=Ubuntu
DISTRIB_RELEASE=16.04
DISTRIB_CODENAME=xenial
DISTRIB_DESCRIPTION="Ubuntu 16.04.5 LTS"

Based on this post over at HiveOS community: https://forum.hiveos.farm/t/custom-miner-integration/4521/212

2-3 MH/s increase (reported hashrate) over Claymore 11.9, BUT a significant increase in stale shares! [using https://www.hiveon.net/ ETH pool]

screenshot:
https://ibb.co/fBu5h9

[PhoenixMiner]

3.5b same result, log:

1970.01.01:07:15:48.496: unkn OpenCL driver version: 18.5.1
...

I tried the 3.5b. No change:

Code:

...

miner freeze
here log
...

   Thank you for reporting this problem. We have send a PM to each of you with additional information and questions that will help us resolve it.

-clgreen 1   what is this parameter

   Activates new power-efficient kernels for AMD RX460/470/480/560/570/580. They aren't faster than the normal kernels (in most cases are slightly slower but not always) but should lower your power consumption by 2-3 W per card (RX570). Whether they are more optimal for you depends on the price of electricity and the settings of your cards. Please note that you have to run auto-tune again to find the optimal GT settings for these kernels as they are different from the normal kernels.

   Good news! Almost every message after releasing new version is about problems (which is quite normal and alright), so it's quite nice to get a few positive reports. Don't hesitate to write us with any ideas for improvements, etc.

Did you see: https://bitcointalk.org/index.php?topic=2647654.msg43145022#msg43145022

   Yes, thank you for this suggestion. We are planning much more feature-rich remote management API in the future releases (we will keep compatibility with Claymore's as fallback). Note that you can get the per-GPU hashrate with the current API. The Nvidia overclocking options are planned for the next release.

PhoenixMiner 3.5b works stable for my only 2x Sapphire RX580 Nitro+ rig but I don't see any change on my GPUs power draw when using new green kernels.
I get same hashrate (30.3MH) with same GPU only power draw in GPU-Z sensors tab (90W for every card) when using new kernels.

   You should see about 2-3W per card but probably not with GPU-Z. We have measured 2.4W per RX570 with settings 1100/2000  MHz and 870mV core voltage. The hashrate drop was from 29.15 to 29.0 MH/s.

green kernel 1275w 304mh/s, without 308mh/s 1287w on wattmeter. 

   Please make sure that you have auto-tuned the green kernels (the old GT values are not optimal for the green kernels). Sometimes it may take same time before you see the real difference in power (30 mintues or so after starting). Also the drops in the power and in the hashrate depend on the settings of the card and the ratio between the core clock and memory clocks, as well as the memory timings. The green kernels can be used only on some gpus by specifying -clgrean for each gpu individually: for example -clgreen 1,1,0,0,0 will run the green kernels only on the first two GPUs in five GPU rig.

miner freeze v3.5b detects all devices but then ends with error !!!!

Code:

....

please HELP

   Can you tell us if you see any error message window, or the miner just freezes without showing anything?

Здpaвcтвyйтe кoллeги мaйнepы!
cтoлкнyлcя c пpoблeмoй пpи нacтpoйкe мaйнepa PhoenixMiner , в OS HiveOS
Hacтpaивaл coглacнo oпиcaния в пocтy: https://forum.hiveos.farm/t/custom-miner-integration/4521/212?u=chivekubik
нacтpoить yдaлocь, нo пocлe зaпycкa мaйнepa, cмoтpю в лoги и вижy:

Eth: New job #2699da4d from eu1-etc.ethermine.org:4444; diff: 4000MH
Eth speed: 0.000 MH/s, shares: 0/0/0, time: 0:01
GPUs: 1: 0.000 MH/s (0) 2: 0.000 MH/s (0) 3: 0.000 MH/s (0)
Eth speed: 0.000 MH/s, shares: 0/0/0, time: 0:01
GPUs: 1: 0.000 MH/s (0) 2: 0.000 MH/s (0) 3: 0.000 MH/s (0)
Eth speed: 0.000 MH/s, shares: 0/0/0, time: 0:01
GPUs: 1: 0.000 MH/s (0) 2: 0.000 MH/s (0) 3: 0.000 MH/s (0)
Eth speed: 0.000 MH/s, shares: 0/0/0, time: 0:01
GPUs: 1: 0.000 MH/s (0) 2: 0.000 MH/s (0) 3: 0.000 MH/s (0)
Eth: New job #8e242334 from eu1-etc.ethermine.org:4444; diff: 4000MH

xeшpeйт нe пoднимaeтcя в тeчeниe 15 мин.
Teмпepaтypa GPU нe пoднимaeтcя
________
Moe жeлeзo:
OS:
DISTRIB_ID=Ubuntu
DISTRIB_RELEASE=16.04
DISTRIB_CODENAME=xenial
DISTRIB_DESCRIPTION=“Ubuntu 16.04.4 LTS”
__
GPU:
GeForce GTX 1080 8119 MiB · MSI - 3 шт.
____
Пpилaгaю cкpиншoты c нacтpoйкaми https://prnt.sc/ksozce
и xeшpeйтoм https://prnt.sc/ksozsi
Фepмa https://prnt.sc/kspa8p
_______________
Пoмoгитe пoжaлyйcтa, нacтpoить кoppeктнo мaйнep

   Can you please send us (or post here) the first few pages from the log file? It seems that the DAG generation never finishes but we can't be sure because we can see the start of the log in your screenshot, and then an excerpt after a few minutes but not what happens in between.

BUG report: Linux version PM 3.5a has support for fan/temp only upto 7 devices.
http://prntscr.com/kspvgc
Temperature monitoring will not work on 7+ devices, otherwise it seems the fastest and most efficient ethash miner to me. Good job!
EDIT: Does rmode on linux execs reboot.bat or reboot.bash/sh ?
EDIT2: It does read temp/fan till PCI 0x09, miner marks it as 0x10 but its actually 0x0a.

   Thank you for reporting this problem. We haven't tested the Linux version on a rig with more than 6 GPUs yet and sure enough, there is a problem. We have found the issue and it will be fixed in 3.5b, which will be released later today or first thing tomorrow after we are sure that there aren't any more problems that we can find here.

Hi all, just reporting my results... on:

PhoenixMiner 3.5a -- First release with support for Linux

Code:

4.10.17-hiveos #1 SMP Sun Dec 10 08:48:43 EET 2017 x86_64 x86_64 x86_64 GNU/Linux
DISTRIB_ID=Ubuntu
DISTRIB_RELEASE=16.04
DISTRIB_CODENAME=xenial
DISTRIB_DESCRIPTION="Ubuntu 16.04.5 LTS"

Based on this post over at HiveOS community: https://forum.hiveos.farm/t/custom-miner-integration/4521/212

2-3 MH/s increase (reported hashrate) over Claymore 11.9, BUT a significant increase in stale shares! [using https://www.hiveon.net/ ETH pool]

screenshot:

   Thank you, this is very helpful. Most probably the miner can't recognize the OpenCL driver and some of the most aggressive driver-specific optimizations aren't used. Can you please check if you have a line like this:

Code:

2018.09.10:06:24:11.757: main OpenCL driver version: 17.40

in the start of PhoenixMiner log (it should be among the first five to ten lines in the log file)? Also, could you please tell us the version of your AMD drivers?

[bitcoin.dbi]

  Activates new power-efficient kernels for AMD RX460/470/480/560/570/580. They aren't faster than the normal kernels (in most cases are slightly slower but not always) but should lower your power consumption by 2-3 W per card (RX570). Whether they are more optimal for you depends on the price of electricity and the settings of your cards. Please note that you have to run auto-tune again to find the optimal GT settings for these kernels as they are different from the normal kernels.

Do i need to kick out -gt 11 command from bat file if i want to use this new green kernel?

The green kernels can be used only on some gpus by specifying -clgrean for each gpu individually: for example -clgreen 1,1,0,0,0 will run the green kernels only on the first two GPUs in five GPU rig.

If i got rig with 5 cards (1-4 AMD and 5  Nvidia) what should i write in bat file? -clgreen 1,1,1,1,0 or -clgreen 1,1,1,1
Thanks.

-rmode <n> Selects the restart mode when a GPU crashes or freezes:
     0: disabled - miner will shut down instead of restarting
     1: restart with the same command line options - this is the default
     2: reboot (shut down miner and execute reboot.bat)

Is it possible to add rmode which will reboot PC instead of miner (want to use wdog if one cart will stuck)? Or maybe i can just put "shutdown /r /o /t 0" in reboot.bat file?

[ZoomhashLLC]

Very excited to see the Linux version in fruition PhoenixMiner, great job!

We may look into this version after the beta for our customers depending on the stability.