OFFICIAL CGMINER mining software thread for linux/win/osx/mips/arm/r-pi 4.11.1

[kano]

Actually, on linux, it's better to use:

now="`date +%Y%m%d%H%M%S`"

so now looks like: 20111101121520
and them something like:

./cgminer ....... 2> run.$now.$$.log

That way the name sorts in time order and '$$' adds the process number in case there are accidentally 2 running at the same time

Very nice, you wouldn't believe how hard it is to get people to understand why that date (and date-time in this case) structure is the logical way to go, or maybe you've been there, done that.

I prefer the more compact version but the result is the same.

./cgminer ....  2> run-`date +%y:%T`.log

 creates the file "run-02:02:01:56.log"

Best
//GoK

I think the time must be wrong on your computer ...
%y is the 2 digit year - and 02 is definitely not this year
Did you want %F maybe?

Just putting the year there wouldn't help with sorting.
As The00Dustin said, my choice is so the files automatically sort in date/time order.

[1713507569]

1713507569

[1713507569]

1713507569

[1713507569]

1713507569

[btcex]

Just change from GUIMiner to CGMINER on Windows 7 x64 with two 6990 - just awesome, great work!

[DeathAndTaxes]

Just change from GUIMiner to CGMINER on Windows 7 x64 with two 6990 - just awesome, great work!

Once you switch you won't ever consider another miner.   Throw some donations towards the author if you found it useful. If you don't have the coins then you can enable donations and send 1% of your hashing power to him.

[P4man]

Minor bug report; as DrHaribo already explained in a PM I believe, Id like to confirm the issue is real.

When using failover, cgminer 2.0.7 is sending withheld shares to the wrong pool, obviously resulting in stales.

I saw this first hand when bitminter pool was having trouble this morning. I didnt log it, but by memory, cgminer first displayed that bitminter was slow to respond, and was witholding results. A few seconds later, it decided that bitminter pool was unreachable, and switched to slush's pool. Then it resubmitted the withheld shares, which were obviously rejected.  Ive seen it happen a few times. IIRC it also happened in the other direction, when bitminter went live again, it sent shares which should have been sent to slush.

Is it necessary or useful to enable logging and try to force the issue by blocking bitminter on my firewall?

update: I just tried on my windows machine, with just one gpu, and cgminer's failover seems to work fine. Possibly this is only an issue on linux or with 2+ gpus? Ill test some more and report back.

[-ck]

The work item stores a reference to which pool it came from and that reference is never changed. If the pool itself is having communication trouble of some sort, it's entirely possible that the pool doesn't recognise its own work afterwards? Unless there's a bug I haven't tracked down, cgminer never changes reference to where the work came from. Now if you're piping it through some other proxy of some sort or hopper or something, then perhaps they mess with the headers as they come through.

static bool submit_upstream_work(const struct work *work)
struct pool *pool = work->pool;
val = json_rpc_call(curl, pool->rpc_url, pool->rpc_userpass, s, false, false, &rolltime, pool);

So it sends the work upstream each time with the pool information directly stored in the work structure. As I said, there may be a bug I haven't tracked down, but that field is never changed once the work is grabbed.

[DeathAndTaxes]

Anyone get an issue where cgminer hangs w/ 100% CPU usage in linuxcoin?

I have cgminer set to startup automtically (auto.sh).  ~95% of time after power cycling a rig it starts up just fine but sometimes the following happens ...

cgminer starts
it begins processing some shares
the "display" never appears

Instead of this

Code:

cgminer version 2.0.7 - Started: [2011-11-07 03:53:00]
-------------------------------------------------------------------------------
(5s):2271.6 (avg):2255.4 Mh/s | Q:70  A:102  R:0  HW:0  E:146%  U:29.60/m
TQ: 11  ST: 12  SS: 0  DW: 22  NB: 3  LW: 189  GF: 1  RF: 0
Connected to http://api2.bitcoin.cz:8332 with LP as user .....
Block: 000003786a1f68a61c89c31b2ce8f9bb...  Started: [03:55:49]
-------------------------------------------------------------------------------
[P]ool management [G]PU management [S]ettings [D]isplay options [Q]uit
GPU 0: 48.5C | 376.8/381.0Mh/s | A:20 R:0 HW:0 U:5.80/m I:4
GPU 1: 49.5C | 386.1/386.4Mh/s | A:16 R:0 HW:0 U:4.64/m I:9
GPU 2: 48.5C  960RPM | 376.8/384.3Mh/s | A:17 R:0 HW:0 U:4.93/m I:9
GPU 3: 48.0C  960RPM | 379.3/383.5Mh/s | A:15 R:0 HW:0 U:4.35/m I:9
GPU 4: 374.5/379.6Mh/s | A:20 R:0 HW:0 U:5.80/m I:9
GPU 5: 49.0C | 376.2/377.8Mh/s | A:15 R:0 HW:0 U:4.35/m I:9

I get something like this ...

Code:

GPU 0: 48.5C | 376.8/381.0Mh/s | A:20 R:0 HW:0 U:5.80/m I:4
[2011-11-07 03:56:39] Accepted 00000000.e18ff5e4.7bf0da85 GPU 1 thread 7 pool 0
GPU 3: 48.0C  960RPM | 379.3/383.5Mh/s | A:15 R:0 HW:0 U:4.35/m I:9
[2011-11-07 03:56:42] Accepted 00000000.f2bb9183.2f81f5c6 GPU 1 thread 1 pool 0
GPU 1: 49.5C | 386.1/386.4Mh/s | A:16 R:0 HW:0 U:4.64/m I:9
[2011-11-07 03:56:42] Accepted 00000000.d0d064f8.b2a7d847 GPU 1 thread 7 pool 0
[2011-11-07 03:56:43] Accepted 00000000.5b0a721c.7479a52d GPU 0 thread 0 pool 0
GPU 4: 374.5/379.6Mh/s | A:20 R:0 HW:0 U:5.80/m I:9
GPU 2: 48.5C  960RPM | 376.8/384.3Mh/s | A:17 R:0 HW:0 U:4.93/m I:9
GPU 5: 49.0C | 376.2/377.8Mh/s | A:15 R:0 HW:0 U:4.35/m I:9
GPU 2: 48.5C  960RPM | 376.8/384.3Mh/s | A:17 R:0 HW:0 U:4.93/m I:9
GPU 2: 48.5C  960RPM | 376.8/384.3Mh/s | A:17 R:0 HW:0 U:4.93/m I:9

Almost like it isn't updating the "display area" and insteading dumping everything to the command line.  This only seems to happen on "startup" and only rarely.  The bad news is it seems to eventually take 100% of CPU and then hard lock all the GPU.  When I detect it (which is easy because it only happens when cgminer startsup) I simply reboot the rig and the issue goes away. 

It is just kinda annoying.  Just wonder if anyone has seem anything like this or any ideas on prventing it.

[kano]

The '-T' option produces output somewhat like that (instead of curses)

[DeathAndTaxes]

The '-T' option produces output somewhat like that (instead of curses)

Hmm I wonder if some bug is happening in the curses library then ...

Since I use all my instances remotely I don't really need the curses interface.  I may try the -T option.  Thanks.

[gnar1ta$]

Anyone get an issue where cgminer hangs w/ 100% CPU usage in linuxcoin?

I have cgminer set to startup automtically (auto.sh).  ~95% of time after power cycling a rig it starts up just fine but sometimes the following happens ...

cgminer starts
it begins processing some shares
the "display" never appears

I've seen this a few times on remote linuxcoin and ubuntu rigs.  It's always turned out to be an issue with extenders for me, or at least replacing them seems to have fixed it.

[P4man]

It is just kinda annoying.  Just wonder if anyone has seem anything like this or any ideas on prventing it.

I havent seen it. But Ive booted linuxcoin only once so far. And its still running. I havent configured it for headless  and removed the monitor since booting, so I hope it keeps running for some time .

Are you using "screen" ? If not, Id give that a try. It runs the console in a 'session', that you can attach and detach over ssh. install it with

sudo apt-get install screen

and run it with

Code:

screen ./yourminingscrip.sh

To detach the screen press control+A and then D. To reattach,

Code:

screen -r

or

Code:

screen -r -d

if its already attached elsewhere.
well, you probably know all that already but someone else might not

[Red Emerald]

I would really love some sort of remote control (i.e. JSONRPC) for cgminer.  The config is already in JSON and bitcoin uses JSON.  It would be nice to have a BAMT style webgui on top of cgminer.  Even if the commands can only output stats and not change anything, that would be a nice step.

[coretechs]

First off, thanks for writing this miner, I've used it for a few weeks on a linux system and it's fantastic.  I tried switching to cgminer on a Windows 7 machine but I'm running into device init problems.  The machine has 3x 5970s and cgminer reports 3 GPUs disabled on startup and says it wont be able to start them from the menu either.  It is then unable to mine.  GUIMiner runs fine on all 6 GPUs.  I tried running it with various parameters but with no luck.  11.9 drivers, Win 7  Home x64.  Any ideas?

[malevolent]

Is cgminer better than guiminer and barelyclocked?

Does it support voltage changes on a lot of cards? Do they have to be of the same model?
Im using guiminer + barelyclocked ATM, but with BC I cannot change voltage or memory clocks on my non-ref VTX3D HD 6850 (only trixx does that well but I can only increase it), on my Sapphire non-ref HD 5850s I can only OC GPU core to 900MHz (memory and voltage changing works fine).

How's with hashing speeds compared to guiminer?
Im getting 360 MHash/s per HD 5850 (@900/350)
and 225 Mhash/s for my HD 6850 (@850/750)
drivers are ati 11.5 as far as I remember

[P4man]

How's with hashing speeds compared to guiminer?
Im getting 360 MHash/s per HD 5850 (@900/350)

I have slightly higher hashrate with the same card at same clocks (5850 900/300). I get 367 MH/s with cgminer (using it on my desktop thats used for other stuff too).

More importantly perhaps, cgminer is a joy to use, all in one program.

[AniceInovation]

1 BTC for you ckolivas, you deserve it.

And another to kano, thanks for your hints.

[kano]

1 BTC for you ckolivas, you deserve it.

And another to kano, thanks for your hints.

Thanks
Not sure if I deserve it - but certainly thanks

[Luigi]

Code:

/usr/bin/ld: cgminer-adl.o: undefined reference to symbol 'dlopen@@GLIBC_2.1'

Can anyone help me on this?
I have all *.h files from the AMD-ADL-SDK copied to the corresponding folder.

configure-procedure went through just fine

Code:

------------------------------------------------------------------------
cgminer 2.0.7
------------------------------------------------------------------------


Configuration Options Summary:

  OpenCL...............: FOUND. GPU mining support enabled
  ADL..................: SDK found, GPU monitoring support enabled
  ASM..................: true

Compilation............: make (or gmake)
  CPPFLAGS.............: 
  CFLAGS...............: -O2 -Wall -march=native
  LDFLAGS..............:  -lpthread -ldl

Installation...........: make install (as root if needed, with 'su' or 'sudo')
  prefix...............: /usr/local

I tried both... the latest git sources and the tarball provided.

[kano]

Hmm - have you actually installed the SDK as per the instructions?
(and what version of the SDK did you install?)

[os2sam]

First off, thanks for writing this miner, I've used it for a few weeks on a linux system and it's fantastic.  I tried switching to cgminer on a Windows 7 machine but I'm running into device init problems.  The machine has 3x 5970s and cgminer reports 3 GPUs disabled on startup and says it wont be able to start them from the menu either.  It is then unable to mine.  GUIMiner runs fine on all 6 GPUs.  I tried running it with various parameters but with no luck.  11.9 drivers, Win 7  Home x64.  Any ideas?

Did your two .bin files get created?
Sam

[MadHacker]

i had the exact same problem
i reverted to version 2.0.6 and it worked