Topic: PhoenixMiner 6.2c: fastest Ethereum/Ethash miner with lowest devfee (Win/Linux) - page 404. (Read 784958 times)
June 02, 2018, 03:12:32 AM
Once it finds the proper settings - you can copy them to your startup parameters.
June 02, 2018, 01:53:48 AM
Or do you waste 5-10mins of sub optimal hashrates at the beginning of every time you start the miner?
How often do you restart your miner?That’s irrelevant to my question.
At the very least it’s useful to know what values the auto tuning settled on
June 02, 2018, 01:09:53 AM
Or do you waste 5-10mins of sub optimal hashrates at the beginning of every time you start the miner?
How often do you restart your miner? June 01, 2018, 11:34:19 PM
Possible feature request.
How does PM handle the auto-tune settings? Are they “remembered” in any way? Or do you waste 5-10mins of sub optimal hashrates at the beginning of every time you start the miner?
If they aren’t remembered, maybe you could have the miner auto-append the config.txt or the start.bat file with the optimized gt values? That way you won’t have to auto-tune when simply re-running the miner.
How does PM handle the auto-tune settings? Are they “remembered” in any way? Or do you waste 5-10mins of sub optimal hashrates at the beginning of every time you start the miner?
If they aren’t remembered, maybe you could have the miner auto-append the config.txt or the start.bat file with the optimized gt values? That way you won’t have to auto-tune when simply re-running the miner.
June 01, 2018, 09:42:32 PM
Can anyone explain the time value circled:
https://www.dropbox.com/s/4nnsa2aii9bvb41/mine.jpg?dl=0
The time value below it is the uptime for the miner, but I do not understand what the time value for the pool represents.
https://www.dropbox.com/s/4nnsa2aii9bvb41/mine.jpg?dl=0
The time value below it is the uptime for the miner, but I do not understand what the time value for the pool represents.
When pool disconnects, miner begins new timer. That's your new time count since that or other event occurred. Current total time still ticking. At least, that's how I understand it.
June 01, 2018, 07:54:41 PM
Can anyone explain the time value circled:
https://www.dropbox.com/s/4nnsa2aii9bvb41/mine.jpg?dl=0
The time value below it is the uptime for the miner, but I do not understand what the time value for the pool represents.
https://www.dropbox.com/s/4nnsa2aii9bvb41/mine.jpg?dl=0
The time value below it is the uptime for the miner, but I do not understand what the time value for the pool represents.
June 01, 2018, 07:54:04 PM
Running 18 AMD cards across 2 rigs.
1x rig using 3.0a and i have a 1 MH increase from 2.9e. It is now the same hashrate as claymore 11.6. Running at 277.6 across 9 cards. Cards are 3x MSI rx 570 gaming x, 2x rx 580 Nitro+, 3x rx 570 pulse and 1x MSI rx 570 armor.
2.9e GT was set at 17 across the board.
RUnning auto-tuned GT.
Stable for 24 hours now.
1x rig just started running 3.0b upgraded from 2.9e with random cards between MSI gaming X, armor, powercolor, xfx and asus. .3 MH increased from 276.1 to 276.4 but the hashrate bounces around alot more with averages coming to the same as 276.1. Auto tuned GT.
2.9e GT was set at 14 across the board.
1x rig using 3.0a and i have a 1 MH increase from 2.9e. It is now the same hashrate as claymore 11.6. Running at 277.6 across 9 cards. Cards are 3x MSI rx 570 gaming x, 2x rx 580 Nitro+, 3x rx 570 pulse and 1x MSI rx 570 armor.
2.9e GT was set at 17 across the board.
RUnning auto-tuned GT.
Stable for 24 hours now.
1x rig just started running 3.0b upgraded from 2.9e with random cards between MSI gaming X, armor, powercolor, xfx and asus. .3 MH increased from 276.1 to 276.4 but the hashrate bounces around alot more with averages coming to the same as 276.1. Auto tuned GT.
2.9e GT was set at 14 across the board.
June 01, 2018, 07:26:32 PM
Sorry if this is a stupid request, but would it be possible to add a feature for naming gpu's? I know you can re-number them, but custom alphanumeric naming might help me take out some frustration on poorly performing cards. 
June 01, 2018, 05:19:15 PM
Reading all the posts regarding dual mining (dead atm IMO).... I wonder if it was possible to mine ethash (memory is everything, core almost doesn't matter) alongside x16r (core is everything, memory almost doesn't matter).... any thoughts?
Imagine that.. both algos largely asic-resistant..... a gpu miner's dream come true... if any1 comes up with it, yeah it would really push the gpus to the limit, BUT it would be a killer thing even if both algos ran at 80% of there solo performance/efficiency.
Imagine that.. both algos largely asic-resistant..... a gpu miner's dream come true... if any1 comes up with it, yeah it would really push the gpus to the limit, BUT it would be a killer thing even if both algos ran at 80% of there solo performance/efficiency.
June 01, 2018, 11:40:11 AM
any plans on doing dual?.
Dual mining is dead. XVG just got attacked again. Sia and decred are owned by ASICs...For dual mining, there is claymore. I hope Phoenix won't do the mistake to implement dual mining.
Whoever introduces ethash/zilliqa dual mining first, will make great job
Zilliqa is which algo?
Its very unique (they call whole thing "sharding" instead "mining"), and its partially based on ethash
June 01, 2018, 11:33:17 AM
have been trying to use Phoenix on one of my small rigs -- keep getting a variety of cuda errors sometimes including illegal instruction -- with the miner crashing right after start -- it also now has decided not to write logfiles so i don't know what the problem is now -- running win 10 with 4gig ddr3 with 2-1060 3gb 2-1060 6gb 2 r9 280x and 1 rx570 8gb -- currently using claymore with no issues. Have increased the virtual memory to 60 gig from 30 gig added the -log 2 commands -- still crashes right away -- any suggestions would be appreciated. The rig is really just a spare parts rig -- but hashes quite well.
ok turns out part of this is win 10 -- lets just say it sucks .
The cuda errors are still happening will run for 20 minutes and then will crash -- running on ubq so dag shoud not be an issue -- cards are overclocked but not by much -- did try it with stock and same thing happens
ok turns out part of this is win 10 -- lets just say it sucks .
The cuda errors are still happening will run for 20 minutes and then will crash -- running on ubq so dag shoud not be an issue -- cards are overclocked but not by much -- did try it with stock and same thing happens
June 01, 2018, 08:51:04 AM
With -gsi 30, my reported hashrate on the nanopool is much lower than miner window.. please fix it.
why is the -gt ?? option has no effect whatsoever on the mining result hashrate on the Nvidia GPUs, everything for amd and for nvidia gpus niks.al you do not put anything on the start.bat if you press S is standard on -gt 15. people best solution for the -GSI 0 and the -minrigspeed certainly 40 or 50 lower put due to startup rig, unfortunately on the pool lower report hashrate but there is currently nothing to do until version 3.0c comes out.
-------------------------------------------------------------
WiNEther Miner is a graphical interface to use with ethminer with advanced watchdog options and monitoring................. . .. Download : https://github.com/digitalpara/WiNETH
June 01, 2018, 07:56:07 AM
Thanks dev I keep using the version 3.0b, with a small adjustment in the start bat the -minrigspeed 133.000 to -minrigspeed 80.000 at least now no restart anymore, but -gsi 0 setting stays much lower report hashrate on the pool ethermine see.I hope therefore also version 3.0C everything is solved soon and no additional problems.
-------------------------------------------------------------
WiNEther Miner is a graphical interface to use with ethminer with advanced watchdog options and monitoring................. . .. Download : https://github.com/digitalpara/WiNETH
-------------------------------------------------------------
WiNEther Miner is a graphical interface to use with ethminer with advanced watchdog options and monitoring................. . .. Download : https://github.com/digitalpara/WiNETH
June 01, 2018, 07:45:27 AM
how to set -gt in 3.0b?!
tried
-gt 8,9,10 - but it ignored the input and started autotuning ?!
PS: 1 hour later it still autotunes (up tp gt values 50) - on system with just 3 cards...
tried
-gt 8,9,10 - but it ignored the input and started autotuning ?!
PS: 1 hour later it still autotunes (up tp gt values 50) - on system with just 3 cards...
Same isssue here, -gt is not working anymore
We can't reproduce this problem here: when -gt is specified, the auto-tune doesn't start automatically, and when it isn't, it does as it should be. Could you please send as a log file (especially the first few pages)?Thanks dev for update -gsi option on -gsi 0 is super only on the pool reported hashrate is no longer correct with what on the screen is given much lower, and -gt option does not work properly rig start again with the communication setting -minrigspeed not achieved therefore restart. like an early solution. 
Yes, we can reproduce the -gsi and -minrigspeed problems, sorry about that. They will be fixed in 3.0c.How to see which gt parameter is used while it mined?
You can press 's' key in the console and you will see the current -gt values like this:Quote
Current -gt 89,91,91
June 01, 2018, 06:03:21 AM
Thanks dev for update -gsi option on -gsi 0 is super only on the pool reported hashrate is no longer correct with what on the screen is given much lower, and -gt option does not work properly rig start again with the communication setting -minrigspeed not achieved therefore restart. like an early solution.
----------------------------------------------------------------------------
WiNEther Miner is a graphical interface to use with ethminer with advanced watchdog options and monitoring................. . .. Download : https://github.com/digitalpara/WiNETH
----------------------------------------------------------------------------
WiNEther Miner is a graphical interface to use with ethminer with advanced watchdog options and monitoring................. . .. Download : https://github.com/digitalpara/WiNETH
Same isssue here, -gt is not working anymore
June 01, 2018, 04:52:22 AM
Thanks dev for update -gsi option on -gsi 0 is super only on the pool reported hashrate is no longer correct with what on the screen is given much lower, and -gt option does not work properly rig start again with the communication setting -minrigspeed not achieved therefore restart. like an early solution.
----------------------------------------------------------------------------
WiNEther Miner is a graphical interface to use with ethminer with advanced watchdog options and monitoring................. . .. Download : https://github.com/digitalpara/WiNETH
----------------------------------------------------------------------------
WiNEther Miner is a graphical interface to use with ethminer with advanced watchdog options and monitoring................. . .. Download : https://github.com/digitalpara/WiNETH
June 01, 2018, 04:35:09 AM
I try 3.0b on nvidia gpus. Its 5 - 6 mh/s better hasrate if i compare 3.0b or older version. Nice 
June 01, 2018, 04:04:29 AM
How to see which gt parameter is used while it mined?
June 01, 2018, 02:48:32 AM
how to set -gt in 3.0b?!
tried
-gt 8,9,10 - but it ignored the input and started autotuning ?!
PS: 1 hour later it still autotunes (up tp gt values 50) - on system with just 3 cards...
tried
-gt 8,9,10 - but it ignored the input and started autotuning ?!
PS: 1 hour later it still autotunes (up tp gt values 50) - on system with just 3 cards...
June 01, 2018, 01:41:18 AM
PhoenixMiner 3.0b can be downloaded from:
(MEGA links are no longer active)
Here are the checksums to verify the download:
Note that this is not an official release yet. The changes from 3.0a are:
For reference, these were the new features and changes in 3.0a:
WARNING! Because the new auto-tune functionality is automatically started if you don't specify -gt parameter, your hashrage will be lower and will fluctuate in the first few minutes while the miner searches for the best GT values for each GPU. If you want to avoid that, you have to specify -gt value on the command-line (or in config.txt). If you want the same behavior as 2.9e, specify -gt 15 (15 is the default value of the GT parameter).
(MEGA links are no longer active)
Here are the checksums to verify the download:
Code:
File: PhoenixMiner_3.0b.zip
SHA-1: 6c41a7cff9180cdbc625c88bff272685f0c78961
SHA-256: 11be2019e469d0deccc860963ddbe6c597d8b53e2d4c792d446962fd6792d7ce
SHA-512: 80d321bfb04d8b331d9b3e3f60365f5deed997f83bccc3ae2cc824c4e1ac4542d66cb783b4d5c1a9fb62e136f8e93b1ed2bce8eb9978a988256362ea5eae61c9
SHA-1: 6c41a7cff9180cdbc625c88bff272685f0c78961
SHA-256: 11be2019e469d0deccc860963ddbe6c597d8b53e2d4c792d446962fd6792d7ce
SHA-512: 80d321bfb04d8b331d9b3e3f60365f5deed997f83bccc3ae2cc824c4e1ac4542d66cb783b4d5c1a9fb62e136f8e93b1ed2bce8eb9978a988256362ea5eae61c9
Note that this is not an official release yet. The changes from 3.0a are:
- Added option -gsi to set the speed stats interval (5-30 seconds, default 5; 0 turns off the speed stats). The detailed stats are still shown every 45 seconds and aren't affected by the -gsi value
- Fixed crashing with Vega cards with AMD drivers 18.4.1 and newer
- Bugfix: don't restart the miner if -minrigspeed is exceeded but some cards are in auto-tuning
- Other small changes
For reference, these were the new features and changes in 3.0a:
Quote
- Implemented auto-tune functionality which will find the best GT value for each GPU. You can activate it by either omitting the -gt parameter in the command line, or by pressing 'z' in the console. Note that auto-tune process takes about 3 to 5 minutes on average and during this time the hashrate will be lower and will go up and down. You can abort the auto-tuning by pressing the 'g' key in the console window.
- Added support for 'x' key in console window. This will allow you to select a single GPU for manual or automatic GT tuning
- Added support for direct mining (without DAG switching for DevFee) of the following coins: Nekonium (NUKO), MIX, EtherGem (EGEM), AURA, Hotelbyte Coin (HBC), Genom (GEN), EtherZero (ETZ), Callisto (CLO). See the -coin option documentation in Readme.txt for details how to specify the coin you are mining.
- Added support for on-the-fly reload of config.txt file and applying the new options by pressing the key 'c' in the console window. This allows more convenient adjustment and fine-tuning of big mining rigs by avoiding the requirement to restart the miner every time an option is changed. Note that most options require restart in order to change. Currently the follwing options can be changed without restaring: -mi, -gt, -clf, -nvf, and all hardware control parameters (-tt, -fanmin, -fanmax, -powlim, -tmax, -cclock, -cvddc, -mclock, -mvddc).
- Added -cdmrs option to reload the settings if config.txt is edited/uploaded by a remote manager. This allows you to change and reload the config.txt options via remote manager without access to the console window of the miner.
- Small improvements in AMD kernels
- Added -nvf 3 setting that could solve some problems with unstable Nvidia cards (but may affect hashrate negatively)
- Added option -acm to turn on AMD compute mode on the supported GPUs. This is equivalent of pressing 'y' in the miner console.
- Added option -retrydelay that sets the pause between the reconnection attempts in seconds (min value 0, default value: 20)
- Added option -resetoc to reset the HW overclocking setting on startup to their default values
- Added option -gpureset, which forces full reset of the GPU when the miner is paused (or before DAG generation when switching DAG epochs). This is designed to avoid problems like the hashrate drop of GeForce GTX1080 Ti after pause/resume. This option can be specified per GPU and is turned on by default for GTX1080 Ti.
- Added option -gser for serializing of DAG creation if your PSU(s) can't take all GPUs generating DAG simultaneously.
- Graceful shutdown when closed by the close button of the console window (including reseting OC settings to defaults)
- Multiple small improvements and fixes
WARNING! Because the new auto-tune functionality is automatically started if you don't specify -gt parameter, your hashrage will be lower and will fluctuate in the first few minutes while the miner searches for the best GT values for each GPU. If you want to avoid that, you have to specify -gt value on the command-line (or in config.txt). If you want the same behavior as 2.9e, specify -gt 15 (15 is the default value of the GT parameter).
Jump to: