Posts by STE\/E

21) Message boards : Number crunching : GPU Requirements [OLD] (Message 44643) Posted 4 Dec 2010 by STE\/E Post: Okay Thanks, I didn't really think it would work anyway but tried them for the Heck of it, guess I'll have to get some cards that work ... lol
22) Message boards : Number crunching : GPU Requirements [OLD] (Message 44639) Posted 3 Dec 2010 by STE\/E Post: I got this when I tried to run the NVIDIA GPU Wu's on my M8700 GT ??? stderr out <core_client_version>6.10.58</core_client_version> <![CDATA[ <message> Incorrect function. (0x1) - exit code 1 (0x1) </message> <stderr_txt> <search_application> milkywayathome separation 0.48 Windows x86 double OpenCL </search_application> Found 1 platforms Platform 0 information: Platform name: NVIDIA CUDA Platform version: OpenCL 1.0 CUDA 3.2.1 Platform vendor: Platform profile: Platform extensions: cl_khr_byte_addressable_store cl_khr_icd cl_khr_gl_sharing cl_nv_d3d9_sharing cl_nv_d3d10_sharing cl_khr_d3d10_sharing cl_nv_d3d11_sharing cl_nv_compiler_options cl_nv_device_attribute_query cl_nv_pragma_unroll Using device 0 on platform 0 Found 1 CL devices Device GeForce 8700M GT (NVIDIA Corporation:0x10de) Type: CL_DEVICE_TYPE_GPU Driver version: 260.99 Version: OpenCL 1.0 CUDA Compute capability: 1.1 Little endian: CL_TRUE Error correction: CL_FALSE Image support: CL_TRUE Address bits: 32 Max compute units: 4 Clock frequency: 1250 Mhz Global mem size: 519634944 Max mem alloc: 134217728 Global mem cache: 0 Cacheline size: 0 Local mem type: CL_LOCAL Local mem size: 16384 Max const args: 9 Max const buf size: 65536 Max parameter size: 4352 Max work group size: 512 Max work item dim: 3 Max work item sizes: { 512, 512, 64 } Mem base addr align: 2048 Min type align size: 128 Timer resolution: 1000 ns Double extension: MW_NONE_DOUBLE Extensions: cl_khr_byte_addressable_store cl_khr_icd cl_khr_gl_sharing cl_nv_d3d9_sharing cl_nv_d3d10_sharing cl_khr_d3d10_sharing cl_nv_d3d11_sharing cl_nv_compiler_options cl_nv_device_attribute_query cl_nv_pragma_unroll cl_khr_global_int32_base_atomics cl_khr_global_int32_extended_atomics Compiler flags: -cl-mad-enable -cl-no-signed-zeros -cl-strict-aliasing -cl-finite-math-only -DUSE_CL_MATH_TYPES=0 -DUSE_MAD=0 -DUSE_FMA=0 -cl-nv-verbose -DDOUBLEPREC=1 -DMILKYWAY_MATH_COMPILATION -DNSTREAM=3 -DFAST_H_PROB=1 -DAUX_BG_PROFILE=0 -DUSE_IMAGES=1 -DI_DONT_KNOW_WHY_THIS_DOESNT_WORK_HERE=0 Build status: CL_BUILD_ERROR Build log: ptxas application ptx input, line 58; error : Instruction 'ld' requires SM 1.3 or higher, or map_f64_to_f32 directive ptxas application ptx input, line 74; error : Instruction 'ld' requires SM 1.3 or higher, or map_f64_to_f32 directive ptxas application ptx input, line 75; error : Instruction 'ld' requires SM 1.3 or higher, or map_f64_to_f32 directive ptxas application ptx input, line 177; error : Instruction 'ld' requires SM 1.3 or higher, or map_f64_to_f32 directive ptxas application ptx input, line 178; error : Instruction 'ld' requires SM 1.3 or higher, or map_f64_to_f32 directive ptxas application ptx input, line 179; error : Instruction 'ld' requires SM 1.3 or higher, or map_f64_to_f32 directive ptxas application ptx input, line 180; error : Instruction 'ld' requires SM 1.3 or higher, or map_f64_to_f32 directive ptxas application ptx input, line 181; error : Instruction 'ld' requires SM 1.3 or higher, or map_f64_to_f32 directive ptxas application ptx input, line 182; error : Instruction 'ld' requires SM 1.3 or higher, or map_f64_to_f32 directive ptxas application ptx input, line 183; error : Instruction 'ld' requires SM 1.3 or higher, or map_f64_to_f32 directive ptxas application ptx input, line 184; error : Instruction 'ld' requires SM 1.3 or higher, or map_f64_to_f32 directive ptxas application ptx input, line 185; error : Instruction 'ld' requires SM 1.3 or higher, or map_f64_to_f32 directive ptxas application ptx input, line 198; error : Instruction 'ld' requires SM 1.3 or higher, or map_f64_to_f32 directive ptxas application ptx input, line 199; error : Instruction 'ld' requires SM 1.3 or higher, or map_f64_to_f32 directive ptxas application ptx input, line 200; error : Instruction 'ld' requires SM 1.3 or higher, or map_f64_to_f32 directive ptxas application ptx input, line 201; error : Instruction 'mov' requires SM 1.3 or higher, or map_f64_to_f32 directive ptxas application ptx input, line 211; error : Instruction 'ld' requires SM 1.3 or higher, or map_f64_to_f32 directive ptxas application ptx input, line 212; error : Instruction 'ld' requires SM 1.3 or higher, or map_f64_to_f32 directive ptxas application ptx input, line 213; error : Instruction 'ld' requires SM 1.3 or higher, or map_f64_to_f32 directive ptxas application ptx input, line 214; error : Instruction 'ld' requires SM 1.3 or higher, or map_f64_to_f32 directive ptxas application ptx input, line 215; error : Instruction 'ld' requires SM 1.3 or higher, or map_f64_to_f32 directive ptxas application ptx input, line 216; error : Instruction 'ld' requires SM 1.3 or higher, or map_f64_to_f32 directive ptxas application ptx input, line 219; error : Instruction 'mov' requires SM 1.3 or higher, or map_f64_to_f32 directive ptxas application ptx input, line 220; error : Instruction 'mov' requires SM 1.3 or higher, or map_f64_to_f32 directive ptxas application ptx input, line 221; error : Instruction 'mov' requires SM 1.3 or higher, or map_f64_to_f32 directive ptxas application ptx input, line 230; error : Instruction 'mul' requires SM 1.3 or higher, or map_f64_to_f32 directive ptxas application ptx input, line 231; error : Instruction 'mul' requires SM 1.3 or higher, or map_f64_to_f32 directive ptxas application ptx input, line 232; error : Instruction 'mul' requires SM 1.3 or higher, or map_f64_to_f32 directive ptxas application ptx input, line 233; error : Instruction 'mul' requires SM 1.3 or higher, or map_f64_to_f32 directive ptxas application ptx input, line 234; error : Instruction 'add' requires SM 1.3 or higher, or map_f64_to_f32 directive ptxas application ptx input, line 235; error : Instruction 'mul' requires SM 1.3 or higher, or map_f64_to_f32 directive ptxas application ptx input, line 236; error : Instruction 'mul' requires SM 1.3 or higher, or map_f64_to_f32 directive ptxas application ptx input, line 237; error : Instruction 'mul' requires SM 1.3 or higher, or map_f64_to_f32 directive ptxas application ptx input, line 238; error : Instruction 'add' requires SM 1.3 or higher, clBuildProgram: Build failure: CL_INVALID_BINARY Error creating kernel 'mu_sum_kernel': CL_INVALID_PROGRAM_EXECUTABLE Error building program from source: CL_INVALID_PROGRAM_EXECUTABLE Error creating program from source: CL_INVALID_PROGRAM_EXECUTABLE Failed to setup up CL 15:00:59 (3704): called boinc_finish </stderr_txt>
23) Message boards : Application Code Discussion : compatible units gtx 4xx... (Message 44112) Posted 23 Nov 2010 by STE\/E Post: You were getting that message because there wasn't any GPU WUs available at the time of the download request, just the pesky N-Body WUs were available. I get that message quite a bit, also. I do not run Milkyway on my CPU, just the GPUs. -Mike Same here Mike, I don't run any CPU Tasks at the GPU Projects ...
24) Message boards : Number crunching : GTX 580 (Message 43997) Posted 20 Nov 2010 by STE\/E Post: I bought the 580 Cards for GPU Grid & Possibly PrimeGrid on the TPS Wu's and any other Wu's they can get to run with the GTX 4xx & 5xx Series of Cards. I expect the 6970 will run circles around the 580 at this Project and Collatz & DNET. The 580's weren't really built for those Projects but will run them, at least the Milkyway & Collatz Projects as I have run them with the GTX 460's already.
25) Message boards : Number crunching : GTX 580 (Message 43992) Posted 20 Nov 2010 by STE\/E Post: Fired up a couple of EVGA GTX 580 Black Ops last night ... :) I didn't really buy them for this Project but thought I'd see what they can do here anyway ...
26) Message boards : Application Code Discussion : compatible units gtx 4xx... (Message 43947) Posted 18 Nov 2010 by STE\/E Post: Of course, you could just download the optimized app for "Fermi" cards. The url for it can be found in this thread. http://milkyway.cs.rpi.edu/milkyway/forum_thread.php?id=1297 I'm trying that App on 1 of my GTX 460's and I keep getting >>> 11/18/2010 4:59:37 AM \| Milkyway@home \| Message from Milkyway@home: Your app_info.xml file doesn't have a version of MilkyWay@Home N-Body Simulation. <<< What do I have to do now to get the Wu's to run ... Thanks EDIT: Seems to be working now, around 10 Mins, slow but it's working anyway & I didn't expect any speed out of it when I bought it ...
27) Message boards : Number crunching : Lot's of Invalid Wu's ? (Message 41805) Posted 28 Aug 2010 by STE\/E Post: Seems like I'm getting a lot of Invalid Wu's, over 100 since starting back running here yesterday, I never used to get any so don't know what the problem could be now other than the Validator is messed up ??? EDIT: Looked at my Box's and it seems most of the Invalids are coming off 2 Box's so I'll take a look at them, don't get any at DNET or Collatz with those 2 Box's so don't know why they would get Invalids here ?
28) Message boards : Cafe MilkyWay : Milestones III (Message 40061) Posted 30 May 2010 by STE\/E Post: I keep having a continual New Message Notification in my Account on the Milestone III Thread but when I Click on it I get this > Unable to handle request This thread has been hidden for administrative purposes. I'm assuming it's on the Old Milestone III Thread Blurf hid & I was Subscribed to so am I now going to have this Notification Message Forever or what ...
29) Message boards : Number crunching : I have no idea what caused this (Message 39984) Posted 27 May 2010 by STE\/E Post: Poorboy said : Milkyway didn't harm your Fan, you harmed your Fan running Milkyway 24/7 if that's what your running it ... If I remember correctly my 48xx Cards showed a RPM, I know earlier ATI Cards I had showed an RPM & my 58xx Cards show some RPM so I don't see why the 48xx Series of Cards wouldn't. He can't just look & see if the Fan is turning or stick his finger on the center of the Fan to feel if it's turning, I do that all the time. With the Temp's at 100c I would say the card is no good, my Box's will Reboot if the Video Card Temp reaches around 100c ... Well thats serius, because actually I was looking around before I started crouch to milky way, and the staff says they didnt heard ever that any boinc project caused damage to the hardware. Well I still think that my fan should not give away so soon, I've joined on feb 10, and others running more hardly without problems. Anyway, I only remember 1 week contunus crounching, other times I suspended the project time by time. It's not necessarily the Projects that Harm you Hardware, it's running your Hardware 24/7 that eventually finds any weak links in your Hardware. All My Video Cards are the 58xx Type, I have had to RMA 6 of them already in less than 7 Month's for Fan Failure. I don't blame any of the GPU Projects for the Fan's failing, I just consider it part of running the projects 24/7. Apparently the Fan's on the 58xx Series Cards is the weak Link ...
30) Message boards : Number crunching : I have no idea what caused this (Message 39967) Posted 26 May 2010 by STE\/E Post: They will do that, I've had to RMA 5 58xx Cards already for Fan Noise or Failure & they were still producing good results up to the Point they Failed completely. I've replaced the Fan on some older ATI & NVIDIA Cards but have never attempted it on the 48xx or 58xx Cards, not even sure you can get a Fan for them. He never did say what Brand or Model of Card he has, if he does some Goggling he should be able to tell if the Fan is replaceable. If he's the Original Owner it could be under Warranty yet as long as he has the Sales Slip yet. They almost always require a Sales Slip to prove your the original owner of the Card except for XFX Cards which have a Double Lifetime Warranty. An open face design probably would be easier to replace than a closed face one. I know they make aftermarkets coolers for the 48xx & 58xx Cards so he should be able to come up with something to fix it if it is the Fan gone bad ...
31) Message boards : Number crunching : I have no idea what caused this (Message 39964) Posted 26 May 2010 by STE\/E Post: Milkyway didn't harm your Fan, you harmed your Fan running Milkyway 24/7 if that's what your running it ... If I remember correctly my 48xx Cards showed a RPM, I know earlier ATI Cards I had showed an RPM & my 58xx Cards show some RPM so I don't see why the 48xx Series of Cards wouldn't. He can't just look & see if the Fan is turning or stick his finger on the center of the Fan to feel if it's turning, I do that all the time. With the Temp's at 100c I would say the card is no good, my Box's will Reboot if the Video Card Temp reaches around 100c ...
32) Message boards : Cafe MilkyWay : Milestones III (Message 39924) Posted 25 May 2010 by STE\/E Post: Yay You GG ... :)
33) Message boards : Cafe MilkyWay : Milestones III (Message 39864) Posted 20 May 2010 by STE\/E Post: Congratz Pete, went over 500,000,000 myself last night ...
34) Message boards : Number crunching : PCI Express Configuration Distribution (Message 39853) Posted 20 May 2010 by STE\/E Post: I'm running 1 Box that has a 1x PCI Slot on it or at last that's what GPUz Reports with no problems Arif. It runs the Wu's just as fast as a 16 Slot does ...
35) Message boards : Number crunching : 2x 5970 CrossfireX Stuck wus (Message 39795) Posted 18 May 2010 by STE\/E Post: So if I was to use a dummy plug with my 5970 and 5870 I would just connect one card and put a dummy plug on the other? I don't need a dummy plug on the second DVI connector of 5970 as well to stop the second core going to sleep? Seems to me when I was running Dual Sapphire 4850 X2 Cards together I had Attach one card to a Monitor & then had to run 3 Dummy Plugs to get all 4 Cores to work. I also had to use the CCC Display Manager to Enable the 3 Dummy Plugged Cores.
36) Message boards : Number crunching : Server Clint Software ? (Message 39347) Posted 1 May 2010 by STE\/E Post: As The Gas Giant said ...
37) Message boards : Number crunching : Server Clint Software ? (Message 39343) Posted 1 May 2010 by STE\/E Post: I think the Server Client Software needs Updating, when I use BAM to set the Resources Share to 0.000 BAM resets the Use CPU & Use NVIDIA Card to Yes from the No I had it at. Then When I try to Set the Resource Share to 0.000 here at the Project it won't do it, it keeps Resetting it to the Default 100 from the 0.000 I set it to. Collatz had this same Problem but they Updated the Server Client Software (or that's what I was lead to believe they did) & now the Collatz Project can be set to 0.000 right at the Project ... Thank's
38) Message boards : Number crunching : Slower CPUs (Message 38588) Posted 11 Apr 2010 by STE\/E Post: Reporting deadlines should never be an issue here for 3 reasons - 1. The project on;y issues a maximum of 6 WUs per core as your cache; 2. The cache setting for BOINC Manager should be set to <the 3 day reporting deadline; 3. The time taken to crunch a WU will determine the cache BNM allows, so slower CPU only rigs are catered for. No problems then! Unless your trying to run to many Project's on a slower PC & your Contact time is set to high then there can be problems ...
39) Message boards : Number crunching : Hardware Poll (Message 38505) Posted 9 Apr 2010 by STE\/E Post: Running Various Versions of Gigabyte DQ6's across my Pharm other than 1 ASUS DH7 Deluxe which is about the worst Motherboard I've ever owned ...
40) Message boards : Number crunching : Marked as Invalid? (Part 2) (Message 38492) Posted 9 Apr 2010 by STE\/E Post: The server is down to < 3% invalids, so I think that means the ones flagged as invalid are actually invalid now. Actually the vast majority of invalids still being reported against my HD5870 are due to the earlier buggy versions of anonymous platforms out-voting it. I've notified 12 owners now by PM but only about 4 of them that I know of have upgraded their app to 0.23. The Project just needs to stop sending work to any Host with less than v0.23 Application and I bet you would see them Update in a Jiffy ....

Previous 20 · Next 20