Latest posts of: wogaut

Quote from: Inaba on May 31, 2012, 07:17:01 PM

Finally... thought we were going to break a record.

What duration was the record?

Also, when looking at the block stats page, block 182403 shows 0 shares but 2/120 confirms right now. This came right after the marathon block with 100% luck, what's up?

BTW, round duration in quick stats is showing "15491d 19:36:02" for me right now... something looks screwed up.

Very interesting thread.

I'm watching you closely, BFL Wink

Just fulfilled my initial pledge with a bitcoin that's special to me:
It's the first one my BFL/RaspberryPi combo mined together.

Quote from: kano on May 25, 2012, 10:45:46 PM

Quote from: wogaut on May 25, 2012, 06:39:58 PM

I've been trying to run cgminer with remoting into my Raspberry Pi via ssh.
I tried no use nohup to avoid for cgminer to receive a SIGHUP when I leave ssh, but whenever the input is redirected no /dev/null (what nohup does), cgminer maxes out the CPU usage. Bad thing on the RPi.

How can I get around this?

Add to cgminer:
... --api-listen --api-allow W:127.0.0.1,192.168.0/24 ...
(of course you'll have to correct 192.168.0 to match your network)

Then to exit cgminer:
echo -n quit | nc 127.0.0.1 4028 ; echo
OR, if you don't have nc (or ncat) then you can use:
java API quit
if you have API.class in the current directory

i.e. see if a clean exit resolves it

Also, killing screen after 1 second is often before cgminer completes exiting
(since it has to wait on a bunch of threads and then exit with the summary)
... just get the screen to exit when cgminer exits

Edit: OK that reply is a mix of comments to the previous posts ... but the point is yes use screen ... and also a clean exit

screen works well.

the api-listen I'll try soon too, seems quite convenient for remote control.

I'm interested to see in how low this goes Cheesy

Watching closely...

Quote from: P_Shep on May 25, 2012, 06:50:32 PM

Use screen instead?

Look at the scripts in my dd-wrt implementation in my sig. may help you.

Ah, the S99cgminer script I presume. I'll try the screen command.

Thanks!

OK, with the hint of P_Shep https://bitcointalk.org/index.php?topic=28402.msg919542#msg919542
and some additional command lines here's how to compile and install cgminer on your Raspberry Pi:

Note: These instructions are for Debian Squeeze Linux http://www.raspberrypi.org/downloads. Other Linux distros may differ.

Code:

sudo apt-get update
sudo apt-get install autoconf
sudo apt-get install libtool
sudo apt-get install libncurses-dev
sudo apt-get install yasm
sudo apt-get install curl
sudo apt-get install libcurl4-openssl-dev
sudo apt-get install pkg-config

Download zip archive from https://github.com/ckolivas/cgminer

Code:

unzip ckolivas-cgminer-v2.4.1-9-gb69d735.zip 
cd ckolivas-cgminer-b69d735/
aclocal
./autogen.sh
export LIBCURL_CFLAGS='-I/usr/include/curl'
export LIBCURL_LIBS='-L/usr/lib -lcurl'
./configure --enable-bitforce
make
sudo make install

Now to run your BFL Single:
Plug it in now (may need a USB hub if you plan to also use USB kbd/mouse, I got around that with a PS/2-USB splitter).
Do a quick check if it registered with your Raspberry Pi Linux:

Code:

ls -l /dev/ttyUSB*

will show some ttyUSB device (typically ttyUSB0).
If not, check out that post: https://bitcointalk.org/index.php?topic=65879.msg915045#msg915045

Run cgminer the usual way but add the option

Code:

-S auto

Have fun!

Quote from: P_Shep on May 24, 2012, 04:54:01 PM

Quote from: wogaut on May 24, 2012, 04:50:06 PM

Does anybody have an idea what the issue might be?

to get it working in openwrt, i had to manually specify the location of the lib.

LIBCURL_CFLAGS=-L/path/to/lib LIBCURL_LIBS=-lcurl

Good catch, ~~but~~ after defining these variables myself ./configure works

Code:

LIBCURL_CFLAGS='-I/usr/include/curl'
LIBCURL_LIBS='-L/usr/lib -lcurl'

and having a closer look at the error, it appears to me that it doesn't like the syntax of PKG_CHECK_MODULES.
Commenting out these two lines unfortunately leads to an undefined variable ACEOF which causes more issues.
Did you have these issues too?

Scratch that, I had to run aclocal before ./autogen.sh

I'm reposting this from this newbie thread (since I think here's a better place for it:

Quote from: wogaut on May 24, 2012, 03:59:42 PM

Re: Running an FPGA on Raspberry Pi, possible?

OK, here's how far I got installing cgminer on my Raspberry Pi:

Code:

sudo apt-get update
sudo apt-get install autoconf
sudo apt-get install libtool
sudo apt-get install libncurses-dev
sudo apt-get install yasm
sudo apt-get install curl
sudo apt-get install libcurl4-openssl-dev
sudo apt-get install pkg-config

Download zip archive from https://github.com/ckolivas/cgminer

Code:

unzip ckolivas-cgminer-v2.4.1-9-gb69d735.zip 
cd ckolivas-cgminer-b69d735/
./autogen.sh
./configure --enable-bitforce

configure then quits after a while with the following errors:

Code:

./configure: line 9269: syntax error near unexpected token `PKG_CHECK_MODULES'
./configure: line 9269: `PKG_CHECK_MODULES(LIBCURL, libcurl >= 7.15.6, AC_DEFINE([CURL_HAS_SOCKOPT], [1], [Defined if version of curl supports sockopts.]),'

Doing a

Code:

curl-config --version

results in

Code:

libcurl 7.21.0

so the libcurl version should work.

Does anybody have an idea what the issue might be?

Quote from: Jackbauer on May 24, 2012, 04:14:12 PM

Python will run fine on the device, its what they recommend you learn (the device is mostly meant for students). But honestly unless you try it yourself you will never know, ARM is a weird platform, some things will run fine with no issues, some things will explode.

I'm confused, is this in response to the specific configure issues I quoted in my last post? Doesn't seem to help, sorry man.

OK, here's what I got so far:

Code:

sudo apt-get update
sudo apt-get install autoconf
sudo apt-get install libtool
sudo apt-get install libncurses-dev
sudo apt-get install yasm
sudo apt-get install curl
sudo apt-get install libcurl4-openssl-dev
sudo apt-get install pkg-config

Download zip archive from https://github.com/ckolivas/cgminer

Code:

unzip ckolivas-cgminer-v2.4.1-9-gb69d735.zip 
cd ckolivas-cgminer-b69d735/
./autogen.sh
./configure --enable-bitforce

configure then quits after a while with the following errors:

Code:

./configure: line 9269: syntax error near unexpected token `PKG_CHECK_MODULES'
./configure: line 9269: `PKG_CHECK_MODULES(LIBCURL, libcurl >= 7.15.6, AC_DEFINE([CURL_HAS_SOCKOPT], [1], [Defined if version of curl supports sockopts.]),'

Any insights are appreciated!

Edit: Doing a

Code:

curl-config --version

results in

Code:

libcurl 7.21.0

so the libcurl version should work.

Has anyone done that yet who can share their experience?

In this thread there's a nice discussion about fans with the BFL:
https://bitcointalk.org/index.php?topic=60586.msg868363#msg868363

I just replaced mine with the Noiseblocker BlackSilentPro.
Sooo much more quiet (and a more healthy acoustic frequency spectrum) and about the same temperature as the stock BFL fan.

Boy, that firmware update almost gave me a heart attack. Cry

My single was happily mining at 832MH/s and 48deg C with zero errors, so I gave the update a try.
I ended up getting about 440MH/s average on the 864 update and 370MH/s average on the 872 update, with mining rates fluctuating widely between 75 and 850MH/s and error rate through the roof, while FPGA temps were about 34deg C.

So I flashed it back to the default 832MH/s firmware and it's happily mining again as before.

Quote from: bo2573 on May 22, 2012, 08:07:34 PM

It took me about 4 hours last night to figure this out.

I wish you would have posted this 24 hours ago. Undecided

Dang, if I only knew that sooner!
Then I hope it will be helpful to someone else Cheesy

Quote from: gigavps on February 27, 2012, 07:48:01 PM

I have determined that BAMT does not contain the proper serial support needed to create the ttyUSB* files.

Just want to note the solution to that issue here (this has been posted by somebody elsewhere too), since I searched for it a while ago and it's somewhat frustrating to find this thread without the obvious solution for the generic Linux user without automatic ttyUSB mapping:

Depending on yourLinux distro your BFL might not show as a ttyUSB* device.

If you do a

Code:

ls /dev/ttyUSB*

and nothing shows up then

Code:

sudo modprobe ftdi_sio vendor=0x0403 product=0x6014
sudo chmod a+rw /dev/ttyUSB*

This reqires that you have general USB device support installed.

I got the vendor/product pair from dmesg (after plugging in the Single)

Code:

dmesg | grep -i bitforce

to find the USB device number

Code:

dmesg | grep -i vendor

to find the vendor/product codes (use the one with the matching USB device number)

compile cgminer with

Code:

./configure --enable-bitforce

and then

Code:

cgminer -S auto

and all the usual other parameters, should find your BFL Single.

Freut mich dass von meiner Alma Mater auch etwas über Bitcoin kommt.

Danke für den Link!

Quote from: jddebug on May 15, 2012, 07:20:20 AM

I flashed 4 brand new singles with the 872 firmware. Plugged them into my Kill-O-Watt using stock power supply on each.

With the 832 firmware they took total of 322 watts.

With the 872 firmware they take a total of 336 watts.

Went from 3250 MH/s to 3400 MH/s. EDIT: I had mistyped as 3340.

(cgminer) U went from 44 to U of 48

I believe I'm seeing some throttling occurring on 2 of them although the light never seems to blink. I'll flash them to the next level down and see that I get.

So with those numbers you have about the same MH/W just dividing the numbers you posted (the throttling might result in some variability over time).
That is good to hear, as this would mean you just got 4.6% more Singles (if stable).

Good point. Several times when upgrading my internet connection, my provider sent me a new "free" gateway/router/wireless access point. I might as well use them for something.

Also I have a couple of Buffalo Link Stations with USB and Ethernet. I have installed the open Linux ver on them to ssh into them, maybe I can install cgminer there?