I've backported the fix to the 7.2, 7.4, and 7.6 branches. ----- Rom
-----Original Message----- From: boinc_dev [mailto:[email protected]] On Behalf Of Christian Beer Sent: Tuesday, July 21, 2015 5:43 AM To: [email protected] Subject: Re: [boinc_dev] Boinc for Arm on Linux doesn't report the CPU model, only the vendor. Debian stable (Jessy) is on 7.4 old-stable (wheezy) is on 7.0 but 7.4 is available through wheezy-backports. Ubuntu Trusty (14.04LTS) is on 7.2 but the latest 7.2 is only available through trusty-backports. Ubuntu Utopic (14.10) is on 7.4.8 with no newer version in backports. Ubuntu Vivid (15.04) is on 7.4.23. So it seems backporting to at least 7.2 is necessary to get the fix into Ubuntu 14.04LTS backports. OpenSuse, Fedora and CentOS6 seem to be on 7.2.42 for newer versions and 7.0.x for older versions. Gianfranco is maintaining the Debian based packages, I don't know who is doing RPM packaging for CentOS and OpenSuse. MfG / Regards Christian Beer Am 20.07.2015 um 23:09 schrieb David Anderson: > What version are the package maintainers using? > Hopefully patching 7.4 would suffice. > -- David > > On 20-Jul-2015 1:20 PM, Stephen Maclagan wrote: >> I've patched my local 7.2 head and recompiled Boinc 7.2.47, and it >> works: >> >> http://setiweb.ssl.berkeley.edu/beta/show_host_detail.php?hostid=7413 >> 8 >> >> Mon 20 Jul 2015 20:13:07 UTC | | Starting BOINC client version >> 7.2.47 for armv7l-unknown-linux-gnueabihf Mon 20 Jul 2015 20:13:07 >> UTC | | log flags: file_xfer, sched_ops, task, sched_op_debug Mon 20 >> Jul 2015 20:13:07 UTC | | Libraries: libcurl/7.26.0 OpenSSL/1.0.1e >> zlib/1.2.7 libidn/1.25 libssh2/1.4.2 librtmp/2.3 Mon 20 Jul 2015 >> 20:13:07 UTC | | Data directory: /home/pi/BOINC Mon 20 Jul 2015 >> 20:13:07 UTC | | No usable GPUs found Mon 20 Jul 2015 20:13:07 UTC | >> SETI@home | Found app_info.xml; using anonymous platform Mon 20 Jul >> 2015 20:13:07 UTC | | Host name: raspberrypi Mon 20 Jul 2015 >> 20:13:07 UTC | | Processor: 4 ARM ARMv7 Processor rev 5 (v7l) Mon 20 >> Jul 2015 20:13:07 UTC | | Processor features: half thumb fastmult >> vfp edsp neon vfpv3 tls vfpv4 idiva idivt vfpd32 lpae evtstrm Mon 20 >> Jul 2015 20:13:07 UTC | | OS: Linux: 4.0.8-v7+ Mon 20 Jul 2015 >> 20:13:07 UTC | | Memory: 926.03 MB physical, 100.00 MB virtual Mon >> 20 Jul 2015 20:13:07 UTC | | Disk: 14.48 GB total, 8.42 GB free Mon >> 20 Jul 2015 20:13:07 UTC | | Local time is UTC +0 hours Mon 20 Jul >> 2015 20:13:07 UTC | Albert@Home | URL http://albert.phys.uwm.edu/; >> Computer ID 12650; resource share 100 Mon 20 Jul 2015 20:13:07 UTC | >> SETI@home Beta Test | URL http://setiweb.ssl.berkeley.edu/beta/; >> Computer ID 74138; resource share 100 Mon 20 Jul 2015 20:13:07 UTC | >> Einstein@Home | URL http://einstein.phys.uwm.edu/; Computer ID >> 11741356; resource share 100 Mon 20 Jul 2015 20:13:07 UTC | SETI@home >> | URL http://setiathome.berkeley.edu/; Computer ID 7495179; resource >> share 100 Mon 20 Jul 2015 20:13:07 UTC | SETI@home | General prefs: >> from SETI@home (last modified 02-Feb-2015 14:45:48) >> >> >> Any chance of it being packported to the 7.0, 7.2, 7.4 and 7.6 heads >> please, then at least the repository builds have a small chance of >> getting updated. >> >> Claggy >> >> --------------------------------------------------------------------- >> --------------- >> >> Date: Sun, 19 Jul 2015 12:50:58 -0700 >> From: [email protected] >> To: [email protected]; [email protected] >> Subject: Re: [boinc_dev] Boinc for Arm on Linux doesn't report the >> CPU model, only the vendor. >> >> Stephen: >> Thanks. It looks like the /proc/cpuinfo format changed at some >> point, and we weren't parsing the model name correctly for ARM. >> >> I checked in changes that will parse the /proc/cpuinfo examples you >> sent. >> Hopefully this will also work on recent Android. >> >> Rom, can you please test this on whatever Android devices you have? >> >> -- David >> >> On 19-Jul-2015 10:36 AM, Stephen Maclagan wrote: >> >> On my Quad Core Raspberry Pi running Raspbian Wheezy: >> >> pi@raspberrypi ~ $ cat /proc/cpuinfo >> processor: 0 >> model name: ARMv7 Processor rev 5 (v7l) >> BogoMIPS: 57.60 >> Features: half thumb fastmult vfp edsp neon vfpv3 tls vfpv4 idiva >> idivt vfpd32 >> lpae evtstrm >> CPU implementer: 0x41 >> CPU architecture: 7 >> CPU variant: 0x0 >> CPU part: 0xc07 >> CPU revision: 5 >> >> processor: 1 >> model name: ARMv7 Processor rev 5 (v7l) >> BogoMIPS: 57.60 >> Features: half thumb fastmult vfp edsp neon vfpv3 tls vfpv4 idiva >> idivt vfpd32 >> lpae evtstrm >> CPU implementer: 0x41 >> CPU architecture: 7 >> CPU variant: 0x0 >> CPU part: 0xc07 >> CPU revision: 5 >> >> processor: 2 >> model name: ARMv7 Processor rev 5 (v7l) >> BogoMIPS: 57.60 >> Features: half thumb fastmult vfp edsp neon vfpv3 tls vfpv4 idiva >> idivt vfpd32 >> lpae evtstrm >> CPU implementer: 0x41 >> CPU architecture: 7 >> CPU variant: 0x0 >> CPU part: 0xc07 >> CPU revision: 5 >> >> processor: 3 >> model name: ARMv7 Processor rev 5 (v7l) >> BogoMIPS: 57.60 >> Features: half thumb fastmult vfp edsp neon vfpv3 tls vfpv4 idiva >> idivt vfpd32 >> lpae evtstrm >> CPU implementer: 0x41 >> CPU architecture: 7 >> CPU variant: 0x0 >> CPU part: 0xc07 >> CPU revision: 5 >> >> Hardware: BCM2709 >> Revision: a01041 >> Serial: 000000005e986701 >> >> >> >> >> Claggy >> >> >> > Date: Sun, 19 Jul 2015 10:11:30 -0700 >> > From: [email protected] <mailto:[email protected]> >> > To: [email protected] <mailto:[email protected]> >> > Subject: Re: [boinc_dev] Boinc for Arm on Linux doesn't report >> the CPU >> model, only the vendor. >> > >> > On Android (i.e. Linux) BOINC gets CPU info by parsing >> /proc/cpuinfo. >> > Maybe the format of this has changed. >> > Can someone who's seeing this problem please post the contents >> of /proc/cpuinfo >> > on their device? >> > Thanks -- David >> > >> > On 19-Jul-2015 6:09 AM, Stephen Maclagan wrote: >> > > The reason I'm posting this is Eric has released an Arm Seti >> app for >> Linux, at present it only works on Armv7l processors, and not on >> Armv6l >> processors, >> > > The different Boinc's available all show incomplete CPU >> information, as >> well as using a generic arm platform (for repository builds), >> > > so he's had to remove all the restrictions to allow hosts to >> get work, >> meaning Armv6l hosts get work that can't be completed successfully. >> > > >> > > All that he recent clients report is 'ARM': >> > > >> > > LocutusOfBorg's ppa Boinc 7.6.2: >> > > >> http://setiathome.berkeley.edu/show_host_detail.php?hostid=7506529 >> > > >> > > Self compiled Boinc 7.2.47: >> > > >> http://setiweb.ssl.berkeley.edu/beta/show_host_detail.php?hostid=74138 >> > > >> > > Back in the days of Boinc 7.0.27 it did report 'ARMv7 >> Processor rev 5 >> (v7l)', but not 'ARM' as the vendor: >> > > >> http://setiweb.ssl.berkeley.edu/beta/show_host_detail.php?hostid=75690 >> > > >> > > or 'ARMv6-compatible processor rev 7 (v6l)' >> > > >> http://setiathome.berkeley.edu/show_host_detail.php?hostid=7470252 >> > > >> > > Can we have it fixed in each head, so both are displayed, >> like the Android >> clients report: >> > > >> > > ARM >> > > ARMv7 Processor rev 5 (v7l) >> > > (4 processors) >> > > >> > > NativeBoinc also manages to report the CPU speed, is it >> possible for that >> to be added to the Android and Linux clients, >> > > so it mirrors what the x86 Windows/Linux/Mac clients report? >> > > >> > > Line 795 onwards: >> > > >> >> https://github.com/matszpk/native-boinc-for-android/blob/master/src/boinc-7.0.36/client/hostinfo_unix.cpp >> > > >> > > >> > > Claggy >> > > >> > > _______________________________________________ >> > > boinc_dev mailing list >> > > [email protected] <mailto:[email protected]> >> > > http://lists.ssl.berkeley.edu/mailman/listinfo/boinc_dev >> > > To unsubscribe, visit the above URL and >> > > (near bottom of page) enter your email address. >> > >> > _______________________________________________ >> > boinc_dev mailing list >> > [email protected] <mailto:[email protected]> >> > http://lists.ssl.berkeley.edu/mailman/listinfo/boinc_dev >> > To unsubscribe, visit the above URL and >> > (near bottom of page) enter your email address. >> >> > > _______________________________________________ > boinc_dev mailing list > [email protected] > http://lists.ssl.berkeley.edu/mailman/listinfo/boinc_dev > To unsubscribe, visit the above URL and (near bottom of page) enter > your email address. _______________________________________________ boinc_dev mailing list [email protected] http://lists.ssl.berkeley.edu/mailman/listinfo/boinc_dev To unsubscribe, visit the above URL and (near bottom of page) enter your email address. _______________________________________________ boinc_dev mailing list [email protected] http://lists.ssl.berkeley.edu/mailman/listinfo/boinc_dev To unsubscribe, visit the above URL and (near bottom of page) enter your email address.
