![]() Note that most options require restart in order to change.Ĭurrently the following options can be changed without restarting: -mi, -gt, -sci, -clf, -nvf, -gpow, and most of the hardware control parameters ( -tt, -fcm, -fanmin, -fanmax, -powlim, -tmax, -ttli, -cclock, -cvddc, -mclock, -mvddc, -ppf, -straps, -vmt1, -vmt2, -vmt3, -vmr). ![]() Reload the settings if config.txt is edited/uploaded remotely. You can also specify if you have a secure VPN connection and want to bind the CDM port to it Set the CDM remote monitoring port (default is 3333). Selects the level of support of the CDM remote monitoring: If you want to benchmark the ProgPOW BCI algorithm, use the options -bench -coin bci Remote control options -cdm If you want to bench the dual mining, use the options -bench -dcoin blake2s. If you specify only the -bench option, you will benchmark the ethash algorithm. Report hashrate to the pool: 1 - yes, 0 - no (1 is the default), 2 - (for solo mining only) use alternative name of the report method eth_submitHashRate instead of eth_submitHashrate Benchmark mode -bench ,-benchmark īenchmark mode, optionally specify DAG epoch. Recheck period for Solo/GetWork mining (default: 200 ms) Seconds to wait before reconnecting (default: 5) This setting is 30 minutes by default set to 0 to disable automatic switch back to primary pool. Switch back to primary pool after n minutes. Reconnect if no new ethash job is receved for n seconds (default: 600) Switch to next pool afer N failed connection attempts (default: 3) Submit stales to the dual mining pool: 1 - yes (default), 0 - no If you want to put all dual mining pools in dpools.txt, you need to set -dcoin blake2s in the command-line or in config.txt to force the miner to load the dual mining pools from dpools.txt -dstales Phoenix viewer names in red password#Submit stales to the failover pool: 1 - yes (default), 0 - noĭual mining pool password (most pools don’t require it, use x as password if unsure)Ĭurrently only the Blake2s algorithm is supported for dual mining. Same as -pool but for the failover poolįailover ethash wallet (if missing -wal will be used for the failover pool too)įailover ethash password (if missing -pass will be used for the failover pool too)įailover ethash worker name (if missing -worker will be used for the failover pool too)įailover ethash stratum protocol (if missing -proto will be used for the failover pool too)įailover devfee Ethash coin (if missing -coin will be used for the failover pool too) Submit stales to ethash pool: 1 - yes (default), 0 - noįailover ethash pool address. ethermine, nanopool) - this is the default, works for most poolsĮthash coin to use for devfee to avoid switching DAGs: Selects the kind of stratum protocol for the ethash pool: Pool options -pool Įthash pool address (prepend the host name with ssl:// for SSL pool, or for solo mining).Įthash wallet (some pools require appending of user name and/or worker).Įthash password (most pools don’t require it, use x as password if unsure).Įthash worker name (most pools accept it as part of wallet). So you can use the same command line options as the ones you would have used with Claymore’s miner. Note that PhoenixMiner supports most of the command-line options of Claymore’s dual Ethereum miner PhoenixMiner in the command-line examples below. ![]() Under Linux you need to replace PhoenixMiner.exe with. Phoenix viewer names in red download#You can download PhoenixMiner 6.2c from here: You can use this list as a reference for all Launch Parameters supported by PhoenixMiner. Hardware control options (you may specify these options per-GPU).That in itself is a lot of the reason people turned to other Veiwers cause of all the constant changes. Instead of trying to make SL so “New & Improved” they need to focus on fixing everything that is broken right now. As for SL Veiwer 2, I don’t like it at all. There really isn’t much of a difference at all. I personally used the Emerald Veiwer myself and am now on Emergence. guess what? You are going to lag regardless of how damn good your internet connection is.Īll in all, get your facts straight before spouting off its all the other veiwers accessing SL cause you are dead freaking wrong. If you live in, lets say, Kentucky and a bad storm comes through between where you live and the main SL office where the main internet connection is…. Also, there is the memory, the graph card, internet connection all the way down to SL’s/Open Veiwers connection to the net. Trust me I know as the fact on my desktop lag is very rare but my laptop is an almost constant. A lot of the lag is contributed to your own PC’s. There are a lot of things that contribute to lag. The lag is SL and it don’t matter what freaking Veiwer you use… there will be lag. The lag has NOT a damn thing to do with all the other viewers at all. I remember when 5k people online at a time was amazing. For your info, I have been in SL over 4 yrs now. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |