OFFICIAL CGMINER mining software thread for linux/win/osx/mips/arm/r-pi 4.11.0 - page 498.

Subo1977

sr. member

Activity: 344

Merit: 250

Flixxo - Watch, Share, Earn!

Quote from: kano on September 05, 2012, 05:18:38 PM

Quote from: Subo1977 on September 05, 2012, 05:11:48 AM

It there a Plan to implemet queue and Threats in the API?

At the moment the socket queue is 100 but a single thread.
What are you doing with the API that needs more than that?

Ok i miswrote it.
I dont wont Threat and queue for the API. I want to Set These options over the API like Intensity.

If i Mine with a normal Pool the Standard Setting for these Parameters are ok.

If i Switch to p2pool over the API in an Script, i want to change the Queue And threats too.

kano

legendary

Activity: 4634

Merit: 1851

Linux since 1997 RedHat 4

Quote from: Subo1977 on September 05, 2012, 05:11:48 AM

It there a Plan to implemet queue and Threats in the API?

At the moment the socket queue is 100 but a single thread.
What are you doing with the API that needs more than that?

Subo1977

sr. member

Activity: 344

Merit: 250

Flixxo - Watch, Share, Earn!

It there a Plan to implemet queue and Threats in the API?

mdude77

legendary

Activity: 1540

Merit: 1001

Quote from: kano on September 04, 2012, 09:32:17 PM

1) Is that once or over and over again?
Things like a dynamic IP address change, or an OzCoin server DNS switch, or a pool restart can cause that.
2) Try 2.7.5

Endlessly, a page of it before I restarted it.

If it happens again I'll upgrade.. I like stability.

Tx,

M

kano

legendary

Activity: 4634

Merit: 1851

Linux since 1997 RedHat 4

Quote from: mdude77 on September 04, 2012, 08:20:25 PM

Quote from: kano on September 04, 2012, 08:11:49 PM

Quote from: mdude77 on September 04, 2012, 07:46:23 PM

...
M

Completely unrelated to using those two options.
We'd need to know about the cgminer version you are using (certain older versions have known issues) and the pool being used and other such information.
Also, that is well known to happen with pools like ABC and GPUMax caused by the pool.

Using 2.7.4 on ozcoin.

M

2 things:
1) Is that once or over and over again?
Things like a dynamic IP address change, or an OzCoin server DNS switch, or a pool restart can cause that.
2) Try 2.7.5

mdude77

legendary

Activity: 1540

Merit: 1001

Quote from: kano on September 04, 2012, 08:11:49 PM

Quote from: mdude77 on September 04, 2012, 07:46:23 PM

...
M

Completely unrelated to using those two options.
We'd need to know about the cgminer version you are using (certain older versions have known issues) and the pool being used and other such information.
Also, that is well known to happen with pools like ABC and GPUMax caused by the pool.

Using 2.7.4 on ozcoin.

M

kano

legendary

Activity: 4634

Merit: 1851

Linux since 1997 RedHat 4

Quote from: mdude77 on September 04, 2012, 07:46:23 PM

...
M

Completely unrelated to using those two options.
We'd need to know about the cgminer version you are using (certain older versions have known issues) and the pool being used and other such information.
Also, that is well known to happen with pools like ABC and GPUMax caused by the pool.

crazyates

legendary

Activity: 952

Merit: 1000

Quote from: mdude77 on September 04, 2012, 07:46:23 PM

Quote from: mdude77 on September 04, 2012, 06:31:55 PM

No, I saw it, and I already changed my command line to include it. Someone else, might have been you, to add the cutoff, which was already in the config.

What was tripping me up was the lines in the config that I didn't put there, and someone telling me to add the temp cutoff line.

Thanks for the assistance.

M

EDIT: It occurred to me after I wrote this that the auto-gpu and auto-fan lines might have been in the config file to begin with, and I might have removed them. That of course would lead to this situation. I don't recall doing so, but that doesn't mean it didn't happen.

Alright, I just got this error that I've never seen before. I've seen others report this, I never have until I added those two lines:

Code:

[2012-09-04 20:43:11] Rejected 36800659.0478c728 GPU 0 pool 0 (Stale or unknown
work)
[2012-09-04 20:43:17] Rejected 710d0f98.46c1d6fc GPU 0 pool 0 (Stale or unknown
work)
[2012-09-04 20:43:19] Rejected 1617f4a0.ca588d24 GPU 0 pool 0 (Stale or unknown
work)
[2012-09-04 20:43:20] Rejected d857c0d0.b392795b GPU 0 pool 0 (Stale or unknown
work)
[2012-09-04 20:43:20] Rejected 0af37905.5c08917f GPU 0 pool 0 (Stale or unknown
work)
[2012-09-04 20:43:23] Rejected 9b8e310c.5e5363de GPU 0 pool 0 (Stale or unknown
work)
[2012-09-04 20:43:23] Rejected 2186400e.50964116 GPU 0 pool 0 (Stale or unknown
work)
[2012-09-04 20:43:33] Rejected 80a6c9cb.0acea6f5 GPU 0 pool 0 (Stale or unknown
work)
[2012-09-04 20:43:41] Rejected 6a9eaba7.fe0df6c3 GPU 0 pool 0 (Stale or unknown
work)
[2012-09-04 20:43:43] Rejected ef982720.75f0d021 GPU 0 pool 0 (Stale or unknown
work)
[2012-09-04 20:43:46] Rejected 22eb21ec.e426caee GPU 0 pool 0 (Stale or unknown
work)
[2012-09-04 20:43:53] Rejected 2aa476d7.db9f2003 GPU 0 pool 0 (Stale or unknown
work)

M

--auto-gpu and --auto-fan don't have anything to do with stales. Perhaps you missed a LP? Happens to me every once in a while.

mdude77

legendary

Activity: 1540

Merit: 1001

Quote from: mdude77 on September 04, 2012, 06:31:55 PM

No, I saw it, and I already changed my command line to include it. Someone else, might have been you, to add the cutoff, which was already in the config.

What was tripping me up was the lines in the config that I didn't put there, and someone telling me to add the temp cutoff line.

Thanks for the assistance.

M

EDIT: It occurred to me after I wrote this that the auto-gpu and auto-fan lines might have been in the config file to begin with, and I might have removed them. That of course would lead to this situation. I don't recall doing so, but that doesn't mean it didn't happen.

Alright, I just got this error that I've never seen before. I've seen others report this, I never have until I added those two lines:

Code:

[2012-09-04 20:43:11] Rejected 36800659.0478c728 GPU 0 pool 0 (Stale or unknown
work)
[2012-09-04 20:43:17] Rejected 710d0f98.46c1d6fc GPU 0 pool 0 (Stale or unknown
work)
[2012-09-04 20:43:19] Rejected 1617f4a0.ca588d24 GPU 0 pool 0 (Stale or unknown
work)
[2012-09-04 20:43:20] Rejected d857c0d0.b392795b GPU 0 pool 0 (Stale or unknown
work)
[2012-09-04 20:43:20] Rejected 0af37905.5c08917f GPU 0 pool 0 (Stale or unknown
work)
[2012-09-04 20:43:23] Rejected 9b8e310c.5e5363de GPU 0 pool 0 (Stale or unknown
work)
[2012-09-04 20:43:23] Rejected 2186400e.50964116 GPU 0 pool 0 (Stale or unknown
work)
[2012-09-04 20:43:33] Rejected 80a6c9cb.0acea6f5 GPU 0 pool 0 (Stale or unknown
work)
[2012-09-04 20:43:41] Rejected 6a9eaba7.fe0df6c3 GPU 0 pool 0 (Stale or unknown
work)
[2012-09-04 20:43:43] Rejected ef982720.75f0d021 GPU 0 pool 0 (Stale or unknown
work)
[2012-09-04 20:43:46] Rejected 22eb21ec.e426caee GPU 0 pool 0 (Stale or unknown
work)
[2012-09-04 20:43:53] Rejected 2aa476d7.db9f2003 GPU 0 pool 0 (Stale or unknown
work)

M

os2sam

legendary

Activity: 3586

Merit: 1099

Think for yourself

Quote from: mdude77 on September 04, 2012, 06:31:55 PM

Quote from: kano on September 04, 2012, 05:52:29 PM

Yeah I mentioned that at the start also
https://bitcointalksearch.org/topic/m.1158935

Though I did add the edit back then saying if there was a bug it would need following up just in case I was wrong.

I guess that comment about --auto-gpu --auto-fan has been missed each time?

No, I saw it, and I already changed my command line to include it. Someone else, might have been you, to add the cutoff, which was already in the config.

What was tripping me up was the lines in the config that I didn't put there, and someone telling me to add the temp cutoff line.

Thanks for the assistance.

M

EDIT: It occurred to me after I wrote this that the auto-gpu and auto-fan lines might have been in the config file to begin with, and I might have removed them. That of course would lead to this situation. I don't recall doing so, but that doesn't mean it didn't happen.

This little exercise in frustration is why I still use all command line options.

Of course I also prefer a config.sys to a registry any day too

Sam

mdude77

legendary

Activity: 1540

Merit: 1001

Quote from: kano on September 04, 2012, 05:52:29 PM

Yeah I mentioned that at the start also
https://bitcointalksearch.org/topic/m.1158935

Though I did add the edit back then saying if there was a bug it would need following up just in case I was wrong.

I guess that comment about --auto-gpu --auto-fan has been missed each time?

No, I saw it, and I already changed my command line to include it. Someone else, might have been you, to add the cutoff, which was already in the config.

What was tripping me up was the lines in the config that I didn't put there, and someone telling me to add the temp cutoff line.

Thanks for the assistance.

M

EDIT: It occurred to me after I wrote this that the auto-gpu and auto-fan lines might have been in the config file to begin with, and I might have removed them. That of course would lead to this situation. I don't recall doing so, but that doesn't mean it didn't happen.

mdude77

legendary

Activity: 1540

Merit: 1001

Quote from: crazyates on September 04, 2012, 05:46:30 PM

We're not being sarcastic. You need the --auto-gpu and --auto-fan options, and you've been told this many times! In the config, it would look like this:

Code:

"auto-gpu" : true,
"auto-fan" : true,

Alright, twice someone has said to use parms, this is the first time someone said to add it to the config file. I'll adjust it now.

What this means is the lines in the config file, written by cgminer, are misleading, as they don't do a thing unless you tweak it. Which is fine..

Quote

My grandfather has a saying: When 3 people tell you you're drunk, you better sit down.

If this isn't sarcasm, and "another case of operator error", what is?

M

kano

legendary

Activity: 4634

Merit: 1851

Linux since 1997 RedHat 4

Yeah I mentioned that at the start also
https://bitcointalksearch.org/topic/m.1158935

Though I did add the edit back then saying if there was a bug it would need following up just in case I was wrong.

I guess that comment about --auto-gpu --auto-fan has been missed each time?

crazyates

legendary

Activity: 952

Merit: 1000

Quote from: mdude77 on September 04, 2012, 05:40:07 PM

Quote

It's overheating because you don't have auto-fan and auto-gpu turned on. You have told cgminer to run your GPU at a set clock speed, with a set fan speed, and that's exactly what it's doing. It will happily continue to do so until you GPU bursts into flame. The temp settings don't mean anything if you aren't allowing cgminer to control the temperature.

Just another case of operator error.

Okay, let's start over again.

My cgminer.cfg clearly states, as I said a few posts back:

Code:

"gpu-engine" : "0-1125",
"gpu-fan" : "0-55",
"gpu-memdiff" : "0",
"gpu-powertune" : "0",
"gpu-vddc" : "0.870",
"temp-cutoff" : "90",
"temp-overheat" : "85",
"temp-target" : "75",

Where is the problem? Is the config file missing something, or do I need to add more parms to the command line? Note that I didn't put any of these lines in here, cgminer wrote them when I told it to create a .cfg. All I did was change some parms. It's a bit misleading for these parms to be here and do nothing. Specifically the temp-cutoff part, I would think that means, well, when it reaches that temperature, it stops dead in the water.

And, I would hope the internal shutdown on the GPU would prevent it from bursting into flame.

BTW, thanks for the sarcastic help. Much appreciated.

M

We're not being sarcastic. You need the --auto-gpu and --auto-fan options, and you've been told this many times! In the config, it would look like this:

Code:

"auto-gpu" : true,
"auto-fan" : true,

My grandfather has a saying: When 3 people tell you you're drunk, you better sit down.

mdude77

legendary

Activity: 1540

Merit: 1001

Quote

It's overheating because you don't have auto-fan and auto-gpu turned on. You have told cgminer to run your GPU at a set clock speed, with a set fan speed, and that's exactly what it's doing. It will happily continue to do so until you GPU bursts into flame. The temp settings don't mean anything if you aren't allowing cgminer to control the temperature.

Just another case of operator error.

Okay, let's start over again.

My cgminer.cfg clearly states, as I said a few posts back:

Code:

"gpu-engine" : "0-1125",
"gpu-fan" : "0-55",
"gpu-memdiff" : "0",
"gpu-powertune" : "0",
"gpu-vddc" : "0.870",
"temp-cutoff" : "90",
"temp-overheat" : "85",
"temp-target" : "75",

Where is the problem? Is the config file missing something, or do I need to add more parms to the command line? Note that I didn't put any of these lines in here, cgminer wrote them when I told it to create a .cfg. All I did was change some parms. It's a bit misleading for these parms to be here and do nothing. Specifically the temp-cutoff part, I would think that means, well, when it reaches that temperature, it stops dead in the water.

And, I would hope the internal shutdown on the GPU would prevent it from bursting into flame.

BTW, thanks for the sarcastic help. Much appreciated.

M

kano

legendary

Activity: 4634

Merit: 1851

Linux since 1997 RedHat 4

Quote from: TheHarbinger on September 04, 2012, 02:58:16 PM

...
It's overheating because you don't have auto-fan and auto-gpu turned on. You have told cgminer to run your GPU at a set clock speed, with a set fan speed, and that's exactly what it's doing. It will happily continue to do so until you GPU bursts into flame. The temp settings don't mean anything if you aren't allowing cgminer to control the temperature.

Just another case of operator error.

Made me laugh

Yes that is correct of course

Roland68

member

Activity: 103

Merit: 10

using the provided example.cfg file would help ...just cut/paste auto settings into your cfg file ...

The00Dustin

hero member

Activity: 807

Merit: 500

Quote from: TheHarbinger on September 04, 2012, 02:58:16 PM

It's overheating because you don't have auto-fan and auto-gpu turned on. You have told cgminer to run your GPU at a set clock speed, with a set fan speed, and that's exactly what it's doing. It will happily continue to do so until you GPU bursts into flame. The temp settings don't mean anything if you aren't allowing cgminer to control the temperature.

Just another case of operator error.

To clarify, you need something like this:
--auto-gpu --temp-cutoff --gpu-engine --gpu-memclock --gpu-fan <%>

Note that all of the values in <>'s are chosen by you and can be set or ranges, so in this case, --gpu-fan could be 60 or 50-60. I don't remember exactly what --temp-cutoff does, so you might want to set it a few degrees cooler than you think you should, but it sounds like you have plenty of room to experiment without damaging your card.

TheHarbinger

sr. member

Activity: 378

Merit: 250

Why is it so damn hot in here?

Quote from: mdude77 on September 04, 2012, 02:48:45 PM

Quote from: crazyates on September 04, 2012, 01:02:15 PM

I don't run any of my GPUs above 60%. All but this one do just fine between 50 and 60%. Most run in a very cooled environment (air conditioning blowing right on them), "free" from any chasis with a box fan blowing on them. They usually run high 60s, low 70s. This one is in my main workstation, which has cooling issues. Usually 60% is fine, sometimes I can do 50-55% w/o a problem. However, twice recently I found it in the low 90s, and cgminer seemed oblivious to it, even though it clearly showed the temp on the screen in cgminer.

M

Well there you go. You just answered your own question. If all your caseless, air conditioned GPUs do fine with 60% fan, but your workstation GPU (which has cooling issues) isn't fine with 60%, then I say again, bump up the fan speed! "--auto-fan --gpu-fan 25-75".

My question wasn't why it's overheating, my question was why didn't cgminer shut down when it exceeded my threshold? Obviously I can speed the fan up, and obviously I don't want to otherwise I would!!

M

It's overheating because you don't have auto-fan and auto-gpu turned on. You have told cgminer to run your GPU at a set clock speed, with a set fan speed, and that's exactly what it's doing. It will happily continue to do so until you GPU bursts into flame. The temp settings don't mean anything if you aren't allowing cgminer to control the temperature.

Just another case of operator error.

Topic: OFFICIAL CGMINER mining software thread for linux/win/osx/mips/arm/r-pi 4.11.0 - page 498. (Read 5806088 times)