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

I just git cloned on arch RPi and it built fine so not sure what's going on... Heck it even mines fine on the bitfury plugged straight into it.

In that case I wonder if it's the older libudev in raspbian? We continue to get shafted by external libraries...

./autogen.sh fails with a can not find makefile.in.

Seems to be something with raspbian wheezy. I have had it up stable for around 10 hours now on minepeon.

ltmain.sh is supposed to be generated by the autotools themselves and is deleted every time.

I figured that much out. I tried it using the older directions first. I later retried with Kano's code that he posts for his other versions.

The issue seems to be a missing file at least so far.


Never mind my impatience has gotten the better of me. It deletes, checks, then copies one in. I didn't wait long enough.

What a disgrace, we've been fighting with this issue for as long as I can remember and we went to all that effort to include the least worst version of libusb statically yet it still doesn't go away.

Here try a build with statically linked version of the latest libusbx instead please since you have a way of reproducing the issue:
http://ck.kolivas.org/apps/cgminer/temp/cgminer-nogpu.exe
http://ck.kolivas.org/apps/cgminer/temp/cgminer.exe

There is no way to link in your own libusb any more. You have to use the statically included libusb.

I'm having a bad time compiling the 3.5.0 cgminer.

I start with a git pull. I finally got that working so I can do everything from the command line.
Actually git clone (con's git address). Pretty sure I copied that too.

well not everything as copying the libusb folder that I have already gotten working I haven't done from the prompt.

Then I have tried both ways
./autogen.sh followed by the configure to link the working lubusb.
and
./autogen.sh --enable- (I put in everything but am too lazy to type it all out.)

./autogen.sh by itself says something about not devices and completes but I am guessing it isn't successfully (am assuming the opencl thing made this work before) but configure completes seemingly correctly and says mining is enabled on all the devices.

./autogen.sh with enables runs and says mining is enabled on all the devices that I enabled and actually all that seem to be in the main distro. I just copied kano's.

make clean completes without errors

make completes without errors

Ok I noticed under ./autogen.sh that a ../ltmain.sh is required and not found. I wonder If I can use one from the last version or why that one didn't clone.
if I copy one as soon as I run the autogen.sh it is deleted or removed in some way before the check for it shows up. I have tried copying it in after starting ./autogen.sh. Maybe this time it won't disappear.

./cgminer says something like starting cgminer 3.5.0Segmentation fault

I have always made my own since I got my Raspberry pi. The version 3.4.3 I made still runs. So it isn't like I am screwed. I did everything the same way the first time, and a few other times. I tried Kano's way the rest of the times.

FYI I randomly see this error on my win7 machines.  I can usually cause it by initiating other things on the PC.  The PC isn't resource starved, but I definitely noticed the errors pop up when I kick something off, like say windows update.

M

Ztex code is, unfortunately, unmaintained, for the developer who worked on it has disappeared indefinitely and none of us other developers have one to work on. I don't think it has worked in a long time.

A number of things potentially going on. We have problems with some usb implementations on certain OSs and the libusb library we use. 

How long does it normally take before you see these errors and do all of them have it at the same time?

XP is a bit limited for USB. Try starting with just 2 BEs and increase it by one at a time (waiting long enough for the errors to normally appear) till you see the errors reappear.
If possible, try windows7 or ideally a linux to see if they go away.

i don't know if it's new with 3.5 (as i used 3.3.1), but there's a bug with ztex boards. cgminer says:
libztex_checkDevice: Can not open ZTEX device: -3
Ztex: Can not check device: 0

all of the 4 fpga processors work fine, it seems it is trying to find a devide with id 0, which does not exist, only 1,2,3,4.

Hello,

i have the same problem with Timeout messages for all BE.

AMU1: TIMEOUT GetResults took 1531ms but was 100ms
AMU0: TIMEOUT GetResults took 1531ms but was 100ms
AMU3: TIMEOUT GetResults took 1531ms but was 100ms
AMU2: TIMEOUT GetResults took 1531ms but was 100ms

Timeout variates from few 100ms to 2000ms or more. 
Till nowi used cgminer 3.3.0 and there was no problem, when i tried 3.4.0 and now currently 3.5.0 version i got this messagess.
I run cgminer in Windows XP SP2.
Zadig drivers are installed ( otherwise i couldn't run cgminer 3.3.0 ).
USB HUB has 3.5A max output, so there is no under power problem.
I also rebooted XP before i started cgminer 3.5.0.

How can i eliminate this timeout problem?
Here is the command for starting of cgminer: cgminer-nogpu.exe -c cgminer.conf --no-submit-stale

And this is the content of cgminer.conf:

P.S.: sorry for duplicating post, but on other thread was no answer.

Well that sounds nasty and you should stop using cgminer for now with that combo.

It is running on a powered USB hub (albeit a cheap one) with an external 4A supply running five BF1s, it ran stable fine from Ubuntu and BFGminer for a few days so the hub shouldn't be a problem

Edit - Pi is running new Raspbian release

Well, haven't tried it on a pi, just linux and windows PCs so far.

Same thing happened to me. Using a d-link hub. Also on Raspbian.