So we’ve replaced the R52 with a 68 kOhm resistor, assembled everything up (do not try to run the ASIC disassembled with this mod as you can burn the voltage regulators in a matter of a few seconds). With these settings we were planning to get stable around 600 KHS if we would succeed in actually running the GC3355 chips at a bit over 2 volts. With this modification we were aiming to get 1400 MHz while still fitting in the power consumption that the ASIC could handle in Dual Mining mode or about 60W, however running in Scrypt only mode. Well, we have decided to try out and push things to the maximum, namely replacing the R52 resistor with a 68 kOhm 402 1% SMD resistor. Back then we discussed what could be the theoretical maximum you might be able to push the voltmod to in order to try to get the best possible overclock, though that would be achieved with an unreasonably high power usage. The last time we talked about voltmodding the 5-chip Gridseed ASIC devices we did what we considered the optimal voltmod for optimal performance/power consumption. – You can download the latest cgminer 3.7.2 with Gridseed ASICs support on Windows OS here… Check the Readme file for more information on the list of supported frequencies and how to set individual frequencies per device for overclocking your Gridseed ASIC miners. You can download the windows binary below and the source folder contains the files modified from the original source should you want to compile it yourself. Other than that the updated version is compiled and packaged with the latest OpenSSL libraries with a fix for the the Heartbleed bug. Now if you set the chips value from 5 to 40 in the BAT file for running the cgminer you should be seeing the correct local hashrate for the G-Blade, it should work just fine though we haven’t been able to test it as we do not yet have a G-Blade in our hands. Previous releases did not properly reported the local hashrate of the new Gridseed G-Blade miners that consist of two 40-chip PCBs, though they were working just fine with the hardware and poolside everything was Ok. I'm getting slightly more too.We have updated our windows build of the cgminer 3.7.2 with support for Gridseed 5-chip GC3355 ASICs to properly support the new 80-chip Gridseed G-Blade miners, this release is based on the ( girnyau source) with the fix for more than 8 chips (up to 256) from dbartle’s version. I had a bit more with intensity set to 14, but Desktop response was slower than when GUIMiner was set to 14, I think. If I understand correctly, I'm getting about 255khash/s now - thanks! I've gone ahead and changed it to your recommend settings. Seems to work flawlessly so far and gives a much more wide range of intensity.Īdmittedly I don't understand it though, so if intensity is the standard and it works, that's better. Xintensity: Very new and still experimental and as far as I know only available from the kalroth release (see below). Shaders setting is alsoīeing ignored if it is set to zero - first device setting tested only. Memclock exit/disabled values, through both ncurses interface and API. Saving configuration now supports xintensity, rawintensity, cl-filename, gpu engine and This is from the Kalroth changes document I did a bit of searching, since I was curious.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |