1) Message boards : Questions and problems : Ubuntu 20.10 but getting error on BOINC (Message 103860) Posted 6 Apr 2021 by Josh Post: Hi all I'm running BOINC on Raspberry 4B with Ubuntu 20.10. I experienced these issues, and also the issues from this thread https://boinc.berkeley.edu/dev/forum_thread.php?id=14013&sort_style=&start=0. In addition to many of the suggestions made here, the final solution for me was to follow the Optional Setup Hints for Debian listed here. https://boinc.berkeley.edu/wiki/Installing_BOINC_on_Debian Hope this is helpful to someone.

2) Message boards : GPUs : Nvidia GPUs Hot Hours After Running SETI (Message 50324) Posted 27 Aug 2013 by Josh Post: Hi Richard SETI returned 3 or 4 work units yesterday for you to examine. Regards Josh

3) Message boards : GPUs : Nvidia GPUs Hot Hours After Running SETI (Message 50314) Posted 26 Aug 2013 by Josh Post: Hi Richard I suspended the tasks manually. I'll run SETI for a number of hours today to give tasks a chance to complete so you can examine the results. Disabling SLI manually every night is not ideal, since I use the cards in SLI for games. I'll learn to live with GPU 1 clocking up. On a positive note, I'm loving GPU compute. I've done more work on this machine in 1 month than 3 years on my laptops :) Thanks for all your help so far! Regards Josh

4) Message boards : GPUs : Nvidia GPUs Hot Hours After Running SETI (Message 50309) Posted 25 Aug 2013 by Josh Post: Hi Richard and community. I've some more detailed information to describe my issue. I've just run SETI work on demand (outside my normally scheduling hours)and noted some key values from MSI Afterburner. After a restart, both GPUS have the following values. Core Clock: 51 MHz Shader Clock: 101 MHz Memory Clock: 135 MHz During BOINC Work, the following values are displayed. Remember that only GPU 2 (of two) is performing work, yet the values for both GPUs are identical. Core Clock: 830 MHz Shader Clock: 1661 MHz Memory Clock: 2005 MHz These values are maintained after stopping SETI from working. So it appears that even after finishing work, the GPUs remain at full clocks. Further more, GPU 1 is clocking up even though BOINC is instructed to ignore it. Clocks return to normal following a restart. I also noticed that whatever data SETI loads into the GDDR5 is not being dumped after work stops. 367 MBs are occupied both during and post work. It may be worth mentioning that these GPUs were not purchased 1st hand. I bought both from a single seller to keep me going until I can afford a better solution in a later generation. As before, this behaviour is only evident after running SETI v7 cuda 42. Thank you for the assistance thus far. Regards Josh[/list]

5) Message boards : GPUs : Nvidia GPUs Hot Hours After Running SETI (Message 50308) Posted 25 Aug 2013 by Josh Post: Hi Richard I apologise. I should have given more detailed information. I've been allowing my PC to sleep overnight (thus not working) for the last month until I have this problem resolved. I would prefer to allow my computer to sleep (after 15 mins) during daylight hours, and then use Insomnia (or another app) to keep it awake overnight. Before I changed the sleep behaviour SETI was running (at least the event log reported completed work and I was awarded credit). Should I allow SETI to run for the next few evenings to give you data to work with? I have MSI Afterburner on always to preserve custom fan curves and limit FPS for gaming. I'll run SETI and get back to you with some more detailed information. Regards Josh

6) Message boards : GPUs : Nvidia GPUs Hot Hours After Running SETI (Message 50300) Posted 24 Aug 2013 by Josh Post: Thanks for your response Richard Is this what you were after? 23/08/2013 6:37:26 PM | SETI@home | URL http://setiathome.berkeley.edu/; Computer ID 7034435; resource share 200 By scheduling do you mean running for fixed hours over night? The CPU limitation is to keep power usage and heat under control. Using Geforce 320.49 drivers at present. Happy to post any further required information. Regards Josh

7) Message boards : GPUs : Nvidia GPUs Hot Hours After Running SETI (Message 50288) Posted 23 Aug 2013 by Josh Post: Hello BOINC Community I've recently built a new desktop machine, in part for the purpose of running BOINC. Relevant Info ------------- OS: Windows 8 x64 Client: 7.0.64 GPU: 2 x ASUS Nvidia 560Ti in SLI App: SETI@home v7 (cuda42) I've set my machine to run SETI and other apps overnight. Compute finishes at 7am. When I return to my computer hours after compute finishes, MSI Afterburner reports GPU temps of around 58 (GPU 1) and 40 (GPU 2). These are 15 - 20*C higher than normal idle temps. Can anyone explain what is going on? There doesn't seem to be a problem with other GPU apps. A restart solves the problem. Additionally, I've now set <ignore_nvidia_dev>0</ignore_nvidia_dev> since I throttle my CPU to 10% where it can't feed 2 GPUs. Even with this command enabled, GPU 1 still gets hot while GPU 2 is working, even though it's not being used (verified with Afterburner). Perversely, due to airflow constraints, it gets hotter than GPU 2. Regards Josh

8) Message boards : GPUs : PCIe Bus Saturation (Message 48298) Posted 21 Mar 2013 by Josh Post: Hi Ageless There seems to be some confusion about my question. I mustn't have explained properly. The motherboard has a Gen1 PCIe x16 slots, so its not a problem of physical dimension. What I want to know is, if I max out a given graphics card performing work for BOINC (or any application for that matter), how do I know what its interface bandwidth requirements are? I will compare this information against the available bandwidth from the PCI bus to see if I should get a better motherboard or buy a cheaper GPU. Regards Josh

9) Message boards : GPUs : PCIe Bus Saturation (Message 48295) Posted 21 Mar 2013 by Josh Post: Thanks for your response Richard I should have been clearer. My question relates the bandwidth requirement of the card itself. The Radeon 7770 at my local etailer is a PCIe 3.0 model with x16 connector. I want to know if such a card would saturate a PCIe 1.0 x 16 connector (probably yes). If so, how could I determine bandwidth requirement for GPUs generally? Josh

10) Message boards : GPUs : PCIe Bus Saturation (Message 48293) Posted 21 Mar 2013 by Josh Post: Hello BOINC Community I'm considering buying a refurbished desktop to dedicate to BOINC tasks. I'd like to buy a value GPU (eg; AMD 7770) to accelerate tasks. Its likely that said desktop will only have a PCIe 1 bus to equip the GPU. My question is, how can I tell if any graphics card I buy will saturate such an interface? I understand that PCIe 1 handles 250MB/second/lane. Where can I find out how much bandwidth the graphics card requires? If a 7770 saturates the available bus, I would prefer buy a cheaper GPU. Regards Albino

11) Message boards : GPUs : Using Sandy Bridge Integrated Graphics (Message 37149) Posted 11 Mar 2011 by Josh Post: I understand its not objectively powerful, but I have been impressed by its ability. I thought the Sandy Bridge integrated GPU would be a valuable resource for BOINC. Given it will ship on many notebooks and desktops, replacing other integrated Nvidia and AMD chips. Even operating in tandem with a graphics card it could be a power supplement for BOINC. It's a shame intel won't releasing an API.

12) Message boards : GPUs : Using Sandy Bridge Integrated Graphics (Message 37134) Posted 10 Mar 2011 by Josh Post: Hi I've recently purchased a new MacBook Pro 13' which only has the on die Intel Sandy Bridge graphics (Intel 3000 I believe). BOINC does not detect this GPU, according to the messages generated on loading it. Am I to infer that BOINC is not using my GPU? If not, how can I make it do so? Thanks Josh

---

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.