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

[-ck]

ck.kolivas.org is down :/ mirror needed

Again, to repeat.
Opening post, mirror of files.

[TwinTurbo]

ck.kolivas.org is down :/ mirror needed

Again, to repeat.
Opening post, mirror of files.

That mirror doesn't contain the compiled avalon firmwares though does it?

[kano]

ck.kolivas.org is down :/ mirror needed

Again, to repeat.
Opening post, mirror of files.

That mirror doesn't contain the compiled avalon firmwares though does it?

I don't have an Avalon so I don't have the binaries ... and I don't want an Avalon either

I do have 20 Avalon chips on a BitBurner USB Miner ... and indeed the BitBurner is very good ...

[bvoid]

No compiled Windows version available on the Github mirror..

[kano]

No compiled Windows version available on the Github mirror..

... ah ... yes there is ...

[bo122081]

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

https://bitcointalk.org/index.php?topic=28402.msg3052634#msg3052634

That is not actually a response to my post, nor does it seem especially relevant.

[scrawler]

ck.kolivas.org - still down?

[kano]

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

https://bitcointalk.org/index.php?topic=28402.msg3052634#msg3052634

That is not actually a response to my post, nor does it seem especially relevant.

Your miner stops mining ... why does it stop?
Try setting the settings down and ... it may not happen
(as per that post)

[-ck]

ck.kolivas.org - still down?

7 hours to go.

[bo122081]

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

https://bitcointalk.org/index.php?topic=28402.msg3052634#msg3052634

That is not actually a response to my post, nor does it seem especially relevant.

Your miner stops mining ... why does it stop?
Try setting the settings down and ... it may not happen
(as per that post)

As noted in my original post, it doesn't seem to be indicating any crash or overheat. The cards are not significantly overclocked, nor do I have any real indication of a possible problem. The software dev said this only happens on API request or command execution - which seems a bit scary to me - because I'm wondering if I'm getting hacked or something, then? Or is there any other possible case I could get this message??

[DrGuns4Hands]

Somewhat noob linux user here, I'm going through the Read Me and just want to make sure I understand properly for install on Raspberry Pi

DEPENDENCIES:
Mandatory:
   curl dev library    http://curl.haxx.se/libcurl/
   (libcurl4-openssl-dev)

   pkg-config      http://www.freedesktop.org/wiki/Software/pkg-config
   libtool         http://www.gnu.org/software/libtool/
Optional:
   curses dev library
   (libncurses5-dev or libpdcurses on WIN32 for text user interface)

   AMD APP SDK      http://developer.amd.com/sdks/AMDAPPSDK
   (This sdk is mandatory for GPU mining)

   AMD ADL SDK      http://developer.amd.com/sdks/ADLSDK
   (This sdk is mandatory for ATI GPU monitoring & clocking)

   libudev dev library (libudev-dev)
   (This is only required for ASIC+FPGA support and is linux only)

If building from git:
   autoconf
   automake

Where autoconf and automake are listed it makes it look like they are Dependencies but I wanted to be sure they were not commands that needed to be run prior to autogen

Basic *nix build instructions:
   To actually build:

   ./autogen.sh   # only needed if building from git repo
   CFLAGS="-O2 -Wall -march=native" ./configure <options>

For the actual install in the past I have done ./autogen.sh --(options)

what is the CFLAGS command and is it necessary for all builds?
also is the ./configure a second step that should be run after autogen with the appropriate options, or is adding the options to autogen okay?
Or should it be one full line command?

Thank you for your valuable time in both writing the code and in answering questions.

[vapourminer]

[snip..] 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 ht 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.

shiney.. kinda figured as much but wasnt sure if theres a standard "goto" distro..

thanks!

[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.

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

3.4.1 did the same thing: it just restarted by itself. I saw it hit 1million shares around 2am, and then it seems it restarted itself at 8:15am. I'll download the debug builds when the site is back up.

[ScaryHash]

Hi,

I'm trying to compile this for the first time under MinGW for windows.

Followed your instructions up to this point under windows-build.txt (all the libraries and stuff into their proper location, except no AMD SDK because I can't find the AMD APP folder. No biggy there).

copied the cgminer.c file into my build directory.

when I typed make, it says *** No targets specified and no makefile found. Stop*

when I typed in make install, it says *** No rule to make target 'install'. Stop ****


I just copied and pasted the source code into notepad and saved it in the directory. Did I do something wrong? The only file in that directory is cgminer.c

It's been a while since I've compiled stuff, and I'm a MinGW/unix noob, so forgive me if these questions are too stupid.

Thanks.

[-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

3.4.1 did the same thing: it just restarted by itself. I saw it hit 1million shares around 2am, and then it seems it restarted itself at 8:15am. I'll download the debug builds when the site is back up.

Darn, well the site is back up and I just uploaded the new debug builds for 3.4.1.

[PinkMouse]

hello!
Cgminer works well with sha256, but with scrypt does not.
It shows 850 kH (it's too much, right?), with no sound/submitted shares for 3 hours.
Is problem in config or in driver?
(...)
I have a Radeon Hd4870 512MB+ Catalyst 11.12 + Win XP (1.5G RAM)

Probably all HW errors...

Cuold you give me more details?
It mines bitcoins with 100 MH @ 840 MHZ. What kind of HW error could it be?

[...]
Try this config for starters. Then look here to fine tune: https://en.bitcoin.it/wiki/Mining_hardware_comparison

Code:

"scrypt" : true,
"intensity" : "13",
"vectors" : "2",
"worksize" : "128",
"lookup-gap" : "2",
"thread-concurrency" : "4000",
"shaders" : "800",
"gpu-engine" : "750",
"gpu-fan" : "25-100",
"gpu-memclock" : "900",
"auto-fan" : true,
"gpu-vddc" : "0.000",
"temp-cutoff" : "95",
"temp-overheat" : "90",
"temp-target" : "80",
"api-port" : "4028",
"gpu-threads" : "1",
"hotplug" : "0",
"log" : "5",
"temp-hysteresis" : "6",
"shares" : "0",
"kernel-path" : "/usr/local/bin"

here's my result

Code:

C:\cgminer-s\cgminer.exe --scrypt -D -T
 [2013-09-02 17:07:58] Started cgminer 3.4.0
 [2013-09-02 17:07:58] Loaded configuration file cgminer.conf

 [2013-09-02 17:07:58] CL Platform 0 vendor: Advanced Micro Devices, Inc.

 [2013-09-02 17:07:58] CL Platform 0 name: AMD Accelerated Parallel Processing

 [2013-09-02 17:07:58] CL Platform 0 version: OpenCL 1.1 AMD-APP (831.4)

 [2013-09-02 17:07:58] Platform 0 devices: 1
 [2013-09-02 17:07:58]  0       ATI RV770
 [2013-09-02 17:07:59] GPU 0 iAdapterIndex 0 strUDID PCI_VEN_1002&DEV_9440&SUBSY
S_E131174B&REV_00_4&178951BB&0&0008A iBusNumber 3 iDeviceNumber 0 iFunctionNumbe
r 0 iVendorID 1002 strAdapterName  ATI Radeon HD 4800 Series

 [2013-09-02 17:07:59] GPU 0 ATI Radeon HD 4800 Series hardware monitoring enabl
ed
 [2013-09-02 17:07:59] Setting GPU 0 engine clock to 750
 [2013-09-02 17:07:59] Setting GPU 0 memory clock to 900
 [2013-09-02 17:07:59] GPU 0 call to fanspeed get failed
 [2013-09-02 17:07:59] Popping work to stage thread
 [2013-09-02 17:07:59] Probing for an alive pool
 [2013-09-02 17:07:59] Testing pool stratum+tcp://127.0.0.1:3333

 [2013-09-02 17:07:59] Pool 0 stratum session id: ae6812eb4cd7735a302a8a9dd95cf7
1f
 [2013-09-02 17:07:59] Pool 0 difficulty changed to 32
 [2013-09-02 17:07:59] Stratum authorisation success for pool 0

 [2013-09-02 17:07:59] Pool 0 stratum+tcp://127.0.0.1:3333 alive

 [2013-09-02 17:08:00] Init GPU thread 0 GPU 0 virtual GPU 0

 [2013-09-02 17:08:00] CL Platform vendor: Advanced Micro Devices, Inc.

 [2013-09-02 17:08:00] CL Platform name: AMD Accelerated Parallel Processing

 [2013-09-02 17:08:00] CL Platform version: OpenCL 1.1 AMD-APP (831.4)

 [2013-09-02 17:08:00] List of devices:
 [2013-09-02 17:08:00]  0       ATI RV770
 [2013-09-02 17:08:00] Selected 0: ATI RV770
 [2013-09-02 17:08:00] Preferred vector width reported 4
 [2013-09-02 17:08:00] Max work group size reported 256
 [2013-09-02 17:08:00] Max mem alloc size is 134217728
 [2013-09-02 17:08:00] Selecting scrypt kernel
 [2013-09-02 17:08:00] No binary found, generating from source

 [2013-09-02 17:08:00] Setting worksize to 128
 [2013-09-02 17:08:00] cl_amd_media_ops not found, will not set BITALIGN

 [2013-09-02 17:08:00] BFI_INT patch requiring device not found, will not BFI_IN
T patch
 [2013-09-02 17:08:00] CompilerOptions: -D LOOKUP_GAP=2 -D CONCURRENT_THREADS=40
00 -D WORKSIZE=128 -D GOFFSET -D OCL1

Netstat shows open connection. No GPU activity in Catalyst control center "OverDrive" tab.

[bitcoindaddy]

Having a problem running 3.4.1 from cgminer-3.4.1-x86_64-built.tar.bz2:

Code:

cat /etc/issue
Ubuntu 12.04.2 LTS \n \l

dpkg -l | grep libudev
ii  libgudev-1.0-0                         1:175-0ubuntu9.4                        GObject-based wrapper library for libudev
ii  libudev-dev                            175-0ubuntu9.4                          udev library (development files)
ii  libudev0                               175-0ubuntu9.4                          udev library

cgminer-nogpu: error while loading shared libraries: libudev.so.1: cannot open shared object file: No such file or directory

[-ck]

Having a problem running 3.4.1 from cgminer-3.4.1-x86_64-built.tar.bz2:

Code:

cat /etc/issue
Ubuntu 12.04.2 LTS \n \l

dpkg -l | grep libudev
ii  libgudev-1.0-0                         1:175-0ubuntu9.4                        GObject-based wrapper library for libudev
ii  libudev-dev                            175-0ubuntu9.4                          udev library (development files)
ii  libudev0                               175-0ubuntu9.4                          udev library

cgminer-nogpu: error while loading shared libraries: libudev.so.1: cannot open shared object file: No such file or directory

Alas it's built for ubuntu 13.04 so you'll have to build it yourself since it looks like your ubuntu has only udev0 and not udev1.

[DareC]

I've been unable to get any cgminer version after 3.3.1 to start on Win7 x64, using the pre-built binaries. I get the message "Error opening terminal: dumb"

3.3.1 works fine with identical configuration, but I'd rather not be stuck on an old version.

[-ck]

I've been unable to get any cgminer version after 3.3.1 to start on Win7 x64, using the pre-built binaries. I get the message "Error opening terminal: dumb"

3.3.1 works fine with identical configuration, but I'd rather not be stuck on an old version.

Unrelated to cgminer. Google for it, seems to be related to some windows environment variable with various solutions offered.