|
581
|
Alternate cryptocurrencies / Mining (Altcoins) / Re: Swedish ASIC miner company kncminer.com
|
on: August 17, 2015, 05:34:17 PM
|
Hey, TXSteve ....
How is my latest firmware changes working for ya?
I think its working well on my single titan, its done some soft / hard resets once or 2x ... my code handled it as intended .. I think =)
Whats ur experience been?
Im gonna make an updated official release soon if all keeps going well.
I think it's ok too, still waiting for word on the 5.1/5.2 issue on the bfgminer thread haven't had much in the way of hard resets yet to confirm, temp control is solid !! Luke-Jr saying to use the git bisect command, you know anything about that? Looks like it checks revisions to find where a bug is introduced Nope, I dont =/ yeah it is beyond me too, would it be too much trouble to get a 5.1 version? that way I'll at least have temp control on that rig and then use 5.2 on the others I suppose many don't use load balance, but probably going to be a problem if anyone else tries it with 5.2 btw I did have a successful hard reset today, seems to be working Very cool, Im glad the soft / hard reset is finally working as intended.... thus far.... fingers crossed ... LOL If ur just using 5.1 for one rig, couldnt u just git clone 5.1 to that pi and compile it for yourself? Thats what I assumed u did anyways to run the comparisons no?... I wish I was that advanced, lol I just used the knc 2.0 image and tried your v.85 img too let me think about that, I'm trying to wrap my brain around this git stuff actually starting to make some sense, thx for the tip Oh, I see what you mean, the stock bfgminer is what you want? Wasnt something broken in it.... isnt that why everyone wanted the latest? lol I dont know anymore. Basically if you wanted that version again, u would need to go to the bfgminer_stock directory and just copy bfgminer from that folder to bfgminer folder then restart bfgminer. All of this is in /home/pi. Make a backup of the newest one first if you wanted to, by moving it to a diff filename. IE: mv bfgminer/bfgminer bfgminer/bfgminer_new_bak |
|
|
|
|
582
|
Alternate cryptocurrencies / Mining (Altcoins) / Re: Swedish ASIC miner company kncminer.com
|
on: August 17, 2015, 03:54:03 PM
|
Hey, TXSteve ....
How is my latest firmware changes working for ya?
I think its working well on my single titan, its done some soft / hard resets once or 2x ... my code handled it as intended .. I think =)
Whats ur experience been?
Im gonna make an updated official release soon if all keeps going well.
I think it's ok too, still waiting for word on the 5.1/5.2 issue on the bfgminer thread haven't had much in the way of hard resets yet to confirm, temp control is solid !! Luke-Jr saying to use the git bisect command, you know anything about that? Looks like it checks revisions to find where a bug is introduced Nope, I dont =/ yeah it is beyond me too, would it be too much trouble to get a 5.1 version? that way I'll at least have temp control on that rig and then use 5.2 on the others I suppose many don't use load balance, but probably going to be a problem if anyone else tries it with 5.2 btw I did have a successful hard reset today, seems to be working Very cool, Im glad the soft / hard reset is finally working as intended.... thus far.... fingers crossed ... LOL If ur just using 5.1 for one rig, couldnt u just git clone 5.1 to that pi and compile it for yourself? Thats what I assumed u did anyways to run the comparisons no?... |
|
|
|
|
583
|
Alternate cryptocurrencies / Mining (Altcoins) / Re: Swedish ASIC miner company kncminer.com
|
on: August 16, 2015, 10:23:35 PM
|
Hey, TXSteve ....
How is my latest firmware changes working for ya?
I think its working well on my single titan, its done some soft / hard resets once or 2x ... my code handled it as intended .. I think =)
Whats ur experience been?
Im gonna make an updated official release soon if all keeps going well.
I think it's ok too, still waiting for word on the 5.1/5.2 issue on the bfgminer thread haven't had much in the way of hard resets yet to confirm, temp control is solid !! Luke-Jr saying to use the git bisect command, you know anything about that? Looks like it checks revisions to find where a bug is introduced Nope, I dont =/ |
|
|
|
|
587
|
Bitcoin / Bitcoin Discussion / Re: Did you read this? This is crazy shit.
|
on: August 16, 2015, 01:12:03 AM
|
Eyes rolled as soon as I saw it's Mike Hearn. He and Gavin don't care about 'Bitcoin'... Not really. They have ulterior motives with this fork. Be careful and take what he writes with a grain of salt.
This is quite a longshot, but Satoshi's opinion is really needed about the matter here.
And that is exactly why an imposer appeared to please retards like you http://lists.linuxfoundation.org/pipermail/bitcoin-dev/2015-August/010238.htmlI have been following the recent block size debates through the mailing list. I had hoped the debate would resolve and that a fork proposal would achieve widespread consensus. However with the formal release of Bitcoin XT 0.11A, this looks unlikely to happen, and so I am forced to share my concerns about this very dangerous fork.
The developers of this pretender-Bitcoin claim to be following my original vision, but nothing could be further from the truth. When I designed Bitcoin, I designed it in such a way as to make future modifications to the consensus rules difficult without near unanimous agreement. Bitcoin was designed to be protected from the influence of charismatic leaders, even if their name is Gavin Andresen, Barack Obama, or Satoshi Nakamoto. Nearly everyone has to agree on a change, and they have to do it without being forced or pressured into it. By doing a fork in this way, these developers are violating the "original vision" they claim to honour.
They use my old writings to make claims about what Bitcoin was supposed to be. However I acknowledge that a lot has changed since that time, and new knowledge has been gained that contradicts some of my early opinions. For example I didn't anticipate pooled mining and its effects on the security of the network. Making Bitcoin a competitive monetary system while also preserving its security properties is not a trivial problem, and we should take more time to come up with a robust solution. I suspect we need a better incentive for users to run nodes instead of relying solely on altruism.
If two developers can fork Bitcoin and succeed in redefining what "Bitcoin" is, in the face of widespread technical criticism and through the use of populist tactics, then I will have no choice but to declare Bitcoin a failed project. Bitcoin was meant to be both technically and socially robust. This present situation has been very disappointing to watch unfold.
Satoshi Nakamoto
Enjoy your masturbation Unless the poster of this message signs it w/ one of the addresses that discovered blocks in the beginning (satoshi's blocks) .... its completely fake. |
|
|
|
|
589
|
Alternate cryptocurrencies / Mining (Altcoins) / Re: Swedish ASIC miner company kncminer.com
|
on: August 15, 2015, 06:47:07 PM
|
GenTarkin I think we got that problem fixed, now I have something else for you to look at :|
in this Bfgminer 5.2 I am getting a ton of stale share errors when using load balancing, it's like the buffer isn't getting properly flushed after a new block is found. Eventually it clears out and starts submitting valid shares. And it usually just effect 1 or 2 pools that are being load balanced. btw these pools run great when not load balanced
I reverted back to 5.1 and these issues went away
I realize that these are probably BFgminer bugs, but since 5.2 is part of the upgrade I'm throwing it out there on the off chance there is anything you can do about it
Well, I could revert to 5.1 in the build, but prefer to stay with the latest. Since that seems what people want. |
|
|
|
|
590
|
Alternate cryptocurrencies / Mining (Altcoins) / Re: Swedish ASIC miner company kncminer.com
|
on: August 15, 2015, 06:32:03 PM
|
|
Yeah, guys its ok if he sells it, It brings more publicity I guess to make people aware that such firmware exists. If they want to seek out the free version of it then so be it. I dont know much about licensing crap either so... w/e.
So yeah, he has my permission as long as a cut is coming to me =)
Ive never actually written software people are willing to pay for so, this is all new to me. ROFL!
Far as my latest work goes, theres been a lot done since my latest release. Will be making a new release soon once all the changes are tested thorougly, I may make it a non prerelease as well if all goes well =)
|
|
|
|
|
591
|
Alternate cryptocurrencies / Mining (Altcoins) / Re: Swedish ASIC miner company kncminer.com
|
on: August 15, 2015, 02:38:44 AM
|
OK ... go ahead and do a git pull, think I got the syntax nailed. It worked on my end for a fake hard reset & a live soft reset so... yeah
Also, I made it so in my loop it will attempt a soft reset every 60 seconds up to 7 times, if it fails all those it will do a hard reset at that point.
Now that my code is working, since that die of yours constantly shows 0 amps even with successful soft resets, it will succumb to my hard reset loop after it attempts 7 times. =(
ok I'll try it out I can write a custom version for you that will tell the KNC loop to ignore the die u have clocked at 150mhz that way it snot constantly doing a hard reset on you every 20mins =) Let me know. let me see how it goes, I might take you up on that yeah, It lasted about 12 min before the hard reset, I wonder why it took 5 min before starting the resets? maybe it initially has an amp reading?? maybe create a file that can be edited with a custom list of dies to ignore?? Alrighty, just pushed a commit for you. You can add dies in knc-asic/bypass_dies.conf file for any sort of resetting(bypasses the current checking in KNC's main loop). If you wanted you can add the dies that you have flagged a "off" as well to the file =) If you read the contents of that file, I think ull figure it out. In your case it would be this below the line in the file: 5 1 |
|
|
|
|
592
|
Alternate cryptocurrencies / Mining (Altcoins) / Re: Swedish ASIC miner company kncminer.com
|
on: August 14, 2015, 11:44:49 PM
|
OK ... go ahead and do a git pull, think I got the syntax nailed. It worked on my end for a fake hard reset & a live soft reset so... yeah
Also, I made it so in my loop it will attempt a soft reset every 60 seconds up to 7 times, if it fails all those it will do a hard reset at that point.
Now that my code is working, since that die of yours constantly shows 0 amps even with successful soft resets, it will succumb to my hard reset loop after it attempts 7 times. =(
ok I'll try it out I can write a custom version for you that will tell the KNC loop to ignore the die u have clocked at 150mhz that way it snot constantly doing a hard reset on you every 20mins =) Let me know. let me see how it goes, I might take you up on that yeah, It lasted about 12 min before the hard reset, I wonder why it took 5 min before starting the resets? maybe it initially has an amp reading?? maybe create a file that can be edited with a custom list of dies to ignore?? It takes about 5 mins before KNC's main loop flags the die for needing a reset(which sends it to my custom loop at that point) ... which is why previously when my code wasnt working correctly(before I fixed the syntax error) it it was just soft resetting every 6mins or so for you. Yeah, I may be able to setup a custom file for listing dies to ignore checking DCDC condition period. That will take a bit more research how to do, Im sure it isnt hard w/ grepping a text file =) |
|
|
|
|
594
|
Alternate cryptocurrencies / Mining (Altcoins) / Re: Swedish ASIC miner company kncminer.com
|
on: August 14, 2015, 10:01:11 PM
|
OK ... go ahead and do a git pull, think I got the syntax nailed. It worked on my end for a fake hard reset & a live soft reset so... yeah
Also, I made it so in my loop it will attempt a soft reset every 60 seconds up to 7 times, if it fails all those it will do a hard reset at that point.
Now that my code is working, since that die of yours constantly shows 0 amps even with successful soft resets, it will succumb to my hard reset loop after it attempts 7 times. =(
ok I'll try it out I can write a custom version for you that will tell the KNC loop to ignore the die u have clocked at 150mhz that way it snot constantly doing a hard reset on you every 20mins =) Let me know. |
|
|
|
|
595
|
Alternate cryptocurrencies / Mining (Altcoins) / Re: Swedish ASIC miner company kncminer.com
|
on: August 14, 2015, 09:50:35 PM
|
|
OK ... go ahead and do a git pull, think I got the syntax nailed. It worked on my end for a fake hard reset & a live soft reset so... yeah
Also, I made it so in my loop it will attempt a soft reset every 60 seconds up to 7 times, if it fails all those it will do a hard reset at that point.
Now that my code is working, since that die of yours constantly shows 0 amps even with successful soft resets, it will succumb to my hard reset loop after it attempts 7 times. =(
|
|
|
|
|
597
|
Alternate cryptocurrencies / Mining (Altcoins) / Re: Swedish ASIC miner company kncminer.com
|
on: August 14, 2015, 08:59:43 PM
|
OK, added current logging to KNC's loop for when it detects a DCDC that has failed current test.
Paste log =)
ok, Will do here's a screen shot of it hashing away -- it only ran a couple mins there   so, restart the monitoring script as I described above and paste the latest contents of log since its restart here. If both DCDC's are really reading 0 then dont know what to say, not much I can do lol It could be that the DCDC current detection script is actually detecting an erronous output from the DCDC's in which case it sets the measured amps to 0, and thats why the die is being flagged for reset by the main loop (KNC's loop) Thats really beyond my control =/ yeah, I don't know -- the extra soft resets don't seem to be hurting anything ... what is suppose to happen when a soft reset fails? into the loop for a count of ten, or does knc sending into the loop too mess that up? [2015-08-14 14:53:51] --Start monitoring!-- DCDC temp monitoring ENABLED & threshold set to: 90 Manually disabled die detected, skipping dead die detection. ASIC# 4, DIE# 2 Manually disabled die detected, skipping dead die detection. ASIC# 4, DIE# 4 Moving on with dead die test, no manual disabled die found Current measurement on ASIC# 5 DIE# 1: 0 Amps Current measurement on ASIC# 5 DIE# 1: 0 Amps [2015-08-14 14:58:48] Die 5-1 requires restartAttempting softreset of ASIC# 5 DIE# 1 { "asic_6_voltage": { "die2": "-0.0366" }, "asic_6_frequency": { "die2": "150" } } STATUS=S,When=1439582340,Code=92,Msg=PGA 0 set OK: Die setup Ok; asic 5 die 1 cmd RECONFIGURE,Description=bfgminer 5.2.0| Detected AMPS DCDC0 0 Detected AMPS DCDC1 0 [2015-08-14 14:59:30] Die 5-1 restarted Manually disabled die detected, skipping dead die detection. ASIC# 4, DIE# 2 Manually disabled die detected, skipping dead die detection. ASIC# 4, DIE# 4 Moving on with dead die test, no manual disabled die found Current measurement on ASIC# 5 DIE# 1: 0 Amps Current measurement on ASIC# 5 DIE# 1: 0 Amps [2015-08-14 15:04:43] Die 5-1 requires restartAttempting softreset of ASIC# 5 DIE# 1 { "asic_6_voltage": { "die2": "-0.0366" }, "asic_6_frequency": { "die2": "150" } } STATUS=S,When=1439582694,Code=92,Msg=PGA 0 set OK: Die setup Ok; asic 5 die 1 cmd RECONFIGURE,Description=bfgminer 5.2.0| Detected AMPS DCDC0 0 Detected AMPS DCDC1 0 [2015-08-14 15:05:25] Die 5-1 restarted Yeahp, KNC's loop is detecting both DCDC's @ 0 amps SO..... my script is gonna do soft resets on that die all the time and so would KNC's original script LOL On another note: So, just noticed something, my AND comparison in my loop is not evaluating correctly, which is why its not doing the up to 10 soft resets. I have NO idea why its not working as designed. Will have to find some different syntax to try. |
|
|
|
|
598
|
Alternate cryptocurrencies / Mining (Altcoins) / Re: Swedish ASIC miner company kncminer.com
|
on: August 14, 2015, 08:01:11 PM
|
OK, added current logging to KNC's loop for when it detects a DCDC that has failed current test.
Paste log =)
ok, Will do here's a screen shot of it hashing away -- it only ran a couple mins there so, restart the monitoring script as I described above and paste the latest contents of log since its restart here. If both DCDC's are really reading 0 then dont know what to say, not much I can do lol It could be that the DCDC current detection script is actually detecting an erronous output from the DCDC's in which case it sets the measured amps to 0, and thats why the die is being flagged for reset by the main loop (KNC's loop) Thats really beyond my control =/ |
|
|
|
|
600
|
Alternate cryptocurrencies / Mining (Altcoins) / Re: Swedish ASIC miner company kncminer.com
|
on: August 14, 2015, 07:43:28 PM
|
Alright, do perform a git pull n test it out.
Basically, if I have it set correctly, Ive modified KNC's loop to see if either DCDC are supplying current, if so then it doesnt kick it over to my loop(the custom resetting loop)
If all is correct, it will only kick over to my custom reset loop when both dcdc's on a die are registering current below the threshold of 5 amps.
ok, I'll check it now looks like it is still going into that loop, I haven't had a failed soft reset yet -- otherwise it's running good sometimes it scrolls "KNC 4b[5:1:55]: Got nonce for unknown work in slot 0" before the reset, other times not (always been like that)
[2015-08-14 13:52:24] Die 5-1 requires restartAttempting softreset of ASIC# 5 DIE# 1 { "asic_6_voltage": { "die2": "-0.0366" }, "asic_6_frequency": { "die2": "150" } } STATUS=S,When=1439578355,Code=92,Msg=PGA 0 set OK: Die setup Ok; asic 5 die 1 cmd RECONFIGURE,Description=bfgminer 5.2.0| Detected AMPS DCDC0 0 Detected AMPS DCDC1 0 [2015-08-14 13:53:05] Die 5-1 restarted Manually disabled die detected, skipping dead die detection. ASIC# 4, DIE# 2 Manually disabled die detected, skipping dead die detection. ASIC# 4, DIE# 4 Moving on with dead die test, no manual disabled die found [2015-08-14 13:58:24] Die 5-1 requires restartAttempting softreset of ASIC# 5 DIE# 1 { "asic_6_voltage": { "die2": "-0.0366" }, "asic_6_frequency": { "die2": "150" } } STATUS=S,When=1439578716,Code=92,Msg=PGA 0 set OK: Die setup Ok; asic 5 die 1 cmd RECONFIGURE,Description=bfgminer 5.2.0| Detected AMPS DCDC0 0 Detected AMPS DCDC1 0 [2015-08-14 13:59:06] Die 5-1 restarted Manually disabled die detected, skipping dead die detection. ASIC# 4, DIE# 2 Manually disabled die detected, skipping dead die detection. ASIC# 4, DIE# 4 Moving on with dead die test, no manual disabled die found [2015-08-14 14:04:24] Die 5-1 requires restartAttempting softreset of ASIC# 5 DIE# 1 { "asic_6_voltage": { "die2": "-0.0366" }, "asic_6_frequency": { "die2": "150" } } STATUS=S,When=1439579075,Code=92,Msg=PGA 0 set OK: Die setup Ok; asic 5 die 1 cmd RECONFIGURE,Description=bfgminer 5.2.0| Detected AMPS DCDC0 0 Detected AMPS DCDC1 0 [2015-08-14 14:05:06] Die 5-1 restarted Manually disabled die detected, skipping dead die detection. ASIC# 4, DIE# 2 Manually disabled die detected, skipping dead die detection. ASIC# 4, DIE# 4 Moving on with dead die test, no manual disabled die found [2015-08-14 14:10:19] Die 5-1 requires restartAttempting softreset of ASIC# 5 DIE# 1 { "asic_6_voltage": { "die2": "-0.0366" }, "asic_6_frequency": { "die2": "150" } } STATUS=S,When=1439579427,Code=92,Msg=PGA 0 set OK: Die setup Ok; asic 5 die 1 cmd RECONFIGURE,Description=bfgminer 5.2.0| Detected AMPS DCDC0 0 Detected AMPS DCDC1 0 [2015-08-14 14:10:57] Die 5-1 restarted BTW, whenever you do a git pull .... reapply your DCDC monitoring settings(in advanced tab) so it restarts the monitoring script. Because just downloading the changes wont change the running script. |
|
|
|
|
Show Posts
