Quote from: Mudbankkeith on January 11, 2014, 05:33:01 PM

Quote from: captplanet on January 11, 2014, 05:26:57 PM

Quote from: captplanet on January 11, 2014, 03:50:11 PM

Quote from: Mudbankkeith on January 11, 2014, 09:00:56 AM

Quote from: captplanet on January 11, 2014, 07:12:43 AM

I'm using the new bfgminer that was posted here(Thank you forever, btw) and one of my miners is getting a bunch of HW errors. The problem is it's always a different one whenever I cycle the mining software. This happened with both cgminer and BFGMiner. Does anyone have any ideas on this problem?

Its probably the same stick with errors, the software allocates the table positions in sequence of power up, not port number. So each start up is different.

As an update, I went ahead and switched out all the miners to just random different ports, making sure each one is on a different port. Currently, I get no hardware errors on them, but one of them has only accepted 34 shares in 8.5 hours. I'm using eclipseMC and I'm not sure how to have the pool utilize my full potential as it's only displaying between 5-8 GH/s whenever I look at it's displayed hash rate.

New Update(Not that many of you care, but maybe someone's having a similar issue): I took out every stick, including block erupters, from my hub, and made sure to hit every port in the hub. It re-installed the silicon labs driver on some of them, so that leads me to believe the driver wasn't on all of them which is why I was getting so many issues.

Mixing devices in one session will continue to be difficult until the drivers are fully implemented.
Run one session for your erupters.
Then plug in your U1 sticks then start a second session for them.

nwoolls has done a great job with BFGminer but, until LukeJr builds then into the formal release, there may still be conflicts.

Currently everything is running smoothly after I did the whole unplug everything and plug them back in to make sure I hit every port