|
By the way, just put a Noctura fan in my Jally because I broke a fan blade on the stock unit.
Man is it quiet.
Man is it HOT AS HELL!
Went from 60 with a working fan to 70 with two blades broken (balance, sort of) to 80 with the noctura. Not good, I have my throttle at 85. With the copper heat sink on the bottom of the case and thermal grease I'm back down to 65-70 but boo!
Note these are with the unit closed up, a good heat sink.
Anyone want to send me their old fan? Or I can run till I get my two jallies from BFL and do something with it.
C
|
|
|
|
Regarding BFL's firmware; I just got a shiny new 50GH/s single in yesterday and after nearly destroying the case drilling out the screws, I was able to get the case open.
Out of the box it was running at 50.5 GH/s, so I opened up Atmel studio - made sure engine zero was enabled, #DEFINE_PRODUCT to SINGLE, auto tune to 60GH/s disabled and set the ASIC_FREQUENCY_ACTUAL to 8 and flashed it (FW 1.2.9)
BFGminer and CGminer both report it running about 54ish GH/s now. Which is good, but I looked into the engine status and surprisingly almost all the chips have 14-16 engines, and THEORETICAL_MAX was something like 67 GH/s
So the question is, is there another speed crippler in the code somewhere or is there a reason that there would be such a large difference in hashing speed reported by software versus the THEORETICAL_MAX? My other two BFL miners (an early Jalapeno and Little Single run at pretty much the max value (31 and 8.2 GH/s respectively with less engines since they can't use engine zero)
Thanks
WARNING THERE IS! There is a 60gh limiter in the code, and it's there for a reason: If you run all 8 chips full out you will run the risk of overloading the twelve FETS under those little heat sinks. When that happens they short, it blows out the power supply, and will smoke your board when you plug in a bigger supply. I sort of recommend not flashing the Singles. You're out of warranty and in that case out of luck. We can do it on jallies because we have two chips and a full set of FETs. I am running five, and my fets are hot. Six might be the logical limit. Good luck. If you blow up your unit I'll buy it for scrap, but I don't want to do that. C |
|
|
|
|
On a side note, if one wants to do escow on a small (<1btc) transcation, how would be the best way to do it?
C
|
|
|
|
Yeah sorry didn't look that closely -_- I flipped over my 3rd one and just set a stock heat sink on the bottom no thermal paste dropped from 70c to 54c. I think amazon works in the UK you could try adding chips yourself. Making a mistake hasn't seemed to fry any yet...
Oh good, you're doing this as a service. Means I don't have to :-) Yes, heat sink makes a diff, but try the thermal grease and original case. Case gets very warm but temps stay around 60c or so with 5 chips. Not bad. I wish I could get my "immediate delivery" jallies, but it looks like it's gonna wait for a bit... C |
|
|
|
|
Helldiver: If your chips are the little ones, then you probably have 1.2.9. Remember you have to compile it with LITTLE_SINGLE, and it doesn't fit in a 128mb chip.
C
|
|
|
|
|
Just contacted Magnagen and have a deal in the works to test, I should be able to get some chips shortly. So far it looks good.
C
|
|
|
|
|
That board looks so clean...... God mine's looking like hell by comparison.
Please if you can figure out which leds on the back coorespond to which chips, I'm still curious as to which of mine was screwing up the lower CSEL lines.
|
|
|
|
Glad I didn't buy one of these the BE Blade was a far better deal 10.5 GH for $239.
*snort*. My super-jally does 20gh for $169+100. Much better than a BE blade. :-) Are you adding chips to get them that fast? Yes. |
|
|
|
|
Out of curiousity, did these ever sell?
C
|
|
|
|
Glad I didn't buy one of these the BE Blade was a far better deal 10.5 GH for $239.
*snort*. My super-jally does 20gh for $169+100. Much better than a BE blade. :-) |
|
|
|
|
No, there is a tool at the BFL forums called Handy Dandy BFL Commport something or other. It can query the jally and tell you everything.
Something I discovered though: 128mb ATMel chips in older jallies cannot run 1.2.9 software. Which means they can't take the later chips as those require 1.2.9. So if you flash a 128mb jally with 1.2.9 you get a perfect brick. Reflash with 1.2.5 and all will be well again.
C
|
|
|
|
|
Thanks for the tip, I just bought one from Amazon as I managed to break a blade on my turbo-Jally. Broke a blade on the opposite side to keep mining, but not optimal.
C
|
|
|
|
|
And another update:
This evening I got three more chips and tried to put a chip on the unit. I took off the bad chip, prepped the board, lined it up perfectly, and soldered it on. No problems, system fires up.
Fail.
Complete fail. That's insane. Rebooted it, it finds there chips.
Three chips that include chips 2,3,4 (4,5 are the original old chips, 2,3 have never been lit.)
That's the problem. One of the other chips I have put on must have a short on the select lines. As such it is thinking it's another chip and when I try to go beyond 5 it causes the unit to go nuts. The chips I have been putting on were not bad, one of the existing chips was.
I give up. Removed the chip, stopping everything for now. At this point this poor jally has been flowed a dozen times, has wrecked two chips, deballed two more, and is bannanas. I cleaned up the board, put it back together, promptly broke a fan blade *AARRGGHH*, broke a blade on the other side to pretty much balance it, put it together, and it's hashing at 20gh.
I'm going to wait till the new jallies I ordered come in, then put 2 chips on each. So I will leave it to someone else to go past 5 chips; if you can make a 6 chip jally do post.
This has been an excellent learning experience: I picked up a lot of knowledge, and will probably break even on the upgrade (since I spent for 6 chips and only got three working, $200 spent). Then again I boosted this thing more than a new jally, jally and a half, and it cost the same as a new unit. And it's here now. So it was still a pretty good deal.
Such is life. I'll post again when/if I get my new units, then I'll try putting these chips on. My guess is they will work without a problem, until I short the next CSEL line.
C
|
|
|
|
|
I'm not quite up to doing that for another person, but do you want to sell your totally wrecked jally? I'd like to test some hot-wiring thoughts.
Note: Read your other post, it looks way too screwed up. I'd recommend float the chips off and put them on another jally. Since they are old style chips they should work on a 128mb board as a set of four.
C
|
|
|
|
|
WARNING: THIS IS IMPORTANT:
Big big stopping point here. I think this is important:
I know people are flashing these things with all sorts of firmware. We know that the newer jallies with the 256mb flash chips need to be defined specifically in order to flash them. And we know that 1.2.5 and 1.2.9 work on the 256mb chips.
HOWEVER Has anyone successfully flashed 1.2.9 onto a jalapeno that has only 128mb chips?
Here is the reason: I got a Jally in for a chip upgrade. No I am not doing this for money, person asked really nicely and agreed to take all risks. Ok.
As is my protocol I change only one thing at a time. First I unboxed their unit and ran it last night. Says it's 1.2.6, kind of weird firmware but it hashes at 7.6gh overnight without overheating or anything.
Then I flashed it to 1.2.9. Failed flash with the ATMEL set to 256mb chip. Reset to 128mb chip, erased and flashed. However the Jally was *DEAD*. Totally, and completely dead. Power light, no front flashing LED, looked like a serial port. Nothing else, game over.
Flashed two more times, verified code, all good. Fails.
Flasked CK's 1.2.5 code release, Jally comes up happy with 15 cores. Now letting it run for another day to verify stable operation.
WHAT THIS MEANS!
If you have a 128mb Jally, I am not sure if you can load 1.2.8 or 1.2.9 code. Given that this code is needed for running the newer chips, it means YOU CANNOT LOAD NEWER CHIPS ON YOUR JALLY.
So, has anyone verified you can load 1.2.9 compiled code on a 128mb Jally?
C
|
|
|
|
|
Big big stopping point here. I think this is important:
I know people are flashing these things with all sorts of firmware. We know that the newer jallies with the 256mb flash chips need to be defined specifically in order to flash them. And we know that 1.2.5 and 1.2.9 work on the 256mb chips.
HOWEVER Has anyone successfully flashed 1.2.9 onto a jalapeno that has only 128mb chips?
Here is the reason: I got a Jally in for a chip upgrade. No I am not doing this for money, person asked really nicely and agreed to take all risks. Ok.
As is my protocol I change only one thing at a time. First I unboxed their unit and ran it last night. Says it's 1.2.6, kind of weird firmware but it hashes at 7.6gh overnight without overheating or anything.
Then I flashed it to 1.2.9. Failed flash with the ATMEL set to 256mb chip. Reset to 128mb chip, erased and flashed. However the Jally was *DEAD*. Totally, and completely dead. Power light, no front flashing LED, looked like a serial port. Nothing else, game over.
Flashed two more times, verified code, all good. Fails.
Flasked CK's 1.2.5 code release, Jally comes up happy with 15 cores. Now letting it run for another day to verify stable operation.
WHAT THIS MEANS!
If you have a 128mb Jally, I am not sure if you can load 1.2.8 or 1.2.9 code. Given that this code is needed for running the newer chips, it means YOU CANNOT LOAD NEWER CHIPS ON YOUR JALLY.
So, has anyone verified you can load 1.2.9 compiled code on a 128mb Jally?
C
However has 128mb flash
|
|
|
|
i got my 2 jalapenos ordered in april 2013 today!  one is hashing at 5.600 mh/s sometimes up to 6.000 mh/s (so not realy good) but the other one hashes stable at 7.700 and sometimes 8.000 mh/s without any modefications. i think that one got very good chips! i have 2 asic chips from a death jalapeno, now iam playing with my mind to solder it into the bad one. question is: i expect the new jalapenos have the new chips but the death jalapeno may have old chips. can i mix them? did someone did this already? Yes, however removing the old chips might be even more complex and you will have to reball them. You should sell me the shot jally for $50-$60 or so that I can figure out why it is dead. |
|
|
|
Whats the difference between the old and newer chips?
Height and old chips can't use engine 0 in a parallel config. New ones can. |
|
|
|
I've just flashed my Jalapeno (1 Nov build date) with CK's 1.25 firmware, and also tried the 1.26 firmware. Neither seem to work. The 1.25 firmware runs but it's showing 500GH with 100% HW errors.  1.26 it won't run on at all, just flashes it's LED quickly.  I'm running BFGMiner 3.6.0 on Minepeon, and also tried BFGMiner 3.8.0 on Windows - it just spews out errors. Any ideas? "BFL 0a: Ran out of buffer space for results, discarding extra data" You must have newer chips. Flash with 1.2.9 with "Little_single" defined and the other "single" commented out. C Where would one do this commenting out and how? I am familiar with the bundle of files used in the process but it looks like it is all written in C and I wouldn't know off hand where to mess with it and how to mess with it without breaking it. I have an actual LS but I have either been unable to get the official release flashes to work (led4 flashes continuously) or they have hashed seriously wrong which is more or less what I here HellDiverUK saying about his Jalapeno. std_defs.h, line is: Waiting for atmel here.... sigh /*************** Product Model *********************/ //#define __PRODUCT_MODEL_JALAPENO__ #define __PRODUCT_MODEL_LITTLE_SINGLE__ //#define __PRODUCT_MODEL_SINGLE__ //#define __PRODUCT_MODEL_MINIRIG__ Use that. C |
|
|
|
I've just flashed my Jalapeno (1 Nov build date) with CK's 1.25 firmware, and also tried the 1.26 firmware. Neither seem to work. The 1.25 firmware runs but it's showing 500GH with 100% HW errors. 1.26 it won't run on at all, just flashes it's LED quickly. I'm running BFGMiner 3.6.0 on Minepeon, and also tried BFGMiner 3.8.0 on Windows - it just spews out errors. Any ideas? "BFL 0a: Ran out of buffer space for results, discarding extra data" You must have newer chips. Flash with 1.2.9 with "Little_single" defined and the other "single" commented out. C |
|
|
|
|
Show Posts
