Message boards :
Number crunching :
BOINC 4.16
Message board moderation
Author | Message |
---|---|
littleBouncer Send message Joined: 28 May 99 Posts: 151 Credit: 666,283 RAC: 0 |
when I upgraded BOINC 4.13 to 4.16 the CPU-Type changed ! o) Why that??? I saw this before when I upgrated a other machine from 4.13 to 4.57 (after Xmas), but I wasn't sure , so I didn't post. But now I saw it at new (see the copy/paste of this computer from the PAH-UsersComputerSite after changing from 4.13 to 4.16): 41485 XXXXX 6.80 253.04 Intel(R) Pentium(R) M processor 1.50GHz Pentium Microsoft Windows XP Home Edition, Service Pack 2, (05.01.2600.00) 44803 XXXXX 0.00 0.00 GenuineIntel Intel(R) Pentium(R) M processor 1.50GHz Microsoft Windows XP Home Edition, Service Pack 2, (05.01.2600.00) First line 4.13, second line 4.16 |
Jord Send message Joined: 9 Jun 99 Posts: 15184 Credit: 4,362,181 RAC: 3 |
It's known. See the developers mailing list. If not already implemented, the merge option will change. |
Pete49 Send message Joined: 28 Jul 04 Posts: 64 Credit: 250,376 RAC: 0 |
> when I upgraded BOINC 4.13 to 4.16 the CPU-Type changed ! o) > Why that??? Predictor@home has been trying to send work only to the same types of computers. This was susposed to be a feature of BOINC but it was not correctly implemented. 4.15 and higher correct the error. Anyone who upgrades to 4.15 or higher will experience the same thing. <img src="http://www.boincstats.com/stats/teambanner.php?teamname=GasBuddy"> <img src="http://www.boincstats.com/stats/banner.php?cpid=84c0cf7846cbf28338406e54b3eb8a83"> |
littleBouncer Send message Joined: 28 May 99 Posts: 151 Credit: 666,283 RAC: 0 |
@pete49: the logic of your statement is that: in the older version (4.13 = official public version)the CC (CoreClient) use a "wrong" CPU-Type all the time, and it is only correct after installing 4.15 or higher. or have I understood it wrong?? @ageless I see by your link only, that others noticed the same, but no solution. Thanks for your replies! |
Professor Desty Nova Send message Joined: 17 May 99 Posts: 59 Credit: 579,918 RAC: 0 |
Yes, the upcoming BOINC 4.16 CC have a corrected CPU identification code. In the still "official" 4.13, AMD computers appear as AMD xxxxxx Pentium. And in some cases CPU appear as Unknown Pentium. In PredictorAtHome, these unknown CPU would get less or no work, so it was corrected. PS: I updated to BOINC CC 4.16 a few hours ago, and everything is OK until now. I didn't get new host IDs. In all projects the CPU ID were just updated. SETI@home classic workunits: 1,985 CPU time: 24,567 hours Professor Desty Nova Researching Karma the Hard Way |
Jord Send message Joined: 9 Jun 99 Posts: 15184 Credit: 4,362,181 RAC: 3 |
> @ageless > I see by your link only, that others noticed the same, but no solution. > > Thanks for your replies! It's possible you have to subscribe to it. Here if you want to. But if you want, I can copy&paste those posts here (later). :) |
Benher Send message Joined: 25 Jul 99 Posts: 517 Credit: 465,152 RAC: 0 |
"Pentium" in the case of AMD computers was a designation applied by checking a flag in windows. What it really meant was it has the features of a Pentium class machine (IE greater than a 80486). Windows returns a variable stating which generation a CPU belongs to. case PROCESSOR_INTEL_386: strcpy( p_model, "80386" ); break; case PROCESSOR_INTEL_486: strcpy( p_model, "80486" ); break; case PROCESSOR_INTEL_PENTIUM: strcpy( p_model, "Pentium" ); break; Thats why the word pentium was getting added to AMD cpus. The server code that checked for "homogeneous redundancy", ie system matching code, is below. This server code has not changed recently, unlike the BOINC client. What it really checks for is the presence of the words anywhere in the CPU string "AMD" or "Intel", or "Macintosh". If some science application came out in the future that needed finer distinctions it could look for "Athlon" or "Pentium(R) 4", etc. ================ // Check that the two platform has the same architecture and operating system // Architectures: AMD, Intel, Macintosh // OS: Linux, Windows, Darwin, SunOS const int unspec = 0; const int nocpu = 1; const int Intel = 2; const int AMD = 3; const int Macintosh = 4; const int noos = 128; const int Linux = 256; const int Windows = 384; const int Darwin = 512; const int SunOS = 640; inline int OS(SCHEDULER_REQUEST& sreq){ if ( strstr(sreq.host.os_name, "Linux") != NULL ) return Linux; else if( strstr(sreq.host.os_name, "Windows") != NULL ) return Windows; else if( strstr(sreq.host.os_name, "Darwin") != NULL ) return Darwin; else if( strstr(sreq.host.os_name, "SunOS") != NULL ) return SunOS; else return noos; }; inline int CPU(SCHEDULER_REQUEST& sreq){ if ( strstr(sreq.host.p_vendor, "Intel") != NULL ) return Intel; else if( strstr(sreq.host.p_vendor, "AMD") != NULL ) return AMD; else if( strstr(sreq.host.p_vendor, "Macintosh") != NULL ) return Macintosh; else return nocpu; }; |
7822531 Send message Joined: 3 Apr 99 Posts: 820 Credit: 692 RAC: 0 |
In that case, I'd expect to see something like this (in pseudo-code): case PROCESSOR_PPC_6XX: strcpy( p_model, "PowerPC 600 Series" ); break; case PROCESSOR_PPC_750: strcpy( p_model, "PowerPC G3" ); break; case PROCESSOR_PPC_75XX: strcpy( p_model, "PowerPC G4 Series" ); break; case PROCESSOR_PPC_97X: strcpy( p_model, "PowerPC G5 Series" ); break; const int unspec = 0;<BR>const int nocpu = 1;<BR>const int Intel = 2;<BR>const int AMD = 3;<BR>//[i]const int Macintosh = 4; is a misnomer - correction follows[/i]<BR>[b]const int Motorola = 4; // (68k, 603, 604(?), G4)<BR>const int IBM = 5 ; // (601, G3, G5)</B> const int noos = 128; const int Linux = 256; const int Windows = 384; //[i]const int Darwin = 512; isn't clear - Pure Darwin or Mac OS X?[/i] const int SunOS = 640; const int BSD = [b]512[/b]; //[i]Includes pure Darwin ppc/x86[/i] const int MacOS = [b]1984[/b]; //[i]OS X only[/i]2¢, but it would help to have accurate information about a CPU. I don't run Darwin 7.7; It's X.3.7. It's not a Macintosh processor; It's a Motorola PowerPC 7450. |
Merlin.huff Send message Joined: 5 May 02 Posts: 16 Credit: 337,728 RAC: 0 |
I have updated to 4.15 and the cpu type changed but, it has also given me new host id's and I cannot merge these even though its the same computer <img src="http://www.boincstats.com/stats/banner.php?cpid=eb8a66ae028924190ff09df10e79003e" /> |
littleBouncer Send message Joined: 28 May 99 Posts: 151 Credit: 666,283 RAC: 0 |
Thanks alot to all replies!!! It helped me to clear some probs. specielly Mr. Benher's CVS shows how CPU are "defined" by the CC. still not sure if those "famous"message from PAH :"there was work, but was commited to other platform..." has to do with the "wrong" CPU-Identification by the CC 4.13. |
Pete49 Send message Joined: 28 Jul 04 Posts: 64 Credit: 250,376 RAC: 0 |
> @pete49: > the logic of your statement is that: in the older version (4.13 = official > public version)the CC (CoreClient) use a "wrong" CPU-Type all the time, and it > is only correct after installing 4.15 or higher. > or have I understood it wrong?? > Correct. This was discovered by the folks at P@H. see: http://www.ssl.berkeley.edu/pipermail/boinc_dev/2005-January/001312.html <img src="http://www.boincstats.com/stats/teambanner.php?teamname=GasBuddy"> <img src="http://www.boincstats.com/stats/banner.php?cpid=84c0cf7846cbf28338406e54b3eb8a83"> |
Heffed Send message Joined: 19 Mar 02 Posts: 1856 Credit: 40,736 RAC: 0 |
> I have updated to 4.15 and the cpu type changed but, it has also given me new > host id's and I cannot merge these even though its the same computer Word on the street is that they are working on a method to merged these. |
littleBouncer Send message Joined: 28 May 99 Posts: 151 Credit: 666,283 RAC: 0 |
Thanks to all ! specially: to pete49, benher, NA and ageless. To be sure; to be "on the right spot" on PAH, I will change CC 4.56 (same Identification - "error" as 4.13) to 4.16. procedure: backup the Client in suspend/exit-state, deinstall CC4.56,controlling that no BOINC-processes are active (taskmanager), restart winXP, install 4.16. |
Mike Send message Joined: 17 Feb 01 Posts: 34258 Credit: 79,922,639 RAC: 80 |
Hi Normally there is no need to reboot WinXP. I´ve just installed 4.60 without any problems. greetz from Germany Mike With each crime and every kindness we birth our future. |
littleBouncer Send message Joined: 28 May 99 Posts: 151 Credit: 666,283 RAC: 0 |
Hi Mike Thanks for advise, maybe I risque to change direkt to 4.60. I wouldn't "over-post" you, but correction in the text is set to 60 minutes, so I couldn't EDIT bellow. greetz from Switzerland |
Aurora Borealis Send message Joined: 14 Jan 01 Posts: 3075 Credit: 5,631,463 RAC: 0 |
Please advise were this cc v.4.16 can be d/l from. I don't see it on the boinc_alpha/download/ page. Also, are there any remaining issues with using it on win98se? Thank you. |
Mike Send message Joined: 17 Feb 01 Posts: 34258 Credit: 79,922,639 RAC: 80 |
Hi Look at Einstein@home Page http://einstein.phys.uwm.edu/download.html greetz Mike With each crime and every kindness we birth our future. |
Astro Send message Joined: 16 Apr 02 Posts: 8026 Credit: 600,015 RAC: 0 |
> Please advise were this cc v.4.16 can be d/l from. I don't see it on the > boinc_alpha/download/ page. > > Also, are there any remaining issues with using it on win98se? > > Thank you. > I'm using win98 and can say 4.16 works just like 4.13, 4.15, and earlier versions when it comes to Seti, PPAH, and Einstein. As a matter of fact, I can find no reason to "upgrade" as it were. Nor, do I see any reason not to Upgrade. It seems 4.15 and 4.16 changes are addressed to those using CPDN (which I am not). tony |
Aurora Borealis Send message Joined: 14 Jan 01 Posts: 3075 Credit: 5,631,463 RAC: 0 |
Thank you for the replies. I've opted to test out cc v.4.56 instead. I like to live dangerously and the bloated (10M) software has me intrigued. Currently running Seti, Predictor, and CPDN. Waiting for reactivation of LHC. Hoping to be accepted at Einstein. |
Divide Overflow Send message Joined: 3 Apr 99 Posts: 365 Credit: 131,684 RAC: 0 |
|
©2024 University of California
SETI@home and Astropulse are funded by grants from the National Science Foundation, NASA, and donations from SETI@home volunteers. AstroPulse is funded in part by the NSF through grant AST-0307956.