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

[The00Dustin]

Well the crash is happening in the share submission path, so it must be trying to submit a share. That said, I found something else that might be a problem. Try current git master please.

Just cloned the master & installed.  Didn't crash at startup, but apparently that doesn't mean much.  If there's a crash, I'll provide the debug info.

[rampone]

Oh darn, seems like building on a 64 bit ubuntu with 64bit curl makes problem, when it tries to include it. mmmh. well, i guess ill try a 32bit ubuntu to cross compile cgminer... I'll report...

No, that makes no sense as full 64bit ubuntu is the main development platform for it and where the binaries come from.

was (trying) to compile it for 32bit mipseb... I am trying under a 32bit system soon, i will report, this is not a cgminer problem, when googling, found out, that debian has trouble offering the right stuff when cross compiling.


compiling it to run under the 64bit ubuntu is no problem...

[crazyearner]

Could someone tell me how to make a .bat file to mine with both gpu and cpu at same time what is the commands needed to use both gpu and cup at same time usin cgimner and amd cpu??

[kano]

Could someone tell me how to make a .bat file to mine with both gpu and cpu at same time what is the commands needed to use both gpu and cup at same time usin cgimner and amd cpu??

As per the README

Q: What happened to CPU mining?
A: Being increasingly irrelevant for most users, and a maintenance issue, it is no longer under active development and will not be supported ...

[rav3n_pl]

Could someone tell me how to make a .bat file to mine with both gpu and cpu at same time what is the commands needed to use both gpu and cup at same time usin cgimner and amd cpu??

Cgminer CPU mining code is obsolete, use another CPU miner you will get 2x hash rate.

[CheezWiz]

I think there's still something awry with gracefully handling disconnects.  It isn't unique to stratum, as I've seen it on LPs as well.

Right now have three units running... one with 1 GPU, one with 2 GPUs, and one with 3 GPUs.  At the time all were pointed to stratum pools with bitcoind (LP) as a backup.

My internet connection dropped for a short bit.  The 1GPU machine recovered properly.  The 2GPU crashed, the 3GPU hung.

I've seen this before, where those with multiple GPUs crash or hang when the 1GPU continues working.  The 1 and 3 GPU machines are window 7 x64, the 2 GPU is windows 8 x64.

Using 2.9.6.

M

I just started using cgminer after over a year with phoenix and no issues and I am seeing this behavior. If there is a network issue, cgminer crashes in Windows and I get the not responding...searching for a resolution dialog from Windows. I can replicate the behavior like clockwork because I am mining over an SSH tunnel and I have a scheduled task that kills plonk every 30 minutes and restarts it. When plonk gets killed, cgminer crashes. So it does not like losing its network connection at all.

Additionally, I think the issue only happens when connected via the stratum protocol, but I am investigating the details...

[-ck]

Longstanding bug on windows for when network goes down; it's my secret way to get people to move to linux.

Obviously not the case, but anyway I've not been able to reproduce it myself so must be some combination of windows or other issue. You could always try helping debug it following instructions in here:
http://ck.kolivas.org/apps/cgminer/debug/

I suspect it's just the libcurl implementation on windows... which would be bad news since it won't be something I can personally fix.

[CheezWiz]

Longstanding bug on windows for when network goes down; it's my secret way to get people to move to linux.

Obviously not the case, but anyway I've not been able to reproduce it myself so must be some combination of windows or other issue. You could always try helping debug it following instructions in here:
http://ck.kolivas.org/apps/cgminer/debug/

I suspect it's just the libcurl implementation on windows... which would be bad news since it won't be something I can personally fix.

   between linux and mac users, the jabs never end...

Will do on the debug.... I may be working in an uncommon setup which may be compounding the issue. I run plonk to create an ssh tunnel on port 3333 to the pool via my home DDWRT router. Because the SSH tunnel can collapse at the slightest of network hiccups, which we have many, I restart plonk every 30 minutes. I believe the issue only happens when connected via stratum protocols. Too early to tell, I just started with cgminer since my pool switched over to stratum. However, I wish I had looked at it sooner because I am getting much better hash rates with cgminer!

Thanks!!

[sharky112065]

Longstanding bug on windows for when network goes down; it's my secret way to get people to move to linux.

Obviously not the case, but anyway I've not been able to reproduce it myself so must be some combination of windows or other issue. You could always try helping debug it following instructions in here:
http://ck.kolivas.org/apps/cgminer/debug/

I suspect it's just the libcurl implementation on windows... which would be bad news since it won't be something I can personally fix.

   between linux and mac users, the jabs never end...

Will do on the debug.... I may be working in an uncommon setup which may be compounding the issue. I run plonk to create an ssh tunnel on port 3333 to the pool via my home DDWRT router. Because the SSH tunnel can collapse at the slightest of network hiccups, which we have many, I restart plonk every 30 minutes. I believe the issue only happens when connected via stratum protocols. Too early to tell, I just started with cgminer since my pool switched over to stratum. However, I wish I had looked at it sooner because I am getting much better hash rates with cgminer!

Thanks!!

You might try downloading the cgminer source and following the windows-build.txt instructions for building your own binary of cgminer. That would get you the latest version of libcurl. If it is a libcurl issue this may fix it as C. kolivas does not update his dependencies  that often. Good Luck

[-ck]

mingw32-curl 7.27.0-1 is what I'm distributing libcurl from.
The one people usually post as a bug is that their own IP address changed or something like that.

[Luke-Jr]

Longstanding bug on windows for when network goes down; it's my secret way to get people to move to linux.

Obviously not the case, but anyway I've not been able to reproduce it myself so must be some combination of windows or other issue. You could always try helping debug it following instructions in here:
http://ck.kolivas.org/apps/cgminer/debug/

I suspect it's just the libcurl implementation on windows... which would be bad news since it won't be something I can personally fix.

One might note that I fixed this in BFGMiner a while ago, thanks to much debugging help from jddebug. It's not the most elegant fix, but it does do the job.

[-ck]

There will shortly be some massive changes to the git master tree - no unfortunately it still isn't any ASIC driver, but it will be stuff to prepare for it. In anticipation, I have created a 2.9 branch for those who want just fixes to the stable tree in the meantime. Some fixes to existing issues have already been committed to the 2.9 branch, but lots of potential breakage will be making its way into the master tree.

[Askit2]

Found an issue, Unsure on the cause but it could just be windows.

Win7 64 bit, CGMiner 2.9.6, BFL single.

Pool: Eclipse.

Eclipse seemed to have failed. US2, US3, on stratum marked dead as well as US3 GBT. US1 marked alive but no hashes submitted in 30 mins. Disabling US1 knocked me back to my backup pool and Bitpenny is working as shares are being submitted.

Debug showed all stratum pools marked dead as initiate failed, but US1 didn't seem to be doing anything. No rolling work messages, just test messages about the failed pools and a dropping hashrate when I re-enabled to double check the messages. Actually it shows a can't initiate for pool 1 (us1.eclipsemc.com:3333) so it should be dropping back to my backup pool and marking US1 dead too right?

Oh when I first came back and saw the issue I had 2 New block detected I can't remember if it was a LP, Stratum, or on network before the pool. Sadly I wish I hadn't tried to correct the lost money first and had typed what I noticed.

EDIT: It looks like there was an underlying issue with my internet connection. After eclipse died on me bitpenny worked for a while. Router log showed some errors. LRP router so the information was some better then consumer units. Once corrected well once a new IP was procured everything is running smooth. Strangely despite a duplicate IP message (unsure if someone was assigned mine or there was a spoof going on) some data still went out. I don't think it should have.

[c4n10]

Receiving unusual error when trying to connect to BitMinter:

Code:

JSON stratum auth failed: <unknown reason>

cgminer works fine at all the other pools I use it at though. Any ideas?

[Inaba]

Seems to be a strange problem with CGMiner and EMC as far as Stratum goes:

If I start cgminer with stratum pointed at one of my servers, it works fine and mines via stratum.  However, if I have one of the servers as backup and it's listed as stratum, it shows as dead and won't switch to it. 

Put another way, if I start with stratum on one of my servers, no problem.  If I try to add/switch to stratum on one of my servers, CGMiner won't work. 

Any ideas?  This is for version 2.9.6, I haven't tried previous versions.

[-ck]

Seems to be a strange problem with CGMiner and EMC as far as Stratum goes:

If I start cgminer with stratum pointed at one of my servers, it works fine and mines via stratum.  However, if I have one of the servers as backup and it's listed as stratum, it shows as dead and won't switch to it. 

Put another way, if I start with stratum on one of my servers, no problem.  If I try to add/switch to stratum on one of my servers, CGMiner won't work. 

Any ideas?  This is for version 2.9.6, I haven't tried previous versions.

Yeah, are you specifying the stratum server with stratum+tcp:// ? There's an issue with backup pools specified that way at the moment. Try leaving out the prefix, or specify them as http:// and it will just do stratum.

[ninjaboon]

Receiving unusual error when trying to connect to BitMinter:

Code:

JSON stratum auth failed: <unknown reason>

cgminer works fine at all the other pools I use it at though. Any ideas?

I have the same error on v2.9.3 but it works fine on v2.9.5.
Weird.

[-ck]

New version: 2.9.7, 7th December 2012

Bugfix only release. There are lots of pending changes which will be a new point release, but this is concentrating only on the known bugs that have fixes for 2.9.


Human readable changelog

Fixed the problem where backup stratum pools specified with stratum+tcp:// first would never come online.
Fixed another crash with GBT.
Decrease rejects with stratum by tying in target difficulty only with the work difficulty, as discussed on this forum thread with slush et. al
Don't show WU with scrypt mining since the number is wrong.
Windows builds are built and shipped with a new libcurl (and libusb) dll that hopefully improves stability.
Better load balance with stratum.


Full changelog

- Set pool probed to true on successful authorisation with stratum to avoid it
being pinged later with pool_getswork.
- Allow pool active to be called on stratum or disabled pools in the watchpool
thread if the pool has not been probed.
- Remove unused variable.
- Use a variable length string array in submit_upstream_work to cope with
massive GBT submissions.
- Remove unused getwork times in getswork.
- Don't show broken WU value with scrypt mining.
- The specification for stratum has been elaborated to say that a changed diff
applies only to new work so do not retarget when submitting shares.

[SAC]

Either I was too quick on the draw or you have not updated the version string as a fresh git clone tells me I will compile a version 2.9.6.

[-ck]

Either I was too quick on the draw or you have not updated the version string as a fresh git clone tells me I will compile a version 2.9.6.

You're right, it wasn't tagged. Tagged now (and be aware it's on the 2.9 branch).