Claymore's Dual Ethereum AMD+NVIDIA GPU Miner v15.0 (Windows/Linux)

[trader1a]

The attack on Verge XVG coin does not look good. Where are we going now? What currency do we go to for dual mining?

Blake2s Neva, Taj, Info, Shield?
Keccak smartcash?

 

Keccak maxcoin

[1714873092]

1714873092

[1714873092]

1714873092

[Bigdrago]

Hi Claymore.
If phoenix really is faster (as he claims) u should lower fee to 0.60% (he have 0.65%.)
That would make you steal his customers.

[WhackOBill]

V11.6 has eliminated the "incorrect shares" that I was getting in prior versions.  Was running just over 1% ... now none.  No other changes than moving from 11.5 to 11.6.  Thanks Claymore.

[WhackOBill]

Maybe ignorant question, but how are the ASICs going to work? I thought the whole point of DAGs was to prevent ASICs. How do the ASICs fit the DAG file on their chips affordably?

They don't ... they have DDR3 memory attached to the ASICs / FPGAs.  If you look on the Bitmain site, you can see that the device is a) twice the size of their other miners and b) is about the hash equivalent of 4x 580's.  If you consider the 800 watts of draw, it uses more Watts/MH than a rig with 4x 580s.  About the only attractive thing about it is the price ... $800.

The only decent way to attack the Ethash mechanism is to take advantage of the 64 DAG lookup steps in the algorithm.  If you broke your DAG storage into 64 or 128 or 256 separately accessible pieces, you could pipeline the 64 lookup's and take advantage of the random nature of the lookup addresses.  The point is to do 64 lookup's at the same time taking advantage of their being in separate pieces of memory ... usually.  In this way you could pipeline the Ethash and have 64 going on at the same time with each at one point along the 64 step process ... ignoring the pre and post processing.  Occasionally, you would have a collision when two or more lookup's needed the same DAG section and so you'd stall for that step.  It's difficult to get all of that address and data bus space hooked into an ASIC or FPGA.  So it's still a hard problem ... not impossible though.

[blockaudit]

1. CVE-2017-16929 works only if you specified -mport > 0 and don't use password (-mpsw). Also it can crash miner:

From History.txt:

...
v10.2
- fixed critical issues in remote management feature (attacker could crash miner even in read-only mode).
...

That was the last known security issue and it was fixed in v10.2 and above.

Here is my opinon:
Yes my miners have "remote management" feature that allows administrators to upload files, restart miners etc. It's not a vulnerability itself. Also I know that this feature can be used by attackers, therefore by default miner uses "read-only" mode which ignores all commands except "miner_getstat1" (I mean recent versions of my miners, very old versions have no "read-only mode"). User must specify "-mport" option and positive port manually to enable potentially dangerous commands. Also I added "-mpsw" option that allows users to set a password for remote management. Also miner shows warning during startup if "read-only" mode is disabled and -mpsw is missed. Also I added necessary information to Readme file. And, of course, it's bad idea to make these ports public, they must be used in local network only, "-mport" option can expose the port to specified network interface only.
To make this feature dangerous, user must do the following:
1. Disable "read-mode", ignore miner warning.
2. Ignore "-mpsw", i.e. don't set a password, again ignore miner warning.
3. Expose the port(s) to internet.
So, in my opinion, I did everything to make this feature safe as much as possible, but some users have no idea/knowledge what they do when they change default settings.

• cve-2017-16929 - authenticated directory traversal - as statet in the advisory (link) requires remote mgmt enabled (write) and you need the password if set
  
• cve-2017-16930 - unauthenticated buffer overflow - as statet in the advisory (link) requires remote mgmt enabled; read-only is also affected; attacker does not need to have a password; This case "could cause a crash" (best case) whereas one would likely aim for remote code execution to hijack the process (shellcode -> exploit; worst case; consider your machine compromised if your vulnerable version was reachable from the internet).

Yep, it would be easier to reason about the security of the code if it were open source, or at least had a formal code audit.

[z0n0]

v11.6:

- improved hashrate for weak Nvidia cards by about 1%.
- zero devfee for 3GB cards in Windows 10, same as for all 2GB cards.
- applied some tricks to increase available memory for 3GB cards in Windows 10 so you can mine ETH a bit longer.
- now you can press "y" key to turn on "Compute Mode" in AMD drivers for all cards (Windows only).
- Linux version: removed openssl library dependency.
- improved "-logfile" option, now you can use it to specify a folder for log files, use slash at the end to do it, for example, "-logfile logs\".
- added "-epoolsfile" and "-dpoolsfile" options.
- remote management: now "miner_getstat2" command also returns PCI bus index for every GPU.
- a few minor bug fixes and improvements.

Thanks Claymore, for bringing life back to 3GB cards, worked right off the bat!

+1, I can mine Eth on 1060 3GB cards in W10 only with Claymore, all other miners fail now. Also 0% developer fee

No luck on Win7 though...  

[Lunga Chung]

Does anyone have random disconnects from ethermine?

I noticed that some miners appear offline on the pools side but when i log in i see they are submitting shares, only thing I noticed that the latency doubled (from 60 to 120ms in my case). Using 11.5 version previously 10.6 never had this...

Can someone point me for what to look in a claymor log file maybe i missed something.

Search this pattern in log
ETH: Stratum - Failed to connect, retry

Also ethermine's new UI might highlight rig that's offline in red if they don't get any update within 20 minutes. Most of them are false alarm. That's normal, nothing to worry as long as ethermine gets the update in the next round.

I did find this actually, maybe some more experienced can have a look:

02:40:40:115   1164   ETH: checking pool connection...
02:40:40:115   1164   sent: {"worker": "", "jsonrpc": "2.0", "params": [], "id": 3, "method": "eth_getWork"}

02:40:40:209   1164   buf: {"jsonrpc":"2.0","id":0,"result":["0x658de68c04f3cb57c14378332bccf71f9cca302c1db3e52ed587090636422c54","0xa74dd84414948aba4bfd6580908dbf9c32a494aa336609746d19a35bb4cccb24","0x000000006df37f675ef6eadf5ab9a2072d44268d97df837e6748956e5c6c2116"]}

02:40:40:678   11d0   em hbt: 15, fm hbt: 93,
02:40:40:678   11d0   watchdog - thread 0 (gpu0), hb time 547
02:40:40:678   11d0   watchdog - thread 1 (gpu0), hb time 234
02:40:40:678   11d0   watchdog - thread 2 (gpu1), hb time 297
02:40:40:678   11d0   watchdog - thread 3 (gpu1), hb time 609
02:40:40:678   11d0   watchdog - thread 4 (gpu2), hb time 297
02:40:40:678   11d0   watchdog - thread 5 (gpu2), hb time 609
02:40:40:678   11d0   watchdog - thread 6 (gpu3), hb time 140
02:40:40:678   11d0   watchdog - thread 7 (gpu3), hb time 453
02:40:40:678   11d0   watchdog - thread 8 (gpu4), hb time 609
02:40:40:678   11d0   watchdog - thread 9 (gpu4), hb time 297
02:40:40:678   11d0   watchdog - thread 10 (gpu5), hb time 297
02:40:40:678   11d0   watchdog - thread 11 (gpu5), hb time 609
02:40:41:444   c8   srv_thr cnt: 1, IP: 192.168.1.5
02:40:41:444   c8   recv: 51
02:40:41:444   c8   srv pck: 50
02:40:41:444   c8   srv bs: 0
02:40:41:444   c8   sent: 335
02:40:45:772   1164   sent: {"id":6,"jsonrpc":"2.0","method":"eth_submitHashrate","params":["0xadd3ef8", "0x0000000000000000000000000000000000000000000000000000000033ef23e2"]}

02:40:46:522   fc4   srv_thr cnt: 1, IP: 192.168.1.5
02:40:46:522   fc4   recv: 51
02:40:46:522   fc4   srv pck: 50
02:40:46:522   fc4   srv bs: 0
02:40:46:522   fc4   sent: 335
02:40:50:132   1164   ETH: checking pool connection...
02:40:50:132   1164   sent: {"worker": "", "jsonrpc": "2.0", "params": [], "id": 3, "method": "eth_getWork"}

02:40:50:226   1164   buf: {"jsonrpc":"2.0","id":0,"result":["0x658de68c04f3cb57c14378332bccf71f9cca302c1db3e52ed587090636422c54","0xa74dd84414948aba4bfd6580908dbf9c32a494aa336609746d19a35bb4cccb24","0x000000006df37f675ef6eadf5ab9a2072d44268d97df837e6748956e5c6c2116"]}

02:40:50:554   1164   buf: {"jsonrpc":"2.0","id":0,"result":["0xaeef20c127f6068a2e4c19681e2ee97ddd2aeed92ecf84fe7ee95f30363cafb9","0xa74dd84414948aba4bfd6580908dbf9c32a494aa336609746d19a35bb4cccb24","0x000000006df37f675ef6eadf5ab9a2072d44268d97df837e6748956e5c6c2116"]}

02:40:50:554   1164   ETH: 04/05/18-02:40:50 - New job from eu1.ethermine.org:4444
02:40:50:554   1164   target: 0x000000006df37f67 (diff: 10000MH), epoch 179(2.40GB)
02:40:50:554   1164   gpu #2 dt 0.15 (0%, good)
02:40:50:554   1164   gpu #3 dt 0.15 (0%, good)
02:40:50:554   1164   ETH - Total Speed: 182.312 Mh/s, Total Shares: 17089, Rejected: 0, Time: 108:18
02:40:50:554   1164   ETH: GPU0 30.318 Mh/s, GPU1 30.471 Mh/s, GPU2 30.483 Mh/s, GPU3 30.095 Mh/s, GPU4 30.487 Mh/s, GPU5 30.458 Mh/s
02:40:51:570   e54   srv_thr cnt: 1, IP: 192.168.1.5
02:40:51:570   e54   recv: 51
02:40:51:570   e54   srv pck: 50
02:40:51:570   e54   srv bs: 0
02:40:51:570   e54   sent: 335
02:40:52:211   1334   checked ETH share on CPU, spent 4ms
02:40:52:211   1334   sent: {"id":13,"method":"eth_submitWork","params":["0x4b1517000258e5ad","0xaeef20c127f6068a2e4c19681e2ee97ddd2aeed92ecf84fe7ee95f30363cafb9","0x8b6339c1548718a413840e2f41a2142556c527b58dbd7b1fd1235826ee16520b"]}

02:40:52:211   1334   ETH: put share nonce 4b1517000258e5ad
02:40:52:226   1164   ETH: 04/05/18-02:40:52 - SHARE FOUND - (GPU 3)
02:40:52:320   1164   buf: {"jsonrpc":"2.0","id":13,"result":true}

02:40:52:320   1164   ETH: Share accepted (109 ms)!

02:40:56:258   12d8   checked ETH share on CPU, spent 6ms
02:40:56:258   12d8   sent: {"id":12,"method":"eth_submitWork","params":["0x9ab71b640a2f8dea","0xaeef20c127f6068a2e4c19681e2ee97ddd2aeed92ecf84fe7ee95f30363cafb9","0xa5f9f9f145952fb2644f5d7e0e656d060a1df6fa127fa1c0a2b685aa3cfe0384"]}

02:40:56:258   12d8   ETH: put share nonce 9ab71b640a2f8dea
02:40:56:273   1164   ETH: 04/05/18-02:40:56 - SHARE FOUND - (GPU 2)
02:40:56:367   1164   buf: {"jsonrpc":"2.0","id":12,"result":true}

02:40:56:367   1164   ETH: Share accepted (110 ms)!

02:40:56:680   1440   srv_thr cnt: 1, IP: 192.168.1.5
02:40:56:680   1440   recv: 51
02:40:56:680   1440   srv pck: 50
02:40:56:680   1440   srv bs: 0
02:40:56:680   1440   sent: 335
02:40:57:492   11d4   GPU0 t=59C fan=37%, GPU1 t=58C fan=36%, GPU2 t=55C fan=36%, GPU3 t=59C fan=36%, GPU4 t=59C fan=41%, GPU5 t=58C fan=36%
02:41:00:149   1164   ETH: checking pool connection...
02:41:00:149   1164   sent: {"worker": "", "jsonrpc": "2.0", "params": [], "id": 3, "method": "eth_getWork"}

02:41:00:243   1164   buf: {"jsonrpc":"2.0","id":0,"result":["0xaeef20c127f6068a2e4c19681e2ee97ddd2aeed92ecf84fe7ee95f30363cafb9","0xa74dd84414948aba4bfd6580908dbf9c32a494aa336609746d19a35bb4cccb24","0x000000006df37f675ef6eadf5ab9a2072d44268d97df837e6748956e5c6c2116"]}

02:41:01:727   844   srv_thr cnt: 1, IP: 192.168.1.5
02:41:01:727   844   recv: 51
02:41:01:727   844   srv pck: 50
02:41:01:727   844   srv bs: 0
02:41:01:727   844   sent: 335
02:41:05:790   1164   sent: {"id":6,"jsonrpc":"2.0","method":"eth_submitHashrate","params":["0xadd23c5", "0x0000000000000000000000000000000000000000000000000000000033ef23e2"]}

02:41:06:915   fa8   srv_thr cnt: 1, IP: 192.168.1.5
02:41:06:915   fa8   recv: 51
02:41:06:915   fa8   srv pck: 50
02:41:06:915   fa8   srv bs: 0
02:41:06:915   fa8   sent: 335
02:41:10:166   1164   ETH: checking pool connection...



I can see the only dev fee getting connected in the span of 5 hourse

[qnarkill]

Does anybody know or have idea what would work for when -tstop is reached and i would want to reboot entire miner?

I have the -r 1 to reboot and it works ok if a gpu fails but in this case when the gpu is just switched off the claymore will just stop mining having me to restart miner manually to get it going again.

[QuintLeo]

Maybe ignorant question, but how are the ASICs going to work? I thought the whole point of DAGs was to prevent ASICs. How do the ASICs fit the DAG file on their chips affordably?

They don't ... they have DDR3 memory attached to the ASICs / FPGAs.  If you look on the Bitmain site, you can see that the device is a) twice the size of their other miners and b) is about the hash equivalent of 4x 580's.  If you consider the 800 watts of draw, it uses more Watts/MH than a rig with 4x 580s.  About the only attractive thing about it is the price ... $800.

180 Mhash/sec is at least 6 RX 470/480/570/580 even with BIOS straps and all other optimizations. (widely reported in the 28-30 Mhash range for best optimized cards, sometimes a bit less).
It's also a HAIR less than 6 x GTX 1070 (31-32 Mhash common numbers, rarely under 31).

Power usage is pretty much a tossup with a well-optimized 6 card rig - bit higher than the Nvidia option, right around the same vs the AMD option.

The size IS interesting, and has led to some speculation that it's somehow a GPU rig - but the PRICE makes it unlikely to be GPU based.

[leonix007]

Hi,

I apologize, I am newbie here.  I read and follow all the directions.
I am experience problems with 2 of my PCs, using Claymore Miner 11.6
I have a Nvidia Card.

First PC:  Windows 7 pro 64-bit
I got error message that "DCR: 0 pool specificed.
No AMD or Nvidia card found ..

Check if your GPU's are properly installed and has a correct driver, it should be detected by your system before firing up miners.

2nd PC:  Windows 10 pro 64-bit
This app cannot run on this PC.

I am testing on my older PC, I know it is not efficient.  I want to get to know at least the setup first.

any suggestion would be appreciated.

Thanks

Ensure that your Windows defender is not hampering the .exe file, exempt this and turn off the defender

[Coroto]

Hello, i will throw this here, thanks in advance for your kindly answers.

Been mining for a while with 5x 1060 3GB on Win 10. Sometimes the driver crash, but i have been able to solve the issue by downclocking mem in one of the GPUs (i always check logs and find the problematic GPU). Im currently on 11.6 and the miner restarted. Since most of you are far more experienced than me, i will appreciate a possible troubleshooting.

Code:

 20:51:59:545	1730	ETH: 04/05/18-20:51:59 - New job from eth-us.dwarfpool.com:8008
20:51:59:545	1730	target: 0x0000000225c17d04 (diff: 2000MH), epoch 179(2.40GB)
20:51:59:545	1730	ETH - Total Speed: 124.580 Mh/s, Total Shares: 2006, Rejected: 0, Time: 08:52
20:51:59:545	1730	ETH: GPU0 25.328 Mh/s, GPU1 25.250 Mh/s, GPU2 24.408 Mh/s, GPU3 24.852 Mh/s, GPU4 24.742 Mh/s
20:51:59:561	19e8	GPU 4, GpuMiner cu_k1 failed 77, an illegal memory access was encountered
20:51:59:561	19e8	GPU 4, GpuMiner kx failed 1
20:51:59:561	19e8	Set global fail flag, failed GPU4
20:51:59:561	19e8	GPU 4 failed
20:51:59:577	1740	GPU 4, GpuMiner cu_k1 failed 77, an illegal memory access was encountered
20:51:59:577	1740	GPU 4, GpuMiner kx failed 1
20:51:59:577	1840	GPU 0, GpuMiner cu_k1 failed 77, an illegal memory access was encountered
20:51:59:577	1740	Set global fail flag, failed GPU4
20:51:59:577	1840	GPU 0, GpuMiner kx failed 1
20:51:59:577	1740	GPU 4 failed
20:51:59:577	1840	Set global fail flag, failed GPU0
20:51:59:577	185c	GPU 0, GpuMiner cu_k1 failed 77, an illegal memory access was encountered
20:51:59:577	1840	GPU 0 failed
20:51:59:577	185c	GPU 0, GpuMiner kx failed 1
20:51:59:577	185c	Set global fail flag, failed GPU0
20:51:59:577	185c	GPU 0 failed
20:51:59:608	1834	GPU 1, GpuMiner cu_k1 failed 77, an illegal memory access was encountered
20:51:59:609	1834	GPU 1, GpuMiner kx failed 1
20:51:59:610	1834	Set global fail flag, failed GPU1
20:51:59:611	1838	GPU 1, GpuMiner cu_k1 failed 77, an illegal memory access was encountered
20:51:59:612	1834	GPU 1 failed
20:51:59:613	1838	GPU 1, GpuMiner kx failed 1
20:51:59:614	1838	Set global fail flag, failed GPU1
20:51:59:614	1838	GPU 1 failed
20:51:59:646	8d8	GPU 2, GpuMiner cu_k1 failed 77, an illegal memory access was encountered
20:51:59:646	8d8	GPU 2, GpuMiner kx failed 1
20:51:59:646	8d8	Set global fail flag, failed GPU2
20:51:59:646	1830	GPU 2, GpuMiner cu_k1 failed 77, an illegal memory access was encountered
20:51:59:646	8d8	GPU 2 failed
20:51:59:646	1830	GPU 2, GpuMiner kx failed 1
20:51:59:646	1830	Set global fail flag, failed GPU2
20:51:59:646	1830	GPU 2 failed
20:51:59:661	19dc	GPU 3, GpuMiner cu_k1 failed 77, an illegal memory access was encountered
20:51:59:661	19dc	GPU 3, GpuMiner kx failed 1
20:51:59:661	19dc	Set global fail flag, failed GPU3
20:51:59:661	19e0	GPU 3, GpuMiner cu_k1 failed 77, an illegal memory access was encountered
20:51:59:661	19dc	GPU 3 failed
20:51:59:661	19e0	GPU 3, GpuMiner kx failed 1
20:51:59:661	19e0	Set global fail flag, failed GPU3
20:51:59:661	19e0	GPU 3 failed
20:52:04:321	12c0	srv_thr cnt: 1, IP: 192.168.137.3
20:52:04:321	12c0	recv: 51
20:52:04:321	12c0	srv pck: 50
20:52:04:321	12c0	srv bs: 0
20:52:04:321	12c0	sent: 187
20:52:07:557	1730	buf: {"result":["0xb6a6c7f1b78cb48b5d1660ec5a167361bd257d5c57f4641c744dd5dd59a1deed","0xa74dd84414948aba4bfd6580908dbf9c32a494aa336609746d19a35bb4cccb24","0x0000000225c17d04dad2965cc5a02a23e254c0c3f75d9178046aeb27ce1ca574"],"jsonrpc":"2.0","id":0}


20:52:07:557	1730	ETH: 04/05/18-20:52:07 - New job from eth-us.dwarfpool.com:8008
20:52:07:557	1730	target: 0x0000000225c17d04 (diff: 2000MH), epoch 179(2.40GB)
20:52:07:557	1730	ETH - Total Speed: 0.000 Mh/s, Total Shares: 2006, Rejected: 0, Time: 08:53
20:52:07:557	1730	ETH: GPU0 0.000 Mh/s, GPU1 0.000 Mh/s, GPU2 0.000 Mh/s, GPU3 0.000 Mh/s, GPU4 0.000 Mh/s
20:52:08:743	1730	ETH: checking pool connection...
20:52:08:743	1730	sent: {"worker": "", "jsonrpc": "2.0", "params": [], "id": 3, "method": "eth_getWork"}

20:52:08:922	1730	buf: {"result":["0xb6a6c7f1b78cb48b5d1660ec5a167361bd257d5c57f4641c744dd5dd59a1deed","0xa74dd84414948aba4bfd6580908dbf9c32a494aa336609746d19a35bb4cccb24","0x0000000225c17d04dad2965cc5a02a23e254c0c3f75d9178046aeb27ce1ca574"],"jsonrpc":"2.0","id":3}


20:52:09:326	1d74	srv_thr cnt: 1, IP: 192.168.137.3
20:52:09:327	1d74	recv: 51
20:52:09:327	1d74	srv pck: 50
20:52:09:328	1d74	srv bs: 0
20:52:09:328	1d74	sent: 187
20:52:12:179	19b0	GPU0 t=49C fan=49%, GPU1 t=52C fan=56%, GPU2 t=50C fan=50%, GPU3 t=51C fan=50%, GPU4 t=53C fan=59%
20:52:14:313	14b4	srv_thr cnt: 1, IP: 192.168.137.3
20:52:14:313	14b4	recv: 51
20:52:14:313	14b4	srv pck: 50
20:52:14:328	14b4	srv bs: 0
20:52:14:329	14b4	sent: 187
20:52:14:582	c98	em hbt: 16, fm hbt: 94, 
20:52:14:582	c98	watchdog - thread 0 (gpu0), hb time 15031
20:52:14:582	c98	watchdog - thread 1 (gpu0), hb time 15031
20:52:14:582	c98	watchdog - thread 2 (gpu1), hb time 15031
20:52:14:582	c98	watchdog - thread 3 (gpu1), hb time 15031
20:52:14:582	c98	watchdog - thread 4 (gpu2), hb time 15031
20:52:14:582	c98	watchdog - thread 5 (gpu2), hb time 15031
20:52:14:582	c98	watchdog - thread 6 (gpu3), hb time 15031
20:52:14:582	c98	watchdog - thread 7 (gpu3), hb time 15031
20:52:14:582	c98	watchdog - thread 8 (gpu4), hb time 15016
20:52:14:582	c98	watchdog - thread 9 (gpu4), hb time 15234
20:52:14:582	c98	WATCHDOG: GPU error, you need to restart miner :( 
20:52:15:798	c98	Restarting OK, exit... 

As you can see, it was about after 9 hours of mining. The miner restarted and its mining just fine. Again, appreciate some troubleshooting. Kind regards...

[WhackOBill]

Maybe ignorant question, but how are the ASICs going to work? I thought the whole point of DAGs was to prevent ASICs. How do the ASICs fit the DAG file on their chips affordably?

They don't ... they have DDR3 memory attached to the ASICs / FPGAs.  If you look on the Bitmain site, you can see that the device is a) twice the size of their other miners and b) is about the hash equivalent of 4x 580's.  If you consider the 800 watts of draw, it uses more Watts/MH than a rig with 4x 580s.  About the only attractive thing about it is the price ... $800.

180 Mhash/sec is at least 6 RX 470/480/570/580 even with BIOS straps and all other optimizations. (widely reported in the 28-30 Mhash range for best optimized cards, sometimes a bit less).
It's also a HAIR less than 6 x GTX 1070 (31-32 Mhash common numbers, rarely under 31).

Power usage is pretty much a tossup with a well-optimized 6 card rig - bit higher than the Nvidia option, right around the same vs the AMD option.

The size IS interesting, and has led to some speculation that it's somehow a GPU rig - but the PRICE makes it unlikely to be GPU based.

You're right of course.  I'm not sure why my brain settled on 4x when 180/30 is clearly 6x.  The only thing close to 4x would have been Vega64's.

[Alex55466452]

Hello,

How can I set fixed fan speed on AMD cards with claymore? -tt 40 -fanmin -70 -fanmax 90 doesn't work? What am I doing wrong?

[ivanpop]

Read the readme. -tt -40

How big should the pagefile be for 13 GPU's?

[Raja_MBZ]

Hello,

How can I set fixed fan speed on AMD cards with claymore? -tt 40 -fanmin -70 -fanmax 90 doesn't work? What am I doing wrong?

You're trying to achieve a temperature that's impossible during mining, so your fan with -tt 40 will probably always work with full speed. Increase the temperature to somewhat like 80 and see then how it goes.

[tg88]

Hello,

How can I set fixed fan speed on AMD cards with claymore? -tt 40 -fanmin -70 -fanmax 90 doesn't work? What am I doing wrong?

Do not forget to also set the parameter -tstop.

[Viaggiatore]

11.6 is no go for me, I tested it today and after 4 hours crashed a rig with four AMD GPUs, on another AMD rig 11.5 is up and running since days. Of course same settings, same OC, etc etc

[Call_Me_Bambi]

Maybe ignorant question, but how are the ASICs going to work? I thought the whole point of DAGs was to prevent ASICs. How do the ASICs fit the DAG file on their chips affordably?

Its not actually an ASIC, its FPGA board

https://bitcointalk.org/index.php?topic=2182826.0

Ethereum ASICs are about to be released onto the market, I hope that there's a fix to the algo to let GPU miners still continue mining.

We are pleased to announce the Antminer E3, world's most powerful and efficient EtHash ASIC miner. Ordering limit of one miner per user and not available in China. Limited stock, order here now.
https://twitter.com/BITMAINtech

[BSAlex]

Maybe ignorant question, but how are the ASICs going to work? I thought the whole point of DAGs was to prevent ASICs. How do the ASICs fit the DAG file on their chips affordably?

Its not actually an ASIC, its FPGA board

https://bitcointalk.org/index.php?topic=2182826.0

Ethereum ASICs are about to be released onto the market, I hope that there's a fix to the algo to let GPU miners still continue mining.

We are pleased to announce the Antminer E3, world's most powerful and efficient EtHash ASIC miner. Ordering limit of one miner per user and not available in China. Limited stock, order here now.
https://twitter.com/BITMAINtech

As for now Ethash ASIC miner have no advantages to make GPU mining impossible. Hashes per watt are pretty the same. Hashrate is comparable to GPU farm. So today Ethereum authority decided NOT to emergency fork.

[Premiermine]

is any XVG pool online? 
when we can continue to mine in dual XVG?

After many hours it seems that our pool has returned to synchronize entire blockchain, mining works again, we will see what happens now with the fork.