Anyone having problems with SDK 2.4/2.5 and CGMiner 1.5.1 on Windows? With SDK 2.1 I fire up fine, but if I try 2.4 it crashes immediately on launch.
On one of my boxes it works perfectly. On another I get the 0 byte whatever error.
So, sort of.
Topic: OFFICIAL CGMINER mining software thread for linux/win/osx/mips/arm/r-pi 4.11.0 - page 815. (Read 5805740 times)
August 02, 2011, 08:49:11 AM
On one of my boxes it works perfectly. On another I get the 0 byte whatever error.
So, sort of.
August 02, 2011, 08:43:28 AM
Yes, I'm persistent.
I've found that with a -g 1 it does not happen anymore (it's been running for half a hour now), but I loose a couple Mh/s.
spiccioli.
ps. I had to install curl since it's not installed in linuxcoin by default.
I've found that with a -g 1 it does not happen anymore (it's been running for half a hour now), but I loose a couple Mh/s.
spiccioli.
ps. I had to install curl since it's not installed in linuxcoin by default.
BTW, cgminer found 128 as optimal worksize, but using -w 256 gives me 3-5Mh/s more juice, steady
So now I'm forcing it to -w 256 ( and -g 1 -I 8 -w 256 -Q 2 ).
It is running at 361 on my 880/270 5850 and 444 on my 980/280 5870
spiccioli.
MH rate gets irrelevant at the point where shares/minute come to play, I can get +10MH with -I 14 but -2 shares/minute, 128 or 256 doesn't make a difference in terms of shares/per minute, got one rig with 3 5850s and one with 1 plus a 6950... after a couple of hours the 3x does ~1080MHs/s ~15 shares/min @"-w 256" and the other with "-w 128" does 729MHs/s ~10 shares both with "-I 8". It might do a difference in the hashrate but the shares/minute seem to be stable at the same rate after a couple of hours.
cards compared directly are about the same "U" but different hashrates...
1+1!=3
August 02, 2011, 08:42:55 AM
Anyone having problems with SDK 2.4/2.5 and CGMiner 1.5.1 on Windows? With SDK 2.1 I fire up fine, but if I try 2.4 it crashes immediately on launch.
Windows version is on hold while we await the developer who is working on it to show up.
August 02, 2011, 08:35:34 AM
Anyone having problems with SDK 2.4/2.5 and CGMiner 1.5.1 on Windows? With SDK 2.1 I fire up fine, but if I try 2.4 it crashes immediately on launch.
August 02, 2011, 08:18:50 AM
Yes, I'm persistent.
I've found that with a -g 1 it does not happen anymore (it's been running for half a hour now), but I loose a couple Mh/s.
spiccioli.
ps. I had to install curl since it's not installed in linuxcoin by default.
Do you have linuxcoin final? Everything should just work with it.
[/quote]
No, I'm sticking with v0.2b, since it's working ok for me and I don't need all the network boot stuff.
spiccioli.
August 02, 2011, 08:15:34 AM
Yes, I'm persistent.
I've found that with a -g 1 it does not happen anymore (it's been running for half a hour now), but I loose a couple Mh/s.
spiccioli.
ps. I had to install curl since it's not installed in linuxcoin by default.
I've found that with a -g 1 it does not happen anymore (it's been running for half a hour now), but I loose a couple Mh/s.
spiccioli.
ps. I had to install curl since it's not installed in linuxcoin by default.
BTW, cgminer found 128 as optimal worksize, but using -w 256 gives me 3-5Mh/s more juice, steady
So now I'm forcing it to -w 256 ( and -g 1 -I 8 -w 256 -Q 2 ).
It is running at 361 on my 880/270 5850 and 444 on my 980/280 5870
spiccioli.
August 02, 2011, 08:11:39 AM
Hi ckolivas,
today I decided to give your miner a try, it has so many features that I could not resist anymore
Sadly, after a couple of minutes both GPUs in my rig ( a 5850 and a 5870 on a linuxcoin v0.2b system) are declared SICK and then DEAD.
This is without any fancy parameters, just -o -u -p and -I 8 (it is a dedicated rig) and -Q 2 to have a little more buffer (so I thought).
Is there some other parameter I can try?
spiccioli
ps. my rig is running since june with phoenix and poclmb without problems, so I don't think this is due to hardware/OS issues.
today I decided to give your miner a try, it has so many features that I could not resist anymore
Sadly, after a couple of minutes both GPUs in my rig ( a 5850 and a 5870 on a linuxcoin v0.2b system) are declared SICK and then DEAD.
This is without any fancy parameters, just -o -u -p and -I 8 (it is a dedicated rig) and -Q 2 to have a little more buffer (so I thought).
Is there some other parameter I can try?
spiccioli
ps. my rig is running since june with phoenix and poclmb without problems, so I don't think this is due to hardware/OS issues.
ckolivas is on a two week vacation.
Are you running persistent? I had the same problem before I starting running in persistent mode with a r/w file.
Yes, I'm persistent.
I've found that with a -g 1 it does not happen anymore (it's been running for half a hour now), but I loose a couple Mh/s.
spiccioli.
ps. I had to install curl since it's not installed in linuxcoin by default.
Do you have linuxcoin final? Everything should just work with it.
August 02, 2011, 08:04:23 AM
Hi ckolivas,
today I decided to give your miner a try, it has so many features that I could not resist anymore
Sadly, after a couple of minutes both GPUs in my rig ( a 5850 and a 5870 on a linuxcoin v0.2b system) are declared SICK and then DEAD.
This is without any fancy parameters, just -o -u -p and -I 8 (it is a dedicated rig) and -Q 2 to have a little more buffer (so I thought).
Is there some other parameter I can try?
spiccioli
ps. my rig is running since june with phoenix and poclmb without problems, so I don't think this is due to hardware/OS issues.
today I decided to give your miner a try, it has so many features that I could not resist anymore
Sadly, after a couple of minutes both GPUs in my rig ( a 5850 and a 5870 on a linuxcoin v0.2b system) are declared SICK and then DEAD.
This is without any fancy parameters, just -o -u -p and -I 8 (it is a dedicated rig) and -Q 2 to have a little more buffer (so I thought).
Is there some other parameter I can try?
spiccioli
ps. my rig is running since june with phoenix and poclmb without problems, so I don't think this is due to hardware/OS issues.
ckolivas is on a two week vacation.
Are you running persistent? I had the same problem before I starting running in persistent mode with a r/w file.
Yes, I'm persistent.
I've found that with a -g 1 it does not happen anymore (it's been running for half a hour now), but I loose a couple Mh/s.
spiccioli.
ps. I had to install curl since it's not installed in linuxcoin by default.
August 02, 2011, 07:51:34 AM
Yeah, I installed it (and therefore got rid of the missing openCl.dll-error).
Now I get this:
Now I get this:
Quote
C:\cgminer>cgminer
[2011-08-02 14:51:15] Error: Getting Device IDs (num)
clDevicesNum returned error
[2011-08-02 14:51:15] Error: Getting Device IDs (num)
clDevicesNum returned error
August 02, 2011, 07:49:31 AM
I don't want to talk about the reasons why I cpu-mine. It leads to nothing but arguments.
All I want to know is how to get cgminer to work without an openCl-device.
I'm being a bit of an eco freak there All I want to know is how to get cgminer to work without an openCl-device.
, you can do what ever you want... but ck wont do anything to cpu support if not paid for so I guess the calculation is important even if your cpu does 25MH/s!Without opencl it should just say that there is no opencl and still compile without oCL support, have you tried with opencl (sdk, etc) installed to your system? (even if you do not use it...)
August 02, 2011, 07:47:03 AM
Hi ckolivas,
today I decided to give your miner a try, it has so many features that I could not resist anymore
Sadly, after a couple of minutes both GPUs in my rig ( a 5850 and a 5870 on a linuxcoin v0.2b system) are declared SICK and then DEAD.
This is without any fancy parameters, just -o -u -p and -I 8 (it is a dedicated rig) and -Q 2 to have a little more buffer (so I thought).
Is there some other parameter I can try?
spiccioli
ps. my rig is running since june with phoenix and poclmb without problems, so I don't think this is due to hardware/OS issues.
today I decided to give your miner a try, it has so many features that I could not resist anymore
Sadly, after a couple of minutes both GPUs in my rig ( a 5850 and a 5870 on a linuxcoin v0.2b system) are declared SICK and then DEAD.
This is without any fancy parameters, just -o -u -p and -I 8 (it is a dedicated rig) and -Q 2 to have a little more buffer (so I thought).
Is there some other parameter I can try?
spiccioli
ps. my rig is running since june with phoenix and poclmb without problems, so I don't think this is due to hardware/OS issues.
ckolivas is on a two week vacation.
Are you running persistent? I had the same problem before I starting running in persistent mode with a r/w file.
August 02, 2011, 07:38:59 AM
Hi ckolivas,
today I decided to give your miner a try, it has so many features that I could not resist anymore
Sadly, after a couple of minutes both GPUs in my rig ( a 5850 and a 5870 on a linuxcoin v0.2b system) are declared SICK and then DEAD.
This is without any fancy parameters, just -o -u -p and -I 8 (it is a dedicated rig) and -Q 2 to have a little more buffer (so I thought).
Is there some other parameter I can try?
spiccioli
ps. my rig is running since june with phoenix and poclmb without problems, so I don't think this is due to hardware/OS issues.
today I decided to give your miner a try, it has so many features that I could not resist anymore
Sadly, after a couple of minutes both GPUs in my rig ( a 5850 and a 5870 on a linuxcoin v0.2b system) are declared SICK and then DEAD.
This is without any fancy parameters, just -o -u -p and -I 8 (it is a dedicated rig) and -Q 2 to have a little more buffer (so I thought).
Is there some other parameter I can try?
spiccioli
ps. my rig is running since june with phoenix and poclmb without problems, so I don't think this is due to hardware/OS issues.
August 02, 2011, 07:22:37 AM
I don't want to talk about the reasons why I cpu-mine. It leads to nothing but arguments.
All I want to know is how to get cgminer to work without an openCl-device.
All I want to know is how to get cgminer to work without an openCl-device.
August 02, 2011, 07:17:20 AM
Can I skip that step somehow so it just mines with the CPU?
nothing personal Ali, it was just your post to let me become mad!
This thread is filled with CPU miners complaining about stuff, I do not get why you people still care that much about CPU mining?! My CPUs get 3MH/s each even my crappy 2 year old nvidia graphics does 28MH/s using less power... want it? 5 btc + shipping! If it is a game, pay for it before you play with it, you know ck's BTC address! You won't ever return any amount of investment with CPU mining. Let me do the math for you, ~2 valid shares/hour per core, 2 BTC sent to ck for fixing up some cpu related stuff in cgminer == 4.6 CPU-Years without increase in difficulty to pay the 2 BTC at current difficulty... think of the environment, you waste +95W for 2 BTC a year (reference is Athlon II X4 in this case and difficulty is not raised)...
Buy a $200 gpu and have it payed in 3-5 month including your powerbills... or buy the 2 BTC for $20
well fo number of reasons
because my
1. cpu make 20Mh/s
2. cpu is already in rig and doing nothing (load 1%)
3. in 5 years will cost 1BTC many thousands $ so even making almost nothing or loosing - will be profit in future if you keep it
4. because this is only decent cpu miner
5. On my rig is GPU mining 20% more effective with combination Phoenix + Smartcoin
it has more Mhash/s and failover with more options. Cgminer is running for CPU only under Smartcoin, so I don't care about Cgminer GPU hashing at all.
August 02, 2011, 06:13:17 AM
Looks like the 1.5.3 configure script inadvertently dropped support for alternate cURL library path support via --with-libcurl:
Yes, because it's the crappy way to do it. The right way is to export a variable to specify the PKG_CONFIG_PATH to the correct *.pc file. See my RPMs for reference...
Seems to be a way that works on more systems and with local built binaries is the right way to do it. Dependance on a packaging system is the crappy way to do it.
August 02, 2011, 06:06:12 AM
Can I skip that step somehow so it just mines with the CPU?
nothing personal Ali, it was just your post to let me become mad!
This thread is filled with CPU miners complaining about stuff, I do not get why you people still care that much about CPU mining?! My CPUs get 3MH/s each even my crappy 2 year old nvidia graphics does 28MH/s using less power... want it? 5 btc + shipping! If it is a game, pay for it before you play with it, you know ck's BTC address! You won't ever return any amount of investment with CPU mining. Let me do the math for you, ~2 valid shares/hour per core, 2 BTC sent to ck for fixing up some cpu related stuff in cgminer == 4.6 CPU-Years without increase in difficulty to pay the 2 BTC at current difficulty... think of the environment, you waste +95W for 2 BTC a year (reference is Athlon II X4 in this case and difficulty is not raised)...
Buy a $200 gpu and have it payed in 3-5 month including your powerbills... or buy the 2 BTC for $20
August 02, 2011, 05:16:15 AM
I tried cgminer on a couple of my boxes last night and woke up to find 3/4 GPU marked as DEAD on one and 2/4 DEAD on another. Trying to restart the DEAD GPU doesnt seem to do anything on either machine (restarting the ones still running did seem to restart them OK). Both boxes have been running for weeks using poclbm without errors. Running the 1.5.3 binary on Ubuntu (3xHD5870 and HD6310).
Anyone else seeing problems with DEAD GPU that won't recover unless cgminer is restarted?
BB.
Anyone else seeing problems with DEAD GPU that won't recover unless cgminer is restarted?
BB.
I do too, but only on my linux boxes.
Actually, I have switched to persistent mode of Linuxcoin, and this does not seem to be happening anymore. Are you just running off of a USB stick? Perhaps persistent mode will fix you as well.
August 02, 2011, 04:01:17 AM
Is it possible to use a proxy-server with cgminer?
I can't find any option about it in the first post.
I can't find any option about it in the first post.
I think I told you that you don't need any options for that, just export the http_proxy variable before starting cgminer.
Sorry, I forgot about this.
I'm trying to run it ONLY for CPU-mining. Had to install AMD's Stream SDK.
When I start with this options:
Quote
I get this error:
Quote
[2011-08-02 10:57:54] Error: Getting Device IDs (num)
clDevicesNum returned error
clDevicesNum returned error
Can I skip that step somehow so it just mines with the CPU?
August 02, 2011, 03:47:41 AM
Is it possible to use a proxy-server with cgminer?
I can't find any option about it in the first post.
I can't find any option about it in the first post.
I think I told you that you don't need any options for that, just export the http_proxy variable before starting cgminer.
August 02, 2011, 03:46:27 AM
I have a couple of improvement requests if I may
1) I've been purposefully feeding cgminer some getworks that will never be accepted for my pool testing purposes and noticed a pattern - even if the first share it sends back in a getwork is rejected, it still carries on processing that getwork anyway, sometimes leading to a second (and maybe even third or more?) reject out of the same work unit. I think cgminer should abandon a work unit if a share in it is rejected, as subsequent submissions are very likely to be rejected as well.
2) it would be nice to be able to PageUp and PageDown the log in the lower part of the display
3) optional millisecond timestamp display would be useful - maybe a --developer mode or something for people who want exact precision?
1) I've been purposefully feeding cgminer some getworks that will never be accepted for my pool testing purposes and noticed a pattern - even if the first share it sends back in a getwork is rejected, it still carries on processing that getwork anyway, sometimes leading to a second (and maybe even third or more?) reject out of the same work unit. I think cgminer should abandon a work unit if a share in it is rejected, as subsequent submissions are very likely to be rejected as well.
2) it would be nice to be able to PageUp and PageDown the log in the lower part of the display
3) optional millisecond timestamp display would be useful - maybe a --developer mode or something for people who want exact precision?
Jump to: