Bitcoin Forum

Hello all, long time lurker and first time poster here. I have run a ground and would like any help I can get. I am creating a "Bitcoin Mining Museum" (or that's what I tell myself at least.), the best of the new and the old. Eventually I want some network miners but we are starting off with USB Miners for now. I have gotten my 2PAC USB Miners to run without issue using the custom built CGMiner version needed for the 2PAC, see more in the Troubleshoot Thread https://bitcointalk.org/index.php?topic=1764803.0 (https://bitcointalk.org/index.php?topic=1764803.0). I cannot get my ASCIMiner Block Erupters to work with it though. I have tried compiling it with both --enable-blockerupter and --enable-icarus. The --enable-icarus flag sees the miner, but it returns failure to initialize, and returns no work. It seems I am missing some extra flag, similar to frequency setting on the 2PAC. Any help or point in the right direction would be great. Thanks!

System Info - Raspberry Pi 2b+ on newest raspian install.
Minera as a front end for custom built CGMiner designed to run the 2PAC

EDIT

Log of me plugging in, unplugging, and plugging in a different Block Erupter
-snip-
[2017-04-17 19:13:14.645] failed usb_init
[2017-04-17 19:13:16.038] Hotplug: Icarus added AMU 0
[2017-04-17 19:14:15.366] AMU 0: Comms error (rerr=-9 amt=33210144)
[2017-04-17 19:14:15.370] AMU 0 failure, disabling!
[2017-04-17 19:14:27.474] failed usb_init
[2017-04-17 19:14:29.980] Hotplug: Icarus added AU3 0
[2017-04-17 19:14:32.085] AU3 0: No valid hashes for over 2 secs, attempting to reset
[2017-04-17 19:14:32.279] AU3 0 attempted reset got err:(0) LIBUSB_SUCCESS / LIBUSB_TRANSFER_COMPLETED
[2017-04-17 19:14:35.103] AU3 0: No valid hashes for over 2 secs, attempting to reset
[2017-04-17 19:14:35.309] AU3 0 attempted reset got err:(0) LIBUSB_SUCCESS / LIBUSB_TRANSFER_COMPLETED
[2017-04-17 19:14:50.094] AU3 0: No valid hashes for over 2 secs, attempting to reset
-snip-

Only thing I can think of is does Zadig see it? The CGminer USB coms run through it. Run Zadig and see if the device needs to be added to what it controls.
EDIT: nvm: Just caught on is not a Win system... Kept here for Win uses.
Could still be related to the device not being recognized for USB coms though.

i assume you compiling it from source? if so you need --enable-icarus  for usb miners
--enable-blockerupter   Compile support for ASICMINER BlockErupter Tube/Prisma (so completely pointless and could be what causing your problems) it may also be the fact that its a custom version with 2PAC USB, you could always compile a 2nd version cgminer1 and cgminer2 1 can run 2pac and 2 can run the ASIC miners (iv found this works best with mixed USB miners that dont like playing together

If you compile the new 4.10.0 of cgminer, it won't work.
Also U2 got the same problem.
Use 4.9.2 and it will work.
It looks like that there is a id problem with the 2Pac driver.

Lol that would be funny if it was true.
I asked them to send me one miner so I could test it with the older devides ... that I have most of ... but it seemed that was too expensive to do and they claimed some random person did check it and it was OK.

Of course the code was committed into cgminer 4.10.0 without a care if it worked or not :P

... and it's no longer my problem :D

FYI I have one of the first ever block erupters sent out to the public.