Re: Claymore's Dual Ethereum AMD+NVIDIA GPU Miner v7.1 (Windows/Linux)

Hello,

I am finally able to run version 7.1 on ubuntu 16.04
However - when started in an ssh session it gives me segmentation fault. Doesn't happen from the local console. I can post whatever information you require to track down the bug. It should be easy to reproduce however ?

Thanks !

Well, I don't like Linux (I have enough reasons for that) and its problems that are often called as "features".
Please start Genoil's miner, or original ethminer. If it works from ssh, I need to know more about your setup/config and I will check it because it can be another "feature" from Linux that I can fix. If it does not work too, say thanks to Linux, it's a "feature", not a bug.

ethminer runs from ssh.

Here is the error I get:

[ 13.452864] ethdcrminer64[1092]: segfault at 110 ip 00007f13d3eead22 sp 00007ffeeb18c9e8 e
rror 4 in libdrm_amdgpu.so.1.0.0[7f13d3ee7000+a000]

This is when trying to execute it as a cron job on startup. Same issue as starting it from ssh.
Hope that helps !

I could set up a test linux system and give you access if you don't have one ? I could throw one rx470 in it - that should be enough ?

I have several versions of Ubuntu, 480 cards etc - I just want to know how to reproduce the problem. Not from startup, don't want to reboot every time. How to see the problem from ssh? Step by step please. You can PM me instead of writing here.

I´m also having a segmentation fault error when running Claymore 7.0 on clean Ethos 1.11 with admgpu drivers. Will reproduce and post procedure asap.

Could be that this missing libjansson packages are the problem? I couldn´t install them at first try from ubuntu trusty universal repositories nor from .deb package. Will try from sources tomorrow.

Quote from: scryptr on September 25, 2016, 07:40:53 PM

Quote from: fran2k on September 25, 2016, 01:20:28 PM

Nice release guys, will test asap.

Quote from: scryptr on September 22, 2016, 06:28:15 PM

Quote from: Wolf0 on September 22, 2016, 02:08:00 PM

Quote from: YIz on September 22, 2016, 01:27:39 PM

I'm getting steady 30MH/s on each Fury X on stock clocks (1050/500). Claymore's can only get about 28MH.
A 390 at 1040Mhz gets 29Mh, with some overclocking I can surely can 32-33MH, but my cards warm up too much. Definitely the best miner out there.

The only issue I can spot is the CPU usage, which makes this miner basically worthless on weak CPUs. I couldn't run it on a single-core AMD CPU and a friend of mine had his rig crashing with a dual core Celeron installed. most mining rigs have very weak CPUs, and if this miner gets updated to support them, I am sure it will get much more traction.

I can fix it with a new binary - just needs to be recompiled against a better pthreads lib.

WILL THE SGMINER-GM RECEIVE UPDATES? --

I run this SGminer on a sensitive 280X rig that is not stable with Claymore and dual mining. Currently, SGminer-gm is running under Ethos 1.1.1 on 4 280X cards, mining at 16.7MH/s at stock clocks. It runs with less heat than either Genoil v1.1.7 or Claymore, and does not crash as often. The CPU is a Haswell Celeron 1820 at 2.7GHz. The rig is not perfectly stable, but it runs.

Are updated binaries gong to be posted for both Linux and Windows? I am hoping that the repository will be an active one. --scryptr

Did you manage to run Claymore´s dual miner stable in Ethos? Setup?

CLAYMORE RUNS IN ETHOS--

On my other rigs, Claymore is very stable. It is easy to set up, but off-topic for this thread. Make a directory for Claymore in the home directory, copy the Linux binaries there, make sure libjansson is installed, and run Claymore as described in the Claymore README!!!.txt. The command "sudo-apt-get-ubuntu install libjansson*" will install all of libjansson. Don't forget the asterisk. And, turn off mining in EthOS with "disallow" and "minestop". If your launch scrypt is ready, launch Claymore.

Just a note: Claymore's README!!!.txt is mistaken for a BASH script in a Linux console. It needs to be renamed with "mv READ*.txt readme.txt". I could not open it to read without renaming it. --scryptr