Hello,

After running BOINC with QCN and Radioactive@home projects on a Raspberry Pi, I see the ARM application for WUprop, but after the attach got this error:

	Host	Project	Date	Message
	raspberrypi	http://wuprop.boinc-af.org/	03/01/2013 1.19.57	Master file download succeeded
	raspberrypi	http://wuprop.boinc-af.org/	03/01/2013 1.20.02	Sending scheduler request: Project initialization.
	raspberrypi	http://wuprop.boinc-af.org/	03/01/2013 1.20.02	Requesting new tasks for CPU
	raspberrypi	WUProp@Home	03/01/2013 1.20.15	Scheduler request completed: got 0 new tasks
	raspberrypi	WUProp@Home	03/01/2013 1.20.15	Message from server: This project doesn't support computers of type armv6l-unknown-linux-gnueabihf

I'm run a custom QCN version of BOINC (7.1.0)
If the admins needs, I can test a WUprop raspbian application.

I've actually compiled a version of data_collect and tried attaching using anonymous platform, however, it doesn't seem to be pushing data into WU out file. I have it running alongside a POGS attached project. I've sent the admin a private message. Hope to get a response soon...

WUProp would be great for Raspberry Pis with other tasks.

I think I've figured this out. It looks like it relies on p_model in client_state.xml to be populated. When I forced p_model to armv61 it started working...

I can see what NativeBOINC has done to resolve this. They wrote a seperate function that reads model data out of /system.

I'll put something together and post back here. Hopefully the admin has a read and provides some feedback.

OK, I've patched using this code:

-----------------------------------------------------------------------------------------

--- data_collect.cpp	2013-01-20 19:25:34.495467156 +1100
+++ data_collect.cpp.arm	2013-01-20 19:24:27.936472976 +1100
@@ -7,6 +7,7 @@
 #include <sys/types.h>
 #include <sys/time.h>
 #include <sys/socket.h>
+#include <sys/utsname.h>
 #include <netinet/in.h>
 #include <netdb.h>
 #include <stdio.h>
@@ -1106,6 +1107,14 @@
 					recherche_hostid(&hostid);
 					p_model=aid.host_info.p_model;
 					p_ncpus=aid.host_info.p_ncpus;
+					// Try last resort method for geting a model
+					if (p_model == "")
+					{
+						struct utsname uname_d;
+						if(uname(&uname_d) >= 0){
+							p_model = uname_d.machine;
+						}
+					}
 				}
 				else
 				{

-----------------------------------------------------------------------------------------

I know the "uname -m" (which is essentially what this is) doesn't give as detailed info, but it's going to be there. Using assembly to get CPU info is ridiculously complex and different across architecture versions. /proc/cpuinfo is also different on Raspbian kernel build but you can get CPU speed equivalent (BogoMIPS) from it. E.g:

$ cat /proc/cpuinfo 
Processor	: ARMv6-compatible processor rev 7 (v6l)
BogoMIPS	: 944.53
Features	: swp half thumb fastmult vfp edsp java tls 
CPU implementer	: 0x41
CPU architecture: 7
CPU variant	: 0x0
CPU part	: 0xb76
CPU revision	: 7

Hardware	: BCM2708
Revision	: 100000f
Serial		: 0000000064a6f4d2

I'd really like to get some feedback from a project admin regarding this.

Just waiting for a task to finish so I can see if it validates.

ADDITIONAL NOTE:

The way that NativeBOINC read_build_prop() function gets model will not work for ARM on Linux as /system/build.prop does not exist.

OK, confirming the job ran successfully:

http://wuprop.boinc-af.org/result.php?resultid=22948654

So now just waiting for some feedback...

The results returned by your application are valid.
Could you send me the app?
sebastien [at] statseb [dot] fr

---

Hello

I've sent you an email with links. In case you didn't receive:

Source: https://github.com/dcarrion87/boinc-rpi/tree/master/src/project_wuprop

Binaries: https://github.com/dcarrion87/boinc-rpi/raw/master/bin/wuprop-armv6l.tar.gz

Cheers

Daniel

Sorry for late .... reading all post seems that is going out an official client for Raspbian ?
My Raspberry is already attached so I think that when it will become available i'll see a fourth WU running together the QCN + Radioactive + Asteroids ones ?

Binaries: https://github.com/dcarrion87/boinc-rpi/raw/master/bin/wuprop-armv6l.tar.gz

I've uncompress this file in the correct path, but updating the project continue to see this message:

	Host	Project	Date	Message
	raspberrypi	WUProp@Home	07/02/2013 22.51.22	update requested by user
	raspberrypi	WUProp@Home	07/02/2013 22.51.25	Sending scheduler request: Requested by user.
	raspberrypi	WUProp@Home	07/02/2013 22.51.25	Requesting new tasks for CPU
	raspberrypi	WUProp@Home	07/02/2013 22.51.38	Scheduler request completed: got 0 new tasks
	raspberrypi	WUProp@Home	07/02/2013 22.51.38	Message from server: This project doesn't support computers of type armv6l-unknown-linux-gnueabihf

Notice: I'm using BOINC 7.1.0 with mods from QCN for the nci process.

You may need to add in the app_info.xml (e.g. after the line <version_num>339</version_num>):

<platform>XXXXXXX</platform>

(what to put in place of XXXXXXX I can't say, somebody running similar system have to check (search for <platform>) in his client_state.xml)

P.S.
Instead of "I've uncompress this file in the correct path" better post (copy) the real path here so people can check is it really 'the correct path'

Do you see in the startup messages:
"[WUProp@Home] Found app_info.xml; using anonymous platform"

---

- ALF - "Find out what you don't do well ..... then don't do it!" :)

Do you see in the startup messages:
"[WUProp@Home] Found app_info.xml; using anonymous platform"[quote]

Yes, I see the anonymous message.

[quote]You may need to add in the app_info.xml (e.g. after the line <version_num>339</version_num>):

<platform>XXXXXXX</platform>

(what to put in place of XXXXXXX I can't say, somebody running similar system have to check (search for <platform>) in his client_state.xml)

Ok, found in client_state.xml and copy into app_info this line:

<platform>armv6l-unknown-linux-gnueabihf</platform>

and after boinc restart it works! :)
Thank you!
Now my rasPi run 4 WUs (3 nci) and 1 full CPU, attached to 5 different projects (radioactive, QCN, asteroids, albert and WUprop), good job for a 5-watt-PC.

*Sigh* I just found out that in newer BOINC clients (e.g. 7.1.0) they correctly interrogate ARM CPU info.

There's no need for that additional code I added to the source to add platform info. Just upgrade the BOINC client.

Feel like an idiot...