In case ya missed my edit:
In other words could one calculate the ratio of NMW to HW errors by doing (NMW / (HW errors - NMW)) * 100?
or would it be (NMW / HW errors) * 100
Either way, since they both are diff1 related work then either of the above should be valid .. right?
It will be (NMW / HW errors) * 100 Don't concern yourself too much by the distinction between the different type of hardware errors. Sometimes we just expose too much internal information that doesn't help the users much. Yeah, I realize in the end all that matters is the cumulative amount between the 2 types, but I like the knowledge of knowing whats really goin on behind the scenes, so thanks for explaining it to me =) |
|
|
|
|
In case ya missed my edit:
In other words could one calculate the ratio of NMW to HW errors by doing (NMW / (HW errors - NMW)) * 100?
or would it be (NMW / HW errors) * 100
Either way, since they both are diff1 related work then either of the above should be valid .. right?
|
|
|
|
I looked up the code (in relation to my HW error comments before)
HW is the count of bad nonces generated plus NMW
NMW is when work comes back but it doesn't match any work sent to it (thus cannot be used)
Anyway to minimize NMW? My NMW hovers right around .52% of all matching work... Or is NMW ALSO the result of chip errors? Chip errors, even worse than regular HW errors. Oh, so let me see if I understand, NMW is just chip errors - probably related directly to OC/ heat, while HW errors is NMW + .. comm errors.. etc? Send work off, get an answer. The answer should be a valid share, and cgminer can track which chip bank it was sent to. If the response is not a valid share, it's an "invalid nonce" type of hardware error. If the response is garbled to the point of being gibberish and doesn't even look like a response, it's "no matching work" and cgminer can't even tell which chip was giving the garbage response. HW errors is the sum of both of these types of error. Ah, ok thanks for the explanation. In short OC'n can cause both types. So would each NMW constitute as an invalid diff1 share? cuz afaik HW errors are all equivilant to invalid diff1 shares .. which is why it used as 2% of diff1shares for --avalon-auto...? In other words could one calculate the ratio of NMW to HW errors by doing (NMW / (HW errors - NMW)) * 100? |
|
|
|
I looked up the code (in relation to my HW error comments before)
HW is the count of bad nonces generated plus NMW
NMW is when work comes back but it doesn't match any work sent to it (thus cannot be used)
Anyway to minimize NMW? My NMW hovers right around .52% of all matching work... Or is NMW ALSO the result of chip errors? Chip errors, even worse than regular HW errors. Oh, so let me see if I understand, NMW is just chip errors - probably related directly to OC/ heat, while HW errors is NMW + .. comm errors.. etc? OR is HW errors a direct result of NMW? Does NMW in any way relate to shares / share difficulty? |
|
|
|
|
I dont know where the master spreadsheet went, but my entry can be updated =)
Received order# 35xx July 5th =)
|
|
|
|
|
An even more optimal application of MX-2 might be to do a thin layer across entire pcb first(kinda how it was stock on early samples) .. then apply a tad to each little thermal pad for the chips.
QFN, iirc is designed to not only release heat through the thermal pad but also to the PCB around it - both work as a cooling element for the chip.
|
|
|
|
Ambient is sensor one. That thermal pad was delivered with my batch two unit.
oh interesting... So, I was thinking, arent the temp sensors attached to the heatsink and not the asic chips themselves? Given that...if ur thermal transfer effeciency increased by ur application of MX-2 .. shouldnt the heatsinks be a bit hotter as per the thermal sensors?? |
|
|
|
just found my first confirmed block ever =) 43mil diff share....freakin badass! woot!
From my single avy...lol
solo mining? i have tried setting up solo with no luck  even had help view team viewer from someone who has solo setup and for some reason it just would not work on my computer psh I wish I was solo mining...looks like by my calc, solo mining @ current diff should find a block every 2 weeks or so =P |
|
|
|
I looked up the code (in relation to my HW error comments before)
HW is the count of bad nonces generated plus NMW
NMW is when work comes back but it doesn't match any work sent to it (thus cannot be used)
Anyway to minimize NMW? My NMW hovers right around .52% of all matching work... Or is NMW ALSO the result of chip errors? |
|
|
|
|
or if you have othr devices on the network that depend on that subnet ... then dont change the subnet of the router. Rather set a PC temporarily to an ip within the same subnet, then go to config page on avalon and change it to correct subnet...
|
|
|
|
|
oh I see, that thermal foil, u tried first on ur WC blocks? I didnt even realize the pictures were a WC block =P
Thats pretty nice, whats the ambient @ that clock?
|
|
|
|
|
just found my first confirmed block ever =) 43mil diff share....freakin badass! woot!
From my single avy...lol
|
|
|
|
Finally got my Avalon today!
I'm running it with dynamic speed adjustment and I have it on a desk and a box right in front of my window AC unit which is feeding into the inlet. I have the AC set on high, cool, and 69 degrees. Seems right now frequency is stabilized at about 349MHz so far, and I'm getting about 87GH/s although sometimes it's as high as 90 or as low as 83. Probably needs more time to find out what the real average is.
I have a better AC unit coming tomorrow. It's a standalone unit and I'm going to have it piped right into the avalon intake. It's 12000 BTU so it might be a bit of an overkill. Hopefully I can run it on low. Will I be able to get above 90GH/s or so without getting a new power supply?
Anyways, my question is why does it show as a much lower (78GH/s or so) hash rate on the 50BTC.com website. Should I be using a different pool perhaps (I signed up for ozcoin but haven't tried it yet)? I believe 50BTC.com supports the stratum protocol and it says "true" under the stratum entries on the cgminer table, except for the last one "StratumURL".
Which is the hardware error field, btw? And what should that be kept below? Ugh, sorry for all the questions. I'm reading up as many threads as I can about the Avalon now, but it's hard to find all this information in one place (yes, I've read the wiki).
The higher you set vardiff at the pool, the more variance the pool will show in hashrate. If you mine there consistently, try setting the pool poll window of ur worker to the last 1hr or so.. should provide a more accurate sample. HW errors is the amount of diff1 work that ended up being invalid due to chip heat / clocks / instability / comm errors(I think) ... etc.... .. so yes hardware errors. HW error field, ideally(or at least according to way --avalon-auto) should be 2% or less of total diff1shares |
|
|
|
when are we going to be able to order 4th modules for batch 2 units?
aftermarket, like from bitmine.ch they are sold out. know of any others? thanks Like I said, once BTC value plummets, these modules will be dirt cheap, hold out =) |
|
|
|
|
now THATS stable =) NICE!
|
|
|
|
|
avalon switched from a huge sludge of thermal goop(thread u linked) .. ..to the thermal sheet shown in ur picture?
I find it hard to believe that the foil makes little / no contact w/ the chips under the pressure of the screws. It would have to touch them... that thermal foil type stuff is squishy right? ...
Given that, Im sure its just the thermal effeciency working in ur favor of the MX-2 over the horrible effeciency of a thermal pad. =)
Post screenshot of clocks / temps / HW error after several hours of mining(webgui) .. that would be great =)
If its enough of a difference, I may attempt this.
|
|
|
|
I cracked it! Hitting 120GH on a 3 module now   was wondering how long it'd take people to notice ( and more importantly share the constant that we've released on github.) the number you are all aiming for is 450  of course, that's not really possible on just air cooling. huh? I dont get it... ops wrong quote, I corrected, posted just to emphasize that the secret is on github and bold on SHARE... but I find it nice its something most people cant find. I still cant. Im still confused .. is there some magic being hinted too that we are unaware of or is this a silly joke of some sort... |
|
|
|
I cracked it! Hitting 120GH on a 3 module now was wondering how long it'd take people to notice ( and more importantly share the constant that we've released on github.) the number you are all aiming for is 450 of course, that's not really possible on just air cooling. huh? I dont get it... |
|
|
|
|
did ya figure it out? if not, the ip you changed it to, was it in the same subnet still?
|
|
|
|
This is strange.
- I cannot ping one of my avalons, and web interface stopped responding
- but on the pool I see that it still keeps submitting shares! And even the hash estimate for it is increasing.
how this can be possible? Maybe something is wrong in my LAN...
Perhaps it changed IP, due to your dhcp setup? nmap -v -sP your network range and look for new IP's that are "up" Yeah, this is why I have my avy set to static DHCP in router |
|
|
|
|
Show Posts
