I searched the web. Found sudo aticonfig --initial . Got CCC to work. Will play with this a little and see how it goes. Tomorrow I will try prime grid and see if it will load. Thanks everyone for the help.

I used this way to install the Nvidia 260.xx driver when I was setting up my new machine earlier this month. I learned something about it a couple days ago: If you don't want even newer drivers to be included in updates, remove this repository after installing the driver you want or set it not to be included in updates.

I didn't think to do that, and the other day the update manager came up and I just let it do all the updates. Next thing I knew, my MilkyWay WUs were erroring out as fast as they could start. I hadn't done the necessary reboot after the update, so I did that (which got the driver and the kernel matched up again so CUDA operations work again). So I now have the Nvidia 270.xx driver. With it, MilkWay is running much faster than it did before -- but is hogging an entire CPU thread, which it didn't used to. I'll probably go back to the 260 shortly.

I added the line as was suggested, didnt work. Changed it to 30 and still didnt work. Probably have to uninstall/reinstall boinc. Will do some web searching first though.

Yep, mine is in the right place. I put 30 in there but boinc still shows no usable GPU. Might try 60 to see what happens.

Bearcat -- All that the "sleep 15" accomplishes is to delay BOINC starting up long enough after boot to give the GPU time to start up. Soin a way, it's equivalent to restarting the BOINC daemon after boot. So as a diagnostic, why don't you try manually restarting the daemon:

cd /etc/init.d
sudo ./boinc-client restart

If BOINC still doesn't find a usable GPU, then the problem isn't with the start-up script but something else -- drivers or whatever.

Kate

P.S. Remember -- Brink beat me to giving you this suggestion, so if it isn't working for you, it's his fault, not mine.