Posts by pvh

1) Message boards : Questions and problems : BOINC and amdgpu-pro (Message 77528)
Posted 21 Apr 2017 by pvh
Post:
OK, got it figured out. The problem was that my /etc/ld.so.cache was out of date and also my LD_LIBRARY_PATH was set wrong. Both errors had the same effect: opencl code would pick up the wrong version of libamdocl64.so. The proprietary driver puts its libraries in /opt/amdgpu-pro/lib64 while the open source amdgpu driver has its libraries in /usr/lib64. When the /usr/lib64 version is picked up, opencl code doesn't work. Got that all sorted and the GPU is happily crunching away now...

PS - amdgpu-pro is officially still not supported under openSUSE, but you can download the SLES version and then apply the patch outlined here:

https://community.amd.com/thread/212558
2) Message boards : Questions and problems : BOINC and amdgpu-pro (Message 77526)
Posted 21 Apr 2017 by pvh
Post:
I am running openSUSE Leap 42.2 and recently bought a Radeon RX 480 gfx card. I got it running fine with the AMD proprietary driver amdgpu-pro v17.10. However, when I try to open run_manager, it fails to open a window and when I look at the client output, it says "No usable GPUs found". I am using client version 7.6.31 from rechenaugust.de. Is amdgpu-pro supported, and if so, how do I get it to work with BOINC?
3) Message boards : Questions and problems : BOINC 7.0.18 forces autoraise (Message 43068)
Posted 16 Mar 2012 by pvh
Post:
I thought you would be interested in fixing problems, but if you are not, feel free to ignore my reports...
4) Message boards : Questions and problems : BOINC 7.0.18 forces autoraise (Message 43057)
Posted 16 Mar 2012 by pvh
Post:
I have noticed that the Linux 64-bit version of the run manager of BOINC 7.0.18 forces the window autoraise feature (i.e. when I move the mouse over the window, the window is automatically raised). I do not have this feature enabled on my desktop as I find it extremely annoying. I would like to ask you to respect my desktop settings and not force the autoraise feature on me. Thank you!
5) Message boards : Questions and problems : BOINC 7.0.18 doesn't set execute permission (Message 43056)
Posted 16 Mar 2012 by pvh
Post:
I found that when the updated Rosetta binary was downloaded recently, BOINC did not set the execute permission. As a result all subsequent WUs failed because executing the binary was not permitted. The Rosetta people assured me that they changed nothing and this is likely a BOINC problem. This is the 64-bit Linux version of BOINC 7.0.18.
6) Message boards : Questions and problems : How do I limit backup projects to 1 WU at a time (Message 39600)
Posted 12 Aug 2011 by pvh
Post:
OK, too bad...

I am quite happy with the cache settings I have now, they have saved my bacon on more than one occasion. So I don't want to change those.

These short Milkyway outages happen every 24-48h from my limited experience so far, so babysitting Boinc is not really an option. I have manually aborted jobs up to now, but I cannot keep that up in the long run.

So I guess the only option I have is to detach from Primegrid and take the down time whenever it comes...

Thanks!
7) Message boards : Questions and problems : How do I limit backup projects to 1 WU at a time (Message 39596)
Posted 11 Aug 2011 by pvh
Post:
Thanks, but fetching 1 WU per time for all projects would be unacceptable. I would be out of work almost immediately every time there is a network / server outage...

I do not see any option to set the cache size with Primegrid either. They just inherit the global setting for all projects with no possibility to override that.

I am really stomped on this one...
8) Message boards : Questions and problems : How do I limit backup projects to 1 WU at a time (Message 39593)
Posted 11 Aug 2011 by pvh
Post:
I wonder how I can force Boinc to only download 1 WU at a time for backup projects. I am running Milkyway as a main project for my ATI GPU with PrimeGrid as a backup. Milkyway only allows me to keep 12 WUs max in the queue, which is good for 15-25 min of work. So even a brief server outage can drain the queue. Hence I have PrimeGrid as a backup project. However, every time that kicks in, Boinc immediately downloads 22 PrimeGrid WUs, which is good for 20h of work or so. This is far more than I want to spend on PrimeGrid. That should really only be run when there is absolutely nothing else to do. I want Boinc to return to Milkyway as quickly as possible. So what I want is an option to download only 1 WU at a time from the backup project until the Milkyway server is back up. How can I do this? I am using Boinc 6.10.58.




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.