Quote from: efudd on November 28, 2018, 01:02:19 PM

Quote from: chipless on November 28, 2018, 12:59:20 PM

...snip...

any higher on any of the boards I either start to lose hash or get an x the the status. With Jasons version I don't get the x but still lose hash at higher then 656 on any board

If you are "losing hash higher than 656 on my firmware" relative to what you are running, then that is called "placebo".

@chipless -- did you figure out what was going on with your firmware bricking (well, locking them out) those 6 miners? At least, I think it was 6 -- one user said 5, the other said 1. I offered to help them via teamviewer but they had downgraded by doing a factory reset using the "bricked miner" recovery process. I think you just said you didn't know what was going on?

As numerous customers and users of my firmwares can attest to of their own accord, I go out of my way to ensure satisfaction. Over the weeks I've spent multiple hours working directly with users on their miners to understand and resolve issues and have been incorporating those lessons learned into both my instructions and firmware.

Before releasing any firmware, I test it multiple ways, from bare metal installation, to upgrades over other firmwares. I ensure downgrades work properly and that all factory defaults (such as passwords) are functioning as expected.

My failure rate with firmware flashes at customer sites is exactly 0.
My failure rate with functionality failing to work as expected at customer sites is exactly 0.
Caveats to this are a small handful of users that were unable to overclock at all due to hardware limitations; they were the driving force behind my per-hashboard work.

For posterity, the issue I have with your actions is posting on this thread about whatever firmware you have cobbled together from other peoples works; release all the firmwares you want on your own time, your own accord, and without any endorsement or indictment from me. Please stop making assumptions about me or about my intentions, and stop with the passive aggressive subterfuge attempts.

I'd like to ask you nicely to please stop posting in my thread. I am not interested in having you as a customer in any way, shape, or form.

Jason

Never said I didn't know what I was doing and never used your work or others besides the factory firmware. As far as the lockout problem your firmware will have the same issue at some point unless you found the cause. By your statements you have had the issue or have helped already. Your fix was just do a recovery but you don't know the cause of the issue as far as I know your explanation on my post was unsure. I forget but in the end you still had to tell them to do a recovery.

You also need to inform your customers that their miner on the current 2.1 version may stop mining if it cant reach your api callback server us-api1.fudd.net or your dev-fee pool zec-bj.ss.poolin.com or they may lose shares on a callback or dev-fee connection error. I did some testing and from bootup for 6 hours and anytime the callback couldnt reach your server or the dev server it gave the error I posted to you in an earlier post it which the kernel log stated that about 100 shares were lost and I stopped mining at different times and eventually would start again. Callbacks seem to happen more then once every 280 minutes also.

To sumit up if your server is down or unreachable the miner may stop mining all servers for a short time and the owner lose shares because of it.

Enjoy the input