Message boards :
Number crunching :
Boinc v7.8.0 for linux
Message board moderation
Author | Message |
---|---|
W3Perl Send message Joined: 29 Apr 99 Posts: 251 Credit: 3,696,783,867 RAC: 12,606 |
I'm using boinc v7.8.0 provided by TBar on his website : http://www.arkayn.us/forum/index.php?topic=197.msg4519#msg4519 I have an issue about selecting options in 'Computing preferences' No way to scroll inside sub-windows.... Does someone else have the same problem ? Is there a 7.8.2 available (it seems to be the last stable version on Windows/Mac) ? [/img] PS: Oupss..title should be 'Boinc 7.8.0' and not '8.0.0' ! |
Richard Haselgrove Send message Joined: 4 Jul 99 Posts: 14650 Credit: 200,643,578 RAC: 874 |
I would avoid all versions of the 7.8.x line for the time being. We're still finding bugs in it (on top of the 20 or so we know about already), despite it having been declared - falsely - as having passed alpha testing. For Windows, the only benefits are a newer version of VBox (which you can get from Oracle anyway), and a possible reduction in file corruptions when downloading multiple large files for the VBox wrapper/docker type of application. Neither of those are used here. For Mac, you should be able to get a "recommended" v7.8.2 from the standard download site: http://boinc.berkeley.edu/download.php - that one has been prepared by the official BOINC developer for Mac. If the same problem (or any other problem) appears, please report it. For Linux, the usual advice is to see whether there is an active BOINC maintainer making a more modern version of BOINC available as a package tailored for your Linux distro. Again, I see no benefit from upgrading beyond v7.6.x at this time. |
W3Perl Send message Joined: 29 Apr 99 Posts: 251 Credit: 3,696,783,867 RAC: 12,606 |
I would avoid all versions of the 7.8.x line for the time being. We're still finding bugs in it (on top of the 20 or so we know about already), despite it having been declared - falsely - as having passed alpha testing. I use 7.2.42 on Mageia (no maintainer available) which is more than 3 year's old. This is 'stone age' in the computer timescale ;) On the forthcoming Ubuntu 17.10 (next month) , boinc 7.8.2 have been packaged....but I will to wait for the next LTS 18.04 as we use only LTS. Except the sub-windows problem (and the scroll back in 'tasks' when you download new tasks), 7.8.0 works fine for me. |
TBar Send message Joined: 22 May 99 Posts: 5204 Credit: 840,779,836 RAC: 2,768 |
I thought you reported this earlier and found the problem was with driver 384? You have 2 other machines running 7.8.0 without driver 384, do they have the same problem? I can't even run driver 384 on my Ubuntu 16.04.3 system with kernel 4.10.x, the driver fails at startup. Keith also had problems with driver 384, that's why he is using driver 375.66. I can't test BOINC 7.8.0 with kernel 4.10 due to boot failure, but 7.8.0 works fine with every other system/driver I've tried. I would suggest using a different driver, 375.66 seems to work well. Here's the Linux board at nVidia, you'll see driver 384 there a few times, https://devtalk.nvidia.com/default/board/98/linux/1/ |
Richard Haselgrove Send message Joined: 4 Jul 99 Posts: 14650 Credit: 200,643,578 RAC: 874 |
TBar, what's the last commit in your v7.8.0 source? Did you pull it from master or the release branch? (the release branch is still missing multiple commits - see my pull request #2065) |
TBar Send message Joined: 22 May 99 Posts: 5204 Credit: 840,779,836 RAC: 2,768 |
The zip file used for the 7.8.0 compile came from the release branch on 23 July, you'll have to decide which commit that was. You might note there was a similar problem with the same machine with the GPU Fan Control App here, https://setiathome.berkeley.edu/forum_thread.php?id=81771&postid=1884361#1884361. As far as I know, no one else reported that problem either. I don't have any problems on my machines using driver 375.66 with the 4.10 kernel, driver 384 simply won't work though. Driver 384 Will work on my machines with the 4.8 and lower kernels, it's just the higher kernels that have problems. For me the solution was to use driver 375.66 with kernel 4.10 in Ubuntu. |
Richard Haselgrove Send message Joined: 4 Jul 99 Posts: 14650 Credit: 200,643,578 RAC: 874 |
It's easy enough to look them up here: https://github.com/BOINC/boinc/commits/client_release/7/7.8 I'd say you're missing https://github.com/BOINC/boinc/commit/709a04cebe50ff7ca47a3d2f6effc419ffb02a2c, which was certainly critical in the public release cycle. |
TBar Send message Joined: 22 May 99 Posts: 5204 Credit: 840,779,836 RAC: 2,768 |
Hmmm, that doesn't sound like a text display issue. It sounds like a 'jump to the bottom of the page' issue. I might try that in a day or two, IF, I make it through the next 24 hours of Hurricane. For now I have other things to do while I can still do them. |
Richard Haselgrove Send message Joined: 4 Jul 99 Posts: 14650 Credit: 200,643,578 RAC: 874 |
OK, hang on tight in there. |
Jeff Buck Send message Joined: 11 Feb 00 Posts: 1441 Credit: 148,764,870 RAC: 0 |
You might note there was a similar problem with the same machine with the GPU Fan Control App here, https://setiathome.berkeley.edu/forum_thread.php?id=81771&postid=1884361#1884361. As far as I know, no one else reported that problem either.That problem was simply an issue with Mageia 6 not respecting a text alignment property for the caption in a specific widget used by the app. It wasn't dependent on driver version or anything else that I'm aware of. |
Keith Myers Send message Joined: 29 Apr 01 Posts: 13164 Credit: 1,160,866,277 RAC: 1,873 |
I've seen only one fluke with BOINC 7.8.0. When using the set NNT, suspend Network activity method to get tasks flowing again, I see that the Network Activity state button NOT CHANGE state after toggling and restarting BOINC. The status of Network Activity DOES change, it just isn't being reflected in the radio button status correctly and not following the current Network Activity state. Seti@Home classic workunits:20,676 CPU time:74,226 hours A proud member of the OFA (Old Farts Association) |
W3Perl Send message Joined: 29 Apr 99 Posts: 251 Credit: 3,696,783,867 RAC: 12,606 |
I have one good reason to upgrade to 7.8.0 ! AstroPulse GPU tasks are aborted with '201 (0x000000C9) EXIT_MISSING_COPROC' with boinc 7.2.42 because boinc doesn't detect opencl in coprocesseurs. When using 7.8.0 openCL is detected and tasks are completed. 7.6.X may be the good version to use but the only way to upgrade on Mageia is to use TBar package (7.2.42 is the only one version available). |
Richard Haselgrove Send message Joined: 4 Jul 99 Posts: 14650 Credit: 200,643,578 RAC: 874 |
OK, that's a fair enough comment - I sympathise with your predicament. But with a - shall we say, perhaps - non-mainstream distro like Mageia (is that an acceptable description? To be honest, I hadn't heard of it before, but that may just be me), I think you'll find it hard to get bugs fixed by the central BOINC team. Your easiest solution is probably to find someone who experiences the same bug in a Linux distro with an in-house BOINC maintainer. They have better communications back into BOINC central. Failing that, could you persuade Mageia to incorporate BOINC into their distro? Having code and compilation experience together in the same place makes it much, much easier to test potential fixes, to say the very least. |
Jeff Buck Send message Joined: 11 Feb 00 Posts: 1441 Credit: 148,764,870 RAC: 0 |
I have one good reason to upgrade to 7.8.0 !Is that a problem specific to Mageia? On my machines running 7.2.42 with Ubuntu 14.04, I haven't had any issues with AstroPulse. In fact, there were quite a few processed just in the last 24 hours. See my hosts 8289033, 8253697 and 8257247. |
W3Perl Send message Joined: 29 Apr 99 Posts: 251 Credit: 3,696,783,867 RAC: 12,606 |
Is that a problem specific to Mageia? On my machines running 7.2.42 with Ubuntu 14.04, I haven't had any issues with AstroPulse. No...I'm using also Ubuntu and there is openCL info in the coprocesseur :( Need to install 7.8 to get opencl But boinccmd 7.8.0 doesn't seems to work ... :( I only get "Authorization failure: -102" from "boinccmd --host <host> --passwd <password> --get_cc_status" I will have to downgrade to 7.2.42 and forget about the AP.... |
Jeff Buck Send message Joined: 11 Feb 00 Posts: 1441 Credit: 148,764,870 RAC: 0 |
Hmmm, that certainly seems odd, but I don't know enough about Linux to even have a clue. I didn't have to do anything special on my 3 Linux boxes to get the AstroPulse tasks to run just fine. They've simply worked okay right from the beginning with 7.2.42.Is that a problem specific to Mageia? On my machines running 7.2.42 with Ubuntu 14.04, I haven't had any issues with AstroPulse. |
W3Perl Send message Joined: 29 Apr 99 Posts: 251 Credit: 3,696,783,867 RAC: 12,606 |
Hmmm, that certainly seems odd, but I don't know enough about Linux to even have a clue. I didn't have to do anything special on my 3 Linux boxes to get the AstroPulse tasks to run just fine. They've simply worked okay right from the beginning with 7.2.42.Is that a problem specific to Mageia? On my machines running 7.2.42 with Ubuntu 14.04, I haven't had any issues with AstroPulse. I have no problem running AP on CPU but on GPU it require openCL as the client is astropulse_7.08_x86_64-pc-linux-gnu__opencl_nvidia_100 I will try boinc v7.2.47 from AP and see if I have still the "Authorization failure: -102" with boinccmd Thanks for your help :) |
rob smith Send message Joined: 7 Mar 03 Posts: 22203 Credit: 416,307,556 RAC: 380 |
No problems running astropulse_7.08_x86_64-pc-linux-gnu__opencl_nvidia_100 under Mint 18.?? with BOINC version 7.6.31 Bob Smith Member of Seti PIPPS (Pluto is a Planet Protest Society) Somewhere in the (un)known Universe? |
Jeff Buck Send message Joined: 11 Feb 00 Posts: 1441 Credit: 148,764,870 RAC: 0 |
...on GPU it require openCL as the client isYes, that's the same app that I'm running successfully on my 3 boxes with 7.2.42. No OpenCL detection problems here, so I would have to guess that there's some component missing that BOINC needs to call in order to find OpenCL. I don't know what that might be, though. EDIT: BTW, I have driver 375.39 on one of my boxes and 375.66 on the other two. |
TBar Send message Joined: 22 May 99 Posts: 5204 Credit: 840,779,836 RAC: 2,768 |
The problem with 7.2.42 Not finding OpenCL has been discussed Numerous times previously. 7.2.42 is Only looking for the link named libOpenCL.so which some of the Repository drivers Don't create. I even walked Keith through creating a link to the OpenCL Library and naming it libOpenCL.so and then OpenCL was immediately found. It's the Driver that creates the link, NOT BOINC. That Bug was Repeatedly Named as being Fixed in the Rebuilt 7.2.47. If you don't want to use 7.2.42 because it isn't finding OpenCL with the Driver you are using, then use 7.2.47 as it has the Bug fixed; Bug, https://github.com/BOINC/boinc/blob/client_release/7/7.2/client/gpu_opencl.cpp#L179 Bug Fixed, https://github.com/BOINC/boinc/blob/client_release/7/7.6/client/gpu_opencl.cpp#L186 BOINC 7.2.47 Also looks for libOpenCL.so.1, which 7.2.42 Doesn't. 7.2.47 Also lists the CUDA Driver version, 7.2.42 Doesn't. 7.2.47 Also works in Ubuntu 16.04, where 7.2.42 complains about a mismatched wxWidget Shared Library in 16.04 and Doesn't work. I use 7.2.47, it works for me, http://www.arkayn.us/forum/index.php?PHPSESSID=l5gmuovk14on7mio8eqf5vtfa0&topic=197.msg4515#msg4515 |
©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.