Topic: OFFICIAL CGMINER mining software thread for linux/win/osx/mips/arm/r-pi 4.11.0 - page 390. (Read 5806015 times)
March 23, 2013, 05:00:57 PM
Something is weird with the 2.11.3 kernel. I can't use it very well with my 7950s, I get the same hash rates as with reaper but with about 5% invalids. Not sure why this is. Try rolling back to one of the older scrypt######.cl files and seeing if that fixes it.
March 23, 2013, 09:09:26 AM
Has intensity for LTC been fixed yet in 7xxx cards? I much prefer cgminer over reaper, but I cant use it with my 7950 right now.
I'm not sure what problem you're referring to, but for me, cgminer works at least as well as reaper for LTC mining.
With a GIGABYTE GV-R785OC-2GD clocked at 1150/1000, intensity 19, thread concurrency 27164, 1 gpu thread, I get pretty much the same hashrate with cgminer and reaper (~390kH/s).
I also played around with another configuration at intensity 13, thread concurrency 13632, and 2 gpu threads. With this, I get ~360kH/s in cgminer, and a hard crash requiring a reboot with reaper. With cgminer at this intensity, I *am* able to use the desktop for other purposes.
Interestingly, reaper in the first configuration uses ~1.7GB of system memory. cgminer in both configs uses ~40K...!
With my hardware, I don't see any reason to ever use reaper. YMMV with different hardware, of course.
Ya, I'm an idiot. I found a guide showing how to set it up correctly, and now it is doing AWESOME. Getting 670kh/s at -I 20
EDIT:
Ok, now I am having issues when trying to tweak my 6950. If I delete my bins and then even use the same .bat files I was using, it runs SLOW, but if I restore my old bin from the recycle bin (Win 7 64bit), and again use the same .bat, speeds are how they used to be. Tried with 2.7.5 and with the newest version, but same results. Anyone have any idea why this is happening? Because of this issue, I can only use 2.7.5 with my 6950, and I would like to start using the newest version.
March 23, 2013, 04:53:58 AM
?
sudo aticonfig --initial -f --adapter=all
Yes, I had done that prior to the results I showed. I was following the procedure from the Unofficial Wiki for the AMD Linux Driver. I used the commands to create fglrx .deb packages from the AMD Catalyst 11.12 download and install the packages, plus aticonfig etc.sudo aticonfig --initial -f --adapter=all
...
March 23, 2013, 04:34:27 AM
?
sudo aticonfig --initial -f --adapter=all
Yes, I had done that prior to the results I showed. I was following the procedure from the Unofficial Wiki for the AMD Linux Driver. I used the commands to create fglrx .deb packages from the AMD Catalyst 11.12 download and install the packages, plus aticonfig etc.sudo aticonfig --initial -f --adapter=all
Quote
and of course the usual (which I put in here a few days ago)
To see that your display is correct:
export DISPLAY=:0
xlsfonts
That returns a long list of fonts.To see that your display is correct:
export DISPLAY=:0
xlsfonts
EDIT: However...
Code:
proofer@prooferminer:~/miners/cgminer$ DISPLAY=:0 fglrxinfo
X Error of failed request: BadRequest (invalid request code or no such operation)
Major opcode of failed request: 153 (GLX)
Minor opcode of failed request: 19 (X_GLXQueryServerString)
Serial number of failed request: 12
Current serial number in output stream: 12
March 23, 2013, 01:43:14 AM
?
sudo aticonfig --initial -f --adapter=all
and of course the usual (which I put in here a few days ago)
To see that your display is correct:
export DISPLAY=:0
xlsfonts
sudo aticonfig --initial -f --adapter=all
and of course the usual (which I put in here a few days ago)
To see that your display is correct:
export DISPLAY=:0
xlsfonts
March 22, 2013, 10:45:42 PM
I was mining OK with Ubuntu 11.04 and Catalyst 11.06. After upgrading to Ubuntu 12.04 and Catalyst 11.12, I built the current cgminer from source, which has been my usual practice. Two problems:
1. The system is not detecting my display monitor's characteristics and is using a generic "laptop" monitor config with the wrong resolution. This is not a big problem, but I'm mentioning it here in case it's a clue.
2. cgminer 2.11.3 is not seeing my three 5970 GPUs:
I'm stumped.
1. The system is not detecting my display monitor's characteristics and is using a generic "laptop" monitor config with the wrong resolution. This is not a big problem, but I'm mentioning it here in case it's a clue.
2. cgminer 2.11.3 is not seeing my three 5970 GPUs:
Code:
proofer@prooferminer:~/miners/cgminer$ aticonfig --lsa
* 0. 13:00.0 ATI Radeon HD 5900 Series
1. 12:00.0 ATI Radeon HD 5900 Series
2. 0b:00.0 ATI Radeon HD 5900 Series
3. 0a:00.0 ATI Radeon HD 5900 Series
4. 07:00.0 ATI Radeon HD 5900 Series
5. 06:00.0 ATI Radeon HD 5900 Series
* - Default adapter
proofer@prooferminer:~/miners/cgminer$ xhost + &> /dev/null
proofer@prooferminer:~/miners/cgminer$ DISPLAY=:0 cgminer -n
[2013-03-22 20:29:53] CL Platform 0 vendor: Advanced Micro Devices, Inc.
[2013-03-22 20:29:53] CL Platform 0 name: AMD Accelerated Parallel Processing
[2013-03-22 20:29:53] CL Platform 0 version: OpenCL 1.1 AMD-APP (831.4)
[2013-03-22 20:29:53] Error -1: Getting Device IDs (num)
[2013-03-22 20:29:53] clDevicesNum returned error, no GPUs usable
[2013-03-22 20:29:53] 0 GPU devices max detected
I'm stumped.
March 22, 2013, 10:23:02 PM
Since 10.5 CGMiner crashes on launch and all the versions following that. 10.4 works fine. Using Windows 7 64bit. Any ideas on what to look for?
March 22, 2013, 05:31:58 PM
I use Catalyst 11.12 and SDK 2.5 on Ubuntu 12.04 (phatk kernel). It took me a long time to figure out how to install both of them properly. Unless you're using 7000 series cards, I'd recommend this combo.
I just upgraded from 11.04 to 12.04 and am in the throes of trying to figure out what you figured out. After about 24 hours of messing around I'm just about to re-install 12.04 to get a clean slate. Do any memories/hints/notes come to mind? March 22, 2013, 11:26:13 AM
Has intensity for LTC been fixed yet in 7xxx cards? I much prefer cgminer over reaper, but I cant use it with my 7950 right now.
I'm not sure what problem you're referring to, but for me, cgminer works at least as well as reaper for LTC mining.
With a GIGABYTE GV-R785OC-2GD clocked at 1150/1000, intensity 19, thread concurrency 27164, 1 gpu thread, I get pretty much the same hashrate with cgminer and reaper (~390kH/s).
I also played around with another configuration at intensity 13, thread concurrency 13632, and 2 gpu threads. With this, I get ~360kH/s in cgminer, and a hard crash requiring a reboot with reaper. With cgminer at this intensity, I *am* able to use the desktop for other purposes.
Interestingly, reaper in the first configuration uses ~1.7GB of system memory. cgminer in both configs uses ~40K...!
With my hardware, I don't see any reason to ever use reaper. YMMV with different hardware, of course.
March 22, 2013, 09:51:37 AM
Has intensity for LTC been fixed yet in 7xxx cards? I much prefer cgminer over reaper, but I cant use it with my 7950 right now.
March 21, 2013, 08:28:17 PM
cgminer is using about 25% cpu when mining bitcoin.. Uses 0% cpu when mining litecoin..
Is this normal?
I hope you're not using the same Intensity for both BTC and LTC. Your -I for BTC should only be like -7. Is this normal?
March 21, 2013, 01:08:18 PM
cgminer is using about 25% cpu when mining bitcoin.. Uses 0% cpu when mining litecoin..
Is this normal?
Is this normal?
Nope!, I assume you have a quad core CPU? Check to see if you have the "100% cpu bug" by setting CGminer to just one core, If the one core is loaded up beyond 97%, Then you have the bug.
It might be nothing more than an SDK/Driver bug that is fixed with the newer drivers
March 21, 2013, 12:37:09 PM
cgminer is using about 25% cpu when mining bitcoin.. Uses 0% cpu when mining litecoin..
Is this normal?
Is this normal?
March 21, 2013, 06:01:50 AM
what happened with 2.11.3 log format, why is not reporting hashrate anymore ?
March 20, 2013, 07:41:46 PM
For some reason cgminer is "consuming" all available ports when run with '--fix-protocol' and p2pool on local machine. Not sure if one of distro updates is causing this or misconfiguration somewhere. Tried cgminer versions all the way back to 2.7.4 and Python 2.7 and 2.6.
Anyone got idea what could be the cause? Below is part of very long list of netstat -tnp
Anyone got idea what could be the cause? Below is part of very long list of netstat -tnp
Code:
tcp 0 0 127.0.0.1:9332 127.0.0.1:39383 ESTABLISHED 25198/python2.7
tcp 0 0 127.0.0.1:9332 127.0.0.1:39355 ESTABLISHED 25198/python2.7
tcp 0 0 127.0.0.1:39417 127.0.0.1:9332 ESTABLISHED 29338/cgminer
tcp 0 0 127.0.0.1:39135 127.0.0.1:9332 ESTABLISHED 29338/cgminer
tcp 0 0 127.0.0.1:39183 127.0.0.1:9332 ESTABLISHED 29338/cgminer
tcp 0 0 127.0.0.1:39338 127.0.0.1:9332 ESTABLISHED 29338/cgminer
tcp 0 0 127.0.0.1:39729 127.0.0.1:9332 ESTABLISHED 29338/cgminer
tcp 0 0 127.0.0.1:9332 127.0.0.1:39739 ESTABLISHED 25198/python2.7
tcp 0 0 127.0.0.1:9332 127.0.0.1:39492 ESTABLISHED 25198/python2.7
tcp 0 0 127.0.0.1:39639 127.0.0.1:9332 ESTABLISHED 29338/cgminer
March 20, 2013, 11:52:44 AM
Does anyone else get about 5% invalids using the new cgminer and high thread concurrencies? Gonna switch my 7950s back to reaper for now until I figure this out.
March 20, 2013, 03:57:46 AM
I'm guessing you're talking about windows. Windows does random things with the logging output it seems. Gotta love its (arse)soul.
Seems like a dotNet issue, since Python on windows handles it fine.
I'm saying the problem with Nemo's dotNet-based front-end is a dotNet issue, since a GUIMiner, a similar Python/Win32 front-end does not have the same problem.
Then this is inconsistent. I am only observing this issue with CGMiner and cpuminer (from which CGMiner was forked). Poclbm, rpcminer, as well as some other command-line tools, which I ran for test purposes from my front-end (like ping.exe -t) are handled just fine, with output showing just when it is expected.
March 19, 2013, 07:21:15 PM
I'm guessing you're talking about windows. Windows does random things with the logging output it seems. Gotta love its (arse)soul.
Seems like a dotNet issue, since Python on windows handles it fine.
I'm saying the problem with Nemo's dotNet-based front-end is a dotNet issue, since a GUIMiner, a similar Python/Win32 front-end does not have the same problem.
March 19, 2013, 07:15:39 PM
I'm guessing you're talking about windows. Windows does random things with the logging output it seems. Gotta love its (arse)soul.
Seems like a dotNet issue, since Python on windows handles it fine.
March 19, 2013, 06:59:38 PM
I'm guessing you're talking about windows. Windows does random things with the logging output it seems. Gotta love its (arse)soul.
Seems like a dotNet issue, since Python on windows handles it fine.
Jump to: