Author

Topic: Swedish ASIC miner company kncminer.com - page 1233. (Read 3049528 times)

full member
Activity: 210
Merit: 100
October 23, 2013, 04:10:54 PM
...with my proprietary triple clipboard & cardboard cooling baffle, producing 32.0C and 31.5C VRM temps.  /sperg off.   I don't know how you hosted guys can stand not being able to ghetto mod your stuff, I would be in modding withdrawls.

Wait 'till you discover aluminum foil duct tape -- there'll be no stopping you (no workbench is complete without it Cool )
hero member
Activity: 532
Merit: 500
October 23, 2013, 04:09:02 PM
I see network hashrate that was 3.25PH/s when I looked late yesterday was a moment ago only 2.72 and now is 2.9.  I wonder if it's KnC miner users shutting down and restarting with the new firmware.


KNC Pool (https://portal.kncminer.com/) speed already 70 +TH/s (from about 25 TH/s for 24 hrs ). What it mean?

The firmware worked in the datacentre. It was tested on the hosting facility last night, then released today as it was deemed stable.

Hi, Bitcoinorama!

While we have you here and since you mention the hosting facility. Any news from there? Any fires or other disasters preventing new units from being added to it?

Only my and several other people's orders are skipped, while later non-hosted orders are being shipped. You said earlier that the queue was sacred...

The responses I got from support were non-commital, along the lines of "we know there are problems with the data centre, our engineers are working on it." I haven't heard any single existing hosted customer reporting any problems with their equipment that is already running there.

Any specific information would be welcome.

Thank you.

Yes, Bitcoinorama, please enlighten us! Have they run out of power/space or something? What is going on

I have no idea about the datacentre. I know there were API issues before I left for Berlin. I've been with the Life on Bitcoin guys since.

The only thing I know about the datacentre was that 0.97 was meant to add a huge boost to performance, as for the most case has been reported and reflected in the hashrate.

I'm not cust serv, but I'll ask when I get a chance with someone involved, and hit you back. I've said words to that effect in the PM you sent me earlier.
sr. member
Activity: 1176
Merit: 265
October 23, 2013, 03:55:15 PM
update...
the slowest saturn, (255)normally, reported earlier as 260, is still inching upward, and now at 262.
The others, are 267 & 280 at present... Thumbs up

Who fucking cares! Are you trying to break a forum speed record for the most of inane/autistic posts per hour.
some of us are sharing information as it unfolds...
you obviously don't get what "Sharing information" is about... get lost...

on another note...


hope it makes someone smile!

IT does with leverage trading Smiley Been making me smile all week lol
legendary
Activity: 938
Merit: 1000
LIR DEV
October 23, 2013, 03:47:31 PM
Question for the group.....
This is my friend's Jupiter...


It came from factory using 0.95
The circled area is where we attempted to load 0.96...
tried opencores, yes...
We since flashed back to 0.95, and you see that it's ok again...
So, the Q is:  Should we try 0.97?   I know it will stop the "Flushwork" issue
but we are hesitant to load 0.97 since what 0.96 did...?

The downward spikes were internet connection problems he had...
(Evidently, his Son downloading videos & stuff unbeknownst to him...)....
cgminer had values listed on the RF field every round.
upgrading the connection to a bit faster dsl...
soy
legendary
Activity: 1428
Merit: 1013
October 23, 2013, 03:42:02 PM
update...
the slowest saturn, (255)normally, reported earlier as 260, is still inching upward, and now at 262.
The others, are 267 & 280 at present... Thumbs up

Who fucking cares! Are you trying to break a forum speed record for the most of inane/autistic posts per hour.

Maybe everyone who has a Saturn and is debating whether to update or not? Stop being such an ass.

Absolutely.  Mashed the ignore.
sr. member
Activity: 446
Merit: 250
October 23, 2013, 03:37:36 PM
update...
the slowest saturn, (255)normally, reported earlier as 260, is still inching upward, and now at 262.
The others, are 267 & 280 at present... Thumbs up

Who fucking cares! Are you trying to break a forum speed record for the most of inane/autistic posts per hour.

Maybe everyone who has a Saturn and is debating whether to update or not? Stop being such an ass.

Your autism is showing. Ignore.
legendary
Activity: 1904
Merit: 1007
October 23, 2013, 03:34:34 PM
Firmware 0.97 is better than 0.96 which is better than 0.95 and so on. Good job KnC!
legendary
Activity: 938
Merit: 1000
LIR DEV
October 23, 2013, 03:31:06 PM
update...
the slowest saturn, (255)normally, reported earlier as 260, is still inching upward, and now at 262.
The others, are 267 & 280 at present... Thumbs up

Who fucking cares! Are you trying to break a forum speed record for the most of inane/autistic posts per hour.
some of us are sharing information as it unfolds...
you obviously don't get what "Sharing information" is about... get lost...

on another note...


hope it makes someone smile!
sr. member
Activity: 314
Merit: 250
October 23, 2013, 03:29:38 PM
I also noticed a decrease in the past 24h but it seems is recovering in the last rounds.
sr. member
Activity: 446
Merit: 250
October 23, 2013, 03:26:52 PM
update...
the slowest saturn, (255)normally, reported earlier as 260, is still inching upward, and now at 262.
The others, are 267 & 280 at present... Thumbs up

Who fucking cares! Are you trying to break a forum speed record for the most of inane/autistic posts per hour.
full member
Activity: 143
Merit: 100
October 23, 2013, 03:20:27 PM
Hey guys,

I have a Jupiter unit hosted with KnC since the beginning. It was performing really nice, with averages near the 550 GH/s on Bitminter, sometimes even reaching the 600 GH/s

After the firmware update yesterday it has been hashing all day in the 400's range. I'm reading very good feedback about the new firmware, but whatever it was, it really screwed my hashing rates.

Anyone experiencing a similar situation?

Thank you in advance for your feedback,

Best,

legendary
Activity: 1064
Merit: 1001
October 23, 2013, 03:19:58 PM
Quite a response on the PSU / Miner issue! Had to go back through a 1.5 pages in just a couple hours to catch up Tongue
Pretty good advice from folks so far as well.

On just the PS with the mb cable jumped - I get 1-4 revs of the PS fan, then nothing. It's like something clicks off in the PS as soon as it ramps up.

That's the issue right there then. Presuming the paperclip is in the right place and securely in the MB connector (no looseness), it may be that the PSU is hitting the 'protection' threshold and powering off.
I think was already pointed out, but you could try hooking this one up to a desktop computer (assuming you have one) and see if it makes any difference.
legendary
Activity: 938
Merit: 1000
LIR DEV
October 23, 2013, 03:19:52 PM
update...
the slowest saturn, (255)normally, reported earlier as 260, is still inching upward, and now at 262.
The others, are 267 & 280 at present... Thumbs up
sr. member
Activity: 378
Merit: 250
October 23, 2013, 03:17:31 PM
Hey - I apologize profusely ... I imagine this HAS been answered before.

I was away for a week, just got back - and found my Jupiter waiting for me.

The problem is, can't get the thing to boot.

Have an XFX pro 1050W modular to run it.

Everything looks connected fine ... pci-e's are solid and the molex is in.
Paper clip tricked it on pins 4-5, 4-6, 4-whatever the one that's a row down and over is .... all with the same results .... PS fan and the jupiter fans spin for a sec, then nothing.

Not getting any lights, or anything else. That's it.


Now I'm wondering if I have a dead supply out of the box, which seems unlikely .... or if I'm simply fucking something up .... which sounds much more likely.

Can you help a (very excited) brother out?

Thanks very much.
John

[EDIT] I AM trying to catch up ... but I'm still about hundred pages behind.

You have to whisper "up yours, BFL!" before turning it on.  ;-)
soy
legendary
Activity: 1428
Merit: 1013
October 23, 2013, 02:51:05 PM
Just back from 7 miles with my dog and found my miners down.  Must have been cable work nearby.  

So, here's what I think.  If an ASIC module has one or more dies showing high cores being disabled, shut down the system, let sit a minute before unplugging cables from the module.  Remove the module's heatsink, remove the board from the unit.  Then with some gentle support under 1 VRM at a time, exert pressure down on the flat metal top.  Continue with each VRM supporting under that module as you do so.  Reassemble the unit.  Run enablecores.bin and if you see improvement it's not that the VRMs are providing improved power but that the VRMs are losing more heat from their top rather than there bottom.  When they lose heat from the bottom the heat travels by way of the PCB to the nearby ASIC module and the nearest die will come up with errors.  That one reason the lower the fans to the deck method works so effectively - it passes air between the VRMs and ASIC module.

You all are welcome.  I know this is helping my competition but then I've never been an overachiever.



And if it works, the tops of the VRMs may have been jogged away from the underlying components when the fans got knocked free in transit or struck by a bouncing fan in transit.  If those tops do just snap on/off I wouldn't go just using any old heatsink compound.  I had noticed earlier this year when I built a heatsink for a USB Block Erupter, the heatsink contacting both the CP2102 and the ASIC, if the compound came in contact with the ASIC pins the hashrate suffered.  The stuff is suppose to be non-conductive but who knows.

If you remember the mid-west miner company, they chose the wrong FETs, the problem then wasn't so much the FETs but that the buck-converter got hot and I bet it was the ASIC closest to the overheating buck converter that got most often populated.  I can't understand when the buck converter datasheet clearly stated it will overheat if the wrong fets.  Then that most often populated ASIC would have high errors and they perhaps wondered why.
soy
legendary
Activity: 1428
Merit: 1013
October 23, 2013, 02:29:04 PM
Just back from 7 miles with my dog and found my miners down.  Must have been cable work nearby.  

So, here's what I think.  If an ASIC module has one or more dies showing high cores being disabled, shut down the system, let sit a minute before unplugging cables from the module.  Remove the module's heatsink, remove the board from the unit.  Then with some gentle support under 1 VRM at a time, exert pressure down on the flat metal top.  Continue with each VRM supporting under that module as you do so.  Reassemble the unit.  Run enablecores.bin and if you see improvement it's not that the VRMs are providing improved power but that the VRMs are losing more heat from their top rather than there bottom.  When they lose heat from the bottom the heat travels by way of the PCB to the nearby ASIC module and the nearest die will come up with errors.  That one reason the lower the fans to the deck method works so effectively - it passes air between the VRMs and ASIC module.

You all are welcome.  I know this is helping my competition but then I've never been an overachiever.



And if it works, the tops of the VRMs may have been jogged away from the underlying components when the fans got knocked free in transit or struck by a bouncing fan in transit.  If those tops do just snap on/off I wouldn't go just using any old heatsink compound.  I had noticed earlier this year when I built a heatsink for a USB Block Erupter, the heatsink contacting both the CP2102 and the ASIC, if the compound came in contact with the ASIC pins the hashrate suffered.  The stuff is suppose to be non-conductive but who knows.
hero member
Activity: 532
Merit: 500
October 23, 2013, 02:26:25 PM
Roughly one second.

I'm talking 1-3 revolutions of the fan.
It's on, then it's instantly off.

It's not even getting to boot, so can't see it being firmware.

This seems squarely a hardware / me screwing it up somehow-ware issue.

Run one module at a time.

And make note of the light sequence on boot up.

To be fair though sound like something tripped your PSU. Turn everything off, before removing or inserting anything. . Remove the ATX cable, from the PSU. Reinsert it. Make sure all other cables are plugged in.

If it's not a Corsair Hx series PSU, turn it back on. If it is a Corsair Hx series PSU I would not risk turning it back on.

Does it start?

If it doesn't try one module at a time and as I typed before make not of boot sequence lighting, is the bright LED solid and longish, 3-5 secs, or a blip, what combination of the red and green light remain at the end.

If no modules work it's likely to be the PSU.
legendary
Activity: 938
Merit: 1000
LIR DEV
October 23, 2013, 02:22:40 PM
indeed CYPHER, I'm happy now... close enough for horseshoes & handgernades....
soy
legendary
Activity: 1428
Merit: 1013
October 23, 2013, 02:19:54 PM
Roughly one second.

I'm talking 1-3 revolutions of the fan.
It's on, then it's instantly off.

It's not even getting to boot, so can't see it being firmware.

This seems squarely a hardware / me screwing it up somehow-ware issue.

Run one module at a time.
newbie
Activity: 39
Merit: 0
October 23, 2013, 02:17:04 PM
On 0.97 I get better WU, better hashrate and quicker flushwork. But I still get lower hashrate on pool, because HW almost doubled (~9% vs ~16% now)
Jump to: