Innosilicon S11 powers up but won’t start hashing — what am I missing?

Bitcoin
1

Paul or someone please help!

FINALLY got the two S11s powered up and trying to get one hashing. They’re both running the April 2019 firmware. Fans run and I can get into the web UI, but the miner status page just sits there spinning and never shows a hashrate.

I tried pointing one at PyBLØCK Lotto pool.pyblock.xyz:23112 with a fresh bc1q address as the worker and x for the password. I tested the connection from a laptop on the same network and the pool/port is reachable.

My BLAKE2b node is still syncing, and I haven’t been able to generate an address from it because the wallet RPCs don’t seem to be available in the build I’m running, so for now I’m using a fresh BlueWallet bc1q address.

You mentioned the S11 should work. Have you actually gotten yours hashing yet? If so, what firmware are you running and what exact pool/DATUM address and worker format did you use?

Also, do I even need to wait for my node to finish syncing? At this point I just want to point one of these S11s at something you know works and see it hash. If you’ve got a working S11 config I can copy, that would be perfect.

Thank you.

2

Yes, mine is hashing. I also went through a crazy process to get it working. I don’t know how much of this is needed, but here is the steps:

I also had it running, and it never got up hashing at first.

I decided to do a factory reset. That reset changed the password from “dragonadmin” to “admin”, which took me a while to figure out.

I set Settings > Performance to “Balanced”, saved, and restarted the device

I still wasn’t getting it to hash, so I put in details for a Sia pool and a random real Sia donation address I found online:

Pool URL:
stratum+tcp://sc.f2pool.com:7788

Worker:
26117c19ca3975b315d663dcbbc19cf9c07274f441689d4392ed380b2337589ef1aacfbdc93f.SCBoxII

Password:
x

At some point I read that after a factory reset, it can take up to 30 minutes to tune. So I left it running and came back later. At this point it was mining Sia.

Then I changed the Stratum back to my endpoint (of course yours will be different):
URL: stratum+tcp://192.168.0.2:23337
Worker: s11
Password: x

(I may have restarted the device here, can’t remember)

Then I let it run, and eventually it started mining. It now works fine without having to repeat any of the above steps. The only issue is that any time it stops and then starts up, it takes a god-aweful amount of time warming up or whatever it is doing before it starts mining.

The bad part is that if you get the Stratum settings wrong, it doesn’t error out – it just sits in the “tuning” state forever, no different than it looks normally when starting up, so that is a time killer.

3

Oh, also, mine was rather beat up and used. Two of the hash boards are bad (the seller is sending me two new ones), so probably we should rule out problems with the hash boards on yours too. There should be red lights on the board when they start up. Do you see any patterns of them turning off and/or back on? On mine, it starts with all three red, then one goes dark, then after a while another one goes dark. Then finally the last one goes dark for a short whle, then comes back on. Soon after it starts mining on the one board with just the one red light.

4

Thanks. This definitely helped. I factory reset both of mine and put them on Balanced. Both are doing pretty much the same thing — all 3 red lights come on, fans surge up and down for a while, then all 3 red lights go out together. They’re both still showing tuning.

Do you think getting yours hashing on the Sia pool first was actually the key? Like maybe these things need a valid Sia job to get through that first tune before they’ll work with DATUM?

Also when all 3 boards are good, do you know what the red lights are supposed to do once it finishes tuning? Mine all going out together has me wondering.

And if you know any way to see an actual tuning/error log on these things that would be huge. The web interface basically tells you nothing.

Appreciate the help. At least knowing you actually got an S11 hashing gives me some hope here. Thanks again.

5

Yes, to get the log, go to /logs after signing in. I used Claude to help me determine the two hashboards on mine are bad, so if you have an LLM look at the log it could be useful.

6

Thank you!!!

I’ll pull the log and take a look at it. Mine finally started hashing on the Sia pool at around 5.1 TH/s, so at least I know the miner itself works

What I need help with now is the exact BLAKE2b setup. How did you move yours from Sia over to Bitcoin BLAKE2b? What exact Stratum/DATUM endpoint are you pointing the S11 at, and is there anything special with the worker format or DATUM config for the S11?

Basically now that I finally got the damn thing hashing, I’m trying not to screw with it too much. If you can post your known-good S11 pool settings and what you’re running on the DATUM side, that would save me a ton of trial and error.

One other question — while my node finishes syncing, is there a DATUM/Stratum endpoint I can point the S11 at tonight just to get it hashing BLAKE2b? Either yours or a public one you know works with the S11. Now that I finally have the miner hashing I’d love to get some BLAKE2b work on it instead of letting it mine Sia all night

Thanks again.