Topic: OFFICIAL CGMINER mining software thread for linux/win/osx/mips/arm/r-pi 4.11.0 - page 32. (Read 5805649 times)

Put a pause after your command line so that you can see what the error. 

such as

cgminer.exe -o *** -u *** -p *** --au3-freq 250 --au3-volt 850
pause


Or open a command line dos box prompt and then type in your complete command so you can see why if failed.

Hi, everybody,

I need help with 4.9.2

I have - 
Windows XP sp3
Antminer U3
cgminer 4.9.2 from official download page.
All drivers are installed

The problem with 4.9.2 is the next - it doesn't start with batch file in any syntax. No matter cgminer or cgminer.exe. That means I have to start my cgminer manually everytime and run it with standart freq 225/volt 775. I did the conf file with changes in --au3 lines from default 225/775 to 250/850. The conf file is in the same folder with cgminer as well as the batch file. No results at all. If I start the batch file the cmd window appears and drops in ½ second. If I start cgminer itself it come and works but with default 225/775! How I can organize start with batch file and change the settings for my u3?

There were no problems with my previous  cgminer 4.6.1 at all except the speed and tons of errors. Now with 4.9.2 and default settings for u3 I have speed up to 54 Gh/s and 1-2% of dups/stoles. The only thing that makes me sad is the configuration and batch which still useless.

Could you give me any suggestion?

The sample of batch I try to use - "cgminer.exe -o *** -u *** -p *** --au3-freq 250 --au3-volt 850"

I thought that the batch file with just "cgminer.exe -n" in line will start cgminer and show the settings for device. But this one doesn't work too...

Thanks!  I was able to get what I needed from your code.

  For some reason, I was messing up the poola:porta part.  I didn't realize that it was poolA:PortA .   ugh.  I guess this is why I'm not a programmer. I was looking for a 'poola' command...

If you just want a 50/50 split, I'd suggest using the --balance option instead, or use --load-balance without setting quotas (they default to an even split across pools).  You do need one of those commands or else it'll just be in failover mode, regardless of you having used --quota

In terms of your command line, have a look at the documentation:
"Will give poola 1/3 of the work and poolb 2/3 of the work."

so in your case you might use any one of:

Yet another alternative would be to use the --rotate option, presuming the pools perform much the same then rotating through the pools every N minutes has roughly the same 'even split' effect.

I'm trying to get a config file to split hashrate between 2 different pools.  I'm running on Win7 with a gekko usb stick.  I would like to run maybe 50% on pool1 and 50% pool2.  I have the following code:



I believe that I just have a simple error or two somewhere.  Not sure where of if I'm even getting the context correct.

Not really. When I say mine died, they all ended up like that - they'd start up ok but last progressively less time before dying. Think of them as evolving into antminer U3s (in a bad way).

Hmm, well that's disheartening to hear.  I had one die on me months and months ago, but I had it OC'd and was just asking to burn it out.  These 6 have been champs since that one burned out, I've run them at stock setting with a fan the entire time.

The screen cap above shows errors only on one stick, maybe I've got one bad apple in the group, I'll mess with them tonight and see.

Does the fact that they come back just fine for a while (hours at this point) when unplugged/replugged not mean anything?  Just another symptom of their inevitable demise?  If so then I just got room for a few more compacs.

Looks like a fatal error on the sticks - they're just not talking back. Not sure how they would have gotten damaged by a power outage but they look like they've had it. Each and every one of my nanofuy USB stick based miners eventually died on me.

Had a power outage yesterday, since then I've been getting weird errors with my nanofury usb sticks.  They'll run fine for a while, then this starts:


The only cure is to quit cgminer, physically unplug and replug each stick (some of them the mining light stays on even after quitting cgminer), then restart cgminer.

Any ideas what is causing this?  Thanks.

Thank you ck!

=>and check the syntax of your rpcipallow as it changed not too long ago.

that is what I found out now on github:

 -rpcallowip=
       Allow JSON-RPC connections from specified source. Valid for are a
       single IP (e.g. 1.2.3.4), a network/netmask (e.g. 1.2.3.4/255.255.255.0)
       or a network/CIDR (e.g. 1.2.3.4/24). This option can be specified
       multiple times


my fault was located in bitcoin.conf:

rpcallowip=192.168.2.0/192.168.2.255 WRONG!

should be:
rpcallowip=192.168.2.0/24

  I am sorry!


Anyway I am happy that it works now!

Sometimes I wounder about where a central source for those kind of Information exist?

Check you are explicitly using http:// as well for the address, and check the syntax of your rpcipallow as it changed not too long ago.

@Kano:
yes I did, same as I used before on Windows bitcoin-qt (v 0.8.0 because of xp).

@ck:
Did you compile with libcurl and are you specifying a btc address in your configuration?

yes I did compile with libcurl and a btc adress was also supplyed.


BUT: it is my first attempt on Debian64 and the v0.11.0 bitcoin core.

=> you need the rpc component

in bitcoin.conf stored under ~/.bitcoin I enter the rpcuser / rpcpassword and rpcipallow=the raspi ip where
cgminer is running on.

or do i need to start something on the Debian64 server?
at the moment I do ./bitcoin-qt -server

Did you compile with libcurl and are you specifying a btc address in your configuration? They're essential for solo mining. Furthermore the bitcoin-qt binary alone isn't enough to solo mine with any more, you need the rpc component.

You need to send an address
https://github.com/ckolivas/cgminer/blob/master/README#L57

Sorry for asking:

I am running Bitcoin Core v0.11.0 on a Debian64 PC and it runs well.
Now i added the bitcoin.conf and start with -server.

On my Win PC I am able to mine solo with cgminer 4.7.1 to my Bitcoin core XXX.
EDIT:
It look's like i am wrong, http request failed connect.


Then I tryed using cgminer 4.9.2 and I got the Message:
No Stratum, GBT or Solo support  in pool 0 http://192.168.2.112:8332 unable to use.

To test that the compile is ok I did a change from my bitcoin core to solockpool
and it works with stratum ok.


I am a bit lost about what i am doing (config on Debian site or cgminer) wrong?

Awesome, thanks.

Make sure it uses USB, not serial.
Serial is crap.

... and if you don't do most of this I will label it trash:
https://bitcointalksearch.org/topic/optimal-firmwarehardware-design-for-mining-with-cgminer-294499

(as I do consider trash things like the U3 that ignore all that)

I doubt it looks acceptable yet, it's pretty much the half of icarus that I wanted plus some initialization.  I intend to clean it up more when I add multi-chip support. 

But I do plan to push it into cgminer so it's available.

--
novak

Yep.

Got it. So once it's mature he'd push back this way then possibly you merge it if it looks acceptable?