Hacking KNC Titan / Jupiter / Neptune miners back to life. Why not? - page 29.

lightfoot

legendary

Activity: 3164

Merit: 2258

I fix broken miners. And make holes in teeth :-)

And in the "Take some pictures of what's up" mode, we have the following:

This is the connector on a display module that had some of the pins not soldered properly so it worked intermittently. Notice the tilt. Bit of love with a soldering iron and some flux and all is well again.

A bad repair job that was sent to me. Note the bottom right pin on the molex and how it is distended. That via is blown clear of the board, so this board would only use 2 +12v pins. Note the black mess. That is due to using a big soldering iron without pre-heat. Sad. However this is the one where the chip core is shorted to +hashing power instead of fucking ground, so there is a chance of a snowball in hell that I can figure this out.

A nice old Jupiter controller board retrofitted with two new 10 pin plugs to even it out. Take your time, desolder all the holes, then use hot air to allow the plugs to come through without pressure.

Yet another reason not to push cubes to the limit. That is a stock KNC splitter, the problem is the damn plug isn't rated for that kind of power draw....

Now I have a Titan controller on the bench that blew up. Oddly enough looks to be the Rpi went bad as the controller baseboard is happily hashing with a bbb board on it.

lightfoot

legendary

Activity: 3164

Merit: 2258

I fix broken miners. And make holes in teeth :-)

Try running all dies at 50mhz, then 100mhz. See what happens then.

junkspam

newbie

Activity: 2

Merit: 0

Can this neptune be fixed? It worked perfectly until 1 week ago.

Can new custom firmware help?
What voltage/frequency is best to use for long life?
Do I start with lowering the voltage or frequency to get temps down? I have no clue...
is temp 70 ok for DC/DC?

ASIC 2 - die 2 dead? Possible to revive?

DC/DC   Voltage (V)   Current (A)   Power (W)   Temperature (°C)
0   0.8093   6.4766   5.242   35.875
1   0.8104   6.3125   5.116   35.875
2   0.7855   35.7500   28.082   48.375
3   0.7881   35.8125   28.224   47.375
4   0.8131   1.3066   1.062   30.594
5   0.8113   0.8281   0.672   32.313
6   0.7871   35.3125   27.794   45.000
7   0.7864   35.1250   27.622   46.125

ASIC 4 - OK?

DC/DC   Voltage (V)   Current (A)   Power (W)   Temperature (°C)
0   0.7866   34.3125   26.990   56.688
1   0.7839   34.8750   27.339   58.125
2   0.7797   44.8750   34.989   68.250
3   0.7802   44.0625   34.378   69.000
4   0.7792   43.8125   34.139   61.688
5   0.7775   44.2500   34.404   66.375
6   0.7780   42.9375   33.405   66.500
7   0.7803   43.0000   33.553   63.438

ASIC 6 - all dies dead? What could be wrong?

DC/DC   Voltage (V)   Current (A)   Power (W)   Temperature (°C)
0   0.8250   0.8779   0.724   24.688
1   0.8257   0.8369   0.691   24.000
2   0.8251   0.8252   0.681   24.031
3   0.8226   1.5840   1.303   23.156
4   0.8243   0.8311   0.685   23.031
5   0.8254   1.0566   0.872   25.563
6   0.8246   1.7578   1.449   24.313
7   0.8231   1.2168   1.002   23.969

lightfoot

legendary

Activity: 3164

Merit: 2258

I fix broken miners. And make holes in teeth :-)

And while 571 is prime, 63*9 is 567 which leaves four dies left over. So they could have 9 strings of 63 per die. Hm And once again it would REALLY be helpful to have ANY specs on these things....

lightfoot

legendary

Activity: 3164

Merit: 2258

I fix broken miners. And make holes in teeth :-)

Quote from: Maxumark on March 05, 2016, 04:58:35 PM

Quote from: lightfoot on March 05, 2016, 04:22:36 PM

Question: Does anyone know how many engines are in each core of a Titan? Got a theory here....

Each miner will include four ASICs featuring a "record-breaking" 2,284 cores each. Each chip will be capable of running 18,727 threads.

Is this the information you are looking for?

That's interesting. 571 (2284/4) is a prime number.

Why would they ever have a prime number of cores per die?

Hm.

Ok, here's the thought: Pin 6 is power to the chip's housekeeping circuits. Each die has capacitors on the bottom that go to ground and to this common line 6. The line comes out to a pad on the bottom, then goes via two small traces to two pins on the chip. There are 5 pads per die, the outside two power two pins each, and the inside three power 5 pins together making 9 connections to the chip.

This is different from the actual engine power, which is supplied by the big DC-DC's. Think of this power as what runs the signal thing that polls the engines, puts work in the engine memory, that sort of thing. Each housekeeper is responsible for some number of engines, and they all then communicate on the low voltage spi bus which goes back to the fpga for figuring out.

What I think happens is that when the chip shorts due to a bad surge everything welds to ground on that die. die power, as well as the engine power. This is what we see when a board burns. Worse is if one board loses its' ground, then the ground gets pulled over the lines from the other chips which makes a real mess of either burned ribbon cables or blown dies.

So what to do?

Well, isolating the dead die is the right thing. Since there exists no stencil on earth for us to re-ball the die and remove the balls for the blown connections (the simple solution) we have to cut the lines.

The common line for those dies is very thick and runs all along the back of the board. However with a very sharp knife we should be able to cut the 9 traces to the pin vias. I'm going to need to order some very sharp surgical knives with fine points; copper dulls steel quickly and this will require very precise cuts so as not to hit the layer underneath.

Hm.

Maxumark

full member

Activity: 159

Merit: 108

Quote from: lightfoot on March 05, 2016, 04:22:36 PM

Question: Does anyone know how many engines are in each core of a Titan? Got a theory here....

Each miner will include four ASICs featuring a "record-breaking" 2,284 cores each. Each chip will be capable of running 18,727 threads.

Is this the information you are looking for?

lightfoot

legendary

Activity: 3164

Merit: 2258

I fix broken miners. And make holes in teeth :-)

Question: Does anyone know how many engines are in each core of a Titan? Got a theory here....

lightfoot

legendary

Activity: 3164

Merit: 2258

I fix broken miners. And make holes in teeth :-)

Close. I can see how to clear the lines for the pin 6 connection to the chip. There's a reason why I can't blow this open with voltage, it's eight connections into the chip off the transfer line. Given the chance it will destroy the board transfer lines before the chip core opens.

Unfortunately it's a one-way trip to clear the lines so I need to be able to find the *right* die. Back to work.

lightfoot

legendary

Activity: 3164

Merit: 2258

I fix broken miners. And make holes in teeth :-)

Interesting development on the pin 6 short thing this morning.

Got another board, this time it's a Neptune that had a destroyed power plug that someone repaired... poorly. The cube does not run. So as a part of my inspection I checked the resistance of the pins.

Pin 6 is VERY unusual: It is supposed to read 10k or so ohms, Titans that have had power plug issues can read 0 ohms (kills the controller board). This one doesn't read 0 ohms.

It reads 17 ohms. *VERY* *VERY* interesting. Every time I have seen this, it's been on a unit with a burned power connector. Not all burns do this, but I haven't found a unit that wasn't in a burned situation with a short on those lines.

So I take a chance, clean up the plug solder connections (cold solder joints do not conduct properly, you NEED board heat to do this...) and plugged it in. Get this at 100mhz clock:

KNC 0a: | 0.0/ 0.0/ 0.0 h/s | A: 0 R:0+0(none) HW: 0/none
KNC 0b: | 34.42/36.08/36.08Gh/s | A: 4 R:0+0(none) HW: 1/.02%
KNC 0c: | OFF / 0.0/ 0.0 h/s | A: 0 R:0+0(none) HW: 0/none
KNC 0d: | 7.70/14.28/128.5Mh/s | A: 0 R:0+0(none) HW:128/ 88%

0b is running, 0d is trying to run but wrecked, but look at 0c. It's "off".

I think the short here is in cube die 0c. I think in this case the short isn't to ground, it's to the chip engine's +vcc so chip control is shorting to chip engine power. And I think this is happening on die "C"....

Now to rip apart anything around die C to see if I can clear this. Finally I have a location on the chip, I can't get this with Titans because they short the controller. But in this case I have a chance to find this.

Food time.

(Edit: Look at this insanity at 200mhz)
KNC 0a: | 0.0/ 0.0/ 0.0 h/s | A:0 R:0+0(none) HW: 0/none
KNC 0b: | 114.2/173.7/346.7Gh/s | A:0 R:0+0(none) HW:4750/ 59%
KNC 0c: | OFF / 0.0/ 0.0 h/s | A:0 R:0+0(none) HW: 0/none
KNC 0d: | OFF / 0.0/ 0.0 h/s | A:0 R:0+0(none) HW: 0/none

It was at 400+gh for a second there. All through one die? Nope, short.....

edgar

legendary

Activity: 1848

Merit: 1001

Impressive!!

lightfoot

legendary

Activity: 3164

Merit: 2258

I fix broken miners. And make holes in teeth :-)

So in the meantime I figured out two other things:

1) How to fix a completely wedged Beaglebone: The normal recovery image doesn't work, the thing does nothing but light the one blue LED and you feel sad. Solution is to build a beaglebone/debian image, set it to flash to the emmc. It will pound for 30 mins with the cylon light pattern, then go solid. Reboot, then install the recovery image and restart. Presto, emmc is back, beaglebone is up, miller time!

2) Fix a display. If you have a display that's crapped out but lights check the little connectors on the bottom that go to the board. On this one it turned out that the connectors had literally not been soldered down properly to the board's pads. A little work with flux first then a soldering iron at 700f (something C) and a quick touch to each pad reflows the solder and makes for a happy display.

On to other stuff.

lightfoot

legendary

Activity: 3164

Merit: 2258

I fix broken miners. And make holes in teeth :-)

Sent out the unit with 3/4 dies restored, that's nice. It's actually not that bad, you can run the 3 dies to 60mh total without drawing 200w from the supply so you still won't blow up anything as long as the DC-DC temps are reasonable.

And doing it for bitcoin works, it's fast, reliable, works across borders, etc. Maybe I should also accept litecoin...

Now to spend the weekend tackling these two other Titans. I'm going to try to clear the short on the first one after seeing if there is any way I can disconnect the line from the bottom of the board. The onto replacing all the signal components on this second board to see if I can get more dies working (it's one die and minimal quality at that. We'll see).

C

FineHash

newbie

Activity: 14

Merit: 0

Quote from: lightfoot on March 04, 2016, 12:50:42 AM

Sure. I can take a look at it. No guarantees I can get it working, but the fact that pressure on the chip makes differences is something worth taking a deeper look into. I'll PM you information, working on getting a few things out today.

Thank you. Immensely appreciated. Worst case scenario, you send it back to me and it gets introduced to fireworks.

Bump question:

Quote from: lightfoot on March 03, 2016, 12:06:45 AM

Anyone found a source for huge .6mm pitch reballing stencils?

lightfoot

legendary

Activity: 3164

Merit: 2258

I fix broken miners. And make holes in teeth :-)

Sure. I can take a look at it. No guarantees I can get it working, but the fact that pressure on the chip makes differences is something worth taking a deeper look into. I'll PM you information, working on getting a few things out today.

FineHash

newbie

Activity: 14

Merit: 0

Quote from: lightfoot on March 03, 2016, 12:06:45 AM

Quote from: FineHash link=topic=1283859.msg14079070#msg14079070 date=1456978229\
Here is a bfgminer screenshot:
[img

http://i.imgur.com/e17mQIf.png[/img]

Here is a pic of the bottom of the board:
http://i.imgur.com/bsqMHSX.jpg

Now here is a crazy detail... depending on how tight/loose the heat sink is cinched, the entire cube will/won't appear on the (gentarkin) firmware advanced settings page. So in other words, if I screw it on normally, no cube or dies appear at all. If I crank it down a bit more, I see dies but no hashing. Possible short?

What do you get with the waas command? And how does bfgminer look when cranked down (don't do this too hard).

Based on the condition of the back of the board my guess is that either it was run like super hell or the heat sink was bad/loose and the top dies burned the board. That takes more heat than I can generate with pre-heat and my air tools, so it's a lot of heat. Enough to melt the solder and make a mess under the board.

A reflow *might* help, but those are dicey. If you want me to try let me know and send it in. I'll give it a shot, but my guess is that's the root of the problem.

Anyone found a source for huge .6mm pitch reballing stencils?

Here is the waas result, running as root below, heat sink cranked down good (but not excessive) so that dies appear. bfg shows the same as prior, "NO DEVICES FOUND" message, keeping in mind that I put the single cube on a controller all by itself for this particular test. Interesting thing to note is that for a very brief time last night the cube hashed on 3 dies. hmm.

Would you be OK with taking a look at it? I'd be happy to cover shipping there/back.

Code:

Error reading /sys/bus/i2c/devices/2-0050/eeprom
ASIC board #0 is non-functional: Bad EEPROM data
i2c_smbus_read_word_data failed: addr 0xD0
i2c_smbus_read_byte_data failed: addr 0x98
i2c_smbus_read_word_data failed: addr 0xD0
i2c_smbus_read_byte_data failed: addr 0x98
i2c_smbus_read_word_data failed: addr 0xD0
i2c_smbus_read_byte_data failed: addr 0x98
i2c_smbus_read_word_data failed: addr 0xD0
i2c_smbus_read_byte_data failed: addr 0x98
i2c_smbus_read_word_data failed: addr 0xD0
i2c_smbus_read_byte_data failed: addr 0x98
i2c_smbus_read_word_data failed: addr 0xD0
i2c_smbus_read_byte_data failed: addr 0x98
i2c_smbus_read_word_data failed: addr 0xD0
i2c_smbus_read_byte_data failed: addr 0x98
i2c_smbus_read_word_data failed: addr 0xD0
i2c_smbus_read_byte_data failed: addr 0x98
i2c_smbus_read_word_data failed: addr 0xD0
i2c_smbus_read_byte_data failed: addr 0x98
i2c_smbus_read_word_data failed: addr 0xD0
i2c_smbus_read_byte_data failed: addr 0x98
i2c_smbus_read_word_data failed: addr 0xD0
i2c_smbus_read_byte_data failed: addr 0x98
i2c_smbus_read_word_data failed: addr 0xD0
i2c_smbus_read_byte_data failed: addr 0x98
i2c_smbus_read_word_data failed: addr 0xD0
i2c_smbus_read_byte_data failed: addr 0x98
i2c_smbus_read_word_data failed: addr 0xD0
i2c_smbus_read_byte_data failed: addr 0x98
i2c_smbus_read_word_data failed: addr 0xD0
i2c_smbus_read_byte_data failed: addr 0x98
i2c_smbus_read_word_data failed: addr 0xD0
i2c_smbus_read_byte_data failed: addr 0x98
i2c_smbus_read_word_data failed: addr 0xD0
i2c_smbus_read_byte_data failed: addr 0x98
i2c_smbus_read_word_data failed: addr 0xD0
i2c_smbus_read_byte_data failed: addr 0x98
i2c_smbus_read_word_data failed: addr 0xD0
i2c_smbus_read_byte_data failed: addr 0x98
i2c_smbus_read_word_data failed: addr 0xD0
i2c_smbus_read_byte_data failed: addr 0x98
i2c_smbus_read_word_data failed: addr 0xD0
i2c_smbus_read_byte_data failed: addr 0x98
i2c_smbus_read_word_data failed: addr 0xD0
i2c_smbus_read_byte_data failed: addr 0x98
i2c_smbus_read_word_data failed: addr 0xD0
i2c_smbus_read_byte_data failed: addr 0x98
i2c_smbus_read_word_data failed: addr 0xD0
i2c_smbus_read_byte_data failed: addr 0x98
i2c_smbus_read_word_data failed: addr 0xD0
i2c_smbus_read_byte_data failed: addr 0x98
i2c_smbus_read_word_data failed: addr 0xD0
i2c_smbus_read_byte_data failed: addr 0x98
i2c_smbus_read_word_data failed: addr 0xD0
i2c_smbus_read_byte_data failed: addr 0x98
i2c_smbus_read_word_data failed: addr 0xD0
i2c_smbus_read_byte_data failed: addr 0x98
i2c_smbus_read_word_data failed: addr 0xD0
i2c_smbus_read_byte_data failed: addr 0x98
i2c_smbus_read_word_data failed: addr 0xD0
i2c_smbus_read_byte_data failed: addr 0x98
i2c_smbus_read_word_data failed: addr 0xD0
i2c_smbus_read_byte_data failed: addr 0x98
i2c_smbus_read_word_data failed: addr 0xD0
i2c_smbus_read_byte_data failed: addr 0x98
KnC: Frequency change FAILED!
KnC 1-0: Frequency change FAILED!KnC: Frequency change FAILED!
KnC 1-1: Frequency change FAILED!KnC: Frequency change FAILED!
KnC 1-2: Frequency change FAILED!KnC: Frequency change FAILED!
KnC 1-3: Frequency change FAILED!KnC: Frequency change FAILED!
KnC 2-0: Frequency change FAILED!KnC: Frequency change FAILED!
KnC 2-1: Frequency change FAILED!KnC: Frequency change FAILED!
KnC 2-2: Frequency change FAILED!KnC: Frequency change FAILED!
KnC 2-3: Frequency change FAILED!KnC: Frequency change FAILED!
KnC 3-0: Frequency change FAILED!KnC: Frequency change FAILED!
KnC 3-1: Frequency change FAILED!KnC: Frequency change FAILED!
KnC 3-2: Frequency change FAILED!KnC: Frequency change FAILED!
KnC 3-3: Frequency change FAILED!KnC: Frequency change FAILED!
KnC 4-0: Frequency change FAILED!KnC: Frequency change FAILED!
KnC 4-1: Frequency change FAILED!KnC: Frequency change FAILED!
KnC 4-2: Frequency change FAILED!KnC: Frequency change FAILED!
KnC 4-3: Frequency change FAILED!KnC: Frequency change FAILED!
KnC 5-0: Frequency change FAILED!KnC: Frequency change FAILED!
KnC 5-1: Frequency change FAILED!KnC: Frequency change FAILED!
KnC 5-2: Frequency change FAILED!KnC: Frequency change FAILED!
KnC 5-3: Frequency change FAILED!i2c_smbus_read_word_data failed: addr 0xD0
i2c_smbus_read_byte_data failed: addr 0x98
i2c_smbus_read_word_data failed: addr 0xD0
i2c_smbus_read_byte_data failed: addr 0x98
i2c_smbus_read_word_data failed: addr 0xD0
i2c_smbus_read_byte_data failed: addr 0x98
i2c_smbus_read_word_data failed: addr 0xD0
i2c_smbus_read_byte_data failed: addr 0x98
i2c_smbus_read_word_data failed: addr 0xD0
i2c_smbus_read_byte_data failed: addr 0x98
i2c_smbus_read_word_data failed: addr 0xD0
i2c_smbus_read_byte_data failed: addr 0x98
i2c_smbus_read_word_data failed: addr 0xD0
i2c_smbus_read_byte_data failed: addr 0x98
i2c_smbus_read_word_data failed: addr 0xD0
i2c_smbus_read_byte_data failed: addr 0x98
i2c_smbus_read_word_data failed: addr 0xD0
i2c_smbus_read_byte_data failed: addr 0x98
i2c_smbus_read_word_data failed: addr 0xD0
i2c_smbus_read_byte_data failed: addr 0x98
i2c_smbus_read_word_data failed: addr 0xD0
i2c_smbus_read_byte_data failed: addr 0x98
i2c_smbus_read_word_data failed: addr 0xD0
i2c_smbus_read_byte_data failed: addr 0x98
i2c_smbus_read_word_data failed: addr 0xD0
i2c_smbus_read_byte_data failed: addr 0x98
i2c_smbus_read_word_data failed: addr 0xD0
i2c_smbus_read_byte_data failed: addr 0x98
i2c_smbus_read_word_data failed: addr 0xD0
i2c_smbus_read_byte_data failed: addr 0x98
i2c_smbus_read_word_data failed: addr 0xD0
i2c_smbus_read_byte_data failed: addr 0x98
i2c_smbus_read_word_data failed: addr 0xD0
i2c_smbus_read_byte_data failed: addr 0x98
i2c_smbus_read_word_data failed: addr 0xD0
i2c_smbus_read_byte_data failed: addr 0x98
i2c_smbus_read_word_data failed: addr 0xD0
i2c_smbus_read_byte_data failed: addr 0x98
i2c_smbus_read_word_data failed: addr 0xD0
i2c_smbus_read_byte_data failed: addr 0x98
i2c_smbus_read_word_data failed: addr 0xD0
i2c_smbus_read_byte_data failed: addr 0x98
i2c_smbus_read_word_data failed: addr 0xD0
i2c_smbus_read_byte_data failed: addr 0x98
i2c_smbus_read_word_data failed: addr 0xD0
i2c_smbus_read_byte_data failed: addr 0x98
i2c_smbus_read_word_data failed: addr 0xD0
i2c_smbus_read_byte_data failed: addr 0x98
i2c_smbus_read_word_data failed: addr 0xD0
i2c_smbus_read_byte_data failed: addr 0x98
i2c_smbus_read_word_data failed: addr 0xD0
i2c_smbus_read_byte_data failed: addr 0x98
i2c_smbus_read_word_data failed: addr 0xD0
i2c_smbus_read_byte_data failed: addr 0x98
i2c_smbus_read_word_data failed: addr 0xD0
i2c_smbus_read_byte_data failed: addr 0x98
i2c_smbus_read_word_data failed: addr 0xD0
i2c_smbus_read_byte_data failed: addr 0x98
i2c_smbus_read_word_data failed: addr 0xD0
i2c_smbus_read_byte_data failed: addr 0x98
i2c_smbus_read_word_data failed: addr 0xD0
i2c_smbus_read_byte_data failed: addr 0x98
i2c_smbus_read_word_data failed: addr 0xD0
i2c_smbus_read_byte_data failed: addr 0x98
{
"asic_1_voltage": {
        "die1": "",
        "die2": "",
        "die3": "",
        "die4": ""
},
"asic_1_frequency": {
        "die1": "",
        "die2": "",
        "die3": "",
        "die4": ""
},
"asic_2_voltage": {
        "die1": "",
        "die2": "",
        "die3": "",
        "die4": ""
},
"asic_2_frequency": {
        "die1": "325",
        "die2": "300",
        "die3": "300",
        "die4": "325"
},
"asic_3_voltage": {
        "die1": "",
        "die2": "",
        "die3": "",
        "die4": ""
},
"asic_3_frequency": {
        "die1": "325",
        "die2": "325",
        "die3": "325",
        "die4": "325"
},
"asic_4_voltage": {
        "die1": "-0.0366",
        "die2": "-0.0366",
        "die3": "-0.0366",
        "die4": "-0.0366"
},
"asic_4_frequency": {
        "die1": "100",
        "die2": "100",
        "die3": "100",
        "die4": "100"
},
"asic_5_voltage": {
        "die1": "",
        "die2": "",
        "die3": "",
        "die4": ""
},
"asic_5_frequency": {
        "die1": "300",
        "die2": "300",
        "die3": "300",
        "die4": ""
},
"asic_6_voltage": {
        "die1": "",
        "die2": "",
        "die3": "",
        "die4": ""
},
"asic_6_frequency": {
        "die1": "325",
        "die2": "",
        "die3": "",
        "die4": "325"
}
}

lightfoot

legendary

Activity: 3164

Merit: 2258

I fix broken miners. And make holes in teeth :-)

Quote from: FineHash link=topic=1283859.msg14079070#msg14079070 date=1456978229\
Here is a bfgminer screenshot:
[img

http://i.imgur.com/e17mQIf.png[/img]

Here is a pic of the bottom of the board:

Now here is a crazy detail... depending on how tight/loose the heat sink is cinched, the entire cube will/won't appear on the (gentarkin) firmware advanced settings page. So in other words, if I screw it on normally, no cube or dies appear at all. If I crank it down a bit more, I see dies but no hashing. Possible short?

What do you get with the waas command? And how does bfgminer look when cranked down (don't do this too hard).

Based on the condition of the back of the board my guess is that either it was run like super hell or the heat sink was bad/loose and the top dies burned the board. That takes more heat than I can generate with pre-heat and my air tools, so it's a lot of heat. Enough to melt the solder and make a mess under the board.

A reflow *might* help, but those are dicey. If you want me to try let me know and send it in. I'll give it a shot, but my guess is that's the root of the problem.

Anyone found a source for huge .6mm pitch reballing stencils?

FineHash

newbie

Activity: 14

Merit: 0

Quote from: lightfoot on March 02, 2016, 10:13:29 PM

Quote from: FineHash on March 02, 2016, 06:49:25 PM

I have a cube (board) that looks identical to this pic. Sent PM, could greatly use your assistance if and when you might have time.

It is awake, but lazy and unmotivated to do any work

http://i.imgur.com/iHxOgVR.png

Can compensate you in electronic currency and compliments, and/or beer if you're close enough.

Hate to say it but most of my success is on boards that are blown up. Either incinerated, blown supplies, and the like. The titan chips are finicky, have you tried Tarkin's firmware?

Anyway when you log into the board using ssh as user pi and password whatever your password is and type screen -r what do you see?

C

Too bad about this "newbie" label I have...

I am very familiar with bfgminer, linux, etc.

Here is a bfgminer screenshot:
http://i.imgur.com/e17mQIf.png

Here is a pic of the bottom of the board:
http://i.imgur.com/bsqMHSX.jpg

Now here is a crazy detail... depending on how tight/loose the heat sink is cinched, the entire cube will/won't appear on the (gentarkin) firmware advanced settings page. So in other words, if I screw it on normally, no cube or dies appear at all. If I crank it down a bit more, I see dies but no hashing. Possible short?

lightfoot

legendary

Activity: 3164

Merit: 2258

I fix broken miners. And make holes in teeth :-)

Quote from: FineHash on March 02, 2016, 06:49:25 PM

I have a cube (board) that looks identical to this pic. Sent PM, could greatly use your assistance if and when you might have time.

It is awake, but lazy and unmotivated to do any work

Can compensate you in electronic currency and compliments, and/or beer if you're close enough.

Hate to say it but most of my success is on boards that are blown up. Either incinerated, blown supplies, and the like. The titan chips are finicky, have you tried Tarkin's firmware?

Anyway when you log into the board using ssh as user pi and password whatever your password is and type screen -r what do you see?

C

FineHash

newbie

Activity: 14

Merit: 0

I have a cube (board) that looks identical to this pic. Sent PM, could greatly use your assistance if and when you might have time.

It is awake, but lazy and unmotivated to do any work

http://i.imgur.com/iHxOgVR.png

Can compensate you in electronic currency and compliments, and/or beer if you're close enough.

lightfoot

legendary

Activity: 3164

Merit: 2258

I fix broken miners. And make holes in teeth :-)

Thank you! At the moment it looks like this repaired unit hashes pretty well at 60 or so, will be contacting the user to discuss. I think it's a pretty neat repair, all things considered :-)

And on another Titan note, got one in that was dead shorted on the 12v side, turns out the person took off the heat sink and didn't re-apply paste when putting it back on. The paste KNC uses is a one time thing that hardens like a ROCK. The result is this:

And a DC-DC converter that blows its' FETs (you can see the worst heat damage is over in that corner of the board), which causes +12 to hit the hashing die which if the die wasn't already fried, ends the die. Fortunately the other three were fix-able and the unit is back to hashing at a solid 60mh.

On to the next thing. Still working on trying to fix a unit that hashes on only one engine (I think this was from the factory, it already has two bypassed) and thinking about how to clear these shorts on line 6.

Topic: Hacking KNC Titan / Jupiter / Neptune miners back to life. Why not? - page 29. (Read 76793 times)