Quote from: pekatete on October 21, 2014, 09:43:06 PM

Quote from: moss on October 21, 2014, 09:32:18 PM

Quote from: pekatete on October 21, 2014, 04:43:33 PM

Quote from: daddyfatsax on October 21, 2014, 04:35:10 PM

Quote from: pekatete on October 21, 2014, 04:32:45 PM

Quote from: daddyfatsax on October 21, 2014, 04:26:20 PM

Even with the new cgminer file, my units are doing a little worse than with the previous one. I am guessing I am losing around 10-14 GH/s per device, which is not bad but when you have 11 of them it makes a slight difference.

Do you have the latest firmware on them? i had exactly the same experience with my batch 6 units and reverted to the stock cgminer, however (again as is documented in this thread), when I updated to the latest firmware, which I had to do when upgrading my S1's, I get the same result as the stock, or slightly better, but with the security flaws plugged.

Yeah I have the latest firmware, it is dated 8/26/2014. My issue is probably the 5 batch 1 miners I have, even though some of my batch 5 units are a little slow as well.

Yep, the earlier batches do not seem to be up to it. I suspect it is due to their poor temp handling and suggested to someone to re-do their heat paste; Though he had some good results using a conductive compound, he re-applied using a non conductive paste and has not reported their results. With several units .... that would be a day's work! Worth it? Not sure.

Hi m8, not sure if it's me you're thinking of above, but I did have my best results with Arctic Silver conductive paste and my latest application of Zalman paste was a lot of effort for not much reward. I've just bought some Innovation Cooling IC Diamond 7-Carat thermal compound, so will give that a whirl when I have a chance. Still deliberating about doing the big central heatsinks - presumably this involves removing the blades? Is that a straightforward process? I get funny results with my asics at different frequencies: one 'x' always shows up at 225, but not at higher frequencies and similarly with some of the others, so although I always get an 'x' at higher frequencies somewhere, it's often in different places. Also, my hashrate is rubbish at higher freqs anyway now, it only goes quicker at 231 and that doesn't seem to last long. I tend to keep it at the default 118 now and main task is to stop my hashrate dwindling away, which gradually seems to happen on my problem s3.
BTW, I've upgraded to ck's latest cgminer (4.6.1-141020) and seems ok so far - no restarts, etc. I also removed --queue 4096 and added --lowmem in the cgminer startup script, as recommended by ck.

Yes moss, that was a reference to you, and thanks for updating us. Bummer about having to run at stock freqs ...
Removing board from the heatsink does not involve much more than removing the top heatsink, just another set of screws then you slide it off (you do not have to unscrew the heatsinks from the braces).
I have not tried adding the --lowmem switch yet as I do not readily know the process, but will dig around tonite (or tomorow) and try it.
Thanks again for keeping us up to date.

Hi m8. Another little update... I tried to do the big heatsinks between the boards, but could not remove one of the screws (as you know, they go through the board itself) whatever I tried - the others were very tight too, but I managed those. In the end, I gave up on that part of the plan. However, the rest of the plan seems to have worked well: I redid the outer heatsinks using Diamond 7-Carat thermal compound and I fitted little heatsinks on the DC-DC converter chips. Since doing that, the problem S3 has sat solidly at 440 Ghash/s for weeks. So a big result (so far...). Grin

Edit: Hmmm. My first forced reboot today (19th Nov) of the problem S3 since 'fixing' it. Average hash was heading south, after being rock solid for weeks. Didn't see that coming... Sad

Edit2: Lost my average hash reading (again), so updated to latest firmware to see if that improved things. Ran reliably at 440 Ghash/s until 23rd Nov, when it suddenly stopped hashing and started beeping for 5 minutes. Couldn't find anything wrong via the web interface and it suddenly started working again - back at 440Ghash/s. Other S3 on same router not affected. Don't know what caused that... Huh