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

[xyzzy099]

Trying to run cgminer to mine Litecoin with Kattare pool on an NVIDIA GTX 550 Ti and getting the following error with these BAT file settings:

For Litecoin try cudaMiner:
https://bitcointalk.org/index.php?topic=167229.0
It's way faster on Nvidia cards.

Oh, no - please don't mention a different miner in this thread!  Kano will post a 10 paragraph reply accusing you of being a shill who is just advertising for that crapminer you mentioned. 

A miner that adds features that CGMiner does not have is not a bad thing. A miner that copies CGMiner and then claims that CGMiner is inferior in every imaginable way is something that Kano does not seem to take lightly. See the difference?

I don't care about the difference.  When a user posts a bug report and happens to mention that the problem does not occur with some other mining software, that user does not deserve to be attacked, and the report ignored just because Kano has personal issues with another developer.

[1713912681]

1713912681

[1713912681]

1713912681

[1713912681]

1713912681

[-ck]

Fortunately we have nothing against the author of cudaminer, and it fills a need which I have no intention of filling - direct cuda support for nvidia miners - though the miners themselves have to figure out they can't make a profit with nvidia cards.

[kentt]

Hi
I'm hoping to get some advice on debugging an issue I'm having.  I'm not sure it's directly related to cgminer, but after running for a few days Xorg eats up 100% of my CPU.  I can't kill/relaunch it (even with -9).  This happens every few days.  Any advice?

[kano]

Trying to run cgminer to mine Litecoin with Kattare pool on an NVIDIA GTX 550 Ti and getting the following error with these BAT file settings:

For Litecoin try cudaMiner:
https://bitcointalk.org/index.php?topic=167229.0
It's way faster on Nvidia cards.

Oh, no - please don't mention a different miner in this thread!  Kano will post a 10 paragraph reply accusing you of being a shill who is just advertising for that crapminer you mentioned.  

A miner that adds features that CGMiner does not have is not a bad thing. A miner that copies CGMiner and then claims that CGMiner is inferior in every imaginable way is something that Kano does not seem to take lightly. See the difference?

I don't care about the difference.  When a user posts a bug report and happens to mention that the problem does not occur with some other mining software, that user does not deserve to be attacked, and the report ignored just because Kano has personal issues with another developer.

No.

As I stated in the reply before, the logic you presented was complete fail.

Something didn't work for you with program A whatever you did wrong.

So you ran program Bleargh on another operating system with a different configuration.

Even a inept fool should be able to see the logic fail there.

[xyzzy099]

Trying to run cgminer to mine Litecoin with Kattare pool on an NVIDIA GTX 550 Ti and getting the following error with these BAT file settings:

For Litecoin try cudaMiner:
https://bitcointalk.org/index.php?topic=167229.0
It's way faster on Nvidia cards.

Oh, no - please don't mention a different miner in this thread!  Kano will post a 10 paragraph reply accusing you of being a shill who is just advertising for that crapminer you mentioned.  

A miner that adds features that CGMiner does not have is not a bad thing. A miner that copies CGMiner and then claims that CGMiner is inferior in every imaginable way is something that Kano does not seem to take lightly. See the difference?

I don't care about the difference.  When a user posts a bug report and happens to mention that the problem does not occur with some other mining software, that user does not deserve to be attacked, and the report ignored just because Kano has personal issues with another developer.

No.

As I stated in the reply before, the logic you presented was complete fail.

Something didn't work for you with program A whatever you did wrong.

So you ran program Bleargh on another operating system with a different configuration.

Even a inept fool should be able to see the logic fail there.

It's not clear to me what "logic" you are referring to.

I simply reported a problem I had with CGMiner using the official release binaries on Windows 7 x64.  I then pointed out that I did not have this problem when NOT using the official release binaries of CGMiner on Windows 7 x64.

There was no logical implication, just a report that something that was known to work in a different configuration did NOT work when using the official release binary distribution of CGMiner on Windows7 x64.  End of report.

The right thing for you to do would be to simply apologize and admit that you flew off the handle because I inadvertently mentioned a topic that apparently is a hot-button for you.  I did not intend to bait you, and you will notice that I have refrained, out of courtesy to you, from further mention of that specific topic.

[Xian01]

Trying to run cgminer to mine Litecoin with Kattare pool on an NVIDIA GTX 550 Ti and getting the following error with these BAT file settings:

For Litecoin try cudaMiner:
https://bitcointalk.org/index.php?topic=167229.0
It's way faster on Nvidia cards.

Oh, no - please don't mention a different miner in this thread!  Kano will post a 10 paragraph reply accusing you of being a shill who is just advertising for that crapminer you mentioned.  

A miner that adds features that CGMiner does not have is not a bad thing. A miner that copies CGMiner and then claims that CGMiner is inferior in every imaginable way is something that Kano does not seem to take lightly. See the difference?

I don't care about the difference.  When a user posts a bug report and happens to mention that the problem does not occur with some other mining software, that user does not deserve to be attacked, and the report ignored just because Kano has personal issues with another developer.

No.

As I stated in the reply before, the logic you presented was complete fail.

Something didn't work for you with program A whatever you did wrong.

So you ran program Bleargh on another operating system with a different configuration.

Even a inept fool should be able to see the logic fail there.

Kano, you need to chill out dude. You're a tremendous douche-bag at times. No need for that unless you are applying for a job at Butterfly Labs.

[-ck]

I'm unable to compile 3.4.0 on Mac OS X:

Code:

util.c: In function ‘cgtimer_time’:
util.c:891: warning: implicit declaration of function ‘clock_gettime’
util.c:891: error: ‘CLOCK_MONOTONIC’ undeclared (first use in this function)
util.c:891: error: (Each undeclared identifier is reported only once
util.c:891: error: for each function it appears in.)
util.c: In function ‘nanosleep_abstime’:
util.c:899: warning: implicit declaration of function ‘clock_nanosleep’
util.c:899: error: ‘CLOCK_MONOTONIC’ undeclared (first use in this function)
util.c:899: error: ‘TIMER_ABSTIME’ undeclared (first use in this function)

Seems like clock_gettime(CLOCK_MONOTONIC, ...) is not available on OS X.

Yay for more unimplemented POSIX features on an operating system that claims to be POSIX. More like POSOSX.

Will create a generic workaround for the next version.

If you can build from git and you're on OSX, try building now as I've added a generic workaround for this.

[Karin]

If you can build from git and you're on OSX, try building now as I've added a generic workaround for this.

Cool!  Thanks for doing this.  I get this when compiling now:

Code:

util.c: In function ‘cgtimer_time’:
util.c:1017: error: ‘ts’ undeclared (first use in this function)

[-ck]

If you can build from git and you're on OSX, try building now as I've added a generic workaround for this.

Cool!  Thanks for doing this.  I get this when compiling now:

Code:

util.c: In function ‘cgtimer_time’:
util.c:1017: error: ‘ts’ undeclared (first use in this function)

Thanks. git pull and try again please (I'm coding blind!)

[monstrs]

For the brave (and very few) BFL SC single owners out there that wish to flash your devices to try and get the last bit of hashrate out of them, I have uploaded 3 different compiled firmwares here:

http://ck.kolivas.org/apps/cgminer/BitForce_SC/BitForce_SC_1.2.6ck.zip

They all try to enable extra engines than the default firmware does, but in addition I have made 3 different speed ones available, they're tagged 7,8 and 9.

I suggest you start with the 7 first, and if your HW error% rate is less than 2%, try the next one up. I have two singles and one worked best with the 7 version while the other with the 9, so each device will be different.

Remember to put the pins right when connecting your AVR dragon to flash it, and note the different device that Amtel Studio tells you the single is (compared to the Jalapeno) and change your settings accordingly.

If you don't know what the hell I'm talking about, then just ignore this message, since it assumes lots of prior knowledge about flashing the Jalapeno.

any chance that it could work on Little single?

[Askit2]

Trying to run cgminer to mine Litecoin with Kattare pool on an NVIDIA GTX 550 Ti and getting the following error with these BAT file settings:

For Litecoin try cudaMiner:
https://bitcointalk.org/index.php?topic=167229.0
It's way faster on Nvidia cards.

Oh, no - please don't mention a different miner in this thread!  Kano will post a 10 paragraph reply accusing you of being a shill who is just advertising for that crapminer you mentioned.  

A miner that adds features that CGMiner does not have is not a bad thing. A miner that copies CGMiner and then claims that CGMiner is inferior in every imaginable way is something that Kano does not seem to take lightly. See the difference?

I don't care about the difference.  When a user posts a bug report and happens to mention that the problem does not occur with some other mining software, that user does not deserve to be attacked, and the report ignored just because Kano has personal issues with another developer.

No.

As I stated in the reply before, the logic you presented was complete fail.

Something didn't work for you with program A whatever you did wrong.

So you ran program Bleargh on another operating system with a different configuration.

Even a inept fool should be able to see the logic fail there.

Kano, you need to chill out dude. You're a tremendous douche-bag at times. No need for that unless you are applying for a job at Butterfly Labs.

Maybe I missed where the OP of the complaint stated that he tried compiling on windows, or compiled CGminer on Linux. Re-reading it a few times I noted the OP had only stated trying the binary release on windows. Not compiling, not an older version, not switching to Linux.

What the OP did was shortly after posting a problem that could be A) windows related, B) cgminer software related or C) hardware related the OP posted that switching the OS to Linux, the software to another software that the problem disappeared. As far as I know the OP of the complaint switched hardware too as I am not seeing where the OP had gone to the trouble of reformatting to run Linux. So sure by changing everything but the block erupters I can assure you the problem was not directly the block erupters. But as far as a bug in cgminer I think maybe a little more stringent diagnostic procedure is required to have a guess at that.

To be honest I can assure you using less shortcuts on the same testing strategy months before I had issues with CGminer on windows. All timeout related. Even increasing the timeout (Kano did it to try to fix the problem) there was nothing fixing that version. I could have stratum on eclipse or far lower errors on cgminer rolling back to an older version. I did build on windows from kano's git. I did try other things. I finally ordered a Raspberry pi compiled the newest cgminer (at the time) and suddenly the errors went away. Same version I wanted to run on windows just on Linux. Now unfortunately the problem could be A) the computer I used to use, or B) the operating system. Since I could run the previous version without issues without the hardware errors the problem wasn't directly with my hardware. There was a compatibility issue with the timer in windows not being accurate enough. Since I could keep the CGminer version the same on both I could prove that cgminer itself wasn't the issue. If the timeouts had been caused by cgminers lower latency on that version it would apply to the much slower raspberry pi with even lower latency on linux.

Now given that level or more of testing I would say maybe the OP had a bug. Given the information posted either the OP didn't test anything or forgot to mention any tests the ran to try to track down the error. Maybe there is a bug. But is the bug with windows, cgminer or the OP's hardware? I can't answer that. No one can off of the information provided.

I am sure they are looking for the bug right now. Given a little more information maybe they will know where to look for the bug. To me it seems better to ask what would help them find the bug that was so bothersome. Maybe hold other variables still while changing only one at a time so as to narrow down the possibilities.

I have reported bugs here. I have been met with no real hostility by anyone. I just ask how to fix whatever error I was having. I let them know what versions the error hadn't shown up on until. By doing that at least the places to look for the bug is limited to the changes between the last known good version and  the current version

[kano]

...
Kano, you need to chill out dude. You're a tremendous douche-bag at times. No need for that unless you are applying for a job at Butterfly Labs.

Fuck off

[xyzzy099]

Trying to run cgminer to mine Litecoin with Kattare pool on an NVIDIA GTX 550 Ti and getting the following error with these BAT file settings:

For Litecoin try cudaMiner:
https://bitcointalk.org/index.php?topic=167229.0
It's way faster on Nvidia cards.

Oh, no - please don't mention a different miner in this thread!  Kano will post a 10 paragraph reply accusing you of being a shill who is just advertising for that crapminer you mentioned.  

A miner that adds features that CGMiner does not have is not a bad thing. A miner that copies CGMiner and then claims that CGMiner is inferior in every imaginable way is something that Kano does not seem to take lightly. See the difference?

I don't care about the difference.  When a user posts a bug report and happens to mention that the problem does not occur with some other mining software, that user does not deserve to be attacked, and the report ignored just because Kano has personal issues with another developer.

No.

As I stated in the reply before, the logic you presented was complete fail.

Something didn't work for you with program A whatever you did wrong.

So you ran program Bleargh on another operating system with a different configuration.

Even a inept fool should be able to see the logic fail there.

Kano, you need to chill out dude. You're a tremendous douche-bag at times. No need for that unless you are applying for a job at Butterfly Labs.

Maybe I missed where the OP of the complaint stated that he tried compiling on windows, or compiled CGminer on Linux. Re-reading it a few times I noted the OP had only stated trying the binary release on windows. Not compiling, not an older version, not switching to Linux.

What the OP did was shortly after posting a problem that could be A) windows related, B) cgminer software related or C) hardware related the OP posted that switching the OS to Linux, the software to another software that the problem disappeared. As far as I know the OP of the complaint switched hardware too as I am not seeing where the OP had gone to the trouble of reformatting to run Linux. So sure by changing everything but the block erupters I can assure you the problem was not directly the block erupters. But as far as a bug in cgminer I think maybe a little more stringent diagnostic procedure is required to have a guess at that.

To be honest I can assure you using less shortcuts on the same testing strategy months before I had issues with CGminer on windows. All timeout related. Even increasing the timeout (Kano did it to try to fix the problem) there was nothing fixing that version. I could have stratum on eclipse or far lower errors on cgminer rolling back to an older version. I did build on windows from kano's git. I did try other things. I finally ordered a Raspberry pi compiled the newest cgminer (at the time) and suddenly the errors went away. Same version I wanted to run on windows just on Linux. Now unfortunately the problem could be A) the computer I used to use, or B) the operating system. Since I could run the previous version without issues without the hardware errors the problem wasn't directly with my hardware. There was a compatibility issue with the timer in windows not being accurate enough. Since I could keep the CGminer version the same on both I could prove that cgminer itself wasn't the issue. If the timeouts had been caused by cgminers lower latency on that version it would apply to the much slower raspberry pi with even lower latency on linux.

Now given that level or more of testing I would say maybe the OP had a bug. Given the information posted either the OP didn't test anything or forgot to mention any tests the ran to try to track down the error. Maybe there is a bug. But is the bug with windows, cgminer or the OP's hardware? I can't answer that. No one can off of the information provided.

I am sure they are looking for the bug right now. Given a little more information maybe they will know where to look for the bug. To me it seems better to ask what would help them find the bug that was so bothersome. Maybe hold other variables still while changing only one at a time so as to narrow down the possibilities.

I have reported bugs here. I have been met with no real hostility by anyone. I just ask how to fix whatever error I was having. I let them know what versions the error hadn't shown up on until. By doing that at least the places to look for the bug is limited to the changes between the last known good version and  the current version

All this might be applicable, if my goal was to troubleshoot CGMiner.  It was not.  My goal was to get my mining hardware mining reliably.  I tried one configuration, which happened to be a very generic install of the release distribution of CGMiner, and I had problems with that configuration.  I then tried a different configuration that worked 100%.  I'm done, my problem is solved.

I posted the problem that I had experienced here to alert the developers that there might be an issue, because I thought that was the right thing to do.  I would think that the information that a generic install of CGMiner appeared to have problems with Block Erupters might be worth knowing to the developers, and the fact that the same Block Erupters worked perfectly in another configuration was just included to demonstrate that there was no hardware problem involved.

Now, you can fairly say that that is not a very detailed bug report, and therefore of limited value to the developer.  I did not invest any time at all in trying to fix CGMiner, because my goal was just to get my hardware reliably making money ASAP, and I accomplished that.

That being said, I could understand if my post was answered with "Well, that's not really enough information for me to determine the problem you were having, and I cannot reproduce this failure, so I can't act on this report."

Instead, I was attacked as a SHILL, who was somehow ADVERTISING for a 'competitor'!  Does that not seems just a little over the top to you?

Maybe it wasn't the best bug report ever written, but I did not deserve the response I got.

[kano]

So by your own admission, the first part of your post was pretty much useless

...
Now, you can fairly say that that is not a very detailed bug report, and therefore of limited value to the developer.  I did not invest any time at all in trying to fix CGMiner, because my goal was just to get my hardware reliably making money ASAP, and I accomplished that.
...

But in case it wasn't obvious, it was not of limited value, it was of no value at all.
It works for others who do it correctly and read the READMEs, so your complete lack of any information at all says indeed the first half of your post was completely useless.

And the 2nd part of your post is saying to use another miner.

OK, it's worse than fail logic, it's a completely pointless post that only tells people to use another miner.

... and to top it off you're filling this thread up with big useless crap posts also ...

As I said at the start of this: Go away.

I will also point out something that you probably completely missed also ... that your USBs you have bought will never mine the amount of BTC you paid for them.

[-ck]

* ckolivas groans

[mdude77]

I will also point out something that you probably completely missed also ... that your USBs you have bought will never mine the amount of BTC you paid for them.

Are you in the future telling business now?  You know for certain the value of BTC will never go above the current $120/USD? 

M

[kano]

I will also point out something that you probably completely missed also ... that your USBs you have bought will never mine the amount of BTC you paid for them.

Are you in the future telling business now?  You know for certain the value of BTC will never go above the current $120/USD? 

M

... will never mine the amount of BTC you paid for them.

[Xian01]

* ckolivas groans

Hey man, he's your partner... (Passive-aggressive smiley face)

[xyzzy099]

So by your own admission, the first part of your post was pretty much useless

...
Now, you can fairly say that that is not a very detailed bug report, and therefore of limited value to the developer.  I did not invest any time at all in trying to fix CGMiner, because my goal was just to get my hardware reliably making money ASAP, and I accomplished that.
...

But in case it wasn't obvious, it was not of limited value, it was of no value at all.
It works for others who do it correctly and read the READMEs, so your complete lack of any information at all says indeed the first half of your post was completely useless.

And the 2nd part of your post is saying to use another miner.

OK, it's worse than fail logic, it's a completely pointless post that only tells people to use another miner.

... and to top it off you're filling this thread up with big useless crap posts also ...

As I said at the start of this: Go away.

I will also point out something that you probably completely missed also ... that your USBs you have bought will never mine the amount of BTC you paid for them.

It was of NO value because instead of asking for more detail, you just attacked me irrationally, claiming I was advertising for your 'competition'.

I never instructed anyone to use any other miner.  I just stated what happened in my case.  I used configuration A, and it failed.  Then I used configuration B, and it worked 100 %.  End of story.

[Xian01]

So by your own admission, the first part of your post was pretty much useless

...
Now, you can fairly say that that is not a very detailed bug report, and therefore of limited value to the developer.  I did not invest any time at all in trying to fix CGMiner, because my goal was just to get my hardware reliably making money ASAP, and I accomplished that.
...

But in case it wasn't obvious, it was not of limited value, it was of no value at all.
It works for others who do it correctly and read the READMEs, so your complete lack of any information at all says indeed the first half of your post was completely useless.

And the 2nd part of your post is saying to use another miner.

OK, it's worse than fail logic, it's a completely pointless post that only tells people to use another miner.

... and to top it off you're filling this thread up with big useless crap posts also ...

As I said at the start of this: Go away.
I will also point out something that you probably completely missed also ... that your USBs you have bought will never mine the amount of BTC you paid for them.

It was of NO value because instead of asking for more detail, you just attacked me irrationally, claiming I was advertising for your 'competition'.
I never instructed anyone to use any other miner.  I just stated what happened in my case.  I used configuration A, and it failed.  Then I used configuration B, and it worked 100 %.  End of story.

 As much as I loathe Luke-Jr, I'm tempted to try Bllllaaaarrrggghhhhminer on Windows to see if resolves a consistent crash issues after a couple days I'm having with CGMiner driving AMUs.

 Thanks Kano. Much like with Butterfly Labs, your terrible attitude has driven me to your competition.