Hi,

I tried to use "cgminer --benchmark" with an BlockEruptor (seems also
known as Icarus and is labeled "USB BE Rev. 3.00" on the device as shown
on http://bitcoinrigs.org/product/asicminer-block-erupter-usb-bitcoin-miner/)
and it recognizes the deivce, but can't initialise it:

 [2015-05-15 22:33:38] Icarus detect (1:11) failed to initialise (incorrect device?)
 [2015-05-15 22:33:45] USB init, claim ifinfo 0 interface 0 in use - BET device 1:11
 [2015-05-15 22:33:45] blockerupter detect (1:11) failed to initialise (incorrect device?)
 [2015-05-15 22:33:45] Blockerupter usb init failed
 [2015-05-15 22:33:45] USB init, claim ifinfo 0 interface 0 in use - AMU device 1:11
 [2015-05-15 22:33:45] Icarus detect (1:11) failed to initialise (incorrect device?)
 [2015-05-15 22:33:46] USB init, claim ifinfo 0 interface 0 in use - AMU device 1:11
 [2015-05-15 22:33:46] Icarus detect (1:11) failed to initialise (incorrect device?)
 [2015-05-15 22:33:52] USB init, claim ifinfo 0 interface 0 in use - BET device 1:11
 [2015-05-15 22:33:52] blockerupter detect (1:11) failed to initialise (incorrect device?)
 [2015-05-15 22:33:52] Blockerupter usb init failed
 [2015-05-15 22:33:52] USB init, claim ifinfo 0 interface 0 in use - AMU device 1:11
 [2015-05-15 22:33:52] Icarus detect (1:11) failed to initialise (incorrect device?)
 [2015-05-15 22:33:53] USB init, claim ifinfo 0 interface 0 in use - AMU device 1:11
 [2015-05-15 22:33:53] Icarus detect (1:11) failed to initialise (incorrect device?)
 [2015-05-15 22:33:59] USB init, claim ifinfo 0 interface 0 in use - BET device 1:11
 [2015-05-15 22:33:59] blockerupter detect (1:11) failed to initialise (incorrect device?)
 [2015-05-15 22:33:59] Blockerupter usb init failed
 [2015-05-15 22:34:00] USB init, claim ifinfo 0 interface 0 in use - AMU device 1:11
 [2015-05-15 22:34:00] Icarus detect (1:11) failed to initialise (incorrect device?)
 [2015-05-15 22:34:00] USB init, claim ifinfo 0 interface 0 in use - AMU device 1:11
 [2015-05-15 22:34:00] Icarus detect (1:11) failed to initialise (incorrect device?)
 [2015-05-15 22:34:06] USB init, claim ifinfo 0 interface 0 in use - BET device 1:11
 [2015-05-15 22:34:06] blockerupter detect (1:11) failed to initialise (incorrect device?)
 [2015-05-15 22:34:06] Blockerupter usb init failed
 [2015-05-15 22:34:07] USB init, claim ifinfo 0 interface 0 in use - AMU device 1:11
 [2015-05-15 22:34:07] Icarus detect (1:11) failed to initialise (incorrect device?)
 [2015-05-15 22:34:07] USB init, claim ifinfo 0 interface 0 in use - AMU device 1:11
 [2015-05-15 22:34:07] Icarus detect (1:11) failed to initialise (incorrect device?)

It doesn't seem to make a difference if I run cgminer as root or as
normal user.

A friend of mine ran into the same issue on Jessie and said, it worked
for him with an unofficial cgminer package from
http://archive.getdeb.net/ubuntu/pool/apps/c/cgminer/cgminer_4.9.1-1~getdeb1_i386.deb
http://archive.getdeb.net/ubuntu/pool/apps/c/cgminer/cgminer_4.9.1-1~getdeb1.dsc

So if it's an upstream issue, it's likely already fixed upstream. At
least the upstream changlog lists a lot of icarus related changes for
the 4.8.0 release.

But it could also be a package difference as the packages don't seem to
have a common ancestor (according to the changelogs and
https://bugs.launchpad.net/getdeb.net/+bug/1257439) and differ a lot,
too. On the other hand the unofficial package has no specific udev
rules, etc. So I rather assume it's an upstream issue.

Thanks for the detailed report!
I tried to look into the getdeb.net version but couldn't see how/what
they are doing differently. Now that jessie is released I uploaded
cgminer 4.9.2. Could you test that version (in unstable) and see if it
works any better?
~Scott

Hi,

Scott Howard wrote:

This looks much better, indeed:

[2015-06-25 19:54:44] AMU 0: Found at 2:102

Can be closed with 4.9.2-1 from my point of view.

		Regards, Axel

Dear submitter,

as the package cgminer has just been removed from the Debian archive
unstable we hereby close the associated bug reports.  We are sorry
that we couldn't deal with your issue properly.

For details on the removal, please see https://bugs.debian.org/1033881

The version of this package that was in Debian prior to this removal
can still be found using https://snapshot.debian.org/.

Please note that the changes have been done on the master archive and
will not propagate to any mirrors until the next dinstall run at the
earliest.

This message was generated automatically; if you believe that there is
a problem with it please contact the archive administrators by mailing
ftpmaster@ftp-master.debian.org.

Debian distribution maintenance software
pp.
Scott Kitterman (the ftpmaster behind the curtain)