Pages:
Author

Topic: Innosilicon A4+ setup tutorial - page 8. (Read 6676 times)

newbie
Activity: 66
Merit: 0
January 15, 2018, 09:00:17 PM
how can i overclock them?
newbie
Activity: 19
Merit: 0
January 14, 2018, 09:57:10 AM
You have to telnet into the machine:

Code:
telnet 192.168.1.254 8100

Then use:

Code:
username: root
password: t1t2t3a5

Then you can look for all files that have ".log"

Code:
find / -name *.log

which yields for me and by 1 downed chain:

Code:
/tmp/log/innominer.log
/tmp/log/analys3.log
/tmp/log/analys0.log
/tmp/log/analys1.log
/innocfg/log/miner.log
/innocfg/log/upgrade.log

I look at each one with cat:

Code:
cat /tmp/log/innominer.log
newbie
Activity: 21
Merit: 0
January 14, 2018, 05:59:10 AM
newbie
Activity: 19
Merit: 0
January 14, 2018, 02:51:24 AM
I just read through this thread. Saw a few people having problems with 1 or more chains not working.

I have one chain that isn't working.

All 4 chains light up on boot but after a minute or so, one light goes out. The unit hashes fine but one chain doesn't work.

Checked the cables, looked good. I'm using a Bitmain APW3++ PSU, worked great for the last 7 days straight. This only starting today after a reboot.

I've tried updating the firmware and restoring factory settings. Can anyone provide a tip for what to try next?

I'm going to try telnetting into the machine but was hoping a solution might be more straightforward.

My other 2 units and all their chains are working great. Just having an issue with this one unit and this one chain  Sad

Here is my log after reseting to factory defaults:

Code:
Jan 14 06:56:48 (none) local0.warn innominer_T2: Started cgminer 4.10.0
Jan 14 06:56:48 (none) local0.info innominer_T2: hardware version is G19
Jan 14 06:56:48 (none) local0.info innominer_T2: miner type is T2
Jan 14 06:56:48 (none) local0.notice innominer_T2: A1 = 1044,92, Clock = 1044MHz
Jan 14 06:56:48 (none) local0.notice innominer_T2: A1 = 1044,92, Clock = 1044MHz
Jan 14 06:56:48 (none) local0.notice innominer_T2: A1 = 1044,92, Clock = 1044MHz
Jan 14 06:56:48 (none) local0.notice innominer_T2: A1 = 1044,92, Clock = 1044MHz
Jan 14 06:56:48 (none) local0.notice innominer_T2: A1 = 1044,92, Clock = 1044MHz
Jan 14 06:56:48 (none) local0.notice innominer_T2: A1 = 1044,92, Clock = 1044MHz
Jan 14 06:56:48 (none) local0.notice innominer_T2: A1 = 1044,92, Clock = 1044MHz
Jan 14 06:56:48 (none) local0.notice innominer_T2: A1 = 1044,92, Clock = 1044MHz
Jan 14 06:56:48 (none) local0.warn innominer_T2: A1: checking A1 chain
Jan 14 06:56:48 (none) local0.warn innominer_T2: SPI '/dev/spidev0.0': mode=1, bits=8, speed=1500000
Jan 14 06:56:50 (none) local0.warn innominer_T2: SPI '/dev/spidev1.0': mode=1, bits=8, speed=1500000
Jan 14 06:56:52 (none) local0.warn innominer_T2: SPI '/dev/spidev2.0': mode=1, bits=8, speed=1500000
Jan 14 06:56:54 (none) local0.warn innominer_T2: SPI '/dev/spidev3.0': mode=1, bits=8, speed=1500000
Jan 14 06:56:56 (none) local0.warn innominer_T2: SPI '/dev/spidev4.0': mode=1, bits=8, speed=1500000
Jan 14 06:56:58 (none) local0.warn innominer_T2: SPI '/dev/spidev5.0': mode=1, bits=8, speed=1500000
Jan 14 06:57:00 (none) local0.warn innominer_T2: SPI '/dev/spidev6.0': mode=1, bits=8, speed=1500000
Jan 14 06:57:02 (none) local0.warn innominer_T2: SPI '/dev/spidev7.0': mode=1, bits=8, speed=1500000
Jan 14 06:57:09 (none) local0.err innominer_T2: Plug Status[0] = 0
Jan 14 06:57:15 (none) local0.err innominer_T2: Plug Status[1] = 0
Jan 14 06:57:21 (none) local0.err innominer_T2: Plug Status[2] = 0
Jan 14 06:57:27 (none) local0.err innominer_T2: Plug Status[3] = 0
Jan 14 06:57:33 (none) local0.err innominer_T2: Plug Status[4] = 1
Jan 14 06:57:33 (none) local0.err innominer_T2: chain:4 the plat is not inserted
Jan 14 06:57:33 (none) local0.err innominer_T2: Plug Status[5] = 1
Jan 14 06:57:33 (none) local0.err innominer_T2: chain:5 the plat is not inserted
Jan 14 06:57:33 (none) local0.err innominer_T2: Plug Status[6] = 1
Jan 14 06:57:33 (none) local0.err innominer_T2: chain:6 the plat is not inserted
Jan 14 06:57:33 (none) local0.err innominer_T2: Plug Status[7] = 1
Jan 14 06:57:33 (none) local0.err innominer_T2: chain:7 the plat is not inserted
Jan 14 06:57:33 (none) local0.info innominer_T2: pre 0: A1 init chain
Jan 14 06:57:34 (none) local0.warn innominer_T2: 0: detected 72 chips
Jan 14 06:57:34 (none) local0.warn innominer_T2: collect core success
Jan 14 06:57:34 (none) local0.warn innominer_T2: 0: no A1 chip-chain detected
Jan 14 06:57:34 (none) local0.warn innominer_T2: spidev0.0: 0: Found 72 A1 chips
Jan 14 06:57:34 (none) local0.warn innominer_T2: Detected the 0 A1 chain with 72 chips
Jan 14 06:57:34 (none) local0.info innominer_T2: pre 1: A1 init chain
Jan 14 06:57:35 (none) local0.warn innominer_T2: 1: detected 72 chips
Jan 14 06:57:35 (none) local0.warn innominer_T2: collect core success
Jan 14 06:57:35 (none) local0.warn innominer_T2: 1: no A1 chip-chain detected
Jan 14 06:57:35 (none) local0.warn innominer_T2: spidev1.0: 1: Found 72 A1 chips
Jan 14 06:57:35 (none) local0.warn innominer_T2: Detected the 1 A1 chain with 72 chips
Jan 14 06:57:35 (none) local0.info innominer_T2: pre 2: A1 init chain
Jan 14 06:57:35 (none) local0.warn innominer_T2: cmd reset: poll fail !
Jan 14 06:57:36 (none) local0.warn innominer_T2: cmd bist start: poll fail !
Jan 14 06:57:36 (none) local0.warn innominer_T2: bist start fail
Jan 14 06:57:36 (none) local0.err innominer_T2: init 2 A1 chain fail
Jan 14 06:57:36 (none) local0.info innominer_T2: pre 3: A1 init chain
Jan 14 06:57:37 (none) local0.warn innominer_T2: 3: detected 72 chips
Jan 14 06:57:37 (none) local0.warn innominer_T2: collect core success
Jan 14 06:57:37 (none) local0.warn innominer_T2: 3: no A1 chip-chain detected
Jan 14 06:57:37 (none) local0.warn innominer_T2: spidev3.0: 3: Found 72 A1 chips
Jan 14 06:57:37 (none) local0.warn innominer_T2: Detected the 3 A1 chain with 72 chips
Jan 14 06:57:37 (none) local0.info innominer_T2: start to configure all chain from 0 to 120
Jan 14 06:57:37 (none) local0.err innominer_T2: start to read temp
Jan 14 06:57:37 (none) local0.info innominer_T2: start to configure chain 0
Jan 14 06:57:37 (none) local0.notice innominer_T2: A1 = 120,0, Clock = 120MHz
Jan 14 06:57:37 (none) local0.err innominer_T2: start to read temp
Jan 14 06:57:38 (none) local0.info innominer_T2: start to configure chain 1
Jan 14 06:57:38 (none) local0.notice innominer_T2: A1 = 120,0, Clock = 120MHz
Jan 14 06:57:38 (none) local0.info innominer_T2: chain 2 has been disable
Jan 14 06:57:38 (none) local0.err innominer_T2: start to read temp
Jan 14 06:57:38 (none) local0.info innominer_T2: start to configure chain 3
Jan 14 06:57:38 (none) local0.notice innominer_T2: A1 = 120,0, Clock = 120MHz
Jan 14 06:57:39 (none) local0.info innominer_T2: chain 4 has been disable
Jan 14 06:57:39 (none) local0.info innominer_T2: chain 5 has been disable
Jan 14 06:57:39 (none) local0.info innominer_T2: chain 6 has been disable
Jan 14 06:57:39 (none) local0.info innominer_T2: chain 7 has been disable
Jan 14 06:57:39 (none) local0.info innominer_T2: start to configure all chain from 120 to 320
Jan 14 06:57:39 (none) local0.err innominer_T2: start to read temp
Jan 14 06:57:39 (none) local0.info innominer_T2: start to configure chain 0
Jan 14 06:57:39 (none) local0.notice innominer_T2: A1 = 320,20, Clock = 318MHz
Jan 14 06:57:39 (none) local0.notice innominer_T2: A1 = 120,0, Clock = 120MHz
Jan 14 06:57:42 (none) local0.err innominer_T2: start to read temp
Jan 14 06:57:42 (none) local0.info innominer_T2: start to configure chain 1
Jan 14 06:57:42 (none) local0.notice innominer_T2: A1 = 320,20, Clock = 318MHz
Jan 14 06:57:42 (none) local0.notice innominer_T2: A1 = 120,0, Clock = 120MHz
Jan 14 06:57:45 (none) local0.info innominer_T2: chain 2 has been disable
Jan 14 06:57:45 (none) local0.err innominer_T2: start to read temp
Jan 14 06:57:45 (none) local0.info innominer_T2: start to configure chain 3
Jan 14 06:57:45 (none) local0.notice innominer_T2: A1 = 320,20, Clock = 318MHz
Jan 14 06:57:45 (none) local0.notice innominer_T2: A1 = 120,0, Clock = 120MHz
Jan 14 06:57:48 (none) local0.info innominer_T2: chain 4 has been disable
Jan 14 06:57:48 (none) local0.info innominer_T2: chain 5 has been disable
Jan 14 06:57:48 (none) local0.info innominer_T2: chain 6 has been disable
Jan 14 06:57:48 (none) local0.info innominer_T2: chain 7 has been disable
Jan 14 06:57:48 (none) local0.info innominer_T2: start to configure all chain from 320 to 520
Jan 14 06:57:48 (none) local0.err innominer_T2: start to read temp
Jan 14 06:57:48 (none) local0.info innominer_T2: start to configure chain 0
Jan 14 06:57:48 (none) local0.notice innominer_T2: A1 = 520,39, Clock = 510MHz
Jan 14 06:57:48 (none) local0.notice innominer_T2: A1 = 320,20, Clock = 318MHz
Jan 14 06:57:51 (none) local0.err innominer_T2: start to read temp
Jan 14 06:57:51 (none) local0.info innominer_T2: start to configure chain 1
Jan 14 06:57:51 (none) local0.notice innominer_T2: A1 = 520,39, Clock = 510MHz
Jan 14 06:57:51 (none) local0.notice innominer_T2: A1 = 320,20, Clock = 318MHz
Jan 14 06:57:54 (none) local0.info innominer_T2: chain 2 has been disable
Jan 14 06:57:54 (none) local0.err innominer_T2: start to read temp
Jan 14 06:57:54 (none) local0.info innominer_T2: start to configure chain 3
Jan 14 06:57:54 (none) local0.notice innominer_T2: A1 = 520,39, Clock = 510MHz
Jan 14 06:57:54 (none) local0.notice innominer_T2: A1 = 320,20, Clock = 318MHz
Jan 14 06:57:57 (none) local0.info innominer_T2: chain 4 has been disable
Jan 14 06:57:57 (none) local0.info innominer_T2: chain 5 has been disable
Jan 14 06:57:57 (none) local0.info innominer_T2: chain 6 has been disable
Jan 14 06:57:57 (none) local0.info innominer_T2: chain 7 has been disable
Jan 14 06:57:57 (none) local0.info innominer_T2: start to configure all chain from 520 to 720
Jan 14 06:57:57 (none) local0.err innominer_T2: start to read temp
Jan 14 06:57:57 (none) local0.info innominer_T2: start to configure chain 0
Jan 14 06:57:57 (none) local0.notice innominer_T2: A1 = 720,60, Clock = 720MHz
Jan 14 06:57:57 (none) local0.notice innominer_T2: A1 = 520,39, Clock = 510MHz
Jan 14 06:58:00 (none) local0.err innominer_T2: start to read temp
Jan 14 06:58:00 (none) local0.info innominer_T2: start to configure chain 1
Jan 14 06:58:00 (none) local0.notice innominer_T2: A1 = 720,60, Clock = 720MHz
Jan 14 06:58:00 (none) local0.notice innominer_T2: A1 = 520,39, Clock = 510MHz
Jan 14 06:58:03 (none) local0.info innominer_T2: chain 2 has been disable
Jan 14 06:58:03 (none) local0.err innominer_T2: start to read temp
Jan 14 06:58:03 (none) local0.info innominer_T2: start to configure chain 3
Jan 14 06:58:03 (none) local0.notice innominer_T2: A1 = 720,60, Clock = 720MHz
Jan 14 06:58:03 (none) local0.notice innominer_T2: A1 = 520,39, Clock = 510MHz
Jan 14 06:58:06 (none) local0.info innominer_T2: chain 4 has been disable
Jan 14 06:58:06 (none) local0.info innominer_T2: chain 5 has been disable
Jan 14 06:58:06 (none) local0.info innominer_T2: chain 6 has been disable
Jan 14 06:58:06 (none) local0.info innominer_T2: chain 7 has been disable
Jan 14 06:58:06 (none) local0.info innominer_T2: start to configure all chain from 720 to 920
Jan 14 06:58:06 (none) local0.err innominer_T2: start to read temp
Jan 14 06:58:06 (none) local0.info innominer_T2: start to configure chain 0
Jan 14 06:58:06 (none) local0.notice innominer_T2: A1 = 920,79, Clock = 912MHz
Jan 14 06:58:06 (none) local0.notice innominer_T2: A1 = 720,60, Clock = 720MHz
Jan 14 06:58:09 (none) local0.err innominer_T2: start to read temp
Jan 14 06:58:09 (none) local0.info innominer_T2: start to configure chain 1
Jan 14 06:58:09 (none) local0.notice innominer_T2: A1 = 920,79, Clock = 912MHz
Jan 14 06:58:09 (none) local0.notice innominer_T2: A1 = 720,60, Clock = 720MHz
Jan 14 06:58:12 (none) local0.info innominer_T2: chain 2 has been disable
Jan 14 06:58:12 (none) local0.err innominer_T2: start to read temp
Jan 14 06:58:12 (none) local0.info innominer_T2: start to configure chain 3
Jan 14 06:58:12 (none) local0.notice innominer_T2: A1 = 920,79, Clock = 912MHz
Jan 14 06:58:12 (none) local0.notice innominer_T2: A1 = 720,60, Clock = 720MHz
Jan 14 06:58:15 (none) local0.info innominer_T2: chain 4 has been disable
Jan 14 06:58:15 (none) local0.info innominer_T2: chain 5 has been disable
Jan 14 06:58:15 (none) local0.info innominer_T2: chain 6 has been disable
Jan 14 06:58:15 (none) local0.info innominer_T2: chain 7 has been disable
Jan 14 06:58:15 (none) local0.info innominer_T2: start to configure all chain from 920 to 1044
Jan 14 06:58:15 (none) local0.err innominer_T2: start to read temp
Jan 14 06:58:15 (none) local0.info innominer_T2: start to configure chain 0
Jan 14 06:58:15 (none) local0.notice innominer_T2: A1 = 1044,92, Clock = 1044MHz
Jan 14 06:58:15 (none) local0.notice innominer_T2: A1 = 920,79, Clock = 912MHz
Jan 14 06:58:17 (none) local0.err innominer_T2: start to read temp
Jan 14 06:58:17 (none) local0.info innominer_T2: start to configure chain 1
Jan 14 06:58:17 (none) local0.notice innominer_T2: A1 = 1044,92, Clock = 1044MHz
Jan 14 06:58:17 (none) local0.notice innominer_T2: A1 = 920,79, Clock = 912MHz
Jan 14 06:58:19 (none) local0.info innominer_T2: chain 2 has been disable
Jan 14 06:58:19 (none) local0.err innominer_T2: start to read temp
Jan 14 06:58:20 (none) local0.info innominer_T2: start to configure chain 3
Jan 14 06:58:20 (none) local0.notice innominer_T2: A1 = 1044,92, Clock = 1044MHz
Jan 14 06:58:20 (none) local0.notice innominer_T2: A1 = 920,79, Clock = 912MHz
Jan 14 06:58:21 (none) local0.info innominer_T2: chain 4 has been disable
Jan 14 06:58:21 (none) local0.info innominer_T2: chain 5 has been disable
Jan 14 06:58:21 (none) local0.info innominer_T2: chain 6 has been disable
Jan 14 06:58:21 (none) local0.info innominer_T2: chain 7 has been disable
Jan 14 06:58:21 (none) local0.info innominer_T2: 0: A1 init chain
Jan 14 06:58:22 (none) local0.warn innominer_T2: 0: detected 72 chips
Jan 14 06:58:22 (none) local0.warn innominer_T2: collect core success
Jan 14 06:58:22 (none) local0.warn innominer_T2: 0: no A1 chip-chain detected
Jan 14 06:58:22 (none) local0.warn innominer_T2: spidev0.0: 0: Found 72 A1 chips
Jan 14 06:58:23 (none) local0.warn innominer_T2: 0: Found chip 1 with 9 active cores
Jan 14 06:58:23 (none) local0.warn innominer_T2: 0: Found chip 2 with 9 active cores
Jan 14 06:58:23 (none) local0.warn innominer_T2: 0: Found chip 3 with 9 active cores
Jan 14 06:58:23 (none) local0.warn innominer_T2: 0: Found chip 4 with 9 active cores
Jan 14 06:58:23 (none) local0.warn innominer_T2: 0: Found chip 5 with 9 active cores
Jan 14 06:58:23 (none) local0.warn innominer_T2: 0: Found chip 6 with 9 active cores
Jan 14 06:58:23 (none) local0.warn innominer_T2: 0: Found chip 7 with 9 active cores
Jan 14 06:58:23 (none) local0.warn innominer_T2: 0: Found chip 8 with 9 active cores
Jan 14 06:58:23 (none) local0.warn innominer_T2: 0: Found chip 9 with 9 active cores
Jan 14 06:58:23 (none) local0.warn innominer_T2: 0: Found chip 10 with 9 active cores
Jan 14 06:58:23 (none) local0.warn innominer_T2: 0: Found chip 11 with 9 active cores
Jan 14 06:58:23 (none) local0.warn innominer_T2: 0: Found chip 12 with 9 active cores
Jan 14 06:58:23 (none) local0.warn innominer_T2: 0: Found chip 13 with 9 active cores
Jan 14 06:58:23 (none) local0.warn innominer_T2: 0: Found chip 14 with 9 active cores
Jan 14 06:58:23 (none) local0.warn innominer_T2: 0: Found chip 15 with 9 active cores
Jan 14 06:58:23 (none) local0.warn innominer_T2: 0: Found chip 16 with 9 active cores
Jan 14 06:58:23 (none) local0.warn innominer_T2: 0: Found chip 17 with 9 active cores
Jan 14 06:58:23 (none) local0.warn innominer_T2: 0: Found chip 18 with 9 active cores
Jan 14 06:58:23 (none) local0.warn innominer_T2: 0: Found chip 19 with 9 active cores
Jan 14 06:58:23 (none) local0.warn innominer_T2: 0: Found chip 20 with 9 active cores
Jan 14 06:58:23 (none) local0.warn innominer_T2: 0: Found chip 21 with 9 active cores
Jan 14 06:58:23 (none) local0.warn innominer_T2: 0: Found chip 22 with 9 active cores
Jan 14 06:58:23 (none) local0.warn innominer_T2: 0: Found chip 23 with 9 active cores
Jan 14 06:58:23 (none) local0.warn innominer_T2: 0: Found chip 24 with 9 active cores
Jan 14 06:58:23 (none) local0.warn innominer_T2: 0: Found chip 25 with 9 active cores
Jan 14 06:58:23 (none) local0.warn innominer_T2: 0: Found chip 26 with 9 active cores
Jan 14 06:58:23 (none) local0.warn innominer_T2: 0: Found chip 27 with 9 active cores
Jan 14 06:58:23 (none) local0.warn innominer_T2: 0: Found chip 28 with 9 active cores
Jan 14 06:58:23 (none) local0.warn innominer_T2: 0: Found chip 29 with 9 active cores
Jan 14 06:58:23 (none) local0.warn innominer_T2: 0: Found chip 30 with 9 active cores
Jan 14 06:58:23 (none) local0.warn innominer_T2: 0: Found chip 31 with 9 active cores
Jan 14 06:58:23 (none) local0.warn innominer_T2: 0: Found chip 32 with 9 active cores
Jan 14 06:58:23 (none) local0.warn innominer_T2: 0: Found chip 33 with 9 active cores
Jan 14 06:58:23 (none) local0.warn innominer_T2: 0: Found chip 34 with 9 active cores
Jan 14 06:58:23 (none) local0.warn innominer_T2: 0: Found chip 35 with 9 active cores
Jan 14 06:58:23 (none) local0.warn innominer_T2: 0: Found chip 36 with 9 active cores
Jan 14 06:58:23 (none) local0.warn innominer_T2: 0: Found chip 37 with 9 active cores
Jan 14 06:58:23 (none) local0.warn innominer_T2: 0: Found chip 38 with 9 active cores
Jan 14 06:58:23 (none) local0.warn innominer_T2: 0: Found chip 39 with 9 active cores
Jan 14 06:58:23 (none) local0.warn innominer_T2: 0: Found chip 40 with 9 active cores
Jan 14 06:58:23 (none) local0.warn innominer_T2: 0: Found chip 41 with 9 active cores
Jan 14 06:58:23 (none) local0.warn innominer_T2: 0: Found chip 42 with 9 active cores
Jan 14 06:58:23 (none) local0.warn innominer_T2: 0: Found chip 43 with 9 active cores
Jan 14 06:58:23 (none) local0.warn innominer_T2: 0: Found chip 44 with 9 active cores
Jan 14 06:58:23 (none) local0.warn innominer_T2: 0: Found chip 45 with 9 active cores
Jan 14 06:58:23 (none) local0.warn innominer_T2: 0: Found chip 46 with 9 active cores
Jan 14 06:58:23 (none) local0.warn innominer_T2: 0: Found chip 47 with 9 active cores
Jan 14 06:58:23 (none) local0.warn innominer_T2: 0: Found chip 48 with 9 active cores
Jan 14 06:58:23 (none) local0.warn innominer_T2: 0: Found chip 49 with 9 active cores
Jan 14 06:58:23 (none) local0.warn innominer_T2: 0: Found chip 50 with 9 active cores
Jan 14 06:58:23 (none) local0.warn innominer_T2: 0: Found chip 51 with 9 active cores
Jan 14 06:58:23 (none) local0.warn innominer_T2: 0: Found chip 52 with 9 active cores
Jan 14 06:58:23 (none) local0.warn innominer_T2: 0: Found chip 53 with 9 active cores
Jan 14 06:58:23 (none) local0.warn innominer_T2: 0: Found chip 54 with 9 active cores
Jan 14 06:58:23 (none) local0.warn innominer_T2: 0: Found chip 55 with 9 active cores
Jan 14 06:58:23 (none) local0.warn innominer_T2: 0: Found chip 56 with 9 active cores
Jan 14 06:58:23 (none) local0.warn innominer_T2: 0: Found chip 57 with 9 active cores
Jan 14 06:58:23 (none) local0.warn innominer_T2: 0: Found chip 58 with 9 active cores
Jan 14 06:58:23 (none) local0.warn innominer_T2: 0: Found chip 59 with 9 active cores
Jan 14 06:58:23 (none) local0.warn innominer_T2: 0: Found chip 60 with 9 active cores
Jan 14 06:58:23 (none) local0.warn innominer_T2: 0: Found chip 61 with 9 active cores
Jan 14 06:58:23 (none) local0.warn innominer_T2: 0: Found chip 62 with 9 active cores
Jan 14 06:58:23 (none) local0.warn innominer_T2: 0: Found chip 63 with 9 active cores
Jan 14 06:58:23 (none) local0.warn innominer_T2: 0: Found chip 64 with 9 active cores
Jan 14 06:58:23 (none) local0.warn innominer_T2: 0: Found chip 65 with 9 active cores
Jan 14 06:58:23 (none) local0.warn innominer_T2: 0: Found chip 66 with 9 active cores
Jan 14 06:58:23 (none) local0.warn innominer_T2: 0: Found chip 67 with 9 active cores
Jan 14 06:58:23 (none) local0.warn innominer_T2: 0: Found chip 68 with 9 active cores
Jan 14 06:58:23 (none) local0.warn innominer_T2: 0: Found chip 69 with 9 active cores
Jan 14 06:58:23 (none) local0.warn innominer_T2: 0: Found chip 70 with 9 active cores
Jan 14 06:58:23 (none) local0.warn innominer_T2: 0: Found chip 71 with 9 active cores
Jan 14 06:58:23 (none) local0.warn innominer_T2: 0: Found chip 72 with 9 active cores
Jan 14 06:58:23 (none) local0.warn innominer_T2: [chain_ID:0]: Found 72 Chips With Total 648 Active Cores
Jan 14 06:58:23 (none) local0.warn innominer_T2: [chain_ID]: Temp:519
Jan 14 06:58:23 (none) local0.warn innominer_T2: Detected the 0 A1 chain with 72 chips
Jan 14 06:58:23 (none) local0.warn innominer_T2: Detected the 0 A1 chain with 72 chips / 648 cores
Jan 14 06:58:23 (none) local0.info innominer_T2: 1: A1 init chain
Jan 14 06:58:24 (none) local0.warn innominer_T2: 1: detected 72 chips
Jan 14 06:58:24 (none) local0.warn innominer_T2: collect core success
Jan 14 06:58:24 (none) local0.warn innominer_T2: 1: no A1 chip-chain detected
Jan 14 06:58:24 (none) local0.warn innominer_T2: spidev1.0: 1: Found 72 A1 chips
Jan 14 06:58:25 (none) local0.warn innominer_T2: 1: Found chip 1 with 9 active cores
Jan 14 06:58:25 (none) local0.warn innominer_T2: 1: Found chip 2 with 9 active cores
Jan 14 06:58:25 (none) local0.warn innominer_T2: 1: Found chip 3 with 9 active cores
Jan 14 06:58:25 (none) local0.warn innominer_T2: 1: Found chip 4 with 9 active cores
Jan 14 06:58:25 (none) local0.warn innominer_T2: 1: Found chip 5 with 9 active cores
Jan 14 06:58:25 (none) local0.warn innominer_T2: 1: Found chip 6 with 9 active cores
Jan 14 06:58:25 (none) local0.warn innominer_T2: 1: Found chip 7 with 9 active cores
Jan 14 06:58:25 (none) local0.warn innominer_T2: 1: Found chip 8 with 9 active cores
Jan 14 06:58:25 (none) local0.warn innominer_T2: 1: Found chip 9 with 9 active cores
Jan 14 06:58:25 (none) local0.warn innominer_T2: 1: Found chip 10 with 9 active cores
Jan 14 06:58:25 (none) local0.warn innominer_T2: 1: Found chip 11 with 9 active cores
Jan 14 06:58:25 (none) local0.warn innominer_T2: 1: Found chip 12 with 9 active cores
Jan 14 06:58:25 (none) local0.warn innominer_T2: 1: Found chip 13 with 9 active cores
Jan 14 06:58:25 (none) local0.warn innominer_T2: 1: Found chip 14 with 9 active cores
Jan 14 06:58:25 (none) local0.warn innominer_T2: 1: Found chip 15 with 9 active cores
Jan 14 06:58:25 (none) local0.warn innominer_T2: 1: Found chip 16 with 9 active cores
Jan 14 06:58:25 (none) local0.warn innominer_T2: 1: Found chip 17 with 9 active cores
Jan 14 06:58:25 (none) local0.warn innominer_T2: 1: Found chip 18 with 9 active cores
Jan 14 06:58:25 (none) local0.warn innominer_T2: 1: Found chip 19 with 9 active cores
Jan 14 06:58:25 (none) local0.warn innominer_T2: 1: Found chip 20 with 9 active cores
Jan 14 06:58:25 (none) local0.warn innominer_T2: 1: Found chip 21 with 9 active cores
Jan 14 06:58:25 (none) local0.warn innominer_T2: 1: Found chip 22 with 9 active cores
Jan 14 06:58:25 (none) local0.warn innominer_T2: 1: Found chip 23 with 9 active cores
Jan 14 06:58:25 (none) local0.warn innominer_T2: 1: Found chip 24 with 9 active cores
Jan 14 06:58:25 (none) local0.warn innominer_T2: 1: Found chip 25 with 9 active cores
Jan 14 06:58:25 (none) local0.warn innominer_T2: 1: Found chip 26 with 9 active cores
Jan 14 06:58:25 (none) local0.warn innominer_T2: 1: Found chip 27 with 9 active cores
Jan 14 06:58:25 (none) local0.warn innominer_T2: 1: Found chip 28 with 9 active cores
Jan 14 06:58:25 (none) local0.warn innominer_T2: 1: Found chip 29 with 9 active cores
Jan 14 06:58:25 (none) local0.warn innominer_T2: 1: Found chip 30 with 9 active cores
Jan 14 06:58:25 (none) local0.warn innominer_T2: 1: Found chip 31 with 9 active cores
Jan 14 06:58:25 (none) local0.warn innominer_T2: 1: Found chip 32 with 9 active cores
Jan 14 06:58:25 (none) local0.warn innominer_T2: 1: Found chip 33 with 9 active cores
Jan 14 06:58:25 (none) local0.warn innominer_T2: 1: Found chip 34 with 9 active cores
Jan 14 06:58:25 (none) local0.warn innominer_T2: 1: Found chip 35 with 9 active cores
Jan 14 06:58:25 (none) local0.warn innominer_T2: 1: Found chip 36 with 9 active cores
Jan 14 06:58:25 (none) local0.warn innominer_T2: 1: Found chip 37 with 9 active cores
Jan 14 06:58:25 (none) local0.warn innominer_T2: 1: Found chip 38 with 9 active cores
Jan 14 06:58:25 (none) local0.warn innominer_T2: 1: Found chip 39 with 9 active cores
Jan 14 06:58:25 (none) local0.warn innominer_T2: 1: Found chip 40 with 9 active cores
Jan 14 06:58:25 (none) local0.warn innominer_T2: 1: Found chip 41 with 9 active cores
Jan 14 06:58:25 (none) local0.warn innominer_T2: 1: Found chip 42 with 9 active cores
Jan 14 06:58:25 (none) local0.warn innominer_T2: 1: Found chip 43 with 9 active cores
Jan 14 06:58:25 (none) local0.warn innominer_T2: 1: Found chip 44 with 9 active cores
Jan 14 06:58:25 (none) local0.warn innominer_T2: 1: Found chip 45 with 9 active cores
Jan 14 06:58:25 (none) local0.warn innominer_T2: 1: Found chip 46 with 9 active cores
Jan 14 06:58:25 (none) local0.warn innominer_T2: 1: Found chip 47 with 9 active cores
Jan 14 06:58:25 (none) local0.warn innominer_T2: 1: Found chip 48 with 9 active cores
Jan 14 06:58:25 (none) local0.warn innominer_T2: 1: Found chip 49 with 9 active cores
Jan 14 06:58:25 (none) local0.warn innominer_T2: 1: Found chip 50 with 9 active cores
Jan 14 06:58:25 (none) local0.warn innominer_T2: 1: Found chip 51 with 9 active cores
Jan 14 06:58:25 (none) local0.warn innominer_T2: 1: Found chip 52 with 9 active cores
Jan 14 06:58:25 (none) local0.warn innominer_T2: 1: Found chip 53 with 9 active cores
Jan 14 06:58:25 (none) local0.warn innominer_T2: 1: Found chip 54 with 9 active cores
Jan 14 06:58:25 (none) local0.warn innominer_T2: 1: Found chip 55 with 9 active cores
Jan 14 06:58:25 (none) local0.warn innominer_T2: 1: Found chip 56 with 9 active cores
Jan 14 06:58:25 (none) local0.warn innominer_T2: 1: Found chip 57 with 9 active cores
Jan 14 06:58:25 (none) local0.warn innominer_T2: 1: Found chip 58 with 9 active cores
Jan 14 06:58:25 (none) local0.warn innominer_T2: 1: Found chip 59 with 9 active cores
Jan 14 06:58:25 (none) local0.warn innominer_T2: 1: Found chip 60 with 9 active cores
Jan 14 06:58:25 (none) local0.warn innominer_T2: 1: Found chip 61 with 9 active cores
Jan 14 06:58:25 (none) local0.warn innominer_T2: 1: Found chip 62 with 9 active cores
Jan 14 06:58:25 (none) local0.warn innominer_T2: 1: Found chip 63 with 9 active cores
Jan 14 06:58:25 (none) local0.warn innominer_T2: 1: Found chip 64 with 9 active cores
Jan 14 06:58:25 (none) local0.warn innominer_T2: 1: Found chip 65 with 9 active cores
Jan 14 06:58:25 (none) local0.warn innominer_T2: 1: Found chip 66 with 9 active cores
Jan 14 06:58:25 (none) local0.warn innominer_T2: 1: Found chip 67 with 9 active cores
Jan 14 06:58:25 (none) local0.warn innominer_T2: 1: Found chip 68 with 9 active cores
Jan 14 06:58:25 (none) local0.warn innominer_T2: 1: Found chip 69 with 9 active cores
Jan 14 06:58:25 (none) local0.warn innominer_T2: 1: Found chip 70 with 9 active cores
Jan 14 06:58:25 (none) local0.warn innominer_T2: 1: Found chip 71 with 9 active cores
Jan 14 06:58:25 (none) local0.warn innominer_T2: 1: Found chip 72 with 9 active cores
Jan 14 06:58:25 (none) local0.warn innominer_T2: [chain_ID:1]: Found 72 Chips With Total 648 Active Cores
Jan 14 06:58:25 (none) local0.warn innominer_T2: [chain_ID]: Temp:524
Jan 14 06:58:25 (none) local0.warn innominer_T2: Detected the 1 A1 chain with 72 chips
Jan 14 06:58:25 (none) local0.warn innominer_T2: Detected the 1 A1 chain with 72 chips / 648 cores
Jan 14 06:58:25 (none) local0.info innominer_T2: 3: A1 init chain
Jan 14 06:58:26 (none) local0.warn innominer_T2: 3: detected 72 chips
Jan 14 06:58:26 (none) local0.warn innominer_T2: collect core success
Jan 14 06:58:26 (none) local0.warn innominer_T2: 3: no A1 chip-chain detected
Jan 14 06:58:26 (none) local0.warn innominer_T2: spidev3.0: 3: Found 72 A1 chips
Jan 14 06:58:26 (none) local0.warn innominer_T2: 3: Found chip 1 with 9 active cores
Jan 14 06:58:26 (none) local0.warn innominer_T2: 3: Found chip 2 with 9 active cores
Jan 14 06:58:26 (none) local0.warn innominer_T2: 3: Found chip 3 with 9 active cores
Jan 14 06:58:26 (none) local0.warn innominer_T2: 3: Found chip 4 with 9 active cores
Jan 14 06:58:26 (none) local0.warn innominer_T2: 3: Found chip 5 with 9 active cores
Jan 14 06:58:26 (none) local0.warn innominer_T2: 3: Found chip 6 with 9 active cores
Jan 14 06:58:26 (none) local0.warn innominer_T2: 3: Found chip 7 with 9 active cores
Jan 14 06:58:26 (none) local0.warn innominer_T2: 3: Found chip 8 with 9 active cores
Jan 14 06:58:26 (none) local0.warn innominer_T2: 3: Found chip 9 with 9 active cores
Jan 14 06:58:26 (none) local0.warn innominer_T2: 3: Found chip 10 with 9 active cores
Jan 14 06:58:26 (none) local0.warn innominer_T2: 3: Found chip 11 with 9 active cores
Jan 14 06:58:26 (none) local0.warn innominer_T2: 3: Found chip 12 with 9 active cores
Jan 14 06:58:26 (none) local0.warn innominer_T2: 3: Found chip 13 with 9 active cores
Jan 14 06:58:26 (none) local0.warn innominer_T2: 3: Found chip 14 with 9 active cores
Jan 14 06:58:26 (none) local0.warn innominer_T2: 3: Found chip 15 with 9 active cores
Jan 14 06:58:26 (none) local0.warn innominer_T2: 3: Found chip 16 with 9 active cores
Jan 14 06:58:26 (none) local0.warn innominer_T2: 3: Found chip 17 with 9 active cores
Jan 14 06:58:26 (none) local0.warn innominer_T2: 3: Found chip 18 with 9 active cores
Jan 14 06:58:26 (none) local0.warn innominer_T2: 3: Found chip 19 with 9 active cores
Jan 14 06:58:26 (none) local0.warn innominer_T2: 3: Found chip 20 with 9 active cores
Jan 14 06:58:26 (none) local0.warn innominer_T2: 3: Found chip 21 with 9 active cores
Jan 14 06:58:26 (none) local0.warn innominer_T2: 3: Found chip 22 with 9 active cores
Jan 14 06:58:26 (none) local0.warn innominer_T2: 3: Found chip 23 with 9 active cores
Jan 14 06:58:26 (none) local0.warn innominer_T2: 3: Found chip 24 with 9 active cores
Jan 14 06:58:26 (none) local0.warn innominer_T2: 3: Found chip 25 with 9 active cores
Jan 14 06:58:26 (none) local0.warn innominer_T2: 3: Found chip 26 with 9 active cores
Jan 14 06:58:26 (none) local0.warn innominer_T2: 3: Found chip 27 with 9 active cores
Jan 14 06:58:26 (none) local0.warn innominer_T2: 3: Found chip 28 with 9 active cores
Jan 14 06:58:26 (none) local0.warn innominer_T2: 3: Found chip 29 with 9 active cores
Jan 14 06:58:26 (none) local0.warn innominer_T2: 3: Found chip 30 with 9 active cores
Jan 14 06:58:26 (none) local0.warn innominer_T2: 3: Found chip 31 with 9 active cores
Jan 14 06:58:26 (none) local0.warn innominer_T2: 3: Found chip 32 with 9 active cores
Jan 14 06:58:26 (none) local0.warn innominer_T2: 3: Found chip 33 with 9 active cores
Jan 14 06:58:26 (none) local0.warn innominer_T2: 3: Found chip 34 with 9 active cores
Jan 14 06:58:26 (none) local0.warn innominer_T2: 3: Found chip 35 with 9 active cores
Jan 14 06:58:26 (none) local0.warn innominer_T2: 3: Found chip 36 with 9 active cores
Jan 14 06:58:26 (none) local0.warn innominer_T2: 3: Found chip 37 with 9 active cores
Jan 14 06:58:26 (none) local0.warn innominer_T2: 3: Found chip 38 with 9 active cores
Jan 14 06:58:26 (none) local0.warn innominer_T2: 3: Found chip 39 with 9 active cores
Jan 14 06:58:27 (none) local0.warn innominer_T2: 3: Found chip 40 with 9 active cores
Jan 14 06:58:27 (none) local0.warn innominer_T2: 3: Found chip 41 with 9 active cores
Jan 14 06:58:27 (none) local0.warn innominer_T2: 3: Found chip 42 with 9 active cores
Jan 14 06:58:27 (none) local0.warn innominer_T2: 3: Found chip 43 with 9 active cores
Jan 14 06:58:27 (none) local0.warn innominer_T2: 3: Found chip 44 with 9 active cores
Jan 14 06:58:27 (none) local0.warn innominer_T2: 3: Found chip 45 with 9 active cores
Jan 14 06:58:27 (none) local0.warn innominer_T2: 3: Found chip 46 with 9 active cores
Jan 14 06:58:27 (none) local0.warn innominer_T2: 3: Found chip 47 with 9 active cores
Jan 14 06:58:27 (none) local0.warn innominer_T2: 3: Found chip 48 with 9 active cores
Jan 14 06:58:27 (none) local0.warn innominer_T2: 3: Found chip 49 with 9 active cores
Jan 14 06:58:27 (none) local0.warn innominer_T2: 3: Found chip 50 with 9 active cores
Jan 14 06:58:27 (none) local0.warn innominer_T2: 3: Found chip 51 with 9 active cores
Jan 14 06:58:27 (none) local0.warn innominer_T2: 3: Found chip 52 with 9 active cores
Jan 14 06:58:27 (none) local0.warn innominer_T2: 3: Found chip 53 with 9 active cores
Jan 14 06:58:27 (none) local0.warn innominer_T2: 3: Found chip 54 with 9 active cores
Jan 14 06:58:27 (none) local0.warn innominer_T2: 3: Found chip 55 with 9 active cores
Jan 14 06:58:27 (none) local0.warn innominer_T2: 3: Found chip 56 with 9 active cores
Jan 14 06:58:27 (none) local0.warn innominer_T2: 3: Found chip 57 with 9 active cores
Jan 14 06:58:27 (none) local0.warn innominer_T2: 3: Found chip 58 with 9 active cores
Jan 14 06:58:27 (none) local0.warn innominer_T2: 3: Found chip 59 with 9 active cores
Jan 14 06:58:27 (none) local0.warn innominer_T2: 3: Found chip 60 with 9 active cores
Jan 14 06:58:27 (none) local0.warn innominer_T2: 3: Found chip 61 with 9 active cores
Jan 14 06:58:27 (none) local0.warn innominer_T2: 3: Found chip 62 with 9 active cores
Jan 14 06:58:27 (none) local0.warn innominer_T2: 3: Found chip 63 with 9 active cores
Jan 14 06:58:27 (none) local0.warn innominer_T2: 3: Found chip 64 with 9 active cores
Jan 14 06:58:27 (none) local0.warn innominer_T2: 3: Found chip 65 with 9 active cores
Jan 14 06:58:27 (none) local0.warn innominer_T2: 3: Found chip 66 with 9 active cores
Jan 14 06:58:27 (none) local0.warn innominer_T2: 3: Found chip 67 with 9 active cores
Jan 14 06:58:27 (none) local0.warn innominer_T2: 3: Found chip 68 with 9 active cores
Jan 14 06:58:27 (none) local0.warn innominer_T2: 3: Found chip 69 with 9 active cores
Jan 14 06:58:27 (none) local0.warn innominer_T2: 3: Found chip 70 with 9 active cores
Jan 14 06:58:27 (none) local0.warn innominer_T2: 3: Found chip 71 with 9 active cores
Jan 14 06:58:27 (none) local0.warn innominer_T2: 3: Found chip 72 with 9 active cores
Jan 14 06:58:27 (none) local0.warn innominer_T2: [chain_ID:3]: Found 72 Chips With Total 648 Active Cores
Jan 14 06:58:27 (none) local0.warn innominer_T2: [chain_ID]: Temp:523
Jan 14 06:58:27 (none) local0.warn innominer_T2: Detected the 3 A1 chain with 72 chips
Jan 14 06:58:27 (none) local0.warn innominer_T2: Detected the 3 A1 chain with 72 chips / 648 cores
Jan 14 06:58:27 (none) local0.notice cgminer[8070]: Probing for an alive pool
Jan 14 06:58:27 (none) local0.info cgminer[8070]: Testing pool stratum+tcp://ltc.s.innomining.com:1900
Jan 14 06:58:27 (none) local0.err cgminer[8070]: ------POOL ACTIVE  FOR XNSUB------
Jan 14 06:58:29 (none) local0.info cgminer[8070]: Stratum authorisation success for pool 0
Jan 14 06:58:29 (none) local0.info cgminer[8070]: Pool 0 stratum+tcp://ltc.s.innomining.com:1900 alive
Jan 14 06:58:29 (none) local0.notice cgminer[8070]: Pool 0 difficulty changed to 32768
Jan 14 06:58:29 (none) local0.info cgminer[8070]: recieve notify,we must flush work
Jan 14 06:58:29 (none) local0.notice cgminer[8070]: Network diff set to 3.54M
Jan 14 06:58:29 (none) local0.info cgminer[8070]: New block: 10c2fe220f3271b722a680f9ce1783a0ae48d635da0248b3d9d0dfde29f139b9... diff 3.54M
Jan 14 06:58:29 (none) local0.info cgminer[8070]: Work update message received
Jan 14 06:58:29 (none) local0.info cgminer[8070]: Testing pool stratum+tcp://ltc.s.innomining.com:1900
Jan 14 06:58:29 (none) local0.err cgminer[8070]: 3: A1_scanwork first in set all parameter!
Jan 14 06:58:29 (none) local0.err cgminer[8070]: 0: A1_scanwork first in set all parameter!
Jan 14 06:58:29 (none) local0.err cgminer[8070]: 1: A1_scanwork first in set all parameter!
Jan 14 06:58:30 (none) local0.err cgminer[8070]: A1_scanwork n cid 3:arv:36.00, lest:23.33, hest:522 witt
Jan 14 06:58:30 (none) local0.err cgminer[8070]: A1_scanwork n cid 0:arv:37.33, lest:24.67, hest:515 witt
Jan 14 06:58:30 (none) local0.err cgminer[8070]: A1_scanwork n cid 1:arv:36.00, lest:20.67, hest:521 witt
Jan 14 06:58:30 (none) local0.info cgminer[8070]: recieve notify,we must flush work
Jan 14 06:58:30 (none) local0.info cgminer[8070]: Work update message received
Jan 14 06:58:34 (none) local0.warn cgminer[8070]: API running in local read access mode on port 4028 (13)
Jan 14 06:58:34 (none) local0.info cgminer[8070]: Testing pool stratum+tcp://ltc.s.innomining.com:1900
Jan 14 06:58:36 (none) local0.info cgminer[8070]: recieve notify,we must flush work
Jan 14 06:58:36 (none) local0.info cgminer[8070]: New block: 0a1c8b4c347eec5eb233d97ade8b473714bc80e39a583a134c9a9c8783580ece... diff 3.54M
Jan 14 06:58:36 (none) local0.notice cgminer[8070]: Stratum from pool 0 detected new block at height 1349993
Jan 14 06:58:36 (none) local0.info cgminer[8070]: Work update message received
Jan 14 06:58:39 (none) local0.info cgminer[8070]: Testing pool stratum+tcp://ltc.s.innomining.com:1900
Jan 14 06:58:40 (none) local0.err cgminer[8070]: A1_scanwork n cid 3:arv:38.00, lest:24.00, hest:519 witt
Jan 14 06:58:40 (none) local0.err cgminer[8070]: A1_scanwork n cid 1:arv:38.00, lest:22.00, hest:518 witt
Jan 14 06:58:40 (none) local0.err cgminer[8070]: A1_scanwork n cid 0:arv:39.33, lest:25.33, hest:513 witt
Jan 14 06:58:41 (none) local0.info cgminer[8070]: New best share: 69.5K
Jan 14 06:58:41 (none) local0.info cgminer[8070]: Submitting share f160aa7e to pool 0
Jan 14 06:58:41 (none) local0.info cgminer[8070]: YEAH: 1: chip 53 / job_id 1: nonce 0x1424ac00
newbie
Activity: 66
Merit: 0
January 12, 2018, 12:31:29 AM
what is the best temperature?

and how can i see the temp in awesome miner?

newbie
Activity: 1
Merit: 0
January 10, 2018, 04:17:33 PM
Hi,

I placed an order for 10 units on 12/21. It took my bank several days to confirm the wire as they wanted to make sure I wasn't getting ripped off. Innosilicon confirmed my wire on 12/29.

On 1/3, they provided me with a DHL tracking number and I received my units today!

I have put four into service and they all seem to be working as expected within their stated +- 8%.

They came with firmware dated 12/29 and I've only updated 1 of them to the latest version...

Does anyone have the 12/29 firmware version? I updated the one but I'd like to compare the performance to the earlier version.

Running the Jan 5th firmware.
More stable.
More overclock options
now running at 700mh/s and barely warm.

Hello all,

I've had my A4+ up and running for a few days off and on again. I finally got it to take the upgrade to the Jan 5th firmware. Fan speed has now run as low as 40%, and I no longer get the incremental HW errors or whatever those were indicating. They could be as high as 36 after running all night.

I've got mine inside a Macgyverd OSB coffin with 2 AC dust filters at each end and a $20 wall mart fan to push cool air in and hot air out of the coffin/ tube. I'm running it in a large RV building and not taking any chances with dust! BTW this is all a temp setup as I give that fan about 1 week before it burns up Smiley

Gazdac2, care to share the settings you are using to overclock to 700mh/s? Smiley

Anyone else, what would be considered a "safe" temp range for the miners? Either measured at the input air, chip, or output temp. I'm planning to build a fairly elaborate setup with some temp sensors and relays to control all sorts of things like AC units, fans, miner power supplies, etc. and want to have an idea for what I should be shooting for. I'm setup in Florida so I'm doing the reverse GoT, "Summer is coming". BTW I have dirt cheap if not free power through my hot headed friend Sol.







jr. member
Activity: 35
Merit: 3
January 10, 2018, 01:49:23 PM
Hi,

just started to Setup my new A4+ (first time ever that I Setup a miner).

I have uploaded the new Firmware, Settings seem OK.
However:

Even after 5hours operating, I still see in the "Minor Status" site only three rotating asterixes ("Sanduhren"). No Contents/ results, only the template
Sometimes the fan Speeds up.

Who can help?



check the network configurations, specially Gateway

make sure that the miner can reach internet
 
jr. member
Activity: 35
Merit: 3
January 10, 2018, 12:24:56 PM
Hi,

I placed an order for 10 units on 12/21. It took my bank several days to confirm the wire as they wanted to make sure I wasn't getting ripped off. Innosilicon confirmed my wire on 12/29.

On 1/3, they provided me with a DHL tracking number and I received my units today!

I have put four into service and they all seem to be working as expected within their stated +- 8%.

They came with firmware dated 12/29 and I've only updated 1 of them to the latest version...

Does anyone have the 12/29 firmware version? I updated the one but I'd like to compare the performance to the earlier version.

based on my expeciance since Nov firmware, the latest version 5 Jan 2018 is the most stable in the hashrate in the long run
Code:
http://www.innosilicon.com.cn/download/update_180105.bin
newbie
Activity: 35
Merit: 0
January 10, 2018, 04:18:01 AM
Hi,

just started to Setup my new A4+ (first time ever that I Setup a miner).

I have uploaded the new Firmware, Settings seem OK.
However:

Even after 5hours operating, I still see in the "Minor Status" site only three rotating asterixes ("Sanduhren"). No Contents/ results, only the template
Sometimes the fan Speeds up.

Who can help?



This means your miner has booted but is not mining.
fans will speed up when it resets, or tries again.
If it is more than 5 minutes for mining stats to show then there is a problem. stats will NEVER show before 3 minutes.
First check your pool settings. Enter them again, even if they seem correct. Try another pool.
Make sure the  network settings match your internet connection. netmask and gateway are important.

After that, maybe more voltage, But  that's the extent of what you can do without telnet into the linux. probably faster to log onto chat with inno support.





newbie
Activity: 1
Merit: 0
January 10, 2018, 03:57:01 AM
Hi,

just started to Setup my new A4+ (first time ever that I Setup a miner).

I have uploaded the new Firmware, Settings seem OK.
However:

Even after 5hours operating, I still see in the "Minor Status" site only three rotating asterixes ("Sanduhren"). No Contents/ results, only the template
Sometimes the fan Speeds up.

Who can help?

 


newbie
Activity: 35
Merit: 0
January 10, 2018, 12:43:42 AM
Hi,

I placed an order for 10 units on 12/21. It took my bank several days to confirm the wire as they wanted to make sure I wasn't getting ripped off. Innosilicon confirmed my wire on 12/29.

On 1/3, they provided me with a DHL tracking number and I received my units today!

I have put four into service and they all seem to be working as expected within their stated +- 8%.

They came with firmware dated 12/29 and I've only updated 1 of them to the latest version...

Does anyone have the 12/29 firmware version? I updated the one but I'd like to compare the performance to the earlier version.

Running the Jan 5th firmware.
More stable.
More overclock options
now running at 700mh/s and barely warm.
full member
Activity: 167
Merit: 100
January 09, 2018, 10:54:13 PM
Wow, glad to here you received them. Must of been the Christmas batch to ship already.

I made an order on Dec 14th for 18-28th batch. Haven't heard anything back from Inno? I paid in LTC.

What communication channel is best? I have been told skype, trying to verify correct skype account.

My one reply via email from Inno only mentioned they would ship soon. This was 6 days ago.
newbie
Activity: 2
Merit: 0
January 09, 2018, 10:40:58 PM
Hi,

I placed an order for 10 units on 12/21. It took my bank several days to confirm the wire as they wanted to make sure I wasn't getting ripped off. Innosilicon confirmed my wire on 12/29.

On 1/3, they provided me with a DHL tracking number and I received my units today!

I have put four into service and they all seem to be working as expected within their stated +- 8%.

They came with firmware dated 12/29 and I've only updated 1 of them to the latest version...

Does anyone have the 12/29 firmware version? I updated the one but I'd like to compare the performance to the earlier version.
full member
Activity: 167
Merit: 100
January 09, 2018, 10:18:18 PM
Hello Everyone,  I would first like to think everyone who’s has contributed to this thread very informative.

I just received my A4+ yesterday and have a few issues to get worked out.  It looks like mine is a G19 and a build date of December 15.



Out of curiosity what was your order date and expected delivery of your batch?

Trying to figure out were Inno is at with order deliveries.
jr. member
Activity: 35
Merit: 3
January 09, 2018, 03:46:08 PM
Hello Everyone,  I would first like to think everyone who’s has contributed to this thread very informative.

I just received my A4+ yesterday and have a few issues to get worked out.  It looks like mine is a G19 and a build date of December 15.

First question is should I do the upgrade first before configuring network IP address?  I noticed accessing the browser was a little buggy and had to be constantly restarted.  It also hanged up a lot when accessing different  tabs.  I just didn’t want to lose access while in middle of update so haven’t updated yet.

I think because my gate way is 10.0.0.1 I need to use the network cross cable method to configure IP address correctly. 

I did change my gateway to 192.168.1.1 which allowed me to access 192.168.1.254.  The problem is all other devices are 10.0.0.* on network including an Antminer S9 which went offline.

The steps I plan to take to tackle the IP configuration.
1. Change gateway back to 10.0.0.1.
2. Then take a crossover cable and connect A4+ to laptop off network.
3. Go into the settings on laptop and change IP address to 192.168.1.1.  Try to access A4+ with 192.168.1.254 and change Network to DCHP.
4. Change laptop back to dynamic IP
5. Reconnect A4+ and laptop back onto 10.0.0.1 gateway.
6. Look up new IP address for A4+
7. Hope this address allows connection.

I want to make sure to do firmware update correctly so here are my step
1. Download latest build Jan###
2. Save to desktop
3. Access miner from browser
4. Go to update tab
5. Select file to update
6. Run
7. Keep fingers crossed!

Hopefully this make the browser less buggy!

Thanks for any insight to these steps about to be performed.

Also, what PSU are you guys using?  I thought I was getting a Innosilicon version, but was shipped a 1850 watt PSU that is European voltage 180-240 volt with yellow & black leads. 

I ended up testing with Bitmain power supply.

I’m in process of upgrading circuit to 220 volt to run both miners on same circuit.

Any thoughts?

Thanks.

Chance


i would do it this sequence easier - before you change your gateway back

1. Go into the settings on laptop and change IP address to 192.168.1.1.  Try to access A4+ with 192.168.1.254 and change Network to DCHP.
2. Change gateway back to 10.0.0.1.
3. Change laptop back to dynamic IP
4. Reconnect A4+ and laptop back onto 10.0.0.1 gateway.
5. Look up new IP address for A4+
6. Hope this address allows connection.
newbie
Activity: 49
Merit: 0
January 09, 2018, 11:30:06 AM
New firmware out today update_180105

for me fixed the miners that refused to start mining

do u have a link for download the update ? I can't find it on their website.

It is there, while maybe slightly hidden. Here's a direct link: http://www.innosilicon.com.cn/download/update_180105.bin

It may take some time to download (or even to start the download).
member
Activity: 98
Merit: 10
January 09, 2018, 10:58:41 AM
New firmware out today update_180105

for me fixed the miners that refused to start mining

do u have a link for download the update ? I can't find it on their website.
jr. member
Activity: 35
Merit: 3
January 09, 2018, 09:56:59 AM
Hello. I bought an ASIC, previously configured. Someone changed the password 12345678 to another. An instruction is required to reset the ASIC A4 + Dominator password. Specified in the instruction 12345678, does not accept
Resetting to factory settings - does not help. Is it possible to configure via telnet? thanks for the help

telnet to the box and execute the following command

Code:
cat /innocfg/www/conf/password

it will show you the current password
then you can change it to what ever you want from the Web interface
jr. member
Activity: 35
Merit: 3
January 08, 2018, 04:05:14 PM
Well... a few days with 50 A4+ now and they really do suck.

I've got all 50 in Awesome Miner so I know when they stop mining and the stats aren't good.
If I mine on a pool that isn't 100% stable/efficient they can't handle it and where I assume the AntMiner D3s/S9s I have just deals with it  and pick up where it left off the A4+ stops mining and restarts the mining process, losing you 5-10minutes of shares. NiceHash is a complete no-go too, they're can't handle it for some reason (vardiff?)

I'm using litecoinpool.org and this does appear to have helped stability. will update again in a few days.

The difficulty the pool gives you just adjusts the amount of work you do before returning results.  Giving you a low difficulty when you have a high hash rate means that you're banging the server more frequently, asking for more work and returning results, which will greatly increase server loads, which can kill your pool.

those are the work around I can think of to help with this

Option 1
try to split your 50 miners over the 4 servers of Litecoinpool
stratum+tcp://litecoinpool.org:3333   (Europe)
stratum+tcp://us.litecoinpool.org:3333   (US East Coast)
stratum+tcp://us2.litecoinpool.org:3333   (US West Coast)
stratum+tcp://ltcpool5brio2gaj.onion:3333   (Tor hidden service)
this might help you to decrease your hits to one server and hence lower the diff you will be given

Option 2

split the miners over multiple litecoinpool accounts not workers


Option 3

spit the miners over multiple real IP's

I hope any of those helps
jr. member
Activity: 35
Merit: 3
January 08, 2018, 03:49:11 PM
the replacement fan is available on Ebay between 8$ to 11$ a piece
just search on Ebay for "delta 120mm fan 6000rpm 4-Pin connector"
Pages:
Jump to: