Quote from: jmordica on May 30, 2014, 04:35:02 PM

It seems like you have the right config but that one of your Fury's isn't getting the right amount of power. Can you try a few different power combinations? If this doesn't work, just try the non working device alone. If this doesn't work, the unit may need to be RMA'd. This is handled through gawminers.com and/or orders@gawminers.com.

Ok. I'll go ahead and try them individually and I'll swap the power bricks between the units to see if that makes a difference. Both bricks feel about the same warmth so it seems that both a pulling about the same power. I'll report back in a few minutes.

Thanks for the help. Grin

EDIT: Ok after playing around with them here is what I've found.

1. Both Fury's can hash just fine by themselves. Well other than the issues with cgminer you guys are working on.

2. The Fury's were originally on COM7 and COM8. I decided to try and run 2 instances of cgminer both pointed at a different COM port. This didn't work; when I'd fire up the COM8 cgminer instance it would kill the COM7 instance (Shares would stop being submitted).

3. After swapping which usb ports they were plugged into I ended up with them being on COM7 and COM9. This time I was able to run 2 instances of cgminer, and other than some extreme fluctuation in hashrate; it seems that it's working now. Pool shows ~~~2.6MH which is where it should be.~~ EDIT: Seems like it's swinging over 500KH/s on both the pool and the local hashrate reported. Shocked

So, it looks like there is some kind of software issue when trying to run both off of one cgminer instance. This was on Windows 7; is the same issue going to occur on the ZenMiner? Where it looks like it's hashing correctly, but it's silently only sending one miners work?