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

[techman05]

I only cross compile with mxe for mingw on linux myself. Those instructions were done by a helpful member of the forum over a year ago and probably no longer apply.

My cross compiler gcc version is:
i686-pc-mingw32-gcc (GCC) 4.8.1

I know they don't necessarily apply I installed 0.6.2 from the website, I've been working on this for the last 2 weeks accidentally updating it ... You've been doing this for alot longer. Look on the bright side if I or you figure out whats going on You can copy what I updated on it and not have to worry about updating it for another year   .

I did find another windows.h  in util.c that was probably giving grief but I'm not going to fudge with it till tomorrow.

Sorry if I'm giving you a head ache I'm trying not to break anything you know works and its unintended side effect

[rgr_rgr]

I finally was able to reproduce this bug with nanofury usb sticks and have debugged it. The fix for this crash is now in git master and I suggest all users with these devices upgrade. Given the prevalence of these devices, I've also uploaded updated windows binaries denoted 3.11.0-1 with the bugfix.

Nice, thanks.
Did this affect p2pool also? p2pool is working now here.

[-ck]

I finally was able to reproduce this bug with nanofury usb sticks and have debugged it. The fix for this crash is now in git master and I suggest all users with these devices upgrade. Given the prevalence of these devices, I've also uploaded updated windows binaries denoted 3.11.0-1 with the bugfix.

Nice, thanks.
Did this affect p2pool also? p2pool is working now here.

Bug occurred with nanofury usb sticks during a restart message, and p2pool's restarts are 20 times more common.

[techman05]

I thank for any help but I hope I won't have to go through this every time I want to compile. At least I'm doing edits in github, so at least if I find the golden bitcoin ckOlivias can merge it.

I think the new minGW is really picky about header it wants to use ,so if getting rid of windows.h being its in winsock2.h is right, cgminer will be easier to fix minus the gobs of math in the future.

[Cantrip]

Sent you 0.05 BTC.  Have been mining LTC for a while, and wanted to give you a donation.  Thanks!!

[techman05]

I replaced  all windows.h with the files set and then found myself removing ws2tcpip.h and got this error.  Every time I think I follow a fix a new thing comes out  . Any idea what this error means.

Code:

In file included from ./sha2.h:36:0,
                 from cgminer.c:53:
./miner.h:1180:18: error: field 'stratum_hints' has incomplete type
  struct addrinfo stratum_hints;
                  ^

It means your headers are missing heaps of definitions. You're clearly headed in the wrong direction...

I put back in the ws2tcpip.h header and commented out the windows.h's In the lines and got this. Any idea if winsock2.h has the file info you need to run cgminer alone and remove this header. I kinda wish there was one .h file to change to get them all in line since each driver calls for winsock.h by itself.

Code:

c:\mingw\include\sdkddkver.h:154:0: note: this is the location of the previous d
efinition
 #    define _WIN32_WINNT _WIN32_WINNT_WIN2K
 ^
  CC     cgminer-api.o
  CC     cgminer-logging.o
  CC     cgminer-usbutils.o
  CC     cgminer-libbitfury.o
  CC     cgminer-mcp2210.o
  CC     cgminer-driver-bitfury.o
  CC     cgminer-driver-drillbit.o
  CC     cgminer-driver-icarus.o
In file included from util.h:30:0,
                 from miner.h:27,
                 from compat.h:11,
                 from driver-icarus.c:48:
c:\mingw\include\ws2tcpip.h:38:2: error: #error "ws2tcpip.h is not compatible wi
th winsock.h. Include winsock2.h instead."
 #error "ws2tcpip.h is not compatible with winsock.h. Include winsock2.h instead
."
  ^
In file included from util.h:30:0,
                 from miner.h:27,
                 from compat.h:11,
                 from driver-icarus.c:48:
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 driver-icarus.c:45:
c:\mingw\include\winsock.h:315:8: note: originally defined here
 struct ip_mreq {
        ^
In file included from util.h:30:0,
                 from miner.h:27,
                 from compat.h:11,
                 from driver-icarus.c:48:
c:\mingw\include\ws2tcpip.h:390:13: error: expected '=', ',', ';', 'asm' or '__a
ttribute__' before 'freeaddrinfo'
 void WSAAPI freeaddrinfo (struct addrinfo*);
             ^
c:\mingw\include\ws2tcpip.h:391:12: error: expected '=', ',', ';', 'asm' or '__a
ttribute__' before 'getaddrinfo'
 int WSAAPI getaddrinfo (const char*,const char*,const struct addrinfo*,
            ^
c:\mingw\include\ws2tcpip.h:393:12: error: expected '=', ',', ';', 'asm' or '__a
ttribute__' before 'getnameinfo'
 int WSAAPI getnameinfo(const struct sockaddr*,socklen_t,char*,DWORD,
            ^
make[2]: *** [cgminer-driver-icarus.o] Error 1

Edit...
new fun same problem

I tried to use winsock2.h on icarus driver instead of windows.h and got this

Code:

make[2]: Entering directory `/home/USER/cgminer-master'
  CC     cgminer-driver-icarus.o
  CCLD   cgminer.exe
cgminer-cgminer.o:cgminer.c:(.text+0x84d9): undefined reference to `llround'
collect2.exe: error: ld returned 1 exit status
make[2]: *** [cgminer.exe] Error 1

Is this me using the wrong version of libcurl for to use winsock2.h ? I just installed what was specified in the howto other than the changes I've already specified to it.

[cooliobongo]

I'd be thankful if you could look into my issue.

Setup: CGMINER 3.7.2 ,W7 64, 8GB RAM, AMD 13.12, 2x 795WF F43  in computer case. One GPU works less hard to maintain a good Windows and Youtube interactivity. My config is special made so it doesn't go above 76C even after hours.

Using one CGMINER for one GPU, i have optimal speeds, CGMINER never crash, GPU never sick, computer never reboot.
Using one CGMINER for BOTH GPU, yet again optimal speeds.
Having TWO CGMINERS instances open (one each dealing with one GPU), speed loss of 40-60%, CGMINER randomly stops responding.

Code:

del *.bin
cgminer.exe --scrypt -o (login info) -d 1 --lookup-gap 2 --gpu-powertune 16 --thread-concurrency 21712 -g 1 -I 14 -w 256 --gpu-memclock 1250 --gpu-engine 900

[techman05]

If I knew what was wrong with my development enviroment I would have stopped trying a while ago. Now I'm trying to install a linux distro and see if I can work around this.Worst case scenario I can run my miners through it as long as the linux version compiles properly. The only advise I kept seeming to get was to add winsock2 to his code and all that's going to is annoy ckolivias.

WinGM is reading me as windows  And I didn't mess with any winsock files and the only change I made was ptthread.


To be continued

[CustomDesigned]

I have cgminer-3.10.0 on Fedora 19 with AntMiner.  (I had to add --enable-bitfury to configure for it to compile - otherwise it would miss mcp2210.c.)  It is mining at 600Mh/s, not the vaunted 1.6Gh/s, and it is barely warm (unlike the block erupters, which get quite hot in operation).

(5s):631.4M (avg):378.7Mh/s | A:349  R:9  HW:32  WU:0.0/m

Also, it is detected as USB1.1, not 2.0 (other 2.0 devices plugged into the port are detected as 2.0).

[Karin]

I have cgminer-3.10.0 on Fedora 19 with AntMiner.  (I had to add --enable-bitfury to configure for it to compile - otherwise it would miss mcp2210.c.)  It is mining at 600Mh/s, not the vaunted 1.6Gh/s, and it is barely warm (unlike the block erupters, which get quite hot in operation).

(5s):631.4M (avg):378.7Mh/s | A:349  R:9  HW:32  WU:0.0/m

Also, it is detected as USB1.1, not 2.0 (other 2.0 devices plugged into the port are detected as 2.0).

There is no official Antminer U1 support in cgminer yet, since the creators of Antminer never contacted the cgminer devs with code and/or hardware before it was released.  The developers just recently received units they can develop for, and so Antminer support is likely eventually forthcoming.  There are some forks of cgminer out there that have implemented an Antminer driver already though, though you'll have to look around for 'em and they're generally unsupported.

[CustomDesigned]

I have cgminer-3.10.0 on Fedora 19 with AntMiner.  (I had to add --enable-bitfury to configure for it to compile - otherwise it would miss mcp2210.c.)  It is mining at 600Mh/s, not the vaunted 1.6Gh/s, and it is barely warm (unlike the block erupters, which get quite hot in operation).

(5s):631.4M (avg):378.7Mh/s | A:349  R:9  HW:32  WU:0.0/m

Also, it is detected as USB1.1, not 2.0 (other 2.0 devices plugged into the port are detected as 2.0).

There is no official Antminer U1 support in cgminer yet, since the creators of Antminer never contacted the cgminer devs with code and/or hardware before it was released.  The developers just recently received units they can develop for, and so Antminer support is likely eventually forthcoming.  There are some forks of cgminer out there that have implemented an Antminer driver already though, though you'll have to look around for 'em and they're generally unsupported.

Ah, well I am impressed that with no software changes it does the work of 2 Block Erupters at less than half the power.  So with a little code merging and/or waiting, it should do the work of 5 Block Erupters.

[-ck]

I have cgminer-3.10.0 on Fedora 19 with AntMiner.  (I had to add --enable-bitfury to configure for it to compile - otherwise it would miss mcp2210.c.)  It is mining at 600Mh/s, not the vaunted 1.6Gh/s, and it is barely warm (unlike the block erupters, which get quite hot in operation).

(5s):631.4M (avg):378.7Mh/s | A:349  R:9  HW:32  WU:0.0/m

Also, it is detected as USB1.1, not 2.0 (other 2.0 devices plugged into the port are detected as 2.0).

There is no official Antminer U1 support in cgminer yet, since the creators of Antminer never contacted the cgminer devs with code and/or hardware before it was released.  The developers just recently received units they can develop for, and so Antminer support is likely eventually forthcoming.  There are some forks of cgminer out there that have implemented an Antminer driver already though, though you'll have to look around for 'em and they're generally unsupported.

Ah, well I am impressed that with no software changes it does the work of 2 Block Erupters at less than half the power.  So with a little code merging and/or waiting, it should do the work of 5 Block Erupters.

Someone want to point me to the best current cgminer code for them please?

[streetuff]

I have cgminer-3.10.0 on Fedora 19 with AntMiner.  (I had to add --enable-bitfury to configure for it to compile - otherwise it would miss mcp2210.c.)  It is mining at 600Mh/s, not the vaunted 1.6Gh/s, and it is barely warm (unlike the block erupters, which get quite hot in operation).

(5s):631.4M (avg):378.7Mh/s | A:349  R:9  HW:32  WU:0.0/m

Also, it is detected as USB1.1, not 2.0 (other 2.0 devices plugged into the port are detected as 2.0).

There is no official Antminer U1 support in cgminer yet, since the creators of Antminer never contacted the cgminer devs with code and/or hardware before it was released.  The developers just recently received units they can develop for, and so Antminer support is likely eventually forthcoming.  There are some forks of cgminer out there that have implemented an Antminer driver already though, though you'll have to look around for 'em and they're generally unsupported.

Ah, well I am impressed that with no software changes it does the work of 2 Block Erupters at less than half the power.  So with a little code merging and/or waiting, it should do the work of 5 Block Erupters.

Someone want to point me to the best current cgminer code for them please?

https://github.com/fractalbc/cgminer

thats what i use. it works nice with 21 antminers and 37 block erupters!

[CustomDesigned]

Ah, well I am impressed that with no software changes it does the work of 2 Block Erupters at less than half the power.  So with a little code merging and/or waiting, it should do the work of 5 Block Erupters.

Someone want to point me to the best current cgminer code for them please?

https://github.com/bitmaintech/cgminer

That is a fork of cgminer back in Sep of '13.  I have started on a patch from cgminer-3.10.0 (just did the diff -r), but now that you are interested, I'll go back to my real job...

[ThinkFast]

Just searched the README.txt, NEWS.txt and ASIC-README.txt. Found nothing about Antminer support.  What am I missing?
Thanks.

[os2sam]

Just searched the README.txt, NEWS.txt and ASIC-README.txt. Found nothing about Antminer support.  What am I missing?
Thanks.

Your missing the 6 post just before you posted this message.

[ThinkFast]

Just searched the README.txt, NEWS.txt and ASIC-README.txt. Found nothing about Antminer support.  What am I missing?
Thanks.

Thanks.

[Buchi-88]

I have cgminer-3.10.0 on Fedora 19 with AntMiner.  (I had to add --enable-bitfury to configure for it to compile - otherwise it would miss mcp2210.c.)  It is mining at 600Mh/s, not the vaunted 1.6Gh/s, and it is barely warm (unlike the block erupters, which get quite hot in operation).

(5s):631.4M (avg):378.7Mh/s | A:349  R:9  HW:32  WU:0.0/m

Also, it is detected as USB1.1, not 2.0 (other 2.0 devices plugged into the port are detected as 2.0).

There is no official Antminer U1 support in cgminer yet, since the creators of Antminer never contacted the cgminer devs with code and/or hardware before it was released.  The developers just recently received units they can develop for, and so Antminer support is likely eventually forthcoming.  There are some forks of cgminer out there that have implemented an Antminer driver already though, though you'll have to look around for 'em and they're generally unsupported.

Ah, well I am impressed that with no software changes it does the work of 2 Block Erupters at less than half the power.  So with a little code merging and/or waiting, it should do the work of 5 Block Erupters.

Someone want to point me to the best current cgminer code for them please?

https://github.com/fractalbc/cgminer

thats what i use. it works nice with 21 antminers and 37 block erupters!

Hello, is the inofficial Cgminer 24/7 stable?


If so, what version it is under the link?

https://github.com/fractalbc/cgminer

greets

[chek2fire]

I have cgminer-3.10.0 on Fedora 19 with AntMiner.  (I had to add --enable-bitfury to configure for it to compile - otherwise it would miss mcp2210.c.)  It is mining at 600Mh/s, not the vaunted 1.6Gh/s, and it is barely warm (unlike the block erupters, which get quite hot in operation).

(5s):631.4M (avg):378.7Mh/s | A:349  R:9  HW:32  WU:0.0/m

Also, it is detected as USB1.1, not 2.0 (other 2.0 devices plugged into the port are detected as 2.0).

There is no official Antminer U1 support in cgminer yet, since the creators of Antminer never contacted the cgminer devs with code and/or hardware before it was released.  The developers just recently received units they can develop for, and so Antminer support is likely eventually forthcoming.  There are some forks of cgminer out there that have implemented an Antminer driver already though, though you'll have to look around for 'em and they're generally unsupported.

Ah, well I am impressed that with no software changes it does the work of 2 Block Erupters at less than half the power.  So with a little code merging and/or waiting, it should do the work of 5 Block Erupters.

Someone want to point me to the best current cgminer code for them please?

https://github.com/fractalbc/cgminer

thats what i use. it works nice with 21 antminers and 37 block erupters!

Hello, is the inofficial Cgminer 24/7 stable?


If so, what version it is under the link?

https://github.com/fractalbc/cgminer

greets

this version is stable i run it for days without any problem. The version of cgminer there is 3.09

[-ck]

New version: 3.12.0, 29th January 2014

- Another even number, so it's gotta be stable!

Human readable changelog:

- Antminer U1 support
- Numerous fixes for behaviour surrounding USB errors - pipe and IO errors, and no more attempting to reset the device since it's rarely helpful and occasionally harmful.
- Libusb and libusbx have finally reconciled their differences and merged all their fixes together into a new official libusb release, so the main change in this version is updating the core code to include this latest libusb. Hopefully this might increase compatibility with some USB3 hubs on windows and make it more reliable (based on the changelogs I can see in libusb). This is the reason for the minor version number update to 12 as it's quite a substantial code change, hopefully only for the better!
- Increased the hashfast overheat limit default to 90 after extensive discussions with the engineers who designed the devices.
- Fixed a crash in the nanofury USB stick code.
- Fixed the displayed diff shown being wrong when solo mining.
- bab driver fixes courtesy of Kano.


Full changelog:

- Add support for AntminerU1 devices with the icarus driver.
- Add antminer U1 to comment in udev rules.
- Do away with usb resets entirely since we retry on both pipe and io errors now
and they're of dubious value.
- Retry on usb IO errors instead of faking success.
- Check that we've cleared the pipe error after a clear request, not the err
value which is unchanged.
- Update to libusb-1.0.18
- Change hfa overheat limit to 90 degrees.
- Relax timeout in hf get header to 500ms to match the usb timeout.
- Minion - check/clear interrupts for all chips
- Set info work to null after it is freed in nf1 after a restart to prevent
double free later.
- The second_run bool in libbitfury should be per device. Microoptimise its and
job_switched usage, removing the unused results array for NF1 devices.
- Fix displayed diff when solo mining at >2^32 diff.
- bab - stop stale work accumulating
- bab - set the default SPI speed back to 96000