USB ASIC ERUPTER - Setup & Config. BCG Miner, cgminer & Hubs "Oh Pi"!

[runam0k]

New cgminer version, 3.2.2, hopefully fixes a lot of bugs with the direct USB behaviour on these devices.

Great.

Now just need to properly uninstall the USB to UART stuff...

[1715368069]

1715368069

[1715368069]

1715368069

[1715368069]

1715368069

[1715368069]

1715368069

[Remember remember the 5th of November]

You know, I've rarely had HW errors with my GPUs. How come these USB Eruptors that cost as much as a new gen GPU produce ANY HW errors at all?

[FiatKiller]

You know, I've rarely had HW errors with my GPUs. How come these USB Eruptors that cost as much as a new gen GPU produce ANY HW errors at all?

Considing it's the size of a thumb, you are being a bit picky.  :-D    GPUs mining BTC may have low error rates, but mining scrypt all out... anything less than 3-5% is acceptable, and normal. BTC is intensity 8-11(depending on GPU model) and scrypt is usually 13+

[os2sam]

You know, I've rarely had HW errors with my GPUs. How come these USB Eruptors that cost as much as a new gen GPU produce ANY HW errors at all?

Supposedly that is the nature of all ASIC's.

[whonesta]

6 - AMU devices thru a Raspberry Pi running MinePeon (6-11-2013 rev) and mining with CGMiner 3.2.1, I can confirm the DLink DUB-7H powered hub does work. I DID NOT use any of the icarus options nor timing when launching CGMiner.

I can confirm that the Plugable USB 3.0 High Powered hub DOES NOT work with the AMUs.

[MikeMike]

6 - AMU devices thru a Raspberry Pi running MinePeon (6-11-2013 rev) and mining with CGMiner 3.2.1, I can confirm the DLink DUB-7H powered hub does work. I DID NOT use any of the icarus options nor timing when launching CGMiner.

I can confirm that the Plugable USB 3.0 High Powered hub DOES NOT work with the AMUs.

Absolutely Beautiful!

[LogicalUnit]

6 - AMU devices thru a Raspberry Pi running MinePeon (6-11-2013 rev) and mining with CGMiner 3.2.1, I can confirm the DLink DUB-7H powered hub does work. I DID NOT use any of the icarus options nor timing when launching CGMiner.

Hey, buddy! We've got a similar setup! What's your guess about the ROI of the AMUs?

BTW, what sort of cooling are you using, if any?

[whonesta]

6 - AMU devices thru a Raspberry Pi running MinePeon (6-11-2013 rev) and mining with CGMiner 3.2.1, I can confirm the DLink DUB-7H powered hub does work. I DID NOT use any of the icarus options nor timing when launching CGMiner.

Hey, buddy! We've got a similar setup! What's your guess about the ROI of the AMUs?

BTW, what sort of cooling are you using, if any?

I was just talking about that, I am not sure ROI will be reached inside of 365 days sadly. There is however a growing market on the auction sites which could be profitable. I have a fan mounted on my rack which moves air across all the mining hardware, I had a usb fan but it was causing hardware errors on a couple of the AMUs, I suspect the fan is a power hog and the DLink did not have it to spare. I have been running for 6+ Hours with NO issues 

[LogicalUnit]

I was just talking about that, I am not sure ROI will be reached inside of 365 days sadly. There is however a growing market on the auction sites which could be profitable. I have a fan mounted on my rack which moves air across all the mining hardware, I had a usb fan but it was causing hardware errors on a couple of the AMUs, I suspect the fan is a power hog and the DLink did not have it to spare. I have been running for 6+ Hours with NO issues  

What's your HW error % rate? Divide HW by A to get it. Mine is 0.8%.

EDIT: You might need to calculate it individually because you have other hardware besides the AMUs.

[monkeymonkey]

I've got the same/similar setup(hub/pi/bfgminer).  when i plugged in 7 sticks i had 2 give problems.  one was puking errors and the other refused to hash.

i unplugged 1 stick and started a fan blowing across the 6 USB sticks.  the 1 stick which was previously giving >10% hw errors started hashing normally.
the 6 sticks even after not clearing errors are now averaging ~1% hw errs over 30 hours now.  the actual rate should be much lower once i restart and clear the counters.  i measured the sticks at 140 degrees F without the fan.  with fan they're comfortable to the touch.

[LogicalUnit]

I've got the same/similar setup(hub/pi/bfgminer).  when i plugged in 7 sticks i had 2 give problems.  one was puking errors and the other refused to hash.

i unplugged 1 stick and started a fan blowing across the 6 USB sticks.  the 1 stick which was previously giving >10% hw errors started hashing normally.
the 6 sticks even after not clearing errors are now averaging ~1% hw errs over 30 hours now.  the actual rate should be much lower once i restart and clear the counters.  i measured the sticks at 140 degrees F without the fan.  with fan they're comfortable to the touch.

How much current does your power adapter deliver? The USB eruptors require 500mA each. The DUB-H7 can deliver 3A, which is 5 eruptors and 1 fan, or 6 eruptors.

[jaycuse]

So I have 2 USB ASIC Erupters on a DLink H7 connected to my pi (using latest wheezy hard-float build). Got cgminer 3.2.2 installed and it's mining. However, 1 is averaging at 60 MH/s and the other one is averaging 116 MH/s. I have no clue why it's going so slow.

I using these current configurations
http://learn.adafruit.com/piminer-raspberry-pi-bitcoin-miner/configure-settings


Now when I go a plug the hub into my PC running Windows 7 and I run cgminer with same configs, I'm getting the desired average of 333 MH/s per stick.

Since I'm getting my desired hashrate on my windows machine it's making me think that it's a software problem. I though of it maybe being a hardware problem concerning power, but people are posting this hub works fine with 7 usb erupter's connected to them. I only have 2 connected at the moment.

I'm running out of ideas. Anyone have an idea of what it could be?

[jaycuse]

I thought you didn't need drivers for linux? I don't recall installing any or reading that I need to for my pi.

[LaserHorse]

So I have 2 USB ASIC Erupters on a DLink H7 connected to my pi (using latest wheezy hard-float build). Got cgminer 3.2.2 installed and it's mining. However, 1 is averaging at 60 MH/s and the other one is averaging 116 MH/s. I have no clue why it's going so slow.

I using these current configurations
http://learn.adafruit.com/piminer-raspberry-pi-bitcoin-miner/configure-settings


Now when I go a plug the hub into my PC running Windows 7 and I run cgminer with same configs, I'm getting the desired average of 333 MH/s per stick.

Since I'm getting my desired hashrate on my windows machine it's making me think that it's a software problem. I though of it maybe being a hardware problem concerning power, but people are posting this hub works fine with 7 usb erupter's connected to them. I only have 2 connected at the moment.

I'm running out of ideas. Anyone have an idea of what it could be?

I had trouble with 3.2.2 on wheezy as well - 3.1.1 works fine using icarus params

here's a step-by-step for the install:
http://learn.adafruit.com/piminer-raspberry-pi-bitcoin-miner/install-cgminer#cgminer

[MikeMike]

So I have 2 USB ASIC Erupters on a DLink H7 connected to my pi (using latest wheezy hard-float build). Got cgminer 3.2.2 installed and it's mining. However, 1 is averaging at 60 MH/s and the other one is averaging 116 MH/s. I have no clue why it's going so slow.

I using these current configurations
http://learn.adafruit.com/piminer-raspberry-pi-bitcoin-miner/configure-settings


Now when I go a plug the hub into my PC running Windows 7 and I run cgminer with same configs, I'm getting the desired average of 333 MH/s per stick.

Since I'm getting my desired hashrate on my windows machine it's making me think that it's a software problem. I though of it maybe being a hardware problem concerning power, but people are posting this hub works fine with 7 usb erupter's connected to them. I only have 2 connected at the moment.

I'm running out of ideas. Anyone have an idea of what it could be?

Make sure you are using a Verified Hub when using Pi.

Verified Peripherals/Hubs:
http://elinux.org/RPi_VerifiedPeripherals#Powered_USB_Hubs

[jaycuse]

I had trouble with 3.2.2 on wheezy as well - 3.1.1 works fine using icarus params

here's a step-by-step for the install:
http://learn.adafruit.com/piminer-raspberry-pi-bitcoin-miner/install-cgminer#cgminer

Just installed it and it looks like it solved the problem.

Thanks

[MikeMike]

So I have 2 USB ASIC Erupters on a DLink H7 connected to my pi (using latest wheezy hard-float build). Got cgminer 3.2.2 installed and it's mining. However, 1 is averaging at 60 MH/s and the other one is averaging 116 MH/s. I have no clue why it's going so slow.

I using these current configurations
http://learn.adafruit.com/piminer-raspberry-pi-bitcoin-miner/configure-settings


Now when I go a plug the hub into my PC running Windows 7 and I run cgminer with same configs, I'm getting the desired average of 333 MH/s per stick.

Since I'm getting my desired hashrate on my windows machine it's making me think that it's a software problem. I though of it maybe being a hardware problem concerning power, but people are posting this hub works fine with 7 usb erupter's connected to them. I only have 2 connected at the moment.

I'm running out of ideas. Anyone have an idea of what it could be?

I had trouble with 3.2.2 on wheezy as well - 3.1.1 works fine using icarus params

here's a step-by-step for the install:
http://learn.adafruit.com/piminer-raspberry-pi-bitcoin-miner/install-cgminer#cgminer

OP updated.
Thanks!

[Polyatomic]

Im using difficulty 128 , HW values seem high . Any feedback would be helpful , I will be moving my hardware to a PI today.

[Troupster]

Im using difficulty 128 , HW values seem high . Any feedback would be helpful , I will be moving my hardware to a PI today.

Higher difficulty threw more errors in my testing.

Don't know why

[os2sam]

Im using difficulty 128 , HW values seem high . Any feedback would be helpful , I will be moving my hardware to a PI today.

Higher difficulty threw more errors in my testing.

Don't know why

Because you need to convert your shares to Diff1 to calculate HW errors correctly.