Quote from: KaChingCoinDev on May 23, 2014, 01:08:21 AM

Quote from: jekv2 on May 23, 2014, 12:36:32 AM

Quote from: KaChingCoinDev on May 23, 2014, 12:33:23 AM

Quote from: RowanX on May 22, 2014, 11:05:07 PM

aChingCoinDev does it work if you bypass the config file and run a minimal .bat file? e.g.

Code:

minerd-gc3355 --freq=850 --gc3355-detect --url=stratum+tcp://us-east.multipool.us:7777 --userpass=brandonb01.1:x

pause

It statts up, gets work, but then does not do anything:

Code:

cpuminer-gc3355 (v1.0d) - Started: [2014-05-22 20:32:07]
================================================================================
(2s) | 0.00/0.00 MH/s | A: 0 R: 0 HW: 0
Connected to us-east.multipool.us:7777 diff 64 with stratum as user brandonb01.
================================================================================
GSD 0: 8D9117765449 | 0 MHz | 0.0/0.0 KH/s | A: 0 R: 0 H: 0
GSD 1: 8D76576C5355 | 0 MHz | 0.0/0.0 KH/s | A: 0 R: 0 H: 0

================================================================================
[2014-05-22 20:32:07] Starting Stratum on stratum+tcp://us-east.multipool.us:7
777
[2014-05-22 20:32:07] 0: GC3355 chip mining thread started, in SINGLE mode
[2014-05-22 20:32:07] 0: Open device \\.\COM3
[2014-05-22 20:32:07] 0: Terminating GC3355 chip mining thread
[2014-05-22 20:32:07] 1: GC3355 chip mining thread started, in SINGLE mode
[2014-05-22 20:32:07] 1: Open device \\.\COM3
[2014-05-22 20:32:07] 1: Terminating GC3355 chip mining thread
[2014-05-22 20:32:08] Stratum detected new block
[2014-05-22 20:32:08] New Job_id: 62e9 Diff: 2048 Work_id: 97084a27
[2014-05-22 20:32:58] New Job_id: 62ea Diff: 64 Work_id: 97084a27

You have to let it sit for about five minutes the HR will climb. Try it. I see 0 for MHz. HMM.

Nope. After 30 minutes, still no change. Some more "New Job_id", but that is it.

I think you're looking in the wrong place for the cause/solution.
It says it's receiving new blocks. It doesn't matter if the chips aren't hashing. 0.00MHz means DEAD! NUTTIN! NADA!

They are not firing up. When they do, it's almost instant before you start seeing accepts, there are chips firing up and hashing away. That's the only way it works.
Something is not starting the chips up. Perhaps a missing command? Perhaps a bad comm line between machine and controller? Are you using a PC or a controller?
I've seen this happen when the FIFO's get gummed up or the USB chips aren't working correctly and require a reset. Try disabling and re-enabling them.
Unplug and plug them back in then try.
Anyway, make sure your command line is all straight first, then if no joy, check your communications hardware.....
Good luck!