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

[techman05]

You have the right driver? WinUsb is what I'm using from the list of installable drivers for cgminer . Thats what I think the unsupported error is about.

If all your using your xp machine is for mining, kill it and install umbuntu or windows 7. Make ckolivias life alot easier fixing whats going on.

[PatMan]

Xubuntu = YES!

winblows 7 = NO!

 

ADIT: winblows 8/prism = OH NONONONONO!!

[zamot]

You have the right driver? WinUsb is what I'm using from the list of installable drivers for cgminer . Thats what I think the unsupported error is about.

If all your using your xp machine is for mining, kill it and install umbuntu or windows 7. Make ckolivias life alot easier fixing whats going on.

Yes, i am using WinUSB driver, and regular cgminer 3.5.0 recognize BE's and they are doing thei job, but there are tons of timeout messages which were not on cgminer 3.3.0 which i used before and in mean time ther ewas no change of drivers or something else.
And yes, i am doing to install an linux on one of laptops. Hope it will be dome till weekend

[-ck]

So, i tried with cgminer-nogpu.exe from ( http://ck.kolivas.org/apps/cgminer/temp/cgminer-nogpu.exe ) and i got this :

[2013-10-01 11:36:13] Started cgminer 3.5.0
[2013-10-01 11:36:13] Loaded configuration file cgminer.conf
[2013-10-01 11:36:14] AMU 0 usb write error: LIBUSB_ERROR_NOT_SUPPORTED


This was try with just one BE.  

Ok, try redownloading again please (remember I don't have this hardware/OS combination to test for myself).

[-ck]

I'm still having trouble getting my Block Erupter to work on anything besides 3.1.1

With 3.5.0 I get:

AMU0: TIMEOUT GetResults took 659ms but was 100ms
...
AMU0: TIMEOUT GetResults took 659ms but was 100ms

AMU0: Comms error (werr=-7 amt=0)
...
AMU0: Comms error (werr=-7 amt=0)


I think this is a known problem but posting just to be sure.   I'll continue to use 3.1.1 as it is working fine.  


FYI - I'm mining using a recent Ubuntu release running under VMWare Fusion on a Mac.  The Block Erupter is plugged into a USB2 D-Link HUB.  It is connected to a 'high speed' USB port on the Mac which should mean it is USB2.

If you know how to build from git, can you try building the latest libusbx branch and see if it helps?

[zamot]

So, i tried with cgminer-nogpu.exe from ( http://ck.kolivas.org/apps/cgminer/temp/cgminer-nogpu.exe ) and i got this :

[2013-10-01 11:36:13] Started cgminer 3.5.0
[2013-10-01 11:36:13] Loaded configuration file cgminer.conf
[2013-10-01 11:36:14] AMU 0 usb write error: LIBUSB_ERROR_NOT_SUPPORTED


This was try with just one BE.  

Ok, try redownloading again please (remember I don't have this hardware/OS combination to test for myself).

I made test with newly downloaded ( http://ck.kolivas.org/apps/cgminer/temp/cgminer-nogpu.exe ) and the result was:
- Timeout message after 10-15 seconds
- after a while there was also an write error: LIBUSB_ERROR_NOT_SUPPORTED
- cgminer only recognized 4 BE's ( even if they were added one by one )

If you have any other idea i willing to try and to report is this issue is solved.

I understand you, that you can not simulate every possible combination of HW/OS configuration.
Like i write before, cgminer 3.5.0 works and BE's make minig, but there are this timeout warnings. I will try to port ASAP to linux and then we will see if there will be some surprises or not.

[techman05]

If it wasn't for the fact you had 25 of these I'd think to uninstall the drivers and re install them but if its like my pc it will grump at every one of them. You are using a new folder with the new install right?

I expand reset the shortcut and point to my config file in the new folder.

I can't imagine how much might have changed between 3.3 and 3.5 . It just keep things cleaner to start a new folder with all the nooks that came with it.

CKOlivias too bad you can't just remote connect since windows xp had a token to send out to share your desktop with I thought.

[zamot]

If it wasn't for the fact you had 25 of these I'd think to uninstall the drivers and re install them but if its like my pc it will grump at every one of them. You are using a new folder with the new install right?

I expand reset the shortcut and point to my config file in the new folder.

I can't imagine how much might have changed between 3.3 and 3.5 . It just keep things cleaner to start a new folder with all the nooks that came with it.

CKOlivias too bad you can't just remote connect since windows xp had a token to send out to share your desktop with I thought.

Yeah, i done this all before but it doesn't helped. Bad luck ...

[-ck]

So, i tried with cgminer-nogpu.exe from ( http://ck.kolivas.org/apps/cgminer/temp/cgminer-nogpu.exe ) and i got this :

[2013-10-01 11:36:13] Started cgminer 3.5.0
[2013-10-01 11:36:13] Loaded configuration file cgminer.conf
[2013-10-01 11:36:14] AMU 0 usb write error: LIBUSB_ERROR_NOT_SUPPORTED


This was try with just one BE.  

Ok, try redownloading again please (remember I don't have this hardware/OS combination to test for myself).

I made test with newly downloaded ( http://ck.kolivas.org/apps/cgminer/temp/cgminer-nogpu.exe ) and the result was:
- Timeout message after 10-15 seconds
- after a while there was also an write error: LIBUSB_ERROR_NOT_SUPPORTED
- cgminer only recognized 4 BE's ( even if they were added one by one )

If you have any other idea i willing to try and to report is this issue is solved.

Youch. That does not spell good news since I can't even imagine what other libusb feature is not supported. While it won't make it any better, could you start it with the following extra parameters:
-D -T 2>log.txt
and then stop it after a minute or so and see what's in the log.txt file?

EDIT: I mean trying it with that new executable of course.

[Askit2]

This was a move from 3.4 to 3.5 for me and I had to install the libudev-devel package to get cgminer to compile again. Perhaps there's an issue with the centos implementation of libudev-devel.

Thank You!
You pointed out why I was having seg faults. It doesn't fix it per se but I can at least run the current version. I wish I would have seen this info before I messed up my building.

Since I stopped limiting my usb devices and only am running one instance I am able to run 3.5.0. I could start the limited ones first and just catch the remainder with the new version but I really want to see if it locks up using quotas.

EDIT: am running a log file now on Raspberry pi as I can't seem to get the monitor to stop shutting off. When I can see it dying it is always one instance first, then the second then a while later the third. Printed on TOP is failure to read from swap. I assume it is caching some data in a swap file cgminer or some system process I am unsure. TOP only shows before things go horribly wrong 0 virtual memory use, but if I run X I can use task manager and it shows some Virtual memory use. The previous data is from 3.4.3 and before nothing on 3.5.0 yet.

It seems to me like (as a windows user mostly) if I am using virtual memory there should be data in the swap file. But the two different tools seem to have conflicting data to me. I am sure that there is something I am missing.

[zamot]

Youch. That does not spell good news since I can't even imagine what other libusb feature is not supported. While it won't make it any better, could you start it with the following extra parameters:
-D -T 2>log.txt
and then stop it after a minute or so and see what's in the log.txt file?

EDIT: I mean trying it with that new executable of course.

I made the log file. It was running for about 2 minutes.
Log file can be found here.

[-ck]

Youch. That does not spell good news since I can't even imagine what other libusb feature is not supported. While it won't make it any better, could you start it with the following extra parameters:
-D -T 2>log.txt
and then stop it after a minute or so and see what's in the log.txt file?

EDIT: I mean trying it with that new executable of course.

I made the log file. It was running for about 2 minutes.
Log file can be found here.

Thanks very much for doing that. That was all working fine there... I was trying to figure out what happens when you have a problem and it doesn't appear to have had a problem in that time?

[Rant2112]

I'm still having trouble getting my Block Erupter to work on anything besides 3.1.1

With 3.5.0 I get:

AMU0: TIMEOUT GetResults took 659ms but was 100ms
...
AMU0: TIMEOUT GetResults took 659ms but was 100ms

AMU0: Comms error (werr=-7 amt=0)
...
AMU0: Comms error (werr=-7 amt=0)


I think this is a known problem but posting just to be sure.   I'll continue to use 3.1.1 as it is working fine.  


FYI - I'm mining using a recent Ubuntu release running under VMWare Fusion on a Mac.  The Block Erupter is plugged into a USB2 D-Link HUB.  It is connected to a 'high speed' USB port on the Mac which should mean it is USB2.

If you know how to build from git, can you try building the latest libusbx branch and see if it helps?

Do I need to put the libusbx code in the cgminer libusb directory?  Is that still there or can I just install the latest libusbx and then build cgminer?

[-ck]

If you know how to build from git, can you try building the latest libusbx branch and see if it helps?

Do I need to put the libusbx code in the cgminer libusb directory?  Is that still there or can I just install the latest libusbx and then build cgminer?

It's called the libusbx branch because the libusb included in there is the latest libusbx version. You don't need to do anything different than a regular git compile (i.e. you only need ./autogen.sh in addition to a normal build procedure).

[Beastlymac]

3.5.0 on raspbian wheezy. Crashed. Any ideas on what I can do to fix it?

[-ck]

3.5.0 on raspbian wheezy. Crashed. Any ideas on what I can do to fix it?

Eh, but that's a kernel crash, not a cgminer crash... and while I am a kernel developer, I had nothing to do with this one
Kernel upgrade, either the package provided for raspbian, or migrating to another distribution is the only way unless you want to help the raspbian maintainers debug this crash.

[Beastlymac]

3.5.0 on raspbian wheezy. Crashed. Any ideas on what I can do to fix it?

Eh, but that's a kernel crash, not a cgminer crash... and while I am a kernel developer, I had nothing to do with this one
Kernel upgrade, either the package provided for raspbian, or migrating to another distribution is the only way unless you want to help the raspbian maintainers debug this crash.

Ok I will give upgrading a shot. Thanks.
Edit: updated everything so lets se how it goes...

[RaTTuS]

....
Ok I will give upgrading a shot. Thanks.

I've just built and run mine on raspbian
and it seems to be fine .. however I do it like :-
ver=3.5.0
wget http://ck.kolivas.org/apps/cgminer/cgminer-$ver.tar.bz2
tar xf cgminer-$ver.tar.bz2
cd cgminer-$ver
mkdir libusb
cd libusb
wget http://sourceforge.net/projects/libusb/files/libusb-1.0/libusb-1.0.16-rc10/libusb-1.0.16-rc10.tar.bz2
tar -xf libusb-1.0.16-rc10.tar.bz2
cd libusb-1.0.16-rc10
./configure
make CC=distcc
cd ../..
LIBUSB_CFLAGS="-I./libusb/libusb-1.0.16-rc10/libusb" LIBUSB_LIBS="./libusb/libusb-1.0.16-rc10/libusb/.libs/libusb-1.0.a -ludev" ./configure --enable-icarus --enable-bitfury --disable-opencl
make CC=distcc

[P_Shep]

Still having issues with libudev on mipsel.

Can't get it to statically link libudev.

In fact it doesn't seem to be statically linking in any library. It did used to.

[Beastlymac]

....
Ok I will give upgrading a shot. Thanks.

I've just built and run mine on raspbian
and it seems to be fine .. however I do it like :-
ver=3.5.0
wget http://ck.kolivas.org/apps/cgminer/cgminer-$ver.tar.bz2
tar xf cgminer-$ver.tar.bz2
cd cgminer-$ver
mkdir libusb
cd libusb
wget http://sourceforge.net/projects/libusb/files/libusb-1.0/libusb-1.0.16-rc10/libusb-1.0.16-rc10.tar.bz2
tar -xf libusb-1.0.16-rc10.tar.bz2
cd libusb-1.0.16-rc10
./configure
make CC=distcc
cd ../..
LIBUSB_CFLAGS="-I./libusb/libusb-1.0.16-rc10/libusb" LIBUSB_LIBS="./libusb/libusb-1.0.16-rc10/libusb/.libs/libusb-1.0.a -ludev" ./configure --enable-icarus --enable-bitfury --disable-opencl
make CC=distcc

I think the problem was I just hadn't updated anything when I re flashed the sd card.