32-bit

I have 4 FC6 computers with different processors.
this error on all of them.

---

I have the same segmentation faults on my 32 bit P4 3.06 GHz..

Johan

---

Hi,

the segfault is caused by static linking, most probaly libpthread.

I've got some apps mirrored those are not fully static and should work.
You can use them until simon fixes the download on lunatics.at and adds both static and shared binaries.

Those should be used only on newer distributions that include at least a GLIBC 2.3.4

remember to check for missing dependencies fist.

Run a "ldd setiathome-5.15.i686-pc-linux-gnu" AND rename the binaries matching to the name in the app_info.xml !


MMX
SSE
SSE2
SSE3

---

Join BOINC United now!

SSE2

this version in running ok.
thks.

This SSE2 is also running fine on my P4 3.06 GHz.

Thanks, Johan

---

I sort priority thing out by installing boinc-client from backports using aptitude. To retain previous tasks just copy project catalog and .xml files.

Do you mean that if I (re)install boinc from a repository it will work at the right priority again? The boinc client I have been using for quite a while on my linux server is 5.2.14, the one in the Ubuntu repository is 5.2.13.... not sure how a downgrade would solve anything in my case.

Greetings,
Sander

---

Howdy,
Thanks Crunch3r the SSE3 works great on two 2.6.9 kernel RHEL4 systems, The app at the download site was crashing with reference to a "Signal 11".
Unfortunately, on two 2.4.21 kernel RHEL3 systems the SSE2 app won't work. It turns out your SSE2 app actually needs GLIBC 2.3.4 (instead of 2.3.2) according to the ldd test of the app.

N.B. the url of the SSE3 app is "...sse3.tar.bz22" instead of "...sse3.tar.bz2"

Thanks again, I was beginning to think my systems were the only ones with problems.

Happy Distributed Computing to all, and to all a good night. Chris

Hi,

the segfault is caused by static linking, most probaly libpthread.

I've got some apps mirrored those are not fully static and should work.
You can use them until simon fixes the download on lunatics.at and adds both static and shared binaries.

Those should be used only on newer distributions that include at least a GLIBC 2.3.2.

remember to check for missing dependencies fist.

Run a "ldd setiathome-5.15.i686-pc-linux-gnu" AND rename the binaries matching to the name in the app_info.xml !


MMX
SSE
SSE2
SSE3

Run a "ldd setiathome-5.15.i686-pc-linux-gnu" AND rename the binaries matching to the name in the app_info.xml !

Have a problem. The machine has GLIBC_2.3.2 installed, but here is what ldd returns:

$ ldd setiathome-5.15-kwsn-2.2-sse
./setiathome-5.15-kwsn-2.2-sse: /lib/tls/libc.so.6: version `GLIBC_2.3.4' not found (required by ./setiathome-5.15-kwsn-2.2-sse)
libdl.so.2 => /lib/libdl.so.2 (0x00b45000)
libm.so.6 => /lib/tls/libm.so.6 (0x00f1e000)
libpthread.so.0 => /lib/tls/libpthread.so.0 (0x00aec000)
libc.so.6 => /lib/tls/libc.so.6 (0x0032d000)
/lib/ld-linux.so.2 => /lib/ld-linux.so.2 (0x00eec000)

$ ls -l /lib/tls
total 1936
-rwxr-xr-x 1 root root 1568924 Aug 30 2004 libc-2.3.2.so
lrwxr-xr-x 1 root root 13 Apr 1 2005 libc.so.6 -> libc-2.3.2.so

Do you mean that if I (re)install boinc from a repository it will work at the right priority again?

It works for me (sarge, repository from www.backports.org).

The boinc client I have been using for quite a while on my linux server is 5.2.14, the one in the Ubuntu repository is 5.2.13.... not sure how a downgrade would solve anything in my case.

I doubt client is an issue (if U want just after reinstalling replace client - ive replaced it from 5.4.9 to 5.5.0 and priority has remained the same). In my case client was in /usr/bin directory.

---

Hi,

@all who downloaded the linux sse3 app. from http://calbe.dw70.de

please download it again. It contains now a bug fix regarding invalid results.

Url for download is the same.

SSE3

---

Join BOINC United now!

Hi,

@all who downloaded the linux sse3 app. from http://calbe.dw70.de

please download it again. It contains now a bug fix regarding invalid results.

Url for download is the same.

SSE3

Awesome, thank you. Just got it running.

For everyone else, I'll share the secret why Crunch3r is so good. I downloaded his binaries, and they are dated April 7th 2007. He just lives in the future ;)

Mikey

---

Hi Crunch3r, and all the fantastic optimizers involved in this project.
I just wonder why there is no application compiled for AMD64 : SSE2 or 3 ones are 32 bits, and Crunch3r has proven that 64 bits apps can be #15% faster (read on another thread of this forum). I would compile myself... if I could ! I still use last year 5.12 64 bits app, I don't know if the new 2.2b 32 bits is faster. Can someone help, please ? Unless it's proven to be unnecessary with 2.2b apps ?
Thanks.

---

Hi Crunch3r, and all the fantastic optimizers involved in this project.
I just wonder why there is no application compiled for AMD64 : SSE2 or 3 ones are 32 bits, and Crunch3r has proven that 64 bits apps can be #15% faster (read on another thread of this forum). I would compile myself... if I could ! I still use last year 5.12 64 bits app, I don't know if the new 2.2b 32 bits is faster. Can someone help, please ? Unless it's proven to be unnecessary with 2.2b apps ?
Thanks.

Hi,

Since i'm Crunch3r and i did the post you quoted that 64 bit apps can/are faster on AMD64, i think i'm the most qualified one to answer :-)

So here we go ...

there's allready a 64 bit app. BUT it's giving me some trouble atm.
I'm working atm on the linux 32 bit version. Today i fixed a bug in the sse3 app AND did some changes to get the code working on linux machines runing 2.4 kernels. (we're testing atm).

So if that all works i'm focusing on the 64 apps both windows and linux. But atm we'll have to get the things working for the "masses".

Unfortunately building the apps form the ported source is quite complicated atm. and the code is changed on a dayly basis... (there's no configure script involed in building the apps... it's a bunch of hand coded scripts that do the build and is kinda complicated atm).

As soon we're getting ALL things working(all scripts involved in the build process) there'll be the source available at lunatics.at and you can try for yourself.

HTH

---

Join BOINC United now!

You guys rock!

...So if that all works i'm focusing on the 64 apps both windows and linux. But atm we'll have to get the things working for the "masses".

Good move even if I'm not amongst "The Masses". The 32-bits stuff is in EDF... The 64-bits stuff is ready and waiting for chomping.

Unfortunately building the apps form the ported source is quite complicated atm. and the code is changed on a dayly basis... (there's no configure script involed in building the apps... it's a bunch of hand coded scripts that do the build and is kinda complicated atm)...

OK, a naive question:

Why no Makefile...?


Good luck with all the hackings!

Regards,
Martin

---

See new freedom: Mageia Linux
Take a look for yourself: Linux Format
The Future is what We all make IT (GPLv3)

Why no Makefile...?

We're doing the optimizer_lib on the fly, compiling and linking static.

ATM there are 10+ build scripts matching cpu instruction sets and kernel versions and same amount as makefiles for the client.


HTH

---

Join BOINC United now!

Why no Makefile...?

We're doing the optimizer_lib on the fly, compiling and linking static.

ATM there are 10+ build scripts matching cpu instruction sets and kernel versions and same amount as makefiles for the client.

Now that sounds like some fancy bit of scripting a versions matrix!

I'll let you carry on hacking rather than waste compile time explaining that lot!!

Good luck,

and

Happy hackings,
Martin

---

See new freedom: Mageia Linux
Take a look for yourself: Linux Format
The Future is what We all make IT (GPLv3)

It'll be fun updating the How-To, that's for sure...

I'll try and get new versions that should fix issues and work for 2.4 + 2.6 kernels uploaded tonight or tomorrow morning.

Regards,
Simon.

---

Donate to SETI@Home via PayPal!

Optimized SETI@Home apps + Information

It'll be fun updating the How-To, that's for sure...

I'll try and get new versions that should fix issues and work for 2.4 + 2.6 kernels uploaded tonight or tomorrow morning.

Regards,
Simon.

Simon, from what I've seen so far, the 2.4 apps are slightly less efficient than 2.6 apps. So, I'd keep the 2.6 apps as is (except sse3 which had a bug), and add 2.4 apps. We are after efficiency here, aren't we :)

---

It'll be fun updating the How-To, that's for sure...

I can't wait to see the new How To.

---

Join BOINC United now!