I'm running 0.93. Just tried to upgrade to 0.95, and it seems to work, but after restart the web interface still says that the current firmware revision is 0.93. I tried to upgrade (downgrade) to other versions but it's the same.

It is possible that the upgrade was successful and the web interface displays the wrong version number? Is there a way to check firmware version through ssh?

Don't plug it in.  Go buy something else at your local electronics store.  It will pay for itself in 24 hours.  You do NOT want a downed machine currently.

Also - .95 seems to be working very well for me:

 (5s):585.5G (avg):556.7Gh/s | A:65024  R:512  HW:3533  WU:7784.1/m

I'm sure you guys are aware.. but if not:

It does not want to die!

  766 root      2152 S    grep asic_status
root@Jupiter-20E:~# ps | grep asic_status
  768 root      2152 S    grep asic_status
root@Jupiter-20E:~# ps | grep asic_status
  770 root      2152 S    grep asic_status
root@Jupiter-20E:~# ps | grep asic_status
  772 root      2152 S    grep asic_status
root@Jupiter-20E:~# ps | grep asic_status
  774 root      2152 S    grep asic_status
root@Jupiter-20E:~# ps | grep asic_status
  776 root      2152 S    grep asic_status
root@Jupiter-20E:~# ps | grep asic_status
  778 root      2152 S    grep asic_status
root@Jupiter-20E:~# ps | grep asic_status
  780 root      2152 S    grep asic_status
root@Jupiter-20E:~# ps | grep asic_status
  782 root      2152 S    grep asic_status
root@Jupiter-20E:~# ps | grep asic_status
  784 root      2152 S    grep asic_status
root@Jupiter-20E:~# ps | grep asic_status
  786 root      2152 S    grep asic_status
root@Jupiter-20E:~# ps | grep asic_status
  788 root      2152 S    grep asic_status
root@Jupiter-20E:~# ps | grep asic_status
  790 root      2152 S    grep asic_status
root@Jupiter-20E:~# ps | grep asic_status
  792 root      2152 S    grep asic_status
root@Jupiter-20E:~# ps | grep asic_status
  794 root      2152 S    grep asic_status
root@Jupiter-20E:~# ps | grep asic_status
  796 root      2152 S    grep asic_status
root@Jupiter-20E:~#

ps  | grep asic_status | grep -v grep 

running .95 --  pushing over 600 at the moment.  i know that wont last but nice to see.

0.95 fixed it for me, thanks KNC went from 440 to 533. 20% HW error to 8-10% HW error

Someone knows what does it mean "FAULT 17" on status of VRM's?

Firmware 0.94, nice performing Saturn, 2 days without a reboot of CGMiner and average of 271Gh/s.
I don't even want to try 0.95 ...

2 minutes before the hour I lost connection with the Jupiter. Both the pool and the cgminer status page had lost connection as well.

The web interface was responsive however ssh was not working.

After a few moments I was able to connect and cgminer logging page updated from 542Gh/s down to 511Gh/s

Their was no downtime or cgminer restart however it seemed that the beaglebone was stalled.

As you can see the system load was low. The power draw at the wall is 580 watts so I am not sure if this may have been due to the custom script to view the status of the vrm's. I may have to restart the system and not add the vrm monitor script.



I will keep an eye out and see if it does recover over the next hour to 542 GH/s

 ps | grep asic_status 

 kill <pid_of_asic_status.pl> 

As you have said I think this had occurred. I posted the details above.

Unfortunately for this experiment I am using windows 7 pro.

sickpig

do you power one the bad core
or still off???

Here is the same results after not moving from the update tab for over 14 mins.

KnCMiner stats after 45 minutes.
https://i.imgur.com/WOCz6VX.jpg

tar xzf bertmod_0_2_1_for_knc_0_94.bin
scp asic_status.pl root@<ip_of_your_miner>:.
ssh root@<ip_of_your_miner>:.
perl ./asic_status.pl > status.html
exit
scp root@<ip_of_your_miner>:./status.html 
firefox status.html

I'm not sure why people are freaking out, I get responses within 24 hours every time when I make a reasonable, non answered in the FAQ and fully formed request of them. See below:

Hi,
 
We are aware of some performance and stability issues with some of the Jupiter’s and we are working on a fix for these issues. As soon as the fix is released on our website please update your miner and leave it to run for a few hours to check the average hashing speed.
 
If after applying the updated firmware you still have a lower performance we can then arrange an RMA for your miner or board.
 
If you have any further questions please do not hesitate in contacting us.
 
Best regards  | Med vänlig hälsning  
Keith Gurnett  
Kncminer
www.kncminer.com
Office: +46 8559 253 20

EDIT:
Just got a second reply:
Hi,
 
We are in the final stages of testing the latest firmware update and it will be released on our website soon.
 
Please could you try a hard reset of your miner by following the instructions which can be found in our manual available for download here: https://www.kncminer.com/pages/support
 
Apologies for the inconvenience caused, if you have any further questions please do not hesitate in contacting us.
 
Best regards  | Med vänlig hälsning  
Keith Gurnett  
Kncminer
www.kncminer.com
Office: +46 8559 253 20

My guess is that (KnC) under specified on the power requirements by saying 860 watts was enough to power a Jupiter.
These Jupiters can easily use more than 1000 watts, probably more like 1200 watts.  Even if then can upgrade firmware to be more efficient, at moment each of the 4 cards on my Jupiter is drawing between 285 watts and 305 watts. In total that's 1150 watts to 1220 watts so in reality you would need minimum 1350 watt power supply, but I would go a 1500 - 1600 watt just to be safe.  Even if they state they could make it more efficient you still need the head room to be safe for testing out past, present and future firmwares.

At moment I can't run all cards at once as my 860 watt power supply over loads and shut down, but I will be more sure hopefully tomorrow after I get another 860 watt power supply to add with the existing one or I may buy a 1500 - 1600 watt to run Jupiter on its own if I can find one tomorrow. 

Again, this is my initial thoughts and I'll know more next couple days as I do more testing.  Also just guessing here but this may explain problems at the data center because if you can remember they bought hundreds of the 860 watt Corsair power supplies and they must be experiencing similar problems.

I don't think it's a huge problem, as all is required is more power and after power problems are worked out then they can focus on driver/software problems to fix hardware errors etc. It wouldn't make sense to do it the other way round.

I'm not sure if the amount of VRM's has anything to do with it, as my cards have 4 VRM's not 8.

sitarow, can I ask what you are using to produce that stats image, looks good.

I had to make the tests that would tell me what the culprit to the performance hit is.

Very well.

I may as well do that first before attempting to see what the max performance from this unit would be using firmware v0.9.0 and adequate air movement along with a low temp environment.

UNDERSTAND

I THINK FINAL

that maybe not damaged chips

maybe wrong firmware

maybe not of course

you mean

3 jupiter
and the 3 jupiter  have these faulty?

or only 1 jupiter is faulty?

Sure.
This picture was taken with an iphone through the closed case, sorry for the bad quality.
I don't want to open my case at the moment.

http://s14.postimg.org/tl4834ak1/Photo_11_10_13_12_26_23.jpg

Remember, it makes only sense for Saturns. Those flaps/wings (how would a native speaker call them?)
make much sense for a Jupiter!