Innosilicon releases A9 Zmaster 50ksol/s Equihash miner at 620W

[HagssFIN]

@minefarmbuy
How many pluses can they put in the miner model name?

[minefarmbuy]

@minefarmbuy
How many pluses can they put in the miner model name?

Lol all they like I suppose.

[Solsichu]

think this works..
the password file is here. this is the default.

# cd /
# cd config
# cat web-users.json
[
    {
        "username": "admin",
        "password": "5349d16d5869aa18af565c4c32e4d56916d8ac9d0c5176594cf80b6e07020a3a"
    },
    {
        "username": "guest",
        "password": "b015aa9f37299ed52c30137d447f97b1b176b341145cf7fe5f9a92e89292e8db"
    }
]


editing 101
#vi web-users.json
press
i       -to enter insert mode and edit
esc   - to exit insert mode
:wq! Enter - to save/exit

hopefully this works for you

[mattaero]

Anyone know if the newest firmware allows proper overclocking?  I purchased some used but overclocked A9 zmasters from a chinese farm and they were set to 1425/177 and running between 55k and 60k sol/s but they had the July firmware.

I am hesitant to update the firmware for risk that it might cause chain 2 and chain 3 to lose their overclock, regardless if I change the config.  Can anyone confirm that all three hashboards maintain an overclock with the newer firmware?

Also, anyone know where I can download the old firmware in case I want to go back?

Thanks in advance!

[linkt2]

Regarding overclock, my voltage setting seems to be ignored for chain1 and chain2.

I set the following params in my cgminer.conf:

"noauto": true,
"T1Pll1": "1425",
"T1Pll2": "1425",
"T1Pll3": "1425",
"T1VID1": "175",
"T1VID2": "175",
"T1VID3": "175"

According to the miner logs clock speed is set fine, but the vid is set correctly only for chain0.

Jan 29 11:36:02 InnoMiner mcompat_lib[1327]: chain0: set vid 160
...
Jan 29 11:36:11 InnoMiner mcompat_lib[1327]: chain0: chip0 set pll 0(30MHz) -> 150(300MHz)
Jan 29 11:36:12 InnoMiner mcompat_lib[1327]: chain0: set spi speed 2
Jan 29 11:36:12 InnoMiner mcompat_lib[1327]: chain0: chip0 set pll 150(300MHz) -> 300(900MHz)
Jan 29 11:36:14 InnoMiner mcompat_lib[1327]: chain0: set vid 160 -> 175
Jan 29 11:36:23 InnoMiner mcompat_lib[1327]: chain0: chip0 set pll 300(900MHz) -> 368(1416MHz)
...
Jan 29 11:36:26 InnoMiner mcompat_lib[1327]: chain1: set vid 160
...
Jan 29 11:36:34 InnoMiner mcompat_lib[1327]: chain1: chip0 set pll 0(30MHz) -> 150(300MHz)
Jan 29 11:36:36 InnoMiner mcompat_lib[1327]: chain1: set spi speed 2
Jan 29 11:36:36 InnoMiner mcompat_lib[1327]: chain1: chip0 set pll 150(300MHz) -> 300(900MHz)
Jan 29 11:36:38 InnoMiner mcompat_lib[1327]: chain1: set vid 160 -> 160
Jan 29 11:36:38 InnoMiner mcompat_lib[1327]: chain1: chip0 set pll 300(900MHz) -> 368(1416MHz)
...
Jan 29 11:36:40 InnoMiner mcompat_lib[1327]: chain2: set vid 160
...
Jan 29 11:36:49 InnoMiner mcompat_lib[1327]: chain2: chip0 set pll 0(30MHz) -> 150(300MHz)
Jan 29 11:36:50 InnoMiner mcompat_lib[1327]: chain2: set spi speed 2
Jan 29 11:36:50 InnoMiner mcompat_lib[1327]: chain2: chip0 set pll 150(300MHz) -> 300(900MHz)
Jan 29 11:36:52 InnoMiner mcompat_lib[1327]: chain2: set vid 160 -> 160
Jan 29 11:36:52 InnoMiner mcompat_lib[1327]: chain2: chip0 set pll 300(900MHz) -> 368(1416MHz)


Any ideas? What am I doing wrong?

Did you find a fix?

[VoskCoin]

My review on what the best equihash asic miner(s) are and which one I would pick & why
https://youtu.be/DzqBJb7chG8

[Zingger]

I've been trying to find a solution to this as well. It looks like the latest firmware (b29+_20181023_130635) does not accept higher PLL values (Invalid config option --T1Pll1: Value out of range). It also appears to ignore VID values on chain 2 and 3. They default to 160.

I'm not sure it there will be a work around to this, but I would like to find one.

If you don't care about the memory bug, the extra rejected shares and the lack of xnsub then you could run a ealier firmware.

I personally don't want to go back to an earlier version of the firmware for the reasons stated above. I run a dozen A9's and I'm getting good hash rate from them, but I feel I'm leaving some hashrate on the table due to the overclock limitations.

What I think is that we need to do is find a way to change the cgminer to allow the overclock setting to work correctly.

It seems strange, because when you set the Performance + setting, the VID is 170 on all chains. Seems to me that there should be a way to get around this.

I've dug through all of the spots I could think of and even did some comparing of the cgminer bin file, but I think we need a better linux/coder than me to crack this.

Anyone know someone that could maybe tackle this?

[Gedaskv]

Good day,

What's the best combination of Firmaware+ overlock, to reach stable 50+Ksol on nicsehash?
I'm running 2018 October Firmware, but miner stops working each second day.
Thank you in advance.
BR
Gedas

[Zingger]

The settings really depend on your unit and your power requirements. I use the in following in my cgminer.conf on my units:

    "api-listen": true,
    "api-port": "4028",
    "api-allow": "W:0/0,W:127.0.0.1",
    "A1Fanspd": "90",
    "A1Fanmode": "0",
    "noauto": true,
    "T1Pll1": "1425",
    "T1Pll2": "1425",
    "T1Pll3": "1425",
    "T1VID1": "175",
    "T1VID2": "175",
    "T1VID3": "175"

(Make sure your unit is behind a good firewall, if you open up the API like this!)

With the October firmware, it will ignore the PLL values and the second and third VID values, however, this config does produce good hashrates. You may not want to run the fan at 90 due to the extra power draw, but my experience is that if you can keep the temps right around 50c or below, you get more consistent hashrates.

One trick... Set your unit to performance +, all the way to the right in the GUI. Run it for at least 2 hours. Check which hashboard is giving the best average hashrate. Remove the power from the unit and rearrange the hash cables (small flat orange and white ribbon cables) to put the best hashing board as the 1st one. Reconnect your power and then go adjust your cgminer.conf file. This will get you a bit better hashrate because your best board will be running at a higher performance setting.

One other note. I recommend using a Bitmain APW3++ power supply... I've had some issues with any others and if you have the option, it seems to be the best for consistent results.

I use Awesome Minner to monitor all of my rigs. This allows me to set rules based on hashrate. For example with the A9, if the accepted shares are above 400 and the hashrate is drops below 45, I have it restart the A9. I also have a rule that says if accepted shares are above 3000 and the hashrate drops below 50, I have it restart. In this way I can maximize the hashrate and not worry about them. Awesome Miner is free for up to 2 rigs, so you can give it a try without cost. You can also use it to do profit mining (switching to different coins/pools based on profit).

If you are not comfortable with using that software (which I understand), then the next best way to solve that issue is to optimize the unit by tweaking the performance settings to get the best hashrate and then either setting up a automatic restart with power outlet device or do a manual restart once a day. On Nicehash, due to their fluctuation, you almost have to have someway to do this, since leaving it just run will eventually cause you to start being less profitable or worse.

I've run my A9's on many different pools, but using the strategy above on Nicehash is currently providing my best profitability.   

Hope this helps.

[Gedaskv]

The settings really depend on your unit and your power requirements. I use the in following in my cgminer.conf on my units:

    "api-listen": true,
    "api-port": "4028",
    "api-allow": "W:0/0,W:127.0.0.1",
    "A1Fanspd": "90",
    "A1Fanmode": "0",
    "noauto": true,
    "T1Pll1": "1425",
    "T1Pll2": "1425",
    "T1Pll3": "1425",
    "T1VID1": "175",
    "T1VID2": "175",
    "T1VID3": "175"

(Make sure your unit is behind a good firewall, if you open up the API like this!)

With the October firmware, it will ignore the PLL values and the second and third VID values, however, this config does produce good hashrates. You may not want to run the fan at 90 due to the extra power draw, but my experience is that if you can keep the temps right around 50c or below, you get more consistent hashrates.

One trick... Set your unit to performance +, all the way to the right in the GUI. Run it for at least 2 hours. Check which hashboard is giving the best average hashrate. Remove the power from the unit and rearrange the hash cables (small flat orange and white ribbon cables) to put the best hashing board as the 1st one. Reconnect your power and then go adjust your cgminer.conf file. This will get you a bit better hashrate because your best board will be running at a higher performance setting.

One other note. I recommend using a Bitmain APW3++ power supply... I've had some issues with any others and if you have the option, it seems to be the best for consistent results.

I use Awesome Minner to monitor all of my rigs. This allows me to set rules based on hashrate. For example with the A9, if the accepted shares are above 400 and the hashrate is drops below 45, I have it restart the A9. I also have a rule that says if accepted shares are above 3000 and the hashrate drops below 50, I have it restart. In this way I can maximize the hashrate and not worry about them. Awesome Miner is free for up to 2 rigs, so you can give it a try without cost. You can also use it to do profit mining (switching to different coins/pools based on profit).

If you are not comfortable with using that software (which I understand), then the next best way to solve that issue is to optimize the unit by tweaking the performance settings to get the best hashrate and then either setting up a automatic restart with power outlet device or do a manual restart once a day. On Nicehash, due to their fluctuation, you almost have to have someway to do this, since leaving it just run will eventually cause you to start being less profitable or worse.

I've run my A9's on many different pools, but using the strategy above on Nicehash is currently providing my best profitability.   

Hope this helps.

Thank you for your reply. What FW version you are using and what mining pool?
Thanks in advance.

[Zingger]

b29+_20181023_130635

Currently Nicehash pool.

I've seen lots of folks mining using the July Firmware and higher VID & PLL settings, but those don't work well on Nicehash. The settings I stated before are currently yielding my best results.

[dsmn]

Did anyone order the new A9++ ?
What should i expect, sendt them coins half a week ago, and no confirmation on payment or anything yet.
Used the official site at https://www.innosilicon.com/html/miner/index.html

[Asterixrus]

Hi! Who can get a new root password from the 2019 firmware for Innosilicon A8+? Support denied.
http://www.innosilicon.com.cn/download/a8+_20190403_034116.swu
I think that for the new A9++ it will be the same.

[Phuripat]

Hi

New Firmware fo A9 Zmaster is released.

b29+_20190419_062649.swu  3431F7AD7A47B2C27FF8C0C7627D4F5A
https://www.innosilicon.com/html/support_en/download.html

Anyone tested it ? What are the differences ?

Thanks ...

More hashrate more stable like A9 upgraded.. 55-60ksol

[jeffpcyo]

I did found the originals links for the firmware of the Innosilicon A9:

The one I got when it got ship and oldest I know of :
http://www.innosilicon.com.cn/download/b29+_20180802_092136.swu
An firmware version that many talk about :
http://www.innosilicon.com.cn/download/b29+_20181023_130635.swu

The version that every one hate for ssh :
http://www.innosilicon.com.cn/download/b29+_20190419_062649.swu

Hope it help, have a good day!

[jeffpcyo]

The hashed password with both files combined is :
root:$6$JxiwJEDHq0mEKJQ$scMTBRi95vb6/JQvcTW8LakIMgHQuUieuqIw8gpndSg3DDMW96r5LsuYSjj2d.gqD9NhRgq9VD/5LzmbIjKYy.:0:0:root:/root:/bin/sh
if some one wants to try

For now I made an compilation of all version I found of the firmwares of the Innosilicon (Only for the A4+ A5 and A6 the files G9_R1.2.zip and G19_R1.2.zip can't be distributed on Github)
https://github.com/jeffpcyo/asic-firmware
If you know other versions you can tell me and I will add them, all of those versions came from the official website as if you know the file you can force the download

Hope it helps, on the Github I wall add other ASICs over time

[typerc]

The hashed password with both files combined is :
root:$6$JxiwJEDHq0mEKJQ$scMTBRi95vb6/JQvcTW8LakIMgHQuUieuqIw8gpndSg3DDMW96r5LsuYSjj2d.gqD9NhRgq9VD/5LzmbIjKYy.:0:0:root:/root:/bin/sh
if some one wants to try

For now I made an compilation of all version I found of the firmwares of the Innosilicon (Only for the A4+ A5 and A6 the files G9_R1.2.zip and G19_R1.2.zip can't be distributed on Github)
https://github.com/jeffpcyo/asic-firmware
If you know other versions you can tell me and I will add them, all of those versions came from the official website as if you know the file you can force the download

Hope it helps, on the Github I wall add other ASICs over time

your missing these 4 for the A9
b29+_20180720_152600.swu
b29+_20180828_062024.swu
b29+_20180911_095547.swu
b29+_20181009_094439.swu

[supersemoule]

Hi all,

Does anyone know if there is safety if the miner is warming up or if the fans stop working ?

Happy mining !

[Solsichu]

Hi all,

Does anyone know if there is safety if the miner is warming up or if the fans stop working ?

Happy mining !

This is along the lines of what I came to post about. So heres some info from when I made a stupid mistake.
After taking pics of my boards, forgot to plug in the fans  Found out the blades will shutdown at high temperature.
I think they restarted when they cooled off and then overheated and shutdown again in a cycle. But it was a while ago.


So, I came to share, for the sake of science, my much bigger and more recent mistake. Since the current firmware restricts or is bugged to only adjust VID voltages for Blade #1/3. I was investigating a hardware solution todo this. I believe I found the VID control point. Put while trying to de-solder and raise the Pin in the chip, it broke it off 

I tried to daisy chain 1 blade to the other but both didnt work and I got really scared and backed off this idea. The other blade was fine after being disconnected. I tried for 2 week to recover the pin but it wasnt meant to be. Then I said fuck it. Tied my point right to 3.3V. Bam, blades working again! Under Debug, Vol(voltage) is at a whopping 1050 (1.05V). Its running at 65C w/ %80 fan. With Blade 1 Vid 175, Blade 2 Vid 160 (no control) and Blade 3 Vid 255 (assumed equivalent) im drawing a whopping 950W!! lol. for what seems like 1k/sol more  , but im going to run it the night and see how things even out. Ultimately I want to get them all running VID 175ish at a good frequency and see what the Unit does as a whole.

I will have to try daisy chaining again because I think I may have had a bad connection. If not I guess ill use an Arduino or something to control the VID. Hopefully it survives my reckless decision to run it at max for a bit 

[OrionX]

Nice.  I hope it survives as well.  Makes for a fine datapoint we might all someday rely upon if we decide to do something like that ourselves.

Thanks for mentioning it.  Cheers!