idee2013
|
|
October 20, 2013, 09:58:33 AM |
|
back to all 3 sats running 0.96, but they all hang around 275 now still same procedure on all 3 saturns... 1. flash 0.90 on the miner, reboot 2. flash enablecores.bin to the miner, POWER CYCLE the miner. 3. putty in and watch cgminer until it crashes, when it does, go to the gui page again, and flash 0.96 back onto the miner, apply, then POWER CYCLE the miner(turn off for 15 seconds via the power supply switch) thats it. i had 3 sats going at 255, 265, and 275.... now all at 270 - 275ish +1 THAAANNNK YOU VERY MUCH Phoenix. That was it. My slow 220gh/s saturn runs now at avg 275GH/s and my Jupiter at avg 555 GH/s. Both with the same firmware at the end and both with the same flashing steps. But i have 1 difference Jupiter with about 540 Watts and each VRM 35.6A - 40.1A. Boards with 8 VRMs Saturn with about 430 Watts and each VRM 53.9A - 58.1A. Boards with 4 VRMs The amps are really freaky.... you're 'overclockin' with pre-95 FW (voltages run high, amps out over spec, but make ASIC jump hoops more for higher WU but higher HW error%...as you see, the 8 VRMs can handle it..) not really, the saturn has now more WU/s (4370) and less HW errors (about 7%) with 0.94 and before with 0.95 and 0.96 it had 15-20% HW Errors and 3600-3700 WU/s
|
|
|
|
ur0pl
Newbie
Offline
Activity: 56
Merit: 0
|
|
October 20, 2013, 10:01:18 AM |
|
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.
|
|
|
|
Bitcoinorama
|
|
October 20, 2013, 10:19:15 AM |
|
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.
Hold on, have you tried booting each board individually and seeing what each hashes at on it's own - without any other connected? You might determine where a fault exists that way. In any case do that and call cust serv tomo. Also take note of the length of time the bright LED stays lit for. 3-4 secs, or a blip. Whether you end up with a solid red, or green light once boot has completed. Do this for each board individually.
|
Make my day! Say thanks if you found me helpful BTC Address ---> 1487ThaKjezGA6SiE8fvGcxbgJJu6XWtZp
|
|
|
ur0pl
Newbie
Offline
Activity: 56
Merit: 0
|
|
October 20, 2013, 10:22:41 AM |
|
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
|
|
|
|
kano
Legendary
Offline
Activity: 4592
Merit: 1851
Linux since 1997 RedHat 4
|
|
October 20, 2013, 10:31:39 AM |
|
I'm thinking of getting a refund for November. I have a feeling I am going to be battling that one. Sam was such a nice person back in May. (When I had money of course) Now they all seem like a bunch of dicks. They are probably just busy engineers but it sucks seeing how they don't really want to work with people anymore. They seem to be pretty open to working with people still IMO. I wouldn't pay too much attention to the troll(s). (Not to say KnC is The Perfect Company, but they seem to be getting a lot of FUD and exaggerations...) LOL You who had zero to do with them before they released the hardware ... ah your funny. Go back to what you are good at - coming last in elections
|
|
|
|
ur0pl
Newbie
Offline
Activity: 56
Merit: 0
|
|
October 20, 2013, 11:11:55 AM |
|
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
|
|
|
|
sbfree
|
|
October 20, 2013, 11:35:35 AM |
|
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.
be sure it's not a temp. issue....they have been known to leave the plastic cover between the heat sink and the chip...if that don't help, try connecting the asic board to a different port on the beagle...shits and giggles at this points...can't hurt.
|
|
|
|
sbfree
|
|
October 20, 2013, 11:40:03 AM |
|
back to all 3 sats running 0.96, but they all hang around 275 now still same procedure on all 3 saturns... 1. flash 0.90 on the miner, reboot 2. flash enablecores.bin to the miner, POWER CYCLE the miner. 3. putty in and watch cgminer until it crashes, when it does, go to the gui page again, and flash 0.96 back onto the miner, apply, then POWER CYCLE the miner(turn off for 15 seconds via the power supply switch) thats it. i had 3 sats going at 255, 265, and 275.... now all at 270 - 275ish +1 THAAANNNK YOU VERY MUCH Phoenix. That was it. My slow 220gh/s saturn runs now at avg 275GH/s and my Jupiter at avg 555 GH/s. Both with the same firmware at the end and both with the same flashing steps. But i have 1 difference Jupiter with about 540 Watts and each VRM 35.6A - 40.1A. Boards with 8 VRMs Saturn with about 430 Watts and each VRM 53.9A - 58.1A. Boards with 4 VRMs The amps are really freaky.... you're 'overclockin' with pre-95 FW (voltages run high, amps out over spec, but make ASIC jump hoops more for higher WU but higher HW error%...as you see, the 8 VRMs can handle it..) not really, the saturn has now more WU/s (4370) and less HW errors (about 7%) with 0.94 and before with 0.95 and 0.96 it had 15-20% HW Errors and 3600-3700 WU/s wish I could get my saturn to perform like yours...i tried your steps but seemto make it much worse for me...so back to .96 where I have 20% hardware errors and just shy of 3800 WU, hashing around 250GH/s on cgminer, but server says 210-225 GH/s....stabilizes to 250GH/s after 24hrs last time, so hope this time too....but am hoping it can go like phoenix1969's 3 Saturns at 275GH/s each at the server side....now that is over delivered.
|
|
|
|
WastedLTC
|
|
October 20, 2013, 12:58:40 PM |
|
can someone explain exactly what the "hard reset" does... does the firmware stay, or revert to...?
That "hard reset" never worked for me. Press the button 5 times, wait 5 seconds, then presss again 5 times. Nothing. Nada. I even have a constant ping on the IP address and that never even goes out. What's up with that hard reset? I truly would think a total power off is the trick. What is this crazy Contra type pattern you are trying for a hard reset? Its very easy, just hold the button down for 5 seconds and you will see a bright flash of light then power down and power up. This reset has helped in the past with a few issues. (prior to .95)
|
|
|
|
FiatKiller
|
|
October 20, 2013, 01:01:10 PM |
|
Is a Hero Member mudwrestling match coming to On Demand soon? lol
|
|
|
|
RoadStress
Legendary
Offline
Activity: 1904
Merit: 1007
|
|
October 20, 2013, 01:07:18 PM |
|
back to all 3 sats running 0.96, but they all hang around 275 now still same procedure on all 3 saturns... 1. flash 0.90 on the miner, reboot 2. flash enablecores.bin to the miner, POWER CYCLE the miner. 3. putty in and watch cgminer until it crashes, when it does, go to the gui page again, and flash 0.96 back onto the miner, apply, then POWER CYCLE the miner(turn off for 15 seconds via the power supply switch) thats it. i had 3 sats going at 255, 265, and 275.... now all at 270 - 275ish Where do i get enablecores.bin?
|
|
|
|
Silv0r
|
|
October 20, 2013, 01:10:28 PM |
|
back to all 3 sats running 0.96, but they all hang around 275 now still same procedure on all 3 saturns... 1. flash 0.90 on the miner, reboot 2. flash enablecores.bin to the miner, POWER CYCLE the miner. 3. putty in and watch cgminer until it crashes, when it does, go to the gui page again, and flash 0.96 back onto the miner, apply, then POWER CYCLE the miner(turn off for 15 seconds via the power supply switch) thats it. i had 3 sats going at 255, 265, and 275.... now all at 270 - 275ish Where do i get enablecores.bin? Here you go: https://www.kncminer.com/pages/support
|
|
|
|
Micky25
Legendary
Offline
Activity: 974
Merit: 1000
|
|
October 20, 2013, 01:17:26 PM |
|
Nope, it sucks. It is broken. DAMN. =(
no offence, but following your posts about your steady fumbling around with your machine, I just waited for a post like this. My stuff is running 24/7 without touching, with the original 0.95 firmware. I just checked that everything sits well after unpacking. If its not broken, don't fix it and never change a running system. Phoenix will be probably the next to cry.
|
|
|
|
Silv0r
|
|
October 20, 2013, 02:10:36 PM |
|
Hi guys, so I played a little with firmware settings, voltage (0.7 / 0.9) and after a few restarts I now have my Mercury running stable at 130 GH/s and only have ~15 cores disabled instead of 40 cores with firmware 0.90 and enablecore.bin. I made a few photos from the ASIC board and found out that the VRM with an output voltage from 0.9V they reach temperatures over 89°C. Here is an album I made: http://imgur.com/a/wVSbq
|
|
|
|
sickpig
Legendary
Offline
Activity: 1260
Merit: 1008
|
|
October 20, 2013, 02:17:15 PM Last edit: October 20, 2013, 02:29:46 PM by sickpig |
|
Hi guys, so I played a little with firmware settings, voltage (0.7 / 0.9) and after a few restarts I now have my Mercury running stable at 130 GH/s and only have ~15 cores disabled instead of 40 cores with firmware 0.90 and enablecore.bin. I made a few photos from the ASIC board and found out that the VRM with an output voltage from 0.9V they reach temperatures over 89°C. Here is an album I made: http://imgur.com/a/wVSbqSorry but maybe I missed some news along the way. Are you able to change voltage at will? Or are you saying that using 0.90 fw means using higher voltage, while 0.95/96 lower voltage? edit1: very nice pics by the way
|
Bitcoin is a participatory system which ought to respect the right of self determinism of all of its users - Gregory Maxwell.
|
|
|
joeventura
|
|
October 20, 2013, 02:31:00 PM |
|
A well, just for once i wil do the picture also. Just for you "joeventura" And don't bother to reply, you are on ignore. No worries, sent you a nice response in PM.
|
|
|
|
rograz
|
|
October 20, 2013, 02:44:03 PM |
|
If its not broken, don't fix it and never change a running system.
Such true words, I checked fans and flashed my saturn to 0.93 the day I got it and not even logged into the web interface since.
|
|
|
|
soy
Legendary
Offline
Activity: 1428
Merit: 1013
|
|
October 20, 2013, 02:48:08 PM |
|
Yes, and the efficiency looks quite good. I see that using 0.90, which I believe uses the most energy and produces a high percentage of duplicate shares that count as rejects, this on a Mercury, using a cheap 12vdc switching supply (the output voltage of which I can adjust) and an inexpensive BBB supply, I'm drawing 259½ watts (174 watts on BertMod) at the wall so it's an efficiency of 67% so that's not great. Of course the BBB draws and it's 1 BBB to 1 module while with a Saturn it's 1BBB to 2 modules. I may be able to increase my efficiency even more by dropping the ASIC PCIE voltage down. The onboard vrms aren't completely efficient and lowering that voltage might find a sweeter spot. That's the only advantage of this cheap supply designed for powering a huge load of LEDs, the output is adjustable. That and its cost, $27.88 free shipping and a few bucks for tantalum capacitors I added. Still, 600 watts on 2 Saturns, that's 150watts per. I'm getting 134GH/s as the final settling point on 0.90 at 174watts on BertMod. If you're getting 150watts at the wall per then I suspect you aren't getting 134GH/s per avg. Of course you could be if the efficiency of the later firmware versions is great but I've heard that's at a cost of hashrate. Eliminating the duplicate shares would have gone a long way to increasing efficiency. I'll know later today when I go to higher versions of the firmware until the duplicate shares stop.
|
|
|
|
soy
Legendary
Offline
Activity: 1428
Merit: 1013
|
|
October 20, 2013, 02:59:54 PM |
|
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?
you're probably using pre-94 FW and one of your dies/VRMs is a bit flaky 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 I suggest, if you're running with the top off, cut a piece of cardboard the width of a front fan, about 5.75" wide, and high enough to abut the front of a front or both front ASIC module(s) and reach under the lip of the top front of the miner, and put it aside. When the hashrate crashes down, try putting the cardboard between the two front fans so the outside halves are pushing air into the box but the center halves are pushing air down onto the BBB. I think it's the BBB heating that causes the drop after hours of otherwise good hashing. If I'm right, when you put the cardboard in place, you can watch the first figure in the cgminer hashrate, that you can view ssh'ing in using putty, immediately rise up. If I'm wrong it won't.
|
|
|
|
Crypto_Cumbrian
Member
Offline
Activity: 113
Merit: 10
|
|
October 20, 2013, 03:04:58 PM |
|
Well I am at a total loss why my Jupiter does not get above 410Gh/s. (380 at BTC Guild)
Tried every firmware, tried the Enable cores patch and still the same.
Look at the results from bertmod, I have 1 Asic #4 showing (192 Cores all on hashing at 130Gh/s)
The other 3 Asics (# 0 , 2 , 3)
#0=80.58Gh's , #2=93.36Gh/s , #3=88Gh/s
The DC/DC are all showing 4 on and ok apart from Aisc #3 only showing 3 DC/DC on and ok , no other found.
Temps are as Follows
HW status:
ASIC slot #1: 53.5 ℃ ASIC slot #2: - ASIC slot #3: 54.0 ℃ ASIC slot #4: 61.0 ℃ ASIC slot #5: 58.5 ℃ ASIC slot #6: -
Thought this was to be plug and play, I have spend Hours upon Hours trying to nurse this Lemon back into life.
Got in Mining on the Day it arrived Wednesday the 16th at 14:00 (UK time), Mining via BTC-Guild I have the grand total of :-
2.25 BTC's
Any Suggestions on what KNC should be offering to do when I call them again tomorrow.
|
|
|
|
|