Show Posts
I am not going to claim much technical knowledge about chips.. but from what I read, sha2 asic chips gives up error checking for speed, hence the HW errors...
as long as the pool is reporting a good hashrate, which is estimated by accepted shares.. then your good to go, the pool pays you for your shares!!
It's all about the balance. If it's too much HW, you're losing accepted shares but if your overall hashrate is much higher, it could be desirable anyway.
Just have to find the sweet spot. 393.75mhz has worked best for me.
Mine:
375Mhz - 195 or so GHs - almost no HW errors
393.75Mhz - 204 GHs - 0.06% HW
400Mhz - 206 GHs - 1.98% HW
The HW seems miniscule in the example above, but 393.75 resulted in the best Accepted rate.
Could you please post the the freq and time out numbers you're using for 393.75? I can't seem to find them in the thread. Thanks
option 'freq_value' '5f05' #393.75M
option 'chip_freq' '393.75'
option 'timeout' '36'
I am using the same seems to run much better then 400
First of all Hello for my first post and second I agree with the above, after experimenting with a few frequency's and running 10 hour benchmarks on each i have found the sweet to spot to be 393.75, at 375 i get no hardware errors at all for a speed of about 195gh but at 393 it gains that extra 10gh (205gh) with very minimal HW. Its interesting that another small bump above this can push the HW error rate well over 1%. So i guess bottom line is don't set it at 400 its not worth 1-2gh for all the hardware errors imo. I'm going to try some cooling mods on the unit and will post results later
