The only one on bitmain homepage:
Antminer-Z9-Mini-NAND-500M-201808311812.tar.gz
I tried both, keep settings and also unchecked it.
Did it several times and tried every combination.
the only tiny success:
installing batch 2 firmware --> change to turbo --> keep settings ---> install original firmware
Result: 550 frequency + working temperature sensor + working fan
sadly this trick does not work with batch 1 firmware and (e.g.) 650 frequency.
Keeping setting and reverting to batch 3 firmware resets the frequency to 500.
please link with bacht 2 FW 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. Who has been "messing with" images? Here are the md5sums of the image you linked to, and the one I host: # md5sum antminer-z9-mini-201805262047-500m.tar.gz 0682b350dd8b53d62a11231d16d133a7 antminer-z9-mini-201805262047-500m.tar.gz # md5sum Antminer-Z9-Mini-201805262047-500M.tar.gz 0682b350dd8b53d62a11231d16d133a7 Antminer-Z9-Mini-201805262047-500M.tar.gz You will note they are the same. Jason |
|
|
|
I just want to say great work here Efudd. I am stable at 675 now for 2 days with fans at 75% running at 69oC. I did want to point out one thing about your "10 minute" mining.. If pool 0 is dead, my miner keeps mining for you, doesn't come back after the first 10 mins. Not sure if you knew about it or not. Thanks again for your hard work.
zx10r07 - In your scenario, was pool0 working and then went offline? Or were you just using pool1 or pool2 and did not expect pool0 to work? Thank you, Jason Ok, I've reproduced this and I know what is happening. I'll work on fixing this, but for now, it can be worked around by not having a dead pool0. Thank you for reporting it. Jason Alright, this is fixed in version 2.0d, which is live now. Thank you again for reporting this. Jason |
|
|
|
I just want to say great work here Efudd. I am stable at 675 now for 2 days with fans at 75% running at 69oC. I did want to point out one thing about your "10 minute" mining.. If pool 0 is dead, my miner keeps mining for you, doesn't come back after the first 10 mins. Not sure if you knew about it or not. Thanks again for your hard work.
zx10r07 - In your scenario, was pool0 working and then went offline? Or were you just using pool1 or pool2 and did not expect pool0 to work? Thank you, Jason Ok, I've reproduced this and I know what is happening. I'll work on fixing this, but for now, it can be worked around by not having a dead pool0. Thank you for reporting it. Jason |
|
|
|
I just want to say great work here Efudd. I am stable at 675 now for 2 days with fans at 75% running at 69oC. I did want to point out one thing about your "10 minute" mining.. If pool 0 is dead, my miner keeps mining for you, doesn't come back after the first 10 mins. Not sure if you knew about it or not. Thanks again for your hard work.
zx10r07 - In your scenario, was pool0 working and then went offline? Or were you just using pool1 or pool2 and did not expect pool0 to work? Thank you, Jason |
|
|
|
I just want to say great work here Efudd. I am stable at 675 now for 2 days with fans at 75% running at 69oC. I did want to point out one thing about your "10 minute" mining.. If pool 0 is dead, my miner keeps mining for you, doesn't come back after the first 10 mins. Not sure if you knew about it or not. Thanks again for your hard work.
zr10r07 - Ah, crap. Someone else had a similar issue, but they had a "unique" way of handling pool management and I could not readily discern the cause or directly reproduce it. I will test this later today and releases a "d" version when I can reproduce and fix it. Thank you, Jason |
|
|
|
efudd I wrote you a PM offering you help. Check it out!
Ok, thank you. -j Ur welcome mate....but you didn't answer  I also have pictures of batch 1&2 boards ready for you... Ok - I will get through my PMs later this weekend. Thank you, Jason |
|
|
|
how is everyone doing with this firmware?
I may be wrong, and I definitely have a personal bias here, but I think many are using my firmware after having issues of various sorts with this one. If you have a different experience, please do share! Jason |
|
|
|
efudd I wrote you a PM offering you help. Check it out!
Ok, thank you. -j |
|
|
|
Really appreciate your hard work. I messaged you regarding the unlocked version I received. As far as batch 1 z9. I tried a little research of my own by taking the control board from my 750 hashing batch one mini and placing it on the batch 2 mini and the same issue existed where the hashing would go to zero after some time and could only handle 650 at times. So not sure what they really changed with batch 2 as I assumed all config were stored on the control board.
Thanks
I responded to your PM re: unlock/Z9. My understanding, and note I never had a Z9 batch2+ myself - my 12 were all batch1, is that the Batch2s had a hardware change. From the pictures I saw, my best guess is 2 VRMs (voltage regulation modules) were removed which limited the power distribution ability to the boards. Again, just a wild guess. -j Hey guys. Just for making things clear. Z9 mini Batch 1 and 2 hashing boards look basically the same to me. I can provide photos of both batches boards front and back. fliperone, that'd be awesome. Thank you. -j |
|
|
|
i have batch 2, would it matter or the FW will work as batch 1 z9's ?
Thank you. It will work with any when i'm done. I may have something lined up now. Jason |
|
|
|
Does anybody know if we need to upgrade our miners for the Zcash sapling fork? I am still on one of the good pieces of firmware but if I am unable to mine Zcash that will be an issue. (I mine NiceHash anyway but it is possible that I could be mining Zcash) So does anyone know if a firmware update is required? Also as for the memory problem Y'all remember when I was talking about HiveOS on these ASIC's? I talked with the Dev and he has implemented a reboot cron timer on it, for either the ASIC or the Miner software. https://github.com/minershive/hiveos-asic You can see how to enable the reboot command down below. They also have a bulk tool installation. Do keep in mind it does take a while to install on the ASIC (About 4-5 minutes) and once you have all of your ASIC's on Hive you can initiate the command all at once for all of your ASIC's. They will all appear as offline but come back after about 15 minutes but they will keep mining and after that is done you have no need to worry about the memory leak error as it will reboot the ASIC every 24 hours. I have not had a problem with the memory leak since I initiated this command. I recommend that y'all do the same. I believe only "nodes" need to update for sapling. Miners are fine to the best of my awareness. -j When are you gonna pimp our ride?  lol... I'm unsure if this ride can be pimped, but stay tuned! -j |
|
|
|
|
Folk,
I should have the mini variant out soon. I have the majority of it ready, I just need to get it tested.
Thank you!
Jason
|
|
|
|
Does anybody know if we need to upgrade our miners for the Zcash sapling fork? I am still on one of the good pieces of firmware but if I am unable to mine Zcash that will be an issue. (I mine NiceHash anyway but it is possible that I could be mining Zcash) So does anyone know if a firmware update is required? Also as for the memory problem Y'all remember when I was talking about HiveOS on these ASIC's? I talked with the Dev and he has implemented a reboot cron timer on it, for either the ASIC or the Miner software. https://github.com/minershive/hiveos-asic You can see how to enable the reboot command down below. They also have a bulk tool installation. Do keep in mind it does take a while to install on the ASIC (About 4-5 minutes) and once you have all of your ASIC's on Hive you can initiate the command all at once for all of your ASIC's. They will all appear as offline but come back after about 15 minutes but they will keep mining and after that is done you have no need to worry about the memory leak error as it will reboot the ASIC every 24 hours. I have not had a problem with the memory leak since I initiated this command. I recommend that y'all do the same. I believe only "nodes" need to update for sapling. Miners are fine to the best of my awareness. -j |
|
|
|
A feature that would help my wife at night would be:
On network loss the fans don't max out
On server loss same issue with fans
On reboot/restart same issue with fans
oh did I mention any help on the fans would be great...LOL
I am being sarcastic...I get yelled at about 30 times a week from the wife
about the fans when I am playing around with it. Other then that the rebooting
has stopped.
I do have a question about the cgminer recompile, in all other versions factory and mods
I had cards randomly show x for an asic then disappear later back to normal in your version
I don't seem to have that issue with the same settings was this an api issue that you fixed or
something else might have changed that issue
Thanks
Definitely heard on the fans.... As far as cgminer goes, I want to be clear that this is not a recompile. I wish it were as this would be 1000 times easier. As far as ASICs disappearing, that I cannot explain for you at this time. I have not personally seen individual ASICs "x" out and would consider that a problem, I think... at least without any other knowledge. I have not changed anything related to that, at least. I definitely would not expect that to be an 'api issue' regardless of the firmware, but rather a real indication of something to investigate (chip at too high of a frequency, perhaps?). Thank you, Jason |
|
|
|
Could you please add one more feature related to fans? When Customize the fan speed percentage is ticked and set to 0%, all fan detection/monitoring should be disabled or at least ignored. A little bit of background, so because of the noise, people are trying to use no standard fans with fan simulators. Fan detection on Z9 controller gets burned easily by messing up middle pins on fan connector and controller becomes unusable, throwing something like no fan detected, everything else on controller seems to be working fine. So by adding this feature, there will be no more need to purchase fan simulators/spoofers, and everyone that has burned fan detection on controller, will be able to use that controller again.  This sounds reasonable and something I can look at in the initial fan work. Jason |
|
|
|
Hi again, I've had the problem a few other times even while using the firmware above. The workaround below slipped my mind a couple weeks ago when I rebooted my miners. Within 24 hours I had an abuse report presented to me by the datacenter ops for an ip (miner) of mine participating in an NTP attack against some ip in some other datacenter. Heres my solution: Since the data in the antminer's /config/ directory is persistent through reboots, I ssh into the antminer and stored an .sh file there in the config directory. vi /config/ntpconfig.sh echo "restrict -4 default kod notrap nomodify nopeer noquery" >> /etc/ntp.conf
echo "restrict -6 default kod notrap nomodify nopeer noquery" >> /etc/ntp.conf
/etc/init.d/ntpd restart save/exit :wq of course you may need to add execute privilege chmod +x /config/ntpconfig.sh So now I can just ssh into my miner after it reboots and run the /config/ntpconfig.sh program Of course automating it even further would be ideal and I've attempted that below. Meanwhile I'm working through terminal on a Macbook (i know shhhh you all) You could of course set up ssh keys and use the default terminal ssh program through mac and send the command over automatically. BUT! as soon as you reboot those ssh keys will be overwritten and the Mac ssh program doesnt allow passing the password along as an argument. sshpass works on ubuntu also So I used https://gist.github.com/arunoda/7790979 to install "sshpass" which will do just that. Now I've made a .sh file on the mac that calls the sshpass program, logs into the miner, tells it to run the little config program which mods the NTPconfig and restarts NTP. nano restartNTP.sh sshpass -p <mypassword> ssh -o StrictHostKeyChecking=no root@<myminerIPaddress> "/config/ntpconfig.sh” of course you may need to add execute privilege My next task will be setting this to run as a cron job so it does this maybe 2x daily in case a miner randomly restarts! That or I might get fancy and make a cron job that just reboot my miners daily (so they stop hogging bandwidth as they seem to do after running for a long time) and when they reboot it'll patch the NTP. what a pain in the ass, hope this finds anyone who stumbles here well. Take care! Ok, I took the image above "L3-201804241834-384M" and simply added support for /config/rc.local to it. If /config/rc.local exists, it is sourced on boot. That said, I DO NOT HAVE AN L3, so this image is UNTESTED.. please do not try it unless you know how to recover from a failed flash.... I've checked, doublechecked, sanity checked, and I think everything is ok, but I cannot be 100% certain. There is one oddity in the naming of the uBoot image that I spent some time trying to understand and ultimately decided was likely accidental noise in bitmain's build process... or it might be something that causes this image to fail flashing..... so use it at your own risk. ... And if it works, please let me know. I'll provide the link here and will not link it on my growing master firmware page until I can get some confirmation that this functions as expected. http://releases.broked.net/Antminer-L3-201804241834-384M-rclocal.tar.gzThe only change is: if [ -f "/config/rc.local" ];
then
. /config/rc.local
fi
in bootmisc.sh Thanks, Jason |
|
|
|
|
It would be relatively easy to modify this firmware to support a custom init script in /config that is persistent.
I'll give it a shot in a few minutes, assuming the firmware link above is correct.
Jason
|
|
|
|
|
Folk,
I made a mistake in the "2.0b" image that I have since corrected. However, it looks like there were approximately 8 downloads during that time window. If you are running 2.0b and you are having an issue with cgminer "restarting for no reason", please re-download the updated image and apply it.
I apologize for this mistake and will strive to not try to rush a fix out the door next time around.
Thank you,
Jason
|
|
|
|
I tried it on my z9 with 4 hash boards and the 4th don't show in the web gui so I cant control it unless I change the global to what I want board 4 running at then set the other three manually in the web gui
chipless, yeah, that is a reasonable way to handle that condition. I had not tested that since I only have 3 hash boards. Updating their web interface can be done, but it is ugly 'code'. jason |
|
|
|
|
Show Posts
