Hello,
Yesterday 08 August Einstein@home was offline due to maintenance. Today 09 August I do not get new work for my Intel GPU and I have nothing changed to my settings. But I get this message:
8/9/2017 7:10:36 AM | Einstein@Home | Your current settings do not allow tasks from this project. To fix this, you can change Project Preferences on the project's web site.
And there I see my Intel GPU is still switched on the receive work. But I do not get any.
Has it to do with yesterday's maintenance?
Thank you.
Greetings from
TJ
Copyright © 2024 Einstein@Home. All rights reserved.
maybe there is no work at the
)
maybe there is no work at the moment, this can be because of the maintenance, but maybe not
Your computers are hidden so
)
Your computers are hidden so it's not possible for a volunteer to consult the scheduler logs to see what the cause might be. However you certainly can.
If you consult this thread on the Getting Started board, it describes how to consult the scheduler logs on the server to get a description of the various procedures the scheduler went through in trying to see if there was any work that could be allocated to your host. If you have any trouble in understanding the content of the log, you will either need to 'unhide' your computers or at least give us the hostID of your machine so that someone can see what the problem is.
Let us know how you go.
Cheers,
Gary.
Hi, you have one host with
)
Hi,
you have one host with RAC > 0 that stopped requesting Intel GPU work yesterday evening 17:25 UTC. The last task was reported back at 18:09 UTC. The current coprocessor information for this host shows no Intel GPU, only a GTX 980. Usually a Windows update removes OpenCL support from the driver and you need to reinstall the GPU driver after the Windows update. I think that's what happened here.
Hi Christian, Thank you for
)
Hi Christian,
Thank you for your replay. Indeed there was a Windows update this morning. So I will try to reinstall.
However after other windows updates I continue to get work...
Greetings from
TJ
If you finally got the
)
If you finally got the creators update, that one is probably to blame. It killed the openCL on all my boxes when it installed.