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

Hi Gents,
Anyone using Claymore v11.6 on ethOS 1.3.1?
Since the latest update of the miner to v11.6 I am loosing connectivity for monitoring the miner on port 3333 after 15-21 hours of mining.
While Claymore keeps mining with no troubles only the monitoring is an issue. If I restart the mining process the monitoring is restored. I had no issue with the previous updates.
Tried to set the port manually but the problem still exist.
Anyone else experiencing this issue or has a solution?
Thanks in advance.

Are you from the past? Welcome to the future, now read this f*cked first post of this thread and your dreams come true.

Mr. Claymore,

I am using your miner and I am very satisfied its performance. However I have an issue about fee. Previously, I have to say you are very succesful with your job. And this fee is absolutely your right. There is definitely no problem. I have never thought about using the miner with nofee options. It is not an argument about fee. But I just want to say, when I mine Dual (Not Double), fee increase to %2 (so it is double). However my profit does not increase to double while I mine dual. In my opinion %1.5 fee on dual mining more fair. Of course it is your issue and I will continue using your miner. Just you might think about this.

Best Regards
Utku ORUN
ETH: 0x1674f04fca1edc56aee7eb7efbbe5d354a173c62

seems -oldkernels 0 helped me to for stable hashrate

I have seen the same issue with ethermine, and only on a wireless connection using SSL.  Once I switch over to NON-SSL, I no longer get that issue.  I noticed this because my one rigs was sending a ton of stale shares to the pool, but my other rig wasn't (wired rig) and I assumed it was a specific rig issue with wireless connectivity since it was only one rig but both are on the same internet connection.  But switching back to NON-SSL should solve it until ethermine gets back to you.  On occasion I would notice the discnnect message also when using SSL on any ethermine server.

Haven't ever seen it on ethermine, but I've seen it occasionally on nicehash when first starting up - seems to be a temporary "pool overloading on making new connections" issue, as it normally resolves itself in a few minutes.

Dropping the wait time down from the default 20 secs to 10 secs seemed to help a little, but that might have been a coincidence as I only tried that once.


I'm think Claymore dropped support for pre-GCN AMD cards somewhere along the line - he definitely has NOT added and has stated he has no plans TO add -asm cores for older cards so you might just need to reconfigure to "don't use ASM" on those.

Just a query if anyone can help. I keep getting a “socket was closed remotely (by pool)” message come up since i restarted my rig. I havent changed any settings and my internet connection is working fine. I have contacted the pool (ethermine) but no response yet. Just wondered if anyone else has experienced this problem lately?

@AzzAz , Many thanks for your suggestion... currently after changing it to 32000 it run successfully for few minutes now.
I will observed further...

The E3 is NOT going to "spike" the total network hashrate for Ethereum or the other ethash coins.

It will take about 2 MILLION of those units built and operating JUST TO MATCH THE EXISTING HASHRATE.

They aren't shipping 'till mid-July timeframe.

In the almost 2 YEARS since Bitmain introduced the S9 (which was a LOT more efficient than anything else available for months, and STILL is the most efficient SHA256 miner that is shipping) they might have sold a little over ONE MILLION of them (total SHA256 network hashrate says up to 2 million, but you also have to factor in the Avalon 721/741 sales, the eBang sales, sales of whatever miners with Bitfury chips have been built, however much hashrate LW.COM has on it's internally-built miners, and at least one "smaller fry" mining operation I know of that is using their own chip).

The E3 will push network hashrate - but it's NOT going to be a "spike", there is too much EXISTING hashrate from mining rigs that are the SAME OR BETTER efficiency than the E3 announced specs.


It's a lot closer to the situation in Scrypt mining when Bitmain introduced the L3 - which STILL hasn't managed to push all "older rigs" out of profitable service if you have cheap enough electric and has a LOT of competition helping it TRY to push A2/Titan/Alcheminers out of profitability.

Thanks for the response, i will try and check..
Will inform you..

Does it work with BIOS modded cards?
I've seen conflicting info about which Adrenalin drivers do so and which don't.

That's also why Claymore's recommendation of 16.12.x made ZERO sense, as 16.11.x and up DISABLED support for BIOS modded cards while 16.9.x and 16.10.x DID work with them.