OFFICIAL CGMINER mining software thread for linux/win/osx/mips/arm/r-pi 4.11.1

[jake262144]

Alternatively you could install upgrade but (in windows) select custom install and UNCHECK SDK.  Not sure if 12.2 has any notable changes compared to 12.1 but if it does that is way to get "improved" ( with AMD deproved) and keep existing SDK installation.

<amd bashing>
Definitely deproved  

Feeling sorry for Con? Think of the pain AMD people must be going through with those damned faildrivers...
Nothing strange that the CTO of AMD's graphics products group abandoned ship.


</amd bashing>

[1715588980]

1715588980

[blandead]

If you're trying to use vectors then there is a type mis-match either stick with putting a (u) in front or use (uint4) and the (0, 1, 2, 3) should be on the outside parenthesis.

Here is a float4 example...

float4 f = (float4)(1.0f, 2.0f, 3.0f, 4.0f);

Also in the _kernal void search if you keep (_global uint * output) then you're not really utilizing vectors correctly

And, sorry was just trying to provide some general feedback with Out of Order Execution, wasn't trying to offend you, I'm just not sure how to edit cgminer directly.

Thanks.

Are you saying the existing code is losing shares with __global uint * output? 99% of users on cgminer are currently using 2 vectors. Again I doubt that's the case.

It's not losing shares, just takes much longer to deal with them. Any found shares are being stored/loaded to a one component variable, I'm working on a kernel replacing it with (_global uint4 * output) and I can directly work with nonce.xyzw, which is a true 4 vector variable, I am just having trouble figuring out how to pass the found nonces after it's stored. May have to use some kind of loop or "unroll"

Oh yea, glad to see you got GOFFSET to work, btw do you have MAD optimization enabled in your program? There can be a nice speed boost if you do.

[-ck]

I'm trying to get together a collection of binaries for different hardware from different SDKs. If anyone has binaries for the different SDKs, please check http://ck.kolivas.org/apps/cgminer/bins/ to see if they exist and if not, can you send me a copy?

[kano]

Big post
I guess I'll ask ckolivas about putting this into cgminer as a separate file:

AMD-SDK upgrade/downgrade in Linux
==================================
Firstly to install the 2.4 SDK is just as I have said in my linux
USB install script.

My script has exactly the same effect as the cgminer README except
that I copy all the files into the target directories rather than
linking to any of them
(this is mandatory on USB persistent storage coz casper doesn't
keep /opt)

Anyway from the current linux USB script it is:
-----------------------------------------------------------
12) get AMD-APP-SDK-v2.4-lnx64.tgz from
 http://developer.amd.com/sdks/amdappsdk/downloads/pages/default.aspx
  ( http://developer.amd.com/Downloads/AMD-APP-SDK-v2.4-lnx64.tgz )

 sudo su
 cd /opt
  (replace /home/ubuntu/ with wherever you put the file: )
 tar -xvzf /home/ubuntu/AMD-APP-SDK-v2.4-lnx64.tgz

 cd AMD-APP-SDK-v2.4-lnx64/
 cp -pv lib/x86_64/* /usr/lib/
 rsync -avl include/CL/ /usr/include/CL/
 tar -xvzf icd-registration.tgz
 rsync -avl etc/OpenCL/ /etc/OpenCL/
 ldconfig
 sync
 shutdown -r now
-----------------------------------------------------------

I believe SDK 2.5 is exactly the same but replace "2.4" with "2.5"
everywhere - anyone who knows otherwise please tell me.
Also if anyone does know if it is exactly the same please tell
me and I can remove these comments
However, I'm certain it really is exactly the same but have never
touched 2.5

Now 2.4 SDK doesn't touch the drivers that fglrx+++ installs

However, the 2.6 SDK does

So before installing the 2.6 SDK it is best to rename the 2 files
that it overwrites in case you need to go back.
It saves from having to repair the fglrx installs
(which I'd guess is a simple command in apt but I'm not an apt guru)
but it is also so easy to do that it's best just to manually do it.

The two library files are of course in /usr/lib/
   libaticalcl.so  libaticalrt.so

IF YOU ARE ALREADY USING FGLRX DRIVER 12.1 OR NEWER:
then you don't want to overwrite libaticalrt.so and libaticalcl.so
So you DON'T want to do 2 steps listed below marked (*A*) and (*B*)

(*A*) If your fglrx is before 12.0:
-----------------------------------------------------------
 cd /usr/lib/
 sudo mv -v libaticalrt.so libaticalcl.so.old
 sudo mv -v libaticalcl.so libaticalcl.so.old
-----------------------------------------------------------

It is mandatory to remove the 2.4 SDK first if you installed it using
ckolivas' README since the first link causes issues - see the bottom of
this for the details of how to remove the 2.4 SDK if you used  ckolivas'
README to install it

Next install 2.6 manually so you know exactly what is changed.
Also this means you won't overwrite the fglrx drivers if you
don't want to.

Remember don't do the step below (*B*) if you already have
fglrx 12.1 or newer

To install 2.6 it's:
-----------------------------------------------------------
get AMD-APP-SDK-v2.6-lnx64.tgz from
 http://developer.amd.com/sdks/amdappsdk/downloads/pages/default.aspx
  ( http://developer.amd.com/Downloads/AMD-APP-SDK-v2.6-lnx64.tgz )

 sudo su
 cd /opt
 mkdir SDK2.6
 cd SKD2.6/
  (replace /home/ubuntu/ with wherever you put the file: )
 tar -xvf /home/ubuntu/AMD-APP-SDK-v2.6-lnx64.tgz

 tar -xvf AMD-APP-SDK-v2.6-RC3-lnx64.tgz

 cd AMD-APP-SDK-v2.6-RC3-lnx64/
 cp -pv lib/x86_64/* /usr/lib/
 cp -pv lib/*.so /usr/lib/                 <- (*B*)

 rsync -avl include/CL/ /usr/include/CL/

 cd ..
 tar -xvzf icd-registration.tgz
 rsync -avl etc/OpenCL/ /etc/OpenCL/

 ldconfig
 sync
 shutdown -r now
-----------------------------------------------------------

Now the last part - how to get back to 2.4 from 2.6.

It's not much different except you need to put back the
two old library files if you installed the 2 new ones

IF YOU DIDN'T DO STEPS (*A*) AND (*B*) ABOVE:
then of course you don't need to undo them.
i.e. you don't need to do the 3 steps below marked (*C*)

You of course don't need to repeat the download if you already
have the file.
And you don't need to repeat the 'tar' commands if everything
is still in /opt

To downgrade the 2.6 SDK back to the 2.4 SDK:
-----------------------------------------------------------
12) get AMD-APP-SDK-v2.4-lnx64.tgz from
 http://developer.amd.com/sdks/amdappsdk/downloads/pages/default.aspx
  ( http://developer.amd.com/Downloads/AMD-APP-SDK-v2.4-lnx64.tgz )

 sudo su

(First cleanup the old 2.6 SDK non-fglrx files)
 rm -rvf /usr/include/CL/
 rm -rvf /etc/OpenCL/
 cd /usr/lib/
 rm -v libamdocl64.so libGLEW.so libglut.so libOpenCL.so libOpenCL.so.1 libSlotMaximizerAg.so libSlotMaximizerBe.so

 cd /opt
  (replace /home/ubuntu/ with wherever you put the file: )
 tar -xvf /home/ubuntu/AMD-APP-SDK-v2.4-lnx64.tgz

 cd AMD-APP-SDK-v2.4-lnx64/
 cp -pv lib/x86_64/* /usr/lib/
 rsync -avl include/CL/ /usr/include/CL/
 tar -xvf icd-registration.tgz
 rsync -avl etc/OpenCL/ /etc/OpenCL/

 cd /usr/lib/                                      <- (*C*)
 mv -v libaticalrt.so.old libaticalcl.so           <- (*C*)
 mv -v libaticalcl.so.old libaticalcl.so           <- (*C*)

 ldconfig
 sync
 shutdown -r now
-----------------------------------------------------------

Edit: added the 2.6 cleanup just in case in the future is causes some problem

Edit2: someone asked how to remove 2.4 ...
If you installed it the way I said to install it then:
-----------------------------------------------------------
sudo su
 rm -rvf /usr/include/CL/
 rm -rvf /etc/OpenCL/
 cd /usr/lib/
 rm -v libamdocl64.so libGLEW.so libglut.so libOpenCL.so libOpenCL.so.1
-----------------------------------------------------------

Edit3: how to remove 2.4 if you used ckolivas' README to install it
This will be necessary if you want to upgrade from 2.4 to 2.6 the way I documented
(due to the 1st link):
-----------------------------------------------------------
sudo su
 rm -vf /usr/include/CL
 rm -rvf /etc/OpenCL/
 cd /usr/lib/
 rm -v libamdocl64.so libGLEW.so libglut.so libOpenCL.so libOpenCL.so.1
-----------------------------------------------------------
(just the first 'rm' is different coz it's a link not a directory)

[-ck]

I'm trying to get together a collection of binaries for different hardware from different SDKs. If anyone has binaries for the different SDKs, please check http://ck.kolivas.org/apps/cgminer/bins/ to see if they exist and if not, can you send me a copy?

Thanks everyone who promptly sent me their binaries! I now have a collection in the cgminer directory that people can download if they're having issues with their SDKs.

How do people feel about me providing "optimal bins" included as a separate "full package" with cgminer?

I figure 2.4/2.5 bins for vliw4 (R6xxx), 2.1 bins for vliw5 (R5xxx) and 2.6 bins for GCN (R7xxx).

[The00Dustin]

How do people feel about me providing "optimal bins" included as a separate "full package" with cgminer?

I figure 2.4/2.5 bins for vliw4 (R6xxx), 2.1 bins for vliw5 (R5xxx) and 2.6 bins for GCN (R7xxx).

If you do this and cgminer automatically uses the best one, you might get lonely when newbs stop posting about how the latest update slowed them down...

[-ck]

How do people feel about me providing "optimal bins" included as a separate "full package" with cgminer?

I figure 2.4/2.5 bins for vliw4 (R6xxx), 2.1 bins for vliw5 (R5xxx) and 2.6 bins for GCN (R7xxx).

If you do this and cgminer automatically uses the best one, you might get lonely when newbs stop posting about how the latest update slowed them down...

LOL that's my kind of ronery.

[jjiimm_64]

I'm trying to get together a collection of binaries for different hardware from different SDKs. If anyone has binaries for the different SDKs, please check http://ck.kolivas.org/apps/cgminer/bins/ to see if they exist and if not, can you send me a copy?

Thanks everyone who promptly sent me their binaries! I now have a collection in the cgminer directory that people can download if they're having issues with their SDKs.

How do people feel about me providing "optimal bins" included as a separate "full package" with cgminer?

I figure 2.4/2.5 bins for vliw4 (R6xxx), 2.1 bins for vliw5 (R5xxx) and 2.6 bins for GCN (R7xxx).

this would be good, especially with a flag  "use-bins" : true,   

[-ck]

cgminer sets clocks all back to default on exit... if it exits cleanly, and of course on windows it's a miracle when it does.

Sadly this is not the case.

windows machine, pair of 6950's, set to 850/1300 for normal operation, in cgminer they are set to 700-880/300... when cgminer exits it leaves the cards at 880/300.

even updated to 12.1 drivers, both 2.4 and 2.6 SDK.

Is it exiting or crashing?

I run cgminer from a .bat file in windows, and when I hit the "Q" button, it gives me the 2-page summary of stats, then sits for about 3 seconds and then closes the dos window. I'm not getting any complaints from windows about it crashing/hanging/etc.

ckolivas: I know you have the impossible task of trying to make an app play nice with windows. I'm HAPPY to run any sort of debug load/options you might have to give better/more-detailed information.

It should not be closing the dos window... there's still something going wrong.
Try the experimental binary
http://ck.kolivas.org/apps/cgminer/temp/cgminer.exe
This one tries to reset GPU settings before trying to shut down so that even if it crashes/hangs on exit, your GPUs should go to default values.

[os2sam]

What does long4 vs. long8 mean in the .bin filename?
Sam

[-ck]

What does long4 vs. long8 mean in the .bin filename?
Sam

Notably there are Tahiti (7970) .bins for 32 bit (long4) and 64 bit (long8)

[-ck]

Okay I've just uploaded a windows exe that *might* have fixed the long term crash on shutdown problem.

Anyone want to try it please?

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

Put into a 2.2.6 directory.

[stevegee58]

Okay I've just uploaded a windows exe that *might* have fixed the long term crash on shutdown problem.

Anyone want to try it please?

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

Put into a 2.2.6 directory.

I started and stopped it like 10 times and it didn't crash.

Isn't supposed to restore the GPU settings though?  It still leaves the GPU at its mining settings (a minor inconvenience).

[-ck]

Okay I've just uploaded a windows exe that *might* have fixed the long term crash on shutdown problem.

Anyone want to try it please?

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

Put into a 2.2.6 directory.

I started and stopped it like 10 times and it didn't crash.

Isn't supposed to restore the GPU settings though?  It still leaves the GPU at its mining settings (a minor inconvenience).

Yes it is supposed to restore the GPU settings. Though that's only if you actually make it change any settings when you start it. It does not try to restore anything if it never adjusted any settings to begin with.

[-ck]

More AMD breakage coming up. As Diapolo hinted earlier, there is a new AMD driver 12.2 with an SDK that claims to be sdk 2.6 but  comes up with the version number 898.1. It breaks cgminer completely making it unable to build any binaries.  I have yet to investigate why but please do not upgrade unless you already have .bin files that work. I'm going to start a collection of bin files that people may be able to download and they'll be housed here:

Alternatively you could install upgrade but (in windows) select custom install and UNCHECK SDK.  Not sure if 12.2 has any notable changes compared to 12.1 but if it does that is way to get "improved" ( with AMD deproved) and keep existing SDK installation.

Yes, for now one should uncheck OpenCL Runtime during Catalyst upgrade until CGMINER is fixed.
My first look made me scream on another fact, they did heavy work on their OpenCL compiler, which tends to behave again very differently compared to former versions ... seems like more work in the future (it looks like they preffer vector GPRs over scalar GPRs with the new runtime as there are massive shifts in GPR usage).

Well I believe I've fixed this in my git tree, and I've uploaded an exe into that temp directory as always. If someone is brave enough to try the latest driver 12.2 with its sdk on 64 bit windows with this executable I'd be mighty grateful:

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

[stevegee58]

Okay I've just uploaded a windows exe that *might* have fixed the long term crash on shutdown problem.

Anyone want to try it please?

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

Put into a 2.2.6 directory.

I started and stopped it like 10 times and it didn't crash.

Isn't supposed to restore the GPU settings though?  It still leaves the GPU at its mining settings (a minor inconvenience).

Yes it is supposed to restore the GPU settings. Though that's only if you actually make it change any settings when you start it. It does not try to restore anything if it never adjusted any settings to begin with.

Yes, I do have it change the settings.  Here's my command line:

cgminer -o http://127.0.0.1:9332 -u xxx-p xxx--auto-gpu --gpu-engine 750-960 --gpu-memclock 250 --temp-target 80 --gpu-vddc 1.1 -g 1

[The00Dustin]

Yes, I do have it change the settings.  Here's my command line:

cgminer -o http://127.0.0.1:9332 -u xxx-p xxx--auto-gpu --gpu-engine 750-960 --gpu-memclock 250 --temp-target 80 --gpu-vddc 1.1 -g 1

But did you reboot or manually set them back after using the previous version that didn't set them back due to the crash?  CGMINER sets them back to where they were when it started, it doesn't know the defaults.

[-ck]

Yes, I do have it change the settings.  Here's my command line:

cgminer -o http://127.0.0.1:9332 -u xxx-p xxx--auto-gpu --gpu-engine 750-960 --gpu-memclock 250 --temp-target 80 --gpu-vddc 1.1 -g 1

But did you reboot or manually set them back after using the previous version that didn't set them back due to the crash?  CGMINER sets them back to where they were when it started, it doesn't know the defaults.

This is correct, it assumes you have set certain values for a reason before it starts up its code. It reads off your profile as cgminer is started, and then on exit it writes back the profile that was there before it started. The only thing it sets to "default" behaviour is the fan management.

[stevegee58]

Yes, I do have it change the settings.  Here's my command line:

cgminer -o http://127.0.0.1:9332 -u xxx-p xxx--auto-gpu --gpu-engine 750-960 --gpu-memclock 250 --temp-target 80 --gpu-vddc 1.1 -g 1

But did you reboot or manually set them back after using the previous version that didn't set them back due to the crash?  CGMINER sets them back to where they were when it started, it doesn't know the defaults.

I set them back to their mfg defaults using the Catalyst Control Center, then ran cgminer to see if it restored them (which it didn't).

[-ck]

Yes, I do have it change the settings.  Here's my command line:

cgminer -o http://127.0.0.1:9332 -u xxx-p xxx--auto-gpu --gpu-engine 750-960 --gpu-memclock 250 --temp-target 80 --gpu-vddc 1.1 -g 1

But did you reboot or manually set them back after using the previous version that didn't set them back due to the crash?  CGMINER sets them back to where they were when it started, it doesn't know the defaults.

I set them back to their mfg defaults using the Catalyst Control Center, then ran cgminer to see if it restored them (which it didn't).

Shafted.