Pages:
Author

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

jr. member
Activity: 559
Merit: 4
Z11-Chipless-v1-Beta 2 Released

Fix restart bug when setting pools and updated to 775m speeds are now around 143-148k/sol

From your first post: "A bit of what to look forward to...…… I have set manually to 775 right now. The holdback so far is voltage if it cannot be overcome
these machines wont hold much more then 143-148k/sol as far as I can tell right now"

No, the limit is not voltage.
Also, you should find that 775 as a fixed frequency will not work for many hash boards.

-j

Well thank you for that input. I know there is more to do to improve my image. Its better to get it out there so many can use it if they choose and as with your fw as time goes on it will get better. The best part is it's free. Even if no one uses it the fw has increased my own speed and that is what really matters to me.

I find a couple things funny about this....First you kept reporting you couldn't get past the 142k and hold it and second how you tried telling me you cant change a 7 to an 8 and get more power. Then all of a sudden you start saying your getting 150k+ after I released an image. So that either makes you a liar, a bullshitter or both. Your image was suppose to be released 2 days ago per your words. I am beginning to think you enjoy making statements then not following thru with them. That is like 4+ times now you haven't stuck with what you say.

The only thing holding back the 142k was clock and power. I know power was the main holdback because as soon as I set the 7 to an 8 I was getting more speed. Hmm... You must either still be having trouble with the small problems or your spending a lot of time trying to protect the code.
member
Activity: 504
Merit: 51
Z11-Chipless-v1-Beta 2 Released

Fix restart bug when setting pools and updated to 775m speeds are now around 143-148k/sol

From your first post: "A bit of what to look forward to...…… I have set manually to 775 right now. The holdback so far is voltage if it cannot be overcome
these machines wont hold much more then 143-148k/sol as far as I can tell right now"

No, the limit is not voltage.
Also, you should find that 775 as a fixed frequency will not work for many hash boards.

-j
jr. member
Activity: 559
Merit: 4
Z11-Chipless-v1-Beta 2 Released

Fix restart bug when setting pools and updated to 775m speeds are now around 143-148k/sol
member
Activity: 504
Merit: 51


*shrug*.

-j

So what are you referring to let see some times and averages etc shit i can reboot mine and it boosts upto over 160k that wold be aboout 53.3k each but it last for a few minutes till it settles in at 145....I am still waiting for the pm and link for the safe cgminer file to test. You never sent a link so it must be another thing you say then dont do. Wasnt I suppose to look at it and see how wrong I was.

22m14s   167.11   150.32
34m59s   157.93   149.85

*shrug*.

-j

Not very long, hope it stays any improvement is good improvement. I know I still have some tweaking I can do and hopefully can get a little more out of them.

1h0m44s   150.07   149.57
...
9h8m9s   152.03   147.09

Shrug.

-j
jr. member
Activity: 559
Merit: 4


*shrug*.

-j

So what are you referring to let see some times and averages etc shit i can reboot mine and it boosts upto over 160k that wold be aboout 53.3k each but it last for a few minutes till it settles in at 145....I am still waiting for the pm and link for the safe cgminer file to test. You never sent a link so it must be another thing you say then dont do. Wasnt I suppose to look at it and see how wrong I was.

22m14s   167.11   150.32
34m59s   157.93   149.85

*shrug*.

-j

Not very long, hope it stays any improvement is good improvement. I know I still have some tweaking I can do and hopefully can get a little more out of them.
member
Activity: 504
Merit: 51


*shrug*.

-j

So what are you referring to let see some times and averages etc shit i can reboot mine and it boosts upto over 160k that wold be aboout 53.3k each but it last for a few minutes till it settles in at 145....I am still waiting for the pm and link for the safe cgminer file to test. You never sent a link so it must be another thing you say then dont do. Wasnt I suppose to look at it and see how wrong I was.

22m14s   167.11   150.32
34m59s   157.93   149.85

*shrug*.

-j
jr. member
Activity: 559
Merit: 4


*shrug*.

-j

So what are you referring to let see some times and averages etc shit i can reboot mine and it boosts upto over 160k that wold be aboout 53.3k each but it last for a few minutes till it settles in at 145....I am still waiting for the pm and link for the safe cgminer file to test. You never sent a link so it must be another thing you say then dont do. Wasnt I suppose to look at it and see how wrong I was.
member
Activity: 504
Merit: 51
jr. member
Activity: 559
Merit: 4
I love it.

The more you overclock and overvolt the Z11's the greater the difficulty becomes and the less profit you make.

Brilliant!

The difficulty is going up no matter what so you either get the profit now or you lose profit anyways. Since last August I have received half my costs back already. The faster I recover that the faster I start to profit.
jr. member
Activity: 559
Merit: 4
If we want to play the poolside game: 148.0 KH/s   5549 (100%)   0 (0%)   a minute ago

-j

Sorry I dont play games, I have proven you wrong now a few times today just accept it for what it is and work on your own rather then sit here trying to say mine is bogus shit.

You wanted me to use my own shit and leave yours alone so I did, now thats not enough for you. If you want to pay me off I will stop public release of free files, if not everything I do is gonna be put out for free. Your starting to act like Bitmain and want to corner the market.

Fact is machine side I am getting 2k more then you in speed, the server side varies I know that, so we will deal with only the machine side from here out. You may not agree with how I changed the code and thats fine it is a beta 1 first release and I know there is tweaking to do. I have 1 test version that held closer to 150k for awhile.

You need to do like I did and invest close to 25k in miners and test away without depending on others. I also dont know how many times I have to tell you dont under estimate what I know how to and what I dont know how to do. I am retired and have many hours to play with these things and the firmware.
member
Activity: 129
Merit: 17
I love it.

The more you overclock and overvolt the Z11's the greater the difficulty becomes and the less profit you make.

Brilliant!
member
Activity: 504
Merit: 51
If we want to play the poolside game: 148.0 KH/s   5549 (100%)   0 (0%)   a minute ago

-j
jr. member
Activity: 559
Merit: 4
Well your wrong or you did something wrong with the second image you post because this is what my graph looks like. It also looks like I am getting a couple more k/sol then you are. Temps here are 80-90 outside the last few days. Miners are running in 70-80's

The graph is 4x mini's, 2x Z9 Full, and 2x Z11's

flypool
145.9 KH/s   5472 (100%)   0 (0%)   a minute ago

machine
Elapsed   KSol/S(RT)   KSol/S(avg)
15h15m58s   149.73   145.4



edit.....
must be Cooling off outside
flypool
Hashrate
464.3 KH/s 460.1 KH/s

miner
Elapsed   KSol/S(RT)   KSol/S(avg)
16h4m47s   143.34   145.46   
member
Activity: 504
Merit: 51
See, this is what a run of Z11 properly modded for voltage and frequencies should look like after a few hours.... You should note that there are no errors, no spamming of a failed scanning thread running every 2 minutes, blahblah. You'll note the frequencies here in this example are explicitly set by the user based on their environmental conditions and frequencies can be set and will lock PLL at anything from 200-850Mhz.

From a statistics perspective, things would look something like this:

Elapsed       R/T           Avg
5h17m4s   152.03   143.29

... This particular system has been running in an unfortunately hot area with chip temps at 80/81C, which is throttling it down some. Overnight it'll speed up again as it cools back down into the 60C's.

Here's a picture of the server side of my firmware over a few hours (with some downtime in the middle for some upgrades)


And here's a picture of a firmware running auto-tuning over that same time period


What you'll note here is that the hash rates running my firmware server side are very stable and almost never drop below the 140kSol line... yet if you run an image that has auto-tuning or scanning enabled, the results of the second pictures are true... fluctuations and drops, general hash instability as the control loop for scanning/auto-tune is poor. Even when the dip from my downtime roll off, the rates are stable.

Anyway...

Code:
Apr 30 19:09:34 (none) local0.err cgminer: Miner compile time: Tue Aug 21 16:00:32 CST 2018 (v2.2) type: Antminer Z11
Apr 30 19:09:34 (none) local0.warn cgminer: Started cgminer 4.9.0
Apr 30 19:09:34 (none) local0.warn cgminer[29510]: bitmain_ZCASH_init
Apr 30 19:09:34 (none) local0.notice cgminer[29510]: No 2 Fan find, check again
Apr 30 19:09:35 (none) local0.notice cgminer[29510]: fan-num 2 fan-map 3
Apr 30 19:09:35 (none) local0.notice cgminer[29510]: check_chain
Apr 30 19:09:35 (none) local0.notice cgminer[29510]: Chain 0 existed!
Apr 30 19:09:35 (none) local0.notice cgminer[29510]: Chain 1 existed!
Apr 30 19:09:35 (none) local0.notice cgminer[29510]: Chain 2 existed!
Apr 30 19:09:35 (none) local0.notice cgminer[29510]: chain0 every_chain_reset_PIC16F1704_pic_new
Apr 30 19:09:37 (none) local0.notice cgminer[29510]: reset_PIC16F1704_pic_new ok
Apr 30 19:09:37 (none) local0.notice cgminer[29510]: chain1 every_chain_reset_PIC16F1704_pic_new
Apr 30 19:09:38 (none) local0.notice cgminer[29510]: reset_PIC16F1704_pic_new ok
Apr 30 19:09:39 (none) local0.notice cgminer[29510]: chain2 every_chain_reset_PIC16F1704_pic_new
Apr 30 19:09:40 (none) local0.notice cgminer[29510]: chain0 every_chain_jump_from_loader_to_app_PIC16F1704_new
Apr 30 19:09:41 (none) local0.notice cgminer[29510]: jump_from_loader_to_app_PIC16F1704_new ok
Apr 30 19:09:41 (none) local0.notice cgminer[29510]: chain1 every_chain_jump_from_loader_to_app_PIC16F1704_new
Apr 30 19:09:41 (none) local0.notice cgminer[29510]: jump_from_loader_to_app_PIC16F1704_new ok
Apr 30 19:09:41 (none) local0.notice cgminer[29510]: chain2 every_chain_jump_from_loader_to_app_PIC16F1704_new
Apr 30 19:09:42 (none) local0.notice cgminer[29510]: jump_from_loader_to_app_PIC16F1704_new ok
Apr 30 19:09:43 (none) local0.notice cgminer[29510]: reset_all_hash_board_low 4204
Apr 30 19:09:43 (none) local0.notice cgminer[29510]: pic_heart_beat_func_new
Apr 30 19:09:43 (none) local0.notice cgminer[29510]: every_chain_disable_PIC16F1704_dc_dc_new
Apr 30 19:09:44 (none) local0.notice cgminer[29510]: disable_PIC16F1704_dc_dc_new ok
Apr 30 19:09:44 (none) local0.notice cgminer[29510]: disable_PIC16F1704_dc_dc_new ok
Apr 30 19:09:44 (none) local0.notice cgminer[29510]: disable_PIC16F1704_dc_dc_new ok
Apr 30 19:09:49 (none) local0.notice cgminer[29510]: every_chain_enable_PIC16F1704_dc_dc_new
Apr 30 19:09:49 (none) local0.notice cgminer[29510]: enable_PIC16F1704_dc_dc_new ok
Apr 30 19:09:49 (none) local0.notice cgminer[29510]: enable_PIC16F1704_dc_dc_new ok
Apr 30 19:09:49 (none) local0.notice cgminer[29510]: enable_PIC16F1704_dc_dc_new ok
Apr 30 19:09:50 (none) local0.notice cgminer[29510]: reset_all_hash_board_high 4210
Apr 30 19:09:50 (none) local0.notice cgminer[29510]: tty_init
Apr 30 19:09:50 (none) local0.notice cgminer[29510]: tty_init_chain chainid = 0
Apr 30 19:09:50 (none) local0.err cgminer[29510]: create rx read thread for chain 0 ok
Apr 30 19:09:50 (none) local0.notice cgminer[29510]: Start A New Asic Response.Chain Id:[0]
Apr 30 19:09:50 (none) local0.err cgminer[29510]: create tx read thread for chain 0 ok
Apr 30 19:09:50 (none) local0.notice cgminer[29510]: open device over
Apr 30 19:09:50 (none) local0.notice cgminer[29510]: tty_init_chain chainid = 1
Apr 30 19:09:50 (none) local0.err cgminer[29510]: create rx read thread for chain 1 ok
Apr 30 19:09:50 (none) local0.notice cgminer[29510]: Start A New Asic Response.Chain Id:[1]
Apr 30 19:09:50 (none) local0.err cgminer[29510]: create tx read thread for chain 1 ok
Apr 30 19:09:50 (none) local0.notice cgminer[29510]: open device over
Apr 30 19:09:50 (none) local0.notice cgminer[29510]: tty_init_chain chainid = 2
Apr 30 19:09:50 (none) local0.err cgminer[29510]: create rx read thread for chain 2 ok
Apr 30 19:09:50 (none) local0.notice cgminer[29510]: Start A New Asic Response.Chain Id:[2]
Apr 30 19:09:51 (none) local0.err cgminer[29510]: create tx read thread for chain 2 ok
Apr 30 19:09:51 (none) local0.notice cgminer[29510]: open device over
Apr 30 19:09:55 (none) local0.notice cgminer[29510]: calculate_address_interval:addrInterval = 64
Apr 30 19:09:57 (none) local0.notice cgminer[29510]: check_every_chain_asic_number
Apr 30 19:09:58 (none) local0.notice cgminer[29510]: check_asic_reg: chain J0 has 3 ASIC
Apr 30 19:10:00 (none) local0.notice cgminer[29510]: check_asic_reg: chain J1 has 3 ASIC
Apr 30 19:10:02 (none) local0.notice cgminer[29510]: check_asic_reg: chain J2 has 3 ASIC
Apr 30 19:10:02 (none) local0.notice cgminer[29510]: chainid0 set_frequency_chain freq=750
Apr 30 19:10:02 (none) local0.notice cgminer[29510]: chainid1 set_frequency_chain freq=750
Apr 30 19:10:02 (none) local0.notice cgminer[29510]: chainid2 set_frequency_chain freq=750
Apr 30 19:10:02 (none) local0.notice cgminer[29510]: set_ticket_mask_chain chainID0 ticket_mask = 0x0000000f
Apr 30 19:10:02 (none) local0.notice cgminer[29510]: set_ticket_mask_chain chainID1 ticket_mask = 0x0000000f
Apr 30 19:10:02 (none) local0.notice cgminer[29510]: set_ticket_mask_chain chainID2 ticket_mask = 0x0000000f
Apr 30 19:10:02 (none) local0.notice cgminer[29510]: software_set_address_chain chainID0 asics 3 addrInterval 64
Apr 30 19:10:02 (none) local0.notice cgminer[29510]: software_set_address_chain chainID1 asics 3 addrInterval 64
Apr 30 19:10:03 (none) local0.notice cgminer[29510]: software_set_address_chain chainID2 asics 3 addrInterval 64
Apr 30 19:10:03 (none) local0.notice cgminer[29510]: chainid0 set_core_timeout_chain: core timeout = 00014820
Apr 30 19:10:03 (none) local0.notice cgminer[29510]: chainid1 set_core_timeout_chain: core timeout = 00014820
Apr 30 19:10:03 (none) local0.notice cgminer[29510]: chainid2 set_core_timeout_chain: core timeout = 00014820
Apr 30 19:10:03 (none) local0.notice cgminer[29510]: enable_read_temperature_from_asic_chain: reg_value=0x07006061 chainid 0
Apr 30 19:10:03 (none) local0.notice cgminer[29510]: enable_read_temperature_from_asic_chain: reg_value=0x07006061 chainid 1
Apr 30 19:10:03 (none) local0.notice cgminer[29510]: enable_read_temperature_from_asic_chain: reg_value=0x07006061 chainid 2
Apr 30 19:10:03 (none) local0.notice cgminer[29510]: dev.timeout = 10000000 us
Apr 30 19:10:04 (none) local0.notice cgminer[29510]: bitmain_ZCASH_init: fan_eft : 1  fan_pwm : 100
Apr 30 19:10:06 (none) local0.notice cgminer[29510]:  424116one
Apr 30 19:10:06 (none) local0.err cgminer[29510]: cgminer time error total_secs = 1556651406.912049 last_total_secs = 1.000000
Apr 30 19:10:07 (none) local0.info cgminer[29510]: Pool 0 extranonce set to a800e7ee60
Apr 30 19:10:07 (none) local0.info cgminer[29510]: Pool 1 extranonce set to ae0e45a3be
Apr 30 19:10:07 (none) local0.info cgminer[29510]: Pool 2 extranonce set to a1013ef095
Apr 30 19:10:12 (none) local0.warn cgminer[29510]: API running in IP access mode on port 4028 (7)
jr. member
Activity: 559
Merit: 4
Oh whatever dude. Sully your name more by releasing bogus shit.

You haven’t overvolted it either.

The voltage range is defined as 800-880 and each chip is initialized at 870. Past that, there are additional checks to ensure it isn’t initialized outside of that range. The PIC then will not pass more than the defined 870 when converted to an i2c message to the downstream hardware, also... so hacking a 7 to an 8 does you no good at all. And the reason you think it is 840/870 is because you have not understood the code you are attempting to disassemble yet... You can completely ignore the 840.

You have changed some hard coded values, selected which stats you think look best, and released some hacked up bullshit.

I’ll tell you what, I’ll give you a special image that disables the autotuning so you can see how wrong you are with your claims.

Do you even know why the auto tuning kicks off every couple of minutes? I do, and it isn’t because you have modded this right.. I don’t even have to look at this to know. Bitmain has hacked some bullshit in to check for a specific frequency setting to try to scan for tuning. At the end, it restarts cgminer to actually initialize them at the selected frequencies..... if you have hacked out those bits to disable that restart, you are also screwing up for reasons that SHOULD be obvious if you were competent.

The autotuning scan thread running is an exception case and not the expected normal run state. Did you fix the case where auto-scanning will tune your boards down to 0mhz? (Rare, but can happen and is hilarity).

Oh, and there is actually a simple way for you to disable auto scan, (but not autotune) through binary edits.

Ghidra has not made you more capable, it has instead increased your confirmation bias.


-j

I am waiting for the link to your special image so you can prove me wrong

edit....current miner reported hash
Elapsed   KSol/S(RT)   KSol/S(avg)
8h51m28s   151.04         145.58

Elapsed   KSol/S(RT)   KSol/S(avg)
9h24m2s   143.99         144.43   


No randomness....Steady and holding I also believe I know why there is a 1k difference and need to try some things to make sure
jr. member
Activity: 559
Merit: 4
BTW, the illegal voltage response does not come from the PIC.

-j

No shit but a code is sent back from the pic saying it wasnt set.... The pic literally wont accept anything higher then 880 even on a forced default the pic resorts back to 840 on any error. I been playing with this and know what is going on so dont sit and act like it dont work. You are just trying to push people away to your dev shit you were gonna release. By your own word you havent been able to hold anything steady over 142 and I have so just get over it. Your not the only person who can make mods that work.

Maybe you need to buy a machine and play with it rather then use someone elses. Again rather then run your mouth lets let the public decide if they are getting more or not. Then you can run your mouth if it is proven not to be working. I was even gonna share the batch 1 mini pic codes with you but your nothing but an asshole so get it yourself
member
Activity: 504
Merit: 51
BTW, the illegal voltage response does not come from the PIC.

-j
jr. member
Activity: 559
Merit: 4


"your" -> "you're".

And "you are" welcome to your opinion, however flawed they are.

See, I won't release "shit". How exactly have you spent 2 weeks "modding" yours when just a week ago you expected to receive them?

My first beta user came online 4/17 @ 21:43 hours.

[pid: 5573|app: 0|req: 13158/60407] ... () {46 vars in 574 bytes} [Wed Apr 17 21:43:27 2019] POST / => generated 1600 bytes in 6 msecs (HTTP/1.1 200) 1 headers in 51 bytes (1 switches on core 0)

As of 29 minutes ago, that system is still running just fine.

[pid: 17806|app: 0|req: 7881/48031] ... () {46 vars in 574 bytes} [Tue Apr 30 16:26:03 2019] POST / => generated 1538 bytes in 7 msecs (HTTP/1.1 200) 1 headers in 51 bytes (1 switches on core 0)

Your own posts state you didn't have machines on 4/17, which is less than two weeks ago... yet I actually have folk running working images with this stuff you claim (but implemented correctly) for almost two real weeks, not two made up weeks.

You will (hopefully) figure out that trying to use the scan thread that way is not going to achieve the results you desire...

-j

I am sorry 10-11 days I received mine on 4/21/2019 ... Your data came from people you asked to use for testing miners because you dont have your own. I have seen your posts asking people to send you one and so on. I dont care when you started this isnt your release. I and others realy dont care how sloppy or how good the inside coding is what matters is the end results. Thats why the first is a beta release if all works like people want I will look more into the cleaning up and maybe some performance improvement.

It seems all you can do is worry about my grammer. What a petty fucker you are

I have already received the results I desire without the scanmode it gets about 1 k less then it does running it.

Flypool stats again
146.6 KH/s   5496 (100%)   0 (0%)   3 minutes ago
145.4 KH/s   5453 (100%)   0 (0%)   3 minutes ago


member
Activity: 504
Merit: 51
jr. member
Activity: 559
Merit: 4
Oh whatever dude. Sully your name more by releasing bogus shit.

You haven’t overvolted it either.

The voltage range is defined as 800-880 and each chip is initialized at 870. Past that, there are additional checks to ensure it isn’t initialized outside of that range. The PIC then will not pass more than the defined 870 when converted to an i2c message to the downstream hardware, also... so hacking a 7 to an 8 does you no good at all. And the reason you think it is 840/870 is because you have not understood the code you are attempting to disassemble yet... You can completely ignore the 840.

You have changed some hard coded values, selected which stats you think look best, and released some hacked up bullshit.

I’ll tell you what, I’ll give you a special image that disables the autotuning so you can see how wrong you are with your claims.

Do you even know why the auto tuning kicks off every couple of minutes? I do, and it isn’t because you have modded this right.. I don’t even have to look at this to know. Bitmain has hacked some bullshit in to check for a specific frequency setting to try to scan for tuning. At the end, it restarts cgminer to actually initialize them at the selected frequencies..... if you have hacked out those bits to disable that restart, you are also screwing up for reasons that SHOULD be obvious if you were competent.

The autotuning scan thread running is an exception case and not the expected normal run state. Did you fix the case where auto-scanning will tune your boards down to 0mhz? (Rare, but can happen and is hilarity).

Oh, and there is actually a simple way for you to disable auto scan, (but not autotune) through binary edits.

Ghidra has not made you more capable, it has instead increased your confirmation bias.


-j


I guess we are back to the fuck you jason. Before you run your shit mouth why dont you let the public decide if they get an improvement. Easy to watch your server for the increase. The stats speak........ The pic accepts 880 anything higher is rejected not 870 as you claim. I have tried even do a force but 880 is where the illegal voltage message stops. I am using the autotune to keep the speed higher else over a hour or so the speed will drop into a lower range to reduce the limit back to 142k and so on it works and you didnt do it the best thing is its free

The 840 is the default set if the volt is out of range. Once you receive the illegal voltage message it automaticcaly resorts to the default of 840 the normal voltage is between the 800 and 880 range try 881 and you get error try 880 all is ok the normal running is 870 so yes i increased the voltage from 870 to 880 and the default to 880 so if there is an error somehow the voltage by default will still go back to 880

In my opinion your trying to rip miners off....You knew the limits of these machines but led customers to think 180k is what you could maybe bring. Then claim it is so hard to do. I had the initial file done in 6 hours the last 2 weeks have been testing every scenario I can think of.

Reported by miner
Elapsed   KSol/S(RT)   KSol/S(avg)
6h50m11s   138.75          144.56

Elapsed   KSol/S(RT)   KSol/S(avg)
6h18m37s   136.13           145.6


Reported by flypool
149.1 KH/s   5591 (100%)   0 (0%)   4 minutes ago
142.2 KH/s   5331 (100%)   0 (0%)   4 minutes ago


I will add maybe you should have put off your vacation and bought a z11 instead of sit online begging for someone to loan you one. And yes I know what the file is doing the limit is 880mv anything higher is rejected by the pic. Therefore these miners are not going to get much improvement unless the voltage can be unlocked more. I bought mine then spent 2 weeks modding for the best speed. Next is voltage on the Z9's i may get it working.

another flypool stats...I can post these all week long....So dont accuse of picking and choosing my stats to post
147.2 KH/s   5519 (100%)   0 (0%)   6 minutes ago
144.2 KH/s   5407 (100%)   0 (0%)   6 minutes ago
Pages:
Jump to: