hello patrike, I have a question about C# API, in the recent betas you've changed the initializer for PredefinedPool class now it is declared as PredefinedPoolProvider(AwesomeMiner.Infrastructure.Intelligence.OnlineServiceType, string, AwesomeMiner.Infrastructure.Mining.Pools.MiningRegion) can you please describe what MiningRegions are available? I've tried to guess but didn't succeed. thank you. Depends on your pool. You can find the regions at the pools or in awesomeminer options in profit switching section. I appreciate your desire to help, but I'm sure you didn't understand what I'm asking. I use Nicehash EU North server in my C# script. have tried every possible name that could be used. using NicehashRegion.EU results in incompatible type assignment warning. also, script editor complains that AwesomeMiner.Infrastructure.Mining assembly is missing, so type MiningRegion is undefined. hope that's enough details to find the issue. patiently waiting for a fixed build, @patrike. thanks again. This specific class has not changed in about two years. The available MiningRegions for Nicehash did however change a few months ago, when they introduced new regions (where the MiningRegion can be one of: USAWest, USAEast, EuropeWest,EuropeNorth) like MiningRegion.USAWest. Can you share some context how you use it and in what way it changed/broke in the latest development release? You can send the details via PM if you want. Thanks! sent you a PM. |
|
|
|
hello patrike, I have a question about C# API, in the recent betas you've changed the initializer for PredefinedPool class now it is declared as PredefinedPoolProvider(AwesomeMiner.Infrastructure.Intelligence.OnlineServiceType, string, AwesomeMiner.Infrastructure.Mining.Pools.MiningRegion) can you please describe what MiningRegions are available? I've tried to guess but didn't succeed. thank you. Depends on your pool. You can find the regions at the pools or in awesomeminer options in profit switching section. I appreciate your desire to help, but I'm sure you didn't understand what I'm asking. I use Nicehash EU North server in my C# script. have tried every possible name that could be used. using NicehashRegion.EU results in incompatible type assignment warning. also, script editor complains that AwesomeMiner.Infrastructure.Mining assembly is missing, so type MiningRegion is undefined. hope that's enough details to find the issue. patiently waiting for a fixed build, @patrike. thanks again. |
|
|
|
hello patrike, I have a question about C# API, in the recent betas you've changed the initializer for PredefinedPool class now it is declared as PredefinedPoolProvider(AwesomeMiner.Infrastructure.Intelligence.OnlineServiceType, string, AwesomeMiner.Infrastructure.Mining.Pools.MiningRegion) can you please describe what MiningRegions are available? I've tried to guess but didn't succeed. thank you. |
|
|
|
increase your pagefile size and don't connect your display to any GPU that is busy with mining, Thanks for your response, but my virtual mem is, and has always been increased appropriately. Also, I have been using TeamViewer to remotely connect, therefore there's no monitor connected to the unit. I should have added that they're 4gb cards, but to my understanding they work fine mining ETH still - 5 of my other 4gb cards in that rig are all running as they should. are you on Windows, and is your integrated GPU enabled? if not then Windows will reserve some amount of RAM on GPU0 and it may show decreased performance or fail to mine at all. |
|
|
|
Hi all, hope everyone is well.
I have a situation with one of my RX480's on GPU0 all of a sudden giving me only 2 mh/s on the latest Claymore miner, as well as during a test using PhoenixMiner.
A few hours ago I was getting 31 mh/s for quite some time with absolutely no issues at all.
Since I've discovered this problem, I've made sure it was in compute mode (it was), I've properly removed and updated drivers.
I've even reverted my card back to it's stock bios. None of this has given me my precious 31 mh/s back, sadly.
Strange thing is, if I disable compute mode, while enabling graphics mode, I get a max of 12 mh/s on that card. Compute mode only gives me 2 mh/s, no matter what stock/bios modded, tweaks I do.
What do you folks think is the problem here? If anyone has any ideas, I'd love to hear them.
Perhaps the riser is crapping out on me?
Cheers.
increase your pagefile size and don't connect your display to any GPU that is busy with mining, |
|
|
|
I don't know why but I'm not having these issues with DAG size.
I have 3 rigs each with 6 RX 580 4Gb running on Windows 10.
Maybe because I have Onboard video?
exactly |
|
|
|
Could you please consider adding 6gb solvers for ct31? You already have this for ct32 and it would allow 8gb cards to mine this algo under win10. 4gb solvers for everything would also be cool  it's pointless and does not worth it. |
|
|
|
Guys, why do I have this hard regression on my hashrate over time in Handshake with 1.98?
My rig starts at 897 MH/s and after 10 mins or so drop all the way to 877 MH/s.
I am only using Gminer on my NVidia rigs and haven't seen this much of a drop on any algo so far.
Using standard command line miner.exe --algo handshake --server hns.f2pool.com:6000 --user xyz.rig1
so you say that 2% hashrate loss is a hard regression?  |
|
|
|
Hi all! Do you know how to fix the problem when main window of awesome miner software displayed above other subwindows with menus or dialogues? Sometimes I can see a piece of window and move it to another place outside the main window, but sometimes I even can not see other windows under the main window and can not control them at all.
I've seen this issue several times too. restarting Awesome Miner usually fixes it |
|
|
|
|
change all the Pstate voltages, not just the last one. if you decrease the last value you should decrease all the values before too.
core clock and core voltage for each Pstate should be higher than previous values (so they rise gradually from P0 to P7) and then it will be fine.
|
|
|
|
Is there any way to control the rigs with the main application from main computer AND have them auto-profit-switch when the main computer is offline? It doesn't seem efficient to run a non-mining computer 24/7 just to send commands, if I run copies of main application on all rigs, they auto-switch by themselves, so it would be logical that if I pay money for a full version, I should get even more convenience and utility, not less. Can't I somehow run the main app AND the remote agent, or something, I want the rigs to auto-switch by themselves AND to be able to control them from main computer without remote-desktoping to every rig and manually changing settings
you can run main AM application on one of your rigs then  |
|
|
|
Patrike, I'm thinking to buy the Premium version of Awesome Miner, there is just one thing I do not understand and cannot find answer to: does the remote agent only execute commands from the main application, or it performs all operations on its own? In other words, do I have to run the main application on a separate computer to control the mining rigs? If so, what happens if the main computer loses connection or freezes? does the profit switching stop until the control is restored?
yup. profit switching won't work but mining will continue. |
|
|
|
as far as I understand - it should work. The power feed to a North American residence is normally provided by a center-tapped transformer, with the center tap of the transformer secondary grounded. the full secondary winding produces 240 Volts.  |
|
|
|
|
C29M is disabled for lolMiner, does not work even if I manually enable it and add "--coin C29M" - looks like the custom command line argument is not used so the miner silently fails.
|
|
|
|
Awesome Miner version 7.2.6
GPU mining
- Support variables in the command line field for a pool
- The configuration file for the mining software NanoMiner and XmRig can be modified via the Properties of a Managed Miner
Integration
- Nicehash Eaglesong pool added
- Nicehash SHA-256 AsicBoost pool added in addition to the standard SHA-256 pool
- Updated block explorer for ETC wallet balance
Mining software
- CpuMiner-Opt 3.11.1
- Phoenix Miner 4.9c
Corrections
- Correction to nVidia GPU initialization on Linux
seen some strange bugs like negative profit estimate (??) for dual CKB+ETH mining if NBMiner is on top of miners list inside the profit profile. if I set the ETH hashrate to 0 then the profit switcher shows correct profit estimate, NBMiner starts and runs fine, but AM thinks that it's not in dual mode, shows that the miner is mining ETH and only ETH hashrate is used to show current profitability. additional CKB profit is ignored. also CKB+ETH mode is not supported for GMiner. the whole dual mining implementation seems broken and buggy. should be much better and easier to understand if you remove the "dual hashrate" field, and instead show all the dual mining combos as separate profit profile algo entries (like "Ethereum+Eaglesong") with two assigned hashrates, if both parent algos are enabled. thank you  |
|
|
|
Does anyone have such problem - on Win 7, v15, drvs 436.30 and 441.66 and GTX1070 cards hashrate is about 22Mhash.... Tried to clean drivers with DDU and reinstall them, tried with/withous straps, w/wo OC etc.... On other algorythms speed is same as before, no change. And some months ago with older claymore all was fine, but now, with v15 such problem
upd: same issue on Phoenix miner, but all fine on nanominer and gminer.... can't even guess what it can be...
increase your core clock. |
|
|
|
Is is normal to have different hashrate for eth and etc? Nvidia gpus. Difference is about 2.5% more when mining ethereum. 4.8c version.
why there is a difference with the same config eth mining and etc 3% difference is nobody understands because of different DAG size. |
|
|
|
Don't know if you guys have heard but apparently there is a fork coming up on New Years Day to delay the Ice age once again. For some reason I have no idea why they decided to make a hard-fork on a holiday which is celebrated in most of the world. They had issues with this before when they made a testnet launch on a weekend and they ran into issues since many devs took the weekend off. Most likely same will happen on New Years day with all the devs being hung over or passed out instead of watching the fork and taking action if there are any issues. Anyways its going to bring the block times back to 13 seconds because we are currently at 17 seconds according to, https://etherscan.io/chart/blocktimeSo it should make mining slightly more profitable than currently which is record low mining profitability levels since maybe 2015. Increase of blocktime from 13 to 17 seconds is reducing the amount of eth given out to miners by 3000 eth per day. :-) it will reduce the block time from the current 17 to the previous 13 per second You understood it wrong it will create more ETH per mining hour hoping that the price will remain the same or will go up, will give miners much more profit, but I'm seeing the scenario where ETH is going backwards with the value  I think that he wrote about current situation so 3k ETH/day are now lost (or not created) because of rising difficulty and block time. |
|
|
|
|
hello patrike,
I think it would be great if you could add a feature that will allow us to modify the profit estimate stats from profit switching pools, using a C# script or a custom formula.
then instead of using "current estimate/24hr estimate/24hr actual" for profit switching we could use some complicated formulas to improve the profit estimate accuracy - for example, the profit switcher could use arithmetic mean of current estimate and actual 24hr profit, and so on.
what do you think about this?
also, there's a bug with ProHashing 24hr actual profit stats. the values should be multiplied by 1000 to be correct.
thank you
|
|
|
|
IS VERSION 1.84 SERIOUSLY BUGGED? Why was this version removed from GitHub? --scryptr what happens with binary file for ver. 1.84 on GitHub  1) we forgot to add some check in Cuckatoo31 solver, that may lead to crash of miner. 2) seems 1.84 run slower on mining edition cards under windows 10, we have to check it P104-100s have 10+% slower C31 hashrate with 1.85. |
|
|
|
|
Show Posts
