Forum > Linux

64-bit science apps based on Rev-2.2B code released

<< < (2/3) > >>

Metod, S56RKO:

--- Quote from: Simon on 13 Apr 2007, 06:15:13 pm ---Nota bene - Requirements

* 64-bit Linux 2.6.x - sorry, no 2.4 supported.
* glibc 2.3.4 or newer - find out what version yours is by typing "/lib/libc.so.6" on a new line - as if you were trying to execute the library itself, that will show you details about your installed glibc version.
* 64-bit BOINC client - caution: this will limit your choice of other project to participate in at the same time, because not a lot of them offer 64-bit science apps yet.
--- End quote ---

While it's a good idea to have 64-bit BOINC client, this is not really a requirement. I've tested and successfully run 64-bit SAH app with 32-bit BOINC client (I need that for CPDN).


--- Quote from: michael37 on 14 Apr 2007, 02:59:32 am ---I switched from Seti 32-bit apps to 64-bit apps in midstream and have experienced no ill effects.  As usual with risky configurations, YMMV.    I suspect switching Boincs from i386 to x86_64 architecture may  have ill effects. 
--- End quote ---

You can change BOINC from i686 to x86_64, but you need to hand-edit the file client_state.xml. Near the end of the file there's tag <platform_name> which needs to match platform name of your BOINC client. If it doesn't, BOINC client will reset all the projects.
Been there, done that ... :(

Simon:
Ah, good hint, Metod!

That's happened to me before, as well.
Seems useful to be able to run a 64-bit science app with 32-bit BOINC.

Regards,
Simon.

Suzuki:
May I first point out that my intense stupidity with Linux is probably more frustrating for you, than me.  Reason for that is that there's good people out there who are so willing to help!  Thanks in advance ...

So, for my next stupid question ...

I had my Linux box (Suse 10) running just fine .. and then managed to break BOINC.  I'm sure I had a previous 64-bit SETI app running on standard BOINC.  But having read a few threads, thought I'd try the 64-bit client too. 

Predictably, I broke it again with the SETI servers telling me that x86--- was not recognised etc.  So I went back to the standard client and copied the 2.2B apps into the relevant folder; which now won't run.  I'm still seeing the standard science app running in the Performance Monitor - and the "aux | grep" thing means nothing to me!

What on earth have I buffooned this time?!  Apart from trashing lord knows how many units!

Does the 64-bit client support SETI (or vice versa) and, if so, how to make it run?  And is there more to switching to the optimised app than just copying the files after stopping BOINC? 

I've done this before, and have no idea what I've cocked up!  As in the SETI threads, I've got a book on order to prevent persistent asking of moronic questions!  Please bear with me!!

Thanks in advance ...

Steve.

Metod, S56RKO:

--- Quote from: Suzuki on 21 Apr 2007, 02:24:18 pm ---Does the 64-bit client support SETI (or vice versa) and, if so, how to make it run?  And is there more to switching to the optimised app than just copying the files after stopping BOINC?
--- End quote ---

An user named Augustine is quite active in lobbying support for 64-bit Linux in many of projects. He also posts occasionally list of projects that support 64-bit linux as OS platform. Seti is one of them. However, there are a couple of gotcha's:

* Some projects support platform named x86_64-unknown-linux-gnu (Seti being one of them) and some support x86_64-pc-linux-gnu. The later is official name for platform as set by Berkeley. Some of projects that support platform in question do it via 32-bit applications. If the 64-bit linux platform is not supported at all, you may have luck running it and use anonymous platform mechanism (ie. use app_info.xml). I am successful doing so at Einstein@Home, but not at CPDN.
* If you decide to switch platform (eg. from i686 to x86_64), BOINC client will reset all projects the host is attached to. You can avoid this by hand-editing file client_state.xml.
Now, as to your problem: perhaps you are best off starting a new install and (re)attach your box to all projects you want to. Here's what I usually do:

* Install official Berkeley's BOINC client. Then get a 64-bit one and simply copy the executable over the original one. Actually what I do is to create a sym-link named boinc and pointing to the executable I wish to run.
* Start (64-bit) BOINC and attach to projects you wish to participate in. Don't worry about warnings that some projects don't support your platform.
* Stop BOINC client.
* Install proper project scientific executables and pay attention to install also proper version of app_info.xml.Use 64-bit apps for SETI of course. You can get necessary project executables for 32-bit linux by manually downloading them from projects' servers and then construct appropriate app_info.xml.
* Start BOINC client and keep an eye on it for a couple of days to make sure everything is fine.
I hope you'll get it sorted out.

Suzuki:
That sounds like something I can manage ... I'll give it a whirl and let you know how I get on.

Many thanks for your help.

Steve.

Navigation

[0] Message Index

[#] Next page

[*] Previous page