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

nitrox

member

Activity: 136

Merit: 10

tester

OS : windows7 SP1 x64
driver : 12.8
SDK : 2.7
cgminer 2.7.5
uptime : 1day 05h 01m 12s

at the moment work good but i see something strange in logs i see from time to time :

Code:

 ..................
 [2012-09-02 09:27:23] Rejected b8a8196a.c6c20544 GPU 0 pool 1 (upstream-says-stale) 
 [2012-09-02 09:27:28] Rejected 3ce8fd66.8d8a571b GPU 1 pool 1 (stale-prevblk) 
 [2012-09-02 09:27:28] Rejected 5f1b4b87.abc42c41 GPU 0 pool 1 (stale-prevblk) 
 [2012-09-02 09:27:28] Pool 1 not providing work fast enough
 [2012-09-02 09:27:28] Rejected 25c96b82.1f96cc5e GPU 1 pool 1 (stale-prevblk) 
 [2012-09-02 09:27:29] Rejected adaa307f.031bcc66 GPU 1 pool 1 (upstream-says-stale) 
 ..................
 [2012-09-02 09:36:57] Rejected 25c85ee9.d834e1f7 GPU 0 pool 1 (unknown-work) 
 [2012-09-02 09:36:57] Rejected 17156a15.7f599a62 GPU 1 pool 1 (unknown-work) 
 [2012-09-02 09:36:59] Rejected 8f6fdcbc.59577ccc GPU 1 pool 1 (stale-prevblk) 
 [2012-09-02 09:37:02] Rejected 779ae1a7.ac1f121b GPU 0 pool 1 (stale-prevblk) 
  ..................
 [2012-09-02 09:37:56] Rejected 35056481.51c5e9b6 GPU 0 pool 1 (upstream-says-stale) 
 ..................
 [2012-09-02 09:58:01] Rejected b399a23b.820eccef GPU 1 pool 1 (stale-prevblk) 
 [2012-09-02 09:58:06] Rejected d9248c7b.fb8a2b16 GPU 0 pool 1 (stale-prevblk) 
 [2012-09-02 09:58:07] Rejected c44fdd72.44464cbe GPU 1 pool 1 (stale-prevblk) 
 [2012-09-02 09:58:10] Rejected 863b5b70.df31fbff GPU 0 pool 1 (stale-prevblk) 
 ..................
 [2012-09-02 10:06:41] Rejected 3302fd70.583a307c GPU 1 pool 1 (duplicate-hash) (resubmit)
 ..................
 [2012-09-02 10:07:33] Rejected bd3ed8e5.49a0ab21 GPU 0 pool 1 (duplicate-hash) (resubmit)
 ..................
 [2012-09-02 10:10:39] Rejected 9b56b4a0.9c6b5d44 GPU 1 pool 1 (duplicate-hash) (resubmit)
 ..................
 [2012-09-02 10:20:56] Rejected 82ed519e.2dec8b38 GPU 0 pool 1 (upstream-says-stale) 
 [2012-09-02 10:20:56] Rejected 7447d43e.367736ac GPU 1 pool 1 (upstream-says-stale) 
 [2012-09-02 10:20:56] Rejected ee299f97.177f1dd6 GPU 0 pool 1 (stale-prevblk) 
 ..................
 [2012-09-02 10:20:59] Rejected 8e8b04d3.79980a0b GPU 0 pool 1 (upstream-says-stale) 
 ..................
 [2012-09-02 18:41:34] Rejected 0522df9d.6163360b GPU 1 pool 1 (upstream-says-stale) 
 ..................
 [2012-09-02 18:41:40] Rejected 52aefd51.93bbd32a GPU 1 pool 1 (upstream-says-stale) 
 ..................
 [2012-09-03 00:00:51] Rejected 54e2598f.c0025de8 GPU 0 pool 1 (stale-prevblk) 
 [2012-09-03 00:00:53] Rejected 0bcefc51.935adc37 GPU 1 pool 1 (stale-prevblk) 
 [2012-09-03 00:00:54] Rejected fcad886b.1b2e7c6d GPU 1 pool 1 (stale-prevblk) 
 [2012-09-03 00:00:54] Rejected 0a53513f.e6e79da7 GPU 0 pool 1 (stale-prevblk) 
 ..................
 [2012-09-03 00:00:55] Rejected fe1019c9.4c38f3da GPU 0 pool 1 (stale-prevblk) 
 ..................
 [2012-09-03 00:08:13] Rejected 597e81af.bef9d478 GPU 0 pool 1 (stale-prevblk) 
 ..................
 [2012-09-03 00:08:15] Rejected 88d55ddf.bd654bab GPU 0 pool 1 (upstream-says-stale) 
 ..................
 [2012-09-03 00:23:33] Rejected d9190502.43190606 GPU 0 pool 1 (stale-prevblk) 
 [2012-09-03 00:23:33] Rejected 3e920d96.eca7b7cd GPU 1 pool 1 (stale-prevblk) 
 [2012-09-03 00:23:35] Rejected 261fc999.1632757f GPU 0 pool 1 (stale-prevblk) 
 ..................
 [2012-09-03 00:57:49] Rejected ebc7b827.6dbbdbb8 GPU 1 pool 1 (stale-prevblk) 
 [2012-09-03 00:57:50] Rejected 04026e1e.f06146f9 GPU 1 pool 1 (stale-prevblk) 
 [2012-09-03 00:57:52] Rejected bacdaff9.71316629 GPU 1 pool 1 (stale-prevblk) 
 ..................
 [2012-09-03 01:47:05] Rejected 0c3e07b8.a4042fa9 GPU 1 pool 1 (stale-prevblk) 
 ..................
 [2012-09-03 01:47:13] Rejected 698ee594.8cccd645 GPU 1 pool 1 (upstream-says-stale) 
 ..................
 [2012-09-03 01:47:26] Rejected 53d70544.1158207a GPU 0 pool 1 (upstream-says-stale) 
 ..................
 [2012-09-03 02:09:55] Rejected 7f182eb3.79ab8459 GPU 0 pool 1 (stale-prevblk) 
 [2012-09-03 02:09:55] Rejected 5bb2df86.62e361be GPU 0 pool 1 (stale-prevblk) 
 ..................
 [2012-09-03 02:15:13] Rejected 718331f0.9c197977 GPU 0 pool 1 (stale-prevblk) 
 [2012-09-03 02:15:14] Rejected e6ba7a91.1711bc9d GPU 1 pool 1 (stale-prevblk) 
 ..................
 [2012-09-03 02:15:19] Rejected 8a7b1c43.56df5655 GPU 0 pool 1 (upstream-says-stale) 
  ..................

and this is i see in api statistic

POOL	Getworks	Accepted	Rejected	Discarded	Stale	Get Failures	Remote Failures	Diff1
0	1,467	16,221	211	7	30	4	7	16,462
1	12,624	11,591	168	555	1	28	4	11,760

Should I be worried or is it look normal to you ?

TheHarbinger

sr. member

Activity: 378

Merit: 250

Why is it so damn hot in here?

Quote from: TheHarbinger on September 01, 2012, 08:04:54 AM

Quote from: TheHarbinger on August 31, 2012, 01:26:16 PM

2.7.5 test update:

Has been running for about 6 hours now and no sign of the -10 intensity bug so far. This is a good sign, it usually showed up within 30 minutes of CGminer starting previously.

Running one card at intensity 8, and one on dynamic, dynamic card is hooked to a monitor.
Test rig is a WIN7 x64 with 2 5870s not in crossfire, it is a daily use desktop, not a dedicated mining rig.
Connecting to a LAN P2Pool server.

I will let it run for a full 24 hours and do a follow up post. So far it looks good Con, here's hoping that bug is squashed for good this time.

And now for something completely different.....
Some good news,

24+ hours running in the background, with the system going under all sorts of other CPU and GPU stresses, and still no sign of the -10 intensity issue. I'm getting a little bit excited.

Sigh....
After running 2.7.5 for about 36 hours with no problems at all, I came home last night/this morning after a fine night of drinking to find my dynamic intensity had gotten drunk also. It had fallen, and couldn't get up. I = -8

monstrs

hero member

Activity: 555

Merit: 504

Is it just me, but last day i had very poor spped with my 7970 rig and 5870 rig with different cgminer versions.

Thought maybe its pool foult, changed that BTCguild is my primary pool, but after a wile ist again the same.
Till now it was E: ~ 92%, now its 74 - 83. Speed was 675 now its 633, card with the same settings.

Anyone else got similar problem? Pool are ABCpool, BTCguild, Deepbit

SiegeBreaker

newbie

Activity: 26

Merit: 0

On 2.7.5 I am having a problem with dynamic intensity dropping after running several hours. I haven't figured out whether it is time related or triggered by something I do. It sounds similar to some other reports, but mine only drops to -7 instead of -9. It first happened to my second (of two crossfired) cards, so I set that to fixed intensity this morning, then when I came back this afternoon my primary card had done the same thing. So, I set my primary card to fixed intensity, then back to dynamic and that fixed it (Obviously, restarting also fixes it). This machine runs Windows 7, but I had it happen on a Ubuntu machine downstairs earlier this week. I have dyn-interval set to 30.

crazyates

legendary

Activity: 952

Merit: 1000

Quote from: sharky112065 on September 01, 2012, 03:46:21 PM

Quote from: crazyates on September 01, 2012, 01:35:36 PM

Quote from: sharky112065 on September 01, 2012, 01:21:02 PM

Quote from: jjshabadoo on September 01, 2012, 10:00:11 AM

Thanks for this work Con and Kano. I just finally went from 2.3.2 windows to 2.7.4 as I was wondering about waiting to work out any bugs in 2.7.5.

I have almost all 5870's and 5970's with one 7970 rig.

Has anyone figured the optimal settings for 5xxx series under Cons new kernel ? Should I change worksize, etc. ? How about SDK, I am still using driver 11.12 and SDK 2.1 for all of my 5xxx series cards and using 12.4 for my 7970's.

Any help would be aprreciated.

I am running 11.9 and SDK 2.5 (Windows 7) for my 5870's. Going from 2.7.0 to 2.7.5, I had to change mem from 170 to 300 and set work size to 256 to get the same hash rate.

At 970/300 -w 256 I get 445.6 MH per 5870. Fan is at 75% and temp is 69 to 74 depending on how hot it is outside.

I use SDK 2.5 because I also have one 6970 in that rig. I did not have to raise memory or change work size for the 6970 in that rig to maintain the same hash rate as before (960/170 - 430.3 MH)

Yes, I know it has the CPU bug, but I use affinity to only use one core. I have tried other driver versions but loose hash rate and have worse stability.

I thought 11.11 got rid of the cpu bug, and still had excellent performance?

Edit: fixed.

I was getting a lot of driver not responding messages and pool x not providing work fast enough with other versions. Do what works for you, but the hours I wasted on testing other SDK's and other drivers was nothing but trouble. If it ain't broke, don't fix it.

Haha sounds fair. I can't stand not having the latest version of any piece of software, so Im always updating everything.

sharky112065

sr. member

Activity: 383

Merit: 250

Quote from: crazyates on September 01, 2012, 01:35:36 PM

Quote from: sharky112065 on September 01, 2012, 01:21:02 PM

Quote from: jjshabadoo on September 01, 2012, 10:00:11 AM

Thanks for this work Con and Kano. I just finally went from 2.3.2 windows to 2.7.4 as I was wondering about waiting to work out any bugs in 2.7.5.

I have almost all 5870's and 5970's with one 7970 rig.

Has anyone figured the optimal settings for 5xxx series under Cons new kernel ? Should I change worksize, etc. ? How about SDK, I am still using driver 11.12 and SDK 2.1 for all of my 5xxx series cards and using 12.4 for my 7970's.

Any help would be aprreciated.

I am running 11.9 and SDK 2.5 (Windows 7) for my 5870's. Going from 2.7.0 to 2.7.5, I had to change mem from 170 to 300 and set work size to 256 to get the same hash rate.

At 970/300 -w 256 I get 445.6 MH per 5870. Fan is at 75% and temp is 69 to 74 depending on how hot it is outside.

I use SDK 2.5 because I also have one 6970 in that rig. I did not have to raise memory or change work size for the 6970 in that rig to maintain the same hash rate as before (960/170 - 430.3 MH)

Yes, I know it has the CPU bug, but I use affinity to only use one core. I have tried other driver versions but loose hash rate and have worse stability.

I thought 11.11 got rid of the cpu bug, and still had excellent performance?

Edit: fixed.

I was getting a lot of driver not responding messages and pool x not providing work fast enough with other versions. Do what works for you, but the hours I wasted on testing other SDK's and other drivers was nothing but trouble. If it ain't broke, don't fix it.

LegitBit

full member

Activity: 140

Merit: 100

Any news on a Mac Binary?

crazyates

legendary

Activity: 952

Merit: 1000

Quote from: sharky112065 on September 01, 2012, 01:21:02 PM

Quote from: jjshabadoo on September 01, 2012, 10:00:11 AM

Thanks for this work Con and Kano. I just finally went from 2.3.2 windows to 2.7.4 as I was wondering about waiting to work out any bugs in 2.7.5.

I have almost all 5870's and 5970's with one 7970 rig.

Has anyone figured the optimal settings for 5xxx series under Cons new kernel ? Should I change worksize, etc. ? How about SDK, I am still using driver 11.12 and SDK 2.1 for all of my 5xxx series cards and using 12.4 for my 7970's.

Any help would be aprreciated.

I am running 11.9 and SDK 2.5 (Windows 7) for my 5870's. Going from 2.7.0 to 2.7.5, I had to change mem from 170 to 300 and set work size to 256 to get the same hash rate.

At 970/300 -w 256 I get 445.6 MH per 5870. Fan is at 75% and temp is 69 to 74 depending on how hot it is outside.

I use SDK 2.5 because I also have one 6970 in that rig. I did not have to raise memory or change work size for the 6970 in that rig to maintain the same hash rate as before (960/170 - 430.3 MH)

Yes, I know it has the CPU bug, but I use affinity to only use one core. I have tried other driver versions but loose hash rate and have worse stability.

I thought 11.11 got rid of the cpu bug, and still had excellent performance?

Edit: fixed.

af_newbie

legendary

Activity: 2702

Merit: 1468

Quote from: optimator on August 30, 2012, 11:36:53 AM

Hey All! Thanks for creating an absolutely incredible mining program. You all rock!

I'm writing a monitoring program for my miner, I've IP address restricted access to the port, but I was wondering if there is any way of providing a password on access?

Cheers!

IP address restriction in cgminer is sufficient. You can have your monitoring program on the same subnet as cgminer and expose HTTP interface in your monitor. Built access control into your monitoring program. NAT your monitor IP to external IP or port forward external port to your monitor port.

sharky112065

sr. member

Activity: 383

Merit: 250

Quote from: jjshabadoo on September 01, 2012, 10:00:11 AM

Thanks for this work Con and Kano. I just finally went from 2.3.2 windows to 2.7.4 as I was wondering about waiting to work out any bugs in 2.7.5.

I have almost all 5870's and 5970's with one 7970 rig.

Has anyone figured the optimal settings for 5xxx series under Cons new kernel ? Should I change worksize, etc. ? How about SDK, I am still using driver 11.12 and SDK 2.1 for all of my 5xxx series cards and using 12.4 for my 7970's.

Any help would be aprreciated.

I am running 11.9 and SDK 2.5 (Windows 7) for my 5870's. Going from 2.7.0 to 2.7.5, I had to change mem from 170 to 300 and set work size to 256 to get the same hash rate.

At 970/300 -w 256 I get 445.6 MH per 5870. Fan is at 75% and temp is 69 to 74 depending on how hot it is outside.

I use SDK 2.5 because I also have one 6970 in that rig. I did not have to raise memory or change work size for the 6970 in that rig to maintain the same hash rate as before (960/170 - 430.3 MH)

Yes, I know it has the CPU bug, but I use affinity to only use one core. I have tried other driver versions but loose hash rate and have worse stability.

jjshabadoo

hero member

Activity: 535

Merit: 500

Thanks for this work Con and Kano. I just finally went from 2.3.2 windows to 2.7.4 as I was wondering about waiting to work out any bugs in 2.7.5.

I have almost all 5870's and 5970's with one 7970 rig.

Has anyone figured the optimal settings for 5xxx series under Cons new kernel ? Should I change worksize, etc. ? How about SDK, I am still using driver 11.12 and SDK 2.1 for all of my 5xxx series cards and using 12.4 for my 7970's.

Any help would be aprreciated.

os2sam

legendary

Activity: 3583

Merit: 1094

Think for yourself

Quote from: kano on September 01, 2012, 07:50:46 AM

Quote from: sharky112065 on September 01, 2012, 07:48:53 AM

Quote from: Askit2 on September 01, 2012, 06:26:24 AM

PS: Did anyone else asking for help on this thread get a PM from lukeJR?

As a religious zealot, it is in his nature to try to convert people.

Come to the dark side ... we have cookies

We are all on the dark side ... cookies optional.

TheHarbinger

sr. member

Activity: 378

Merit: 250

Why is it so damn hot in here?

Quote from: TheHarbinger on August 31, 2012, 01:26:16 PM

2.7.5 test update:

Has been running for about 6 hours now and no sign of the -10 intensity bug so far. This is a good sign, it usually showed up within 30 minutes of CGminer starting previously.

Running one card at intensity 8, and one on dynamic, dynamic card is hooked to a monitor.
Test rig is a WIN7 x64 with 2 5870s not in crossfire, it is a daily use desktop, not a dedicated mining rig.
Connecting to a LAN P2Pool server.

I will let it run for a full 24 hours and do a follow up post. So far it looks good Con, here's hoping that bug is squashed for good this time.

And now for something completely different.....
Some good news,

24+ hours running in the background, with the system going under all sorts of other CPU and GPU stresses, and still no sign of the -10 intensity issue. I'm getting a little bit excited.

kano

legendary

Activity: 4634

Merit: 1851

Linux since 1997 RedHat 4

Quote from: sharky112065 on September 01, 2012, 07:48:53 AM

Quote from: Askit2 on September 01, 2012, 06:26:24 AM

PS: Did anyone else asking for help on this thread get a PM from lukeJR?

As a religious zealot, it is in his nature to try to convert people.

Come to the dark side ... we have cookies

sharky112065

sr. member

Activity: 383

Merit: 250

Quote from: Askit2 on September 01, 2012, 06:26:24 AM

PS: Did anyone else asking for help on this thread get a PM from lukeJR?

As a religious zealot, it is in his nature to try to convert people.

Askit2

hero member

Activity: 981

Merit: 500

DIV - Your "Virtual Life" Secured and Decentralize

When It acts up it does this

Proof of work result false booo
block info
BFL waited (time proper varies a little) Line seems to appear when no nonce is found so not if it says rejected.
Pushing work to staged thread
sucessfully rolled work
Repeat

How many repeats depends. If the work was from the previous block would it come in about 5 second submissions? I think no but only because I assume it would try to submit more then one every 5 seconds to the pool to get credit for stales. What I see will repeat until it stops rolling work (at 120 seconds and 5 seconds per work unit that should leave me with 24 possible work units to get rejected before it runs out of work). The pool is disabled at 13 work units or so being rejected. If the units are truely stales that I am submitting would it count expected stales into the pools rejected work in a row? My thought is not as likely. Maybe it is but somewhere in the 70 or so seconds between LP notice and pool change because of excessive rejects I should submit some work from the current pools LP that my single has been working on. If what I am thinking is accurate I am asking for help from the wrong place and really should ask at EclipseMC thread about it. If I am wrong in my thinking I am sure someone will point out what I am missing.

PS: Did anyone else asking for help on this thread get a PM from lukeJR?

BkkCoins

hero member

Activity: 784

Merit: 1009

firstbits:1MinerQ

Quote from: kano on September 01, 2012, 01:57:43 AM

Your log shows 3 GPU's but you are only setting some of the settings for 2 of them ...
"intensity" : "8,8",

Yes. As mentioned above I have a problem with GPU#2 not accepting any start up settings (even very conservative ones). It's fussy and will crash if I add the third intensity,engine,memory values. I have a small script that uses the API to set that GPU after startup. eg.

Code:

#!/bin/bash

export AMDAPPSDKROOT=/home/miner/AMD-APP-SDK-v2.4-lnx32/
export LD_LIBRARY_PATH=${AMDAPPSDKROOT}lib/x86:${LD_LIBRARY_PATH}
export DISPLAY=:0

fixcg&
cgminer 2>>/var/log/cgminer.log

and fixcg

Code:

#!/bin/bash
sleep 30
echo -n "gpuintensity|2,8" | nc 127.0.0.1 4028 >/dev/null
echo -n "gpumem|2,250" | nc 127.0.0.1 4028 >/dev/null
echo -n "gpuengine|2,900" | nc 127.0.0.1 4028 >/dev/null

That works and 30 seconds after starting GPU#2 gets fixed and runs fine. But apparently a side effect may be my GPU#0 intensity going dynamic - though I haven't rebooted since manually setting it back to 8, so maybe that's gone away.

kano

legendary

Activity: 4634

Merit: 1851

Linux since 1997 RedHat 4

Your log shows 3 GPU's but you are only setting some of the settings for 2 of them ...
"intensity" : "8,8",

BkkCoins

hero member

Activity: 784

Merit: 1009

firstbits:1MinerQ

Quote from: -ck on September 01, 2012, 01:22:09 AM

I bet you're loading *2* configuration files...

I just start it as:

cgminer 2>>/var/log/cgminer.log

letting it load the default in .cgminer/cgminer.conf

Excerpt from last reboot,

Code:

[2012-09-01 10:27:57] Started cgminer 2.6.1
 [2012-09-01 10:27:57] Loaded configuration file /home/miner/.cgminer/cgminer.conf
 [2012-09-01 10:27:58] Probing for an alive pool

-ck

legendary

Activity: 4088

Merit: 1631

Ruu \o/

Quote from: BkkCoins on September 01, 2012, 01:05:00 AM

Quote from: -ck on August 31, 2012, 10:43:50 PM

Quote from: BkkCoins on August 31, 2012, 10:36:36 PM

I have a minor problem here that maybe someone knows how to fix up. I'm still using 2.6.1 on Linux with 3x 5830 cards.
Any ideas?

Set an intensity

That's odd. I have intensity 8 set in the conf file.

Code:

"intensity" : "8,8",
"gpu-engine" : "1000,1000",
"gpu-fan" : "40-85,40-85,40-85",
"gpu-memclock" : "250,250",
"gpu-powertune" : "0,0",
"gpu-vddc" : "1.161,1.161",
"temp-cutoff" : "95,95,95",
"temp-overheat" : "85,85,85",
"temp-target" : "72,72,72",

But you're right of course. Manually setting intensity 8 after starting made the paused thread go live again.

I do have a script that uses the API to alter settings on GPU #2 after startup because it will crash on startup if I put the same settings in the conf file. See conf file has missing arguments for #2. For some reason maybe that API tweaking is causing GPU #0 to think it's intensity is dynamic...? Or not. IDK.

I bet you're loading *2* configuration files...

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