v2.02 beta :: 14/12 :: test version
Download:
https://mega.nz/#!DghG2KwC!OJEK4_d47skRB6yrLRE2bfzlX7FWXLXzgoKA_q5dKco
Changes 14/12:
- fixed auto recover from xxxx
- cleaned up kernel logging
- a bit more aggressive tuning
- tunes down faster now when too many HW errors are detected
Changes 13/12:
- Totally rewritten code base, based from latest available bitmain / cgminer sources
- ASIC's now automatically recovers from xxxxx errors without restarting (The auto reboot options are still in there in case it doesn't succeed)
- blazing fast mining status overview in the webinterface
- as requested: the dev mining starts later now (after 5 minutes)
- as requested: dev pools status is now visible in the miner status
and last but not least...
- added a first version of the auto tune!
When enabled this will search for the best possible frequency at the given voltage setting. The first 5 to 10 minutes it will search for a good base to start from. After that it checks for excessive HW errors every 15 minutes and adjusts the frequency accordingly.
Important: This feature is not completely finished and the startup is a bit slow now.. Therefore I need your help. So what do you need to do:
set your advanced settings the same as displayed bellow
let it run for at least 20 minutes
PM your (complete) kernel log
By doing so I can get to a conclusion what the starting frequency of the auto tune algorithm should be.
In case you want to help more: increase the voltage a bit and do the steps above again as it will give some more information
Thank you!
https://img15.hostingpics.net/pics/453940Untitled.jpg
Download:
https://mega.nz/#!DghG2KwC!OJEK4_d47skRB6yrLRE2bfzlX7FWXLXzgoKA_q5dKco
Changes 14/12:
- fixed auto recover from xxxx
- cleaned up kernel logging
- a bit more aggressive tuning
- tunes down faster now when too many HW errors are detected
Changes 13/12:
- Totally rewritten code base, based from latest available bitmain / cgminer sources
- ASIC's now automatically recovers from xxxxx errors without restarting (The auto reboot options are still in there in case it doesn't succeed)
- blazing fast mining status overview in the webinterface
- as requested: the dev mining starts later now (after 5 minutes)
- as requested: dev pools status is now visible in the miner status
and last but not least...
- added a first version of the auto tune!
When enabled this will search for the best possible frequency at the given voltage setting. The first 5 to 10 minutes it will search for a good base to start from. After that it checks for excessive HW errors every 15 minutes and adjusts the frequency accordingly.
Important: This feature is not completely finished and the startup is a bit slow now.. Therefore I need your help. So what do you need to do:
set your advanced settings the same as displayed bellow
let it run for at least 20 minutes
PM your (complete) kernel log
By doing so I can get to a conclusion what the starting frequency of the auto tune algorithm should be.
In case you want to help more: increase the voltage a bit and do the steps above again as it will give some more information
Thank you!
https://img15.hostingpics.net/pics/453940Untitled.jpg
Please test and give feedback / a kernel log how it works for you. I need some feedback on this version guys
Well, i think it screwed my string 2 up Blissz!
Now no matter what software i run, INCLUDING BM FW Newest, I NOW GET A LOT OF HW on my coolest string.
When I upgraded or downgraded, I left it on keep settings, WAS THAT WRONG? Please inform....
It is still cooler than the other two and not hot, but it gives HW now.
Hmmmmm
GRRRRRRRRRR
Appreciate any help.
M
I went back to 12/10 for now....I Have to run the card on three levels lower frequency than the other two.
It feels like it has an over written temperature warning sensor....
i don't know,
This sucked today.
Lost my 8 bucks!