 Show Posts
|
|
Pages: [1]
|
Tell please airdrop still active and I can to accept participation in this ?
Yes, you can participate and get some tokens. Especially until the sales rounds have started. So now it will be the most profitable. |
|
|
|
Tell please airdrop still active and I can to accept participation in this ?
The second round is still running and you can take part. This is a good opportunity to get tokens while sales have not yet started. And if you invite friends you can get a very good reward and help to form a huge community of green project. |
|
|
|
|
Please tell me what will be the minimum contribution to the project on November 1? I would like to buy tokens with the maximum discount.
|
|
|
|
Now the project looks interesting and it is definitely worth a look I think. I will continue to follow the news from the team.
I will follow this project and I think that I will be able to buy tokens tokens in the near future. I think that a 20% discount will be a good motivation. |
|
|
|
I could see things not getting updated being a sd card issue, if the pattern of LEDs is the same on the dead board as the others then you don't have a blown chip, normally there drastically different or not at all, you said green/red LEDs so I am guessing the boards are green, check cables , swap two of them and see if the dead board moves or stays the same, if it moves then maybe a bad cable if the same then might be a messed up board, most trouble shooting steps at this point are very advanced, requires probing stuff and such. I don't know if I would buy a new board really the cost vs/ the payback is going to be a bit off .
Ok, so after some troubleshooting with no luck, I decided to let it be for a few days. Suddenly tonight I had another board basically die. This has to be a power supply issue, right? Should I try switching out the 6+2 pin PCI cables? Or switching around where they're plugged in? PSU is fully modular, so I have a few open plugs to try, but I'd imagine if one part of the power rail fails, it all does... I'm starting to get really worried that I dropped over $900 on a rig that is just falling apart, and then another $280 for a PSU that I got no reimbursement for from Zoomhash, but I'm holding out hope that it's just the PSU. Is there a way I can test the output of the PSU? Having 2 boards die off of a 1300W gold rated output shouldn't happen. Hoping for a very fast response before I throw this thing off of a cliff. |
|
|
|
Thanks for the tip, mxnsch. I'll definitely look into tweaking some of the values in the future. I did figure out what the problem was, though. Turns out the outlet I had the miner plugged into died, but not completely. Once I turned the miner off and unplugged it, I tested the outlet with a multimeter. The output was, and currently still is, 15VAC. Something that's also a bit more troubling, all other outlets in half of my house are now over-volting, including ones on the same circuit as the dead outlet. All are reading between 155-165VAC, which I know is a dangerous thing when it comes to sensitive electronics. They also have a higher amperage than my multimeter can read, which has a cap of 20A. I'm 99% certain that the miner did NOT cause this problem, but rather was the first thing to be 'punished' by the problem.
But with the good news comes bad news... Plugged the miner back into a stable circuit, turned it on, and cs3 (Board #4) is dead. Board 4 is the one that hit 101*C, which I would imagine any piece of equipment hitting the boiling point means the kiss of death. I'm planning on opening up the rig tomorrow to see if there's any visual damage, as well as reconnecting all of the cables. Will also reflash the SD card just in case. But, as it stands right now, the board is dead as far as I can tell. It always ran hot to begin with, averaging close to 6*C hotter than the other 5 boards, even with super cold winter air. Probably little to no thermal paste on there is my theory...
Last little question, but does anyone know if replacement boards are sold anywhere? Or if anyone, most likely someone on this forum, offers repairs? I don't know the specifics of the multiple ways heat can damage a board, so I'm not sure if it's repairable. Poor old rig has been mine for less than 3 months and this happens lol
Anyways, thanks for your help guys. I'll check back in a few days if I find out anything interesting.
Well at least you got some answers, as for bad boards normally they will blow a chip and then it is done, they cant communicate anymore , I have fixed a few but most of the time it takes more than one chip. As far as thermal paste there problems with all the ones I worked on I tore them all down for some unknown reason on the bottom there was thermal paste on a thermal pad which is worse , I put paste on the bottoms of the board under the chips and on top of them helped a lot with temps and just got rid of the pads all together. I think you can get replacement boards from zoomhash they were like $85 when I contacted them which means like a bit of time to pay it off. I wouldnt bother with a reflash, are the LEDs different on the dead board? mjgraham, initially the board had no LEDs at all, but starting today the board 'woke up' and now shows signs of life. The 5 working boards all have solid green/red lights while hashing, and the dead board just continues to flash the LEDs. It's almost as if the Pi isn't recognizing it, or it could be to what you mentioned where once the board blows a chip, it just stops communicating. I had a theory that perhaps the board might not be receiving sufficient power. When the problem first started, I received this message for all 6 boards, which were all "on" but being powered by the dead power outlet: [2016-03-27 18:48:49] ACK(cs0) timeout:cmd_POWER_ON_BCAST-0.0553s
[2016-03-27 18:48:49] SPI(cs0) no device
[2016-03-27 18:48:49] ACK(cs0) timeout:cmd_RESET_BCAST - 0.27 ms
[2016-03-27 18:48:49] Failure(cs1)(2): missing ACK for cmd 0x02
[2016-03-27 18:48:49] ACK(cs1) timeout:cmd_POWER_ON_BCAST-0.0575s
[2016-03-27 18:48:49] SPI(cs1) no device
[2016-03-27 18:48:49] ACK(cs1) timeout:cmd_RESET_BCAST - 0.27 ms
[2016-03-27 18:48:49] Failure(cs2)(2): missing ACK for cmd 0x02
[2016-03-27 18:48:49] ACK(cs2) timeout:cmd_POWER_ON_BCAST-0.0487s
[2016-03-27 18:48:49] SPI(cs2) no device
[2016-03-27 18:48:49] ACK(cs2) timeout:cmd_RESET_BCAST - 0.27 ms
[2016-03-27 18:48:49] Failure(cs3)(2): missing ACK for cmd 0x02
[2016-03-27 18:48:49] ACK(cs3) timeout:cmd_POWER_ON_BCAST-0.0499s
[2016-03-27 18:48:49] SPI(cs3) no device
[2016-03-27 18:48:49] ACK(cs3) timeout:cmd_RESET_BCAST - 0.27 ms
[2016-03-27 18:48:49] Failure(cs4)(2): missing ACK for cmd 0x02
[2016-03-27 18:48:49] ACK(cs4) timeout:cmd_POWER_ON_BCAST-0.0489s
[2016-03-27 18:48:49] SPI(cs4) no device
[2016-03-27 18:48:49] ACK(cs4) timeout:cmd_RESET_BCAST - 0.27 ms
[2016-03-27 18:48:49] Failure(cs5)(2): missing ACK for cmd 0x02
[2016-03-27 18:48:49] ACK(cs5) timeout:cmd_POWER_ON_BCAST-0.0509s
[2016-03-27 18:48:49] SPI(cs5) no device
[2016-03-27 18:48:49] ACK(cs5) timeout:cmd_RESET_BCAST - 0.27 ms After fixing the power problem, 5 boards work, but board #4 (cs3) still gives that exact message. I'm also starting to think that I should reflash the SD because ever since the problem started a week ago, the graphs on the main page refuse to repopulate. All 8 graphs show Saturday (March 26) at 6:00 PM to Sunday at 6:00 PM, right when the temperatures hit 100*C. This is also the case for the 'Historical Statistics', 'Logs - Messages', and 'Logs - Syslog' pages. In my eyes, I see 3 variables that could be the problem: corrupted SD, corrupted Pi/ribbon cable to cs3, or a dead board altogether. However, if the board is dead, that doesn't explain the non-responsiveness of the logging system. Thanks again mjgraham. |
|
|
|
|
Thanks for the tip, mxnsch. I'll definitely look into tweaking some of the values in the future. I did figure out what the problem was, though. Turns out the outlet I had the miner plugged into died, but not completely. Once I turned the miner off and unplugged it, I tested the outlet with a multimeter. The output was, and currently still is, 15VAC. Something that's also a bit more troubling, all other outlets in half of my house are now over-volting, including ones on the same circuit as the dead outlet. All are reading between 155-165VAC, which I know is a dangerous thing when it comes to sensitive electronics. They also have a higher amperage than my multimeter can read, which has a cap of 20A. I'm 99% certain that the miner did NOT cause this problem, but rather was the first thing to be 'punished' by the problem.
But with the good news comes bad news... Plugged the miner back into a stable circuit, turned it on, and cs3 (Board #4) is dead. Board 4 is the one that hit 101*C, which I would imagine any piece of equipment hitting the boiling point means the kiss of death. I'm planning on opening up the rig tomorrow to see if there's any visual damage, as well as reconnecting all of the cables. Will also reflash the SD card just in case. But, as it stands right now, the board is dead as far as I can tell. It always ran hot to begin with, averaging close to 6*C hotter than the other 5 boards, even with super cold winter air. Probably little to no thermal paste on there is my theory...
Last little question, but does anyone know if replacement boards are sold anywhere? Or if anyone, most likely someone on this forum, offers repairs? I don't know the specifics of the multiple ways heat can damage a board, so I'm not sure if it's repairable. Poor old rig has been mine for less than 3 months and this happens lol
Anyways, thanks for your help guys. I'll check back in a few days if I find out anything interesting.
|
|
|
|
Hi all, I've posted before on the Ultra Under-overclock thread by emdje, but I thought I should post here since I'm using this image on my A2 Mega. Bought it this past January, finally got everything set up and working after replacing the power supply, and it's been working smoothly for about 3 months. Tonight, however, I received one of the automated emails from Mining Rig Rentals saying the rig is offline, which shouldn't be the case. I pulled up the control interface on my computer and saw something a bit unsettling. The cgminer log kept repeating the same message which was followed 10 seconds later with a forced restart, which kept repeating until I stopped the miner. This is the most recent display in cgminer: [2016-03-27 18:48:45] Started cgminer 3.9.0 innosilicon-12chip-v0p5
[2016-03-27 18:48:45] Run Reset=1
[2016-03-27 18:48:45] ST MCU hardware reset start
[2016-03-27 18:48:49] SPI Speed 4000 kHz
[2016-03-27 18:48:49] ST MCU - Enable (Pre-header)
[2016-03-27 18:48:49] Run temperature 35C
[2016-03-27 18:48:49] A1 = 1200,7
[2016-03-27 18:48:49] A1 PLL Clock = 1200MHz
[2016-03-27 18:48:49] A1 = 1200,7
[2016-03-27 18:48:49] A1 PLL Clock = 1200MHz
[2016-03-27 18:48:49] A1 = 1200,7
[2016-03-27 18:48:49] A1 PLL Clock = 1200MHz
[2016-03-27 18:48:49] A1 = 1200,7
[2016-03-27 18:48:49] A1 PLL Clock = 1200MHz
[2016-03-27 18:48:49] A1 = 1200,7
[2016-03-27 18:48:49] A1 PLL Clock = 1200MHz
[2016-03-27 18:48:49] A1 = 1200,7
[2016-03-27 18:48:49] A1 PLL Clock = 1200MHz
[2016-03-27 18:48:49] AUTO GPIO CS
[2016-03-27 18:48:49] Failure(cs0)(2): missing ACK for cmd 0x02
[2016-03-27 18:48:49] ACK(cs0) timeout:cmd_POWER_ON_BCAST-0.0553s
[2016-03-27 18:48:49] SPI(cs0) no device
[2016-03-27 18:48:49] ACK(cs0) timeout:cmd_RESET_BCAST - 0.27 ms
[2016-03-27 18:48:49] Failure(cs1)(2): missing ACK for cmd 0x02
[2016-03-27 18:48:49] ACK(cs1) timeout:cmd_POWER_ON_BCAST-0.0575s
[2016-03-27 18:48:49] SPI(cs1) no device
[2016-03-27 18:48:49] ACK(cs1) timeout:cmd_RESET_BCAST - 0.27 ms
[2016-03-27 18:48:49] Failure(cs2)(2): missing ACK for cmd 0x02
[2016-03-27 18:48:49] ACK(cs2) timeout:cmd_POWER_ON_BCAST-0.0487s
[2016-03-27 18:48:49] SPI(cs2) no device
[2016-03-27 18:48:49] ACK(cs2) timeout:cmd_RESET_BCAST - 0.27 ms
[2016-03-27 18:48:49] Failure(cs3)(2): missing ACK for cmd 0x02
[2016-03-27 18:48:49] ACK(cs3) timeout:cmd_POWER_ON_BCAST-0.0499s
[2016-03-27 18:48:49] SPI(cs3) no device
[2016-03-27 18:48:49] ACK(cs3) timeout:cmd_RESET_BCAST - 0.27 ms
[2016-03-27 18:48:49] Failure(cs4)(2): missing ACK for cmd 0x02
[2016-03-27 18:48:49] ACK(cs4) timeout:cmd_POWER_ON_BCAST-0.0489s
[2016-03-27 18:48:49] SPI(cs4) no device
[2016-03-27 18:48:49] ACK(cs4) timeout:cmd_RESET_BCAST - 0.27 ms
[2016-03-27 18:48:49] Failure(cs5)(2): missing ACK for cmd 0x02
[2016-03-27 18:48:49] ACK(cs5) timeout:cmd_POWER_ON_BCAST-0.0509s
[2016-03-27 18:48:49] SPI(cs5) no device
[2016-03-27 18:48:49] ACK(cs5) timeout:cmd_RESET_BCAST - 0.27 ms
[2016-03-27 18:48:49] No any A1 board I've seen in another thread that a possible reason to this might be the power supply or a bad SD card. Since I'm not the best at computer coding, especially Linux, I'm not sure how to tell what the problem is. The power supply shouldn't be a problem since I put a brand new EVGA Suprnova 1300W Gold in about 2 months ago. The SD card came with the miner, so I'm not sure about it's reliability, but it works enough that I can still pull up the interface. Also, another thing to note, right when the miner stopped working and displayed the message above, the board temperatures SKYROCKETED almost instantly. During the day they average about 52*C, but within 2 minutes of the error message, the boards (0 through 5) had temps of 68*C, 59*C, 80*C, 101*C, 97*C, and 55*C, respectively. They are receiving a strong airflow and no problem with air circulation to get rid of the heat, so I'm hoping that factor isn't a bad sign, and that it's just caused by the malfunction with the image, or whatever might be wrong. Hoping to hear back very soon with a possible solution or any ideas. Thanks |
|
|
|
|
Hey guys, just had a few quick questions about the A2 in general, and wanted to get a few opinions. I know this isn't an "A2 general support" thread, but everywhere else I've looked is super sketchy, so I thought that I should try.
So I ordered an A2 110MH/s unit from Zoomhash and I got it in the mail this past Monday. Tested it out with the stock image provided on the SD card to get a general idea of an average hashrate. Had it running for about 3 hours on the "default" 1100MHz frequency, and lo and behold the PSU died while mining. I've contacted Zoomhash about getting a replacement, but I'm starting to get nervous because I haven't gotten a reply in almost 3 days. I'll still hold out hope until the end of the week, but it's looking like I'm going to be replacing the PSU on my own dime, which I'm definitely not thrilled about an extra $220 on top of the $900 already spent...
A few questions I have in regards to using the Version 3.1 or 4.0 firmware with my A2:
- During my bench testing, I received an extremely erratic "average" hashrate while mining Litecoin (slow and steady coin, wasn't on coin-changing multipool). Over the 4 hour period, my 30-minute average ranged from 65MH/s to 90MH/s, spiking back and forth between the two every 10 minutes or so. I'm not at all familiar with how Raspberry Pi's work, but could this problem have been caused by a bad (outdated/defective) image? Or possibly by the near-death power supply? The PSU it was sold with is "supposedly" a 1100W Gold unit, but I wouldn't think that running it on 1100MHz would push the PSU to die like that. I have not opened the case because doing so would "void the warranty" just in case they get back to me with a replacement.
- If I were to replace the power supply myself with a reliable unit, what range of power/efficiency rating should I go with? Based on the answer to that question, what would be the optimum frequency setting I should use with the overclock image? I'd like to get as close as I can to the *advertised* 110MH. Also, assume that the chips and boards that I have are completely untouched and not modded in any way, and I'd prefer to keep it that way since I'm not the best (or luckiest) working with electricity and circuits.
Any help would be greatly appreciated. I might as well learn about the A2 and anticipate what I need to do while I wait to get it fixed. Thanks guys!
|
|
|
|
|
