Topic: bitcoind running on the N900 smartphone (Read 10758 times)
Oh, i see, thanx
Btw, when i do bitcoind stop it seems it doesn't close (i still see it running with htop, and trying to fire it up again gives me an error about the .lock), am i doing somthing wrong?
It takes quite a while (a few minutes) to stop but it does eventually. I don't know why.
Run it with '-no-irc' to prevent it from making an IRC connection. You can also use '-no-listen' to prevent it from listening for incoming connections and use '-connect' to explicitly connect to a node. This minimizes the number of connections to your phone.
It's -nolisten and -noirc.
Btw, when i do bitcoind stop it seems it doesn't close (i still see it running with htop, and trying to fire it up again gives me an error about the .lock), am i doing somthing wrong?
Bitcoin opens an IRC connection to lfnet for bootstrapping (finding peers). New nodes have to find out about existing nodes somehow.
Run it with '-no-irc' to prevent it from making an IRC connection. You can also use '-no-listen' to prevent it from listening for incoming connections and use '-connect' to explicitly connect to a node. This minimizes the number of connections to your phone.
Update: 2010-02-04: The changes to ParseHex are no longer needed as they're part of the bitcoin source now. An updated build for the N900 is available here:
http://www.bluishcoder.co.nz/bitcoin-pool/bitcoind-b1a657.gz
This is built from github commit b1a657.
When I'm running bitcoind-b1a657 I notice an irc connection to some irc server being established, e.g.
tcp 0 0 192.168.3.118:56738 irc.lfnet.org:ircd ESTABLISHED
What's the purpose of this connection?
Update: 2010-02-04: The changes to ParseHex are no longer needed as they're part of the bitcoin source now. An updated build for the N900 is available here:
http://www.bluishcoder.co.nz/bitcoin-pool/bitcoind-b1a657.gz
This is built from github commit b1a657.
When I'm running bitcoind-b1a657 I notice an irc connection to some irc server being established, e.g.
tcp 0 0 192.168.3.118:56738 irc.lfnet.org:ircd ESTABLISHED
What's the purpose of this connection?
Sorry, I haven't read this whole thread but I've seen that some people managed to hash at around 280kH/s. I know the N900 has some graphic capable hardware: any chance this device could be used to hash?
lol nice, probably not the most effective thing but nice nonetheless
I'm getting 280 khash/s while overclocked to 1150 Mhz. Not bad at all. 
If you want to fry your N900 in a matter of months (at most).
I'm getting 280 khash/s while overclocked to 1150 Mhz. Not bad at all.
Could you make a .deb for installing this please (optfication and all) ?
You can also do this on android by installing a few libs or using a chroot. 
I was referred to this topic from https://www.bitcoin.org/smf/index.php?topic=3940.msg56271#msg56271 . Did you have to change anything in the makefile? If so what all did you have to change and/or replace?
I had to remove the -march and SSE stuff from the makefile. I've posted the makefile I used in the other thread. Hope that helps.
I was referred to this topic from https://www.bitcoin.org/smf/index.php?topic=3940.msg56271#msg56271 . Did you have to change anything in the makefile? If so what all did you have to change and/or replace?
... make one minor change to util.cpp. The ParseHex function in util.cpp has code like:
'c' is a 'char' type which is unsigned so this comparison never does what's expected. Changing both instances of this to the following gets a working bitcoind:
This "fix" seems wrong. Really, 'phexdigit' should be redefined to a 'signed char' array, and 'c' a simple 'signed char'-- then none of this casting mess is necessary. The problem stems from the fact that the C standard allows 'char' to be either signed or unsigned: implementors can choose (and I've often see it signed). That means if you might need to use values above 127 or below 0, you must specify signed/unsigned explicitly for your variables. What (char)-1 does, is turn it into 0xff (255) on compilers that have an unsigned 'char', which might work, but it really depends a lot on how the compiler handles the constant "-1" stored in the (undefined signedness) phexdigit array. Code:
if (c == -1)
'c' is a 'char' type which is unsigned so this comparison never does what's expected. Changing both instances of this to the following gets a working bitcoind:
Code:
if (c == (char)-1)
I've updated the N900 binary to a newer version. I built from gitub commit b1a657. It's available here:
http://www.bluishcoder.co.nz/bitcoin-pool/bitcoind-b1a657.gz
I start it on the N900 using:
Replacing 'xx.xx.xx.xx' with a node to connect too. This means no incoming connections will be made to the phone and only one connection is made outgoing.
http://www.bluishcoder.co.nz/bitcoin-pool/bitcoind-b1a657.gz
I start it on the N900 using:
Code:
./bitcoind -noirc -connect=xx.xx.xx.xx -nolisten
Replacing 'xx.xx.xx.xx' with a node to connect too. This means no incoming connections will be made to the phone and only one connection is made outgoing.
I experience problems with the bitcoin version for the n900 (I got it from http://bluishcoder.co.nz/bitcoin-pool/bitcoind.gz). When I try to execute the file I get the following error:
Did you download it and gunzip it on the phone? I just tried the following steps from the N900 terminal and it worked:
Code:
$ wget http://www.bluishcoder.co.nz/bitcoin-pool/bitcoind.gz
$ gunzip bitcoind.gz
$ chmod +x bitcoind.gz
$ ./bitcoind
I'm off-topic but : anyone has a spare USB cable for n900 to sell for bitcoins ?
Hi all,
I experience problems with the bitcoin version for the n900 (I got it from http://bluishcoder.co.nz/bitcoin-pool/bitcoind.gz). When I try to execute the file I get the following error:
http://img227.imageshack.us/img227/2541/screenshot15d.png
I'm running version 20.2010.36-2.
Cheers,
britschler
I experience problems with the bitcoin version for the n900 (I got it from http://bluishcoder.co.nz/bitcoin-pool/bitcoind.gz). When I try to execute the file I get the following error:
http://img227.imageshack.us/img227/2541/screenshot15d.png
I'm running version 20.2010.36-2.
Cheers,
britschler
Jump to: