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

[-ck]

To get the repository I did:

git clone -b libusbx git://github.com/ckolivas/cgminer

I'm still getting errors:

AMU0: TIMEOUT GetResults took 658ms but was 100ms
...
AMU 0 usb write error: LIBUSB_TRANFER_TIMED_OUT
AMU0: Comms error (werr=2 amt=0)
..
repeats


Is there a way to check to ensure I'm properly on the branch?  I haven't built from git before but I hopefully did it correctly.  

Thanks.

'git branch' is enough to tell you what branches you have and what branch you're on.

Your case is particularly interesting because every report so far has been on windows. Can you see what the CPU usage is like when you're running cgminer and see if there are spikes when the error messages occur?

[Rant2112]

To get the repository I did:

git clone -b libusbx git://github.com/ckolivas/cgminer

I'm still getting errors:

AMU0: TIMEOUT GetResults took 658ms but was 100ms
...
AMU 0 usb write error: LIBUSB_TRANFER_TIMED_OUT
AMU0: Comms error (werr=2 amt=0)
..
repeats


Is there a way to check to ensure I'm properly on the branch?  I haven't built from git before but I hopefully did it correctly. 

Thanks.

'git branch' is enough to tell you what branches you have and what branch you're on.

Your case is particularly interesting because every report so far has been on windows. Can you see what the CPU usage is like when you're running cgminer and see if there are spikes when the error messages occur?

git branch says:
* libusbx

The error messages happen every 2 seconds.  Using top or xload only shows every 1 second so I don't know how to see spikes. 

CPU utilization is very low - something like 0.3% for cgminer.

[-ck]

git branch says:
* libusbx

The error messages happen every 2 seconds.  Using top or xload only shows every 1 second so I don't know how to see spikes.  

CPU utilization is very low - something like 0.3% for cgminer.

Try the latest libusbx async branch. More sheer desperation in the code. Then show us the output of api stats if you know how to (easiest is to use 'java API stats') after it's been running for a while.

[-ck]

Here is new log version which contains this TIMEOUT messages. Hope it helps you somehow.

Thank you very much, I'll be studying it shortly. One question: Can you monitor the CPU usage of cgminer and see how it fluctuates over time? The task manager in windows ill allow you to do that. I'm most interested to see if it ever spikes at high levels (close to 100%) and if that correlates with these timeout error messages.

More experimental binaries uploaded for windows:

http://ck.kolivas.org/apps/cgminer/temp/cgminer-nogpu.exe
http://ck.kolivas.org/apps/cgminer/temp/cgminer.exe

[darkfriend77]

I got the info from asic-hardware (cryptX) that the BitBurner Fury ... should run ... with cgminer.

Code:

It's the same basic cgminer the Avalons use. see under news on the site www.burninmining.com

regards

Bert

This is what I have done ...

Code:

Once raspbian is running open LXTerminal and type the following commands to install the needed prequisites to build cgminer:
sudo apt-get update
sudo apt-get install autoconf libusb-1.0-0-dev libncurses5-dev libcurl4-openssl-dev screen
Then clone the cgminer repository:
git clone https://github.com/ckolivas/cgminer.git cgminer
Enter the new directory, configure and build cgminer
cd cgminer
./autogen.sh –enable-avalon
make clean
make
Now cgminer should compile

now as root I submited ...

./cgminer -n

Code:

root@bitfury:/home/pi/cgminer# ./cgminer -n
 [2013-10-07 07:59:57] USB all: found 4 devices - listing known devices
.USB dev 0: Bus 1 Device 4 ID: 0403:6001
  Manufacturer: 'Burnin Electronics'
  Product: 'BitBurner'
 [2013-10-07 07:59:57] 1 known USB devices

Code:

./cgminer -o stratum+tcp://nl1.ghash.io:3333 -u xxx.2-p x

[-ck]

I got the info from asic-hardware (cryptX) that the BitBurner Fury ... should run ... with cgminer.

Code:

It's the same basic cgminer the Avalons use. see under news on the site www.burninmining.com

You'll have to ask them. We don't have the hardware and therefore are not maintaining any code ourselves that currently supports it. I think they're the ones who submitted a pull request for us to include code for them but it has been low priority for us and we have not reviewed or incorporated any new code for it.

[spacebob]

....
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.

I had a similar error and I solved it by adding slub_debug=FP to /boot/cmdline.txt. I talked about it over at the Raspberry Pi support forums. http://www.raspberrypi.org/phpBB3/viewtopic.php?f=28&t=55370

[zamot]

Here is new log version which contains this TIMEOUT messages. Hope it helps you somehow.

Thank you very much, I'll be studying it shortly. One question: Can you monitor the CPU usage of cgminer and see how it fluctuates over time? The task manager in windows ill allow you to do that. I'm most interested to see if it ever spikes at high levels (close to 100%) and if that correlates with these timeout error messages.

cgminer uses CPU on average 5% and it jumps to around 15% when this timeout error occurs and then is back to its 5% or less.
Overall CPU usage is around 30%, and it jumps to 100% by timeout error and them back to normal. This difference of CPU usage is made by System process which uses normaly around 10% CPU.

[gnar1ta$]

Any developers had a chance to work on a Jupiter?

[-ck]

Here is new log version which contains this TIMEOUT messages. Hope it helps you somehow.

Thank you very much, I'll be studying it shortly. One question: Can you monitor the CPU usage of cgminer and see how it fluctuates over time? The task manager in windows ill allow you to do that. I'm most interested to see if it ever spikes at high levels (close to 100%) and if that correlates with these timeout error messages.

cgminer uses CPU on average 5% and it jumps to around 15% when this timeout error occurs and then is back to its 5% or less.
Overall CPU usage is around 30%, and it jumps to 100% by timeout error and them back to normal. This difference of CPU usage is made by System process which uses normaly around 10% CPU.

Interesting, and cause for further speculation. We're working with the libusb developer to see if we can't find the problem since it seems to be within the library. Still worth trying the latest binaries I uploaded yesterday, thanks.

[superresistant]

Will cgminer support other algorithm than SHA256 and scrypt ?

[-ck]

Will cgminer support other algorithm than SHA256 and scrypt ?

No

[P_Shep]

So try as I might, udev will not work on routers. The kernel is simply too old and there's not anything we can do about that. So...

I'd like to request a configuration option to allow for udev to be disabled and just have the USB ports scanned on startup like we had before.

Also, if GPU isn't specified, no need to copy the *.cl files in the install

And allow it to be statically compiled.

Thanks

[superresistant]

Does cgminer support KNC miner hardware ? If yes how to do ?

[-ck]

Does cgminer support KNC miner hardware ? If yes how to do ?

Nope. KFC support cgminer on their own fork and have yet to reveal their sauce.

[superresistant]

Thank you for the answers.

[Its About Sharing]

Does cgminer support KNC miner hardware ? If yes how to do ?

Nope. KFC support cgminer on their own fork and have yet to reveal their sauce.

I wonder if they suped it up some? I know Burnin supposedly was shooting for getting the Bitfury chips (2Ghash/s) to 5Ghash/s using an external clock or something like that. There are some tricks out there...

[Myrddindc]

Apologies for noobish question.

I have  been using cgminer to run my 6 usb block eruptors for a few weeks now with all being great. Now that I have finally received my BFL little(which also performs perfectly well, running with bfgminer for now) my cgminer keeps reporting:

Code:

USB init, open device failed, err -12, you need to install a Windows USB driver for - BFL device 5:1

But I already have all the drivers installed and the device is running just fine in another window.

My question is how do I stop cgminer from searching for or reporting this device, as it makes for messy on screen monitoring of my block eruptors.

The line that initializes the block eruptors is:

Code:

cgminer-nogpu.exe -o stratum.btcguild.com:3333 -u myUserName_com9 -p 1234  ---icarus-options 115200:1:1 --icarus-timing 3.0=100 -S //./COM9

Apologies again for a noobish question! Many thanks in advance for any suggestions!

Myrdd.

[os2sam]

Apologies for noobish question.

I have  been using cgminer to run my 6 usb block eruptors for a few weeks now with all being great. Now that I have finally received my BFL little(which also performs perfectly well, running with bfgminer for now) my cgminer keeps reporting:

Code:

USB init, open device failed, err -12, you need to install a Windows USB driver for - BFL device 5:1

You need to run Zadig and install WinUSB for that device.

[os2sam]

My question is how do I stop cgminer from searching for or reporting this device, as it makes for messy on screen monitoring of my block eruptors.

Add
"--usb BAS:0"

It is covered in the readme under Advanced USB Options