Topic: Z9 Mini all batches 1-4 Unlocked with working temp, fan, Overclock NO Dev-Fee - page 2. (Read 1379 times)

Yeah, the V9 utilizes the same ASIC design as the S7, Bitmain just ordered a new run of those chips under a new model number for whatever bizarre reason. Fundamentally impossible for it to handle equihash at the core level, nevermind the fact that there isn't any DRAM present either.

Just for a point of clarity, I did not say that it is an issue some have seen after an upgrade. I said "I cannot see how this would happen", which is very different.

Are you saying your plan is to take a "v9 hashboard" and make it do "equihash" as a Z9?... I'm just going to assume you are trolling at this point and get off of the chipless train. An ASIC cannot be repurposed like that.

Jason

Glad you got it working. As Jason said it is an issue some have seen after an upgrade. My brother has the same issue on a couple of his after an upgrade of fw..

I am far from an expert on these units and hopefully we can all learn as we move on.

I am looking into trying to port the V9 hashboards to work on z9 machines.....But that is a project that will take some time that is even if it is possible. So I may steer away from this project. If it is possible to do what I want a V9 should produce as much as 3 z9's if it is possible.


Jason you have any thoughts on porting the v9

You could try mine, but try it on just one to make sure it works for you first.

Jason

Thanks Jason, you are kind, but i did the V9 reset and its working for me, now im looking for at firmware to unlock the freq.

I’m on the road at the moment, but I am willing to try to help via team viewer at some point if you would like.

Have you tried ssh or just http?

chipless, trying to help with this response regardless what you may think....

I have not tried chipless' firmware, but the default http login is root/root and the default ssh login is root/admin. If the password is changed via the web interface, then the ssh and web logins are synchronized.

I disagree with the comments on this being network issues (ignoring IP changes) or browser caching -- that simply doesn't happen for HTTP Authorization requests.

If you do a _full_ factory reset using the V9 procedure, the MAC address on the unit will change and your router will assign a new IP address (Incidentally, I've had the instructions on this recovery at the bottom of my first post on the firmware thread from day one for worst-case scenarios).

Unless something has changed since the version of chipless' firmware I looked at, I'm going to agree with him and say I cannot see how this would happen. If you install firmware with the 'keep settings' unchecked, all configuration is removed except for the MAC address (which means IP address is likely to stay the same, even if using DHCP; this is part of my disagreement on the network issue comments).

If we assume that the passwords are out of whack for whatever reason, then yes, the V9->Z9 recovery process will work, 100%. Personally, I'd try to look at the ssh login and see if root/admin works (and root/root, in case something wacky has happened).

@chipless - in this scenario, I've worked with the users via teamviewer to understand and resolve the issues. That may be an option if you can get one of these users to work with you. Does not take long and goes a long way towards customer satisfaction as well as knowledge gained.

@Kunolyb -- I do not completely understand your response. smarty's firmware is for the Z9 and chipless' firmware is for the Z9Mini. How and why would you have upgraded from smarty's to this one?

Thank you,

Jason

Thanks man, i will try it when i get home good job - and i think i will stay away from the firmware, despite the wonderful effort making it, but its not for my machines. 5 with that firmware and 5 not working. But Thanks anyway

I found a solution to the problem, I have already restored my z9 mini

https://support.bitmain.com/hc/en-us/articles/360006020914-V9-Z9-Mini-Control-Board-Program-Recovery

So if you had a static ip it would default back to dhcp mode which the router then may assign a new ip to it. I had weird issues with that on the stock firmware also. You may need to reboot your router to clear its cache and show the correct ip so you can access it. Or you can download the ipreporter software from bitmain's support area and run it then press the ip report button on the front of the miner control box it will send the correct ip to the software so you can verify it. Also the reset button is in the small hole on the front while the miner is running press a pin into it for about 10-20 seconds ...you will see red and green light flash.  This is still the may firmware with the cgminer replaced which has no affect on logging into it that is why I don't understand how you are locked out of it. There is no possible way the software I released can lock you out. I do know if you have it in a DMZ zone on your router you can get locked out and you have to reset it with the reset button. I don't know why this can happen I found that weird crap on the stock firmware when I was accessing it remotely. Don't know if bitmain somehow accessed it then or hacker but none of the default passwords would work until I did a reset by the front button then a few hours later it would happen again finally I took it out of the dmz zone.

right after your firmware, I started requesting a login and password ... and before the firmware I removed the tick "Keep settings:", that is, everything should have been on the standard settings

Before this was the May firmware bitmain

Goodmorning. So the upgrade have been made from Smarass´s firmware ind it have been working flawless until i installed this firmware, it started fine, i adjusted the overclock a little and nothing was wrong, log on worked no problem right after upgrade, then i turned off the computer and went to work came back turned on the computer and it asked for the user and password, normal it just auto log on, so i tried all the things you have written og more, even a new computer, smartphone and tablets. so next step, reset, reset and another reset then factory reset, factory reset and last another factory reset, the same result. went on bitmain site to be sure that´s its done correct, and i´m sure it was the wright way. so, after factory reset the old ip is gone and a new has come up, so im on the network and i can see the unit is reset due to i not hashing on my pool, i can find the unit on the network and i also come too the log on screen but nothing i plug in is working. (Sorry for my english i´m Danish ) Hope this makes i a bit cleare.   

That is a network issue of some sort. The router isn't getting the data it should be. What batch mini are you trying it on? and What version of the firmware did you last load to it?

I tried different browsers, in the list of clients of the router ip has not changed, the name of ASIC has changed from antminer to Unknown

When you try to login what does it do?  Also check your units IP to make sure it didn't change unless you had it set to static ip. Otherwise I don't know why you are not logging in. The only thing changed was cgminer and it has nothing to do with the units login or web gui. Sounds like a ip or a pc browser issue. All the login credential were never touched everything is factory user and passwords. Bitmain has a utility called iPreporter that you can run on your pc then you press the ip button on the unit and it will send the ip to the reporter or you can look for it under devices in your router  One of the first posts the user says it works fine so I don't know

nothing helps ... maybe your login and password are in the firmware?

the fan works 100%, even though it was standing on my machine, and the red light flashes as if there is no Internet.

Password is same as default user/pass  root  and  root  if you cant login clear your browsers cache. If you need to reset it press the reset for 10 seconds.   I don't know know why you cant login nothing was changed that would effect the login or a factory reset. If you changed your password on the unit before the upgrade then you would use that password.

bad things
so whats the problem? we were thrown?