No not at nothing just correcting the wrong information you posted. It is dishonesty when you say there has not been no issues with paid version when in fact you know there have been. I thought you were Mr Honest when it came to users.
You have no problem hiding behind your discord making comments about me and since you block me there I chose to comment here in the open not behind your back. Just like one of your users asked the difference between your and my versions and all you tell them is mine is bullshit. You wanted a truce but then hide and do the same crap, not much of a truce. Sad thing is I have recommended to some users over mine.
*sigh* This was received yesterday from a farm... [2:44 PM] REDACTED: just a follow-up after a few days. your firmware is rock steady without a blip using a license.... But hey.. you are right... one time in the last year, I fucked up for about 4 hours and impacted licensed users. Otherwise, *EVERY SINGLE ISSUE* has been a *USER* or *ENVIRONMENT* issue, not a firmware issue. I have 0 interest in having any discussion about you to anyone, so 'bullshit' is a dismissive statement of non-interest, not an accusation. I'm going to ask you again, to kindly go to your thread and mind your own business. -j |
|
|
|
*EDIT*: Non-dev fee options are available, if you were not aware. 0 issues reported from any users w/ a no-dev license.
Thank you,
-j
That's not true there have been issues reported by licensed and non-licensed users. Some have posted here and others on your discord mostly about the miner going into dev mode when it is suppose to be a licensed miner going into dev mode too often. Just give the guy a free license like you have others. Still at it I see.... -j |
|
|
|
What I'm trying to determine, is - how much time is being spent mining the dev fee. Seems like it's a lot; literally every other time that I checked throughout the past few days - I caught it mining on his pool.
To answer your question, the dev fee is 10 minutes out of every 290 minutes. The exception case is on first start, where it mines for you for 10 minutes, then dev fee for 10 minutes, then you for 280, then dev for 10... repeat. The "first 10 minutes to you" is so you can reasonably tune your units without incurring dev fees. If you are seeing something different, then it sounds broken. We should probably try to figure that out. You said: "I will not trust a large farm of 100+ Z11 machines to a custom firmware that is leeching so much from me. Why is it mining your pool for most of the day??" Likewise, I don't want a "large farm of 100+ Z11 machines" who cannot communicate in a reasonable manner. I've offered via PM and via discord. PM goes straight to my phone. Discord goes straight to my phone. A post here, does not go anywhere and requires me to check.. which then requires a series of delays back and forth which is not productive for either one of us. The first step to me answering "why" in your environment is to be able to look and see what is happening on the license server side. That simply requires a Support ID (status page) from one of your miners that is having an issue. From there, we can work to resolve. I strongly suggest sending that in a PM here, or via a DM on discord because it is "private to your machine". My oldest users have now been using my firmware(s) for almost a year now. Any time there has been an issue, it has been resolved in a mutually satisfactory manner. It just requires communication. *EDIT*: Non-dev fee options are available, if you were not aware. 0 issues reported from any users w/ a no-dev license. Thank you, -j |
|
|
|
Hi, what settings do you use on Z11? I hava a problem with large power comsumption. 791 mhz /960 and i get 2100-2200W with 155-160 kh/s Does anyone get better results? I have 2000W PSu so its problematic  on a new Bitmain firmware I get 135-140 kh/s and 1500W only. These are crazy power hungry when pushed. Join the discord as others may have some views and experiences to share there in the z11 channel as well... but the trick at that point in your testing would be to see how much power you can pull back out while maintaining a given hashrate. Tuning each board may help you optimize the power draw as well. Some folk have cheap power and don’t mind the draw, others are undervolting to maintain stock rates with lower power draw. -j can you post the link for the discord channel ? please. It's in my signature also.  -j |
|
|
|
Hello,
New user here. Just flashed a few test machines. Everything is working fine except the pool configuration. Awesome Miner is showing that the pool stays stuck at pools.fudd.net instead of my chosen pool.
I have stratum+tcp:// in my pool configuration and I'm using Antpool ZEC.
Advice?
Catch me on discord and/or PM me the support ID from the status page on one of your miners please and I will look into what you are seeing. -j |
|
|
|
"Fan control is removed in the 2.3 NiceHash releases -- I am working to add it back."
Hi, Jason! How's the work going to add back fan control to the latest firmware?
It isn’t... i have not had time to allocate to it in a while now. (Summer heat and such limits what I can run for testing). I wish I had better news. -j Good day. Problems with auto fan solved as I see? And can you find out this firmware for the old version of Nicehash or the new one? Old. New is busted again to the best of my awareness; nicehash server problems. -j |
|
|
|
"Fan control is removed in the 2.3 NiceHash releases -- I am working to add it back."
Hi, Jason! How's the work going to add back fan control to the latest firmware?
It isn’t... i have not had time to allocate to it in a while now. (Summer heat and such limits what I can run for testing). I wish I had better news. -j |
|
|
|
No clue, check your network.
-j
are my network speed make possibility to go for dev fee mining??? Aug 7 05:33:43 (none) local0.warn cgminer[1002]: Switching to pool 3 stratum+tcp://pools.fudd.net:6666 Aug 7 05:33:44 (none) local0.notice cgminer[1002]: Pool 3 extranonce set to 942F5203401EA53E other minres who have license at same time does not have this on logs.... i,m a bit not understand.. No clue. In fact, your systems are specifically and explicitly set to *NOT* go into dev fee mode in *ANY* condition. You don't know this, but your non-licensed systems are actually configured as licensed behind the scenes. I did this because you constantly seem to have issues and don't engage via chat to work through (which is significantly annoying, time consuming, and ineffective) whatever it is you have going on at a given point in time. ... So I decided to eliminate a variable and just remove that from the configuration aspect of your non-licensed systems. So... if you are seeing changes away from your primary pool, check your network. -j |
|
|
|
|
No clue, check your network.
-j
|
|
|
|
|
Honestly dude...
Go remove your damned support IDs from your post as they are private to you.
If you have an issue, send me a PM or move to another firmware. I honestly don’t care which you do.
Just a day ago you were saying you had DNS problems... you jump back and forth with some random issue all the time.
-j
|
|
|
|
what happens with luxor pool? wont accept shares, hashrates jumping around  If you are having issues with luxor, please talk to luxor on their discord or support. I do not represent luxor. As best I can tell, your licensed miners are working fine from the API pings. -j miners working but why not accepted shares?? on miner web page not show accepted shares, if switch to another pool, it works well and show accepted shares every time when refresh page, You said this ended up being a DNS issue with your network? -j |
|
|
|
what happens with luxor pool? wont accept shares, hashrates jumping around If you are having issues with luxor, please talk to luxor on their discord or support. I do not represent luxor. As best I can tell, your licensed miners are working fine from the API pings. -j |
|
|
|
... devicetree.dtb does not have anything to do with 'unlocking SSH' in any way, shape, or form. It really has nothing to do with the 'firmware' at all. -j |
|
|
|
@Efudd are you going to return `Fan control` back ? when ?
For the nicehash version, that is my intention. So far I have not been successful. No ETA unfortunately. :/ -j |
|
|
|
|
Yeah.... my bet is chipless doesn’t understand how the ssh config file is saved in /config.
After you install his stuff via SD, try installing again via web interface (chipless, release an image for upload installs if you haven’t already) and check the box to not save config.
Bet that fixes it for him.
-j
|
|
|
|
I updated one of my Z11's with 2.3.1nh firmware two days ago. I am mining ZEC on Luxor and the last two nights the miner switch to mine on the pools.fudd.net:6666 site. At 10:33 pm it switched as was still mining at about 6:30 am when I switched the pool back to Luxor via Awesome miner. My other z11's haven't experienced this, so I am confident it is something in the new firmware. Is anyone else experiencing this or have a recommendation other than flashing back to 2.3?
I turned on logging in Awesome miner to get more detail on the switch but would like any feedback from the community if possible.
Thank you,
Sean
Sean, Are you mining against NH or Luxor? If Luxor, there is no reason for you to use 2.3.1nh. 3 things: 1) please ensure your miner pool configuration starts with stratum+tcp://. 2) Send me your supportId from the status page in a private message will help me troubleshoot. 3) are you running minerstat? If so, you must manage your miner through their web interface as their stuff overwrites your config. -j -j |
|
|
|
How do you revert a z9 mini from Fuddware 2.3 back to Bitmain antminer-z9-mini-201805262047-500m.tar.gz? (batch 1 firmware)
When I load Bitmain firmware, the miners are complaining
"Invalid system and miner configuration file. Edit manually or reset to default."
I have tried to reset to defaults but Bitmain code still complains.
Any advice on this?
Thanks,
Tom
Clear your browser cache, click save on configuration (pool page or anywhere really). That simple. -j |
|
|
|
Just thought I would give you some follow up. I updated with your firmware on 2 Z11J's, and they seem to operate at between 125K-135k sol/s, at 781mhz/920mv. So at least for the purposes of the Z11J, it looks like they simply under clocked a regular Z11 somehow. I actually have an option to get some Z11e at 70K sol/s for a reasonable price (relatively), and may order a couple to see if they did the same thing. If I could get a Z11e to 125-135k sol/s I would have gotten it at nearly half price!
What is your price for licenses for say 5-10?
Thanks!
...snip...
Awesome update! Glad to hear that! Send me a PM and we'll work out details on license. Thank you. Jason |
|
|
|
I just received my Z11J, and they operate at a bit over 110K sol/s. I see you added functionality for the Z11J but can you shed more light on how they are throttled? Is it less chips or is it firmware limited? If it is firmware limited, is there a way to turn it into a fully functional Z11 at 135k sol/s? Thanks! 2.3 and 2.3.1nh have been updated to support Z11/Z11e/Z11j.
Thank you,
Jason
Unclear, to be honest. You'd have to give it a shot and try to see what you can get out of it. Stock voltage is 870. For Z11, you have to add voltage to get more hash with an increased frequency. With e/j, that might not be the case. My sample set is too small to speak for sure... regardless, it is firmware limited in that the stock firmware attempts to automatically tune things, and generally does not do that great of a job. It also limits the max voltage as well as the max frequency within the auto-tune range. -j |
|
|
|
|
2.3 and 2.3.1nh have been updated to support Z11/Z11e/Z11j.
Thank you,
Jason
|
|
|
|
|
Show Posts
