Search content
Sort by
Showing 20 of 35 results by Gazdac2
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
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
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?
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.
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.
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.
Daaaaaamn that's nasty.... suddenly I have the urge to go see my miners as well. 
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.
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
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
From this store
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.
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
From this store
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.
Just got mine fixed also, Guy was helping me install some software thru remote and reboot the System and worked.. like I said Im 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.
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.
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"
ValueError: bad marshal data (unknown type code)
Does anyone have any ideas?
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)
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.
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.
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
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
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
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
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-miningdid 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
which fan should i buy?
if one fan is down
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.
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
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
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.
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.
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.
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.
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.
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~:
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.
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.
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
:)
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.
/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.
Re: [Awesome Miner]- Powerful Windows GUI to manage and monitor up to 5000 miners
Looking for a way to see temps on the innosilicon a4+
e.g. AVG 34/34/34/34
in AM:
https://i.imgur.com/zWV2T8c.jpg
Looks like the API can see it.
Any suggestions of how to either get it populated to the ASIC list? or even just the customize progress bar?
Too bad they didn't stick with the same format as antminer. Can't really find enough documentation to hack it myself.
e.g. AVG 34/34/34/34
in AM:
https://i.imgur.com/zWV2T8c.jpg
Looks like the API can see it.
Code:
PI command: devs
{...
"STATUS": [
{
"STATUS": "S",
"When": 1515017401,
"Code": 9,
"Msg": "4 ASC(s)",
"Description": "cgminer 4.10.0"
}
],
"DEVS": [
{
"PREHT": 0,
"CID": 0,
"CPIDA": 0,
"CPIDB": 0,
"TEMPH": 0,
"ASC": 0,
"Name": "BA1",
"ID": 0,
"Enabled": "Y",
"Status": "Alive",
"TempAVG": 49.33,
"TempMAX": 61.33,
"TempMIN": 36.67,
"CHIP": 72,
"CORE": 648,
"DUTY": 70,
"MHS av": 157.06,
"MHS 5s": 157.22,
"Accepted": 6,
"Rejected": 0,
"Hardware Errors": 0,
"Utility": 1.27,
"Device Elapsed": 284
},
...
{...
"STATUS": [
{
"STATUS": "S",
"When": 1515017401,
"Code": 9,
"Msg": "4 ASC(s)",
"Description": "cgminer 4.10.0"
}
],
"DEVS": [
{
"PREHT": 0,
"CID": 0,
"CPIDA": 0,
"CPIDB": 0,
"TEMPH": 0,
"ASC": 0,
"Name": "BA1",
"ID": 0,
"Enabled": "Y",
"Status": "Alive",
"TempAVG": 49.33,
"TempMAX": 61.33,
"TempMIN": 36.67,
"CHIP": 72,
"CORE": 648,
"DUTY": 70,
"MHS av": 157.06,
"MHS 5s": 157.22,
"Accepted": 6,
"Rejected": 0,
"Hardware Errors": 0,
"Utility": 1.27,
"Device Elapsed": 284
},
...
Any suggestions of how to either get it populated to the ASIC list? or even just the customize progress bar?
Too bad they didn't stick with the same format as antminer. Can't really find enough documentation to hack it myself.
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.Power is good - they're hosted in a data center using Innosilicon PSU
I've submitted a ticket to Innosilicon - see what they say.
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
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."
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
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
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
...
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
...
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.
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.
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'
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
gInnoCmd1Pool = gInnoInitCmdStr
gInnoCmd2Pool = gInnoInitCmdStr
gInnoCmd3Pool = gInnoInitCmdStr
and #comment out the other gInnoCmd#Pool lines
*edit
--if you are only using one pool
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.
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
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.
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'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)