Topic: OFFICIAL CGMINER mining software thread for linux/win/osx/mips/arm/r-pi 4.11.0 - page 683. (Read 5805728 times)
January 29, 2012, 05:20:45 PM
Try cleaning out your tree with a fresh ./autogen.sh && ./configure && make clean first perhaps.
January 29, 2012, 05:12:26 PM
[...]
Most unusualNo system changes should be needed.
ADL failing to initialise could be anything, but seems more common with multiple instances of cgminer running. Can you do a git pull and start with --verbose -D and see what it says with the extra debugging I just committed?
What does the startup debugging give on the first device if you delete the binaries?
30% sounds like something horribly wrong. In fact it looks like all 3 "GPUs" may just be one device.
EDIT: You did do "export DISPLAY=:0" didn't you?
Code:
[Thread debugging using libthread_db enabled]
[2012-01-29 23:06:22] Started cgminer 2.2.0
Program received signal SIGSEGV, Segmentation fault.
0x0026dc0e in ?? () from /lib/i386-linux-gnu/libc.so.6
(gdb) bt
#0 0x0026dc0e in ?? () from /lib/i386-linux-gnu/libc.so.6
#1 0x0026f925 in ?? () from /lib/i386-linux-gnu/libc.so.6
#2 0x00272f22 in calloc () from /lib/i386-linux-gnu/libc.so.6
#3 0x01b2f8b2 in XOpenDisplay () from /usr/lib/i386-linux-gnu/libX11.so.6
#4 0x02653003 in ?? () from /usr/lib/fglrx/libatiadlxx.so
#5 0x02652dc8 in ADL_Main_Control_Create () from /usr/lib/fglrx/libatiadlxx.so
#6 0x08062403 in init_adl (nDevs=3) at adl.c:172
#7 0x0804e731 in opencl_detect () at main.c:5563
#8 0x08058820 in main (argc=1, argv=0xbffff6d4) at main.c:5982
2.1.1 binary still working :-/
WTF? Sorry if it as known issue, though. Was not able to read the whole thread to find some indication.
January 29, 2012, 04:55:49 PM
i have 2 GPU, one 5870 and oone 3xxx
And this newer version does not work on my setup, used to work fine.
Go here:And this newer version does not work on my setup, used to work fine.
https://bitcointalksearch.org/topic/m.720267
January 29, 2012, 04:54:19 PM
i have 2 GPU, one 5870 and oone 3xxx
And this newer version does not work on my setup, used to work fine.
And this newer version does not work on my setup, used to work fine.
January 29, 2012, 04:25:31 PM
Any system changes needed with Linux to move from 2.1.1 to 2.2.0?
I'm observing massive problems with the latest updates.
I kept the previous working binary as reference, but was not able to isolate the problem. First obvious thing is ADL fails to initialize:
The remaining initialization sequence looks ok, at least no obvious differences to what 2.1.1 was reporting:
...but the hash rates achieved are at about 30%
of what 2.1.1 does:
As said, using the same APP and ADL version, same kernel. I also tried with deleting previous kernel binaries with the same result. I am using the current git HEAD for 2.2.0 (82af288e69).
Any ideas?
Most unusualI'm observing massive problems with the latest updates.
I kept the previous working binary as reference, but was not able to isolate the problem. First obvious thing is ADL fails to initialize:
Code:
[2012-01-29 19:30:32] ADL Initialisation Error!
The remaining initialization sequence looks ok, at least no obvious differences to what 2.1.1 was reporting:
Code:
[2012-01-29 19:30:35] Loaded binary image phatk110817Caymanbitalignv2w128long4.bin
...but the hash rates achieved are at about 30%
Code:
[2012-01-29 20:18:56] GPU2 (5s):95.6 (avg):121.2 Mh/s | A:43 R:0 HW:0 U:1.44/m I: 9
of what 2.1.1 does:
Code:
[2012-01-29 20:22:51] GPU2 (5s):372.4 (avg):350.6 Mh/s | A:4 R:0 HW:0 U:4.35/m | I: 9
As said, using the same APP and ADL version, same kernel. I also tried with deleting previous kernel binaries with the same result. I am using the current git HEAD for 2.2.0 (82af288e69).
Any ideas?
No system changes should be needed.
ADL failing to initialise could be anything, but seems more common with multiple instances of cgminer running. Can you do a git pull and start with --verbose -D and see what it says with the extra debugging I just committed?
What does the startup debugging give on the first device if you delete the binaries?
30% sounds like something horribly wrong. In fact it looks like all 3 "GPUs" may just be one device.
EDIT: You did do "export DISPLAY=:0" didn't you?
January 29, 2012, 04:18:16 PM
when using anything above intensity 9 on my 5970 w/ 11.12 drivers. The cpu usage is pegged... 9 and below cpu usage is 0%
Any reason why its higher on I 10+? thanks
Any reason why its higher on I 10+? thanks
just curious what mhash your getting with your 5970 using 11.12 ? I messed around with several different configurations over the last couple of days for mine and the best I came up with is 11.9 w/ cgminer 2.20 - I get a nice 820 mhash - woohoo!
wow nice mhash! what clocks?
I get 715mh/s @ 780/300mhz vgpu @ 1.030v
850/180 - untouched voltage
Win7 x64 w/ CCC 11.9 + CGM 2.2.0
Kano: thanks for a bunch of information I did not ask for! - Looks like dummies like me should just read the damn README before wasting your time!
(just kidding - I already figured that out but thanks)
January 29, 2012, 04:07:43 PM
when using anything above intensity 9 on my 5970 w/ 11.12 drivers. The cpu usage is pegged... 9 and below cpu usage is 0%
Any reason why its higher on I 10+? thanks
Any reason why its higher on I 10+? thanks
just curious what mhash your getting with your 5970 using 11.12 ? I messed around with several different configurations over the last couple of days for mine and the best I came up with is 11.9 w/ cgminer 2.20 - I get a nice 820 mhash - woohoo!
btw: ckvolias do you know why Anubis web front end stopped working with the 2.2.0 upgrade?
thanks!
The README explains all the other changes to the API ...
Most notably, it mentions that the CPU|N command is no longer available on software not compiled with CPU support.
The README also says that you should check "cpucount" or "config" to determine if there is any CPU info available.
"config" also tells you if ADL is available and also if any GPU's use ADL - thus if the new ADL commands should succeed or fail.
January 29, 2012, 04:05:38 PM
when using anything above intensity 9 on my 5970 w/ 11.12 drivers. The cpu usage is pegged... 9 and below cpu usage is 0%
Any reason why its higher on I 10+? thanks
Any reason why its higher on I 10+? thanks
just curious what mhash your getting with your 5970 using 11.12 ? I messed around with several different configurations over the last couple of days for mine and the best I came up with is 11.9 w/ cgminer 2.20 - I get a nice 820 mhash - woohoo!
wow nice mhash! what clocks?
I get 715mh/s @ 780/300mhz vgpu @ 1.030v
January 29, 2012, 03:51:49 PM
Tell me then why I don't have any cpu usage with even 12 intensity with 2.1, but have all up to 100% on one core (with 1 gpu miner) with all other sdk's? It's the same bug.
If you posted your driver version, OS and GPU config someone could try to unravel your issue but this is hardly the appropriate thread.Proof by counter-example: a lot of miners moved to 11.11 or 11.12 driver and reported no CPU-hogging issues. Therefore, the major CPU-hogging flaw has been fixed.
Computers and operating systems are inherently very complex subjects and great many things can go wrong. Unexpected combinations of drivers, SDKs and system libraries can still peg the CPU but it's luckily relatively uncommon. Mixing x64 and x86 code can be a real pain.
EDIT:: Con, latest git works like a charm
The GPU order has changed on my Debian machines, though.https://bitcointalksearch.org/topic/m.718469
And btw I use intensity @ 9 right now.
January 29, 2012, 03:44:01 PM
Tell me then why I don't have any cpu usage with even 12 intensity with 2.1, but have all up to 100% on one core (with 1 gpu miner) with all other sdk's? It's the same bug.
If you posted your driver version, OS and GPU config someone could try to unravel your issue but this is hardly the appropriate thread.Proof by counter-example: a lot of miners moved to 11.11 or 11.12 driver and reported no CPU-hogging issues. Therefore, the major CPU-hogging flaw has been fixed.
Computers and operating systems are inherently very complex subjects and great many things can go wrong. Unexpected combinations of drivers, SDKs and system libraries can still peg the CPU but it's luckily relatively uncommon. Mixing x64 and x86 code can not only be a real pain but also result in undefined behavior.
EDIT:: Con, latest git works like a charm
The GPU order has changed on my Debian machines, though.EDIT:: Another donation is due as soon as my wallet recuperates.
January 29, 2012, 03:39:28 PM
when using anything above intensity 9 on my 5970 w/ 11.12 drivers. The cpu usage is pegged... 9 and below cpu usage is 0%
Any reason why its higher on I 10+? thanks
Any reason why its higher on I 10+? thanks
just curious what mhash your getting with your 5970 using 11.12 ? I messed around with several different configurations over the last couple of days for mine and the best I came up with is 11.9 w/ cgminer 2.20 - I get a nice 820 mhash - woohoo!
btw: ckvolias do you know why Anubis web front end stopped working with the 2.2.0 upgrade?
thanks!
January 29, 2012, 03:36:19 PM
Calm down fellas. They're different CPU bugs. There are 3 in all. Either way intensity above 9 is mostly harmful.
January 29, 2012, 03:32:46 PM
This is the infamous cpu bug.
No it's bloody damned not.THE cpu bug would eat a whole core no matter what intensity/aggression you'd chosen.
It was caused by AMD's driver fuck-up and has since been fixed.
There have been some OS-specific CPU hogging issues, eg with Ubuntu.
Do the research first and don't post misleading and inaccurate information, k?
January 29, 2012, 03:28:35 PM
This is the infamous cpu bug.
No it's bloody damned not.THE cpu bug would eat a whole core no matter what intensity/aggression you'd chosen.
It was caused by AMD's driver fuck-up and has since been fixed.
There have been some OS-specific CPU hogging issues, eg with Ubuntu.
Do the research first and don't post misleading and try not to post inaccurate information, k?
Intensity higher than 9 is only supposed to be used with 79xx cards.
January 29, 2012, 03:21:38 PM
when using anything above intensity 9 on my 5970 w/ 11.12 drivers. The cpu usage is pegged... 9 and below cpu usage is 0%
Any reason why its higher on I 10+? thanks
This is the infamous cpu bug. Any reason why its higher on I 10+? thanks
January 29, 2012, 03:05:55 PM
when using anything above intensity 9 on my 5970 w/ 11.12 drivers. The cpu usage is pegged... 9 and below cpu usage is 0%
Any reason why its higher on I 10+? thanks
Any reason why its higher on I 10+? thanks
just curious what mhash your getting with your 5970 using 11.12 ? I messed around with several different configurations over the last couple of days for mine and the best I came up with is 11.9 w/ cgminer 2.20 - I get a nice 820 mhash - woohoo!
btw: ckvolias do you know why Anubis web front end stopped working with the 2.2.0 upgrade?
thanks!
January 29, 2012, 02:56:59 PM
when using anything above intensity 9 on my 5970 w/ 11.12 drivers. The cpu usage is pegged... 9 and below cpu usage is 0%
Any reason why its higher on I 10+? thanks
You are only supposed to use 10+ with the new 79xx cards. I'm positive Con mentioned that somewhere around here. Any reason why its higher on I 10+? thanks
January 29, 2012, 02:35:39 PM
when using anything above intensity 9 on my 5970 w/ 11.12 drivers. The cpu usage is pegged... 9 and below cpu usage is 0%
Any reason why its higher on I 10+? thanks
Any reason why its higher on I 10+? thanks
January 29, 2012, 02:31:52 PM
Any system changes needed with Linux to move from 2.1.1 to 2.2.0?
I'm observing massive problems with the latest updates.
I kept the previous working binary as reference, but was not able to isolate the problem. First obvious thing is ADL fails to initialize:
The remaining initialization sequence looks ok, at least no obvious differences to what 2.1.1 was reporting:
...but the hash rates achieved are at about 30%
of what 2.1.1 does:
As said, using the same APP and ADL version, same kernel. I also tried with deleting previous kernel binaries with the same result. I am using the current git HEAD for 2.2.0 (82af288e69).
Any ideas?
I'm observing massive problems with the latest updates.
I kept the previous working binary as reference, but was not able to isolate the problem. First obvious thing is ADL fails to initialize:
Code:
[2012-01-29 19:30:32] Started cgminer 2.2.0
[2012-01-29 19:30:32] CL Platform vendor: Advanced Micro Devices, Inc.
[2012-01-29 19:30:32] CL Platform name: AMD Accelerated Parallel Processing
[2012-01-29 19:30:32] CL Platform version: OpenCL 1.1 AMD-APP-SDK-v2.4 (595.10)
[2012-01-29 19:30:32] ADL Initialisation Error!
The remaining initialization sequence looks ok, at least no obvious differences to what 2.1.1 was reporting:
Code:
[2012-01-29 19:30:35] Init GPU thread 0 GPU 0 virtual GPU 0
[2012-01-29 19:30:35] CL Platform vendor: Advanced Micro Devices, Inc.
[2012-01-29 19:30:35] CL Platform name: AMD Accelerated Parallel Processing
[2012-01-29 19:30:35] CL Platform version: OpenCL 1.1 AMD-APP-SDK-v2.4 (595.10)
[2012-01-29 19:30:35] List of devices:
[2012-01-29 19:30:35] 0 Cayman
[2012-01-29 19:30:35] 1 Cayman
[2012-01-29 19:30:35] 2 Cayman
[2012-01-29 19:30:35] Selected 0: Cayman
[2012-01-29 19:30:35] Preferred vector width reported 4
[2012-01-29 19:30:35] Max work group size reported 256
[2012-01-29 19:30:35] Long-polling activated for http://pit.deepbit.net:8332/listenChannel
[2012-01-29 19:30:35] Loaded binary image phatk110817Caymanbitalignv2w128long4.bin
[2012-01-29 19:30:35] Initialising kernel phatk110817.cl with BFI_INT, 2 vectors and worksize 128
[2012-01-29 19:30:35] initCl() finished. Found Cayman
[2012-01-29 19:30:35] Pushing ping to thread 1
...but the hash rates achieved are at about 30%
Code:
[2012-01-29 20:18:56] GPU0 (5s):131.0 (avg):123.5 Mh/s | A:53 R:0 HW:0 U:1.77/m I: 9
[2012-01-29 20:18:56] GPU1 (5s):103.2 (avg):121.8 Mh/s | A:55 R:0 HW:0 U:1.84/m I: 9
[2012-01-29 20:18:56] GPU2 (5s):95.6 (avg):121.2 Mh/s | A:43 R:0 HW:0 U:1.44/m I: 9
of what 2.1.1 does:
Code:
[2012-01-29 20:22:51] GPU0 (5s):363.3 (avg):370.0 Mh/s | A:5 R:0 HW:0 U:4.58/m | I: 9
[2012-01-29 20:22:51] GPU1 (5s):360.9 (avg):365.9 Mh/s | A:2 R:0 HW:0 U:3.61/m | I: 9
[2012-01-29 20:22:51] GPU2 (5s):372.4 (avg):350.6 Mh/s | A:4 R:0 HW:0 U:4.35/m | I: 9
As said, using the same APP and ADL version, same kernel. I also tried with deleting previous kernel binaries with the same result. I am using the current git HEAD for 2.2.0 (82af288e69).
Any ideas?
January 29, 2012, 02:25:51 PM
Ok, I'm running 2.1 SDK now, but most of gpu stats (like temp, clocks, voltage, etc) isn't showing in gpu menu. 
However yesterday with 2.1.2 and 2.5 it worked fine. Using 2.2.0 now.
UPD: oops, looks, like missing "[C]hange settings" option in 2.2.0.
However yesterday with 2.1.2 and 2.5 it worked fine. Using 2.2.0 now.UPD: oops, looks, like missing "[C]hange settings" option in 2.2.0.
That happens when cgminer doesn't detect ADL support. For me it happens when using remote desktop. The change in driver version is likely coincidental. cgminer makes changes to cards and gets "stats" via ADL.
Are you accessing the rig remotely? If not try a reboot and use cgminer before anything else. I have seen AMD ADL driver? service? crash and that causes those options to "disapear".
Jump to: