OFFICIAL CGMINER mining software thread for linux/win/osx/mips/arm/r-pi 4.11.1

[benxvn]

Hey, since yesterday i can't connect to any pool on my RPi using cgminer and two Antminer U3's.

I use this command: sudo ./cgminer --bmsc-options 115200:0.57 -o stratum+tcp://stratum.bitcoin.cz:3333 -u xxx.xxx -p xxx --bmsc-voltage 0800 --bmsc-freq 1286

It always puts out this:

[2015-08-10 11:29:27] Started cgminer 4.9.0
 [2015-08-10 11:29:27] ---------------------start voltage----------------------
 [2015-08-10 11:29:28] Send voltage aab800c0
 [2015-08-10 11:29:28] Send voltage ok
 [2015-08-10 11:29:28] -----------------start freq-------------------
 [2015-08-10 11:29:28] Send frequency 82128614
 [2015-08-10 11:29:29] Send freq getstatus 84000400
 [2015-08-10 11:29:31] Recv 1 freq getstatus=802501020a
 [2015-08-10 11:29:31] Recv 2 freq getstatus=802501020a
 [2015-08-10 11:29:31] Recv 3 freq getstatus=802501020a
 [2015-08-10 11:29:31] Recv 4 freq getstatus=802501020a
 [2015-08-10 11:29:31] --------recv freq getstatus ok finish---------
 [2015-08-10 11:29:32] -----------------start nonce------------------
 [2015-08-10 11:29:32] Bmsc send golden nonce1
 [2015-08-10 11:29:32] Bmsc recv golden nonce1 0345182b9f -- 0345182b
 [2015-08-10 11:29:32] Bmsc send golden nonce2
 [2015-08-10 11:29:32] Bmsc recv golden nonce2 466b30a59f -- 466b30a5
 [2015-08-10 11:29:32] Bmsc send golden nonce3
 [2015-08-10 11:29:32] Bmsc recv golden nonce 857e65ee9f -- 857e65ee
 [2015-08-10 11:29:32] Bmsc send golden nonce4
 [2015-08-10 11:29:32] Bmsc recv golden nonce c6f702849f -- c6f70284
 [2015-08-10 11:29:32] AMU0 Init: mode=default read_time=57ms limit=0ms Hs=2.976100e-09
 [2015-08-10 11:29:32] Probing for an alive pool
 [2015-08-10 11:29:42] Waiting for work to be available from pools.

Sorry i'm kinda nooby and i haven't got really good knowledge.

[-ck]

Hey, since yesterday i can't connect to any pool on my RPi using cgminer and two Antminer U3's.

I use this command: sudo ./cgminer --bmsc-options 115200:0.57 -o stratum+tcp://stratum.bitcoin.cz:3333 -u xxx.xxx -p xxx --bmsc-voltage 0800 --bmsc-freq 1286

It always puts out this:

Sorry i'm kinda nooby and i haven't got really good knowledge.

That's a bitmain forked version based on the use of options that don't exist in the official cgminer. You're on the official cgminer forum thread. Use the official cgminer linked in the top post before asking any questions, or seek help elsewhere for bitmain's version, thanks.

[kano]

does official version has support for Antminer U3 like they have ?

No, it's way better support in cgminer.
It's nothing like the bitmain one that has all sorts of bugs in it.

Our version also does not require any U3 options to work.

[jvamos]

Hey all,

Just wondering if someone could tell me what the --enable-ants1 configuration options are for and if they should be ignored when running CGMiner alongside the pool. Also what is the relationship between the cgminer instance running along side the pool (running the miners) and the cgminer installed on the miners? I want to understand the work relationship. I assume the work is parsed from the pool via the first instance and then work is passed to the cluster of ASICS managed by CGMiner on each respective miner.
Am I way off here?

J

[kano]

Hey all,

Just wondering if someone could tell me what the --enable-ants1 configuration options are for and if they should be ignored when running CGMiner alongside the pool. Also what is the relationship between the cgminer instance running along side the pool (running the miners) and the cgminer installed on the miners? I want to understand the work relationship. I assume the work is parsed from the pool via the first instance and then work is passed to the cluster of ASICS managed by CGMiner on each respective miner.
Am I way off here?

J

Like all other "--enable-*" configure options, it means that you compile in the given driver into the binary you create.
--enable-ants1 is for the Bitmain Antminer S1 (as per the README says)
https://github.com/ckolivas/cgminer/blob/master/README#L116

The S1 runs cgminer just like any other device, you don't run 'another' cgminer anywhere else for it.
But you need to cross compile it for the OpenWRT CPU and then put that cgminer into the S1
... or use my binary https://github.com/kanoi/cgminer-binaries/tree/master/AntS1

You wouldn't compile in AntS1 support for anything but an AntS1 and conversely, you would only compile in AntS1 support, not anything else, if you were cross compiling an AntS1 driver.

Edit: when you run configure it tells you this if you include AntS1 with another driver.

[Mikestang]

Hey, since yesterday i can't connect to any pool on my RPi using cgminer and two Antminer U3's.

Follow ck's advice, but also know that U3s are notoriously unreliable and they could easily have both just died.  In fact that is much more likely than there being any problems with cgminer.  But try 4.9.2 official release and associated --au3 commands.

[Anonymailer]

Due to a request on twitter I've compiled 4.9.2 for Mac
http://macminer.fabulouspanda.com/commandline/cgminer/

And recompiled MacMiner to include it with no other changes (not even docs changing re the move from fabulouspanda.co.uk to fabulouspanda.com - both work but I'm using .com now)
http://macminer.fabulouspanda.com/macminer/downloads/

[-ck]

Due to a request on twitter I've compiled 4.9.2 for Mac
http://macminer.fabulouspanda.com/commandline/cgminer/

Appreciated since 4.9.2 has been the stable release for a while and will be for some time to come, I expect.

[toptek]

You'll probably have to swap the PWM and tachometer terminals on the fan if it is not showing speeds on the second fan.

I tiried to find a guide on how to not sure how to do that .I am willing to runn in a few fans to try it but not sure just how i went looking finding no real way . it just annoying to see the temps and not know that fans exact speed more a cosmetic thing then any thing.I know it doesn't matter .

[wariner]

Hi guys,

I have 2 questions but i not find the response:

1 - Which are the best settings for Antminer S5 of expirytime-scantime-queue for solo-pool (ex. tbdice.org)?
2 - If difficulty is set to 1024 cgminer (v4.8.0) not show share (Accepted 00000080 Diff 0/1024 ) and best share it remains 0 ...this is not a problem for normal pool but for solo pool it's ok? (if i change diff work fine= Accepted 3e047efc Diff 1.06K/341 )

Thank you

ps: i use S5 with latest firmware (cgminer 4.8.0.)

[Mikestang]

Hi guys,

I have 2 questions but i not find the response:

1 - Which are the best settings for Antminer S5 of expirytime-scantime-queue for solo-pool (ex. tbdice.org)?
2 - If difficulty is set to 1024 cgminer (v4.8.0) not show share (Accepted 00000080 Diff 0/1024 ) and best share it remains 0 ...this is not a problem for normal pool but for solo pool it's ok? (if i change diff work fine= Accepted 3e047efc Diff 1.06K/341 )

Thank you

ps: i use S5 with latest firmware (cgminer 4.8.0.)

Post to the S5 thread or to a thread that supports that cgminer fork.  It's been posted several times (and is in capital letters in the thread topic) that this thread is for the OFFICIAL release of cgminer.

[pekatete]

Post to the S5 thread or to a thread that supports that cgminer fork.  It's been posted several times (and is in capital letters in the thread topic) that this thread is for the OFFICIAL release of cgminer.

Stop creating noise by pretending to be the responsible user of this forum, when in actual fact you are just signature-ad spamming. If you are un-happy about a post, just report it to the moderator rather than spam us with your nonsensical posts (you've also just done that in the S3 thread!).

[Mikestang]

This user is currently ignored.

[os2sam]

Post to the S5 thread or to a thread that supports that cgminer fork.  It's been posted several times (and is in capital letters in the thread topic) that this thread is for the OFFICIAL release of cgminer.

Stop creating noise by pretending to be the responsible user of this forum, when in actual fact you are just signature-ad spamming. If you are un-happy about a post, just report it to the moderator rather than spam us with your nonsensical posts (you've also just done that in the S3 thread!).

He's just stating the obvious, which in turn will help the person who posted the original message, who obviously doesn't know where to turn for help.

I don't see why you should have a problem with that.

[wariner]

Hi guys,

I have 2 questions but i not find the response:

1 - Which are the best settings for Antminer S5 of expirytime-scantime-queue for solo-pool (ex. tbdice.org)?
2 - If difficulty is set to 1024 cgminer (v4.8.0) not show share (Accepted 00000080 Diff 0/1024 ) and best share it remains 0 ...this is not a problem for normal pool but for solo pool it's ok? (if i change diff work fine= Accepted 3e047efc Diff 1.06K/341 )

Thank you

ps: i use S5 with latest firmware (cgminer 4.8.0.)

Post to the S5 thread or to a thread that supports that cgminer fork.  It's been posted several times (and is in capital letters in the thread topic) that this thread is for the OFFICIAL release of cgminer.

ok thank you...but on S5 thread i had not received any response..I have no idea where to find answers 

[kano]

...
ok thank you...but on S5 thread i had not received any response..

The well known problems in Bitmain's version are not in our master version.
So you need to ask them to do something about it.

queue is gone from master cgminer, and expiry/scantime should be left alone for solo BTC stratum.
The '1024' or 'power of 2' bug isn't in master cgminer.

[kano]

Anyone who updated and built from git since after 4.9.2 - this git commit that isn't in a release yet:
https://github.com/ckolivas/cgminer/commit/661088e6db6ba99b8de2a7b65bbc743bbfd994d4
Should re-get current git and rebuild.

I've reverted that commit until they supply a fixed version.
It causes a dump of 1 diff shares to be sent to the pool when you first connect - ignoring the pool difficulty sent on connect.

[NiceHashSupport]

Anyone who updated and built from git since after 4.9.2 - this git commit that isn't in a release yet:
https://github.com/ckolivas/cgminer/commit/661088e6db6ba99b8de2a7b65bbc743bbfd994d4
Should re-get current git and rebuild.

I've reverted that commit until they supply a fixed version.
It causes a dump of 1 diff shares to be sent to the pool when you first connect - ignoring the pool difficulty sent on connect.

Does the pool where you tested this set diff before first job or does it send job first and then hoping that miner will blindly know the diff that is wanted for this job?

[kano]

Anyone who updated and built from git since after 4.9.2 - this git commit that isn't in a release yet:
https://github.com/ckolivas/cgminer/commit/661088e6db6ba99b8de2a7b65bbc743bbfd994d4
Should re-get current git and rebuild.

I've reverted that commit until they supply a fixed version.
It causes a dump of 1 diff shares to be sent to the pool when you first connect - ignoring the pool difficulty sent on connect.

Does the pool where you tested this set diff before first job or does it send job first and then hoping that miner will blindly know the diff that is wanted for this job?

The change (as stated in the pull request) is to effectively do exactly what the problem is.
The issue is, of course, that it shouldn't do that on the first diff sent from the pool.

cgminer has to have a default diff until the pool sends a diff - this is one of the side effects of the problem in stratum of separation of diff from work - that we both pointed out to slush and eleuthria, and they ignored. Oh well.

[NiceHashSupport]

Anyone who updated and built from git since after 4.9.2 - this git commit that isn't in a release yet:
https://github.com/ckolivas/cgminer/commit/661088e6db6ba99b8de2a7b65bbc743bbfd994d4
Should re-get current git and rebuild.

I've reverted that commit until they supply a fixed version.
It causes a dump of 1 diff shares to be sent to the pool when you first connect - ignoring the pool difficulty sent on connect.

Does the pool where you tested this set diff before first job or does it send job first and then hoping that miner will blindly know the diff that is wanted for this job?

The change (as stated in the pull request) is to effectively do exactly what the problem is.
The issue is, of course, that it shouldn't do that on the first diff sent from the pool.

cgminer has to have a default diff until the pool sends a diff - this is one of the side effects of the problem in stratum of separation of diff from work - that we both pointed out to slush and eleuthria, and they ignored. Oh well.

If pools do not follow specifications, then make them follow. Usually after some time, they adopt.