I'm a noob about this stuff, so apologies for any cluelessness here.

I'm running BOINC on a Macbook Pro (6,2) with an NVIDIA GeForce GT330M. I had the NVIDIA CUDA 3.0 driver installed, and BOINCManager identified the GPU as "usable."

I just installed the CUDA 3.1.10 update, and now BOINCManager (6.10.58) says "no usable GPUs found."

Any advice? Wait patiently until there's a new version of BOINC?

Still something screwy somewhere.
Forums are slow as, and getting lots of Scheduler request faileds, even though network traffic has dropped off significantly. And even when it does connect, still getting the Project has no tasks available even though there are now plenty there.

Generally... Most DSL Modems are 100 megabit (wired).

What "I would do" is purchase a 1 gigabit Switch so that all of your wired machines go into it (if you have it pay the money for Cat 6e wiring). Then you end up with a link between the machines of 1 gigabit, the machines to the DSl of 100 meagbit and the Wireless to the machines 100 meagbit and 150 to the internet.
The DSL wireless I have is supposed to do 150N, the max I have ever seen is 65 megabits (adaptive). I moved my wireless to a 300N Router which connects at 150 megabits.

10Mbit vs 100 Mbit vs 1000 Mbit... all should choke the same on a 3Mbit pipe(dsl sync speed) and even less upstream. Which is what makes me think it might be a flow control issue on the wireless that is outperforming the wired.

V 1.2

Add: A block on the BOINC client, to run while rescheduling. The BOINC Manager sometimes restarts the client.
Add: A warning in the log, when the BOINC Manager is running.
Add: Rescheduling now uses the CPU and GPU ratio. The ratio is used by SETI to correct runtime estimates.
Changed: Rescheduling on the regular SETI installation is now permitted. (With two different plan classes running).
Fixed: Several small bugs

Just to clarify, as far as i am aware web-servers and file systems the way the work is after a crash or a serious error, the system reboots in read-only mode. Also usually a FSCK(File system check) is done on the server automatically.

It would seem the server encountered an error, and was either rebooted or rebooted itself into read-only mode to prevent any further issues. :)

(Good thing web servers and servers are my specialty.) ;)

As I said in Pappa's thread yesterday, that makes a lot more sense than his off-the-cuff remark about a BOINC database crash. I don't know much about web or general *nix servers, but I do know a bit about databases - and if the early outage was invoked by staff because of database problems, then they would have been the result of the spontaneous reboot, not the original cause. Different symptoms entirely.

Richard, if I understand this right, you saw indications of a short power / Internet access interuption, which may have caused the upload/download servers (and maybe others) to reboot in Read-Only mode, which then caused the Master BOINC database to crash. With ALL that chaos, they shut everything down and did a full restart.

That DOES make a whole lot more sense than just a Database crash.

I am aware of that post, the problem is my results went through the whole weekend last week without reporting anything by itself, i had to report them manually.

BOINC should never wait more than 24 hours to report completed tasks. Are you sure that Network Activity is enabled? If you click 'update' to report them manually, BOINC temporarily opens the network to comply with your request, but them shuts it off again.

Hellsheep try this in a cc_config file


<cc_config>
<options>
<report_results_immediately>1</report_results_immediately>
</options>
</cc_config>

should help

See Message 993241 by Aurora Borealis:

Boinc uploads the results immediately on completion if the Internet is available. It tries to bundle the actual reporting of completed work to ease the load on the server. Accessing the database to report a group of results only adds a small percentage of overhead more than an individual report. Boinc also ensures that work is not reported late by following a set of reporting rules as previously posted by JM7

BOINC returns work to a project at the first of:

1) 24 hours before deadline.
2) Connect Every X before deadline.
3) 24 hours after completion.
4) 60 seconds after the completion of upload if upload completes after any of 1 to 3.
5) On a work request to that project.
6) With any other reported work for that project.
7) On a trickle up to the project (CPDN only as far as I know).
8) On a trickle down request (no projects use this as far as I know).
9) On a server specified schedule (some project uses this, but not certain which).
10) On a BOINC Account Manager specified connection (only if using a BOINC Account Manager).
11) When the user pushes the update button.


Rules 3, 5 and 6 are the ones that are most commonly seen being used especially if you are attached to more than one project.


Gruß,
Gundolf

I should have checked it out further.. One of my computers ran dry over night..
..

It just took a click of the update button to get reported and re-filled.. I do not think I had anything defered/restricted.. Ahh well still about an 80% chance
of ID-10-T failure. Unless a bunch of others have similar happening.

2 of my machines reported...but my i7 timed out.

17 Jul 2010 0:29:46 UTC

I could be wrong but I think they just turned on the data.

Nooooo, wait, they can't get it going, I've still got almost two days worth of work to finish yet!!!! :-)