Hi fellow Grid Denizens,

My client has not received jobs over several days, though the server status indicates work units are available. It's been about a year since I last ran GPUGrid jobs,but would like to start contributing cycles to the project again.

Client is running Rosetta CPU jobs fine, GPUGrid is my only GPU project.

I've reset the project, looked at project preferences, etc. but no joy so far.

Newer builds than 7.2.42 aren't readily available for Suse, though I might be able to jab in the Fedora builds for 7.6.22, or build from source or a spec (though I think that was a bit of a pain last time I tried). And I'm not sure the issue is with the client version.

I'd appreciate any assistance to get things running.

Cheers,
Pete

If you look closely you'll find the reason for it as your host asks GPUGrid for CPU tasks not for GPU tasks:

Thank you for pointing out the "Requesting CPU tasks" (not GPU), and indeed the first lines of event log included "GPU detection failed. error code 512"

After modprobe nvidia_uvm the GPU was still not being detected.

I realized as well I had been starting the client bdirectly via /usr/bin/boinc, and while that allowed Roesetta jobs to run, starting via systemd was needed for GPU detection - which makes sense, I just wasn't thinking of it.

When started via systemd GPU was detected and info logged to /var/lib/boinc/coproc_info.xml and of course the GPU then showed in the initial lines of event log.

Thanks for the help! Chomping away on work units once again...