Search content
Sort by
Showing 15 of 15 results by felix64
KnC: core 3-0 was disabled due to 3 HW errors in a row
core 3-82
core 3-162
core 3-52
core 3-87
core 3-50
core 3-179
core 3-177
core 3-45
core 3-27
core 3-188
core 3-35
core 3-77
core 3-40
core 3-58
This is with cgminer-3.8.2 tuned. It makes no difference between stable and tuned.
My die 3 is the problem one.
I get an occasional errors from die 4 and 0 with one bad thread
KnC: core 4-0 was disabled due to 3 HW errors in a row
KnC: core 4-130 was disabled due to 3 HW errors in a row
KnC: core 4-118 was disabled due to 3 HW errors in a row
KnC: core 4-64 was disabled due to 3 HW errors in a row
KnC: core 4-113 was disabled due to 3 HW errors in a row
KnC: core 0-33 was disabled due to 3 HW errors in a row
But my die 3 is the troublemaker.
(5s) 502.8G (avg): 498.6Gh/s | A:4567616 R: 38764 HW: 221371 WU: 6965.5/m
[/quote]
felix is it 15 bad cores or 5?
You know that with the tuning cgminer it turns cores on and off to try and find a stable medium.
What are your HW error %'s?
I've given up on the firmwares that pump the voltage up (>0.97) and tune the cores, I'm sticking with 0.96 and the non tuning 3.8.2 cgminer and my HW errors are down from 4.5% to 1.3% and dropping.
[/quote]
core 3-82
core 3-162
core 3-52
core 3-87
core 3-50
core 3-179
core 3-177
core 3-45
core 3-27
core 3-188
core 3-35
core 3-77
core 3-40
core 3-58
This is with cgminer-3.8.2 tuned. It makes no difference between stable and tuned.
My die 3 is the problem one.
I get an occasional errors from die 4 and 0 with one bad thread
KnC: core 4-0 was disabled due to 3 HW errors in a row
KnC: core 4-130 was disabled due to 3 HW errors in a row
KnC: core 4-118 was disabled due to 3 HW errors in a row
KnC: core 4-64 was disabled due to 3 HW errors in a row
KnC: core 4-113 was disabled due to 3 HW errors in a row
KnC: core 0-33 was disabled due to 3 HW errors in a row
But my die 3 is the troublemaker.
(5s) 502.8G (avg): 498.6Gh/s | A:4567616 R: 38764 HW: 221371 WU: 6965.5/m
[/quote]
felix is it 15 bad cores or 5?
You know that with the tuning cgminer it turns cores on and off to try and find a stable medium.
What are your HW error %'s?
I've given up on the firmwares that pump the voltage up (>0.97) and tune the cores, I'm sticking with 0.96 and the non tuning 3.8.2 cgminer and my HW errors are down from 4.5% to 1.3% and dropping.
[/quote]
Sorry this is a little late but how many bad cores do you need before KNC will allow an RMA?
Was your ASIC completely dead before KNC would give you an RMA?
I have one ASIC with probably 15 bad cores which slows my hashrate...
Or just live with it?
>>>As soon as the first report good numbers I'll go for it.
>>>Currently running stable on 3.8.2 with my 5/192 bad cores board, so I don't want to mess with it now.
Was your ASIC completely dead before KNC would give you an RMA?
I have one ASIC with probably 15 bad cores which slows my hashrate...
Or just live with it?
>>>As soon as the first report good numbers I'll go for it.
>>>Currently running stable on 3.8.2 with my 5/192 bad cores board, so I don't want to mess with it now.
Thanks alot for writing this. Running 3.6.6 of your code now.
My Jupiter is at 514Gh/s which is likely the real number.
Have not messed with the pressing down on anything yet. Cover is off. Will try putting the cover back on and see if higher temp increases the hash rate.
My Jupiter is at 514Gh/s which is likely the real number.
Have not messed with the pressing down on anything yet. Cover is off. Will try putting the cover back on and see if higher temp increases the hash rate.
hello and thank you ckolivas (and kano if he was involved in anyway in this new release of cgminer).
2ndly, for those of US that find this new version of cgminer works/improves their mining, please don't forget to send some btc love to ckolivas. Lets keep these important members of the btc community well fed so their minds are tip top.
And finally, ckolivas, did you see anything in knc miners code that would cause lower hashing rates, not just report inaccurate HW errors?
thanks.
You're welcome. I didn't spot anything on a brief glance of the code. I have not done a full audit of the code as of yet. It appears quite sound.2ndly, for those of US that find this new version of cgminer works/improves their mining, please don't forget to send some btc love to ckolivas. Lets keep these important members of the btc community well fed so their minds are tip top.
And finally, ckolivas, did you see anything in knc miners code that would cause lower hashing rates, not just report inaccurate HW errors?
thanks.
Good point, thanks.
I asked Liam over the phone and he told me max temp for the ASIC chips is 105C, so you are far from the point where they are overheating 
What are the temps?
http://i.imgur.com/TxUspKh.png
BAM... slow one still not quite done climbing, but Ewikis a happy camper now!
all 0.97, and no doggone fans... not even the case fans, only the heatsink fans!
BAM... slow one still not quite done climbing, but Ewikis a happy camper now!
all 0.97, and no doggone fans... not even the case fans, only the heatsink fans!
However I am going to swap out the stock fans on the case and instead put in higher CFM fans.
Let us know what you use...
Did you SSH into the box to bring up Cgminer?
do you not see that it is Putty?? go log into his miner @ 172.16.1.6 and point it to your bitcoin address lulz
Fat chance routing to RFC 1913 IP space but whatever. Saw the link to Putty after watching it a couple times. I like that 580+ hash rate at times.
Did you SSH into the box to bring up Cgminer? I've seen mention of the web interface for setup but curious how you got that has screen up. The web interface doesn't have the info in your video. That video really helped me relax.
Thank you very much for sharing.
Thank you very much for sharing.
Only got 1 of 3 "1-500" Jupiters that were all suppose to ship together. 
The one Jupiter hashing: https://www.youtube.com/watch?v=G-92pvoxKq0
The one Jupiter hashing: https://www.youtube.com/watch?v=G-92pvoxKq0
How do we configure our miners? Can you plug in a monitor, mouse and keyboard setup to them directly, or are settings accessed via LAN?
Exactly what I was wondering.
KNC said it would be "stand alone".
And what pool would we join to get running?
Oh boy, this'll be fun.
pretty sure its all done by lan, ssh login to the beaglebone then edit settings form there. should be quite simple really. Use any pool you like!
seems like everyone knows about ssh but me, how do you access a linux machine, using ssh from a windows (XP) machine?
Putty. Options are ssh, telnet, rlogin, raw, not in that order.
SecureCRT from www.vandyke.com is probably overkill but a great program.
Digging the hash rate:
Hashrate Average Weighted Shares
3 hours 580.52 Gh/s 1459765
22.5 minutes 609.41 Gh/s 191550
256 seconds 633.50 Gh/s 37759
128 seconds 707.89 Gh/s 21097
Wonder if just 1 Jupiter
This at 10:02am PDT
Hashrate Average Weighted Shares
3 hours 580.52 Gh/s 1459765
22.5 minutes 609.41 Gh/s 191550
256 seconds 633.50 Gh/s 37759
128 seconds 707.89 Gh/s 21097
Wonder if just 1 Jupiter
This at 10:02am PDT
This thread is a total joke - you have finger pointers, speculators, trolls(negative speculators), and those who actually want to share information.
When KNC shows the ASIC all that sh*t goes away.
felix64
http://i.imgur.com/KXzVNV6.jpg
- 365GH vs. 60GH.
- Silent vs. loud as fuck
- Waiting for 13 months after payment vs. waiting for one month after payment
- Both units are around $60/GH. Both use ~270W when mining. They are almost the same size.
- 365GH vs. 60GH.
- Silent vs. loud as fuck
- Waiting for 13 months after payment vs. waiting for one month after payment
- Both units are around $60/GH. Both use ~270W when mining. They are almost the same size.
Thank you so much for posting this. Really. The 60GH Single is so loud.