HashFast BabyJet users thread

[CurcO]

Can we get some reviews here on the new firmware and cgminer?

I have 3.12.0 running stably and hashing 425-435 at 600 clock speed.

Any reason to upgrade?

So far, it seems like maybe if it ain't broke, don't fix it.

same here: cgminer 3.12.0 ,  boards rev 1.1 , original firmware .   clock 550 ,  400 gh/s ... stable

I'm on the new FW for the last day and have no issues with it, it also is better at reducing the the HW error when you OC

After 12 hr run @ 687 see the error count  before it would be almost 50/50 with accepted so its behaves better now.
 HFA 2: 84C/.79V 85C/.79V 77C/.79V 76C/.79V 512.6G/505.1Gh/s | A:1811812 R:2816 HW:423 WU:11853.1/m

[1714894725]

1714894725

[spectre2112]

Me got no pi, no 0.4, no 4.0.1 that sees my BJ

 

Then you in serious poo

Actually, my BabyJet is hashing about 400 GH/s when overclocked between 600 MHz and 612 MHz. It would probably be more, but it keeps disconnecting every 10 - 20 minutes. Fortunately, the hotplug feature in cgminer 4.0.0 finds it again within seconds.

I've Emailed HashFast a couple of times about the Pi. My latest Email was about simply sending me a firmware loader.

All of this has given me a chance to brush-up on my *nix skills. I haven't messed with this stuff in 20+ years... It's actually been kinda fun. Twenty years ago, there was no such thing as github...

Just a suggestion since you have the programming skills - why not try one of the programs to emulate the RPi on a desktop while you wait for Hashfast to never get back to you?

This one seems promising: http://xecdesign.com/qemu-emulating-raspberry-pi-the-easy-way/

[-ck]

Indeed if you have something stable and hashing at a good rate, there is no need to upgrade, using the - if it ain't broke - principle. However if you have one of those devices that keeps firing the watchdog and resetting and shutting down and restarting and cores dropping off and unable to keep it running, then by all means an upgrade is worthwhile.

Meanwhile one thing I've discovered is that one of my devices has slowly worked its way down to a lower clock speed but ended up with the same effective hashrate. This means the power usage is lower but the hashrate is the same. I used to have it overclocked to 615 but it's down to stock speed at 550 with the same hashrate. As always, overclocking is not just a matter of the higher the clockspeed the better.

[Daminqn]

hi, after doing some tests my BJ is going well
would like to make a couple of questions:

1 - with 600mhz cpu clock to get 450gh / s stable, with temperatures of 80 ° C, less than 1% error, someone has proven more stable mhz system?

2 - The fan noise is really high, probe disconnecting one and it turns out that actually make noise are the cooling radiator, the other 3 are silent, no way to lower the speed of the two fans or your I change default by less noisy? (my BJ's in my living room, it's really annoying)....

3 - 24h in btcguild, my gain was 0.05 BTC, is right? is little? Recommend me some other pool? (According to a calculator difficulty should win daily 0.07)

thanks for reading until here

[jelin1984]

My Jupiter hashing at 740 gh

[CryptKeeper]

My Jupiter hashing at 740 gh

Nice, but off topic!

[DoogieHouser]

Can we get some reviews here on the new firmware and cgminer?

I have 3.12.0 running stably and hashing 425-435 at 600 clock speed.

Any reason to upgrade?

So far, it seems like maybe if it ain't broke, don't fix it.

Original firmware, HW 1.1, Flaky Pi, Ubuntu 12.04 LTS, cgminer 4.0.0

Hashes for 10 - 20 minutes, disappears, hotplug finds it & starts hashing again.

Clock speed steadily drops from 612 to below 550 over a period of 14 hours. Stays at 600 the longest.

Hashrate varies from 360 GH/s to 400 GH/s (poolside) as  the clock speed changes.

Actually, my BabyJet is hashing about 400 GH/s when overclocked between 600 MHz and 612 MHz. It would probably be more, but it keeps disconnecting every 10 - 20 minutes. Fortunately, the hotplug feature in cgminer 4.0.0 finds it again within seconds.

I've Emailed HashFast a couple of times about the Pi. My latest Email was about simply sending me a firmware loader.

All of this has given me a chance to brush-up on my *nix skills. I haven't messed with this stuff in 20+ years... It's actually been kinda fun. Twenty years ago, there was no such thing as github...

Just a suggestion since you have the programming skills - why not try one of the programs to emulate the RPi on a desktop while you wait for Hashfast to never get back to you?

This one seems promising: http://xecdesign.com/qemu-emulating-raspberry-pi-the-easy-way/

Hmm... It does look interesting. What jumps out at me is the "Arch Linux requires a few tweaks to work. These will not be explored in this article."

Well, I've got nothing to lose by trying it, and might get my BabyJet running like it was for the first ten days...

Thanks!  

[DoogieHouser]

Question: Is everybody's BabyJet showing up as HFA?

Mine is showing up as HFB, which I thought meant it was a Sierra...

Code:

--------------------------------------------------------------------------------------------------
 [U]SB device management [P]ool management [S]ettings [D]isplay options [Q]uit
 005: HFB 5: 604MHz  80C  33% 0.79V  | 835.8G/903.3Gh/s | A: 20352 R:  0 HW:  83 WU:12563.0/m
--------------------------------------------------------------------------------------------------

I think maybe it's time to Email HashFast, again...

[-ck]

Question: Is everybody's BabyJet showing up as HFA?

Mine is showing up as HFB, which I thought meant it was a Sierra...

Code:

--------------------------------------------------------------------------------------------------
 [U]SB device management [P]ool management [S]ettings [D]isplay options [Q]uit
 005: HFB 5: 604MHz  80C  33% 0.79V  | 835.8G/903.3Gh/s | A: 20352 R:  0 HW:  83 WU:12563.0/m
--------------------------------------------------------------------------------------------------

I think maybe it's time to Email HashFast, again...

No that's my doing. HFB is babyjet. HFS is sierra. HFA is indeterminate (like a Blow Job upgrade).

[DoogieHouser]

Question: Is everybody's BabyJet showing up as HFA?

Mine is showing up as HFB, which I thought meant it was a Sierra...

Code:

--------------------------------------------------------------------------------------------------
 [U]SB device management [P]ool management [S]ettings [D]isplay options [Q]uit
 005: HFB 5: 604MHz  80C  33% 0.79V  | 835.8G/903.3Gh/s | A: 20352 R:  0 HW:  83 WU:12563.0/m
--------------------------------------------------------------------------------------------------

I think maybe it's time to Email HashFast, again...

No that's my doing. HFB is babyjet. HFS is sierra. HFA is indeterminate (like a Blow Job upgrade).

LOL! Okay, thanks, CK.

[tacotime]

So, has anyone hardmodded the voltage on these yet?  Any idea where to start?

[SolarSilver]

2 - The fan noise is really high, probe disconnecting one and it turns out that actually make noise are the cooling radiator, the other 3 are silent, no way to lower the speed of the two fans or your I change default by less noisy? (my BJ's in my living room, it's really annoying)....

There is not much of an option, to evacuate the heat, you'll need some kind of air flow. Put the machines somewhere else....

3 - 24h in btcguild, my gain was 0.05 BTC, is right? is little? Recommend me some other pool? (According to a calculator difficulty should win daily 0.07)

Over the last 24h I got 0.063/BBJet on BTCGuild which is about what I'd expect with variance (luck) and such

[NiteShdw]

Can someone post the steps to download and install the latest HashFast firmware?  My BabyJet won't clock above 570 and I'm hoping the newest firmware will help with that.

[NiteShdw]

ckolivas: cgminer 4.0.1 fails without the new firmware with the OP_NAME error code. It appears in the code that there is supposed to be a mechanism to fall back if the OP_NAME isn't supported, but that doesn't seem to get called or work.

[-ck]

ckolivas: cgminer 4.0.1 fails without the new firmware with the OP_NAME error code. It appears in the code that there is supposed to be a mechanism to fall back if the OP_NAME isn't supported, but that doesn't seem to get called or work.

Right, it's meant to be complementary to the new firmware... but it is still supposed to work without it. Are you running it via a pc plugged into it and it never starts the device at all with 0.2 firmware?

[NiteShdw]

Right, it's meant to be complementary to the new firmware... but it is still supposed to work without it. Are you running it via a pc plugged into it and it never starts the device at all with 0.2 firmware?

I'm running on the RPI. Everything works with 4.0.0, compiled from Git.  When I run 4.0.1 is just shows "Failed to receive OP_NAME response" over and over again.

[CurcO]

So, has anyone hardmodded the voltage on these yet?  Any idea where to start?

Same question I have , how to hardware mod the VRM so an over-volt will get us closer to  900 mhz or more.

[Morblias]

I was trying to get this working on a ubuntu computer, but keep getting

Code:

Hashfast detect (3:3) failed to initialise (incorrect device?)

Am I missing something here? This is how I installed it:

Code:

sudo apt-get install build-essential autoconf automake libtool libcurl3-dev libudev-dev git
git clone git://github.com/ckolivas/cgminer.git
cd cgminer/
sudo ./autogen.sh
sudo ./configure --enable-hashfast
sudo make
sudo make install

Edit: nevermind, I am an idiot. Was getting permission denied had to run cgminer as sudo. Now I am getting

Code:

HFA: Failed to receive OP_NAME response

over and over. Any ideas how to fix? (cgminer version 4.0.1)

Edit: Went to 4.0.0 and it works like a charm.

How do I see the temps, difficulty, connected pool, and all of that other stuff that usually shows on top of cgminer? in ubuntu right now it only shows the speeds, accepts, and rejects at the bottom and not the other info that usually shows up on top.

[-ck]

Code:

HFA: Failed to receive OP_NAME response

over and over. Any ideas how to fix? (cgminer version 4.0.1)

cgminer 4.0.1 basically needs new firmware flashed as 0.2 won't work with it.

[DoogieHouser]

I was trying to get this working on a ubuntu computer, but keep getting

Code:

Hashfast detect (3:3) failed to initialise (incorrect device?)

Am I missing something here? This is how I installed it:

Code:

sudo apt-get install build-essential autoconf automake libtool libcurl3-dev libudev-dev git
git clone git://github.com/ckolivas/cgminer.git
cd cgminer/
sudo ./autogen.sh
sudo ./configure --enable-hashfast
sudo make
sudo make install

Edit: nevermind, I am an idiot. Was getting permission denied had to run cgminer as sudo. Now I am getting

Code:

HFA: Failed to receive OP_NAME response

over and over. Any ideas how to fix? (cgminer version 4.0.1)

Edit: Went to 4.0.0 and it works like a charm.

How do I see the temps, difficulty, connected pool, and all of that other stuff that usually shows on top of cgminer? in ubuntu right now it only shows the speeds, accepts, and rejects at the bottom and not the other info that usually shows up on top.

I have the same issues with 4.0.1.

As for the display, you need to include the curses library that is listed under OPTIONAL in the README file (at compile time).

HTH