 Show Posts
|
|
Pages: [1]
|
BUMPPPPPPPPPP OFFER PRICES I DONT CARE IF THEY ARE 2$ OFFERS JUST OFFER UP !!!!!!!
BRAND NEW NEVER TOUCHED AT A DISCOUNT PRICEEEEEE COMON I KNOW SOMEONE WANTS TO BUY THESE
0.5 BTC |
|
|
|
should I post it on Ebay?
It might do pretty well on ebay, larger buying audience. |
|
|
|
|
One of my bridge boards did this, exactly as you described. I've got a new (identical) replacement pi. Would you say that the copper line repair is more of a novice or advanced job? One of my copper lines seems to have survived, the other smoked.
|
|
|
|
Greetings all. I'd like to know what you would do if your bitcoin did one of the following, as I am a little confused about what I'll do myself...
What would you do if:
Bitcoin hit $1,000,000:
Bitcoin hit $1,000 again:
Bitcoin stayed where it was:
Bitcoin became worthless, or a few cents:
And which of these do you think is most probable?
Thanks for your opinions,
-Lags
Use it to buy a coin that doesn't have transaction limit problems  |
|
|
|
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: Anyone found a source for huge .6mm pitch reballing stencils?
|
|
|
|
https://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? 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. 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"
}
}
|
|
|
|
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 Too bad about this "newbie" label I have... I am very familiar with bfgminer, linux, etc. Here is a bfgminer screenshot:  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? |
|
|
|
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. |
|
|
|
Mattzees, thank you very much for the trade! I look forward to the cubes. |
|
|
|
|
Still looking for some good used hardware.
|
|
|
|
|
Thanks for the great PMs that have been sent.
I'm still interested in offers if you have hardware to sell.
|
|
|
|
$500 minimum. So that means ask for more than $500  |
|
|
|
|
Very good question.
I think it will really depend on what the seller has, that they are willing to part with at the price that makes sense to them individually.
As we all know with cubes, factors like how many working dies make a difference. So the price that might sense for both the seller and myself will vary based on those factors.
I am not looking to make any lowball offers for hardware. For example, I would be willing to pay an absolute minimum of $500 for a working cube with 4 fully working dies. Meaning that $500 is just the starting point, let's go up from there.
Have a cube that has a dead die or two? I am interested in that as well, at a lower but very reasonable price.
|
|
|
|
|
Looking to buy KNC Titan hardware.
Please PM or post offers.
I pay all shipping and escrow fees.
|
|
|
|
|
