Topic: Antminer Z9 mini overclocked - page 2. (Read 26058 times)

htautosjay - it will vary to be honest. With the per-hashboard feature, I've been able to get +5% out of batch2s. That isn't 16k on most, but is an additional 5% from baseline. Tuning takes some work though. Dev fees are disabled until 12/1, so you are welcome to try it on a mini and see.

To tune:

1) Set global frequency to 650. Set each other frequency to "Use Global".
2) Observe your boards for at least 10 minutes, if any drop out, on the next cycle decrease their frequency by 1 step in the pulldown.
3) Repeat this cycle until you have a stable minimum frequency for your boards.
4) To start the 'upwards tuning', choose one board (#1 for example) and increase it's frequency by 1 step.
5) Observe the board for at least 10 minutes to see if it is stable. If it is, repeat #4. If it is not, drop down 1 step and move to the next board.

Going through this process (which hopefully makes sense), you should be able to tune your units for your individual system maximums. It's best to do this with the fans set to 100% so you can remove thermals from the equation -- after which, set the fans back however you want them and see if your boards stay stable. If they do, good, of they don't, eithee decrease freqeuncy by 1 step or increase fan.

Good luck!

Jason

Hi I have missed this thread for a few months.. did i read the above right,,, can we get 16 sols from a batch 2 z9 mini ?
Thanks

Mini support is now available in the Z Series firmware. Please see my other thread for details.

Thanks!

Jason

Guys please. Instead of arguing try to join forces. We've been waiting for Z9 mini FW for way too long. Cracking the voltage control should be the ultimate goal.

Truth; I am not the one who assumed the previous response was an attack, however. And smarty has not been a target; he did his work, acknowledge mine, and I his. that was that. stop comparing yourself to others.

Mine shows 4th just fine, thanks-- this has been commented on by a few so far. And to be fair, I didn't know the answer until your response; at which point I took the time to figure it out myself. So stop assuming, since you are flat out wrong each time you have assumed so far.

If you call that talking down, fine.  Don't threaten me though. rip mine apart, good luck. You'll need help to get through it since you cannot even figure out what the simple shell expansions mean and assumed that shell matches and grouping (example ${foo#bar}) meant correlation in variables inside the firmware. Honestly, I welcome the competition. Please, rip anything past my initial release apart. Let me know when you figure it out because I welcome the awareness on any mistake I made. Don't assume me to be a junior idiot. I can acknowledge mistakes.

I actually apologized to you, took the high road, then you commented that it was a "pissing match" followed by "lame that I...". Grow some, own your mistakes and apologize yourself.

Jason

....snip...

The fan/temp problem lies in cgminer, batch 1 cgminer don't like batch 3 and 4 the best either don't read temp or is wacky temp so taking the batch 3 cgminer and unlocking it and patching it to the batch 1 image gave the over clock options in the web gui. As far as the 4th chain how many are using 4 boards on a mini? The last I checked your versions don't show the 4th chain for the freq selection either.

Other then that no changes needed to be made to make it overclock and working temps/fan for the b3 and 4's.

I already explained what was done when you said you were going to disassemble it so yes it is now a pissing match because you want to sit and act dumb to something you knew the answer to.  All you are looking to do is steer people away from my version which is free and push towards your dev-mode or paid version Bottom line is that it works on ALL mini batches with ALL the intended functions and it is FREE who cares how I got there.

What is lame is how you go and talk down on every fix that has been put out that is free. Mine and Smartass11 have both been your targets. So it is going to be like this from now on, you do your projects and others will do theirs without any talking down on each others work or making accusations. I have visions of what I want to do and you have your own visions, if there continues to be the bs I will rip every version of your images apart and share the info so others can begin to create their own free versions. I have been thru this crap many times over the last 40 yrs so we can all play nice or we can get down to the nitty it your choice at this point.

Was not a pissing match.  Was an honest-to-God question, hence me approaching as "correct me if I'm misspeaking". And I'm glad this is working for you, honestly.

You said it was "cgminer from batch4 firmware in the batch1 image" -- What else was different? The _only_ portion of the image that actually interacts directly with the ASICs *IS* cgminer, so I'm having a hard time understanding what else could have possibly changed. Rephrased: how is what you did any different than just the batch 4 image by itself?

If it was a pissing match, I'd point out that all you did was copy one file.... which tells me there is zero reason that the latest firmware wouldn't just work on all batchX minis. The only other differences in batch1 and "batch4" as you call it from an image perspective is that batch4 added an updated libncurses (and given the opkg configuration, was likely a mistake on bitmain's part), and that the HTML UI was updated to not look for a fourth chain.... So "your" firmware will not work with 4 chains -- at least from a presentation perspective.

Jason

Jason,
Not all batch 3 units work properly with the batch 1 firmware a few later releases of the batch 3 have similar fan or temp issues like the batch 4. Some were shipped with both rev1 and rev2 hashboards., don't know how many were sent out the door that way. Just like some minis may have a rev 1.0.0 controller while others may have a rev 1.x.x. It appears it is about availability and what was on hand during assembly.

Lets not get into a pissing match on every thread I offer the free fix.

chipless, correct me if I'm misspeaking, but don't batch3 units work just fine with batch1 firmware? Is your change not specific to batch4 otherwise?

Jason

I have released a fix for fan and temp issues on batch 3 and 4 units. There is a thread here about it. It does overclock and all the good stuff runs on batch1-4 minis

https://bitcointalk.org/index.php?topic=5073285.new#new

i have got the same problem with my batch 3 mini.
Once i install an other firmware the temperature sensors dont seem to work and the fans always spin on 100%.

Does anyone have the same problem and does anyone have a solution?

Thx!

....
Antminer-Z9-Mini-NAND-500M-201808311812 firmware
blance  Change to blance？？？？？I restarted and restored the default settings. Is it where I am making mistakes?
Or do we set the configuration file to read-only? How can I set it up?

About firmware versions and overclocking:


I've been doing some serious digging!!!


When you login to your Z9 mini you check on first page "System - Overview"
Batch 1, 2 and 3 all seem to have
"Hardware Version:" = 9.0.0.5

"File System Version:" tells you which firmware version your Z9 mini is running on.

There are at LEAST four (4) different firmware versions for z9 mini:

1. Sat May 26 20:42:30 CST 2018 = Antminer-Z9-Mini-201805262047-500M.tar.gz
2. Sun Aug 12 17:43:41 CST 2018 = ? ? ?
3. Thu Aug 30 14:57:48 CST 2018 = ? ? ?
4. Fri Aug 31 17:02:59 CST 2018 = Antminer-Z9-Mini-NAND-500M-201808311812.tar.gz (the now only downloadable fw on Bitmains site for z9 mini.)


May 26 and Aug 12 firmware-versions are overclockable either from SSH into machine and changing the file "/config/cgminer.conf" or from Chrome using "Inspection" for the field where you choose "frequence" (May 26 version) alt. "mode" (Aug 12 version) on page "Miner configuration - Advanced settings" and for the May 26 version ofcourse you just choose the frequence here you wan't just like God intended !


Aug 30 and Aug 31 versions just ignores any frequence value from cgminer.conf or with Chrome's "Inspection" method.
If you go to the "/www/pages/cgi-bin/minerAdvanced.cgi"-file and changes value and saving (after you already made the filesystem writable). After reboot it will have changed the file back!!!


Batch 1 seem to be very overclockable !!!
I, myself, are running my single batch 1 Z9 mini on 768 MHz and it's solid !!!


For Batch 2/3 I have seen quite a few running them on 668 MHz solid with both fw May 26(after upgrade) and Aug 12 firmware's !!!


WHEN you install(upgrade) the May 26 firmware using the page "System - Upgrade" I strongly recommend you UNcheck "Keep settings:" to get as clean install and as little problems as possible.


I really recommend you checkout mining at prohashing.com dispite their "high fee" (not high in relation to what I earn compared to MPH, nanopool and flypool after 48 hours, at least for me and my friends.) Read under "Help" on prohashing.com for further info and earning possibilities if you choose a single coin to hash.)


Howto - Pool settings for prohashing.com: (here you can see mine)
Url : stratum+tcp://prohashing.com:3336
(3336 is for Equihash algorithm that z9 mini calculates)
Worker : imine2
(imine2 is the username I choose to register with at prohashing.com)
Password : n=z9mini101
(I choose the name z9mini101 where the "101" stands for machines ip:10.0.1.101 in my home network and it's just a name to identify your machine for yourself and prohashing.com. Important for them and you if you have more than one machine being able to distinguish each machine.)


May 26 firmware:
File: Antminer-Z9-Mini-201805262047-500M.tar.gz
sha-1: 8791eee569dfff728c8363e5d8fd93f68957a2ee
https://ufile.io/cwnf6 (New link - Uploaded 10 october 2018)
(This link goes to the May 26 firmware which I've shared at Uploadfiles.io and THIS LINK should work for 30 days from october 10, 2018!)


Donations - I hope all my hard work will help up your earnings:

Bitcoin (BTC): 1HY5ZvPvx3fx5iA5cQKjw9ZuArse2STuCb
Litecoin (LTC): LZPmxZdoe8ZNL8av5CkPPBEEBJVdoFQbS6
Zcash (ZEC): t1d35jvkzKcWybpCqojZmgDZkcFC7iBwe8w
Monero (XMR): 48gVGMbZsAD5xtbpEpBKTJiDz6uMrnkTxjMcJGGFtore7i7wckSqmvYKfPVGQGab6U9kK76nGa91fhL SDvPfK4bYKkJaXeW

i have got the same problem with my batch 3 mini.
Once i install an other firmware the temperature sensors dont seem to work and the fans always spin on 100%.

Does anyone have the same problem and does anyone have a solution?

Thx!

I don't think that was a heat problem It looks more of a surge or a short on the chip pins inorder for it to explode out and burn the board like that it would need a full short circuit or surge with good amperage. Heat will brown or discolor the board and the component just fails internally in most cases that I have seen in 30+ yrs of electronics

I decided to test the mini 1 last time before sending it to Bitmain. I tested 1 hashboard at a time and and it turned out 1 of the board was causing the PSU to trip. After opening it up, found the burned hashboard. Mini is hashing fine with 2 good boards now. 3 other Z9s and 2 A9s in the same server case are running fine.





Server Case, it is vented on top with a 1500 CFM QC-ES-1500 fan.

https://file11.bitmain.com/shop-product/firmware/Antminer-Z9-Mini-201805262047-500M.tar.gz

Is from the official bitmain page so you know it has not been messed with.  They kept it on their AWS site but removed the link lol.