Folding Forum

That would be a concern.

Yes it's running systemd. I'm unclear why systemd or other services infrastructure would care whether it's in full screen terminal mode, where GUI overhead detracting from folding is minimized. I see no disadvantage with folding lid closed (screen drawing less power). I'm treating it more like a hea...

Hmm I guess it may be questionable gui settings in use. "Blank Screen" for closing lid on battery or AC power may be some crank dev's idea of "Ok let's mess with their mind and go sleep after all." Will have to try Do Nothing to see if that helps.

I should have been more clear, I'm not using M$oft products. This is debian 12 bookworm or (soon to be) 13 based. Power settings in gui that I know how to nav to are the best they can be for the purpose. You understand what I mean by full screen terminal? It's not a feature you find on Windoze to my...

Oops sorry I didn't notice the earlier post link to github where they explain the sleep prevention protocol dependency fix will be in next client version. @muziqaz Yes, if you mean the Keep Awake setting in machine config, that option is always enabled. But it seems to have no effect on the full scr...

Quick tangentially related question, newbie nondev on new install of debian stable trixie. On amd64 arch particularly, how is the fah client update project going, to deal with the policykit protocol incompatibility with trixie? Rough time horizon? Place to track dev chatter or announcement? Are ther...

It appears that every time I reboot my debian 12.9 bookworm rig with a new kernel, "Machine ID" changes, which invalidates or suspends any WU in progress. Probably they get mothballed indefinitely. Log shows errors for a WU in progress, how it "does not belong" to a certain Clien...

On a debian stable 8.4.9 client for CPU WUs, I've unfortunately managed to have the folding service lose track of a couple units in progress. It looks as though they still exist in the ~folding/work/[unit ID] area, but may have been subtly defeated somehow, by a system irregular shutdown or the like...

Interestingly, the checkbox for anonymous folding was clear in the interface, so I couldn't tell it was giving me guff. When I checked/unchecked it, that's when it started downloading core blobs and enabled WUs to start. Happy now, so I can put the nondebug package back. Thanks much!

Ok thanks, I removed the 5GiB of useless GPU packages to let early missing library errors be benign. Afaict, the permissions of client.db ought to allow writing by UID fah-client, though it's possible the GID setting is wrong; unsure how to check that. Installed the debug build and here's what it sa...

On a debian bookworm & bullseye AMD64 4-core rig, I installed v8.1.18 beta; even though there's only a low-watt incompatible GPU, and I haven't configured for GPU WUs, it appears to require package nvidia-cuda-dev for a library, and ocl-icd-opencl-dev for OpenCL. 5GiB of senseless installed bloa...

Maybe this reply ought to be a new topic. Suggest a subject line? I'm considering installing beta 8.1.x client to see if it's more agreeable. It sounds nearly stable enough to end beta test, maybe at least for nonGPU. Something I should know beforehand though: are there critical incompatibilities be...

Thanks for the info . From what I can gather, v8.1 is maybe more hospitable or efficient.

On debian bullseye and bookworm systems both, I've installed the 7.6.21 fahclient as a systemd service, so it can automatically launch at boot time. So far so good- have racked up loads of points on this config. I've dug through system journal seeing no messages offering clues as to why the explicit...

Care to share your result in case someone else would like to do it? Pardon the delay, but it's embarrassingly trivial: telnet localhost ... finish exit voila: exit brings you back from the telnet to your shell. Incidentally, someone finally built an update of the fahcontrol package that works on de...