Had an electrician around to put a nice chunky cable in my mining room and 10 power ports.
Seems to be more stable however, much more stable... only one difference:
I'm now running each miner from a single power port...
where as before I had two miners into an extension lead, into the wall...
Miners are tipping just over 1000 watts usage - extension cables are usually rated at 2000 watts max...
Maybe this is a problem for other people?
Topic: A4 Dominator - Pre-Order Group Buy - 280mh, roughly 1000w, $1800 + shipping - page 32. (Read 122577 times)
December 01, 2016, 09:36:20 AM
December 01, 2016, 06:37:11 AM
Hi! Guys. Please need your help. Today i have start A4 block (138M) and after connect and config it. (software 1.0.3) i recieve message "Error getting version for 127.0.0.1:4028 ERR: socket connect(127.0.0.1:4028) failed!" What that mean?
1. check Your router IP (you have to fill default gateway same as router ip)
2. check Your DNS adress on router, also have to be added manualy in miner config.
PS. Order only miners with 2.0.1 firmware
December 01, 2016, 01:21:19 AM
I dont have an IR gun, but the web page reports temps of 50-51 on all my cubes.
Fans are 200 CFM...
Fans are 200 CFM...
December 01, 2016, 12:55:00 AM
This is a dumb question but here goes 
Could this be a HEAT issue of the 2 boards crammed into that itty bitty case and getting too hot and resetting?
Looks to me like you could easily mount these in a KNC Jupiter Case say and just put big ass fans on the works (like GPU rigs do) and see what happens
and/or how stable.
Would be hilarious if all this is ..is too much heat crammed into that little box with a fan....
I suppose a 'heat temp gun' would also tell you much on this theory
Anyway for what it is worth what I had rigged up in 2013 on my KNC Jupiter due to heat (ran it this way in the Winter too)
Just a thought..it solved my problems with heat back in the day You could over kill on the fans...more so then you see on the pic below in that
they don't have any 'coolers' per say....?
Could this be a HEAT issue of the 2 boards crammed into that itty bitty case and getting too hot and resetting?
Looks to me like you could easily mount these in a KNC Jupiter Case say and just put big ass fans on the works (like GPU rigs do) and see what happens
and/or how stable.
Would be hilarious if all this is ..is too much heat crammed into that little box with a fan....
I suppose a 'heat temp gun' would also tell you much on this theory
Anyway for what it is worth what I had rigged up in 2013 on my KNC Jupiter due to heat (ran it this way in the Winter too)
Just a thought..it solved my problems with heat back in the day
You could over kill on the fans...more so then you see on the pic below in thatthey don't have any 'coolers' per say....?
November 30, 2016, 07:42:03 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.
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.
Here is a picture of a board we were sent some time ago:
What does the board look like with a thermal camera? Hot spots on the way to those hashing chips?
November 30, 2016, 04:05:48 PM
that means that cgminer did not start yet or bailed out with errors and the web interface cannot connect to the cgminer api.
Wait for it to come online if you see it running in the connect page.
Check your configuration if it will not keep running.
Good luck.
Wait for it to come online if you see it running in the connect page.
Check your configuration if it will not keep running.
Good luck.
Hi! Guys. Please need your help. Today i have start A4 block (138M) and after connect and config it. (software 1.0.3) i recieve message "Error getting version for 127.0.0.1:4028 ERR: socket connect(127.0.0.1:4028) failed!" What that mean?
November 30, 2016, 03:46:36 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.
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.
Here is a picture of a board we were sent some time ago:
November 30, 2016, 03:37:02 PM
Hi! Guys. Please need your help. Today i have start A4 block (138M) and after connect and config it. (software 1.0.3) i recieve message "Error getting version for 127.0.0.1:4028 ERR: socket connect(127.0.0.1:4028) failed!" What that mean?
November 30, 2016, 11:12:03 AM
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?
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?
November 30, 2016, 09:19:18 AM
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
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
Code:
[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
November 30, 2016, 07:44:32 AM
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.
November 30, 2016, 07:35:49 AM
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.
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.
November 30, 2016, 07:22:39 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
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.
November 30, 2016, 04:49:38 AM
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
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
Code:
[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
November 29, 2016, 11:03:19 PM
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
November 29, 2016, 10:33:01 PM
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?
November 29, 2016, 10:18:08 PM
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
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
November 29, 2016, 09:45:24 PM
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?
November 29, 2016, 08:46:48 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
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
November 29, 2016, 05: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/YeJmQ
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/YeJmQ
I 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!
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
Jump to: