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 inhome/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
I used cp -rbackup/bfgminer/* bfgminer .... lol so easy, you wouldn't believe how complicated I was making that
thanks so much for another tip
when I do a git pull will it upgrade to 5.2 again?
Yeah, it will probably complain about local changes and needing to stash them, not sure tho =/ ... or it will just reupdate the file haha!
I could possibly write a webgui box & submit that allows a pulldown of which miner to use and restart the miner w/ selected version. But thats more than I have time to code atm, if you really want it Im sure I could do that sometime this week. More donations would get me coding it for sure haha =P
well, this is what I found out.
If I start with your v.9 img, then restore 5.1, then do a git pull it'll grab your updates and leave 5.1 intact.
If I start with v.93, then restore 5.1, 5.1 overwrites some of your stuff and git pull doesn't get it back
maybe it has to do with an index or something where git keeps track of what's been updated, and if you change it git doesn't know -- but I am just speculating
let me think about that box, I am still not done messing around here
