Release Notes for BOINC 7.2
Version 7.2.33 of BOINC was released for general public use on 26 November 2013. Download it here.
Summary of new features 7.2.28
- Updated Translations.
- OpenCL support for Intel and AMD CPUs.
- Add new AMD GPU descriptions.
- Add new Windows version descriptions. (Windows Only)
- Various changes to CPU and GPU scheduling and work-fetch.
- Support for HTTPS URLs in notices.
- Fix for running VirtualBox VMs when installed as a service. (Windows Support, it was already support for Mac OS X and Linux).
Note that BOINC 7.2 is incompatible with Domain Controllers on Windows (see below).
Summary of new features 7.2.31
- Fix: Disable downloading of images in notices. It was crashing BOINC Manager.
Summary of new features 7.2.33
- client and manager: the set_cc_config and get_cc_config GUI RPCs had nonstandard replies, which weren't parsed correctly by the calling code.
OpenCL support for CPU
BOINC 7.2 has OpenCL support for CPUs, but this does require that you install OpenCL drivers for your CPU.
AMD has an OpenCL 1.2 driver available for any AMD CPU with SSE2 and later.
Get it from their download page. For stability reasons, you may not want to install the sample applications. They may destabilize your system.
Intel has an OpenCL 1.2 driver available for 3rd and 4th Generation Intel Core.
Top right corner of this page has the download links. A separate driver is available for 1st and 2nd Generation Intel Core CPUs, 32bit version here, 64bit version here.
Note: When you have an AMD HD 5XXX or higher, or FirePro GPU installed, with up-to-date Catalyst drivers, your CPU may already have OpenCL support enabled.
To test OpenCL support being enabled, see Determine OpenCL capability of GPU and CPU in the BOINC FAQs Wiki.
For Linux support, AMD requires a minimum of openSUSE 11.x, Ubuntu 11.04, or Red Hat Enterprise Linux 6.x for AMD OpenCL support on the CPU.
Intel requires a minimum of Red Hat Enterprise Linux, or SUSE Linux Enterprise Server for Intel OpenCL support on the CPU.
Note: It's possible that installing either CPU SDK will work on the other CPU brand as well.
OpenCL support for GPU
BOINC + VirtualBox installer
VirtualBox is virtualization software that allows you to run entire operating systems (such as Linux, Mac OS X, Windows XP, Windows Vista, Windows 7, Windows 8, Solaris, FreeBSD and OpenSolaris) in a virtual environment inside the operating system that you run. So if you run Windows, you can at the same time run Linux, without the need to install this separately on part of a hard drive, and the need to reboot to switch between the OSes.
Not all projects running under BOINC require VirtualBox to be installed. At the moment, there are 4 projects which are known to require VirtualBox (see the list here).
We recommend BOINC + VBox because we want there to be a large pool of volunteer hosts with VBox installed.
That will make it feasible for projects to deploy VM apps, which will make it easier for projects to deploy apps in general.
When using the BOINC + VirtualBox installer, and:
- When you have a version of VirtualBox installed already and its version number is 4.2.16 or higher, the installer will just install BOINC 7.2.28.
- When you have a version of Virtualbox installed already and its version number is lower than 4.2.16, the installer will install VBox 4.2.16 and then install BOINC 7.2.28.
You have the choice to install VirtualBox or not. Although the BOINC + VirtualBox installer will tell you it is a requirement, it will also give you the option to install VirtualBox or not. You are not required to do so (but you will want to do so if you run the projects which require it). If you don't need VirtualBox you can also use the standard BOINC installer, which just installs BOINC.
Note: Due to problems with work-fetch for Test4Theory with the 4.2.18, 4.3.0 and 4.3.2 versions of VirtualBox, the version included in the BOINC + VirtualBox installer is VirtualBox 4.2.16
Note: The projects will send a virtual machine (VM) image to you when you add any of the projects using this technology. This image can be several hundreds of megabytes big, maybe more than a gigabyte. If your internet service provider has you on a bandwidth cap (download quota), check with them how much your monthly allowance is, before using this. You can check in the forums of the affected projects how many megabytes of gigabytes their VM image is.
You can set install options by clicking the "Advanced" button on the configuration screen. The options are:
- Program directory - where BOINC's program files will be stored.
- Data directory - where BOINC's data files will be stored.
- Use BOINC screensaver - Use the BOINC screensaver for the current user.
- Service Install - Run project applications under an unprivileged account. This provides increased protection against faulty applications, but it may cause graphics to not work with older applications. Do not install BOINC in protected application execution mode on Windows Vista and Windows 7 if you plan to use a GPU for doing calculations. These OSes run the drivers and user accounts in different sessions, so BOINC will not be able to detect your GPU. This is a security measure by Microsoft, it isn't something BOINC can fix.
- Allow all users on this computer to control BOINC - If selected (public mode), all users can control BOINC (attach/detach projects, etc.). If not selected (private mode), the only users who can control BOINC are: the installing user, members of the Administrator group, and members of the 'boinc_users' group. When other users run the BOINC Manager, they'll be shown a dialog saying to contact the administrator to add them to the 'boinc_users' group.
To run BOINC invisibly, choose the "Protected application execution" option, then in BOINC Manager -> Options, uncheck "Run Manager at login?". You can still run the BOINC Manager by going through Start->All Programs->BOINC and (double)clicking BOINC Manager.
The following issues are already known to the developers:
Incompatibility warning for return to BOINC 6
Due to changes to BOINC on how client_state.xml is written to, once you have gone over to 7.0, you cannot return to 6 without getting problems. We strongly suggest making a backup copy of the data directory before upgrading to the new build just in case something happens and you need to roll-back to an earlier build of BOINC.
To clarify, when you upgrade to BOINC 7.2 or later, everything should work as normal; work in progress will continue to run. When you downgrade from 7.0 or later to an earlier 6.x version, work in progress will disappear. You'll still be attached to all your projects. The client will fetch work from them, only if the project has 'resend lost work' on, will it be reissuing the previous lost work, which will start from the beginning.
Else you set No New Tasks under BOINC 7.2 and run all work in cache to its end, then upload & report it.
Next uninstall 7.0, then delete client_state.xml and client_state_prev.xml from your BOINC Data directory.
Next reinstall BOINC 6.x, then set Allow new tasks.
BOINC and the use of VirtualBox 4.2.18, 4.3.0 or 4.3.2
You can use VirtualBox versions 4.2.18, 4.3.0 or 4.3.2 with BOINC 7.2.28 without any problems, as long as you do not use the Test4Theory project. This project has severe work-fetch problems with these versions of VirtualBox, and is therefore limiting itself to a maximum of 4.2.16 for the time being. This is also why the BOINC + VirtualBox installer includes the 4.2.16 version.
Known Issues on Linux
BOINC 7.2 incompatible with Fedora 14 & 15
Due to a problem with incompatible wxWidget build options BOINC 7.0 will not work on Fedora 14 & 15.
This cannot be fixed, due to a difference in how wxWidgets is compiled between Fedora Core and Ubuntu. Ubuntu is the platform BOINC is built on.
Known Issues on Windows
Service Installation, GPU detection and Windows XP
Due to problems with up-to-date GPU drivers causing BOINC to crash or hang, it was decided that for all versions of Windows the GPU detection will no longer work when BOINC is installed as a service. This may change in a future version, but only after the GPU manufacturers have adjusted their driver code. So even in Windows 2000 and XP you can now no longer install BOINC as a service yet still have it detect your GPU(s) and run work on it. This change is present since 6.12.38
BOINC 7.2 incompatible with Domain Controllers
The present range of BOINC 7 is incompatible with Domain Controllers, meaning that you cannot install it on your system if it is a DC. This is because the developers used the Local Account API's instead of the Global Account API's.
Install BOINC 5.10.45 instead, even though this doesn't support GPUs or multi-threading applications.
Known issues with BOINC 7.2.26 and Seti when updating from BOINC 7.0.28 or before and getting 197 (0xc5) EXIT_TIME_LIMIT_EXCEEDED errors on anonymous platform GPU
When you've updated to BOINC 7.2.26, coming from BOINC 7.0.28 or before, AND when crunching work on an anonymous platform GPU application (such as the ones from Lunatics), you have a good chance that all your work errs with a 197 (0xc5) EXIT_TIME_LIMIT_EXCEEDED error.
This is because of an addition to the code in BOINC 7.0.33, where when you run the anonymous platform and you have not supplied a flops value in your app_info.xml file, that the flops value used for GPU tasks is increased by a factor of 10.
It will only affect old work still in cache from before the upgrade. Any newer work your BOINC downloads, will not be affected.
Two ways to work around this:
1. Before you upgrade, set No New Tasks and run your cache empty. Report all. Then upgrade to the new version and set Allow New Tasks.
2. Done the upgrade with a full cache? Reset the project. This will throw away all present work in cache, but since the project has resend lost work available, your tasks will be resent to you and seen as new work.
Error 1069: Service cannot be started because of a faulty login
This happens after something has removed the "Logon as a Service" from the "boinc_master" user account that was created during setup.
Known reasons for why this might happen:
- The administrator for your network has specified which accounts are allowed to "Logon as a Service" via Group Policy. Any account not on that list is stripped of that user right.
Known Issues on Macintosh OS X
Nvidia CUDA support broken on OS X 10.9 (Mavericks)
Depending on your Nvidia GPU, the CUDA drivers on Mavericks may not support it. This is due to Apple changing some things in the drivers for these models. Nvidia note this in their developer notes, and say it will be fixed soon. Despite their CUDA v5.5.28 drivers stating they support Mavericks, they actually do not.
BOINC ownership or properties are not set correctly
After you updated to Mavericks, you will need to reinstall BOINC to fix the permissions to groups and users. When you neglect to do so, you'll get the message BOINC ownership or permissions are not set properly; please reinstall BOINC. (Error Code - 1008), so just follow that advice and all will be well.