HashFast BabyJet users thread

[SolarSilver]

how do i check what firmware i currently have?  i just popped in the sd card but im not sure if it got updated.

I'm sure there must be an elegant solution (perhaps the minepeon interface has a field for it?) but I never use the rPi so I run cgiminer (3.12 something) direct from an i386 board.

Start it up, go to Display (d) and select Verbose (v)

Plug in your device and you'll see:

Code:

[2014-03-06 09:57:46] HFA 0: Sending OP_USB_INIT with GWQ protocol specified
[2014-03-06 09:57:49] HFB 0:      firmware_rev:    0.4
[2014-03-06 09:57:49] HFB 0:      hardware_rev:    1.1
[2014-03-06 09:57:49] HFB 0:      serial number:   0x00000000
[2014-03-06 09:57:49] HFB 0:      hash clockrate:  583 Mhz
[2014-03-06 09:57:49] HFB 0:      inflight_target: 760
[2014-03-06 09:57:49] HFB 0:      sequence_modulus: 2048

[xunknownx]

how do i check what firmware i currently have?  i just popped in the sd card but im not sure if it got updated.

I'm sure there must be an elegant solution (perhaps the minepeon interface has a field for it?) but I never use the rPi so I run cgiminer (3.12 something) direct from an i386 board.

Start it up, go to Display (d) and select Verbose (v)

Plug in your device and you'll see:

Code:

[2014-03-06 09:57:46] HFA 0: Sending OP_USB_INIT with GWQ protocol specified
[2014-03-06 09:57:49] HFB 0:      firmware_rev:    0.4
[2014-03-06 09:57:49] HFB 0:      hardware_rev:    1.1
[2014-03-06 09:57:49] HFB 0:      serial number:   0x00000000
[2014-03-06 09:57:49] HFB 0:      hash clockrate:  583 Mhz
[2014-03-06 09:57:49] HFB 0:      inflight_target: 760
[2014-03-06 09:57:49] HFB 0:      sequence_modulus: 2048

hmm... i SSHed via putty into my miner, entered (D) and turned on verbose (V) and i dont see what you see.. am i missing a step? 

on minepeon, its showing hashfast firmware as 6e66eb47

[minternj]

The firmware has helped my recently failing BJ. It had become more unstable over time, not sure if anyone else experienced that.

[SolarSilver]

hmm... i SSHed via putty into my miner, entered (D) and turned on verbose (V) and i dont see what you see.. am i missing a step? 

Did you plug in a new device after you set it to Verbose?

Make sure there is no second cgminer running in the background

[starsoccer9]

While I dont notice much difference from my unit, I have noticed that the fan speed percentage basically does nothing. Meaning my unit is running at about 85C and the fan speeds go between 3-7%. I tried manually making it go higher like to 60% and the temp did not even change a degree.

[xunknownx]

hmm... i SSHed via putty into my miner, entered (D) and turned on verbose (V) and i dont see what you see.. am i missing a step? 

Did you plug in a new device after you set it to Verbose?

Make sure there is no second cgminer running in the background

nope, its already mining so i just enable verbose.

[btchedge]

Anyone seen this? Board was not hashing well so we updated firmware and tried CG 4.0.1 and 3.11.0. New errors I had not seen yet. Please advise if you have any insight.

Code:

cgminer version 4.0.1 - Started: [2014-03-07 21:43:05]
--------------------------------------------------------------------------------------------------
 (5s):0.000 (avg):0.000h/s | A:0  R:0  HW:0  WU:0.0/m
 ST: 3  SS: 0  NB: 1  LW: 123  GF: 0  RF: 0
 Connected to stratum.mining.eligius.st diff 16 with stratum as user 
 Block: 6ca4a121...  Diff:3.81G  Started: [21:43:05]  Best share: 0
--------------------------------------------------------------------------------------------------
 [U]SB device management [P]ool management [S]ettings [D]isplay options [Q]uit
 0: HFB 0: 550MHz   0C  33% 1.11V  | ZOMBIE/ 0.000h/s | A:0 R:0 HW:0 WU:0.0/m
--------------------------------------------------------------------------------------------------
 [2014-03-07 21:44:18] Hotplug: Hashfast added HFB 0
 [2014-03-07 21:44:19] HFB 0 HFHash usb write err:(-7) LIBUSB_ERROR_TIMEOUT
 [2014-03-07 21:44:19] HFB 0 attempted reset got err:(0) LIBUSB_SUCCESS
 [2014-03-07 21:44:19] HFB 0: hfa_send_frame: USB Send error, ret 0 amount 0 vs. tx_length 64, retrying
 [2014-03-07 21:44:19] HFB 0 HFGetHeader usb read err:(-4) LIBUSB_ERROR_NO_DEVICE
 [2014-03-07 21:44:19] HFB 0: hfa_send_frame: recovered OK
 [2014-03-07 21:44:19] HFB 0 failure, disabling!
 [2014-03-07 21:44:24] HFA: Found old instance by op name 6c59a3e4 at device 0
 [2014-03-07 21:44:38] Hotplug: Hashfast added HFB 0
 [2014-03-07 21:44:39] HFB 0 HFHash usb write err:(-7) LIBUSB_ERROR_TIMEOUT
 [2014-03-07 21:44:39] HFB 0 HFGetHeader usb read err:(-4) LIBUSB_ERROR_NO_DEVICE
 [2014-03-07 21:44:39] HFB 0 attempted reset got err:(0) LIBUSB_SUCCESS
 [2014-03-07 21:44:39] HFB 0 failure, disabling!
 [2014-03-07 21:44:44] HFA: Found old instance by op name 6c59a3e4 at device 0
 [2014-03-07 21:46:09] HFA 6 HFClearRead usb read err:(-9) LIBUSB_ERROR_PIPE
 [2014-03-07 21:46:09] HFA 6 attempted reset got err:(-5) LIBUSB_ERROR_NOT_FOUND
 [2014-03-07 21:46:09] Hotplug: Hashfast added HFA 6
 [2014-03-07 21:46:15] HFA: Found old instance by op name 6c59a3e4 at device 0
 [2014-03-07 21:46:54] HFB 7 HFClearRead usb read err:(-9) LIBUSB_ERROR_PIPE
 [2014-03-07 21:46:54] HFB 7 attempted reset got err:(-5) LIBUSB_ERROR_NOT_FOUND
 [2014-03-07 21:46:54] Hotplug: Hashfast added HFB 7
 [2014-03-07 21:46:59] HFA: Found old instance by op name 6c59a3e4 at device 0
 [2014-03-07 21:47:13] Hotplug: Hashfast added HFB 0
 [2014-03-07 21:47:14] HFB 0 HFHash usb write err:(-7) LIBUSB_ERROR_TIMEOUT
 [2014-03-07 21:47:14] HFB 0 HFGetHeader usb read err:(-4) LIBUSB_ERROR_NO_DEVICE
 [2014-03-07 21:47:14] HFB 0 attempted reset got err:(0) LIBUSB_SUCCESS
 [2014-03-07 21:47:14] HFB 0 failure, disabling!
 [2014-03-07 21:47:19] HFA: Found old instance by op name 6c59a3e4 at device 0
 [2014-03-07 21:47:31] Hotplug: Hashfast added HFB 0
 [2014-03-07 21:47:32] HFB 0 HFHash usb write err:(-7) LIBUSB_ERROR_TIMEOUT
 [2014-03-07 21:47:32] HFB 0 HFGetHeader usb read err:(-4) LIBUSB_ERROR_NO_DEVICE
 [2014-03-07 21:47:32] HFB 0 attempted reset got err:(0) LIBUSB_SUCCESS
 [2014-03-07 21:47:32] HFB 0 failure, disabling!
 [2014-03-07 21:47:37] HFA: Found old instance by op name 6c59a3e4 at device 0

[btchedge]

After reboot now I am getting this...WTF?

Code:

 cgminer version 4.0.1 - Started: [2014-03-07 21:56:39]
--------------------------------------------------------------------------------------------------
 (5s):3.090G (avg):8.586Gh/s | A:16  R:0  HW:67  WU:112.5/m
 ST: 1  SS: 0  NB: 2  LW: 599  GF: 0  RF: 0
 Connected to stratum.mining.eligius.st diff 16 with stratum as user
 Block: 763843d6...  Diff:3.81G  Started: [21:56:46]  Best share: 28
--------------------------------------------------------------------------------------------------
 [U]SB device management [P]ool management [S]ettings [D]isplay options [Q]uit
 0: HFB 0: 550MHz  32C  33% 0.83V  | ZOMBIE/8.586Gh/s | A:16 R:0 HW:67 WU:112.5/m
--------------------------------------------------------------------------------------------------
 [2014-03-07 21:56:44] HFB 0 NOTICE: Hash Core Error: Still emitting hashes: die 0 core 0, count: 1300
 [2014-03-07 21:56:44] HFB 0 NOTICE: Hash Core Error: Still emitting hashes: die 0 core 0, count: 1400
 [2014-03-07 21:56:44] HFB 0 NOTICE: Hash Core Error: Still emitting hashes: die 0 core 0, count: 1500
 [2014-03-07 21:56:45] HFB 0 NOTICE: Hash Core Error: Still emitting hashes: die 0 core 0, count: 1600
 [2014-03-07 21:56:45] HFB 0 NOTICE: Hash Core Error: Squelching die 0 core 0
 [2014-03-07 21:56:45] HFB 0 NOTICE: Hash Core Error: Squelching die 0 core 0
 [2014-03-07 21:56:45] HFB 0 NOTICE: Hash Core Error: Squelching die 0 core 0
 [2014-03-07 21:56:45] HFB 0 NOTICE: Hash Core Error: Squelching die 0 core 0
 [2014-03-07 21:56:45] HFB 0 NOTICE: Hash Core Error: Still emitting hashes: die 0 core 0, count: 100
 [2014-03-07 21:56:45] HFB 0 NOTICE: Hash Core Error: Still emitting hashes: die 0 core 0, count: 200
 [2014-03-07 21:56:45] HFB 0 NOTICE: Hash Core Error: Still emitting hashes: die 0 core 0, count: 300
 [2014-03-07 21:56:45] HFB 0 NOTICE: Hash Core Error: Still emitting hashes: die 0 core 0, count: 400
 [2014-03-07 21:56:45] HFB 0 NOTICE: Hash Core Error: Still emitting hashes: die 0 core 0, count: 500
 [2014-03-07 21:56:45] HFB 0 NOTICE: Hash Core Error: Still emitting hashes: die 0 core 0, count: 600
 [2014-03-07 21:56:46] HFB 0 NOTICE: Hash Core Error: Still emitting hashes: die 0 core 0, count: 700
 [2014-03-07 21:56:46] HFB 0 NOTICE: Hash Core Error: Squelching die 0 core 0
 [2014-03-07 21:56:46] HFB 0 NOTICE: Hash Core Error: Still emitting hashes: die 0 core 0, count: 100
 [2014-03-07 21:56:46] HFB 0 NOTICE: Hash Core Error: Still emitting hashes: die 0 core 0, count: 200
 [2014-03-07 21:56:46] Stratum from pool 1 detected new block
 [2014-03-07 21:56:46] HFB 0 NOTICE: Hash Core Error: Still emitting hashes: die 0 core 0, count: 300
 [2014-03-07 21:56:46] HFB 0 NOTICE: Hash Core Error: Still emitting hashes: die 0 core 0, count: 400
 [2014-03-07 21:56:47] HFB 0 NOTICE: Hash Core Error: Still emitting hashes: die 0 core 0, count: 500
 [2014-03-07 21:56:47] HFB 0 HFHash usb write err:(-7) LIBUSB_ERROR_TIMEOUT
 [2014-03-07 21:56:47] HFB 0 attempted reset got err:(0) LIBUSB_SUCCESS
 [2014-03-07 21:56:47] HFB 0: hfa_send_frame: USB Send error, ret 0 amount 0 vs. tx_length 64, retrying
 [2014-03-07 21:56:47] HFB 0 HFGetHeader usb read err:(-4) LIBUSB_ERROR_NO_DEVICE
 [2014-03-07 21:56:47] HFB 0: hfa_send_frame: recovered OK
 [2014-03-07 21:56:47] HFB 0 failure, disabling!
 [2014-03-07 21:56:48] Stratum from pool 0 requested work restart
 [2014-03-07 21:56:50] HFA: Found old instance by op name 6c59a3e4 at device 0
 [2014-03-07 21:57:03] Hotplug: Hashfast added HFB 0
 [2014-03-07 21:57:04] HFB 0 HFHash usb write err:(-7) LIBUSB_ERROR_TIMEOUT
 [2014-03-07 21:57:04] HFB 0 HFGetHeader usb read err:(-4) LIBUSB_ERROR_NO_DEVICE
 [2014-03-07 21:57:04] HFB 0 attempted reset got err:(0) LIBUSB_SUCCESS
 [2014-03-07 21:57:04] HFB 0 failure, disabling!

[CurcO]

You need to try a different clock setting , these chips can be fuzzy at certain clock speeds even the stock, I would recommend you start at 600 then go up in 5 clicks at a time ( --hfa-hash-clock xxx)

After reboot now I am getting this...WTF?

Code:

 cgminer version 4.0.1 - Started: [2014-03-07 21:56:39]
--------------------------------------------------------------------------------------------------
 (5s):3.090G (avg):8.586Gh/s | A:16  R:0  HW:67  WU:112.5/m
 ST: 1  SS: 0  NB: 2  LW: 599  GF: 0  RF: 0
 Connected to stratum.mining.eligius.st diff 16 with stratum as user
 Block: 763843d6...  Diff:3.81G  Started: [21:56:46]  Best share: 28
--------------------------------------------------------------------------------------------------
 [U]SB device management [P]ool management [S]ettings [D]isplay options [Q]uit
 0: HFB 0: 550MHz  32C  33% 0.83V  | ZOMBIE/8.586Gh/s | A:16 R:0 HW:67 WU:112.5/m
--------------------------------------------------------------------------------------------------
 [2014-03-07 21:56:44] HFB 0 NOTICE: Hash Core Error: Still emitting hashes: die 0 core 0, count: 1300
 [2014-03-07 21:56:44] HFB 0 NOTICE: Hash Core Error: Still emitting hashes: die 0 core 0, count: 1400
 [2014-03-07 21:56:44] HFB 0 NOTICE: Hash Core Error: Still emitting hashes: die 0 core 0, count: 1500
 [2014-03-07 21:56:45] HFB 0 NOTICE: Hash Core Error: Still emitting hashes: die 0 core 0, count: 1600
 [2014-03-07 21:56:45] HFB 0 NOTICE: Hash Core Error: Squelching die 0 core 0
 [2014-03-07 21:56:45] HFB 0 NOTICE: Hash Core Error: Squelching die 0 core 0
 [2014-03-07 21:56:45] HFB 0 NOTICE: Hash Core Error: Squelching die 0 core 0
 [2014-03-07 21:56:45] HFB 0 NOTICE: Hash Core Error: Squelching die 0 core 0
 [2014-03-07 21:56:45] HFB 0 NOTICE: Hash Core Error: Still emitting hashes: die 0 core 0, count: 100
 [2014-03-07 21:56:45] HFB 0 NOTICE: Hash Core Error: Still emitting hashes: die 0 core 0, count: 200
 [2014-03-07 21:56:45] HFB 0 NOTICE: Hash Core Error: Still emitting hashes: die 0 core 0, count: 300
 [2014-03-07 21:56:45] HFB 0 NOTICE: Hash Core Error: Still emitting hashes: die 0 core 0, count: 400
 [2014-03-07 21:56:45] HFB 0 NOTICE: Hash Core Error: Still emitting hashes: die 0 core 0, count: 500
 [2014-03-07 21:56:45] HFB 0 NOTICE: Hash Core Error: Still emitting hashes: die 0 core 0, count: 600
 [2014-03-07 21:56:46] HFB 0 NOTICE: Hash Core Error: Still emitting hashes: die 0 core 0, count: 700
 [2014-03-07 21:56:46] HFB 0 NOTICE: Hash Core Error: Squelching die 0 core 0
 [2014-03-07 21:56:46] HFB 0 NOTICE: Hash Core Error: Still emitting hashes: die 0 core 0, count: 100
 [2014-03-07 21:56:46] HFB 0 NOTICE: Hash Core Error: Still emitting hashes: die 0 core 0, count: 200
 [2014-03-07 21:56:46] Stratum from pool 1 detected new block
 [2014-03-07 21:56:46] HFB 0 NOTICE: Hash Core Error: Still emitting hashes: die 0 core 0, count: 300
 [2014-03-07 21:56:46] HFB 0 NOTICE: Hash Core Error: Still emitting hashes: die 0 core 0, count: 400
 [2014-03-07 21:56:47] HFB 0 NOTICE: Hash Core Error: Still emitting hashes: die 0 core 0, count: 500
 [2014-03-07 21:56:47] HFB 0 HFHash usb write err:(-7) LIBUSB_ERROR_TIMEOUT
 [2014-03-07 21:56:47] HFB 0 attempted reset got err:(0) LIBUSB_SUCCESS
 [2014-03-07 21:56:47] HFB 0: hfa_send_frame: USB Send error, ret 0 amount 0 vs. tx_length 64, retrying
 [2014-03-07 21:56:47] HFB 0 HFGetHeader usb read err:(-4) LIBUSB_ERROR_NO_DEVICE
 [2014-03-07 21:56:47] HFB 0: hfa_send_frame: recovered OK
 [2014-03-07 21:56:47] HFB 0 failure, disabling!
 [2014-03-07 21:56:48] Stratum from pool 0 requested work restart
 [2014-03-07 21:56:50] HFA: Found old instance by op name 6c59a3e4 at device 0
 [2014-03-07 21:57:03] Hotplug: Hashfast added HFB 0
 [2014-03-07 21:57:04] HFB 0 HFHash usb write err:(-7) LIBUSB_ERROR_TIMEOUT
 [2014-03-07 21:57:04] HFB 0 HFGetHeader usb read err:(-4) LIBUSB_ERROR_NO_DEVICE
 [2014-03-07 21:57:04] HFB 0 attempted reset got err:(0) LIBUSB_SUCCESS
 [2014-03-07 21:57:04] HFB 0 failure, disabling!

[jddebug]

After reboot now I am getting this...WTF?

Code:

 cgminer version 4.0.1 - Started: [2014-03-07 21:56:39]
--------------------------------------------------------------------------------------------------
 (5s):3.090G (avg):8.586Gh/s | A:16  R:0  HW:67  WU:112.5/m
 ST: 1  SS: 0  NB: 2  LW: 599  GF: 0  RF: 0
 Connected to stratum.mining.eligius.st diff 16 with stratum as user
 Block: 763843d6...  Diff:3.81G  Started: [21:56:46]  Best share: 28
--------------------------------------------------------------------------------------------------
 [U]SB device management [P]ool management [S]ettings [D]isplay options [Q]uit
 0: HFB 0: 550MHz  32C  33% 0.83V  | ZOMBIE/8.586Gh/s | A:16 R:0 HW:67 WU:112.5/m
--------------------------------------------------------------------------------------------------
 [2014-03-07 21:56:44] HFB 0 NOTICE: Hash Core Error: Still emitting hashes: die 0 core 0, count: 1300
 [2014-03-07 21:56:44] HFB 0 NOTICE: Hash Core Error: Still emitting hashes: die 0 core 0, count: 1400
 [2014-03-07 21:56:44] HFB 0 NOTICE: Hash Core Error: Still emitting hashes: die 0 core 0, count: 1500
 [2014-03-07 21:56:45] HFB 0 NOTICE: Hash Core Error: Still emitting hashes: die 0 core 0, count: 1600
 [2014-03-07 21:56:45] HFB 0 NOTICE: Hash Core Error: Squelching die 0 core 0
 [2014-03-07 21:56:45] HFB 0 NOTICE: Hash Core Error: Squelching die 0 core 0
 [2014-03-07 21:56:45] HFB 0 NOTICE: Hash Core Error: Squelching die 0 core 0
 [2014-03-07 21:56:45] HFB 0 NOTICE: Hash Core Error: Squelching die 0 core 0
 [2014-03-07 21:56:45] HFB 0 NOTICE: Hash Core Error: Still emitting hashes: die 0 core 0, count: 100
 [2014-03-07 21:56:45] HFB 0 NOTICE: Hash Core Error: Still emitting hashes: die 0 core 0, count: 200
 [2014-03-07 21:56:45] HFB 0 NOTICE: Hash Core Error: Still emitting hashes: die 0 core 0, count: 300
 [2014-03-07 21:56:45] HFB 0 NOTICE: Hash Core Error: Still emitting hashes: die 0 core 0, count: 400
 [2014-03-07 21:56:45] HFB 0 NOTICE: Hash Core Error: Still emitting hashes: die 0 core 0, count: 500
 [2014-03-07 21:56:45] HFB 0 NOTICE: Hash Core Error: Still emitting hashes: die 0 core 0, count: 600
 [2014-03-07 21:56:46] HFB 0 NOTICE: Hash Core Error: Still emitting hashes: die 0 core 0, count: 700
 [2014-03-07 21:56:46] HFB 0 NOTICE: Hash Core Error: Squelching die 0 core 0
 [2014-03-07 21:56:46] HFB 0 NOTICE: Hash Core Error: Still emitting hashes: die 0 core 0, count: 100
 [2014-03-07 21:56:46] HFB 0 NOTICE: Hash Core Error: Still emitting hashes: die 0 core 0, count: 200
 [2014-03-07 21:56:46] Stratum from pool 1 detected new block
 [2014-03-07 21:56:46] HFB 0 NOTICE: Hash Core Error: Still emitting hashes: die 0 core 0, count: 300
 [2014-03-07 21:56:46] HFB 0 NOTICE: Hash Core Error: Still emitting hashes: die 0 core 0, count: 400
 [2014-03-07 21:56:47] HFB 0 NOTICE: Hash Core Error: Still emitting hashes: die 0 core 0, count: 500
 [2014-03-07 21:56:47] HFB 0 HFHash usb write err:(-7) LIBUSB_ERROR_TIMEOUT
 [2014-03-07 21:56:47] HFB 0 attempted reset got err:(0) LIBUSB_SUCCESS
 [2014-03-07 21:56:47] HFB 0: hfa_send_frame: USB Send error, ret 0 amount 0 vs. tx_length 64, retrying
 [2014-03-07 21:56:47] HFB 0 HFGetHeader usb read err:(-4) LIBUSB_ERROR_NO_DEVICE
 [2014-03-07 21:56:47] HFB 0: hfa_send_frame: recovered OK
 [2014-03-07 21:56:47] HFB 0 failure, disabling!
 [2014-03-07 21:56:48] Stratum from pool 0 requested work restart
 [2014-03-07 21:56:50] HFA: Found old instance by op name 6c59a3e4 at device 0
 [2014-03-07 21:57:03] Hotplug: Hashfast added HFB 0
 [2014-03-07 21:57:04] HFB 0 HFHash usb write err:(-7) LIBUSB_ERROR_TIMEOUT
 [2014-03-07 21:57:04] HFB 0 HFGetHeader usb read err:(-4) LIBUSB_ERROR_NO_DEVICE
 [2014-03-07 21:57:04] HFB 0 attempted reset got err:(0) LIBUSB_SUCCESS
 [2014-03-07 21:57:04] HFB 0 failure, disabling!

The squelching is the firmware turning off cores that are not working correctly. This makes the unit far more stable on the USB. Before, you didn't know it, the bad cores were causing problems that effected the good ones and hurt performance.

If you let it sit there and go through the process it should work fine.

[-ck]

New version of cgminer - 4.1.0 - with dramatic stability and performance improvements for these devices, along with new features. This version will work with all older firmwares as well:

https://bitcointalk.org/index.php?topic=28402.msg5581480#msg5581480

The cause of the regression in performance was found and this should outperform any previous cgminer releases.

[ninjarobot]

New version of cgminer - 4.1.0 - with dramatic stability and performance improvements for these devices, along with new features. This version will work with all older firmwares as well:

https://bitcointalk.org/index.php?topic=28402.msg5581480#msg5581480

The cause of the regression in performance was found and this should outperform any previous cgminer releases.

Thank you!

[HashFast_CL]

The firmware has helped my recently failing BJ. It had become more unstable over time, not sure if anyone else experienced that.

The new firmware made my hardware more stable and a little faster.  There's room for more improvement, which upcoming firmware updates will provide.

[raskul]

The firmware has helped my recently failing BJ. It had become more unstable over time, not sure if anyone else experienced that.

The new firmware made my hardware more stable and a little faster.  There's room for more improvement, which upcoming firmware updates will provide.

may I ask, will these firmware upgrades be already built in to say... batch 3 and 4 please? I don't want to have to pfaff about with the rig when it arrives as i'll be on my holidays and a relative will be powering it up for me (to be fair, that relative did a good job setting up my getwork cubes).

[HashFast_CL]

The firmware has helped my recently failing BJ. It had become more unstable over time, not sure if anyone else experienced that.

The new firmware made my hardware more stable and a little faster.  There's room for more improvement, which upcoming firmware updates will provide.

may I ask, will these firmware upgrades be already built in to say... batch 3 and 4 please? I don't want to have to pfaff about with the rig when it arrives as i'll be on my holidays and a relative will be powering it up for me (to be fair, that relative did a good job setting up my getwork cubes).

Shipping with the freshest, newest firmware is risky because it often has bugs that don't show up until extensive testing is done in the wild.  It's better to use a known good version, especially if you need a stable system easily babysat by relatives.

OTOH, faffing about with hardware is the perfect way to get the relatives more interested in mining!

[raskul]

The firmware has helped my recently failing BJ. It had become more unstable over time, not sure if anyone else experienced that.

The new firmware made my hardware more stable and a little faster.  There's room for more improvement, which upcoming firmware updates will provide.

may I ask, will these firmware upgrades be already built in to say... batch 3 and 4 please? I don't want to have to pfaff about with the rig when it arrives as i'll be on my holidays and a relative will be powering it up for me (to be fair, that relative did a good job setting up my getwork cubes).

Shipping with the freshest, newest firmware is risky because it often has bugs that don't show up until extensive testing is done in the wild.  It's better to use a known good version, especially if you need a stable system easily babysat by relatives.

OTOH, faffing about with hardware is the perfect way to get the relatives more interested in mining!

in that case, i'll have to make do with what the babyjet comes with until I get back from holiday, unless it ships early and I can do the work before I go.

[HashFast_CL]

The firmware has helped my recently failing BJ. It had become more unstable over time, not sure if anyone else experienced that.

The new firmware made my hardware more stable and a little faster.  There's room for more improvement, which upcoming firmware updates will provide.

may I ask, will these firmware upgrades be already built in to say... batch 3 and 4 please? I don't want to have to pfaff about with the rig when it arrives as i'll be on my holidays and a relative will be powering it up for me (to be fair, that relative did a good job setting up my getwork cubes).

Shipping with the freshest, newest firmware is risky because it often has bugs that don't show up until extensive testing is done in the wild.  It's better to use a known good version, especially if you need a stable system easily babysat by relatives.

OTOH, faffing about with hardware is the perfect way to get the relatives more interested in mining!

in that case, i'll have to make do with what the babyjet comes with until I get back from holiday, unless it ships early and I can do the work before I go.

Baby Jets are shipping with stable firmware; the most important improvements to prevent crashes have largely been made.  We're working on getting our customized Minepeon to auto-magically install firmware updates, so the issue may soon be moot.

[raskul]

The firmware has helped my recently failing BJ. It had become more unstable over time, not sure if anyone else experienced that.

The new firmware made my hardware more stable and a little faster.  There's room for more improvement, which upcoming firmware updates will provide.

may I ask, will these firmware upgrades be already built in to say... batch 3 and 4 please? I don't want to have to pfaff about with the rig when it arrives as i'll be on my holidays and a relative will be powering it up for me (to be fair, that relative did a good job setting up my getwork cubes).

Shipping with the freshest, newest firmware is risky because it often has bugs that don't show up until extensive testing is done in the wild.  It's better to use a known good version, especially if you need a stable system easily babysat by relatives.

OTOH, faffing about with hardware is the perfect way to get the relatives more interested in mining!

in that case, i'll have to make do with what the babyjet comes with until I get back from holiday, unless it ships early and I can do the work before I go.

Baby Jets are shipping with stable firmware; the most important improvements to prevent crashes have largely been made.  We're working on getting our customized Minepeon to auto-magically install firmware updates, so the issue may soon be moot.

cool, thanks.

[starsoccer9]

The firmware has helped my recently failing BJ. It had become more unstable over time, not sure if anyone else experienced that.

The new firmware made my hardware more stable and a little faster.  There's room for more improvement, which upcoming firmware updates will provide.

may I ask, will these firmware upgrades be already built in to say... batch 3 and 4 please? I don't want to have to pfaff about with the rig when it arrives as i'll be on my holidays and a relative will be powering it up for me (to be fair, that relative did a good job setting up my getwork cubes).

Shipping with the freshest, newest firmware is risky because it often has bugs that don't show up until extensive testing is done in the wild.  It's better to use a known good version, especially if you need a stable system easily babysat by relatives.

OTOH, faffing about with hardware is the perfect way to get the relatives more interested in mining!

in that case, i'll have to make do with what the babyjet comes with until I get back from holiday, unless it ships early and I can do the work before I go.

Baby Jets are shipping with stable firmware; the most important improvements to prevent crashes have largely been made.  We're working on getting our customized Minepeon to auto-magically install firmware updates, so the issue may soon be moot.

Any status on MPP that are now over a month late?

[cedivad]

Any status on MPP that are now over a month late?

However, as some customers were starting to try to point out, this wasn't going to be the case; every evidence (or lack thereof) was pointing towards the worst: the first miners would have been shipped just before the end of December contractual deadline, and the MPP was a bad marketing joke, given the lack of a shipping timeframe.

http://hashfast.org/