Posts by javier

1) Message boards : BOINC client : Problems with OpenCL in Ubuntu using open source driver mesa (Message 80715)
Posted 3 Sep 2017 by javier
Post:
I can provide testdata in case you want to escalate this to the mesa developers. EaH uses the original ATI/Nvidia drivers as a reference and there are no problems there.


I´d love to! i don´t know exasctly how can i help, but i´ll do my best. And yes, there are no problems with propietary drivers.
2) Message boards : BOINC client : Problems with OpenCL in Ubuntu using open source driver mesa (Message 80661)
Posted 1 Sep 2017 by javier
Post:
what do you think about using bleed-edge Mesa from here?

https://launchpad.net/~oibaf/+archive/ubuntu/graphics-drivers

May that help?
3) Message boards : BOINC client : Problems with OpenCL in Ubuntu using open source driver mesa (Message 80651)
Posted 1 Sep 2017 by javier
Post:
as "original ATI driver", you mean propietary ones?

The point is that, propietary ATI drivers:

1) offers much worse performance under Ubuntu, and
2) they are not available anymore for the X version provided in newest Ubuntu versions
4) Message boards : BOINC client : Problems with OpenCL in Ubuntu using open source driver mesa (Message 80645)
Posted 1 Sep 2017 by javier
Post:
well, i see OpenCL support is 1.1.... maybe its not enough...

And, it seems OpenCL support in Mesa is not fully implemented... maybe thats another point.... https://dri.freedesktop.org/wiki/GalliumCompute/
5) Message boards : BOINC client : Problems with OpenCL in Ubuntu using open source driver mesa (Message 80611)
Posted 30 Aug 2017 by javier
Post:
just posted.... Will update with news, if any....

thank you
6) Message boards : BOINC client : Problems with OpenCL in Ubuntu using open source driver mesa (Message 80604)
Posted 30 Aug 2017 by javier
Post:
several,

seti@home, asteroids@home, Einstein@home.....
7) Message boards : BOINC client : Problems with OpenCL in Ubuntu using open source driver mesa (Message 80599)
Posted 30 Aug 2017 by javier
Post:
oh, and also, my GPUs are:

AMD: A6-5200 Quad-core with HD 8400

nVidia: GeForce GT 630
8) Message boards : BOINC client : Problems with OpenCL in Ubuntu using open source driver mesa (Message 80592)
Posted 30 Aug 2017 by javier
Post:
with *every task* i mean, *every task meant to be computed via OpenCL*, not regular CPU tasks
9) Message boards : BOINC client : Problems with OpenCL in Ubuntu using open source driver mesa (Message 80590)
Posted 30 Aug 2017 by javier
Post:
Hello again,

i have 2 different computers, one using AMD GPU ant the other using nVidia

Both of them are running open source drivers, via mesa. And i have installed mesa-opencl-icd package, so that BOINC detects GPU as opencl capable

But, *every* task i start ends with "computing error"!

What am i doing wrong?

BOINC version is 7.6.33, Ubuntu 16.04 and mesa 17.0.7

Thanks in advance!
10) Message boards : GPUs : Debian/Ubuntu/Mint/Derivatives - GPU recognition fixes (Message 44629)
Posted 26 Jun 2012 by javier
Post:
Hello,

This is my /etc/boinc-client/cc_config.xml content:

elhoir@elhoir-desktop:/etc/boinc-client$ cat cc_config.xml
<!--
This is a minimal configuration file cc_config.xml of the BOINC core client.
For a complete list of all available options and logging flags and their
meaning see: http://boinc.berkeley.edu/trac/wiki/ClientMessages
-->
<cc_config>
<log_flags>
<task>1</task>
<file_xfer>1</file_xfer>
<sched_ops>1</sched_ops>
</log_flags>
</cc_config>
elhoir@elhoir-desktop:/etc/boinc-client$

I have tried to insert the lines you previously asked me to add, andi had to reinstall BOINC :D
11) Message boards : GPUs : Debian/Ubuntu/Mint/Derivatives - GPU recognition fixes (Message 44582)
Posted 21 Jun 2012 by javier
Post:
hello again,

im having this problem, but the other way roud :)

BOINC detects my GPU (nVidia GT 220) but its unable to use it.

Currently i have SETI@home CPU tasks disabled, and only GPU tasks enabled, and i cant process any GPU WU.

Im currently running boinc 7.0.24 from official repo, under Ubuntu 12.04

any idea?
12) Message boards : BOINC client : Linux BOINC manager 6.10.17 does not detect any useable GPU... (Message 30637)
Posted 23 Jan 2010 by javier
Post:
err.. well, yeah, drivers are properly installed (as noticed with the glxinfo command, and as i can set dektop-effects and run 3D games :) )

i dont know where do i have to look for finding where BOINC looks for drivers....
13) Message boards : BOINC client : Linux BOINC manager 6.10.17 does not detect any useable GPU... (Message 30635)
Posted 23 Jan 2010 by javier
Post:
...and as you know from my previous posts, i have a nVidia GT 220 (CUDA enabled), which is working properly with the 6.10.18 version in Windows (it was also working fine in 6.10.17)

what can b the cause?

FYI, i use Ubuntu 9.10 and the BOINC manager is from http://www.getdeb.net/updates/Ubuntu/9.10/?q=boinc
14) Message boards : BOINC Manager : No CPU core used while there are available WUs!! (Message 30525)
Posted 13 Jan 2010 by javier
Post:
eithier because Seti was set to NNT

yeah, i set it to not download more WUs until i finish the ones i have in queue... but i didnt see that those WUs could onle be processed by the GPU

ok, thank you so much for your help :)
15) Message boards : BOINC Manager : No CPU core used while there are available WUs!! (Message 30518)
Posted 13 Jan 2010 by javier
Post:
Edit: after another look at your host, your GPU has been doing VLAR (very low angle range) tasks which are very slow using the Cuda app,
which will have driven your host's DCF (Duration Correction Facture) up, Boinc will have thought that all Seti tasks were going to take longer,
and so wouldn't have received as much CPU work, once you're finished any VLAR tasks on the GPU, and the GPU starts doing non-VLAR tasks,
then DCF will go down, run times wiil look more reasonable, and you'll get more CPU work.


So, finally, you think this is the reason?

and btw, link is not working anymore.. sorry :(
16) Message boards : BOINC Manager : No CPU core used while there are available WUs!! (Message 30516)
Posted 13 Jan 2010 by javier
Post:
Is Boinc asking for CPU work from Seti?, since your Boinc log didn't include any work requests at all.


Well, i stopped BOINC to automatically fetch more WUs, since i have many of them available locally to analyse, let me show you a shot about my current BOINC tasks

http://img695.imageshack.us/i/boinc.jpg/
17) Message boards : BOINC Manager : No CPU core used while there are available WUs!! (Message 30515)
Posted 13 Jan 2010 by javier
Post:

After looking at your hosts task list, you're completed all your CPU tasks, leaving only GPU tasks left,

hm.. how can i know which are GPU tasks and which CPU tasks?
18) Message boards : BOINC Manager : No CPU core used while there are available WUs!! (Message 30513)
Posted 13 Jan 2010 by javier
Post:
nah, i have reviewed many times all Preferences pages... they are identical for both projects
i have no idea about whats wrong with it...

Also i have removed the "home" preferences, so that now i only have the default ones.... but they are identical in both seti@home and docking@home

and docking@home uses the cpu... seti@home doesnt....
19) Message boards : BOINC Manager : No CPU core used while there are available WUs!! (Message 30512)
Posted 13 Jan 2010 by javier
Post:
Ah-ha,
i have switched to another project, docking@home, and cores work correctly

so its a seti@home specific preferences issue, lets investigate in that way :)
20) Message boards : BOINC Manager : No CPU core used while there are available WUs!! (Message 30511)
Posted 13 Jan 2010 by javier
Post:
Look and see whether you've perhaps unticked "Do work ... while computer is in use" (processor usage tab).


Hi, no, i dont have any un-ticked option there....

i have checked and restarted BOINC several times, and i dont find a solution.. :-/

The thing is, cores start working when i re-fetch WUs from server, but after analyzing several of them (half of them, i would say), CPU stops....


Next 20

Copyright © 2024 University of California.
Permission is granted to copy, distribute and/or modify this document under the terms of the GNU Free Documentation License, Version 1.2 or any later version published by the Free Software Foundation.