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

crazyates

legendary

Activity: 952

Merit: 1000

Quote from: -ck on May 22, 2012, 06:56:50 AM

Quote from: joyyen on May 22, 2012, 06:23:31 AM

I have run my CGminer about 7 days, and i have about 11 Rigs with 5x 5850 and until today morning i found that some of my CGminer Freeze and stop sending share and i found some funny figure when i freeze something like "LW:50" and high figure around beside "LW"

where some of my CGminer still running fine thich is "LW:0"

you can see that on top of the cgminer !

anyone pls help

i cannot provide screen shot because it is not convenient and it is far from my house to warehouse

so anyone pls help if it happen again i will get the screen shot

sry for my English !

The LW value is almost certainly completely unrelated. If it crashes at approximately 7 days, then you are being hit by the ATI Display Library crashing after a week bug that happens only on windows. Try starting cgminer with --no-restart . You will lose temperature and/or fanspeed monitoring after a week but it at least wont crash.

I have my computer set to restart every day at a certain time, and CGMiner starts when windows starts. Ya lose 3 minutes of hashing a day, but no 7 day bug you're talking about. The temp/fanspeed/dynamic OC is what makes CGMiner great!

Aseras

hero member

Activity: 658

Merit: 500

He's saying it's a bug in ati's drivers ( no stretch there ) not in cgminer. ATI would have to fix it.

However, if ATI could make a decent driver it would be a miracle. That's their Achilles heel. Their hardware is amazing, their drivers are piss poor.

kano

legendary

Activity: 4634

Merit: 1851

Linux since 1997 RedHat 4

Quote from: MrTeal on May 22, 2012, 11:28:01 PM

...
If it keeps hashing after losing its ADL information, I won't even worry about it. I manually set the fan to 85% anyway regardless of how low temps are, so I'm not too concerned with the fan control. I can manually restart it whenever I notice.

Still, if there's a thread on the issue I'd love to read it. A quick search on the forums either turned up not much or way too much.

It's been discussed a few times in this thread.

MrTeal

legendary

Activity: 1274

Merit: 1004

Quote from: kano on May 22, 2012, 10:38:10 PM

Quote from: MrTeal on May 22, 2012, 09:38:19 PM

Quote from: -ck on May 22, 2012, 06:56:50 AM

The LW value is almost certainly completely unrelated. If it crashes at approximately 7 days, then you are being hit by the ATI Display Library crashing after a week bug that happens only on windows. Try starting cgminer with --no-restart . You will lose temperature and/or fanspeed monitoring after a week but it at least wont crash.

I searched this thread but didn't really find any mention of this bug. I have a 5970 that crashes somewhere in the vicinity of once a week, without fully crashing the display driver. Clocks and voltages that often change when a card crashes aren't affected in this case. When it does this cgminer declares it sick and attempts to restart it, at which point cgminer crashes. A quick restart of cgminer fixes the issue, and the system goes about mining again without issue. I recently restarted it with --no-restart and I haven't had an issue yet (7 days will be 12 hours from now). Does anyone have any links to information or a possible solution to this if it is an ATI driver bug? I assumed I had a bad core on my GPU, but it would be great if that's not the issue.

Solution

As you said, use --no-restart (so cgminer doesn't crash when ATI screws up - yes it is the ATI librarys fault on windows)

Also with a separate (simple) program using the API, check when any of the GPU's become sick or lose their ADL info then use an API 'restart'

Edit: I'll also add that anyone expecting there to be a cgminer code fix for this is misunderstanding the problem.
It doesn't happen on linux like this - only windows.
If it happened the same way on both linux and windows then it could be a possible cgminer code fix, but since it is windows specific (and not reproducible on linux) it is extremely likely to be in the ATI windows library
Also the fact that the GPU doesn't stop working (if you use --no-restart) but simply loses it's ADL information, again means it is in the ATI library that is the problem.

If it keeps hashing after losing its ADL information, I won't even worry about it. I manually set the fan to 85% anyway regardless of how low temps are, so I'm not too concerned with the fan control. I can manually restart it whenever I notice.

Still, if there's a thread on the issue I'd love to read it. A quick search on the forums either turned up not much or way too much.

kano

legendary

Activity: 4634

Merit: 1851

Linux since 1997 RedHat 4

Quote from: MrTeal on May 22, 2012, 09:38:19 PM

Quote from: -ck on May 22, 2012, 06:56:50 AM

The LW value is almost certainly completely unrelated. If it crashes at approximately 7 days, then you are being hit by the ATI Display Library crashing after a week bug that happens only on windows. Try starting cgminer with --no-restart . You will lose temperature and/or fanspeed monitoring after a week but it at least wont crash.

I searched this thread but didn't really find any mention of this bug. I have a 5970 that crashes somewhere in the vicinity of once a week, without fully crashing the display driver. Clocks and voltages that often change when a card crashes aren't affected in this case. When it does this cgminer declares it sick and attempts to restart it, at which point cgminer crashes. A quick restart of cgminer fixes the issue, and the system goes about mining again without issue. I recently restarted it with --no-restart and I haven't had an issue yet (7 days will be 12 hours from now). Does anyone have any links to information or a possible solution to this if it is an ATI driver bug? I assumed I had a bad core on my GPU, but it would be great if that's not the issue.

Solution

As you said, use --no-restart (so cgminer doesn't crash when ATI screws up - yes it is the ATI librarys fault on windows)

Also with a separate (simple) program using the API, check when any of the GPU's become sick or lose their ADL info then use an API 'restart'

Edit: I'll also add that anyone expecting there to be a cgminer code fix for this is misunderstanding the problem.
It doesn't happen on linux like this - only windows.
If it happened the same way on both linux and windows then it could be a possible cgminer code fix, but since it is windows specific (and not reproducible on linux) it is extremely likely to be in the ATI windows library
Also the fact that the GPU doesn't stop working (if you use --no-restart) but simply loses it's ADL information, again means it is in the ATI library that is the problem.

MrTeal

legendary

Activity: 1274

Merit: 1004

Quote from: -ck on May 22, 2012, 06:56:50 AM

The LW value is almost certainly completely unrelated. If it crashes at approximately 7 days, then you are being hit by the ATI Display Library crashing after a week bug that happens only on windows. Try starting cgminer with --no-restart . You will lose temperature and/or fanspeed monitoring after a week but it at least wont crash.

I searched this thread but didn't really find any mention of this bug. I have a 5970 that crashes somewhere in the vicinity of once a week, without fully crashing the display driver. Clocks and voltages that often change when a card crashes aren't affected in this case. When it does this cgminer declares it sick and attempts to restart it, at which point cgminer crashes. A quick restart of cgminer fixes the issue, and the system goes about mining again without issue. I recently restarted it with --no-restart and I haven't had an issue yet (7 days will be 12 hours from now). Does anyone have any links to information or a possible solution to this if it is an ATI driver bug? I assumed I had a bad core on my GPU, but it would be great if that's not the issue.

-ck

legendary

Activity: 4088

Merit: 1631

Ruu \o/

They will only clock back up if the temperature drops enough again.

bulanula

hero member

Activity: 518

Merit: 500

Upon further investigation it looks like the fans do throttle down but only by a small amount.

I intervened manually once to change some settings so maybe that is the cause ?

The throttling behaviour still occurs so maybe it is a feature to let you know the cards can't take the heat ?

Once they throttle due to breaking past hysteresis and fans are maxed out they don't clock back up still occurs.

bulanula

hero member

Activity: 518

Merit: 500

Also ( I cannot edit ) I seemed to notice a very strange behaviour with cgminer 2.4.1 and Linux and autofan / autogpu enabled.

When heat builds up around my rigs they do start to go to max set fan value ( say 80% ) and if this is then further accompanied by more heat so that the cards bypass the hysteresis limit ( but they are very far from overheat limit ) they throttle down on the clocks.

I observe that when the source of heat is shutdown and the rigs left to cool the following seems NOT to occur which is quite strange : the cards do not maximize the core clock back up and also the fans spin at maximum set instead of backing down now the rigs are cooler.

Anyone experience the same and know how to fix it ? The cards' clocks not going back up after they have throttled once I can understand but the fans keeping to the high RPMs instead of low RPM after the heat has passed is strangest. The fans were going back down on 2.3.6 if I remember correctly after the heat passed but this seems to be "stuck" on the 2.4.1 so that even after the heat has passed the fans stay at the maximum RPMs they reached during the heat period.

Thanks for the work, ckolivas ! I would appreciate any suggestions about what could be causing this behaviour.

bulanula

hero member

Activity: 518

Merit: 500

Quote from: check_status

P.S. AMD makes you jump through hoops now to get the older SDK's.
http://download2-developer.amd.com/amd/APPSDK/AMD-APP-SDK-v2.4-lnx64.tgz
" "/amd/Stream20GA/ati-stream-sdk-v2.1-lnx64.tgz
" "/amd/Stream20GA/icd-registration.tgz

Might be useful if somebody could setup a mirror for those 2 files for older cards.

I understand AMD pulling the files because they don't want to support old products and software so it might happen soon.

Thanks !

-ck

legendary

Activity: 4088

Merit: 1631

Ruu \o/

Quote from: joyyen on May 22, 2012, 06:23:31 AM

I have run my CGminer about 7 days, and i have about 11 Rigs with 5x 5850 and until today morning i found that some of my CGminer Freeze and stop sending share and i found some funny figure when i freeze something like "LW:50" and high figure around beside "LW"

where some of my CGminer still running fine thich is "LW:0"

you can see that on top of the cgminer !

anyone pls help

i cannot provide screen shot because it is not convenient and it is far from my house to warehouse

so anyone pls help if it happen again i will get the screen shot

sry for my English !

The LW value is almost certainly completely unrelated. If it crashes at approximately 7 days, then you are being hit by the ATI Display Library crashing after a week bug that happens only on windows. Try starting cgminer with --no-restart . You will lose temperature and/or fanspeed monitoring after a week but it at least wont crash.

joyyen

member

Activity: 99

Merit: 10

MMM EXTRA - THE RIGHT STEP TOWARDS THE GOAL

I have run my CGminer about 7 days, and i have about 11 Rigs with 5x 5850 and until today morning i found that some of my CGminer Freeze and stop sending share and i found some funny figure when i freeze something like "LW:50" and high figure around beside "LW"

where some of my CGminer still running fine thich is "LW:0"

you can see that on top of the cgminer !

anyone pls help

i cannot provide screen shot because it is not convenient and it is far from my house to warehouse

so anyone pls help if it happen again i will get the screen shot

sry for my English !

kano

legendary

Activity: 4634

Merit: 1851

Linux since 1997 RedHat 4

Quote from: demkd on May 22, 2012, 01:53:09 AM

I run cgminer with -I 2 parameter, but this parameter is ignored and used intensity in config (since v2.3.4).
How can I override intensity for new versions of cgminer without changing config file?

As stated previously, the issue is that you have it in your default cgminer.conf file.

To change it so that it says changed, you either have to save settings to the default file, or edit the default cgminer.conf file.

To save your current settings into the default file, press "S", "W" then Enter.
N.B. if you save your current settings then you will not need to supply any settings when you run cgminer

If, on the other hand, you want to be able to specify a setting on the command line, then you will have to remove it from the default cgminer.conf file

check_status

full member

Activity: 196

Merit: 100

Web Dev, Db Admin, Computer Technician

Quote from: demkd on May 22, 2012, 01:53:09 AM

I run cgminer with -I 2 parameter, but this parameter is ignored and used intensity in config (since v2.3.4).
How can I override intensity for new versions of cgminer without changing config file?

You have to move the config file out of the .cgminer directory, if your using linux, or change it in the config file.
Alternatively, you can try adjusting it while it is running by choosing 'G' then 'C' or 'S' for change settings, then 'I' for Intensity, then enter the number for your desired Intensity and press enter. Hit any key to return to polling screen.

check_status

full member

Activity: 196

Merit: 100

Web Dev, Db Admin, Computer Technician

OK, so I get this error:

Code:

./cgminer: error while loading shared libraries: libOpenCL.so.1: cannot open shared object file: No such file or directory

I'm trying out SDK 2.1 so I search this thread and find:

Quote from: DeathAndTaxes

Do a "find / -name libOpenCL.so.1"

then copying the file to cgminer's directory would probably the easiest...

Change to cgminers directory then do a "cp /path/to/file/libOpenCL.so.1 ." and start cgminer with ./cgminer

Code:

$ find / -name libOpenCL.so.1
$

Apparently it doesn't exist.

So I files > /opt/lib64/x86_64 to find libOpenCL.so

Are they the same file? Why is it named -.1?
What do I do to correct the issue so cgminer will churn?

Edit: Neglected to mention, in case it's important, I unpacked v2.1 as described in Kano's toot for v2.4.

P.S. AMD makes you jump through hoops now to get the older SDK's.
http://download2-developer.amd.com/amd/APPSDK/AMD-APP-SDK-v2.4-lnx64.tgz
" "/amd/Stream20GA/ati-stream-sdk-v2.1-lnx64.tgz
" "/amd/Stream20GA/icd-registration.tgz

demkd

full member

Activity: 242

Merit: 100

I run cgminer with -I 2 parameter, but this parameter is ignored and used intensity in config (since v2.3.4).
How can I override intensity for new versions of cgminer without changing config file?

-ck

legendary

Activity: 4088

Merit: 1631

Ruu \o/

Quote from: ddd1 on May 21, 2012, 03:18:02 AM

Quote from: -ck on May 21, 2012, 01:59:56 AM

As for accepted shares, this is hash rate * luck. Each card will encounter different luck so this is not unusual at all.

Is there a way to measure rate * luck?

I guess the card might be stable then even as it gave less shares?

Now:
"Card 1" A: 1304 R:65 HW:2 U: 8.86 I:7
"Card 2" A: 1268 R:28 HW:0 U: 8.58 I:9
Seems like wery few HW but the reject rate is 2-3% more on "Card 1"

You are thinking about this backwards. The way to measure rate * luck IS the utility rate. The only hint telling you what rate the card is hashing at is... the hashrate. Rejects are also purely random, but if you're running at higher intensity, it holds onto results for (slightly) longer so they are more likely to come back stale.

ddd1

full member

Activity: 154

Merit: 100

Quote from: -ck on May 21, 2012, 01:59:56 AM

Quote from: ddd1 on May 21, 2012, 01:54:57 AM

Quote from: -ck on May 20, 2012, 05:11:48 PM

Quote from: ddd1 on May 20, 2012, 09:04:20 AM

I really enjoy the program, stable and nice

Is there a way to reset to 0 all the stats without having to close cgminer?
Stats are shown in cgminer directly when running
I mean the 2 row of stats: <5s>: xxx : xxx Mh/s || Q:xxx A:xxx ............ and so on ......

Only with the restart command from the menu.

"[C]gminer restart" you mean?
I tried that and it just turned CGmienr off.

On another note, seems I have a wierd problem:

I think my "Card 1" might be too overclocked? Something is funky:
"Card 1": 663mhash | A: 557 R:16 HW:2 8.83/m I:7
"Card 2": 630mhash | A: 560 R: 3 HW:0 8.83/m I:9

So card one gives 33mhash more but less shares?!
Both cards have 100% load and "Card 1" is also primary connected to a display on windows 7.

Restart works when I test it. I don't know how you start it but presumably this is a windows issue that it's not restarting for you. Maybe you need to start it from a dos prompt and not a .bat file (dunno much about windows).

Card reliability is entirely random, even from the same manufacturer and the same batch, they take different amounts of overclock safely. Some will just plain crash when overclocked too much, some will have glitches in the form of hardware errors at overclocks below the crash level. As for accepted shares, this is hash rate * luck. Each card will encounter different luck so this is not unusual at all.

Is there a way to measure rate * luck?

I guess the card might be stable then even as it gave less shares?

Now:
"Card 1" A: 1304 R:65 HW:2 U: 8.86 I:7
"Card 2" A: 1268 R:28 HW:0 U: 8.58 I:9
Seems like wery few HW but the reject rate is 2-3% more on "Card 1"

-ck

legendary

Activity: 4088

Merit: 1631

Ruu \o/

Quote from: ddd1 on May 21, 2012, 01:54:57 AM

Quote from: -ck on May 20, 2012, 05:11:48 PM

Quote from: ddd1 on May 20, 2012, 09:04:20 AM

I really enjoy the program, stable and nice

Is there a way to reset to 0 all the stats without having to close cgminer?
Stats are shown in cgminer directly when running
I mean the 2 row of stats: <5s>: xxx : xxx Mh/s || Q:xxx A:xxx ............ and so on ......

Only with the restart command from the menu.

"[C]gminer restart" you mean?
I tried that and it just turned CGmienr off.

On another note, seems I have a wierd problem:

I think my "Card 1" might be too overclocked? Something is funky:
"Card 1": 663mhash | A: 557 R:16 HW:2 8.83/m I:7
"Card 2": 630mhash | A: 560 R: 3 HW:0 8.83/m I:9

So card one gives 33mhash more but less shares?!
Both cards have 100% load and "Card 1" is also primary connected to a display on windows 7.

Restart works when I test it. I don't know how you start it but presumably this is a windows issue that it's not restarting for you. Maybe you need to start it from a dos prompt and not a .bat file (dunno much about windows).

Card reliability is entirely random, even from the same manufacturer and the same batch, they take different amounts of overclock safely. Some will just plain crash when overclocked too much, some will have glitches in the form of hardware errors at overclocks below the crash level. As for accepted shares, this is hash rate * luck. Each card will encounter different luck so this is not unusual at all.

ddd1

full member

Activity: 154

Merit: 100

Quote from: -ck on May 20, 2012, 05:11:48 PM

Quote from: ddd1 on May 20, 2012, 09:04:20 AM

I really enjoy the program, stable and nice

Is there a way to reset to 0 all the stats without having to close cgminer?
Stats are shown in cgminer directly when running
I mean the 2 row of stats: <5s>: xxx : xxx Mh/s || Q:xxx A:xxx ............ and so on ......

Only with the restart command from the menu.

"[C]gminer restart" you mean?
I tried that and it just turned CGmienr off.

On another note, seems I have a wierd problem:

I think my "Card 1" might be too overclocked? Something is funky:
"Card 1": 663mhash | A: 557 R:16 HW:2 8.83/m I:7
"Card 2": 630mhash | A: 560 R: 3 HW:0 8.83/m I:9

So card one gives 33mhash more but less shares?!
Both cards have 100% load and "Card 1" is also primary connected to a display on windows 7.

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