Pages:
Author

Topic: HashFast BabyJet users thread - page 49. (Read 69024 times)

sr. member
Activity: 434
Merit: 250
January 29, 2014, 05:51:30 PM
Con is there a way to show the temps of the individual dies without turning on debug?
Check API output. Plenty of info there.

Tried asc|1

STATUS=S,When=1391035500,Code=106,Msg=ASC1,Description=cgminer 3.12.0,ASC=1,Name=HFB,ID=1,Enabled=Y,Status=Alive,Temperature=0.00,MHS av=434726.40,MHS 5s=607976.58,Accepted=6839,Rejected=22,Hardware Errors=2950,Utility=23.64,Last Share Pool=0,Last Share Time=1391035498,Total MH=7545906066.6987,Diff1 Work=1756928,Difficulty Accepted=1750784.00000000,Difficulty Rejected=5632.00000000,Last Share Difficulty=256.00000000,No Device=false,Last Valid Work=1391035499,Device Hardware%=0.1676,Device Rejected%=0.3206,Device Elapsed=17358,


dev
STATUS=S,When=1391035718,Code=9,Msg=2 ASC(s) - 0 PGA(s),Description=cgminer 3.12.0,ASC=0,Name=HFB,ID=0,Enabled=N,Status=Alive,Temperature=0.00,MHS av=18080.34,MHS 5s=84166.69,Accepted=301,Rejected=1,Hardware Errors=125,Utility=0.98,Last Share Pool=0,Last Share Time=1391018115,Total MH=332052511.5110,Diff1 Work=77312,Difficulty Accepted=77056.00000000,Difficulty Rejected=256.00000000,Last Share Difficulty=256.00000000,No Device=true,Last Valid Work=1391018114,Device Hardware%=0.1614,Device Rejected%=0.3311,Device Elapsed=18365,ASC=1,Name=HFB,ID=1,Enabled=Y,Status=Alive,Temperature=0.00,MHS av=435529.15,MHS 5s=514642.31,Accepted=6939,Rejected=22,Hardware Errors=2987,Utility=23.69,Last Share Pool=0,Last Share Time=1391035712,Total MH=7654799950.7847,Diff1 Work=1782272,Difficulty Accepted=1776384.00000000,Difficulty Rejected=5632.00000000,Last Share Difficulty=256.00000000,No Device=false,Last Valid Work=1391035712,Device Hardware%=0.1673,Device Rejected%=0.3160,Device Elapsed=17576,

In these its just shows 0 for temp. Looked through other api commands, not sure where temp is. Will keep looking.
-ck
legendary
Activity: 4088
Merit: 1631
Ruu \o/
January 29, 2014, 05:04:52 PM
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.
-ck
legendary
Activity: 4088
Merit: 1631
Ruu \o/
January 29, 2014, 05:03:11 PM
Con is there a way to show the temps of the individual dies without turning on debug?
Check API output. Plenty of info there.
sr. member
Activity: 490
Merit: 255
January 29, 2014, 03:07:24 PM

Raspberry PI or normal PC?

Ubuntu PC running 3.12.0 cgminer
hero member
Activity: 728
Merit: 500
January 29, 2014, 02:36:34 PM
It's amazing how hot these things run with watercooling, a GPU that is watercooled will only run at 45-50. Inefficient design?
member
Activity: 116
Merit: 10
January 29, 2014, 02:27:40 PM
full member
Activity: 155
Merit: 100
January 29, 2014, 02:05:42 PM
sr. member
Activity: 434
Merit: 250
January 29, 2014, 02:03:59 PM
Con is there a way to show the temps of the individual dies without turning on debug?
sr. member
Activity: 490
Merit: 255
January 29, 2014, 01:52:15 PM
So... what do you guys make of these messages:

Quote
[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.
hero member
Activity: 658
Merit: 500
CCNA: There i fixed the internet.
January 29, 2014, 09:35:39 AM
sr. member
Activity: 490
Merit: 255
January 29, 2014, 08:16:26 AM
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?
-ck
legendary
Activity: 4088
Merit: 1631
Ruu \o/
January 29, 2014, 07:10:25 AM
Just posted a new version of cgminer, 3.12.0 which hopefully copes better with transient USB errors on these.
full member
Activity: 155
Merit: 100
January 29, 2014, 06:34:32 AM
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.
member
Activity: 79
Merit: 10
January 29, 2014, 01:17:21 AM
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.
hero member
Activity: 761
Merit: 500
Mine Silent, Mine Deep
January 29, 2014, 12:55:57 AM
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.
member
Activity: 79
Merit: 10
January 29, 2014, 12:15:33 AM
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?
sr. member
Activity: 446
Merit: 250
January 29, 2014, 12:12:02 AM
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.
hero member
Activity: 761
Merit: 500
Mine Silent, Mine Deep
January 29, 2014, 12:01:50 AM
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.


sr. member
Activity: 392
Merit: 250
January 28, 2014, 11:49:14 PM
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.


hero member
Activity: 991
Merit: 500
January 28, 2014, 10:39:02 PM
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?
Pages:
Jump to: