Topic: Claymore's Dual Ethereum AMD+NVIDIA GPU Miner v15.0 (Windows/Linux) - page 1293. (Read 6590757 times)

I have the same problem as Velmerk when mining eth or eth forks only.  The miner does not respond until a key is entered and then it will restart.

Here is my log file. http://pastebin.com/dnR1D9T3

Image. https://i.imgur.com/IjlKITI.png

Hey, I switched one of my rigs (6 gpu) to Claymore v4.4 from ethminer (genoil) and mining on ethermine.org. I use config.txt and epool.txt with no command line. Everything works good BUT despite finding lots of shares, the page at ethermine.org does not show my rig. It only shows the rigs using genoil miner.
I set the name in config (-eworker Rig5) as well as in epools for the failover.
Any idea what I am doing wrong?

Yes without messing with dcri and around stock clocks

In my case without monitor I'm not able overclock my cards and temperature is not visible..

CPU temp 48-40 C (i5 3570K, only Dual miner)
GPU temp 53-55 C (water cooling)
All Ok with temp.

P.S. when the monitor is disconnected or switched off, temperature isn't visible at the miner or  msi afterburn or sapphire trixx (only HWINFO64 can see all sensors).

hi, with 2 xfx 280x i get 43 mhs on ethereum  but i think i have problem with decred speed , is 630 normal?

To be on the safe side, make read-only to default? And add password option to push configs? Seems like risk of takeover by scanning bots or smth.

You can use the MSI afterburner to do all the monitoring. I do not look at the fan and temperature information in the miner.

Need help.

I have one Fury X. 53-55 C temp. PSU 650W 80+Gold

Dual miner stops sometimes and restarted only manually when pressing a key (Enter).
It's not regular problem, but 1 time at 2-3 days it can happen.

https://www.dropbox.com/s/j9iovzg6n7tvng2/need_restart_miner.png

11:49 - last text from miner (green collor)
nothing
13:00 - after pressing Enter - errors (red color) & restart.

Can you help? Thanx.

Appreciate it!

Anyone been using the miner with MiningRigRentals, here?
Been mining flawlessly on poolto.be and miningpoolhub for a while now;

Few days ago tried to connect to poolto.be through miningrigrentals;
(Havent ever tried with miningpoolhub; maybe i should!)
Miner kept giving this message:
"ETH: Stratum - socket send failed 10053, disconnect."
It had problem staying connected; kept disconnecting and reconnecting.
Reduced average hashrate to about half the usual!

Submitted a ticket to their support, initially suggested I update to 4.4 (was using 4.3.)
It tried with 4.4; had the same issue.
40 hours ago (give or take) their support asked for the op to get a copy of the miner, fiddle and come back to me;
No news yet;

Thought i'd ask here;
Anyone been doin' the same thing successfully?

p.s. Been mining, eversince, as usual using 4.4 no probs;

Could you please add CPU temp monitoring.

claymore

running 4.4 here, no command line options, just the config.txt and epool.txt.

where does it pulls rig or worker names from? I have slightly different worker names in config vs epool. sometimes it grabs one, sometimes the other. even used my password "x" a few times.

no biggies its all to the same addy but Im about to setup an ubuntu box with a couple gpus and wanted to make sure i can tell whos who.

win7pro x64, nanopool, single nitro r9 390 on this pc (my daily driver) if that helps.

Another suggestion for the config file:

- add '-config' option to specify a location for the config file (was already suggested)
- add '-log' option to specify a location for log file and/or directory (was already suggested)
- add '-rig' option for miner instance. If this option presents, then the miner still reads a config file (if no other cmdline options defined), but will understand the rig-specific syntax suggested above. That way we can use the same configuration file for both local config file and uploaded via remote manager. For configs sent remotely the '-rig' option may be ignored (since the manager knows where to send config - so the manager MUST edit the config file and send only options for THIS rig), or may be interpreted the same way (that is, use common options unless specialized ones defined for that rig name - so remote manager just uploads the generalized config file, and then the miner interprets is the same way).

I tend to the 2nd option: no '-rig' - use only common unprefixed options. There is '-rig' parameter - use common options unless specialized ones override them. This keeps compatibility with current behavior.

Of course, in this case the option is only applied to rig01:

And config processing should first collect all unprefixed active options (defaults), then override them with rig-specific options (if some are defined and there is the '-rig' option on the command line or even in the same config).

@Claymore:

- please add a notice about %NAME% to README/HISTORY files. I could not remember where did I see it, and finally found only in the help of remote manager. Would be good to see it in the main manual.
- didn't you implement the same functions for the config file? If not yet, one of implementations could be:


PS. May be this variant is better since options for the same rig are aligned:

Maybe read the README.txt of miner then? Or the same text in the 1st message of this thread on page 1? There is an example of DwarfPool command line there. All you may want is to replace the eu by us in the pool address to get better responses from nearest pool.

Yeah, I agree, posted a kind of stratum specs I implemented in my pool: https://github.com/sammy007/open-ethereum-pool/blob/develop/docs/STRATUM.md

Tested your miner tonight, seems everything is smooth. This stratum implementation is a reverse engineered "-esm -0"/eth-proxy.

I hope you meant "eth_submitHashrate" instead of "eth_sendHashrate".

guys,

just set up a simple mining PC with one R9 390

want to try to mine on dwarfpool. I'm in US so which command line should I put?

sorry for stupid question - tried to read 119 pages, but it is way to much

Check first page of this thread.

@Claymore Just downloaded 4.4 beta 2, but windows defender identified it as a trojan. Previous versions were fine with AV, file identified was Trojan:Win32/Spursint.A!cl

Something new in this release