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

[xyzzy099]

Hi, thanks to your help

I try with gmake compilation some files are compiled but i have this error now:

Code:

gcc: -lpthread: linker input file unused because linking not done
  CC     cgminer-logging.o
In file included from logging.c:16:
miner.h:50:1: warning: "alloca" redefined
In file included from ./compat/jansson-2.5/src/jansson.h:12,
                 from miner.h:10,
                 from logging.c:16:
/usr/include/stdlib.h:237:1: warning: this is the location of the previous definition
gcc: -lpthread: linker input file unused because linking not done
  CCLD   cgminer
/usr/bin/ld: cannot find -ldl
gmake[2]: *** [cgminer] Error 1
gmake[2]: Leaving directory `/tmp/cgminer-3.8.4'
gmake[1]: *** [all-recursive] Error 1
gmake[1]: Leaving directory `/tmp/cgminer-3.8.4'
gmake: *** [all] Error 2

/usr/local/ld exist and works fine on the system

It seems cgminer wants to link against libdl, which does not exist on FreeBSD.  Usually programs that use libdl are looking for functions that are built into libc on FreeBSD, so if you just remove the references to libdl from the makefile it will probably compile and run just fine.

[evolvia31]

Hi,

I try to delete -ldl switch to Makefile.
But now i have an other problem during compilation on the same object:

Code:

 CCLD   cgminer
cgminer-cgminer.o(.text+0x18b4): In function `libusb_poll_thread':
/tmp/cgminer-3.8.4/cgminer.c:7801: undefined reference to `libusb_handle_events_timeout_completed'
cgminer-cgminer.o(.text+0x18da):/tmp/cgminer-3.8.4/cgminer.c:7809: undefined reference to `libusb_handle_events_timeout_completed'
cgminer-util.o(.text+0x17bc): In function `nanosleep_abstime':
/tmp/cgminer-3.8.4/util.c:1001: undefined reference to `clock_nanosleep'
cgminer-usbutils.o(.text+0x1b37): In function `usb_all':
/tmp/cgminer-3.8.4/usbutils.c:999: undefined reference to `libusb_error_name'
cgminer-usbutils.o(.text+0x1cc4):/tmp/cgminer-3.8.4/usbutils.c:903: undefined reference to `libusb_error_name'
cgminer-usbutils.o(.text+0x1cf7):/tmp/cgminer-3.8.4/usbutils.c:899: undefined reference to `libusb_error_name'
cgminer-usbutils.o(.text+0x1d6e):/tmp/cgminer-3.8.4/usbutils.c:979: undefined reference to `libusb_error_name'
cgminer-usbutils.o(.text+0x6988): In function `resource_process':
/tmp/cgminer-3.8.4/usbutils.c:3547: undefined reference to `semtimedop'
cgminer-usbutils.o(.text+0x88f3): In function `_usb_transfer_read':
/tmp/cgminer-3.8.4/usbutils.c:2899: undefined reference to `libusb_error_name'
cgminer-usbutils.o(.text+0x8cec): In function `__usb_transfer':
/tmp/cgminer-3.8.4/usbutils.c:2830: undefined reference to `libusb_error_name'
cgminer-usbutils.o(.text+0x9b74): In function `_usb_write':
/tmp/cgminer-3.8.4/usbutils.c:2732: undefined reference to `libusb_error_name'
cgminer-usbutils.o(.text+0xa181): In function `_usb_read':
/tmp/cgminer-3.8.4/usbutils.c:2641: undefined reference to `libusb_error_name'
gmake[2]: *** [cgminer] Error 1
gmake[2]: Leaving directory `/tmp/cgminer-3.8.4'
gmake[1]: *** [all-recursive] Error 1
gmake[1]: Leaving directory `/tmp/cgminer-3.8.4'
gmake: *** [all] Error 2

you have an idea ?

[xyzzy099]

Hi,

I try to delete -ldl switch to Makefile.
But now i have an other problem during compilation on the same object:

Code:

 CCLD   cgminer
cgminer-cgminer.o(.text+0x18b4): In function `libusb_poll_thread':
/tmp/cgminer-3.8.4/cgminer.c:7801: undefined reference to `libusb_handle_events_timeout_completed'
cgminer-cgminer.o(.text+0x18da):/tmp/cgminer-3.8.4/cgminer.c:7809: undefined reference to `libusb_handle_events_timeout_completed'
cgminer-util.o(.text+0x17bc): In function `nanosleep_abstime':
/tmp/cgminer-3.8.4/util.c:1001: undefined reference to `clock_nanosleep'
cgminer-usbutils.o(.text+0x1b37): In function `usb_all':
/tmp/cgminer-3.8.4/usbutils.c:999: undefined reference to `libusb_error_name'
cgminer-usbutils.o(.text+0x1cc4):/tmp/cgminer-3.8.4/usbutils.c:903: undefined reference to `libusb_error_name'
cgminer-usbutils.o(.text+0x1cf7):/tmp/cgminer-3.8.4/usbutils.c:899: undefined reference to `libusb_error_name'
cgminer-usbutils.o(.text+0x1d6e):/tmp/cgminer-3.8.4/usbutils.c:979: undefined reference to `libusb_error_name'
cgminer-usbutils.o(.text+0x6988): In function `resource_process':
/tmp/cgminer-3.8.4/usbutils.c:3547: undefined reference to `semtimedop'
cgminer-usbutils.o(.text+0x88f3): In function `_usb_transfer_read':
/tmp/cgminer-3.8.4/usbutils.c:2899: undefined reference to `libusb_error_name'
cgminer-usbutils.o(.text+0x8cec): In function `__usb_transfer':
/tmp/cgminer-3.8.4/usbutils.c:2830: undefined reference to `libusb_error_name'
cgminer-usbutils.o(.text+0x9b74): In function `_usb_write':
/tmp/cgminer-3.8.4/usbutils.c:2732: undefined reference to `libusb_error_name'
cgminer-usbutils.o(.text+0xa181): In function `_usb_read':
/tmp/cgminer-3.8.4/usbutils.c:2641: undefined reference to `libusb_error_name'
gmake[2]: *** [cgminer] Error 1
gmake[2]: Leaving directory `/tmp/cgminer-3.8.4'
gmake[1]: *** [all-recursive] Error 1
gmake[1]: Leaving directory `/tmp/cgminer-3.8.4'
gmake: *** [all] Error 2

you have an idea ?

It looks like compiling cgminer on FreeBSD is not going to be a trivial task.  I would be glad to help you through it, but I haven't had a FreeBSD box in some years, so I really can't.  I think your options are these:

1) There may actually be a FreeBSD port for CGMiner that already exists.  If so, that is clearly the best way to build it.

2) If not, download the Linux binary and run it.  The FreeBSD Linux emulation is very good, and I'd be surprised if it didn't work just fine.

3) Get onto the FreeBSD ports mailing lists/forums and ask around.  I would be surprised if no FreeBSD users are using cgminer, and some of them can probably help you get it compiled.  Maybe you can inspire someone to create a port and add it to the ports tree.

[CustomDesigned]

Code:

Making all in compat
Making all in jansson-2.5
"Makefile", line 825: Need an operator
make: fatal errors encountered -- cannot continue

line 825 of compat/jansson-2.5

Code:

# These flags are gcc specific
export AM_CFLAGS = -Wall -Wextra -Wdeclaration-after-statement

Your version of make does not understand the 'export' statement.
The jansson-2.5 directory is the only Makefile that uses it, so perhaps
you can disable jansson or find an equivalent to 'export' in bsd make.

[evolvia31]

Ok thank you to your help.
I can't compile it.

there are too many code incompatibility.

I try to compile bfgminer i can have more chance

There isn't any ports to miner software in FreeBSD ports only one port to bitcoin software.

[xyzzy099]

Ok thank you to your help.
I can't compile it.

there are too many code incompatibility.

I try to compile bfgminer i can have more chance

There isn't any ports to miner software in FreeBSD ports only one port to bitcoin software.

Why not just run a Linux binary?  FreeBSD has excellent Linux emulation.

[evolvia31]

i don't find the cgminer linux binary 32 bits on the website

[xyzzy099]

i don't find the cgminer linux binary 32 bits on the website

Well, hell, I guess you're right

[evolvia31]

bfgminer compilation works fine

I can install it and launch it but it didn't detect my usb erupter

I'm very damned

if you have any idea

https://bitcointalk.org/index.php?topic=168174.msg3824128#msg3824128

[CustomDesigned]

i don't find the cgminer linux binary 32 bits on the website

To run the binary on a foreign system, it probably needs to be statically linked.

[xyzzy099]

i don't find the cgminer linux binary 32 bits on the website

To run the binary on a foreign system, it probably needs to be statically linked.

The FreeBSD Linux compatibility layer includes dynamic libraries.  A given binary may require that you also install any non-standard dynamic libraries required by that binary, of course.

[infofront]

cgminer will only recognize  one of my GPUs. Going on a suggestion from someone, I used the --no-adl argument. Now, it seems adl is permanently disabled. How can I re-enable it?

[erk]

Is there any way to disable the 5min pool stability check that was introduced in 3.5.1? It's playing havoc with multi pools that auto switch to the most profitable coin periodically, as the switch interrupts the stratum for 15-20sec which invokes the 5min stability check.

[mdude77]

cgminer will only recognize  one of my GPUs. Going on a suggestion from someone, I used the --no-adl argument. Now, it seems adl is permanently disabled. How can I re-enable it?

GPU support is not available for cgminer, and the authors only support the newest version of cgminer.

M

[aigeezer]

I just encountered something a bit different in a 3.8.4 test (Win7 64). This run was uneventful except for an occasional zombie and I was mindlessly replugging them as they occurred and they always restarted. Eventually one did not restart and I found it was flagged in the display as "dead" rather than "zombie". I pressed Q and the LEDs came on for all the others as expected and the BAL fan shut down, suggesting that cgminer accepted the command, but cgminer itself did not shut down and appeared to have frozen. I killed it with a Windows "close window" command. On restart, everything looks normal and the formerly "dead" AMU device is now hashing as usual. I should read up on necromancy to prepare for the next one.

[-ck]

I just encountered something a bit different in a 3.8.4 test (Win7 64). This run was uneventful except for an occasional zombie and I was mindlessly replugging them as they occurred and they always restarted. Eventually one did not restart and I found it was flagged in the display as "dead" rather than "zombie". I pressed Q and the LEDs came on for all the others as expected and the BAL fan shut down, suggesting that cgminer accepted the command, but cgminer itself did not shut down and appeared to have frozen. I killed it with a Windows "close window" command. On restart, everything looks normal and the formerly "dead" AMU device is now hashing as usual. I should read up on necromancy to prepare for the next one.

That means the command went out to the device and it got stuck somewhere in the operating system driver code (i.e. outside cgminer) and never returned.

Interestingly - and related - I've been doing some reading about usb hubs that don't have separate transaction translators for usb1.1 devices and wonder if all the flakiness isn't just dodgy hubs with a shared TT and all these usb devices being usb1.1. It's rather annoying that usb2 is a decade old and people are still making 1.1 devices because they can use the cheapest nastiest communication chip money can buy in their devices. What USB hub do you have? I don't even know if hubs are still made with single transaction translators any more or not, but it would be interesting to find out.

See this interesting and ancient comparison of a single TT hub to a multi TT hub:
http://www.tomshardware.com/reviews/usb-technology,677-3.html

[mdude77]

Interestingly - and related - I've been doing some reading about usb hubs that don't have separate transaction translators for usb1.1 devices and wonder if all the flakiness isn't just dodgy hubs with a shared TT and all these usb devices being usb1.1. It's rather annoying that usb2 is a decade old and people are still making 1.1 devices because they can use the cheapest nastiest communication chip money can buy in their devices. What USB hub do you have? I don't even know if hubs are still made with single transaction translators any more or not, but it would be interesting to find out.

It's a neat idea ... except I got zombies with the same hardware (same erupters, same hubs) that worked fine on another rig.  I'm down to 1 USB erupter, and it's happily chugging along at 335mh/s on main PC.

M

[-ck]

Interestingly - and related - I've been doing some reading about usb hubs that don't have separate transaction translators for usb1.1 devices and wonder if all the flakiness isn't just dodgy hubs with a shared TT and all these usb devices being usb1.1. It's rather annoying that usb2 is a decade old and people are still making 1.1 devices because they can use the cheapest nastiest communication chip money can buy in their devices. What USB hub do you have? I don't even know if hubs are still made with single transaction translators any more or not, but it would be interesting to find out.

It's a neat idea ... except I got zombies with the same hardware (same erupters, same hubs) that worked fine on another rig.  I'm down to 1 USB erupter, and it's happily chugging along at 335mh/s on main PC.

M

The PC's own hubs also include transaction translators by the way.

[aigeezer]

What USB hub do you have?

I'm using two powered Anker USB 3.0 hubs daisy-chained and going to a mobo USB 2.0 socket. I think we all found out early on that USB 3.0 (blue) sockets don't work with the Eruptors but the hubs allegedly downgrade from 3.0 to 2.0 without hassle and I think a lot of people use them that way for mining. My other machine that tends always to have similar cgminer issues (but never the "dead" label) also uses an Anker USB 3.0 powered hub connected to a USB 2.0 socket.

[-ck]

What USB hub do you have?

I'm using two powered Anker USB 3.0 hubs daisy-chained and going to a mobo USB 2.0 socket. I think we all found out early on that USB 3.0 (blue) sockets don't work with the Eruptors but the hubs allegedly downgrade from 3.0 to 2.0 without hassle and I think a lot of people use them that way for mining. My other machine that tends always to have similar cgminer issues (but never the "dead" label) also uses an Anker USB 3.0 powered hub connected to a USB 2.0 socket.

Interesting. Perhaps the USB3 hubs that don't work have virtually no USB1.1 TTs, and yours going through a USB2 socket is basically sharing the one TT on the USB2 socket. Also some people with USB3 slots on windows can't even see their devices. I think linux has some kind of software TT to compensate within the kernel so perhaps the operating system is actually working around them.