The firmware is stolen from Bitmain and slightly modified to have Blackminer name and images... highly suspect
The firmware is an open source and we modified it. Ok, but unless I'm mistaken, no one who has "trialed" has seen any return. So... I don't want to use a 4 letter word, but what is the explanation for that? Jason |
|
|
|
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 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#newchipless, 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 |
|
|
|
|
This didn't need another thread. Were I a moderator, I'd ban this into oblivion.
Jason
|
|
|
|
The firmware is stolen from Bitmain and slightly modified to have Blackminer name and images... highly suspect
You lost me at "stolen from Bitmain" considering Bitmain is in violation of the GPL and has technically stolen from all end-users as a result. Otherwise, I also believe this project is suspect, but for different reasons. Jason |
|
|
|
Cheers  Fixed? |
|
|
|
Hi,
I used this software and my 3rd chain is missing?
I tried loading up default firmware and the chain is still missing?
Thanks
Hi. Then the problem is not the firmware. That said, turn off miner. Reseat all power connectors and the data cables between the control board and the hash board. See if problem persists. If so, swap control and power cables between boards 2 and 3 to isolate whether it is the board or the cable or power. A simple set of logical steps will let you isolate the hardware component. Jason |
|
|
|
The reason is clear. Lack of power supply. For frequencies above 750, it is necessary to increase the power supply to at least 0.9V with appropriate cooling of the chips and PWM drivers. At a frequency of 750, the chips work and do not fall off, but due to internal errors, the hashrate drops
i have batch 1 running on 750Mhz, are u suggesting that goign above has no sense as the hash will drop due to not enough power? My batch 1's run at 762 anything higher it loses hashrate but does not error so I know they can handle higher. I ran it as high as 800 but 1 board dropped within a few minutes. You also have to follow the clocking pattern it seems to go in intervals of 6 with the exception of a few where it jumps 7 Ends in 3 or 8, +7. Otherwise +6 |
|
|
|
With this fw is it possible to get above 657mhz and nit to loose one board?
You got the batch 4 to 737?
Regards
If you need to manage individual board frequencies, you’ll have to use mine. Losing boards will vary by machine, too. The only real way to answer your question on 657 is try.... |
|
|
|
The reason is clear. Lack of power supply. For frequencies above 750, it is necessary to increase the power supply to at least 0.9V with appropriate cooling of the chips and PWM drivers. At a frequency of 750, the chips work and do not fall off, but due to internal errors, the hashrate drops
i have batch 1 running on 750Mhz, are u suggesting that goign above has no sense as the hash will drop due to not enough power? It will vary by machine. You will have to see how yours behaves at a given frequency. |
|
|
|
That is just shell expansion and filters on the inputs stream instead of using things like sed and awk. Just presentation. 100% sure. “Final answer” as some tv show used to say. |
|
|
|
Jason
What do you get of this code here... it appears to be double checking fan and temps versus hashrate etc.... It is in the file sbin minerlcd there is more this is just a snippet of it. I assuming the word temp is the temp in c or f and tmp is what it is a tmp file or folder. Even though there is no lcd this routine still runs for the API I believe. Is it possible you can gain control over the fans at this point
....snip...
Read only presentation variables for the UI. |
|
|
|
|
Chipless,
Fair enough. I apologize. Stresses are clearly showing... how I have responded to you is not my goal, ever.
Jason
|
|
|
|
|
Smarty’s fix is incorrect. It causes miscalculations in other parts of the frequency handling around timeouts. This is why folk have issues with it in some circumstances.
I have zero miners other than two on loan so you clearly are off base.
The problem I had is that you posted it in my thread. Simple as that, not that you released a mod.
As far as “in it for money”, you are right I seek to have my time accounted for. As far as greed, you are simply wrong. One example is I have had a handful of users who purchased firmware and their machine could not handle an overclock; they were refunded. That is not greed.
Jason
|
|
|
|
|
Beta testers -- I've pulled the Z9 mini image as there is an issue which will prevent it from mining properly. I will provide an updated version soon.
Thank you,
Jason
|
|
|
|
Sigh. Chipless Posting that firmware in this thread is seriously uncool and I’m just going to call that out. It was a huge douche maneuver.
Antonio, your problems are your network. I worked with you via teamviewer until 4am my time and something at your ISP is blocking network communications. I would appreciate everyone being very clear here so there is not confusion about what is going on.
I request y’all take that conversation to your own thread.
Jason
I don't see why there is a problem with releasing it on your thread all batches of the mini are capable of running batch 1 firmware I just resolved a problem with the temp and fans not working correctly any other improvements you can do but for now it is no different then linking the batch firmware as far as I see it but I started a thread for it found here. Sorry if it offended you but in some cases we all need to work together. I realize you have time into your firmware as do I my fix is far from what you are doing and in no way interferes. https://bitcointalk.org/index.php?topic=5073285.new#newThis is my last response to you: You PMed me yesterday asking to test the firmware while simultaneously asking me to take the dev mode out for you. If you cannot see how these two things add up together to be very questionable, then I do not know what to say. Jason |
|
|
|
I have working batch 4 firmware for the z9 mini unlocked with working temp and fan. I am not asking for dev fee and only ask for donations if you find it helpful for your Batch 4 Z9 mini. This is a one time fix no further updates for this firmware Efudd has the furture updates covered with his projects. I am only releasing this because the fan noise on the batch 4's sucks when using batch 1 firmware. Donations Zcash only can be sent to: t1e4Dmr5RBgnWqTN2mAmZ6JzGavW7qxA4P1 THIS IS FOR Z9 Mini's ONLY WILL WORK ON ALL BATCHES 1-4 https://drive.google.com/file/d/1fSrEopPWO5nChvphh7zvIT_3zj4DI4t5/view?usp=sharingI'll get through reverse engineering this later, but so far it looks like the 'unlocked' part already existed and is not something you added. Also, still uncool. Jason |
|
|
|
I have working batch 4 firmware for the z9 mini unlocked with working temp and fan. I am not asking for dev fee and only ask for donations if you find it helpful for your Batch 4 Z9 mini. This is a one time fix no further updates for this firmware Efudd has the furture updates covered with his projects. I am only releasing this because the fan noise on the batch 4's suck. Donations Zcash only can be sent to: t1e4Dmr5RBgnWqTN2mAmZ6JzGavW7qxA4P1 THIS IS FOR MINI ONLY WILL RUN ON ALL BATCHES 1-4 https://drive.google.com/file/d/1fSrEopPWO5nChvphh7zvIT_3zj4DI4t5/view?usp=sharingThis is a thread about Z9s, not minis. Jason |
|
|
|
Sigh. Chipless Posting that firmware in this thread is seriously uncool and I’m just going to call that out. It was a huge douche maneuver.
Antonio, your problems are your network. I worked with you via teamviewer until 4am my time and something at your ISP is blocking network communications. I would appreciate everyone being very clear here so there is not confusion about what is going on.
I request y’all take that conversation to your own thread.
Jason
Blocking takes place on the whole territory of Russia, and not only this provider, I do not know why. I tried to use other providers - the result is the same. Maybe it makes sense to introduce into the firmware the ability to work via VPN? Use vpn - connect without problems. Yeah, sorry. I'll regionalize later if necessary. It's weird that your provider lets you access releases.broked.net but not the other API server. Jason |
|
|
|
efudd PM.
Thank you -- I am holding off on additional testers for the next 48 hours. Jason |
|
|
|
|
Sigh. Chipless Posting that firmware in this thread is seriously uncool and I’m just going to call that out. It was a huge douche maneuver.
Antonio, your problems are your network. I worked with you via teamviewer until 4am my time and something at your ISP is blocking network communications. I would appreciate everyone being very clear here so there is not confusion about what is going on.
I request y’all take that conversation to your own thread.
Jason
|
|
|
|
|
Show Posts
