Sorry that I have to ask what is likely a dumb question... I've been searching for an answer for no luck.
How do I remove or prevent the default config file from being loaded? At some point I saved a config file using the default settings.
I since saved a config file as "cgminer3.conf", made changes that I want and now run cgminer with the command "screen ./cgminer -c cgminer3.conf"
Using this it loads my pools twice - I assume because it is loading the default file as well. If I run cgminer without the -c option it loads old gpu speeds, etc so it's pulling from somewhere.
The problem is I can't find a default .conf file anywhere to delete/remove. There are no .conf files (except my cgminer3.conf) in the cgminer directory or home directory.
Thanks in advance.
Topic: OFFICIAL CGMINER mining software thread for linux/win/osx/mips/arm/r-pi 4.11.0 - page 619. (Read 5805874 times)
March 13, 2012, 05:59:31 PM
March 13, 2012, 07:40:41 AM
I've started to get ztex boards supported on cgminer. The current implementation uses libusb-1.0, compiles cleanly on linux (ubuntu, but all others should be fine) and osx (snow leopard here). I'll try to make it work for windows soon; https://github.com/nelisky/cgminer/tree/ztex
This is not feature complete, not all that tested so be careful. I have been mining with it for a while and the biggest caveat is that the hash rate measurement is completely broken. It seems cgminer doesn't like when I do a full nonce scan that can take 12~15 secs and only report the calc'd nonces at the end of that. Limiting the nonce space does make it report correctly and of course the actual speed is the ~200MHs expected from the board regardless of what cgminer reports
But what I'd really like to put in, and I'm not sure if this will be well supported in cgminer, is hotplug support. Will I be able to dynamically add / remove workers? Should I use a main worker thread and then spawn child threads, one per board? I would also like to use multiple boards per thread and just split the nonce space, as there is enough time between polls to handle that.
Opinions? Pointers? All well appreciated
This is not feature complete, not all that tested so be careful. I have been mining with it for a while and the biggest caveat is that the hash rate measurement is completely broken. It seems cgminer doesn't like when I do a full nonce scan that can take 12~15 secs and only report the calc'd nonces at the end of that. Limiting the nonce space does make it report correctly and of course the actual speed is the ~200MHs expected from the board regardless of what cgminer reports
But what I'd really like to put in, and I'm not sure if this will be well supported in cgminer, is hotplug support. Will I be able to dynamically add / remove workers? Should I use a main worker thread and then spawn child threads, one per board? I would also like to use multiple boards per thread and just split the nonce space, as there is enough time between polls to handle that.
Opinions? Pointers? All well appreciated
March 12, 2012, 03:00:44 PM
thanks for your work on this tool. it is just what i was looking for as i've developed in the bitcoin arena. having total control in one app is great.
my experience did get off to a bad start though and was about to give up. the system i decided to try it on first would not work. i tried the compiled windows version, then tried to compile myself - oh that was fun.
i just could not get it to initialize the GPU so i moved it over to another system and bam worked right off. it turns out that my first attempt was on a pc that i was messing with the Intel OpenCL SDK earlier. i removed that SDK then CGMINER worked. this may not be news or unexpected but figured i would share in case someone else is in the same boat.
thanks again ckolivas, and all contributing members. now off to research centralized monitoring........
my experience did get off to a bad start though and was about to give up. the system i decided to try it on first would not work. i tried the compiled windows version, then tried to compile myself - oh that was fun.
i just could not get it to initialize the GPU so i moved it over to another system and bam worked right off. it turns out that my first attempt was on a pc that i was messing with the Intel OpenCL SDK earlier. i removed that SDK then CGMINER worked. this may not be news or unexpected but figured i would share in case someone else is in the same boat.
thanks again ckolivas, and all contributing members. now off to research centralized monitoring........
March 12, 2012, 05:18:36 AM
The 'current' SDK determines what is in any new *.bin files you generate.
When you switch back to an old version of cgminer you are using the old *.bin generated with an old SDK unless you delete them.
I think kano is right. At least it was the reason preventing me from updating from version 2.1.2 since phatk opencl code has changed and cgminer had to recompile (or whatever it does with .bin files) it.When you switch back to an old version of cgminer you are using the old *.bin generated with an old SDK unless you delete them.
I had trouble deleting APP SDK runtimes. Somehow it stayed in the system after uninstall.
Here's what you need to do:
1) Uninstall either APP SDK runtimes or whole Catalyst suite through AMD uninstall utility.
2) Search for amdocl.dll and OpenCL.dll in Windows directory and delete them
3) In case you uninstalled whole suite, reinstall it with custom install and uncheck APP SDK runtimes
4) Download and install needed OpenCL driver. Older version avalable for direct download here:
http://support.amd.com/us/gpudownload/windows/previous/Pages/radeonaiw_vista64.aspx
http://support.amd.com/us/gpudownload/windows/previous/Pages/radeonaiw_vista32.aspx
http://support.amd.com/us/gpudownload/windows/previous/Pages/radeonaiw_xp.aspx
For newer versions - download suite, install and select only AMD APP runtimes. You can backup OpenCL.msi from AMD/ATI temp directory on C: for future use.
You can choose driver version according to needed SDK version:
http://developer.amd.com/sdks/AMDAPPSDK/downloads/pages/AMDAPPSDKDownloadArchive.aspx
March 12, 2012, 02:53:10 AM
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!
https://bitcointalksearch.org/topic/graphs-memory-clock-performance-kernels-68357
March 12, 2012, 01:58:30 AM
For anyone who has set this up is it just:
"api-allow" : "W:172.0.0.1, W:192.168.0.100",
assuming you want host 192.168.0.100 and local access to modify the settings through the API.
"api-allow" : "W:172.0.0.1, W:192.168.0.100",
assuming you want host 192.168.0.100 and local access to modify the settings through the API.
March 12, 2012, 01:13:26 AM
...
You answered it good enough. I can just use the older version. I would probably lose more then I would gain messing with my rig drivers.
Actually, the most likely cause is the fact that you have already messed with them.You answered it good enough. I can just use the older version. I would probably lose more then I would gain messing with my rig drivers.
(whether you realise it or not)
If it's windows then any ATI dirver update will have messed it up if it changed the SDK (and other changes can also)
If it's linux and you did an upgrade ... same thing.
The 'current' SDK determines what is in any new *.bin files you generate.
When you switch back to an old version of cgminer you are using the old *.bin generated with an old SDK unless you delete them.
March 11, 2012, 11:03:31 PM
...
You answered it good enough. I can just use the older version. I would probably lose more then I would gain messing with my rig drivers.
Actually, the most likely cause is the fact that you have already messed with them.You answered it good enough. I can just use the older version. I would probably lose more then I would gain messing with my rig drivers.
(whether you realise it or not)
March 11, 2012, 04:54:19 PM
...
You answered it good enough. I can just use the older version. I would probably lose more then I would gain messing with my rig drivers.
Actually, the most likely cause is the fact that you have already messed with them.You answered it good enough. I can just use the older version. I would probably lose more then I would gain messing with my rig drivers.
(whether you realise it or not)
March 11, 2012, 03:52:47 PM
My hash rate is about 10% lower with the newest cgminer. I should be able to use the same config file right?
I am not trying to be mean here, but do you really think anyone can answer that question when you posted so little information?
What driver version are you on?
What AMD-APP Runtime/SDK are you on?
What is the output of "cgminer -n"?
What Video cards are you using?
Did you upgrade your video driver or AMD-APP Runtime/SDK recently?
...?
Yes, you should be able to use the same config file.
March 11, 2012, 09:39:52 AM
My hash rate is about 10% lower with the newest cgminer. I should be able to use the same config file right?
I am not trying to be mean here, but do you really think anyone can answer that question when you posted so little information?
What driver version are you on?
What AMD-APP Runtime/SDK are you on?
What is the output of "cgminer -n"?
What Video cards are you using?
Did you upgrade your video driver or AMD-APP Runtime/SDK recently?
...?
Yes, you should be able to use the same config file.
March 11, 2012, 12:53:10 AM
My hash rate is about 10% lower with the newest cgminer. I should be able to use the same config file right?
March 11, 2012, 12:38:32 AM
March 10, 2012, 09:44:22 PM
Edit - RESOLVED
I had to add "export DISPLAY=:0" to the start script and now fans/temp are detected at startup.
I had to add "export DISPLAY=:0" to the start script and now fans/temp are detected at startup.
Quote
Regarding auto-start.... when i run this command from terminal after gui boots, everything works fine:
I tried putting it in an executable file to run at boot from CRON, and everything works except switches for auto-fan, clocks etc... just default clocks but mining successfully.
I get the same result if run the script from rc.local....
But again, if I run it from CLI after it has booted, auto-fan/clocks etc work great
root@mcp:~# uname -a
Linux mcp 2.6.32-5-686 #1 SMP Mon Jan 16 16:04:25 UTC 2012 i686 GNU/Linux
Any ideas?
Code:
#!/bin/sh
sleep 60
export GPU_USE_SYNC_OBJECTS=1;cd /opt/miners/cgminer;/usr/bin/screen -d -m -S cgminer /opt/miners/cgminer/cgminer --api-listen -o http://x.x.com -u x -p y -I 10 --gpu-engine 1200,1000,1000 --gpu-memclock 1200 --auto-fan --temp-target 70
I tried putting it in an executable file to run at boot from CRON, and everything works except switches for auto-fan, clocks etc... just default clocks but mining successfully.
I get the same result if run the script from rc.local....
But again, if I run it from CLI after it has booted, auto-fan/clocks etc work great
root@mcp:~# uname -a
Linux mcp 2.6.32-5-686 #1 SMP Mon Jan 16 16:04:25 UTC 2012 i686 GNU/Linux
Any ideas?
March 10, 2012, 05:07:38 PM
Hi everybody! it might be stupid, but what am i doing wrong?
I have PC with i5-2500k CPU, Gigabyte p67a-d3-b3 mobo. I have my old GTX480 for gaming and 7970 for mining. GTX at upper PCI-E x16 slot and 7970 at bottom. No monitor, just TV via HDMI-out at my NVidia card. Win7 x64. NVidia is default display.
All works great on diablominer.
DiabloMiner-Windows.exe -u login -p pass -o pool -r 8332 -D 2
no lags, NVidia does it's job for entertainment, ATI's mining bitcoins.
When i start cgminer with
cgminer.exe -u login -p pass -o pool:8332 -D 0
Mining starts at GTX480
cgminer.exe -u login -p pass -o pool:8332 -D 1
it says "Command line options set a device that doesn't exist"
cgminer.exe -u login -p pass -o pool:8332 -D 2
same "Command line options set a device that doesn't exist"
What am I doing wrong?
I have PC with i5-2500k CPU, Gigabyte p67a-d3-b3 mobo. I have my old GTX480 for gaming and 7970 for mining. GTX at upper PCI-E x16 slot and 7970 at bottom. No monitor, just TV via HDMI-out at my NVidia card. Win7 x64. NVidia is default display.
All works great on diablominer.
DiabloMiner-Windows.exe -u login -p pass -o pool -r 8332 -D 2
no lags, NVidia does it's job for entertainment, ATI's mining bitcoins.
When i start cgminer with
cgminer.exe -u login -p pass -o pool:8332 -D 0
Mining starts at GTX480
cgminer.exe -u login -p pass -o pool:8332 -D 1
it says "Command line options set a device that doesn't exist"
cgminer.exe -u login -p pass -o pool:8332 -D 2
same "Command line options set a device that doesn't exist"
What am I doing wrong?
Type "cgminer -n"
Look at the output and remember the number for the 7970.
Add "--gpu-platform #" (where # = the number of the platform you want to use) to your command line.
Here is my output of "cgminer -n". I use 1 as the platform.
D:\cgminer-2.3.1-2.Self.Compiled>cgminer -n
[2012-03-10 14:05:18] CL Platform 0 vendor: NVIDIA Corporation
[2012-03-10 14:05:18] CL Platform 0 name: NVIDIA CUDA
[2012-03-10 14:05:18] CL Platform 0 version: OpenCL 1.1 CUDA 4.1.1
[2012-03-10 14:05:18] Platform 0 devices: 1
[2012-03-10 14:05:18] CL Platform 1 vendor: Advanced Micro Devices, Inc.
[2012-03-10 14:05:18] CL Platform 1 name: AMD Accelerated Parallel Processing
[2012-03-10 14:05:18] CL Platform 1 version: OpenCL 1.1 AMD-APP-SDK-v2.5 (793.1)
[2012-03-10 14:05:18] Platform 1 devices: 1
[2012-03-10 14:05:18] Failed to ADL_Adapter_ID_Get. Error -1
[2012-03-10 14:05:18] Failed to ADL_Adapter_ID_Get. Error -1
[2012-03-10 14:05:18] GPU 0 ATI Radeon HD 5800 Series hardware monitoring enable
d
[2012-03-10 14:05:18] 1 GPU devices max detected
March 10, 2012, 03:35:56 PM
Hi everybody! it might be stupid, but what am i doing wrong?
I have PC with i5-2500k CPU, Gigabyte p67a-d3-b3 mobo. I have my old GTX480 for gaming and 7970 for mining. GTX at upper PCI-E x16 slot and 7970 at bottom. No monitor, just TV via HDMI-out at my NVidia card. Win7 x64. NVidia is default display.
All works great on diablominer.
DiabloMiner-Windows.exe -u login -p pass -o pool -r 8332 -D 2
no lags, NVidia does it's job for entertainment, ATI's mining bitcoins.
When i start cgminer with
cgminer.exe -u login -p pass -o pool:8332 -D 0
Mining starts at GTX480
cgminer.exe -u login -p pass -o pool:8332 -D 1
it says "Command line options set a device that doesn't exist"
cgminer.exe -u login -p pass -o pool:8332 -D 2
same "Command line options set a device that doesn't exist"
What am I doing wrong?
I have PC with i5-2500k CPU, Gigabyte p67a-d3-b3 mobo. I have my old GTX480 for gaming and 7970 for mining. GTX at upper PCI-E x16 slot and 7970 at bottom. No monitor, just TV via HDMI-out at my NVidia card. Win7 x64. NVidia is default display.
All works great on diablominer.
DiabloMiner-Windows.exe -u login -p pass -o pool -r 8332 -D 2
no lags, NVidia does it's job for entertainment, ATI's mining bitcoins.
When i start cgminer with
cgminer.exe -u login -p pass -o pool:8332 -D 0
Mining starts at GTX480
cgminer.exe -u login -p pass -o pool:8332 -D 1
it says "Command line options set a device that doesn't exist"
cgminer.exe -u login -p pass -o pool:8332 -D 2
same "Command line options set a device that doesn't exist"
What am I doing wrong?
March 10, 2012, 02:28:54 PM
ckvolias:using latest cgminer 2.3.1-2 win7 64x
after awhile I loose temps and fan speed displays both on screen and from API - a cgminer reboot fixes the issue
Windows driver ATI Display Library fsckage. I can't do anything about it. Does restarting cgminer fix it or rebooting the machine fix it? I could probably try working around the former by detecting "losing adl support" and re-initialising it.after awhile I loose temps and fan speed displays both on screen and from API - a cgminer reboot fixes the issue
Restarting cgminer always fixes it, no need to restart the whole box.
March 10, 2012, 02:47:21 AM
Dropping in once a week and answering all unanswered questions is much better for my sanity than what I was doing before 
March 10, 2012, 02:18:18 AM
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
I just ran it up the flag pole. Catalyst 11.9 which has SDK 2.5 still has the 100% CPU utilization bug, which was what I kind of thought. I'll do some benchmarking to compare with what I was getting with the 11.6 and 100% CPU Utilization.
Sam
March 10, 2012, 02:13:31 AM
Not sure if this has been covered in previous posts, but MAN, 227 pages of posts to read, and searches don't turn up anything, so what the hey.
Just went from 2.2.6 to 2.3.1 and went from mid 500s on each 7970 and dropped to... 25.
At first I assumed it was to do with the new GPU interval setting it was annoying me about, but after wasting an hour playing with that to no avail I started looking for other causes. The first thing I noticed was it seemed to be taking 99% of each GPU to turn up 25 Mhash/sec. I tried phatk and went to 150 per GPU. POCLBM came in first with 552 at 12 intensity (I don't want the fans offensively loud).
So, not sure what's changed. I have not tried other kernels in the past so I can't tell if phatk has always sucked or, like Diablo, has just started sucking.
Anyway, I hope this helps anyone else with a 7970 confused by a sudden performance hit after an update!
outsidefactor
Yes the diablo kernel and 79x0 only works with the latest sdk included in driver 12.2 onwards. The earlier 2.6 sdk completely and utterly does an AMD on the kernel and produces massive fail instead of good performance. If you did not specify a kernel, by default cgminer detects what sdk you are on and should be giving you my custom poclbm kernel instead for sdk 2.6, which is what you concurred gives the best performance for a 7970 Just went from 2.2.6 to 2.3.1 and went from mid 500s on each 7970 and dropped to... 25.
At first I assumed it was to do with the new GPU interval setting it was annoying me about, but after wasting an hour playing with that to no avail I started looking for other causes. The first thing I noticed was it seemed to be taking 99% of each GPU to turn up 25 Mhash/sec. I tried phatk and went to 150 per GPU. POCLBM came in first with 552 at 12 intensity (I don't want the fans offensively loud).
So, not sure what's changed. I have not tried other kernels in the past so I can't tell if phatk has always sucked or, like Diablo, has just started sucking.
Anyway, I hope this helps anyone else with a 7970 confused by a sudden performance hit after an update!
outsidefactor
Jump to: