I recently came back to SETI@Home, so I'm a complete noob in this matter and in need of help/advice.

I upgraded my video card from an nVidia EN9800GTX+ to an nVidia 670GTX+ yesterday. For another project (GPUGRID) everything is working well with the new video card; blocks I submitted since the upgrade have been checked and are fine. With the old card I had no problems processing cuda blocks for SETI either, but with the new card something seems to have gone wrong.

I'm receiving cuda_fermi blocks for my kepler card. Does this have something to do with the scheduler trouble of the moment, or is something else wrong? The website does seem to report my computer correctly as having:

GenuineIntel
Intel(R) Core(TM) i5-3570K CPU @ 3.40GHz [Family 6 Model 58 Stepping 9]
(4 processoren)

NVIDIA GeForce GTX 670 (2048MB) driver: 310.70

Any info or help is much appreciated, but keep in mind I'm not a pro at this yet.

Thanks all!

[edit]
Forgot to mention:
Every downloaded block for cuda_fermi has processed for between 17 and 19 seconds, after which a calculation error was reported. There are 63 blocks with errors because of this.
[/edit]

---

[edit]
Forgot to mention:
Every downloaded block for cuda_fermi has processed for between 17 and 19 seconds, after which a calculation error was reported. There are 63 blocks with errors because of this.
[/edit]

Try this: http://setiathome.berkeley.edu/forum_thread.php?id=69735

---

[edit]
Forgot to mention:
Every downloaded block for cuda_fermi has processed for between 17 and 19 seconds, after which a calculation error was reported. There are 63 blocks with errors because of this.
[/edit]

Try this: http://setiathome.berkeley.edu/forum_thread.php?id=69735

Made the link active.

Claggy

Thanks Ivan & Claggy

It's not a scheduler problem then. I'll try one of the solutions in the list.


PS. is there a way to force my client to start over on the failed jobs while the scheduler is down? Or can I only wait for the scheduler to come back up later (report failure and ask for new jobs)

Would be good to keep it working on the jobs it already downloaded while we wait.

---

Thanks Ivan & Claggy

It's not a scheduler problem then. I'll try one of the solutions in the list.


PS. is there a way to force my client to start over on the failed jobs while the scheduler is down? Or can I only wait for the scheduler to come back up later (report failure and ask for new jobs)

Would be good to keep it working on the jobs it already downloaded while we wait.

You only need to do the second solution,

You could reset the project and then get your failed work resent (but you'd loose any CPU results that you're completed), then hit update until all your tasks are resent, (you don't need to wait 5 minutes between attempts at resending)
But since you're only got a small cache you'd probably get them all in one attempt, upping to about three days cache might get you some fresh work before the servers go down.

Claggy

You only need to do the second solution,

You could reset the project and then get your failed work resent (but you'd loose any CPU results that you're completed), then hit update until all your tasks are resent, (you don't need to wait 5 minutes between attempts at resending)
But since you're only got a small cache you'd probably get them all in one attempt, upping to about three days cache might get you some fresh work before the servers go down.

Claggy

I added the "CUDA_GRID_SIZE_COMPAT = 1" value as shown in the screenshots. Will that suffice? It's not clear to me whether I'm supposed to do all A B and C steps listed under the Kepler compatibility section, or just pick one of them to make it work. I'd rather not downgrade my drivers. Shame that topic is closed for comments/questions, else I'd have posted it there by now.

I decided to just report the CUDA errors and CPU work I had done. I thought the servers were down already, but apparently they weren't, so I just got some new jobs instead.

I increased the cache to 3 days.

I have some other questions about configuring projects/BOINC, but as I'm offtopic already here, I guess I should start finding the right forum posts to ask away. After all I already found out my problem wasn't scheduler related.

---

UPDATE: the outage scheduled for the weekend of the 4th-6th has been cancelled so normal operations shall continue. We still plan to have our air conditioner repaired and will be completely off line from January 14th to January 15th during that time.

For those who havn't started at the beginning of this thread

Thank You Matt

Em que data (date) o seti@home volta ao normal?

---

[B]JERBIALDO [/ b]

Em que data (date) o seti@home volta ao normal?

Teoricamente já esta normal, pelo menos esta funcionando com o limite de 100WU por host.

---

Ditto here. My completed units are stacking up and not getting uploaded even if I click "update" When I click on "your results" it says I received 20 work units yesterday. I know I had completed units yesterday and those weren't uploaded.

Having the same issue, I cannot upload or get new tasks. Is SETI dying?

crickets are maxed out. you have to wait your turn.

---

Have been waiting for work all day now....

With all of these power outages I have read about recently cursing the eastern limits of the Berkeley campus I can't help but wonder if Pacific Graft & Extortion has a personal grudge against the university.



B.O.H.I.C.A.

Same for me , Please.
With a RAC of 1000 I do more then 100 WU a day.
CPU work continues, but the GPU is getting bored.

---

Am I safe in saying that the Seti@Home servers are now down for the next few days? Not able to get any work.

- William McCausland
Kelso, WA
January 13, 2013 -- 8:10 pm PST (GMT -0800)

I'm trying to figure it out too, no news on this.. maybe they found a signal ;)

I also heard that funding might have been cut... not sure rumor for now tho

Am I safe in saying that the Seti@Home servers are now down for the next few days? Not able to get any work.

- William McCausland
Kelso, WA
January 13, 2013 -- 8:10 pm PST (GMT -0800)

You would be correct. Today they will be doing repairs to the server closet air conditioner. It will take two days ( hopefully ) And probally Wednesday they will do the weekly outage.

When they do get back online expect the pipes to be plugged up for a day or two.

---

[/quote]

Old James

You would be correct. Today they will be doing repairs to the server closet air conditioner. It will take two days ( hopefully ) And probally Wednesday they will do the weekly outage.

When they do get back online expect the pipes to be plugged up for a day or two.

I would think that, depending on just when the AC repairs are finished, they will probably just do the weekly maintenance when they bring everything up but before going live with it. With any luck, that will still be Tuesday.

(Or, the way luck sometimes runs, the AC repairs will take longer than two days and they'll be down all week or longer.)

---

David
Sitting on my butt while others boldly go,
Waiting for a message from a small furry creature from Alpha Centauri.

The AC repairs were successful. We then performed our weekly outage tasks and are coming back on line.

---