Quote from: shackleford on January 04, 2015, 12:39:01 AM

Quote from: shackleford on December 23, 2014, 09:27:28 PM

Quote from: shackleford on December 21, 2014, 08:37:57 PM

Quote from: dogie on November 02, 2014, 05:42:31 AM

Quote from: s2miner on November 02, 2014, 01:38:49 AM

Thanks notlist3d and dogie,

I will wait for new firmware that Bitmain will have to post due to some broken miners that may have gotten shipped.
Also, because I have no energy and time left budgeted for this miner over this weekend.

My only frustration is is that despite known problems in shipped miners, Bitmain has not reacted promptly to provide easy solutions to problems like firmware.

My C1 is operational for now though I have to run it at lower speed and manage it with stupid alternatives e.g. saving miner configuration still does not make all pools operational, (it is random but limited to first pool dead in most cases).
I have to run cgminer from command shell using ssh to make it work.

Thanks for your advise Tupsu, will keep that in mind and that precious link.

regards

The problem you described appears to be a bad SD card which isn't going to be fixed with new firmware.

I just read this entire thread. I have a solo setup and previously had an S1 on it with no issues and I cannot get the C1 to work. It works with other pools no problem but no matter what I have tried it always comes up "dead" on the C1 . The S1 for the URL I just had x.x.x.x:port and then it would add the http:// on front and work fine (mostly/bit flaky still).. the C1 adds the "stratum+tcp://" and even when I set it to http://*.*.*.*:port it still shows up as dead. Is there something different that needs to be done in the C1s?

This quoted post is the only thing I found semi similar but even in different pool slots other than #1 it still is always dead. Everything else is taken care of ie node is fine and other miners including S1 connect fine and ip is in the rpcallow in the conf. Any ideas.. it is 11/26 firmware

My own server has worked exactly 1 time in the last few days of messing with it.. then I changed another unrelated setting and reapplied and poof... hasn't worked again since. S1's work absolutely no problem. I even switch IPs between S1/C1 no matter what the C1 just shows up dead pool for no reason I can see. Pretty sure whatever the problem is it is the C1... This is absolutely pissing me off.

It appears as it is C1 does not work with the standard BTC node solo mining. I tried CG 4.61 by itself and it asks for --btc-address and would not connect to a server until supplied. I think this is the reason it is not functional. I must have been seeing things when I thought it worked once.

This is the last response from bitmain after multiple low comprehension emails.
"Sorry to hear that.
there may be some incompatibles with solo mining for C1."

They keep telling me to use their pool and even told me I could user their "solo" setup which sounds like a complete joke...

"suggest you consider to mine with antpool directly. We're using solo mining and will distribute the payment once blocks are found.
stratum.antpool.com:3333, or solo.antpool.com:3333, solo.antpool.com:25 "

Is there a way to supply arguments to firmware containing CG to actually fix my issue? I really expect to be able to connect to the standard client as a server.. seems pretty fundamental for btc mining equipment to be able to do.

I understand everyone is very eager to say how stupid solo is.. I don't care, I am mostly using it to be involved / gambling and for heat...

I never tried solo mining but about finding blocks: had a zTex, then USB Block Erupters, then a Blade, then my Jalapeno finally arrived, then I bought a Mercury. When I got the Mercury hashing it found a Block very quickly. That has been my only block in couple of years of mining. That includes the S3's, the S3+'s and now my C1. Seems to me finding a block is mysterious and rare.