Swedish ASIC miner company kncminer.com

[AFox]

Fox, did you try enablecores on top of FM 9.8?

Yes, it doesn't help.

CYPER said on an other topic that firmware 0.97 isn't available on KNC's website. Does anybody know why ?
Anyways, it's a good thing I keep a copy on my computer. Here's a link for those how want to download firmware 0.97 : http://1t4pro.1fichier.com/en/index.html

But what I also don't think people realize it's that if your using pre 98 you hash rate it's not accurate, as of pre 98 hardware errors were counted towards your hash rate, and since 98 upgraded cgminer the hash rates are now correct from my understanding.

The only thing I see is that hashrate on the pool is bad with 0.98.

[DigginDeep]

Well if your hash rate on your pool was worse I would definitely be switching back my self, specially since the higher wattage 98 uses, I'm lucky 98 works great for me

[Crypto_Cumbrian]

Anyone with a Jupiter running 0.98.

I switched back to 0.95, but forgot to take a note of the Stale and Dupe shares at the pool, what figures are 0.98 getting for these.

[cognoscente]

Does anybody know why ?

Apparently there's no valid case where .97 works better than .96 or .98.  It had a bug that was corrected in .98.
In my case, .96 has higher peaks, lower valleys, and less power.  .98 has fewer low spots, quicker flushwork,  but uses more power.  I'm on .98 and liking it.

[Phoenix1969]

Did you guys leave enablecores running on top of 0.98 to get the good speeds to stay up there?...
I've been doing enablecores, but immediately re-flashing 0.98 back after the reboot....
?

[arlekyn13]

Anyone can help me with this?

--------------------------------------------------------------------------------
 (5s):0.000 (avg):0.000h/s | A:0  R:128  HW:0  WU:0.0/m
 ST: 2  SS: 0  NB: 1  LW: 281  GF: 0  RF: 0
 Connected to mint.bitminter.com diff 128 with stratum as user myuser
 Block: 000151d9281f7c40...  Diff:391M  Started: [19:54:59]  Best share: 0
--------------------------------------------------------------------------------
 [P]ool management ettings [D]isplay options [Q]uit
 KnC 0:                |  0.000/ 0.000h/s | A:0 R:0 HW:0 WU:0.0/m
--------------------------------------------------------------------------------

 [2013-10-31 19:54:55] Started cgminer 3.6.6
 [2013-10-31 19:54:55] Loaded configuration file /config/cgminer.conf
 [2013-10-31 19:54:55] Error in configuration file, partially loaded.
 [2013-10-31 19:54:55] Start cgminer with -T to see what failed to load.
 [2013-10-31 19:54:55] Probing for an alive pool
 [2013-10-31 19:54:59] Pool 0 difficulty changed to 128
 [2013-10-31 19:54:59] Network diff set to 391M
 [2013-10-31 19:54:59] Stratum from pool 0 detected new block
 [2013-10-31 19:54:59] Stratum from pool 0 requested work restart
 [2013-10-31 19:54:59] Rejected untracked stratum share from pool 0
 [2013-10-31 19:57:01] Stratum from pool 0 requested work restart
 [2013-10-31 19:57:01] KnC running flushwork

The red led on the miner stays red after reboot.

[augustocroppo]

yes, doofus. i know that, thats what i mean you fucktard. why are you still on this forum?

Augusto just being his crabby, permanent on-his-period self as usual.

If that is what you mean, then you would not say that he "solved" the block.

Appeal to insults will not change the fact that you made an incorrect statement. It only shows you fail to learn from mistakes.

I don't get the distinction you are making here.  It looks to me like he solved a block for the pool in exactly the same way he might have solved a block for himself if he had been solo mining.

When people participate in pools they are only providing the SHA-256 hash generated by their machines  to let the pool find a block header with a number equal or lower than the current target. Therefore participants in a pool cannot "solve" a block because it is the pool who execute this process. What the pool participants only do is to provide the necessary requirements to complete this process, know as Proof of Work, which is just to generate a high rate of SHA-256 hash until the current target is found.

Solo "miners" can "solve" a block like pooled "mining" because their are not only generating the SHA-256 hash, but monitoring the block header of every block propagated in the Bitcoin network.

https://en.bitcoin.it/wiki/Pooled_mining

A share is awarded by the mining pool to the clients who present a valid proof of work of the same type as the proof of work that is used for creating blocks, but of lesser difficulty, so that it requires less time on average to generate.

https://en.bitcoin.it/wiki/Proof_of_work

Proofs of work that are tied to the data of each block are required for the blocks to be accepted. The difficulty of this work is adjusted so as to limit the rate at which new blocks can be generated by the network to one every 10 minutes. Due to the very low probability of successful generation, this makes it unpredictable which worker computer in the network will be able to generate the next block.

[Phoenix1969]

Anyone can help me with this?

--------------------------------------------------------------------------------
 (5s):0.000 (avg):0.000h/s | A:0  R:128  HW:0  WU:0.0/m
 ST: 2  SS: 0  NB: 1  LW: 281  GF: 0  RF: 0
 Connected to mint.bitminter.com diff 128 with stratum as user myuser
 Block: 000151d9281f7c40...  Diff:391M  Started: [19:54:59]  Best share: 0
--------------------------------------------------------------------------------
 [P]ool management ettings [D]isplay options [Q]uit
 KnC 0:                |  0.000/ 0.000h/s | A:0 R:0 HW:0 WU:0.0/m
--------------------------------------------------------------------------------

 [2013-10-31 19:54:55] Started cgminer 3.6.6
 [2013-10-31 19:54:55] Loaded configuration file /config/cgminer.conf
 [2013-10-31 19:54:55] Error in configuration file, partially loaded.
 [2013-10-31 19:54:55] Start cgminer with -T to see what failed to load.
 [2013-10-31 19:54:55] Probing for an alive pool
 [2013-10-31 19:54:59] Pool 0 difficulty changed to 128
 [2013-10-31 19:54:59] Network diff set to 391M
 [2013-10-31 19:54:59] Stratum from pool 0 detected new block
 [2013-10-31 19:54:59] Stratum from pool 0 requested work restart
 [2013-10-31 19:54:59] Rejected untracked stratum share from pool 0
 [2013-10-31 19:57:01] Stratum from pool 0 requested work restart
 [2013-10-31 19:57:01] KnC running flushwork

The red led on the miner stays red after reboot.

because you are running the unsupported, unreccommended old cklovas release.... flash 0.98 and be done, it includes the cklovas code.

[FUKT]

Is it just me but is everyone with faulty/shit units fucked? Are KNC doing anything to fix this?

[arlekyn13]

Anyone can help me with this?

--------------------------------------------------------------------------------
 (5s):0.000 (avg):0.000h/s | A:0  R:128  HW:0  WU:0.0/m
 ST: 2  SS: 0  NB: 1  LW: 281  GF: 0  RF: 0
 Connected to mint.bitminter.com diff 128 with stratum as user myuser
 Block: 000151d9281f7c40...  Diff:391M  Started: [19:54:59]  Best share: 0
--------------------------------------------------------------------------------
 [P]ool management ettings [D]isplay options [Q]uit
 KnC 0:                |  0.000/ 0.000h/s | A:0 R:0 HW:0 WU:0.0/m
--------------------------------------------------------------------------------

 [2013-10-31 19:54:55] Started cgminer 3.6.6
 [2013-10-31 19:54:55] Loaded configuration file /config/cgminer.conf
 [2013-10-31 19:54:55] Error in configuration file, partially loaded.
 [2013-10-31 19:54:55] Start cgminer with -T to see what failed to load.
 [2013-10-31 19:54:55] Probing for an alive pool
 [2013-10-31 19:54:59] Pool 0 difficulty changed to 128
 [2013-10-31 19:54:59] Network diff set to 391M
 [2013-10-31 19:54:59] Stratum from pool 0 detected new block
 [2013-10-31 19:54:59] Stratum from pool 0 requested work restart
 [2013-10-31 19:54:59] Rejected untracked stratum share from pool 0
 [2013-10-31 19:57:01] Stratum from pool 0 requested work restart
 [2013-10-31 19:57:01] KnC running flushwork

The red led on the miner stays red after reboot.

because you are running the unsupported, unreccommended old cklovas release.... flash 0.98 and be done, it includes the cklovas code.

I just did, same status. The red led stays on, while the green one goes off after reboot and the machine won't hash. Really no idea what to do

[texaslabrat]

Is it just me but is everyone with faulty/shit units fucked? Are KNC doing anything to fix this?

I had two very marginal boards that lost about half their power due to disabled cores when running on 0.7V firmwares.  Running .94 (0.9V) allowed all of the cores to run, but then I would lose whole dies over time due to (I believe) the VRM's switching off due to being run over-spec at that voltage.  I had created a script run by cron on my linux server to periodically log onto the jupiter and restart cgminer (and for a time bfgminer).  The hit from that downtime was more than offset by the higher peak hashrates achieved.  Not optimal, and probably not healthy for long-term operation.

Then along came .98.  It seems to provide more voltage than the .96-.97 firmwares (I haven't checked, but I assume it's probably .8V) which seems to be enough to make my marginal cores happy.  But it's not running so hot as to be killing the VRMs.  In a 3-bears analogy, the .96-.97 firmware was too cold, .94 was too hot, and .98 is juuuust right.

This is what KnC has being doing to fix this.  Outside of that, they have an RMA process to replace truly bad hardware that can't be coaxed along with a change of software.  Which reminds me, I need to cancel my RMA :p

[xyzzy099]

I don't get the distinction you are making here.  It looks to me like he solved a block for the pool in exactly the same way he might have solved a block for himself if he had been solo mining.

When people participate in pools they are only providing the SHA-256 hash generated by their machines  to let the pool find a block header with a number equal or lower than the current target. Therefore participants in a pool cannot "solve" a block because it is the pool who execute this process. What the pool participants only do is to provide the necessary requirements to complete this process, know as Proof of Work, which is just to generate a high rate of SHA-256 hash until the current target is found.

Solo "miners" can "solve" a block like pooled "mining" because their are not only generating the SHA-256 hash, but monitoring the block header of every block propagated in the Bitcoin network.

https://en.bitcoin.it/wiki/Pooled_mining

A share is awarded by the mining pool to the clients who present a valid proof of work of the same type as the proof of work that is used for creating blocks, but of lesser difficulty, so that it requires less time on average to generate.

https://en.bitcoin.it/wiki/Proof_of_work

Proofs of work that are tied to the data of each block are required for the blocks to be accepted. The difficulty of this work is adjusted so as to limit the rate at which new blocks can be generated by the network to one every 10 minutes. Due to the very low probability of successful generation, this makes it unpredictable which worker computer in the network will be able to generate the next block.

The pool provides you with a block header to work on.  You double-hash the block header iteratively while incrementing the nonce, and return any results that are of higher difficulty than the pool difficulty to the pool.  If one of those results happens to also be higher difficulty than the network difficulty, you have solved the block for the pool.  The pool does not do any of the calculations associated with solving a block, so I don't see how you think the pool "solved" the block.

[texaslabrat]

Anyone can help me with this?

--------------------------------------------------------------------------------
 (5s):0.000 (avg):0.000h/s | A:0  R:128  HW:0  WU:0.0/m
 ST: 2  SS: 0  NB: 1  LW: 281  GF: 0  RF: 0
 Connected to mint.bitminter.com diff 128 with stratum as user myuser
 Block: 000151d9281f7c40...  Diff:391M  Started: [19:54:59]  Best share: 0
--------------------------------------------------------------------------------
 [P]ool management ettings [D]isplay options [Q]uit
 KnC 0:                |  0.000/ 0.000h/s | A:0 R:0 HW:0 WU:0.0/m
--------------------------------------------------------------------------------

 [2013-10-31 19:54:55] Started cgminer 3.6.6
 [2013-10-31 19:54:55] Loaded configuration file /config/cgminer.conf
 [2013-10-31 19:54:55] Error in configuration file, partially loaded.
 [2013-10-31 19:54:55] Start cgminer with -T to see what failed to load.
 [2013-10-31 19:54:55] Probing for an alive pool
 [2013-10-31 19:54:59] Pool 0 difficulty changed to 128
 [2013-10-31 19:54:59] Network diff set to 391M
 [2013-10-31 19:54:59] Stratum from pool 0 detected new block
 [2013-10-31 19:54:59] Stratum from pool 0 requested work restart
 [2013-10-31 19:54:59] Rejected untracked stratum share from pool 0
 [2013-10-31 19:57:01] Stratum from pool 0 requested work restart
 [2013-10-31 19:57:01] KnC running flushwork

The red led on the miner stays red after reboot.

because you are running the unsupported, unreccommended old cklovas release.... flash 0.98 and be done, it includes the cklovas code.

I just did, same status. The red led stays on, while the green one goes off after reboot and the machine won't hash. Really no idea what to do

Run the enablecores patch and reboot.

[texaslabrat]

I don't get the distinction you are making here.  It looks to me like he solved a block for the pool in exactly the same way he might have solved a block for himself if he had been solo mining.

When people participate in pools they are only providing the SHA-256 hash generated by their machines  to let the pool find a block header with a number equal or lower than the current target. Therefore participants in a pool cannot "solve" a block because it is the pool who execute this process. What the pool participants only do is to provide the necessary requirements to complete this process, know as Proof of Work, which is just to generate a high rate of SHA-256 hash until the current target is found.

Solo "miners" can "solve" a block like pooled "mining" because their are not only generating the SHA-256 hash, but monitoring the block header of every block propagated in the Bitcoin network.

https://en.bitcoin.it/wiki/Pooled_mining

A share is awarded by the mining pool to the clients who present a valid proof of work of the same type as the proof of work that is used for creating blocks, but of lesser difficulty, so that it requires less time on average to generate.

https://en.bitcoin.it/wiki/Proof_of_work

Proofs of work that are tied to the data of each block are required for the blocks to be accepted. The difficulty of this work is adjusted so as to limit the rate at which new blocks can be generated by the network to one every 10 minutes. Due to the very low probability of successful generation, this makes it unpredictable which worker computer in the network will be able to generate the next block.

The pool provides you with a block header to work on.  You double-hash the block header iteratively while incrementing the nonce, and return any results that are of higher difficulty than the pool difficulty to the pool.  If one of those results happens to also be higher difficulty than the network difficulty, you have solved the block for the pool.  The pool does not do any of the calculations associated with solving a block, so I don't see how you think the pool "solved" the block.

^^this

[FiatKiller]

Did you guys leave enablecores running on top of 0.98 to get the good speeds to stay up there?...
I've been doing enablecores, but immediately re-flashing 0.98 back after the reboot....
?

no need to reflash 9.8, enablecores is not a firmware - it is merely a set of commands to turn everything on

[Phoenix1969]

Anyone can help me with this?

--------------------------------------------------------------------------------
 (5s):0.000 (avg):0.000h/s | A:0  R:128  HW:0  WU:0.0/m
 ST: 2  SS: 0  NB: 1  LW: 281  GF: 0  RF: 0
 Connected to mint.bitminter.com diff 128 with stratum as user myuser
 Block: 000151d9281f7c40...  Diff:391M  Started: [19:54:59]  Best share: 0
--------------------------------------------------------------------------------
 [P]ool management ettings [D]isplay options [Q]uit
 KnC 0:                |  0.000/ 0.000h/s | A:0 R:0 HW:0 WU:0.0/m
--------------------------------------------------------------------------------

 [2013-10-31 19:54:55] Started cgminer 3.6.6
 [2013-10-31 19:54:55] Loaded configuration file /config/cgminer.conf
 [2013-10-31 19:54:55] Error in configuration file, partially loaded.
 [2013-10-31 19:54:55] Start cgminer with -T to see what failed to load.
 [2013-10-31 19:54:55] Probing for an alive pool
 [2013-10-31 19:54:59] Pool 0 difficulty changed to 128
 [2013-10-31 19:54:59] Network diff set to 391M
 [2013-10-31 19:54:59] Stratum from pool 0 detected new block
 [2013-10-31 19:54:59] Stratum from pool 0 requested work restart
 [2013-10-31 19:54:59] Rejected untracked stratum share from pool 0
 [2013-10-31 19:57:01] Stratum from pool 0 requested work restart
 [2013-10-31 19:57:01] KnC running flushwork

The red led on the miner stays red after reboot.

because you are running the unsupported, unreccommended old cklovas release.... flash 0.98 and be done, it includes the cklovas code.

I just did, same status. The red led stays on, while the green one goes off after reboot and the machine won't hash. Really no idea what to do

it's ok, don't panic.
leave the machine running...
hit the reset button 5x, count to 5, hit it 5x again.
Clear your browser cache.
wait for the machine to boot...
it will be about 13 seconds after the bright white led flashes..
go to the gui page and make sure all your info is entered, this reset it to factory

reflash 0.98.
it will work then.

[Searing]

Ok, been running over a day now no problem:

Is that an experiment ? why the plastic bags ....?

to raise the temperature closer to ideal in my cold basement

this still weirds me out....My Jupiter is working well in the opposite direction...I'm getting around 555gh with 535gh at the slush pool and 5 percent error rate on .95...and am also in a cold bsmt...62F....I also have top off and two fans in front on either side 5" wallmart fans blowing crosswise in an x pattern across the unit

my WU is like 7765 or some such... not sure of watts at wall never checked

anyway as a 'salute' to you experiment I shut 1 external wallmart fan off..core temps rose and gh rate went down 10gh overnight I turn fan back on after an hr or so it all comes back up to where it was at

my core temps are like 27c two one at 36c and two at 39c or so


anyway....how yours can work warmer I've no idea mine works the opposite

er

and don't even get me going on if I should upgrade to .98 or not with all the diff results that seems to be shooting about


last point on this unit I only see 1 core enable off/on 4-86 once every 3hrs or so...I'd guess at most if that

anyway......frigging unit kinda freaks me out it works so well....

(on a side note got my only unit left before upgrade to monarch (I know I'm an idiot but a brick now on the stuff or a brick later..it is all the same my bfl stuff is toast)

went to www.dustcoin.com

and I make more money doing PPCOIN according to that chart then bitcoin@ (53 at this diff)....so guess it is my penance to use it to play with altcoins...too painful with it making .023btc a month at current diff (soon to go down)...too have the unit mine bitcoins will jinx the knc unit ...must keep it across the house....away from knc Jupiter!

(note to self: need to get the voodoo for idiots book and chicken entrails to keep knc miner up....must be black magic my luck is too good)

Searing

[seanrarey]

I am a long-standing member of both Bitcoin and the mining community.  What I am about to say will likely not be understood by some and anger others based on what I read in this forum.

I was pointed to this forum by a person who told me it represented what was wrong with the idea of Crypto, and used it to bolstered his point that mankind at a base level must be ruled, and will himself destroy anything that interferes with that.  I disagree with his point, but much of what I read here indeed strengthens his position.

BTC, at it's core, is about decentralization and wresting power from the few and giving it to many (us).  28nm technology represents a significant plateau in the mechanics of what it will take to create and maintain the network necessary for BTC to have a chance at survival.  Being given the opportunity to get your hands on some effectively puts you on equal footing with the multi-million dollar companies and ultra-rich entities that at this moment are claiming the lion's share of the world's wealth; including Bitcoin.

Given this rare, equalizing opportunity, far too many in this forum are squandering the gift; even handing that power right back to those that will in time find a way to once again enslave you with their fees, interest and control.

Consider this.  When given the most powerful weapon yet in decentralization, many if not most of your immediately hand that power off to the largest pool you can plug into; thus decentralizing your effort and making the whole system that much weaker.

Shame on you, your greed makes us all that much easier to target.

Every individual in this forum seems more worried about their individual ROI then large entities and companies buying up millions of dollars of this technology in an effort to corner, and maybe even STOP this market.

Shame on you!  You are angry that "November orders" are shipping?

People, every single order that goes out to a "little guy", that will in turn put that power toward a small pool to help offset this huge influx of imbalance is one more chance that this experiment might actually succeed.  Pauses in shipping to us, the "little guy", are being used to produce millions of dollars of equipment for the large order guys.  That is the threat.

My hope had been that machines such as the ones being produced by KnC, when placed into the hands of common folk would be a great equalizer.  That it would make it less profitable and more difficult for the massive consortium's to corner this market.  Alas, my friend may be right.  Man must be ruled, because he is selfish and greedy, and these things will destroy him and hopes for society if not controlled by wise rulers.  If this is the case you will continue to bite the hand that gave you this opportunity in the first place.  You will continue to squander the power you were given, in hopes of a fraction more of that piece of gold.  It then becomes a pathetically simple task to dupe you into pointing your power in a direction that will enable "them" to take it away from you; permanently.

I am ashamed at what this, the mining community appears to be turning into.  This is not at all what we had in mind when we built it.


Sean

[Phoenix1969]

Ok, been running over a day now no problem:

Is that an experiment ? why the plastic bags ....?

to raise the temperature closer to ideal in my cold basement

this still weirds me out....My Jupiter is working well in the opposite direction...I'm getting around 555gh with 535gh at the slush pool and 5 percent error rate on .95...and am also in a cold bsmt...62F....I also have top off and two fans in front on either side 5" wallmart fans blowing crosswise in an x pattern across the unit

my WU is like 7765 or some such... not sure of watts at wall never checked

anyway as a 'salute' to you experiment I shut 1 external wallmart fan off..core temps rose and gh rate went down 10gh overnight I turn fan back on after an hr or so it all comes back up to where it was at

my core temps are like 27c two one at 36c and two at 39c or so


anyway....how yours can work warmer I've no idea mine works the opposite

er

and don't even get me going on if I should upgrade to .98 or not with all the diff results that seems to be shooting about


last point on this unit I only see 1 core enable off/on 4-86 once every 3hrs or so...I'd guess at most if that

anyway......frigging unit kinda freaks me out it works so well....

(on a side note got my only unit left before upgrade to monarch (I know I'm an idiot but a brick now on the stuff or a brick later..it is all the same my bfl stuff is toast)

went to www.dustcoin.com

and I make more money doing PPCOIN according to that chart then bitcoin@ (53 at this diff)....so guess it is my penance to use it to play with altcoins...too painful with it making .023btc a month at current diff (soon to go down)...too have the unit mine bitcoins will jinx the knc unit ...must keep it across the house....away from knc Jupiter!

(note to self: need to get the voodoo for idiots book and chicken entrails to keep knc miner up....must be black magic my luck is too good)

Searing

sweetspot on all mine are around 72 degrees....
some cores wont even activate at 45-55
I cant imagine 25-35, lol
until you try 70's, you can't really say you tried "Warmer" temperatures...
They are rated to run up to 105, per KNC elmail response.
The evidence is everywhere, including the articles posted...
I would at least try 70-75C, run enablecores, and flash 0.98.
You can always go back.
just my .000002Btc

[rampalija]

Ok, been running over a day now no problem:

Is that an experiment ? why the plastic bags ....?

to raise the temperature closer to ideal in my cold basement

this still weirds me out....My Jupiter is working well in the opposite direction...I'm getting around 555gh with 535gh at the slush pool and 5 percent error rate on .95...and am also in a cold bsmt...62F....I also have top off and two fans in front on either side 5" wallmart fans blowing crosswise in an x pattern across the unit






my WU is like 7765 or some such... not sure of watts at wall never checked

anyway as a 'salute' to you experiment I shut 1 external wallmart fan off..core temps rose and gh rate went down 10gh overnight I turn fan back on after an hr or so it all comes back up to where it was at

my core temps are like 27c two one at 36c and two at 39c or so


anyway....how yours can work warmer I've no idea mine works the opposite

er

and don't even get me going on if I should upgrade to .98 or not with all the diff results that seems to be shooting about


last point on this unit I only see 1 core enable off/on 4-86 once every 3hrs or so...I'd guess at most if that

anyway......frigging unit kinda freaks me out it works so well....

(on a side note got my only unit left before upgrade to monarch (I know I'm an idiot but a brick now on the stuff or a brick later..it is all the same my bfl stuff is toast)

went to www.dustcoin.com

and I make more money doing PPCOIN according to that chart then bitcoin@ (53 at this diff)....so guess it is my penance to use it to play with altcoins...too painful with it making .023btc a month at current diff (soon to go down)...too have the unit mine bitcoins will jinx the knc unit ...must keep it across the house....away from knc Jupiter!

(note to self: need to get the voodoo for idiots book and chicken entrails to keep knc miner up....must be black magic my luck is too good)

Searing

sweetspot on all mine are around 72 degrees....
some cores wont even activate at 45-55
I cant imagine 25-35, lol
until you try 70's, you can't really say you tried "Warmer" temperatures...
They are rated to run up to 105, per KNC elmail response.
The evidence is everywhere, including the articles posted...
I would at least try 70-75C, run enablecores, and flash 0.98.
You can always go back.
just my .000002Btc

80 + C is not ok, everything under it is ok temperature