| Index | Recent Threads | Unanswered Threads | Who's Active | Guidelines | Search |
 |
World Community Grid Forums
Category: Support
Forum: GPU Support Forum
Thread: Application uses missing NVIDIA GPU Message |
| No member browsing this thread |
|
Thread Status: Active Total posts in this thread: 9
|
|
| Author |
|
|
wplachy
Senior Cruncher Joined: Sep 4, 2007 Post Count: 423 Status: Offline |
I changed the Display adaptor in a PC from a NVidia GT 460 to a ATI 6770. At startup the message:
----------------------------------------World Community Grid Application uses missing NVIDIA GPU is displayed 3 times in the event log. The client does identify the ATI card but is thinks its a HD5700. How do I remove the old NVidia card for this device from the WCG info that is triggering the message? OS: Win 7 64 Client: 6.10.58 Startup Log: 9/25/2012 3:22:20 PM Starting BOINC client version 6.10.58 for windows_x86_64 9/25/2012 3:22:20 PM log flags: file_xfer, sched_ops, task, sched_op_debug 9/25/2012 3:22:20 PM Libraries: libcurl/7.19.7 OpenSSL/0.9.8l zlib/1.2.3 9/25/2012 3:22:20 PM Data directory: E:\WCG\Data 9/25/2012 3:22:20 PM Running under account xxxxxx 9/25/2012 3:22:20 PM Processor: 8 GenuineIntel Intel(R) Core(TM) i7-2600K CPU @ 3.40GHz [Family 6 Model 42 Stepping 7] 9/25/2012 3:22:20 PM Processor: 256.00 KB cache 9/25/2012 3:22:20 PM Processor features: fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss htt tm pni ssse3 cx16 sse4_1 sse4_2 nx lm vmx tm2 popcnt aes pbe 9/25/2012 3:22:20 PM OS: Microsoft Windows 7: x64 Edition, Service Pack 1, (06.01.7601.00) 9/25/2012 3:22:20 PM Memory: 15.98 GB physical, 31.95 GB virtual 9/25/2012 3:22:20 PM Disk: 76.69 GB total, 75.79 GB free 9/25/2012 3:22:20 PM Local time is UTC -5 hours 9/25/2012 3:22:20 PM ATI GPU 0: ATI Radeon HD5700 series (Juniper) (CAL version 1.4.1741, 1024MB, 1280 GFLOPS peak) 9/25/2012 3:22:20 PM World Community Grid Application uses missing NVIDIA GPU 9/25/2012 3:22:20 PM World Community Grid Application uses missing NVIDIA GPU 9/25/2012 3:22:20 PM World Community Grid Application uses missing NVIDIA GPU 9/25/2012 3:22:21 PM World Community Grid URL http://www.worldcommunitygrid.org/; Computer ID 9999999; resource share 100 9/25/2012 3:22:21 PM World Community Grid General prefs: from World Community Grid (last modified 22-Sep-2012 21:30:15) 9/25/2012 3:22:21 PM World Community Grid Computer location: work 9/25/2012 3:22:21 PM General prefs: using separate prefs for work 9/25/2012 3:22:21 PM Preferences: 9/25/2012 3:22:21 PM max memory usage when active: 14724.67MB 9/25/2012 3:22:21 PM max memory usage when idle: 14724.67MB 9/25/2012 3:22:21 PM max disk usage: 69.02GB 9/25/2012 3:22:21 PM don't use GPU while active 9/25/2012 3:22:21 PM (to change preferences, visit the web site of an attached project, or select Preferences in the Manager) 9/25/2012 3:22:21 PM Not using a proxy 9/25/2012 3:22:21 PM Suspending computation - initial delay
Bill P
 |
||
|
|
Ingleside
Veteran Cruncher Norway Joined: Nov 19, 2005 Post Count: 974 Status: Offline Project Badges: 
|
I changed the Display adaptor in a PC from a NVidia GT 460 to a ATI 6770. At startup the message: World Community Grid Application uses missing NVIDIA GPU is displayed 3 times in the event log. The client does identify the ATI card but is thinks its a HD5700. How do I remove the old NVidia card for this device from the WCG info that is triggering the message? OS: Win 7 64 Client: 6.10.58 Probably the only way to remove the message is to reset WCG. You can either choose to set "no new work", for so finishing all WCG-work, reporting it & resetting. Or, you can report all finished work, for so resetting and in the process lose all in-progress work. As for not correctly detecting your Ati-6770, this is because your BOINC-client is too old. v6.10.58 was released in July 2010, while Ati-6770 wasn't released before in April 2011. To correctly detect your card, at this time it's probably best to upgrade to v7.0.36, even this version is currently in testing.  "I make so many mistakes. But then just think of all the mistakes I don't make, although I might." |
||
|
|
wplachy
Senior Cruncher Joined: Sep 4, 2007 Post Count: 423 Status: Offline |
Thank you for the response. I assume by resetting you mean to detach/attach to WCG?
----------------------------------------I have 7.0.36 running on one Linux box and am "fighting" with the new cache treatment so I'll wait a bit before upgrading. Since it's identifing the GPU as one that supports the WCG GPU work I think it should be fine until the upgrade. Guess I'll find out on the next GPU WU release  Thank you again!
Bill P
|
||
|
|
Ingleside
Veteran Cruncher Norway Joined: Nov 19, 2005 Post Count: 974 Status: Offline Project Badges:
|
Thank you for the response. I assume by resetting you mean to detach/attach to WCG? While detach & re-attach also will work, "Reset project" is a separate choise, the one listed above "detach" in the BOINC Manager's advanced view. "I make so many mistakes. But then just think of all the mistakes I don't make, although I might." [Edit 1 times, last edit by Ingleside at Sep 25, 2012 9:36:13 PM] |
||
|
|
nanoprobe
Master Cruncher Classified Joined: Aug 29, 2008 Post Count: 2998 Status: Offline Project Badges: 
|
Bill, if you installed the ATI card into the same slot that held the Nvidia card you'll probably have to uninstall the Nvidia drivers and reinstall the ATI drivers again to get it to work like it should. This is an Nvidia problem.
----------------------------------------As mentioned before you should update your BOINC client to the latest version but not until you finish all the tasks in you cache. The will error out on a version 7 if you don't. Uninstalling the 6 version before installing a 7 version is also a must.
In 1969 I took an oath to defend and protect the U S Constitution against all enemies, both foreign and Domestic. There was no expiration date.
----------------------------------------  [Edit 2 times, last edit by nanoprobe at Sep 25, 2012 11:17:28 PM] |
||
|
|
nanoprobe
Master Cruncher Classified Joined: Aug 29, 2008 Post Count: 2998 Status: Offline Project Badges:
|
Thank you for the response. I assume by resetting you mean to detach/attach to WCG? I have 7.0.36 running on one Linux box and am "fighting" with the new cache treatment so I'll wait a bit before upgrading. Since it's identifing the GPU as one that supports the WCG GPU work I think it should be fine until the upgrade. Guess I'll find out on the next GPU WU release Thank you again! The new cache settings can be testy. The best solution I've found is to set your minimum work buffer higher than your max additional work buffer. I know that sounds backwards but it does seem to work. Some of my settings are .25/.10. Some are .05/.02. Some are 2.0/1.0. Play with it and see what works best for you.
In 1969 I took an oath to defend and protect the U S Constitution against all enemies, both foreign and Domestic. There was no expiration date.
|
||
|
|
wplachy
Senior Cruncher Joined: Sep 4, 2007 Post Count: 423 Status: Offline |
While detach & re-attach also will work, "Reset project" is a separate choise, the one listed above "detach" in the BOINC Manager's advanced view. Thank you! One would think after 5 years of using this thing I would know what I'm doing, oh well, live and learn  Bill, if you installed the ATI card into the same slot that held the Nvidia card you'll probably have to uninstall the Nvidia drivers and reinstall the ATI drivers again to get it to work like it should. This is an Nvidia problem. As mentioned before you should update your BOINC client to the latest version but not until you finish all the tasks in you cache. The will error out on a version 7 if you don't. Uninstalling the 6 version before installing a 7 version is also a must. B4 replacing the NVidia with the ATI I uninstalled all the NVidia drivers and uninstalled the card in Device Manager. I did install the ATI card in the same slot and windows picked it up as a generic VGA card. I then loaded the current ATI drivers. All this was done with the client stopped (I have it set to require a manual start rather than as a service). I knew about the 6->7 upgrade losing WUs, I seldom make any changes to BOINC without completing and reporting everything in the cache. I didn't do that for the card change because the PC was running GFAM tasks and they wouldn't finish until long after my bed time (us old folks need their rest u know  )The new cache settings can be testy. The best solution I've found is to set your minimum work buffer higher than your max additional work buffer. I know that sounds backwards but it does seem to work. Some of my settings are .25/.10. Some are .05/.02. Some are 2.0/1.0. Play with it and see what works best for you. I haven't tried that approach but will shorty (which makes it even more confusing  )Thanks for the tips, seems I owe you both at least a few cool ones for your help  Edit: finger checks
Bill P
----------------------------------------[Edit 1 times, last edit by wplachy at Sep 26, 2012 2:39:03 AM] |
||
|
|
Former Member
Cruncher Joined: May 22, 2018 Post Count: 0 Status: Offline |
[OT]There's a draft FAQ in the BOINC support forum how MinB and MaxAB work with some clarifying discussion following that http://www.worldcommunitygrid.org/forums/wcg/viewthread_thread,32530 . The essence is, MaxAB does not do anything until the cache drops below the MinB level. At that time the client asks for work to the tune of getting back to at least MinB *plus* the size of MaxAB [which is truly *additional*]. Since WCG only gives 30 units max per call, the first fetch that lifts a device over the MinB setting ends any further work requests i.e. you could have the full MaxAB filled or just a portion. Fortunately most tasks at WCG are rather sizy so you get a good chunk extra, but if doing HCC or CFSW only, 30 on an octo means 4 hours max at best over the minimum buffer level. So how I run this: MinB 1.5 days, MaxAB 0.00 which leads to continuous backfilling [every time the client drops below the MinB setting], if connection is allowed, me being on a "during daytime only" internet BOINC scheduling. That leads in the morning when 10-11 hours is reported off 8 cores to big work requests [in seconds], to get back to the MinB setting [/OT]
----------------------------------------[Edit 1 times, last edit by Former Member at Sep 26, 2012 8:56:40 AM] |
||
|
|
Ingleside
Veteran Cruncher Norway Joined: Nov 19, 2005 Post Count: 974 Status: Offline Project Badges:
|
As mentioned before you should update your BOINC client to the latest version but not until you finish all the tasks in you cache. The will error out on a version 7 if you don't. Uninstalling the 6 version before installing a 7 version is also a must. Upgrading to v7 won't lose any work (*), it's by going from v7 to v6 you'll lose all work on client. Uninstalling v6 shouldn't be neccessary either, this is done automatically as part of the upgrade-process. For anyone running multiple BOINC-projects, the upgrade will reset all debts to other projects, since v7 uses a different method to balance resources between BOINC-projects. Where's also the change of cache-behaviour, where "additional..." normally isn't fulfilled. But, in the last couple clients, if does a scheduler-request for any reason (like trying to get GPU-work), if "additional..." isn't full the scheduler-request also includes asking for CPU-work. (*) v7 includes changes to how files are signed. If a project haven't either disabled upload-signing or started using the new signing-format, the work will error-out on upload. But, this means ALL work, also new work downloaded by v7. I'm not aware of any BOINC-project what haven't taken care of this problem by now. "I make so many mistakes. But then just think of all the mistakes I don't make, although I might." |
||
|
|
|