|
jungle_dave
|
 |
October 24, 2013, 01:22:02 PM |
|
Thanks Adeel!
It looks like this firmware upgrade is only from .95 to .97 (woops) even so, some people are only getting 250 GH/s (jupiter) as an improvement .....
This reeks of badly debugged device driver!
Anyone want to look at the code?
|
|
|
|
|
|
|
|
|
|
|
|
|
|
The grue lurks in the darkest places of the earth. Its favorite diet is adventurers, but its insatiable appetite is tempered by its fear of light. No grue has ever been seen by the light of day, and few have survived its fearsome jaws to tell the tale.
|
|
|
Advertised sites are not endorsed by the Bitcoin Forum. They may be unsafe, untrustworthy, or illegal in your jurisdiction.
|
|
|
philipma1957
Legendary
 Online
Activity: 4116
Merit: 7853
'The right to privacy matters'
|
|
October 24, 2013, 01:25:08 PM |
|
Thank you philipma1957 , its just that 0.3 BTC x 15 days = 1.5 btc lost , a single restart wont loose as much.  But after reading what Redacted posted , I think we should just go back to 0.95 & not touch the machines there after , I am fully confident that organizers of this group buy are genuine good people & will take care of things fine. that is not the loss. the loss is .389 btc in 10 days. 30gh is lost and it could be due to a lessor chip. 30gh is .0567 btc today 1 day. 30gh is .0567 btc tomorrow 2 days. that comes to .1134 btc on the third day when diff jumps to 380 mill the loss is .039 btc for 1 day so 11 days at that difficulty is .429 btc plus the .1134 btc that comes .5424 over the next 13 days |
|
|
|
|
-Redacted-
|
|
October 24, 2013, 01:38:25 PM
Last edit: October 24, 2013, 01:52:41 PM by -Redacted- |
|
The upgrade was not a smooth process like other ones. I had the problem of getting 1GH/s after the upgrade and followed the advise in http://forum.kncminer.com/forum/main...0074-erm-1gh-s - Thanks eXceed. Downgrade to 0.95. Before restarting device, ssh to box and copy all *.factory files to original filenames. Restart device. Upgrade EnableCores.bin. Restart. Profit. I did a hard reset instead of doing the copy *.factory files as I believe this does the same step. I then upgraded to 0.97 directly from 0.95 and hey presto working again. I've only been going 10 minutes and my average is already up by 5GH/s. In the past I've had to give it at least 8 hours to get to this level, so looking good so far. The so called "loss" is .0389 BTC, or .000389 BTC per share - about 7 cents per share per day over a ten day period. So, how about figuring how much "gain" there has been at the current hashrate above 400 Gh/s (which was the promised hashrate of the group buy.) on the third day when diff jumps to 380 mill the loss is .039 btc for 1 day so 11 days at that difficulty is .429 btc plus the .1134 btc
that comes .5424 over the next 13 days
or .0052 per share over the next two weeks = $0.99. Now calculate how much gain there has been on a minimum of 120 Gh/s over the promised 400 Gh/s since the GB started hashing. I'm not trying to be a smart-ass here, but you are calling something a "loss" when it is not - it is slightly less of a gain over the expected payout for 400 Gh/s == hashing at 520 Gh/s versus possibly hashing at 550 Gh/s. And we ARE looking at the issue to see what we can do.-R- |
|
|
|
|
|
Tiennou74
|
|
October 24, 2013, 02:34:44 PM |
|
I saw this.
Hope it helps :
from my personal experoence: flashed 96 had to restart cgminer two times and then went good with 274Ghs. flashed 97 had to restart cgminer one time and then 284Ghs. i now think cgminer must be restarted at least one time after upgrading firmwares
Still super happy with our GB!
Thanks
|
|
|
|
|
|
-Redacted-
|
|
October 24, 2013, 02:48:31 PM |
|
I saw this.
Hope it helps :
from my personal experoence: flashed 96 had to restart cgminer two times and then went good with 274Ghs. flashed 97 had to restart cgminer one time and then 284Ghs. i now think cgminer must be restarted at least one time after upgrading firmwares
Still super happy with our GB!
Thanks
Thanks! We're really trying to keep everything transparent and above-board here..96 does seem to be better than .97 on good jupiters. I haven't tried it on a bad jupiter yet.. so far bad jupiters hash better on .94 'overclocked' running bfgminer but the VRMs/chips do have to take a beating.. perhaps heatsinks?
to 'cure' modules, remove the asic_test file and install .96, run enable cores and few times and reboot. It should do its 1-2 min asic tests and then reboot itself. you should have more enabled cores again
There is so much information flying back and forth about the various firmwares that , at the moment, it's difficult to know what's what. it's probably better to hold off on updates in the future until they're at least a week or so old. Might as well let OTHER people figure stuff out before we do something that might adversely affect our machines.... Dunno. Some people say .94 works better, others .95, .96, .97 - some say .97 breaks their machines, so until things calm down for a few days, there isn't much point in doing anything else - lest we keep screwing around and end up with everything hashing at 450 instead of 520... |
|
|
|
|
|
bobsag3
|
|
October 24, 2013, 02:53:12 PM |
|
I saw this.
Hope it helps :
from my personal experoence: flashed 96 had to restart cgminer two times and then went good with 274Ghs. flashed 97 had to restart cgminer one time and then 284Ghs. i now think cgminer must be restarted at least one time after upgrading firmwares
Still super happy with our GB!
Thanks
Thanks! We're really trying to keep everything transparent and above-board here..96 does seem to be better than .97 on good jupiters. I haven't tried it on a bad jupiter yet.. so far bad jupiters hash better on .94 'overclocked' running bfgminer but the VRMs/chips do have to take a beating.. perhaps heatsinks?
to 'cure' modules, remove the asic_test file and install .96, run enable cores and few times and reboot. It should do its 1-2 min asic tests and then reboot itself. you should have more enabled cores again
There is so much information flying back and forth about the various firmwares that , at the moment, it's difficult to know what's what. it's probably better to hold off on updates in the future until they're at least a week or so old. Might as well let OTHER people figure stuff out before we do something that might adversely affect our machines.... Dunno. Some people say .94 works better, others .95, .96, .97 - some say .97 breaks their machines, so until things calm down for a few days, there isn't much point in doing anything else - lest we keep screwing around and end up with everything hashing at 450 instead of 520... Im not going to touch .97 with a 10ft pole until I determine weather or not it had a hand in me having a large issue with a non-GB jupiter. |
|
|
|
|
|
Miramyn
|
|
October 24, 2013, 02:55:10 PM |
|
I am a big proponent of the "If it ain't broke, don't fix it" school of thought.
I'd rather have unit working and working at 30% over spec (520 instead of 400) than try to squeeze another 5% out of it and end up like some of the reports where they are hashing at 0GH or 1GH/s
|
When I was younger we didn't have behavioural disorders. They called it "being a brat". It was as simple as that!
|
|
|
philipma1957
Legendary
Online
Activity: 4116
Merit: 7853
'The right to privacy matters'
|
|
October 24, 2013, 04:19:41 PM |
|
I am a big proponent of the "If it ain't broke, don't fix it" school of thought.
I'd rather have unit working and working at 30% over spec (520 instead of 400) than try to squeeze another 5% out of it and end up like some of the reports where they are hashing at 0GH or 1GH/s
Look lets say the btc lost comes to .52BTC over the next 13 days that is about 104 usd. I donated an 8 pack of ups batteries to the coop they cost 109 usd. http://www.rakuten.com/pr/product.aspx?sku=246155454 I am having these dropped shipped as a donation to the coop on me free gratis this will make up for the "missing" btc for the next 13 days. With hashrate having some importance uptime is the most important thing since diff just rockets. So the coop is not getting f''d as it will now have 2 extra battery packs for the UPS. At bobsag3 I am sending a pm with tracking for the donation 8 pack. best regards Phil |
|
|
|
|
|
|
mootinator
|
|
October 24, 2013, 08:07:47 PM |
|
Thought of the Day: If you're worried this GB can't get a positive ROI, imagine how badly the other ones are doing ;P
|
No
|
|
|
|
thomas_s
|
|
October 24, 2013, 08:14:20 PM |
|
Both rigs are divided 50/50 R5/R6. |
|
|
|
|
philipma1957
Legendary
Online
Activity: 4116
Merit: 7853
'The right to privacy matters'
|
|
October 24, 2013, 09:37:17 PM |
|
Both rigs are divided 50/50 R5/R6. so it is not like r5 gets over and r6 gets screwed. it is share and share alike. so then there is no difference in either group just the overall hashing which means the 30gh "lost" is 15 gh a group even less to worry about. |
|
|
|
|
DyslexicZombei (OP)
|
|
October 26, 2013, 03:38:23 AM |
|
Both rigs are divided 50/50 R5/R6. so it is not like r5 gets over and r6 gets screwed. it is share and share alike. so then there is no difference in either group just the overall hashing which means the 30gh "lost" is 15 gh a group even less to worry about. I just got a msg. from bobsag3. He received boxes and boxes from NY. The exact quote was "so many boxes..."  Thank you Philip! For those that don't know: he gave the co-op a really, really good UPS deal. He sold me $1100+ worth of UPS/Batteries + he threw in an extra $109 worth of extra batteries for only $525. These funds were mostly mine (I had also forgotten to add UPS protection to our at-cost R2 and R2B, but since that was my mistake, I paid for that out of pocket). Some of its also came from remnants of leftover funds from early GBs after R1. Philip, who is also our backup local miner host for R1 in NY, also took the time to wrap and ship those boxes and boxes for the co-op, so he deserves a big thank you from the rest of the co-op IMO. You're a good man. Cheers! |
|
|
|
|
|
Miramyn
|
|
October 26, 2013, 05:44:27 PM |
|
Thanks Philip,
That is definitely above and beyond and awesome news for the Co-op
|
When I was younger we didn't have behavioural disorders. They called it "being a brat". It was as simple as that!
|
|
|
|
Miramyn
|
|
October 26, 2013, 06:05:43 PM |
|
BTW If any fellow Co-op'er is considering trying CEX.IO I would really appreciate if you used my referral link so I can bump up my hashing. https://cex.io/r/0/Miramyn/0/PM me with any questions and I will do my best to answer. |
When I was younger we didn't have behavioural disorders. They called it "being a brat". It was as simple as that!
|
|
|
|
bbxx
|
|
October 27, 2013, 10:18:46 AM |
|
when will be the next payout ? can we set payment to every week? f.ex. sunday |
|
|
|
|
philipma1957
Legendary
Online
Activity: 4116
Merit: 7853
'The right to privacy matters'
|
|
October 27, 2013, 11:26:46 AM
Last edit: October 27, 2013, 12:00:52 PM by philipma1957 |
|
when will be the next payout ? can we set payment to every week? f.ex. sunday THEY ARE DOING 2 payments a month so oct 31 or nov 1. the 2 addresses have 9.11 and 9.07 which is split between gb5 and gb6 so we are at 9.09 for each. which would be .0909 a share. it should grow to about .12 - .13 a share by the 31st. coinbase is 184 usd a coin. I have 19 shares between the 2 buys. so I will get about 2.28 to 2.47 coins. It is early morning so my math my be wrong. |
|
|
|
|
thomas_s
|
|
October 27, 2013, 01:15:56 PM |
|
when will be the next payout ? can we set payment to every week? f.ex. sunday THEY ARE DOING 2 payments a month so oct 31 or nov 1. the 2 addresses have 9.11 and 9.07 which is split between gb5 and gb6 so we are at 9.09 for each. which would be .0909 a share. it should grow to about .12 - .13 a share by the 31st. coinbase is 184 usd a coin. I have 19 shares between the 2 buys. so I will get about 2.28 to 2.47 coins. It is early morning so my math my be wrong. We don't maths we hash |
|
|
|
|
|
Ashitank
|
|
October 29, 2013, 03:49:43 AM |
|
KNC Upcoming firmware News : https://www.kncminer.com/news/news-59All, We have noticed an increase in failures with our boxes when the firmware has been updated to 0.97. There has been a bug identified in this firmware which can cause drop in performance in certain circumstances . There is a fix right now undergoing development but it’s not quite ready to release yet as it must undergo more testing overnight. We are very aware that our customers are waiting for this hotfix to rescue some boxes who’s performance has dropped after applying 0.97. The 0.98 release which is scheduled for release tomorrow will contain 1, A solution to address the bug which can cause dramatically reduced performance. 2, A bug fix which will stop the slowly reducing performance over time, 3, A new version of the CGMiner binary provided to us by the CGMiner developer’s The update will be available tomorrow form our website, Thanks KnCMiner Team |
|
|
|
|
|
DyslexicZombei (OP)
|
|
October 29, 2013, 06:41:42 AM |
|
I say we read that with a grain of salt and wait for other canaries to test the firmware before us.
I told you guys as someone that's a veteran pro to R&D that these miners are prototypes. Some poor miners chasing 10-30GH/s sometimes end up bricking a unit in the process like that poor guy czz in the CH forum whose problems began immediately after .97 was launched and he installed it coincidentally.
He has lost completely unrecoverable hashing time and hashrate in the process. He will likely never reach ROI unless he can take advantage of arbitrage, somehow. I wish that I could've helped him further.
Let's not be the canary in the coal mine (AKA first to install), until we see that the first canaries haven't died.
|
|
|
|
|
|
