bad Block Erupter?

[soy]

Block Erupter from BTCGuild arrived today, rather yesterday.  Spent the last 14 hours trying to get it to hash without success.

ft232r_scan: Found 0424:9512 - not a ft232r was a complaint by minepeon.
connect-debounce failed was noted on various machines.

I can see one of the two crystals isn't square on its pads.

I've order an expensive USB3.0 hub from Amazon and hope that will correct the problem but the Block Erupter arrived with the seal on the small white box opened so, it's even money this is dud.   I don't see an easy way to contact BTCGuild by email.  Seems to be missing from the website.

soy

[1714927921]

1714927921

[1714927921]

1714927921

[1714927921]

1714927921

[1714927921]

1714927921

[1714927921]

1714927921

[1714927921]

1714927921

[bystander]

You might want to PM eleuthria directly, though he might be quite busy with coding and packing (not necessarily at the same time).

[eleuthria]

Block Erupter from BTCGuild arrived today, rather yesterday.  Spent the last 14 hours trying to get it to hash without success.

ft232r_scan: Found 0424:9512 - not a ft232r was a complaint by minepeon.
connect-debounce failed was noted on various machines.

I can see one of the two crystals isn't square on its pads.

I've order an expensive USB3.0 hub from Amazon and hope that will correct the problem but the Block Erupter arrived with the seal on the small white box opened so, it's even money this is dud.   I don't see an easy way to contact BTCGuild by email.  Seems to be missing from the website.

soy

The seal on the box was opened because every unit is tested before being shipped to ensure it is not a DoA unit (~1-2% of units are DoA, ASICMINER includes 2% extra with each shipment to cover them).

Please try following the guide on BTC Guild, found here: http://www.btcguild.com/index.php?page=support&section=blockerupter

[soy]

cgminer version 3.3.1 - Started: [1969-12-31 19:00:29]
--------------------------------------------------------------------------------
 (5s):0.000 (avg):0.000h/s | DA:0  DR:0  HW:0  WU:0.0/m
 ST: 2  SS: 0  NB: 1  LW: 12  GF: 0  RF: 0
 Connected to xxxxxxxxxxxxxx diff 1 with stratum as user xxxxxxxxxxxxx
 Block: 00984d01467e0c43...  Diff:26.2M  Started: [19:00:29]  Best share: 0
--------------------------------------------------------------------------------
 [P]ool management ettings [D]isplay options [Q]uit
--------------------------------------------------------------------------------

 [1969-12-31 19:00:28] Started cgminer 3.3.1
 [1969-12-31 19:00:28] Loaded configuration file /opt/minepeon/etc/miner.conf
 [1969-12-31 19:00:28] No devices detected!
 [1969-12-31 19:00:28] Waiting for USB hotplug devices or press q to quit
 [1969-12-31 19:00:28] Probing for an alive pool
 [1969-12-31 19:00:29] Switching to pool 2 xxxxxxxxxxx:3333 - firs
t alive pool
 [1969-12-31 19:00:29] Pool 0 xxxxxxxxxxxxxxx:3333 alive
 [1969-12-31 19:00:29] Switching to pool 0 xxxxxxxxxxxxxxxxx:3333
 [1969-12-31 19:00:29] Network diff set to 26.2M
 [1969-12-31 19:00:34] API running in IP access mode on port 4028 (11)
 [1969-12-31 19:00:34] FAIL: USB get_lock not found (1:26)
 [1969-12-31 19:00:34] FAIL: USB remove not already in use (1:26)

[candoo]

This looks very odd. Did you find the issue yet?

[Bogart]

Try cgminer 3.1.1.  I find that's the only version my USB BEs are really happy with.

Also try running cgminer using sudo, if you're using linux.

[soy]

This looks very odd. Did you find the issue yet?

No.  And the B.E. LED gives a good, bright light which toggles off and on then stays on after the R.Pi is up and running.  The lines thru the test aren't mine but appeared when I copied and pasted.

When I try to run it on a Ubuntu system, and this has been running bfgminer with a zTex 1.15x, I get 'unable to enumerate USB device on port'.

[alfabitcoin]

This looks very odd. Did you find the issue yet?

No.  And the B.E. LED gives a good, bright light which toggles off and on then stays on after the R.Pi is up and running.  The lines thru the test aren't mine but appeared when I copied and pasted.

When I try to run it on a Ubuntu system, and this has been running bfgminer with a zTex 1.15x, I get 'unable to enumerate USB device on port'.

Are you use usb 2.0 or 3.0?

[soy]

This looks very odd. Did you find the issue yet?

No.  And the B.E. LED gives a good, bright light which toggles off and on then stays on after the R.Pi is up and running.  The lines thru the test aren't mine but appeared when I copied and pasted.

When I try to run it on a Ubuntu system, and this has been running bfgminer with a zTex 1.15x, I get 'unable to enumerate USB device on port'.

Are you use usb 2.0 or 3.0?

Just tried with a PCMCIA USB 2.0 adapter and got unable to enumerate USB device, and again with another PCMCIA USB 2.0 cardbus adapter, same thing. This on a Ubuntu system that runs zTex 1.15x just fine.

[alfabitcoin]

This looks very odd. Did you find the issue yet?

No.  And the B.E. LED gives a good, bright light which toggles off and on then stays on after the R.Pi is up and running.  The lines thru the test aren't mine but appeared when I copied and pasted.

When I try to run it on a Ubuntu system, and this has been running bfgminer with a zTex 1.15x, I get 'unable to enumerate USB device on port'.

Are you use usb 2.0 or 3.0?

Just tried with a PCMCIA USB 2.0 adapter and got unable to enumerate USB device, and again with another PCMCIA USB 2.0 cardbus adapter, same thing. This on a Ubuntu system that runs zTex 1.15x just fine.

-deleted-
EDIT
Quote from: bronan on June 21, 2013, 09:00:39 PM
Its actually connected to my old htpc at the moment since it does not work at all on my new intel i7 system even if i install any of them given winsub drivers
The new machine has many usb3 ports i am not sure if this is the reason why it totally fails to see the device even though its clearly listed in the usb devices under hardware.
You don't want the WinUSB driver for BFL devices. Uninstall that first.
FTDI's current official driver has problems with USB 3 ports.
If it's already installed, you will need to use their CDM_Uninstaller to remove it completely. Put VID 0403 and clear PID (it should be blank); add it to the list and uninstall.
Once that's done, the simple workaround is to use a USB 2 hub (or port) the first time you plug each device in.
After the device has installed correctly, you should be safe to move it back to a USB 3 port/hub.

[Trongersoll]

I'm guessing that you didn't look around much. If the USB Hub you bought is an Anker 10 Port 3.0 it won't work with RPi. You need a RPi verified Hub. there is a link to that list around here somewhere. There is also a whole thread about doing this on a Pi.

[notme]

This looks very odd. Did you find the issue yet?

No.  And the B.E. LED gives a good, bright light which toggles off and on then stays on after the R.Pi is up and running.  The lines thru the test aren't mine but appeared when I copied and pasted.

When I try to run it on a Ubuntu system, and this has been running bfgminer with a zTex 1.15x, I get 'unable to enumerate USB device on port'.

The lines are because the forum uses

Code:

[s]struck text[/s]

for strikethrough.... like this: struck text

Try wrapping what you pasted in code tags.  This will prevent the forum software from attempting to interpret anything within the tags.

[soy]

I'm guessing that you didn't look around much. If the USB Hub you bought is an Anker 10 Port 3.0 it won't work with RPi. You need a RPi verified Hub. there is a link to that list around here somewhere. There is also a whole thread about doing this on a Pi.

What I've been trying to use while awaiting the 7 port Plugable (I see is unverified and some report problems) is a CyberPower CP-HA420 with a 2.6 amp 5 volt supply it came with.  Waking them all up at once I was getting connect-debounce errors.  I just tried waking up the RPi with the hub but not the B.E, then plugged in the B.E.

[   65.763973] usbcore: registered new interface driver usbserial_generic
[   65.764083] USB Serial support registered for generic
[   65.764110] usbserial: USB Serial Driver core
[   65.858437] usbcore: registered new interface driver cp210x
[   65.858635] USB Serial support registered for cp210x
[   65.858781] cp210x 1-1.2.2:1.0: cp210x converter detected
[   65.956346] usb 1-1.2.2: reset full-speed USB device number 5 using dwc_otg
[   66.060840] usb 1-1.2.2: cp210x converter now attached to ttyUSB0
[   66.795443] cp210x ttyUSB0: cp210x converter now disconnected from ttyUSB0
[   66.795590] cp210x 1-1.2.2:1.0: device disconnected

added the B.E.

[root@minepeon minepeon]# dmesg | tail
[   72.506354] usb 1-1.2.2: device descriptor read/64, error -32
[   72.696266] usb 1-1.2.2: device descriptor read/64, error -32
[   72.886272] usb 1-1.2.2: new full-speed USB device number 7 using dwc_otg
[   72.966416] usb 1-1.2.2: device descriptor read/64, error -32
[   73.156318] usb 1-1.2.2: device descriptor read/64, error -32
[   73.346341] usb 1-1.2.2: new full-speed USB device number 8 using dwc_otg
[   73.766120] usb 1-1.2.2: device not accepting address 8, error -32
[   73.846295] usb 1-1.2.2: new full-speed USB device number 9 using dwc_otg
[   74.266224] usb 1-1.2.2: device not accepting address 9, error -32
[   74.266471] hub 1-1.2:1.0: unable to enumerate USB device on port 2

I went into  /sys/module/usbcore/parameters/ and changed old_scheme_first to Y and increased initial_descriptor_timeout from 5000 to 15000.

I rebooted and no joy.  I stopped cgminer and restarted getting this:

 [1969-12-31 19:06:05] Started cgminer 3.3.1
 [1969-12-31 19:06:05] Loaded configuration file /opt/minepeon/etc/miner.conf
 [1969-12-31 19:06:05] No devices detected!
 [1969-12-31 19:06:05] Waiting for USB hotplug devices or press q to quit

Seeing the hotplug notice, I tried disconnecting the B.E. and reconnecting.  No change.

[notme]

I'm guessing that you didn't look around much. If the USB Hub you bought is an Anker 10 Port 3.0 it won't work with RPi. You need a RPi verified Hub. there is a link to that list around here somewhere. There is also a whole thread about doing this on a Pi.

What I've been trying to use while awaiting the 7 port Plugable (I see is unverified and some report problems) is a CyberPower CP-HA420 with a 2.6 amp 5 volt supply it came with.  Waking them all up at once I was getting connect-debounce errors.  I just tried waking up the RPi with the hub but not the B.E, then plugged in the B.E.

[   65.763973] usbcore: registered new interface driver usbserial_generic
[   65.764083] USB Serial support registered for generic
[   65.764110] usbserial: USB Serial Driver core
[   65.858437] usbcore: registered new interface driver cp210x
[   65.858635] USB Serial support registered for cp210x
[   65.858781] cp210x 1-1.2.2:1.0: cp210x converter detected
[   65.956346] usb 1-1.2.2: reset full-speed USB device number 5 using dwc_otg
[   66.060840] usb 1-1.2.2: cp210x converter now attached to ttyUSB0
[   66.795443] cp210x ttyUSB0: cp210x converter now disconnected from ttyUSB0
[   66.795590] cp210x 1-1.2.2:1.0: device disconnected

The "device disconnected" messages here are normal if cgminer was running.

added the B.E.

[root@minepeon minepeon]# dmesg | tail
[   72.506354] usb 1-1.2.2: device descriptor read/64, error -32
[   72.696266] usb 1-1.2.2: device descriptor read/64, error -32
[   72.886272] usb 1-1.2.2: new full-speed USB device number 7 using dwc_otg
[   72.966416] usb 1-1.2.2: device descriptor read/64, error -32
[   73.156318] usb 1-1.2.2: device descriptor read/64, error -32
[   73.346341] usb 1-1.2.2: new full-speed USB device number 8 using dwc_otg
[   73.766120] usb 1-1.2.2: device not accepting address 8, error -32
[   73.846295] usb 1-1.2.2: new full-speed USB device number 9 using dwc_otg
[   74.266224] usb 1-1.2.2: device not accepting address 9, error -32
[   74.266471] hub 1-1.2:1.0: unable to enumerate USB device on port 2

I was getting these messages on one of my 14 hubs.  That hub is going back to Amazon.

I went into  /sys/module/usbcore/parameters/ and changed old_scheme_first to Y and increased initial_descriptor_timeout from 5000 to 15000.

I rebooted and no joy.  I stopped cgminer and restarted getting this:

Changes to /sys do not persist across reboots.  You need to set what you need set at bootup (in rc.local or whatever your distro uses).

[1969-12-31 19:06:05] Started cgminer 3.3.1
 [1969-12-31 19:06:05] Loaded configuration file /opt/minepeon/etc/miner.conf
 [1969-12-31 19:06:05] No devices detected!
 [1969-12-31 19:06:05] Waiting for USB hotplug devices or press q to quit

Seeing the hotplug notice, I tried disconnecting the B.E. and reconnecting.  No change.

I would guess you hub is busted.  Is it possible to test it on a different computer?

[agath]

I advice you to try CGMiner 3.1.1 first, and configure them using -S /dev/ttyUSBx, without direct libusb access.

Check also that the BE receives enough power.

My two bitcoincents.

[Pentel]

Have you tried the Bitminter pool miner software?  I've asked and they say you can use Erupters with there miner software.
No harm in trying...

[notme]

I advice you to try CGMiner 3.1.1 first, and configure them using -S /dev/ttyUSBx, without direct libusb access.

Check also that the BE receives enough power.

My two bitcoincents.

It wouldn't hurt to test your power brick if you have a multimeter, but the dmesg errors are not caused by an incorrect version of cgminer.

[soy]

Well, the other day I had replaced caps in a supply for an old Dell Inspiron 5150.  Power hungry laptop but fast.  I just gave the hub and B.E a try on that and no connections difficulties and correctly identified.  I'll have to fight with it to install mining software tho.  --nope, just looked back and now there's connect-debounce port error messages.  Perhaps after the B.E. warmed up?

[soy]

Well, the other day I had replaced caps in a supply for an old Dell Inspiron 5150.  Power hungry laptop but fast.  I just gave the hub and B.E a try on that and no connections difficulties and correctly identified.  I'll have to fight with it to install mining software tho.  --nope, just looked back and now there's connect-debounce port error messages.  Perhaps after the B.E. warmed up?

Tried it again.  First I put the B.E. at the output of my air conditioning for a minute until it was well cooled.  Then reinserted into the hub.  All was well for just about 60 seconds then the 'device descriptor read/64, read -32' messages appeared, then the 'unable to enumerate device' messages started.  Next to find out if it's the hub or the B.E. that changes.

With an air conditioner that looks like a Dr. Who darlek and the B.E. on a USB cable, the B.E. inserted into the AC output, the hub some distance, there are no error messages after 5 minutes.  Will now remove the B.E. from the AC and insert the hub.  Sixty-four seconds later the error messages started.  So, the problem starts after the B.E. heats.

[soy]

Well, the other day I had replaced caps in a supply for an old Dell Inspiron 5150.  Power hungry laptop but fast.  I just gave the hub and B.E a try on that and no connections difficulties and correctly identified.  I'll have to fight with it to install mining software tho.  --nope, just looked back and now there's connect-debounce port error messages.  Perhaps after the B.E. warmed up?

Tried it again.  First I put the B.E. at the output of my air conditioning for a minute until it was well cooled.  Then reinserted into the hub.  All was well for just about 60 seconds then the 'device descriptor read/64, read -32' messages appeared, then the 'unable to enumerate device' messages started.  Next to find out if it's the hub or the B.E. that changes.

With an air conditioner that looks like a Dr. Who darlek and the B.E. on a USB cable, the B.E. inserted into the AC output, the hub some distance, there are no error messages after 5 minutes.  Will now remove the B.E. from the AC and insert the hub.  Sixty-four seconds later the error messages started.  So, the problem starts after the B.E. heats.

The CP2101 gets hotest, in the neighborhood of 250°F according to my IR meter.  Don't want to give up until after I test it on a USB3.0 hub however and its tracking number isn't registering on the USPO tracking yet.