Author

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

legendary
Activity: 1540
Merit: 1002
Is anyone already doing ztex boards support for cgminer? I'm not sure about timeframes but I'm considering taking a stab at it seeing as I have the protocol "fresh" in my mind from the initial implementation for MPBM, but I'd hate to start it just to find out someone else is almost done with it Smiley
No one has started, but see here: http://bountychest.com/bountychest/ztex-support-for-cgminer/

I see there are already some donations done towards that bounty and I really don't want to step in anybody's toes. If I do.decide to jump into this I'll try to be as public about it as possible and I hope anybody else tackling the same problem does the same.

Ztex already proposed sending a board for free for this purpose, which I will not be requesting so I ask again: anyone thinking of taking the challenge in the next couple of weeks?
-ck
legendary
Activity: 4088
Merit: 1631
Ruu \o/
Smoking...

Looks like I picked a good time for a break from cgminer code, since I smoked my PSU the other day and my mining rig is back in the workshop. Thank goodness for warranties lol.
-ck
legendary
Activity: 4088
Merit: 1631
Ruu \o/
On a side note, on series 5xxx and 6xxx, using poclbm with any sdk above 2.1 is a performance loss, as is using phatk with anything below 2.4.

Really? Using 960/300 clocks on a 5870, -g 1 -I 8 (p2pool), tried with and without -w 256 -v 2, I get much worse performance on poclbm + 2.1 compared to phatk + 2.1.

Phatk + 2.1 and phatk + 2.4 is about the same though, with 2.4 taking a very slight lead (<1%) .

What would you recommend as settings for poclbm? I do remember it being better back in the day too, but haven't played much with 2.1 lately. Also, keeping memory speeds low is a must  Tongue

Any recollection you have about poclbm kernel is irrelevant I'm afraid. Note that the so-called poclbm kernel in cgminer has been DRASTICALLY rewritten by myself to be optimal with sdk 2.6+. So that even though it's called poclbm it really has very little in common with the original poclbm kernel. It appears to work well with 79xx and 69xx cards and sdk 2.6+ only.
-ck
legendary
Activity: 4088
Merit: 1631
Ruu \o/
I know it'll compile fine without CPU mining, but I want to do some testing with it enabled... I want to see how Anubis handles it. If it's more trouble to get it working than it's worth, I'll forget about supporting CPUs in Anubis.
CPU mining is deprecated and the code will be completely removed in the future. Do not try to port or get anything working with it.
-ck
legendary
Activity: 4088
Merit: 1631
Ruu \o/
I'm trying to use the 2.1 SDK for the 5xxx and 2.6 for the 6xxx. Everything works fine using the 2.6 sdk, but it obviously isnt efficient for the 5xxx series.
Phoenix 2.0 lets me use the setup I want, but it lacks lots of features.

I also tried making cgminer use bins compiled for 2.1 while using the 2.6 sdk but it just recompiles them again. The ideal would be making --gpu-platform a per device option, something like --gpu-platform 0,0,1
You can only specify one gpu platform, but you can force it to use whatever combination by starting it a couple of times if you specify exactly the kernel, vectors and worksize.

Eg start with --gpu-platform 0 (if that is sdk 2.1) --kernel phatk,diablo -v 2,1 -w 256,128

Then you will get two bins. Delete the one that you don't want running with sdk 2.1 and start again with the same commands except for --gpu-platform 1 (if that's sdk 2.6) and it will build a bin only the one that doesn't exist.
-ck
legendary
Activity: 4088
Merit: 1631
Ruu \o/
Is anyone already doing ztex boards support for cgminer? I'm not sure about timeframes but I'm considering taking a stab at it seeing as I have the protocol "fresh" in my mind from the initial implementation for MPBM, but I'd hate to start it just to find out someone else is almost done with it Smiley
No one has started, but see here: http://bountychest.com/bountychest/ztex-support-for-cgminer/
legendary
Activity: 1540
Merit: 1002
Is anyone already doing ztex boards support for cgminer? I'm not sure about timeframes but I'm considering taking a stab at it seeing as I have the protocol "fresh" in my mind from the initial implementation for MPBM, but I'd hate to start it just to find out someone else is almost done with it Smiley
sr. member
Activity: 465
Merit: 254
Thanks to both of you. It worked great.
sr. member
Activity: 349
Merit: 250
Is there any way to avoid one of my GPU cores to start at all when I run cgminer?
I have a 5970 card were one core is defect and if I try to mine on it my computer instantly crashes. The other core works fine and I am mining on it using GUIminer, but would like to switch to cgminer.

Is there anything I can put in the config file to make sure GPU0 never starts when I run cgminer?

--device|-d   Select device to use, (Use repeat -d for multiple devices, default: all)

I would start cgminer using the --device 1, assuming a single 5970, this will skip device 0, the problem gpu. Then you can write the config file while cgminer is running. [ S]ettings, [W]rite config file, then you are done.

[Edit]thought I was first to post a reply, twenty minutes later I see a reply before me, odd.
member
Activity: 121
Merit: 10
Is there any way to avoid one of my GPU cores to start at all when I run cgminer?
I have a 5970 card were one core is defect and if I try to mine on it my computer instantly crashes. The other core works fine and I am mining on it using GUIminer, but would like to switch to cgminer.

Is there anything I can put in the config file to make sure GPU0 never starts when I run cgminer?


"cgminer -d 1 -d 2 ... -d n" should work. Or the equivalent in config file, however that works.
sr. member
Activity: 465
Merit: 254
Is there any way to avoid one of my GPU cores to start at all when I run cgminer?
I have a 5970 card were one core is defect and if I try to mine on it my computer instantly crashes. The other core works fine and I am mining on it using GUIminer, but would like to switch to cgminer.

Is there anything I can put in the config file to make sure GPU0 never starts when I run cgminer?
sr. member
Activity: 467
Merit: 250
Here is it
http://pastebin.com/gpFDyXef

requires screen

this should be spun off into its' own thread so people don't miss this great script... I've been looking for something like this for a long while.. well done!

Vbs
hero member
Activity: 504
Merit: 500
On a side note, on series 5xxx and 6xxx, using poclbm with any sdk above 2.1 is a performance loss, as is using phatk with anything below 2.4.

Really? Using 960/300 clocks on a 5870, -g 1 -I 8 (p2pool), tried with and without -w 256 -v 2, I get much worse performance on poclbm + 2.1 compared to phatk + 2.1.

Phatk + 2.1 and phatk + 2.4 is about the same though, with 2.4 taking a very slight lead (<1%) .

What would you recommend as settings for poclbm? I do remember it being better back in the day too, but haven't played much with 2.1 lately. Also, keeping memory speeds low is a must  Tongue

Phatk was specifically written for SDK 2.4+, so compiling it with anything lower than that is a performance loss, since it has specific tweaks for the SDK 2.4+ compilers.

I don't recommend anything for poclbm, since I don't use it. I have two 5850's on two different machines (free power Tongue), both running at stock voltage, one at 970/150 (~400MH/s) and the other at 980/150 (~404MH/s), using phatk V2 W256 I9.

Both are on Win7 x64, Catalyst 12.1 drivers and SDK runtime 2.5.793.1 (comes on the 11.11 drivers).
member
Activity: 121
Merit: 10
On a side note, on series 5xxx and 6xxx, using poclbm with any sdk above 2.1 is a performance loss, as is using phatk with anything below 2.4.

Really? Using 960/300 clocks on a 5870, -g 1 -I 8 (p2pool), tried with and without -w 256 -v 2, I get much worse performance on poclbm + 2.1 compared to phatk + 2.1.

Phatk + 2.1 and phatk + 2.4 is about the same though, with 2.4 taking a very slight lead (<1%) .

What would you recommend as settings for poclbm? I do remember it being better back in the day too, but haven't played much with 2.1 lately. Also, keeping memory speeds low is a must  Tongue

legendary
Activity: 3586
Merit: 1099
Think for yourself
OK, I pretty sure this is ancient history, but here goes anyway.

I've been using Windoze XP with Catalyst 11.6 with a 5830 and 5770 and had low CPU utilization with that combination.  I went back to my Win7 install where I was using 10.9 to get low CPU utilization prior to CGMiner 2.0.  I updated this Win7 to Catalyst 11.6 and now have 100% CPU utilization.  I had thought Catalyst 11.6 had low CPU utilization across all platforms?

Any thoughts?  Or is this just the way it works with Windoze 7?

IIRC was a lot later than 11.6 before 100% bug was solved in Windows.  Why not use 11.11?

Why not use 12.1? As long as you don't install the SDK runtime that comes with it, it's working 100% with my 5850's.

What SDK are you using with it?

I guess I'll have to give that a try.  I'm still perplexed why the 11.6, the last know good version, doesn't work on Win7, or is just my Win7 installation?
Thanks,
Sam

sam: install 11.9 if your using win7 with 5xxx series cards - it does not get better than that and believe me I have done the testing



Well, I'll run it up the flagpole and see what happens.
Thanks,
Sam
hero member
Activity: 896
Merit: 1000
Buy this account on March-2019. New Owner here!!
OK, I pretty sure this is ancient history, but here goes anyway.

I've been using Windoze XP with Catalyst 11.6 with a 5830 and 5770 and had low CPU utilization with that combination.  I went back to my Win7 install where I was using 10.9 to get low CPU utilization prior to CGMiner 2.0.  I updated this Win7 to Catalyst 11.6 and now have 100% CPU utilization.  I had thought Catalyst 11.6 had low CPU utilization across all platforms?

Any thoughts?  Or is this just the way it works with Windoze 7?

IIRC was a lot later than 11.6 before 100% bug was solved in Windows.  Why not use 11.11?

Why not use 12.1? As long as you don't install the SDK runtime that comes with it, it's working 100% with my 5850's.

What SDK are you using with it?

I guess I'll have to give that a try.  I'm still perplexed why the 11.6, the last know good version, doesn't work on Win7, or is just my Win7 installation?
Thanks,
Sam

sam: install 11.9 if your using win7 with 5xxx series cards - it does not get better than that and believe me I have done the testing

Vbs
hero member
Activity: 504
Merit: 500
OK, I pretty sure this is ancient history, but here goes anyway.

I've been using Windoze XP with Catalyst 11.6 with a 5830 and 5770 and had low CPU utilization with that combination.  I went back to my Win7 install where I was using 10.9 to get low CPU utilization prior to CGMiner 2.0.  I updated this Win7 to Catalyst 11.6 and now have 100% CPU utilization.  I had thought Catalyst 11.6 had low CPU utilization across all platforms?

Any thoughts?  Or is this just the way it works with Windoze 7?

IIRC was a lot later than 11.6 before 100% bug was solved in Windows.  Why not use 11.11?

Why not use 12.1? As long as you don't install the SDK runtime that comes with it, it's working 100% with my 5850's.

What SDK are you using with it?

I guess I'll have to give that a try.  I'm still perplexed why the 11.6, the last know good version, doesn't work on Win7, or is just my Win7 installation?
Thanks,
Sam

I'm using the SDK runtime 2.5.793.1 that comes with the 11.11 drivers (it's the newest version of 2.5 sdk available), since I'm using the phatk kernel. If I wanted to use the poclbm kernel, I would use SDK 2.1.

I did a quick test sometime ago, and the phatk GPU ISA code generated with SDK 2.4.650.9 was the same as with SDK 2.5.793.1, so they "should" have identical performance, at least for the phatk kernel.


What SDK are you using with it?


Generally speaking.

2.1 is best for 5000 series cards.
2.4 or 2.5 is best for 6000 series cards.
2.6 is best for 7000 series cards.

That being said the difference between 2.1 and 2.4/2.5 is minimal.

2.6 is a huge performance hit w/ low memclocks I mean 20%+ so avoid it like the plague unless you have a 7000 series card.

Really no reason to use 2.2 or 2.3 for anything.

Damn you! Cool You're increasing my itch of comparing the low-level code of poclbm + 2.1 vs phatk + 2.5... Grin

On a side note, on series 5xxx and 6xxx, using poclbm with any sdk above 2.1 is a performance loss, as is using phatk with anything below 2.4.
donator
Activity: 1218
Merit: 1080
Gerald Davis

What SDK are you using with it?


Generally speaking.

2.1 is best for 5000 series cards.
2.4 or 2.5 is best for 6000 series cards.
2.6 is best for 7000 series cards.

That being said the difference between 2.1 and 2.4/2.5 is minimal.

2.6 is a huge performance hit w/ low memclocks I mean 20%+ so avoid it like the plague unless you have a 7000 series card.

Really no reason to use 2.2 or 2.3 for anything.
legendary
Activity: 3586
Merit: 1099
Think for yourself
I don't remember which version it was fixed in.

>11.6 and <=11.11  Smiley

I know it is fixed in 11.11.  As pointed out above you can even use 12.1 just make sure to install Runtime/SDK FIRST and then do CUSTOM SETUP and the uncheck OpenCL Runtime.  Once installed 2.6 is a pain to get rid of.  That is why I suggested 11.11.  It is a version I know has no 100% CPU bug and it doesn't have 2.6 so no chance of accidentally installing it.

Sounds like my best shot.  I'll give a whirl over the weekend.
Thanks again,
Sam
legendary
Activity: 3586
Merit: 1099
Think for yourself
OK, I pretty sure this is ancient history, but here goes anyway.

I've been using Windoze XP with Catalyst 11.6 with a 5830 and 5770 and had low CPU utilization with that combination.  I went back to my Win7 install where I was using 10.9 to get low CPU utilization prior to CGMiner 2.0.  I updated this Win7 to Catalyst 11.6 and now have 100% CPU utilization.  I had thought Catalyst 11.6 had low CPU utilization across all platforms?

Any thoughts?  Or is this just the way it works with Windoze 7?

IIRC was a lot later than 11.6 before 100% bug was solved in Windows.  Why not use 11.11?

Why not use 12.1? As long as you don't install the SDK runtime that comes with it, it's working 100% with my 5850's.

What SDK are you using with it?

I guess I'll have to give that a try.  I'm still perplexed why the 11.6, the last know good version, doesn't work on Win7, or is just my Win7 installation?
Thanks,
Sam
Jump to: