Just a heads up that I've done the first part of updates to the build system,

sh ./_autosetup
sh ./configure --enable-sse2 --enable-fast-math BOINCDIR=/your_boinc_repo/
make

(or equivalents) should be enough to get a 'working' build in most circumstances now, though still some work to do with making more libs static, and then enabling more robust error handling.

Good stuff, Jason. I've got my two Linux boxes with good GPUs crunching away now, but the app_info.xml files are far from optimal. BTW, makes go faster on multi-core systems if you use the "-j n" flag to use n cores in parallel.

Any questions about these updates & what remains, feel free to ask.

"Multibeam V7 Cuda, Linux Build system prelim updates: nvcc.m4 - disable with-cuda option( updated to full nvcc -gencode strings instead of arch spec. base Cuda version required 3.2 (for now). cuda include directory added to CFLAGs. match nvcc bitlevel to host compiler target. Makefile.incl - Added ORIGIN rpath to LDFLAGS, to enable locating the libraries in executable's directory, tweaked output name. client/Makefile.am - remove deprecated preprocessor definition & kernel file target

I've got something strange going on with a system with an old, slow GPU spontaneously running openCL AP, but I'd better find another thread for that.

---

can you can stay on Fedora 14 for testing purposes ? I'm currently building/tweaking fine on FC13. Just trying to do a 'proper job' as opposed to my first hack attempts. Those hacks work but are not generalised enough, and don't include the robustness of the Windows apps yet. That means I'm digging into & fixing the _autosetup/configure/Makefile templates (which is taking time).

Hi Jason,
I can and I will.

b.t.w.
In the next six weeks I'm going to spend a random amount of time with my family in our summer place, but we'll visit home at least once in the week (at the linux machine) and I'll try to read the forum and check my inbox even if I'm not at home.

--
petri

I have to do "./boinc_client restart" after log on - otherwise cuda work will not start. .. but both cards do work after a manual restart.

Find a way to delay boinc_client start (e.g. for 1-2 minutes) so the NVIDIA driver can start/load fully before BOINC attempt to detect presence of CUDA
(I don't know how to do that on Linux)


Since you have different GPUs:
Device 1: GeForce GTX 560 Ti, 1279 MiB
Device 2: GeForce GTX 660, 2047 MiB

... do you use:
<use_all_gpus>1</use_all_gpus>

http://boinc.berkeley.edu/wiki/Client_configuration#Options

Thanks,

I have the <use_all_gpus>1</use_all_gpus> but I have had no success with all kind of delays in the startup script.

Strangely the 3.19.xx driver seemed to enable the cards in a way that the seti-boinc recognised them at the boot-up/log-in, but that driver did not let me (the machine) to use the second card at all even though boincmgr reported that I have 2 cuda devices.

The "./boinc_client restart" did not correct the situation - even after that, only one card was actually used. The estimated time for the 3 tasks on the second card kept rising.

That's why I had to revert back to 3.10.xx.
--
petri

---

To overcome Heisenbergs:
"You can't always get what you want / but if you try sometimes you just might find / you get what you need." -- Rolling Stones

Now I have to do "./boinc_client restart" after log on - otherwise cuda work will not start. .. but both cards do work after a manual restart.

The reason for this is the way boinc works.
The nvidia driver is functional after the system has booted, it is part of the kernel.
But boinc expects some device nodes to exist before it can use the GPU.
These are normally created when the X-server is started the 1st time.

If you like to start boinc from a system startup script you have to create the device nodes by "hand".
For the first GPU add the following lines to your script:

mknod -m 666 /dev/nvidia0 c 195 0
mknod -m 666 /dev/nvidiactl c 195 255

This way you also can run boinc on systems without an X-server.

Thank You!

I did put these lines in my /etc/rc.local and now boinc GPU apps start right at boot/login.

mknod /dev/nvidiactl c 195 255 ; chmod 666 /dev/nvidiactl
mknod /dev/nvidia0 c 195 0 ; chmod 666 /dev/nvidia0
mknod /dev/nvidia1 c 195 1 ; chmod 666 /dev/nvidia1

---

To overcome Heisenbergs:
"You can't always get what you want / but if you try sometimes you just might find / you get what you need." -- Rolling Stones