I need to get rid of 10 or so Chilis, I'm asking 3.5 BTC per chili which includes UPS Ground Shipping.
If you'd like a different type of shipping it will be extra.
PM if interested (I don't want to hijack this thread)
Topic: The Chili – 30+GH/s BFL based Bitcoin Miner Assembly - page 57. (Read 137978 times)
Got 1 board running at 37+ GH/s with 3.3% HW and another one 32 GH/s with 5.7% HW. The good one prob pushable to do more GH/s with better cooling.
If your Chili took a long time to boot, try bring it to a cold room and turn it on.
If your Chili took a long time to boot, try bring it to a cold room and turn it on.
Alright, looking forward to those firmware updates then. 
Make one that increases the hashrate by 10x.
Make one that increases the hashrate by 10x.
I am getting 30.71 GH at the pool hash rate
6.8% HW+rejects total
I do have one that rides the little short bus to school - 24GH, every family has one right?
This is still a better average than stock BFL if you count out the error rate
6.8% HW+rejects total
I do have one that rides the little short bus to school - 24GH, every family has one right?
This is still a better average than stock BFL if you count out the error rate
Also, my HW error rates on the Chilis are 5-10%, is that normal? My BFL miner has 0.77% HW error rate by comparison. I'm hoping it will be partially made more stable in a future firmware update.
Yes, in an effort to extract as much hash rate as possible, we have enabled some cores/engines that are (as it turns out) somewhat marginal. It is planned to have a future firmware release that will improve this. I have only run 3 Chilis for any length of time and 2 of them have much lower error rates than the other one. It is somewhat luck of the draw.
Also, my HW error rates on the Chilis are 5-10%, is that normal? My BFL miner has 0.77% HW error rate by comparison. I'm hoping it will be partially made more stable in a future firmware update.
Are they plugged into a hub or into three separate USB ports on your computer?
Edit: If you don't want to fiddle around with CGMiner just follow these steps, it literally should take you 3-5 minutes to get mining without issue
This is a workaround version of BFGMiner until a new firmware update for the chilis
Here's a modified version of BFGMiner, I also included the driver inside of it as well that should fix your problem. (I don't know much about CGMiner though)
http://www.speedyshare.com/uKncp/BFGMiner-Chili.zip
Open up bfgminer.conf and change the Pool and Username to whatever you want (It currently uses mine so make sure you change it)
Run CDM v2.08.30 WHQL Certified.exe to install the correct driver for windows
Once you do both of those, just open up bfgminer.exe and it should read from the config automatically and start hashing for you.
If it doesn't see the Chili, all you have to do is keep BFGMiner open, unplug the USB, Plug it back in, press M then + then type all or auto and enter. It should find it.
Please note if it still isn't working then you need to exit BFGMiner, unplug you chili power, plug it back in and wait for all the lights to stop blinking. If you try to find the miner while it's "Booting up" it will have issues.
"Booting Up" is the two most right LEDs (Closer to the Power) blinking back and forth. Again once all the LEDs are not blinking anymore it should be ready to start hashing, start your BFGMiner and follow the above steps.
Let me know if this helps
Here's a modified version of BFGMiner, I also included the driver inside of it as well that should fix your problem. (I don't know much about CGMiner though)
http://www.speedyshare.com/uKncp/BFGMiner-Chili.zip
Open up bfgminer.conf and change the Pool and Username to whatever you want (It currently uses mine so make sure you change it)
Run CDM v2.08.30 WHQL Certified.exe to install the correct driver for windows
Once you do both of those, just open up bfgminer.exe and it should read from the config automatically and start hashing for you.
If it doesn't see the Chili, all you have to do is keep BFGMiner open, unplug the USB, Plug it back in, press M then + then type all or auto and enter. It should find it.
Please note if it still isn't working then you need to exit BFGMiner, unplug you chili power, plug it back in and wait for all the lights to stop blinking. If you try to find the miner while it's "Booting up" it will have issues.
"Booting Up" is the two most right LEDs (Closer to the Power) blinking back and forth. Again once all the LEDs are not blinking anymore it should be ready to start hashing, start your BFGMiner and follow the above steps.
Let me know if this helps
They are plugged into a hub, but it still isn't recognized when plugged in directly. I tried the version of bfgminer you linked to -- thanks! -- but I get the same result -- two devices work, one does not appear.
I have PM'd ChipGeek; fingers crossed!
It appears to me that it's possible that third unit has a problem. If the problem is what I think it is, I can send you directions on how to fix it.
Please PM me with the serial number of that unit.
Please PM me with the serial number of that unit.
I have two units that are not operating correctly.
One had the two LEDs closest to the Power Connection blinking back and forth like it is booting up (but after waiting 5 hours they were still blinking)
the other one has the four LEDs closest to the Power Connection solid lit up (no blinking) and doesn't change from that state.
Any help on these would be appreciated (I'll PM you serial numbers once I get to where they are located)
Does the Chili work under Linux, specifically Ubuntu?
Yes. The Chili works anywhere a BFL SC ASIC works. Note that we're done all of our testing so far with cgminer. It also works with a special version of bfgminer. We will soon release a fix in our firmware that will work with standard bfgminer. I have 3 chilis, all set up the same way and attached to the same machine, and two work great but the third one isn't recognized. When I run Zadig to apply the driver it comes up as "USB Serial Converter" instead of BitFORCE SHA256 SC like the other 2, and subsequently does not appear in cgminer. What am I doing wrong?
It appears to me that it's possible that third unit has a problem. If the problem is what I think it is, I can send you directions on how to fix it.Please PM me with the serial number of that unit.
Does the Chili work under Linux, specifically Ubuntu?
I have 3 chilis, all set up the same way and attached to the same machine, and two work great but the third one isn't recognized. When I run Zadig to apply the driver it comes up as "USB Serial Converter" instead of BitFORCE SHA256 SC like the other 2, and subsequently does not appear in cgminer. What am I doing wrong?
Are they plugged into a hub or into three separate USB ports on your computer?
Edit: If you don't want to fiddle around with CGMiner just follow these steps, it literally should take you 3-5 minutes to get mining without issue
This is a workaround version of BFGMiner until a new firmware update for the chilis
Here's a modified version of BFGMiner, I also included the driver inside of it as well that should fix your problem. (I don't know much about CGMiner though)
http://www.speedyshare.com/uKncp/BFGMiner-Chili.zip
Open up bfgminer.conf and change the Pool and Username to whatever you want (It currently uses mine so make sure you change it)
Run CDM v2.08.30 WHQL Certified.exe to install the correct driver for windows
Once you do both of those, just open up bfgminer.exe and it should read from the config automatically and start hashing for you.
If it doesn't see the Chili, all you have to do is keep BFGMiner open, unplug the USB, Plug it back in, press M then + then type all or auto and enter. It should find it.
Please note if it still isn't working then you need to exit BFGMiner, unplug you chili power, plug it back in and wait for all the lights to stop blinking. If you try to find the miner while it's "Booting up" it will have issues.
"Booting Up" is the two most right LEDs (Closer to the Power) blinking back and forth. Again once all the LEDs are not blinking anymore it should be ready to start hashing, start your BFGMiner and follow the above steps.
Let me know if this helps
Here's a modified version of BFGMiner, I also included the driver inside of it as well that should fix your problem. (I don't know much about CGMiner though)
http://www.speedyshare.com/uKncp/BFGMiner-Chili.zip
Open up bfgminer.conf and change the Pool and Username to whatever you want (It currently uses mine so make sure you change it)
Run CDM v2.08.30 WHQL Certified.exe to install the correct driver for windows
Once you do both of those, just open up bfgminer.exe and it should read from the config automatically and start hashing for you.
If it doesn't see the Chili, all you have to do is keep BFGMiner open, unplug the USB, Plug it back in, press M then + then type all or auto and enter. It should find it.
Please note if it still isn't working then you need to exit BFGMiner, unplug you chili power, plug it back in and wait for all the lights to stop blinking. If you try to find the miner while it's "Booting up" it will have issues.
"Booting Up" is the two most right LEDs (Closer to the Power) blinking back and forth. Again once all the LEDs are not blinking anymore it should be ready to start hashing, start your BFGMiner and follow the above steps.
Let me know if this helps
I have 3 chilis, all set up the same way and attached to the same machine, and two work great but the third one isn't recognized. When I run Zadig to apply the driver it comes up as "USB Serial Converter" instead of BitFORCE SHA256 SC like the other 2, and subsequently does not appear in cgminer. What am I doing wrong?
I ended up ditching the conf file because I think it was setting some things that interfered with how p2pool worked. I just used the same command line settings (only pool ip and user/pass) that I was using on normal BFGMiner. Seems to read everything fine.
Also, I'm occasionally seeing a Chili go 300GH/s / 0 GH/s (high/low) with 100% hardware errors (immediately obvious on opening BFGMiner) until I power cycle it.
Also, I'm occasionally seeing a Chili go 300GH/s / 0 GH/s (high/low) with 100% hardware errors (immediately obvious on opening BFGMiner) until I power cycle it.
I had a couple Chilis gives 100% HW Errors, it ended up being the USB wasn't registering correctly with BFGMiner (This is the best way I can describe it)
You should be able to just unplug/replug in the USB to that miner, let Windows see it and then restart BFGMiner.
The other issue with this is that you tried to start BFGMiner while the Chili wasn't fully booted up. It will see the Chili but not communicate properly.
Make sure all of the LEDs are not blinking anymore before firing up BFGMiner.
Hope this helps
I ended up ditching the conf file because I think it was setting some things that interfered with how p2pool worked. I just used the same command line settings (only pool ip and user/pass) that I was using on normal BFGMiner. Seems to read everything fine.
Also, I'm occasionally seeing a Chili go 300GH/s / 0 GH/s (high/low) with 100% hardware errors (immediately obvious on opening BFGMiner) until I power cycle it.
Also, I'm occasionally seeing a Chili go 300GH/s / 0 GH/s (high/low) with 100% hardware errors (immediately obvious on opening BFGMiner) until I power cycle it.
I don't know if it's the current custom build of BFGMiner or my crap internet atm, but all my submitted shares appear to be stale...
I wasn't seeing this many stale shares before I switched from BFGMiner 3.3.
I wasn't seeing this many stale shares before I switched from BFGMiner 3.3.
No one water cooling yet?
Anyone have 4 thermal pads enough for 4-8chip chilis for sale?
Look up 3 posts before yours to crazydownloaded's post.He only has 3.
I have 4 sets left. Each set is pre-cut into 4 10x20mm pieces that can each cover 2 chips, so one set per 8-chip board. The price is $4 per set, plus shipping ($1.69 for 2-3 day USPS First-Class, or $18.11 for 1-day USPS Priority Express to most locations). I'm also in southern California.
Anyone have 4 thermal pads enough for 4-8chip chilis for sale?
Look up 3 posts before yours to crazydownloaded's post.He only has 3.
Jump to: