![]() > - Install boinc, open it, works fine, GPU detected, add a lot of GPU > This bug is annoying, a true paper cut, and really bad for new users: If any of the above is already fixed upstream, is there any chance to backport the fixes to Precise? LocutusOfBorg is correct to say an LTS will not upgrade to an unreleased version, but maybe these fixes can be chery-picked and patched in ubuntu and warrant an SRU, something like boinc_7.0.27-1ubuntu1. 0.27-1ubuntu1.Īlso, how come the ppa version is 7.0.53 if the official upstream is still 7.0.28? If any of the above is already fixed upstream, is there any chance to backport the fixes to Precise? LocutusOfBorg is correct to say an LTS will not upgrade to an unreleased version, but maybe these fixes can be chery-picked and patched in ubuntu and warrant an SRU, something like boinc_7. ![]() Terminal again: sudo service boinc-client start Manager can stop boinc (if user choose to exit tasks), but it cannot start it (lame!). In terminal: sudo service boinc-client restart Workaround is to restart the service after log in in each boot. boinc starts too early in boot sequence, before GPU drivers (or X, or DE) is active. Frustrated, new users purge boinc, not before giving negative feedback on Software Center Manager works again, but GPU is still not found. ![]() Manager does not work (client is down, and Manager does *not* auto-start it) Exit Manager (selecting to exit tasks too, in attempt to re-try) After reboot, Manager (*if* you care to open it) shows error for all GPU-related tasks, "GPU not available" Install boinc, open it, works fine, GPU detected, add a lot of GPU tasks, crunch happily This bug is annoying, a true paper cut, and really bad for new users: net/~costamagn agianfranco/ +archive/ locutusofborg- ppa net/~costamagn agianfranco/ +archive/ boinc Sorry for not giving an appropriate explanation, but for now this is the best we can do, maybe one day I'll apply for bug control and I'll have a closer connection with the MOTU's but now I really have no time to apply. 27 for now, I don't know when Daniel will update it. There is a version released in wich is the more stable one, but eg it's still at. So in the meanwhile I suggest to use my ppa if you want to "test" always the latest *unstable* release (I can release more than a version each day and no versions at all for weeks) or maybe use if you want a more stable release 34 in my opinion is really a good release, and it should become a stable one (I have to report my testcases on boinc alpha site), but we cannot ask for a SRU if we have no fix for an high importance bug or an updated version in debian (now debian is at. So ubuntu MOTU's could not easily (especially for a LTS release) update boinc, since they cannot update it with an unstable release. The latest boinc officially stable is the. Unfortunately there is a big problem (and partially my fault): This is the truth, but a working ppa is better than nothing.
0 Comments
Leave a Reply. |