Install Steam
login
|
language
简体中文 (Simplified Chinese)
繁體中文 (Traditional Chinese)
日本語 (Japanese)
한국어 (Korean)
ไทย (Thai)
Български (Bulgarian)
Čeština (Czech)
Dansk (Danish)
Deutsch (German)
Español - España (Spanish - Spain)
Español - Latinoamérica (Spanish - Latin America)
Ελληνικά (Greek)
Français (French)
Italiano (Italian)
Bahasa Indonesia (Indonesian)
Magyar (Hungarian)
Nederlands (Dutch)
Norsk (Norwegian)
Polski (Polish)
Português (Portuguese - Portugal)
Português - Brasil (Portuguese - Brazil)
Română (Romanian)
Русский (Russian)
Suomi (Finnish)
Svenska (Swedish)
Türkçe (Turkish)
Tiếng Việt (Vietnamese)
Українська (Ukrainian)
Report a translation problem
https://www.tomshardware.com/news/folding-at-home-worlds-top-supercomputers-coronavirus-covid-19
And of its results, in this case finding a useful binding site in a previously "undruggable" molecule on Ebola:
https://www.biorxiv.org/content/10.1101/2020.02.09.940510v1.abstract
it keeps giving me a warning about "no WUs available for this configuration".
lets wait a day or two
thx for sharing
Think twice before using old hardware. Your contribution may be pointless and you would be wasting energy. IMO, unless you have a high end GPU it's more efficient to directly donate to the project the extra money you would have to pay in your power bill when contributing with your old hardware.
They had about 30k contributors one week and jumped to 400k contributors the next week due to COVID, so they're warning folks that for now some holdups may happen.
True, power efficiency should be accounted for to some extent, but we're currently on a "getting results out as fast as possible even if not at peak efficiency" mode... some coments on the GoL post mention the energy caveat as well. This is still a million times better than burning Watts on bitcoin mining ;)
And yes, they do accept donations! And they do need them to help scale up server-side to reduce the current bottlenecks in distributing new workloads to contributing users.
Also worth noting this will run as lowest priority task and can be paused whenever the user wants, so shouldn't be any issue installing on the beefy main gaming PC where it has a higher chance to run faster and at the same time more efficiently, even if you intend to use it frequently these days.
in 1-2 days if i notice it is indeed pointless, then i'll just stop the service. no big beal
I know, sometimes efficiency has to wait. Still, it would be nice to have a calculator that tells the users if using certain hardware plus a kw price is better than a direct donation or not (as anyone can actually rent hardware in many cloud service it's quite easily to get a ratio to use as base)
If anyone has an AMD GPU like me and wishes to utilize its power for computing instead of just the CPU, OpenCL libs need to be installed.
I'm currently trying to install AMD's OpenCL libs without replacing the opensource AMDGPU driver with the AMDGPU-PRO closed source driver, by following this instruction:
https://einsteinathome.org/pt-br/content/quick-guide-how-install-opencl-amd-gpus-linux-kubuntu-1804-and-similar-distro?page=1
Phoronix has tried to benchmark Folding@home recently and it didn't run on the opensource ROCm OpenCL implementation, hence the need for this.
...but in my case room temperature is ranging from 25ºC to 35ºC most of the year so here this is not useful unless someone invents an egg-boiler CPU dissipator design
https://www.proofpoint.com/us/threat-insight/post/new-redline-stealer-distributed-using-coronavirus-themed-email-campaign
Good warning!
I read the linked article and it's a common case of emails pretending to be from someone else and offering a link to a fake website offering a malicious software... no flaw in the real software from the real website.
So heading to Folding@home's official website directly (not clicking on link from random email) and installing from there is perfectly safe despite this shenanigans.
edit: added an alert to the OP
They just write to install it in headless mode right? like this:
./amdgpu-pro-install --opencl=legacy,pal --headless
doesn't work for me. I mean, CPU would work, but my GPU would be much more efficient.
Gist GPU device Information: https://gist.github.com/NRG-R9T/adb2de58c0bafaeb4c8e5113cbd66c5f
EDIT: found out that I missed the Config to tell the GPU to work, but still doesn't start a job. might need some time.
Try running "clinfo" and check that you get an output. You should see information regarding the OpenCL version that your GPU supports.
Yes, that's exactly what happened to me as well, thanks for bringing that up!
1. download, install and run FAHClient
2. get happy at some CPU work done
3. download and install amdgpu-pro, using these options for install:
2. reboot
3. scratch my head at the gpu still not being detected, and no web interface option to fix this
4. try to install and run FAHConfig, but it doesn't talk to FAHClient correctly for whatever readon
5. figure where config.xml is and what editing is necessary... which is just one extra line for the GPU, similar to the first one with the CPU
6. discover why nothing makes a difference... it's because there can exist two config.xml (one on my home folder, generated on acident when I manually ran the client) and another on a folder for all users (used by the client when it runs as a service when the OS boots)
my guess for gpu not being auto-listed is that the config.xml got generated before I added the OpenCL parts (because I ran it before that) and isn't REgenerated automatically, so would only list the gpu on its own if OpenCL was already there at first run, or if I deleted config.xml first