lightfoot
Legendary
 Offline
Activity: 3206
Merit: 2291
I fix broken miners. And make holes in teeth :-)
|
 |
November 28, 2016, 10:17:05 PM |
|
If you can get cgminer up turn on every logging option possible and post the results.
|
|
|
|
|
wheelz1200
Legendary
Offline
Activity: 3780
Merit: 1418
|
|
November 28, 2016, 11:38:37 PM |
|
v.2.0.1 is probably for the batch 3 miners. Just a guess.
Yes I can confirm this.. Ver 2.0.1 will not be compatible. This is what I was told from a reliable source Anyone want to buy my set up? I am done with this. Send me PM if interested.. What?!? Even if stable im not buying these, so first people in are screwd with shotty firmware, i actually hoped there was an honest manufacturer in this field.....i wonder when this miner manufacturer madness will stop and get some decent companies on board to make some home miners again  |
|
|
|
|
Hhampuz
Legendary
 Online
Activity: 3052
Merit: 6200
Meh.
|
|
November 28, 2016, 11:50:13 PM |
|
v.2.0.1 is probably for the batch 3 miners. Just a guess.
Yes I can confirm this.. Ver 2.0.1 will not be compatible. This is what I was told from a reliable source Anyone want to buy my set up? I am done with this. Send me PM if interested.. What?!? Even if stable im not buying these, so first people in are screwd with shotty firmware, i actually hoped there was an honest manufacturer in this field.....i wonder when this miner manufacturer madness will stop and get some decent companies on board to make some home miners again I agree with this. For far too long there has been shady makers of the hardware. They do not deliver what they promise and then have a very lackluster communication in resolving issues. Sad,, Very sad. I wish some of the BTC Asic companies would make some script miners too. I can see why they would not want to do that, but one could hope. I think I'm done following this thread. Even if things were to be resolved, I am a bit scared as to how long it has taken, even though there are plenty of customers, if not all, who are discouraged at the communication of this company. |
|
|
|
|
Eyedol-X
|
|
November 29, 2016, 12:45:25 AM |
|
Still 0 mh/s using the 1.0.3 software updated anyone have any ideas, I can see the interface, everything's correct, just no work being produced. Other miners are working as usual (albeit the drop problems). http://imgur.com/a/YeJmQI may have missed your previous post(s) Are you using batch 2 firmware on a batch 1 miner? -- That would be my first guess. What version did you have before you updated? |
|
|
|
|
FryguyUK
Legendary
Offline
Activity: 801
Merit: 1000
|
|
November 29, 2016, 01:25:16 AM |
|
Still 0 mh/s using the 1.0.3 software updated anyone have any ideas, I can see the interface, everything's correct, just no work being produced. Other miners are working as usual (albeit the drop problems). http://imgur.com/a/YeJmQI may have missed your previous post(s) Are you using batch 2 firmware on a batch 1 miner? -- That would be my first guess. What version did you have before you updated? It likely is 'batch 2' firmware as I updated it from a file found recently here... does each batch need an individual update version do you think? very confusing  |
|
|
|
|
|
Longsnowsm (OP)
|
|
November 29, 2016, 01:28:02 AM |
|
I have to admit with all the crashing, restarting, and dropped cards even my patience is starting to wear pretty thin here. This is starting to reach the point of no return for me. Either Inno gets on this and gets our existing miners fixed, or if they think they have fixed the issue with Batch 3 and they want to swap out these early miners so they can save face in the mining community. Either way they need to step up to the plate now and drive a resolution for their customers and this needs to be communicated soon to their customers. This is ridiculous.
The current state of the A4's is not acceptable. My batch 2 v1.0.3 miners are constantly restarting, and dropping cards on various pools now. Only place it is half way stable is Litecoinpool. I am on Nicehash right now and will probably go back to Litecoinpool in the hopes of earning something from these miners. No way at this rate that these will make ROI running like this. I am just waiting for the next shoe to drop and start seeing board failures. Nothing would surprise me at this point.
Inno has really let us down with the A4.
|
|
|
|
|
|
Longsnowsm (OP)
|
|
November 29, 2016, 01:30:38 AM |
|
Still 0 mh/s using the 1.0.3 software updated anyone have any ideas, I can see the interface, everything's correct, just no work being produced. Other miners are working as usual (albeit the drop problems). http://imgur.com/a/YeJmQI may have missed your previous post(s) Are you using batch 2 firmware on a batch 1 miner? -- That would be my first guess. What version did you have before you updated? It likely is 'batch 2' firmware as I updated it from a file found recently here... does each batch need an individual update version do you think? very confusing Each batch so far has its own firmware. So if you have a batch 1 miner you need the v0.0.3 firmware. If you have a batch 2 the latest is v1.0.3. Apparently the firmware and miners are not compatible and I understand batch 3 is yet again not compatible with the batch 1 or 2. So it is a REAL MESS! |
|
|
|
|
FryguyUK
Legendary
Offline
Activity: 801
Merit: 1000
|
|
November 29, 2016, 01:35:41 AM |
|
Still 0 mh/s using the 1.0.3 software updated anyone have any ideas, I can see the interface, everything's correct, just no work being produced. Other miners are working as usual (albeit the drop problems). http://imgur.com/a/YeJmQI may have missed your previous post(s) Are you using batch 2 firmware on a batch 1 miner? -- That would be my first guess. What version did you have before you updated? It likely is 'batch 2' firmware as I updated it from a file found recently here... does each batch need an individual update version do you think? very confusing Each batch so far has its own firmware. So if you have a batch 1 miner you need the v0.0.3 firmware. If you have a batch 2 the latest is v1.0.3. Apparently the firmware and miners are not compatible and I understand batch 3 is yet again not compatible with the batch 1 or 2. So it is a REAL MESS! guess the easy question is anyone know where to find that original batch 1 boot file to mount? thanks for the help so far peeps Don't be too down beaten chuck. Even with the dropped blades the money might be half as expected but it should still reach the ROI in a year instead of 6 months. 1 year is still amazing for any ROI and it's all free money after that. Also the problems with pools might be their side if they're the autoswitching one's as I've been discussing with clevermining. Keep the faith! |
|
|
|
|
|
dogjunior
|
|
November 29, 2016, 10:22:29 PM |
|
Still 0 mh/s using the 1.0.3 software updated anyone have any ideas, I can see the interface, everything's correct, just no work being produced. Other miners are working as usual (albeit the drop problems). http://imgur.com/a/YeJmQI may have missed your previous post(s) Are you using batch 2 firmware on a batch 1 miner? -- That would be my first guess. What version did you have before you updated? It likely is 'batch 2' firmware as I updated it from a file found recently here... does each batch need an individual update version do you think? very confusing Each batch so far has its own firmware. So if you have a batch 1 miner you need the v0.0.3 firmware. If you have a batch 2 the latest is v1.0.3. Apparently the firmware and miners are not compatible and I understand batch 3 is yet again not compatible with the batch 1 or 2. So it is a REAL MESS! guess the easy question is anyone know where to find that original batch 1 boot file to mount? thanks for the help so far peeps Don't be too down beaten chuck. Even with the dropped blades the money might be half as expected but it should still reach the ROI in a year instead of 6 months. 1 year is still amazing for any ROI and it's all free money after that. Also the problems with pools might be their side if they're the autoswitching one's as I've been discussing with clevermining. Keep the faith! Your ROI in a year assumes several things. 1) A4 Keeps running and doesn't die 2) Difficulty levels off and does not increase due to Inno flooding the market with their junk 3) LTC/Alt prices remain stable and don't go down You never know and sometimes even a blind squirrel finds a nut |
|
|
|
|
|
Eyedol-X
|
|
November 30, 2016, 01:46:48 AM |
|
I just dropped mine back to 1100mhz and 815mv in an effort to see if underclocking them will help.
Going to go all the way back to 800mhz if necessary to see where it stops. I know I can run them with 800mv at <1000mhz because mine came setup with 800mhz as default
1100mhz @ 815mv -- Dropped Card Now trying 1000mhz @ 810mv 1000mhz @ 810mv, just dropped a card less than 15 mins ago. Several restarts were observed but it made it almost 24 hours... Now trying 900mhz @ 805mv |
|
|
|
|
|
Longsnowsm (OP)
|
|
November 30, 2016, 02:45:24 AM |
|
If you can get cgminer up turn on every logging option possible and post the results.
Lightfoot, I someone here getting you some data? Or do you still need someone to try and dig something up? |
|
|
|
|
lightfoot
Legendary
Offline
Activity: 3206
Merit: 2291
I fix broken miners. And make holes in teeth :-)
|
|
November 30, 2016, 03:18:08 AM |
|
Not right yet. I just got off fixing a bunch of Titans, and porting that code to BBB has given me an appreciation for the diagnostic code in BFGMiner. Thus my question if you can get into the system on a shell console and see if screen -r will get you the cgminer or bfgminer screen.
Then the fun can begin. If someone wants to front me a crap board and controller let me know. What's the worst that can happen?
C
|
|
|
|
|
|
Longsnowsm (OP)
|
|
November 30, 2016, 03:33:01 AM |
|
Ok, I know others were asking about this earlier, but I didn't see an answer. Does anyone know what the ssh login is for the Pi?
|
|
|
|
|
|
SEGMining
|
|
November 30, 2016, 04:03:19 AM |
|
Ok, I know others were asking about this earlier, but I didn't see an answer. Does anyone know what the ssh login is for the Pi?
on the A2 it was username: pi and password: innosilicon |
SEGMINING Miner Co-Location in Vancouver, WA $75/KW/Month with VPN access to your hardware http://segmining.com |
|
|
Nowayz
Newbie
Offline
Activity: 17
Merit: 0
|
|
November 30, 2016, 09:49:38 AM
Last edit: November 30, 2016, 10:05:33 AM by Nowayz |
|
Login is pi/raspberry the problem with the log is that it displays the board drops and init of the boards but its completely random. Sometimes it doesn't even gets it to bring the board back up again. This happens on multi-pools . not so much on the litecoinpool. Diagnostics look like problems in the driver or on the spi bus. The driver is compiled with cgminer so if we do not have hands on the source code its hard to solve this without innosilicon. Greets, Nowayz Edit: Add log from cgminer with faults for those who want to see  These are on nicehash with batch 2 and version 2 software [2016-11-07 17:52:33] Started cgminer 3.9.0
[2016-11-07 17:52:33] Run Reset=1
[2016-11-07 17:52:33] ST MCU hardware reset start
[2016-11-07 17:52:37] SPI Speed 4000 kHz
[2016-11-07 17:52:37] ST MCU - Enable (Pre-header)
[2016-11-07 17:52:37] Run temperature 35C
[2016-11-07 17:52:37] A1 = 1200,7
[2016-11-07 17:52:37] A1 PLL Clock = 1200MHz
[2016-11-07 17:52:37] A1 = 1200,7
[2016-11-07 17:52:37] A1 PLL Clock = 1200MHz
[2016-11-07 17:52:37] A1 = 1200,7
[2016-11-07 17:52:37] A1 PLL Clock = 1200MHz
[2016-11-07 17:52:37] A1 = 1200,7
[2016-11-07 17:52:37] A1 PLL Clock = 1200MHz
[2016-11-07 17:52:37] A1 = 1200,7
[2016-11-07 17:52:37] A1 PLL Clock = 1200MHz
[2016-11-07 17:52:37] A1 = 1200,7
[2016-11-07 17:52:37] A1 PLL Clock = 1200MHz
[2016-11-07 17:52:37] AUTO GPIO CS
[2016-11-07 17:52:37] Failure(cs0)(2): missing ACK for cmd 0x02
[2016-11-07 17:52:37] ACK(cs0) timeout:cmd_POWER_ON_BCAST-0.0625s
[2016-11-07 17:52:40] Failure(cs0)(2): missing ACK for cmd 0x04
[2016-11-07 17:52:40] ACK(cs0) timeout:cmd_RESET_BCAST - 0.61 ms
[2016-11-07 17:52:40] Failure(cs1)(2): missing ACK for cmd 0x02
[2016-11-07 17:52:40] ACK(cs1) timeout:cmd_POWER_ON_BCAST-0.0573s
[2016-11-07 17:52:43] Failure(cs1)(2): missing ACK for cmd 0x04
[2016-11-07 17:52:43] ACK(cs1) timeout:cmd_RESET_BCAST - 0.65 ms
[2016-11-07 17:52:43] spidev0.0(cs2): Found 20 A2 chips
[2016-11-07 17:52:43] Found chip 1 with 100 active cores
[2016-11-07 17:52:43] Found chip 2 with 100 active cores
[2016-11-07 17:52:43] Found chip 3 with 100 active cores
[2016-11-07 17:52:43] Found chip 4 with 100 active cores
[2016-11-07 17:52:43] Found chip 5 with 100 active cores
[2016-11-07 17:52:43] Found chip 6 with 100 active cores
[2016-11-07 17:52:43] Found chip 7 with 100 active cores
[2016-11-07 17:52:43] Found chip 8 with 100 active cores
[2016-11-07 17:52:43] Found chip 9 with 100 active cores
[2016-11-07 17:52:43] Found chip 10 with 100 active cores
[2016-11-07 17:52:43] Found chip 11 with 100 active cores
[2016-11-07 17:52:43] Found chip 12 with 100 active cores
[2016-11-07 17:52:43] Found chip 13 with 100 active cores
[2016-11-07 17:52:43] Found chip 14 with 100 active cores
[2016-11-07 17:52:43] Found chip 15 with 100 active cores
[2016-11-07 17:52:43] Found chip 16 with 100 active cores
[2016-11-07 17:52:43] Found chip 17 with 100 active cores
[2016-11-07 17:52:43] Found chip 18 with 100 active cores
[2016-11-07 17:52:43] Found chip 19 with 100 active cores
[2016-11-07 17:52:43] Found chip 20 with 100 active cores
[2016-11-07 17:52:43] Found 20 chips with total 2000 active cores
[2016-11-07 17:52:43] PI(cs5) match the cg and dr
[2016-11-07 17:52:43] SPI(cs2) A1_SetA1Vol
[2016-11-07 17:52:46] spidev0.0(cs3): Found 20 A2 chips
[2016-11-07 17:52:46] Found chip 1 with 100 active cores
[2016-11-07 17:52:46] Found chip 2 with 100 active cores
[2016-11-07 17:52:46] Found chip 3 with 100 active cores
[2016-11-07 17:52:46] Found chip 4 with 100 active cores
[2016-11-07 17:52:46] Found chip 5 with 100 active cores
[2016-11-07 17:52:46] Found chip 6 with 100 active cores
[2016-11-07 17:52:46] Found chip 7 with 100 active cores
[2016-11-07 17:52:46] Found chip 8 with 100 active cores
[2016-11-07 17:52:46] Found chip 9 with 100 active cores
[2016-11-07 17:52:46] Found chip 10 with 100 active cores
[2016-11-07 17:52:46] Found chip 11 with 100 active cores
[2016-11-07 17:52:46] Found chip 12 with 100 active cores
[2016-11-07 17:52:46] Found chip 13 with 100 active cores
[2016-11-07 17:52:46] Found chip 14 with 100 active cores
[2016-11-07 17:52:46] Found chip 15 with 100 active cores
[2016-11-07 17:52:46] Found chip 16 with 100 active cores
[2016-11-07 17:52:46] Found chip 17 with 100 active cores
[2016-11-07 17:52:46] Found chip 18 with 100 active cores
[2016-11-07 17:52:46] Found chip 19 with 100 active cores
[2016-11-07 17:52:46] Found chip 20 with 100 active cores
[2016-11-07 17:52:46] Found 20 chips with total 2000 active cores
[2016-11-07 17:52:46] PI(cs5) match the cg and dr
[2016-11-07 17:52:46] SPI(cs3) A1_SetA1Vol
[2016-11-07 17:52:49] spidev0.0(cs4): Found 20 A2 chips
[2016-11-07 17:52:49] Found chip 1 with 98 active cores
[2016-11-07 17:52:49] Found chip 2 with 99 active cores
[2016-11-07 17:52:49] Found chip 3 with 99 active cores
[2016-11-07 17:52:49] Found chip 4 with 99 active cores
[2016-11-07 17:52:49] Found chip 5 with 99 active cores
[2016-11-07 17:52:49] Found chip 6 with 94 active cores
[2016-11-07 17:52:49] Found chip 7 with 99 active cores
[2016-11-07 17:52:49] Found chip 8 with 97 active cores
[2016-11-07 17:52:49] Found chip 9 with 98 active cores
[2016-11-07 17:52:49] Found chip 10 with 99 active cores
[2016-11-07 17:52:49] Found chip 11 with 99 active cores
[2016-11-07 17:52:49] Found chip 12 with 98 active cores
[2016-11-07 17:52:49] Found chip 13 with 98 active cores
[2016-11-07 17:52:49] Found chip 14 with 99 active cores
[2016-11-07 17:52:49] Found chip 15 with 99 active cores
[2016-11-07 17:52:49] Found chip 16 with 95 active cores
[2016-11-07 17:52:49] Found chip 17 with 99 active cores
[2016-11-07 17:52:49] Found chip 18 with 99 active cores
[2016-11-07 17:52:49] Found chip 19 with 99 active cores
[2016-11-07 17:52:49] Found chip 20 with 96 active cores
[2016-11-07 17:52:49] Found 20 chips with total 1962 active cores
[2016-11-07 17:52:49] PI(cs5) match the cg and dr
[2016-11-07 17:52:50] SPI(cs4) A1_SetA1Vol
[2016-11-07 17:52:50] Failure(cs5)(2): missing ACK for cmd 0x02
[2016-11-07 17:52:50] ACK(cs5) timeout:cmd_POWER_ON_BCAST-0.0548s
[2016-11-07 17:52:53] Failure(cs5)(2): missing ACK for cmd 0x04
[2016-11-07 17:52:53] ACK(cs5) timeout:cmd_RESET_BCAST - 0.71 ms
[2016-11-07 17:52:53] A2 boards=3, active cores=5962, speed=427.12M
[2016-11-07 17:52:53] Tan total_devices : 3
[2016-11-07 17:52:53] Tan cs_cnt_error
after some time cs2 drops and comes back ..
[2016-11-07 17:56:17] spidev0.0(cs2): Found 20 A2 chips
[2016-11-07 17:56:17] Found chip 1 with 100 active cores
[2016-11-07 17:56:17] Found chip 2 with 100 active cores
[2016-11-07 17:56:17] Found chip 3 with 100 active cores
[2016-11-07 17:56:17] Found chip 4 with 100 active cores
[2016-11-07 17:56:17] Found chip 5 with 100 active cores
[2016-11-07 17:56:17] Found chip 6 with 100 active cores
[2016-11-07 17:56:17] Found chip 7 with 100 active cores
[2016-11-07 17:56:17] Found chip 8 with 100 active cores
[2016-11-07 17:56:17] Found chip 9 with 100 active cores
[2016-11-07 17:56:17] Found chip 10 with 100 active cores
[2016-11-07 17:56:17] Found chip 11 with 100 active cores
[2016-11-07 17:56:17] Found chip 12 with 100 active cores
[2016-11-07 17:56:17] Found chip 13 with 100 active cores
[2016-11-07 17:56:17] Found chip 14 with 100 active cores
[2016-11-07 17:56:17] Found chip 15 with 100 active cores
[2016-11-07 17:56:17] Found chip 16 with 100 active cores
[2016-11-07 17:56:17] Found chip 17 with 100 active cores
[2016-11-07 17:56:17] Found chip 18 with 100 active cores
[2016-11-07 17:56:17] Found chip 19 with 100 active cores
[2016-11-07 17:56:17] Found chip 20 with 100 active cores
[2016-11-07 17:56:17] Found 20 chips with total 2000 active cores
[2016-11-07 17:56:18] Accepted 0880d755 Diff 7.71K/4096 BA2 2 pool 0
[2016-11-07 17:56:18] Accepted 0880d755 Diff 7.71K/4096 BA2 2
[2016-11-07 17:56:18] Accepted 01f39c93 Diff 33.6K/4096 BA2 1 pool 0
[2016-11-07 17:56:18] Accepted 01f39c93 Diff 33.6K/4096 BA2 1
[2016-11-07 17:56:18] chip(cs3) 14: invalid nonce 0x0e12ca00
[2016-11-07 17:56:20] chip(cs2) 10: invalid nonce 0x41f71900
(5s):182.1M (avg):200.0Mh/s | A:626688 R:0 WU:180472.5/m
And cs3 drops and comes back
[2016-11-07 17:57:40] Reinit board (cs3)
[2016-11-07 17:57:40] spidev0.0(cs3): Found 20 A2 chips
[2016-11-07 17:57:40] Found chip 1 with 100 active cores
[2016-11-07 17:57:40] Found chip 2 with 100 active cores
[2016-11-07 17:57:40] Found chip 3 with 100 active cores
[2016-11-07 17:57:40] Found chip 4 with 100 active cores
[2016-11-07 17:57:40] Found chip 5 with 100 active cores
[2016-11-07 17:57:40] Found chip 6 with 100 active cores
[2016-11-07 17:57:40] Found chip 7 with 100 active cores
[2016-11-07 17:57:40] Found chip 8 with 100 active cores
[2016-11-07 17:57:40] Found chip 9 with 100 active cores
[2016-11-07 17:57:40] Found chip 10 with 100 active cores
[2016-11-07 17:57:40] Found chip 11 with 100 active cores
[2016-11-07 17:57:40] Found chip 12 with 100 active cores
[2016-11-07 17:57:40] Found chip 13 with 100 active cores
[2016-11-07 17:57:40] Found chip 14 with 100 active cores
[2016-11-07 17:57:40] Found chip 15 with 100 active cores
[2016-11-07 17:57:40] Found chip 16 with 100 active cores
[2016-11-07 17:57:40] Found chip 17 with 100 active cores
[2016-11-07 17:57:40] Found chip 18 with 100 active cores
[2016-11-07 17:57:40] Found chip 19 with 100 active cores
[2016-11-07 17:57:40] Found chip 20 with 100 active cores
[2016-11-07 17:57:40] Found 20 chips with total 2000 active cores
[2016-11-07 17:57:43] Accepted 0e258aec Diff 4.63K/4096 BA2 2 pool 0
[2016-11-07 17:57:43] Accepted 0e258aec Diff 4.63K/4096 BA2 2
(5s):192.2M (avg):200.0Mh/s | A:864256 R:0 WU:179076.9/m
And cs4 comes back but other board has dropped
[2016-11-07 17:58:36] spidev0.0(cs4): Found 20 A2 chips
[2016-11-07 17:58:36] Found chip 1 with 98 active cores
[2016-11-07 17:58:36] Found chip 2 with 99 active cores
[2016-11-07 17:58:36] Found chip 3 with 99 active cores
[2016-11-07 17:58:36] Found chip 4 with 99 active cores
[2016-11-07 17:58:36] Found chip 5 with 99 active cores
[2016-11-07 17:58:36] Found chip 6 with 94 active cores
[2016-11-07 17:58:36] Found chip 7 with 99 active cores
[2016-11-07 17:58:36] Found chip 8 with 97 active cores
[2016-11-07 17:58:36] Found chip 9 with 98 active cores
[2016-11-07 17:58:36] Found chip 10 with 99 active cores
[2016-11-07 17:58:36] Found chip 11 with 99 active cores
[2016-11-07 17:58:36] Found chip 12 with 98 active cores
[2016-11-07 17:58:36] Found chip 13 with 98 active cores
[2016-11-07 17:58:36] Found chip 14 with 99 active cores
[2016-11-07 17:58:36] Found chip 15 with 99 active cores
[2016-11-07 17:58:36] Found chip 16 with 95 active cores
[2016-11-07 17:58:36] Found chip 17 with 99 active cores
[2016-11-07 17:58:36] Found chip 18 with 99 active cores
[2016-11-07 17:58:36] Found chip 19 with 99 active cores
[2016-11-07 17:58:36] Found chip 20 with 96 active cores
[2016-11-07 17:58:36] Found 20 chips with total 1962 active cores
[2016-11-07 17:58:38] chip(cs2) 4: invalid nonce 0xa3b1e700
[2016-11-07 17:58:38] Accepted 031d35c4 Diff 21K/8192 BA2 0 pool 0
[2016-11-07 17:58:38] Accepted 031d35c4 Diff 21K/8192 BA2 0
[2016-11-07 17:58:39] Accepted a932e209 Diff 99.2K/8192 BA2 1 pool 0
[2016-11-07 17:58:39] Accepted a932e209 Diff 99.2K/8192 BA2 1
(5s):166.0M (avg):197.9Mh/s | A:1101824 R:0 WU:191204.7/m
|
|
|
|
|
|
Eyedol-X
|
|
November 30, 2016, 12:22:39 PM |
|
I just dropped mine back to 1100mhz and 815mv in an effort to see if underclocking them will help.
Going to go all the way back to 800mhz if necessary to see where it stops. I know I can run them with 800mv at <1000mhz because mine came setup with 800mhz as default
1100mhz @ 815mv -- Dropped Card Now trying 1000mhz @ 810mv 1000mhz @ 810mv, just dropped a card less than 15 mins ago. Several restarts were observed but it made it almost 24 hours... Now trying 900mhz @ 805mv 900mhz @ 805mv dropped a card about 5 hours ago. So I guess that settles it, underclocking these things makes no difference. |
|
|
|
|
lightfoot
Legendary
Offline
Activity: 3206
Merit: 2291
I fix broken miners. And make holes in teeth :-)
|
|
November 30, 2016, 12:35:49 PM |
|
Hm. How about when you turn on full diagnostics in CGMiner. Before the board resets, do you ever see anything odd like got Nonce for invalid hash, or stuff like that which might indicate chip cores are yammering on top of each other?
When the dies come back do you once again get invalid nonces coming out of them (meaning the dies reported stale work) or do they just pick up and hash (indicating the dies lost power and reset their buffers)
Any links to close up pictures of a board? How do they have the power laid out between the DC-DC's and the chips?
Edit: I see the nonce error. Interesting. Pi's suck at SPI by the way, they should have used beaglebones. This points away from a power supply dc-dc issue at the moment. Hm.
|
|
|
|
|
lightfoot
Legendary
Offline
Activity: 3206
Merit: 2291
I fix broken miners. And make holes in teeth :-)
|
|
November 30, 2016, 12:44:32 PM |
|
Just for giggles, try running a bitcoin full node on the Pi and see if the miner drops a lot more. What kind of Pi are they using, fastest around or some slow slug.
|
|
|
|
|
Nowayz
Newbie
Offline
Activity: 17
Merit: 0
|
|
November 30, 2016, 02:19:18 PM |
|
Full diagnostic outputs to much information when board drops occurs once in a while. I did found a error on cs3 and short after a reinit of that board. Also it looks like it stalls the other boards as well but this might be normal as nonces display  [2016-11-30 22:11:57] Negative nonce_processed
[2016-11-30 22:11:58] BA22: invalid nonce - HW error
[2016-11-30 22:11:58] chip(cs3) 13: invalid nonce 0x5496af07
[2016-11-30 22:11:58] Negative nonce_processed
[2016-11-30 22:11:59] Job is not working from chip(cs2) 0 <-- boards stall because off board cs3 ??
[2016-11-30 22:11:59] Job is not working from chip(cs2) 1
[2016-11-30 22:11:59] Job is not working from chip(cs2) 2
[2016-11-30 22:11:59] Job is not working from chip(cs2) 4
[2016-11-30 22:11:59] Job is not working from chip(cs2) 5
[2016-11-30 22:11:59] Job is not working from chip(cs2) 7
[2016-11-30 22:11:59] Job is not working from chip(cs2) 8
[2016-11-30 22:11:59] Job is not working from chip(cs2) 9
[2016-11-30 22:11:59] Job is not working from chip(cs2) 10
[2016-11-30 22:11:59] Job is not working from chip(cs2) 12
[2016-11-30 22:11:59] Job is not working from chip(cs2) 13
[2016-11-30 22:11:59] Job is not working from chip(cs2) 14
[2016-11-30 22:11:59] Job is not working from chip(cs2) 15
[2016-11-30 22:11:59] Job is not working from chip(cs2) 16
[2016-11-30 22:11:59] Job is not working from chip(cs2) 17
[2016-11-30 22:12:00] Job is not working from chip(cs2) 18
[2016-11-30 22:12:00] Job is not working from chip(cs2) 19
[2016-11-30 22:12:00] nonces processed 20
[2016-11-30 22:12:00] nonces processed 5
[2016-11-30 22:12:00] Submitting share 9d73b322 to pool 0
[2016-11-30 22:12:00] Accepted 9d73b322 Diff 107K/16384 BA2 0 pool 0
[2016-11-30 22:12:00] Accepted 9d73b322 Diff 107K/16384 BA2 0
[2016-11-30 22:12:00] Job is not working from chip(cs3) 6
[2016-11-30 22:12:00] Job is not working from chip(cs3) 8
[2016-11-30 22:12:00] Job is not working from chip(cs3) 10
[2016-11-30 22:12:00] Job is not working from chip(cs3) 14
[2016-11-30 22:12:00] Job is not working from chip(cs3) 15
[2016-11-30 22:12:00] Job is not working from chip(cs3) 18
[2016-11-30 22:12:00] Reinit board (cs3)
[2016-11-30 22:12:00] spidev0.0(cs3): Found 20 A2 chips
[2016-11-30 22:12:00] Found chip 1 with 100 active cores
[2016-11-30 22:12:00] Found chip 2 with 100 active cores
[2016-11-30 22:12:00] Found chip 3 with 100 active cores
[2016-11-30 22:12:00] Found chip 4 with 100 active cores
[2016-11-30 22:12:00] Found chip 5 with 100 active cores
[2016-11-30 22:12:00] Found chip 6 with 100 active cores
[2016-11-30 22:12:00] Found chip 7 with 100 active cores
[2016-11-30 22:12:00] Found chip 8 with 100 active cores
[2016-11-30 22:12:00] Found chip 9 with 100 active cores
[2016-11-30 22:12:00] Found chip 10 with 100 active cores
[2016-11-30 22:12:00] Found chip 11 with 100 active cores
[2016-11-30 22:12:00] Found chip 12 with 100 active cores
[2016-11-30 22:12:00] Found chip 13 with 100 active cores
[2016-11-30 22:12:00] Found chip 14 with 100 active cores
[2016-11-30 22:12:00] Found chip 15 with 100 active cores
[2016-11-30 22:12:00] Found chip 16 with 100 active cores
[2016-11-30 22:12:00] Found chip 17 with 100 active cores
[2016-11-30 22:12:00] Found chip 18 with 100 active cores
[2016-11-30 22:12:00] Found chip 19 with 100 active cores
[2016-11-30 22:12:00] Found chip 20 with 100 active cores
[2016-11-30 22:12:00] Found 20 chips with total 2000 active cores
[2016-11-30 22:12:00] Job is not working from chip(cs1) 0
[2016-11-30 22:12:00] Job is not working from chip(cs1) 1
[2016-11-30 22:12:00] Job is not working from chip(cs1) 2
[2016-11-30 22:12:00] Job is not working from chip(cs1) 3
[2016-11-30 22:12:00] Job is not working from chip(cs1) 5
[2016-11-30 22:12:00] Job is not working from chip(cs1) 6
[2016-11-30 22:12:00] Job is not working from chip(cs1) 7
[2016-11-30 22:12:00] Job is not working from chip(cs1) 9
[2016-11-30 22:12:00] Job is not working from chip(cs1) 10
[2016-11-30 22:12:00] Job is not working from chip(cs1) 11
[2016-11-30 22:12:00] Job is not working from chip(cs1) 12
[2016-11-30 22:12:00] Job is not working from chip(cs1) 13
[2016-11-30 22:12:00] Job is not working from chip(cs1) 14
[2016-11-30 22:12:00] Job is not working from chip(cs1) 15
[2016-11-30 22:12:00] Job is not working from chip(cs1) 17
[2016-11-30 22:12:00] Job is not working from chip(cs1) 18
[2016-11-30 22:12:00] nonces processed 20
[2016-11-30 22:12:00] Job is not working from chip(cs4) 0
[2016-11-30 22:12:00] Job is not working from chip(cs4) 1
[2016-11-30 22:12:00] Job is not working from chip(cs4) 2
[2016-11-30 22:12:00] Job is not working from chip(cs4) 3
[2016-11-30 22:12:00] Job is not working from chip(cs4) 4
[2016-11-30 22:12:00] Job is not working from chip(cs4) 5
[2016-11-30 22:12:00] Job is not working from chip(cs4) 6
[2016-11-30 22:12:00] Job is not working from chip(cs4) 7
[2016-11-30 22:12:00] Job is not working from chip(cs4) 8
[2016-11-30 22:12:00] Job is not working from chip(cs4) 9
[2016-11-30 22:12:00] Job is not working from chip(cs4) 10
[2016-11-30 22:12:00] Job is not working from chip(cs4) 11
[2016-11-30 22:12:00] Job is not working from chip(cs4) 12
[2016-11-30 22:12:00] Job is not working from chip(cs4) 13
[2016-11-30 22:12:00] Job is not working from chip(cs4) 14
[2016-11-30 22:12:00] Job is not working from chip(cs4) 16
[2016-11-30 22:12:00] Job is not working from chip(cs4) 17
[2016-11-30 22:12:00] Job is not working from chip(cs4) 18
[2016-11-30 22:12:00] Job is not working from chip(cs4) 19
[2016-11-30 22:12:00] nonces processed 20
BA21 cs:2 A:20 -C:20 (10-10-10-10-10-10-10-10-10-10-10-10-10-10-10-1(5s):68.13M (avg):69.03Mh/s | A:350208 R:0 HBA20 cs:1 A:20 -C:20 (10-10-10-10-10-10-10-10-10-10-10-10-10-10-10-1(5s):68.29M (avg):69.11Mh/s | A:274432 R:0 H [2016-11-30 22:12:01] Submitting share e677d523 to pool 0 -0
[2016-11-30 22:12:01] Accepted 02e677d5 Diff 22.6K/16384 BA2 1 pool 0
[2016-11-30 22:12:01] Accepted 02e677d5 Diff 22.6K/16384 BA2 1
BA23 cs:4 A:20 -C:20 (10-10-10-10-10-10-10-10-10-10-10-10-10-10-10-1(5s):68.00M (avg):67.83Mh/s | A:313856 R:0 HBA22 cs:3 A:20 -C:20 (10-10-10-10-10-10-10-10-10-10-10-10-10-10-10-1(5s):65.22M (avg):67.94Mh/s | A:263680 R:0 H [2016-11-30 22:12:02] BA22: invalid nonce - HW error 00-00-0
[2016-11-30 22:12:02] chip(cs3) 18: invalid nonce 0x6f9f1000 |
|
|
|
|
lightfoot
Legendary
Offline
Activity: 3206
Merit: 2291
I fix broken miners. And make holes in teeth :-)
|
|
November 30, 2016, 04:12:03 PM |
|
Ain't that interesting?
Hm. So a chip throws an invalid nonce (typically a comm error) and the other chips jam. I wonder what kind of recovery/isolation code is in place to detect this, isolate the errant chip, and resume the queues on the rest of the die. Does Cgminer allow you to turn off queueing of work to processors?
Likewise you should be able to use tee or something to tee off the full diag logs to a big fucking file, then grep around in it.
Fun, hm?
|
|
|
|
|
|
