It seems that driver-package of nvidia has those bugs,
who are creating trouble under Linux - wherefor it is better
to run vesa under Linux than nvidia-drivers ...
sometimes it is better not to use the most modern or most actual software
like those drivers of nvidia, which are not completely un-bugged.

There are bugs in nVidia drivers (as in any other software) but this thread is not about any of them.

The bug was in the server part of BOINC (at setiathome.berkeley.edu)
(Not connected/induced by anything that you as user do or not do on your machine (except your chosen BOINC version).
The problem: the new BOINC server code (that runs in the SETI lab at Berkeley) 'forgot' that it have to connect also to older (before v7) BOINC versions on the user machines.

The new BOINC server code reported <type>NVIDIA</type> but the older BOINC versions on the user machines understand only <type>CUDA</type>
Now BOINC server code is fixed to report <type>NVIDIA</type> if you use BOINC 7.0 (or later) and <type>CUDA</type> if you use BOINC < v7 (e.g. 6.10.x)
)

So, if I understand this correctly, these WUs are sitting in my caches on 7 rigs like little time bombs waiting to go off when they get to the top of the cache?
____________
***************************************
I am still the kittyman.
Accept no imitations.

My GTX560 TI and 2x GTX550Ti rigs don't seem to have a problem with them other than they take 3-5 times longer to complete than an average work unit (both rigs no signs of bogging down even with each card doing 2 at a time).

It will interesting to see how my 3x 9800GT rig handles them when it comes to getting into its lot, but then drivers have come quite a long way since the VLAR code was first introduced.

So, if I understand this correctly, these WUs are sitting in my caches on 7 rigs like little time bombs waiting to go off when they get to the top of the cache?

No, the problem only happened to hosts running stock where the server sends a complete app_version. Hosts running anonymous platform are merely told which of the app_versions listed in the app_info.xml to use.

So, if I understand this correctly, these WUs are sitting in my caches on 7 rigs like little time bombs waiting to go off when they get to the top of the cache?

No, the problem only happened to hosts running stock where the server sends a complete app_version. Hosts running anonymous platform are merely told which of the app_versions listed in the app_info.xml to use.

Joe

Thanks, Joe.
That gives the kitties a little more peace of mind.
____________
***************************************
I am still the kittyman.
Accept no imitations.

2) the "Server Status" page shows as a blank! (as of time & date posted)

It's partially available on http://setiathome.berkeley.edu/server_status.php although very slow to load to it. Thus looks like a new server setup has been loaded, as the 'server_status.php' page is the default page in the BOINC back-end source code. 'sah_status.html' is the Setified page for it, but not the standard one.
____________Jord

I just put up a new machine, Enigma III. I can't get work. All my machines will be changing over the next two weeks. I never have been successful in bringing work assignments to a new machine. ( a little help? ).

Shouild be soon. The project has had problems and work's underway. Downloads just came back.

If you don't get some soon, open a thread in Q&A or Number Crunching - we don't usually do troubleshooting in this forum.
____________
Another Fred
Support SETI@home when you search the Web with GoodSearch or shop online with GoodShop.