Bitcoin Forum

Alternate cryptocurrencies => Mining (Altcoins) => Topic started by: diaahussein on December 08, 2017, 09:54:17 PM



Title: Innosilicon A4+ setup tutorial
Post by: diaahussein on December 08, 2017, 09:54:17 PM
I just received my A4+ and I am posting here to help on how setup it

I will start with the basic configs then i will add another section for Advanced Settings and configs

the Miner comes with a standard IP of 192.168.1.254 which can be accessed by Webbroswer

general note: the miner interface is a bit sloppy with understanding Enter for submit you need to clock on the button by the mouse in the password forms or any other form

Basic Config

First upgrade your miner to the latest firmware

  • Change your computer IP address to be within the range lets say 192.168.1.90
  • Open your browser and enter Http://192.168.1.254
  • Click System
  • Go to Upgrade
  • Download the latest firmware from Innosilicon from http://www.innosilicon.com.cn/download/update.bin (http://www.innosilicon.com.cn/download/update.bin)
  • upgrade your firmware to the latest and wait for the upgrade to be completed the Miner will restart after the upgrade is done
  • Log back to your miner

Second Step : Change Miner IP
  • Open your browser and enter Http://192.168.1.254
  • Click on Network and change the IP address/Mask/Gateway to your network range
  • the miner will restart and direct you to the new IP

Third Step : Configure your Pool

  • Open your browser and enter your Miner IP
  • Click Miner Configurations
  • Go to end of the page
  • Click Config
  • Enter the password "12345678"
  • Click login
  • in Pool 1 URL Enter your pool Address Including the stratum+tcp://yourpooladress:port
  • Enter Worker Name from your pool example: Worker.1
  • Enter worker password example : 1
  • Click Submit
  • the miner will restart and start Mining to your new pool info

Fourth Step : Change Config Password
  • Open your browser and enter your Miner IP
  • Click on System
  • Click on administration
  • Enter Old Password "12345678"
  • Enter new Password
  • repeat new Password
  • Click submit

you are done with the basic setup now and your miner is up and running

Advanced Configs

Innosilicon have changed the root password in the 22nd Dec firmware release
root access is no longer supported until the new root password is cracked


New root Password for 22nd Dec Firmware is  
Quote
t1t2t3a5
Old root Password is  
Quote
innot1t2

thanks for Funbuxx for cracking both passwords https://bitcointalk.org/index.php?action=profile;u=1151278
 (https://bitcointalk.org/index.php?action=profile;u=1151278)

telnet is available on this miner on port 8100

you will need Putty or your favorite telnet program

for firmware after 22 Dec:
Before doing any of the advances configs you need to make the root file system read-write
follow the below post to change the filesystem to read-write

https://bitcointalk.org/index.php?topic=2549898.msg26944688#msg26944688 (https://bitcointalk.org/index.php?topic=2549898.msg26944688#msg26944688)

Change root Password
  • telnet to your Miner IP and port 8100
  • Enter Username : root
  • Enter Password : innot1t2
  • passrwd
  • Enter new Password
  • repeat new Password


Add web API Management support on Miner for "Awesome Miner monitor"
  • telnet to your Miner IP and port 8100 with root and your new password
  • type "cd /home/inno_py/"
  • type "cp /home/inno_py/inno_config.py ./inno_config.py.bk" to take a backup of your file before editing
  • type "vi /home/inno_py/inno_config.py" to erdit your config file
  • scroll down until you see the value gInnoInitCmdStr
  • click the letter i on the keyboard to enable edit mode in vi
  • at the end of that line replace "--api-listen" with "--api-listen --api-network --api-allow W:0/0" this will enable network privileged access from API
  • Click  "ESC" on the keyboard to exit Edit Mode
  • click ":wq" and Enter to save the file
  • type reboot to reboot your miner and for changes to take effect

Change web Port
  • telnet to your Miner IP and port 8100 with root and your new password
  • cd /etc/init.d/
  • type "cp /etc/init.d/rcS /etc/init.d/rcS.bk" to backup your file
  • type "vi /etc/init.d/rcS" to edit your startup file
  • click the letter i on the keyboard to enable edit mode in vi
  • find "httpd -h /home/www -p 80" and replace 80 with your new port you wish to use
  • Click  "ESC" on the keyboard to exit Edit Mode
  • click ":wq" and Enter to save the file
  • type reboot to reboot your miner and for changes to take effect

Change telnet port
  • telnet to your Miner IP and port 8100 with root and your new password
  • cd /etc/init.d/
  • type "cp /etc/init.d/rcS /etc/init.d/rcS.bk" to backup your file
  • type "vi /etc/init.d/rcS" to edit your startup file
  • click the letter i on the keyboard to enable edit mode in vi
  • find "telnetd -p 8100" and replace 8100 with your new port you wish to use
  • Click  "ESC" on the keyboard to exit Edit Mode
  • click ":wq" and Enter to save the file
  • type reboot to reboot your miner and for changes to take effect


Title: Re: Innosilicon A4+ setup tutorial
Post by: diaahussein on December 09, 2017, 07:24:17 PM
Advanced Configs


Enable crond for scheduled tasks

  • telnet to your Miner IP and port 8100 with root and your new password
  • cp /etc/init.d/rcS /etc/init.d/rcS.bk
  • type "vi /etc/init.d/rcS"
  • press "i" to enable edit mode
  • add a line at before the telnet line "crond -c /home/inno_tools/Crontab"
  • presss "esc" then ":wq" to save the changes
  • type "mkdir /home/inno_tools/Crontab"
  • type "crontab -c /home/inno_tools/Crontab -e"
]
  • press "i" to enable edit mode
  • add your scheduled tasks in the cron format
  • presss "esc" then ":wq" to save the changes
  • type "crond -c /home/inno_tools/Crontab"


General Comments


there is 2 Models of the A4+ (G9 and G19 ) it is pure luck which one you will get

for the G9 do not set the voltage manual as it does not handle it well and you will get a very low hashrate make the software automatic select it
the G9 can handle the Manual voltage selection although i would still recommend to automatic select it by the software


Title: Re: Innosilicon A4+ setup tutorial
Post by: sevenmiles on December 09, 2017, 08:13:30 PM
ok, any idea how to change the fan setting on this A4+ machine?
the fan is always operating at 100%, and the sound is like plane ...

all other asic miners, antminer, baikal miner, could change the fan setting and speed ... at least I would not have 80 db plane in my room...


but this innosilicon A4+ is a noise beast !!  :-[ :-[ :-[ :-[ :-[


Title: Re: Innosilicon A4+ setup tutorial
Post by: diaahussein on December 09, 2017, 10:58:41 PM
I could not agree with you more, i hate how noisy it is.
I am already looking for a way to control the fan speed as we speak
will update you as i find one :)


Title: Re: Innosilicon A4+ setup tutorial
Post by: diaahussein on December 16, 2017, 12:34:53 PM
the new firmware released yesterday seems to lower the fan speed to 70% which made it quieter


Title: Re: Innosilicon A4+ setup tutorial
Post by: needed357 on December 16, 2017, 05:54:04 PM
how long did you wait?

are they really deliver the prebatch end of this year if i order now?


Title: Re: Innosilicon A4+ setup tutorial
Post by: diaahussein on December 16, 2017, 08:04:51 PM
I Pre-ordered in Nov 1st and i received the shipment on Dec 5th

It seems that they handle the pre-order well or that was my case

to be honest I heard that some of the other guys who ordered the old A4 were complaining about the delay

but for me nothing happened


Title: Re: Innosilicon A4+ setup tutorial
Post by: needed357 on December 16, 2017, 11:32:49 PM
I Pre-ordered in Nov 1st and i received the shipment on Dec 5th

It seems that they handle the pre-order well or that was my case

to be honest I heard that some of the other guys who ordered the old A4 were complaining about the delay

but for me nothing happened


i just orderd a week ago and don get any confirmation.. :(

did you get any pay confirm?


Title: Re: Innosilicon A4+ setup tutorial
Post by: diaahussein on December 17, 2017, 10:11:09 AM
I had to chase them for the confirmation it took about 10 days
open the case on their website
and send Emails to
luojm@innosilicon.com.cn,
zhangq@innosilicon.com.cn,
miner_sales@innosilicon.com.cn,
shupp@innosilicon.com.cn
with your order number


Title: Re: Innosilicon A4+ setup tutorial
Post by: diaahussein on December 17, 2017, 07:08:37 PM
any one has this miner and facing low hash rate
i have one miner that is hitting below 500 in the pool while the other one is working perfectly
when i checked the logs i found that the slow miner is giving the following errors

Quote
Dec 17 18:04:06 (none) local0.err innominer_T2: Notice chain 2 maybe has some promble in voltage
Quote
Dec 17 18:04:08 (none) local0.err innominer_T2: Notice chain 3 maybe has some promble in voltage


and it is giving me a lot of HW errors 620 Error
Quote
BA1 3: invalid nonce - HW error

any advise


Title: Re: Innosilicon A4+ setup tutorial
Post by: diaahussein on December 20, 2017, 08:18:48 AM
I noticed that the hash rate is dropped when i select the Voltage manually
if i let the software select it automaticly the hash is Higher but still lower than the other A4+ i have
This Miner is T9 while the other one is T19


Title: Re: Innosilicon A4+ setup tutorial
Post by: Gazdac2 on December 21, 2017, 10:21:41 AM
Thanks for the telnet info.

Funny to hear how quickly some of you got your miners. It took an average of 2 weeks and 5 emails  to get a response from them, for EVERY exchange. even after i replied/paid within 24 hours.

Ordered on Sep 6th, and I see that people that ordered 1+ months after me got theirs earlier. That's pretty annoying. When I asked them whats going on, since I just lost ALL my investors for a 2nd order, they replied with a tracking number. So Yay I got miners, and Boo on their customer service.

Now I'm off to email them because one of the miners stopped working after an hour. There's no TF slot in any of my machines, so Hopefully telnet wont die before I can fix it.


Title: Re: Innosilicon A4+ setup tutorial
Post by: Gazdac2 on December 22, 2017, 08:34:23 AM
For those that might have the same problem. Looks like my a4+ corrupted files during  a reboot  then stopped working.
/home/inno_tools/start_miner.py

The damn thing deleted a couple characters and killed itself.
Here's what the file looked like

vi /lib/python3.4/_sysconfigdata.py...

 'HAVE_GETLOGIN': 1,
 'HAVE_GETNAMEINFO': 1,
 'HAVE_GETPAGESIZE': 1,
E_GETPEERNAME': 1,
 'HAVE_GETPGID': 1,
 'HAVE_GETPGRP': 1,
...

There might have been more errors, i dunno. I coped the file from another miner and now it works.
Symptoms were the HTTP control page loading, but not showing any data e.g. not showing me  "miner type" under system.
I found the file by manually running each of the commands in /etc/init.d/rcS

Good luck to the rest of you.



Title: Re: Innosilicon A4+ setup tutorial
Post by: LICC on December 22, 2017, 01:41:15 PM
my A4+ miner worked only one day. Now, after the restart, usually no LED lights, LAN also does not light up. Sometimes after retset LAN lights up, but the miner still does not connect to the network. I think that the firmware has died. Is it possible to fill the firmware here in any way? G19 does not have a card reader unfortunately.


Title: Re: Innosilicon A4+ setup tutorial
Post by: Gazdac2 on December 22, 2017, 01:55:48 PM
my A4+ miner worked only one day. Now, after the restart, usually no LED lights, LAN also does not light up. Sometimes after retset LAN lights up, but the miner still does not connect to the network. I think that the firmware has died. Is it possible to fill the firmware here in any way? G19 does not have a card reader unfortunately.

 my miners reset to 192.168.1.254 all the time. Check that address?


Title: Re: Innosilicon A4+ setup tutorial
Post by: LICC on December 22, 2017, 03:34:24 PM
of course, many times. After turning on the LEDs do not light, only the fans are buzzing and the green LEDs on the blades.
https://www.youtube.com/watch?v=aqYStcgbCcI (https://www.youtube.com/watch?v=aqYStcgbCcI)


Title: Re: Innosilicon A4+ setup tutorial
Post by: Gazdac2 on December 22, 2017, 07:28:42 PM
of course, many times. After turning on the LEDs do not light, only the fans are buzzing and the green LEDs on the blades.
https://www.youtube.com/watch?v=aqYStcgbCcI (https://www.youtube.com/watch?v=aqYStcgbCcI)

Yeah I had hoped you tried everything reasonable already like changing the cables out. The only other thing I would try is booting  connected directly to your PC, and put your PC on the same subnet (just like the setup docs on inno webpage) you could at least eliminate your networking hardware as a cause.

I haven't ever used mine, and I can't even find it right now, but you might be able to logon to the Pi  with a TTL cable and troubleshoot with telnet https://www.sparkfun.com/products/12977

Did inno have anything to say yet?
And why the hell did they leave off that 6 cent part from our $3000 machine?
I'm guessing aside from soldering your own TF card holder onto there, the next step is Returning the control board. Really sad.
Guess I'm just lucky the corrupted files on mine were after network init.




Title: Re: Innosilicon A4+ setup tutorial
Post by: Miner31415 on December 22, 2017, 11:53:33 PM
I am a first time miner and set up the a4+ miner two days ago using the innosilicon PSU in my garage, but there have been problems. Firstly, of the 4 boards 2 have reported themselves, "dead" (0 and 1) and that was fixed by restarting it. However, today board 3 has decided to stop working and even after restarting the lights turn on for a few minutes, then turn off. I am not sure what is causing this problem and here are my views:

1. There are no loose parts rattling around inside, so there are no shorts
2. The temperature is too cold (The air temperature is about -5C (20F) and at max the miner hits 40C (104) and has an average of 28C (80F). Is this too cold?
3. The power supply may be providing unclean power

If I have to return it, does anyone know what Innosilicon's warranty service is.


Title: Re: Innosilicon A4+ setup tutorial
Post by: Gazdac2 on December 23, 2017, 12:21:57 AM
I am a first time miner and set up the a4+ miner two days ago using the innosilicon PSU in my garage, but there have been problems. Firstly, of the 4 boards 2 have reported themselves, "dead" (0 and 1) and that was fixed by restarting it. However, today board 3 has decided to stop working and even after restarting the lights turn on for a few minutes, then turn off. I am not sure what is causing this problem and here are my views:

1. There are no loose parts rattling around inside, so there are no shorts
2. The temperature is too cold (The air temperature is about -5C (20F) and at max the miner hits 40C (104) and has an average of 28C (80F). Is this too cold?
3. The power supply may be providing unclean power

If I have to return it, does anyone know what Innosilicon's warranty service is.

1,3)Maybe you need to adjust voltages. I thought they said something like "G9 needs auto and G19 can be default."

1,3) if you swapped the power cables between the cards you might be able to tell if one of them isn't doing well.

I also was waiting for a new PSU, and used a cheapo to run one of them for now. The 750w psu cost about $150CAD and grabbed it locally. I needed to add one more power cable, so i used one of my SATA-6pin converters on the Pi board. I'm sure I'll use it in a GPU mining rig later anyways, so its not even wasting money. If you wanted to try that route.

2)My miners are happy at -15. Though the garage is now about +15. They are currently running about 30 average temp.

4)45 day warranty, email your sales person.


Title: Re: Innosilicon A4+ setup tutorial
Post by: Miner31415 on December 23, 2017, 03:40:53 AM

1,3)Maybe you need to adjust voltages. I thought they said something like "G9 needs auto and G19 can be default."



Thanks so much for the response. I tried to check all the cabling again, but even if I switch all the cables from a working miner to the broken one it lights up and then a few minutes later shuts down. I am not sure what to adjust the voltage to (My miner identifies as G19). Thanks


Title: Re: Innosilicon A4+ setup tutorial
Post by: LICC on December 23, 2017, 04:23:50 AM
Gazdac2,Many thanks.
 inno offers to change the miner. But very expensive delivery and a very long time to wait it. and they do not want to change the control board separately. the control board has connectors. They have RX and TX signals. Can I somehow connect to a computer to control this?
https://forum.bits.media/uploads/monthly_2017_12/IMG_0218.JPG.730d7c1b00945793fcf513f7107b4a41.JPG


Title: Re: Innosilicon A4+ setup tutorial
Post by: Gazdac2 on December 23, 2017, 09:21:32 AM


Thanks so much for the response. I tried to check all the cabling again, but even if I switch all the cables from a working miner to the broken one it lights up and then a few minutes later shuts down. I am not sure what to adjust the voltage to (My miner identifies as G19). Thanks

Yeah my G19 's are all at VID 25(default) for the voltage. I ran it on auto for a while and didn't see a difference.


Title: Re: Innosilicon A4+ setup tutorial
Post by: Gazdac2 on December 23, 2017, 10:14:27 AM
Gazdac2,Many thanks.
 inno offers to change the miner. But very expensive delivery and a very long time to wait it. and they do not want to change the control board separately. the control board has connectors. They have RX and TX signals. Can I somehow connect to a computer to control this?
https://forum.bits.media/uploads/monthly_2017_12/IMG_0218.JPG.730d7c1b00945793fcf513f7107b4a41.JPG

Okay. Things are messy here.
Yes it's possible. I don't know if its enabled in the software though. If it works you get to telnet in directly to the board.
I'd probably try all sorts of rebooting and plugging and unplugging random ethernet cables to see if i can somehow get into telnet. if you can there's a chance to fix it.


Uhm. I'm also not willing to try this myself: but the microSD slot is just missing the  6 cent clip to hold the sd card in place. You could see if a cellphone/computer repair shop has one that would fit, or... as a bit of a laugh. sometimes you can tape the microSD in place,  and pray you don't bump it while files copy. Assuming they didn't just disable it in software.


Title: Re: Innosilicon A4+ setup tutorial
Post by: diaahussein on December 23, 2017, 01:25:27 PM
Inno has released a new firmware on 22nd
It is giving me a great hashrate on the pool so far
I will be testing and feed you back
   http://www.innosilicon.com.cn/download/update.bin   (http://www.innosilicon.com.cn/download/update.bin)


Title: Re: Innosilicon A4+ setup tutorial
Post by: diaahussein on December 23, 2017, 01:59:18 PM
For those that might have the same problem. Looks like my a4+ corrupted files during  a reboot  then stopped working.
/home/inno_tools/start_miner.py

The damn thing deleted a couple characters and killed itself.
Here's what the file looked like

vi /lib/python3.4/_sysconfigdata.py...

 'HAVE_GETLOGIN': 1,
 'HAVE_GETNAMEINFO': 1,
 'HAVE_GETPAGESIZE': 1,
E_GETPEERNAME': 1,
 'HAVE_GETPGID': 1,
 'HAVE_GETPGRP': 1,
...

There might have been more errors, i dunno. I coped the file from another miner and now it works.
Symptoms were the HTTP control page loading, but not showing any data e.g. not showing me  "miner type" under system.
I found the file by manually running each of the commands in /etc/init.d/rcS

Good luck to the rest of you.


In that case i would recommend to reflash the firmware and choose the option to restore factory config


Title: Re: Innosilicon A4+ setup tutorial
Post by: Howtrain on December 23, 2017, 02:36:51 PM
I just got the A4+, but I'm having problems connecting to the control page (192.168.1.254). I've changed the IP of my computer, checked that all the cables on the miner were fastened and in place, and ensured that the ethernet cable running from my router was giving an internet connection, but the control page still won't load and the red "fault" button flashes on the miner from time to time. Any ideas on how to fix this?


Title: Re: Innosilicon A4+ setup tutorial
Post by: diaahussein on December 23, 2017, 02:55:28 PM
I just got the A4+, but I'm having problems connecting to the control page (192.168.1.254). I've changed the IP of my computer, checked that all the cables on the miner were fastened and in place, and ensured that the ethernet cable running from my router was giving an internet connection, but the control page still won't load and the red "fault" button flashes on the miner from time to time. Any ideas on how to fix this?

I have not faced this
Are using the original PSU and have you connected it write 2 cables to each hash board and one cable to the control board


Title: Re: Innosilicon A4+ setup tutorial
Post by: Howtrain on December 23, 2017, 02:56:41 PM
Yes, it is the PSU from Innosilicon, and everything is connected properly.


Title: Re: Innosilicon A4+ setup tutorial
Post by: diaahussein on December 23, 2017, 04:17:55 PM
seems that the Miner has hardware issue
my advise contact the support


Title: Re: Innosilicon A4+ setup tutorial
Post by: diaahussein on December 23, 2017, 04:42:19 PM
Innosilicon have changed the root password in the 22nd Dec firmware release
root access is no longer supported until the new root password is cracked


Title: Re: Innosilicon A4+ setup tutorial
Post by: Gazdac2 on December 23, 2017, 09:32:05 PM
Innosilicon have changed the root password in the 22nd Dec firmware release
root access is no longer supported until the new root password is cracked

Root access is the only way I could repair my A4+, since there IS NO TF card slot, none of my miners can be flashed when they fail.

I've had to repair the software on one miner every day, so far. So, not looking good for the future of these things.







Title: Re: Innosilicon A4+ setup tutorial
Post by: cyberdeity on December 24, 2017, 03:59:59 AM
Would one of you mind posting just the cgminer.exe file from your newest firmware somewhere I can download (mega?) ?    I'd like to try using it on the original A4's I have to see if maybe it will hash faster.

Thanks!


Title: Re: Innosilicon A4+ setup tutorial
Post by: kb8679 on December 24, 2017, 09:40:37 AM
Innosilicon have changed the root password in the 22nd Dec firmware release
root access is no longer supported until the new root password is cracked

Root access is the only way I could repair my A4+, since there IS NO TF card slot, none of my miners can be flashed when they fail.

I've had to repair the software on one miner every day, so far. So, not looking good for the future of these things.







GOD DAMN INNO.... My miners are all G19 without the card slot.. so I feel VERY unsecure with the miners at the moment. I have had one issue which resulted in a bricked miner and was only recoverable by accessing the busybox and removing all ".pyc" files (some of them apparently got corrupted by unknown reason). Now that this is not an option.. I have asked for the password but I'm afraid they won't respond or don't share it.

I have been thinking about cracking the password but my skills in that area are limited to bruteforcing. If there is someone clever enough to give me some pointers for more sophisticated methods, they would be most appreciated... I
 made a wordlist for 8 characters long password, all starting with the word "inno" and rest characters are all lower & uppercase alphabets and numbers.

This method is slow as hell. If someone is willing to share the work (ie, I'd cut you half of the wordlist or sth), it would be also most appreciated.

EDIT:
The password wordlist: https://www.dropbox.com/s/5apflpal6rbs3ar/inno_pw.rar?dl=0
When unpacked it's ~130MB. :P


Title: Re: Innosilicon A4+ setup tutorial
Post by: kb8679 on December 24, 2017, 09:46:41 AM
Oh yeah.

These miners don't seem to like vardiff at all. What fixed value have you guys found to work best with these? I've used either 131072 or 262144. Both work fine for me but I'd like to hear what others are using..

EDIT: Can somebody explain what exacly is "HW". Some sort of error indicator, sure, but I'd like to know about it in more detail...
EDIT2: Since the latest FW update, I've found that at least some of the issues regarding the multicoin/vardiff pools are actually fixed. I've still seen "Dead" asic clusters but they are now appearing like once every 24h instead of just few hours and usually just one or two miners are affected.


Title: Re: Innosilicon A4+ setup tutorial
Post by: diaahussein on December 24, 2017, 07:37:42 PM
I have been thinking about cracking the password but my skills in that area are limited to bruteforcing. If there is someone clever enough to give me some pointers for more sophisticated methods, they would be most appreciated... I
 made a wordlist for 8 characters long password, all starting with the word "inno" and rest characters are all lower & uppercase alphabets and numbers.

I have got the passwd file and this is the root password hash

but we need someone to crack the hash

Quote
qHNyiD2GoZb.6

I guess it is DES encryption


Title: Re: Innosilicon A4+ setup tutorial
Post by: kb8679 on December 24, 2017, 08:38:25 PM
Wow awesome! I believe this was a huge help. And I'm asking for others much smarter than me to help. :)

I have been thinking about cracking the password but my skills in that area are limited to bruteforcing. If there is someone clever enough to give me some pointers for more sophisticated methods, they would be most appreciated... I
 made a wordlist for 8 characters long password, all starting with the word "inno" and rest characters are all lower & uppercase alphabets and numbers.

I have got the passwd file and this is the root password hash

but we need someone to crack the hash

Quote
qHNyiD2GoZb.6

I guess it is DES encryption

E: Yeah, most likely DES. And unfortunately the right pw wasn't found in the "inno" wordlist. Damn.
E2: I've submitted this to be cracked by crack.sh - let's see.


Title: Re: Innosilicon A4+ setup tutorial
Post by: diaahussein on December 24, 2017, 10:19:04 PM
Wow awesome! I believe this was a huge help. And I'm asking for others much smarter than me to help. :)

I have been thinking about cracking the password but my skills in that area are limited to bruteforcing. If there is someone clever enough to give me some pointers for more sophisticated methods, they would be most appreciated... I
 made a wordlist for 8 characters long password, all starting with the word "inno" and rest characters are all lower & uppercase alphabets and numbers.

I have got the passwd file and this is the root password hash

but we need someone to crack the hash

Quote
qHNyiD2GoZb.6

I guess it is DES encryption

E: Yeah, most likely DES. And unfortunately the right pw wasn't found in the "inno" wordlist. Damn.
E2: I've submitted this to be cracked by crack.sh - let's see.

good news

thanks to funbuxx https://bitcointalk.org/index.php?action=profile;u=1151278  (https://bitcointalk.org/index.php?action=profile;u=1151278) he manged to crack the new password

the new root password for 22nd Dec Firmware is : t1t2t3a5


Title: Re: Innosilicon A4+ setup tutorial
Post by: kb8679 on December 24, 2017, 10:40:41 PM
Wow awesome! I believe this was a huge help. And I'm asking for others much smarter than me to help. :)

I have been thinking about cracking the password but my skills in that area are limited to bruteforcing. If there is someone clever enough to give me some pointers for more sophisticated methods, they would be most appreciated... I
 made a wordlist for 8 characters long password, all starting with the word "inno" and rest characters are all lower & uppercase alphabets and numbers.

I have got the passwd file and this is the root password hash

but we need someone to crack the hash

Quote
qHNyiD2GoZb.6

I guess it is DES encryption

E: Yeah, most likely DES. And unfortunately the right pw wasn't found in the "inno" wordlist. Damn.
E2: I've submitted this to be cracked by crack.sh - let's see.

good news

thanks to funbuxx https://bitcointalk.org/index.php?action=profile;u=1151278  (https://bitcointalk.org/index.php?action=profile;u=1151278) he manged to crack the new password

the new root password for 22nd Dec Firmware is : t1t2t3a5

Holy SHIT! Thank you very much! It was pretty much wasted 100$ from me then - but really - doesn't matter. This is great news!


Title: Re: Innosilicon A4+ setup tutorial
Post by: zukolega on December 25, 2017, 03:43:49 PM
When i input " :wq " for save the file inno_config.py i get error "READ ONLY FILE" and i can't save the changes. Any solution?


Title: Re: Innosilicon A4+ setup tutorial
Post by: kb8679 on December 25, 2017, 04:15:23 PM
When i input " :wq " for save the file inno_config.py i get error "READ ONLY FILE" and i can't save the changes. Any solution?

Try ":wq!" with ! at the end.

Or you could just change the file to be writeable and use the plain ":wq". "chmod 777 inno_config.py" should do the trick nicely.


Sorry, forget about those. Wouldn't work as it turned out. :P


Title: Re: Innosilicon A4+ setup tutorial
Post by: jonbros on December 25, 2017, 04:27:03 PM
I have same issue... I cant chmod, copy or vi save the file... always same message :

root@miner/home/inno_py:
cp /home/inno_py/inno_config.py ./inno_config.py.bk
cp: can't create './inno_config.py.bk': Read-only file system

Is the only option is to unmount and mount back the file system as a RW?  I am no linux expert, not sure the consequences on the A4+


Title: Re: Innosilicon A4+ setup tutorial
Post by: zukolega on December 25, 2017, 04:42:49 PM
Doensn't work, i got the same response read-only file system using both commands. Alternatives? Thank's!


Title: Re: Innosilicon A4+ setup tutorial
Post by: kb8679 on December 25, 2017, 04:51:29 PM
Doensn't work, i got the same response read-only file system using both commands. Alternatives? Thank's!

I have same issue... I cant chmod, copy or vi save the file... always same message :

root@miner/home/inno_py:
cp /home/inno_py/inno_config.py ./inno_config.py.bk
cp: can't create './inno_config.py.bk': Read-only file system

Is the only option is to unmount and mount back the file system as a RW?  I am no linux expert, not sure the consequences on the A4+

I'd imagine that route will work. I can check out the correct "safe" procedures for the A4+ to make the switch once I get home today. Unless someone is faster to help. :)


Title: Re: Innosilicon A4+ setup tutorial
Post by: zukolega on December 25, 2017, 04:52:37 PM
Thank's @kb8679


Title: Re: Innosilicon A4+ setup tutorial
Post by: kb8679 on December 25, 2017, 05:11:14 PM
Doensn't work, i got the same response read-only file system using both commands. Alternatives? Thank's!

I have same issue... I cant chmod, copy or vi save the file... always same message :

root@miner/home/inno_py:
cp /home/inno_py/inno_config.py ./inno_config.py.bk
cp: can't create './inno_config.py.bk': Read-only file system

Is the only option is to unmount and mount back the file system as a RW?  I am no linux expert, not sure the consequences on the A4+

I'd imagine that route will work. I can check out the correct "safe" procedures for the A4+ to make the switch once I get home today. Unless someone is faster to help. :)
Thank's @kb8679

Ok, this works:

"mount -o remount,rw /dev/root /"

Once you're done, you can change it back to read only with:

"mount -o remount,ro /dev/root /"

I tested it by simply making a empty file to the same folder where the inno_config.py is located. Works just fine.



There are two partitions by default; one being the one pointed to / which is read-only. Other is for the configuration files which are rw by default.

Partition identifier: /dev/root
Mountpoint: /

Partition identifier: /dev/mtdblock5
Mountpoint: /innocfg




Title: Re: Innosilicon A4+ setup tutorial
Post by: diaahussein on December 25, 2017, 05:26:54 PM
to resolve the Read-only issue

Code:
mount / -o rw,remount

filesystem will return to read-only at reboot

to make the Filesystem read-write Permanently ( our friend kb8679 thinks that this might give a risk for files corruption, so do it at your own Risk )
 
Code:
vi /etc/init.d/rcS

look for the line
Code:
mount / -o ro,remount

change it to

Code:
mount / -o rw,remount

then save using  esc " :wq "

you have a read-write root


Title: Re: Innosilicon A4+ setup tutorial
Post by: kb8679 on December 25, 2017, 05:33:00 PM
Very true, but be aware; I've had this one nasty issue where some of the .pyc files got corrupted. While the file system is read-only, this could never happen (I believe the decision to make the FS to read-only was not just to bug the miners, but to eliminate some of the issues that could happen). It's not that big of a work to manually switch between rw&ro when needed and honestly believe that is the safer route.

to resolve the Read-only issue Permanently

Code:
mount / -o rw,remount

then
Code:
vi /etc/init.d/rcS

look for the line
Code:
mount / -o ro,remount

change it to

Code:
mount / -o rw,remount

then save using  " wq! "

you have a read-write root


Title: Re: Innosilicon A4+ setup tutorial
Post by: diaahussein on December 25, 2017, 05:37:34 PM
Very true, but be aware; I've had this one nasty issue where some of the .pyc files got corrupted. While the file system is read-only, this could never happen (I believe the decision to make the FS to read-only was not just to bug the miners, but to eliminate some of the issues that could happen). It's not that big of a work to manually switch between rw&ro when needed and honestly believe that is the safer route.

very good point, that might add to the stability


Title: Re: Innosilicon A4+ setup tutorial
Post by: zukolega on December 26, 2017, 01:17:34 PM
This works, I was able to edit the inno-config file but I still can not add it to the awesome miner program. "Failed to connect. Please ensure that the correct hostname has been entered.  https://ibb.co/mwvPH6

I've a Innosilicon A5, any ideas?

Thank's


Title: Re: Innosilicon A4+ setup tutorial
Post by: jonbros on December 26, 2017, 08:36:05 PM
same here,  I have been able to unmount and mount the file system back with read write,  edit the file to add the new arguments and reboot the A4+... but still I cant add it to awesome miner,  it cant connect to the miner.


Title: Re: Innosilicon A4+ setup tutorial
Post by: diaahussein on December 26, 2017, 09:52:40 PM
This works, I was able to edit the inno-config file but I still can not add it to the awesome miner program. "Failed to connect. Please ensure that the correct hostname has been entered.  https://ibb.co/mwvPH6

I've a Innosilicon A5, any ideas?

Thank's

for the A5 it is the dash Miner so it might be using another Miner app other than CGminer

anyway you can get the miner app

open the miner consol and type innominer_T3 --V or innominer_T3 --help

and let me know what you get ?


Title: Re: Innosilicon A4+ setup tutorial
Post by: zukolega on December 27, 2017, 09:13:20 AM
@diaahussein Attached screenshot of the help parameters https://ibb.co/kz65sG


Title: Re: Innosilicon A4+ setup tutorial
Post by: Gazdac2 on December 27, 2017, 12:03:44 PM
This works, I was able to edit the inno-config file but I still can not add it to the awesome miner program. "Failed to connect. Please ensure that the correct hostname has been entered.  https://ibb.co/mwvPH6

I've a Innosilicon A5, any ideas?

Thank's

I have to wait till the miner is fully booted and mining before it will show in awesome. Once the webUI shows up it will show in awesome as well.
Uhm... also. your screenshot doesn't show a closing quote (& ') on that line. Probably just cut off by the view. just double check that too?


Title: Re: Innosilicon A4+ setup tutorial
Post by: zukolega on December 27, 2017, 12:46:07 PM
This works, I was able to edit the inno-config file but I still can not add it to the awesome miner program. "Failed to connect. Please ensure that the correct hostname has been entered.  https://ibb.co/mwvPH6

I've a Innosilicon A5, any ideas?

Thank's

I have to wait till the miner is fully booted and mining before it will show in awesome. Once the webUI shows up it will show in awesome as well.
Uhm... also. your screenshot doesn't show a closing quote (& ') on that line. Probably just cut off by the view. just double check that too?


I've waiting and nothing, miner is fully booted and mining for two hours and doesn't appear, I've checked again. https://ibb.co/nicv9w


Title: Re: Innosilicon A4+ setup tutorial
Post by: Gazdac2 on December 27, 2017, 03:03:30 PM
This works, I was able to edit the inno-config file but I still can not add it to the awesome miner program. "Failed to connect. Please ensure that the correct hostname has been entered.  https://ibb.co/mwvPH6

I've a Innosilicon A5, any ideas?

Thank's

I have to wait till the miner is fully booted and mining before it will show in awesome. Once the webUI shows up it will show in awesome as well.
Uhm... also. your screenshot doesn't show a closing quote (& ') on that line. Probably just cut off by the view. just double check that too?


I've waiting and nothing, miner is fully booted and mining for two hours and doesn't appear, I've checked again. https://ibb.co/nicv9w

Uhh some thing to check is if it's actually running those settings.
ps| grep inno* > PS.txt and make sure it's got those flags ( I'm on phone so fix typos)
I think the actual file it runs is /tmp/run.ps so make sure of that too
I have a miner that just stops mining, so I jumpstart it with that run.ps without having to reboot. (Voltage adjust fixed that one)


Title: Re: Innosilicon A4+ setup tutorial
Post by: jotaperez on December 27, 2017, 05:38:53 PM
This works, I was able to edit the inno-config file but I still can not add it to the awesome miner program. "Failed to connect. Please ensure that the correct hostname has been entered.  https://ibb.co/mwvPH6

I've a Innosilicon A5, any ideas?

Thank's

I have to wait till the miner is fully booted and mining before it will show in awesome. Once the webUI shows up it will show in awesome as well.
Uhm... also. your screenshot doesn't show a closing quote (& ') on that line. Probably just cut off by the view. just double check that too?


I've waiting and nothing, miner is fully booted and mining for two hours and doesn't appear, I've checked again. https://ibb.co/nicv9w

Uhh some thing to check is if it's actually running those settings.
ps| grep inno* > PS.txt and make sure it's got those flags ( I'm on phone so fix typos)
I think the actual file it runs is /tmp/run.ps so make sure of that too
I have a miner that just stops mining, so I jumpstart it with that run.ps without having to reboot. (Voltage adjust fixed that one)


I don´t have "run.ps", in tmp folder there are run.sh*, is the same file?


Title: Re: Innosilicon A4+ setup tutorial
Post by: Gazdac2 on December 27, 2017, 07:04:47 PM
I don´t have "run.ps", in tmp folder there are run.sh*, is the same file?

Yeah, that's right .sh. Good morning :) 

If your processes (ps) has  the flags in it then there might be something else wrong (not your config files)

Code:
root@miner/:
ps|grep innominer

20685 root      73:25 innominer_T2 -o stratum+tcp://scrypt.mine.zpool.ca:3433 -u 1BPiRf942duu8AqFQGoRVwz4WGHn3APLm8 -p c=BTC --A1Pll1 1044 --A1Pll2 1044 --A1Pll3 1044 --A1Pll4 1044 --A1Pll5 1044 --A1Pll6 1044 --A1Pll7 1044 --A1Pll8 1044 --A1Vol1 23 --A1Vol2 23 --A1Vol3 23 --A1Vol4 23 --A1Vol5 23 --A1Vol6 23 --A1Vol7 23 --A1Vol8 23 --A1Fanmode 1 --A1Fanspd 3 --api-listen --api-network --api-allow W:0/0 --syslog
23359 root       0:00 grep innominer

https://i.imgur.com/yC9Qpxw.jpg
Shows the window in awesome when it works here. Manually typing address. Probably had to choose CgMiner from the drop-down the first time too.
Or you can try the network scan window thing, if you haven't.

What does worry a bit:
A) different miner, so who knows if any of this is helpful
B) if you have config *running* showing the --api-allow W:0/0 then there could be an entirely different set of problems like network connectivity issues. Firewalls. etc.


Title: Re: Innosilicon A4+ setup tutorial
Post by: zukolega on December 28, 2017, 12:13:25 AM
I don´t have "run.ps", in tmp folder there are run.sh*, is the same file?

Yeah, that's right .sh. Good morning :) 

If your processes (ps) has  the flags in it then there might be something else wrong (not your config files)

Code:
root@miner/:
ps|grep innominer

20685 root      73:25 innominer_T2 -o stratum+tcp://scrypt.mine.zpool.ca:3433 -u 1BPiRf942duu8AqFQGoRVwz4WGHn3APLm8 -p c=BTC --A1Pll1 1044 --A1Pll2 1044 --A1Pll3 1044 --A1Pll4 1044 --A1Pll5 1044 --A1Pll6 1044 --A1Pll7 1044 --A1Pll8 1044 --A1Vol1 23 --A1Vol2 23 --A1Vol3 23 --A1Vol4 23 --A1Vol5 23 --A1Vol6 23 --A1Vol7 23 --A1Vol8 23 --A1Fanmode 1 --A1Fanspd 3 --api-listen --api-network --api-allow W:0/0 --syslog
23359 root       0:00 grep innominer

https://i.imgur.com/yC9Qpxw.jpg
Shows the window in awesome when it works here. Manually typing address. Probably had to choose CgMiner from the drop-down the first time too.
Or you can try the network scan window thing, if you haven't.

What does worry a bit:
A) different miner, so who knows if any of this is helpful
B) if you have config *running* showing the --api-allow W:0/0 then there could be an entirely different set of problems like network connectivity issues. Firewalls. etc.


I don't see --api-allow https://ibb.co/fDB11b


Title: Re: Innosilicon A4+ setup tutorial
Post by: Gazdac2 on December 28, 2017, 01:47:11 AM


I don't see --api-allow https://ibb.co/fDB11b

Ok. Another idea.

After the  firmware update it may not update run.sh unless a config change happens. Go edit some setting like pool and resave. (via the webpage) Or just add it to run.sh yourself?
I think somewhere  you said you've tried rebooting. I sure hope so anyways. Reboot, at some point to see if the changes go through the whole system.

So that would be: to enable AwesomeMiner
0)mount RW
1) change /home/inno_py/inno_config.py
2) update something on the webUI to make inno change /tmp/run.sh
3)check if /tmp/run.sh has the correct settings (manually add them if it doesn't work?)
4)hard reboot to make sure it runs the new run.sh with all the fresh settings.


Title: Re: Innosilicon A4+ setup tutorial (or A5)
Post by: chadl2 on December 29, 2017, 02:54:09 AM
I also have some Innosilicon A5's I've been trying to get in Awesome Miner and was finally successful tonight. You need to edit three lines in the /home/inno_py/inno_config.py file. It looks like it generates a new run.sh file for each pool/pool change. I highlighted the lines and the adds below:

gInnoInitCmdStr = 'innominer_%s -o %s -u %s -p %s --A1Pll1 %s --A1Pll2 %s --A1Pll3 %s --A1Pll4 %s --A1Vol %s --api-listen --api-network --api-allow W:0/0 > /dev/null 2>&1'
gInnoBtcName    = 'T1'
gInnoBtcPool    = 'stratum+tcp://btc.s.innomining.com:1800'
gInnoBtcUser    = 'inno.btc'
gInnoBtcPwd     = 'x'
gInnoBtcFreq    = 1332
gInnoBtcVid     = 10
gInnoInitBtcCmd = gInnoInitCmdStr % (gInnoBtcName, gInnoBtcPool, gInnoBtcUser, gInnoBtcPwd, gInnoBtcFreq, gInnoBtcFreq, gInnoBtcFreq, gInnoBtcFreq, gInnoBtcVid)
gInnoLtcName    = 'T2'
gInnoLtcPool    = 'stratum+tcp://ltc.s.innomining.com:1900'
gInnoLtcUser    = 'inno.ltc'
gInnoLtcPwd     = 'x'
gInnoLtcFreq    = 1044
gInnoLtcVid     = 25
gInnoInitLtcCmd = gInnoInitCmdStr % (gInnoLtcName, gInnoLtcPool, gInnoLtcUser, gInnoLtcPwd, gInnoLtcFreq, gInnoLtcFreq, gInnoLtcFreq, gInnoLtcFreq, gInnoLtcVid)
gInnoDashName   = 'T3'
gInnoDashPool   = 'stratum+tcp://dash.s.innomining.com:2000'
gInnoDashUser   = 'inno.dash'
gInnoDashPwd    = 'x'
gInnoDashFreq   = 1100
gInnoDashVid    = 12
gInnoInitDashCmd= gInnoInitCmdStr % (gInnoDashName, gInnoDashPool, gInnoDashUser, gInnoDashPwd, gInnoDashFreq, gInnoDashFreq, gInnoDashFreq, gInnoDashFreq, gInnoDashVid)
gInnoXmrName    = 'T4'
gInnoXmrPool    = 'stratum+tcp://a8.s.innomining.com:19333'
gInnoXmrUser    = 'inno.001'
gInnoXmrPwd     = 'x'
gInnoXmrFreq    = 1000
gInnoXmrVid     = 175
gInnoInitXmrCmd = gInnoInitCmdStr % (gInnoXmrName, gInnoXmrPool, gInnoXmrUser, gInnoXmrPwd, gInnoXmrFreq, gInnoXmrFreq, gInnoXmrFreq, gInnoXmrFreq, gInnoXmrVid)
gInnoCmd1Pool   = gInnoInitCmdStr
gInnoCmd2Pool   = 'innominer_%s -o %s -u %s -p %s -o %s -u %s -p %s --A1Pll1 %s --A1Pll2 %s --A1Pll3 %s --A1Pll4 %s --A1Vol %s --api-listen --api-network --api-allow W:0/0 >/dev/null 2>&1'
gInnoCmd3Pool   = 'innominer_%s -o %s -u %s -p %s -o %s -u %s -p %s -o %s -u %s -p %s --A1Pll1 %s --A1Pll2 %s --A1Pll3 %s --A1Pll4 %s --A1Vol %s --api-listen --api-network --api-allow W:0/0 >/dev/null 2>&1'



Title: Re: Innosilicon A4+ setup tutorial (or A5)
Post by: zukolega on December 29, 2017, 03:29:08 PM
I also have some Innosilicon A5's I've been trying to get in Awesome Miner and was finally successful tonight. You need to edit three lines in the /home/inno_py/inno_config.py file. It looks like it generates a new run.sh file for each pool/pool change. I highlighted the lines and the adds below:

gInnoInitCmdStr = 'innominer_%s -o %s -u %s -p %s --A1Pll1 %s --A1Pll2 %s --A1Pll3 %s --A1Pll4 %s --A1Vol %s --api-listen --api-network --api-allow W:0/0 > /dev/null 2>&1'
gInnoBtcName    = 'T1'
gInnoBtcPool    = 'stratum+tcp://btc.s.innomining.com:1800'
gInnoBtcUser    = 'inno.btc'
gInnoBtcPwd     = 'x'
gInnoBtcFreq    = 1332
gInnoBtcVid     = 10
gInnoInitBtcCmd = gInnoInitCmdStr % (gInnoBtcName, gInnoBtcPool, gInnoBtcUser, gInnoBtcPwd, gInnoBtcFreq, gInnoBtcFreq, gInnoBtcFreq, gInnoBtcFreq, gInnoBtcVid)
gInnoLtcName    = 'T2'
gInnoLtcPool    = 'stratum+tcp://ltc.s.innomining.com:1900'
gInnoLtcUser    = 'inno.ltc'
gInnoLtcPwd     = 'x'
gInnoLtcFreq    = 1044
gInnoLtcVid     = 25
gInnoInitLtcCmd = gInnoInitCmdStr % (gInnoLtcName, gInnoLtcPool, gInnoLtcUser, gInnoLtcPwd, gInnoLtcFreq, gInnoLtcFreq, gInnoLtcFreq, gInnoLtcFreq, gInnoLtcVid)
gInnoDashName   = 'T3'
gInnoDashPool   = 'stratum+tcp://dash.s.innomining.com:2000'
gInnoDashUser   = 'inno.dash'
gInnoDashPwd    = 'x'
gInnoDashFreq   = 1100
gInnoDashVid    = 12
gInnoInitDashCmd= gInnoInitCmdStr % (gInnoDashName, gInnoDashPool, gInnoDashUser, gInnoDashPwd, gInnoDashFreq, gInnoDashFreq, gInnoDashFreq, gInnoDashFreq, gInnoDashVid)
gInnoXmrName    = 'T4'
gInnoXmrPool    = 'stratum+tcp://a8.s.innomining.com:19333'
gInnoXmrUser    = 'inno.001'
gInnoXmrPwd     = 'x'
gInnoXmrFreq    = 1000
gInnoXmrVid     = 175
gInnoInitXmrCmd = gInnoInitCmdStr % (gInnoXmrName, gInnoXmrPool, gInnoXmrUser, gInnoXmrPwd, gInnoXmrFreq, gInnoXmrFreq, gInnoXmrFreq, gInnoXmrFreq, gInnoXmrVid)
gInnoCmd1Pool   = gInnoInitCmdStr
gInnoCmd2Pool   = 'innominer_%s -o %s -u %s -p %s -o %s -u %s -p %s --A1Pll1 %s --A1Pll2 %s --A1Pll3 %s --A1Pll4 %s --A1Vol %s --api-listen --api-network --api-allow W:0/0 >/dev/null 2>&1'
gInnoCmd3Pool   = 'innominer_%s -o %s -u %s -p %s -o %s -u %s -p %s -o %s -u %s -p %s --A1Pll1 %s --A1Pll2 %s --A1Pll3 %s --A1Pll4 %s --A1Vol %s --api-listen --api-network --api-allow W:0/0 >/dev/null 2>&1'



Awesome!! Works works! Thank's @chadl2


Title: Re: Innosilicon A4+ setup tutorial (or A5)
Post by: Gazdac2 on December 29, 2017, 07:53:21 PM
I also have some Innosilicon A5's I've been trying to get in Awesome Miner and was finally successful tonight. You need to edit three lines in the /home/inno_py/inno_config.py file. It looks like it generates a new run.sh file for each pool/pool change. I highlighted the lines and the adds below:

gInnoInitCmdStr = 'innominer_%s -o %s -u %s -p %s --A1Pll1 %s --A1Pll2 %s --A1Pll3 %s --A1Pll4 %s --A1Vol %s --api-listen --api-network --api-allow W:0/0 > /dev/null 2>&1'
gInnoBtcName    = 'T1'
gInnoBtcPool    = 'stratum+tcp://btc.s.innomining.com:1800'
gInnoBtcUser    = 'inno.btc'
gInnoBtcPwd     = 'x'
gInnoBtcFreq    = 1332
gInnoBtcVid     = 10
gInnoInitBtcCmd = gInnoInitCmdStr % (gInnoBtcName, gInnoBtcPool, gInnoBtcUser, gInnoBtcPwd, gInnoBtcFreq, gInnoBtcFreq, gInnoBtcFreq, gInnoBtcFreq, gInnoBtcVid)
gInnoLtcName    = 'T2'
gInnoLtcPool    = 'stratum+tcp://ltc.s.innomining.com:1900'
gInnoLtcUser    = 'inno.ltc'
gInnoLtcPwd     = 'x'
gInnoLtcFreq    = 1044
gInnoLtcVid     = 25
gInnoInitLtcCmd = gInnoInitCmdStr % (gInnoLtcName, gInnoLtcPool, gInnoLtcUser, gInnoLtcPwd, gInnoLtcFreq, gInnoLtcFreq, gInnoLtcFreq, gInnoLtcFreq, gInnoLtcVid)
gInnoDashName   = 'T3'
gInnoDashPool   = 'stratum+tcp://dash.s.innomining.com:2000'
gInnoDashUser   = 'inno.dash'
gInnoDashPwd    = 'x'
gInnoDashFreq   = 1100
gInnoDashVid    = 12
gInnoInitDashCmd= gInnoInitCmdStr % (gInnoDashName, gInnoDashPool, gInnoDashUser, gInnoDashPwd, gInnoDashFreq, gInnoDashFreq, gInnoDashFreq, gInnoDashFreq, gInnoDashVid)
gInnoXmrName    = 'T4'
gInnoXmrPool    = 'stratum+tcp://a8.s.innomining.com:19333'
gInnoXmrUser    = 'inno.001'
gInnoXmrPwd     = 'x'
gInnoXmrFreq    = 1000
gInnoXmrVid     = 175
gInnoInitXmrCmd = gInnoInitCmdStr % (gInnoXmrName, gInnoXmrPool, gInnoXmrUser, gInnoXmrPwd, gInnoXmrFreq, gInnoXmrFreq, gInnoXmrFreq, gInnoXmrFreq, gInnoXmrVid)
gInnoCmd1Pool   = gInnoInitCmdStr
gInnoCmd2Pool   = 'innominer_%s -o %s -u %s -p %s -o %s -u %s -p %s --A1Pll1 %s --A1Pll2 %s --A1Pll3 %s --A1Pll4 %s --A1Vol %s --api-listen --api-network --api-allow W:0/0 >/dev/null 2>&1'
gInnoCmd3Pool   = 'innominer_%s -o %s -u %s -p %s -o %s -u %s -p %s -o %s -u %s -p %s --A1Pll1 %s --A1Pll2 %s --A1Pll3 %s --A1Pll4 %s --A1Vol %s --api-listen --api-network --api-allow W:0/0 >/dev/null 2>&1'



Awesome!! Works works! Thank's @chadl2

this would probably work too : edit the first one then

gInnoCmd1Pool     = gInnoInitCmdStr
gInnoCmd2Pool     = gInnoInitCmdStr
gInnoCmd3Pool     = gInnoInitCmdStr

and #comment out the other gInnoCmd#Pool lines
*edit
--if you are only using one pool



Title: Re: Innosilicon A4+ setup tutorial
Post by: ukjack on January 03, 2018, 01:52:20 AM
thanks guys, your methods for getting the a4+ into awesome miner worked.

anyone managed to get temps to display?


Title: Re: Innosilicon A4+ setup tutorial
Post by: chadl2 on January 03, 2018, 02:14:43 AM
I haven't been able to, but would be great to know if anyone does.


Title: Re: Innosilicon A4+ setup tutorial
Post by: Gazdac2 on January 03, 2018, 04:09:43 AM
So here's a fun one. One of my fans stopped working, and inno said go F#*% yourself and find a fan yourself. Great warranty.

Anyways while I wait for new ones to arrive from china (you CAN get them for "$5 each", but only if you buy like 10-20 at a time and pay +$60 in shipping.)

Anyways. I took the fan apart to diagnose and well... half rusted. perfect straight line across the middle. Rusted as in it sat in a pool of saltwater, one side shiny new, one side dead. I have one more fan that is loud, so I'll take it apart once the new fans arrive. but WTF Inno.

Anyways... if one fan is louder than the others better order replacements early.




Title: Re: Innosilicon A4+ setup tutorial
Post by: Boneyg001 on January 03, 2018, 05:51:46 AM
So here's a fun one. One of my fans stopped working, and inno said go F#*% yourself and find a fan yourself. Great warranty.

Anyways while I wait for new ones to arrive from china (you CAN get them for "$5 each", but only if you buy like 10-20 at a time and pay +$60 in shipping.)

Anyways. I took the fan apart to diagnose and well... half rusted. perfect straight line across the middle. Rusted as in it sat in a pool of saltwater, one side shiny new, one side dead. I have one more fan that is loud, so I'll take it apart once the new fans arrive. but WTF Inno.

Anyways... if one fan is louder than the others better order replacements early.




Wow! That really sucks... It's what happens when these miners are poorly made and tbh they don't really care about the customer.


Title: Re: Innosilicon A4+ setup tutorial
Post by: ukjack on January 03, 2018, 03:11:56 PM
I've got 3 miners that never start mining. I've tried reflashing the firmware and restoring defaults

The logs show it appearing to just loop round

Code:
Jan  3 15:08:29 (none) local0.warn innominer_T2: Started cgminer 4.10.0
Jan  3 15:08:29 (none) local0.info innominer_T2: hardware version is G19
Jan  3 15:08:29 (none) local0.info innominer_T2: miner type is T2
Jan  3 15:08:29 (none) local0.notice innominer_T2: A1 = 1044,92, Clock = 1044MHz
Jan  3 15:08:29 (none) local0.notice innominer_T2: A1 = 1044,92, Clock = 1044MHz
Jan  3 15:08:29 (none) local0.notice innominer_T2: A1 = 1044,92, Clock = 1044MHz
Jan  3 15:08:29 (none) local0.notice innominer_T2: A1 = 1044,92, Clock = 1044MHz
Jan  3 15:08:29 (none) local0.notice innominer_T2: A1 = 1044,92, Clock = 1044MHz
Jan  3 15:08:29 (none) local0.notice innominer_T2: A1 = 1044,92, Clock = 1044MHz
Jan  3 15:08:29 (none) local0.notice innominer_T2: A1 = 1044,92, Clock = 1044MHz
Jan  3 15:08:29 (none) local0.notice innominer_T2: A1 = 1044,92, Clock = 1044MHz
Jan  3 15:08:29 (none) local0.warn innominer_T2: A1: checking A1 chain
Jan  3 15:08:29 (none) local0.warn innominer_T2: SPI '/dev/spidev0.0': mode=1, bits=8, speed=1500000
Jan  3 15:08:31 (none) local0.warn innominer_T2: SPI '/dev/spidev1.0': mode=1, bits=8, speed=1500000
Jan  3 15:08:33 (none) local0.warn innominer_T2: SPI '/dev/spidev2.0': mode=1, bits=8, speed=1500000
Jan  3 15:08:35 (none) local0.warn innominer_T2: SPI '/dev/spidev3.0': mode=1, bits=8, speed=1500000
Jan  3 15:08:37 (none) local0.warn innominer_T2: SPI '/dev/spidev4.0': mode=1, bits=8, speed=1500000
Jan  3 15:08:39 (none) local0.warn innominer_T2: SPI '/dev/spidev5.0': mode=1, bits=8, speed=1500000
Jan  3 15:08:41 (none) local0.warn innominer_T2: SPI '/dev/spidev6.0': mode=1, bits=8, speed=1500000
Jan  3 15:08:43 (none) local0.warn innominer_T2: SPI '/dev/spidev7.0': mode=1, bits=8, speed=1500000
Jan  3 15:08:56 (none) local0.err innominer_T2: Plug Status[0] = 0
Jan  3 15:09:02 (none) local0.err innominer_T2: Plug Status[1] = 0
Jan  3 15:09:08 (none) local0.err innominer_T2: Plug Status[2] = 0
Jan  3 15:09:14 (none) local0.err innominer_T2: Plug Status[3] = 0
Jan  3 15:09:20 (none) local0.err innominer_T2: Plug Status[4] = 1
Jan  3 15:09:20 (none) local0.err innominer_T2: chain:4 the plat is not inserted
Jan  3 15:09:26 (none) local0.err innominer_T2: Plug Status[5] = 1
Jan  3 15:09:26 (none) local0.err innominer_T2: chain:5 the plat is not inserted
Jan  3 15:09:32 (none) local0.err innominer_T2: Plug Status[6] = 1
Jan  3 15:09:32 (none) local0.err innominer_T2: chain:6 the plat is not inserted
Jan  3 15:09:38 (none) local0.err innominer_T2: Plug Status[7] = 1
Jan  3 15:09:38 (none) local0.err innominer_T2: chain:7 the plat is not inserted
Jan  3 15:09:38 (none) local0.info innominer_T2: pre 0: A1 init chain
Jan  3 15:09:39 (none) local0.warn innominer_T2: 0: detected 72 chips
Jan  3 15:09:39 (none) local0.warn innominer_T2: collect core success
Jan  3 15:09:39 (none) local0.warn innominer_T2: 0: no A1 chip-chain detected
Jan  3 15:09:39 (none) local0.warn innominer_T2: spidev0.0: 0: Found 72 A1 chips
Jan  3 15:09:39 (none) local0.warn innominer_T2: Detected the 0 A1 chain with 72 chips
Jan  3 15:09:39 (none) local0.info innominer_T2: pre 1: A1 init chain
Jan  3 15:09:39 (none) local0.warn innominer_T2: cmd reset: poll fail !
Jan  3 15:09:40 (none) local0.warn innominer_T2: cmd bist start: poll fail !
Jan  3 15:09:40 (none) local0.warn innominer_T2: bist start fail
Jan  3 15:09:40 (none) local0.err innominer_T2: init 1 A1 chain fail
Jan  3 15:09:40 (none) local0.info innominer_T2: pre 2: A1 init chain
Jan  3 15:09:41 (none) local0.warn innominer_T2: 2: detected 72 chips
Jan  3 15:09:41 (none) local0.warn innominer_T2: collect core success
Jan  3 15:09:41 (none) local0.warn innominer_T2: 2: no A1 chip-chain detected
Jan  3 15:09:41 (none) local0.warn innominer_T2: spidev2.0: 2: Found 72 A1 chips
Jan  3 15:09:41 (none) local0.warn innominer_T2: Detected the 2 A1 chain with 72 chips
Jan  3 15:09:41 (none) local0.info innominer_T2: pre 3: A1 init chain
Jan  3 15:09:42 (none) local0.warn innominer_T2: 3: detected 72 chips
Jan  3 15:09:42 (none) local0.warn innominer_T2: collect core success
Jan  3 15:09:42 (none) local0.warn innominer_T2: 3: no A1 chip-chain detected
Jan  3 15:09:42 (none) local0.warn innominer_T2: spidev3.0: 3: Found 72 A1 chips
Jan  3 15:09:42 (none) local0.warn innominer_T2: Detected the 3 A1 chain with 72 chips
Jan  3 15:09:42 (none) local0.info innominer_T2: start to configure all chain from 0 to 120
Jan  3 15:09:42 (none) local0.err innominer_T2: start to read temp
Jan  3 15:09:42 (none) local0.info innominer_T2: start to configure chain 0
Jan  3 15:09:42 (none) local0.notice innominer_T2: A1 = 120,0, Clock = 120MHz
Jan  3 15:09:42 (none) local0.err innominer_T2: start to read temp
Jan  3 15:10:46 (none) local0.warn innominer_T2: Started cgminer 4.10.0
Jan  3 15:10:46 (none) local0.info innominer_T2: hardware version is G19
Jan  3 15:10:46 (none) local0.info innominer_T2: miner type is T2
Jan  3 15:10:46 (none) local0.notice innominer_T2: A1 = 1044,92, Clock = 1044MHz
Jan  3 15:10:46 (none) local0.notice innominer_T2: A1 = 1044,92, Clock = 1044MHz
Jan  3 15:10:46 (none) local0.notice innominer_T2: A1 = 1044,92, Clock = 1044MHz
Jan  3 15:10:46 (none) local0.notice innominer_T2: A1 = 1044,92, Clock = 1044MHz
Jan  3 15:10:46 (none) local0.notice innominer_T2: A1 = 1044,92, Clock = 1044MHz
Jan  3 15:10:46 (none) local0.notice innominer_T2: A1 = 1044,92, Clock = 1044MHz
Jan  3 15:10:46 (none) local0.notice innominer_T2: A1 = 1044,92, Clock = 1044MHz
Jan  3 15:10:46 (none) local0.notice innominer_T2: A1 = 1044,92, Clock = 1044MHz
Jan  3 15:10:46 (none) local0.warn innominer_T2: A1: checking A1 chain
Jan  3 15:10:46 (none) local0.warn innominer_T2: SPI '/dev/spidev0.0': mode=1, bits=8, speed=1500000
Jan  3 15:10:48 (none) local0.warn innominer_T2: SPI '/dev/spidev1.0': mode=1, bits=8, speed=1500000
Jan  3 15:10:50 (none) local0.warn innominer_T2: SPI '/dev/spidev2.0': mode=1, bits=8, speed=1500000
Jan  3 15:10:52 (none) local0.warn innominer_T2: SPI '/dev/spidev3.0': mode=1, bits=8, speed=1500000
Jan  3 15:10:54 (none) local0.warn innominer_T2: SPI '/dev/spidev4.0': mode=1, bits=8, speed=1500000
Jan  3 15:10:56 (none) local0.warn innominer_T2: SPI '/dev/spidev5.0': mode=1, bits=8, speed=1500000
Jan  3 15:10:58 (none) local0.warn innominer_T2: SPI '/dev/spidev6.0': mode=1, bits=8, speed=1500000
Jan  3 15:11:00 (none) local0.warn innominer_T2: SPI '/dev/spidev7.0': mode=1, bits=8, speed=1500000


Title: Re: Innosilicon A4+ setup tutorial
Post by: Gazdac2 on January 03, 2018, 06:55:45 PM
I've got 3 miners that never start mining. I've tried reflashing the firmware and restoring defaults

The logs show it appearing to just loop round

Code:
...
Jan  3 15:09:26 (none) local0.err innominer_T2: chain:5 the plat is not inserted
Jan  3 15:09:32 (none) local0.err innominer_T2: Plug Status[6] = 1
Jan  3 15:09:32 (none) local0.err innominer_T2: chain:6 the plat is not inserted
Jan  3 15:09:38 (none) local0.err innominer_T2: Plug Status[7] = 1
Jan  3 15:09:38 (none) local0.err innominer_T2: chain:7 the plat is not inserted
Jan  3 15:09:38 (none) local0.info innominer_T2: pre 0: A1 init chain
Jan  3 15:09:39 (none) local0.warn innominer_T2: 0: detected 72 chips
Jan  3 15:09:39 (none) local0.warn innominer_T2: collect core success
Jan  3 15:09:39 (none) local0.warn innominer_T2: 0: no A1 chip-chain detected
Jan  3 15:09:39 (none) local0.warn innominer_T2: spidev0.0: 0: Found 72 A1 chips
Jan  3 15:09:39 (none) local0.warn innominer_T2: Detected the 0 A1 chain with 72 chips
Jan  3 15:09:39 (none) local0.info innominer_T2: pre 1: A1 init chain
Jan  3 15:09:39 (none) local0.warn innominer_T2: cmd reset: poll fail !
Jan  3 15:09:40 (none) local0.warn innominer_T2: cmd bist start: poll fail !
Jan  3 15:09:40 (none) local0.warn innominer_T2: bist start fail
Jan  3 15:09:40 (none) local0.err innominer_T2: init 1 A1 chain fail
Jan  3 15:09:40 (none) local0.info innominer_T2: pre 2: A1 init chain
Jan  3 15:09:41 (none) local0.warn innominer_T2: 2: detected 72 chips
Jan  3 15:09:41 (none) local0.warn innominer_T2: collect core success
Jan  3 15:09:41 (none) local0.warn innominer_T2: 2: no A1 chip-chain detected
Jan  3 15:09:41 (none) local0.warn innominer_T2: spidev2.0: 2: Found 72 A1 chips
Jan  3 15:09:41 (none) local0.warn innominer_T2: Detected the 2 A1 chain with 72 chips
Jan  3 15:09:41 (none) local0.info innominer_T2: pre 3: A1 init chain
Jan  3 15:09:42 (none) local0.warn innominer_T2: 3: detected 72 chips
Jan  3 15:09:42 (none) local0.warn innominer_T2: collect core success
Jan  3 15:09:42 (none) local0.warn innominer_T2: 3: no A1 chip-chain detected
Jan  3 15:09:42 (none) local0.warn innominer_T2: spidev3.0: 3: Found 72 A1 chips
Jan  3 15:09:42 (none) local0.warn innominer_T2: Detected the 3 A1 chain with 72 chips
Jan  3 15:09:42 (none) local0.info innominer_T2: start to configure all chain from 0 to 120
Jan  3 15:09:42 (none) local0.err innominer_T2: start to read temp
Jan  3 15:09:42 (none) local0.info innominer_T2: start to configure chain 0
Jan  3 15:09:42 (none) local0.notice innominer_T2: A1 = 120,0, Clock = 120MHz
Jan  3 15:09:42 (none) local0.err innominer_T2: start to read temp

Here is where our logs kinda start to differ.
Sure sounds like it can see the chains are plugged in, but they don't reply to commands.
Green lights on all 4 chains?
they getting power? CLEAN power? Need higher (lower #) voltage? I'm using my own power supplies and I think some are as high as Power Level 22.

You have a G19? so you CAN'T flash it right? only use the "upgrade" file or did some actually come with a TF port?

Code:
Jan  3 18:35:54 (none) local0.err innominer_T2: Plug Status[5] = 1
Jan  3 18:35:54 (none) local0.err innominer_T2: chain:5 the plat is not inserted
Jan  3 18:36:00 (none) local0.err innominer_T2: Plug Status[6] = 1
Jan  3 18:36:00 (none) local0.err innominer_T2: chain:6 the plat is not inserted
Jan  3 18:36:06 (none) local0.err innominer_T2: Plug Status[7] = 1
Jan  3 18:36:06 (none) local0.err innominer_T2: chain:7 the plat is not inserted
Jan  3 18:36:06 (none) local0.info innominer_T2: chain_id:0
Jan  3 18:36:18 (none) local0.info innominer_T2: send command [write_reg]
Jan  3 18:36:18 (none) local0.warn innominer_T2: #####Write t/v sensor Value Success!
Jan  3 18:36:18 (none) local0.info innominer_T2: chain_id:1
Jan  3 18:36:30 (none) local0.info innominer_T2: send command [write_reg]
Jan  3 18:36:30 (none) local0.warn innominer_T2: #####Write t/v sensor Value Success!
Jan  3 18:36:30 (none) local0.info innominer_T2: chain_id:2
Jan  3 18:36:41 (none) local0.info innominer_T2: send command [write_reg]
Jan  3 18:36:41 (none) local0.warn innominer_T2: #####Write t/v sensor Value Success!
Jan  3 18:36:41 (none) local0.info innominer_T2: chain_id:3
Jan  3 18:36:53 (none) local0.info innominer_T2: send command [write_reg]
Jan  3 18:36:53 (none) local0.warn innominer_T2: #####Write t/v sensor Value Success!
Jan  3 18:36:53 (none) local0.info innominer_T2: chain_id:4
Jan  3 18:36:53 (none) local0.warn innominer_T2: cmd reset: poll fail !
Jan  3 18:36:53 (none) local0.warn innominer_T2: cmd write reg: poll fail !
Jan  3 18:36:53 (none) local0.warn innominer_T2: set default PLL fail
Jan  3 18:36:53 (none) local0.info innominer_T2: send command [write_reg]
Jan  3 18:36:53 (none) local0.warn innominer_T2: cmd write reg: poll fail !
Jan  3 18:36:53 (none) local0.warn innominer_T2: #####Write t/v sensor Value Failed!
Jan  3 18:36:53 (none) local0.warn innominer_T2: #####Write t/v sensor Value Success!
Jan  3 18:36:53 (none) local0.info innominer_T2: chain_id:5
Jan  3 18:36:53 (none) local0.warn innominer_T2: cmd reset: poll fail !
Jan  3 18:36:53 (none) local0.warn innominer_T2: cmd write reg: poll fail !
Jan  3 18:36:53 (none) local0.warn innominer_T2: set default PLL fail
Jan  3 18:36:53 (none) local0.info innominer_T2: send command [write_reg]
Jan  3 18:36:53 (none) local0.warn innominer_T2: cmd write reg: poll fail !
Jan  3 18:36:53 (none) local0.warn innominer_T2: #####Write t/v sensor Value Failed!
Jan  3 18:36:53 (none) local0.warn innominer_T2: #####Write t/v sensor Value Success!
Jan  3 18:36:53 (none) local0.info innominer_T2: chain_id:6
Jan  3 18:36:53 (none) local0.warn innominer_T2: cmd reset: poll fail !
Jan  3 18:36:53 (none) local0.warn innominer_T2: cmd write reg: poll fail !
Jan  3 18:36:53 (none) local0.warn innominer_T2: set default PLL fail
Jan  3 18:36:53 (none) local0.info innominer_T2: send command [write_reg]
Jan  3 18:36:53 (none) local0.warn innominer_T2: cmd write reg: poll fail !
Jan  3 18:36:53 (none) local0.warn innominer_T2: #####Write t/v sensor Value Failed!
Jan  3 18:36:53 (none) local0.warn innominer_T2: #####Write t/v sensor Value Success!
Jan  3 18:36:53 (none) local0.info innominer_T2: chain_id:7
Jan  3 18:36:53 (none) local0.warn innominer_T2: cmd reset: poll fail !
Jan  3 18:36:53 (none) local0.warn innominer_T2: cmd write reg: poll fail !
Jan  3 18:36:53 (none) local0.warn innominer_T2: set default PLL fail
Jan  3 18:36:53 (none) local0.info innominer_T2: send command [write_reg]
Jan  3 18:36:53 (none) local0.warn innominer_T2: cmd write reg: poll fail !
Jan  3 18:36:53 (none) local0.warn innominer_T2: #####Write t/v sensor Value Failed!
Jan  3 18:36:53 (none) local0.warn innominer_T2: #####Write t/v sensor Value Success!
Jan  3 18:36:55 (none) local0.warn innominer_T2: 0: detected 72 chips
Jan  3 18:36:55 (none) local0.warn innominer_T2: collect core success
Jan  3 18:36:55 (none) local0.warn innominer_T2: 0: no A1 chip-chain detected
Jan  3 18:36:55 (none) local0.warn innominer_T2: spidev0.0: 0: Found 72 A1 chips
Jan  3 18:36:56 (none) local0.warn innominer_T2: 0: Found chip 1 with 9 active cores
Jan  3 18:36:56 (none) local0.warn innominer_T2: 0: Found chip 2 with 9 active cores
Jan  3 18:36:56 (none) local0.warn innominer_T2: 0: Found chip 3 with 9 active cores
Jan  3 18:36:56 (none) local0.warn innominer_T2: 0: Found chip 4 with 9 active cores
Jan  3 18:36:56 (none) local0.warn innominer_T2: 0: Found chip 5 with 9 active cores
Jan  3 18:36:56 (none) local0.warn innominer_T2: 0: Found chip 6 with 9 active cores
Jan  3 18:36:56 (none) local0.warn innominer_T2: 0: Found chip 7 with 9 active cores
Jan  3 18:36:56 (none) local0.warn innominer_T2: 0: Found chip 8 with 9 active cores
Jan  3 18:36:56 (none) local0.warn innominer_T2: 0: Found chip 9 with 9 active cores
Jan  3 18:36:56 (none) local0.warn innominer_T2: 0: Found chip 10 with 9 active cores
Jan  3 18:36:56 (none) local0.warn innominer_T2: 0: Found chip 11 with 9 active cores
...


Title: Re: Innosilicon A4+ setup tutorial
Post by: ukjack on January 03, 2018, 07:04:14 PM
I *think* they had a TF port, I'm not physically near the machines so can't double check.

Power is good - they're hosted in a data center using Innosilicon PSU

I've submitted a ticket to Innosilicon - see what they say.


Title: Re: Innosilicon A4+ setup tutorial
Post by: Pujols89 on January 03, 2018, 07:09:14 PM
I had to chase them for the confirmation it took about 10 days
open the case on their website
and send Emails to
luojm@innosilicon.com.cn,
zhangq@innosilicon.com.cn,
miner_sales@innosilicon.com.cn,
shupp@innosilicon.com.cn
with your order number

I've emailed all of those emails multiple times and still nothing. I wired the rest of my money over a month ago and haven't heard diddly. Anyone have a better way of getting a hold of these people?!


Title: Re: Innosilicon A4+ setup tutorial
Post by: Gazdac2 on January 03, 2018, 07:19:06 PM
I *think* they had a TF port, I'm not physically near the machines so can't double check.

Power is good - they're hosted in a data center using Innosilicon PSU

I've submitted a ticket to Innosilicon - see what they say.
Heh, yeah TF port.

When I first got mine I took my shiny new SD card with the new firmware( Just like the instructions say on the website)  on it and put in the slot and. *plunk*, it just fell in the hole. No actual port, just a hole.

GL, majorly suspicious if you ended up with 3 failures, with a total of 12 cards broken.

Then again parts of mine look like they were physically dunked in water before sending to me.

I had to chase them for the confirmation it took about 10 days
open the case on their website
and send Emails to
luojm@innosilicon.com.cn,
zhangq@innosilicon.com.cn,
miner_sales@innosilicon.com.cn,
shupp@innosilicon.com.cn
with your order number

I've emailed all of those emails multiple times and still nothing. I wired the rest of my money over a month ago and haven't heard diddly. Anyone have a better way of getting a hold of these people?!

That's how my entire ordering process went. My email to tell them that the just lost my future business was replied with "here is tracking number xxxxx"

Funny how they could ship "immediately" if you ordered on Christmas, so I am guessing you are just forgotten.   I think the replies came after sending to miner_sales and shupp. Did they even confirm your payment, and request your mailing address? Guess you can always email miner support and say "my miners are not working, since they are not physically present. Please send replacements."


Title: Re: Innosilicon A4+ setup tutorial
Post by: needed357 on January 03, 2018, 07:41:05 PM
some overclock this miner?

and what is the normal/best temperature for the miner?


Title: Re: Innosilicon A4+ setup tutorial
Post by: BWYeung on January 03, 2018, 11:06:55 PM
New Miner - just got the Innosilicon A4+ LTC Master hooked up to a Bitmain APW3++ (110) and plugged directly into my AT&T Uverse Modem/Router. I've followed the direction from the OP, (upgraded firmware, enter my pool info - Litecoinpool) I have not gone into the Advance Config and change the inno_config.py file. I've also enabled pass through the AT&T modem/router for litecoinpool's ports-TCP 3333 & 8080), been running for over 2 hours. I did have to change the A4+'s IP as it was the same as the modem/router.

Question: How do I know if I'm connected and mining in the pool? Issues, Miner Status Overview does not show me anything, I get the spinning flower fore Summery, InnoMiner, and Pools. Also, my litecoinpool accounts page shows all zeros, if connect, when should you start seeing data?

TIA.

EDIT: Using latest firmware as it works with the Dec 22 Password.


Title: Re: Innosilicon A4+ setup tutorial
Post by: Giantppl on January 03, 2018, 11:51:33 PM
Same here miner status is constantly loading.. no hash rate showed at the pool. Tried to upgrade the software but it stops at 10% and when u refresh the page its gone.
Any idea how to flash it? I have another A4+ working well. Any advice greatly appreciated..


Title: Re: Innosilicon A4+ setup tutorial
Post by: BWYeung on January 04, 2018, 12:15:23 AM
Same here miner status is constantly loading.. no hash rate showed at the pool. Tried to upgrade the software but it stops at 10% and when u refresh the page its gone.
Any idea how to flash it? I have another A4+ working well. Any advice greatly appreciated..

What's your System Version info, mine are:
Miner Type: 17
Hw Version: G19
Build Date: Thur Dec 21 17:56:17 CST 2017
Platform Version: 810e0c2934044ec019b1d929d3de1f3c899b6410
Rootfs Version: 4973e48bd7ab0bb58688ce4845bd7b2b532429f7


Title: Re: Innosilicon A4+ setup tutorial
Post by: Giantppl on January 04, 2018, 12:21:07 AM
Same here miner status is constantly loading.. no hash rate showed at the pool. Tried to upgrade the software but it stops at 10% and when u refresh the page its gone.
Any idea how to flash it? I have another A4+ working well. Any advice greatly appreciated..

What's your System Version info, mine are:
Miner Type: 17
Hw Version: G19
Build Date: Thur Dec 21 17:56:17 CST 2017
Platform Version: 810e0c2934044ec019b1d929d3de1f3c899b6410
Rootfs Version: 4973e48bd7ab0bb58688ce4845bd7b2b532429f7

Mine is the same 17 and G19 just the date is 29 dec instead


Title: Re: Innosilicon A4+ setup tutorial
Post by: BWYeung on January 04, 2018, 02:02:57 AM
Same here miner status is constantly loading.. no hash rate showed at the pool. Tried to upgrade the software but it stops at 10% and when u refresh the page its gone.
Any idea how to flash it? I have another A4+ working well. Any advice greatly appreciated..

What's your System Version info, mine are:
Miner Type: 17
Hw Version: G19
Build Date: Thur Dec 21 17:56:17 CST 2017
Platform Version: 810e0c2934044ec019b1d929d3de1f3c899b6410
Rootfs Version: 4973e48bd7ab0bb58688ce4845bd7b2b532429f7

Mine is the same 17 and G19 just the date is 29 dec instead

I'm on the same Build Date as you, found the 17-12-29 build off the support site. The good thing now, it doesn't sound like a drone trying to take off. :) Weird thing, on their support site, their screenshots shows "Cgminer Version" "Sgminer Version" mine does not, does yours?


Title: Re: Innosilicon A4+ setup tutorial
Post by: BWYeung on January 04, 2018, 04:23:32 AM
Below is the debug log, I'm assuming this is not good.

For Newbies: I telnet in, and use the 1st and 3rd line to run the debug.

Code:
cd /bin
root@miner/bin:
./innominer_T3 --debug
 [1970-01-01 00:09:08] Started sgminer 4.4.2
 [1970-01-01 00:09:08] A1 detect
 [1970-01-01 00:09:08] hardware version is G19
 [1970-01-01 00:09:08] miner type is T2
[ERRO:1970-01-01 00:09:08.331] set fan speed 80
[DEBG:1970-01-01 00:09:08.331] pwm  name:/dev/pwmgen0.0.
[DEBG:1970-01-01 00:09:08.331] pwm  step:5.
[DEBG:1970-01-01 00:09:08.331] duty max: 100.
[DEBG:1970-01-01 00:09:08.332] targ freq:20000.
[DEBG:1970-01-01 00:09:08.332] freq rate:20000.
[DEBG:1970-01-01 00:09:08.332] fan speed thrd:100.
[DEBG:1970-01-01 00:09:08.332] fan up thrd:55.
[DEBG:1970-01-01 00:09:08.332] fan down thrd:35.
[DEBG:1970-01-01 00:09:08.332] auto_fan true, fan_speed 1
 [1970-01-01 00:09:58] A1: checking A1 chain 8,8,8,8,8,8,8,8
 [1970-01-01 00:09:58] SPI '/dev/spidev0.0': mode=1, bits=8, speed=1500000

 [1970-01-01 00:09:59] SPI '/dev/spidev1.0': mode=1, bits=8, speed=1500000

 [1970-01-01 00:10:00] SPI '/dev/spidev2.0': mode=1, bits=8, speed=1500000

 [1970-01-01 00:10:01] SPI '/dev/spidev3.0': mode=1, bits=8, speed=1500000

 [1970-01-01 00:10:02] SPI '/dev/spidev4.0': mode=1, bits=8, speed=1500000

 [1970-01-01 00:10:03] SPI '/dev/spidev5.0': mode=1, bits=8, speed=1500000

 [1970-01-01 00:10:09] spi init
 [1970-01-01 00:10:15] Plug Status[0] = 0
 [1970-01-01 00:10:21] Plug Status[1] = 0
 [1970-01-01 00:10:27] Plug Status[2] = 0
 [1970-01-01 00:10:33] Plug Status[3] = 0
 [1970-01-01 00:10:39] Plug Status[4] = 1
 [1970-01-01 00:10:45] Plug Status[5] = 1
set_vid_value_G19:8.
set_vid_value_G19:8.
set_vid_value_G19:8.
set_vid_value_G19:8.
set_vid_value_G19:8.
set_vid_value_G19:8.
 [1970-01-01 00:10:45] 0: A1 init chain
 [1970-01-01 00:10:45] cmd bist start: poll fail !
 [1970-01-01 00:10:45] bist start fail
 [1970-01-01 00:10:45] init a1 chain fail
 [1970-01-01 00:10:45] 1: A1 init chain
 [1970-01-01 00:10:45] cmd bist start: poll fail !
 [1970-01-01 00:10:45] bist start fail
 [1970-01-01 00:10:45] init a1 chain fail
 [1970-01-01 00:10:45] 2: A1 init chain
 [1970-01-01 00:10:45] cmd bist start: poll fail !
 [1970-01-01 00:10:45] bist start fail
 [1970-01-01 00:10:45] init a1 chain fail
 [1970-01-01 00:10:45] 3: A1 init chain
 [1970-01-01 00:10:46] cmd bist start: poll fail !
 [1970-01-01 00:10:46] bist start fail
 [1970-01-01 00:10:46] init a1 chain fail
 [1970-01-01 00:10:46] 4: A1 init chain
 [1970-01-01 00:10:46] cmd bist start: poll fail !
 [1970-01-01 00:10:46] bist start fail
 [1970-01-01 00:10:46] init a1 chain fail
 [1970-01-01 00:10:46] 5: A1 init chain
 [1970-01-01 00:10:46] cmd bist start: poll fail !
 [1970-01-01 00:10:46] bist start fail
 [1970-01-01 00:10:46] init a1 chain fail
 [1970-01-01 00:10:46] pre init_pll...
[ERRO:1970-01-01 00:10:46.789] set fan speed 30
 [1970-01-01 00:10:46] pll 120 finished

 [1970-01-01 00:10:46] pll 120 finished

 [1970-01-01 00:10:46] pll 120 finished

 [1970-01-01 00:10:46] pll 120 finished

 [1970-01-01 00:10:46] pll 120 finished

 [1970-01-01 00:10:46] pll 120 finished

 [1970-01-01 00:10:46] pll 320 finished

 [1970-01-01 00:10:46] pll 320 finished

 [1970-01-01 00:10:46] pll 320 finished

 [1970-01-01 00:10:46] pll 320 finished

 [1970-01-01 00:10:46] pll 320 finished

 [1970-01-01 00:10:46] pll 320 finished

 [1970-01-01 00:10:46] pll 520 finished

 [1970-01-01 00:10:46] pll 520 finished

 [1970-01-01 00:10:46] pll 520 finished

 [1970-01-01 00:10:46] pll 520 finished

 [1970-01-01 00:10:46] pll 520 finished

 [1970-01-01 00:10:46] pll 520 finished

 [1970-01-01 00:10:46] pll 720 finished

 [1970-01-01 00:10:46] pll 720 finished

 [1970-01-01 00:10:46] pll 720 finished

 [1970-01-01 00:10:46] pll 720 finished

 [1970-01-01 00:10:46] pll 720 finished

 [1970-01-01 00:10:46] pll 720 finished

 [1970-01-01 00:10:46] pll 920 finished

 [1970-01-01 00:10:46] pll 920 finished

 [1970-01-01 00:10:46] pll 920 finished

 [1970-01-01 00:10:46] pll 920 finished

 [1970-01-01 00:10:46] pll 920 finished

 [1970-01-01 00:10:46] pll 920 finished

 [1970-01-01 00:10:46] pll 1120 finished

 [1970-01-01 00:10:46] pll 1120 finished

 [1970-01-01 00:10:46] pll 1120 finished

 [1970-01-01 00:10:46] pll 1120 finished

 [1970-01-01 00:10:46] pll 1120 finished

 [1970-01-01 00:10:46] pll 1120 finished

 [1970-01-01 00:10:46] reload init a1 chain0 fail
 [1970-01-01 00:10:46] reload init a1 chain1 fail
 [1970-01-01 00:10:46] reload init a1 chain2 fail
 [1970-01-01 00:10:46] reload init a1 chain3 fail
 [1970-01-01 00:10:46] reload init a1 chain4 fail
 [1970-01-01 00:10:46] reload init a1 chain5 fail
 [1970-01-01 00:10:46] A1 dectect finish
 [1970-01-01 00:10:46] All devices disabled, cannot mine!
root@miner/bin:


Title: Re: Innosilicon A4+ setup tutorial
Post by: Giantppl on January 04, 2018, 04:27:00 AM
I'm really an illiterate when it comes to tech. the miner status just keeps spinning and not even loading anything..
is there a way where I can copy the files from the working A4+ to the not working one? I do suspect its the software issue.

Same here miner status is constantly loading.. no hash rate showed at the pool. Tried to upgrade the software but it stops at 10% and when u refresh the page its gone.
Any idea how to flash it? I have another A4+ working well. Any advice greatly appreciated..

What's your System Version info, mine are:
Miner Type: 17
Hw Version: G19
Build Date: Thur Dec 21 17:56:17 CST 2017
Platform Version: 810e0c2934044ec019b1d929d3de1f3c899b6410
Rootfs Version: 4973e48bd7ab0bb58688ce4845bd7b2b532429f7

Mine is the same 17 and G19 just the date is 29 dec instead

I'm on the same Build Date as you, found the 17-12-29 build off the support site. The good thing now, it doesn't sound like a drone trying to take off. :) Weird thing, on their support site, their screenshots shows "Cgminer Version" "Sgminer Version" mine does not, does yours?


Title: Re: Innosilicon A4+ setup tutorial
Post by: Gazdac2 on January 04, 2018, 06:00:35 AM
Below is the debug log, I'm assuming this is not good.

For Newbies: I telnet in, and use the 1st and 3rd line to run the debug.

Code:
cd /bin
root@miner/bin:
./innominer_T3 --debug
 :)

I think T3 is for the A5 miner, so here is stuff that works for my A4+

When you first telnet to the miner (192.168.1.xxx:8100) and login (root:t1t2t3a5)
Check if it is even trying to mine (ps|grep innominer)

it should look the same as a properly configured launch string i.e.  (minus the bit on the end):

innominer_T2 -o stratum+tcp://scrypt.mine.zpool.ca:3433 -u 1BPiRf942duu8AqFQGoRVwz4WGHn3APLm8 -p "c=BTC" -o stratum+tcp://hub.miningpoolhub.com:12001 -u gazdac.201 -p "x" --A1Pll1 1100 --A1Pll2 1100 --A1Pll3 1100 --A1Pll4 1100 --A1Pll5 1100 --A1Pll6 1100 --A1Pll7 1100 --A1Pll8 1100 --A1Vol1 18 --A1Vol2 18 --A1Vol3 18 --A1Vol4 18 --A1Vol5 18 --A1Vol6 18 --A1Vol7 18 --A1Vol8 18 --A1Fanmode 1 --A1Fanspd 3  --api-listen --syslog >/dev/null 2>&1

note this  launch string resides in: /tmp/run.sh  whenever you want to restart the miner just type (/tmp/run.sh) and it will restart the process (5 minute start up time)

If it isn't running and/or your launch string is not correct you have to fix the python config files (see 2)

(1)If it is running you can watch the logs real time (tail -50 /tmp/log/innominer.log -f) (remember to ctrl+c to stop watching) you won't see it in the webui unless you get all the way to starting mining (5+ minutes)
I have no idea what to do if it is running and configured properly, other than up the voltages (lower number)

(2)so if you run /tmp/run.sh is wrong or it isn't in ps at all. then config is screwed up.
For those that might have the same problem. Looks like my a4+ corrupted files during  a reboot  then stopped working.
/home/inno_tools/start_miner.py

The damn thing deleted a couple characters and killed itself.
Here's what the file looked like

vi /lib/python3.4/_sysconfigdata.py...

 'HAVE_GETLOGIN': 1,
 'HAVE_GETNAMEINFO': 1,
 'HAVE_GETPAGESIZE': 1,
E_GETPEERNAME': 1,
 'HAVE_GETPGID': 1,
 'HAVE_GETPGRP': 1,
...

There might have been more errors, i dunno. I coped the file from another miner and now it works.
Symptoms were the HTTP control page loading, but not showing any data e.g. not showing me  "miner type" under system.
I found the file by manually running each of the commands in /etc/init.d/rcS

Good luck to the rest of you.


To transfer files I just copied and pasted the broken parts.
Looks like it has ftp available as well.
https://busybox.net/downloads/BusyBox.html (https://busybox.net/downloads/BusyBox.html)
look for ftpd or ftpget/ftpput

remember you have to  mount / -o rw,remount to edit files


uhh this was TMI for everyone probably. just confusing you all more.



Title: Re: Innosilicon A4+ setup tutorial
Post by: BWYeung on January 04, 2018, 06:35:40 AM
Thx Gazdac2

I rebooted and waited 5 min, then I telneted in ran the command, this is what I get.

Code:
(none) login: root
Password:
root@miner~:
ps|grep innominer
  844 root       0:00 syslogd -f /etc/syslog.conf -O /tmp/log/innominer.log -s 1
024 -b 5
 1181 root       0:00 grep innominer
root@miner~:

I also did a test, ran the same command after another reboot (thx for the command) at about 30 sec after the start, when the fan speed reduced (just under 3min), and at 5 min. Prior to 5 min, I got the string of codes like yours with the pool information, but after 5 min, I get the same code as above.


Title: Re: Innosilicon A4+ setup tutorial
Post by: yummyyummy on January 04, 2018, 06:37:07 AM
sorry for disturbing, I've just got my a4+ today, I've checked in the overview, I see it's as below:

A4+
Hw Version    G19
DNA    0x1488076484c2c1
MAC Addr    50:6c:be:08:76:9f
Build Date    Wed Nov 22 09:30:31 CST 2017

May I know which firmware is the most stable one? or if there is any other newer and stable firmware available please? should I upgrade it?. Thanks.


Title: Re: Innosilicon A4+ setup tutorial
Post by: Giantppl on January 04, 2018, 06:38:37 AM
Im lost once I got to the third paragraph... will see if innosilicon gets back to me..

Below is the debug log, I'm assuming this is not good.

For Newbies: I telnet in, and use the 1st and 3rd line to run the debug.

Code:
cd /bin
root@miner/bin:
./innominer_T3 --debug
 :)

I think T3 is for the A5 miner, so here is stuff that works for my A4+

When you first telnet to the miner (192.168.1.xxx:8100) and login (root:t1t2t3a5)
Check if it is even trying to mine (ps|grep innominer)

it should look the same as a properly configured launch string i.e.  (minus the bit on the end):

innominer_T2 -o stratum+tcp://scrypt.mine.zpool.ca:3433 -u 1BPiRf942duu8AqFQGoRVwz4WGHn3APLm8 -p "c=BTC" -o stratum+tcp://hub.miningpoolhub.com:12001 -u gazdac.201 -p "x" --A1Pll1 1100 --A1Pll2 1100 --A1Pll3 1100 --A1Pll4 1100 --A1Pll5 1100 --A1Pll6 1100 --A1Pll7 1100 --A1Pll8 1100 --A1Vol1 18 --A1Vol2 18 --A1Vol3 18 --A1Vol4 18 --A1Vol5 18 --A1Vol6 18 --A1Vol7 18 --A1Vol8 18 --A1Fanmode 1 --A1Fanspd 3  --api-listen --syslog >/dev/null 2>&1

note this  launch string resides in: /tmp/run.sh  whenever you want to restart the miner just type (/tmp/run.sh) and it will restart the process (5 minute start up time)

If it isn't running and/or your launch string is not correct you have to fix the python config files (see 2)

(1)If it is running you can watch the logs real time (tail -50 /tmp/log/innominer.log -f) (remember to ctrl+c to stop watching) you won't see it in the webui unless you get all the way to starting mining (5+ minutes)
I have no idea what to do if it is running and configured properly, other than up the voltages (lower number)

(2)so if you run /tmp/run.sh is wrong or it isn't in ps at all. then config is screwed up.
For those that might have the same problem. Looks like my a4+ corrupted files during  a reboot  then stopped working.
/home/inno_tools/start_miner.py

The damn thing deleted a couple characters and killed itself.
Here's what the file looked like

vi /lib/python3.4/_sysconfigdata.py...

 'HAVE_GETLOGIN': 1,
 'HAVE_GETNAMEINFO': 1,
 'HAVE_GETPAGESIZE': 1,
E_GETPEERNAME': 1,
 'HAVE_GETPGID': 1,
 'HAVE_GETPGRP': 1,
...

There might have been more errors, i dunno. I coped the file from another miner and now it works.
Symptoms were the HTTP control page loading, but not showing any data e.g. not showing me  "miner type" under system.
I found the file by manually running each of the commands in /etc/init.d/rcS

Good luck to the rest of you.


To transfer files I just copied and pasted the broken parts.
Looks like it has ftp available as well.
https://busybox.net/downloads/BusyBox.html (https://busybox.net/downloads/BusyBox.html)
look for ftpd or ftpget/ftpput

remember you have to  mount / -o rw,remount to edit files


uhh this was TMI for everyone probably. just confusing you all more.




Title: Re: Innosilicon A4+ setup tutorial
Post by: Gazdac2 on January 04, 2018, 06:48:21 AM
sorry for disturbing, I've just got my a4+ today, I've checked in the overview, I see it's as below:

A4+
Hw Version    G19
DNA    0x1488076484c2c1
MAC Addr    50:6c:be:08:76:9f
Build Date    Wed Nov 22 09:30:31 CST 2017

May I know which firmware is the most stable one? or if there is any other newer and stable firmware available please? should I upgrade it?. Thanks.

According to inno they keep screwing up the firmware and it burns out the thing, so at least Dec 20th firmware.
just remember the root password changed to t1t2t3a5 with the Dec 20th firmware.

I have some running Dec20th and Dec29th. both seem similarly okay.
Thx Gazdac2

I rebooted and waited 5 min, then I telneted in ran the command, this is what I get.

Code:
(none) login: root
Password:
root@miner~:
ps|grep innominer
  844 root       0:00 syslogd -f /etc/syslog.conf -O /tmp/log/innominer.log -s 1
024 -b 5
 1181 root       0:00 grep innominer
root@miner~:

I also did a test, ran the same command after another reboot (thx for the command) at about 30 sec after the start, when the fan speed reduced (just under 3min), and at 5 min. Prior to 5 min, I got the string of codes like yours with the pool information, but after 5 min, I get the same code as above.

Yep, that's bad. Mine never actually exits, it just loops around if it fails. Sometimes forever... but never actually closes.
you can watch the logs with tail, or go further back in the log with -500 or -10000 or whatever to see when it stopped.
whenever you "save" the pools on the webui I believe it rebuilds the run.sh  you could try that. I think it also runs a different string if you have 2  pools instead of one.  save one pool and try, save 2 pools ( even if the same) and try.  and if not... then digging through those config files and python files.


Title: Re: Innosilicon A4+ setup tutorial
Post by: Gazdac2 on January 04, 2018, 06:55:08 AM
Im lost once I got to the third paragraph... will see if innosilicon gets back to me..
I'm addicted  to these things, so I've been having fun editing things in them. Not surprised that others don't do the same.

Inno might help, I guess... No one's ever reported back saying "inno fixed it yay"

Try resaving your pools and bumping up or putting on auto the voltages again. Maybe it will fix a broken config file.


Title: Re: Innosilicon A4+ setup tutorial
Post by: ukjack on January 04, 2018, 09:07:24 AM
Hi Gazdac2
Wondering if you can help

I have 3 miners that never start mining. System > Overview shows information OK however Miner status just spins forever.

ps|grep inno shows the ./innominer process running

Code:
innominer_T2 -o stratum+tcp://s1.theblocksfactory.com:9004 -u x -p x -o stratum+tcp://scrypt.eu.nicehash.com:3333#xnsub -u x -p x -o stratum+tcp://scrypt.usa.nicehash.com:3333#xnsub -u x -p x --A1Pll1 1044 --A1Pll2 1044 --A1Pll3 1044 --A1Pll4 1044 --A1Pll5 1044 --A1Pll6 1044 --A1Pll7 1044 --A1Pll8 1044 --A1Vol1 25 --A1Vol2 25 --A1Vol3 25 --A1Vol4 25 --A1Vol5 25 --A1Vol6 25 --A1Vol7 25 --A1Vol8 25 --A1Fanmode 1 --A1Fanspd 1 --api-listen --syslog

however a few minutes later...

Code:
ps|grep inno
  839 root       5:44 python3.4 /home/inno_daemon/MServer.py
  844 root       0:00 syslogd -f /etc/syslog.conf -O /tmp/log/innominer.log -s 1024 -b 5

logs show it just seems to loop forever

Code:
tail -n 500 /tmp/log/innominer.log
Jan  1 00:00:14 (none) syslog.info syslogd started: BusyBox v1.27.1
Jan  1 00:00:14 (none) daemon.info : starting pid 845, tty '': '-/bin/sh'
Jan  4 08:57:38 (none) local0.warn innominer_T2: Started cgminer 4.10.0
Jan  4 08:57:38 (none) local0.info innominer_T2: hardware version is G19
Jan  4 08:57:38 (none) local0.info innominer_T2: miner type is T2
Jan  4 08:57:38 (none) local0.notice innominer_T2: A1 = 1044,92, Clock = 1044MHz
Jan  4 08:57:38 (none) local0.notice innominer_T2: A1 = 1044,92, Clock = 1044MHz
Jan  4 08:57:38 (none) local0.notice innominer_T2: A1 = 1044,92, Clock = 1044MHz
Jan  4 08:57:38 (none) local0.notice innominer_T2: A1 = 1044,92, Clock = 1044MHz
Jan  4 08:57:38 (none) local0.notice innominer_T2: A1 = 1044,92, Clock = 1044MHz
Jan  4 08:57:38 (none) local0.notice innominer_T2: A1 = 1044,92, Clock = 1044MHz
Jan  4 08:57:38 (none) local0.notice innominer_T2: A1 = 1044,92, Clock = 1044MHz
Jan  4 08:57:38 (none) local0.notice innominer_T2: A1 = 1044,92, Clock = 1044MHz
Jan  4 08:57:38 (none) local0.warn innominer_T2: A1: checking A1 chain
Jan  4 08:57:38 (none) local0.warn innominer_T2: SPI '/dev/spidev0.0': mode=1, bits=8, speed=1500000
Jan  4 08:57:40 (none) local0.warn innominer_T2: SPI '/dev/spidev1.0': mode=1, bits=8, speed=1500000
Jan  4 08:57:42 (none) local0.warn innominer_T2: SPI '/dev/spidev2.0': mode=1, bits=8, speed=1500000
Jan  4 08:57:44 (none) local0.warn innominer_T2: SPI '/dev/spidev3.0': mode=1, bits=8, speed=1500000
Jan  4 08:57:46 (none) local0.warn innominer_T2: SPI '/dev/spidev4.0': mode=1, bits=8, speed=1500000
Jan  4 08:57:48 (none) local0.warn innominer_T2: SPI '/dev/spidev5.0': mode=1, bits=8, speed=1500000
Jan  4 08:57:50 (none) local0.warn innominer_T2: SPI '/dev/spidev6.0': mode=1, bits=8, speed=1500000
Jan  4 08:57:52 (none) local0.warn innominer_T2: SPI '/dev/spidev7.0': mode=1, bits=8, speed=1500000
Jan  4 08:58:05 (none) local0.err innominer_T2: Plug Status[0] = 0
Jan  4 08:58:11 (none) local0.err innominer_T2: Plug Status[1] = 0
Jan  4 08:58:17 (none) local0.err innominer_T2: Plug Status[2] = 0
Jan  4 08:58:23 (none) local0.err innominer_T2: Plug Status[3] = 0
Jan  4 08:58:29 (none) local0.err innominer_T2: Plug Status[4] = 1
Jan  4 08:58:29 (none) local0.err innominer_T2: chain:4 the plat is not inserted
Jan  4 08:58:35 (none) local0.err innominer_T2: Plug Status[5] = 1
Jan  4 08:58:35 (none) local0.err innominer_T2: chain:5 the plat is not inserted
Jan  4 08:58:41 (none) local0.err innominer_T2: Plug Status[6] = 1
Jan  4 08:58:41 (none) local0.err innominer_T2: chain:6 the plat is not inserted
Jan  4 08:58:47 (none) local0.err innominer_T2: Plug Status[7] = 1
Jan  4 08:58:47 (none) local0.err innominer_T2: chain:7 the plat is not inserted
Jan  4 08:58:47 (none) local0.info innominer_T2: pre 0: A1 init chain
Jan  4 08:58:48 (none) local0.warn innominer_T2: 0: detected 72 chips
Jan  4 08:58:48 (none) local0.warn innominer_T2: collect core success
Jan  4 08:58:48 (none) local0.warn innominer_T2: 0: no A1 chip-chain detected
Jan  4 08:58:48 (none) local0.warn innominer_T2: spidev0.0: 0: Found 72 A1 chips
Jan  4 08:58:48 (none) local0.warn innominer_T2: Detected the 0 A1 chain with 72 chips
Jan  4 08:58:48 (none) local0.info innominer_T2: pre 1: A1 init chain
Jan  4 08:58:48 (none) local0.warn innominer_T2: cmd reset: poll fail !
Jan  4 08:58:49 (none) local0.warn innominer_T2: cmd bist start: poll fail !
Jan  4 08:58:49 (none) local0.warn innominer_T2: bist start fail
Jan  4 08:58:49 (none) local0.err innominer_T2: init 1 A1 chain fail
Jan  4 08:58:49 (none) local0.info innominer_T2: pre 2: A1 init chain
Jan  4 08:58:50 (none) local0.warn innominer_T2: 2: detected 72 chips
Jan  4 08:58:50 (none) local0.warn innominer_T2: collect core success
Jan  4 08:58:50 (none) local0.warn innominer_T2: 2: no A1 chip-chain detected
Jan  4 08:58:50 (none) local0.warn innominer_T2: spidev2.0: 2: Found 72 A1 chips
Jan  4 08:58:50 (none) local0.warn innominer_T2: Detected the 2 A1 chain with 72 chips
Jan  4 08:58:50 (none) local0.info innominer_T2: pre 3: A1 init chain
Jan  4 08:58:51 (none) local0.warn innominer_T2: 3: detected 72 chips
Jan  4 08:58:51 (none) local0.warn innominer_T2: collect core success
Jan  4 08:58:51 (none) local0.warn innominer_T2: 3: no A1 chip-chain detected
Jan  4 08:58:51 (none) local0.warn innominer_T2: spidev3.0: 3: Found 72 A1 chips
Jan  4 08:58:51 (none) local0.warn innominer_T2: Detected the 3 A1 chain with 72 chips
Jan  4 08:58:51 (none) local0.info innominer_T2: start to configure all chain from 0 to 120
Jan  4 08:58:51 (none) local0.err innominer_T2: start to read temp
Jan  4 08:58:52 (none) local0.info innominer_T2: start to configure chain 0
Jan  4 08:58:52 (none) local0.notice innominer_T2: A1 = 120,0, Clock = 120MHz
Jan  4 08:58:52 (none) local0.err innominer_T2: start to read temp
Jan  4 08:59:52 (none) local0.warn innominer_T2: Started cgminer 4.10.0
Jan  4 08:59:52 (none) local0.info innominer_T2: hardware version is G19
Jan  4 08:59:52 (none) local0.info innominer_T2: miner type is T2
Jan  4 08:59:52 (none) local0.notice innominer_T2: A1 = 1044,92, Clock = 1044MHz
Jan  4 08:59:52 (none) local0.notice innominer_T2: A1 = 1044,92, Clock = 1044MHz
Jan  4 08:59:52 (none) local0.notice innominer_T2: A1 = 1044,92, Clock = 1044MHz
Jan  4 08:59:52 (none) local0.notice innominer_T2: A1 = 1044,92, Clock = 1044MHz
Jan  4 08:59:52 (none) local0.notice innominer_T2: A1 = 1044,92, Clock = 1044MHz
Jan  4 08:59:52 (none) local0.notice innominer_T2: A1 = 1044,92, Clock = 1044MHz
Jan  4 08:59:52 (none) local0.notice innominer_T2: A1 = 1044,92, Clock = 1044MHz
Jan  4 08:59:52 (none) local0.notice innominer_T2: A1 = 1044,92, Clock = 1044MHz
Jan  4 08:59:52 (none) local0.warn innominer_T2: A1: checking A1 chain
Jan  4 08:59:52 (none) local0.warn innominer_T2: SPI '/dev/spidev0.0': mode=1, bits=8, speed=1500000
Jan  4 08:59:54 (none) local0.warn innominer_T2: SPI '/dev/spidev1.0': mode=1, bits=8, speed=1500000
Jan  4 08:59:56 (none) local0.warn innominer_T2: SPI '/dev/spidev2.0': mode=1, bits=8, speed=1500000
Jan  4 08:59:58 (none) local0.warn innominer_T2: SPI '/dev/spidev3.0': mode=1, bits=8, speed=1500000
Jan  4 09:00:00 (none) local0.warn innominer_T2: SPI '/dev/spidev4.0': mode=1, bits=8, speed=1500000
Jan  4 09:00:02 (none) local0.warn innominer_T2: SPI '/dev/spidev5.0': mode=1, bits=8, speed=1500000
Jan  4 09:00:04 (none) local0.warn innominer_T2: SPI '/dev/spidev6.0': mode=1, bits=8, speed=1500000
Jan  4 09:00:06 (none) local0.warn innominer_T2: SPI '/dev/spidev7.0': mode=1, bits=8, speed=1500000
Jan  4 09:00:19 (none) local0.err innominer_T2: Plug Status[0] = 0
Jan  4 09:00:25 (none) local0.err innominer_T2: Plug Status[1] = 0
Jan  4 09:00:31 (none) local0.err innominer_T2: Plug Status[2] = 0
Jan  4 09:00:37 (none) local0.err innominer_T2: Plug Status[3] = 0
Jan  4 09:00:43 (none) local0.err innominer_T2: Plug Status[4] = 1
Jan  4 09:00:43 (none) local0.err innominer_T2: chain:4 the plat is not inserted
Jan  4 09:00:49 (none) local0.err innominer_T2: Plug Status[5] = 1
Jan  4 09:00:49 (none) local0.err innominer_T2: chain:5 the plat is not inserted
Jan  4 09:00:55 (none) local0.err innominer_T2: Plug Status[6] = 1
Jan  4 09:00:55 (none) local0.err innominer_T2: chain:6 the plat is not inserted
Jan  4 09:01:01 (none) local0.err innominer_T2: Plug Status[7] = 1
Jan  4 09:01:01 (none) local0.err innominer_T2: chain:7 the plat is not inserted
Jan  4 09:01:01 (none) local0.info innominer_T2: pre 0: A1 init chain
Jan  4 09:01:02 (none) local0.warn innominer_T2: 0: detected 72 chips
Jan  4 09:01:02 (none) local0.warn innominer_T2: collect core success
Jan  4 09:01:02 (none) local0.warn innominer_T2: 0: no A1 chip-chain detected
Jan  4 09:01:02 (none) local0.warn innominer_T2: spidev0.0: 0: Found 72 A1 chips
Jan  4 09:01:02 (none) local0.warn innominer_T2: Detected the 0 A1 chain with 72 chips
Jan  4 09:01:02 (none) local0.info innominer_T2: pre 1: A1 init chain
Jan  4 09:01:02 (none) local0.warn innominer_T2: cmd reset: poll fail !
Jan  4 09:01:03 (none) local0.warn innominer_T2: cmd bist start: poll fail !
Jan  4 09:01:03 (none) local0.warn innominer_T2: bist start fail
Jan  4 09:01:03 (none) local0.err innominer_T2: init 1 A1 chain fail
Jan  4 09:01:03 (none) local0.info innominer_T2: pre 2: A1 init chain
Jan  4 09:01:04 (none) local0.warn innominer_T2: 2: detected 72 chips
Jan  4 09:01:04 (none) local0.warn innominer_T2: collect core success
Jan  4 09:01:04 (none) local0.warn innominer_T2: 2: no A1 chip-chain detected
Jan  4 09:01:04 (none) local0.warn innominer_T2: spidev2.0: 2: Found 72 A1 chips
Jan  4 09:01:04 (none) local0.warn innominer_T2: Detected the 2 A1 chain with 72 chips
Jan  4 09:01:04 (none) local0.info innominer_T2: pre 3: A1 init chain
Jan  4 09:01:05 (none) local0.warn innominer_T2: 3: detected 72 chips
Jan  4 09:01:05 (none) local0.warn innominer_T2: collect core success
Jan  4 09:01:05 (none) local0.warn innominer_T2: 3: no A1 chip-chain detected
Jan  4 09:01:05 (none) local0.warn innominer_T2: spidev3.0: 3: Found 72 A1 chips
Jan  4 09:01:05 (none) local0.warn innominer_T2: Detected the 3 A1 chain with 72 chips
Jan  4 09:01:05 (none) local0.info innominer_T2: start to configure all chain from 0 to 120
Jan  4 09:01:05 (none) local0.err innominer_T2: start to read temp
Jan  4 09:01:06 (none) local0.info innominer_T2: start to configure chain 0
Jan  4 09:01:06 (none) local0.notice innominer_T2: A1 = 120,0, Clock = 120MHz
Jan  4 09:01:06 (none) local0.err innominer_T2: start to read temp
Jan  4 09:02:09 (none) local0.warn innominer_T2: Started cgminer 4.10.0
Jan  4 09:02:09 (none) local0.info innominer_T2: hardware version is G19
Jan  4 09:02:09 (none) local0.info innominer_T2: miner type is T2
Jan  4 09:02:09 (none) local0.notice innominer_T2: A1 = 1044,92, Clock = 1044MHz
Jan  4 09:02:09 (none) local0.notice innominer_T2: A1 = 1044,92, Clock = 1044MHz
Jan  4 09:02:09 (none) local0.notice innominer_T2: A1 = 1044,92, Clock = 1044MHz
Jan  4 09:02:09 (none) local0.notice innominer_T2: A1 = 1044,92, Clock = 1044MHz
Jan  4 09:02:09 (none) local0.notice innominer_T2: A1 = 1044,92, Clock = 1044MHz
Jan  4 09:02:09 (none) local0.notice innominer_T2: A1 = 1044,92, Clock = 1044MHz
Jan  4 09:02:09 (none) local0.notice innominer_T2: A1 = 1044,92, Clock = 1044MHz
Jan  4 09:02:09 (none) local0.notice innominer_T2: A1 = 1044,92, Clock = 1044MHz
Jan  4 09:02:09 (none) local0.warn innominer_T2: A1: checking A1 chain
Jan  4 09:02:09 (none) local0.warn innominer_T2: SPI '/dev/spidev0.0': mode=1, bits=8, speed=1500000
Jan  4 09:02:11 (none) local0.warn innominer_T2: SPI '/dev/spidev1.0': mode=1, bits=8, speed=1500000
Jan  4 09:02:13 (none) local0.warn innominer_T2: SPI '/dev/spidev2.0': mode=1, bits=8, speed=1500000
Jan  4 09:02:15 (none) local0.warn innominer_T2: SPI '/dev/spidev3.0': mode=1, bits=8, speed=1500000
Jan  4 09:02:17 (none) local0.warn innominer_T2: SPI '/dev/spidev4.0': mode=1, bits=8, speed=1500000
Jan  4 09:02:19 (none) local0.warn innominer_T2: SPI '/dev/spidev5.0': mode=1, bits=8, speed=1500000
Jan  4 09:02:21 (none) local0.warn innominer_T2: SPI '/dev/spidev6.0': mode=1, bits=8, speed=1500000
Jan  4 09:02:23 (none) local0.warn innominer_T2: SPI '/dev/spidev7.0': mode=1, bits=8, speed=1500000
Jan  4 09:02:36 (none) local0.err innominer_T2: Plug Status[0] = 0
Jan  4 09:02:42 (none) local0.err innominer_T2: Plug Status[1] = 0
Jan  4 09:02:48 (none) local0.err innominer_T2: Plug Status[2] = 0
Jan  4 09:02:54 (none) local0.err innominer_T2: Plug Status[3] = 0
Jan  4 09:03:00 (none) local0.err innominer_T2: Plug Status[4] = 1
Jan  4 09:03:00 (none) local0.err innominer_T2: chain:4 the plat is not inserted
Jan  4 09:03:06 (none) local0.err innominer_T2: Plug Status[5] = 1
Jan  4 09:03:06 (none) local0.err innominer_T2: chain:5 the plat is not inserted
Jan  4 09:03:12 (none) local0.err innominer_T2: Plug Status[6] = 1
Jan  4 09:03:12 (none) local0.err innominer_T2: chain:6 the plat is not inserted
Jan  4 09:03:18 (none) local0.err innominer_T2: Plug Status[7] = 1
Jan  4 09:03:18 (none) local0.err innominer_T2: chain:7 the plat is not inserted
Jan  4 09:03:18 (none) local0.info innominer_T2: pre 0: A1 init chain
Jan  4 09:03:19 (none) local0.warn innominer_T2: 0: detected 72 chips
Jan  4 09:03:19 (none) local0.warn innominer_T2: collect core success
Jan  4 09:03:19 (none) local0.warn innominer_T2: 0: no A1 chip-chain detected
Jan  4 09:03:19 (none) local0.warn innominer_T2: spidev0.0: 0: Found 72 A1 chips
Jan  4 09:03:19 (none) local0.warn innominer_T2: Detected the 0 A1 chain with 72 chips
Jan  4 09:03:19 (none) local0.info innominer_T2: pre 1: A1 init chain
Jan  4 09:03:19 (none) local0.warn innominer_T2: cmd reset: poll fail !
Jan  4 09:03:20 (none) local0.warn innominer_T2: cmd bist start: poll fail !
Jan  4 09:03:20 (none) local0.warn innominer_T2: bist start fail
Jan  4 09:03:20 (none) local0.err innominer_T2: init 1 A1 chain fail
Jan  4 09:03:20 (none) local0.info innominer_T2: pre 2: A1 init chain
Jan  4 09:03:21 (none) local0.warn innominer_T2: 2: detected 72 chips
Jan  4 09:03:21 (none) local0.warn innominer_T2: collect core success
Jan  4 09:03:21 (none) local0.warn innominer_T2: 2: no A1 chip-chain detected
Jan  4 09:03:21 (none) local0.warn innominer_T2: spidev2.0: 2: Found 72 A1 chips
Jan  4 09:03:21 (none) local0.warn innominer_T2: Detected the 2 A1 chain with 72 chips
Jan  4 09:03:21 (none) local0.info innominer_T2: pre 3: A1 init chain
Jan  4 09:03:22 (none) local0.warn innominer_T2: 3: detected 72 chips
Jan  4 09:03:22 (none) local0.warn innominer_T2: collect core success
Jan  4 09:03:22 (none) local0.warn innominer_T2: 3: no A1 chip-chain detected
Jan  4 09:03:22 (none) local0.warn innominer_T2: spidev3.0: 3: Found 72 A1 chips
Jan  4 09:03:22 (none) local0.warn innominer_T2: Detected the 3 A1 chain with 72 chips
Jan  4 09:03:22 (none) local0.info innominer_T2: start to configure all chain from 0 to 120
Jan  4 09:03:22 (none) local0.err innominer_T2: start to read temp
Jan  4 09:03:23 (none) local0.info innominer_T2: start to configure chain 0
Jan  4 09:03:23 (none) local0.notice innominer_T2: A1 = 120,0, Clock = 120MHz
Jan  4 09:03:23 (none) local0.err innominer_T2: start to read temp
Jan  4 09:04:27 (none) auth.info login[1330]: root login on 'pts/0'
Jan  4 09:04:27 (none) local0.warn innominer_T2: Started cgminer 4.10.0
Jan  4 09:04:27 (none) local0.info innominer_T2: hardware version is G19
Jan  4 09:04:27 (none) local0.info innominer_T2: miner type is T2
Jan  4 09:04:27 (none) local0.notice innominer_T2: A1 = 1044,92, Clock = 1044MHz
Jan  4 09:04:27 (none) local0.notice innominer_T2: A1 = 1044,92, Clock = 1044MHz
Jan  4 09:04:27 (none) local0.notice innominer_T2: A1 = 1044,92, Clock = 1044MHz
Jan  4 09:04:27 (none) local0.notice innominer_T2: A1 = 1044,92, Clock = 1044MHz
Jan  4 09:04:27 (none) local0.notice innominer_T2: A1 = 1044,92, Clock = 1044MHz
Jan  4 09:04:27 (none) local0.notice innominer_T2: A1 = 1044,92, Clock = 1044MHz
Jan  4 09:04:27 (none) local0.notice innominer_T2: A1 = 1044,92, Clock = 1044MHz
Jan  4 09:04:27 (none) local0.notice innominer_T2: A1 = 1044,92, Clock = 1044MHz
Jan  4 09:04:27 (none) local0.warn innominer_T2: A1: checking A1 chain
Jan  4 09:04:27 (none) local0.warn innominer_T2: SPI '/dev/spidev0.0': mode=1, bits=8, speed=1500000
Jan  4 09:04:29 (none) local0.warn innominer_T2: SPI '/dev/spidev1.0': mode=1, bits=8, speed=1500000
Jan  4 09:04:31 (none) local0.warn innominer_T2: SPI '/dev/spidev2.0': mode=1, bits=8, speed=1500000
Jan  4 09:04:33 (none) local0.warn innominer_T2: SPI '/dev/spidev3.0': mode=1, bits=8, speed=1500000
Jan  4 09:04:35 (none) local0.warn innominer_T2: SPI '/dev/spidev4.0': mode=1, bits=8, speed=1500000
Jan  4 09:04:37 (none) local0.warn innominer_T2: SPI '/dev/spidev5.0': mode=1, bits=8, speed=1500000
Jan  4 09:04:39 (none) local0.warn innominer_T2: SPI '/dev/spidev6.0': mode=1, bits=8, speed=1500000
Jan  4 09:04:41 (none) local0.warn innominer_T2: SPI '/dev/spidev7.0': mode=1, bits=8, speed=1500000
Jan  4 09:04:54 (none) local0.err innominer_T2: Plug Status[0] = 0
Jan  4 09:05:00 (none) local0.err innominer_T2: Plug Status[1] = 0
Jan  4 09:05:06 (none) local0.err innominer_T2: Plug Status[2] = 0
Jan  4 09:05:12 (none) local0.err innominer_T2: Plug Status[3] = 0
Jan  4 09:05:18 (none) local0.err innominer_T2: Plug Status[4] = 1
Jan  4 09:05:18 (none) local0.err innominer_T2: chain:4 the plat is not inserted
Jan  4 09:05:24 (none) local0.err innominer_T2: Plug Status[5] = 1
Jan  4 09:05:24 (none) local0.err innominer_T2: chain:5 the plat is not inserted
Jan  4 09:05:30 (none) local0.err innominer_T2: Plug Status[6] = 1
Jan  4 09:05:30 (none) local0.err innominer_T2: chain:6 the plat is not inserted
Jan  4 09:05:36 (none) local0.err innominer_T2: Plug Status[7] = 1
Jan  4 09:05:36 (none) local0.err innominer_T2: chain:7 the plat is not inserted
Jan  4 09:05:36 (none) local0.info innominer_T2: pre 0: A1 init chain
Jan  4 09:05:37 (none) local0.warn innominer_T2: 0: detected 72 chips
Jan  4 09:05:37 (none) local0.warn innominer_T2: collect core success
Jan  4 09:05:37 (none) local0.warn innominer_T2: 0: no A1 chip-chain detected
Jan  4 09:05:37 (none) local0.warn innominer_T2: spidev0.0: 0: Found 72 A1 chips
Jan  4 09:05:37 (none) local0.warn innominer_T2: Detected the 0 A1 chain with 72 chips
Jan  4 09:05:37 (none) local0.info innominer_T2: pre 1: A1 init chain
Jan  4 09:05:37 (none) local0.warn innominer_T2: cmd reset: poll fail !
Jan  4 09:05:38 (none) local0.warn innominer_T2: cmd bist start: poll fail !
Jan  4 09:05:38 (none) local0.warn innominer_T2: bist start fail
Jan  4 09:05:38 (none) local0.err innominer_T2: init 1 A1 chain fail
Jan  4 09:05:38 (none) local0.info innominer_T2: pre 2: A1 init chain
Jan  4 09:05:39 (none) local0.warn innominer_T2: 2: detected 72 chips
Jan  4 09:05:39 (none) local0.warn innominer_T2: collect core success
Jan  4 09:05:39 (none) local0.warn innominer_T2: 2: no A1 chip-chain detected
Jan  4 09:05:39 (none) local0.warn innominer_T2: spidev2.0: 2: Found 72 A1 chips
Jan  4 09:05:39 (none) local0.warn innominer_T2: Detected the 2 A1 chain with 72 chips
Jan  4 09:05:39 (none) local0.info innominer_T2: pre 3: A1 init chain
Jan  4 09:05:40 (none) local0.warn innominer_T2: 3: detected 72 chips
Jan  4 09:05:40 (none) local0.warn innominer_T2: collect core success
Jan  4 09:05:40 (none) local0.warn innominer_T2: 3: no A1 chip-chain detected
Jan  4 09:05:40 (none) local0.warn innominer_T2: spidev3.0: 3: Found 72 A1 chips
Jan  4 09:05:40 (none) local0.warn innominer_T2: Detected the 3 A1 chain with 72 chips
Jan  4 09:05:40 (none) local0.info innominer_T2: start to configure all chain from 0 to 120
Jan  4 09:05:40 (none) local0.err innominer_T2: start to read temp
Jan  4 09:05:40 (none) local0.info innominer_T2: start to configure chain 0
Jan  4 09:05:40 (none) local0.notice innominer_T2: A1 = 120,0, Clock = 120MHz
Jan  4 09:05:41 (none) local0.err innominer_T2: start to read temp

I've tried:
Reflashing firmware
restoring factory defaults
re-saving all pools
checking /lib/python3.4/_sysconfigdata.py for corruption

more logs that might help, this shows where it craps out

Code:
innominer_T2 --debug
 [2018-01-04 11:30:28.195] Started cgminer 4.10.0
 [2018-01-04 11:30:28.195] A1 detect
 [2018-01-04 11:30:28.195] hardware version is G19
 [2018-01-04 11:30:28.196] miner type is T2
pwm  name:/dev/pwmgen0.0.
pwm  step:5.
duty max: 100.
targ freq:20000.
freq rate:20000.
fan speed thrd:100.
fan up thrd:55.
fan down thrd:35.
auto_fan true, fan_speed 1
 [2018-01-04 11:30:28.197] A1 = 120,0, Clock = 120MHz
 [2018-01-04 11:30:28.197] A1 = 120,0, Clock = 120MHz
 [2018-01-04 11:30:28.197] A1 = 120,0, Clock = 120MHz
 [2018-01-04 11:30:28.197] A1 = 120,0, Clock = 120MHz
 [2018-01-04 11:30:28.197] A1 = 120,0, Clock = 120MHz
 [2018-01-04 11:30:28.197] A1 = 120,0, Clock = 120MHz
 [2018-01-04 11:30:28.197] A1 = 120,0, Clock = 120MHz
 [2018-01-04 11:30:28.198] A1 = 120,0, Clock = 120MHz
 [2018-01-04 11:30:28.198] A1: checking A1 chain
 [2018-01-04 11:30:28.198] SPI '/dev/spidev0.0': mode=1, bits=8, speed=1500000
 [2018-01-04 11:30:30.199] SPI '/dev/spidev1.0': mode=1, bits=8, speed=1500000
 [2018-01-04 11:30:32.200] SPI '/dev/spidev2.0': mode=1, bits=8, speed=1500000
 [2018-01-04 11:30:34.201] SPI '/dev/spidev3.0': mode=1, bits=8, speed=1500000
 [2018-01-04 11:30:36.203] SPI '/dev/spidev4.0': mode=1, bits=8, speed=1500000
 [2018-01-04 11:30:38.204] SPI '/dev/spidev5.0': mode=1, bits=8, speed=1500000
 [2018-01-04 11:30:40.205] SPI '/dev/spidev6.0': mode=1, bits=8, speed=1500000
 [2018-01-04 11:30:42.206] SPI '/dev/spidev7.0': mode=1, bits=8, speed=1500000
 [2018-01-04 11:30:55.207] Plug Status[0] = 0
 [2018-01-04 11:31:01.208] Plug Status[1] = 0
 [2018-01-04 11:31:07.209] Plug Status[2] = 0
 [2018-01-04 11:31:13.209] Plug Status[3] = 0
 [2018-01-04 11:31:19.210] Plug Status[4] = 1
 [2018-01-04 11:31:19.210] chain:4 the plat is not inserted
 [2018-01-04 11:31:25.211] Plug Status[5] = 1
 [2018-01-04 11:31:25.211] chain:5 the plat is not inserted
 [2018-01-04 11:31:31.211] Plug Status[6] = 1
 [2018-01-04 11:31:31.211] chain:6 the plat is not inserted
 [2018-01-04 11:31:37.212] Plug Status[7] = 1
 [2018-01-04 11:31:37.212] chain:7 the plat is not inserted
 [2018-01-04 11:31:37.212] pre 0: A1 init chain
send command [reset]
send command [bist_start]
 [2018-01-04 11:31:38.222] 0: detected 72 chips
send command [bist_collect]
 [2018-01-04 11:31:38.239] collect core success
 [2018-01-04 11:31:38.239] 0: no A1 chip-chain detected
 [2018-01-04 11:31:38.249] spidev0.0: 0: Found 72 A1 chips
 [2018-01-04 11:31:38.249] Detected the 0 A1 chain with 72 chips
set_vid_value_g19:1,chain 0.
 [2018-01-04 11:31:38.249] pre 1: A1 init chain
send command [reset]
 [2018-01-04 11:31:38.255] cmd reset: poll fail !
send command [bist_start]
 [2018-01-04 11:31:39.262] cmd bist start: poll fail !
 [2018-01-04 11:31:39.262] bist start fail
 [2018-01-04 11:31:39.272] init 1 A1 chain fail
 [2018-01-04 11:31:39.272] pre 2: A1 init chain
send command [reset]
send command [bist_start]
 [2018-01-04 11:31:40.284] 2: detected 72 chips
send command [bist_collect]
 [2018-01-04 11:31:40.301] collect core success
 [2018-01-04 11:31:40.301] 2: no A1 chip-chain detected
 [2018-01-04 11:31:40.311] spidev2.0: 2: Found 72 A1 chips
 [2018-01-04 11:31:40.311] Detected the 2 A1 chain with 72 chips
set_vid_value_g19:1,chain 2.
 [2018-01-04 11:31:40.311] pre 3: A1 init chain
send command [reset]
send command [bist_start]
 [2018-01-04 11:31:41.323] 3: detected 72 chips
send command [bist_collect]
 [2018-01-04 11:31:41.340] collect core success
 [2018-01-04 11:31:41.340] 3: no A1 chip-chain detected
 [2018-01-04 11:31:41.350] spidev3.0: 3: Found 72 A1 chips
 [2018-01-04 11:31:41.350] Detected the 3 A1 chain with 72 chips
set_vid_value_g19:1,chain 3.
 [2018-01-04 11:31:41.350] start to configure all chain from 0 to 120
 [2018-01-04 11:31:41.351] start to read temp
 [2018-01-04 11:31:41.785] start to configure chain 0
 [2018-01-04 11:31:41.786] A1 = 120,0, Clock = 120MHz
 [2018-01-04 11:31:41.912] start to read temp
Segmentation fault


Title: Re: Innosilicon A4+ setup tutorial
Post by: yummyyummy on January 04, 2018, 11:02:15 AM
According to inno they keep screwing up the firmware and it burns out the thing, so at least Dec 20th firmware.
just remember the root password changed to t1t2t3a5 with the Dec 20th firmware.

I have some running Dec20th and Dec29th. both seem similarly okay.

thanks for your reply, i just wonder since my firmware is 22nd November g19, and as I see instruction from the Inno website, I see it's

"If the firmware build date is before 2017.11.24, you must upgrade through TF card"

but after I read the instruction manual to update through TF card, i have no idea how the TF card can connect with the G19 one. after the step 10 in the instruction, I see it do nothing with the TF card for the miner? so what I need to do

Please sorry for my newbie question. I've just begun some first step to the mining zone.

appreciate so much for your answer. thanks.


Title: Re: Innosilicon A4+ setup tutorial
Post by: needed357 on January 04, 2018, 04:18:14 PM
which fan should i buy?

if one fan is down


Title: Re: Innosilicon A4+ setup tutorial
Post by: Gazdac2 on January 04, 2018, 04:56:58 PM
which fan should i buy?

if one fan is down

https://www.aliexpress.com/item/New-power-motorcycle-conversion-motorcycle-fan-violence-12CM-fan-3-9A-12v-TFC1212DE-120-120-38mm/32581804418.html\
this is what I bought, but it wont arrive till this afternoon or tomorrow to see if it's any good.


According to inno they keep screwing up the firmware and it burns out the thing, so at least Dec 20th firmware.
just remember the root password changed to t1t2t3a5 with the Dec 20th firmware.

I have some running Dec20th and Dec29th. both seem similarly okay.

thanks for your reply, i just wonder since my firmware is 22nd November g19, and as I see instruction from the Inno website, I see it's

"If the firmware build date is before 2017.11.24, you must upgrade through TF card"

but after I read the instruction manual to update through TF card, i have no idea how the TF card can connect with the G19 one. after the step 10 in the instruction, I see it do nothing with the TF card for the miner? so what I need to do

Please sorry for my newbie question. I've just begun some first step to the mining zone.

appreciate so much for your answer. thanks.

Yup. No flashing of machines for us. If it fails  then I guess hope you have another miner you can plug the chains into.

Anyways, the web UI upgraded okay for me from the first firmware using the .bin.

They cleaned up their code a lot on the Dec 29th  firmware. before it was just full of redundant garbage. at least its easier to understand  some of the config files now.

And if you have firmware Before Dec 20th. It can corrupt your miner at any moment. after Dec 20th there is less risk.


Hi Gazdac2
Wondering if you can help

I have 3 miners that never start mining. System > Overview shows information OK however Miner status just spins forever.

ps|grep inno shows the ./innominer process running

Code:
innominer_T2 -o stratum+tcp://s1.theblocksfactory.com:9004 -u x -p x -o stratum+tcp://scrypt.eu.nicehash.com:3333#xnsub -u x -p x -o stratum+tcp://scrypt.usa.nicehash.com:3333#xnsub -u x -p x --A1Pll1 1044 --A1Pll2 1044 --A1Pll3 1044 --A1Pll4 1044 --A1Pll5 1044 --A1Pll6 1044 --A1Pll7 1044 --A1Pll8 1044 --A1Vol1 25 --A1Vol2 25 --A1Vol3 25 --A1Vol4 25 --A1Vol5 25 --A1Vol6 25 --A1Vol7 25 --A1Vol8 25 --A1Fanmode 1 --A1Fanspd 1 --api-listen --syslog


Segmentation fault

Uhh, some type of memory access error.
IDK if if that's related to the read only drive (Dec 20th+ firmware or what)

you can try making the drive read/write and  relaunching the miner. If that works you'd have to see if it just needs that access once, or if it needs it constantly

mount / -o rw,remount
/tmp/run.sh

if it starts mining, then halfway there.

if it successfully mines, then do a full restart(reboot) and see if it continues mining. if it wont mine now, after starting before. Then you'd have to edit the init.d to remove the remount commands.
but then that will leave you vulnerable to corruption.






Title: Re: Innosilicon A4+ setup tutorial
Post by: ukjack on January 04, 2018, 05:10:46 PM
you can try making the drive read/write and  relaunching the miner. If that works you'd have to see if it just needs that access once, or if it needs it constantly

mount / -o rw,remount
/tmp/run.sh

if it starts mining, then halfway there.


tried this, but it does the same thing unfortunately

Code:
(none) login: root
Password:
root@miner~:
mount / -o rw,remount
root@miner~:
/tmp/run.sh
killall: innominer_T2: no process killed
killall: innominer_T2: no process killed
killall: innominer_T2: no process killed
root@miner~:
root@miner~:
ps |grep inno
  839 root     476:43 python3.4 /home/inno_daemon/MServer.py
  844 root       0:00 syslogd -f /etc/syslog.conf -O /tmp/log/innominer.log -s 1024 -b 5
 8704 root       0:00 innominer_T2 -o stratum+tcp://s1.theblocksfactory.com:9004 -u x -p x -o stratum+tcp://scrypt.eu.nicehash.com:3333#xnsub -u x -p x -o stratum+tcp://scrypt.usa.nicehash.com:3333#xnsub -u x -p x --A1Pll1 1044 --A1Pll2 1044 --A1Pll3 1044 --A1Pll4 1044 --A1Pll5 1044 --A1Pll6 1044 --A1Pll7 1044 --A1Pll8 1044 --A1Vol1 25 --A1Vol2 25 --A1Vol3 25 --A1Vol4 25 --A1Vol5 25 --A1Vol6 25 --A1Vol7 25 --A1Vol8 25 --A1Fanmode 1 --A1Fanspd 1 --api-listen --syslog

Code:
root@miner~:
ps |grep inno
  839 root     480:17 python3.4 /home/inno_daemon/MServer.py
  844 root       0:00 syslogd -f /etc/syslog.conf -O /tmp/log/innominer.log -s 1024 -b 5
 8948 root       0:00 grep inno

Code:
root@miner~:
innominer_T2 --debug -o stratum+tcp://s1.theblocksfactory.com:9004 -u x -p x -o stratum+tcp://scrypt.eu.nicehash.com:3
333#xnsub -u x-p x -o stratum+tcp://scrypt.usa.nicehash.com:3333#xnsub -u 3x -p x --A1Pll1 1044 --A1Pll2 1044 --A1Pll3 1044 --A1Pll4 1044 --A1Pll5 1044 --A1Pll6 1044 --A1Pll7 1044 --A1Pll8 1044 --
A1Vol1 25 --A1Vol2 25 --A1Vol3 25 --A1Vol4 25 --A1Vol5 25 --A1Vol6 25 --A1Vol7 25 --A1Vol8 25 --A1Fanmode 1 --A1Fanspd 1 --api-list
en --syslog
 [2018-01-04 17:06:22.949] Global quota greatest common denominator set to 1
 [2018-01-04 17:06:22.949] start to set url
 [2018-01-04 17:06:22.949] Global quota greatest common denominator set to 1
 [2018-01-04 17:06:22.949] Pool 1 extranonce subscribing enabled.
 [2018-01-04 17:06:22.949] start to set url
 [2018-01-04 17:06:22.950] Global quota greatest common denominator set to 1
 [2018-01-04 17:06:22.950] Pool 2 extranonce subscribing enabled.
 [2018-01-04 17:06:22.950] start to set url
pwm  name:/dev/pwmgen0.0.
pwm  step:5.
duty max: 100.
targ freq:20000.
freq rate:20000.
fan speed thrd:100.
fan up thrd:55.
fan down thrd:35.
auto_fan true, fan_speed 1
send command [reset]
send command [bist_start]
send command [bist_collect]
set_vid_value_g19:25,chain 0.
send command [reset]
send command [bist_start]
send command [reset]
send command [bist_start]
send command [bist_collect]
set_vid_value_g19:25,chain 2.
send command [reset]
send command [bist_start]
send command [bist_collect]
set_vid_value_g19:25,chain 3.
Segmentation fault



Title: Re: Innosilicon A4+ setup tutorial
Post by: needed357 on January 04, 2018, 05:25:29 PM
which fan should i buy?

if one fan is down

https://www.aliexpress.com/item/New-power-motorcycle-conversion-motorcycle-fan-violence-12CM-fan-3-9A-12v-TFC1212DE-120-120-38mm/32581804418.html\
this is what I bought, but it wont arrive till this afternoon or tomorrow to see if it's any good.







link not work, can you tell me if you tested that


Title: Re: Innosilicon A4+ setup tutorial
Post by: Gazdac2 on January 04, 2018, 06:22:27 PM
you can try making the drive read/write and  relaunching the miner. If that works you'd have to see if it just needs that access once, or if it needs it constantly

mount / -o rw,remount
/tmp/run.sh

if it starts mining, then halfway there.


tried this, but it does the same thing unfortunately

Code:
(none) login: root
Password:
root@miner~:
mount / -o rw,remount
root@miner~:
/tmp/run.sh
killall: innominer_T2: no process killed
killall: innominer_T2: no process killed
killall: innominer_T2: no process killed
root@miner~:
root@miner~:
ps |grep inno
  839 root     476:43 python3.4 /home/inno_daemon/MServer.py
  844 root       0:00 syslogd -f /etc/syslog.conf -O /tmp/log/innominer.log -s 1024 -b 5
 8704 root       0:00 innominer_T2 -o stratum+tcp://s1.theblocksfactory.com:9004 -u x -p x -o stratum+tcp://scrypt.eu.nicehash.com:3333#xnsub -u x -p x -o stratum+tcp://scrypt.usa.nicehash.com:3333#xnsub -u x -p x --A1Pll1 1044 --A1Pll2 1044 --A1Pll3 1044 --A1Pll4 1044 --A1Pll5 1044 --A1Pll6 1044 --A1Pll7 1044 --A1Pll8 1044 --A1Vol1 25 --A1Vol2 25 --A1Vol3 25 --A1Vol4 25 --A1Vol5 25 --A1Vol6 25 --A1Vol7 25 --A1Vol8 25 --A1Fanmode 1 --A1Fanspd 1 --api-listen --syslog

Code:
root@miner~:
ps |grep inno
  839 root     480:17 python3.4 /home/inno_daemon/MServer.py
  844 root       0:00 syslogd -f /etc/syslog.conf -O /tmp/log/innominer.log -s 1024 -b 5
 8948 root       0:00 grep inno

Code:
root@miner~:
innominer_T2 --debug -o stratum+tcp://s1.theblocksfactory.com:9004 -u x -p x -o stratum+tcp://scrypt.eu.nicehash.com:3
333#xnsub -u x-p x -o stratum+tcp://scrypt.usa.nicehash.com:3333#xnsub -u 3x -p x --A1Pll1 1044 --A1Pll2 1044 --A1Pll3 1044 --A1Pll4 1044 --A1Pll5 1044 --A1Pll6 1044 --A1Pll7 1044 --A1Pll8 1044 --
A1Vol1 25 --A1Vol2 25 --A1Vol3 25 --A1Vol4 25 --A1Vol5 25 --A1Vol6 25 --A1Vol7 25 --A1Vol8 25 --A1Fanmode 1 --A1Fanspd 1 --api-list
en --syslog
 [2018-01-04 17:06:22.949] Global quota greatest common denominator set to 1
 [2018-01-04 17:06:22.949] start to set url
 [2018-01-04 17:06:22.949] Global quota greatest common denominator set to 1
 [2018-01-04 17:06:22.949] Pool 1 extranonce subscribing enabled.
 [2018-01-04 17:06:22.949] start to set url
 [2018-01-04 17:06:22.950] Global quota greatest common denominator set to 1
 [2018-01-04 17:06:22.950] Pool 2 extranonce subscribing enabled.
 [2018-01-04 17:06:22.950] start to set url
pwm  name:/dev/pwmgen0.0.
pwm  step:5.
duty max: 100.
targ freq:20000.
freq rate:20000.
fan speed thrd:100.
fan up thrd:55.
fan down thrd:35.
auto_fan true, fan_speed 1
send command [reset]
send command [bist_start]
send command [bist_collect]
set_vid_value_g19:25,chain 0.
send command [reset]
send command [bist_start]
send command [reset]
send command [bist_start]
send command [bist_collect]
set_vid_value_g19:25,chain 2.
send command [reset]
send command [bist_start]
send command [bist_collect]
set_vid_value_g19:25,chain 3.
Segmentation fault


ahh damnit...
this is a multithreaded application I bet the error is related to
Code:
[2018-01-04 17:06:22.950] start to set url
https://www.nicehash.com/help/scrypt-mining

did you try a different pool other than nicehash?
are you escaping the #?
eg 3333/#xnsub
you might even have to enter it as "///#" depending on how many levels of stupid.

"it works for us, on our own pools. so send it to the customers"- inno


Title: Re: Innosilicon A4+ setup tutorial
Post by: lonerko on January 04, 2018, 06:50:04 PM
Hi all
I  have some problem with a5 after reboot.
Symptoms were the HTTP control page loading, but not showing any data e.g. not showing me  "miner type" under system.

Manually running each of the commands in /etc/init.d/rcS
The problem in "python3.4 /home/inno_daemon/MServer.py"

Code:
root@miner~:
python3.4 /home/inno_daemon/MServer.py
Traceback (most recent call last):
  File "/home/inno_daemon/MServer.py", line 12, in <module>
    from MParser  import *
  File "/home/inno_daemon/MParser.py", line 17, in <module>
    from inno_lib import *
  File "/home/inno_py/inno_lib.py", line 5, in <module>
    import cgi
  File "/lib/python3.4/cgi.py", line 39, in <module>
    from email.parser import FeedParser
  File "/lib/python3.4/email/parser.py", line 12, in <module>
    from email.feedparser import FeedParser, BytesFeedParser
  File "/lib/python3.4/email/feedparser.py", line 27, in <module>
    from email import message
  File "/lib/python3.4/email/message.py", line 16, in <module>
    from email import utils
  File "/lib/python3.4/email/utils.py", line 40, in <module>
    from email.charset import Charset
  File "/lib/python3.4/email/charset.py", line 14, in <module>
    import email.base64mime
  File "/lib/python3.4/email/base64mime.py", line 37, in <module>
    from base64 import b64encode
  File "<frozen importlib._bootstrap>", line 2237, in _find_and_load
  File "<frozen importlib._bootstrap>", line 2226, in _find_and_load_unlocked
  File "<frozen importlib._bootstrap>", line 1200, in _load_unlocked
  File "<frozen importlib._bootstrap>", line 1129, in _exec
  File "<frozen importlib._bootstrap>", line 1467, in exec_module
  File "<frozen importlib._bootstrap>", line 1570, in get_code
  File "<frozen importlib._bootstrap>", line 656, in _compile_bytecode
ValueError: bad marshal data (unknown type code)
Does anyone have any ideas?


Title: Re: Innosilicon A4+ setup tutorial
Post by: Gazdac2 on January 04, 2018, 07:08:19 PM
Hi all
I  have some problem with a5 after reboot.
Symptoms were the HTTP control page loading, but not showing any data e.g. not showing me  "miner type" under system.

Manually running each of the commands in /etc/init.d/rcS
The problem in "python3.4 /home/inno_daemon/MServer.py"

Code:

ValueError: bad marshal data (unknown type code)
Does anyone have any ideas?

Only time i've seen that error is using the wrong \ /. could be in your pool url, could be in their code. who knows.
https://
not
https:\\

or if there is an extra / laying around could be bad too.
this can be a difference between windows and unix.


Title: Re: Innosilicon A4+ setup tutorial
Post by: lonerko on January 04, 2018, 07:37:31 PM
Problem was in /lib/python3.4/base64.py 


Title: Re: Innosilicon A4+ setup tutorial
Post by: vmssecuritycloud on January 04, 2018, 09:16:49 PM
Has anyone had an issue where only one ASIC is showing up? Very frustrating to say the least.


Title: Re: Innosilicon A4+ setup tutorial
Post by: BWYeung on January 05, 2018, 03:20:05 AM
WOOT WOOT...I'm mining.

I had an Innosilicon tech remote into my system and got it running. He was able to determine my A4+ wasn't connecting to the internet correctly. The culprit was the Network Gateway; once he put in the correct one (router's IP address) into the gateway field, I started mining.

Hope this helps others who were having spinning Miner Status page like I was.


Title: Re: Innosilicon A4+ setup tutorial
Post by: Giantppl on January 05, 2018, 03:40:39 AM
Just got mine fixed also, Guy was helping me install some software thru remote and reboot the System and worked.. like I said I’m not tech savvy enuf.. but both running well now! Innosilicon rocks and after sales support is superb!

WOOT WOOT...I'm mining.

I had an Innosilicon tech remote into my system and got it running. He was able to determine my A4+ wasn't connecting to the internet correctly. The culprit was the Network Gateway; once he put in the correct one (router's IP address) into the gateway field, I started mining.

Hope this helps others who were having spinning Miner Status page like I was.


Title: Re: Innosilicon A4+ setup tutorial
Post by: Gazdac2 on January 05, 2018, 05:35:30 AM
Just got mine fixed also, Guy was helping me install some software thru remote and reboot the System and worked.. like I said I’m not tech savvy enuf.. but both running well now! Innosilicon rocks and after sales support is superb!

WOOT WOOT...I'm mining.

I had an Innosilicon tech remote into my system and got it running. He was able to determine my A4+ wasn't connecting to the internet correctly. The culprit was the Network Gateway; once he put in the correct one (router's IP address) into the gateway field, I started mining.

Hope this helps others who were having spinning Miner Status page like I was.

Good to hear. With how little sales would communicate, and receiving damaged fans that I have to replace, I kinda gave up on ever getting any real support from them.
Maybe if something I can't fix happens they would be able to.


Title: Re: Innosilicon A4+ setup tutorial
Post by: Chan8 on January 05, 2018, 06:02:53 AM
Thank you for the set up guide.


Title: Re: Innosilicon A4+ setup tutorial
Post by: ukjack on January 05, 2018, 01:08:48 PM
New firmware out today update_180105

for me fixed the miners that refused to start mining


Title: Re: Innosilicon A4+ setup tutorial
Post by: Giantppl on January 05, 2018, 01:12:03 PM
You can try using a different socket for the individual asic. It could be the problem mine I suspect it’s the WiFi plug that stopped my miner.. tried it today and it stopped after it’s fixed..
Has anyone had an issue where only one ASIC is showing up? Very frustrating to say the least.


Title: Re: Innosilicon A4+ setup tutorial
Post by: kb8679 on January 05, 2018, 05:47:47 PM
New firmware out today update_180105

for me fixed the miners that refused to start mining

And they didn't bother to change the root pw. Excellent. :)


Title: Re: Innosilicon A4+ setup tutorial
Post by: ukjack on January 05, 2018, 08:36:58 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.


Title: Re: Innosilicon A4+ setup tutorial
Post by: kb8679 on January 05, 2018, 11:48:57 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.

Fixed difficulty is The thing with these. With some vardiff pools I've experienced similar behaviour as well. I'm currently mining DGB with 'multipool.us' via local stratum proxy and my measely 10 units keeps on rocking with no issues. Avg hashrate per unit (as reported by the pool side) are around 560-610MHs per unit. And I also tried NH after their "little haxx-problemo". Even tho using vardiff, it seemed to deliver pretty much what they "promised" or estimated.

Maybe the local stratum proxy (which I strongly suggest using, since you have such a huge number of miners) is the answer, or at least would help you out a bit?


Title: Re: Innosilicon A4+ setup tutorial
Post by: Gazdac2 on January 06, 2018, 08:25:52 AM
Hi guys,

Got my replacement fans today.
Pretty interesting stuff.

https://i.imgur.com/LnRKdXN.jpg

So there are the fans from one of my miners that "sings" all day long that I suspect a fan will go out soon.

The rear fan (the one with the extra long cable) is for sure not a new fan. Look how aged the plastic is, there are some pits and scratches in it as well.
The good news is the inside is NOT covered in rust and corrosion on every solder point like my first fan that died in 48 hours. So old used fan, for sure, might last a while longer, Yes.

It also has a different circuit board than the dead one, even though both are labeled the same. Wonder hold old that broken fan I got with my "new" miner is.

Anyways.  The TFC 1212DE i ordered came as a "-5b66" instead of a "-sp07"
I don't know the difference, but it works pretty damn well.

Only issue with this one was the front fan cable will barely reach. The back cable needs to be extended,just like they already did with all of the back fans. Spliced, soldered, whatever. Probably should buy a molex crimper and some ends.

The fans I ordered
https://www.aliexpress.com/item/New-power-motorcycle-conversion-motorcycle-fan-violence-12CM-fan-3-9A-12v-TFC1212DE-120-120-38mm/32581804418.html (https://www.aliexpress.com/item/New-power-motorcycle-conversion-motorcycle-fan-violence-12CM-fan-3-9A-12v-TFC1212DE-120-120-38mm/32581804418.html)
From this store
https://www.aliexpress.com/store/1358964?spm=2114.10010108.0.0.7ff34b8aD4XZRw (https://www.aliexpress.com/store/1358964?spm=2114.10010108.0.0.7ff34b8aD4XZRw) (YX Technology)

And yes, my miners do disconnect and stop mining every now and then, for zero reason.  Stupid miners.



Title: Re: Innosilicon A4+ setup tutorial
Post by: kb8679 on January 07, 2018, 07:27:09 AM
Daaaaaamn that's nasty.... suddenly I have the urge to go see my miners as well. :P

Did you see any difference in temps after installing the new fans?

E: Thanks for the fan model & link tho. I think I'm gonna order few just in case. :)

Hi guys,

Got my replacement fans today.
Pretty interesting stuff.

https://i.imgur.com/LnRKdXN.jpg

So there are the fans from one of my miners that "sings" all day long that I suspect a fan will go out soon.

The rear fan (the one with the extra long cable) is for sure not a new fan. Look how aged the plastic is, there are some pits and scratches in it as well.
The good news is the inside is NOT covered in rust and corrosion on every solder point like my first fan that died in 48 hours. So old used fan, for sure, might last a while longer, Yes.

It also has a different circuit board than the dead one, even though both are labeled the same. Wonder hold old that broken fan I got with my "new" miner is.

Anyways.  The TFC 1212DE i ordered came as a "-5b66" instead of a "-sp07"
I don't know the difference, but it works pretty damn well.

Only issue with this one was the front fan cable will barely reach. The back cable needs to be extended,just like they already did with all of the back fans. Spliced, soldered, whatever. Probably should buy a molex crimper and some ends.

The fans I ordered
https://www.aliexpress.com/item/New-power-motorcycle-conversion-motorcycle-fan-violence-12CM-fan-3-9A-12v-TFC1212DE-120-120-38mm/32581804418.html (https://www.aliexpress.com/item/New-power-motorcycle-conversion-motorcycle-fan-violence-12CM-fan-3-9A-12v-TFC1212DE-120-120-38mm/32581804418.html)
From this store
https://www.aliexpress.com/store/1358964?spm=2114.10010108.0.0.7ff34b8aD4XZRw (https://www.aliexpress.com/store/1358964?spm=2114.10010108.0.0.7ff34b8aD4XZRw) (YX Technology)

And yes, my miners do disconnect and stop mining every now and then, for zero reason.  Stupid miners.




Title: Re: Innosilicon A4+ setup tutorial
Post by: Gazdac2 on January 07, 2018, 11:02:10 PM
Daaaaaamn that's nasty.... suddenly I have the urge to go see my miners as well. :P

Did you see any difference in temps after installing the new fans?

E: Thanks for the fan model & link tho. I think I'm gonna order few just in case. :)


Pretty hard to tell, about temps, the dual fan ones were already just over 60c, and now I have the early Jan firmware installed, which lowers the fan speeds even more. I did run it a few minutes at 100% before disassembling it, and the old-working one would bounce on the table it was so unbalanced. So, really don't want those vibrations either way.

So, no science here. I have higher clock speeds, higher voltage, higher profit, and new fans on this machine, and the same temps. Could be firmware could be the fans. Either way it's now quieter at the same fan %. I'll re purpose the old ones for something one day anyways, like on a GPU miner, or in the crack of the window for exhaust.
And the one with the dead fan is now able to achieve 700 MH/s like the rest now.

If ordering those exact ones just be prepared to add a bit of wire length.

New problem:
I have trouble with chains not starting on the new firmware. Seems like they don't respond fast enough if they are cold. I moved them to ports 0-3 instead of 4-7 and it hasn't had that problem cold booting again. It's almost like it doesn't quite wait long enough for them to wake up.

I have room for 100 more miners, but inno sales team scared all my investors away. Anyone got a $400,000 loan laying around? :p



Title: Re: Innosilicon A4+ setup tutorial
Post by: diaahussein on January 08, 2018, 07: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"


Title: Re: Innosilicon A4+ setup tutorial
Post by: diaahussein on January 08, 2018, 08: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


Title: Re: Innosilicon A4+ setup tutorial
Post by: diaahussein on January 09, 2018, 01:56:59 PM
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


Title: Re: Innosilicon A4+ setup tutorial
Post by: compir on January 09, 2018, 02:58:41 PM
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.


Title: Re: Innosilicon A4+ setup tutorial
Post by: kb8679 on January 09, 2018, 03:30:06 PM
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).


Title: Re: Innosilicon A4+ setup tutorial
Post by: diaahussein on January 09, 2018, 07: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.


Title: Re: Innosilicon A4+ setup tutorial
Post by: ilostmyface on January 10, 2018, 02:18:18 AM
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.


Title: Re: Innosilicon A4+ setup tutorial
Post by: jmirv on January 10, 2018, 02:40:58 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.


Title: Re: Innosilicon A4+ setup tutorial
Post by: ilostmyface on January 10, 2018, 02:54:13 AM
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.


Title: Re: Innosilicon A4+ setup tutorial
Post by: Gazdac2 on January 10, 2018, 04: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.


Title: Re: Innosilicon A4+ setup tutorial
Post by: Didibell24 on January 10, 2018, 07: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?

 




Title: Re: Innosilicon A4+ setup tutorial
Post by: Gazdac2 on January 10, 2018, 08: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.







Title: Re: Innosilicon A4+ setup tutorial
Post by: diaahussein on January 10, 2018, 04: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


Title: Re: Innosilicon A4+ setup tutorial
Post by: diaahussein on January 10, 2018, 05: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
 


Title: Re: Innosilicon A4+ setup tutorial
Post by: CorbinDallas on January 10, 2018, 08: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 :)

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

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.









Title: Re: Innosilicon A4+ setup tutorial
Post by: needed357 on January 12, 2018, 04:31:29 AM
what is the best temperature?

and how can i see the temp in awesome miner?



Title: Re: Innosilicon A4+ setup tutorial
Post by: shepardblue on January 14, 2018, 06: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  :(

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


Title: Re: Innosilicon A4+ setup tutorial
Post by: meet37 on January 14, 2018, 09:59:10 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  :(

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
and where to get the logs of asik ? in the web interface nothing found


Title: Re: Innosilicon A4+ setup tutorial
Post by: shepardblue on January 14, 2018, 01:57:10 PM
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


Title: Re: Innosilicon A4+ setup tutorial
Post by: needed357 on January 16, 2018, 01:00:17 AM
how can i overclock them?


Title: Re: Innosilicon A4+ setup tutorial
Post by: shepardblue on January 16, 2018, 02:31:40 AM
Bump the Frequency to 1152Mhz and Lower VID (which raises the voltage) on the Miner General Configuration page. There are instructions on that Miner General Configuration too. Read those for sure.

Try frequency 1152MHz and then try adjusting VID between 22-14. Should get faster as you approach 14, probably will get the best rate when VID is somewhere below 20. I still haven't explored what's optimal for my machines. Waiting for the warranty to expire before I mess with overclocking but I overclocked my own A4 Dominators and it worked the same way.


Title: Re: Innosilicon A4+ setup tutorial
Post by: needed357 on January 17, 2018, 08:33:49 PM
update_180112.bin

same root password? somebody know? :D


Title: Re: Innosilicon A4+ setup tutorial
Post by: shepardblue on January 18, 2018, 01:32:24 AM
Just upgraded and tested telnet, same username and password: root, t1t2t3a5


Title: Re: Innosilicon A4+ setup tutorial
Post by: meet37 on January 18, 2018, 12:18:29 PM
shepardblue thanks

who faced can be such a problem ? on litecoinpool mainit consistently good, and if you connect on some multipool for example mining-dutch, it is some time works normally and then on any Board gets slick ? how to deal with it ?

noticed when mined 1 coin when a HW is on the Board hashrate in webinterface does not change, and when you mine on multipool when a HW on this Board is reduced hashrate

now multipool worked for an hour without hw, but self-rebooted, the last saved logs here, prompt the logs can be a reason to find out a reboot? maybe the same as the Board disables the

[spoil]Jan 19 13:53:10 (none) local0.err cgminer[935]: A1_scanwork n cid 1:arv:33.33, lest:21.33, hest:522 witt
Jan 19 13:53:12 (none) local0.err cgminer[935]: A1_scanwork n cid 0:arv:33.33, lest:16.00, hest:522 witt
Jan 19 13:53:14 (none) local0.err cgminer[935]: A1_scanwork n cid 3:arv:34.00, lest:20.67, hest:525 witt
Jan 19 13:53:14 (none) local0.info cgminer[935]: Testing pool stratum+tcp://mining-dutch.nl:8888#xnsub
Jan 19 13:53:14 (none) local0.info cgminer[935]: Testing pool stratum+tcp://litecoinpool.org:3333
Jan 19 13:53:14 (none) local0.info cgminer[935]: Testing pool stratum+tcp://scrypt.eu.nicehash.com:3333#xnsub
Jan 19 13:53:16 (none) local0.err cgminer[935]: A1_scanwork n cid 2:arv:34.00, lest:19.33, hest:521 witt
Jan 19 13:53:19 (none) local0.info cgminer[935]: Testing pool stratum+tcp://mining-dutch.nl:8888#xnsub
Jan 19 13:53:19 (none) local0.info cgminer[935]: Testing pool stratum+tcp://litecoinpool.org:3333
Jan 19 13:53:19 (none) local0.info cgminer[935]: Testing pool stratum+tcp://scrypt.eu.nicehash.com:3333#xnsub
Jan 19 13:53:21 (none) local0.err cgminer[935]: A1_scanwork n cid 1:arv:33.33, lest:21.33, hest:522 witt
Jan 19 13:53:22 (none) local0.info cgminer[935]: recieve notify,we must flush work
Jan 19 13:53:22 (none) local0.notice cgminer[935]: Network diff set to 33.6K
Jan 19 13:53:22 (none) local0.info cgminer[935]: New block: 8b91f36c8e0f1e483b1f1e69730a82afd184e9813295028fb985013ca564
7731... diff 33.6K
Jan 19 13:53:22 (none) local0.notice cgminer[935]: Stratum from pool 0 detected new block at height 0
Jan 19 13:53:22 (none) local0.info cgminer[935]: Work update message received
Jan 19 13:53:22 (none) local0.info cgminer[935]: recieve notify,we must flush work
Jan 19 13:53:22 (none) local0.notice cgminer[935]: Stratum from pool 0 requested work restart
Jan 19 13:53:22 (none) local0.info cgminer[935]: Work update message received
Jan 19 13:53:22 (none) local0.info cgminer[935]: Received kill message
Jan 19 13:53:23 (none) local0.info cgminer[935]: recieve notify,we must flush work
Jan 19 13:53:23 (none) local0.notice cgminer[935]: Stratum from pool 0 requested work restart
Jan 19 13:53:23 (none) local0.info cgminer[935]: Work update message received
Jan 19 13:53:23 (none) local0.info cgminer[935]: recieve notify,we must flush work
Jan 19 13:53:23 (none) local0.notice cgminer[935]: Stratum from pool 0 requested work restart
Jan 19 13:53:23 (none) local0.info cgminer[935]: Work update message received
Jan 19 13:53:23 (none) local0.err cgminer[935]: Shutdown signal received.
Jan 19 13:53:23 (none) local0.warn cgminer[935]:  Summary of runtime statistics:
Jan 19 13:53:23 (none) local0.warn cgminer[935]: Started at [2018-01-19 13:13:53.464]
Jan 19 13:53:23 (none) local0.warn cgminer[935]: Runtime: 0 hrs : 39 mins : 29 secs
Jan 19 13:53:23 (none) local0.warn cgminer[935]: Average hashrate: 629.0 Mhash/s
Jan 19 13:53:23 (none) local0.warn cgminer[935]: Solved blocks: 0
Jan 19 13:53:23 (none) local0.warn cgminer[935]: Best share difficulty: 252M
Jan 19 13:53:23 (none) local0.warn cgminer[935]: Share submissions: 139
Jan 19 13:53:23 (none) local0.warn cgminer[935]: Accepted shares: 133
Jan 19 13:53:23 (none) local0.warn cgminer[935]: Rejected shares: 6
Jan 19 13:53:23 (none) local0.warn cgminer[935]: Accepted difficulty shares: 21317536
Jan 19 13:53:23 (none) local0.warn cgminer[935]: Rejected difficulty shares: 966000
Jan 19 13:53:23 (none) local0.warn cgminer[935]: Reject ratio: 4.3%
Jan 19 13:53:23 (none) local0.warn cgminer[935]: Hardware errors: 6
Jan 19 13:53:23 (none) local0.warn cgminer[935]: Utility (accepted shares / min): 3.37/min
Jan 19 13:53:23 (none) local0.warn cgminer[935]: Work Utility (diff1 shares solved / min): 3.52/min
Jan 19 13:53:23 (none) local0.warn cgminer[935]: Stale submissions discarded due to new blocks: 0
Jan 19 13:53:23 (none) local0.warn cgminer[935]: Unable to get work from server occasions: 0
Jan 19 13:53:23 (none) local0.warn cgminer[935]: Work items generated locally: 421713
Jan 19 13:53:23 (none) local0.warn cgminer[935]: Submitting work remotely delay occasions: 0
Jan 19 13:53:23 (none) local0.warn cgminer[935]: New blocks detected on network: 230
Jan 19 13:53:23 (none) local0.warn cgminer[935]: Pool: stratum+tcp://mining-dutch.nl:8888#xnsub
Jan 19 13:53:23 (none) local0.warn cgminer[935]:  Share submissions: 138
Jan 19 13:53:23 (none) local0.warn cgminer[935]:  Accepted shares: 132
Jan 19 13:53:23 (none) local0.warn cgminer[935]:  Rejected shares: 6
Jan 19 13:53:23 (none) local0.warn cgminer[935]:  Accepted difficulty shares: 21252000
Jan 19 13:53:23 (none) local0.warn cgminer[935]:  Rejected difficulty shares: 966000
Jan 19 13:53:23 (none) local0.warn cgminer[935]:  Reject ratio: 4.3%
Jan 19 13:53:23 (none) local0.warn cgminer[935]:  Items worked on: 325708
Jan 19 13:53:23 (none) local0.warn cgminer[935]:  Stale submissions discarded due to new blocks: 0
Jan 19 13:53:23 (none) local0.warn cgminer[935]:  Unable to get work from server occasions: 0
Jan 19 13:53:23 (none) local0.warn cgminer[935]:  Submitting work remotely delay occasions: 0
Jan 19 13:53:23 (none) local0.warn cgminer[935]: Pool: stratum+tcp://litecoinpool.org:3333
Jan 19 13:53:23 (none) local0.warn cgminer[935]:  Share submissions: 1
Jan 19 13:53:23 (none) local0.warn cgminer[935]:  Accepted shares: 1
Jan 19 13:53:23 (none) local0.warn cgminer[935]:  Rejected shares: 0
Jan 19 13:53:23 (none) local0.warn cgminer[935]:  Accepted difficulty shares: 65536
Jan 19 13:53:23 (none) local0.warn cgminer[935]:  Rejected difficulty shares: 0
Jan 19 13:53:23 (none) local0.warn cgminer[935]:  Reject ratio: 0.0%
Jan 19 13:53:23 (none) local0.warn cgminer[935]:  Items worked on: 870
Jan 19 13:53:23 (none) local0.warn cgminer[935]:  Stale submissions discarded due to new blocks: 0
Jan 19 13:53:23 (none) local0.warn cgminer[935]:  Unable to get work from server occasions: 0
Jan 19 13:53:23 (none) local0.warn cgminer[935]:  Submitting work remotely delay occasions: 0
Jan 19 13:53:23 (none) local0.warn cgminer[935]: Pool: stratum+tcp://scrypt.eu.nicehash.com:3333#xnsub
Jan 19 13:53:23 (none) local0.warn cgminer[935]:  Share submissions: 0
Jan 19 13:53:23 (none) local0.warn cgminer[935]:  Accepted shares: 0
Jan 19 13:53:23 (none) local0.warn cgminer[935]:  Rejected shares: 0
Jan 19 13:53:23 (none) local0.warn cgminer[935]:  Accepted difficulty shares: 0
Jan 19 13:53:23 (none) local0.warn cgminer[935]:  Rejected difficulty shares: 0
Jan 19 13:53:23 (none) local0.warn cgminer[935]:  Items worked on: 0
Jan 19 13:53:23 (none) local0.warn cgminer[935]:  Stale submissions discarded due to new blocks: 0
Jan 19 13:53:23 (none) local0.warn cgminer[935]:  Unable to get work from server occasions: 0
Jan 19 13:53:23 (none) local0.warn cgminer[935]:  Submitting work remotely delay occasions: 0
Jan 19 13:53:23 (none) local0.warn cgminer[935]: Summary of per device statistics:
Jan 19 13:53:23 (none) local0.warn cgminer[935]: BA1 0 (5s):943.0M (avg):157.3Mh/s | A:4830000 R:161000 HW:0 WU:0.8/m
Jan 19 13:53:23 (none) local0.warn cgminer[935]: BA1 1 (5s):944.2M (avg):157.2Mh/s | A:3929536 R:0 HW:0 WU:0.6/m
Jan 19 13:53:23 (none) local0.warn cgminer[935]: BA1 2 (5s):943.9M (avg):157.3Mh/s | A:5152000 R:483000 HW:0 WU:0.9/m
Jan 19 13:53:23 (none) local0.warn cgminer[935]: BA1 3 (5s):942.5M (avg):157.3Mh/s | A:7406000 R:322000 HW:0 WU:1.2/m
Jan 19 13:53:23 (none) local0.warn cgminer[935]:
Jan 19 13:54:32 (none) local0.warn innominer_T2: Started cgminer 4.10.0[/spoil]


Title: Re: Innosilicon A4+ setup tutorial
Post by: ilostmyface on January 20, 2018, 04:26:44 PM
Anyone update to update_180112.bin and notice the config section is bugged up ?

When I click CONFIG to change settings everything is blank in the pools and voltage option menus. Unable to change settings.


-edit update, might of been a browser cache problem.


Title: Re: Innosilicon A4+ setup tutorial
Post by: diaahussein on January 21, 2018, 04:25:12 PM
Anyone update to update_180112.bin and notice the config section is bugged up ?

When I click CONFIG to change settings everything is blank in the pools and voltage option menus. Unable to change settings.


-edit update, might of been a browser cache problem.
upgraded to update_180112 and no issues so far


Title: Re: Innosilicon A4+ setup tutorial
Post by: meet37 on January 22, 2018, 10:32:25 AM
has anyone tried the firmware downgrade ? want to try the December to return, but I fear the brick to


Title: Re: Innosilicon A4+ setup tutorial
Post by: ilostmyface on January 22, 2018, 08:07:26 PM
has anyone tried the firmware downgrade ? want to try the December to return, but I fear the brick to

I have not, I have one .bin file I downloaded on 12/15/17. But they didn't label the file apparently. I am curious about downgrading. What firmware date do you have and are looking to load ?


Title: Re: Innosilicon A4+ setup tutorial
Post by: ilostmyface on January 22, 2018, 11:24:03 PM
Anyone have any luck with missing chains ? I have one miner that boots missing ASC1 chain entirely. This happened the first day, I did do a system reboot remotely the next morning and the chain came alive. After re working the miner arrangement the chain and recycling the power arrange it won't come back. I have checked cable connection and PSU with no luck. The green light comes on when booting then goes off. I can tell the board has sharpie mark on one of PCIE connection legs and a solder touch up job on one of the the back pads of the signal cable port.

Log shows after seeing the board

Jan 22 23:32:56 (none) local0.info innominer_T2: pre 1: A1 init chain
Jan 22 23:32:56 (none) local0.warn innominer_T2: cmd reset: poll fail !
Jan 22 23:32:57 (none) local0.warn innominer_T2: cmd bist start: poll fail !
Jan 22 23:32:57 (none) local0.warn innominer_T2: bist start fail
Jan 22 23:32:57 (none) local0.err innominer_T2: init 1 A1 chain fail


Title: Re: Innosilicon A4+ setup tutorial
Post by: shepardblue on January 23, 2018, 01:43:36 PM
Anyone have any luck with missing chains ? I have one miner that boots missing ASC1 chain entirely. This happened the first day, I did do a system reboot remotely the next morning and the chain came alive. After re working the miner arrangement the chain and recycling the power arrange it won't come back. I have checked cable connection and PSU with no luck. The green light comes on when booting then goes off. I can tell the board has sharpie mark on one of PCIE connection legs and a solder touch up job on one of the the back pads of the signal cable port.

Log shows after seeing the board

Jan 22 23:32:56 (none) local0.info innominer_T2: pre 1: A1 init chain
Jan 22 23:32:56 (none) local0.warn innominer_T2: cmd reset: poll fail !
Jan 22 23:32:57 (none) local0.warn innominer_T2: cmd bist start: poll fail !
Jan 22 23:32:57 (none) local0.warn innominer_T2: bist start fail
Jan 22 23:32:57 (none) local0.err innominer_T2: init 1 A1 chain fail

I did, I contacted support and sent the chain back. Running the machine with 3 of 4 chains until I get the chain back from Innosilicon.

Support got back to me quick about the issue when I contacted them through the site (I recommend adding your order number to the message, seems to get a faster response that way but maybe that's just my experience). Your issue looks very similar to mine.


Title: Re: Innosilicon A4+ setup tutorial
Post by: mullick on January 23, 2018, 07:56:03 PM
Anyone had a controller go bad?

Went out to the mine one day after a a4+ showed offline. Strong smell of electrical fire in the mine. Traced it back to the offline a4+

First few boot attempts the smell was VERY strong. My clothes even smelled like it after returning home. Miner starts to boot. Lights on all 4 boards go off and the fault light flashes. Miner never requests an ip address. Will not boot with any boards attached. After a few attempts the smell went away.

Yesterday during troubleshooting it randomly decided to assign itself an ip address outside of my subnet (10.58.133.0/24 when my subnet is 192.168.1.0/24). Grabbed an old router and configured it to that subnet and no luck. It wouldn't even request or assign itself an ip this time.

Innosilicon keeps telling to to update the firmware via the management console. Despite my repeated emails telling them I cannot access it.


Title: Re: Innosilicon A4+ setup tutorial
Post by: kb8679 on January 23, 2018, 09:53:34 PM
Anyone had a controller go bad?

Went out to the mine one day after a a4+ showed offline. Strong smell of electrical fire in the mine. Traced it back to the offline a4+

First few boot attempts the smell was VERY strong. My clothes even smelled like it after returning home. Miner starts to boot. Lights on all 4 boards go off and the fault light flashes. Miner never requests an ip address. Will not boot with any boards attached. After a few attempts the smell went away.

Yesterday during troubleshooting it randomly decided to assign itself an ip address outside of my subnet (10.58.133.0/24 when my subnet is 192.168.1.0/24). Grabbed an old router and configured it to that subnet and no luck. It wouldn't even request or assign itself an ip this time.

Innosilicon keeps telling to to update the firmware via the management console. Despite my repeated emails telling them I cannot access it.

Holy shit.  :o

Innosilicon is one big joke. I must've have extremely good luck with Inno-lottery but this kind of shit keeps coming up. :P

Sounds like some component(s) have released their magic smoke (and even by 2018 there's no cure for that :P). It could be something simple like a resistor or capacitor blown up since you had some luck at somehow get it to "work" for a while. Though this is something you should never be worried about. This is unbeliveable.
I would personally try to fix the board or source a new one rather than deal with Innosilicon with their superior guarantee etc.

Nevertheless, I wouldn't try to boot the thing up again until the problem is located and fixed. It could do a lot more harm than what you already have. :(



Title: Re: Innosilicon A4+ setup tutorial
Post by: needed357 on January 23, 2018, 11:51:00 PM
Bump the Frequency to 1152Mhz and Lower VID (which raises the voltage) on the Miner General Configuration page. There are instructions on that Miner General Configuration too. Read those for sure.

Try frequency 1152MHz and then try adjusting VID between 22-14. Should get faster as you approach 14, probably will get the best rate when VID is somewhere below 20. I still haven't explored what's optimal for my machines. Waiting for the warranty to expire before I mess with overclocking but I overclocked my own A4 Dominators and it worked the same way.


thx

if i do the middle one or 1152 i got so many HW and pool hashrate show me the  half hashrate than inno web shows me



Title: Re: Innosilicon A4+ setup tutorial
Post by: meet37 on January 24, 2018, 07:00:18 AM
Code:
Jan 24 06:55:48 (none) local0.info cgminer[31699]: BA1 0: invalid nonce - HW error
Jan 24 06:55:48 (none) local0.warn cgminer[31699]: 0: chip 10: invalid nonce 0xbd536e01
Jan 24 06:55:49 (none) local0.err cgminer[31699]: A1_scanwork n cid 1:arv:34.00, lest:19.33, hest:521 witt
Jan 24 06:55:51 (none) local0.err cgminer[31699]: A1_scanwork n cid 3:arv:34.00, lest:21.33, hest:525 witt
Jan 24 06:55:52 (none) local0.info cgminer[31699]: BA1 3: invalid nonce - HW error
Jan 24 06:55:52 (none) local0.warn cgminer[31699]: 3: chip 47: invalid nonce 0x60ebe501
Jan 24 06:55:52 (none) local0.err cgminer[31699]: A1_scanwork n cid 0:arv:34.00, lest:16.67, hest:521 witt
Jan 24 06:55:52 (none) local0.err cgminer[31699]: A1_scanwork n cid 2:arv:33.33, lest:21.33, hest:522 witt
Jan 24 06:55:53 (none) local0.info cgminer[31699]: Testing pool stratum+tcp://litecoinpool.org:3333
Jan 24 06:55:53 (none) local0.info cgminer[31699]: Testing pool stratum+tcp://scrypt.eu.nicehash.com:3333#xnsub
Jan 24 06:55:53 (none) local0.info cgminer[31699]: Testing pool stratum+tcp://mining-dutch.nl:8888#xnsub
Jan 24 06:55:53 (none) local0.err cgminer[31699]: ------POOL ACTIVE  FOR XNSUB------
Jan 24 06:55:53 (none) local0.info cgminer[31699]: Failed to connect to stratum on mining-dutch.nl:8888
Jan 24 06:55:54 (none) local0.info cgminer[31699]: BA1 1: invalid nonce - HW error
Jan 24 06:55:54 (none) local0.warn cgminer[31699]: 1: chip 20: invalid nonce 0x14e33402
Jan 24 06:55:57 (none) local0.info cgminer[31699]: BA1 3: invalid nonce - HW error
Jan 24 06:55:57 (none) local0.warn cgminer[31699]: 3: chip 51: invalid nonce 0xadeb9602
Jan 24 06:55:58 (none) local0.info cgminer[31699]: Testing pool stratum+tcp://litecoinpool.org:3333
Jan 24 06:55:58 (none) local0.info cgminer[31699]: Testing pool stratum+tcp://scrypt.eu.nicehash.com:3333#xnsub
Jan 24 06:55:58 (none) local0.info cgminer[31699]: Testing pool stratum+tcp://mining-dutch.nl:8888#xnsub
Jan 24 06:55:58 (none) local0.err cgminer[31699]: ------POOL ACTIVE  FOR XNSUB------
Jan 24 06:55:58 (none) local0.info cgminer[31699]: Failed to connect to stratum on mining-dutch.nl:8888
Jan 24 06:55:59 (none) local0.err cgminer[31699]: A1_scanwork n cid 1:arv:34.00, lest:19.33, hest:521 witt
Jan 24 06:56:00 (none) local0.info cgminer[31699]: BA1 3: invalid nonce - HW error
Jan 24 06:56:00 (none) local0.warn cgminer[31699]: 3: chip 47: invalid nonce 0x21a7ff02
Jan 24 06:56:01 (none) local0.info cgminer[31699]: Submitting share 8c67227c to pool 0
Jan 24 06:56:01 (none) local0.info cgminer[31699]: YEAH: 2: chip 21 / job_id 1: nonce 0x40da1603
Jan 24 06:56:01 (none) local0.info cgminer[31699]: Accepted 8c67227c Diff 119K/65536 BA1 2 pool 0
Jan 24 06:56:01 (none) local0.info cgminer[31699]: BA1 3: invalid nonce - HW error
Jan 24 06:56:01 (none) local0.warn cgminer[31699]: 3: chip 51: invalid nonce 0x80f02903
Jan 24 06:56:02 (none) local0.err cgminer[31699]: A1_scanwork n cid 3:arv:34.00, lest:21.33, hest:525 witt
Jan 24 06:56:02 (none) local0.info cgminer[31699]: BA1 3: invalid nonce - HW error
Jan 24 06:56:02 (none) local0.warn cgminer[31699]: 3: chip 48: invalid nonce 0xad9c3b03
Jan 24 06:56:02 (none) local0.info cgminer[31699]: -----------BA1 1: Share above target-------------
Jan 24 06:56:02 (none) local0.info cgminer[31699]: YEAH: 1: chip 25 / job_id 1: nonce 0xb47f3f03
Jan 24 06:56:02 (none) local0.info cgminer[31699]: BA1 1: invalid nonce - HW error
Jan 24 06:56:02 (none) local0.warn cgminer[31699]: 1: chip 42: invalid nonce 0x02b64d03
Jan 24 06:56:02 (none) local0.err cgminer[31699]: A1_scanwork n cid 2:arv:33.33, lest:21.33, hest:522 witt
Jan 24 06:56:02 (none) local0.info cgminer[31699]: YEAH: 2: chip 5 / job_id 1: nonce 0xfba74103
Jan 24 06:56:02 (none) local0.info cgminer[31699]: Submitting share b3e775a8 to pool 0
Jan 24 06:56:02 (none) local0.err cgminer[31699]: A1_scanwork n cid 0:arv:34.00, lest:16.67, hest:521 witt
Jan 24 06:56:02 (none) local0.info cgminer[31699]: Submitting share 80275c1c to pool 0
Jan 24 06:56:02 (none) local0.info cgminer[31699]: YEAH: 0: chip 22 / job_id 1: nonce 0x9a284903
Jan 24 06:56:02 (none) local0.info cgminer[31699]: Accepted b3e775a8 Diff 93.3K/65536 BA1 2 pool 0
Jan 24 06:56:02 (none) local0.info cgminer[31699]: Accepted 80275c1c Diff 131K/65536 BA1 0 pool 0
Jan 24 06:56:03 (none) local0.info cgminer[31699]: Testing pool stratum+tcp://litecoinpool.org:3333
Jan 24 06:56:03 (none) local0.info cgminer[31699]: Testing pool stratum+tcp://scrypt.eu.nicehash.com:3333#xnsub
Jan 24 06:56:03 (none) local0.info cgminer[31699]: -----------BA1 1: Share above target-------------
Jan 24 06:56:03 (none) local0.info cgminer[31699]: YEAH: 1: chip 37 / job_id 1: nonce 0xf1255f03
Jan 24 06:56:03 (none) local0.info cgminer[31699]: Testing pool stratum+tcp://mining-dutch.nl:8888#xnsub
Jan 24 06:56:03 (none) local0.err cgminer[31699]: ------POOL ACTIVE  FOR XNSUB------
Jan 24 06:56:03 (none) local0.info cgminer[31699]: Failed to connect to stratum on mining-dutch.nl:8888
Jan 24 06:56:05 (none) local0.info cgminer[31699]: BA1 3: invalid nonce - HW error
Jan 24 06:56:05 (none) local0.warn cgminer[31699]: 3: chip 48: invalid nonce 0x4eea9603
Jan 24 06:56:05 (none) local0.info cgminer[31699]: BA1 1: invalid nonce - HW error
Jan 24 06:56:05 (none) local0.warn cgminer[31699]: 1: chip 42: invalid nonce 0xb8f5ae03
Jan 24 06:56:06 (none) local0.info cgminer[31699]: Submitting share 7eae6e08 to pool 0
Jan 24 06:56:06 (none) local0.info cgminer[31699]: YEAH: 3: chip 35 / job_id 1: nonce 0x514ebd03
Jan 24 06:56:06 (none) local0.info cgminer[31699]: Accepted 7eae6e08 Diff 132K/65536 BA1 3 pool 0
Jan 24 06:56:08 (none) local0.info cgminer[31699]: Testing pool stratum+tcp://litecoinpool.org:3333
Jan 24 06:56:08 (none) local0.info cgminer[31699]: Testing pool stratum+tcp://scrypt.eu.nicehash.com:3333#xnsub
Jan 24 06:56:08 (none) local0.info cgminer[31699]: Testing pool stratum+tcp://mining-dutch.nl:8888#xnsub
Jan 24 06:56:08 (none) local0.err cgminer[31699]: ------POOL ACTIVE  FOR XNSUB------
Jan 24 06:56:08 (none) local0.info cgminer[31699]: Failed to connect to stratum on mining-dutch.nl:8888
Jan 24 06:56:10 (none) local0.err cgminer[31699]: A1_scanwork n cid 1:arv:34.00, lest:19.33, hest:521 witt
Jan 24 06:56:10 (none) local0.info cgminer[31699]: -----------BA1 1: Share above target-------------
Jan 24 06:56:10 (none) local0.info cgminer[31699]: YEAH: 1: chip 37 / job_id 1: nonce 0x81ce4404
Jan 24 06:56:11 (none) local0.info cgminer[31699]: BA1 1: invalid nonce - HW error
Jan 24 06:56:11 (none) local0.warn cgminer[31699]: 1: chip 7: invalid nonce 0x193f6704
Jan 24 06:56:12 (none) local0.info cgminer[31699]: Submitting share 0caedf19 to pool 0
Jan 24 06:56:12 (none) local0.info cgminer[31699]: YEAH: 3: chip 25 / job_id 1: nonce 0x45488a04
Jan 24 06:56:12 (none) local0.info cgminer[31699]: Accepted 0caedf19 Diff 1.32M/65536 BA1 3 pool 0
Jan 24 06:56:12 (none) local0.err cgminer[31699]: A1_scanwork n cid 3:arv:34.00, lest:21.33, hest:525 witt
Jan 24 06:56:12 (none) local0.info cgminer[31699]: BA1 3: invalid nonce - HW error
Jan 24 06:56:12 (none) local0.warn cgminer[31699]: 3: chip 51: invalid nonce 0xe3988f04
Jan 24 06:56:12 (none) local0.info cgminer[31699]: start to check disable chips
Jan 24 06:56:13 (none) local0.info cgminer[31699]: Submitting share 2df50a63 to pool 0
Jan 24 06:56:13 (none) local0.info cgminer[31699]: YEAH: 3: chip 2 / job_id 1: nonce 0x4281ac04
Jan 24 06:56:13 (none) local0.info cgminer[31699]: Accepted 2df50a63 Diff 365K/65536 BA1 3 pool 0
Jan 24 06:56:13 (none) local0.info cgminer[31699]: Testing pool stratum+tcp://litecoinpool.org:3333
Jan 24 06:56:13 (none) local0.info cgminer[31699]: Testing pool stratum+tcp://scrypt.eu.nicehash.com:3333#xnsub
Jan 24 06:56:13 (none) local0.err cgminer[31699]: A1_scanwork n cid 0:arv:34.00, lest:16.67, hest:521 witt
Jan 24 06:56:13 (none) local0.err cgminer[31699]: A1_scanwork n cid 2:arv:33.33, lest:21.33, hest:522 witt
Jan 24 06:56:13 (none) local0.info cgminer[31699]: Testing pool stratum+tcp://mining-dutch.nl:8888#xnsub
Jan 24 06:56:13 (none) local0.err cgminer[31699]: ------POOL ACTIVE  FOR XNSUB------
Jan 24 06:56:13 (none) local0.info cgminer[31699]: Failed to connect to stratum on mining-dutch.nl:8888
Jan 24 06:56:17 (none) local0.info cgminer[31699]: BA1 1: invalid nonce - HW error
Jan 24 06:56:17 (none) local0.warn cgminer[31699]: 1: chip 28: invalid nonce 0x23153205
Jan 24 06:56:17 (none) local0.info cgminer[31699]: -----------BA1 1: Share above target-------------
Jan 24 06:56:17 (none) local0.info cgminer[31699]: YEAH: 1: chip 25 / job_id 1: nonce 0x93aa3505
Jan 24 06:56:18 (none) local0.info cgminer[31699]: Testing pool stratum+tcp://litecoinpool.org:3333
Jan 24 06:56:18 (none) local0.info cgminer[31699]: Testing pool stratum+tcp://scrypt.eu.nicehash.com:3333#xnsub
Jan 24 06:56:18 (none) local0.info cgminer[31699]: Testing pool stratum+tcp://mining-dutch.nl:8888#xnsub
Jan 24 06:56:18 (none) local0.err cgminer[31699]: ------POOL ACTIVE  FOR XNSUB------
Jan 24 06:56:18 (none) local0.info cgminer[31699]: BA1 0: invalid nonce - HW error
Jan 24 06:56:18 (none) local0.warn cgminer[31699]: 0: chip 48: invalid nonce 0x7e4f6c05
Jan 24 06:56:18 (none) local0.info cgminer[31699]: Failed to connect to stratum on mining-dutch.nl:8888
Jan 24 06:56:19 (none) local0.info cgminer[31699]: YEAH: 0: chip 20 / job_id 1: nonce 0x34007805
Jan 24 06:56:19 (none) local0.info cgminer[31699]: Submitting share c667ecfc to pool 0
Jan 24 06:56:19 (none) local0.info cgminer[31699]: Accepted c667ecfc Diff 84.6K/65536 BA1 0 pool 0
Jan 24 06:56:19 (none) local0.info cgminer[31699]: BA1 3: invalid nonce - HW error
Jan 24 06:56:19 (none) local0.warn cgminer[31699]: 3: chip 25: invalid nonce 0x2f208805
Jan 24 06:56:20 (none) local0.err cgminer[31699]: A1_scanwork n cid 1:arv:34.00, lest:19.33, hest:521 witt
Jan 24 06:56:20 (none) local0.info cgminer[31699]: -----------BA1 1: Share above target-------------
Jan 24 06:56:20 (none) local0.info cgminer[31699]: YEAH: 1: chip 37 / job_id 1: nonce 0xf2cba805
Jan 24 06:56:20 (none) local0.info cgminer[31699]: start to check disable chips
Jan 24 06:56:22 (none) local0.info cgminer[31699]: -----------BA1 1: Share above target-------------
Jan 24 06:56:22 (none) local0.info cgminer[31699]: YEAH: 1: chip 25 / job_id 1: nonce 0x40e3da05
Jan 24 06:56:23 (none) local0.err cgminer[31699]: A1_scanwork n cid 3:arv:34.00, lest:21.33, hest:525 witt
Jan 24 06:56:23 (none) local0.info cgminer[31699]: Testing pool stratum+tcp://litecoinpool.org:3333
Jan 24 06:56:23 (none) local0.info cgminer[31699]: Testing pool stratum+tcp://scrypt.eu.nicehash.com:3333#xnsub
Jan 24 06:56:23 (none) local0.err cgminer[31699]: A1_scanwork n cid 0:arv:34.00, lest:16.67, hest:521 witt
Jan 24 06:56:23 (none) local0.info cgminer[31699]: start to check disable chips
Jan 24 06:56:23 (none) local0.err cgminer[31699]: A1_scanwork n cid 2:arv:33.33, lest:21.33, hest:522 witt
Jan 24 06:56:23 (none) local0.info cgminer[31699]: start to check disable chips
Jan 24 06:56:23 (none) local0.info cgminer[31699]: Testing pool stratum+tcp://mining-dutch.nl:8888#xnsub
Jan 24 06:56:23 (none) local0.err cgminer[31699]: ------POOL ACTIVE  FOR XNSUB------
Jan 24 06:56:24 (none) local0.info cgminer[31699]: Failed to connect to stratum on mining-dutch.nl:8888
Jan 24 06:56:24 (none) local0.info cgminer[31699]: BA1 3: invalid nonce - HW error
Jan 24 06:56:24 (none) local0.warn cgminer[31699]: 3: chip 44: invalid nonce 0xc7862300
Jan 24 06:56:24 (none) local0.info cgminer[31699]: YEAH: 0: chip 36 / job_id 2: nonce 0xcc952a00
Jan 24 06:56:24 (none) local0.info cgminer[31699]: Submitting share 6a906432 to pool 0
Jan 24 06:56:24 (none) local0.info cgminer[31699]: Accepted 6a906432 Diff 157K/65536 BA1 0 pool 0
Jan 24 06:56:25 (none) local0.info cgminer[31699]: BA1 0: invalid nonce - HW error
Jan 24 06:56:25 (none) local0.warn cgminer[31699]: 0: chip 42: invalid nonce 0xc0884b00
Jan 24 06:56:25 (none) local0.info cgminer[31699]: BA1 0: invalid nonce - HW error
Jan 24 06:56:25 (none) local0.warn cgminer[31699]: 0: chip 42: invalid nonce 0x74094e00
Jan 24 06:56:26 (none) local0.info cgminer[31699]: BA1 3: invalid nonce - HW error
Jan 24 06:56:26 (none) local0.warn cgminer[31699]: 3: chip 47: invalid nonce 0x24ba6700
Jan 24 06:56:26 (none) local0.info cgminer[31699]: Submitting share d006b9da to pool 0
Jan 24 06:56:26 (none) local0.info cgminer[31699]: YEAH: 0: chip 17 / job_id 2: nonce 0x6c636c00
Jan 24 06:56:26 (none) local0.info cgminer[31699]: Accepted d006b9da Diff 80.6K/65536 BA1 0 pool 0
Jan 24 06:56:26 (none) local0.info cgminer[31699]: BA1 3: invalid nonce - HW error
Jan 24 06:56:26 (none) local0.warn cgminer[31699]: 3: chip 47: invalid nonce 0xf9267600
Jan 24 06:56:27 (none) local0.info cgminer[31699]: Submitting share 91f7741e to pool 0
Jan 24 06:56:27 (none) local0.info cgminer[31699]: YEAH: 2: chip 58 / job_id 2: nonce 0x31a18300
Jan 24 06:56:27 (none) local0.info cgminer[31699]: Accepted 91f7741e Diff 115K/65536 BA1 2 pool 0
Jan 24 06:56:28 (none) local0.info cgminer[31699]: Testing pool stratum+tcp://litecoinpool.org:3333
Jan 24 06:56:28 (none) local0.info cgminer[31699]: Testing pool stratum+tcp://scrypt.eu.nicehash.com:3333#xnsub
Jan 24 06:56:28 (none) local0.info cgminer[31699]: BA1 1: invalid nonce - HW error
Jan 24 06:56:28 (none) local0.warn cgminer[31699]: 1: chip 16: invalid nonce 0x6031b100
Jan 24 06:56:29 (none) local0.info cgminer[31699]: Testing pool stratum+tcp://mining-dutch.nl:8888#xnsub
Jan 24 06:56:29 (none) local0.err cgminer[31699]: ------POOL ACTIVE  FOR XNSUB------
Jan 24 06:56:29 (none) local0.info cgminer[31699]: Failed to connect to stratum on mining-dutch.nl:8888
Jan 24 06:56:29 (none) local0.info cgminer[31699]: BA1 1: invalid nonce - HW error
Jan 24 06:56:29 (none) local0.warn cgminer[31699]: 1: chip 61: invalid nonce 0xf798dd00
Jan 24 06:56:29 (none) local0.info cgminer[31699]: BA1 3: invalid nonce - HW error
Jan 24 06:56:29 (none) local0.warn cgminer[31699]: 3: chip 51: invalid nonce 0x0ddbe200
Jan 24 06:56:31 (none) local0.err cgminer[31699]: A1_scanwork n cid 1:arv:34.00, lest:19.33, hest:521 witt
Jan 24 06:56:31 (none) local0.info cgminer[31699]: BA1 3: invalid nonce - HW error
Jan 24 06:56:31 (none) local0.warn cgminer[31699]: 3: chip 21: invalid nonce 0x1f111701
Jan 24 06:56:31 (none) local0.info cgminer[31699]: BA1 1: invalid nonce - HW error
Jan 24 06:56:31 (none) local0.warn cgminer[31699]: 1: chip 60: invalid nonce 0xe8161e01
Jan 24 06:56:32 (none) local0.info cgminer[31699]: BA1 0: invalid nonce - HW error
Jan 24 06:56:32 (none) local0.warn cgminer[31699]: 0: chip 42: invalid nonce 0x07412701
Jan 24 06:56:32 (none) local0.info cgminer[31699]: BA1 1: invalid nonce - HW error
Jan 24 06:56:32 (none) local0.warn cgminer[31699]: 1: chip 23: invalid nonce 0x5eda3501
Jan 24 06:56:32 (none) local0.info cgminer[31699]: recieve notify,we must flush work
Jan 24 06:56:32 (none) local0.info cgminer[31699]: Work update message received
Jan 24 06:56:32 (none) local0.info cgminer[31699]: BA1 1: invalid nonce - HW error
Jan 24 06:56:32 (none) local0.warn cgminer[31699]: 1: chip 54: invalid nonce 0x97014001
Jan 24 06:56:33 (none) local0.info cgminer[31699]: Submitting share a1b9696d to pool 0
Jan 24 06:56:33 (none) local0.info cgminer[31699]: YEAH: 2: chip 4 / job_id 1: nonce 0x13030500
Jan 24 06:56:33 (none) local0.info cgminer[31699]: Accepted a1b9696d Diff 104K/65536 BA1 2 pool 0
Jan 24 06:56:33 (none) local0.info cgminer[31699]: Testing pool stratum+tcp://litecoinpool.org:3333
Jan 24 06:56:33 (none) local0.info cgminer[31699]: Testing pool stratum+tcp://scrypt.eu.nicehash.com:3333#xnsub
Jan 24 06:56:33 (none) local0.err cgminer[31699]: A1_scanwork n cid 3:arv:34.00, lest:21.33, hest:525 witt
Jan 24 06:56:33 (none) local0.info cgminer[31699]: BA1 1: invalid nonce - HW error
Jan 24 06:56:33 (none) local0.warn cgminer[31699]: 1: chip 54: invalid nonce 0xff241800
Jan 24 06:56:33 (none) local0.info cgminer[31699]: BA1 1: invalid nonce - HW error
Jan 24 06:56:33 (none) local0.warn cgminer[31699]: 1: chip 11: invalid nonce 0xb2d31c00
Jan 24 06:56:34 (none) local0.info cgminer[31699]: Testing pool stratum+tcp://mining-dutch.nl:8888#xnsub
Jan 24 06:56:34 (none) local0.err cgminer[31699]: ------POOL ACTIVE  FOR XNSUB------
Jan 24 06:56:34 (none) local0.err cgminer[31699]: A1_scanwork n cid 0:arv:34.00, lest:16.67, hest:521 witt
Jan 24 06:56:34 (none) local0.err cgminer[31699]: A1_scanwork n cid 2:arv:33.33, lest:21.33, hest:522 witt
Jan 24 06:56:34 (none) local0.info cgminer[31699]: Failed to connect to stratum on mining-dutch.nl:8888
Jan 24 06:56:34 (none) local0.info cgminer[31699]: Submitting share 32487a87 to pool 0
Jan 24 06:56:34 (none) local0.info cgminer[31699]: YEAH: 0: chip 55 / job_id 1: nonce 0x533f3700
Jan 24 06:56:34 (none) local0.info cgminer[31699]: Accepted 32487a87 Diff 334K/65536 BA1 0 pool 0
Jan 24 06:56:35 (none) local0.info cgminer[31699]: BA1 1: invalid nonce - HW error
Jan 24 06:56:35 (none) local0.warn cgminer[31699]: 1: chip 54: invalid nonce 0x60775200
Jan 24 06:56:36 (none) local0.info cgminer[31699]: Submitting share d88cd886 to pool 0
Jan 24 06:56:36 (none) local0.info cgminer[31699]: YEAH: 0: chip 26 / job_id 1: nonce 0x446b6b00
Jan 24 06:56:36 (none) local0.info cgminer[31699]: Accepted d88cd886 Diff 77.5K/65536 BA1 0 pool 0
Jan 24 06:56:36 (none) local0.info cgminer[31699]: recieve notify,we must flush work
Jan 24 06:56:36 (none) local0.info cgminer[31699]: Work update message received
Jan 24 06:56:36 (none) local0.info cgminer[31699]: BA1 1: invalid nonce - HW error
Jan 24 06:56:36 (none) local0.warn cgminer[31699]: 1: chip 55: invalid nonce 0x6a450a00
Jan 24 06:56:37 (none) local0.info cgminer[31699]: BA1 1: invalid nonce - HW error
Jan 24 06:56:37 (none) local0.warn cgminer[31699]: 1: chip 50: invalid nonce 0xf1c40b00
Jan 24 06:56:38 (none) local0.info cgminer[31699]: Testing pool stratum+tcp://litecoinpool.org:3333
Jan 24 06:56:38 (none) local0.info cgminer[31699]: Testing pool stratum+tcp://scrypt.eu.nicehash.com:3333#xnsub
Jan 24 06:56:39 (none) local0.info cgminer[31699]: Testing pool stratum+tcp://mining-dutch.nl:8888#xnsub
Jan 24 06:56:39 (none) local0.err cgminer[31699]: ------POOL ACTIVE  FOR XNSUB------
Jan 24 06:56:39 (none) local0.info cgminer[31699]: Failed to connect to stratum on mining-dutch.nl:8888
Jan 24 06:56:39 (none) local0.info cgminer[31699]: YEAH: 0: chip 2 / job_id 1: nonce 0xa2a66a00
Jan 24 06:56:39 (none) local0.info cgminer[31699]: Submitting share da283a72 to pool 0
Jan 24 06:56:39 (none) local0.info cgminer[31699]: Accepted da283a72 Diff 76.9K/65536 BA1 0 pool 0
Jan 24 06:56:41 (none) local0.info cgminer[31699]: BA1 3: invalid nonce - HW error
Jan 24 06:56:41 (none) local0.warn cgminer[31699]: 3: chip 51: invalid nonce 0x0e08a300
Jan 24 06:56:41 (none) local0.err cgminer[31699]: A1_scanwork n cid 1:arv:34.00, lest:19.33, hest:521 witt
Jan 24 06:56:41 (none) local0.info cgminer[31699]: BA1 1: invalid nonce - HW error
Jan 24 06:56:41 (none) local0.warn cgminer[31699]: 1: chip 60: invalid nonce 0x99fc9d00
Jan 24 06:56:42 (none) local0.info cgminer[31699]: recieve notify,we must flush work
Jan 24 06:56:42 (none) local0.info cgminer[31699]: Work update message received
Jan 24 06:56:43 (none) local0.info cgminer[31699]: Testing pool stratum+tcp://litecoinpool.org:3333
Jan 24 06:56:43 (none) local0.info cgminer[31699]: Testing pool stratum+tcp://scrypt.eu.nicehash.com:3333#xnsub
Jan 24 06:56:44 (none) local0.err cgminer[31699]: A1_scanwork n cid 3:arv:34.00, lest:21.33, hest:525 witt
Jan 24 06:56:44 (none) local0.info cgminer[31699]: Testing pool stratum+tcp://mining-dutch.nl:8888#xnsub
Jan 24 06:56:44 (none) local0.err cgminer[31699]: ------POOL ACTIVE  FOR XNSUB------
Jan 24 06:56:44 (none) local0.info cgminer[31699]: Failed to connect to stratum on mining-dutch.nl:8888
Jan 24 06:56:44 (none) local0.err cgminer[31699]: A1_scanwork n cid 2:arv:33.33, lest:21.33, hest:522 witt
Jan 24 06:56:44 (none) local0.err cgminer[31699]: A1_scanwork n cid 0:arv:34.00, lest:16.67, hest:521 witt
Jan 24 06:56:47 (none) local0.info cgminer[31699]: -----------BA1 1: Share above target-------------
Jan 24 06:56:47 (none) local0.info cgminer[31699]: YEAH: 1: chip 20 / job_id 1: nonce 0x4e3bb500
Jan 24 06:56:48 (none) local0.info cgminer[31699]: Testing pool stratum+tcp://litecoinpool.org:3333
Jan 24 06:56:48 (none) local0.info cgminer[31699]: Testing pool stratum+tcp://scrypt.eu.nicehash.com:3333#xnsub
Jan 24 06:56:48 (none) local0.info cgminer[31699]: BA1 1: invalid nonce - HW error
Jan 24 06:56:48 (none) local0.warn cgminer[31699]: 1: chip 61: invalid nonce 0xcba8ca00
Jan 24 06:56:49 (none) local0.info cgminer[31699]: Testing pool stratum+tcp://mining-dutch.nl:8888#xnsub
Jan 24 06:56:49 (none) local0.err cgminer[31699]: ------POOL ACTIVE  FOR XNSUB------
Jan 24 06:56:49 (none) local0.info cgminer[31699]: Failed to connect to stratum on mining-dutch.nl:8888
Jan 24 06:56:52 (none) local0.err cgminer[31699]: A1_scanwork n cid 1:arv:34.00, lest:19.33, hest:521 witt
Jan 24 06:56:53 (none) local0.info cgminer[31699]: Testing pool stratum+tcp://litecoinpool.org:3333
Jan 24 06:56:53 (none) local0.info cgminer[31699]: Testing pool stratum+tcp://scrypt.eu.nicehash.com:3333#xnsub
Jan 24 06:56:54 (none) local0.info cgminer[31699]: -----------BA1 1: Share above target-------------
Jan 24 06:56:54 (none) local0.info cgminer[31699]: YEAH: 1: chip 20 / job_id 1: nonce 0xcb968701
Jan 24 06:56:54 (none) local0.info cgminer[31699]: Testing pool stratum+tcp://mining-dutch.nl:8888#xnsub
Jan 24 06:56:54 (none) local0.err cgminer[31699]: ------POOL ACTIVE  FOR XNSUB------
Jan 24 06:56:54 (none) local0.err cgminer[31699]: A1_scanwork n cid 3:arv:34.00, lest:20.67, hest:525 witt
Jan 24 06:56:54 (none) local0.info cgminer[31699]: Failed to connect to stratum on mining-dutch.nl:8888
Jan 24 06:56:54 (none) local0.err cgminer[31699]: A1_scanwork n cid 2:arv:33.33, lest:21.33, hest:522 witt
Jan 24 06:56:55 (none) local0.err cgminer[31699]: A1_scanwork n cid 0:arv:34.00, lest:16.67, hest:521 witt
Jan 24 06:56:55 (none) local0.info cgminer[31699]: BA1 0: invalid nonce - HW error
Jan 24 06:56:55 (none) local0.warn cgminer[31699]: 0: chip 54: invalid nonce 0x5ff3b801
Jan 24 06:56:56 (none) local0.info cgminer[31699]: BA1 1: invalid nonce - HW error
Jan 24 06:56:56 (none) local0.warn cgminer[31699]: 1: chip 61: invalid nonce 0xfed0d301
Jan 24 06:56:56 (none) local0.info cgminer[31699]: BA1 1: invalid nonce - HW error
Jan 24 06:56:56 (none) local0.warn cgminer[31699]: 1: chip 35: invalid nonce 0xc698e501
Jan 24 06:56:58 (none) local0.info cgminer[31699]: Testing pool stratum+tcp://litecoinpool.org:3333
Jan 24 06:56:58 (none) local0.info cgminer[31699]: Testing pool stratum+tcp://scrypt.eu.nicehash.com:3333#xnsub
Jan 24 06:56:58 (none) local0.info cgminer[31699]: YEAH: 0: chip 72 / job_id 1: nonce 0x7d952802
Jan 24 06:56:58 (none) local0.info cgminer[31699]: Submitting share 2a846b23 to pool 0
Jan 24 06:56:58 (none) local0.info cgminer[31699]: Accepted 2a846b23 Diff 395K/65536 BA1 0 pool 0
Jan 24 06:56:59 (none) local0.info cgminer[31699]: Testing pool stratum+tcp://mining-dutch.nl:8888#xnsub
Jan 24 06:56:59 (none) local0.err cgminer[31699]: ------POOL ACTIVE  FOR XNSUB------
Jan 24 06:56:59 (none) local0.info cgminer[31699]: Failed to connect to stratum on mining-dutch.nl:8888
Jan 24 06:57:00 (none) local0.info cgminer[31699]: BA1 1: invalid nonce - HW error
Jan 24 06:57:00 (none) local0.warn cgminer[31699]: 1: chip 11: invalid nonce 0xede56202
Jan 24 06:57:02 (none) local0.err cgminer[31699]: A1_scanwork n cid 1:arv:34.00, lest:19.33, hest:521 witt
Jan 24 06:57:02 (none) local0.info cgminer[31699]: BA1 3: invalid nonce - HW error
Jan 24 06:57:02 (none) local0.warn cgminer[31699]: 3: chip 15: invalid nonce 0x55a0af02
Jan 24 06:57:03 (none) local0.info cgminer[31699]: Testing pool stratum+tcp://litecoinpool.org:3333
Jan 24 06:57:03 (none) local0.info cgminer[31699]: Testing pool stratum+tcp://scrypt.eu.nicehash.com:3333#xnsub
Jan 24 06:57:04 (none) local0.info cgminer[31699]: Testing pool stratum+tcp://mining-dutch.nl:8888#xnsub
Jan 24 06:57:04 (none) local0.err cgminer[31699]: ------POOL ACTIVE  FOR XNSUB------
Jan 24 06:57:04 (none) local0.info cgminer[31699]: Failed to connect to stratum on mining-dutch.nl:8888
Jan 24 06:57:04 (none) local0.info cgminer[31699]: BA1 1: invalid nonce - HW error
Jan 24 06:57:04 (none) local0.warn cgminer[31699]: 1: chip 16: invalid nonce 0x033cf202
Jan 24 06:57:04 (none) local0.err cgminer[31699]: A1_scanwork n cid 3:arv:34.00, lest:20.67, hest:525 witt
Jan 24 06:57:05 (none) auth.info login[23160]: root login on 'pts/0'
Jan 24 06:57:05 (none) local0.err cgminer[31699]: A1_scanwork n cid 2:arv:33.33, lest:21.33, hest:522 witt
Jan 24 06:57:05 (none) local0.err cgminer[31699]: A1_scanwork n cid 0:arv:34.00, lest:16.67, hest:521 witt
Jan 24 06:57:08 (none) local0.info cgminer[31699]: Testing pool stratum+tcp://litecoinpool.org:3333
Jan 24 06:57:08 (none) local0.info cgminer[31699]: Testing pool stratum+tcp://scrypt.eu.nicehash.com:3333#xnsub
Jan 24 06:57:09 (none) local0.info cgminer[31699]: Testing pool stratum+tcp://mining-dutch.nl:8888#xnsub
Jan 24 06:57:09 (none) local0.err cgminer[31699]: ------POOL ACTIVE  FOR XNSUB------
Jan 24 06:57:09 (none) local0.info cgminer[31699]: Failed to connect to stratum on mining-dutch.nl:8888
Jan 24 06:57:10 (none) local0.info cgminer[31699]: BA1 3: invalid nonce - HW error
Jan 24 06:57:10 (none) local0.warn cgminer[31699]: 3: chip 25: invalid nonce 0x9254c403
Jan 24 06:57:12 (none) local0.info cgminer[31699]: BA1 1: invalid nonce - HW error
Jan 24 06:57:12 (none) local0.warn cgminer[31699]: 1: chip 39: invalid nonce 0xcc96f303
Jan 24 06:57:12 (none) local0.info cgminer[31699]: BA1 3: invalid nonce - HW error
Jan 24 06:57:12 (none) local0.warn cgminer[31699]: 3: chip 41: invalid nonce 0x5b60f203
Jan 24 06:57:12 (none) local0.err cgminer[31699]: A1_scanwork n cid 1:arv:34.00, lest:19.33, hest:521 witt
Jan 24 06:57:13 (none) local0.info cgminer[31699]: Testing pool stratum+tcp://litecoinpool.org:3333
Jan 24 06:57:13 (none) local0.info cgminer[31699]: Testing pool stratum+tcp://scrypt.eu.nicehash.com:3333#xnsub
Jan 24 06:57:14 (none) local0.info cgminer[31699]: Testing pool stratum+tcp://mining-dutch.nl:8888#xnsub
Jan 24 06:57:14 (none) local0.err cgminer[31699]: ------POOL ACTIVE  FOR XNSUB------
Jan 24 06:57:14 (none) local0.info cgminer[31699]: Failed to connect to stratum on mining-dutch.nl:8888
Jan 24 06:57:15 (none) local0.err cgminer[31699]: A1_scanwork n cid 3:arv:34.00, lest:20.67, hest:525 witt
Jan 24 06:57:16 (none) local0.err cgminer[31699]: A1_scanwork n cid 2:arv:33.33, lest:21.33, hest:522 witt
Jan 24 06:57:16 (none) local0.err cgminer[31699]: A1_scanwork n cid 0:arv:34.00, lest:16.67, hest:521 witt
tell me, it's all in the logs so many invalid nonce hw or just me?


Title: Re: Innosilicon A4+ setup tutorial
Post by: mullick on January 24, 2018, 08:03:25 AM
Anyone had a controller go bad?

Went out to the mine one day after a a4+ showed offline. Strong smell of electrical fire in the mine. Traced it back to the offline a4+

First few boot attempts the smell was VERY strong. My clothes even smelled like it after returning home. Miner starts to boot. Lights on all 4 boards go off and the fault light flashes. Miner never requests an ip address. Will not boot with any boards attached. After a few attempts the smell went away.

Yesterday during troubleshooting it randomly decided to assign itself an ip address outside of my subnet (10.58.133.0/24 when my subnet is 192.168.1.0/24). Grabbed an old router and configured it to that subnet and no luck. It wouldn't even request or assign itself an ip this time.

Innosilicon keeps telling to to update the firmware via the management console. Despite my repeated emails telling them I cannot access it.

Holy shit.  :o

Innosilicon is one big joke. I must've have extremely good luck with Inno-lottery but this kind of shit keeps coming up. :P

Sounds like some component(s) have released their magic smoke (and even by 2018 there's no cure for that :P). It could be something simple like a resistor or capacitor blown up since you had some luck at somehow get it to "work" for a while. Though this is something you should never be worried about. This is unbeliveable.
I would personally try to fix the board or source a new one rather than deal with Innosilicon with their superior guarantee etc.

Nevertheless, I wouldn't try to boot the thing up again until the problem is located and fixed. It could do a lot more harm than what you already have. :(



In their defense they have been good at responding quickly. It's just they are having trouble understanding me.

I have avoided opening the miner to find the burned component out of fear of them voiding the warranty but I'm going to open it next visit and figure it out.


Title: Re: Innosilicon A4+ setup tutorial
Post by: ilostmyface on January 25, 2018, 12:40:38 AM
Anyone had a controller go bad?

Went out to the mine one day after a a4+ showed offline. Strong smell of electrical fire in the mine. Traced it back to the offline a4+




Out of curiosity which firmware version was it running?


Title: Re: Innosilicon A4+ setup tutorial
Post by: shepardblue on January 25, 2018, 04:01:07 AM
Bump the Frequency to 1152Mhz and Lower VID (which raises the voltage) on the Miner General Configuration page. There are instructions on that Miner General Configuration too. Read those for sure.

Try frequency 1152MHz and then try adjusting VID between 22-14. Should get faster as you approach 14, probably will get the best rate when VID is somewhere below 20. I still haven't explored what's optimal for my machines. Waiting for the warranty to expire before I mess with overclocking but I overclocked my own A4 Dominators and it worked the same way.


thx

if i do the middle one or 1152 i got so many HW and pool hashrate show me the  half hashrate than inno web shows me



Make sure you're lowering the VID, the unit needs more power at a higher frequency


Title: Re: Innosilicon A4+ setup tutorial
Post by: lam3rch3 on January 25, 2018, 04:45:04 PM
how to increase the fan before was 70% now is 40?


Title: Re: Innosilicon A4+ setup tutorial
Post by: shepardblue on January 26, 2018, 10:29:44 PM
how to increase the fan before was 70% now is 40?

Why do you want to increase the speed?

It should increase in line with temperature based on my experience.


Title: Re: Innosilicon A4+ setup tutorial
Post by: Aepko on January 27, 2018, 12:31:22 AM
For anyone curious, you can turn these A4+'s into A6s. The control board has enough ports for 8 hashboards and 4 fans. I changed over 30 A4s so I only have to monitor 15 ASICs now. Way better. The inno support guy gave me an older firmware that supports it, the latest only ran 6 boards total. He said there should be a new firmware today or tomorrow that supports all 8 again.


Title: Re: Innosilicon A4+ setup tutorial
Post by: lam3rch3 on January 27, 2018, 12:08:07 PM
What are the settings you use for VID and what mh/z


Title: Re: Innosilicon A4+ setup tutorial
Post by: diaahussein on January 27, 2018, 06:39:40 PM
has anyone tried the firmware downgrade ? want to try the December to return, but I fear the brick to

i have tried it and it works OK


Title: Re: Innosilicon A4+ setup tutorial
Post by: lam3rch3 on January 28, 2018, 06:37:01 AM
how to increase the fan before was 70% now is 40?

Why do you want to increase the speed?

It should increase in line with temperature based on my experience.

because 70% liked the temperature, and I'm not a noise problem


Title: Re: Innosilicon A4+ setup tutorial
Post by: kb8679 on January 28, 2018, 10:08:50 AM
What are the settings you use for VID and what mh/z

I'm running all miners @ 1152MHz with VID 14. This combination works perfectly. Miners report 695MHs and it's very close to "real" average hashrates too (anything between 660 to over 700MHs).


Title: Re: Innosilicon A4+ setup tutorial
Post by: lam3rch3 on January 28, 2018, 12:26:37 PM
What are the settings you use for VID and what mh/z

I'm running all miners @ 1152MHz with VID 14. This combination works perfectly. Miners report 695MHs and it's very close to "real" average hashrates too (anything between 660 to over 700MHs).

and what are the temperatures


Title: Re: Innosilicon A4+ setup tutorial
Post by: kb8679 on January 28, 2018, 08:03:34 PM
What are the settings you use for VID and what mh/z

I'm running all miners @ 1152MHz with VID 14. This combination works perfectly. Miners report 695MHs and it's very close to "real" average hashrates too (anything between 660 to over 700MHs).

and what are the temperatures

  Min    Max   Avg
34.67 / 64 / 49.33

These are pretty much the averages for most of my miners. I have two units however, which have higher temps (mainly the max temp shows readings of near 80C).
Also, these are located in cold storage, so ambient temperature is very low during the winter, which helps.


Title: Re: Innosilicon A4+ setup tutorial
Post by: lam3rch3 on January 29, 2018, 09:53:21 AM
What are the settings you use for VID and what mh/z

I'm running all miners @ 1152MHz with VID 14. This combination works perfectly. Miners report 695MHs and it's very close to "real" average hashrates too (anything between 660 to over 700MHs).

and what are the temperatures

  Min    Max   Avg
34.67 / 64 / 49.33

These are pretty much the averages for most of my miners. I have two units however, which have higher temps (mainly the max temp shows readings of near 80C).
Also, these are located in cold storage, so ambient temperature is very low during the winter, which helps.



Thank you for the information


Title: Re: Innosilicon A4+ setup tutorial
Post by: miner1217 on January 29, 2018, 02:37:09 PM
Hi,
Can anyone share original unmodified version of inno_config.py ?
I messed up mine and backup seems corrupted and unreadable somehow.

Thanks in advance


Title: Re: Innosilicon A4+ setup tutorial
Post by: Aepko on January 29, 2018, 08:36:35 PM
Hi,
Can anyone share original unmodified version of inno_config.py ?
I messed up mine and backup seems corrupted and unreadable somehow.

Thanks in advance

Just reflash the firmware to default settings.


Title: Re: Innosilicon A4+ setup tutorial
Post by: needed357 on January 29, 2018, 09:27:19 PM
how often or when do you restart your miner?



Title: Re: Innosilicon A4+ setup tutorial
Post by: Lark on January 29, 2018, 10:17:03 PM
At updating, by the way there was a new update_180129.bin. Who updated, what's new?


Title: Re: Innosilicon A4+ setup tutorial
Post by: lam3rch3 on January 30, 2018, 06:18:46 AM
how often or when do you restart your miner?




And I'm interested in this


Title: Re: Innosilicon A4+ setup tutorial
Post by: Cosmictino on January 30, 2018, 08:44:06 AM
1: same here..  running 3x A4+ and it seems that the miners are restarting without any reason.. and the most important thing is that the miners are sometimes switching to innosilicon pool ..patched yesterday the new firmare "update_180129" and i did some test during the day. first of all the config doesn't recognize the configuration of the pool and start mining @ innosilicon pool .òó. (not OK!)
2: if the miners are running in overclock mode 1152 and auto VID, the reported hashrate to the pool goes down to 55-150 mhs ???? WTF and no matte wich pool im useing.. mining gutch , litecoinpool or other pools also .. absolutely low hashrate.
but on minerstatus the hashrate is ~ 695 mhs (tested with vardiff , d=16384, d=32xxx and higher diff above @ d=206xxx  and so on.. )

3: pls HACK that crap firmware :D


Title: Re: Innosilicon A4+ setup tutorial
Post by: Cosmictino on January 30, 2018, 08:51:53 AM
how often or when do you restart your miner?




And I'm interested in this

1- higher hashpower adjustments in conf. 1044 / 1100 / 1152)
2. autmotated fans (between 50% and 70%)
3. Autovid search
4. seaperate safefing buttons for each section in config
5.. ?


Title: Re: Innosilicon A4+ setup tutorial
Post by: lam3rch3 on January 30, 2018, 09:53:55 AM
my settings 1044 mh/z  27 VID = 640 mh/s litecoinpool.org

Settings 1152 and 14 VID =300 mh/s litecoinpool.org WTF?  ???


Title: Re: Innosilicon A4+ setup tutorial
Post by: needed357 on January 30, 2018, 11:26:49 AM
At updating, by the way there was a new update_180129.bin. Who updated, what's new?

same root pw?


Title: Re: Innosilicon A4+ setup tutorial
Post by: Lark on January 30, 2018, 12:09:56 PM
At updating, by the way there was a new update_180129.bin. Who updated, what's new?

same root pw?


I have not updated to 180129.bin), I still have update_180112.bin, so far satisfied


Title: Re: Innosilicon A4+ setup tutorial
Post by: Gazdac2 on January 30, 2018, 11:15:48 PM
Interesting.

I complained a lot about having no way to flash a TF card. Today breaking down the boxes I received last month there was ONE tiny tf card reader in the bottom of one of the boxes
Flat little bubble package the size of a matchbook was included in my order. I guess if I have a catastrophic failure maybe I can fix it.
It was 2 seconds away from being thrown out.

I'm guessing some of you others received one, but never mentioned it :)


Title: Re: Innosilicon A4+ setup tutorial
Post by: AGlab on January 31, 2018, 07:40:22 AM
Hi all
I  have some problem with a5 after reboot.
Symptoms were the HTTP control page loading, but not showing any data e.g. not showing me  "miner type" under system.

Manually running each of the commands in /etc/init.d/rcS
The problem in "python3.4 /home/inno_daemon/MServer.py"

Code:
root@miner~:
python3.4 /home/inno_daemon/MServer.py
Traceback (most recent call last):
  File "/home/inno_daemon/MServer.py", line 12, in <module>
    from MParser  import *
  File "/home/inno_daemon/MParser.py", line 17, in <module>
    from inno_lib import *
  File "/home/inno_py/inno_lib.py", line 5, in <module>
    import cgi
  File "/lib/python3.4/cgi.py", line 39, in <module>
    from email.parser import FeedParser
  File "/lib/python3.4/email/parser.py", line 12, in <module>
    from email.feedparser import FeedParser, BytesFeedParser
  File "/lib/python3.4/email/feedparser.py", line 27, in <module>
    from email import message
  File "/lib/python3.4/email/message.py", line 16, in <module>
    from email import utils
  File "/lib/python3.4/email/utils.py", line 40, in <module>
    from email.charset import Charset
  File "/lib/python3.4/email/charset.py", line 14, in <module>
    import email.base64mime
  File "/lib/python3.4/email/base64mime.py", line 37, in <module>
    from base64 import b64encode
  File "<frozen importlib._bootstrap>", line 2237, in _find_and_load
  File "<frozen importlib._bootstrap>", line 2226, in _find_and_load_unlocked
  File "<frozen importlib._bootstrap>", line 1200, in _load_unlocked
  File "<frozen importlib._bootstrap>", line 1129, in _exec
  File "<frozen importlib._bootstrap>", line 1467, in exec_module
  File "<frozen importlib._bootstrap>", line 1570, in get_code
  File "<frozen importlib._bootstrap>", line 656, in _compile_bytecode
ValueError: bad marshal data (unknown type code)
Does anyone have any ideas?

Code:
mount / -o rw,remount
find -type f -name "*.pyc" –delete
find -type f -name "*.pyo" -delete
reboot


Title: Re: Innosilicon A4+ setup tutorial
Post by: Vaguas.secur on January 31, 2018, 05:19:03 PM
Hello,
Can anybody help me?
Today i have become 2 Miners!
The First work Fine, The Second have no Green Lights on The Board and on The Front is The Red led on and a Little Bit The Green led. But The Fans Not work and i become no Connection. I have pur The reset, After that The Fans work for The Time i press The reset Button.

best rgds


Title: Re: Innosilicon A4+ setup tutorial
Post by: wkhash on January 31, 2018, 09:08:58 PM
For anyone curious, you can turn these A4+'s into A6s. The control board has enough ports for 8 hashboards and 4 fans. I changed over 30 A4s so I only have to monitor 15 ASICs now. Way better. The inno support guy gave me an older firmware that supports it, the latest only ran 6 boards total. He said there should be a new firmware today or tomorrow that supports all 8 again.

Thanks, update_180129 appears to have no issues running all 8 chains.


https://i.imgur.com/9Iok6Dn.jpg


Title: Re: Innosilicon A4+ setup tutorial
Post by: needed357 on January 31, 2018, 10:23:50 PM
For anyone curious, you can turn these A4+'s into A6s. The control board has enough ports for 8 hashboards and 4 fans. I changed over 30 A4s so I only have to monitor 15 ASICs now. Way better. The inno support guy gave me an older firmware that supports it, the latest only ran 6 boards total. He said there should be a new firmware today or tomorrow that supports all 8 again.

Thanks, update_180129 appears to have no issues running all 8 chains.


https://i.imgur.com/9Iok6Dn.jpg

nice, with 2 psu one modded 6?

is that the same root pw?


Title: Re: Innosilicon A4+ setup tutorial
Post by: wkhash on February 01, 2018, 03:22:47 AM
Used a single 2400w psu to power it. Root password is the same as 22nd Dec firmware.


Title: Re: Innosilicon A4+ setup tutorial
Post by: kb8679 on February 01, 2018, 06:29:58 PM
For anyone curious, you can turn these A4+'s into A6s. The control board has enough ports for 8 hashboards and 4 fans. I changed over 30 A4s so I only have to monitor 15 ASICs now. Way better. The inno support guy gave me an older firmware that supports it, the latest only ran 6 boards total. He said there should be a new firmware today or tomorrow that supports all 8 again.

Thanks, update_180129 appears to have no issues running all 8 chains.


Just made the exact same change to 10 miners today. Appears to work just great! Along with halving the work upkeeping them, the best benefit (IMHO) is having spare controller boards now. :)
I use separate PSUs for each tube, and this has no negative impact either.


Title: Re: Innosilicon A4+ setup tutorial
Post by: solarismedic on February 02, 2018, 05:13:51 AM
For anyone curious, you can turn these A4+'s into A6s. The control board has enough ports for 8 hashboards and 4 fans. I changed over 30 A4s so I only have to monitor 15 ASICs now. Way better. The inno support guy gave me an older firmware that supports it, the latest only ran 6 boards total. He said there should be a new firmware today or tomorrow that supports all 8 again.

Thanks, update_180129 appears to have no issues running all 8 chains.


Just made the exact same change to 10 miners today. Appears to work just great! Along with halving the work upkeeping them, the best benefit (IMHO) is having spare controller boards now. :)
I use separate PSUs for each tube, and this has no negative impact either.

FYI, I did the 0129 upgrade on 10 A4+ today and it seemed to all go smoothly.  I did notice that one of my boxes was running 471 hash rate so I took a look and found that the ASC2 card was missing from the miner status/minerinfo section.  I made sure all the cables, power and data ribbon were all secured and the LED shows the board is getting power.  I upgraded the firmware (0129) twice again to no avail.  So I'm wondering what I should try next.  I cannot say with certainy if this was caused by the firmware...I have a feeling not because the 24 hashrate shows as 465 on the monitoring page (i didn't bother to look before i guess).

Any ideas on what to do next?


Title: Re: Innosilicon A4+ setup tutorial
Post by: needed357 on February 02, 2018, 08:29:05 PM
For anyone curious, you can turn these A4+'s into A6s. The control board has enough ports for 8 hashboards and 4 fans. I changed over 30 A4s so I only have to monitor 15 ASICs now. Way better. The inno support guy gave me an older firmware that supports it, the latest only ran 6 boards total. He said there should be a new firmware today or tomorrow that supports all 8 again.

Thanks, update_180129 appears to have no issues running all 8 chains.


Just made the exact same change to 10 miners today. Appears to work just great! Along with halving the work upkeeping them, the best benefit (IMHO) is having spare controller boards now. :)
I use separate PSUs for each tube, and this has no negative impact either.

FYI, I did the 0129 upgrade on 10 A4+ today and it seemed to all go smoothly.  I did notice that one of my boxes was running 471 hash rate so I took a look and found that the ASC2 card was missing from the miner status/minerinfo section.  I made sure all the cables, power and data ribbon were all secured and the LED shows the board is getting power.  I upgraded the firmware (0129) twice again to no avail.  So I'm wondering what I should try next.  I cannot say with certainy if this was caused by the firmware...I have a feeling not because the 24 hashrate shows as 465 on the monitoring page (i didn't bother to look before i guess).

Any ideas on what to do next?


omg i got this problem too :(

420mhz all other 620 ~


Title: Re: Innosilicon A4+ setup tutorial
Post by: kb8679 on February 03, 2018, 01:14:34 PM
For anyone curious, you can turn these A4+'s into A6s. The control board has enough ports for 8 hashboards and 4 fans. I changed over 30 A4s so I only have to monitor 15 ASICs now. Way better. The inno support guy gave me an older firmware that supports it, the latest only ran 6 boards total. He said there should be a new firmware today or tomorrow that supports all 8 again.

Thanks, update_180129 appears to have no issues running all 8 chains.


Just made the exact same change to 10 miners today. Appears to work just great! Along with halving the work upkeeping them, the best benefit (IMHO) is having spare controller boards now. :)
I use separate PSUs for each tube, and this has no negative impact either.

FYI, I did the 0129 upgrade on 10 A4+ today and it seemed to all go smoothly.  I did notice that one of my boxes was running 471 hash rate so I took a look and found that the ASC2 card was missing from the miner status/minerinfo section.  I made sure all the cables, power and data ribbon were all secured and the LED shows the board is getting power.  I upgraded the firmware (0129) twice again to no avail.  So I'm wondering what I should try next.  I cannot say with certainy if this was caused by the firmware...I have a feeling not because the 24 hashrate shows as 465 on the monitoring page (i didn't bother to look before i guess).

Any ideas on what to do next?


omg i got this problem too :(

420mhz all other 620 ~

Wow. Talk about bad luck. Both of your problems started with the FW upgrade, so signs point to control board issue... Have either of you tried swapping controller from one miner to another?

Also, didn't older ASIC miners use something like raspberry pi as a control unit? I for one would LOVE to ditch the innosilicon g19 board and replace it with ... pretty much anything else.

While I initially thought everything was working just great when I switched from A4+ setup to A6 arrangement, I've now realized that this current setup is not as stable as the old one. I would imagine these issues are sorted out in the future with FW upgrades but still, DAMN.


Title: Re: Innosilicon A4+ setup tutorial
Post by: amful on February 03, 2018, 04:54:20 PM
i have a problem with my a4+ after off/on
https://imgur.com/a/Zrykq


root@miner~:
innominer_T3 --debug
 [2018-02-03 17:03:21] Started sgminer 4.4.2
 [2018-02-03 17:03:21] A1 detect
 [2018-02-03 17:03:21] hardware version is G19
 [2018-02-03 17:03:21] miner type is T2
 [2018-02-03 17:03:22] chip nums:198.
 [2018-02-03 17:03:22] pwm  name:/dev/pwmgen0.0.
 [2018-02-03 17:03:22] pwm  name:/dev/pwmgen1.0.
 [2018-02-03 17:03:22] pwm  step:10.
 [2018-02-03 17:03:22] duty max: 100.
 [2018-02-03 17:03:22] targ freq:7000.
 [2018-02-03 17:03:22] freq rate:7142.
 [2018-02-03 17:03:22] max  thrd:100.00.
 [2018-02-03 17:03:22] up   thrd:55.00.
 [2018-02-03 17:03:22] down thrd:35.00.
 [2018-02-03 17:03:22] temp nums:34.
 [2018-02-03 17:03:22] temp vmin:408.
 [2018-02-03 17:03:22] temp vmax:652.
 [2018-02-03 17:03:22] temp fstp: 5.00.
 [2018-02-03 17:03:22] temp fmin:-40.00.
 [2018-02-03 17:03:22] temp fmax:125.00.
 [2018-02-03 17:03:22] A1 = 1100,98
 [2018-02-03 17:03:22] A1 PLL Clock = 1092MHz
 [2018-02-03 17:03:22] A1 = 1100,98
 [2018-02-03 17:03:22] A1 PLL Clock = 1092MHz
 [2018-02-03 17:03:22] A1 = 1100,98
 [2018-02-03 17:03:22] A1 PLL Clock = 1092MHz
 [2018-02-03 17:03:22] A1 = 1100,98
 [2018-02-03 17:03:22] A1 PLL Clock = 1092MHz
 [2018-02-03 17:03:22] A1 = 1100,98
 [2018-02-03 17:03:22] A1 PLL Clock = 1092MHz
 [2018-02-03 17:03:22] A1 = 1100,98
 [2018-02-03 17:03:22] A1 PLL Clock = 1092MHz
 [2018-02-03 17:03:22] A1 = 1100,98
 [2018-02-03 17:03:22] A1 PLL Clock = 1092MHz
 [2018-02-03 17:03:22] A1 = 1100,98
 [2018-02-03 17:03:22] A1 PLL Clock = 1092MHz
 [2018-02-03 17:03:22] A1: checking A1 chain
 [2018-02-03 17:03:22] SPI '/dev/spidev0.0': mode=1, bits=8, speed=1500000     
 [2018-02-03 17:03:22] SPI '/dev/spidev1.0': mode=1, bits=8, speed=1500000     
 [2018-02-03 17:03:22] SPI '/dev/spidev2.0': mode=1, bits=8, speed=1500000     
 [2018-02-03 17:03:22] SPI '/dev/spidev3.0': mode=1, bits=8, speed=1500000     
 [2018-02-03 17:03:22] SPI '/dev/spidev4.0': mode=1, bits=8, speed=1500000     
 [2018-02-03 17:03:22] SPI '/dev/spidev5.0': mode=1, bits=8, speed=1500000     
set_vid_value:8.
 [2018-02-03 17:03:25] Plug Status[0] = 0

 [2018-02-03 17:03:27] Plug Status[1] = 0

 [2018-02-03 17:03:28] Plug Status[2] = 0

 [2018-02-03 17:03:30] Plug Status[3] = 0

 [2018-02-03 17:03:31] Plug Status[4] = 1

 [2018-02-03 17:03:33] Plug Status[5] = 1

 [2018-02-03 17:03:33] 0: A1 init chain
 [2018-02-03 17:03:33] send command [bist_start]

 [2018-02-03 17:03:33] spi_send_command,147

 [2018-02-03 17:03:33] spi_send_data,126

 [2018-02-03 17:03:33] cmd bist start: poll fail !
 [2018-02-03 17:03:33] bist start fail
 [2018-02-03 17:03:33] init a1 chain fail
 [2018-02-03 17:03:33] 1: A1 init chain
 [2018-02-03 17:03:33] send command [bist_start]

 [2018-02-03 17:03:33] spi_send_command,147

 [2018-02-03 17:03:33] spi_send_data,126

 [2018-02-03 17:03:33] cmd bist start: poll fail !
 [2018-02-03 17:03:33] bist start fail
 [2018-02-03 17:03:33] init a1 chain fail
 [2018-02-03 17:03:33] 2: A1 init chain
 [2018-02-03 17:03:33] send command [bist_start]

 [2018-02-03 17:03:33] spi_send_command,147

 [2018-02-03 17:03:33] spi_send_data,126

 [2018-02-03 17:03:33] cmd bist start: poll fail !
 [2018-02-03 17:03:33] bist start fail
 [2018-02-03 17:03:33] init a1 chain fail
 [2018-02-03 17:03:33] 3: A1 init chain
 [2018-02-03 17:03:33] send command [bist_start]

 [2018-02-03 17:03:33] spi_send_command,147

 [2018-02-03 17:03:33] spi_send_data,126

 [2018-02-03 17:03:33] cmd bist start: poll fail !
 [2018-02-03 17:03:33] bist start fail
 [2018-02-03 17:03:33] init a1 chain fail
 [2018-02-03 17:03:33] 4: A1 init chain
 [2018-02-03 17:03:33] send command [bist_start]

 [2018-02-03 17:03:33] spi_send_command,147

 [2018-02-03 17:03:33] spi_send_data,126

 [2018-02-03 17:03:33] cmd bist start: poll fail !
 [2018-02-03 17:03:33] bist start fail
 [2018-02-03 17:03:33] init a1 chain fail
 [2018-02-03 17:03:33] 5: A1 init chain
 [2018-02-03 17:03:33] send command [bist_start]

 [2018-02-03 17:03:33] spi_send_command,147

 [2018-02-03 17:03:33] spi_send_data,126

 [2018-02-03 17:03:33] cmd bist start: poll fail !
 [2018-02-03 17:03:33] bist start fail
 [2018-02-03 17:03:33] init a1 chain fail
 [2018-02-03 17:03:33] init_ReadTemp...
 [2018-02-03 17:03:33] reload init a1 chain0 fail
 [2018-02-03 17:03:33] reload init a1 chain1 fail
 [2018-02-03 17:03:33] reload init a1 chain2 fail
 [2018-02-03 17:03:33] reload init a1 chain3 fail
 [2018-02-03 17:03:33] reload init a1 chain4 fail
 [2018-02-03 17:03:33] reload init a1 chain5 fail
 [2018-02-03 17:03:33] A1 dectect finish
 [2018-02-03 17:03:33] All devices disabled, cannot mine!





may i update firmware via telnet?


Title: Re: Innosilicon A4+ setup tutorial
Post by: parhom on February 04, 2018, 01:38:02 PM
Hi to everybody!
Need you help with Innosilicon A4+ LTCmaster miners:
Miner Type   17
Hw Version   G19
Build Date   Sat Dec 9 02:33:32 CST 2017

After one week of working it stopped working as wollows:
All green indicators are working but it does not mine and I can not connect web interface, just see the following: http://imgshare.free.fr/uploads/75b925c275.jpg

I rebooted manu times, but no luck. What can I do? May be there is a possibility to upgrade a firmware through telnet?


P.S. One of miners lost one chain, but it was returned back after few reboots, firmware upgrade and clicking "Auto Search" button on "Voltage" block of "Miner General Configuration" tab.

P.S.S. sometimes miners shows huge Running time (above 14 or 17 thousands days!!!) it fixes by rebooting.

Thank you for any help.



Title: Re: Innosilicon A4+ setup tutorial
Post by: kb8679 on February 04, 2018, 07:42:31 PM
Hi to everybody!
Need you help with Innosilicon A4+ LTCmaster miners:
Miner Type   17
Hw Version   G19
Build Date   Sat Dec 9 02:33:32 CST 2017

After one week of working it stopped working as wollows:
All green indicators are working but it does not mine and I can not connect web interface, just see the following:

I rebooted manu times, but no luck. What can I do? May be there is a possibility to upgrade a firmware through telnet?


P.S. One of miners lost one chain, but it was returned back after few reboots, firmware upgrade and clicking "Auto Search" button on "Voltage" block of "Miner General Configuration" tab.

P.S.S. sometimes miners shows huge Running time (above 14 or 17 thousands days!!!) it fixes by rebooting.

Thank you for any help.



You are running old FW and sounds like the issue with few people (incl. me) have had.

Try:
Code:
1) telnet to miner IP at port 8100
2) login: root
3) password: innot1t2
4) rm -rf /lib/python3.4/__pycache__/*.pyc
5) reboot
Hopefully you have working miner after this point, then go ahead and upgrade your firmware via web interface.
Link to the latest FW (as of 04.02.2018): http://www.innosilicon.com.cn/download/update_180129.bin (http://www.innosilicon.com.cn/download/update_180129.bin)


Title: Re: Innosilicon A4+ setup tutorial
Post by: parhom on February 05, 2018, 07:11:09 PM
Hi to everybody!
Need you help with Innosilicon A4+ LTCmaster miners:
Miner Type   17
Hw Version   G19
Build Date   Sat Dec 9 02:33:32 CST 2017

After one week of working it stopped working as wollows:
All green indicators are working but it does not mine and I can not connect web interface, just see the following:

I rebooted manu times, but no luck. What can I do? May be there is a possibility to upgrade a firmware through telnet?


P.S. One of miners lost one chain, but it was returned back after few reboots, firmware upgrade and clicking "Auto Search" button on "Voltage" block of "Miner General Configuration" tab.

P.S.S. sometimes miners shows huge Running time (above 14 or 17 thousands days!!!) it fixes by rebooting.

Thank you for any help.



You are running old FW and sounds like the issue with few people (incl. me) have had.

Try:
Code:
1) telnet to miner IP at port 8100
2) login: root
3) password: innot1t2
4) rm -rf /lib/python3.4/__pycache__/*.pyc
5) reboot
Hopefully you have working miner after this point, then go ahead and upgrade your firmware via web interface.
Link to the latest FW (as of 04.02.2018): http://www.innosilicon.com.cn/download/update_180129.bin (http://www.innosilicon.com.cn/download/update_180129.bin)

Thank you.
I done above mentioned actions, but no result - web interface still not responding and I can not update firmware. And after those actions pool shows this miner as inactive. Is there any other way to update firmware through telnet?


I found that mining process was not executing:
Code:
ps|grep innominer
  840 root       0:00 syslogd -f /etc/syslog.conf -O /tmp/log/innominer.log -s 1024 -b 5
 4269 root       0:00 grep innominer

after that I executed it manually:
Code:
./home/inno_tools/run.sh

and mining process was started, but I still can not access web interface to upgrade FW.

I belive I can upgrade is by loading FW .bin file to miner and running /home/inno_tools/upgrade.py, but I'm not familiar with Python and can not understand how to feed upgrade.py with FW .bin file :(((

Can anybody help me????

Thank you in advance.


UPD. "OK" and "ERROR" LEDs on control board are OFF.

UPD1: Solved the problem by deleting all .pyc files with command  
Code:
find / -name "*.pyc" -delete


Title: Re: Innosilicon A4+ setup tutorial
Post by: needed357 on February 10, 2018, 02:47:56 PM
hey what do you mine and where did you mine?

im actual mine LTC on ltcpool


Title: Re: Innosilicon A4+ setup tutorial
Post by: Patriot872 on February 10, 2018, 11:50:19 PM
Hey fellow A4+ owners - i'm getting my tail kicked a bit
we're running a handful of these and they are only working on some pools.
we're updating everything to the 112 Bin file, the later one seemed to cause more problems than it helped

We're seeking mainly LTC, but litecoinpool will not connect with these - tried dozens of times
F2Pool & Antpool - only show onen board for each miner we connect

after nearly two weeks on this, the only pools withfull hash shown is Hash to coins & Multi Pool
we're pretty familiar with Asics, but dealing with this company has been a nitemare and we will never buy there again

any input would be appreciated
 


Title: Re: Innosilicon A4+ setup tutorial
Post by: swaaaagMaaaan on February 11, 2018, 09:12:53 AM
Hi, it's my first time on this site.

I ordered a couple of Innosilicon A4+ miners. I was having problems with getting them started, however providing them with a dynamic IP did the trick.

The issue is that I want to connect to one of my miners however as it has a dynamic IP, I do not know how. Can anyone help me out?

Thanks Guys!


Title: Re: Innosilicon A4+ setup tutorial
Post by: persocra on February 11, 2018, 10:01:46 AM
For anyone curious, you can turn these A4+'s into A6s. The control board has enough ports for 8 hashboards and 4 fans. I changed over 30 A4s so I only have to monitor 15 ASICs now. Way better. The inno support guy gave me an older firmware that supports it, the latest only ran 6 boards total. He said there should be a new firmware today or tomorrow that supports all 8 again.

Thanks, update_180129 appears to have no issues running all 8 chains.


Just made the exact same change to 10 miners today. Appears to work just great! Along with halving the work upkeeping them, the best benefit (IMHO) is having spare controller boards now. :)
I use separate PSUs for each tube, and this has no negative impact either.

FYI, I did the 0129 upgrade on 10 A4+ today and it seemed to all go smoothly.  I did notice that one of my boxes was running 471 hash rate so I took a look and found that the ASC2 card was missing from the miner status/minerinfo section.  I made sure all the cables, power and data ribbon were all secured and the LED shows the board is getting power.  I upgraded the firmware (0129) twice again to no avail.  So I'm wondering what I should try next.  I cannot say with certainy if this was caused by the firmware...I have a feeling not because the 24 hashrate shows as 465 on the monitoring page (i didn't bother to look before i guess).

Any ideas on what to do next?


omg i got this problem too :(

420mhz all other 620 ~

Me too. Upgraded to 180129.bin, and lost ASC 2 on its next reboot. Have tried to downgrade to 180112.bin witout luck, and the light on ASC 2 is still lit. I'm in touch with Innosilicon support and will keep you posted. Please let me know if you sort out this problem before I do.

Update: I downgraded to http://www.innosilicon.com.cn/download/update_171229.bin (http://www.innosilicon.com.cn/download/update_171229.bin), and everything went back to normal. All four hashboards now hashing on full speed.


Title: Re: Innosilicon A4+ setup tutorial
Post by: parhom on February 13, 2018, 08:02:10 PM
Hi, it's my first time on this site.

I ordered a couple of Innosilicon A4+ miners. I was having problems with getting them started, however providing them with a dynamic IP did the trick.

The issue is that I want to connect to one of my miners however as it has a dynamic IP, I do not know how. Can anyone help me out?

Thanks Guys!

Hi, you can reset IP to default by pressing IP SET button within 10-20 seconds. It's located on the left side from Internet cabble. Chains LEDs shall become OFF and then you can unpress IP SET button. You will reset IP to 192.168.1.254.  To avoid such problems, you have to set static IP from web interface of miner or you can fix IP in your router with MAC address of the miner.
BTW, some routers could provide you with statistic which IP address are leased you you can try to try each one to find miners without IP reset.


Title: Re: Innosilicon A4+ setup tutorial
Post by: parhom on February 13, 2018, 08:25:02 PM
For anyone curious, you can turn these A4+'s into A6s. The control board has enough ports for 8 hashboards and 4 fans. I changed over 30 A4s so I only have to monitor 15 ASICs now. Way better. The inno support guy gave me an older firmware that supports it, the latest only ran 6 boards total. He said there should be a new firmware today or tomorrow that supports all 8 again.

Thanks, update_180129 appears to have no issues running all 8 chains.


Just made the exact same change to 10 miners today. Appears to work just great! Along with halving the work upkeeping them, the best benefit (IMHO) is having spare controller boards now. :)
I use separate PSUs for each tube, and this has no negative impact either.

FYI, I did the 0129 upgrade on 10 A4+ today and it seemed to all go smoothly.  I did notice that one of my boxes was running 471 hash rate so I took a look and found that the ASC2 card was missing from the miner status/minerinfo section.  I made sure all the cables, power and data ribbon were all secured and the LED shows the board is getting power.  I upgraded the firmware (0129) twice again to no avail.  So I'm wondering what I should try next.  I cannot say with certainy if this was caused by the firmware...I have a feeling not because the 24 hashrate shows as 465 on the monitoring page (i didn't bother to look before i guess).

Any ideas on what to do next?


omg i got this problem too :(

420mhz all other 620 ~

Me too. Upgraded to 180129.bin, and lost ASC 2 on its next reboot. Have tried to downgrade to 180112.bin witout luck, and the light on ASC 2 is still lit. I'm in touch with Innosilicon support and will keep you posted. Please let me know if you sort out this problem before I do.

Update: I downgraded to http://www.innosilicon.com.cn/download/update_171229.bin (http://www.innosilicon.com.cn/download/update_171229.bin), and everything went back to normal. All four hashboards now hashing on full speed.

Did you get such solution from Innosilicon support or it's you idea? I also solved the problem by this way, but I'm not sure that's right idea because the same miner had the same problem before and I solved it in another way (I think it was just luck).


Title: Re: Innosilicon A4+ setup tutorial
Post by: compir on February 14, 2018, 05:43:16 PM
my 2 a4+ not working. all boards lights on and fans always working full speed. I can access web interface I did upgrade and downgrade firmware but nothing works. miner configuration page doesn't show hash rate and vid. Try to telnet but I am not good on that always says read only file. Try chmod doesn't work ( or I am doing wrong)


Title: Re: Innosilicon A4+ setup tutorial
Post by: shepardblue on February 15, 2018, 01:10:38 AM
I can access web interface I did upgrade and downgrade firmware but nothing works. miner configuration page doesn't show hash rate and vid.

What does it show?


Title: Re: Innosilicon A4+ setup tutorial
Post by: compir on February 15, 2018, 12:35:49 PM
I can access web interface I did upgrade and downgrade firmware but nothing works. miner configuration page doesn't show hash rate and vid.

What does it show?

it shows pool settings on miner configuration page and on system page other then miner type shows everything. Miner status page never load.

it doesn't show miner frequency and vid on miner configuration page. Just shows url worker and password. Frequency and vid empty


Title: Re: Innosilicon A4+ setup tutorial
Post by: Aepko on February 15, 2018, 05:12:06 PM
I can access web interface I did upgrade and downgrade firmware but nothing works. miner configuration page doesn't show hash rate and vid.

What does it show?

it shows pool settings on miner configuration page and on system page other then miner type shows everything. Miner status page never load.

it doesn't show miner frequency and vid on miner configuration page. Just shows url worker and password. Frequency and vid empty

force reload the page. ctrl+F5


Title: Re: Innosilicon A4+ setup tutorial
Post by: Cosmictino on February 16, 2018, 08:16:35 AM
hi folks.. ;D

im playing around with the config files from G19_R1.2.img and here is what i found in the inno_config.py. seems like they will release or still running XMR miners  ..óÒ..

-----------------------------------------------------------------------------------------------------------------------------------------

#!/usr/bin/env python3
# -*- coding: utf-8 -*-

import platform

#################################### json配置 ###################################
gInnoJsonIndent = 2

#################################### cgi配置 ####################################
gInnoVersionPath = '/build_log'
gInnoPassWordPath= '/home/www/conf/password'
gInnoResolvPath = '/etc/resolv.conf'
gInnoInterfacePath='/etc/network/interfaces'
gInnoTypePath   = '/tmp/type'
gInnoHWVerPath  = '/tmp/hwver'
gInnoRunShPath  = '/home/inno_tools/run.sh'
gInnoMinerConfPath= '/home/www/conf/miner.conf'
gInnoDnaDevicePath= '/dev/dna'
gInnoDnaFilePath= '/innocfg/dna'
gInnoLogoPath = '/home/www/static/images/logo.png'
gInnoBakLogoPath = '/home/www/static/images/logo.png.inno'
gInnoBlankLogoPath = '/home/www/static/images/blank-logo.png'
gInnoSysLogPath = '/innocfg/log/miner.log'
gInnoDefVidPath = '/home/www/conf/defaultVID'
gInnoLogoFileSize = 4 * 1024 * 1024     # 4M
gInnoKeyGPIOValue = '/sys/class/gpio/gpio895/value'

gInnoGetDhcpCmd = "cat %s | grep ^iface | sed -n '$p' | awk '{print $4}'" % (gInnoInterfacePath)
gInnoGetIpCmd   = "ifconfig | grep inet | sed -n '1p' | awk '{print $2}' | awk -F ':' '{print $2}'"
gInnoGetNetmask = "ifconfig |grep inet| sed -n '1p'|awk '{print $4}'|awk -F ':' '{print $2}'"
gInnoGetGateway = "route -n | grep eth0 | grep UG | awk '{print $2}'"
##################################### json键 ####################################
gInnoCallBackKey    = 'callback'
gInnoLogoFileKey    = 'logofile'
gInnoBlankLogoKey   = 'nologo'

gInnoResultKey      = 'result'
gInnoResultValTrue  = 'true'
gInnoResultValFalse = 'false'

gInnoPassWord       = 'password'
gInnoNewPassWdKey   = 'newpwd'
gInnoOldPassWdKey   = 'oldpwd'

gInnoTypeKey    = 'type'
gInnoFreqKey    = 'Frequency'
gInnoVolKey     = 'Voltage'
gInnoDhcpKey    = 'dhcp'
gInnoIpAddrKey  = 'ipaddress'
gInnoNetmaskKey = 'netmask'
gInnoGatawayKey = 'gateway'
gInnoDnsKey     = 'dns'
gInnoPoolNumKey = 'PoolNum'
gInnoPool1Key   = 'Pool1'
gInnoPool2Key   = 'Pool2'
gInnoPool3Key   = 'Pool3'
gInnoUser1Key   = 'UserName1'
gInnoUser2Key   = 'UserName2'
gInnoUser3Key   = 'UserName3'
gInnoPwd1Key    = 'Password1'
gInnoPwd2Key    = 'Password2'
gInnoPwd3Key    = 'Password3'
gInnoFanModeKey = 'fanmode'
gInnoFanSpdKey  = 'fanspeed'
gInnoVidModeKey = 'vidmode'

################################### xgminer配置 #################################
gInnoMinerApiIp     = '127.0.0.1'
gInnoMinerApiPort   = 4028
gInnoMinerApiDict   = {"command" : "devs"}
gInnoMinerApiTest   = {"command" : "summary"}
gInnoMinerApiBufSize= 4096

gInnoChainNum       = 8
gInnoGPIOPwOnBase   = 872       # 872,873,874,875,876,877,878,879
gInnoGPIOLedPwBase  = 881       # 881,882,883,884,885,886,887,888
gInnoGPIOLedGreen   = 869
gInnoGPIOLedRed     = 870
gInnoGPIOKey        = 895
gInnoGPIOBeep       = 867
################################### run.sh模板 ##################################
gInnoRunshTemple    = """#!/bin/sh
killall innominer_%s
killall innominer_%s
killall innominer_%s
sleep 5

"""
gInnoTestTime     = 600
gInnoInitCmdStr   = 'innominer_%s -o %s -u %s -p %s --A1Pll1 %s --A1Pll2 %s --A1Pll3 %s --A1Pll4 %s --A1Pll5 %s --A1Pll6 %s --A1Pll7 %s --A1Pll8 %s --A1Vol1 %s --A1Vol2 %s --A1Vol3 %s --A1Vol4 %s --A1Vol5 %s --A1Vol6 %s --A1Vol7 %s --A1Vol8 %s --api-listen > /dev/null 2>&1 &'
gInnoVidMode    = 'manual'
gInnoFanMode    = 'auto'
gInnoFanSpeed   = '3'
gInnoBtcName      = 'T1'
gInnoBtcPool      = 'stratum+tcp://btc.s.innomining.com:1800'
gInnoBtcPoolTest  = 'stratum+tcp://btc.s.innomining.com:1800'
gInnoBtcUser      = 'inno.btc'
gInnoBtcPwd       = 'x'
gInnoBtcFreq      = 1332
gInnoBtcVid       = 10
gInnoBtcVidList   = [12, 11, 10]
gInnoBtcPllList   = [1332]
gInnoInitBtcCmd   = gInnoInitCmdStr % (gInnoBtcName, gInnoBtcPool, gInnoBtcUser, gInnoBtcPwd, gInnoBtcFreq, gInnoBtcFreq, gInnoBtcFreq, gInnoBtcFreq, gInnoBtcFreq, gInnoBtcFreq, gInnoBtcFreq, gInnoBtcFreq, gInnoBtcVid, gInnoBtcVid, gInnoBtcVid, gInnoBtcVid, gInnoBtcVid, gInnoBtcVid, gInnoBtcVid, gInnoBtcVid)
gInnoLtcName      = 'T2'
gInnoLtcPool      = 'stratum+tcp://ltc.s.innomining.com:1900'
gInnoLtcPoolTest  = 'stratum+tcp://ltc-sz-factory.s.innomining.com:1800'
gInnoLtcUser      = 'inno.ltc'
gInnoLtcPwd       = 'x'
gInnoLtcFreq      = 1044
gInnoLtcVid       = 25
gInnoLtcVidList   = [26, 25, 24]
gInnoLtcPllList   = [1044]
gInnoInitLtcCmd   = gInnoInitCmdStr % (gInnoLtcName, gInnoLtcPool, gInnoLtcUser, gInnoLtcPwd, gInnoLtcFreq, gInnoLtcFreq, gInnoLtcFreq, gInnoLtcFreq, gInnoLtcFreq, gInnoLtcFreq, gInnoLtcFreq, gInnoLtcFreq, gInnoLtcVid, gInnoLtcVid, gInnoLtcVid, gInnoLtcVid, gInnoLtcVid, gInnoLtcVid, gInnoLtcVid, gInnoLtcVid)
gInnoDashName     = 'T3'
gInnoDashPool     = 'stratum+tcp://dash.s.innomining.com:2000'
gInnoDashPoolTest = 'stratum+tcp://dash-sz-factory.s.innomining.com:1800'
gInnoDashUser     = 'inno.dash'
gInnoDashPwd      = 'x'
gInnoDashFreq     = 1100
gInnoDashVid      = 12
gInnoDashVidList  = [14, 13, 12]
gInnoDashPllList  = [1100]
gInnoInitDashCmd  = gInnoInitCmdStr % (gInnoDashName, gInnoDashPool, gInnoDashUser, gInnoDashPwd, gInnoDashFreq, gInnoDashFreq, gInnoDashFreq, gInnoDashFreq, gInnoDashFreq, gInnoDashFreq, gInnoDashFreq, gInnoDashFreq, gInnoDashVid, gInnoDashVid, gInnoDashVid, gInnoDashVid, gInnoDashVid, gInnoDashVid, gInnoDashVid, gInnoDashVid)
gInnoXmrName      = 'T4'
gInnoXmrPool      = 'stratum+tcp://pool.com:800'
gInnoXmrPoolTest  = 'stratum+tcp://a8.s.innomining.com:19333'
gInnoXmrUser      = 'innot4.0001'
gInnoXmrPwd       = 'x'
gInnoXmrFreq      = 1000
gInnoXmrVid       = 175
gInnoXmrVidList   = [175]
gInnoXmrVidList   = [950, 1000, 1050]
gInnoInitXmrCmd   = gInnoInitCmdStr % (gInnoXmrName, gInnoXmrPool, gInnoXmrUser, gInnoXmrPwd, gInnoXmrFreq, gInnoXmrFreq, gInnoXmrFreq, gInnoXmrFreq, gInnoXmrFreq, gInnoXmrFreq, gInnoXmrFreq, gInnoXmrFreq, gInnoXmrVid, gInnoXmrVid, gInnoXmrVid, gInnoXmrVid, gInnoXmrVid, gInnoXmrVid, gInnoXmrVid, gInnoXmrVid)
gInnoCmd1Pool     = gInnoInitCmdStr
gInnoCmd2Pool     = 'innominer_%s -o %s -u %s -p %s -o %s -u %s -p %s --A1Pll1 %s --A1Pll2 %s --A1Pll3 %s --A1Pll4 %s --A1Pll5 %s --A1Pll6 %s --A1Pll7 %s --A1Pll8 %s --A1Vol1 %s --A1Vol2 %s --A1Vol3 %s --A1Vol4 %s --A1Vol5 %s --A1Vol6 %s --A1Vol7 %s --A1Vol8 %s --api-listen >/dev/null 2>&1 &'
gInnoCmd3Pool     = 'innominer_%s -o %s -u %s -p %s -o %s -u %s -p %s -o %s -u %s -p %s --A1Pll1 %s --A1Pll2 %s --A1Pll3 %s --A1Pll4 %s --A1Pll5 %s --A1Pll6 %s --A1Pll7 %s --A1Pll8 %s --A1Vol1 %s --A1Vol2 %s --A1Vol3 %s --A1Vol4 %s --A1Vol5 %s --A1Vol6 %s --A1Vol7 %s --A1Vol8 %s --api-listen >/dev/null 2>&1 &'

-----------------------------------------------------------------------------------------------------------------------------------------




Title: Re: Innosilicon A4+ setup tutorial
Post by: parhom on February 18, 2018, 01:48:16 PM
For anyone curious, you can turn these A4+'s into A6s. The control board has enough ports for 8 hashboards and 4 fans. I changed over 30 A4s so I only have to monitor 15 ASICs now. Way better. The inno support guy gave me an older firmware that supports it, the latest only ran 6 boards total. He said there should be a new firmware today or tomorrow that supports all 8 again.

Thanks, update_180129 appears to have no issues running all 8 chains.


Just made the exact same change to 10 miners today. Appears to work just great! Along with halving the work upkeeping them, the best benefit (IMHO) is having spare controller boards now. :)
I use separate PSUs for each tube, and this has no negative impact either.

FYI, I did the 0129 upgrade on 10 A4+ today and it seemed to all go smoothly.  I did notice that one of my boxes was running 471 hash rate so I took a look and found that the ASC2 card was missing from the miner status/minerinfo section.  I made sure all the cables, power and data ribbon were all secured and the LED shows the board is getting power.  I upgraded the firmware (0129) twice again to no avail.  So I'm wondering what I should try next.  I cannot say with certainy if this was caused by the firmware...I have a feeling not because the 24 hashrate shows as 465 on the monitoring page (i didn't bother to look before i guess).

Any ideas on what to do next?


omg i got this problem too :(

420mhz all other 620 ~

Me too. Upgraded to 180129.bin, and lost ASC 2 on its next reboot. Have tried to downgrade to 180112.bin witout luck, and the light on ASC 2 is still lit. I'm in touch with Innosilicon support and will keep you posted. Please let me know if you sort out this problem before I do.

Update: I downgraded to http://www.innosilicon.com.cn/download/update_171229.bin (http://www.innosilicon.com.cn/download/update_171229.bin), and everything went back to normal. All four hashboards now hashing on full speed.

Did you get such solution from Innosilicon support or it's you idea? I also solved the problem by this way, but I'm not sure that's right idea because the same miner had the same problem before and I solved it in another way (I think it was just luck).

After a week working on 29.12.2017 firmware one chain lost again and no tricks with upgrading and downgrading do not help. Any other ideas?


Title: Re: Innosilicon A4+ setup tutorial
Post by: shepardblue on February 18, 2018, 05:18:32 PM
After a week working on 29.12.2017 firmware one chain lost again and no tricks with upgrading and downgrading do not help. Any other ideas?

I had this issue and sent the chain back to Innoslicon. Idk if anyone else has other tricks, I tried something but was like, this is what the warranty is for. I recommend reaching out and getting the ball rolling on using your warranty. Cost me $150 to ship it back to China plus it took like 2 weeks round trip :/


Title: Re: Innosilicon A4+ setup tutorial
Post by: Patriot872 on February 20, 2018, 09:17:47 AM
Hey Guys - don't have the coding and linnux exp some of you have.
we have a dozen of these running fine, nearly All on the 180112 Bin file
we've got a handful of these A4's that won't accept the 112 or 129 bin files now.
we're plagued with a wide range of other issues on about 10 machines, 2 chains down + + + +
Unfortunately all of these are G19's with no TF port, but if we could determine a work around to simply
clone these from one of our working well units i think that would do the trick.
would appreciate any help at all here - thoughts ? ? ?


Title: Re: Innosilicon A4+ setup tutorial
Post by: dan13l on February 23, 2018, 03:17:57 PM
Hello everyone! I have had some issues with my machines, but thanks to this tread I have managed to fix them to work.
Now I have noticed that one of the machines in the status page of the machine says that is working with ~660 MH/s, but in litecoinpool and other pools, only this machine shows 485~500 MH/s. The other machines are fine - above 600 MH/s. I have checked all the boards - everything is green. Updated the firmware several times, but with no success. Could you suggest where the problem could come from? Thank you in advance!


Title: Re: Innosilicon A4+ setup tutorial
Post by: Cosmictino on February 24, 2018, 12:43:25 PM
Hi folks,

there is a new Update .bin http://www.innosilicon.com/html/downA4/
update_180209t1108.bin

someone tested ?


Title: Re: Innosilicon A4+ setup tutorial
Post by: kb8679 on February 24, 2018, 02:17:05 PM
Just upgraded. Appears to work fine. I haven't had issues such as lost asic chains etc. So can't say if this update helps with that or any other issues.
I'm running 2 tubes with 1 ctrl board configuration and just like with the previous FW, no problems with this arrangement either.

Root pw is still the same: t1t2t3a5

https://i.imgur.com/SAaaYuy.png

Hi folks,

there is a new Update .bin http://www.innosilicon.com/html/downA4/
update_180209t1108.bin

someone tested ?


Title: Re: Innosilicon A4+ setup tutorial
Post by: needed357 on February 25, 2018, 04:05:28 PM
do i really must change the config for API Awesomer with every upgrade? :o


Title: Re: Innosilicon A4+ setup tutorial
Post by: wease on February 26, 2018, 03:43:20 AM
I just upgraded and tried to configure api again and messed something up.  I can access miner page but it just keeps loading.  Can't upload firmware again.  No card reader just an empty slot where it should be.  How do I fix this?  I can still access it with telnet.  Not sure what to do once in there to fix issue.


Title: Re: Innosilicon A4+ setup tutorial
Post by: parhom on February 28, 2018, 08:38:16 PM
One more trouble: I can not access miner configuration using password 12345678. I'm getting reply that password is wrong. Is it possible to reset this password?

Thank you


UPD: Solved:
telnet to the miner and opened file:
cd /home/www/conf
vi password

password is written there


Title: Re: Innosilicon A4+ setup tutorial
Post by: nyesim on March 01, 2018, 05:31:28 PM
I just upgraded and tried to configure api again and messed something up.  I can access miner page but it just keeps loading.  Can't upload firmware again.  No card reader just an empty slot where it should be.  How do I fix this?  I can still access it with telnet.  Not sure what to do once in there to fix issue.


Hi wease,

I had problems similar to your probing too. solution of the problem;

1- Download the latest firmware from innosilicon website.
2- Open console with telnet and login to the innosilicon console
3- cd / tmp
4- Open the hwver file via vi command "vi hwver"
5 - If you do not write anything in the file, this is where the error comes from.
6- hardware version writes on the controller board.
7- write G19 or G9 into the hwver file according to the board version
8 - Save with ESC and: wq
9 - Write device ip address from chrome
10 - Select the firmware file you downloaded last by choosing Upgrade from the miner console by clicking the system tab
11- Press the apply button.

Wait for the device to boot.

regards,
Nuri Yesim



Title: Re: Innosilicon A4+ setup tutorial
Post by: wease on March 01, 2018, 08:39:42 PM
Still not working.  It only shows me system and network.  Under version, it only shows miner type 17.  Everything else is spinning discs.  I have no idea what else to do.  Thank you for the suggestion.

In telnet, I tried what the tech did and got the same result as he did.  he ran fw_printenc rootfs_flag.  It came back flagb and he tried to set flag a and it says bad crc, using default environment.  Whatever that means.


Title: Re: Innosilicon A4+ setup tutorial
Post by: solarismedic on March 01, 2018, 08:54:53 PM
Hi folks,

there is a new Update .bin http://www.innosilicon.com/html/downA4/
update_180209t1108.bin

someone tested ?

I just tried it with one of my A4+ and it bricked the box.  I performed the upgrade through the GUI as one normally would, but upon the automatic restart, it wouldn't come back up.  Couldn't even ping the box.  I walked over to the unit and saw that all lights were off on the hashoard with the fault red light on the controller.  I power cycled (i figured it was safe to since it was about 30 mins since the upgrade ended) all the lights came back on as one would expect.  After about 2 mins of sitting there, all the hasboard lights turned off.  My guess is that the controller upgrade failed and now is corrupted.

Will need to run out and grab a tfcard from the store to see if upgrading via the slot works.  for now, i'll switch all the hasboard cables over to another miner so I don't lose hashrate.  Definitely hold back on the new firmware...let some guinea pigs try it for several weeks first.  Don't get burned like I did.

Before this, had upgraded to 0129 with no issues and running several weeks.


Title: Re: Innosilicon A4+ setup tutorial
Post by: wease on March 02, 2018, 01:46:44 AM
Tech support told me to send an email to miner_support@innosilicon.com.cn and tell them my problem.  They will send me an upgrade device.  My miner has a slot for a card but no card reader installed.  I'll update when I hear back from them.


Title: Re: Innosilicon A4+ setup tutorial
Post by: nyesim on March 02, 2018, 04:41:51 AM
Tech support told me to send an email to miner_support@innosilicon.com.cn and tell them my problem.  They will send me an upgrade device.  My miner has a slot for a card but no card reader installed.  I'll update when I hear back from them.

Hi wease,

The problem is the same as mine,
I sent many mail too. They told me not to restore the firmware. I could not load the old firmware. There were 4 firmware I found on the internet, I tried all of them. I downloaded the last downloaded firmware. I could do it by trying different firmware in at least 10 trials. Do not give up trying. you can finally achieve. If innosilicon comes to me with another suggestion, I will inform you.

Nuri
Regards


Title: Re: Innosilicon A4+ setup tutorial
Post by: solarismedic on March 02, 2018, 09:51:43 AM

I just tried it with one of my A4+ and it bricked the box.  I performed the upgrade through the GUI as one normally would, but upon the automatic restart, it wouldn't come back up.  Couldn't even ping the box.  I walked over to the unit and saw that all lights were off on the hashoard with the fault red light on the controller.  I power cycled (i figured it was safe to since it was about 30 mins since the upgrade ended) all the lights came back on as one would expect.  After about 2 mins of sitting there, all the hasboard lights turned off.  My guess is that the controller upgrade failed and now is corrupted.

Will need to run out and grab a tfcard from the store to see if upgrading via the slot works.  for now, i'll switch all the hasboard cables over to another miner so I don't lose hashrate.  Definitely hold back on the new firmware...let some guinea pigs try it for several weeks first.  Don't get burned like I did.

Before this, had upgraded to 0129 with no issues and running several weeks.

this is embarrassing.  turns out the IP got reset to the static 192.168.1.254.  can confirm the new firmware is hashing now.  i don't notice any difference though.  if i find any difference, I'll report back here.


Title: Re: Innosilicon A4+ setup tutorial
Post by: wease on March 02, 2018, 03:13:55 PM
They are sending me a card reader.  The instructions show that it hooks up to a set of pins on the board.  Who knows how long it will take to get it.


I will keep trying to load firmware.  The newest firmware never stops loading.  I let it get to 1000% last night and still nothing.  The other firmwares giv eme invalid hardware detected.  Atleast its still hashing but would love to be able to load firmware.


Title: Re: Innosilicon A4+ setup tutorial
Post by: bgbaster on March 05, 2018, 06:47:53 PM
Hello everyone! I have had some issues with my machines, but thanks to this tread I have managed to fix them to work.
Now I have noticed that one of the machines in the status page of the machine says that is working with ~660 MH/s, but in litecoinpool and other pools, only this machine shows 485~500 MH/s. The other machines are fine - above 600 MH/s. I have checked all the boards - everything is green. Updated the firmware several times, but with no success. Could you suggest where the problem could come from? Thank you in advance!
I have the same issue with all of my A4+ ASICs. No one of them actually gets 600 MH/s or higher.


Title: Re: Innosilicon A4+ setup tutorial
Post by: needed357 on March 07, 2018, 08:20:24 PM
one chain is down :(

how can i check this in telnet?

i do restart and still 3 chains only on

:(


Title: Re: Innosilicon A4+ setup tutorial
Post by: notepadgamer on March 08, 2018, 03:45:38 AM
Hey guys, got some questions(first post, be gentle :P )

been looking at overclocking my 4 A4+'s but it seems that my miners only have the dropdown for 1044 and 1100.  The Card type is G19 with a FW of 29-12-2017
Is this normal as I see everyone saying 1152 should be avalable. (current hash rate of ~628 , vid 25, Mhz 1044)

furthermore Is there really any reason to overclock as a 10% increase in profit is negligable for possible miner damage??

Im also currently mining verge & gamecredits on miningpoolhub's pool and earning ~£5 gross. Only reason I ask is I swear the ROI was less than 400 days when I got the machines.


Title: Re: Innosilicon A4+ setup tutorial
Post by: jstefanop on March 08, 2018, 08:14:18 AM
Hey can one of you guys pull a board from one of these and take some high res pics of the front/backside. Can’t find any pcb pics for the A4+ just the A4.


Title: Re: Innosilicon A4+ setup tutorial
Post by: needed357 on March 08, 2018, 08:59:14 PM
one chain is down :(

how can i check this in telnet?

i do restart and still 3 chains only on

:(


lol reboot one day later and all 4 chains on the line :D


Title: Re: Innosilicon A4+ setup tutorial
Post by: notepadgamer on March 09, 2018, 12:08:05 AM
Hey can one of you guys pull a board from one of these and take some high res pics of the front/backside. Can’t find any pcb pics for the A4+ just the A4.

Sorry to say but your going to be dissapointed.  the boards look pretty much identical except a slightly diffrent chip number under the heatsinks.


Title: Re: Innosilicon A4+ setup tutorial
Post by: jstefanop on March 09, 2018, 09:28:23 PM
Hey can one of you guys pull a board from one of these and take some high res pics of the front/backside. Can’t find any pcb pics for the A4+ just the A4.

Sorry to say but your going to be dissapointed.  the boards look pretty much identical except a slightly diffrent chip number under the heatsinks.

Highly doubt that...A4 had 80 chips  on 4 boards, A4+ is 288 chips on 4 boards.


Title: Re: Innosilicon A4+ setup tutorial
Post by: shepardblue on March 10, 2018, 08:28:44 PM
Hey can one of you guys pull a board from one of these and take some high res pics of the front/backside. Can’t find any pcb pics for the A4+ just the A4.

Here's the best I have on hand, hope this helps:

https://s3.amazonaws.com/bitcointalkphotos/IMG_1462.JPG
https://s3.amazonaws.com/bitcointalkphotos/IMG_1461.JPG


Title: Re: Innosilicon A4+ setup tutorial
Post by: needed357 on March 12, 2018, 06:14:20 PM
whats the CMD line for auto reboot? in crontab?


Title: Re: Innosilicon A4+ setup tutorial
Post by: Aepko on March 15, 2018, 01:11:32 AM
I downloaded as much of the firmware as I could and put it on github

https://github.com/aepkolol/innofirmware

If anyone needs it for whatever reason


Title: Re: Innosilicon A4+ setup tutorial
Post by: tchor66 on March 16, 2018, 03:17:08 PM
Hello, is it possible to buy 1 control panel?
Where can I find it? and how much does it cost?
Thank you


Title: Re: Innosilicon A4+ setup tutorial
Post by: kilo17 on March 17, 2018, 04:15:20 AM
Here is a script I wrote to make it easy to add the --api extras.  Just change the xxx.xxx.xxx.xxx to the IP of the miner and make sure to make it s .sh file and give it Permissions to execute as a program.

Cheers...

btw - this was written for linux systems (in case you did not know  ;))


Code:
#!/bin/sh

HOST='xxx.xxx.xxx.xxx 8100'
USER='root'
PASSWD='t1t2t3a5'
CMD=''

(
echo open "$HOST"
sleep 2
echo "$USER"
sleep 2
echo "$PASSWD"
sleep 2
echo "cd /home/inno_py/"
sleep 2
echo "mount / -o rw,remount"
sleep 2
echo "vi -c ':%s@--api-listen@--api-listen --api-network --api-allow W:0/0@g' -c wq /home/inno_py/inno_config.py"
sleep 2

) | telnet


Title: Re: Innosilicon A4+ setup tutorial
Post by: OldYoungy on March 17, 2018, 07:53:22 AM
Hello everyone,

Does anyone know how to set share difficulty on an A4+? I can set pseudo with <address>+x but I get an Invalid Argument error when I try to use <address>/x or <address>/x+y

Thanks in advance!


Title: Re: Innosilicon A4+ setup tutorial
Post by: kb8679 on March 17, 2018, 03:07:33 PM
It's something that's actually set by the pool. Most (or quite many of them at least) support manual share difficulty which is usually set in the password field, something like "d=123456" or "x,d=1233456". Check your pools FAQ.

For litecoinpool whole configuration would be like this:

URL: "stratum+tcp://litecoinpool.org:3333"
USER: "username.workername"
PASS: "pass,d=128000"

Hope it helps!

Hello everyone,

Does anyone know how to set share difficulty on an A4+? I can set pseudo with <address>+x but I get an Invalid Argument error when I try to use <address>/x or <address>/x+y

Thanks in advance!


Title: Re: Innosilicon A4+ setup tutorial
Post by: OldYoungy on March 17, 2018, 09:15:41 PM
It's something that's actually set by the pool. Most (or quite many of them at least) support manual share difficulty which is usually set in the password field, something like "d=123456" or "x,d=1233456". Check your pools FAQ.

For litecoinpool whole configuration would be like this:

URL: "stratum+tcp://litecoinpool.org:3333"
USER: "username.workername"
PASS: "pass,d=128000"

Hope it helps!

Hello everyone,

Does anyone know how to set share difficulty on an A4+? I can set pseudo with <address>+x but I get an Invalid Argument error when I try to use <address>/x or <address>/x+y

Thanks in advance!

Thanks mate, this is for P2Pool mining where passwords are ignored, I have tried the password arguments but to no avail. My mates L3+ has no problem setting both share and psuedo-share but my A4+ is only accepting the psuedo-share difficulty argument (presumably, the pool only shows worker share difficulty stat but the miner accepts the ± argument).

It's not too big of an issue it just reduces my shares per day but when I get a share the predicted payout is larger when a block is found. Although leaving it set to the node default has its benefits if I get lucky with finding lots of shares and blocks within the share lapse period.


Title: Re: Innosilicon A4+ setup tutorial
Post by: OldYoungy on March 18, 2018, 01:40:35 AM
Hello, is it possible to buy 1 control panel?
Where can I find it? and how much does it cost?
Thank you

probably not easy. I have a bunch spare, I can see how much we'd want to sell it for.

Can you please message me with a price for an A4+ control board?


Title: Re: Innosilicon A4+ setup tutorial
Post by: Aepko on March 18, 2018, 03:25:01 AM
Here is a script I wrote to make it easy to add the --api extras.  Just change the xxx.xxx.xxx.xxx to the IP of the miner and make sure to make it s .sh file and give it Permissions to execute as a program.

Cheers...

btw - this was written for linux systems (in case you did not know  ;))


Code:
#!/bin/sh

HOST='xxx.xxx.xxx.xxx 8100'
USER='root'
PASSWD='t1t2t3a5'
CMD=''

(
echo open "$HOST"
sleep 2
echo "$USER"
sleep 2
echo "$PASSWD"
sleep 2
echo "cd /home/inno_py/"
sleep 2
echo "mount / -o rw,remount"
sleep 2
echo "vi -c ':%s@--api-listen@--api-listen --api-network --api-allow W:0/0@g' -c wq /home/inno_py/inno_config.py"
sleep 2

) | telnet

Thanks for this! I don't know why I didn't think of doing that. I edited it to do all 60 of our A4+'s. Saving me loads of effort every firmware update.

It would be super easy for awesomeminer to bypass that. If they could just parse the JSON from http://192.168.1.xx/cgi-bin/temper.py instead of accessing the cgminer API directly, you wouldn't need to modify system files and we'd have system temps as well. Plus you could do POST commands to it to change the pool on the ASIC so it doesn't flip back every reboot. Could also see/change OC and fan speeds.. etc..


Title: Re: Innosilicon A4+ setup tutorial
Post by: tchor66 on March 20, 2018, 09:39:34 AM
Hello AEKPO, how much are you selling the control panel stp?
you have several to sell?
can you contact me by messages?
thank you
(sorry for my english, I'm french lol)


Title: Re: Innosilicon A4+ setup tutorial
Post by: ilostmyface on March 25, 2018, 05:57:32 PM
Maybe someone can help me brainstorm on an issue. I have a A4+ that had 1 chain down day after arrival from Inno. Board would light up green then the light would go out after bootup. Board never hashes. After trying to swap data cables/PSU/firmwares/data ports nothing resolved the issue. I contacted Inno and had the board sent in under warranty and they replaced the board. After swapping the board all 4 boards worked for a few days. Now the exact same board from Inno is having the same issue. Very odd...


Title: Re: Innosilicon A4+ setup tutorial
Post by: OKorator on March 28, 2018, 07:25:33 AM
what a huge f u from innosiicon.

price for an a4+ is now 1180 usd.

bought for 3200; resale value gone!


Title: Re: Innosilicon A4+ setup tutorial
Post by: Cosmictino on March 28, 2018, 08:21:58 AM
what a huge f u from innosiicon.

price for an a4+ is now 1180 usd.

bought for 3200; resale value gone!

yes rly.. i payed too 3200 with a f.. waiting of 5 months.. 


Title: Re: Innosilicon A4+ setup tutorial
Post by: Cosmictino on March 28, 2018, 08:29:25 AM
and the A6 now available for 18.467 LTC ( or 2360 USD; 0.315588 BTC ) min. 3 units .. i  rly hope this minerseller will disappear from market


Title: Re: Innosilicon A4+ setup tutorial
Post by: stianeggum on March 28, 2018, 08:41:49 PM
Ye they are so smart over there at Innosilicon...

I ordered 10 a5s in the new year promotion, payed 30k usd total. and they sent me an mail 2 weeks after the purchase asking me if i wanted to buy a5+ for 4200 each or more A5s for 2100.


21 of may Innosilicon gave me a price that was gonna compensate the pricedrop for the A5 purchase for: A4+ with psu 1900 usd, and now they are selling them for 1180+120 usd for psu, how fucking rude?!?

These people are the worst kind.


Title: Re: Innosilicon A4+ setup tutorial
Post by: yamada-tech on April 01, 2018, 12:05:04 PM
Hi,

I'm thinking of mining altcoin.
Could mining to the local Wallet ?

[A4+ IP] 192.168.1.254
[Wallet innstalled PC IP] 192.168.1.60

[setting1] can not
URL 192.168.1.60:port
Waler user
Pass x

[setting2] can not
URL http://192.168.1.60:port
Waler user
Pass x

 ???


Title: Re: Innosilicon A4+ setup tutorial
Post by: needed357 on April 01, 2018, 06:18:49 PM
awesome miner is showing me x100 more HW error than the miner local page?

wtf??

awesomer miner HW ERROR: 519
miner local page: none 0!


Title: Re: Innosilicon A4+ setup tutorial
Post by: RoosterVT on April 05, 2018, 11:13:16 AM
Good Morning,
I have one hashing board that the green LED goes off after reboot. How are the boards identified by the control board? I did a dmesg from CLI and not sure what to look for. I figure that if all boards are present in dmesg I should be able to see them there. Are there any onboard diag commands I can run?

Regards,


Title: Re: Innosilicon A4+ setup tutorial
Post by: BobbyMartin on April 06, 2018, 01:35:23 PM
I don't know what to try anymore.

I had been running on AwesomeMiner, but it never really worked that well. I'd tell it to switch pools and it would just stayed 'Dead' or 'Disabled'.

Yesterday all 10 of my A4+s got stuck in a boot loop. I can telnet. I can log in. I can reboot, change config, upload new firmware. I can do almost anything... Except it never connects to a pool. It just reboots over and over and all I see are the spinning wheels on the status page. Currently trying to connect to prohashing.


Title: Re: Innosilicon A4+ setup tutorial
Post by: shepardblue on April 07, 2018, 01:48:55 PM
I don't know what to try anymore.

I had been running on AwesomeMiner, but it never really worked that well. I'd tell it to switch pools and it would just stayed 'Dead' or 'Disabled'.

Yesterday all 10 of my A4+s got stuck in a boot loop. I can telnet. I can log in. I can reboot, change config, upload new firmware. I can do almost anything... Except it never connects to a pool. It just reboots over and over and all I see are the spinning wheels on the status page. Currently trying to connect to prohashing.

I had a problem like that with one of my machines and it turned out to be that the machine was not getting enough power. I move the machine to another circuit and it worked fine.


Title: Re: Innosilicon A4+ setup tutorial
Post by: BobbyMartin on April 07, 2018, 04:31:09 PM
That's definitely not the case.

I ended up pointing them to miningpoolhub for the moment. Putting that in and then doing a reboot seemed to fix it. How on earth am I supposed to get AwesomeMiner to work for me? It took all of my miners offline.

Any time I try to set up a new pool profile to switch my ASICs over, the pool just says "dead". I want to solo mine verge on Prohashing or securepayment but this program just doesn't seem to like it.


Title: Re: Innosilicon A4+ setup tutorial
Post by: Cosmictino on April 11, 2018, 01:51:14 AM
That's definitely not the case.

I ended up pointing them to miningpoolhub for the moment. Putting that in and then doing a reboot seemed to fix it. How on earth am I supposed to get AwesomeMiner to work for me? It took all of my miners offline.

Any time I try to set up a new pool profile to switch my ASICs over, the pool just says "dead". I want to solo mine verge on Prohashing or securepayment but this program just doesn't seem to like it.

seems like that its not a miner prob. check your ports on firewall, router or anything else ..


Title: Re: Innosilicon A4+ setup tutorial
Post by: omshree on April 13, 2018, 01:51:08 PM
I changed to --api-listen --api-network --api-allow W:0/0  ,and still AM cannot see the miner


Title: Re: Innosilicon A4+ setup tutorial
Post by: Jroc561 on April 16, 2018, 06:14:13 PM
May have bricked my miner, as soon as power is turned on the fault light illuminates red. No LEDs elsewhere, no fan movement. It does run while the reset button is pushed in, well at least the fans click on, will try to have someone push down the reset button while I attempt to log into the miner console later.

(Tried switching the PSU, No IP is being registered on the router when connecting directly via ethernet)

No TF reader.

May have to send it in or perhaps score a controller second hand...... any other ideas. Wish there was a foolproof hard reboot button like a push in reset for 10-15seconds...


Title: Re: Innosilicon A4+ setup tutorial
Post by: persocra on April 16, 2018, 07:22:51 PM
May have bricked my miner, as soon as power is turned on the fault light illuminates red. No LEDs elsewhere, no fan movement. It does run while the reset button is pushed in, well at least the fans click on, will try to have someone push down the reset button while I attempt to log into the miner console later.

(Tried switching the PSU, No IP is being registered on the router when connecting directly via ethernet)

No TF reader.

May have to send it in or perhaps score a controller second hand...... any other ideas. Wish there was a foolproof hard reboot button like a push in reset for 10-15seconds...

The exact same thing happened to mine. I'm trying to connect via serial cable and figure something out, but please let me know if you come up with something. Innosilicon charges USD 150 + shipping for a new control board, but I'll give the serial cable a go first.


Title: Re: Innosilicon A4+ setup tutorial
Post by: Jroc561 on April 17, 2018, 02:20:38 AM
May have bricked my miner, as soon as power is turned on the fault light illuminates red. No LEDs elsewhere, no fan movement. It does run while the reset button is pushed in, well at least the fans click on, will try to have someone push down the reset button while I attempt to log into the miner console later.

(Tried switching the PSU, No IP is being registered on the router when connecting directly via ethernet)

No TF reader.

May have to send it in or perhaps score a controller second hand...... any other ideas. Wish there was a foolproof hard reboot button like a push in reset for 10-15seconds...

The exact same thing happened to mine. I'm trying to connect via serial cable and figure something out, but please let me know if you come up with something. Innosilicon charges USD 150 + shipping for a new control board, but I'll give the serial cable a go first.

I hate that you are going through the same thing but I’m glad I have at least one mind trying to solve the issue


Title: Re: Innosilicon A4+ setup tutorial
Post by: BabylonTreker on June 08, 2018, 10:55:54 PM
What is a good temp to try and maintain? I feel like mine are running to hot but I'm new to mining.


Title: Re: Innosilicon A4+ setup tutorial
Post by: AltcoinScamfinder on June 28, 2018, 05:17:40 AM
If someone wants to make a DHCP enabled stock latest version of the A4 firmware (SD Image) I will send you $200 in crypto of your choice. If you don't want it public you can DM.

Please and thank you.


Title: Re: Innosilicon A4+ setup tutorial
Post by: tchor66 on June 29, 2018, 01:20:14 PM
Hello, I sell 4 miners A4 + and also 2 miners A8 +
make Offer
thank you


Title: Re: Innosilicon A4+ setup tutorial
Post by: Bitreo on July 12, 2018, 01:28:10 PM
Hi Guys,

sorry but not sure if has been mentioned here but does anyone have the API access details for the Innosilicon D9 miners ?

Regards,


Title: Re: Innosilicon A4+ setup tutorial
Post by: shadowelite on July 24, 2018, 10:59:59 PM
hi I need some help
I got an a4+ g19 and one board went down
so I downgraded firmware working fine all 4 worked,
changed pools a few days later and it came up with 3 boards again
so i reflushed as image and now i have issue
i cant re flush any image even latest one
its stuck on 15%
also in the settings it says its g9 but before it said g19 and board says g19
any ideas?
only flushed .bin , no sd card slot on mine
can i flash via telnet?
thanks


Title: Re: Innosilicon A4+ setup tutorial
Post by: spfan on August 19, 2018, 12:43:53 AM
I really need some help here!  I have 2 Innosilicon A4+ miners.  My router died a couple weeks ago.  I've since replaced it with a new one but neither miner will hash.  I can get to all of the pages in the Miner Status interface, input the mining pool and username/password, etc.  But when I go to the Miner Status page it just spins the "thinking" symbols forever.  Confirmed through the mining pool that it isn't hashing.  There are no fault lights, i've updated the firmware, I'm out of ideas and/or skills and need help.  Please and Thank You!


Title: Re: Innosilicon A4+ setup tutorial
Post by: mvelikov on September 04, 2018, 09:02:20 AM
Hello, I saw the post is about Innosilicon A4+, buy I can't find such one for Innosilicon D9.

I have 2 Innosilicon D9 opened to Internet  (Yes, I know that this is a bad idea) since yesterday when 1 of the miner starts mining for someone else. The password was changed and I cannot login to the miner. Now I am trying to hard reset (reset the firmware) to its defaults. I am trying to to the tutorial from this post, but it is not working for D9. I can connect via PuTTy wit miner IP + port 22 and SSH, but the username and/or password is incorrect. Any suggestions?


Title: Re: Innosilicon A4+ setup tutorial
Post by: mvelikov on September 04, 2018, 01:42:15 PM
Hello, I saw the post is about Innosilicon A4+, buy I can't find such one for Innosilicon D9.

I have 2 Innosilicon D9 opened to Internet  (Yes, I know that this is a bad idea) since yesterday when 1 of the miner starts mining for someone else. The password was changed and I cannot login to the miner. Now I am trying to hard reset (reset the firmware) to its defaults. I am trying to to the tutorial from this post, but it is not working for D9. I can connect via PuTTy wit miner IP + port 22 and SSH, but the username and/or password is incorrect. Any suggestions?

I found it: blacksheepwall <- This is the password for root for D9 and Z9


Title: Re: Innosilicon A4+ setup tutorial
Post by: KhobHosting on September 28, 2018, 04:27:05 PM
i cant seem to connect o the Inno a9 Zmater on port 8100?
anyone know what i doing wrong
telnet ip port


Title: Re: Innosilicon A4+ setup tutorial
Post by: FloDu66 on October 29, 2018, 05:09:32 PM
Hello, I sell 4 miners A4 + and also 2 miners A8 +
make Offer
thank you
Hello,

Does all hashboard all devices work well?


Title: Re: Innosilicon A4+ setup tutorial
Post by: ketyMINING on November 11, 2019, 07:49:53 PM
So I just inherited an Innosilicon  A4+ and updated the firmware after resetting to factory default and cannot get in... What is the right password


Title: Re: Innosilicon A4+ setup tutorial
Post by: hogito on May 03, 2020, 11:25:42 PM
One more trouble: I can not access miner configuration using password 12345678. I'm getting reply that password is wrong. Is it possible to reset this password?

Thank you


UPD: Solved:
telnet to the miner and opened file:
cd /home/www/conf
vi password

password is written there

I tried this and no value returns.  Worked on one miner but not on another.  Any thoughts?


Title: Re: Innosilicon A4+ setup tutorial
Post by: thomasmorrison on May 06, 2020, 08:36:44 PM
When i input " :wq " for save the file inno_config.py i get error "READ ONLY FILE" and i can't save the changes. Any solution?


The sudo command allows you to override the permissions of the file 550 (rxrx-). 
":wq" won't override but ":w!" will.

Note that the purpose of the "!" is to 'force' your command "w".
":wq" doesn't include the 'force' modifier.


Title: Re: Innosilicon A4+ setup tutorial
Post by: T3ch92 on November 11, 2020, 10:40:47 PM
Hi,

Got some A4+ and I want to change freq.

Anyone know if this work?
Telnet into miner.
cd innocfg/www/conf
vi miner.conf

And change freq there from 1044 to 522?

Would be fun to know if underclocking work on A4+, with original firmware, or I need to make custom.

If anyone know a simple way to underclock, please reply  :)

Regards


Title: Re: Innosilicon A4+ setup tutorial
Post by: T3ch92 on November 12, 2020, 01:20:51 PM
It worked to telnet and vi innocfg/www/conf/miner.conf
And change freq from 1044 to 600, so now I can try diff settings, and see if I can get som quiet home solo miners ;)
When freq was 600, fan was in auto and did 30%. Will try to get it down to 10%

Dont know if anyone else here want quiet solo miners, but this is a cheaper way to do it then buying a Apollo miner for $350 or something like that.
Where I am, A4+ goes for $50.


Title: Re: Innosilicon A4+ setup tutorial
Post by: claypaky on December 02, 2020, 05:51:03 PM
a4+_20190312_032956.swu  6750DDF4B654344926B1C66AF09D666D

what is this file ?


Title: Re: Innosilicon A4+ setup tutorial
Post by: mishut on April 28, 2021, 09:09:41 PM
It worked to telnet and vi innocfg/www/conf/miner.conf
And change freq from 1044 to 600, so now I can try diff settings, and see if I can get som quiet home solo miners ;)
When freq was 600, fan was in auto and did 30%. Will try to get it down to 10%

Dont know if anyone else here want quiet solo miners, but this is a cheaper way to do it then buying a Apollo miner for $350 or something like that.
Where I am, A4+ goes for $50.

Hi!
What firmware do you have? What is your hashrate on that 600MHz? And what about power usage?
Im very interested!  :)
I have two L3+@BlissZ on 312MHz@405MHs@550W and now want to make that same thing with A4+. Im curious about about W/MHs


Title: Re: Innosilicon A4+ setup tutorial
Post by: T3ch92 on June 02, 2021, 10:47:27 PM
It worked to telnet and vi innocfg/www/conf/miner.conf
And change freq from 1044 to 600, so now I can try diff settings, and see if I can get som quiet home solo miners ;)
When freq was 600, fan was in auto and did 30%. Will try to get it down to 10%

Dont know if anyone else here want quiet solo miners, but this is a cheaper way to do it then buying a Apollo miner for $350 or something like that.
Where I am, A4+ goes for $50.

Hi!
What firmware do you have? What is your hashrate on that 600MHz? And what about power usage?
Im very interested!  :)
I have two L3+@BlissZ on 312MHz@405MHs@550W and now want to make that same thing with A4+. Im curious about about W/MHs

Hi,
On the A4+ I use factory firmware, that I tune using telnet.

You could tune L3+ also, or use custom firmware.
DM if you want more info :-)


Title: Re: Innosilicon A4+ setup tutorial
Post by: Ilovegold on June 23, 2021, 10:27:04 PM
Has anyone posted how to manually set the fan speed? I am new to trying to telnet mods. I can log in and look around but haven't found any global fanspeed variables.

My miner is doing a weird paradoxical thing since I had to replace a fan where on the miner console page 70% fan speed behaves actually like 30% and vice versa. So my miner thinks it is increasing speed as it heats up but actually reduces fan speed, ie barely moving air at 100% but a jet engine at 30%.

EDIT:

I figured it out. I broke a fan pedal but I now have full fan control.

New problem one of my hashing boards won't recognize. I have no clue why, I fully inspected it and everything is totally intact. But it won't establish it's type or mine.

the "type" says "TYPE_ERR" and the log says "unknown miner !!!" Anyway, I am sure all the chips are fine, but have no clue how to fix it or check it.
Any ideas?


Title: Re: Innosilicon A4+ setup tutorial
Post by: T3ch92 on July 05, 2021, 06:43:57 PM
Does anyone have any idea what this problem might be?  After power on 3 of the hashboards we´re going down in hashing power now they jump back and forth from dead to alive status with 0 H/s hash

Code:
Jul 02 23:03:54 InnoMiner mcompat_lib[1329]: chain0: ERROR - failed to recv spi data
Jul 02 23:03:54 InnoMiner mcompat_lib[1329]: chip clear work false
Jul 02 23:03:54 InnoMiner mcompat_lib[1329]: chain2: ERROR - failed to recv spi data
Jul 02 23:03:54 InnoMiner mcompat_lib[1329]: chip clear work false
Jul 02 23:03:54 InnoMiner mcompat_lib[1329]: chain3: ERROR - failed to recv spi data
Jul 02 23:03:54 InnoMiner mcompat_lib[1329]: chip clear work false
Jul 02 23:03:54 InnoMiner mcompat_lib[1329]: chain3: ERROR - failed to recv spi data
Jul 02 23:03:54 InnoMiner mcompat_lib[1329]: chain3: RESET failed
Jul 02 23:03:54 InnoMiner mcompat_lib[1329]: chain3: power down
Jul 02 23:03:54 InnoMiner mcompat_lib[1329]: chain2: ERROR - failed to recv spi data
Jul 02 23:03:54 InnoMiner mcompat_lib[1329]: chain2: RESET failed
Jul 02 23:03:54 InnoMiner mcompat_lib[1329]: chain2: power down
Jul 02 23:03:54 InnoMiner mcompat_lib[1329]: chain0: ERROR - failed to recv spi data
Jul 02 23:03:54 InnoMiner mcompat_lib[1329]: chain0: RESET failed
Jul 02 23:03:54 InnoMiner mcompat_lib[1329]: chain0: power down
Jul 02 23:03:55 InnoMiner dm-monitor[1316]: ## Error: "watchdog" not defined
Jul 02 23:03:56 InnoMiner nginx[1340]: 127.0.0.1 - - [02/Jul/2021:23:03:56 +0000] "POST /api/auth HTTP/1.1" 200 208 "-" "curl/7.59.0"
Jul 02 23:03:56 InnoMiner mcompat_lib[1329]: chain3: set vid 0
Jul 02 23:03:56 InnoMiner mcompat_lib[1329]: chain3: sleep(6)
Jul 02 23:03:56 InnoMiner mcompat_lib[1329]: chain2: set vid 0
Jul 02 23:03:56 InnoMiner mcompat_lib[1329]: chain2: sleep(6)
Jul 02 23:03:56 InnoMiner mcompat_lib[1329]: chain0: set vid 0
Jul 02 23:03:56 InnoMiner mcompat_lib[1329]: chain0: sleep(6)
Jul 02 23:03:57 InnoMiner mcompat_lib[1329]: API: access denied to '192.168.1.15' for 'privileged' command
Jul 02 23:03:57 InnoMiner mcompat_lib[1329]: BA1 1: invalid nonce - HW error
Jul 02 23:03:57 InnoMiner mcompat_lib[1329]: 1: chip 68: invalid nonce 0xf8627900 !
Jul 02 23:03:58 InnoMiner mcompat_lib[1329]: BA1 1: invalid nonce - HW error
Jul 02 23:03:58 InnoMiner mcompat_lib[1329]: 1: chip 48: invalid nonce 0xad6f8700 !
Jul 02 23:04:01 InnoMiner mcompat_lib[1329]: BA1 1: invalid nonce - HW error
Jul 02 23:04:01 InnoMiner mcompat_lib[1329]: 1: chip 25: invalid nonce 0x8e9ff200 !
Jul 02 23:04:01 InnoMiner mcompat_lib[1329]: BA1 1: invalid nonce - HW error
Jul 02 23:04:01 InnoMiner mcompat_lib[1329]: 1: chip 46: invalid nonce 0xfebaf400 !
Jul 02 23:04:01 InnoMiner mcompat_lib[1329]: BA1 0: Idle for more than 60 seconds, declaring SICK!
Jul 02 23:04:01 InnoMiner mcompat_lib[1329]: BA1 0: Attempting to restart
Jul 02 23:04:01 InnoMiner mcompat_lib[1329]: BA1 1: invalid nonce - HW error
Jul 02 23:04:01 InnoMiner mcompat_lib[1329]: 1: chip 67: invalid nonce 0x8a610601 !
Jul 02 23:04:02 InnoMiner mcompat_lib[1329]: BA1 1: invalid nonce - HW error
Jul 02 23:04:02 InnoMiner mcompat_lib[1329]: 1: chip 47: invalid nonce 0x16381e01 !
Jul 02 23:04:02 InnoMiner mcompat_lib[1329]: chain3: encore fourth mode
Jul 02 23:04:02 InnoMiner mcompat_lib[1329]: chain2: encore fourth mode
Jul 02 23:04:02 InnoMiner mcompat_lib[1329]: chain0: encore fourth mode
Jul 02 23:04:02 InnoMiner mcompat_lib[1329]: API: access denied to '192.168.1.15' for 'privileged' command
Jul 02 23:04:03 InnoMiner mcompat_lib[1329]: recieve notify,we must flush work
Jul 02 23:04:03 InnoMiner mcompat_lib[1329]: New block: 39377ed685d70d9159c5262cc93cfc2ccd34a1313a1da9d2174680fe919c7d74... diff 6.84M

Fan speed can be adjusted in telnet with vi.
Did you figure it out?

When I had same problem with hashboard, I just needed to flash new firmware.

Firmware "update_180622.bin" worked for me :-)
But you could also try "update_180129.bin"


Title: Re: Innosilicon A4+ setup tutorial
Post by: T3ch92 on July 11, 2021, 08:49:50 PM
Does anyone have any idea what this problem might be?  After power on 3 of the hashboards we´re going down in hashing power now they jump back and forth from dead to alive status with 0 H/s hash

Code:
Jul 02 23:03:54 InnoMiner mcompat_lib[1329]: chain0: ERROR - failed to recv spi data
Jul 02 23:03:54 InnoMiner mcompat_lib[1329]: chip clear work false
Jul 02 23:03:54 InnoMiner mcompat_lib[1329]: chain2: ERROR - failed to recv spi data
Jul 02 23:03:54 InnoMiner mcompat_lib[1329]: chip clear work false
Jul 02 23:03:54 InnoMiner mcompat_lib[1329]: chain3: ERROR - failed to recv spi data
Jul 02 23:03:54 InnoMiner mcompat_lib[1329]: chip clear work false
Jul 02 23:03:54 InnoMiner mcompat_lib[1329]: chain3: ERROR - failed to recv spi data
Jul 02 23:03:54 InnoMiner mcompat_lib[1329]: chain3: RESET failed
Jul 02 23:03:54 InnoMiner mcompat_lib[1329]: chain3: power down
Jul 02 23:03:54 InnoMiner mcompat_lib[1329]: chain2: ERROR - failed to recv spi data
Jul 02 23:03:54 InnoMiner mcompat_lib[1329]: chain2: RESET failed
Jul 02 23:03:54 InnoMiner mcompat_lib[1329]: chain2: power down
Jul 02 23:03:54 InnoMiner mcompat_lib[1329]: chain0: ERROR - failed to recv spi data
Jul 02 23:03:54 InnoMiner mcompat_lib[1329]: chain0: RESET failed
Jul 02 23:03:54 InnoMiner mcompat_lib[1329]: chain0: power down
Jul 02 23:03:55 InnoMiner dm-monitor[1316]: ## Error: "watchdog" not defined
Jul 02 23:03:56 InnoMiner nginx[1340]: 127.0.0.1 - - [02/Jul/2021:23:03:56 +0000] "POST /api/auth HTTP/1.1" 200 208 "-" "curl/7.59.0"
Jul 02 23:03:56 InnoMiner mcompat_lib[1329]: chain3: set vid 0
Jul 02 23:03:56 InnoMiner mcompat_lib[1329]: chain3: sleep(6)
Jul 02 23:03:56 InnoMiner mcompat_lib[1329]: chain2: set vid 0
Jul 02 23:03:56 InnoMiner mcompat_lib[1329]: chain2: sleep(6)
Jul 02 23:03:56 InnoMiner mcompat_lib[1329]: chain0: set vid 0
Jul 02 23:03:56 InnoMiner mcompat_lib[1329]: chain0: sleep(6)
Jul 02 23:03:57 InnoMiner mcompat_lib[1329]: API: access denied to '192.168.1.15' for 'privileged' command
Jul 02 23:03:57 InnoMiner mcompat_lib[1329]: BA1 1: invalid nonce - HW error
Jul 02 23:03:57 InnoMiner mcompat_lib[1329]: 1: chip 68: invalid nonce 0xf8627900 !
Jul 02 23:03:58 InnoMiner mcompat_lib[1329]: BA1 1: invalid nonce - HW error
Jul 02 23:03:58 InnoMiner mcompat_lib[1329]: 1: chip 48: invalid nonce 0xad6f8700 !
Jul 02 23:04:01 InnoMiner mcompat_lib[1329]: BA1 1: invalid nonce - HW error
Jul 02 23:04:01 InnoMiner mcompat_lib[1329]: 1: chip 25: invalid nonce 0x8e9ff200 !
Jul 02 23:04:01 InnoMiner mcompat_lib[1329]: BA1 1: invalid nonce - HW error
Jul 02 23:04:01 InnoMiner mcompat_lib[1329]: 1: chip 46: invalid nonce 0xfebaf400 !
Jul 02 23:04:01 InnoMiner mcompat_lib[1329]: BA1 0: Idle for more than 60 seconds, declaring SICK!
Jul 02 23:04:01 InnoMiner mcompat_lib[1329]: BA1 0: Attempting to restart
Jul 02 23:04:01 InnoMiner mcompat_lib[1329]: BA1 1: invalid nonce - HW error
Jul 02 23:04:01 InnoMiner mcompat_lib[1329]: 1: chip 67: invalid nonce 0x8a610601 !
Jul 02 23:04:02 InnoMiner mcompat_lib[1329]: BA1 1: invalid nonce - HW error
Jul 02 23:04:02 InnoMiner mcompat_lib[1329]: 1: chip 47: invalid nonce 0x16381e01 !
Jul 02 23:04:02 InnoMiner mcompat_lib[1329]: chain3: encore fourth mode
Jul 02 23:04:02 InnoMiner mcompat_lib[1329]: chain2: encore fourth mode
Jul 02 23:04:02 InnoMiner mcompat_lib[1329]: chain0: encore fourth mode
Jul 02 23:04:02 InnoMiner mcompat_lib[1329]: API: access denied to '192.168.1.15' for 'privileged' command
Jul 02 23:04:03 InnoMiner mcompat_lib[1329]: recieve notify,we must flush work
Jul 02 23:04:03 InnoMiner mcompat_lib[1329]: New block: 39377ed685d70d9159c5262cc93cfc2ccd34a1313a1da9d2174680fe919c7d74... diff 6.84M

Fan speed can be adjusted in telnet with vi.
Did you figure it out?

When I had same problem with hashboard, I just needed to flash new firmware.

Firmware "update_180622.bin" worked for me :-)
But you could also try "update_180129.bin"

Where can i get those firmwares?  I was looking for older version but with no luck.   

Also the .bin file available on Inno downloads section.  How can i upload it to the minner? Trough the miner status i can only upload SWU files, does not accept a BIN file

And one more thing if you dont mind...Don´t know how to telnet and adjudt fan speeed.  Still showing 10% fan speed.

Thank yu¿ou in advance...   =)



You have the wrong firmware if you only can flash SWU file...
Think you need to flash back with SD card.
You can read more here:
https://www.innosilicon.com/html/support_en/download.html
Click on "Innosilicon A4+ Miner"

The bin firmwares:
www.innosilicon.com.cn/download/update_180129.bin
www.innosilicon.com.cn/download/update_180622.bin

To telnet, you need to type in terminal:
telnet "miner-ip" 8100
example:
telnet 192.168.1.10 8100

username: root
password: t1t2t3a5

then type:
vi /innocnfg/www/conf/miner.conf

There you can change fanspeed with vi editor.
- press "i" to enable edit mode
- change speed
- presss "esc" then ":wq" to save the changes

Not sure if telnet password is the same on the SWU firmware, so you may need to brute force with hydra or something, if you dont flash back to bin firmware.
t1t2t3a5 is the password after 22nd Dec Firmware, innot1t2 is the oldest.

Many of the miners I got from people, because they did not work got "fixed" after flashing back to "update_180129.bin" & "update_180622.bin"

Hope this helped!


Title: Re: Innosilicon A4+ setup tutorial
Post by: gincoin21 on July 12, 2021, 02:01:28 PM
Hello all. Long time user but have never posted.

I recently bought 6 A4+ from alibaba. I knew it was a risk but I got them at a good price. I got videos of the miners hashing at 630+ for each one before shipping. I am using 220 volt power supplies each being 1000 watts or more. The first thing I did was update the firmware on each machine. I immediately noticed that hash boards were missing on the overview page of some of the miners. I did not check the hash boards before updating firmware. Some miners had hash boards present that eventually went away. I went from 4 hash boards initially being down to now 8. I've tried using previous bin files to change firmware on miners which brought back 2 hash boards. Now I am down 6 boards. Two of the miners only accept swu files so I cannot go backwards on the firmware on those miners. Does anyone have a previous swu firmware file to try?

I am hoping to get advice from you guys for a process to go through to diagnose these hash boards to see if they are actually dead or if they can be revived. My supplier has video proof that they worked before shipping and is offering to send me more hash boards for free. I want to keep this guy's trust though so I want to try everything I can before taking him up on this offer. Any help would be appreciated.


Title: Re: Innosilicon A4+ setup tutorial
Post by: gincoin21 on July 13, 2021, 01:44:25 PM
Hello all. Long time user but have never posted.

I recently bought 6 A4+ from alibaba. I knew it was a risk but I got them at a good price. I got videos of the miners hashing at 630+ for each one before shipping. I am using 220 volt power supplies each being 1000 watts or more. The first thing I did was update the firmware on each machine. I immediately noticed that hash boards were missing on the overview page of some of the miners. I did not check the hash boards before updating firmware. Some miners had hash boards present that eventually went away. I went from 4 hash boards initially being down to now 8. I've tried using previous bin files to change firmware on miners which brought back 2 hash boards. Now I am down 6 boards. Two of the miners only accept swu files so I cannot go backwards on the firmware on those miners. Does anyone have a previous swu firmware file to try?

I am hoping to get advice from you guys for a process to go through to diagnose these hash boards to see if they are actually dead or if they can be revived. My supplier has video proof that they worked before shipping and is offering to send me more hash boards for free. I want to keep this guy's trust though so I want to try everything I can before taking him up on this offer. Any help would be appreciated.

I have a very similar problem but with a A4+ LTC master.    How did u flash the bin Firmware?     My A4+ has an alternative control board that doesn´t have a TF card slot and the web interface only accept SWU files.


If you get the firmware please let me know, i been looking around for a while now



I have 2 of the LTC masters I suppose. I ordered 6 A4+ and 4 of them are the normal web interface and use .bin firmware updates but two of them have very different web interfaces and only accept .swu files for firmware updates. The web interface for the LTC master is cleaner and you can tell it is more modern but I cannot find older firmwares to try to get the hash boards to be recognized. I may end up connecting the hashboards and fans from the LTC master into one of my A4+ control boards. My supplier is sending me 6 hashboards to replace the ones that are not working. I was able to get two of them to come back online by flashing the A4+ to an older firmware.

On one of the LTC masters, it shows 4 hash boards and only one is hashing. The other 3 say "alive" next to them but have no hashrate. I don't know what to do with that but will try connecting them to an A4+ with an older firmware to see what happens.


Title: Re: Innosilicon A4+ setup tutorial
Post by: minerwannabe on July 27, 2021, 03:57:09 PM
these are the biggest issues, i have...

In the miner configuration selection, what are your frequency setting at, 1100, 1152 or 1044?

if the hashrates are not at 157 -170 all the time then what does it mean, issues are at somewhere, i cant see to narrow it to make them all run at the same rate.

if a card get the same accepted/rejected shares like one maybe two boards having all the shares and the other do not have any, then what does it mean, issues are at somewhere, i cant see to narrow it to make them all run at the same rate to producing shares.

Does anyone have a solution?


Title: Re: Innosilicon A4+ setup tutorial
Post by: btcstore88x on August 20, 2021, 09:25:44 PM
me too does not access, connection refused


Title: Re: Innosilicon A4+ setup tutorial
Post by: Victorreach on September 06, 2021, 03:14:17 PM
Good day, tell me how to reset the password on the factory one?


Title: Re: Innosilicon A4+ setup tutorial
Post by: Victorreach on September 06, 2021, 03:18:56 PM
For some reason, my password did not change from factory to custom, after a while some hacker climbed up to me and registered his pool and changed the password and I cannot change anything. With the help of the firmware on this forum, it was possible to delete its pools, but the password could not be (((Tell me, can anyone have encountered such a problem


Title: Re: Innosilicon A4+ setup tutorial
Post by: Jon_Bones on April 23, 2022, 06:54:01 AM
Quote
To telnet, you need to type in terminal:
telnet "miner-ip" 8100
example:
telnet 192.168.1.10 8100

username: root
password: t1t2t3a5

then type:
vi /innocnfg/www/conf/miner.conf

There you can change fanspeed with vi editor.
- press "i" to enable edit mode
- change speed
- presss "esc" then ":wq" to save the changes


Hello need help , command list how can open kernel log, one board starts work and after 5 minutes i see hashrate but on pool it didn't mining, in miner interface everything looks great. thank.

root@miner/tmp:
/tmp/log/innominer.log
-sh: /tmp/log/innominer.log: Permission denied