Folding Forum

A long time ago, some WUs were worth 0.6 points for 1.5 hours of compute on an Athlon XP 2000+ ... and there was no quick return bonus ...

The science FAH produces is a rather slow process and it has to follow the academic rules : you only get updates when something is published (and reviewed).

It must have been a transient error, it downloads your team certificate when I click on the link.

Yes, the bad WUs are automatically turned off after a few retries ...

But posting some logs and WU references could help us reporting them directly to the researcher.

Bob_6591 wrote: ↑Tue Nov 21, 2023 2:02 pm Medium Settings – F@H Web Control
[...]
Full Settings – F@H Web Control
[...]

This setting has no effect on GPU folding.

bikeaddict wrote: ↑Sun Dec 03, 2023 2:18 am It may be trying to execute instructions like AVX or SSE4.x that aren't supported on a CPU as old as an AMD Phenom II X2.

Don't worry about this, the core is running perfectly fine on my old first generation i7s (920 and 860).

This is definitely a library issue. Fedora 39 is very new ...

Is there a log somewhere the show the startup of the client ?

I guess he's seeing the bug that show bad PPD estimates after a resume from checkpoint of a CPU WU ... since the first % after a resume is not a full %, PPD are inflated until the client progresses a couple more.

But without precise numbers or logs, we can't tell for sure.

Usually, the FAH compute core doesn't like when the number of threads is adjusted too often ... it increases the risk of loosing WUs.

It is also highly inefficient to run more working thread than available CPU threads ...

Why do you have this in your settings ?
Disable proxy or use a valid address for the proxy setting ...

I guess it's from the CPU core ? If yes, v7 was showing the same behaviour and it's because of how CPU core handles checkpoints.

One of your GPUs doesn't seem stable ... did you run some stability tests ?

Did you try to start FAH on only one GPU at once ?

Is PSU powerful enough to feed both GPUs ?

Folding@home server infrastructure has no way to know that you (or any specific user) can't access a specific server ... it only monitors the server availability (up or down) and jobs availability.

I alerted (again) the person in charge of these servers, but it might be a campus wide policy ...

This system keeps cycling 23:51:31:WU00:FS00:Starting 23:51:31:WU00:FS00:Removing old file 'work/00/logfile_01-20231031-231156.txt' 23:51:31:WU00:FS00:Running FahCore: /usr/bin/FAHCoreWrapper /var/lib/fahclient/cores/cores.foldingathome.org/openmm-core-23/centos-7.9.2009-64bit/release/0x23-8.0.3/Co...

There's nothing wrong here ... the client seen the the Vega M GPU and the Intel HD 630 integrated in your CPU since they are both capable to fold. Although the Intel iGPUs are too slow for most work, which mean why it doesn't get work. The Intel dedicated GPUs (Arc) are no capable of folding, so no ...