Sorry, my bad. I was talking about 5.8.15, the current stable release. Since 5.8.17 is running into "GLIBC" problems I don't want to risk playing around with it atm, but of course this explains the somewhat lower benchmarks. Sorry about that.
There's no risk in it ... you just won't see information about CPU on project pages.
This problem affects also the 5.8.15 AFAIK. I've compiled my own 64-bit binary from CVS sources for 5.8.15 under GLIBC 2.3 system (Debian Etch). If I run it on recent Gentoo which has GLIBC 2.4, it also doesn't show any CPU info, only GenuineIntel. Other than this, it runs fine.
BTW, as 5.8.17 mainly fixes benchmark results and I tend to compile my own linux binaries using GCC 4, which have different benchmark results tan official Berkeley anyway, I'll stay at 5.8.15 for a while.
Sorry if this sounds "nooblike" to you but how exactly do you get the new version to run? On my box it just exits with said "GLIBC" error. So I googled that and read from someone who said "messing around with the GLIBC was more risky than a kernel update" and decided to leave it alone. I'm kinda new to using beta clients and stuff and have usually been using BOINC under Windows (sad but true) although I do have some Linux experience so if I got a tip from someone who has done this already I think I could handle it.
Thanks in advance
Annika
Sorry if this sounds "nooblike" to you but how exactly do you get the new version to run? On my box it just exits with said "GLIBC" error.
Well, you don't get it run. Upgrading glibc is really risky as you may break all other applications you have ...
If you want to run the latest and greatest BOINC cc, you might try to compile it yourself. It's not a big thing, basic instructions on how to do it are here. You'll need to install a cvs client and most of development packages. Lately I didn't have to change anything in sources. I had to change config script though. BOINC nowadays requires quite a modern version of CURL libraries while Debian Sarge ships with a slightly older. As I never had problems which were observed by other users and were attributed to older version of CURL I just tend to change the required version of CURL to something lower than I have on Sarge.
On the other hand, you may want to upgrade your Debian to Etch. It won't solve problems regarding GLIBC 2.4 (it's still at 2.3.4). I'm running it on workstations and never had bigger problems. I still run Sarge on my servers though ;)
Additionally you can play with compiler switches to make executable customized for your type of hardware. It'll boost benchmark results, but those are not used by many projects anyway.
Thanks a lot for all that information, sounds like something I might want to try when I have the time for it :-) And you're right, most projects don't rely on benchmarks any more, but sadly PrimeGrid and MalariaControl do and my little Intel box just tends to do quite well in those, so it would be worth the effort. I'll probably be leaving the AMD alone for the time being, though, 'cause that does mostly Einstein and a bit of TMRL DRTG, so it really doesn't matter there.
RE: Sorry, my bad. I was
)
There's no risk in it ... you just won't see information about CPU on project pages.
This problem affects also the 5.8.15 AFAIK. I've compiled my own 64-bit binary from CVS sources for 5.8.15 under GLIBC 2.3 system (Debian Etch). If I run it on recent Gentoo which has GLIBC 2.4, it also doesn't show any CPU info, only GenuineIntel. Other than this, it runs fine.
BTW, as 5.8.17 mainly fixes benchmark results and I tend to compile my own linux binaries using GCC 4, which have different benchmark results tan official Berkeley anyway, I'll stay at 5.8.15 for a while.
[edit] Spilling mistkaes
Metod ...
Sorry if this sounds
)
Sorry if this sounds "nooblike" to you but how exactly do you get the new version to run? On my box it just exits with said "GLIBC" error. So I googled that and read from someone who said "messing around with the GLIBC was more risky than a kernel update" and decided to leave it alone. I'm kinda new to using beta clients and stuff and have usually been using BOINC under Windows (sad but true) although I do have some Linux experience so if I got a tip from someone who has done this already I think I could handle it.
Thanks in advance
Annika
RE: Sorry if this sounds
)
Well, you don't get it run. Upgrading glibc is really risky as you may break all other applications you have ...
If you want to run the latest and greatest BOINC cc, you might try to compile it yourself. It's not a big thing, basic instructions on how to do it are here. You'll need to install a cvs client and most of development packages. Lately I didn't have to change anything in sources. I had to change config script though. BOINC nowadays requires quite a modern version of CURL libraries while Debian Sarge ships with a slightly older. As I never had problems which were observed by other users and were attributed to older version of CURL I just tend to change the required version of CURL to something lower than I have on Sarge.
On the other hand, you may want to upgrade your Debian to Etch. It won't solve problems regarding GLIBC 2.4 (it's still at 2.3.4). I'm running it on workstations and never had bigger problems. I still run Sarge on my servers though ;)
Additionally you can play with compiler switches to make executable customized for your type of hardware. It'll boost benchmark results, but those are not used by many projects anyway.
Metod ...
Thanks a lot for all that
)
Thanks a lot for all that information, sounds like something I might want to try when I have the time for it :-) And you're right, most projects don't rely on benchmarks any more, but sadly PrimeGrid and MalariaControl do and my little Intel box just tends to do quite well in those, so it would be worth the effort. I'll probably be leaving the AMD alone for the time being, though, 'cause that does mostly Einstein and a bit of TMRL DRTG, so it really doesn't matter there.