HashFast BabyJet users thread

[jspielberg]

I am using 3.11 compiled for ubuntu.

The temperatures were reading 80 to 85 range (with occasional thermal throttling at 85).
I threw big box fan in back of the units and now they rarely go above 80.

They have been stable for me (1 since friday and 1 since this morning).

Whats the ambient temperature in the room?

I haven't measured... but it is an unfinished basement.... figure high 60s low 70s.

[1715276996]

1715276996

[1715276996]

1715276996

[1715276996]

1715276996

[1715276996]

1715276996

[joshv06]

Eligius is showing exactly 4800 Ghash with 12 of my BJ's. I guess it's safe to say 400Ghash/rig. About 3 of my BJ's had the radiators pulling are in rather than blowing out. Does having a cooler BJ yield higher Ghash?

[perezoso]

At ambient 70f/21c, my BJ reported 73-74c, with cgminer 3.11, no overclock.  It did not rise higher and throttling obviously did not kick in.

But I may have a low spec machine.  Out of the box mine does 390-395 gh/s.

If it ran faster, like the 430 gh/s some people report, the temp might be higher.

Brief experience so far suggests to me that cooling it down to the upper 60s centigrade yields a few gh/s improvement.

Cooling it down further - to 58-59c - doesn't seem to make much additional difference so far, although maybe that could provide more "room" to overclock.

[ninjarobot]

In other news, my BJ still goes belly up after ~30 hrs of stable mining. I'm still on cgminer3.9.0h2 so I might try compiling the 3.11 version to see if that fixes my stability issues.

Just happened again. Checking the cgminer logs this is the error I get:

Code:

[2014-01-28 20:53:32] HFA 0: Bad work sequence tail                                                              
[2014-01-28 20:53:33] HFA 0 HFClearRead usb read err:(-9) LIBUSB_ERROR_PIPE                                      
[2014-01-28 20:53:33] HFA 0 attempted reset got err:(-5) LIBUSB_ERROR_NOT_FOUND                                  
[2014-01-28 20:53:38] Hotplug: Hashfast added HFA 1 

In most cases I end up with two devices HFA 0 reporting some crazy TH figures, and a new HFA 1 device working correctly. In some cases HFA 1 does not appear and mining stops.

[jddebug]

In other news, my BJ still goes belly up after ~30 hrs of stable mining. I'm still on cgminer3.9.0h2 so I might try compiling the 3.11 version to see if that fixes my stability issues.

Just happened again. Checking the cgminer logs this is the error I get:

Code:

[2014-01-28 20:53:32] HFA 0: Bad work sequence tail                                                              
[2014-01-28 20:53:33] HFA 0 HFClearRead usb read err:(-9) LIBUSB_ERROR_PIPE                                      
[2014-01-28 20:53:33] HFA 0 attempted reset got err:(-5) LIBUSB_ERROR_NOT_FOUND                                  
[2014-01-28 20:53:38] Hotplug: Hashfast added HFA 1 

In most cases I end up with two devices HFA 0 reporting some crazy TH figures, and a new HFA 1 device working correctly. In some cases HFA 1 does not appear and mining stops.

On BFL devices these types of things are usually due to USB cables or hubs that are bad. Dunno about hashfast as I don't have mine yet.

[zero-asic]

In other news, my BJ still goes belly up after ~30 hrs of stable mining. I'm still on cgminer3.9.0h2 so I might try compiling the 3.11 version to see if that fixes my stability issues.

Just happened again. Checking the cgminer logs this is the error I get:

Code:

[2014-01-28 20:53:32] HFA 0: Bad work sequence tail                                                              
[2014-01-28 20:53:33] HFA 0 HFClearRead usb read err:(-9) LIBUSB_ERROR_PIPE                                      
[2014-01-28 20:53:33] HFA 0 attempted reset got err:(-5) LIBUSB_ERROR_NOT_FOUND                                  
[2014-01-28 20:53:38] Hotplug: Hashfast added HFA 1 

In most cases I end up with two devices HFA 0 reporting some crazy TH figures, and a new HFA 1 device working correctly. In some cases HFA 1 does not appear and mining stops.

I'm experiencing a similar problem.  What version of minepeon and cgminer are you using?

[ninjarobot]

I'm experiencing a similar problem.  What version of minepeon and cgminer are you using?

I'm using what HF shipped me:

• MinePeon Version: MinePeon 0.2.4.3
• Miner Version: cgminer3.9.0h2

Once I find some free time I will try a different USB cable, upgrading to 3.11 and reflashing the SD card to see if any of these options help.

[zero-asic]

I'm experiencing a similar problem.  What version of minepeon and cgminer are you using?

I'm using what HF shipped me:

• MinePeon Version: MinePeon 0.2.4.3
• Miner Version: cgminer3.9.0h2

Once I find some free time I will try a different USB cable, upgrading to 3.11 and reflashing the SD card to see if any of these options help.

I reflashed the SD card to 0.2.4.3 and it's stable.  When I tried to update to cgminer 3.11 on 0.2.4.3 it crashed after a few hours and so did Minepeon 0.2.5-pr1, even when I had the clock speed set to default.

[edgie13]

I'm experiencing a similar problem.  What version of minepeon and cgminer are you using?

I'm using what HF shipped me:

• MinePeon Version: MinePeon 0.2.4.3
• Miner Version: cgminer3.9.0h2

Once I find some free time I will try a different USB cable, upgrading to 3.11 and reflashing the SD card to see if any of these options help.

It's more likely an issue with the Raspberry PI's USB port. I had similar issues with running 49 block erupters on a powered hub. You can setup a cron job to restart your PI every few hours. If possible, run your Baby Jet off of a normal computer for a few days.  That way you could confirm whether or not the RPI is the problem. Good luck.

[-ck]

Just posted a new version of cgminer, 3.12.0 which hopefully copes better with transient USB errors on these.

[jspielberg]

Ck, I just upgraded to 3.12.  With 3.11, I was seeing CRC error messages.

When I start up I see a bunch of these messages.

Code:

Jan 29 06:32:01 cgminer[24956]: HFB 0: Bad CRC 0 vs 175, discarding packet
Jan 29 06:32:01 cgminer[24956]: HFB 0: Bad CRC 0 vs 175, discarding packet
Jan 29 06:32:01 cgminer[24956]: HFB 0: Bad CRC 0 vs 75, discarding packet
Jan 29 06:32:02 cgminer[24956]: HFB 0: Bad CRC 0 vs 175, discarding packet
Jan 29 06:32:02 cgminer[24956]: HFB 0: Bad CRC 0 vs 175, discarding packet
Jan 29 06:32:02 cgminer[24956]: HFB 0: Bad CRC 0 vs 75, discarding packet
Jan 29 06:32:02 cgminer[24956]: HFB 0: Bad CRC 0 vs 175, discarding packet
Jan 29 06:32:02 cgminer[24956]: HFB 0: Bad CRC 0 vs 175, discarding packet
Jan 29 06:32:02 cgminer[24956]: HFB 0: Bad CRC 0 vs 75, discarding packet

I only saw these during cgminer startup and on rare occasion during mining.
Will the new version handle whatever was causing those better?

[Taugeran]

yup hashfast device failing to initialize

 cgminer version 3.9.0 - Started: [2014-01-24 01:47:40]
--------------------------------------------------------------------------------
 (5s):0.000 (avg):0.000h/s | A:0  R:0  HW:0  WU:0.0/m
 ST: 2  SS: 0  NB: 1  LW: 12  GF: 0  RF: 0
 Connected to stratum.btcguild.com diff 256 with stratum as user xxxxxxxxxxxx
 Block: 23c5db73...  Diff:1.79G  Started: [01:47:40]  Best share: 0
--------------------------------------------------------------------------------
 [P]ool management [  S]ettings [D]isplay options [Q]uit
--------------------------------------------------------------------------------

 [2014-01-24 01:48:31] Hashfast detect (1:4) failed to initialise (incorrect device?)
 [2014-01-24 01:48:38] USB init, open device failed, err -3, you don't have privilege to access - HFA device 1:4-i1
 [2014-01-24 01:48:38] See README file included for help
 [2014-01-24 01:48:38] Hashfast detect (1:4) failed to initialise (incorrect device?)
 [2014-01-24 01:48:45] USB init, open device failed, err -3, you don't have privilege to access - HFA device 1:4-i1
 [2014-01-24 01:48:45] See README file included for help
 [2014-01-24 01:48:45] Hashfast detect (1:4) failed to initialise (incorrect device?)
 [2014-01-24 01:48:53] USB init, open device failed, err -3, you don't have privilege to access - HFA device 1:4-i1
 [2014-01-24 01:48:53] See README file included for help
 [2014-01-24 01:48:53] Hashfast detect (1:4) failed to initialise (incorrect device?)
 [2014-01-24 01:49:00] USB init, open device failed, err -3, you don't have privilege to access - HFA device 1:4-i1
 [2014-01-24 01:49:00] See README file included for help
 [2014-01-24 01:49:00] Hashfast detect (1:4) failed to initialise (incorrect device?)

try running cgminer as sudo. my clue is this line:

 [2014-01-24 01:48:38] USB init, open device failed, err -3, you don't have privilege to access - HFA device 1:4-i1


mentioning priveleges

[jspielberg]

So... what do you guys make of these messages:

[2014-01-29 11:49:42] HFB 12: Bad CRC 0 vs 159, discarding packet
 [2014-01-29 11:49:43] HFB 12: Bad CRC 0 vs 175, discarding packet
 [2014-01-29 11:49:43] HFB 12: Bad CRC 0 vs 175, discarding packet
 [2014-01-29 11:49:43] HFB 12: Bad CRC 0 vs 159, discarding packet
 [2014-01-29 11:49:44] HFB 12 HFGetHeader usb read err:(-9) LIBUSB_ERROR_PIPE
 [2014-01-29 11:49:44] HFB 12: device disappeared, disabling
 [2014-01-29 11:49:44] HFB 12 failure, disabling!
 [2014-01-29 11:49:49] Accepted 67770695 Diff 633/512 HFB 11
 [2014-01-29 11:49:51] Hotplug: Hashfast added HFB 13
 [2014-01-29 11:49:51] HFB 11: Bad CRC 0 vs 175, discarding packet
 [2014-01-29 11:49:51] HFB 11: Bad CRC 0 vs 175, discarding packet
 [2014-01-29 11:49:51] HFB 11: Bad CRC 0 vs 175, discarding packet
 [2014-01-29 11:49:51] HFB 11: Bad CRC 0 vs 178, discarding packet
 [2014-01-29 11:49:52] HFB 11: Bad CRC 0 vs 175, discarding packet
 [2014-01-29 11:49:52] HFB 11: Bad CRC 0 vs 175, discarding packet
 [2014-01-29 11:49:52] HFB 11: Bad CRC 0 vs 178, discarding packet
 [2014-01-29 11:49:52] HFB 11: Bad CRC 0 vs 175, discarding packet
 [2014-01-29 11:49:52] HFB 11: Bad CRC 0 vs 175, discarding packet
 [2014-01-29 11:49:52] HFB 11: Bad CRC 0 vs 178, discarding packet
 [2014-01-29 11:49:53] HFB 11: Bad CRC 0 vs 175, discarding packet
 [2014-01-29 11:49:53] HFB 11: Bad CRC 0 vs 175, discarding packet
 [2014-01-29 11:49:53] HFB 11: Bad CRC 0 vs 178, discarding packet
 [2014-01-29 11:49:53] HFB 11: Bad CRC 0 vs 175, discarding packet
 [2014-01-29 11:49:53] HFB 11: Bad CRC 0 vs 175, discarding packet
 [2014-01-29 11:49:53] HFB 11: Bad CRC 0 vs 178, discarding packet
 [2014-01-29 11:49:54] HFB 11: Bad CRC 0 vs 175, discarding packet
 [2014-01-29 11:49:54] HFB 11: Bad CRC 0 vs 175, discarding packet
 [2014-01-29 11:49:54] HFB 11: Bad CRC 0 vs 178, discarding packet
 [2014-01-29 11:49:54] HFB 11: Bad CRC 0 vs 175, discarding packet
 [2014-01-29 11:49:54] HFB 11: Bad CRC 0 vs 175, discarding packet
 [2014-01-29 11:49:55] Accepted 6dcaae63 Diff 597/512 HFB 13
 [2014-01-29 11:49:59] Accepted 5e7269c3 Diff 694/512 HFB 11
 [2014-01-29 11:50:00] Accepted 7d2a89d4 Diff 524/512 HFB 11

Looks to me like USB communication issues.

[minternj]

Con is there a way to show the temps of the individual dies without turning on debug?

[edgie13]

So... what do you guys make of these messages:

[2014-01-29 11:49:42] HFB 12: Bad CRC 0 vs 159, discarding packet
 [2014-01-29 11:49:43] HFB 12: Bad CRC 0 vs 175, discarding packet
 [2014-01-29 11:49:43] HFB 12: Bad CRC 0 vs 175, discarding packet
 [2014-01-29 11:49:43] HFB 12: Bad CRC 0 vs 159, discarding packet
 [2014-01-29 11:49:44] HFB 12 HFGetHeader usb read err:(-9) LIBUSB_ERROR_PIPE
 [2014-01-29 11:49:44] HFB 12: device disappeared, disabling
 [2014-01-29 11:49:44] HFB 12 failure, disabling!
 [2014-01-29 11:49:49] Accepted 67770695 Diff 633/512 HFB 11
 [2014-01-29 11:49:51] Hotplug: Hashfast added HFB 13
 [2014-01-29 11:49:51] HFB 11: Bad CRC 0 vs 175, discarding packet
 [2014-01-29 11:49:51] HFB 11: Bad CRC 0 vs 175, discarding packet
 [2014-01-29 11:49:51] HFB 11: Bad CRC 0 vs 175, discarding packet
 [2014-01-29 11:49:51] HFB 11: Bad CRC 0 vs 178, discarding packet
 [2014-01-29 11:49:52] HFB 11: Bad CRC 0 vs 175, discarding packet
 [2014-01-29 11:49:52] HFB 11: Bad CRC 0 vs 175, discarding packet
 [2014-01-29 11:49:52] HFB 11: Bad CRC 0 vs 178, discarding packet
 [2014-01-29 11:49:52] HFB 11: Bad CRC 0 vs 175, discarding packet
 [2014-01-29 11:49:52] HFB 11: Bad CRC 0 vs 175, discarding packet
 [2014-01-29 11:49:52] HFB 11: Bad CRC 0 vs 178, discarding packet
 [2014-01-29 11:49:53] HFB 11: Bad CRC 0 vs 175, discarding packet
 [2014-01-29 11:49:53] HFB 11: Bad CRC 0 vs 175, discarding packet
 [2014-01-29 11:49:53] HFB 11: Bad CRC 0 vs 178, discarding packet
 [2014-01-29 11:49:53] HFB 11: Bad CRC 0 vs 175, discarding packet
 [2014-01-29 11:49:53] HFB 11: Bad CRC 0 vs 175, discarding packet
 [2014-01-29 11:49:53] HFB 11: Bad CRC 0 vs 178, discarding packet
 [2014-01-29 11:49:54] HFB 11: Bad CRC 0 vs 175, discarding packet
 [2014-01-29 11:49:54] HFB 11: Bad CRC 0 vs 175, discarding packet
 [2014-01-29 11:49:54] HFB 11: Bad CRC 0 vs 178, discarding packet
 [2014-01-29 11:49:54] HFB 11: Bad CRC 0 vs 175, discarding packet
 [2014-01-29 11:49:54] HFB 11: Bad CRC 0 vs 175, discarding packet
 [2014-01-29 11:49:55] Accepted 6dcaae63 Diff 597/512 HFB 13
 [2014-01-29 11:49:59] Accepted 5e7269c3 Diff 694/512 HFB 11
 [2014-01-29 11:50:00] Accepted 7d2a89d4 Diff 524/512 HFB 11

Looks to me like USB communication issues.

Raspberry PI or normal PC?

[xuemike]

So... what do you guys make of these messages:

[2014-01-29 11:49:42] HFB 12: Bad CRC 0 vs 159, discarding packet
 [2014-01-29 11:49:43] HFB 12: Bad CRC 0 vs 175, discarding packet
 [2014-01-29 11:49:43] HFB 12: Bad CRC 0 vs 175, discarding packet
 [2014-01-29 11:49:43] HFB 12: Bad CRC 0 vs 159, discarding packet
 [2014-01-29 11:49:44] HFB 12 HFGetHeader usb read err:(-9) LIBUSB_ERROR_PIPE
 [2014-01-29 11:49:44] HFB 12: device disappeared, disabling
 [2014-01-29 11:49:44] HFB 12 failure, disabling!
 [2014-01-29 11:49:49] Accepted 67770695 Diff 633/512 HFB 11
 [2014-01-29 11:49:51] Hotplug: Hashfast added HFB 13
 [2014-01-29 11:49:51] HFB 11: Bad CRC 0 vs 175, discarding packet
 [2014-01-29 11:49:51] HFB 11: Bad CRC 0 vs 175, discarding packet
 [2014-01-29 11:49:51] HFB 11: Bad CRC 0 vs 175, discarding packet
 [2014-01-29 11:49:51] HFB 11: Bad CRC 0 vs 178, discarding packet
 [2014-01-29 11:49:52] HFB 11: Bad CRC 0 vs 175, discarding packet
 [2014-01-29 11:49:52] HFB 11: Bad CRC 0 vs 175, discarding packet
 [2014-01-29 11:49:52] HFB 11: Bad CRC 0 vs 178, discarding packet
 [2014-01-29 11:49:52] HFB 11: Bad CRC 0 vs 175, discarding packet
 [2014-01-29 11:49:52] HFB 11: Bad CRC 0 vs 175, discarding packet
 [2014-01-29 11:49:52] HFB 11: Bad CRC 0 vs 178, discarding packet
 [2014-01-29 11:49:53] HFB 11: Bad CRC 0 vs 175, discarding packet
 [2014-01-29 11:49:53] HFB 11: Bad CRC 0 vs 175, discarding packet
 [2014-01-29 11:49:53] HFB 11: Bad CRC 0 vs 178, discarding packet
 [2014-01-29 11:49:53] HFB 11: Bad CRC 0 vs 175, discarding packet
 [2014-01-29 11:49:53] HFB 11: Bad CRC 0 vs 175, discarding packet
 [2014-01-29 11:49:53] HFB 11: Bad CRC 0 vs 178, discarding packet
 [2014-01-29 11:49:54] HFB 11: Bad CRC 0 vs 175, discarding packet
 [2014-01-29 11:49:54] HFB 11: Bad CRC 0 vs 175, discarding packet
 [2014-01-29 11:49:54] HFB 11: Bad CRC 0 vs 178, discarding packet
 [2014-01-29 11:49:54] HFB 11: Bad CRC 0 vs 175, discarding packet
 [2014-01-29 11:49:54] HFB 11: Bad CRC 0 vs 175, discarding packet
 [2014-01-29 11:49:55] Accepted 6dcaae63 Diff 597/512 HFB 13
 [2014-01-29 11:49:59] Accepted 5e7269c3 Diff 694/512 HFB 11
 [2014-01-29 11:50:00] Accepted 7d2a89d4 Diff 524/512 HFB 11

Looks to me like USB communication issues.

Raspberry PI or normal PC?

One of my units is behaving in a very similar fashion.  it might be the unit is constantly resetting, if you keep hearing the clicking sound it means that cgminer is trying to bring up these guys online, and the reason why you keep seeing a high hashrate count on the cgminer is because the web UI is constantly detecting the units after the reset and stacks the old gh/s to the new gh/s.  So it looks like you have a lot of units running like HFA0 HFA1 HFA2, HFA0 died, and HFA1 is the new hardware detected after HFA resetted.

This is a RMA case for sure. try to get in contact with someone at hashfast.  I've been trying to RMA this for few days now, but still no answer.

[wpgdeez]

It's amazing how hot these things run with watercooling, a GPU that is watercooled will only run at 45-50. Inefficient design?

[jspielberg]

Raspberry PI or normal PC?

Ubuntu PC running 3.12.0 cgminer

[-ck]

Con is there a way to show the temps of the individual dies without turning on debug?

Check API output. Plenty of info there.

[-ck]

Ck, I just upgraded to 3.12.  With 3.11, I was seeing CRC error messages.

When I start up I see a bunch of these messages.

Code:

Jan 29 06:32:01 cgminer[24956]: HFB 0: Bad CRC 0 vs 175, discarding packet
Jan 29 06:32:01 cgminer[24956]: HFB 0: Bad CRC 0 vs 175, discarding packet
Jan 29 06:32:01 cgminer[24956]: HFB 0: Bad CRC 0 vs 75, discarding packet
Jan 29 06:32:02 cgminer[24956]: HFB 0: Bad CRC 0 vs 175, discarding packet
Jan 29 06:32:02 cgminer[24956]: HFB 0: Bad CRC 0 vs 175, discarding packet
Jan 29 06:32:02 cgminer[24956]: HFB 0: Bad CRC 0 vs 75, discarding packet
Jan 29 06:32:02 cgminer[24956]: HFB 0: Bad CRC 0 vs 175, discarding packet
Jan 29 06:32:02 cgminer[24956]: HFB 0: Bad CRC 0 vs 175, discarding packet
Jan 29 06:32:02 cgminer[24956]: HFB 0: Bad CRC 0 vs 75, discarding packet

I only saw these during cgminer startup and on rare occasion during mining.
Will the new version handle whatever was causing those better?

CRC errors are something wrong in firmware, hardware or something else and long before USB is involved. Presumably if it only happens on startup there's some stale communication data lying around for some reason and cgminer is tossing it, waiting till the information is normal. The point of the CRC is to see if we're receiving what the device thinks it's sending.

However it should cope with USB comms errors better which seem to happen just before these happen, so maybe it will help.