Just talked to the rest of the dev team (and David Anderson who happens to be here on a visit) about your problem with using the OpenCL card. We'd like to narrow it down to either the app (and its BOINC API library) or the BOINC client, so we suggest to do the following for debugging the problem:
We would like to have a look at the init_data.xml file from the slot directory of a failed OpenCL task. DO NOT post that file here entirely because it contains confidential info!
Anyway the app_info.xml file and the rest of the slot files will be deleted shortly after the app fails, so the way to get this file is to use a special flag in cc_config.xml to tell the Boinc core client to exit before starting a new task (which allows to inspect the init_data.xml file of a new OpenCL task).
The tags that are interesting in the init_data.xml
xxx
yyy
zzz
and the whole stuff between the tags
and
The app (or more specifically the BOINC lib that gets linked to this app) will try to detect the device specified in the XML and this is where it fails currently.
The thing is: the OpenCL albert application is _not_ only the einsteinbinary_BRP4_1.23_i686-pc-linux-gnu__atiOpenCL. This binary is only one half of the OpenCL application and the other half is ... einsteinbinary_BRP4_1.00_graphics_i686-pc-linux-gnu. This is a bit strange and confused me for a long time, but finally one must provide this binary with the proper libraries. In my case the libs in question were available ... but in the 64-bit version only. So I copied the missing libs from a 32-bit system to /usr/local/lib/ and linked them to /usr/lib32/.
After this I asked the albert server for work again and now the OpenCL application is running. 13 minutes and still crunching.
Really ... I can understand that the application wants some essential libraries like the ones provided from the ATI driver, but the additional libraries ...
So I think that the dev may think about the use of this libs for future releases but for now I can say: nice work. It's running.
Thanks for the all the help, ideas and inspiration. May be this will be part of the documentation / FAQ for the OpenCL app to help others not to trap into this problem.
Stephan
Good to hear that...even tho I do not fully understand it :-) . This other program you mentioned is the graphics (screensaver equivalent) which is only executed when you ask for it by pressing a button in BOINC manager. It is not required to run the science app.
I suspect that it was more a reboot perhaps that fixed this, or maybe the OpenCL driver indirectly needs one of those libs that you installed additionally. Anyway, this is interesting an good to know in case the problem occurs with other volunteers, thanks for the feedback.
No reboot since ... erm ... well, no reboot in at least nearly two weeks. You may ask the devs if the OpenCL app depends somehow on the graphics application. They should know ... and I would not be suprised if it does.
Or you may try to unlink the libraries I mentioned or move them out of the library directory and restart boinc. I think I remember that you wrote that you installed the libGLU library to get the app running and this library is only needed by the graphics app, not the OpenCL app (see the ldd stuff above).
Anyway: I hope to see the OpenCL app sooner or later in the einstein project. Happy crunching.
:)
Stephan
PS:
boinc@celeron:~$ strings projects/albert.phys.uwm.edu/einsteinbinary_BRP4_1.23_i686-pc-linux-gnu__atiOpenCL |grep -i graphics
_ZN12GRAPHICS_APPC1Eb
_ZN12GRAPHICS_APP10is_runningEv
_ZN12GRAPHICS_APP3runEPc
_ZN12GRAPHICS_MSGC2Ev
xml_graphics_modes
_ZN12GRAPHICS_MSGC1Ev
_Z25boinc_graphics_make_shmemPKci
_ZN12GRAPHICS_APP4killEv
boinc_web_graphics_url
send_web_graphics_url
_Z24boinc_graphics_get_shmemPKc
_ZN14APP_CLIENT_SHM19decode_graphics_msgEPcR12GRAPHICS_MSG
boinc_init_graphics_diagnostics
graphics_info
graphics_app
%s
A lot of references to graphics in the OpenCL app ...
Hi Stephan, Just talked to
)
Hi Stephan,
Just talked to the rest of the dev team (and David Anderson who happens to be here on a visit) about your problem with using the OpenCL card. We'd like to narrow it down to either the app (and its BOINC API library) or the BOINC client, so we suggest to do the following for debugging the problem:
We would like to have a look at the init_data.xml file from the slot directory of a failed OpenCL task. DO NOT post that file here entirely because it contains confidential info!
Anyway the app_info.xml file and the rest of the slot files will be deleted shortly after the app fails, so the way to get this file is to use a special flag in cc_config.xml to tell the Boinc core client to exit before starting a new task (which allows to inspect the init_data.xml file of a new OpenCL task).
The flag is 1 , described here: http://boinc.berkeley.edu/wiki/Client_configuration
The tags that are interesting in the init_data.xml
xxx
yyy
zzz
and the whole stuff between the tags
and
The app (or more specifically the BOINC lib that gets linked to this app) will try to detect the device specified in the XML and this is where it fails currently.
Thanks for your help,
Heinz-Bernd
Okay ... I solved this
)
Okay ... I solved this puzzle.
The thing is: the OpenCL albert application is _not_ only the einsteinbinary_BRP4_1.23_i686-pc-linux-gnu__atiOpenCL. This binary is only one half of the OpenCL application and the other half is ... einsteinbinary_BRP4_1.00_graphics_i686-pc-linux-gnu. This is a bit strange and confused me for a long time, but finally one must provide this binary with the proper libraries. In my case the libs in question were available ... but in the 64-bit version only. So I copied the missing libs from a 32-bit system to /usr/local/lib/ and linked them to /usr/lib32/.
libGLU.so.1
libX11.so.6
libXau.so.6
libXdmcp.so.6
libXext.so.6
libxcb.so.1
After this I asked the albert server for work again and now the OpenCL application is running. 13 minutes and still crunching.
Really ... I can understand that the application wants some essential libraries like the ones provided from the ATI driver, but the additional libraries ...
So I think that the dev may think about the use of this libs for future releases but for now I can say: nice work. It's running.
Thanks for the all the help, ideas and inspiration. May be this will be part of the documentation / FAQ for the OpenCL app to help others not to trap into this problem.
Stephan
Hi! Good to hear that...even
)
Hi!
Good to hear that...even tho I do not fully understand it :-) . This other program you mentioned is the graphics (screensaver equivalent) which is only executed when you ask for it by pressing a button in BOINC manager. It is not required to run the science app.
I suspect that it was more a reboot perhaps that fixed this, or maybe the OpenCL driver indirectly needs one of those libs that you installed additionally. Anyway, this is interesting an good to know in case the problem occurs with other volunteers, thanks for the feedback.
Cheers
HBE
RE: Hi! ... I suspect that
)
boinc@celeron:~$ uptime
02:32:07 up 13 days, 10:12, 2 users, load average: 2.40, 2.37, 2.36
No reboot since ... erm ... well, no reboot in at least nearly two weeks. You may ask the devs if the OpenCL app depends somehow on the graphics application. They should know ... and I would not be suprised if it does.
Or you may try to unlink the libraries I mentioned or move them out of the library directory and restart boinc. I think I remember that you wrote that you installed the libGLU library to get the app running and this library is only needed by the graphics app, not the OpenCL app (see the ldd stuff above).
Anyway: I hope to see the OpenCL app sooner or later in the einstein project. Happy crunching.
:)
Stephan
PS:
boinc@celeron:~$ strings projects/albert.phys.uwm.edu/einsteinbinary_BRP4_1.23_i686-pc-linux-gnu__atiOpenCL |grep -i graphics
_ZN12GRAPHICS_APPC1Eb
_ZN12GRAPHICS_APP10is_runningEv
_ZN12GRAPHICS_APP3runEPc
_ZN12GRAPHICS_MSGC2Ev
xml_graphics_modes
_ZN12GRAPHICS_MSGC1Ev
_Z25boinc_graphics_make_shmemPKci
_ZN12GRAPHICS_APP4killEv
boinc_web_graphics_url
send_web_graphics_url
_Z24boinc_graphics_get_shmemPKc
_ZN14APP_CLIENT_SHM19decode_graphics_msgEPcR12GRAPHICS_MSG
boinc_init_graphics_diagnostics
graphics_info
graphics_app
%s
A lot of references to graphics in the OpenCL app ...
no problemo
)
no problemo