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

[malandante]

v4.1 updated: Added build for Linux x64 (tested on Ubuntu 12.04 + Catalyst 15.12).

I can confirm it works on ubuntu 15.04. Mining ETH on dwarfpool and DCR on suprnova. Will report later about stability. Thanks!

Well, it crashes after a few minutes I have 8 GB ram on each rig and the swap partition is not 16 GB as advised, it is 2, 4 or 12 GB depending on the rig. I don't think that's the reason. I have had a look at the logs and can't find any errors at the end.

[Q_R_V]

Well, it crashes after a few minutes I have 8 GB ram on each rig and the swap partition is not 16 GB as advised, it is 2, 4 or 12 GB depending on the rig. I don't think that's the reason. I have had a look at the logs and can't find any errors at the end.

How does it looks like? Gpu driver crash or terminal closing without a warning??

[malandante]

Well, it crashes after a few minutes I have 8 GB ram on each rig and the swap partition is not 16 GB as advised, it is 2, 4 or 12 GB depending on the rig. I don't think that's the reason. I have had a look at the logs and can't find any errors at the end.

How does it looks like? Gpu driver crash or terminal closing without a warning??

terminal closing without a warning, exactly

[vectisitch]

just started using this. i have 2x 7970's reporting 41.6 m/hash. so thats ok and a bit better than before. in the miner window the total shares  are at 40 with no rejects. how many shares should i be getting with 2x7970. the rate seems to be going up slowly

[malandante]

Well, it crashes after a few minutes I have 8 GB ram on each rig and the swap partition is not 16 GB as advised, it is 2, 4 or 12 GB depending on the rig. I don't think that's the reason. I have had a look at the logs and can't find any errors at the end.

How does it looks like? Gpu driver crash or terminal closing without a warning??

terminal closing without a warning, exactly

The rigs are running stable now for more than one hour. It seems it was a misconfiguration in wallet/rig field. I used wallet.rig format and the correct way is wallet/rig

[Q_R_V]

The rigs are running stable now for more than one hour. It seems it was a misconfiguration in wallet/rig field. I used wallet.rig format and the correct way is wallet/rig

Good to hear that. Have you noticed any hashrate change in relation to windows dual miner?

[Marvell1]

having a problem on one of my machines since the new Epoc

Code:

23:03:56:142	e9c	
23:03:56:157	e9c	ÉÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍ»
23:03:56:157	e9c	º   Claymore's Dual Ethereum + Decred AMD GPU Miner  v4.0 Beta   º
23:03:56:173	e9c	ÈÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍͼ
23:03:56:173	e9c	
23:03:56:392	e9c	ETH: 1 pool is specified
23:03:56:392	e9c	DCR: 1 pool is specified
23:03:56:798	e9c	
Cards available: 5 
23:03:56:798	e9c	GPU #0: name: Hawaii, 8192 MB available, 40 units 
23:03:56:798	e9c	GPU #1: name: Hawaii, 8192 MB available, 40 units 
23:03:56:814	e9c	GPU #2: name: Hawaii, 8192 MB available, 40 units 
23:03:56:814	e9c	GPU #3: name: Fiji, 4096 MB available, 64 units 
23:03:56:829	e9c	GPU #4: name: Hawaii, 8192 MB available, 40 units 
23:03:56:829	e9c	Total cards: 5 
23:03:56:829	e9c	Initializing...

23:03:56:829	e9c	GPU #0 recognized as Radeon 390
23:03:56:829	e9c	GPU #1 recognized as Radeon 390
23:03:56:829	e9c	GPU #2 recognized as Radeon 390
23:03:56:845	e9c	GPU #3 recognized as Fury X/Nano
23:03:56:845	e9c	GPU #4 recognized as Radeon 390
23:03:56:845	e9c	POOL version
23:03:56:845	e9c	b121
23:03:56:860	e9c	GPU #0: set -etha as 0 (ETH algo for fast cards)
23:03:56:860	e9c	GPU #1: set -etha as 0 (ETH algo for fast cards)
23:03:56:860	e9c	GPU #2: set -etha as 0 (ETH algo for fast cards)
23:03:56:860	e9c	GPU #3: set -etha as 0 (ETH algo for fast cards)
23:03:56:876	e9c	GPU #4: set -etha as 0 (ETH algo for fast cards)
23:03:57:829	33c	ETH: Stratum - connecting to 'coinotron.com' <178.217.186.125> port 3344
23:03:57:939	e9c	DUAL MINING MODE ENABLED: ETHEREUM+DECRED
23:03:57:939	131c	 DCR: Stratum - connecting to 'dcr.suprnova.cc' <178.33.228.14> port 2252
23:03:57:954	e9c	Decred HTTP requests time (-dcrt) is set to 10
23:03:57:970	e9c	miner-proxy stratum mode
23:03:57:970	e9c	"-allpools" option is set, default pools can be used for devfee, check "Readme" file for details.
23:03:57:985	e9c	Watchdog enabled
23:03:57:985	e9c	
23:03:57:985	33c	send: {"id": 1, "method": "mining.subscribe", "params": []}

23:03:58:001	33c	send: {"id": 2, "method": "mining.authorize", "params": ["Marvell9.55","x"]}

23:03:58:001	33c	ETH: Stratum - Connected (coinotron.com:3344)
23:03:58:079	131c	send: {"id": 1, "method": "mining.subscribe", "params": ["dcr 1.0"]}

23:03:58:079	131c	send: {"id": 5, "method": "mining.extranonce.subscribe", "params": []}

23:03:58:095	131c	send: {"id": 2, "method": "mining.authorize", "params": ["Marvell9.55","x"]}

23:03:58:095	131c	 DCR: Stratum - Connected (dcr.suprnova.cc:2252)
23:03:58:173	33c	got 107 bytes
23:03:58:173	33c	buf: {"error": null, "id": 1, "result": [["mining.notify", "1b2888e9ff6c4cf1ae113322ad37d930"], "08001443", 4]}

23:03:58:189	33c	parse packet: 99
23:03:58:189	33c	new buf size: 0
23:03:58:220	131c	got 591 bytes
23:03:58:220	131c	buf: {"error": null, "id": 1, "result": [["mining.notify", "ae6812eb4cd7735a302a8a9dd95cf71f"], "00000000f8000752f8000752", 12]}
{"params": [1], "id": null, "method": "mining.set_difficulty"}
{"params": ["8c", "931c82a0a9dbbe2d06f3dabd121b279fd581d5fbff2d4d8a0000088800000000", "ca3750d31f2611f45e94488a4bf6844ad842eca4c677edb25582dc43094aeaafa4c928a58668058ac63e946fb81e71f8a7256fea6e4df42a91929135fdb6dfe40100155dea317971050002004ba60000d6091d1adb11556d00000000395f0000ff150000d6c226570000000000000000", "", [], "01000000", "1a1d09d6", "5726c2d6", true], "id": null, "method": "mining.notify"}

23:03:58:220	131c	parse packet: 116
23:03:58:220	131c	remove first packet 449
23:03:58:220	131c	new buf size: 449
23:03:58:220	131c	parse packet: 58
23:03:58:235	131c	remove first packet 391
23:03:58:235	131c	new buf size: 391
23:03:58:235	131c	parse packet: 391
23:03:58:235	131c	new buf size: 0
23:03:58:329	33c	got 342 bytes
23:03:58:329	131c	got 82 bytes
23:03:58:329	33c	buf: { "id": null, "method": "mining.set_difficulty", "params": [55000]}
{"params": ["7178", "0xddf13e0d55b3a4f9951c662550853b13bd58bece9373fb7d533c4709fad16271","0x17a7217f2673ce6267021cc82e7b328a755f010d6741bde6c25d3c2b0373e989","0x00000001310A508148DF1ECB62908D334643D83B47C1251FE95C3C06679770B6", true], "id": null, "method": "mining.notify"}

23:03:58:329	131c	buf: {"error": null, "id": 5, "result": true}
{"error": null, "id": 2, "result": true}

23:03:58:345	33c	parse packet: 62
23:03:58:345	131c	parse packet: 36
23:03:58:360	33c	remove first packet 267
23:03:58:360	131c	remove first packet 36
23:03:58:360	33c	new buf size: 267
23:03:58:360	131c	new buf size: 36
23:03:58:360	33c	parse packet: 267
23:03:58:376	131c	parse packet: 36
23:03:58:376	33c	eth: job changed
23:03:58:376	131c	 DCR: Authorized
23:03:58:376	33c	new buf size: 0
23:03:58:376	131c	new buf size: 0
23:03:58:454	97c	Setting DAG epoch #48...
23:03:58:532	33c	got 101 bytes
23:03:58:532	33c	buf: {"error": null, "id": 2, "result": true}
{ "id": 9876, "method": "client.get_version", "params": []}

23:03:58:532	33c	parse packet: 36
23:03:58:532	33c	ETH: Authorized
23:03:58:532	33c	remove first packet 54
23:03:58:532	33c	new buf size: 54
23:03:58:532	33c	parse packet: 54
23:03:58:548	33c	send: {"error": null, "id": 9876, "result": "eth 1.0"}

23:03:58:548	33c	new buf size: 0
23:03:59:673	97c	Setting DAG epoch #48 for GPU #4
23:03:59:673	12dc	Setting DAG epoch #48 for GPU #3
23:03:59:673	1238	Setting DAG epoch #48 for GPU #2
23:03:59:673	c94	Setting DAG epoch #48 for GPU #0
23:03:59:673	1244	Setting DAG epoch #48 for GPU #1
23:03:59:673	97c	Create GPU buffer for GPU #4
23:03:59:673	12dc	Create GPU buffer for GPU #3
23:03:59:673	1238	Create GPU buffer for GPU #2
23:03:59:689	c94	Create GPU buffer for GPU #0
23:03:59:689	1244	Create GPU buffer for GPU #1
23:03:59:767	97c	GPU 4, OpenCL error -48 - cannot create DAG on GPU
23:03:59:767	1238	GPU 2, OpenCL error -48 - cannot create DAG on GPU
23:03:59:767	c94	GPU 0, OpenCL error -48 - cannot create DAG on GPU
23:03:59:829	12dc	GPU 3, OpenCL error -48 - cannot create DAG on GPU
23:03:59:845	1244	GPU 1, OpenCL error -48 - cannot create DAG on GPU
23:04:01:048	e9c	OC v6, Reset control for GPU 0, close miner right now if you want to use default control from Catalyst 
23:04:01:064	e9c	OC v6, Reset control for GPU 6, close miner right now if you want to use default control from Catalyst 
23:04:01:064	e9c	OC v6, Reset control for GPU 12, close miner right now if you want to use default control from Catalyst 
23:04:01:064	e9c	OC v6, Reset control for GPU 18, close miner right now if you want to use default control from Catalyst 
23:04:01:079	e9c	OC v6, Reset control for GPU 24, close miner right now if you want to use default control from Catalyst 

reinstalled the box and now it works I was on the correct version 15.12 idk what happend

[Marvell1]

having a problem on one of my machines since the new Epoc

Code:

23:03:56:142	e9c	
23:03:56:157	e9c	ÉÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍ»
23:03:56:157	e9c	º   Claymore's Dual Ethereum + Decred AMD GPU Miner  v4.0 Beta   º
23:03:56:173	e9c	ÈÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍͼ
23:03:56:173	e9c	
23:03:56:392	e9c	ETH: 1 pool is specified
23:03:56:392	e9c	DCR: 1 pool is specified
23:03:56:798	e9c	
Cards available: 5 
23:03:56:798	e9c	GPU #0: name: Hawaii, 8192 MB available, 40 units 
23:03:56:798	e9c	GPU #1: name: Hawaii, 8192 MB available, 40 units 
23:03:56:814	e9c	GPU #2: name: Hawaii, 8192 MB available, 40 units 
23:03:56:814	e9c	GPU #3: name: Fiji, 4096 MB available, 64 units 
23:03:56:829	e9c	GPU #4: name: Hawaii, 8192 MB available, 40 units 
23:03:56:829	e9c	Total cards: 5 
23:03:56:829	e9c	Initializing...

23:03:56:829	e9c	GPU #0 recognized as Radeon 390
23:03:56:829	e9c	GPU #1 recognized as Radeon 390
23:03:56:829	e9c	GPU #2 recognized as Radeon 390
23:03:56:845	e9c	GPU #3 recognized as Fury X/Nano
23:03:56:845	e9c	GPU #4 recognized as Radeon 390
23:03:56:845	e9c	POOL version
23:03:56:845	e9c	b121
23:03:56:860	e9c	GPU #0: set -etha as 0 (ETH algo for fast cards)
23:03:56:860	e9c	GPU #1: set -etha as 0 (ETH algo for fast cards)
23:03:56:860	e9c	GPU #2: set -etha as 0 (ETH algo for fast cards)
23:03:56:860	e9c	GPU #3: set -etha as 0 (ETH algo for fast cards)
23:03:56:876	e9c	GPU #4: set -etha as 0 (ETH algo for fast cards)
23:03:57:829	33c	ETH: Stratum - connecting to 'coinotron.com' <178.217.186.125> port 3344
23:03:57:939	e9c	DUAL MINING MODE ENABLED: ETHEREUM+DECRED
23:03:57:939	131c	 DCR: Stratum - connecting to 'dcr.suprnova.cc' <178.33.228.14> port 2252
23:03:57:954	e9c	Decred HTTP requests time (-dcrt) is set to 10
23:03:57:970	e9c	miner-proxy stratum mode
23:03:57:970	e9c	"-allpools" option is set, default pools can be used for devfee, check "Readme" file for details.
23:03:57:985	e9c	Watchdog enabled
23:03:57:985	e9c	
23:03:57:985	33c	send: {"id": 1, "method": "mining.subscribe", "params": []}

23:03:58:001	33c	send: {"id": 2, "method": "mining.authorize", "params": ["Marvell9.55","x"]}

23:03:58:001	33c	ETH: Stratum - Connected (coinotron.com:3344)
23:03:58:079	131c	send: {"id": 1, "method": "mining.subscribe", "params": ["dcr 1.0"]}

23:03:58:079	131c	send: {"id": 5, "method": "mining.extranonce.subscribe", "params": []}

23:03:58:095	131c	send: {"id": 2, "method": "mining.authorize", "params": ["Marvell9.55","x"]}

23:03:58:095	131c	 DCR: Stratum - Connected (dcr.suprnova.cc:2252)
23:03:58:173	33c	got 107 bytes
23:03:58:173	33c	buf: {"error": null, "id": 1, "result": [["mining.notify", "1b2888e9ff6c4cf1ae113322ad37d930"], "08001443", 4]}

23:03:58:189	33c	parse packet: 99
23:03:58:189	33c	new buf size: 0
23:03:58:220	131c	got 591 bytes
23:03:58:220	131c	buf: {"error": null, "id": 1, "result": [["mining.notify", "ae6812eb4cd7735a302a8a9dd95cf71f"], "00000000f8000752f8000752", 12]}
{"params": [1], "id": null, "method": "mining.set_difficulty"}
{"params": ["8c", "931c82a0a9dbbe2d06f3dabd121b279fd581d5fbff2d4d8a0000088800000000", "ca3750d31f2611f45e94488a4bf6844ad842eca4c677edb25582dc43094aeaafa4c928a58668058ac63e946fb81e71f8a7256fea6e4df42a91929135fdb6dfe40100155dea317971050002004ba60000d6091d1adb11556d00000000395f0000ff150000d6c226570000000000000000", "", [], "01000000", "1a1d09d6", "5726c2d6", true], "id": null, "method": "mining.notify"}

23:03:58:220	131c	parse packet: 116
23:03:58:220	131c	remove first packet 449
23:03:58:220	131c	new buf size: 449
23:03:58:220	131c	parse packet: 58
23:03:58:235	131c	remove first packet 391
23:03:58:235	131c	new buf size: 391
23:03:58:235	131c	parse packet: 391
23:03:58:235	131c	new buf size: 0
23:03:58:329	33c	got 342 bytes
23:03:58:329	131c	got 82 bytes
23:03:58:329	33c	buf: { "id": null, "method": "mining.set_difficulty", "params": [55000]}
{"params": ["7178", "0xddf13e0d55b3a4f9951c662550853b13bd58bece9373fb7d533c4709fad16271","0x17a7217f2673ce6267021cc82e7b328a755f010d6741bde6c25d3c2b0373e989","0x00000001310A508148DF1ECB62908D334643D83B47C1251FE95C3C06679770B6", true], "id": null, "method": "mining.notify"}

23:03:58:329	131c	buf: {"error": null, "id": 5, "result": true}
{"error": null, "id": 2, "result": true}

23:03:58:345	33c	parse packet: 62
23:03:58:345	131c	parse packet: 36
23:03:58:360	33c	remove first packet 267
23:03:58:360	131c	remove first packet 36
23:03:58:360	33c	new buf size: 267
23:03:58:360	131c	new buf size: 36
23:03:58:360	33c	parse packet: 267
23:03:58:376	131c	parse packet: 36
23:03:58:376	33c	eth: job changed
23:03:58:376	131c	 DCR: Authorized
23:03:58:376	33c	new buf size: 0
23:03:58:376	131c	new buf size: 0
23:03:58:454	97c	Setting DAG epoch #48...
23:03:58:532	33c	got 101 bytes
23:03:58:532	33c	buf: {"error": null, "id": 2, "result": true}
{ "id": 9876, "method": "client.get_version", "params": []}

23:03:58:532	33c	parse packet: 36
23:03:58:532	33c	ETH: Authorized
23:03:58:532	33c	remove first packet 54
23:03:58:532	33c	new buf size: 54
23:03:58:532	33c	parse packet: 54
23:03:58:548	33c	send: {"error": null, "id": 9876, "result": "eth 1.0"}

23:03:58:548	33c	new buf size: 0
23:03:59:673	97c	Setting DAG epoch #48 for GPU #4
23:03:59:673	12dc	Setting DAG epoch #48 for GPU #3
23:03:59:673	1238	Setting DAG epoch #48 for GPU #2
23:03:59:673	c94	Setting DAG epoch #48 for GPU #0
23:03:59:673	1244	Setting DAG epoch #48 for GPU #1
23:03:59:673	97c	Create GPU buffer for GPU #4
23:03:59:673	12dc	Create GPU buffer for GPU #3
23:03:59:673	1238	Create GPU buffer for GPU #2
23:03:59:689	c94	Create GPU buffer for GPU #0
23:03:59:689	1244	Create GPU buffer for GPU #1
23:03:59:767	97c	GPU 4, OpenCL error -48 - cannot create DAG on GPU
23:03:59:767	1238	GPU 2, OpenCL error -48 - cannot create DAG on GPU
23:03:59:767	c94	GPU 0, OpenCL error -48 - cannot create DAG on GPU
23:03:59:829	12dc	GPU 3, OpenCL error -48 - cannot create DAG on GPU
23:03:59:845	1244	GPU 1, OpenCL error -48 - cannot create DAG on GPU
23:04:01:048	e9c	OC v6, Reset control for GPU 0, close miner right now if you want to use default control from Catalyst 
23:04:01:064	e9c	OC v6, Reset control for GPU 6, close miner right now if you want to use default control from Catalyst 
23:04:01:064	e9c	OC v6, Reset control for GPU 12, close miner right now if you want to use default control from Catalyst 
23:04:01:064	e9c	OC v6, Reset control for GPU 18, close miner right now if you want to use default control from Catalyst 
23:04:01:079	e9c	OC v6, Reset control for GPU 24, close miner right now if you want to use default control from Catalyst 

Probably you use "Data.bin" file from v3.x version.

dont think it was the Data.bin, I always overwrite the previous files with the new builds , anyhow its working now

[davembg]

v4.1 updated: Added build for Linux x64 (tested on Ubuntu 12.04 + Catalyst 15.12).

AWSOME - THX.
Is the source code available?
I try not to put anything on my hardware I that I DON'T BUILD.
Especially in the shady world of crypto

[crazyearner]

Is their any problems to use latest AMD driver out current version 16.15.2211  than using Catalyst 15.12 ? Is their any reported problems on this as its asking me to update to new driver?

[vectisitch]

why does the share rate take hours to rise when you first start?

[IncludeBeer]

So I finally added the last 2 GPUs to my mining rig.  Before, I had 4 cards hooked up and everything hashed as expected, but with some "mildly" frequent disconnects from pools (especially suprnova), according to the software.

Last night I added the last 2 390x's, and everything booted and all cards were recognized just fine.  However, once I start the miner, TeamViewer would almost immediately disconnect and I would have a very hard time reconnecting.  The miner reported eth hashrate as expected (~160 mh), but my pool (coinotron) reports only 2-5 mh, which is a fraction of what it should be.  I tried running Genoi's latest release, but the CPU usage jumped to 99% once the mining started, and after a couple minutes I saw TeamViewer disconnecting as well as display driver crashes, so quickly scrapped that strategy.

I'm not really sure what might be the issue, but it seems maybe the wireless adapter I have installed isn't doing what it needs to.  Any advice as to what might be the issue?  For completeness sake:

4gb RAM
Celeron CPU
2x 1k watt PSU
4x 390x
2x 280x
Windows 10

Thanks!

[citronick]

So I finally added the last 2 GPUs to my mining rig.  Before, I had 4 cards hooked up and everything hashed as expected, but with some "mildly" frequent disconnects from pools (especially suprnova), according to the software.

Last night I added the last 2 390x's, and everything booted and all cards were recognized just fine.  However, once I start the miner, TeamViewer would almost immediately disconnect and I would have a very hard time reconnecting.  The miner reported eth hashrate as expected (~160 mh), but my pool (coinotron) reports only 2-5 mh, which is a fraction of what it should be.  I tried running Genoi's latest release, but the CPU usage jumped to 99% once the mining started, and after a couple minutes I saw TeamViewer disconnecting as well as display driver crashes, so quickly scrapped that strategy.

I'm not really sure what might be the issue, but it seems maybe the wireless adapter I have installed isn't doing what it needs to.  Any advice as to what might be the issue?  For completeness sake:

4gb RAM
Celeron CPU
2x 1k watt PSU
4x 390x
2x 280x
Windows 10

Thanks!

I had a similar issue previously, until I installed a "headless HDMI or DVI adapter" - after that my TeamViewer or VNC connects as per normal as if the remote irg is attached to a PC monitor.

[dpcoinz]

@claymore : Is it possible to use your miner on miningrigrentals?  if so could you help with the options.  I've tried multiple qtminer combinations, but so far nothing works.  according to miningrigrentals, they have a qtminer example that shows :  qtminer -s us-west01.miningrigrentals.com:3333 -u username.rignumber -G

Love all the work you've done on this miner.  Thanks!!!

I read this: https://www.miningrigrentals.com/rigs/hashimotog
....
This algo is typically used to mine Ethereum. This section is for the GETWORK miner and related pools only. Typically this is ethminer. Attempting to use rigs from this section with stratum based pools will fail.
....

So it seems they don't support stratum, I cannot find page with your sample about qtminer.

They haven't updated their faq about the stratum side.  When you setup a Dagger-Hashimoto(S) rig, in the properties block of the rig they give an example of a qtminer command line.  That is the only place I have found an example for their stratum based dagger-hashimoto rigs.

dp

@claymore,  For mining rig rentals, the problem is that everything has to support qtminer from the miner all the way to the pool.  So when you setup the rig on miningrigrentals.com many of the pools fail.  But I got it all sorted out.  Thanks for all the hard on the miner. 

dp

[malandante]

The rigs are running stable now for more than one hour. It seems it was a misconfiguration in wallet/rig field. I used wallet.rig format and the correct way is wallet/rig

Good to hear that. Have you noticed any hashrate change in relation to windows dual miner?

I don't use windows. Compared to stock ethminer I still don't know, would need more stable time to check. And finally after several hours the miner has crashed on all my rigs and they have stopped mining

I think I will put up a script to check if the miner is working and if it is not, will relaunch it.

[Abcederian]

FUD

I appreciate the help earlier in the thread.

I am currently running ethOS on a Rampage II Gene motherboard with an Intel(R) Core(TM) i7 Quad Core CPU with 8gb RAM. My rig has an MSI R9280x and an xfx R9-380. It hasn't been broke so I really haven't needed to fix, but, I have a brand new 240gb SSD with Windows 10 64 bit. So I am planning to switch to Claymore's Dual Miner.

Is it really as simple as downloading v 4.1, unzipping it and adding my command line?

I am planning to add-
Chrome
MSI Afterburner
AMD Crimson 15.12 (might that already be there?)

I am currently using putty to view my rig from my desktop. How are you monitoring your rigs remotely? I apologize if that is answered the thread. TeamViewer is not in the budget. Anyone using this? https://bitcointalk.org/index.php?topic=1448855.0

What am I missing?

If this goes smooth I plan to switch over my other rig as well.

Thanks for answering my NOOB questions.
 

[IncludeBeer]

So I finally added the last 2 GPUs to my mining rig.  Before, I had 4 cards hooked up and everything hashed as expected, but with some "mildly" frequent disconnects from pools (especially suprnova), according to the software.

Last night I added the last 2 390x's, and everything booted and all cards were recognized just fine.  However, once I start the miner, TeamViewer would almost immediately disconnect and I would have a very hard time reconnecting.  The miner reported eth hashrate as expected (~160 mh), but my pool (coinotron) reports only 2-5 mh, which is a fraction of what it should be.  I tried running Genoi's latest release, but the CPU usage jumped to 99% once the mining started, and after a couple minutes I saw TeamViewer disconnecting as well as display driver crashes, so quickly scrapped that strategy.

I'm not really sure what might be the issue, but it seems maybe the wireless adapter I have installed isn't doing what it needs to.  Any advice as to what might be the issue?  For completeness sake:

4gb RAM
Celeron CPU
2x 1k watt PSU
4x 390x
2x 280x
Windows 10

Thanks!

I had a similar issue previously, until I installed a "headless HDMI or DVI adapter" - after that my TeamViewer or VNC connects as per normal as if the remote irg is attached to a PC monitor.

Well, whenever I first start the rig up, I have a monitor plugged into the first GPU, and I still see the same behavior.  TeamViewer only disconnects or somehow seems less stable when I fire up a miner....

[parmatiya]

FUD

I appreciate the help earlier in the thread.

I am currently running ethOS on a Rampage II Gene motherboard with an Intel(R) Core(TM) i7 Quad Core CPU with 8gb RAM. My rig has an MSI R9280x and an xfx R9-380. It hasn't been broke so I really haven't needed to fix, but, I have a brand new 240gb SSD with Windows 10 64 bit. So I am planning to switch to Claymore's Dual Miner.

Is it really as simple as downloading v 4.1, unzipping it and adding my command line?

I am planning to add-
Chrome
MSI Afterburner
AMD Crimson 15.12 (might that already be there?)

I am currently using putty to view my rig from my desktop. How are you monitoring your rigs remotely? I apologize if that is answered the thread. TeamViewer is not in the budget.

What am I missing?

If this goes smooth I plan to switch over my other rig as well.

Thanks for answering my NOOB questions.
 

It is quite simple, you need to install the 15.12 and do not overclock your GPU. Then unzip the 4.1.  Set the pool information.

[dannygroove]

FUD

I appreciate the help earlier in the thread.

I am currently running ethOS on a Rampage II Gene motherboard with an Intel(R) Core(TM) i7 Quad Core CPU with 8gb RAM. My rig has an MSI R9280x and an xfx R9-380. It hasn't been broke so I really haven't needed to fix, but, I have a brand new 240gb SSD with Windows 10 64 bit. So I am planning to switch to Claymore's Dual Miner.

Is it really as simple as downloading v 4.1, unzipping it and adding my command line?

I am planning to add-
Chrome
MSI Afterburner
AMD Crimson 15.12 (might that already be there?)

I am currently using putty to view my rig from my desktop. How are you monitoring your rigs remotely? I apologize if that is answered the thread. TeamViewer is not in the budget.

What am I missing?

If this goes smooth I plan to switch over my other rig as well.

Thanks for answering my NOOB questions.
 

Can you report hashrate for the XFX R9 380 once you get it running?

[Q_R_V]

I don't use windows. Compared to stock ethminer I still don't know, would need more stable time to check. And finally after several hours the miner has crashed on all my rigs and they have stopped mining

I think I will put up a script to check if the miner is working and if it is not, will relaunch it.

I will try to test it under ubuntu and GenEthOS, will report back if i find something usefull.
You didn't mentioned drivers version your ubuntu is running, 15.12?