Im lost once I got to the third paragraph... will see if innosilicon gets back to me..

Quote from: Gazdac2 on January 04, 2018, 06:00:35 AM

Quote from: 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
:)

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.

Quote from: 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.

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
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.