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

[kano]

Since I have no idea which versions you are talking about and which AntMiner you have ... I'll take a guess.

The S3 update in https://github.com/kanoi/cgminer-binaries/AntS3/

Once you have updated it, it is wise (as it says there) to check the settings and see that they are what you had before.
The easiest way to do that is to look at the "Miner Status" page at the bottom when cgminer is running.
If you've got the Frequency set a lot higher than standard then you can expect to get more HW errors.

--

Now, whatever AntMiner you do have, please enlighten us with exactly where you got the firmware, how you built the cgminer or where you got the cgminer, what AntMiner you have and the actual numbers shown on the web page before and after, including how long it ran and what the settings were before and after.
Thanks

[luthermarcus]

can somebody please explain to me why when I install cgminer fork from bitmaintech

Code:

https://github.com/bitmaintech/cgminer

i have only 10 HW errors per day

and when i install

Code:

https://github.com/ckolivas/cgminer

i have 10 HW per minute ??

does HW destroy my antminers ?

Please provide a screenshot because my  miners HW% went down minimally but seem to start jumping around now but still at good levels what is the percentage of hw screen shot would give us a good overall of what is going on.

[studysession]

With the USB devices being plug-n-play does that mean for removal as well?

I started down this path for some self learning and now long as I keep finding these little USB Asic miners for cheap on eBay I keep buying them. Even though I keep adding them I also want to remove as I want for testing another RasPi box.

When I remove one does software keep working like normal? I want to add and remove freely.

Thanks -
Keith

[os2sam]

When I remove one does software keep working like normal? I want to add and remove freely.

It does with my Block Erupters.

[studysession]

It does with my Block Erupters.

Thanks

[philipma1957]

Hi ck and kano

I have been testing sidehack's

new usb sticks in this thread.

https://bitcointalk.org/index.php?topic=1086011.0


I used the 4.9.2 build from the first page of this thread.

and the sticks work great up to  freq 250

is it possible you can add support from  freq 250 to  freq 300

that would be :

 256.25
 262.50
 268.75
 275.00
 281.25
 287.50
 293.75
 300.00

 Side hack's sticks use your cgminer software and base it on your U-3 part of the build.

Basically I am really poor on the software end of the game. and cgminer is too hard for me to add these freq's

I use window's 7 to run my gear.

thanks phil

maybe in the 4.9.3 build.

[pekatete]

@Kano, any chance of  updating the S1 cgminer with the power-reboot fix you applied to the S3 cgminer?

[Mikestang]

hello again

2 mins ago my Antminer U3 start to biping.
Lol
First time hear that

Before today I used bitmaintech fork of cgminer
install with this

Code:

su
cd /opt
git clone https://github.com/bitmaintech/cgminer.git
cd cgminer
./autogen.sh
CFLAGS="-O2 -Wall -march=native" ./configure --enable-bmsc
make install

everything works perfect. I used freq 250MHz and 0.8V (I know that I overclocked it)
With that overclocked stats my cgminer shows max 10-15 HW per day, and I have 5 U3's

Today I decided to install ckoliva's fork of cgminer 4.9.2

Since I posted my last post (12h ago) cgminer show around 1300 HW errors

That's 100 times more. Why

Probably because Bitmain's fork was showing HW incorrectly.

Or the U3 finally burned something out running overclocked all the time.

[kano]

@Kano, any chance of  updating the S1 cgminer with the power-reboot fix you applied to the S3 cgminer?

There is already an updated cgminer-monitor script in my AntS1 binaries git, but I guess you also mean the change to try to force the time correct in the script that starts cgminer?

Next time I update the AntS1 version I'll probably do an archive like I did for S3 that does away with the API hack and uses a similar Status screen as the S3 one I did - just that's way down on the todo list at the moment since it's only a visual change - my AntS1 binary already (since I first did it) has the Bitmain problems removed and the cgminer version is almost current, behind by less one version.

Unless I get some Bitmain go-ahead on S5 stuff, for now (since I put out the last S3 update) priority is the pool and pool code (and it's tax time also)

[rkinnin]

I upgraded my s3's as was suggested.

I checked one of them tonight and now it says it found 6 blocks. 

How can I really verify the validity of the 6?

[kano]

I upgraded my s3's as was suggested.

I checked one of them tonight and now it says it found 6 blocks. 

How can I really verify the validity of the 6?

Clearly alt-coin blocks.

No idea - we don't really care about alt-coins ... at all

[NathanB]

win 7, version 4.9.2
rotate doesn't seem to work
tried different amt of time from 0 to 60 minutes
always stayed on which ever pool it was running on at time of change to rotate.
all pools were alive, and could switch pools manual
let run all night with rotate set to 13 minutes and when check this AM.
found it had ran the same pool all night.
checked pools web site, have graph showing hash over time
only one show hashing on graph, all other pools showed no hashing at all
pressed p for pool in cgminer display and still showed rotate at 13 minutes.
didn't switch off pool to next one.
bug?

[rkinnin]

I upgraded my s3's as was suggested.

I checked one of them tonight and now it says it found 6 blocks. 

How can I really verify the validity of the 6?

Clearly alt-coin blocks.

No idea - we don't really care about alt-coins ... at all

agreed. 

Ty

[rkinnin]

...
Would you suggest I use the same instructions to upgrade my s1's and s2's as you posted for the s3?

S1: https://github.com/kanoi/cgminer-binaries/tree/master/AntS1

S2: https://github.com/kanoi/cgminer-binaries/tree/master/AntS2

when attempting to use the s2 link on the actual s2 on the upgrade page I get the following error after I hit "flash image":

tar: invalid magic tar: short read cp: can't stat '*': No such file or directory

Thoughts??

[kano]

Download it again and check the checksum on the file?

[rkinnin]

Download it again and check the checksum on the file?

i misunderstood one of your steps....sorry about that. 

RTFM.   

I am good.  Thanks.

[kenshirothefist]

ckolivas, could you please pull this pull request: https://github.com/ckolivas/cgminer/pull/679? This is a small but annoying bug, causing small loss of performance (in terms of accounted shares on pool) when changing difficulty - especially when using vardiff or often diff changing (when switching from low to high diff miner immediately sends high diff while is should/could still send low diff and pool might wrongly account for shares). Thanks!

[-ck]

ckolivas, could you please pull this pull request: https://github.com/ckolivas/cgminer/pull/679? This is a small but annoying bug, causing small loss of performance (in terms of accounted shares on pool) when changing difficulty - especially when using vardiff or often diff changing (when switching from low to high diff miner immediately sends high diff while is should/could still send low diff and pool might wrongly account for shares). Thanks!

I will look at it eventually; the original behaviour was chosen to be robust with dodgy pools' handling of diff so it was actually there intentionally. Saying you lose a lot of shares is a gross exaggeration as most decent pools change diff only once or twice ever and that many shares will not even amount to a single satoshi over a lifetime of mining.

[NiceHashSupport]

ckolivas, could you please pull this pull request: https://github.com/ckolivas/cgminer/pull/679? This is a small but annoying bug, causing small loss of performance (in terms of accounted shares on pool) when changing difficulty - especially when using vardiff or often diff changing (when switching from low to high diff miner immediately sends high diff while is should/could still send low diff and pool might wrongly account for shares). Thanks!

I will look at it eventually; the original behaviour was chosen to be robust with dodgy pools' handling of diff so it was actually there intentionally. Saying you lose a lot of shares is a gross exaggeration as most decent pools change diff only once or twice ever and that many shares will not even amount to a single satoshi over a lifetime of mining.

A robust implementation would be, if the miner was still sending low diff shares when pool requested higher diff. That way you may get some % of rejects, but would work without speed loss on pools that don't implement diff change correctly and on pools that do.

Of course, it is not a big loss, a percent or two on a pool that does vardiff moderately. But I cannot agree with satoshi claim. You forgot about reconnects (whenever miner goes offline and comes back, switches to another pool etc). There is a lot more lost than a single satoshi. Besides, according to how simple the fix is, it is also totally non-understandable to us, why it is not pulled yet (or taken look at it).

And, say this to miners; there is a patch waiting for cgminer that improves performance but "I will look at it eventually".

[-ck]

ckolivas, could you please pull this pull request: https://github.com/ckolivas/cgminer/pull/679? This is a small but annoying bug, causing small loss of performance (in terms of accounted shares on pool) when changing difficulty - especially when using vardiff or often diff changing (when switching from low to high diff miner immediately sends high diff while is should/could still send low diff and pool might wrongly account for shares). Thanks!

I will look at it eventually; the original behaviour was chosen to be robust with dodgy pools' handling of diff so it was actually there intentionally. Saying you lose a lot of shares is a gross exaggeration as most decent pools change diff only once or twice ever and that many shares will not even amount to a single satoshi over a lifetime of mining.

A robust implementation would be, if the miner was still sending low diff shares when pool requested higher diff. That way you may get some % of rejects, but would work without speed loss on pools that don't implement diff change correctly and on pools that do.

Of course, it is not a big loss, a percent or two on a pool that does vardiff moderately. But I cannot agree with satoshi claim. You forgot about reconnects (whenever miner goes offline and comes back, switches to another pool etc). There is a lot more lost than a single satoshi. Besides, according to how simple the fix is, it is also totally non-understandable to us, why it is not pulled yet (or taken look at it).

And, say this to miners; there is a patch waiting for cgminer that improves performance but "I will look at it eventually".

No, you are speaking ONLY of your pool/proxy/service which does lots of reconnects. You are biased towards your pool whereas I'm biased towards normal pools. Nonetheless the patch has been pulled into master git but it may be a very long time before a new cgminer release comes out since there's virtually nothing happening anywhere with regards to hardware till the next generation comes around.