Topic: OFFICIAL CGMINER mining software thread for linux/win/osx/mips/arm/r-pi 4.11.0 - page 834. (Read 5805677 times)

2) Running the program from /usr/local/bin/ results in non-ncurses output (without flag) and the program segfaults on exit (ctrl-c) without displaying statistics.

Yes, I have the same problem, it tries to find the *.cl files in the current directory, should probably try to do basename argv[0] instead.

Reboot?

I hate to bump my own post, but has anyone else experienced this? Am I missing something obvious? Thanks.

So it seems I can only run the program properly with my current directory set to /opt/cgminer-1.3.1/ for the time being.

Running 1.3.0 on Fedora 14 x86.. Had it hang last night, and no either awareness of the hang, and/or no attempt at recovery.. Here's what I saw on the screen:
Ideas?

Thank you!

Further along the road, but still bombing out with a "This program has stopped working" error:


Then boom! 

cgminer version 1.3.0 - Started: [2011-07-19 22:47:23]
--------------------------------------------------------------------------------
 [(5s):647.3  (avg):1086.5 Mh/s] [Q:3254  A:3033  R:5  HW:0  E:93%  U:15.21/m]
 TQ: 0  ST: 0  LS: 0  SS: 0  DW: 2  NB: 22  LW: 0  LO: 0  RF: 0  I: 9
 Connected to http://x.x.x.x:xx/ as user xxx
 Block 00011b498db7e0db5082d5ff0cb5d1ef  started: [2011-07-20 02:03:16]
--------------------------------------------------------------------------------
 GPU 0: [361.4 Mh/s] [Q:1076  A:1007  R:1  HW:0  E:94%  U:5.08/m]
 GPU 1: [363.0 Mh/s] [Q:1084  A:1026  R:1  HW:0  E:95%  U:5.15/m]
 GPU 2: [362.1 Mh/s] [Q:1094  A:1000  R:3  HW:0  E:91%  U:5.02/m]
--------------------------------------------------------------------------------

[2011-07-20 02:04:53] Share 8ebbdcf8 accepted from GPU 1 thread 10
[2011-07-20 02:04:58] Share 73c5c9f9 accepted from GPU 0 thread 6
[2011-07-20 02:05:05] Share 54452047 accepted from GPU 0 thread 9
[2011-07-20 02:05:07] Share 22cc6c6f accepted from GPU 0 thread 0
[2011-07-20 02:05:08] Share 7b2a4075 accepted from GPU 0 thread 0
[2011-07-20 02:05:09] Share da4bf061 accepted from GPU 1 thread 7
[2011-07-20 02:05:13] Share 2406795e accepted from GPU 2 thread 5
[2011-07-20 02:05:13] Share 08250b9c accepted from GPU 0 thread 0
[2011-07-20 02:05:23] Share fa3eada8 accepted from GPU 1 thread 7
[2011-07-20 02:05:30] Share df9407d0 accepted from GPU 1 thread 7
[2011-07-20 02:05:32] Share 891499dc accepted from GPU 1 thread 1
[2011-07-20 02:05:34] Share 37f3e9b8 accepted from GPU 0 thread 6
[2011-07-20 02:05:37] Share 9837a519 accepted from GPU 1 thread 4
[2011-07-20 02:05:42] Share 1337dd1c accepted from GPU 0 thread 9
[2011-07-20 02:05:46] Share fa18714a accepted from GPU 0 thread 0
[2011-07-20 02:05:47] Share 27eb7a1e accepted from GPU 1 thread 1
[2011-07-20 02:05:48] Share 59d02639 accepted from GPU 0 thread 3
[2011-07-20 02:05:54] Share 3773b873 accepted from GPU 0 thread 0
[2011-07-20 02:05:59] Share 30e7df8c accepted from GPU 1 thread 7
[2011-07-20 02:06:02] Share 0761b69f accepted from GPU 2 thread 2
[2011-07-20 02:06:18] Share 5b1257d2 accepted from GPU 1 thread 7
[2011-07-20 02:06:22] Share d0d5bdc5 accepted from GPU 1 thread 1
[2011-07-20 02:06:37] Share c0ecc4f0 accepted from GPU 1 thread 10
[2011-07-20 02:06:37] Share a1c01ee9 accepted from GPU 2 thread 11
[2011-07-20 02:06:45] Share 72d7a8ee accepted from GPU 2 thread 5
[2011-07-20 02:06:52] Share b07c920f accepted from GPU 2 thread 5
[2011-07-20 02:06:53] Share 2ce34d13 accepted from GPU 2 thread 5
[2011-07-20 02:06:55] Attempting to restart thread 0, idle for more than 60 seconds
[2011-07-20 03:15:18] LONGPOLL received after new block already detected
[2011-07-20 03:15:18] New block detected on network before longpoll, waiting on fresh work
[2011-07-20 05:26:19] LONGPOLL received after new block already detected
[2011-07-20 05:26:19] New block detected on network before longpoll, waiting on fresh work
[2011-07-20 05:27:38] LONGPOLL received after new block already detected
[2011-07-20 05:27:38] New block detected on network before longpoll, waiting on fresh work
[2011-07-20 07:38:38] LONGPOLL received after new block already detected
[2011-07-20 07:38:38] New block detected on network before longpoll, waiting on fresh work

I have a problem getting 1.3.1 running on Windows. I'm starting using the following parameters:


And get the following response:


Followed by a "This program has stopped working" message in Windows. I'm running Windows 7 64-bit and have SDK 2.4.

Any idea what could be wrong?

Hi,

for JSON a sensible multi-host config would look like this:

{
…
connections: [
   {url: "http://foo.example.org:8332", username: "bar", password: "baz"},
   {url: "http://bar.example.org:8332", username: "baz", password: "quux"}
],
…
}

{"config":
        [
                {
                "url": "http://mining.eligius.st:8337",
                "user": "user",
                "pass": "pass"
                },
                {
                "url": "http://useast.btcguild.com:8332",
                "user": "user2",
                "pass": "pass2"
                },
                {
                "url": "http://pit.x8s.de:8337",
                "user": "user3",
                "pass": "pass3"
                }
        ]
}

ck, installed latest Catalyst, sdk 2.1, Ubuntu 10.04.3 x86_64, ATI FirePro V5700, compiles fine, when run:


Any idea?

cgminer version 1.3.1 - Started: [2011-07-20 14:45:22]
--------------------------------------------------------------------------------

 TQ: 1  ST: 1  LS: 0  SS: 0  DW: 0  NB: 0  LW: 0  LO: 0  RF: 0  I: 0
 Connected to http://api2.bitcoin.cz:8332 as user xxx
 Block xxx  started: [2011-07-20 14:45:22]
--------------------------------------------------------------------------------
 GPU 0: [0.0 Mh/s] [Q:0  A:0  R:0  HW:0  E:0%  U:0.00/m]
--------------------------------------------------------------------------------

[2011-07-20 14:45:24] Attempting to restart thread 0, idle for more than 60 seco
nds

Segmentation fault

Thanks for this great program!  I'll be sure to donate as soon as I start generating some decent bitcoin.

I had an issue with the (now) older version 1.2.8 where it would crash on startup when a system had more than 4 NVIDIA GPUs available (Windows 7 64-bit).  I'll test it again with the new version.


One issue I see with the new 1.3.1 version is with the --load-balance option with 2 pools, it continually repeats that new block detected before longpoll.  One pool is bitcoin while the other is namecoin if that makes a difference.  Running 2 instances separately this message does not occur.

Btw, forgot to mention this doesn't seem to be working on Windows. And should the run time output include hash rate per thread? I only see per device.

I have never been able to get this miner working, added the -D flag to show results before windows error saying it has stopped working....


Any Suggestions?