Posts by computezrmle

1) Message boards : News : Linux Apps Avaliable (Message 292)
Posted 10 May 2018 by computezrmle
Post:
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
2) Message boards : News : Linux Apps Avaliable (Message 287)
Posted 10 May 2018 by computezrmle
Post:
... 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.
3) Message boards : News : Linux Apps Avaliable (Message 276)
Posted 9 May 2018 by computezrmle
Post:
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.




©2020 Jon Sonntag; All rights reserved