Only about 9 day too late whereas I could have made ROI AND PROFIT if it my jupiters were delivered on the 8th instead of the 17th. Now, i am trying to sell both of them. That was the difference between being a day 1 and not being that

okay that seems to have worked and fixed it
Okay. that seems to have worked and fixed it. However, someone told me that I could hit "d" then "z" in cgminer to 0 out the statistics. So this is a cgminer error problem because even though I would get 1.8 Mb/s average, I would still get 500+ gh/s 5s hash rate

How can I keep on running asic_test until I get the highest amount of good cores, then use that information to put into the emprom for the max amount of cores

Okay nothing work, so now i tried to do what someone else said with downgrade to .90, power cycle, run enable cores, power cycle, upgrade to fw. .96. So far I went through one cycle of many enable cores back from disable and then some going to disable again. SO, maybe it works now. I really hope this fixes it.

Also, i tried connecting only one hashboard at a time, and i got the same error of hashing going to 2 Mb/s after an enable core disable core cycle.

I hope this new try works.

okay the asic_test thing with .96 didn't work. I am going to swap one of the bad boards with the one jupiter that I am keeping. Then, i could sell the unit. then, i could return the bad board for a good one, abit, i have to pay around 200 for shipping, but whatever. this is more a hobby at this point than profit and roi, unfortunately.

Okay, like people said in kncminer forum. You go to fw .95, you delete /config/asic_test (NOT THE Bin file, only the config file). Then, you upgrade to fw .96 and you get a new asic_test file with bad and good cores quickly mapped. Now i need to figure out how to enable more cores without running enable_cores.bin, because i don't want to enable all the cores, i want to just enable most good ones that fw .96 misses

I am trying asic_test, maybe that will fix it by mapping the good and bad cores. What happens is a lot of cores get enabled, then some of the shares are like 1k-3k , then it goes to an average of 2 Mb/s. I really hope this asic_test fixes it. I am shit out of luck now

Nope, it sucks. It is broken. DAMN. =(

it goes through enable all these cores. then it disables all those cores like 5 seconds later. and then it stays less than 5 Mh/s

I was going to sell this miner, and now I lost 7k.

Okay, part of the beagle board was not pushed all the way down. maybe that was the problem. I don't know if that happened before the problem or after. I'll see and update you. All my bad luck, i hope this isn't another one. it psychologically hurts soo much how much bad luck I have had in recent years.

For one chip, after a while and after one run of all enable from disable and then some disabled, everything runs fine and stable. Then, after another run mostof the cores for some die get enabled from disabled state. Then, it continues to work fine. Then, like almost all those cores get disabled again, and then, my average hashrate is 2 Mh/s, BUT my 5s hashrate is 526 gh/s. The average hashrate is increasing only by .003 M/h/s, So maybe there is something wrong with cgminer? It didn't have these problems until today, and it ran fine for two days straight.

I have so much bad luck in my life. what the hell.

15 btc plus 2 btc more for shipping

10 btc

with fw .95 and .96, they each give me a high hash rate whereas .96 is 20 gh/s more; however, after running at that level for four hours the hashrate went down to 1.86 mb/s. Then, after restarting it again, it would give out after about 30 minutes; then, it would do it in like 15 minutes. Is my Jupiter dying?I ran enable cores.bin. I don't know what could be wrong. Bertmod reports that most of the cores are on, only about 38 out of the 768 are off. Furthermore, the 5s hashrate shows it is getting a 525+ gh/s , but the avg hashrate is 1.86 mb/s. My hardware error rate is at about 7%

The 3rd asic slot chip reaches temperatures of around 67.5. Maybe there is a hardware shutdown temperature it it goes a little higher than that? I put a case fan on it and it runs cooler. I'll see if that was the problem

One of my miners hashes to a max for a like 4+ hours straight; then, everything fails. it goes to like infinitety hardware errors and 0 hashrate. What could be wrong and how could I fix this?

Is there a way to make the automatic threshold for bitcoin be .1 instead of 1?

for "each" or "both" ? If it is for both, then run enabled cores. It works like magic.

http://forum.kncminer.com/forum/main-category/hardware/8848-everyone-run-enabled-cores

Hashfast's original date of delivery was September 30th, so this does not come as a shock to me that there is some delay. I think it would be good that you guys get your MPP; however, they probably didn't order enough chips to fulfill that right now. They get their chips on a schedule of 3-4 weeks apart.

No one is mining for profit anymore. We are mining just to mine. If you want ROI, then sell your miner on ebay right after you get it. There are many people who would buy it just to mine.

On one chip, one die is at 50%, another is at 35%, the third is at 0%, and the fourth is at 100%. One of the dies is not active. What kind of ribbon cable would i get to replace for it?

Hi, I have a die on my chip that is completely dead. How do i revive it? I have the fan on to see if heat will revive it. The only other option i can think of is to make it extremely cold. It looks like a overall bad chip though.

Temperature sensor: 45.0 C
Die ID    Cores ON    Cores OFF    %
0   25   23    52.1
1   17   31    35.4
2   0   48    0
3   48   0    100
DC/DC ID    ON/OFF    Status    Input Voltage    Output Voltage    Output Current
0    ON    OK    11.9 V    0.732 V    26.6 A (19.5 W)
1    No DC/DC detected
2    ON    OK    12 V    0.73 V    22.6 A (16.5 W)
3    No DC/DC detected
4    ON    OK    12 V    0.739 V    13.4 A (9.9 W)
5    No DC/DC detected
6    No DC/DC detected
7    ON    OK    11.9 V    0.745 V    40.9 A (30.5 W)

How do i fixed the off cores on one of my dies?



3    

Temperature sensor: 39.5 C
Die ID    Cores ON    Cores OFF    %
0   27   21    56.2
1   17   31    35.4
2   0   48    0
3   48   0    100
DC/DC ID    ON/OFF    Status    Input Voltage    Output Voltage    Output Current
0    ON    OK    11.9 V    0.748 V    28 A (20.9 W)
1    No DC/DC detected
2    ON    OK    11.9 V    0.746 V    22.2 A (16.6 W)
3    No DC/DC detected
4    ON    OK    12 V    0.724 V    13.4 A (9.7 W)
5    No DC/DC detected
6    No DC/DC detected
7    ON    OK    11.9 V    0.745 V    40.4 A (30.1 W)


maybe if i change my ribbon cable?