edit. sorry wrong thread, I thought I was in KNC official thread
Topic: KnCMiner Jupiter Miner First Impressions - page 14. (Read 65993 times)
tracking numbers are being issued now...
edit. sorry wrong thread, I thought I was in KNC official thread
edit. sorry wrong thread, I thought I was in KNC official thread
the core with 0.95 run asap
or you wait some hours before wake up the dead core?
or you wait some hours before wake up the dead core?
with 0.94 and 0.95 my ASIC slot #4 give me always this:
ASIC slot 4
Temperature sensor: 32.0 C
Die ID Cores ON Cores OFF %
0 48 0 100
1 0 48 0
2 47 1 97.9
3 48 0 100
(the temp differ sometimes but only by half a Celsius or so)
unfortunately for various reasons I hadn't data for 0.90 to 0.93.
the core with 0.95 run asap
or you wait some hours before wake up the dead core?
or you wait some hours before wake up the dead core?
how do 0.95 and only 48 core
when i install 0.95 firmware my jupiter
have all the asic chip off
you how do these with firmware 0.95( i mean only 48 core off)
when i install 0.95 firmware my jupiter
have all the asic chip off
you how do these with firmware 0.95( i mean only 48 core off)
dunno really. it simply works like that. I didn't anything fancy just upgrade from .94 to .95.
anyway if your miner work better with 0.91 stick with it.
how do 0.95 and only 48 core
when i install 0.95 firmware my jupiter
have all the asic chip off
you how do these with firmware 0.95( i mean only 48 core off)
when i install 0.95 firmware my jupiter
have all the asic chip off
you how do these with firmware 0.95( i mean only 48 core off)
I have this
ASIC slot 4
Temperature sensor: 32.0 C
Die ID Cores ON Cores OFF %
0 48 0 100
1 0 48 0
2 47 1 97.9
3 48 0 100
DC/DC ID ON/OFF Status Input Voltage Output Voltage Output Current
0 ON OK 11.9 V 0.738 V 38 A (28 W)
1 OFF OFF 11.9 V 0.714 V 0 A
2 ON OK 11.9 V 0.821 V 14.8 A (12.2 W)
3 OFF OFF 11.9 V 0.816 V 0 A
4 ON OK 11.9 V 0.742 V 38.5 A (28.6 W)
5 OFF OFF 11.9 V 0.71 V 0 A
6 OFF OFF 11.9 V 0.74 V 0 A
7 ON OK 11.9 V 0.752 V 41.3 A (31.1 W)
sickpig
what psu you have for jupiter?
also what fimware now you run at jupiter?
you have 48 core off at board with sticker number 3?
what psu you have for jupiter?
also what fimware now you run at jupiter?
you have 48 core off at board with sticker number 3?
psu: cooler master v850
fw: 0.95
yes I have 48 core off at with sticker number 3
I have this
sickpig
what psu you have for jupiter?
also what fimware now you run at jupiter?
you have 48 core off at board with sticker number 3?
what psu you have for jupiter?
also what fimware now you run at jupiter?
you have 48 core off at board with sticker number 3?
Major update: (a VRM comes back to life, lots of rambling, no sleep, sorry)
Since I really want to split up jupiters into saturns some day, I ran some more solo and paired tests. It is true that when you run one or two modules they seem to fly.
It seems the controller board has some explainin' to do. I was able to get ~270Gh paired and ~135Gh solo but when putting those three together it was a disaster.
Cores flopping on one chip that seems really picky when not running solo or paired. Instead of a total over ~400 it would be under ~360 or worse for the three boards
Then as I was putting everything back in resignation, setting up my auto-restart script again for .94 and settling for ~410Gh... I saw the dead VRM show output current again (instead of < 1)
quickly I updated to .95 (yes that is what started this mess, but now I believe I could preserve it by not overclocking it anymore)
also, that board was a #1 sticker board which usually have perfect ASICs in them (hardly any cores go down) so it was good to see that VRM wake the hell up again and use more the 3 dies
and here I stand with ~480Gh running the safer .95 which was only getting ~360Gh before.
I am not back to the ~520 it was running overclocked, and it is tempting, but I'll just take the lower wattage and being close to what I had for now.
time to get some sleep
(ps - if you ever want to save a file on the miner, put it in /config since most everything gets rewritten on reboot)
Since I really want to split up jupiters into saturns some day, I ran some more solo and paired tests. It is true that when you run one or two modules they seem to fly.
It seems the controller board has some explainin' to do. I was able to get ~270Gh paired and ~135Gh solo but when putting those three together it was a disaster.
Cores flopping on one chip that seems really picky when not running solo or paired. Instead of a total over ~400 it would be under ~360 or worse for the three boards
Then as I was putting everything back in resignation, setting up my auto-restart script again for .94 and settling for ~410Gh... I saw the dead VRM show output current again (instead of < 1)
quickly I updated to .95 (yes that is what started this mess, but now I believe I could preserve it by not overclocking it anymore)
also, that board was a #1 sticker board which usually have perfect ASICs in them (hardly any cores go down) so it was good to see that VRM wake the hell up again and use more the 3 dies
and here I stand with ~480Gh running the safer .95 which was only getting ~360Gh before.
I am not back to the ~520 it was running overclocked, and it is tempting, but I'll just take the lower wattage and being close to what I had for now.
time to get some sleep
(ps - if you ever want to save a file on the miner, put it in /config since most everything gets rewritten on reboot)
by chance did you measure BeagleBloard load (using uptime) while you test the "Saturn" configuration?
You might want to give 0.93 a try.
I think that gives the best performance so far for Saturns.
I'm trying it out now, 0.93 seems good. I'll add it to my stats after running it 24h.I think that gives the best performance so far for Saturns.
I have a board 1 and 2 with 4 VRMs per board.
.93 restarts often if you have hardware issues.. .94 will just let you slowly go down. That is why I wrote a auto-restart script that would run every hour or so when I was forced to run .94 instead of .93 (had a board with a dormant VRM that wouldn't let me run .93 anymore)
but it came back to life now (see above post) so I am running the safe and slow .95 since that miner has had stability issues.
You might want to give 0.93 a try.
I think that gives the best performance so far for Saturns.
I'm trying it out now, 0.93 seems good. I'll add it to my stats after running it 24h.I think that gives the best performance so far for Saturns.
I have a board 1 and 2 with 4 VRMs per board.
Major update: (a VRM comes back to life, lots of rambling, no sleep, sorry)
Since I really want to split up jupiters into saturns some day, I ran some more solo and paired tests. It is true that when you run one or two modules they seem to fly.
It seems the controller board has some explainin' to do. I was able to get ~270Gh paired and ~135Gh solo but when putting those three together it was a disaster.
Cores flopping on one chip that seems really picky when not running solo or paired. Instead of a total over ~400 it would be under ~360 or worse for the three boards
Then as I was putting everything back in resignation, setting up my auto-restart script again for .94 and settling for ~410Gh... I saw the dead VRM show output current again (instead of < 1)
quickly I updated to .95 (yes that is what started this mess, but now I believe I could preserve it by not overclocking it anymore)
also, that board was a #1 sticker board which usually have perfect ASICs in them (hardly any cores go down) so it was good to see that VRM wake the hell up again and use more the 3 dies
and here I stand with ~480Gh running the safer .95 which was only getting ~360Gh before.
I am not back to the ~520 it was running overclocked, and it is tempting, but I'll just take the lower wattage and being close to what I had for now.
time to get some sleep
(ps - if you ever want to save a file on the miner, put it in /config since most everything gets rewritten on reboot)
Since I really want to split up jupiters into saturns some day, I ran some more solo and paired tests. It is true that when you run one or two modules they seem to fly.
It seems the controller board has some explainin' to do. I was able to get ~270Gh paired and ~135Gh solo but when putting those three together it was a disaster.
Cores flopping on one chip that seems really picky when not running solo or paired. Instead of a total over ~400 it would be under ~360 or worse for the three boards
Then as I was putting everything back in resignation, setting up my auto-restart script again for .94 and settling for ~410Gh... I saw the dead VRM show output current again (instead of < 1)
quickly I updated to .95 (yes that is what started this mess, but now I believe I could preserve it by not overclocking it anymore)
also, that board was a #1 sticker board which usually have perfect ASICs in them (hardly any cores go down) so it was good to see that VRM wake the hell up again and use more the 3 dies
and here I stand with ~480Gh running the safer .95 which was only getting ~360Gh before.
I am not back to the ~520 it was running overclocked, and it is tempting, but I'll just take the lower wattage and being close to what I had for now.
time to get some sleep
(ps - if you ever want to save a file on the miner, put it in /config since most everything gets rewritten on reboot)
I'm having the opposite problem with my bad Jupiter.
I have the three good ones have a sticker 2 on them. The bad one is a sticker of 1.
My other two Jupiters running perfectly fine though have the same configuration.
1 2
2 2
I have 4 VRM's per board fyi.
I have the three good ones have a sticker 2 on them. The bad one is a sticker of 1.
My other two Jupiters running perfectly fine though have the same configuration.
1 2
2 2
I have 4 VRM's per board fyi.
mine has 8 VRMs per board.
did you have any chance to use bertmod to get an idea of cores status on your board?
if not look at this mini-guide to get asic status without the need of installing the bertmod fw
https://bitcointalksearch.org/topic/m.3320948
I'm having the opposite problem with my bad Jupiter.
I have the three good ones have a sticker 2 on them. The bad one is a sticker of 1.
My other two Jupiters running perfectly fine though have the same configuration.
1 2
2 2
I have 4 VRM's per board fyi.
I have the three good ones have a sticker 2 on them. The bad one is a sticker of 1.
My other two Jupiters running perfectly fine though have the same configuration.
1 2
2 2
I have 4 VRM's per board fyi.
Can anyone running the factory 0.90 (no upgrades ever made) please share a full image of their firmware?
No unfortunately. So you think that the 0.90 they provided is different from the original?
@ Sitarow: let us know which front fans you get, I am shopping as well. You have the good early miner so I would say no one will have better conditions than you for jupiters.
That is why I am planning on making two saturns from my one jupiter. If I can't get another controller from KNC, I will atleast cut the case in half (front and back) then put the back part 90 degrees like |_ so the ASIC cables can still connect from the separated case. I can make a makeshift grill to hold new case fans in front of it
@ jelin: It is a 850psu that was running 770 watts stable. Some say they got their dead dies to come back, we'll see if I play around with that as solo sometime
http://www.microcenter.com/product/410331/Hale90_Series_V2_850_Watt_Modular_Power_Supply
@ ecliptic: I would like KNC to explain the decision more. The VRMs had their caps and everything around removed from the board so they sure saved a few nickles at our expense. I am still baking my 4 VRM boards since they give better performance than using .95
That is why I am planning on making two saturns from my one jupiter. If I can't get another controller from KNC, I will atleast cut the case in half (front and back) then put the back part 90 degrees like |_ so the ASIC cables can still connect from the separated case. I can make a makeshift grill to hold new case fans in front of it
@ jelin: It is a 850psu that was running 770 watts stable. Some say they got their dead dies to come back, we'll see if I play around with that as solo sometime
http://www.microcenter.com/product/410331/Hale90_Series_V2_850_Watt_Modular_Power_Supply
@ ecliptic: I would like KNC to explain the decision more. The VRMs had their caps and everything around removed from the board so they sure saved a few nickles at our expense. I am still baking my 4 VRM boards since they give better performance than using .95
I had posted early in this thread as to what ones I would be trying out first.
Here is a photo of both the one I am going to use compared to an avalon fan.
You can read this post here for more info.
https://bitcointalksearch.org/topic/m.3303326
You can find the avalon fans at the link below
http://www.amazon.com/gp/product/B0045733JE/ref=oh_details_o00_s00_i00?ie=UTF8&psc=1
Can anyone running the factory 0.90 (no upgrades ever made) please share a full image of their firmware?
Jump to: