Server stopped sending for 7970
Message boards :
Number crunching :
Server stopped sending for 7970
Message board moderation
| Author | Message |
|---|---|
 Send message Joined: 2 May 11 Posts: 4 Credit: 1,038,974,772 RAC: 679,848 
|
Was getting lot's of work for my 7970 (Link) then it suddenly dried up. I've tried resetting the project, restarting BOINC and rebooting the system. Still no work. 2/26/2014 5:51:06 PM - Starting BOINC client version 7.0.64 for windows_x86_64 2/26/2014 5:51:06 PM - log flags: file_xfer, sched_ops, task 2/26/2014 5:51:06 PM - Libraries: libcurl/7.25.0 OpenSSL/1.0.1 zlib/1.2.6 2/26/2014 5:51:06 PM - Data directory: C:\Programdata\BOINC 2/26/2014 5:51:06 PM - Running under account ********** 2/26/2014 5:51:06 PM - Processor: 8 GenuineIntel Intel(R) Core(TM) i7 CPU 860 @ 2.80GHz [Family 6 Model 30 Stepping 5] 2/26/2014 5:51:06 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 popcnt syscall nx lm vmx smx tm2 pbe 2/26/2014 5:51:06 PM - OS: Microsoft Windows 7: Ultimate x64 Edition, (06.01.7600.00) 2/26/2014 5:51:06 PM - Memory: 4.00 GB physical, 7.99 GB virtual 2/26/2014 5:51:06 PM - Disk: 41.26 GB total, 35.50 GB free 2/26/2014 5:51:06 PM - Local time is UTC -5 hours 2/26/2014 5:51:06 PM - VirtualBox version: 4.2.12 2/26/2014 5:51:06 PM - CUDA: NVIDIA GPU 0: GeForce GTX 570 (driver version 334.89, CUDA version 6.0, compute capability 2.0, 1280MB, 1143MB available, 1530 GFLOPS peak) 2/26/2014 5:51:06 PM - CAL: ATI GPU 0: AMD Radeon HD 7870/7950/7970 series (Tahiti) (CAL version 1.4.1848, 3072MB, 3032MB available, 10240 GFLOPS peak) 2/26/2014 5:51:06 PM - OpenCL: NVIDIA GPU 0: GeForce GTX 570 (driver version 334.89, device version OpenCL 1.1 CUDA, 1280MB, 1143MB available, 1530 GFLOPS peak) 2/26/2014 5:51:06 PM - OpenCL: AMD/ATI GPU 0: AMD Radeon HD 7870/7950/7970 series (Tahiti) (driver version 1348.5 (VM), device version OpenCL 1.2 AMD-APP (1348.5), 3072MB, 3032MB available, 10240 GFLOPS peak) : : : Moo! Wrapper - 2/26/2014 6:36:18 PM - Requesting new tasks for ATI Moo! Wrapper - 2/26/2014 6:36:20 PM - Scheduler request completed: got 0 new tasks Moo! Wrapper - 2/26/2014 6:37:13 PM - update requested by user Moo! Wrapper - 2/26/2014 6:37:15 PM - Sending scheduler request: Requested by user. Moo! Wrapper - 2/26/2014 6:37:15 PM - Requesting new tasks for ATI Moo! Wrapper - 2/26/2014 6:37:17 PM - Scheduler request completed: got 0 new tasks --->>> HELP! <<<--- 
ID: 5923 · Rating: 0 · rate:
 /   |
 Send message Joined: 22 Jun 11 Posts: 2080 Credit: 1,826,336,240 RAC: 414 |
Was getting lot's of work for my 7970 (Link) then it suddenly dried up. I've tried resetting the project, restarting BOINC and rebooting the system. Still no work. This part would bother me: 2/26/2014 5:51:06 PM - OpenCL: NVIDIA GPU 0: GeForce GTX 570 2/26/2014 5:51:06 PM - OpenCL: AMD/ATI GPU 0: AMD Radeon HD 7870/7950/7970 They are BOTH being seen as gpu #0, one should be #0 and one should be #1. Do you have a 2nd monitor close enough to plug it into the 2nd gpu when the pc starts up, so both have screens attached to them? If not do you have a "dummy plug" on one of them? Windows has a bad habit sometimes of not enabling resources if it thinks they aren't going to be used, ie no screen connected to a gpu. ID: 5924 · Rating: 0 · rate:
/ |
 Teemu MannermaaSend message Joined: 20 Apr 11 Posts: 388 Credit: 822,356,221 RAC: 0 |
Was getting lot's of work for my 7970 (Link) then it suddenly dried up. I've tried resetting the project, restarting BOINC and rebooting the system. Still no work. Hmm, interesting, it seems to have worked for you despite the problems with Dnet Client vs. 7xxx cards. I disabled sending work to these few days ago in preparation for getting the OpenCL app out. But if some of these cards were actually working then it would explain why the key speed has been fluctuating lately. I've enabled the CAL app for this card family again. Sorry about that! -w ID: 5929 · Rating: 0 · rate:
/ |
|
Send message Joined: 13 Nov 13 Posts: 3 Credit: 173,925,466 RAC: 0 |
They are both seen as #0 and that is correct. This has been the naming convention in the new boinc managers for months. As one is an ATI and one is a nVidia the new convention is to name the cards by there make then by number, hence ATI #0 and nVidia #0. If you were to add a second , say ATI, to give three cards, then you would have ATI #0, ATI #1, nvidia #0. etc Totally messed up all my gpu exclude files when that came about as some of my systems have 3 different types of graphics adapters and 4 cards of differing abilities. ID: 5933 · Rating: 0 · rate:
/ |
|
Send message Joined: 22 Jun 11 Posts: 2080 Credit: 1,826,336,240 RAC: 414 |
They are both seen as #0 and that is correct. This has been the naming convention in the new boinc managers for months. As one is an ATI and one is a nVidia the new convention is to name the cards by there make then by number, hence ATI #0 and nVidia #0. If you were to add a second , say ATI, to give three cards, then you would have ATI #0, ATI #1, nvidia #0. etc Whew that will mess me up too, fortunately I have both of the gpu's in my dual gpu machine running the same project right now so I didn't notice it. But that is far from the normal situation for me! THANKS! ID: 5934 · Rating: 0 · rate:
/ |
Copyright © 2011-2024 Moo! Wrapper Project