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

[Ntrain2k]

will this work with ATI 7970 single card?

Q: What happened to CPU and GPU mining?
A: Their efficiency makes them irrelevant in the bitcoin mining world today
and the author has no interest in supporting alternative coins that are better
mined by these devices.

Try BFGminer or SGminer for GPU mining.

[AngusCanine]

What is the newest software that I can download and flash to my S1

[Taugeran]

@conman, @Kano: question/input request from you regarding a section of code.


In regards to:

Code:

/* Base the fail time on no valid nonces for 25 full nonce ranges at
* the current expected hashrate. */
fail_time = 25.0 * (double)hashfast->drv->max_diff * 0xffffffffull /
(double)(info->base_clock * 1000000) / hfa_basejobs(info);
if (unlikely(share_work_tdiff(hashfast) > fail_time)) {
applog(LOG_WARNING, "%s %s: No valid hashes for over %.0f seconds, shutting down thread",
      hashfast->drv->name, hashfast->unique_id, fail_time);
hfa_running_shutdown(hashfast, info);
return -1;
}

does tripping this indicate the device is spewing garbage(that cgminer is filtering), no spewing anything at all, or something else?

I ask as I am troubleshooting a couple of Habaneros, whom are ridiculously cool at the chip level(850MHz is 86-87C), and yet when set this high will continually trip this and clock down until ~750-767MHz.


EDIT: just made an obervation that prior to the message appearing in CGMiner, the fan on my RM1000 PSU, which is powering one of them, stops spinning indicating that the load completely drops. will investigate if additional VRM cooling is needed. also need to break down and grab a good FLIR cam (or at least an IR thermometer).

[MrTeal]

@conman, @Kano: question/input request from you regarding a section of code.


In regards to:

Code:

/* Base the fail time on no valid nonces for 25 full nonce ranges at
* the current expected hashrate. */
fail_time = 25.0 * (double)hashfast->drv->max_diff * 0xffffffffull /
(double)(info->base_clock * 1000000) / hfa_basejobs(info);
if (unlikely(share_work_tdiff(hashfast) > fail_time)) {
applog(LOG_WARNING, "%s %s: No valid hashes for over %.0f seconds, shutting down thread",
      hashfast->drv->name, hashfast->unique_id, fail_time);
hfa_running_shutdown(hashfast, info);
return -1;
}

does tripping this indicate the device is spewing garbage(that cgminer is filtering), no spewing anything at all, or something else?

I ask as I am troubleshooting a couple of Habaneros, whom are ridiculously cool at the chip level(850MHz is 86-87C), and yet when set this high will continually trip this and clock down until ~750-767MHz.


EDIT: just made an obervation that prior to the message appearing in CGMiner, the fan on my RM1000 PSU, which is powering one of them, stops spinning indicating that the load completely drops. will investigate if additional VRM cooling is needed. also need to break down and grab a good FLIR cam (or at least an IR thermometer).

cgminer spits out the VRM temperature for each die if you enable debugging or use the API, so you can see what they are. The VRM will shut down if it reaches 90C.

[Taugeran]

@conman, @Kano: question/input request from you regarding a section of code.


In regards to:

Code:

/* Base the fail time on no valid nonces for 25 full nonce ranges at
* the current expected hashrate. */
fail_time = 25.0 * (double)hashfast->drv->max_diff * 0xffffffffull /
(double)(info->base_clock * 1000000) / hfa_basejobs(info);
if (unlikely(share_work_tdiff(hashfast) > fail_time)) {
applog(LOG_WARNING, "%s %s: No valid hashes for over %.0f seconds, shutting down thread",
      hashfast->drv->name, hashfast->unique_id, fail_time);
hfa_running_shutdown(hashfast, info);
return -1;
}

does tripping this indicate the device is spewing garbage(that cgminer is filtering), no spewing anything at all, or something else?

I ask as I am troubleshooting a couple of Habaneros, whom are ridiculously cool at the chip level(850MHz is 86-87C), and yet when set this high will continually trip this and clock down until ~750-767MHz.


EDIT: just made an obervation that prior to the message appearing in CGMiner, the fan on my RM1000 PSU, which is powering one of them, stops spinning indicating that the load completely drops. will investigate if additional VRM cooling is needed. also need to break down and grab a good FLIR cam (or at least an IR thermometer).

cgminer spits out the VRM temperature for each die if you enable debugging or use the API, so you can see what they are. The VRM will shut down if it reaches 90C.

can you show an example line so i know what to be looking for? API and debuglog

[-ck]

@conman, @Kano: question/input request from you regarding a section of code.


In regards to:

Code:

/* Base the fail time on no valid nonces for 25 full nonce ranges at
* the current expected hashrate. */
fail_time = 25.0 * (double)hashfast->drv->max_diff * 0xffffffffull /
(double)(info->base_clock * 1000000) / hfa_basejobs(info);
if (unlikely(share_work_tdiff(hashfast) > fail_time)) {
applog(LOG_WARNING, "%s %s: No valid hashes for over %.0f seconds, shutting down thread",
      hashfast->drv->name, hashfast->unique_id, fail_time);
hfa_running_shutdown(hashfast, info);
return -1;
}

does tripping this indicate the device is spewing garbage(that cgminer is filtering), no spewing anything at all, or something else?

I ask as I am troubleshooting a couple of Habaneros, whom are ridiculously cool at the chip level(850MHz is 86-87C), and yet when set this high will continually trip this and clock down until ~750-767MHz.


EDIT: just made an obervation that prior to the message appearing in CGMiner, the fan on my RM1000 PSU, which is powering one of them, stops spinning indicating that the load completely drops. will investigate if additional VRM cooling is needed. also need to break down and grab a good FLIR cam (or at least an IR thermometer).

Tripping it indicates it hasn't generated a single correct share. It may be producing nothing or just garbage, the effect is the same. Sounds to me like it's picking up the failure correctly (of course it can't tell you why it failed, just that it did).

[Taugeran]

@conman, @Kano: question/input request from you regarding a section of code.


In regards to:

Code:

/* Base the fail time on no valid nonces for 25 full nonce ranges at
* the current expected hashrate. */
fail_time = 25.0 * (double)hashfast->drv->max_diff * 0xffffffffull /
(double)(info->base_clock * 1000000) / hfa_basejobs(info);
if (unlikely(share_work_tdiff(hashfast) > fail_time)) {
applog(LOG_WARNING, "%s %s: No valid hashes for over %.0f seconds, shutting down thread",
      hashfast->drv->name, hashfast->unique_id, fail_time);
hfa_running_shutdown(hashfast, info);
return -1;
}

does tripping this indicate the device is spewing garbage(that cgminer is filtering), no spewing anything at all, or something else?

I ask as I am troubleshooting a couple of Habaneros, whom are ridiculously cool at the chip level(850MHz is 86-87C), and yet when set this high will continually trip this and clock down until ~750-767MHz.


EDIT: just made an obervation that prior to the message appearing in CGMiner, the fan on my RM1000 PSU, which is powering one of them, stops spinning indicating that the load completely drops. will investigate if additional VRM cooling is needed. also need to break down and grab a good FLIR cam (or at least an IR thermometer).

cgminer spits out the VRM temperature for each die if you enable debugging or use the API, so you can see what they are. The VRM will shut down if it reaches 90C.

can you show an example line so i know what to be looking for? API and debuglog

yup ended up being something VRM related (though not sure what exactly) cuz with a repositioning into my windowsill with open windows and an outdoor ambient of 1C both my spicy peppers are purring at 950 on all cores.

[MrTeal]

@conman, @Kano: question/input request from you regarding a section of code.


In regards to:

Code:

/* Base the fail time on no valid nonces for 25 full nonce ranges at
* the current expected hashrate. */
fail_time = 25.0 * (double)hashfast->drv->max_diff * 0xffffffffull /
(double)(info->base_clock * 1000000) / hfa_basejobs(info);
if (unlikely(share_work_tdiff(hashfast) > fail_time)) {
applog(LOG_WARNING, "%s %s: No valid hashes for over %.0f seconds, shutting down thread",
      hashfast->drv->name, hashfast->unique_id, fail_time);
hfa_running_shutdown(hashfast, info);
return -1;
}

does tripping this indicate the device is spewing garbage(that cgminer is filtering), no spewing anything at all, or something else?

I ask as I am troubleshooting a couple of Habaneros, whom are ridiculously cool at the chip level(850MHz is 86-87C), and yet when set this high will continually trip this and clock down until ~750-767MHz.


EDIT: just made an obervation that prior to the message appearing in CGMiner, the fan on my RM1000 PSU, which is powering one of them, stops spinning indicating that the load completely drops. will investigate if additional VRM cooling is needed. also need to break down and grab a good FLIR cam (or at least an IR thermometer).

cgminer spits out the VRM temperature for each die if you enable debugging or use the API, so you can see what they are. The VRM will shut down if it reaches 90C.

can you show an example line so i know what to be looking for? API and debuglog

yup ended up being something VRM related (though not sure what exactly) cuz with a repositioning into my windowsill with open windows and an outdoor ambient of 1C both my spicy peppers are purring at 950 on all cores.

In the OP_DIE_STATUS it's the Board Temperature. You might have to update your firmware to support it.

It's a little flaky at extreme temperatures though. For some reason the original HashFast devices supplied an ADC reading for temperature and relied on cgminer to linearize it, so we take the actual temperature and perform the reverse function on it prior to sending it out, and then it gets converted back to a temp. This limits the range of temperatures supported though.

[Taugeran]

In the OP_DIE_STATUS it's the Board Temperature. You might have to update your firmware to support it.

It's a little flaky at extreme temperatures though. For some reason the original HashFast devices supplied an ADC reading for temperature and relied on cgminer to linearize it, so we take the actual temperature and perform the reverse function on it prior to sending it out, and then it gets converted back to a temp. This limits the range of temperatures supported though.

Gotcha. Will look into it this evening

[-ck]

What is the newest software that I can download and flash to my S1

The S1 firmwares generated by the cgminer team are virtually unmaintained due to the hardware's end-of-life status. The last available one was here:
https://github.com/kanoi/cgminer-binaries/blob/master/AntS1/cgminer-ants1-4.3.2a-85fcf0c

[salfter]

New release: Version 4.7.1, 4th November 2014

- Changed the configure build system to make it impossible to build more than one device in if the chosen driver was meant to be used standalone, along with more explicit tagging of standalone drivers in the configure help. This should make it easier to choose a more suitable configuration for distribution packaging.

Is there an option to override this new behavior?  I have had a couple of BFL Jalapeños running off the Raspberry Pi in my Bitfury rig for at least a year now. In recent months, I've been using the Black Arrow Bitfury driver in cgminer; its auto-tune support has been pretty nice, and it works like a champ with BFSB hardware.  Now I'll have to build cgminer twice (once with --enable-bab and again with --enable-bflsc) and run two instances of cgminer, where before a single instance would suffice.

[knowndragon]

  Hey guys I have a question? what does mining on an orphaned block mean?

 [2014-11-20 17:44:30] Block height change to 272530 detected on pool 0
 [2014-11-20 17:44:30] Network diff set to 130K
 [2014-11-20 17:49:27] Block height change to 272531 detected on pool 0
 [2014-11-20 17:49:27] Network diff set to 131K
 [2014-11-20 17:50:19] Block height change to 272532 detected on pool 0
 [2014-11-20 17:50:19] Network diff set to 133K
 [2014-11-20 17:50:50] Block height change to 272533 detected on pool 0
 [2014-11-20 17:50:50] Network diff set to 135K
 [2014-11-20 17:51:09] Block height change to 272534 detected on pool 0
 [2014-11-20 17:51:09] Network diff set to 130K
 [2014-11-20 17:51:59] Mining on orphan branch detected, switching!
 [2014-11-20 17:51:59] Network diff set to 138K

Also cgwatcher isn't showing any getworks and efficiency is at 0.00% now is it mining or is it just running.

[-ck]

Hey guys I have a question? what does mining on an orphaned block mean?

 [2014-11-20 17:44:30] Block height change to 272530 detected on pool 0
 [2014-11-20 17:44:30] Network diff set to 130K
 [2014-11-20 17:49:27] Block height change to 272531 detected on pool 0
 [2014-11-20 17:49:27] Network diff set to 131K
 [2014-11-20 17:50:19] Block height change to 272532 detected on pool 0
 [2014-11-20 17:50:19] Network diff set to 133K
 [2014-11-20 17:50:50] Block height change to 272533 detected on pool 0
 [2014-11-20 17:50:50] Network diff set to 135K
 [2014-11-20 17:51:09] Block height change to 272534 detected on pool 0
 [2014-11-20 17:51:09] Network diff set to 130K
 [2014-11-20 17:51:59] Mining on orphan branch detected, switching!
 [2014-11-20 17:51:59] Network diff set to 138K

Also cgwatcher isn't showing any getworks and efficiency is at 0.00% now is it mining or is it just running.

Firstly, you're mining altcoins which I wouldn't normally provide support for, but your questions are generic enough to deserve their own answer.

Cgminer in solo mining mode goes to great lengths to make sure you're mining on the most current block that your bitcoind knows about, and you have witnessed one of those moments in action where someone near your *coind found a block and informed you that it was the latest block, only to later on have their block orphaned and your bitcoind decided to switch to the other branch as the one true branch. At that time cgminer noticed the block hash changed but the block height did not and informed you it noticed the change. i.e. everything's working fine.

Getworks and efficiency were measures removed from cgminer displays a long time as being irrelevant to modern mining and any wrapper you have such as cgwatcher should also be doing that.

[phillipsjk]

Update: I have decided to try bfgminer instead. If it fails to work, I may install cgminer on a nearby Gnu/Linux machine and run a USB extension cable.

I was curious if anybody has been successful in compiling this for FreeBSD.
[spoiler]

Code:

$ ./configure --enable-blockerupter
checking build system type... amd64-unknown-freebsd9.2
checking host system type... amd64-unknown-freebsd9.2
checking target system type... amd64-unknown-freebsd9.2
checking for a BSD-compatible install... /usr/bin/install -c
checking whether build environment is sane... yes
checking for a thread-safe mkdir -p... ./install-sh -c -d
checking for gawk... no
checking for mawk... no
checking for nawk... nawk
checking whether make sets $(MAKE)... yes
checking whether make supports nested variables... yes
checking whether make supports nested variables... (cached) yes
checking for style of include used by make... GNU
checking for gcc... gcc
checking whether the C compiler works... yes
checking for C compiler default output file name... a.out
checking for suffix of executables...
checking whether we are cross compiling... no
checking for suffix of object files... o
...
checking for windres... no
checking for inline... inline
checking operating system... configure: error: unsupported operating system
configure: error: ./configure failed for compat/libusb-1.0

It says the OS is unsupported. Not sure what kind of porting would be involved.

Code:

$ ./configure --enable-blockerupter --with-system-libusb
checking build system type... amd64-unknown-freebsd9.2
checking host system type... amd64-unknown-freebsd9.2
checking target system type... amd64-unknown-freebsd9.2
checking for a BSD-compatible install... /usr/bin/install -c
checking whether build environment is sane... yes
checking for a thread-safe mkdir -p... ./install-sh -c -d
checking for gawk... no
checking for mawk... no
checking for nawk... nawk
checking whether make sets $(MAKE)... yes
checking whether make supports nested variables... yes
checking whether make supports nested variables... (cached) yes
checking for style of include used by make... GNU
checking for gcc... gcc
checking whether the C compiler works... yes
checking for C compiler default output file name... a.out
checking for suffix of executables...
checking whether we are cross compiling... no
...
checking for gcc __sync builtins... yes
checking for gcc __atomic builtins... no
checking that generated files are newer than configure... done
configure: creating ./config.status
config.status: creating jansson.pc
config.status: creating Makefile
config.status: creating src/Makefile
config.status: creating src/jansson_config.h
config.status: creating config.h
config.status: config.h is unchanged
config.status: executing depfiles commands
config.status: executing libtool commands



------------------------------------------------------------------------
cgminer 4.7.1
------------------------------------------------------------------------



Configuration Options Summary:

  libcurl(GBT+getwork).: Enabled: -L/usr/local/lib -lcurl  
  curses.TUI...........: FOUND: -lncurses

  Antminer.S1.Bitmain..: Disabled
  Antminer.S2.Bitmain..: Disabled
  Avalon.ASICs.........: Disabled
  Avalon2.ASICs........: Disabled
  BlackArrowMinion.ASIC: Disabled
  BlackArrow.ASICs.....: Disabled
  BFL.ASICs............: Disabled
  BitForce.FPGAs.......: Disabled
  BitFury.ASICs........: Disabled
  BlockErupter.ASICs...: Enabled
  Cointerra.ASICs......: Disabled
  Spond-sp10.ASICs.....: Disabled
  Spond-sp30.ASICs.....: Disabled
  Bitmine-A1.ASICs.....: Disabled
  Drillbit.BitFury.....: Disabled
  Hashfast.ASICs.......: Disabled
  Hashratio.ASICs......: Disabled
  Icarus.ASICs/FPGAs...: Disabled
  Klondike.ASICs.......: Disabled
  KnC.ASICs............: Disabled
  ModMiner.FPGAs.......: Disabled

Compilation............: make (or gmake)
  CPPFLAGS.............:
  CFLAGS...............: -g -O2
  LDFLAGS..............:  -lpthread
  LDADD................: -ldl -L/usr/local/lib -lcurl   compat/jansson-2.6/src/.libs/libjansson.a -lpthread    -lm -lusb -lrt

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

$ make
make  all-recursive
Making all in lib
  GEN      arg-nonnull.h
  GEN      c++defs.h
  GEN      warn-on-use.h
  GEN      signal.h
  GEN      stdint.h
  GEN      string.h
make  all-recursive
  CC       dummy.o
  CC       memmem.o
  AR       libgnu.a
Making all in compat
Making all in jansson-2.6
"Makefile", line 860: Need an operator
make: fatal errors encountered -- cannot continue
*** [all-recursive] Error code 1

Stop in /usr/home/P2Pool/cgminer/compat.
*** [all-recursive] Error code 1

Stop in /usr/home/P2Pool/cgminer.
*** [all] Error code 1

Stop in /usr/home/P2Pool/cgminer.

If the full configure output is required, I can redirect it to a file.

Edit: forgot that "make clean" also fails:

Code:

$ make clean
Making clean in lib
test -z "" || rm -f
rm -rf .libs _libs
test -z "libgnu.a" || rm -f libgnu.a
test -z "" || rm -f
rm -f *.o
test -z "core *.stackdump arg-nonnull.h arg-nonnull.h-t  c++defs.h c++defs.h-t signal.h signal.h-t stddef.h stddef.h-t  stdint.h stt
rm -f *.lo
Making clean in compat
Making clean in jansson-2.6
"Makefile", line 860: Need an operator
make: fatal errors encountered -- cannot continue
*** [clean-recursive] Error code 1

Stop in /usr/home/P2Pool/cgminer/compat.
*** [clean-recursive] Error code 1

Stop in /usr/home/P2Pool/cgminer.

Edit2: dug up this advice...testing (rerunning autogen.sh)

It's been a lot of years since I ran FreeBSD, but as I recall, the default 'make' command they use is BSD-specific and not compatible in all ways with the Gnu make that comes with GCC, so you typically have to tell it to use gmake explicitly when using some Gnu make makefiles.  I think if you type 'MAKE=gmake; gmake' it will probably work.

gmake failed as well. (./configure still failed with the same error as above without system-usb)

Code:

gmake
gmake  all-recursive
gmake[1]: Entering directory `/usr/home/P2Pool/cgminer'
Making all in lib
gmake[2]: Entering directory `/usr/home/P2Pool/cgminer/lib'
  GEN      arg-nonnull.h
  GEN      c++defs.h
  GEN      warn-on-use.h
  GEN      signal.h
  GEN      stdint.h
  GEN      string.h
gmake  all-recursive
gmake[3]: Entering directory `/usr/home/P2Pool/cgminer/lib'
gmake[4]: Entering directory `/usr/home/P2Pool/cgminer/lib'
  CC       dummy.o
  CC       memmem.o
  AR       libgnu.a
gmake[4]: Leaving directory `/usr/home/P2Pool/cgminer/lib'
gmake[3]: Leaving directory `/usr/home/P2Pool/cgminer/lib'
gmake[2]: Leaving directory `/usr/home/P2Pool/cgminer/lib'
Making all in compat
gmake[2]: Entering directory `/usr/home/P2Pool/cgminer/compat'
Making all in jansson-2.6
gmake[3]: Entering directory `/usr/home/P2Pool/cgminer/compat/jansson-2.6'
gmake  all-recursive
gmake[4]: Entering directory `/usr/home/P2Pool/cgminer/compat/jansson-2.6'
Making all in src
gmake[5]: Entering directory `/usr/home/P2Pool/cgminer/compat/jansson-2.6/src'
  CC       dump.lo
  CC       error.lo
  CC       hashtable.lo
  CC       load.lo
  CC       memory.lo
  CC       pack_unpack.lo
  CC       strbuffer.lo
  CC       strconv.lo
  CC       value.lo
  CCLD     libjansson.la
gmake[5]: Leaving directory `/usr/home/P2Pool/cgminer/compat/jansson-2.6/src'
gmake[5]: Entering directory `/usr/home/P2Pool/cgminer/compat/jansson-2.6'
gmake[5]: Leaving directory `/usr/home/P2Pool/cgminer/compat/jansson-2.6'
gmake[4]: Leaving directory `/usr/home/P2Pool/cgminer/compat/jansson-2.6'
gmake[3]: Leaving directory `/usr/home/P2Pool/cgminer/compat/jansson-2.6'
gmake[3]: Entering directory `/usr/home/P2Pool/cgminer/compat'
gmake[3]: Nothing to be done for `all-am'.
gmake[3]: Leaving directory `/usr/home/P2Pool/cgminer/compat'
gmake[2]: Leaving directory `/usr/home/P2Pool/cgminer/compat'
Making all in ccan
gmake[2]: Entering directory `/usr/home/P2Pool/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
gmake[2]: Leaving directory `/usr/home/P2Pool/cgminer/ccan'
gmake[2]: Entering directory `/usr/home/P2Pool/cgminer'
  CC       cgminer-cgminer.o
In file included from ./sha2.h:36,
                 from cgminer.c:52:
./miner.h:50:1: warning: "alloca" redefined
In file included from cgminer.c:19:
/usr/include/stdlib.h:246:1: warning: this is the location of the previous definition
gcc: -lpthread: linker input file unused because linking not done
  CC       cgminer-util.o
In file included from util.c:42:
miner.h:50:1: warning: "alloca" redefined
In file included from util.c:14:
/usr/include/stdlib.h:246:1: warning: this is the location of the previous definition
gcc: -lpthread: linker input file unused because linking not done
  CC       cgminer-sha2.o
In file included from sha2.h:36,
                 from sha2.c:37:
miner.h:50:1: warning: "alloca" redefined
In file included from ./compat/jansson-2.6/src/jansson.h:12,
                 from miner.h:10,
                 from sha2.h:36,
                 from sha2.c:37:
/usr/include/stdlib.h:246:1: warning: this is the location of the previous definition
gcc: -lpthread: linker input file unused because linking not done
  CC       cgminer-api.o
In file included from api.c:25:
miner.h:50:1: warning: "alloca" redefined
In file included from api.c:16:
/usr/include/stdlib.h:246:1: warning: this is the location of the previous definition
api.c: In function 'mcast':
api.c:4717: error: 'IPV6_ADD_MEMBERSHIP' undeclared (first use in this function)
api.c:4717: error: (Each undeclared identifier is reported only once
api.c:4717: error: for each function it appears in.)
gmake[2]: *** [cgminer-api.o] Error 1
gmake[2]: Leaving directory `/usr/home/P2Pool/cgminer'
gmake[1]: *** [all-recursive] Error 1
gmake[1]: Leaving directory `/usr/home/P2Pool/cgminer'
gmake: *** [all] Error 2

Edit: More hints...

Hi,

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

Code:

SNIP!

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.

Point 1 appears to be a "no". There is a cpuminer in /usr/ports/net-p2p/cpuminer
find was not accepting wildcards, so did not check other categories. (The ports list on the website appears
to miss some: like bitcoin-daemon.)

I suppose I should try point 2.
Edit3:

Code:

$ ./cgminer -o 192.168.243.2:9332
ELF binary type "0" not known.
./cgminer: Exec format error

--looks like I actually need to install Linux binary compatibility.
--Appears to be fedora 10
Tried without installing Linux base-system (based on these instructions).

Code:

root@casey:~ # kldload linux
root@casey:~ # kldstat
Id Refs Address            Size     Name
 1   11 0xffffffff80200000 15b9440  kernel
 2    1 0xffffffff81812000 10d97    geom_eli.ko
 3    1 0xffffffff81823000 1efc1    crypto.ko
 4    1 0xffffffff81842000 57bcf    linux.ko
root@casey:~ # su P2Pool
$ cd
$ cd cgminer-4.7.1-x86_64-built
$ ./cgminer -o 192.168.243.2:9332
ELF binary type "0" not known.
./cgminer: Exec format error
$ brandelf -t Linux cgminer
$ ./cgminer -o 192.168.243.2:9332
ELF binary type "3" not known.
./cgminer: Exec format error

Did not appear to work even installing the fedora package:

Code:

root@casey:~ # pkg install linux_base-f10-10_7
Updating FreeBSD repository catalogue...
FreeBSD repository is up-to-date.
All repositories are up-to-date.
The following 1 packages will be affected (of 0 checked):

New packages to be INSTALLED:
        linux_base-f10: 10_7

The process will require 134 MB more space.
16 MB to be downloaded.

Proceed with this action? [y/N]: y
Fetching linux_base-f10-10_7.txz: 100%   16 MB   2.9M/s    00:06    
Checking integrity... done (0 conflicting)
[1/1] Installing linux_base-f10-10_7: 100%

+++ Some programs may need linprocfs, please add it to /etc/fstab! +++

Running linux ldconfig...
root@casey:~ # su P2Pool
$ cd
$ cd cgminer-4.7.1-x86_64-built
$ ./cgminer -o 192.168.243.2:9332
ELF binary type "3" not known.
./cgminer: Exec format error
$ brandelf -t Linux cgminer
$ ./cgminer -o 192.168.243.2:9332
ELF binary type "3" not known.
./cgminer: Exec format error

Edit4: does the 2.9.1 changelog mean anything?

- Changes to build prototypes to support building on FreeBSD 9.1-RC2 amd64

YAEdit: I wonder if the Linux binary compatibility only works for 32 bit binaries.

Base set of packages needed in Linux mode for i386/amd64 (Linux Fedora 10)

..so should work with amd64
[/spoiler]

[-ck]

Edit4: does the 2.9.1 changelog mean anything?

- Changes to build prototypes to support building on FreeBSD 9.1-RC2 amd64

That should be the most telling quote for you, no? It's the last time anyone pushed any changes for 'bsd support into cgminer and it has since moved further and further away from being code compatible, so unless you or someone else is interested in sitting down and doing patches for it as some kind of (large) project, it has no chance of compiling. I'm not even sure of the status of freebsd support in libusb which is pivotal to running most modern mining equipment.

[-ck]

Okay here goes. Even though I don't have the U3 yet, bitmainUSA let me work on one remotely in the interim so I've merged my own U3 driver into the main cgminer git master and it is now available for testing.

Note the following changes:
You do not need to specify ANY command line parameters to run the U3 (no weird options, timeouts or frequency or voltage required) for it to run at default voltage and frequency.
The default frequency is set to 225Mhz
The default voltage is set to 750mV

In addition, the following parameters are recognised, though the defaults are obviously safest.

Code:

--au3-freq <arg>    Set AntminerU3 frequency in MHz, range 100-250 (default: 225.0)
--au3-volt <arg>    Set AntminerU3 voltage in mv, range 725-850, 0 to not set (default: 750)

In addition, I have a test windows binary:
http://ck.kolivas.org/apps/cgminer/temp/cgminer.exe

Of course this is all new code but so far it's looking stable, but I'm unable to test the windows binary myself.

[GrrOucH]

It does work. Picks up the U3 just fine. I think I have a bad us though. With the defaults you have it will only hash at about 43gh. I have not tried to play with the volt/freq settings because I would like to think the defaults should wrk. Thanks for getting it working without all those nasty settings.

[-ck]

It does work. Picks up the U3 just fine. I think I have a bad us though. With the defaults you have it will only hash at about 43gh. I have not tried to play with the volt/freq settings because I would like to think the defaults should wrk. Thanks for getting it working without all those nasty settings.

Try the latest git or binary if you haven't updated recently. The last update was only about 12 hours ago.

[GrrOucH]

what is the --enable flag for the u3?

[-ck]

what is the --enable flag for the u3?

--enable-icarus
though you only use that when building your own binary...