Author

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

-ck
legendary
Activity: 4088
Merit: 1631
Ruu \o/
The git ride is about to get rather bumpy. Please be careful if you're pulling at random intervals.

With such a big update going to 2.2.0 it was inevitable some bugs would creep in. I'm trying to iron them all out and work on a bugfix-only 2.2.1 release as soon as is feasible. Having my mining rig AT LAST back will make it much much easier to test all this shit.
sr. member
Activity: 435
Merit: 250
I know it's a bit late with having made the device reorder part of an official release but I was wondering if people would prefer it to be optional in the next release instead of mandatory? I know some of you have some complex set ups with config files and device specific setting and so on that will be broken on going to 2.2.0, and I'm not against changing it back to the old behaviour and making it optional with something like --dev-reorder .

+1 for --dev-reorder. It's really awkward to have (for example) gpumon saying one thing, and cgminer saying it in reverse. Or the other way around.
-ck
legendary
Activity: 4088
Merit: 1631
Ruu \o/
I know it's a bit late with having made the device reorder part of an official release but I was wondering if people would prefer it to be optional in the next release instead of mandatory? I know some of you have some complex set ups with config files and device specific setting and so on that will be broken on going to 2.2.0, and I'm not against changing it back to the old behaviour and making it optional with something like --dev-reorder .
-ck
legendary
Activity: 4088
Merit: 1631
Ruu \o/
Sleep tight, but unfortunately you've picked one of the bad commits. That code never worked as they were attempts at doing it that didn't work properly and evolved like this (first unbroken commit was 05970):

commit 83a836765432dbc88b972588fb678aff17979a35
    Linux's ADL uses a busnumber in descending order for devices so enumerate them in the opposite order to windows.

commit 059701272c75bc30236f1c4a3aaf8db5e59bf718
    Carry virtual gpu number across.

commit 3bc0583454b09b5c4dac18450c4766572d69644f
    Iterate and change virtual device order instead of shuffling ram.

commit 371e5f688a2b6e5446e243ac9edcc490c0243a79
    Reorder displayed devices to map to physical locations and initialise according to logical location instead.

commit 5a0b4f62d0966d08bd92142d92d8b97f8e68f1e7
    Map GPU devices to virtual devices in their true physical order based on BusNumber.

donator
Activity: 919
Merit: 1000
Try cleaning out your tree with a fresh ./autogen.sh && ./configure && make clean first perhaps.
Did everything, also freshly installed APP-2.5.

Problem is reliably reproducible with my setup (3*6950).

I bisected and found that the problematic commit is 371e5f68, while all builds with up to 5a0b4f62 work.

Need to go now. If you have some ideas on how I can help identifying the problem, let me know.


Good night.
-ck
legendary
Activity: 4088
Merit: 1631
Ruu \o/
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:
https://bitcointalksearch.org/topic/m.720267

http://ck.kolivas.org/apps/cgminer/temp/

Since this may be a recurring theme, I've uploaded a new bleeding edge binary for both windows and linux into that directory which can work around the problem but will give a warning when it happens. I'll try and keep bleeding edge binaries in there if/when required.

Starting with --verbose with these binaries should give you a lot more information which will help you debug where devices are going as well if you're having a new ordering issue.
-ck
legendary
Activity: 4088
Merit: 1631
Ruu \o/
Try cleaning out your tree with a fresh ./autogen.sh && ./configure && make clean first perhaps.
donator
Activity: 919
Merit: 1000
[...]
Most unusual

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?
Something's really fishy. Rebuilt HEAD (f0746f0b4c), now it's crashing:
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.
-ck
legendary
Activity: 4088
Merit: 1631
Ruu \o/
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:
https://bitcointalksearch.org/topic/m.720267
member
Activity: 77
Merit: 10
i have 2 GPU, one 5870 and oone 3xxx
And this newer version does not work on my setup, used to work fine.
-ck
legendary
Activity: 4088
Merit: 1631
Ruu \o/
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:
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?
Most unusual

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?
hero member
Activity: 896
Merit: 1000
Buy this account on March-2019. New Owner here!!
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

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! Smiley

(just kidding - I already figured that out but thanks)
legendary
Activity: 4634
Merit: 1851
Linux since 1997 RedHat 4
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

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 RPC API version is now 1.0
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.
legendary
Activity: 2450
Merit: 1002
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

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
hero member
Activity: 535
Merit: 500
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 Smiley The GPU order has changed on my Debian machines, though.
I fixed it already, just said that he has the same bug. Sometimes it's a very minor cpu load with low intensity/aggression, but it's the same issue. Read this reply and 2 next ones.
https://bitcointalksearch.org/topic/m.718469
 And btw I use intensity @ 9 right now.
full member
Activity: 210
Merit: 100
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 Smiley The GPU order has changed on my Debian machines, though.
EDIT:: Another donation is due as soon as my wallet recuperates.
-ck
legendary
Activity: 4088
Merit: 1631
Ruu \o/
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

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!
Changed API with the newer commands I would guess.
-ck
legendary
Activity: 4088
Merit: 1631
Ruu \o/
Calm down fellas. They're different CPU bugs. There are 3 in all. Either way intensity  above 9 is mostly harmful.
hero member
Activity: 535
Merit: 500
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?
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 (in case of Win7)? It's the same bug. It's a slight usage ~15-17% on one core, if I use buggy sdk and aggression 9, with 8 - zero usage. Higher intensity > higher cpu load with buggy sdk's, cept 8.
full member
Activity: 210
Merit: 100
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.
Jump to: