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

[JPoet]

Before I was getting messages about blocks and submitted hashes.  Now it seems to be returning info from the blocksize method but not mining. Do you think I'm mining?  thanks

[kano]

Doesn't really make sense since if it can talk to it, it will mine on it.
If it can't mine on it, then that would be coz it can't talk to it thus it can't tell it to turn the led off.

It is possible to enable/disable a device using the USB menu. I have sometimes slow nanofurys because of several reasons. To find them I disable and wait. Then I try to find the cold one. If the LED would be switched off, it would be much easier.

It is possible to add an API command to send commands to devices that are being mined on.
e.g. switch led on/off could be possible if the command is documented somewhere.
(and yes we'll consider a post about it here on the forum as documentation ...)

However, since I don't have any nanofuries I don't know anything about them (and can't test changes)
We'll see what Con has to say about it

[kano]

Before I was getting messages about blocks and submitted hashes.  Now it seems to be returning info from the blocksize method but not mining. Do you think I'm mining?  thanks

At 3.130Gh/s you'd expect to find, on average, solo mining, a block once every ...
97,194days 5hr 1min 47sec

So yeah don't expect anything but block notifications for a few hundred years.

WU will tell you if you are mining.

... and an aside ... you are running 4.2.0 ... update to 4.2.3

[JPoet]

Thanks, I'm getting old but won't last it out . Anyway just wanted to try it out along with pooling.  Peace.

[-ck]

Doesn't really make sense since if it can talk to it, it will mine on it.
If it can't mine on it, then that would be coz it can't talk to it thus it can't tell it to turn the led off.

It is possible to enable/disable a device using the USB menu. I have sometimes slow nanofurys because of several reasons. To find them I disable and wait. Then I try to find the cold one. If the LED would be switched off, it would be much easier.

Disable doesn't currently turn them off, it just stops sending them work because the init sequence is involved and once they're running I try and not visit the init/shutdown code as the driver design assumes it will only ever be done once and prefers to just drop the device if it fails and lets it be hotplugged again if need be. I can revisit it.

[techman05]

Before I was getting messages about blocks and submitted hashes.  Now it seems to be returning info from the blocksize method but not mining. Do you think I'm mining?  thanks

At 3.130Gh/s you'd expect to find, on average, solo mining, a block once every ...
97,194days 5hr 1min 47sec

So yeah don't expect anything but block notifications for a few hundred years.

WU will tell you if you are mining.

... and an aside ... you are running 4.2.0 ... update to 4.2.3

Wheres a good place to find the math to find out if you can get a block at a certain speed. I haven't tried tweaking the settings on an antminer but I'd like to have solo mine as an option on that if its got enough kick to find and complete a few blocks.

I'd love to hope sometime in the future there'd be somekind of collection mode in cgminer so if I find myself with more devices like the s1 I can treat them like a single pooled device. I have to assume I'd have to do some stuff to make sure that if I have enough separated Gh's that I can complete a block in the time allotted[sot of speak]. No one else is mining so I'd love to have a borg hive manner [I think] for my hashings.

[-ck]

Wheres a good place to find the math to find out if you can get a block at a certain speed. I haven't tried tweaking the settings on an antminer but I'd like to have solo mine as an option on that if its got enough kick to find and complete a few blocks.

I'd love to hope sometime in the future there'd be somekind of collection mode in cgminer so if I find myself with more devices like the s1 I can treat them like a single pooled device. I have to assume I'd have to do some stuff to make sure that if I have enough separated Gh's that I can complete a block in the time allotted[sot of speak]. No one else is mining so I'd love to have a borg hive manner [I think] for my hashings.

There is never a guarantee that you can "complete a block in time". It's just purely random. That said, it's easy to work out on average how long it takes. Look at your work utility, WU, that's how many diff1 attempts per minute you are doing, and the difficulty is displayed on the screen (currently 6.1 billion). So at a work utility of 1000, you need 6100000000 / 1000 minutes on average to find a block.

[Zich]

Hi ck,

I got this error message while trying to compile cgminer for windows using mingw. Any clue?

"autoreconf -fvi" done without error
"CFLAGS="-O2 -msse2" ./configure" also done without error

Thanks  

Code:

Making all in ccan
make[2]: Entering directory `/home/Zinc/cgminer/ccan'
  CC     opt/libccan_a-helpers.o
  CC     opt/libccan_a-opt.o
  CC     opt/libccan_a-parse.o
  CC     opt/libccan_a-usage.o
  AR     libccan.a
make[2]: Leaving directory `/home/Zinc/cgminer/ccan'
make[2]: Entering directory `/home/Zinc/cgminer'
  CC     cgminer-cgminer.o
In file included from ./util.h:32:0,
                 from ./miner.h:27,
                 from ./sha2.h:36,
                 from cgminer.c:52:
c:\mingw\include\ws2tcpip.h:38:2: error: #error "ws2tcpip.h is not compatible
th winsock.h. Include winsock2.h instead."
 #error "ws2tcpip.h is not compatible with winsock.h. Include winsock2.h inste
."
  ^
In file included from ./util.h:32:0,
                 from ./miner.h:27,
                 from ./sha2.h:36,
                 from cgminer.c:52:
c:\mingw\include\ws2tcpip.h:147:8: error: redefinition of 'struct ip_mreq'
 struct ip_mreq {
        ^
In file included from c:\mingw\include\windows.h:93:0,
                 from cgminer.c:42:
c:\mingw\include\winsock.h:315:8: note: originally defined here
 struct ip_mreq {
        ^
In file included from ./util.h:32:0,
                 from ./miner.h:27,
                 from ./sha2.h:36,
                 from cgminer.c:52:
c:\mingw\include\ws2tcpip.h:390:13: error: expected '=', ',', ';', 'asm' or '_
ttribute__' before 'freeaddrinfo'
 void WSAAPI freeaddrinfo (struct addrinfo*);
             ^
c:\mingw\include\ws2tcpip.h:391:12: error: expected '=', ',', ';', 'asm' or '_
ttribute__' before 'getaddrinfo'
 int WSAAPI getaddrinfo (const char*,const char*,const struct addrinfo*,
            ^
c:\mingw\include\ws2tcpip.h:393:12: error: expected '=', ',', ';', 'asm' or '_
ttribute__' before 'getnameinfo'
 int WSAAPI getnameinfo(const struct sockaddr*,socklen_t,char*,DWORD,
            ^
make[2]: *** [cgminer-cgminer.o] Error 1
make[2]: Leaving directory `/home/Zinc/cgminer'
make[1]: *** [all-recursive] Error 1
make[1]: Leaving directory `/home/Zinc/cgminer'
make: *** [all] Error 2

[techman05]

Hi ck,

I got this error message while trying to compile cgminer for windows using mingw. Any clue?

"autoreconf -fvi" done without error
"CFLAGS="-O2 -msse2" ./configure" also done without error

Thanks  

Code:

Making all in ccan
make[2]: Entering directory `/home/Zinc/cgminer/ccan'
  CC     opt/libccan_a-helpers.o
  CC     opt/libccan_a-opt.o
  CC     opt/libccan_a-parse.o
  CC     opt/libccan_a-usage.o
  AR     libccan.a
make[2]: Leaving directory `/home/Zinc/cgminer/ccan'
make[2]: Entering directory `/home/Zinc/cgminer'
  CC     cgminer-cgminer.o
In file included from ./util.h:32:0,
                 from ./miner.h:27,
                 from ./sha2.h:36,
                 from cgminer.c:52:
c:\mingw\include\ws2tcpip.h:38:2: error: #error "ws2tcpip.h is not compatible
th winsock.h. Include winsock2.h instead."
 #error "ws2tcpip.h is not compatible with winsock.h. Include winsock2.h inste
."
  ^
In file included from ./util.h:32:0,
                 from ./miner.h:27,
                 from ./sha2.h:36,
                 from cgminer.c:52:
c:\mingw\include\ws2tcpip.h:147:8: error: redefinition of 'struct ip_mreq'
 struct ip_mreq {
        ^
In file included from c:\mingw\include\windows.h:93:0,
                 from cgminer.c:42:
c:\mingw\include\winsock.h:315:8: note: originally defined here
 struct ip_mreq {
        ^
In file included from ./util.h:32:0,
                 from ./miner.h:27,
                 from ./sha2.h:36,
                 from cgminer.c:52:
c:\mingw\include\ws2tcpip.h:390:13: error: expected '=', ',', ';', 'asm' or '_
ttribute__' before 'freeaddrinfo'
 void WSAAPI freeaddrinfo (struct addrinfo*);
             ^
c:\mingw\include\ws2tcpip.h:391:12: error: expected '=', ',', ';', 'asm' or '_
ttribute__' before 'getaddrinfo'
 int WSAAPI getaddrinfo (const char*,const char*,const struct addrinfo*,
            ^
c:\mingw\include\ws2tcpip.h:393:12: error: expected '=', ',', ';', 'asm' or '_
ttribute__' before 'getnameinfo'
 int WSAAPI getnameinfo(const struct sockaddr*,socklen_t,char*,DWORD,
            ^
make[2]: *** [cgminer-cgminer.o] Error 1
make[2]: Leaving directory `/home/Zinc/cgminer'
make[1]: *** [all-recursive] Error 1
make[1]: Leaving directory `/home/Zinc/cgminer'
make: *** [all] Error 2

Sadly never found an answer to this. I tried to get this to go through with mingw with no luck. Its got to be something wierd with the current mingw version but all I got from the mingw newsgroup was that is was my fault mingw didn't work.  Search back a few months here for mentions of mingw and theres about 2 pages of attempts to get a solution that never came to flortition.

You may want to try mxe though then you'll need to find you way on their issues board where they did say it compiles for them with instruction they gave me in their issues area on github I haven't tried any further since u1's came to be supported

[Zich]

Sadly never found an answer to this. I tried to get this to go through with mingw with no luck. Its got to be something wierd with the current mingw version but all I got from the mingw newsgroup was that is was my fault mingw didn't work.  Search back a few months here for mentions of mingw and theres about 2 pages of attempts to get a solution that never came to flortition.

You may want to try mxe though then you'll need to find you way on their issues board where they did say it compiles for them with instruction they gave me in their issues area on github I haven't tried any further since u1's came to be supported

Thanks for the head up.

Edit:

After searching on google, look like i found the problem. http://msdn.microsoft.com/en-us/library/windows/desktop/ms737629%28v=vs.85%29.aspx
There is some wrong include on util.h line 32. Base on the article, winsock.h must be include before ws2tcpip.h.

Code:

#elif defined WIN32
          #include <ws2tcpip.h>
          #include <winsock2.h>

Other problem is  Windows.h header defaults to including the Winsock.h which will conflict with the declarations in the Winsock2.h.

So this is the adjustment.

Code:

#elif defined WIN32
#ifndef WIN32_LEAN_AND_MEAN
        #define WIN32_LEAN_AND_MEAN
        #endif

#include <windows.h>
#include <winsock2.h>
#include <ws2tcpip.h>
        #include <iphlpapi.h>
        #include <stdio.h>

But then i got other error  

Code:

 CCLD   cgminer.exe
cgminer-cgminer.o: In function `clean_up':
C:\MinGW\msys\1.0\home\Zinc\cgminer/cgminer.c:8794: undefined reference to `time
EndPeriod'
cgminer-cgminer.o: In function `hashmeter':
C:\MinGW\msys\1.0\home\Zinc\cgminer/cgminer.c:6096: undefined reference to `llro
und'
cgminer-cgminer.o: In function `clean_up':
C:\MinGW\msys\1.0\home\Zinc\cgminer/cgminer.c:8794: undefined reference to `time
EndPeriod'
cgminer-cgminer.o: In function `main':
C:\MinGW\msys\1.0\home\Zinc\cgminer/cgminer.c:9657: undefined reference to `time
BeginPeriod'
collect2.exe: error: ld returned 1 exit status
make[2]: *** [cgminer.exe] Error 1
make[2]: Leaving directory `/home/Zinc/cgminer'
make[1]: *** [all-recursive] Error 1
make[1]: Leaving directory `/home/Zinc/cgminer'
make: *** [all] Error 2

[-ck]

After searching on google, look like i found the problem. http://msdn.microsoft.com/en-us/library/windows/desktop/ms737629%28v=vs.85%29.aspx
There is some wrong include on util.h line 32. Base on the article, winsock.h must be include before ws2tcpip.h.

Thanks for your investigating. I build all the official binaries with mxe, so it works either way, but I have shuffled things slightly based on that info and removed the windows.h include entirely. I have no idea what effect that will have on other build environments 

[Zich]

After searching on google, look like i found the problem. http://msdn.microsoft.com/en-us/library/windows/desktop/ms737629%28v=vs.85%29.aspx
There is some wrong include on util.h line 32. Base on the article, winsock.h must be include before ws2tcpip.h.

Thanks for your investigating. I build all the official binaries with mxe, so it works either way, but I have shuffled things slightly based on that info and removed the windows.h include entirely. I have no idea what effect that will have on other build environments 

I see, now i need to ask google about mxe  or you maybe can add some guide to windows-build.txt 

[-ck]

After searching on google, look like i found the problem. http://msdn.microsoft.com/en-us/library/windows/desktop/ms737629%28v=vs.85%29.aspx
There is some wrong include on util.h line 32. Base on the article, winsock.h must be include before ws2tcpip.h.

Thanks for your investigating. I build all the official binaries with mxe, so it works either way, but I have shuffled things slightly based on that info and removed the windows.h include entirely. I have no idea what effect that will have on other build environments 

I see, now i need to ask google about mxe  or you maybe can add some guide to windows-build.txt 

That file is horribly outdated from the GPU days and since I started cross compiling with mxe there is no way I'm going to try and build it directly on windows or any other way any more, sorry. In fact that windows build file wasn't even made by me if you read it, but a very dedicated user...

[Zich]

I see, now i need to ask google about mxe  or you maybe can add some guide to windows-build.txt 

That file is horribly outdated from the GPU days and since I started cross compiling with mxe there is no way I'm going to try and build it directly on windows or any other way any more, sorry. In fact that windows build file wasn't even made by me if you read it, but a very dedicated user...

No problem 
I will learn mxe step by step 

[techman05]

I see, now i need to ask google about mxe  or you maybe can add some guide to windows-build.txt 

That file is horribly outdated from the GPU days and since I started cross compiling with mxe there is no way I'm going to try and build it directly on windows or any other way any more, sorry. In fact that windows build file wasn't even made by me if you read it, but a very dedicated user...

No problem 
I will learn mxe step by step 

This is the closest update for that windows build file and I at least put the details I got from the issues area on mxe's github page https://github.com/mxe/mxe/issues/338

Here https://github.com/techman05/cgminer/blob/master/windows-build.txt

I should probably try to add it into ckolivias/cgminer but most of my other files in my github fork of cgminer that I tried to tweak should be purged or put in the closet sot of speak

[Zich]

This is the closest update for that windows build file and I at least put the details I got from the issues area on mxe's github page https://github.com/mxe/mxe/issues/338

Here https://github.com/techman05/cgminer/blob/master/windows-build.txt

I should probably try to add it into ckolivias/cgminer but most of my other files in my github fork of cgminer that I tried to tweak should be purged or put in the closet sot of speak

Thanks, this is what i looking for 

[ManeBjorn]

I have a quick question.
I have a clean Win  system all updated and no issues running my OneString Miner setup and cgminer every 8 hrs or so crashes.  I have ran it alone and on another system and it just says it stops working.  It will take multiple tries to get it restarted.
4.2.3 did not fix it either.  I have no problems with any other miners or software I have tried on it to test if it was the system.

[-ck]

I have a quick question.
I have a clean Win  system all updated and no issues running my OneString Miner setup and cgminer every 8 hrs or so crashes.  I have ran it alone and on another system and it just says it stops working.  It will take multiple tries to get it restarted.
4.2.3 did not fix it either.  I have no problems with any other miners or software I have tried on it to test if it was the system.

I've not seen this on linux, so try a debug build with the instructions here:
http://ck.kolivas.org/apps/cgminer/debug/

[ManeBjorn]

Thank you I will do this tomorrow afternoon and get you the results.

I have a quick question.
I have a clean Win  system all updated and no issues running my OneString Miner setup and cgminer every 8 hrs or so crashes.  I have ran it alone and on another system and it just says it stops working.  It will take multiple tries to get it restarted.
4.2.3 did not fix it either.  I have no problems with any other miners or software I have tried on it to test if it was the system.

I've not seen this on linux, so try a debug build with the instructions here:
http://ck.kolivas.org/apps/cgminer/debug/

[-ck]

New release: version 4.3.0, 18th April 2014

Mainly new driver updates. Uploaded 32 bit linux binaries as well now.


Human readable changelog:

- Spondoolies driver. Note this is for dedicated hardware attached to a beaglebone so the code should not be compiled into a generic use-everywhere binary.
- Add API output for spondoolies driver.
- Add temperature to spondoolies API output.
- Update to bi*fury driver (bxf) to support many chips, it will report up to 6 chips as HXF for hex*fury and more than that generically as MXF which currently is how the onestring miners appear until newer firmware comes out uniquely identifying them.
- Fixed the output for the proper amount of chips in *XF devices.
- Fix for solo mining to detect when we are mining on an orphan branch and switch to the correct one.
- Fix for syslog.
- Fixes for building on windows.
- Much faster startup for hashfast devices, the more devices the bigger the speedup.


Full changelog:

- Put sleep in spond hash instead of queue full function
- Remove unused function for when compiled without curses
- Fix typo
- Add temperature rate, front, rear and device temperature to spond API output
- Limit bxf sleep in bxf_scan to 100ms minimum for strings of many chips
- -Werror=format-security error on driver-bitmain.c
- Fix parameters passed with getblockhash
- Check the block hash with the proper command when looking for orphan chains
- syslog requires a facility ... in more than one place
- Shuffle windows headers included
- Adjust the bxf sleep time according to the number of chips detected
- Fix off by one error in bxf chip count when adjusting device size
- Recalloc correct pointer
- Make instructions associated with winusb error even more explicit
- Add midsing headers to cgminer source in Makefile
- Trivial style changes to mg proto parser
- Trivial style and warning clean ups on spondoolies driver
- Merge spondoolies driver patch
- Call any BXF device with 3-6 chips reported HXF
- Avoid derefrence when calling statline before on hfa device during init
sequence
- Calloc the info structures even on failed hfa reset to prevent later possible
dereference
- Load all hfa devices based on identification alone and defer init sequence
till mining thread init sequence to allow all devices to be recognised rapidly
but each device initialisation not delay others
- Do not do thread shutdown unless thread init succeeded
- Remove unnecessary check for thread_prepare function
- Recognise variations on BXF based on chip value returned in responses
- Provide helper function for recallocing memory
- syslog requires a facility