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

Segfault then trying to  switch from pool without LP to second pool with LP. Second pool was added manually after programm starts.
ubuntu 11.04 x32, cgminer 1.6.2, git version

Thanks, I figured it out, it was missing the LD_LIBRARY_PATH which the script seems to need if you want to launch it without starting it from an existing terminal window. As for the script starting 4 instances of AMDOverdriveCtrl, I had to run that script directly instead of via a new terminal, and then apparently it works fine without terminal windows and without exiting. Some fine hours wasted nitpicking, but finally it works, time to move her to the basement and get a good (silent) night sleep.

If it can be of help to anyone, here are my scripts (modify, launch via start.sh and run 'directly', not in a new terminal):

start.sh

oca.sh

miner1.sh

miner2.sh

Linux and Unix os's are build up around a few very easy concepts which makes them quite predictable.
I almost only work with Linux in commercial environments so i do not have any experience with Ubuntu...

Nevertheless its almost impossible to answer the question w/o knowing the output of the doubleclicked .sh file
seeing your script and maybe an "ls -l" of the directory where cgminer is located.

One reason might be that the user you are logged into X with does not have the correct permissions to access cgminer.
At least that is where i could but my 2 bitcents w/o knowing more.


Best
/GoK

Thanks, however the script already does that, it cd's to the cgminer dir and then ./ starts it with a config file argument, also located in the same directory. I suppose I'm asking in the wrong place, since I also have the same problem with a script that starts 4 instances of AMDOverdriveCtrl. The scripts both work fine when launched from an existing terminal (./script). It just doesn't work when I call the scripts from another script (or start-up script) or when I try to double-click it and select run in terminal. *sigh* Why is linux always such a b*tch, there ought to be a Steve Jobs for the linux community, to simplify these overly complicated, very basic tasks.

I don't know if I could use start-stop daemon, since I have to launch two instances of cgminer each with different parameters. Thanks for the heads-up though.

Either use an option to point it to the kernels or add a cd /path/to/cgminer before the line starting the binary.

Use a wrapper utility such as start-stop-daemon, suppress all output with 'really-quiet' flag.

I wrote a dead-simple shell script to start cgminer, and it works, but the peculiar thing is that it starts up fine from an existing terminal, but it won't start if I just double-click the script and select run in terminal, or when I add it to Ubuntu start-up applications (or try to call it from another script). It didn't work before on Linuxcoin and now I'm still having this problem with Ubuntu. I've looked around everywhere but I can't find a working fix, any hints?

I'm having some issues with the Windows release of 1.6.2. It will not activate 2/3 of my GPU's it fails to lock the thread on the GPU's. If I go back to 1.6.0 everything is fine. What sort of output do I need to provide for this issue to be troubleshooted? Screenshot or some sort of log?

keep up the good work love the app

Yes I figured out what I had broken from the old curl at last. Please note that the old curl does not have support for sockoptions that make longpoll reliable. So while it is compiling with older libcurls, it may not be as reliable with longpoll on some servers.

If anyone is interested, thought this might be helpful to some.

If you run Cgminer on Windows 7 (should work on other versions) this startup .cmd will launch Cgminer using only one CPU core and outputs log info to a log file that has the date and time in the filename.

Open notepad.exe and put the following in (changing username and password and your servers of course):


This will use core number 4.

1st core = 1
2nd core = 2
3rd core = 4
4th core = 8
5th core = 10 ( hexadecimal 16 )
6th core = 20 ( hexadecimal 32 )

now if you want something to run on just one core, you pick the right number like this, just multiply by 2 until you get to the core you want.

if you want something to run on two cores, you ADD their values:

1st and 2nd core = 1 + 2 = 3
1st and 3rd core = 1 + 4 = 5
2nd and 3rd core = 2 + 4 = 6
2nd and 4th core = 2 + 8 = A

Same thing if you want more than two cores, just add each core numerical value up and use the sum as the /affinity parameter

Yay! It compiles with curl from RHEL5 again! CPU-only RPMs are ready: http://rpm.zaytsev.net/test/cgminer/ . I will edit the RPM post later.

The configure script from the tarball (1.6.2) contains the following:


It doesn't set LIBCURL_CPPFLAGS anywhere (which makes pkg-config detection obsolete IMO). Also, in the Makefile.am it should be changed to LIBCURL_CFLAGS instead of LIBCURL_CPPFLAGS.

Yes, yours are the problems that I mentioned above. I am preparing an RPM that you can rebuild with rpmbuild if you need GPU mining or use it as is if you only need CPU mining this evening, which features a static build against curl, so which version is in the base system repos would be irrelevant.

What GPU does include the PCs, and what driver/SDK version are installed?

working on one PC, but will not run on others

tried 2 different pools, internet is working, pools up

i get a message saying no servers were found

it just exits straight away

vista 32bit fresh install :/

New version: 1.6.2

Executive summary:
New --failover-only feature for those who complain too much work goes to the backup pool even without the primary pool failing. NOTE that you may get more idle periods with this enabled (which is why it leaked work to the backup pool in the first place).
New scheduling features to specify a start and stop time.
Various fixes and more verbose pebkac warnings.


Full changelog:

- Add --failover-only option to not leak work to backup pools when the primary
pool is lagging.
- Change recommendation to intensity 9 for dedicated miners.
- Fix the bouncing short term value by allowing it to change dynamically when
the latest value is very different from the rolling value, but damp the change
when it gets close.
- Use the curses_lock to protect the curses_active variable and test it under
lock.
- Go back to requesting work 2/3 of the way through the current scantime with
CPU mining as reports of mining threads running out of work have occurred with
only 5 seconds to retrieve work.
- Add start and stop time scheduling for regular time of day running or once off
start/stop options.
- Print summary on quit modes.
- Put some sanity checks on the times that can be input.
- Give a verbose message when no active pools are found and pause before
exiting.
- Add verbose message when a GPU fails to initialise, and disable the correct
GPU.
- Cryptopp asm32 was not correctly updated to the incremental nonce code so the
hash counter was bogus.
- Get rid of poorly executed curl check.
- If curl does not have sockopts, do not try to compile the
json_rpc_call_sockopt_cb function, making it possible to build against older
curl libraries.
- Most people expect /usr/local when an unspecified prefix is used so change to
that.
- Rename localgen occasions to getwork fail occasions since localgen is
unrelated now.


Links in top post.

libcurl.m4 defines LIBCURL_CPPFLAGS and CFLAGS would be something completely different as far as I understand it, so you're missing the m4 file from some package.

Given the single purpose of the mining rig, the smaller, the more stripped, the more stable, the better.. that does not match, sadly, the goals of most new distros. I've been running on Fedora14/15 and am actually trying to move backwards to Centos5 for the greater stability... currently being stopped short compiling 1.6.1 with:


which sounds a lot like problems with older curl to me..
.

Obviously, I need it. It's not because I care so much about other people that might need it that I am asking for it. Having to do it myself is a logical answer though.

A typical mining rig isn't your production-class server running old stable userland. I don't see any point putting developer time in working on older curl compatibility. It probably won't be used by many, if anyone at all.

just my 2c.