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

[kano]

Actually, yes. If I wanted to know how many diff1 shares I've submitted, I would multiply. To me, and some others looking back on this thread, the new information is useless and alarming.

So what exactly would you multiply by?
You have to know the diff1 total, divide it by the old A ... and that answer you can multiply by the old A to get the diff1 total
... So yeah you can multiply as long as you already know the answer ...
You see ... not every share is the same diff ................

[twmz]

I just fetched the latest CGMiner, and oh, god, what happened to the share logging? Please change it back.

If you mean A: and R: (and WU:) no it will not be changed back to displaying meaningless information

It was very much meaningful information. It told me how many shares I have submitted.

So let me get this straight, rather than have it tell you how much work you've done that the pool will reward you for, you want a variable on the screen from the cpu mining era of diff1 shares that today correlates with absolutely nothing at all unless you happen to mine on one of the last remaining pools that accepts diff1 shares, in which case the result is equal to what's shown in the current cgminer anyway?

I like it the way it is now.  Please don't change it back.

[kano]

Actually, yes. If I wanted to know how many diff1 shares I've submitted, I would multiply. To me, and some others looking back on this thread, the new information is useless and alarming.

So what exactly would you multiply by?
You have to know the diff1 total, divide it by the old A ... and that answer you can multiply by the old A to get the diff1 total
... So yeah you can multiply as long as you already know the answer ...
You see ... not every share is the same diff ................

I know not every share is the same diff, but CGMiner shows the share diff on the screen.

No - it shows the current share diff target.
That changes.

[kano]

Actually, yes. If I wanted to know how many diff1 shares I've submitted, I would multiply. To me, and some others looking back on this thread, the new information is useless and alarming.

So what exactly would you multiply by?
You have to know the diff1 total, divide it by the old A ... and that answer you can multiply by the old A to get the diff1 total
... So yeah you can multiply as long as you already know the answer ...
You see ... not every share is the same diff ................

I know not every share is the same diff, but CGMiner shows the share diff on the screen.

No - it shows the current share diff target.
That changes.

Only with VARDIFF.

What pool doesn't?
If not - then use a proper pool

[os2sam]

FWIW, I've not been able to run a version of CGMiner higher than 3.3.1 for longer than 48 hours driving Erupter USB's on Windows 7 64 bit or Windows 8 64 bit. 3.4.0 just died on me across two rigs.

Any version that uses the new USB drivers eventually crashes on me with mwsock.dll causing the error under Windows

Have there been other reports of this perchance ?

Yeah, same here.. same setup (Win7 64bit).. never really checked the crash/dump though to confirm that dll.

I got this, this morning as well.  Win7 64 bit.

In my case I was running 4 instances and the three Stratum crashed and the one Getwork was still working.

Don't know if that means anything?

[kano]

Actually, yes. If I wanted to know how many diff1 shares I've submitted, I would multiply. To me, and some others looking back on this thread, the new information is useless and alarming.

So what exactly would you multiply by?
You have to know the diff1 total, divide it by the old A ... and that answer you can multiply by the old A to get the diff1 total
... So yeah you can multiply as long as you already know the answer ...
You see ... not every share is the same diff ................

I know not every share is the same diff, but CGMiner shows the share diff on the screen.

No - it shows the current share diff target.
That changes.

Only with VARDIFF.

What pool doesn't?
If not - then use a proper pool

http://middlecoin.com/

Lulz a random altcoin pool

[-ck]

New release: Version 3.4.12, 1st September 2013

Happy Father's day (in Australia, dunno about rest of the world). Big changes to the build process, read changelog for details. If building from git, make sure to do make clean and ./autogen.sh before attempting to build the significantly changed build process. Sorry I can't provide avalon firmware now since I went to push the reset button on my avalon and instead of it pressing it broke off... so I don't trust myself to make untested brickwarefirmware as I just mine on it via a USB cable to my PC now.

EDIT: 3.4.2 released shortly after with hotfix for crash on BFLSC


Human readable changelog:

3.4.2:
- Fixed crash with BFLSC hardware.
- Added ability to put arbitrary values in miner.php

3.4.1:
- Libusb and jansson have  both been updated to the latest version and are now part of the build tree.
- Libusb and jansson will both be built into the binary statically so all binaries will include the latest version of these libraries, avoiding the problems associated with older versions.
- There is no need for libusb dev or jansson dev to be installed when compiling cgminer now.
- Linux users will now need to install libudev dev to build for any usb devices.
- API muticast listener option --api-mcast so you can request all cgminer APIs on the local network to identify themselves on request
- Also a new $mcast option in miner.php to automatically find all your cgminers that are using the --api-mcast option and related sample Java code MCast.java/MCast.class
- New Icarus timing limit option for short and long timing, that can be set appropriately to ensure no device idle time if timing estimates the timeout badly
- Bugfixes for numerous causes of corruption/crashes in stratum, usb, avalon and bflsc code.
- Some rare errors in BFLSC messages were being ignored, they should now show up.
- Fixed the broken OSX build from 3.4.0, but so many things were changed after that in the build process that it may be broken again.
- Some hardware errors were being counted in diff1shares in avalon code leading to a mismatch of diff1 vs diffa+diffr. This has been corrected, but it will make the hardware error percentage look higher (though the actual amount will not have changed).
- Maximum avalon frequency is now 1000 instead of 450 since some overclockers have pushed beyond 450.
- Use higher resolution timers consistently on windows now.


Full changelog:

3.4.2:
- take_queued_work_bymidstate should use a write lock.
- miner.php coding warning
- miner.php disable 'gen' by default
- miner.php allow formula generation of new fields
- miner.php add doctype
- miner.php remove incorrect echo
- miner.php optional error if not enough mcast rigs are found

3.4.1:
- API mcast add a description option with miner.php
- Always use a maxpacketsize buffer in usb_bulk_transfer
- bflsc ensure getinfo cannot overflow its storage buffer
- Don't decref json values in stratum parsing due to memory corruption.
- Use 64 bytes for all libusb control transfers.
- Skip dissecting opt->names in parse_config if it doesn't exist.
- Use an internal buffer in _usb_transfer_read in case the read is larger than
the buffer passed to it.
- ICA optional limit timing with short=N or long=N
- Revert to old custom tolines function since strtok_r is not portable.
- bflsc remove unused commented out code
- logging - code mistake
- logging - applogsiz() for large messages
- Provide base structures for getaddrinfo.
- Include string.h in bflsc driver.
- Get rid of linear removal of spaces in bflsc text parsing and use strstr
throughout instead.
- Use reentrant strtok in tolines() function in bflsc to avoid racing on
contextless calls.
- Show how small a too small result in bflsc is.
- Duplicate the buffer in process_results in bflsc since strtok modifies it
making debugging output limited to one line.
- Only process nonces in bflsc if the breakdown function succeeds.
- Ignore zero count messages in bflsc instead of trying to parse them.
- Return ok in tolines when it doesn't match inprocess message for bflsc.
- Remove inprocess line instead of deleting all following responses in bflsc.
- Change ok testing logic in breakdown() in bflsc and return if not ok at any
stage.
- Check the return value of tolines in bflsc driver.
- Use strtok to parse lines in bflsc driver.
- Add libusb-1.0 m4 directory and gitignore file.
- Properly convert from ranlib to lt_init in configure.ac
- Make autoconf always build for libusb.
- More autoconf fixes.
- Unconditionally build jansson statically from the cgminer source tree.
- Only test for all usb devices once in configure.ac
- Fix various libusb warnings and possible bugs on linux build.
- Add make clean and maintainer-clean to autogen
- Remove examples from libusb Makefile and generated autoconf files.
- Fix libusb subdirectory builds.
- Remove cached files from libusb autoconf on running autogen.sh
- Remove unused HAVE_LISBUSB macro and use USE_USBUTILS everywhere.
- Use direct auto* files to avoid failure of autoreconf
- Remove unused and maintainer cleaned files
- Show RT_LIBS in ./configure output.
- First import of libusb-1.0
- bflsc xlinkstr use snprintf
- Fix win32 build.
- Use take_queued_work_bymidstate in the bflsc driver to avoid the rare chance
repeated results come back from the same work item.
- Provide a function that looks up queued work by midstate and then removes it
from the device hash database.
- Fix no -rt library on darwin.
- Update included jansson to v2.4
- Fix OSX build.
- Provide an osx fix for cgtimers and a fallback to timevals for all other
platforms !linux !win32 !osx.
- Move two more timer functions out of define macros to enable them to be used
by future osx code.
- cgtimer_sub is now the same since cgtimer_t should be the same on all
platforms.
- miner.php fix missing global
- Only count submitted nonces as diff1shares if they're valid.
- Substantially raise the maximum avalon frequency for water-cooled, over-volted
designs.
- Compile MCast.java with an old java
- API Multicast sample MCast.java+MCast.class
- BTB show C/MHz/mV for device
- api.c remove unused reply string
- api.c fix mcast debug message bug
- miner.php implement API Multicast handling to automatically find your local
net miners
- API mcast only reply to remote IP's that are allowed access
- Initial API Multicast response v0.1 to find cgminer APIs
- Use timespecs on windows as cgtimer_t to capitalise on the higher resolution
clock changes.
- Abstract out the conversion of system time to an lldiv_t in decimicroseconds.
- Use our own gettimeofday implementation on windows for it to be consistent
across ming builds and higher resolution.

[kano]

FWIW, I've not been able to run a version of CGMiner higher than 3.3.1 for longer than 48 hours driving Erupter USB's on Windows 7 64 bit or Windows 8 64 bit. 3.4.0 just died on me across two rigs.

Any version that uses the new USB drivers eventually crashes on me with mwsock.dll causing the error under Windows

Have there been other reports of this perchance ?

Yeah, same here.. same setup (Win7 64bit).. never really checked the crash/dump though to confirm that dll.

I got this, this morning as well.  Win7 64 bit.

In my case I was running 4 instances and the three Stratum crashed and the one Getwork was still working.

Don't know if that means anything?

Try 3.4.1

[nwoolls]

Big changes to the build process, read changelog for details. If building from git, make sure to do make clean and ./autogen.sh before attempting to build the significantly changed build process.

I am trying to compile from the Git source on OS X. I am cloning into a brand new, clean directory. From there I autogen.sh like I always have, and I get an error:

Code:

checking that generated files are newer than configure... done
configure: creating ./config.status
config.status: error: cannot find input file: `Makefile.in'

I've tried using autoconf and automake as the readme file suggests under the "Build cgminer for yourself" but that does not help. I have also tried doing make clean but there is no target for 'clean' as nothing has been configured or build yet.

[-ck]

Big changes to the build process, read changelog for details. If building from git, make sure to do make clean and ./autogen.sh before attempting to build the significantly changed build process.

I am trying to compile from the Git source on OS X. I am cloning into a brand new, clean directory. From there I autogen.sh like I always have, and I get an error:

Code:

checking that generated files are newer than configure... done
configure: creating ./config.status
config.status: error: cannot find input file: `Makefile.in'

I've tried using autoconf and automake as the readme file suggests under the "Build cgminer for yourself" but that does not help. I have also tried doing make clean but there is no target for 'clean' as nothing has been configured or build yet.

- Fixed the broken OSX build from 3.4.0, but so many things were changed after that in the build process that it may be broken again.

Try a release tarball instead of building from git, but I can't guarantee anything on OSX.
If that fails, the last known good release for osx on git was
git checkout 036c7b73f1244e52a8aedf3990ecf862d03310f4

[nwoolls]

Try a release tarball instead of building from git, but I can't guarantee anything on OSX.
If that fails, the last known good release for osx on git was
git checkout 036c7b73f1244e52a8aedf3990ecf862d03310f4

It's not really a problem of finding a compatible version. I release both Homebrew formulas and precompiled binaries for OS X and haven't been able to provide users with either 3.4.0 or 3.4.1. I am fine with telling my users they have to use an old version of cgminer or use the newest version of some other miner.

Here is more error info, which may help pinpoint the issue:

Code:

configure.ac:39: error: required file '../../ltmain.sh' not found
libusb/Makefile.am:4: warning: source file 'os/darwin_usb.c' is in a subdirectory,
libusb/Makefile.am:4: but option 'subdir-objects' is disabled
automake: warning: possible forward-incompatibility.
automake: At least a source file is in a subdirectory, but the 'subdir-objects'
automake: automake option hasn't been enabled.  For now, the corresponding output
automake: object file(s) will be placed in the top-level directory.  However,
automake: this behaviour will change in future Automake versions: they will
automake: unconditionally cause object files to be placed in the same subdirectory
automake: of the corresponding sources.
automake: You are advised to start using 'subdir-objects' option throughout your
automake: project, to avoid future incompatibilities.
libusb/Makefile.am:3: warning: source file 'os/linux_usbfs.c' is in a subdirectory,
libusb/Makefile.am:3: but option 'subdir-objects' is disabled
libusb/Makefile.am:33: warning: source file 'os/linux_netlink.c' is in a subdirectory,
libusb/Makefile.am:33: but option 'subdir-objects' is disabled
libusb/Makefile.am:33: warning: source file 'os/linux_udev.c' is in a subdirectory,
libusb/Makefile.am:33: but option 'subdir-objects' is disabled
libusb/Makefile.am:5: warning: source file 'os/openbsd_usb.c' is in a subdirectory,
libusb/Makefile.am:5: but option 'subdir-objects' is disabled
libusb/Makefile.am:6: warning: source file 'os/poll_windows.c' is in a subdirectory,
libusb/Makefile.am:6: but option 'subdir-objects' is disabled
libusb/Makefile.am:6: warning: source file 'os/windows_usb.c' is in a subdirectory,
libusb/Makefile.am:6: but option 'subdir-objects' is disabled
libusb/Makefile.am:42: warning: source file 'os/threads_windows.c' is in a subdirectory,
libusb/Makefile.am:42: but option 'subdir-objects' is disabled
libusb/Makefile.am:42: warning: source file 'os/threads_posix.c' is in a subdirectory,
libusb/Makefile.am:42: but option 'subdir-objects' is disabled
autoreconf: automake failed with exit status: 1

[nwoolls]

Try a release tarball instead of building from git, but I can't guarantee anything on OSX.

Here's the error compiling from the release tarball:

Code:

  CCLD   cgminer
Undefined symbols for architecture x86_64:
  "_CFDictionaryCreateMutable", referenced from:
      _darwin_init in libusb-1.0.a(libusb_1_0_la-darwin_usb.o)
  "_CFDictionarySetValue", referenced from:
      _darwin_init in libusb-1.0.a(libusb_1_0_la-darwin_usb.o)
  "_CFGetTypeID", referenced from:
      _darwin_devices_detached in libusb-1.0.a(libusb_1_0_la-darwin_usb.o)
  "_CFNumberCreate", referenced from:
      _darwin_init in libusb-1.0.a(libusb_1_0_la-darwin_usb.o)
  "_CFNumberGetTypeID", referenced from:
      _darwin_devices_detached in libusb-1.0.a(libusb_1_0_la-darwin_usb.o)
  "_CFNumberGetValue", referenced from:
      _darwin_get_interface in libusb-1.0.a(libusb_1_0_la-darwin_usb.o)
      _darwin_devices_detached in libusb-1.0.a(libusb_1_0_la-darwin_usb.o)
  "_CFRelease", referenced from:
      _darwin_get_interface in libusb-1.0.a(libusb_1_0_la-darwin_usb.o)
      _darwin_kernel_driver_active in libusb-1.0.a(libusb_1_0_la-darwin_usb.o)
      _darwin_release_interface in libusb-1.0.a(libusb_1_0_la-darwin_usb.o)
      _darwin_close in libusb-1.0.a(libusb_1_0_la-darwin_usb.o)
      _darwin_init in libusb-1.0.a(libusb_1_0_la-darwin_usb.o)
      _darwin_event_thread_main in libusb-1.0.a(libusb_1_0_la-darwin_usb.o)
      _darwin_devices_detached in libusb-1.0.a(libusb_1_0_la-darwin_usb.o)
      ...
  "_CFRetain", referenced from:
      _darwin_open in libusb-1.0.a(libusb_1_0_la-darwin_usb.o)
      _darwin_event_thread_main in libusb-1.0.a(libusb_1_0_la-darwin_usb.o)
  "_CFRunLoopAddSource", referenced from:
      _darwin_claim_interface in libusb-1.0.a(libusb_1_0_la-darwin_usb.o)
      _darwin_open in libusb-1.0.a(libusb_1_0_la-darwin_usb.o)
      _darwin_event_thread_main in libusb-1.0.a(libusb_1_0_la-darwin_usb.o)
  "_CFRunLoopGetCurrent", referenced from:
      _darwin_event_thread_main in libusb-1.0.a(libusb_1_0_la-darwin_usb.o)
  "_CFRunLoopRemoveSource", referenced from:
      _darwin_release_interface in libusb-1.0.a(libusb_1_0_la-darwin_usb.o)
      _darwin_close in libusb-1.0.a(libusb_1_0_la-darwin_usb.o)
      _darwin_event_thread_main in libusb-1.0.a(libusb_1_0_la-darwin_usb.o)
  "_CFRunLoopRun", referenced from:
      _darwin_event_thread_main in libusb-1.0.a(libusb_1_0_la-darwin_usb.o)
  "_CFRunLoopStop", referenced from:
      _darwin_exit in libusb-1.0.a(libusb_1_0_la-darwin_usb.o)
  "_CFUUIDGetConstantUUIDWithBytes", referenced from:
      _darwin_claim_interface in libusb-1.0.a(libusb_1_0_la-darwin_usb.o)
      _usb_get_next_device in libusb-1.0.a(libusb_1_0_la-darwin_usb.o)
  "_CFUUIDGetUUIDBytes", referenced from:
      _darwin_claim_interface in libusb-1.0.a(libusb_1_0_la-darwin_usb.o)
      _usb_get_next_device in libusb-1.0.a(libusb_1_0_la-darwin_usb.o)
  "_IOCreatePlugInInterfaceForService", referenced from:
      _darwin_claim_interface in libusb-1.0.a(libusb_1_0_la-darwin_usb.o)
      _usb_get_next_device in libusb-1.0.a(libusb_1_0_la-darwin_usb.o)
  "_IOIteratorIsValid", referenced from:
      _usb_get_next_device in libusb-1.0.a(libusb_1_0_la-darwin_usb.o)
  "_IOIteratorNext", referenced from:
      _darwin_get_interface in libusb-1.0.a(libusb_1_0_la-darwin_usb.o)
      _process_new_device in libusb-1.0.a(libusb_1_0_la-darwin_usb.o)
      _usb_get_next_device in libusb-1.0.a(libusb_1_0_la-darwin_usb.o)
      _darwin_event_thread_main in libusb-1.0.a(libusb_1_0_la-darwin_usb.o)
      _darwin_devices_detached in libusb-1.0.a(libusb_1_0_la-darwin_usb.o)
  "_IONotificationPortCreate", referenced from:
      _darwin_event_thread_main in libusb-1.0.a(libusb_1_0_la-darwin_usb.o)
  "_IONotificationPortDestroy", referenced from:
      _darwin_event_thread_main in libusb-1.0.a(libusb_1_0_la-darwin_usb.o)
  "_IONotificationPortGetRunLoopSource", referenced from:
      _darwin_event_thread_main in libusb-1.0.a(libusb_1_0_la-darwin_usb.o)
  "_IOObjectRelease", referenced from:
      _darwin_get_interface in libusb-1.0.a(libusb_1_0_la-darwin_usb.o)
      _darwin_kernel_driver_active in libusb-1.0.a(libusb_1_0_la-darwin_usb.o)
      _darwin_claim_interface in libusb-1.0.a(libusb_1_0_la-darwin_usb.o)
      _process_new_device in libusb-1.0.a(libusb_1_0_la-darwin_usb.o)
      _usb_get_next_device in libusb-1.0.a(libusb_1_0_la-darwin_usb.o)
      _darwin_init in libusb-1.0.a(libusb_1_0_la-darwin_usb.o)
      _darwin_event_thread_main in libusb-1.0.a(libusb_1_0_la-darwin_usb.o)
      ...
  "_IORegistryEntryCreateCFProperty", referenced from:
      _darwin_get_interface in libusb-1.0.a(libusb_1_0_la-darwin_usb.o)
      _darwin_kernel_driver_active in libusb-1.0.a(libusb_1_0_la-darwin_usb.o)
      _darwin_devices_detached in libusb-1.0.a(libusb_1_0_la-darwin_usb.o)
  "_IOServiceAddMatchingNotification", referenced from:
      _darwin_event_thread_main in libusb-1.0.a(libusb_1_0_la-darwin_usb.o)
  "_IOServiceGetMatchingServices", referenced from:
      _darwin_init in libusb-1.0.a(libusb_1_0_la-darwin_usb.o)
  "_IOServiceMatching", referenced from:
      _darwin_init in libusb-1.0.a(libusb_1_0_la-darwin_usb.o)
      _darwin_event_thread_main in libusb-1.0.a(libusb_1_0_la-darwin_usb.o)
  "___CFConstantStringClassReference", referenced from:
      CFString in libusb-1.0.a(libusb_1_0_la-darwin_usb.o)
      CFString in libusb-1.0.a(libusb_1_0_la-darwin_usb.o)
      CFString in libusb-1.0.a(libusb_1_0_la-darwin_usb.o)
      CFString in libusb-1.0.a(libusb_1_0_la-darwin_usb.o)
  "_kCFAllocatorDefault", referenced from:
      _darwin_get_interface in libusb-1.0.a(libusb_1_0_la-darwin_usb.o)
      _darwin_kernel_driver_active in libusb-1.0.a(libusb_1_0_la-darwin_usb.o)
      _darwin_init in libusb-1.0.a(libusb_1_0_la-darwin_usb.o)
      _darwin_devices_detached in libusb-1.0.a(libusb_1_0_la-darwin_usb.o)
  "_kCFAllocatorSystemDefault", referenced from:
      _usb_get_next_device in libusb-1.0.a(libusb_1_0_la-darwin_usb.o)
  "_kCFRunLoopCommonModes", referenced from:
      _darwin_open in libusb-1.0.a(libusb_1_0_la-darwin_usb.o)
  "_kCFRunLoopDefaultMode", referenced from:
      _darwin_release_interface in libusb-1.0.a(libusb_1_0_la-darwin_usb.o)
      _darwin_claim_interface in libusb-1.0.a(libusb_1_0_la-darwin_usb.o)
      _darwin_close in libusb-1.0.a(libusb_1_0_la-darwin_usb.o)
      _darwin_event_thread_main in libusb-1.0.a(libusb_1_0_la-darwin_usb.o)
  "_kCFTypeDictionaryKeyCallBacks", referenced from:
      _darwin_init in libusb-1.0.a(libusb_1_0_la-darwin_usb.o)
  "_kCFTypeDictionaryValueCallBacks", referenced from:
      _darwin_init in libusb-1.0.a(libusb_1_0_la-darwin_usb.o)
  "_kIOMasterPortDefault", referenced from:
      _darwin_init in libusb-1.0.a(libusb_1_0_la-darwin_usb.o)
      _darwin_event_thread_main in libusb-1.0.a(libusb_1_0_la-darwin_usb.o)
  "_objc_registerThreadWithCollector", referenced from:
      _darwin_event_thread_main in libusb-1.0.a(libusb_1_0_la-darwin_usb.o)
ld: symbol(s) not found for architecture x86_64
collect2: ld returned 1 exit status
make[2]: *** [cgminer] Error 1
make[1]: *** [all-recursive] Error 1
make: *** [all] Error 2

[crazyates]

CGMiner seems to be randomly closing. I'm running cgminer-nogpu on Win 8x64 with a BFL Little Single and 2 AMUs. It runs in a batch file that loops, and the batch file keeps restarting it, so it is closing nicely, and I haven't lost any downtime. I think it's done it about 4-5 times since I updated to 3.4.0, which was about 8 days ago? The newest one was this morning, after I had left for work. It had been running for about 2 days solid before that.

It never did this before. The AMUs are pretty new. Is it the AMUs causing it, or upgrading to 3.4.0, or both?

Hard to know without excluding one thing at a time? Try running the AMUs in their own instance and see if one the other or both crashes? Also there are debug builds which would help me find out where it's crashing and fix it.
http://ck.kolivas.org/apps/cgminer/debug/

I ran 2 instances of CGMiner-nogpu like you suggested, one with 2 SC Single (1x 30GH + 1x 60GH), and one with 2 AMUs. The instance with the 2 BFL miners was the one that crashed. I didn't see it happened, as it was about 45 minutes ago, but again my batch file seems to have restarted it. I'll try 3.4.1 and see if anything changed.

[kano]

3.4.1a 3.4.1 recompiled on:
Fedora 18
64 bit xubuntu 11.04 (should also work on Fedora 16 and 17)
RPi 32bit Arch
RPi 32bit Raspbian

e.g. to get the 64 bit xubuntu 11.04 binary:
wget https://github.com/kanoi/cgminer-binaries/raw/master/Ubuntu_11.04_x86_64/cgminer-3.4.1a
chmod +x cgminer-3.4.1a

The 3 others are:
https://github.com/kanoi/cgminer-binaries/raw/master/Fedora18_x86_64/cgminer-3.4.1a
https://github.com/kanoi/cgminer-binaries/raw/master/RPi_Arch/cgminer-3.4.1a
https://github.com/kanoi/cgminer-binaries/raw/master/RPi_Raspbian/cgminer-3.4.1a

The Xubuntu configure option (with GPU and scrypt):
CFLAGS="-g -W -Wall" ./autogen.sh --enable-bflsc --enable-icarus --enable-bitforce --enable-modminer --enable-ztex --enable-avalon --enable-scrypt

The rest are USB only (no GPU):
CFLAGS="-g -W -Wall" ./autogen.sh --enable-bflsc --enable-icarus --enable-bitforce --enable-modminer --enable-ztex --enable-avalon

The -g (instead of -O2) means it's a debug build so if anyone finds a problem and has core dumps enabled, it will dump a much more useful debug core.

Note I have binary folders of ckolivas official release files in my binaries git also, for if you can't get to his downloads
To get them you select the folder (e.g. 3.4.1) then click on the file you want then right-click save-as the "View Raw" link.

Important: Read README, ASIC-README or FPGA-README about USB configuration on linux and windows

[bo122081]

My miner is having a fairly annoying problem and I have no idea of the reason or solution.
Every couple hours, I get

Code:

[2013-08-31 13:54:18] Attempting to restart cgminer 3.4.0

in the log, then the miner slows down to around 1/5th of it's usual speed, the fans start randomly changing speeds, almost no work is produced, and cgminer becomes nearly unresponsive in some cases.

What is going on? I don't see any errors being produced, nothing's overheating. It just randomly 'attempts to restart' and then stops working right.

[vapourminer]

Hi

longtime happy cgminer user here.

been running under win xp/vista/7 with great results on GPU and now ASICs.

now Im going to use a laptop I got from work so I can retire the old power hog P4/XP rig running the ASICs currently. the laptop has an intel t6600 CPU (dual core 2.2 Ghz) with 2 gigs RAM, 500 gig HD. huge overkill but it was free

HD was wiped and Im going to install *nix. just not sure which flavor.

currently have a bfl single, bfl jalapeño, and it will have a block erupter on it soon as well. it will mine BTC 24/7.

Im thinking of ubuntu 13.04 as Im somewhat familiar with it, although Ive never run cgminer on it. might even go with dual boot if its easier, ubuntu 13.04 off the HD for occasional non mining and something else via USB flash drive for mining.

any suggestions?

[Krak]

Hi

longtime happy cgminer user here.

been running under win xp/vista/7 with great results on GPU and now ASICs.

now Im going to use a laptop I got from work so I can retire the old power hog P4/XP rig running the ASICs currently. the laptop has an intel t6600 CPU (dual core 2.2 Ghz) with 2 gigs RAM, 500 gig HD. huge overkill but it was free

HD was wiped and Im going to install *nix. just not sure which flavor.

currently have a bfl single, bfl jalapeño, and it will have a block erupter on it soon as well. it will mine BTC 24/7.

Im thinking of ubuntu 13.04 as Im somewhat familiar with it, although Ive never run cgminer on it. might even go with dual boot if its easier, ubuntu 13.04 off the HD for occasional non mining and something else via USB flash drive for mining.

any suggestions?

I used Ubuntu for all my mining until I got my Pi and it's always been great for me. Can't really go wrong with it.

[-ck]

CGMiner seems to be randomly closing. I'm running cgminer-nogpu on Win 8x64 with a BFL Little Single and 2 AMUs. It runs in a batch file that loops, and the batch file keeps restarting it, so it is closing nicely, and I haven't lost any downtime. I think it's done it about 4-5 times since I updated to 3.4.0, which was about 8 days ago? The newest one was this morning, after I had left for work. It had been running for about 2 days solid before that.

It never did this before. The AMUs are pretty new. Is it the AMUs causing it, or upgrading to 3.4.0, or both?

Hard to know without excluding one thing at a time? Try running the AMUs in their own instance and see if one the other or both crashes? Also there are debug builds which would help me find out where it's crashing and fix it.
http://ck.kolivas.org/apps/cgminer/debug/

I ran 2 instances of CGMiner-nogpu like you suggested, one with 2 SC Single (1x 30GH + 1x 60GH), and one with 2 AMUs. The instance with the 2 BFL miners was the one that crashed. I didn't see it happened, as it was about 45 minutes ago, but again my batch file seems to have restarted it. I'll try 3.4.1 and see if anything changed.

It won't debug anything unless you install the debugger as described in the debug readme in there. Anyway see how you go with 3.4.1, I found a few places that could lead to crashes that I fixed in that version. I will also update the debug binaries to be 3.4.1

[Jriker1]

Primary cgminer binary download site down. Git repo won't allow downloading of files either right now.

FYI

[-ck]

Primary cgminer binary download site down. Git repo won't allow downloading of files either right now.

FYI

Down for maintenance yet again. There is an alternate download location listed in the opening post.