Topic: T17 OC/OV. S17 Series OC/OV, Antminer B7 OC/OV, S9k, Z11 + others 100% FREE - page 17. (Read 10178 times)

The irony...

I see you’re still struggling to grasp the basics of the English language. It doesn’t matter how many times you’re corrected.

Your = showing possession
You’re = you + are

Replied Enjoy

Hi chipless,

I send you a private message, I am ready to heat it's z11 as it should 

Thank you !

LOL go for it......You think I am stupid not to report it. Your a fucking idiot because you have no choice to report it if you use coinbase. LOL good one though.

Elapsed       KSol/S(RT)   KSol/S(avg)
7h49m16s       148.1           159.36

Chain#   ASIC#   Frequency   KSol/S(RT)   HW   Temp(PCB)   Temp(Chip)   ASIC status
1                3                  825   47.18              3   67                      94                    ooo
2                3                  825   53.74            11   69                    104                ooo --- 80+ degrees outside
3                3                  825   47.18              0   62                      92                    ooo



still going

Elapsed    KSol/S(RT)   KSol/S(avg)
8h32m21s    166.45          159.45

Released the Chipless Nitrous v1.5 Public with speeds of 155k/Sol

Enjoy keep it cool and earn some extra coins....Private release is available with speeds of 158 k/sol +

since many of us know your real name and contact info, Marky Mark (since you're dumb enough to publicly dox yourself via your youtube page), it wouldn't be a stretch for someone to drop an anonymous tip to the IRS about your new business that you're definitely reporting income for , right? RIGHT?

 

i like how all of his posts trying to brag are all less (way less) than 5 hrs run time.

show me one post 24hrs and maybe it'll be impressive...

Get your fire extinguisher!

Yeah, 5s peaks on mine are 225k+, but ok.

-j

So now I will show you more later......I am going to sleep now because I have been tweaking this since yesterday for maximum efficiency.....I will catch up PMs later today.

2h34m12s      182.18k/sol 5 sec. nice peak.....

even better on 2nd machine

48m58s   192.01k/sol

the latest .....lol your so funny you dont even know how low I have the power and you already know it all. Make me laugh some more. At least I am doing direct editing to the binary instead of compiling my own stuff to intercept and link into cgminer. More clean less errors. I can add to the binary just as if I wrote a loader for it it only a matter of knowing what to put where and adjusting sizes. I told you long ago I am not a rookie at reverse engineering binaries and writing code. Every file I have put out you try down talking it like your the guru in the coding world.

edit ... I am sure you know what I am changing there are public releases that you have been looking at

You keep saying power and efficiency but a mini uses as much as 425 watts and you get a max 17k if lucky so adding 200-300 watts to a z11 isnt woth it for 20-25k increase. When I do the math it looks like more profit to me, the mini would cost at least a couple hundred and mabout 55-65 or so a month at the cost of about 35.00 so in the end you get more for your bang bumping up a z11.

No one is screwing any end user. If I wont use it I wont offer it plain and simple. Do you think I want to burn up 4500 in miners just to say I could do it.


Elapsed       KSol/S(RT)   KSol/S(avg)
1h29m47s       175.63            159.73


Chain#   ASIC#   Frequency      KSol/S(RT)   HW   Temp(PCB)   Temp(Chip)    ASIC status
1             3            825              53.08            0      64                     90                 ooo
2             3            825              61.60            2      66                      101         ooo
3             3            825              60.94            0      59                       88         ooo

Lol.... hey, with the power that is burning maybe your cheaper power solution will help.

I’ve said 160 stable is possible... power cost is too high. Temp and longevity will be effected. And the tuning needing to get 160 will vary greatly by individual machine.

Let me add that since all you can do is hex edit the binary, there is a limited set of changes you can make so I do have a pretty good idea of what it is you have or are changing .

Don’t screw the end user.

-j

No actually I am going to say fuck you Jason and release an even better version for the public. Your claims of150 stable is bs maybe you need to quit testing other peoples equipment and get your own to test. Your the one who hasnt released a single stable release all you so far or all claims nothing other then your word that dont mean shit your said so many things that you havent followed thru with your users are still waiting for the 2% dev fee which you said you were giving them 4 months ago.

Edit...

Let me add you dont even know what I have done or changes. If you wanna know I will sell ya a copy for 5 ZEC


this was a recent change so you must missed something or arent being honest with users again. After a small tweak

Elapsed   KSol/S(RT)   KSol/S(avg)
50m29s   174.31           160.07


Chain#   ASIC#   Frequency     KSol/S(RT)   HW   Temp(PCB)  Temp(Chip)   ASIC status
1              3              825           60.29            0   64                90            ooo
2              3              825           55.05            0   66              100            ooo
3              3              825           58.98            0   59                88            ooo

And it is still climbing some

He took those down, sadly. They were quality material for sure. :/

-j

He must not be getting enough donations. So he’s trying to sell now lololol

I wish he didn’t abandon that power thread. Many laughs when he posted those videos showing his own idiocy.

Good job on hw errors. That was actually my point. There is a positive correlation between increased voltage and decreases in hw errors.

However I do not have any correlation between a decrease in hw errors and any other effect.

I will say that the voltage necessary to stop hw errors on on board is generally different than what is needed on another board. What this means is if that imbalance exists, all one does is add heat into the other boards for no positive return. Which equates to an increase in wattage for no return.

-j

Fact: less than 36 hours ago you posted that you needed to test with more that one PSU. Now a few short hours later you want to sell/claim/whatever “159kSol+“ that requires more than one PSU.

At a minimum, your testing times suck as there is no way you can both state you need to test with more than one PSU and have the confidence to release something claiming to need it in less than 36 hours without only looking at very short term results.

FACT: I have been testing for a long time with multiple PSU systems.

FACT: 160k stable is doable, but it blows power efficiency out of the water negating all value add.

FACT: the maximum stable frequency is 825Mhz.

FACT: I have been able to test in a well ventilated environment and maintain chip temps under 85c at 825Mhz and the hash is not stable.

FACT: voltage and hw error rate have a positive relationship (let me know when you figure this statement out)

FACT: a voltage that works on one board will result in other boards going offline

FACT: hash rate is unstable over 150kSol. On long runs the average WILL return to the 150kSol or less.

FACT: these systems are highly voltage sensitive and something that runs on one will not run on another.

FACT: when pushing voltages you WILL have boards drop out and it make take hours or days, but it WILL happen

FACT: there is not a stable hash at the level you claim on these systems, barring any unicorn units.

I expect that the success rate of holding 160 (ignoring the fact power consumption goes shitty) is in the 2% range.... incidentally Z9 units holding >681mhz is also around 2% of the total statistical population.

FACT: there is no way, by your own statements, you hVs tested and validated anything to the point of deserving the confidence to sell a non refundable “159k+” variant.

FACT: my comments here have absolutely nothing to do with protecting myself... users are going to get screwed because you don’t even know why you don’t know.

FACT: you are ignoring feedback from users who report problems to you (its time they speak up in public).

FACT: you brick people’s machines with some regularity. Your “private”L3 image bricks machines... annoyingly I had someone contact me about your release just yesterday.you also released multiple mini images that bricked machines.  This comment has nothing to do with bricking directly, but rather a point of reference to your generalized incompetence in precision and correctness when releasing work.

FACT: a request is not the same thing as a success.

FACT: I look forward to seeing the feedback from users.

This is going to be at least as good as your power thread where you plugged a battery charger into a battery to charge the battery.... which also is a great example of your generalized incompetence.

Good luck.

-j


[/quote]

Fact is I dont care what you think. As far as the L3 well he was suppose to let me know what happened today. For all I know he could have unchecked the box to save setting and it changed IP's so lets not jump the gun. The gus asked for 1 thing only and you can compare the images yourself he lets you. The web page was updated to show the temp and beep feature. So if that bricked a machine then there is a real problem. I still have the images. Fact is I have 2 machines here both running separate times spans and different images for testing. Like you I only share so much information at times. Fact is the HW error rate is almost 0 and the reject rate is about or lower then the factory stuff as well as the discarded. Fact is I have the fucking reply to the users you are referring to so get it right.

The minis well there were a few issues with the images yes but I did correct the problem. You act like an error in a file or a machine that acts up is always the firmware writers fault.

So I really dont know what your point is I am not twisting a users arm to try the same files I am using or care to share. This is a forum where people share firmware,ideas, and whatever else they care to share or talk about. Many guys like you use it as a business and get pissed when guys like me who do it mainly for a hobby step up and give files away.

Fact: less than 36 hours ago you posted that you needed to test with more that one PSU. Now a few short hours later you want to sell/claim/whatever “159kSol+“ that requires more than one PSU.

At a minimum, your testing times suck as there is no way you can both state you need to test with more than one PSU and have the confidence to release something claiming to need it in less than 36 hours without only looking at very short term results.

FACT: I have been testing for a long time with multiple PSU systems.

FACT: 160k stable is doable, but it blows power efficiency out of the water negating all value add.

FACT: the maximum stable frequency is 825Mhz.

FACT: I have been able to test in a well ventilated environment and maintain chip temps under 85c at 825Mhz and the hash is not stable.

FACT: voltage and hw error rate have a positive relationship (let me know when you figure this statement out)

FACT: a voltage that works on one board will result in other boards going offline

FACT: hash rate is unstable over 150kSol. On long runs the average WILL return to the 150kSol or less.

FACT: these systems are highly voltage sensitive and something that runs on one will not run on another.

FACT: when pushing voltages you WILL have boards drop out and it make take hours or days, but it WILL happen

FACT: there is not a stable hash at the level you claim on these systems, barring any unicorn units.

I expect that the success rate of holding 160 (ignoring the fact power consumption goes shitty) is in the 2% range.... incidentally Z9 units holding >681mhz is also around 2% of the total statistical population.

FACT: there is no way, by your own statements, you hVs tested and validated anything to the point of deserving the confidence to sell a non refundable “159k+” variant.

FACT: my comments here have absolutely nothing to do with protecting myself... users are going to get screwed because you don’t even know why you don’t know.

FACT: you are ignoring feedback from users who report problems to you (its time they speak up in public).

FACT: you brick people’s machines with some regularity. Your “private”L3 image bricks machines... annoyingly I had someone contact me about your release just yesterday.you also released multiple mini images that bricked machines.  This comment has nothing to do with bricking directly, but rather a point of reference to your generalized incompetence in precision and correctness when releasing work.

FACT: a request is not the same thing as a success.

FACT: I look forward to seeing the feedback from users.

This is going to be at least as good as your power thread where you plugged a battery charger into a battery to charge the battery.... which also is a great example of your generalized incompetence.

Good luck.

-j