61)
Message boards :
Number crunching :
Wow! CPU WUs done in just 160 secs!
(Message 42971)
Posted 19 Oct 2010 by Crunch3r Post: This has been taken care of, the server-side database says his credit is zero - I am guessing that it is taking its time to show up where you can see it. Yeah, his account shows 0 credits now. Only thing left todo is remove the equal amount (27,635,131.00) from his team credits as well. |
62)
Message boards :
Number crunching :
Wow! CPU WUs done in just 160 secs!
(Message 42968)
Posted 19 Oct 2010 by Crunch3r Post: Just read this one here -> Another 10+ days later... still the same, nothing happened.... |
63)
Message boards :
Number crunching :
2 x GTX470 worked with milkyway 0.24 (cuda23)
(Message 42940)
Posted 18 Oct 2010 by Crunch3r Post: From where you DLed this app? That's because the app isn't available over there ;) Anyway.... to quote myself from another thread.... I'm tired of it... Apparently the app seems to work and results validate (Thanks _heinz for testing). |
64)
Message boards :
Number crunching :
GTS 450 GPU 'Computation Error'
(Message 42912)
Posted 17 Oct 2010 by Crunch3r Post: I'm tired of it... Here's the modified 0.24 MW CUDA app that should work on GTx4xx cards. http://calbe.dw70.de/milkyway/MW_0.24_CUDA.zip This is not tested (Why would i buy a slow cuda card :p ? ) and if it fails to work or does any harm to your system, YOU take full responsibility. If it does work, but somehow results fail to validate, YOU will have to take actions to immediately remove the app from your system and notify me here. |
65)
Message boards :
Number crunching :
Computation Errors
(Message 42823)
Posted 13 Oct 2010 by Crunch3r Post: Just had another comp error on the mac. Big bummer. That's quite interesting. If we take a look at one of those results : <message> <file_xfer_error> <file_name>de_14_2s_5_1054160_1286929219_0_0</file_name> <error_code>-161</error_code> </file_xfer_error> So that means that the app itself expected to have a result file <file_name>de_14_2s_5_1054160_1286929219_0_0</file_name>... Now cosidering that the new code logs it's results directly into "stderr" and doesn't create the usual result file associated with it, the boinc client now "thinks" that the app didn't finnish properly (missing result file) and reports the WU back as an tranfer error although everything finnished just fine. |
66)
Message boards :
Number crunching :
Computation Errors
(Message 42815)
Posted 13 Oct 2010 by Crunch3r Post: Maybe I missed it, but I don't see anything from the folks who run this project explaining what's going on. That's because the folks don't have a clue either, which is one major part of the issue itself... None of them is really running/testing any of their own apps. As for the latest screw up... If only one of those developers would have had a look at one of those error messages of the latest icarnation of the MW app... it would have been interesting to know why a CPU app suddenly identifies itself as a "stock_win32_gpu"... |
67)
Message boards :
Number crunching :
Wow! CPU WUs done in just 160 secs!
(Message 42466)
Posted 30 Sep 2010 by Crunch3r Post: was mistakenly using the SP app back when it could slip by. He and I have agreed to reduce his total credit to something more fair, as he was unaware that he was being dishonest. Suggestions are welcome. Just read this one here -> http://milkyway.cs.rpi.edu/milkyway/forum_thread.php?id=1305&nowrap=true#34439 It was obviously done on purpose.... Oh.. and btw, make sure you reduce that guy's team credit as well by the same amount... |
68)
Message boards :
Number crunching :
GPU detection problem with both ATI and nVidia cards installed
(Message 42262)
Posted 20 Sep 2010 by Crunch3r Post: This will sound a little drastic, however with all the hardware swopping and driver installs, there could be a real mix of issues going on - equally it could be a simple thing we are not yet aware of. I suggest you pull the NVidia card from the machine (its producing small credits only, and has gone off line), clean up the drivers, get machine working with the 5870, then move step by step from there. That pretty much sums it up. Since i've been stuck with this mess about a week ago, here's how to get both cards working again. 1. uninstall both ATI & NVIDA drivers 2. reboot and run "Driver Cleaner" -> remove all references to ATI & NVIDIA 3. shutdown and remove the NVIDIA card 4. download and install the ATI drivers & reboot 5. shutdown and insert the NVIDIA card again 6. download and install the latest NV drivers & reboot After that, both cards should be recognized by boinc again |
69)
Message boards :
Number crunching :
Getting lots of Invalid Wus - Help?
(Message 42194)
Posted 16 Sep 2010 by Crunch3r Post: Hi, this is Jed Smith, I crunch for Team Seti.Usa under the username DrPop. GPU core clock: 800 MHz, memory clock: 800 MHz Reduce the core clock to stock settings or slightly above that, say 775 MHz. Along with that, drop the memory clock to 500 Mhz. That'll save energy and your card will run quite cooler. MW doesn't depend on memory bandwidth. |
70)
Message boards :
Number crunching :
Wow! CPU WUs done in just 160 secs!
(Message 41969)
Posted 7 Sep 2010 by Crunch3r Post: I think this is a SP app build in action (again!). I was hoping that these were already banned. Unfortunately it doesn't seem so. Remember this thread -> http://milkyway.cs.rpi.edu/milkyway/forum_thread.php?id=1620&nowrap=true#37763 ???? That machine/user/team credits should have been taken care off too... But then again, it's MW so i don't expect anything here. Some random guy from the street would most likely do a better job at administrating and programming. |
71)
Message boards :
Number crunching :
GPU Requirements [OLD]
(Message 41720)
Posted 24 Aug 2010 by Crunch3r Post: Hello! You can't use that card here on MW. However you can use it here -> http://boinc.thesonntags.com/collatz/index.php or there -> http://dnetc.net |
72)
Message boards :
Number crunching :
GPU Requirements [OLD]
(Message 41604)
Posted 19 Aug 2010 by Crunch3r Post: As I've learned from gpugrid, openCL works fine on nVidia, but is not yet optimized for the ati-cards. And it runs only on 58xx cards. Here's a PDF describung what he's talking about.. (GPUGrid experiments with OpenCL... epic fail) Experiences porting from CUDA to OpenCL -> http://www.cse.scitech.ac.uk/disco/mew20/presentations/GPU_MattHarvey.pdf |
73)
Message boards :
Number crunching :
GPU Requirements [OLD]
(Message 41597)
Posted 19 Aug 2010 by Crunch3r Post: Even if on the back-end you guys are refactoring your programs to use OpenCL for better cross-hardware and cross-platform support, wouldn't it be worth it to update the old code to accept newer cards as a stop-gap solution?). I'm guessing that for "better cross-hardware and cross-platform support" you're willing to sacrifice an awfull lot of performance on all those ATI cards crunching here. Any bets on what that factor will be on 48x0 cards ? |
74)
Message boards :
Number crunching :
Aaargh! Server out of new work!
(Message 41229)
Posted 3 Aug 2010 by Crunch3r Post: I need wooooooooooooooooooooooooork! ;-)))))) |
75)
Message boards :
News :
New Website Coming Soon
(Message 40853)
Posted 8 Jul 2010 by Crunch3r Post: Somone messed around with it again... now the first "news" post is a complete mess...
besides that ...
F- epic fail |
76)
Message boards :
Number crunching :
Can't stop CPU based WU on ATi system.
(Message 40666)
Posted 25 Jun 2010 by Crunch3r Post: This is weird i see this old thread and see mine getting cpu units also even though i set on the site no cpu use allowed I could bet that those WUs only show up in boinc manager as "CPU" WUs. In fact those are beeing processed using the GPU app. When one of those tasks starts you should take a look at the taskmanager. There you'll see what's really going on. That's what was going on here as well before i fixed it. |
77)
Message boards :
Number crunching :
Unable to reattach to MW.
(Message 40652)
Posted 25 Jun 2010 by Crunch3r Post: Tried Crunch3r's idea and it didn't work for me. Sorry that it didn't work. Now it's up to the one who screwed up the front page in the first place to fix that mess ;) |
78)
Message boards :
News :
New Website Coming Soon
(Message 40650)
Posted 25 Jun 2010 by Crunch3r Post: It looks horrible, like a copy of the old apple homepage ... anyway, sinc we're now stuck with that mess (an alternative link to the 'old' homepage would have been nice), you should have used some dropdown menues like Docking@homes uses them (http://docking.cis.udel.edu/) Now let's get to the part where you screwed up even worse .... people are unable to attach to milkyway because of the new homepage... Here's why ---> http://milkyway.cs.rpi.edu/milkyway/forum_thread.php?id=1819&nowrap=true#40649 |
79)
Message boards :
Number crunching :
Unable to reattach to MW.
(Message 40649)
Posted 25 Jun 2010 by Crunch3r Post: I was hoping the server was going slow, but here we are this morning: Until the frontpage is restored to what it was before that design fiasco took place, you won't be able to attach again.... The frontpage/master url (index.php) is what the boinc client parses to get the scheduler url... Here's a sample of a proper index.php <!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd"><html> here's a possible fix that might work(untested). Shutdown boinc completely and open the file "master_milkyway.cs.rpi.edu_milkyway.xml" (boinc data directory) copy and paste <!-- <scheduler>http://milkyway.rpi.edu/cgi/cgi</scheduler>--> <link rel="boinc_scheduler" href="http://milkyway.rpi.edu/cgi/cgi"> between <head><title>MilkyWay@home</title> ....... <link rel=stylesheet type=text/css href=white.css> It should look like this:
save the file and restart boinc. |
80)
Message boards :
Number crunching :
v0.23 performance drop?
(Message 39702)
Posted 14 May 2010 by Crunch3r Post: Tested on 6.10.21/.51/.52 That seems to be a driver issue. I've experienced something similar with Cat 10.3 and 10.4 here. Reverting back to 10.2 solved the problem. |
©2024 Astroinformatics Group