Has anyone done the math to figure out if the 2-for-1 offer is better with a Neptune or a Titan?  I'm worried that my house can't (easily) meet the power requirements for 4 neptunes (2 ordered + 2 free).  Can the Titan provide a similar ROI with less power requirement?

Upgrade? Are they shipping upgrade modules?  All I got was an email asking me to exchange my upgrade option for an Evo board in June.

Mine isn't stable above 575mhz.  If I push it any higher at all I get constant USB disconnects and the hash rate plummets.  Have you installed any extra cooling that is helping push the clocks higher?

I upgraded the firmware and now my BabyJet with cgminer 4.0.1 is mining 50-100GH/s SLOWER than it was previously.  Is anyone else having problems with the miner slowing down?  At fully stock settings, I get about 50GH/s slower, when I try to overclock I get a burst of great speed and then cgminer will freeze for a minute, try to downclock, and get stuck until the hashfast startscreen app restarts cgminer.

user: minepeon
pass: peon

Regarding this file:

http://setup.hashfast.com/files/hashfast-20140224-0-multiarch.tar.gz

Since that has a RPI version on it, can I just SSH into my RPI, wget the file, and run it?  There's a warning about writing to a different SD card, but that's for the auto-upgrade image, which I don't need if I just run the upgrade from the above archive, right?

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.

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.

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.

I don't know how to get a message to ckolivas, but I'm testing the current master branch of cgminer and one feature that was added is fan speed control (OP code 143).  However, I keep getting the error that OP_CODE 143 is unhandled.

Is it possible that I have an older revision of the board/firmware something that doesn't support controlling the fan speed using that op code?

I compiled 3.12 directly from ckolivas's github. That seems to run pretty well. There is a weird oddity when it starts up sometimes it gets a USB error, but once I get it going it's pretty solid and seems to get a better hash rate than the hf3 version.  Since the unpatched version seems to run pretty good, maybe the reliability issue has to do with your (HashFast's) patch.

I woke up this morning to by BJ fan turning off an on.  Last night I got the 3.12.0hf3 update and since then the miner mines for about an hour and then restarts.  It's not a full RPI reboot, but cgminer crashes/quits then restarts.  The cgminer restarts seem to be about every 75 minutes or so. I'm running stock clocks.

Since the automatic update I'm only getting about 350-370GH/s.

I restored my minepeon settings and it completely corrupted my miner-start.sh file. Clicking "default" in settings doesn't replace it. Can someone post the hashfast firmare miner-start.sh file?

I haven't been able to get mine to clock over 580.  Anything above that results in either not starting or the USB device disconnecting every few minutes.  I guess some people just lucked out with better chips.

I'm also getting periodic kernel panics, which is not good.

cgminer 3.11, compiled from git, shows a hash rate that's almost exactly 2x what eligius shows.  For example, my average hash rate according to cgminer is 830 GH/s, but eligius reports around 415 GH/s.

I noticed that ckolivas has been making a lot of changes to the cgminer git repo with hashfast changes.  I've cloned the git repo on my rpi and I'm going to compile a new version that has the latest changes.

Cgminer is showing me 422GH/s at stock speeds. Eligius shows < 400GH/s.

Where do you go to adjust the clock speed? I haven't been able to figure out if it's a cgminer option or somewhere else in the firmware.

How can you change the clock rate on the miner?

How do you adjust the clock rate? I had a peek through the cgminer source and the firmware but I couldn't figure out how to change the clock rate.

If you are having issues with the beta firmware (0.98.1) with the last two dies not turning on, the solution is to heat the chip up to at least 60C.  Once you get up into the 60s, the last two dies will turn on.  Several people have confirmed this.  I turn off the heatsink fans, block the airflow from the front fans until the heat gets up to 60+, then I allow the front fans to run while leaving the heatsink fans turned off.  If temps drop back below 60C, the dies will turn off.