![]() 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. 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).Went through everything in the discord, everything I found here, all the tricks I'd used several times before to get it working.Īgain, for what they charge for transactions, it should work a lot better, but give those ideas a try. Couldn't get the miners to start mining again after that. It worked fine for days, and then it just stopped working. I had my rig mining this way for a while. Make sure you save the profile in afterburner in one of the five slots. Then you should be able to use afterburner on that rig to set your settings. Make a custom config in the web interface, then assign it to the rig in question. The devs don't seem to care to fix issues or provide features the community is asking for, despite charging some of the highest transaction fees. Honestly, Cudo seems to be a neglected wreck. You'll get the famous "Error: No jobs queued" message, and your miners won't even start. And Cudo miner is notorious (at least the Windows client) for not wanting to start at all when overclocking is disabled. There is a way to get afterburner settings to stick, but it requires you turning overclocking OFF in Cudo miner. Welcome to the reason I don't use Cudo miner anymore. ![]() What am I doing wrong? Very grateful for any help from users with more experience than me! After a half hour, or possibly an hour, one (or two) of the GPUs will suddenly "forget" the settings, and start chugging at 100% power and heating up again. My remedy has been to use MSI Afterburner (as others have done) to manually downclock the core, overclock the memory, and reduce power % down to reasonable levels. Windows can see the proper GPUs, as well as their stats and power levels, but the Cudo Miner software is not following set power limits! It's cranking everything to 100% and running my GPUs very hot in the process. I can't find any way in the web interface to resolve this issue. ![]() It doesn't seem to see them, nor does it appear to be using them properly. With the Cudo OS installed, after downloading drivers and restarting a few times, it says I have three 1660 super installed, and it mines at a rate of 20Mh/s total, which is worse than even a single 1660 super would do, but I only have ONE 1660 super installed. I am really struggling to get it working, however. So I am reaching out multiple ways in the hopes that SOMEONE will be able to help me here! I love the idea of running Cudo Miner, as it came highly recommended by a friend. At least with Cudo overclocking disabled, MSI afterburner will now keep settings, and it has been running mostly ok since. So now it works, but even with admin privileges, Cudo won't follow power and heat limits that I set when allowed to do the overclocking itself. ![]() Edit: I ended up reinstalling and deleting and clearing data enough times that I got it up and running finally with overclocking options OFF.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |