| View previous topic :: View next topic |
| Author |
Message |
number_nine
Tux's lil' helper
Joined: 05 May 2005
Posts: 136
|
 Posted: Tue Mar 14, 2006 5:11 pm Post subject: setiathome / boinc on AMD64 |
 |
|
I can't seem to get setiathome (via boinc) to run on my AMD64 machine. I have the following lines in /etc/portage/package.keywords:
| Code: |
sci-misc/boinc ~amd64
sci-astronomy/setiathome ~amd64
|
This leaves me with boinc version 4.72.20050813-r3 and setiathome 4.18-r1 installed on my system.
Now, when I try to do "/etc/init.d/boinc attach", it prompts me for the project URL, I enter "http://setiathome.berkeley.edu", and when it prompts me for my key, I enter that.
This is the output I then receive:
| Code: |
* Starting BOINC ... [ ok ]
* Attaching to project ... [ !! ]
2006-03-13 16:58:51 [---] Memory Inventory: Memory total - 1002.79 MB, Swap total - 980.52 MB
2006-03-13 16:58:51 [---] Disk Inventory: Disk total - 7.52 GB, Disk available - 6.80 GB
2006-03-13 16:58:51 [---] No general preferences found - using BOINC defaults
2006-03-13 16:58:51 [---] Remote control not allowed; using loopback address
2006-03-13 16:58:51 [---] This computer is not attached to any projects.
2006-03-13 16:58:51 [---] There are several ways to attach to a project:
2006-03-13 16:58:51 [---] 1) Run the BOINC Manager and click Projects.
2006-03-13 16:58:51 [---] 2) (Unix/Mac) Use boinc_cmd --project_attach
2006-03-13 16:58:51 [---] 3) (Unix/Mac) Run this program with the -attach_project command-line option.
2006-03-13 16:58:51 [---] Visit http://boinc.berkeley.edu for more information
|
Why can't I attach to the project? For what it's worth, I do have a seti@home account, and have the boinc client+setiathome running on my other machines.
Any help would be much appreciated,
Thanks,
Matt |
|
| Back to top |
|
 |
hielvc
Advocate
Joined: 19 Apr 2002
Posts: 2805
Location: Oceanside, Ca
|
| Posted: Tue Mar 14, 2006 6:34 pm Post subject: |
|
|
What I did this morning to connect a new computer was after trying the "/etc/init.d/boinc attach" method of frusttration, was at the the end of the boinc emerge was | Quote: | If you need to use the graphical client the password is in
* /var/lib/boinc/gui_rpc_auth.cfg which is randomly generated
* by BOINC. You can change this to something more memorable. |
So I ran boinc_gui put in that password , put in the seti URL, http://setiathome.berkeley.edu/ ,It then asked " new or existing" ==> existing EMAIL and new password I created this morning a damn if didnt finally connect.
_________________
An A-Z Index of the Linux BASH command line |
|
| Back to top |
|
|
3n0k
n00b
Joined: 21 Aug 2004
Posts: 73
Location: Portugal
|
| Posted: Fri Mar 24, 2006 9:47 am Post subject: |
|
|
god damn... am i pissed up or what?
where do you insert that password? wich username do you use? |
|
| Back to top |
|
|
3n0k
n00b
Joined: 21 Aug 2004
Posts: 73
Location: Portugal
|
| Posted: Fri Mar 24, 2006 11:18 am Post subject: |
|
|
i just did it.. dunno why i couldn't login yesterday and today i can.. as i used the same method.
bu now i have another problem:
| Quote: |
Fri Mar 24 09:41:10 2006||Starting BOINC client version 5.2.14 for x86_64-pc-linux-gnu
Fri Mar 24 09:41:10 2006||libcurl/7.15.1 OpenSSL/0.9.7i zlib/1.2.3 libidn/0.5.15
Fri Mar 24 09:41:10 2006||Data directory: /var/lib/boinc
Fri Mar 24 09:41:10 2006||Processor: 1 AuthenticAMD AMD Athlon(tm) 64 Processor 3200+
Fri Mar 24 09:41:10 2006||Memory: 1002.87 MB physical, 494.18 MB virtual
Fri Mar 24 09:41:10 2006||Disk: 27.84 GB total, 22.20 GB free
Fri Mar 24 09:41:10 2006||No general preferences found - using BOINC defaults
Fri Mar 24 09:41:10 2006||Remote control not allowed; using loopback address
Fri Mar 24 09:41:10 2006||This computer is not attached to any projects.
Fri Mar 24 09:41:10 2006||There are several ways to attach to a project:
Fri Mar 24 09:41:10 2006||1) Run the BOINC Manager and click Projects.
Fri Mar 24 09:41:10 2006||2) (Unix/Mac) Use boinc_cmd --project_attach
Fri Mar 24 09:41:10 2006||3) (Unix/Mac) Run this program with the -attach_project command-line option.
Fri Mar 24 09:41:10 2006||Visit http://boinc.berkeley.edu for more information
Fri Mar 24 09:41:12 2006||Running CPU benchmarks
Fri Mar 24 09:42:11 2006||Benchmark results:
Fri Mar 24 09:42:11 2006|| Number of CPUs: 1
Fri Mar 24 09:42:11 2006|| 1928 double precision MIPS (Whetstone) per CPU
Fri Mar 24 09:42:11 2006|| 5213 integer MIPS (Dhrystone) per CPU
Fri Mar 24 09:42:11 2006||Finished CPU benchmarks
Fri Mar 24 09:42:12 2006||Resuming computation and network activity
Fri Mar 24 09:42:12 2006||request_reschedule_cpus: Resuming activities
Fri Mar 24 11:12:54 2006||Fetching config info from http://setiathome.berkeley.edu/get_project_config.php
Fri Mar 24 11:13:18 2006|http://setiathome.berkeley.edu/|Master file download succeeded
Fri Mar 24 11:13:18 2006|http://setiathome.berkeley.edu/|Sending scheduler request to http://setiboinc.ssl.berkeley.edu/sah_cgi/cgi
Fri Mar 24 11:13:18 2006|http://setiathome.berkeley.edu/|Reason: Requested by user
Fri Mar 24 11:13:18 2006|http://setiathome.berkeley.edu/|Requesting 8640 seconds of new work
Fri Mar 24 11:13:20 2006|http://setiathome.berkeley.edu/|Scheduler request to http://setiboinc.ssl.berkeley.edu/sah_cgi/cgi succeeded
Fri Mar 24 11:13:20 2006|SETI@home|Message from server: platform 'x86_64-pc-linux-gnu' not found
Fri Mar 24 11:13:20 2006|SETI@home|New host venue: home
Fri Mar 24 11:13:20 2006|SETI@home|Successfully attached to SETI@home
Fri Mar 24 11:14:48 2006||request_reschedule_cpus: project op
Fri Mar 24 11:14:52 2006|SETI@home|Sending scheduler request to http://setiboinc.ssl.berkeley.edu/sah_cgi/cgi
Fri Mar 24 11:14:52 2006|SETI@home|Reason: Requested by user
Fri Mar 24 11:14:52 2006|SETI@home|Requesting 8640 seconds of new work
Fri Mar 24 11:14:57 2006|SETI@home|Scheduler request to http://setiboinc.ssl.berkeley.edu/sah_cgi/cgi succeeded
Fri Mar 24 11:14:57 2006|SETI@home|Message from server: platform 'x86_64-pc-linux-gnu' not found
|
now what?  |
|
| Back to top |
|
|
3n0k
n00b
Joined: 21 Aug 2004
Posts: 73
Location: Portugal
|
| Posted: Fri Mar 24, 2006 11:31 pm Post subject: |
|
|
ok.. solved..
seems like you have to emerge setiathome too in order to start "playing". |
|
| Back to top |
|
|
hielvc
Advocate
Joined: 19 Apr 2002
Posts: 2805
Location: Oceanside, Ca
|
| Posted: Sat Mar 25, 2006 5:01 pm Post subject: |
|
|
Glad jyou got it going. It sounds as if you had as much fun ss I did. We some how got it up and going useing the monkey at keyboard approache  Whats really wierd is | Code: | emerge setia -s
Searching...
[ Results for search key : setia ]
[ Applications found : 1 ]
* sci-astronomy/setiathome [ Masked ]
Latest version available: 4.18-r1
Latest version installed: [ Not Installed ]
Size of files: 7,730 kB
Homepage: http://setiweb.ssl.berkeley.edu/
Description: Search for Extraterrestrial Intelligence SETI@home
License: GPL-2 |
Yet when I run "top" theres setiathome-4.02 running. Is there a smart person out there who can explain this wierdness ?
_________________
An A-Z Index of the Linux BASH command line |
|
| Back to top |
|
|
Icer
Guru
Joined: 26 Aug 2003
Posts: 395
Location: @home
|
| Posted: Sat Apr 08, 2006 2:53 pm Post subject: |
|
|
After reading numerous posts and emerging and re-emerging boinc several times and pulling my hair and what not the thing started working. Now it seems that as silly as it is boinc doesnt support 64bit cpu's. To use boinc and seti at home one has to emerge setiatohome using i686 chost. Like this:
| Code: | | CHOST="i686-pc-linux-gnu" emerge -a setiathome |
This will pull boinc too. Now I dunno why, but when doing update world it seems that many packages(not just boinc) downgrade and on next update they upgrade the same package. Frustrating. Anyhoo if you notice your boinc was downgraded you only need to upgrade boinc back and you dont need to emerge setiathome again. Note that before upgrading boinc stop boinc and after upgrade restart it:
| Code: | /etc/init.d/boinc stop
emerge -a boinc
/etc/init.d/boinc start
|
Then I use boinc manager to continue projects.
_________________
Everything can be done. There's just a longer delivery time for impossible projects. |
|
| Back to top |
|
|
number_nine
Tux's lil' helper
Joined: 05 May 2005
Posts: 136
|
| Posted: Wed Jun 14, 2006 2:52 am Post subject: |
|
|
| Icer wrote: | | After reading numerous posts and emerging and re-emerging boinc several times and pulling my hair and what not the thing started working. Now it seems that as silly as it is boinc doesnt support 64bit cpu's. |
Do they document that anywhere? Or is it only 64 bit CPUs running Linux?
| Icer wrote: | To use boinc and seti at home one has to emerge setiatohome using i686 chost. Like this:
| Code: | | CHOST="i686-pc-linux-gnu" emerge -a setiathome |
This will pull boinc too. Now I dunno why, but when doing update world it seems that many packages(not just boinc) downgrade and on next update they upgrade the same package. Frustrating. Anyhoo if you notice your boinc was downgraded you only need to upgrade boinc back and you dont need to emerge setiathome again. Note that before upgrading boinc stop boinc and after upgrade restart it:
| Code: | /etc/init.d/boinc stop
emerge -a boinc
/etc/init.d/boinc start
|
Then I use boinc manager to continue projects. |
Did you use the "i686-pc-linux-gnu" CHOST for the emerge of boinc as well?
Does anyone have a comprehensive HOWTO or Wiki on how to set up boinc + setiathome on x86_64 under gentoo? I had a working setup for a few months. Now it no longer works. I have no idea what changed (if anything). I can't remember how I got it working in the first place---I think it just magically "started working" and by then I was so frustrated that I didn't bother to (1) figure out what actually made it work and (2) document it.
Does anyone know if any bugs have been filed for this? I.e., in particular, the whole "/etc/init.d/boinc attach" just doesn't work (at least on AMD64).
Thanks! |
|
| Back to top |
|
|
skutnar
n00b
Joined: 13 Jun 2006
Posts: 65
|
| Posted: Sat Jun 17, 2006 3:29 pm Post subject: |
|
|
Simple answer: don't use BOINC or SETI from Portage. x86_64-pc-linux-gnu is not yet a supported platform. If you want to read more info, check the BOINC forums and/or the forums for the projects you want to run.
SETI is running enhanced now, so the version in Portage is obsolete and useless. 4.18 will never be used again.
For background, the "proper" way to install SETI from Portage required that you emerge i686 BOINC first, then attached to SETI, which would download the standard application and some work. After it started crunching, stop BOINC and emerge i686 SETI. But, it's moot now as I mentioned. |
|
| Back to top |
|
|
number_nine
Tux's lil' helper
Joined: 05 May 2005
Posts: 136
|
| Posted: Tue Jun 20, 2006 4:33 am Post subject: |
|
|
| skutnar wrote: | | Simple answer: don't use BOINC or SETI from Portage. x86_64-pc-linux-gnu is not yet a supported platform. If you want to read more info, check the BOINC forums and/or the forums for the projects you want to run. |
So are you running seti@home on AMD64?
It then looks like using portage to install boinc+setiathome on AMD64 is a futile endeavor (and based on my experience pretty much always has been).
Should I just go to the boinc and setiathome web pages, and do a manual install? Is that what you've done (assuming you answered yes to my first question)? What platform did you choose? Did you just use the "vanilla" x86 (32 bit) version, or did you go with one of those "optimized" setiathome binaries for Athlon 64?
What about BOINC for other distributed computing projects on AMD64? Do you run folding@home or any other grid computing application?
Basically, I'd just like to compute my extra CPU cycles to something with a minimum of hassle. It's a shame the seti/boinc/portage/??? folks haven't jumped on the Athlon 64 platform---it just seems so well suited to this kind of project.
Oh well!
Thanks for your input!
#9 |
|
| Back to top |
|
|
morrow
n00b
Joined: 25 Dec 2004
Posts: 17
Location: NL
|
| Posted: Fri Jun 23, 2006 9:35 pm Post subject: |
|
|
I stumbled across this website, it's referenced in the boinc/setiathome forums:
http://www.lb.shuttle.de/apastron/boincDown.shtml
In any case, just download the archive, extract it and attach to the project ...
I'm not sure about the issue mentioning that some configurations of AMD64 systems have speed problems. I just downloaded the binary, extracted it and fired it up, so I might be able to comment on it in a couple of days. |
|
| Back to top |
|
|
girona
n00b
Joined: 20 Apr 2004
Posts: 20
|
| Posted: Sat Jul 01, 2006 11:11 am Post subject: Updated boinc ebuild... |
|
|
I posted an updated ebuild on bugzilla. It uses cvs to pull down the latest stable version. Copy the init and conf files from the old version, may need to change the attach command to use new syntax (put in --host and --passwd), host is localhost and passwd is the gui_rpc one.
It works for me on plain old x86 so cant guarantee for amd64. Make sure you uninstall previous version otherwise compilation uses libboinc in /usr/lib instead of new one it just compiled (ordering of -L in Makefile is bad).
https://bugs.gentoo.org/show_bug.cgi?id=135309
Tom |
|
| Back to top |
|
|
skutnar
n00b
Joined: 13 Jun 2006
Posts: 65
|
| Posted: Thu Jul 06, 2006 4:23 am Post subject: |
|
|
| number_nine wrote: | | skutnar wrote: | | Simple answer: don't use BOINC or SETI from Portage. x86_64-pc-linux-gnu is not yet a supported platform. If you want to read more info, check the BOINC forums and/or the forums for the projects you want to run. |
So are you running seti@home on AMD64?
It then looks like using portage to install boinc+setiathome on AMD64 is a futile endeavor (and based on my experience pretty much always has been).
Should I just go to the boinc and setiathome web pages, and do a manual install? Is that what you've done (assuming you answered yes to my first question)? What platform did you choose? Did you just use the "vanilla" x86 (32 bit) version, or did you go with one of those "optimized" setiathome binaries for Athlon 64?
What about BOINC for other distributed computing projects on AMD64? Do you run folding@home or any other grid computing application?
Basically, I'd just like to compute my extra CPU cycles to something with a minimum of hassle. It's a shame the seti/boinc/portage/??? folks haven't jumped on the Athlon 64 platform---it just seems so well suited to this kind of project.
Oh well!
Thanks for your input!
#9 |
I apologize for not responding sooner. I don't regularly visit the Gentoo forums and tend to forget what threads I've posted to! 
I don't run Linux AMD64 (yet). All my Linux machines are 32-bit. I just happen to follow the BOINC projects somewhat closely and have picked up the information along the way.
You could do a manual install, but it is far preferable to have Portage do a BOINC install for you. Try the new ebuild to see what it gives you. I "cheated" a few weeks ago by using the 5.2.14 out of Portage, then uninstalling it. Portage left the cfgpro'd files in /etc/conf.d, /etc/init.d, and /var/lib/boinc which I then used with the standard client download. It works great. |
|
| Back to top |
|
|
l_bratch
Guru
Joined: 08 Feb 2005
Posts: 494
Location: Jersey
|
| Posted: Tue Sep 12, 2006 5:17 pm Post subject: |
|
|
| Icer wrote: | After reading numerous posts and emerging and re-emerging boinc several times and pulling my hair and what not the thing started working. Now it seems that as silly as it is boinc doesnt support 64bit cpu's. To use boinc and seti at home one has to emerge setiatohome using i686 chost. Like this:
| Code: | | CHOST="i686-pc-linux-gnu" emerge -a setiathome |
This will pull boinc too. Now I dunno why, but when doing update world it seems that many packages(not just boinc) downgrade and on next update they upgrade the same package. Frustrating. Anyhoo if you notice your boinc was downgraded you only need to upgrade boinc back and you dont need to emerge setiathome again. Note that before upgrading boinc stop boinc and after upgrade restart it:
| Code: | /etc/init.d/boinc stop
emerge -a boinc
/etc/init.d/boinc start
|
Then I use boinc manager to continue projects. |
This worked for me, except I didn't emerge setiathome, I just let the boinc client (which I compiled with CHOST set to i686) download setiathome data itself.
Edit:
This didn't actually work at all - nothing seems to download correctly within boinc, it all fails the checksum test, and boinc reports 0 disk space. |
|
| Back to top |
|
|
zhark
n00b
Joined: 26 Feb 2006
Posts: 29
|
| Posted: Mon Oct 09, 2006 11:48 pm Post subject: |
|
|
Anyone got BOINC from portage running on AMD64?
I tried the x86_64 version of boinc from portage, created custom app_info.xml's and downloaded the 32-bit executables from the project homepages. It went as far as downloading WU's, but then every files failes with "checksum or signature error".
I tried installing the x86 (32bit) version with CHOST=i686.. as mentioned above, but got a problem with libcurl beeing unusable (according to configure).
Anyone got a solution for the checksum error problem? |
|
| Back to top |
|
|
likewhoa
l33t
Joined: 04 Oct 2006
Posts: 778
Location: Brooklyn, New York
|
| Posted: Sun Dec 17, 2006 8:29 am Post subject: |
|
|
| same here,.. gonna need to figure it out.. |
|
| Back to top |
|
|
gliverman
n00b
Joined: 24 Dec 2006
Posts: 51
Location: Carrollton, GA
|
| Posted: Wed Jan 10, 2007 1:08 am Post subject: Common thread |
|
|
I am in the same boat as you guys... I want seti on my amd64 machine. I think you should merge your discussion with BOINC and seti@home on AMD64 so that we can all work together to find a solution. That topic is in the Gentoo on AMD64 forum so it might be easier for people to find also... at least it was for me  |
|
| Back to top |
|
|
swimmer
Veteran
Joined: 15 Jul 2002
Posts: 1330
Location: Netherlands
|
| Posted: Wed Jan 10, 2007 2:13 am Post subject: |
|
|
Hmm - I got it working by just adding "sci-misc/boinc ~amd64" to /etc/portage/package.keywords and emerging boinc. Afterwards I downloaded http://www.lb.shuttle.de/apastron/boinc/boinc5.4.9seti5.13-linux-x86_64.tar.bz2 and unpacked it in /var/lib/boinc/projects/. The last step was to move boinc_5.4.9_opteron-64-linux-gnu to /usr/local/bin and change the referring variable BOINCBIN in /etc/conf.d/boinc.
After that it was simply a matter of starting the boinc service and attaching a project ...
HTH
swimmer |
|
| Back to top |
|
|
gliverman
n00b
Joined: 24 Dec 2006
Posts: 51
Location: Carrollton, GA
|
| Posted: Wed Jan 10, 2007 2:35 am Post subject: |
|
|
| swimmer wrote: | | The last step was to move boinc_5.4.9_opteron-64-linux-gnu to /usr/local/bin and change the referring variable BOINCBIN in /etc/conf.d/boinc. |
Pardon my ignorance... but where will I find "boinc_5.4.9_opteron-64-linux-gnu" if I try this? |
|
| Back to top |
|
|
swimmer
Veteran
Joined: 15 Jul 2002
Posts: 1330
Location: Netherlands
|
|
| Back to top |
|
|
gliverman
n00b
Joined: 24 Dec 2006
Posts: 51
Location: Carrollton, GA
|
| Posted: Wed Jan 10, 2007 12:58 pm Post subject: Thanks! |
|
|
| Thanks swimmer! That one works for me too... now if we can get the one in Portage to do the same |
|
| Back to top |
|
|
swimmer
Veteran
Joined: 15 Jul 2002
Posts: 1330
Location: Netherlands
|
| Posted: Wed Jan 10, 2007 1:03 pm Post subject: |
|
|
Glad I could help  |
|
| Back to top |
|
|
urcindalo
l33t
Joined: 08 Feb 2005
Posts: 623
Location: Almeria, Spain
|
| Posted: Thu Mar 15, 2007 9:48 am Post subject: |
|
|
Muchísimas gracias, swimmer.
Thanks to you I've finally recovered a working SETI@home on my AMD64. Now my two cents: you can download a new x86_64 binary from here. The rest of the instructions remain the same. |
|
| Back to top |
|
|
swimmer
Veteran
Joined: 15 Jul 2002
Posts: 1330
Location: Netherlands
|
| Posted: Thu Mar 15, 2007 11:19 am Post subject: |
|
|
No hay de que
You helped me as well by remembering me to look for the latest client 
Saludos
swimmer |
|
| Back to top |
|
|
urcindalo
l33t
Joined: 08 Feb 2005
Posts: 623
Location: Almeria, Spain
|
| Posted: Wed Mar 28, 2007 9:55 am Post subject: |
|
|
I've updated boinc to portage's latest version (5.8.15 ~amd64), put back the boinc client reference to portage's one in /etc/conf.d/boinc: | Code: | # Location of the boinc command line binary
BOINCBIN="/usr/bin/boinc_client"
#BOINCBIN="/usr/local/bin/boinc" |
and restarted /etc/init.d/boinc. KBoincSpy showed SETI@home working.
To be completely sure, I restarted. After that boinc is still working, as can be seen from within KBoincSpy.
Since the only change done is which boinc client to use (now portage's), I don't know if this means portage's boinc is back to work on AMD64 without following the instructions by swimmer.
Hope this info helps. |
|
| Back to top |
|
|
|
Other Things Gentoo
