Guess we should have asked earlier, but which GPU project are you doing?
Guess we should have asked earlier, but which GPU project are you doing?
Joined Original Message Board: Fri Jan 27, 2006 1:47 pm, Currently with 11298 Posts
If it ain't crunch'n, unplug it!
I have it set to use 100% of the processoers 100% of the time.
It's on Dirt with the same preferences for the machine that is running both gpus.
Which is making this real strange. Other that different hardware the machines are identically set up, save for the 64 vs 32. If I didn't have to deal with comcast adding things to my bill, my lost amazon package, my broken windshield, flat tire, and burned out headlight, and now 6 inches of snow I would have time to switch the cards between the machines to replicate this.
Last edited by krazy k; 04-11-13 at 11:27 AM.
Just out of curiosity have you gone to the advanced tab and told BOINC to "read config file?
RETIRED. NO JOB. NO MONEY. NO WORRIES!
Crunched SETI Classic to the end.
SETI@home classic workunits
17,550
SETI@home classic CPU time 86,861 hours
I do that after every change but haven't seen anything different. I've restarted BOINC quite a few times too; just to be sure. I could fire up the VPN and give you guys a chance to look at it yourselves. I'll send some beer to whomever can figure it out.
Other projects are also only seeing just the one. It has to be something so easy that I'm missing. Maybe I'll try that E=MCHammered thing tonight.
Last edited by krazy k; 04-11-13 at 12:35 PM.
You aren't using the built in windows version of VNC are you? That is not compatible with BOINC GPU crunching. You have to use a real VNC client like ultravnc, or a proprietary version like TeamViewer.
Question:
What does it say at the top of the Event Log about the GPU/S? Does it only show the one or give any errors?
And does it say "Config: use all coprocessors"?
BOINC Sees it - BOINC DOES it!
Yup.
Capture.JPG