I missed RCN recent developments (HT to Skip).

Native 64-bit Application Sent to AMD64 Clients:

* SIMAP (Linux)
* Chess960 (Linux)
* ABC & ABC ß
* Predictor (Linux)
* RieselSieve (Linux: Sieve)
* Leiden (Linux)
* APS
* Cosmology (Linux)
* Tanpaku (Linux)
* Malaria (Linux)
* SHA-1 (Linux)
* Yoyo (Linux)
* PrimeGrid (Windows: Sieve)
* Sudoku (Linux)
* TSP
* RCN (Linux: TCAPE)

32-bit Application Sent to AMD64 Clients:

* SETI & SETI ß (Linux)
* HashClash
* Docking
* RieselSieve (Linux: LLR, Windows: Sieve)
* WCG (Linux)
* Pirates (Linux)
* WEP-M+2 (Linux)
* NanoHive (Windows)
* Rosetta & RALPH
* Superlink (Linux)
* Gridfinity
* RND
* Hydrogen (Linux)
* NNSIMU (Linux)
* LHC
* CPDN (HadSM3)
* RCN (CAPE & RCross)

32-bit Application Sent Only to AMD64 Clients 5.10.x or Newer:

* DepSpid
* Lattice
* SciLINC
* QMC
* SZTAKI
* Gerasim
* Enigma
* Einstein
* Eternity2
* Sudoku
* Milkyway
* PrimeGrid (Linux: Sieve, Linux & Windows: LLR)
* N-Queens
* POEM
* Spinhenge (Linux: ß)

32-bit Application Sent Only to AMD64 Windows Clients 5.10.x or Newer:

* RieselSieve (Windows: LLR)
* WCG (Windows)
* Pirates (Windows)
* Malaria (Windows)
* SETI & SETI ß (Windows)
* SIMAP (Windows)
* Superlink (Windows)
* µFluids (Windows)
* Predictor (Windows)
* Leiden (Windows)
* Tanpaku (Windows)
* Hydrogen (Windows)
* SHA-1 (Windows)
* Yoyo (Windows)
* Spinhenge (Windows)

Pirates@Home has 64bit-apps for both win and linux now.

Nope, they're still 32-bit applications.

Thanks.

On the Pirates site it shows 64bit apps:

http://pirates.spy-hill.net/apps.php

You're misreading it. It says that 64-bit platforms are supported. But when one downloads the applications, one will notice that they are supported through 32-bit applications.

HTH

I sure hope ya'll might be able to help me. I just converted a machine from winXP to Ubuntu v7.10 64bit and am getting the following errors:



Now an interesting note here is that the WCG error only occurs on one of the two different apps I've rx'd from them but not on the other. This is with the 64bit version of boinc client v5.10.8 (newest one out there in a package).

you didnt keep the same directory, did you? I doubt installing the linux BOINC ontop the windows BOINC will work correctly.

Did you install the ia32 libs?

Hello,

Actually, that version is a bit old. The latest official x64 Linux version is 5.10.21. I run a 32-bit Ubuntu, and I found this version was a bit better behaved than the Ubuntu-packaged version. There is also a "beta" version that fixes some issues that first appeared in Ubuntu, version 5.10.28. This is the version I use on my x64 Fedora box. Again, it's just better behaved. (The manager window defaults to the simple view, which I don't like, but it otherwise works.)

There are installation instructions if you're new to Linux, or someone here (or myself) could give you a hand.

http://boinc.berkeley.edu/download_all.php

As for WCG, issues with that can be "fun" to track down because they run several projects, and some run different rendering software. (I have no idea what the Africa Climate project runs, as I've never seen a work unit, or heard from anyone who has.) The HPF project generally uses Rosetta exclusively. DDDT usually uses the ZINC engine, but I've seen stray work units that have a different nomenclature. FA@H is a bit more diverse. For a while they were using primarily ZINC like DDDT. Now they seem to use mostly JEDI, though I've seen a few more ZINC driven units recently. If I remember correctly, I've also seen a few Rosetta and AMBER driven units with them in the past. So, for WCG issues, you have to get the work unit name (which you've done, thank you), to narrow down the specific project and rendering engine. That's why it would fail on you apparently randomly.

No, not even. I formatted the drive and installed Xubuntu from scratch. Boinc from package.

I had installed the stdc++ v5 libs prior to installing BOINC as I'd had that error (think it was -127) on a 32bit Xubuntu install but had missed the IA32 shared libs.

That was it! Don't know why I didn't find this link in various searches I did. But anyway. I'm now crunching a E@H and a QMC WU (they'd fail at start before) and will have to wait another 4 hours before I can get another CPDN WU to make sure it fixed that also.

Thanx SO much.

PS: For my Gutsy 64bit Xubuntu

Proven to work now:
ABC
QMC
SETI
Rsieve
WCG
E@H
Malaria Control
SIMAP
Leiden
Rosetta
RCN
LHC

Assume to be working, need new WU to test:
CPDN
Pirates
Predictor
APS
ORBIT

Not expected to work (either only Windows or Linux in beta testing):
uFluids
Spinhenge
NanoHive
SZTAKI (32bit only, will retest)


PS: Somehow I ended up with libglut.so.3.8.0 in /usr/lib32 but it was there with Gutsy scratch install, installed with IA32 or installed with stdc++ v5. I'll be repeating this install process on another machine tonight so I'll try to remember to check before / after each.

Yes, I'm a Linux noob. If you could give me step by steps to install 5.10.28 I'd really appreciate it.

I had downloaded boinc_ubuntu_5.10.28_x86_64-pc-linux-gnu. Put it in /home/skip. Then I used Thunar to mark it as executable. Next I did


This gives me a directory /home/skip/BOINC that contains (all owned by skip):

file:///home/skip/BOINC/locale
file:///home/skip/BOINC/run_manager
file:///home/skip/BOINC/run_client
file:///home/skip/BOINC/ca-bundle.crt
file:///home/skip/BOINC/boincmgr.48x48.png
file:///home/skip/BOINC/boincmgr.32x32.png
file:///home/skip/BOINC/boincmgr.16x16.png
file:///home/skip/BOINC/boincmgr
file:///home/skip/BOINC/boinc_cmd
file:///home/skip/BOINC/boinc
file:///home/skip/BOINC/binstall.sh

Since my current v5.10.8 package install (running as daemon) has in /usr/bin/ (all owned by root):

file:///usr/bin/boincmgr
file:///usr/bin/boinc_cmd
file:///usr/bin/boinc_client
file:///usr/bin/boinc (a link to boinc_client)

Can I just

*stop the boinc_client daemon
*rename /home/skip/BOINC/boinc to boinc_client
*copy from /home/skip/BOINC/ to /usr/bin/ the following:

*boincmgr
*boinc_cmd
*boinc_client

Would my command to copy the files be as follows?:

sudo cp -t=/usr/bin/ boincmgr boinc_cmd boinc_client

Assuming this would work isn't there a command I need to do to "rebuild" the link "boinc"?
Or is there some other "registration" process I need to go thru?

Thanx much, Skip

You should uninstall the Ubuntu boinc package to avoid any conflict.

Although not a point answer to your questions, this README that accompanied the AMD64 client I've provided for a while should give you some tips.

HTH

Where is this README located? It wasn't with the file I downloaded from Berkeley.
These names seem wrong for updating the results of the apt-get install that I did... but what it is telling me is that "yes" I can just rename and copy the executable files I have from my /home/skip/BOINC/ to my /usr/bin/ as I described.

Great! This leaves only the details on the cp command I'd looked up with man cp (I can play with that) and the rebuilding of the link file... I don't know how to tell if the link file "boinc" that points to "boinc-client" is a hard or symbolic link and maybe I don't even need to worry about it... anyway... you've given me enough to believe I can rename/copy/move these executable files and then play with chmod or chown to get them back to owner=root. I'll read up more on the "ln" command.

Thanx

PS: I don't have ca-bundle.crt in /usr/bin/ where my executables are and WCG is downloading WUs.

PPS: Any idea why the v5.10.28 files are SO much larger?
old vs new: boinc .5MB vs 1.8MB, boincmgr 3.3MB vs 6.4MB. I'm wondering if we've got some debug stuff linked into this version still.

Will this remove or leave these?:

/etc/default/boinc-client - (modified to run as daemon)
# This file is /etc/default/boinc-client, it is a configuration file for the
# /etc/init.d/boinc-client init script.

/etc/init.d/boinc-client
# init script

/var/lib/boinc-client/
# projects & slots directories (would be D:/BOINC in my Win installs)
# xml and log files
# oh, and found ca-bundle.crt here

I believe it will remove them. I've never installed from a package manager though.

The instructions for installing as a daemon I used are here. If I can do it, anyone should be able to do it. Just go step by step and ask if you have any questions. I know for sure it works on Fedora 7 (x86). As soon as my new computer comes in (argh, 48 hours is so long to wait) I'll try it on the x64 version of Fedora 7.

Note, the latest version of BOINC (5.10.28) from Berkeley doesn't work on Fedora 8. It was built to definitely work on Ubuntu Gutsy. I believe it's still listed as alpha (you'll have to grab it from the all versions page) but it's been rock solid for me.

I'm not exactly a wizard myself. I do not run BOINC as a daemon. If you do, it would be best to uninstall that through the package manager first. Otherwise you could have two BOINC sessions running. Also, mixing versions of the client and manager is not pretty.

I usually have a terminal window devoted to BOINC, or no my new Linux box, one tab for BOINC and the other for Folding. If you manually run it, all the messages are directed to the terminal. Some find this messy. I glance through these to look for errors without running the console, and don't use that shell for anything else.

To start things like this, go to the BOINC directory.

To start the client, type: ./run_client &

(The "&" runs the program in background mode, and lets you get your prompt back.)

To start the manager window: ./run_manager &

The manager will appear. Note that in the messages in the shell, you may see a widget error. I cannot remember it, but I've seen the same one on several versions of BOINC, on Fedora core 4, 5, 6, 8 x64, and Kubuntu 7.10.

When you're done with the manager, close it. Hit the enter key in the terminal, and the close window message will appear and your prompt will return.



Umm... Pardon?

I wasn't able to get 5.10.2 to run on FC8 x86 at all. I have been running 5.10.28 on FC8 x64 since Thursday evening (Monday morning now). The projects I've checked show the WU's have been OK. When I get home from work I'll re-check all my projects. The only two issues I've had are trivial.

1- The manager always starts in simplified mode. I don't like that. When I switch to advanced mode, the sorting by project name I always set it lost.

2- This one is my fault. I installed BOINC and connected to two projects before renaming my PC. Now some projects show the PC connected as the default "localhost.localdomain" rather than "trismegistus". That may be buried in the xml files somewhere.

As I said, I added this README to the AMD64 Linux client that I used to provide before Berkeley would do so. You can find the latest one here.

HTH

Thanks. I had only seen reports that it didn't work. I'm not tempting the fates. My new computer will get Fedora 7 as well.

That link gives me a 404.

The files I quoted are the locations the package install puts stuff. I only had to modify the boinc-client (conf file for the startup script) to tell it to run as a daemon but that's also where I turned on allow_remote_gui as my crunchers are off in another room and don't have crts, keyboards or mice hooked to them. I am starting to see the sense of where the package installs things now. I think I'm going to just try the rename/copy/move of the two executables I need and see what happens. I'll get the latest BOINC version for 32bit and try it on that machine first since it's gonna get wiped and 64bit Gutsy installed on it very soon. That way if I really screw it up I can just format the drive and start with what I was gonna do to it anyway.... if it does work then I'll have a simple process to upgrade boinc if I feel the urge. However with the IA32 and stdc++ v5 libs on the 64bit machine v5.10.8 seems to be running fine.

This way when the neighbor finds my extension cord running into his garage to power my crunchers and yanks it, I can just run a new one to the other neighbor's garage and the machines will all start back up running BOINC.

crap I had entered all the steps in great detail... took to long and got logged off and lost it all...

Well the moving of the v5.10.28 executables over the v5.10.8 versions worked fine. I'll go create a .doc or .txt file now while I can still remember it in case any noobs like me want the full detail of the steps to updgrade to current version after doing the install with sudo apt-get install boinc-client boinc-manager

Skip

If anyone is interested in my v5.10.8 to v5.10.28 upgrade over top of the install done by get-apt install boinc-client boinc-manager you can grab THIS .doc file.

If you find any errors let me know and I'll update it.

Sorry for the 404. Bad copy/paste. I ended up with an extra / somehow.

http://www.spy-hill.net/~myers/help/boinc/unix.html

Hi,

Well, for reasons not understood by me, since getting the latest kernel version (and many other updates) for Fedora Core 8 x64, suddenly this behavior stopped. The BOINC manager now always starts in advanced mode, and the sorting on all tabs is preserved.