Swedish ASIC miner company kncminer.com

[timmmers]

I wonder about modules which lost fans in transit.  I wonder if they somehow saw a greater shock and as a result will have a higher disabled core rate.  If so that might indicate shock damage at the Ball Grid Array where the rubber meets the road, the ASIC meets the PCB.

My Mercury, with upgraded firmware to 0.96 and having ran enablecores.bin, ran all night on Slush's, never reached 100GH/s, only registered 75-77GH/s on Slush.  Can't see the cores without BertMod but the last time I did on 0.95 the cores were 0/75.0%, 1/95.8%, 2/89.6%, 3/91.7%.  Plenty of cooling (34.5°C).  Cgminer:  KnC 0:| 99.02G/99.10Gh/s | A:883542 R:5697 HW:370264 WU:1505.5/m which means HW is 41.9%.

Something of a disappointment after reading most Jupiters were getting well over 500GH/s.  And to think, the Merc's cost the customer more per GH/s than Saturns or Jupiters.

If the 1 sticker isn't wrong then perhaps a shock in transit damaged the BGA as the fan was off the one module.

What do KnC say? 100 is the rig you paid for. Anything less is faulty.

[1713950348]

1713950348

[1713950348]

1713950348

[1713950348]

1713950348

[1713950348]

1713950348

[The Avenger]

To distract myself from the fact I'm losing about $1000+ in bitcoin due to KNC late shipping, I thought I'd write a:

So I guess you only bought a mercury. If only we all had that power of foresight.

Show me the math that leads you to that conclusion? I don't think you realise how much a mercury is mining per day.

[jimini]

To distract myself from the fact I'm losing about $1000+ in bitcoin due to KNC late shipping, I thought I'd write a:

So I guess you only bought a mercury. If only we all had that power of foresight.

Show me the math that leads you to that conclusion? I don't think you realise how much a mercury is mining per day.

Oh I just pulled that conclusion out of my ass.
But I have since done some calculations. I think you most likely would have paid about 20 btc for a mercury (early July). Geniblock says it will only ever mine 14 btc, and right now btc are worth about $1000 for 6.

[Searing]

Ok I managed to get putty to work and ssh...here is a screen shot of my Jupiter? all Greek to me...how does it look ...ballpark for HW errors etc ...difficulty? someone said you could set that as well..again this is STOCK came with .95 and hash wise seems OK so I did not touch anything but add ssh and putty...so anyway what does the screen shot tell you anything of note...

 er also check my other two pics here on imgur.....the box was sooooo trashed by DHL and full of water too the case was....but anyway to my untrained eye it looks pretty good this screen shot any tweaking is welcome I'm a noob to cgminer

http://imgur.com/vpTscD0


 much better today then the look on my face when I saw the DHL guy with my box lte me tell you!!!!!

 Searing

[Phoenix1969]

looks ok... but i'd use 0.96 asap
looks like it wasnt running for long?
takes about 15 mins to come up to par

[The Avenger]

To distract myself from the fact I'm losing about $1000+ in bitcoin due to KNC late shipping, I thought I'd write a:

So I guess you only bought a mercury. If only we all had that power of foresight.

Show me the math that leads you to that conclusion? I don't think you realise how much a mercury is mining per day.

Oh I just pulled that conclusion out of my ass.
But I have since done some calculations. I think you most likely would have paid about 20 btc for a mercury (early July). Geniblock says it will only ever mine 14 btc, and right now btc are worth about $1000 for 6.

Yes, it fairly obvious where you got the original conclusion from. You can check this post to see where I got my $1000+ figure from if you are interested https://bitcointalk.org/index.php?topic=170332.msg3362943#msg3362943

[Phoenix1969]

Personally, I think the WU theory is straight B.S.
Look at these and tell me...

[Searing]

looks ok... but i'd use 0.96 asap
looks like it wasnt running for long?
takes about 15 mins to come up to par

yeah I heard that 96 does not bring up bad cores...but again ...was gonna wait see how it shakes out...I mean it is doing 535gh as ave so and yeah it was down I turned it off with ssh trgettig that going prob only up 1hr...i'll upgrade eventually but imho on these knc upgrades you prob sholdd like to every other one...the first users of such seem to get creamed imho

prob i'll see .97 come out...wait a bit then slip up to that (im still tramatized by how my unit arrived from DHL the fiends...I thought I had a block erruptor at best)

Searing

[Searing]

Personally, I think the WU theory is straight B.S.
Look at these and tell me...

wu theory?? 

Searing

[Phoenix1969]

looks ok... but i'd use 0.96 asap
looks like it wasnt running for long?
takes about 15 mins to come up to par

yeah I heard that 96 does not bring up bad cores...but again ...was gonna wait see how it shakes out...I mean it is doing 535gh as ave so and yeah it was down I turned it off with ssh trgettig that going prob only up 1hr...i'll upgrade eventually but imho on these knc upgrades you prob sholdd like to every other one...the first users of such seem to get creamed imho

prob i'll see .97 come out...wait a bit then slip up to that (im still tramatized by how my unit arrived from DHL the fiends...I thought I had a block erruptor at best)

Searing

the cores enable/disable fine in 0.96...

WU theory.....peeps keep sayin' WU is most important...more is better.. I see opposite
as they fluctuate, wu's also change...
fact is...the one with the LEAST WU's is fastest always on mine

***I also wonder if trying slot 6 on those two boards may help?
is anyone experiencing different speeds changing slot plugins on the controller board?


edit:   0.96 also adds features to the gui

[soy]

I wonder about modules which lost fans in transit.  I wonder if they somehow saw a greater shock and as a result will have a higher disabled core rate.  If so that might indicate shock damage at the Ball Grid Array where the rubber meets the road, the ASIC meets the PCB.

My Mercury, with upgraded firmware to 0.96 and having ran enablecores.bin, ran all night on Slush's, never reached 100GH/s, only registered 75-77GH/s on Slush.  Can't see the cores without BertMod but the last time I did on 0.95 the cores were 0/75.0%, 1/95.8%, 2/89.6%, 3/91.7%.  Plenty of cooling (34.5°C).  Cgminer:  KnC 0:| 99.02G/99.10Gh/s | A:883542 R:5697 HW:370264 WU:1505.5/m which means HW is 41.9%.

Something of a disappointment after reading most Jupiters were getting well over 500GH/s.  And to think, the Merc's cost the customer more per GH/s than Saturns or Jupiters.

If the 1 sticker isn't wrong then perhaps a shock in transit damaged the BGA as the fan was off the one module.

Just tried firmware 0.90 with enablecores.bin

KnC 0: | 168.0G/109.9Gh/s | A:5014 R:257 HW:774 WU:1985.0/m

Previously the best WU: I could get were just above 1500.

It's only been up a few minutes but that's the first I've seen the average over 100!

a minute later...   KnC 0:   | 168.3G/121.1Gh/s | A:8254 R:500 HW:1048 WU:2060.0/m

[soy]

I wonder about modules which lost fans in transit.  I wonder if they somehow saw a greater shock and as a result will have a higher disabled core rate.  If so that might indicate shock damage at the Ball Grid Array where the rubber meets the road, the ASIC meets the PCB.

My Mercury, with upgraded firmware to 0.96 and having ran enablecores.bin, ran all night on Slush's, never reached 100GH/s, only registered 75-77GH/s on Slush.  Can't see the cores without BertMod but the last time I did on 0.95 the cores were 0/75.0%, 1/95.8%, 2/89.6%, 3/91.7%.  Plenty of cooling (34.5°C).  Cgminer:  KnC 0:| 99.02G/99.10Gh/s | A:883542 R:5697 HW:370264 WU:1505.5/m which means HW is 41.9%.

Something of a disappointment after reading most Jupiters were getting well over 500GH/s.  And to think, the Merc's cost the customer more per GH/s than Saturns or Jupiters.

If the 1 sticker isn't wrong then perhaps a shock in transit damaged the BGA as the fan was off the one module.

Just tried firmware 0.90 with enablecores.bin

KnC 0: | 168.0G/109.9Gh/s | A:5014 R:257 HW:774 WU:1985.0/m

Previously the best WU: I could get were just above 1500.

It's only been up a few minutes but that's the first I've seen the average over 100!

a minute later...   KnC 0:   | 168.3G/121.1Gh/s | A:8254 R:500 HW:1048 WU:2060.0/m

KnC 0:| 161.3G/129.0Gh/s | A:23158 R:1067 HW:2166 WU:2099.0/m

root@Mercury-3DF:~# uptime
 17:46:50 up 13 min,  load average: 1.99, 1.84, 1.12

Smiley face isn't big enough for this hashrate, 129.0GH/s
------------------
root@Mercury-3DF:~# uptime
17:59:24 up 25 min,  load average: 1.99, 1.98, 1.61
KnC 0: | 143.9G/131.6Gh/s | A:49321 R:2525 HW:4234 WU:2130.3/m
-------------------

So, the load on the BBB?  I've heard mention those figures should be <1.0.

[DPoS]

looks ok... but i'd use 0.96 asap
looks like it wasnt running for long?
takes about 15 mins to come up to par

yeah I heard that 96 does not bring up bad cores...but again ...was gonna wait see how it shakes out...I mean it is doing 535gh as ave so and yeah it was down I turned it off with ssh trgettig that going prob only up 1hr...i'll upgrade eventually but imho on these knc upgrades you prob sholdd like to every other one...the first users of such seem to get creamed imho

prob i'll see .97 come out...wait a bit then slip up to that (im still tramatized by how my unit arrived from DHL the fiends...I thought I had a block erruptor at best)

Searing

the cores enable/disable fine in 0.96...

WU theory.....peeps keep sayin' WU is most important...more is better.. I see opposite
as they fluctuate, wu's also change...
fact is...the one with the LEAST WU's is fastest always on mine

***I also wonder if trying slot 6 on those two boards may help?
is anyone experiencing different speeds changing slot plugins on the controller board?


edit:   0.96 also adds features to the gui

how many time you have to show how clueless you are?
WU is important along with HW error rate

High WU and low HW error % will be your highest Gh avg

run along now

[Phoenix1969]

Run along now...lol
did you bother to look at the pic...?
can you explain why the 3 sats don't jive with that statement?
I'd like to try enablecores on the slowest one...
could someone post a crude procedure?

[FeedbackLoop]

I wonder about modules which lost fans in transit.  I wonder if they somehow saw a greater shock and as a result will have a higher disabled core rate.  If so that might indicate shock damage at the Ball Grid Array where the rubber meets the road, the ASIC meets the PCB.

My Mercury, with upgraded firmware to 0.96 and having ran enablecores.bin, ran all night on Slush's, never reached 100GH/s, only registered 75-77GH/s on Slush.  Can't see the cores without BertMod but the last time I did on 0.95 the cores were 0/75.0%, 1/95.8%, 2/89.6%, 3/91.7%.  Plenty of cooling (34.5°C).  Cgminer:  KnC 0:| 99.02G/99.10Gh/s | A:883542 R:5697 HW:370264 WU:1505.5/m which means HW is 41.9%.

Something of a disappointment after reading most Jupiters were getting well over 500GH/s.  And to think, the Merc's cost the customer more per GH/s than Saturns or Jupiters.

If the 1 sticker isn't wrong then perhaps a shock in transit damaged the BGA as the fan was off the one module.

Just tried firmware 0.90 with enablecores.bin

KnC 0: | 168.0G/109.9Gh/s | A:5014 R:257 HW:774 WU:1985.0/m

Previously the best WU: I could get were just above 1500.

It's only been up a few minutes but that's the first I've seen the average over 100!

a minute later...   KnC 0:   | 168.3G/121.1Gh/s | A:8254 R:500 HW:1048 WU:2060.0/m

KnC 0:| 161.3G/129.0Gh/s | A:23158 R:1067 HW:2166 WU:2099.0/m

root@Mercury-3DF:~# uptime
 17:46:50 up 13 min,  load average: 1.99, 1.84, 1.12

Smiley face isn't big enough for this hashrate, 129.0GH/s

So, the load on the BBB?  I've heard mention those figures should be <1.0.

How much at pool?

[soy]

Run along now...lol
did you bother to look at the pic...?
can you explain why the 3 sats don't jive with that statement?

I say quit the bickering you two, 0.90 with enablecores.bin dropped my error rate from 50% to 8.6% and WU's from ~1500 up to 2125.3, max avg hashrate from 99GH/s to presently 131.1GH/s!

[Phoenix1969]

so how to get the enablecores.bin to run on the slo sat?
i have it (the file) on my desktop...
using putty I imagine,...

[soy]

I wonder about modules which lost fans in transit.  I wonder if they somehow saw a greater shock and as a result will have a higher disabled core rate.  If so that might indicate shock damage at the Ball Grid Array where the rubber meets the road, the ASIC meets the PCB.

My Mercury, with upgraded firmware to 0.96 and having ran enablecores.bin, ran all night on Slush's, never reached 100GH/s, only registered 75-77GH/s on Slush.  Can't see the cores without BertMod but the last time I did on 0.95 the cores were 0/75.0%, 1/95.8%, 2/89.6%, 3/91.7%.  Plenty of cooling (34.5°C).  Cgminer:  KnC 0:| 99.02G/99.10Gh/s | A:883542 R:5697 HW:370264 WU:1505.5/m which means HW is 41.9%.

Something of a disappointment after reading most Jupiters were getting well over 500GH/s.  And to think, the Merc's cost the customer more per GH/s than Saturns or Jupiters.

If the 1 sticker isn't wrong then perhaps a shock in transit damaged the BGA as the fan was off the one module.

Just tried firmware 0.90 with enablecores.bin

KnC 0: | 168.0G/109.9Gh/s | A:5014 R:257 HW:774 WU:1985.0/m

Previously the best WU: I could get were just above 1500.

It's only been up a few minutes but that's the first I've seen the average over 100!

a minute later...   KnC 0:   | 168.3G/121.1Gh/s | A:8254 R:500 HW:1048 WU:2060.0/m

KnC 0:| 161.3G/129.0Gh/s | A:23158 R:1067 HW:2166 WU:2099.0/m

root@Mercury-3DF:~# uptime
 17:46:50 up 13 min,  load average: 1.99, 1.84, 1.12

Smiley face isn't big enough for this hashrate, 129.0GH/s

So, the load on the BBB?  I've heard mention those figures should be <1.0.

How much at pool?

Slush changes slowly.  The overnight hashrate was about 75GH/s and it's just gone up to 79.92GH/s in a half hour.

[Searing]

looks ok... but i'd use 0.96 asap
looks like it wasnt running for long?
takes about 15 mins to come up to par

yeah I heard that 96 does not bring up bad cores...but again ...was gonna wait see how it shakes out...I mean it is doing 535gh as ave so and yeah it was down I turned it off with ssh trgettig that going prob only up 1hr...i'll upgrade eventually but imho on these knc upgrades you prob sholdd like to every other one...the first users of such seem to get creamed imho

prob i'll see .97 come out...wait a bit then slip up to that (im still tramatized by how my unit arrived from DHL the fiends...I thought I had a block erruptor at best)

Searing

the cores enable/disable fine in 0.96...

WU theory.....peeps keep sayin' WU is most important...more is better.. I see opposite
as they fluctuate, wu's also change...
fact is...the one with the LEAST WU's is fastest always on mine

***I also wonder if trying slot 6 on those two boards may help?
is anyone experiencing different speeds changing slot plugins on the controller board?


edit:   0.96 also adds features to the gui

thanks I always appreciate your advice my speed is going past 550gh now so I'm still gonna sit on my hands...i'll eventually upgrade to .96 or beyond..but hey i'd like to get thru 1 full day w/o mucking something up which is usually the case....

what i'm really interested is in what the tweaks will be when the bfgminer version comes out

anyway has been quite the last couple days....looking at the hash rate and diff seems I made the right choice on getting rid of my 2nd unit Saturn ..because it would ship after the 16th the 520x..they allowed a full refund which I promptly took.....prob would not have gotten it till end of month at best w/shipping and of course all that low priced stuff nov 15th going out the door ...same tune next month....(arg shipping shudder feel the need to fly to Sweden and get next unit..the horror of my destroyed pkg by dhl)..anyway....already burnt by bfl and bailed out by the 150 some extra free GH from kncminer....breaking even is looking good maybe a bit better fyi....(still no units from bfl april order they do 1 day of order per day at current rate sometime in December.....the stuff is doorstops)

anyway knc has been very good on my Saturn return chased it down from processing and everything..i may just sit stuff out till feb/march ...by that time it will probably be all shares in cloudhashing....who could keep up at this rate with the purchase of miners vs delivery vs holding the bag on risk?.....interesting times

Searing

[soy]

so how to get the enablecores.bin to run on the slo sat?
i have it (the file) on my desktop...
using putty I imagine,...

Shut down, let sit a minute, unplug the ASIC modules at the modules (the PCIE power), restart and only BBB will be running, go to the Sat. web page, upgrade to 0.90, shutdown, let sit a minute, plug the ASIC modules back in, start, go to web page, run Upgrade with enablecores.bin.  At least that's how I did it.