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

Thanks for doing that search for me, I don't think I'd have ever thought to search for that particular string.
I'd downloading the GPU compuing SDK and the CUDA toolkit. They're massive downloads, about a gig between the 2.
It seems odd to me that we'd need development tools to run miners, but I guess I'll add that to the list of things I don't understand about mining! lol

That applies to mining ...

Again, I have no idea about nVidia and CUDA but I even typed your google search for you and found this page:
http://developer.nvidia.com/cuda-downloads

No idea if you need something else to mine, but no doubt the fact that your NON-ATI miner doesn't work at all probably means you are missing something to make it work ... and at a wild guess it may be that? (I don't know)

Windows. Manual build just before release usually 

Hi Con,

in be8ad579 you fixed some missing includes in the modularized logging module. Was this required for Windows or OS/X builds?

I'm asking because I always perform full builds of all potential configuration combinations on my Linux system before I commit and never saw a problem with that missing include. Do you have some automated build scripts to check commits for regressions and QA? I'd like to ensure that my future modifications do not break anything before I issue a pull request.

Thanks,
Zefir

I don't know anything about Nvidia GPU or Cuda, so I couldn't say.
Sam

In the meantime, while I'm still on the GTX480, do I need to be concerned with anything SDK-related?

I have never upgraded SDK, always used original 2.4 from LinuxCoin final, but still have problem with every newly compiled cgminer (those compiled one month ago still works fine)

That was probably going to be one of the next "suggestions" someone was going to make.  When you get the AMD GPU CGMiner is definitely what you will want to use.


I like using the AMD Catalyst 11.6 which includes the OpenCL SDK 2.4.  That seems to work pretty good for me.  But if you get one of the newer GPU's you may need to get a newer Catalyst version.  Post that question again when you get said GPU and someone will, I'm sure, have a more informed suggestion for you.

Good Luck,
Sam

Hi guys, thanks for staying on this for me.

@Kano:I promise I DID use the -D and -T args. I can make a video if that will help.
I'm updating my GPU drivers to the latest Beta right now, so see if that has any effect.

@Sam: I'm not interested in trying another miner, since I plan to get a good AMD card, and have heard great things about cgminer.
I'll try the new drivers and report back.

I see a bunch of stuff about SDKs flaoting around. Do I need to do anything with that or does that only apply to Linux/AMD/whatever?

"Short of a loud message repeatedly saying "you are running sdk 2.6 SDK which sucks dicks"

Could implement that as a popup.

Seriously I understand your frustration was just trying to think of ways to make it more "idiot" proof.

Reminds me of this quote (which I am sure you have heard):

- Rich Cook

Still the point I was (possibly badly) trying to make is -n & -d -t simply shows the system as configured however w/ cached bin files it doesn't necessarily reflect the "execution plan" (to borrow some SQL Server terminology).

How often should this flashing warning be said? 

If for whatever reason you need to run sdk2.6, it sucks lesser dicks on cgminer 2.2.5.

I think your assumption is correct, I recall upgrading drivers/SDK/something about a month ago.
So what you are saying is I should downgrade the drivers / SDK and upgrade CGminer?

ckolivas: You could try including "you are running sdk 2.6 SDK which sucks dicks" as a flashing warning in the actual program :-)

Containing "metadata like SDK" is just as useful as asking for the output of -n which tells you the same thing. It won't stop people from asking and it won't make them read the readme which has lots about hashrate dropping... but then it's TOO WELL DOCUMENTED now since there's so much in the readme... Short of a loud message repeatedly saying "you are running sdk 2.6 SDK which sucks dicks" I don't think anyone is gonna get the message =(

Likely has nothing to do w/ cgminer and everything to do w/ updated drivers / SDK.

To Conman:
I really think including the SDK in the product title is a good idea.

This scenario keeps happening over and over.

a) person is running one version of cgminer and one version of SDK (say 2.1)
b) they upgrade drivers but cgminer caches the bin files (SDK 2.1) so they see no change in performance.  "wow 12.1 w/ SDK 2.6 works great on my 5970".
c) some time later person upgrades cgminer = no bin files
d) on first run bin files are created (SDK 2.6) and performance is lower.  wow cgminer 2.2.x really sucks.
e) to confirm they try running older version of cgminer (w/ cached SDK 2.1 bin) and performance is good again.

It really complicates troubleshooting as I am sure you are aware.

Would it be possible to modify bin files so they contain "metadata like SDK version at time of compilation"?

Then it might be more obvious to users.

cgminer 2.1.2 (w/ SDK 2.1 binaries) = 715 MH/s.
cgminer 2.1.2 (w/ SDK 2.6 binaries) = 600 MH/s.
cgminer 2.2.5 (w/ SDK 2.6 binaries) = 600 MH/s.

Pretty obvious there where the problem lies.

I tried upgrading from 2.0.8 to 2.2.5 but my 5s average dropped from 715 Mh/s to 600 Mh/s.

Dual 5850, one at 850, the other at 900 Mhz, memory at 300 Mhz on both. Windows 7, intensity 9.

export DISPLAY=:0
before running, and try latest  cgminer only please

This is what I experienced during the weekend:

I received a 5970 and replaced one of my 5870 with it, after graphic card change, the previous LinuxCoin installation cannot start correctly

So, I took another USB stick, installed freshly a new LinuxCoin on it, boot it into LinuxCoin, run phoenix miner, and all 5 GPU gave decent hash rates stable for 6 hours

Then, I downloaded cgminer 2.2.4, updated and installed other dependency packages, then compiled and started it, after 1 minute, it claimed 2 of 5 GPUs dead and rest of GPUs' hash rate dropped 20%

I downloaded cgminer 2.1.2 (which worked flawlessly on the original USB stick), compiled and started (after removing the .bin file from home directory), same problem

Then, I rebooted the machine, fall back to my original phoenix miner method, surprisingly found out that even phoenix only worked on one of the GPU and hang on rest of them

There is one thing I remember: Last time when I tried to compile cgminer 2.1.2, I tried to install libcurl4-openssl-dev and  libncurses5-dev but one of them just can not be found, so eventually I installed something else to bypass the dependency check. But this time, it went all smooth. I think one or both of the packages have changed since one month ago and caused these new issues

Finally I have to switch back to the previous working HW/SW configuration, hoping that I could just fix the xorg.conf to get new graphic card recognized

It's a disaster, don't waste your time. It just happened to build with certain versions of all the necessary packages when I got it working at one time in the past approximately 6 months ago, and if you get the latest versions of all the packages, it won't build. One day we'll slowly shake out that mess, but given windows users are not used to compiling their own software, it has priority zero at the moment.

Hehe ;-) I actually read over that in the README... I'll see whether I can get it build as well ;-)

Actually - it's in the README
(well that's what I used to do it)
Someone else is trying to make a detailed one at the moment that may or may not work well.
Stay tuned ... for a few more weeks maybe?