I have been using phoenix for some time, but CGminer have the most powerful and beautiful interface I have ever seen, a master piece!
Really loved it and run it through screen in auto-start script, but sometimes that screen session just disappeared and I have to restart the machine to get it back to work, is it due to overclocking of the card or network problem? Anyone have same experience?
Topic: OFFICIAL CGMINER mining software thread for linux/win/osx/mips/arm/r-pi 4.11.0 - page 694. (Read 5805728 times)
January 23, 2012, 04:58:32 AM
January 23, 2012, 04:51:10 AM
Code:
cgminer version 2.1.2 - Started: [2012-01-16 18:14:21]
--------------------------------------------------------------------------------
(5s):1664.2 (avg):1656.5 Mh/s | Q:198847 A:200504 R:5649 HW:0 E:101% U:22.
TQ: 4 ST: 5 SS: 10 DW: 9250 NB: 938 LW: 75021 GF: 531 RF: 16
Connected towith LP as user
Block: 00000b6e89bb00a92d1f75b327f1573f... Started: [00:20:12]
--------------------------------------------------------------------------------
[P]ool management [G]PU management [S]ettings [D]isplay options [Q]uit
GPU 0: | 373.3/372.4Mh/s | A:44859 R:1137 HW:0 U: 4.98/m I: 8
GPU 1: | 373.9/372.3Mh/s | A:45492 R:1214 HW:0 U: 5.05/m I: 8
GPU 2: | 303.0/302.6Mh/s | A:36805 R:1074 HW:0 U: 4.08/m I: 8
GPU 3: | 304.6/304.2Mh/s | A:36709 R:1051 HW:0 U: 4.07/m I: 8
GPU 4: | 305.6/304.9Mh/s | A:36640 R:1173 HW:0 U: 4.06/m I: 8
--------------------------------------------------------------------------------
Hmmm...where did my temps and fan speeds go ?
Did you either compile a non-ADL binary or (if you use linux) run without export DISPLAY=:0
Would be good to know if anyone else has the same issue in the same OS
January 23, 2012, 04:29:33 AM
Sounds like you compiled without ADL support, no?
EDIT:: I just verified that the most recent git version compiles as expected. What Eveofwar posted is NOT a bug in cgminer itself.
EDIT:: I just verified that the most recent git version compiles as expected. What Eveofwar posted is NOT a bug in cgminer itself.
January 23, 2012, 03:29:34 AM
Code:
cgminer version 2.1.2 - Started: [2012-01-16 18:14:21]
--------------------------------------------------------------------------------
(5s):1664.2 (avg):1656.5 Mh/s | Q:198847 A:200504 R:5649 HW:0 E:101% U:22.
TQ: 4 ST: 5 SS: 10 DW: 9250 NB: 938 LW: 75021 GF: 531 RF: 16
Connected towith LP as user
Block: 00000b6e89bb00a92d1f75b327f1573f... Started: [00:20:12]
--------------------------------------------------------------------------------
[P]ool management [G]PU management [S]ettings [D]isplay options [Q]uit
GPU 0: | 373.3/372.4Mh/s | A:44859 R:1137 HW:0 U: 4.98/m I: 8
GPU 1: | 373.9/372.3Mh/s | A:45492 R:1214 HW:0 U: 5.05/m I: 8
GPU 2: | 303.0/302.6Mh/s | A:36805 R:1074 HW:0 U: 4.08/m I: 8
GPU 3: | 304.6/304.2Mh/s | A:36709 R:1051 HW:0 U: 4.07/m I: 8
GPU 4: | 305.6/304.9Mh/s | A:36640 R:1173 HW:0 U: 4.06/m I: 8
--------------------------------------------------------------------------------
Hmmm...where did my temps and fan speeds go ?
January 22, 2012, 04:56:59 PM
Why do people keep torturing themselves with windows? Just use plain old debian and save yourself tons of time and headaches.
Well much to your, and my, chagrin the computing world has decided to use M$ Windoze.
And those of use who support vertical market applications need to have multiple machines with the various versions of M$ OS's on them. So when I can, I mine on them, which is why I really like stand alone miners like CGMiner and Ufasoft. But when I need to do my job on them they are ready to go for work as well.
So diverting machines to dedicated use with some *nix variant doesn't work for me.
So I appreciate the effort of doing the Windoze builds as well.
Sam
January 22, 2012, 04:34:51 PM
Because on some cards you can not down clock the memory far enough on Linux (6970). On Windows my rigs that have 6970's, the mem can be down clocked to 300, on Linux they cannot!
If it's a dedicated mining rig, just flash the BIOS. Yeah, it's lame that the ATI driver in Linux wont let you change the memclock, but a quick BIOS flash completely takes care of the issue.
January 22, 2012, 03:15:41 PM
Why do people keep torturing themselves with windows? Just use plain old debian and save yourself tons of time and headaches.
Because on some cards you can not down clock the memory far enough on Linux (6970). On Windows my rigs that have 6970's, the mem can be down clocked to 300, on Linux they cannot!
When Cgminer finds an exploit in the AMD's driver that will allow for lower mem clock on all my rigs then they all will run Linux. MSI Afterburner on Windows uses an exploit and it works. The exploit I am talking about was left open in the windows driver for backward compatibility for one of ATI/AMD's OC utilities. There is no exploit/hole in the Linux driver. If you want everyone on Linux then start bugging AMD to allow for settings below and over bios limits for all their drivers.
This Linux is way better than Windows diatribe is getting really old. I use both Linux and Windows as do many people that use Cgminer. We also donate.
January 22, 2012, 02:47:16 PM
But yeah - state exactly what you want with those 2 commands and once the CPU changes happen I'll put those 2 on first priority (for 5 BTC
I would like to add V to the list. the more i read about undervolting, the more I want to try it. especially with summer approaching.
Also, since reconfiguring a bunch of rigs will be easy to do from this interface, would be nice to be able to write the config to a file.
Kano, I am willing to up the anti to get this stuff in.... 10btc? anyone else willing to contribute?
1. ability to switch pools (i think setting a pools priority to 0 would work?)
2. setting the following, for gpus's:
- "intensity" : "newValue",
- "gpu-engine" : "newValue",
- "gpu-vddc" : "newValue",
- "gpu-memclock" : "newValue",
- "gpu-fan": "newValue", ex(50-85)
I think Kano main objection to modification now is the code base will be changed significantly when cpu mining is removed. He would rather wait until cpu mining is complete, finalized, and then work off that version for more PRC enhancements.
Thanks DAT.
while making the webmonitor. I cannot report what the pool strategy is from the rpc request. can we add the pool strategy? here is a sample of a pool get that is currently in load balance mode.:
...
It will be part of cgminer 2.2.0 when it's ready or you can get it from the git directly as usual
I updated the API version to "1.0"
A few differences in names (see the README) ... also of course you need to specify the GPU number for GPU commands ... and one difference in functionality for gpufan: just a single value.
If you want 'fan' to also work like some of the cgminer options, then specify what you want using the cgminer option names
(I've made it like the screen interface but can change it of course)
While I also think the new "switchpool", "config", "gpuintensity" and "save" are useful, I will say, however, that changing the GPU/fan values doesn't really make a lot of sense.
If you have auto-fan and auto-gpu on, then changing them wont work very well (cgminer will change them back soon enough)
Also if you have an external program looking after them, same issue.
If you don't have auto-fan and auto-gpu on (or something checking them) then you better make sure your API program pays good attention to the settings and adjusts them well.
Kano,
Thank you very much. will be sending five btc's your way.
glanced at the readme. my only comment at this point is when switching pools, setting a pools priority to 0 will 'switch pools' only when the strategy is failover, yes? or is it possible to change the strategy?
JIm
January 22, 2012, 01:37:18 PM
Why do people keep torturing themselves with windows? Just use plain old debian and save yourself tons of time and headaches.
January 22, 2012, 01:27:26 PM
Yaaaaaaaaaaay! i blew a fan totally by my own fault of using cgminers "rapingly powerful fan control"
Time for me to not use that!, xD had my fan running at 100% for three days without knowing it xD Now it turns at 1/5th the RPM.
Lol, Never believed it before, BUT FANS ARE NOT MEANT TO RUN AT 100%!!!!
Time for me to not use that!, xD had my fan running at 100% for three days without knowing it xD Now it turns at 1/5th the RPM.
Lol, Never believed it before, BUT FANS ARE NOT MEANT TO RUN AT 100%!!!!
January 22, 2012, 04:04:06 AM
But yeah - state exactly what you want with those 2 commands and once the CPU changes happen I'll put those 2 on first priority (for 5 BTC
I would like to add V to the list. the more i read about undervolting, the more I want to try it. especially with summer approaching.
Also, since reconfiguring a bunch of rigs will be easy to do from this interface, would be nice to be able to write the config to a file.
Kano, I am willing to up the anti to get this stuff in.... 10btc? anyone else willing to contribute?
1. ability to switch pools (i think setting a pools priority to 0 would work?)
2. setting the following, for gpus's:
- "intensity" : "newValue",
- "gpu-engine" : "newValue",
- "gpu-vddc" : "newValue",
- "gpu-memclock" : "newValue",
- "gpu-fan": "newValue", ex(50-85)
I think Kano main objection to modification now is the code base will be changed significantly when cpu mining is removed. He would rather wait until cpu mining is complete, finalized, and then work off that version for more PRC enhancements.
Thanks DAT.
while making the webmonitor. I cannot report what the pool strategy is from the rpc request. can we add the pool strategy? here is a sample of a pool get that is currently in load balance mode.:
...
It will be part of cgminer 2.2.0 when it's ready or you can get it from the git directly as usual
I updated the API version to "1.0"
A few differences in names (see the README) ... also of course you need to specify the GPU number for GPU commands ... and one difference in functionality for gpufan: just a single value.
If you want 'fan' to also work like some of the cgminer options, then specify what you want using the cgminer option names
(I've made it like the screen interface but can change it of course)
While I also think the new "switchpool", "config", "gpuintensity" and "save" are useful, I will say, however, that changing the GPU/fan values doesn't really make a lot of sense.
If you have auto-fan and auto-gpu on, then changing them wont work very well (cgminer will change them back soon enough)
Also if you have an external program looking after them, same issue.
If you don't have auto-fan and auto-gpu on (or something checking them) then you better make sure your API program pays good attention to the settings and adjusts them well.
January 21, 2012, 08:49:15 PM
Having done this sort of drudgery in the past I appreciate what you went through to get it working in Windows. It shows true devotion to your project.
Not at all the response I was expecting, thanks! 
January 21, 2012, 08:44:51 PM
No doubt building on windows is nothing short of a pain. I can't even remember any more what I had to install manually but I'm pretty sure what's listed in the README covers all the essentials. Both binaries and dev libraries need to be installed and I had to manually shift some header files into the include directory to get everything recognised. I think installing pkg-config was the most troublesome, but even that I'm not sure of any more since I just kept randomly installing shit till the mother worked.
In short, windows is very much the 2nd class citizen for cgminer. The fact I can provide binaries for it at all is a miracle and I'd rather do without it myself.
In short, windows is very much the 2nd class citizen for cgminer. The fact I can provide binaries for it at all is a miracle and I'd rather do without it myself.
Having done this sort of drudgery in the past I appreciate what you went through to get it working in Windows. It shows true devotion to your project.
January 21, 2012, 07:33:59 PM
No doubt building on windows is nothing short of a pain. I can't even remember any more what I had to install manually but I'm pretty sure what's listed in the README covers all the essentials. Both binaries and dev libraries need to be installed and I had to manually shift some header files into the include directory to get everything recognised. I think installing pkg-config was the most troublesome, but even that I'm not sure of any more since I just kept randomly installing shit till the mother worked.
In short, windows is very much the 2nd class citizen for cgminer. The fact I can provide binaries for it at all is a miracle and I'd rather do without it myself.
In short, windows is very much the 2nd class citizen for cgminer. The fact I can provide binaries for it at all is a miracle and I'd rather do without it myself.
January 21, 2012, 06:24:39 PM
So when you build for Windows do you build under Linux or Windows?
In a windows virtual machine running XP.Do I have to add anything for the build to find the Windows Platform SDK?
January 21, 2012, 06:22:13 PM
Hashrate of all my cards (5830, 5870, 5970, 6870) and rigs are exacly 10% slower after version 2.0.8. So, is the hashrate really lower or hashrate calculation has been fixed?
Cgminer's hashrate is unchanged. You upgraded your drivers. It is sheer coincidence. See all the discussions about SDK 2.6... 
January 21, 2012, 06:13:29 PM
Hashrate of all my cards (5830, 5870, 5970, 6870) and rigs are exacly 10% slower after version 2.0.8. So, is the hashrate really lower or hashrate calculation has been fixed?
January 21, 2012, 05:58:36 PM
So when you build for Windows do you build under Linux or Windows?
In a windows virtual machine running XP. January 21, 2012, 05:49:43 PM
When everything is installed properly, you shouldn't need to be hacking configure or makefile scripts for it to build on mingw32. On the other hand, I never build it from git or autoreconf. I always grab a tarball (make dist-bzip2) and use that to build the windows version from.
So when you build for Windows do you build under Linux or Windows?
January 21, 2012, 05:43:08 PM
When everything is installed properly, you shouldn't need to be hacking configure or makefile scripts for it to build on mingw32. On the other hand, I never build it from git or autoreconf. I always grab a tarball (make dist-bzip2) and use that to build the windows version from.
Jump to: