No ethminer does not run inside of Awesome Miner. I just use TightVNC for eth mining.

Your very welcome. 
As to your remote question:  Awesome Miner.  Just do it.

Yeah, man, I probably should have included this handy link:

http://www.gobitgo.com/articles/1001/How-To-Correctly-Use-and-Install-PCI-E-Riser-Cables/

It will work just hang in there.

Depends on the GPU.  My XFX's can't be undervolted past 1.125 or they lock up.  The Sapphires and Gigabytes can.

This is the brand I chose as well.  I have 4 of the Extreme 3 boards and 2 of the Extreme 4 boards.  One of the Extreme 4 boards required jumpers to get it to recognize the 4th GPU.  Don't ask me why, I have no idea.  All I know is that it worked.  Why the other MB didn't need I have no idea.





Also, the order that you put the cards in matters.

For each card I recommend a full shut down and reboot before inserting the next card.

The PCI slot second from the left is GPU 0.  Do it first.
Next is the PCI slot immediately to it's left.
Then do the far right one.
Finally the one to it's immediate left.

I never could get the 5th slot to work for me, but frankly I just gave up.

I have used them and they sent me a good 280x.  No problems.

I recommend no less than 1200 watts gold rated 80 power supply.  My 7970's x 4 average 950watts at the wall for ETH. 
1200x.8 = 960.

Any links to a windows binary for this?  Just got a new i7 4790K and I wanna burn it in real good.

Optimal speed for my 7970's are achieved with AMD drivers 14.7rc3, not 15.7.1.  I have done direct comparisons with X11, quark, lyra2REv2, as well as neoscrypt using the latest NicehashMiner sgminers from the bin folder.  Of course, YMMV, but that is how it works for me.

For OpenCl, ethminer will run all GPU's it finds unless you limit the number with the "-t n" command where n is the number of GPU's you want to run.  You CANNOT however select which GPU's.  In order to troubleshoot a bad GPU I had to physically remove each PCI extension cable...bummer.  Wish it had the "device command" like sgminer.

You do not have to run a terminal of ethminer for every card.  You only need to run geth on the machine to serve as a node for your wallet. 

I have not tried it, but I do believe you can run separate instances of OpenCL and Nvidia as long as they have distinct DAG files, obviously in different terminals.

Thanks!

As far as I know, I am not using a proxy. Like the batch file states this rig is dialing straight into suprnova. What I am looking for is a command similar to when sgminer uses the command device = 0, 2, 3.

Let's say I need to troubleshoot a GPU on Win7-64 with ethminer.

I want to only start GPU 0, 2, and 3.  What is the command line config in a batch file to do that?

I know this isolates one card, GPU3, but I cannot figure out how to add 0, and 2:

ethminer -G --opencl-device 3 -F http://eth-us.suprnova.cc:3000/USER.1/24 -G --cl-local-work 256 --cl-global-work 8192



Thanks.

Me, too.  Exact same problem.

Patrike,

Do you have plans for adding ETH and Ethminer as options to Awesome Miner?

Now, about that promise to release windows binaries for Wolf's solomining fork...

Yeah, that makes sense.  Lot's of ways to represent success. 

Here's what I got with your new Windows 64 miner, all GPU voltages at 1.2, I used Sapphire HD 7970s (Hynix), and your recommended configuration:


I rebooted the rig between each test and deleted the existing .bin file.  I didn't use any type of driver cleaner utility.
I achieved the following after 5 minutes of mining from various AMD drivers when placed in your miner's folder:
------------------------------------------------------------------------------------------
AMD 15.7.1 (stock installation on rig):

[08:20:20] OCL0                | 5s:  0.0 avg:226.3 u:316.5 KH/s | A:24 R:0 HW:0 WU:18.1/m
[08:20:20] OCL1                | 5s:  0.0 avg:230.4 u:184.6 KH/s | A:14 R:0 HW:0 WU:10.6/m
[08:20:20] OCL2                | 5s:  0.0 avg:226.7 u:224.2 KH/s | A:17 R:0 HW:0 WU:12.8/m
[08:20:20] OCL3                | 5s:  0.0 avg:226.9 u:158.3 KH/s | A:12 R:0 HW:0 WU:9.1/m

------------------------------------------------------------------------------------------
AMD 14.12:

[08:29:23] OCL0                | 5s:  0.0 avg:239.2 u:228.7 KH/s | A:18 R:0 HW:0 WU:13.1/m
[08:29:23] OCL1                | 5s:  0.0 avg:239.4 u:282.5 KH/s | A:21 R:0 HW:0 WU:16.2/m
[08:29:23] OCL2                | 5s:  0.0 avg:239.2 u:228.7 KH/s | A:17 R:0 HW:0 WU:13.1/m
[08:29:23] OCL3                | 5s:  0.0 avg:239.6 u:336.3 KH/s | A:25 R:0 HW:0 WU:19.2/m

--------------------------------------------------------------------------------------------
AMD 14.9:

[08:13:28] OCL0                | 5s:  0.0 avg:379.2 u:459.8 KH/s | A:37 R:0 HW:0 WU:26.3/m
[08:13:28] OCL1                | 5s:  0.0 avg:378.2 u:410.1 KH/s | A:33 R:0 HW:0 WU:23.5/m
[08:13:28] OCL2                | 5s:  0.0 avg:378.6 u:360.4 KH/s | A:29 R:0 HW:0 WU:20.6/m
[08:13:28] OCL3                | 5s:  0.0 avg:378.4 u:298.2 KH/s | A:24 R:0 HW:0 WU:17.1/m

-------------------------------------------------------------------------------------------
AMD 14.7rc3:

[09:11:02] OCL0                | 5s:  0.0 avg:370.1 u:409.0 KH/s | A:31 R:0 HW:0 WU:23.4/m
[09:11:02] OCL1                | 5s:  0.0 avg:370.7 u:277.1 KH/s | A:21 R:0 HW:0 WU:15.9/m
[09:11:02] OCL2                | 5s:  0.0 avg:370.1 u:303.5 KH/s | A:23 R:0 HW:0 WU:17.4/m
[09:11:02] OCL3                | 5s:  0.0 avg:371.1 u:422.2 KH/s | A:32 R:0 HW:0 WU:24.2/m

--------------------------------------------------------------------------------------------
AMD 14.6:

[08:51:58] OCL0                | 5s:  0.0 avg:368.9 u:290.3 KH/s | A:22 R:0 HW:0 WU:16.6/m
[08:51:58] OCL1                | 5s:  0.0 avg:369.0 u:395.9 KH/s | A:30 R:0 HW:0 WU:22.7/m
[08:51:58] OCL2                | 5s:  0.0 avg:368.9 u:382.7 KH/s | A:29 R:0 HW:0 WU:21.9/m
[08:51:58] OCL3                | 5s:  0.0 avg:368.3 u:435.5 KH/s | A:33 R:0 HW:0 WU:24.9/m

--------------------------------------------------------------------------------------------
AMD 14.4:

[08:42:44] OCL0                | 5s:  0.0 avg:351.1 u:255.0 KH/s | A:19 R:0 HW:0 WU:14.6/m
[08:42:44] OCL1                | 5s:  0.0 avg:351.3 u:241.6 KH/s | A:18 R:0 HW:0 WU:13.8/m
[08:42:44] OCL2                | 5s:  0.0 avg:351.1 u:308.7 KH/s | A:23 R:0 HW:0 WU:17.7/m
[08:42:44] OCL3                | 5s:  0.0 avg:350.9 u:295.3 KH/s | A:22 R:0 HW:0 WU:16.9/m

--------------------------------------------------------------------------------------------

Okay, so that was for a rig of 4 HD 7970s, all Hynix memory.  Next I tested the 14.9 drivers on
4 Gigabyte Windforce R9 280x GPUs, all Elpida.  They wouldn't start with I 16, so I bumped them
down to I 15.

AMD 14.9 at I=15:

[09:36:18] OCL0                | 5s:  0.0 avg:374.0 u:284.6 KH/s | A:22 R:0 HW:0 WU:16.3/m
[09:36:18] OCL1                | 5s:361.6 avg:374.9 u:271.7 KH/s | A:21 R:0 HW:0 WU:15.5/m
[09:36:18] OCL2                | 5s:361.7 avg:374.0 u:323.5 KH/s | A:25 R:0 HW:0 WU:18.5/m
[09:36:18] OCL3                | 5s:361.4 avg:373.9 u:258.8 KH/s | A:20 R:0 HW:0 WU:14.8/m

That looks like comparable output for Hynix memory but at lower intensity.


==============================================================================

Now I will test Wolf0's neoscrypt.cl and .bin from the most recent Nicehash miner bin folder with sgminer-5-0-1, xI=2. gpu-threads=2, 1000/1500:


280x Elpida, with Wolf0's neoscrypt kernel with AMD 14.7rc3 drivers I get:

[09:53:00] GPU0                | (5s):403.8K (avg):424.4Kh/s | A:2496 R:0 HW:0 WU:403.230/m
[09:53:00] GPU1                | (5s):406.7K (avg):426.6Kh/s | A:2432 R:0 HW:0 WU:399.363/m
[09:53:00] GPU2                | (5s):406.3K (avg):425.7Kh/s | A:1728 R:0 HW:0 WU:253.722/m
[09:53:00] GPU3                | (5s):405.3K (avg):425.6Kh/s | A:2048 R:0 HW:0 WU:331.606/m


And going back to the HD7970 cards with 14.7rc3 drivers I get:

[09:57:30] GPU0                | (5s):407.0K (avg):417.7Kh/s | A:2368 R:0 HW:0 WU:373.366/m
[09:57:30] GPU1                | (5s):408.4K (avg):419.9Kh/s | A:2368 R:0 HW:0 WU:380.408/m
[09:57:30] GPU2                | (5s):410.5K (avg):419.4Kh/s | A:1856 R:0 HW:0 WU:291.159/m
[09:57:30] GPU3                | (5s):406.9K (avg):416.4Kh/s | A:2368 R:0 HW:0 WU:387.625/m


So, in summary, from the perspective of this dead-end user, it seems that for the moment Wolf0's kernel and .bin file from the most recent Nicehash miner bin folder and AMD 14.7rc3 drivers has the better hashrate.

Also, I cannot explain the apparent discrepancy in sgminer's accepted as compared to nsgminer's accepted.  I assume that there is a factor of 100 somewhere.

Thanks, I am running some tests on your latest Win 64 miner now with various AMD drivers on four R9 280x AMDs.  I'll report back later.

I just did that now I get another error:  The application was unable to start correctly (0xc000007b)