Bitcoin Forum

Bitcoin => Hardware => Topic started by: FiloSottile on August 22, 2013, 06:06:25 PM



Title: Jalapeno pulling < 5 Gh/s, possible reasons?
Post by: FiloSottile on August 22, 2013, 06:06:25 PM
Just started a new BFL Jal unit, connected to a RaspberryPi with MinePeon.
I removed the box, flipped the fan and the temp is a good 35C.

However the hashrate never got to 5 Gh/s.

What's a list of possible reasons I should look into?


Title: Re: Jalapeno pulling < 5 Gh/s, possible reasons?
Post by: FiloSottile on August 22, 2013, 06:14:32 PM
Ah, I have a quite high HW Error rate: 1514 [7.24%]


Title: Re: Jalapeno pulling < 5 Gh/s, possible reasons?
Post by: bcp19 on August 22, 2013, 06:48:15 PM
Just started a new BFL Jal unit, connected to a RaspberryPi with MinePeon.
I removed the box, flipped the fan and the temp is a good 35C.

However the hashrate never got to 5 Gh/s.

What's a list of possible reasons I should look into?
Did it get above 4.5GH?


Title: Re: Jalapeno pulling < 5 Gh/s, possible reasons?
Post by: FiloSottile on August 22, 2013, 07:50:46 PM
Just started a new BFL Jal unit, connected to a RaspberryPi with MinePeon.
I removed the box, flipped the fan and the temp is a good 35C.

However the hashrate never got to 5 Gh/s.

What's a list of possible reasons I should look into?
Did it get above 4.5GH?
Yeah, pulling 4.864 GH/s since unboxing.


Title: Re: Jalapeno pulling < 5 Gh/s, possible reasons?
Post by: joris on August 22, 2013, 07:53:03 PM
Then it meets Jalapeno specs: 4,5 Gh +/- 10%


Title: Re: Jalapeno pulling < 5 Gh/s, possible reasons?
Post by: derr777 on August 22, 2013, 07:57:54 PM
put it in the freezer for about 10-15 mins before plugging it in.. it initializes engines when plugged in (and never again unless it loses power or usb communications request a reset.) only.  

There is a risk here of condensation, but once you get it cold and plug it in and get more engines pretty much until you unplug it again, the risk is arguably worth it.  I use a bag to prevent condensation.

Let us know how high it goes after being that cold.. the firmware basically is very vigorous with engine initialization.. i've found you can generally eek out 2-4 borderline engines by doing this, and each of them will add around 250gh each..


Title: Re: Jalapeno pulling < 5 Gh/s, possible reasons?
Post by: ElitePork on August 23, 2013, 05:51:22 AM
How many engines are running? You can check using cgminer --api-listen and java API stats.
Post the results here and i can see from there....


Title: Re: Jalapeno pulling < 5 Gh/s, possible reasons?
Post by: derr777 on August 23, 2013, 09:39:50 AM
How many engines are running? You can check using cgminer --api-listen and java API stats.
Post the results here and i can see from there....

Yes, or install cgwatcher and look at its info dialog, as it polls the engines as well..


Title: Re: Jalapeno pulling < 5 Gh/s, possible reasons?
Post by: Red_Wolf_2 on August 23, 2013, 01:14:45 PM
Or plug it in, fire up a terminal program and connect to its COM port, then issue the command ZCX. That should give you output similar to the following:
DEVICE: BitFORCE SC
FIRMWARE: 1.0.0
MINIG SPEED: 7.61 GH/s
PROCESSOR 3: 15 engines @ 259 MHz
PROCESSOR 7: 14 engines @ 271 MHz
ENGINES: 29
FREQUENCY: 266 MHz
XLINK MODE: MASTER
CRITICAL TEMPERATURE: 0
XLINK PRESENT: NO
OK


Title: Re: Jalapeno pulling < 5 Gh/s, possible reasons?
Post by: rammy2k2 on August 23, 2013, 01:52:35 PM
do NOT put it in the fridge .. u will ruin it ... 4.8 GH is just normal


Title: Re: Jalapeno pulling < 5 Gh/s, possible reasons?
Post by: volosator on August 23, 2013, 02:55:22 PM
Firmware is not 1.2.5 or 1.2.6
There is a topic on the forum with flashing instructions.


Title: Re: Jalapeno pulling < 5 Gh/s, possible reasons?
Post by: Red_Wolf_2 on August 23, 2013, 03:25:50 PM
Firmware is not 1.2.5 or 1.2.6
There is a topic on the forum with flashing instructions.

Before running a flash on the unit, please grab the stats using the ZCX command as listed above. If a lot of the engines are disabled then reflashing might not get you a huge performance increase. At the very least we'll be able to tell whether its deliberately limited or not :-)