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

[Jay_Pal]

S7? What's that?

Isn't that the one you should get after the S6 and before the S8? 

[mm5aes]

S7? What's that?

Isn't that the one you should get after the S6 and before the S8?  

No it's a new entity, a Nativity Calendar Miner, a new heat sink falls off every day apparently .....

[Jay_Pal]

S7? What's that?

Isn't that the one you should get after the S6 and before the S8?  

No it's a new entity, a Nativity Calendar Miner, a new heat sink falls off every day apparently .....

Uh!!! I'd love to buy such calendar!!!
But they are still too expensive for me...

[fullintegrity]

where do i find how to create the file to run the miners? a cgminer .bat file runs inside the extracted cgminer program files? on c drive? i dont get how to initiate the miner? using x3 thunder and ispace.co.uk pool, but dont know the exact .bat file. Anyone have sample, i could plug my pool credentials in or even better, a simple set of instructions?
thanks a mil

[kano]

where do i find how to create the file to run the miners? a cgminer .bat file runs inside the extracted cgminer program files? on c drive? i dont get how to initiate the miner? using x3 thunder and ispace.co.uk pool, but dont know the exact .bat file. Anyone have sample, i could plug my pool credentials in or even better, a simple set of instructions?
thanks a mil

https://github.com/ckolivas/cgminer/blob/master/README#L55

[helipotte]

Anyone had any problems with poor performance of Monarchs using firmware 1.4.5?  Mine all hash at about 25% of their expected rate.  This problem

does not happen with the units I have using firmware 1.4.2 or 1.4.3.  I have tried CGminer 4.9.2 in Windows 7 X64 and with Minera on a beaglebone.

Same issue on both platforms.

[kano]

My monarch died long ago ... that someone else (not BFL) supplied me with.

BFL never contacted us about firmware changes or anything like that (or even about the Monarch until LONG after they should have) so your on your own with support of newer firmware in them since I've no idea at all what might have changed and no way to test it.

[helipotte]

My monarch died long ago ... that someone else (not BFL) supplied me with.

BFL never contacted us about firmware changes or anything like that (or even about the Monarch until LONG after they should have) so your on your own with support of newer firmware in them since I've no idea at all what might have changed and no way to test it.

I am just guessing here but it seem like CGminer is treating this unit (Monarch W/1.4.5 FW) as a "single".  My units all hash at about 60-70Gh.  Maybe incorrect

identification in some way.

[kano]

My monarch died long ago ... that someone else (not BFL) supplied me with.

BFL never contacted us about firmware changes or anything like that (or even about the Monarch until LONG after they should have) so your on your own with support of newer firmware in them since I've no idea at all what might have changed and no way to test it.

I am just guessing here but it seem like CGminer is treating this unit (Monarch W/1.4.5 FW) as a "single".  My units all hash at about 60-70Gh.  Maybe incorrect

identification in some way.

Well if you can try an older version of cgminer and if an older version works and a newer one doesn't then that would relate to identification issues.
However, that won't be the cause of slowing it down, that would more be a case of it not working.

Looking at
https://github.com/ckolivas/cgminer/blob/master/NEWS

I'd guess maybe try a real old one about the time it was working for me ...
I was running an old one back on 19-Jan (last day my moth worked for me)  but I was using 4.6.0 (or try 4.6.1)
If either of them work OK, then the problem is something that someone changed in cgminer since then.

[helipotte]

Older versions Identify it as a "BAS' aka single.  I think back around March, or page 798 of this thread:

https://bitcointalk.org/index.php?topic=28402.msg10844936#msg10844936

-ck updated the driver to properly tell the difference  between a monarch and the older 65nm stuff.  CGminer works great with my older monarchs but these

units all have later firmware (the latest i think) and they behave poorly when using cgminer.  They mine at full speed with that "other" mining software but

it has very high CPU usage with many monarchs connected to one host.

[-ck]

Older versions Identify it as a "BAS' aka single.  I think back around March, or page 798 of this thread:

https://bitcointalk.org/index.php?topic=28402.msg10844936#msg10844936

-ck updated the driver to properly tell the difference  between a monarch and the older 65nm stuff.  CGminer works great with my older monarchs but these

units all have later firmware (the latest i think) and they behave poorly when using cgminer.  They mine at full speed with that "other" mining software but

it has very high CPU usage with many monarchs connected to one host.

This was reported before (I believe by Os2sam) where they updated the firmware and never told us anything, breaking cgminer. We've lost all contact with BFL (which was very tenuous at the best of times anyway) and neither Kano nor I have any working BFL hardware any more to update the software, so there really isn't much choice I'm afraid.

[Bink]

Hearing that some buyers of used S3s on fLeaBay are getting much less hash on their pools, than their rigs show. Seems another go-round of asshats going out of their way to trash legit miner SW devs to line their own pockets.

Let's face it, someone running 6 S3s would have MUCH more than 1.2 TH/s on a pool with a legit cgm on their rigs...

[kano]

Hearing that some buyers of used S3s on fLeaBay are getting much less hash on their pools, than their rigs show. Seems another go-round of asshats going out of their way to trash legit miner SW devs to line their own pockets.

Let's face it, someone running 6 S3s would have MUCH more than 1.2 TH/s on a pool with a legit cgm on their rigs...

Yeah there's one, very much appreciated by me, person on my pool running an S3 24/7 mining to my account.

The best thing to do with the S3 is wipe it back to factory settings (with a firmware from bitmain) then add my update:
https://github.com/kanoi/cgminer-binaries/tree/master/AntS3

His averages 0.44TH/s
Here's an accepted share rate graph of his worker over the last 12 days:

Pretty boring graph - but also pretty consistent.

[os2sam]

Older versions Identify it as a "BAS' aka single.  I think back around March, or page 798 of this thread:

https://bitcointalk.org/index.php?topic=28402.msg10844936#msg10844936

-ck updated the driver to properly tell the difference  between a monarch and the older 65nm stuff.  CGminer works great with my older monarchs but these

units all have later firmware (the latest i think) and they behave poorly when using cgminer.  They mine at full speed with that "other" mining software but

it has very high CPU usage with many monarchs connected to one host.

This was reported before (I believe by Os2sam) where they updated the firmware and never told us anything, breaking cgminer. We've lost all contact with BFL (which was very tenuous at the best of times anyway) and neither Kano nor I have any working BFL hardware any more to update the software, so there really isn't much choice I'm afraid.

Yep,  I forgot about it over my summer as I shutdown the Monarchs because it was just too warm to run them.

But if hardware is what you need I would be happy to send you my unit for development purposes.  I would need it back when the software was working with it though.

[Mikestang]

Let's face it, someone running 6 S3s would have MUCH more than 1.2 TH/s on a pool with a legit cgm on their rigs...

They should check that all the chips are firing, no X's in the status screen.

My S3+ averages about 490GH/s, I just turned it back on as a lottery machine a few days ago.

Code:

"hashrate1m": "592G", "hashrate5m": "497G", "hashrate1hr": "486G", "hashrate1d": "484G"

6 S3s should be just under 3TH/s if they are configured correctly and not broken parts.

[helipotte]

Older versions Identify it as a "BAS' aka single.  I think back around March, or page 798 of this thread:

https://bitcointalk.org/index.php?topic=28402.msg10844936#msg10844936

-ck updated the driver to properly tell the difference  between a monarch and the older 65nm stuff.  CGminer works great with my older monarchs but these

units all have later firmware (the latest i think) and they behave poorly when using cgminer.  They mine at full speed with that "other" mining software but

it has very high CPU usage with many monarchs connected to one host.

This was reported before (I believe by Os2sam) where they updated the firmware and never told us anything, breaking cgminer. We've lost all contact with BFL (which was very tenuous at the best of times anyway) and neither Kano nor I have any working BFL hardware any more to update the software, so there really isn't much choice I'm afraid.

Yep,  I forgot about it over my summer as I shutdown the Monarchs because it was just too warm to run them.

But if hardware is what you need I would be happy to send you my unit for development purposes.  I would need it back when the software was working with it though.

I do have a unit I could part with in the name of development.  Shipping would be pricey though.

[-ck]

Thanks for the offer guys, but being in Australia means it would cost more to ship than the hardware itself is worth. Perhaps if you could find a document somewhere with firmware change details I could guess what modifications might be needed in the driver from it and work on one remotely.

[bitsolutions]

Thanks for the offer guys, but being in Australia means it would cost more to ship than the hardware itself is worth. Perhaps if you could find a document somewhere with firmware change details I could guess what modifications might be needed in the driver from it and work on one remotely.

According to BFL "Monarchs shipped April 2015 and after can use the official BFGMiner 5.1.0 or later." and it would appear there were changes there that broke all older versions since BFL says to use a custom version built on Jun 23rd 2014 for "Monarchs shipped before April 2015".

I would guess that the change can be found somewhere here on a date after Jun 23rd 2014.

[-ck]

I would guess that the change can be found somewhere here on a date after Jun 23rd 2014.

Sorry that URL makes my eyes bleed so I can't use it.

[p3yot33at3r]

I would guess that the change can be found somewhere here on a date after Jun 23rd 2014.

Sorry that URL makes my eyes bleed so I can't use it.