Linux versions of the Collatz Sieve application are now available. This includes 32 and 64 bit versions of the cpu apps, ATI OpenCL, Intel OpenCL, and nVidia OpenCL apps.

Excellent work Slicker, thank you.

They are taking a while on a CPU, but I like a challenge.

Conan

Thank you Slicker!

However, my Linux doesn't download anything from collatz.

Tue 08 May 2018 11:53:03 AM JST | collatz | Sending scheduler request: To fetch work.
Tue 08 May 2018 11:53:03 AM JST | collatz | Requesting new tasks for CPU and NVIDIA GPU
Tue 08 May 2018 11:53:05 AM JST | collatz | Scheduler request completed: got 0 new tasks
Tue 08 May 2018 11:53:05 AM JST | collatz | No tasks sent

This repeats every two minutes. Its project directory is created (/var/lib/boinc/projects/boinc.thesonntags.com_collatz), but it contains nothing.

Why?

---

Luckiest man in the world

My Linux machine began downloading workunits for cpu, but not for nvidia OpenCL although my boinc client requested. As a matter of course it's ready to crunch. Now my nvidia gpus are crunching for Amicable numbers OpenCL apps which will be the backup project of Collatz.

Why again?

---

Luckiest man in the world

Thank you Slicker!

However, my Linux doesn't download anything from collatz.

Tue 08 May 2018 11:53:03 AM JST | collatz | Sending scheduler request: To fetch work.
Tue 08 May 2018 11:53:03 AM JST | collatz | Requesting new tasks for CPU and NVIDIA GPU
Tue 08 May 2018 11:53:05 AM JST | collatz | Scheduler request completed: got 0 new tasks
Tue 08 May 2018 11:53:05 AM JST | collatz | No tasks sent

This repeats every two minutes. Its project directory is created (/var/lib/boinc/projects/boinc.thesonntags.com_collatz), but it contains nothing.

Why?

See Number Crunching FAQ.

See Number Crunching FAQ.

Thank you for your reply. I read FAQ and I checked sched_op_debug on and requested work units. It actually requests workunits for nvidia cards and my Linux is ready for OpenCL as it is now crunching for amicable numbers with OpenCL. The log says as follows:

Tue 08 May 2018 11:07:31 PM JST | collatz | sched RPC pending: Requested by user
Tue 08 May 2018 11:07:31 PM JST | collatz | [sched_op] Starting scheduler request
Tue 08 May 2018 11:07:31 PM JST | collatz | Sending scheduler request: Requested by user.
Tue 08 May 2018 11:07:31 PM JST | collatz | Requesting new tasks for NVIDIA GPU
Tue 08 May 2018 11:07:31 PM JST | collatz | [sched_op] CPU work request: 0.00 seconds; 0.00 devices
Tue 08 May 2018 11:07:31 PM JST | collatz | [sched_op] NVIDIA GPU work request: 688721.59 seconds; 2.00 devices
Tue 08 May 2018 11:07:33 PM JST | collatz | Scheduler request completed: got 0 new tasks
Tue 08 May 2018 11:07:33 PM JST | collatz | [sched_op] Server version 711
Tue 08 May 2018 11:07:33 PM JST | collatz | Project requested delay of 121 seconds
Tue 08 May 2018 11:07:33 PM JST | collatz | [sched_op] Deferring communication for 00:02:01
Tue 08 May 2018 11:07:33 PM JST | collatz | [sched_op] Reason: requested by project

Actually I had enabled nvidia gpu and cpu works in Collatz preference page and it had downloaded cpu workunits (now cpu work is disabled in preference page). Now it requests nvidia workunits for nearly 700000 seconds and got 0 new tasks. So I'm wondering why.

Thanks in advance!

---

Luckiest man in the world

Can't get work for my GPUs (NVIDIA and ATI) running on linux.
What makes me wonder is that the app page shows different naming patterns for windows and linux apps:

windows: (opencl_ati_gpu), (opencl_intel_gpu), (opencl_nvidia_gpu)
linux: (ati_opencl), (intel_opencl), (nvidia_opencl)

According to my backups, the old linux apps had the same naming patterns than the windows apps.

Will the ARM executables for Linux be back at some point as well?

Can't get work for my GPUs (NVIDIA and ATI) running on linux.
What makes me wonder is that the app page shows different naming patterns for windows and linux apps:

windows: (opencl_ati_gpu), (opencl_intel_gpu), (opencl_nvidia_gpu)
linux: (ati_opencl), (intel_opencl), (nvidia_opencl)

According to my backups, the old linux apps had the same naming patterns than the windows apps.

Thank you so much for pointing out the discrepancy. I was pulling my hair out trying to find the issue when it all looked OK. Given the way BOINC sets up the app names in folders with xml files, it will be a few hours of work to dot the i's and cross the t's but I'll get it fixed ASAP. Thanks again.

... it will be a few hours of work to dot the i's and cross the t's but I'll get it fixed ASAP.

Do 10 Mai 2018 09:11:29 CEST | collatz | Requesting new tasks for NVIDIA GPU
Do 10 Mai 2018 09:11:29 CEST | collatz | [sched_op] CPU work request: 0.00 seconds; 0.00 devices
Do 10 Mai 2018 09:11:29 CEST | collatz | [sched_op] NVIDIA GPU work request: 87940.65 seconds; 1.00 devices
Do 10 Mai 2018 09:11:30 CEST | collatz | Scheduler request completed: got 0 new tasks

No success.
Did you finish the changes?
If the app page shows recent numbers, nobody got a linux task so far.


What about the "_gpu" at the end of the app name?
Does it correspond to "<plan_class>opencl_nvidia_gpu</plan_class>"?

If you kept your naming convention
Old app: collatz_sieve_1.21_x86_64-pc-linux-gnu__opencl_nvidia_gpu
New app (expected): collatz_sieve_1.40_x86_64-pc-linux-gnu__opencl_nvidia_gpu
app page (expected): 1.40 (opencl_nvidia_gpu)

I'm not sure if this "_gpu" tells the scheduler to decide between cpu and gpu apps and answer a request accordingly.

As another volunteer mentioned here, activating "Run test applications" did the trick.

Nonetheless, as I had prepared a *.config file prior to the app download I got a checksum error and burned the first task:
https://boinc.thesonntags.com/collatz/result.php?resultid=1065689

Do 10 Mai 2018 16:47:43 CEST | collatz | Started download of collatz_sieve_1.40_x86_64-pc-linux-gnu__opencl_nvidia
Do 10 Mai 2018 16:47:43 CEST | collatz | File collatz_sieve_1.40_x86_64-pc-linux-gnu__opencl_nvidia.config exists already, skipping download
Do 10 Mai 2018 16:47:43 CEST | collatz | Started download of collatz_sieve_679b27c5-e6ae-40af-a699-b6fe52e6d549
Do 10 Mai 2018 16:47:43 CEST | collatz | [error] Signature verification failed for collatz_sieve_1.40_x86_64-pc-linux-gnu__opencl_nvidia.config
Do 10 Mai 2018 16:47:43 CEST | collatz | [error] Checksum or signature error for collatz_sieve_1.40_x86_64-pc-linux-gnu__opencl_nvidia.config

The 2nd attempt was successful and I managed to get the *.config back in place before the tasks started.
It then ran with the optimization setting I used prior to the outage.
The result can be seen here:
https://boinc.thesonntags.com/collatz/result.php?resultid=1065916

... it will be a few hours of work to dot the i's and cross the t's but I'll get it fixed ASAP.

Do 10 Mai 2018 09:11:29 CEST | collatz | Requesting new tasks for NVIDIA GPU
Do 10 Mai 2018 09:11:29 CEST | collatz | [sched_op] CPU work request: 0.00 seconds; 0.00 devices
Do 10 Mai 2018 09:11:29 CEST | collatz | [sched_op] NVIDIA GPU work request: 87940.65 seconds; 1.00 devices
Do 10 Mai 2018 09:11:30 CEST | collatz | Scheduler request completed: got 0 new tasks

No success.
Did you finish the changes?
If the app page shows recent numbers, nobody got a linux task so far.


What about the "_gpu" at the end of the app name?
Does it correspond to "opencl_nvidia_gpu"?

If you kept your naming convention
Old app: collatz_sieve_1.21_x86_64-pc-linux-gnu__opencl_nvidia_gpu
New app (expected): collatz_sieve_1.40_x86_64-pc-linux-gnu__opencl_nvidia_gpu
app page (expected): 1.40 (opencl_nvidia_gpu)

I'm not sure if this "_gpu" tells the scheduler to decide between cpu and gpu apps and answer a request accordingly.

I implemented the plan_class_spec.xml (see https://boinc.berkeley.edu/trac/wiki/AppPlanSpec#FieldsforGPUapps) with every combination of names (opencl_ati, opencl_amd, ati_opencl, amd_opencl, etc.) although prior to that, WUs were being returned successfully for all apps so people were getting work.

Hello - thankyou for the linux-client software. My Intel-GPU works fine - great work! Greetings, Klaus

It seems to be working for me.