Was getting a 486ghs(avg) in CG now getting after a few min 516ghs(avg) WOAH!! All I did was stop CGminer by pressing q inside it, then I applied the enablecores.bin and rebooted. I'm an 8 VRM Jupiter guys DO THIS, stop waiting.
so let check if I understand this correctly.
1) u where running on 0.94 @ 486GH/s
2) you have a die on one of your ASIC slot with all 48cores disabled.
3) you stopped cgminer
4) apply enablecore.bin from web interface
5) click on the reboot link in the web interface.
6) after that you're mining @ 516GH/s
is it right ?
The die that came back was Die "1" on my slot 4, below is a current bertmod output of it. I have 12 other cores out across the other chips for 13 total now and usually they almost all turn on after 2 hours. I still have this damn power down slide after 6 hours but it slides only to 500 ghs in the five second instead of 440ghs or less as it use to before enablecores.bin usage.
(5s):541.7G (avg):519.5Gh/s NOW!
Temperature sensor: 38.5 C
Die ID Cores ON Cores OFF %
0 48 0 100
1 47 1 97.9
2 48 0 100
3 48 0 100
DC/DC ID ON/OFF Status Input Voltage Output Voltage Output Current
0 ON OK 11.8 V 0.744 V 35.5 A (26.4 W)
1 OFF OFF 11.8 V 0.712 V 0 A
2 ON OK 11.8 V 0.738 V 38.5 A (28.4 W)
3 OFF OFF 11.8 V 0.747 V 0 A
4 ON OK 12 V 0.745 V 38.2 A (28.5 W)
5 OFF OFF 11.9 V 0.695 V 0 A
6 OFF OFF 11.8 V 0.739 V 0 A
7 ON OK 11.8 V 0.732 V 40.3 A (29.5 W)
Total DC/DC power output: 446 W
Finally I've rolled the dice and have applied enablecore.bin remotely.
it works
It has resurrected my dead die

(for both jups), this the number I got after 20 min
cgminer version 3.4.0 - Started: [2013-10-22 09:42:08]
--------------------------------------------------------------------------------
(5s):547.1G (avg):509.1Gh/s | A:174812 R:1030 HW:11986 WU:7354.1/m
a few things tho share enablecore.bin just do this:
#!/bin/sh
for i in 0 1 2 3 4 5 ; do
./enable_all_cores $i >/dev/null 2>&1
if [ $? = 0 ] ; then
echo ASIC board \#$i: All cores enabled\
else
echo ASIC board \#$i: not found\
fi
done
sync
this is pure speculation someway it removes the map of faulty cores from the asic eeprom, because it requires a reboot to take effect. Just running the above don't change anything in terms of hashrate, the real effect take place at the next reboot.
edit: I forgot to add that probably one of my dies die due fw 0.90 putting to much stress to the machine (to high voltage)