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

[kano]

I had to restart cgminer 2.6.1 on two different rigs because the API did no longer respond to any request (it did not even time out!?)
Mining was still working and this has never happened with earlier versions.

Anyone experienced the same problem?

The API reports all incoming requests and out going replies when debug is turned on -D
(of course turning on debug produces a whole heap of other stuff)
What OS? (and version)

Edit: of course you can turn on debug from the cgminer screen at any time ... i.e. when the problem occurs

[1715256154]

1715256154

[1715256154]

1715256154

[1715256154]

1715256154

[1715256154]

1715256154

[1715256154]

1715256154

[ShadesOfMarble]

I'll turn debug on the next time this problem happens, thanks for the hint.

I'm using Windows 7 32-bit SP1. (Don't moan because of windows, my rigs are usually running for months witout interruption...)

[-ck]

Does 2.60 not leak shares to backup pools anymore?
Sam

It does, but likely less than before.

[farfie]

What are you running on?

There seems to be an ongoing bug fix on bug fix on bug fix for this at the moment (nothing to do with me)

The first bugfix pshep did was mostly to remove the 2 lines of luke-jr's commit
(which has gone in the chain of bug fixes and not returned)

I might be able to make a version that just removes that commit and compile it for you until the mess is sorted out by the others.
If it's windows - then yep that's OK also I can make one of them.

Let me know.

It is indeed Windows 7 x64.

[-ck]

What are you running on?

There seems to be an ongoing bug fix on bug fix on bug fix for this at the moment (nothing to do with me)

The first bugfix pshep did was mostly to remove the 2 lines of luke-jr's commit
(which has gone in the chain of bug fixes and not returned)

I might be able to make a version that just removes that commit and compile it for you until the mess is sorted out by the others.
If it's windows - then yep that's OK also I can make one of them.

Let me know.

It is indeed Windows 7 x64.

Here try this executable with that one change backed out:
http://ck.kolivas.org/apps/cgminer/temp/cgminer.exe

[farfie]

What are you running on?

There seems to be an ongoing bug fix on bug fix on bug fix for this at the moment (nothing to do with me)

The first bugfix pshep did was mostly to remove the 2 lines of luke-jr's commit
(which has gone in the chain of bug fixes and not returned)

I might be able to make a version that just removes that commit and compile it for you until the mess is sorted out by the others.
If it's windows - then yep that's OK also I can make one of them.

Let me know.

It is indeed Windows 7 x64.

Here try this executable with that one change backed out:
http://ck.kolivas.org/apps/cgminer/temp/cgminer.exe

Half an hour so far with no problems on either machine. Going to bed soon, so I'll just lettem do their thing and report in the morning.

[BlackPrapor]

I've got mini rigs hanging after some time with cgminer 2.6.1 so I switched back to bfgminer 2.5.1. It does produce almost 1% more rejects (cgminer had almost none 0.07%), but at least it works  . Since my computer is running on Linux and I'm a noob in linux, please don't ask me to send you debug files or anything like that  . I didn't have "bitforce:" line for every device btw, if that helps.

[-ck]

I've got mini rigs hanging after some time with cgminer 2.6.1 so I switched back to bfgminer 2.5.1. It does produce almost 1% more rejects, but at least it works  . Since my computer is running on Linux and I'm a noob in linux, please don't ask me to send you debug files or anything like that  . I didn't have "bitforce:" line for every device btw, if that helps.

Um, why bfgminer 2.5.1 and not cgminer 2.5.0?

EDIT: never mind that question, I suspect people actually believe luke-jr's FUD.

I think the minirig is probably burnt by the same thing affecting the singles.

[BlackPrapor]

I've got mini rigs hanging after some time with cgminer 2.6.1 so I switched back to bfgminer 2.5.1. It does produce almost 1% more rejects, but at least it works  . Since my computer is running on Linux and I'm a noob in linux, please don't ask me to send you debug files or anything like that  . I didn't have "bitforce:" line for every device btw, if that helps.

Um, why bfgminer 2.5.1 and not cgminer 2.5.0?

EDIT: never mind that question, I suspect people actually believe luke-jr's FUD.

I think the minirig is probably burnt by the same thing affecting the singles.

Well, I had 2.5.1 installed, so I run that one. Don't know how to update, and I guess since you guys share the code, I would've got the same issue with bfgminer 2.6.1. Maybe its a good thing I still have 2.5.1  ...but I do need to learn how to use linux

[kano]

Anyone who got 2.6.1a from my git downloads - I've made a 2.6.1b that has the problematic BFL commit removed
(and deleted 2.6.1a)

https://github.com/kanoi/cgminer/downloads

cgminer-2.6.1b — cgminer-2.6.1b = Distro cgminer 2.6.1 executable file compiled on Xubuntu 11.04 with all device + scrypt support included - and the BFL bug removed

Edit: FYI 2.6.1a didn't ever fail on my BFL (25.5 hours) - which is rather odd considering the problems with my BFL
Anyway, I'm running 2.6.1b on all my 3 setups.

[Luke-Jr]

I've got mini rigs hanging after some time with cgminer 2.6.1 so I switched back to bfgminer 2.5.1. It does produce almost 1% more rejects (cgminer had almost none 0.07%), but at least it works  .

No, CGMiner has them - it just hides them from you, along with other shares that would have been accepted...

[BlackPrapor]

I've got mini rigs hanging after some time with cgminer 2.6.1 so I switched back to bfgminer 2.5.1. It does produce almost 1% more rejects (cgminer had almost none 0.07%), but at least it works  .

No, CGMiner has them - it just hides them from you, along with other shares that would have been accepted...

So, you're saying that I should see a difference in U or shares accepted between cgminer and bfgminer? I'll check it. Atm I'm having 51.7Ghs very stable speed with cgminer 2.6.1b. Do you mind telling me how to update bfgminer from 2.5.1, so I can make a fair comparison of both up to date miners?

[-ck]

I've got mini rigs hanging after some time with cgminer 2.6.1 so I switched back to bfgminer 2.5.1. It does produce almost 1% more rejects (cgminer had almost none 0.07%), but at least it works  .

No, CGMiner has them - it just hides them from you, along with other shares that would have been accepted...

So, you're saying that I should see a difference in U or shares accepted between cgminer and bfgminer? I'll check it. Atm I'm having 51.7Ghs very stable speed with cgminer 2.6.1b. Do you mind telling me how to update bfgminer from 2.5.1, so I can make a fair comparison of both up to date miners?

His 2.5.1 should be enough to tell...

[BlackPrapor]

Here are the results I've got for both miners running around 45k shares across 3 longpolls both:

[-ck]

Here are the results I've got for both miners running around 45k shares across 3 longpolls both:

Unfortunately this is ONLY over 2 longpolls as can be seen by NB being 3, but that's enough to tell there's a difference. The more longpolls, the greater the difference.

Summary:
Jesusminer
Hashrate 51.8GH (51.4U recognised)
Rejects: 85
U: 718.3

cgminer
Hashrate 51.8GH
Rejects: 30
U:719.5

PLONK
FUD DEBUNKED

The fact is that cgminer discards half a work item on average across longpolls with BFL, and it does NOT count that half a work item artificially. So the reject rate is lower by not working on useless work and then submitting it. But the REAL KICKER is that it also does half a useful work item MORE at the same time which is why the utility was actually higher on cgminer.

Now once again, luke-jr fuck off with your fud and seriously stay the fuck out of my thread with your horseshit.

[farfie]

Half an hour so far with no problems on either machine. Going to bed soon, so I'll just lettem do their thing and report in the morning.

Following up on this, everything seems to be great. Across 11 Singles nothing has hung over night, and all measurements seem to be up to par or better. Excellent work.

[-ck]

Half an hour so far with no problems on either machine. Going to bed soon, so I'll just lettem do their thing and report in the morning.

Following up on this, everything seems to be great. Across 11 Singles nothing has hung over night, and all measurements seem to be up to par or better. Excellent work.

Thanks for the feedback. I'm quite sure other bugs for BFL have crept in since 2.5.0 as well, but at least one major one was quashed.

[farfie]

Thanks for the feedback. I'm quite sure other bugs for BFL have crept in since 2.5.0 as well, but at least one major one was quashed.

I will keep a steady eye on the miners, and they will also be introduced to a couple mini rigs later today as well
The timing is almost kind of creepy, but here's hoping to a smooth experience.

[ddd1]

I'm on windows 7 and cgminer 2.5.0

Should I update to a newer cgminer?

[-ck]

I'm on windows 7 and cgminer 2.5.0

Should I update to a newer cgminer?

Only if you don't have any BFLs at this stage.