Topic: OFFICIAL CGMINER mining software thread for linux/win/osx/mips/arm/r-pi 4.11.0 - page 605. (Read 5806103 times)
April 10, 2012, 03:04:04 AM
I have only autogpu enabled (dont want cgminer to control fans), and it worked before, on older version.
April 10, 2012, 02:45:12 AM
Huge issue with cgminer cant shut down gpu if its overheats. Cgminer trying it to disable the gpu over and over again, but its continuing to mine!
Do you have auto fan and auto gpu both enabled ?
I think that is the condition for the safety to kick in.
Read a few pages back, it is all there !
April 10, 2012, 02:40:14 AM
Huge issue with cgminer cant shut down gpu if its overheats. Cgminer trying it to disable the gpu over and over again, but its continuing to mine!
April 09, 2012, 07:44:05 PM
Woke up to a hung cgminer 
0% activity and no hashing
The log below hasn't changed in the last 5 hours, so I've restarted cgminer (had to X out of the window, as "q" wasn't working)
GPU 0/1 = 5970
GPU 2 = 5830
GPU 3 = 5830
GPU 4 = 5830
[2012-04-09 04:07:28] Accepted 00000000.398219cb.0ccf2195 GPU 4 thread 9
[2012-04-09 04:07:30] Accepted 00000000.5bb7eedb.2e813ef8 GPU 3 thread 7
[2012-04-09 04:07:30] GPU 3 stopped reporting fanspeed
[2012-04-09 04:07:30] Will attempt to re-initialise ADL
[2012-04-09 04:07:30] ADL re-initialisation complete
[2012-04-09 04:07:32] Accepted 00000000.031c03e9.d02f5836 GPU 3 thread 6
[2012-04-09 04:07:32] GPU 3 stopped reporting fanspeed
[2012-04-09 04:07:32] Will attempt to re-initialise ADL
[2012-04-09 04:07:32] ADL re-initialisation complete
That would probably be the new code that attempts to restart ADL when it stops reporting GPU info. 0% activity and no hashingThe log below hasn't changed in the last 5 hours, so I've restarted cgminer (had to X out of the window, as "q" wasn't working)
GPU 0/1 = 5970
GPU 2 = 5830
GPU 3 = 5830
GPU 4 = 5830
[2012-04-09 04:07:28] Accepted 00000000.398219cb.0ccf2195 GPU 4 thread 9
[2012-04-09 04:07:30] Accepted 00000000.5bb7eedb.2e813ef8 GPU 3 thread 7
[2012-04-09 04:07:30] GPU 3 stopped reporting fanspeed
[2012-04-09 04:07:30] Will attempt to re-initialise ADL
[2012-04-09 04:07:30] ADL re-initialisation complete
[2012-04-09 04:07:32] Accepted 00000000.031c03e9.d02f5836 GPU 3 thread 6
[2012-04-09 04:07:32] GPU 3 stopped reporting fanspeed
[2012-04-09 04:07:32] Will attempt to re-initialise ADL
[2012-04-09 04:07:32] ADL re-initialisation complete
Someone else mentioned a problem with it in IRC.
Looks like it doesn't work ... has anyone had it work yet?
It's this commit:
https://github.com/ckolivas/cgminer/commit/d4c513030f6d6da4cb54c0d1499d332a3987c376
If you remove the lines added at 686 to 690 (the whole 'if') it should stop it from attempting to do that for the time being until ckolivas gets back.
Good to know I'm not alone then. It just started in 2.3.2 and was fine in 2.3.1-2 Windows
I'll just wait for a fix in the meantime.
April 09, 2012, 07:40:29 PM
Can confirm, I have this same error on my 6950. The fan stops "reporting" or w/e and cgminer goes poop. I just restart CGMINER for now, but this happens maybe once a day or 2.
April 09, 2012, 04:26:39 PM
Woke up to a hung cgminer 0% activity and no hashing
The log below hasn't changed in the last 5 hours, so I've restarted cgminer (had to X out of the window, as "q" wasn't working)
GPU 0/1 = 5970
GPU 2 = 5830
GPU 3 = 5830
GPU 4 = 5830
[2012-04-09 04:07:28] Accepted 00000000.398219cb.0ccf2195 GPU 4 thread 9
[2012-04-09 04:07:30] Accepted 00000000.5bb7eedb.2e813ef8 GPU 3 thread 7
[2012-04-09 04:07:30] GPU 3 stopped reporting fanspeed
[2012-04-09 04:07:30] Will attempt to re-initialise ADL
[2012-04-09 04:07:30] ADL re-initialisation complete
[2012-04-09 04:07:32] Accepted 00000000.031c03e9.d02f5836 GPU 3 thread 6
[2012-04-09 04:07:32] GPU 3 stopped reporting fanspeed
[2012-04-09 04:07:32] Will attempt to re-initialise ADL
[2012-04-09 04:07:32] ADL re-initialisation complete
That would probably be the new code that attempts to restart ADL when it stops reporting GPU info. 0% activity and no hashingThe log below hasn't changed in the last 5 hours, so I've restarted cgminer (had to X out of the window, as "q" wasn't working)
GPU 0/1 = 5970
GPU 2 = 5830
GPU 3 = 5830
GPU 4 = 5830
[2012-04-09 04:07:28] Accepted 00000000.398219cb.0ccf2195 GPU 4 thread 9
[2012-04-09 04:07:30] Accepted 00000000.5bb7eedb.2e813ef8 GPU 3 thread 7
[2012-04-09 04:07:30] GPU 3 stopped reporting fanspeed
[2012-04-09 04:07:30] Will attempt to re-initialise ADL
[2012-04-09 04:07:30] ADL re-initialisation complete
[2012-04-09 04:07:32] Accepted 00000000.031c03e9.d02f5836 GPU 3 thread 6
[2012-04-09 04:07:32] GPU 3 stopped reporting fanspeed
[2012-04-09 04:07:32] Will attempt to re-initialise ADL
[2012-04-09 04:07:32] ADL re-initialisation complete
Someone else mentioned a problem with it in IRC.
Looks like it doesn't work ... has anyone had it work yet?
It's this commit:
https://github.com/ckolivas/cgminer/commit/d4c513030f6d6da4cb54c0d1499d332a3987c376
If you remove the lines added at 686 to 690 (the whole 'if') it should stop it from attempting to do that for the time being until ckolivas gets back.
April 09, 2012, 11:42:09 AM
Woke up to a hung cgminer 0% activity and no hashing
The log below hasn't changed in the last 5 hours, so I've restarted cgminer (had to X out of the window, as "q" wasn't working)
GPU 0/1 = 5970
GPU 2 = 5830
GPU 3 = 5830
GPU 4 = 5830
[2012-04-09 04:07:28] Accepted 00000000.398219cb.0ccf2195 GPU 4 thread 9
[2012-04-09 04:07:30] Accepted 00000000.5bb7eedb.2e813ef8 GPU 3 thread 7
[2012-04-09 04:07:30] GPU 3 stopped reporting fanspeed
[2012-04-09 04:07:30] Will attempt to re-initialise ADL
[2012-04-09 04:07:30] ADL re-initialisation complete
[2012-04-09 04:07:32] Accepted 00000000.031c03e9.d02f5836 GPU 3 thread 6
[2012-04-09 04:07:32] GPU 3 stopped reporting fanspeed
[2012-04-09 04:07:32] Will attempt to re-initialise ADL
[2012-04-09 04:07:32] ADL re-initialisation complete
0% activity and no hashingThe log below hasn't changed in the last 5 hours, so I've restarted cgminer (had to X out of the window, as "q" wasn't working)
GPU 0/1 = 5970
GPU 2 = 5830
GPU 3 = 5830
GPU 4 = 5830
[2012-04-09 04:07:28] Accepted 00000000.398219cb.0ccf2195 GPU 4 thread 9
[2012-04-09 04:07:30] Accepted 00000000.5bb7eedb.2e813ef8 GPU 3 thread 7
[2012-04-09 04:07:30] GPU 3 stopped reporting fanspeed
[2012-04-09 04:07:30] Will attempt to re-initialise ADL
[2012-04-09 04:07:30] ADL re-initialisation complete
[2012-04-09 04:07:32] Accepted 00000000.031c03e9.d02f5836 GPU 3 thread 6
[2012-04-09 04:07:32] GPU 3 stopped reporting fanspeed
[2012-04-09 04:07:32] Will attempt to re-initialise ADL
[2012-04-09 04:07:32] ADL re-initialisation complete
April 08, 2012, 08:53:50 PM
likely your pool implemented longer/better NTimeRolling.
Ozcoin just announced that they have adjusted their X-Roll-Ntime to 120 seconds, if you mine there it may have made a difference for you.
April 08, 2012, 08:18:48 PM
likely your pool implemented longer/better NTimeRolling.
Ozcoin just announced that they have adjusted their X-Roll-Ntime to 120 seconds, if you mine there it may have made a difference for you. 
April 08, 2012, 06:20:56 PM
(but it doesn't mean you are getting more shares)
I realize this. It's just nice to see overall network efficiency improving and less discarded work because of it. April 08, 2012, 06:18:34 PM
It is a pretty useless stat.
....unless you are a Pool OP that is and I am sure the OPs appreciate the newly found efficiency of CGMiner and the affect it has on Getwork requests and their server loads 
April 08, 2012, 06:07:48 PM
I'm a bit out of the loop, but, did something drastic change in 2.3.2 ?
I have rigs reporting as high as 170% Efficiency right now, with 125-150% being the average range for the others.
Win7 x64, CGMiner 2.3.2
5 rigs each with either SDK 2.1 or 2.4 and CAT 11.12 on all.
Mixed 5xxx/6xxx series card machines, exclusive 5xxx series card machines and exclusive 6xxx series card machines.
The performance is not specific to any card/config. The ONLY thing they all have in common is the 11.12 driver and CGminer version 2.3.2.
WTF ?
I double checked and didn't rely on the Efficiency% readout only. The ratio of GetWork's to Accepted's (even with Rejected included/excluded) does not lie.
Colour me impressed
Efficiency is the number of shares you find per work requests from the pool.I have rigs reporting as high as 170% Efficiency right now, with 125-150% being the average range for the others.
Win7 x64, CGMiner 2.3.2
5 rigs each with either SDK 2.1 or 2.4 and CAT 11.12 on all.
Mixed 5xxx/6xxx series card machines, exclusive 5xxx series card machines and exclusive 6xxx series card machines.
The performance is not specific to any card/config. The ONLY thing they all have in common is the 11.12 driver and CGminer version 2.3.2.
WTF ?
I double checked and didn't rely on the Efficiency% readout only. The ratio of GetWork's to Accepted's (even with Rejected included/excluded) does not lie.
Colour me impressed
However, with RollNTime, a miner can generate multiple work from the one work request.
So on my cgminer at the moment that shows Efficiency of 271% (which isn't actually very high) it means for each work request I ask from the pool, I generate on average 2.71 work requests (and on average reply with 2.71 shares)
The time it takes to mine those 2.71 shares is on average 2.71 times as long as mining 1 share.
A higher efficiency means that the pool had to provide you with less work and thus less communication and thus also less communication for your miner to the pool when trying to get work ...
Overall it's a big advantage for the pool and usually a small advantage for each miner
(but it doesn't mean you are getting more shares)
April 08, 2012, 05:40:17 PM
likely your pool implemented longer/better NTimeRolling.
BTW high (or low) efficiency has absolutely no effect on your bottom line. It is a pretty useless stat.
BTW high (or low) efficiency has absolutely no effect on your bottom line. It is a pretty useless stat.
April 08, 2012, 03:39:08 PM
I'm a bit out of the loop, but, did something drastic change in 2.3.2 ?
I have rigs reporting as high as 170% Efficiency right now, with 125-150% being the average range for the others.
Win7 x64, CGMiner 2.3.2
5 rigs each with either SDK 2.1 or 2.4 and CAT 11.12 on all.
Mixed 5xxx/6xxx series card machines, exclusive 5xxx series card machines and exclusive 6xxx series card machines.
The performance is not specific to any card/config. The ONLY thing they all have in common is the 11.12 driver and CGminer version 2.3.2.
WTF ?
I double checked and didn't rely on the Efficiency% readout only. The ratio of GetWork's to Accepted's (even with Rejected included/excluded) does not lie.
Colour me impressed
I have rigs reporting as high as 170% Efficiency right now, with 125-150% being the average range for the others.
Win7 x64, CGMiner 2.3.2
5 rigs each with either SDK 2.1 or 2.4 and CAT 11.12 on all.
Mixed 5xxx/6xxx series card machines, exclusive 5xxx series card machines and exclusive 6xxx series card machines.
The performance is not specific to any card/config. The ONLY thing they all have in common is the 11.12 driver and CGminer version 2.3.2.
WTF ?
I double checked and didn't rely on the Efficiency% readout only. The ratio of GetWork's to Accepted's (even with Rejected included/excluded) does not lie.
Colour me impressed
April 07, 2012, 04:20:22 PM
Seems like diablo and poclbm now fail to compile on SDK 2.1 and seg fault.
Not a problem just letting others know on 5870s.
Use diakgcn or phatk with 5870s and SDK 2.1
It seems that diakgcn is not as good as phatk.
Not a problem just letting others know on 5870s.
Use diakgcn or phatk with 5870s and SDK 2.1
It seems that diakgcn is not as good as phatk.
April 05, 2012, 08:45:31 AM
The problem is that BAMT then does a process kill after the quit command - which of course only a program running on the same machine can kill a process.
Ahh that makes sense. Thanks a lot!
April 04, 2012, 05:57:44 PM
I have a weird problem, doesn't happen in 2.3.1, but 2.3.2 has the problem... whenever I run in a screen, cgminer stops within a minute or two with this in the log:
...
BAMT running?Code:
[2012-04-04 16:50:02] API: connection from 127.0.0.1 - Accepted
[2012-04-04 16:50:02] API: recv command: (6) 'quit|
'
[2012-04-04 16:50:02] API: access denied to '127.0.0.1' for 'quit' command
[2012-04-04 16:50:02] API: send reply: (96) 'STATUS=E,W...'
[2012-04-04 16:50:02] API: sent 96
That "quit|\n" is what BAMT used to send cgminer (and probably still does) rather than just "quit"
Anyway the message means that something somewhere on your computer is send a "quit|\n" to cgminer and then killing the cgminer process (when the quit fails)
My guess would be BAMT - since that's what it does.
(unless someone else has written something to work like BAMT)
Yup... BAMT. Now that I look there, I see it sending the quit in the logs... But the quit only kills cgminer when I run cgminer in a screen... weird.
It was fix 20 that added a cgminer watchdog.... since I'm not starting cgminer with the official BAMT profile, that probably caused some issue. I removed BAMT fix 20 and its running fine now. Thanks Kano!
Any way to make the cgminer API "readonly" or block the "quit" command?
Code:
[2012-04-04 16:50:02] API: access denied to '127.0.0.1' for 'quit' command
The problem is that BAMT then does a process kill after the quit command - which of course only a program running on the same machine can kill a process.
April 04, 2012, 05:31:07 PM
I have a weird problem, doesn't happen in 2.3.1, but 2.3.2 has the problem... whenever I run in a screen, cgminer stops within a minute or two with this in the log:
...
BAMT running?Code:
[2012-04-04 16:50:02] API: connection from 127.0.0.1 - Accepted
[2012-04-04 16:50:02] API: recv command: (6) 'quit|
'
[2012-04-04 16:50:02] API: access denied to '127.0.0.1' for 'quit' command
[2012-04-04 16:50:02] API: send reply: (96) 'STATUS=E,W...'
[2012-04-04 16:50:02] API: sent 96
That "quit|\n" is what BAMT used to send cgminer (and probably still does) rather than just "quit"
Anyway the message means that something somewhere on your computer is send a "quit|\n" to cgminer and then killing the cgminer process (when the quit fails)
My guess would be BAMT - since that's what it does.
(unless someone else has written something to work like BAMT)
Yup... BAMT. Now that I look there, I see it sending the quit in the logs... But the quit only kills cgminer when I run cgminer in a screen... weird.
It was fix 20 that added a cgminer watchdog.... since I'm not starting cgminer with the official BAMT profile, that probably caused some issue. I removed BAMT fix 20 and its running fine now. Thanks Kano!
Any way to make the cgminer API "readonly" or block the "quit" command?
April 04, 2012, 05:25:06 PM
I have a weird problem, doesn't happen in 2.3.1, but 2.3.2 has the problem... whenever I run in a screen, cgminer stops within a minute or two with this in the log:
...
BAMT running?Code:
[2012-04-04 16:50:02] API: connection from 127.0.0.1 - Accepted
[2012-04-04 16:50:02] API: recv command: (6) 'quit|
'
[2012-04-04 16:50:02] API: access denied to '127.0.0.1' for 'quit' command
[2012-04-04 16:50:02] API: send reply: (96) 'STATUS=E,W...'
[2012-04-04 16:50:02] API: sent 96
That "quit|\n" is what BAMT used to send cgminer (and probably still does) rather than just "quit"
Anyway the message means that something somewhere on your computer is send a "quit|\n" to cgminer and then killing the cgminer process (when the quit fails)
My guess would be BAMT - since that's what it does.
(unless someone else has written something to work like BAMT)
April 04, 2012, 05:02:42 PM
EDIT: Found out it was fix 20 for bamt, just happened to apply that the same time i went to 2.3.2.... thank Kano!
I have a weird problem, doesn't happen in 2.3.1, but 2.3.2 has the problem... whenever I run in a screen, cgminer stops within a minute or two with this in the log:
However, if I run it without the screen command, it runs just fine....
My script to start with screen is:
Where quickcgminer.sh is:
If run just /root/quickcgminer.sh, then it runs just fine... without any quitting, so seems to be something with the screen command?
Any ideas?
I have a weird problem, doesn't happen in 2.3.1, but 2.3.2 has the problem... whenever I run in a screen, cgminer stops within a minute or two with this in the log:
Code:
[2012-04-04 16:50:02] API: connection from 127.0.0.1 - Accepted
[2012-04-04 16:50:02] API: recv command: (6) 'quit|
'
[2012-04-04 16:50:02] API: access denied to '127.0.0.1' for 'quit' command
[2012-04-04 16:50:02] API: send reply: (96) 'STATUS=E,W...'
[2012-04-04 16:50:02] API: sent 96
However, if I run it without the screen command, it runs just fine....
My script to start with screen is:
Code:
/usr/bin/screen -dmS cgminer /root/quickcgminer.sh
Where quickcgminer.sh is:
Code:
export GPU_USE_SYNC_OBJECTS=1
export DISPLAY=:0
cd /opt/miners/ckolivas-cgminer-ef76ec8
/opt/miners/ckolivas-cgminer-ef76ec8/cgminer -D --verbose --api-listen -Q 8 --gpu-threads 2 --gpu-engine 800-1180,800-1190,800-1220 --gpu-memdiff -150 --auto-fan --auto-gpu --temp-target 75 -I 11 -o http://gpumax.com:8332 -u x -p x -o http://pool.bitlc.net:80 -u x -p x -o http://mint.bitminter.com:8332 -u x -p x 2>/root/log.txt
If run just /root/quickcgminer.sh, then it runs just fine... without any quitting, so seems to be something with the screen command?
Any ideas?
Jump to: