Message boards :
Number crunching :
HD5870
Message board moderation
Previous · 1 · 2 · 3 · 4 · 5 · 6 · 7 · Next
Author | Message |
---|---|
Send message Joined: 26 Jun 09 Posts: 47 Credit: 276,827,695 RAC: 0 |
The 5870's run okay under Win XP64 over at Collatz, I'm running 2 of them there. But the Milkyway's won't run for me either on my 5870's, I'm running the 0.20 exe & don't really know if that's the one to be running as I haven't been paying much attention to this project lately. Maybe an upgrade on the exe would help ??? My Cards didn't Freeze but all the Wu's just erred out immediatly ... Same thing for me, 2 cards running fine on Collatz and hang up here. I may actually have to upgrade to Win 7 .... damn :( Bryan |
Send message Joined: 29 Aug 07 Posts: 486 Credit: 576,521,257 RAC: 35,227 |
The 5870's run okay under Win XP64 over at Collatz, I'm running 2 of them there. But the Milkyway's won't run for me either on my 5870's, I'm running the 0.20 exe & don't really know if that's the one to be running as I haven't been paying much attention to this project lately. Maybe an upgrade on the exe would help ??? My Cards didn't Freeze but all the Wu's just erred out immediatly ... My 5870's are sitting Idle ATM, they ran out their Collatz Wu's already and won't run the Milkyway Wu's so they may get to cool their heels until Monday morning ... PS: Bryan I got my 5870's to run the Wu's by going to the 0.20b Application so you may want to try that if you haven't already, I'm running Win XP 64-Bit ... PS2: Never mind on that Bryan, I've had countless VPU Error's & Lockups already, it's like when the 4890's came out, they run for a little bit & then you get the VPU error's or a Lockup. I've stopped running them for now. Somebody will figure out how to run them on the 5870's & Win XP 64 Bit but it's beyond my realm of intelligence to do so ... |
Send message Joined: 15 Jul 08 Posts: 383 Credit: 729,293,740 RAC: 0 |
PS2: Never mind on that Bryan, I've had countless VPU Error's & Lockups already, it's like when the 4890's came out, they run for a little bit & then you get the VPU error's or a Lockup. I've stopped running them for now. Somebody will figure out how to run them on the 5870's & Win XP 64 Bit but it's beyond my realm of intelligence to do so ... I never did get MW to work with my 4770 cards under WinXP64. They run under WinXP32 (on v9.8 no CCC, v9.9 causes far more VPU errors) but doing ANYTHING but crunching WUs on the machine when MW is running leads to VPU errors. Switched one 4770 to a hardware identical Win 7 64bit machine the day before yesterday and that's running fine so far with no VPU errors (v9.9 no CCC). Interesting side note: MW runs at about the same speed (or maybe even 1% faster) in Win7-64, but about 5% slower in Collatz with Win7. Is there perhaps a setting I need to change in Win7 for the more memory intensive Collatz? |
Send message Joined: 29 Aug 07 Posts: 81 Credit: 60,360,858 RAC: 0 |
BUMP! Any news on getting MW to run on 5870 under WinXP 64? Collatz is running superfine, so I don't think it's big thing to fix the MW ATI app. BR, |
Send message Joined: 26 Jan 09 Posts: 589 Credit: 497,834,261 RAC: 0 |
>Any news on getting MW to run on 5870 under WinXP 64? And similarly for win 7 home premium 64, for those of us too lazy to reread this [and other] threads. Something along the lines of 0. stop boinc. 1. install driver ver. x, available from <url> 2. install boinc ver. x, available from <url> 3. restart boinc 4. enjoy the incredible... Mine came with ccc9.10 installed. I copied the win64 app_info, astronomy_20, brook64 to boincdata/mw Restarted boinc, computation error, computation error, ..., CPDN crunching madly. Cheers, PeterV . |
Send message Joined: 6 Apr 08 Posts: 2018 Credit: 100,142,856 RAC: 0 |
|
Send message Joined: 26 Jan 09 Posts: 589 Credit: 497,834,261 RAC: 0 |
|
Send message Joined: 6 Apr 08 Posts: 2018 Credit: 100,142,856 RAC: 0 |
|
Send message Joined: 26 Jan 09 Posts: 589 Credit: 497,834,261 RAC: 0 |
|
Send message Joined: 18 Feb 09 Posts: 158 Credit: 110,699,054 RAC: 0 |
Weird, my 5870 is blazing MW with the default drivers from the CD. Just popped my ati app zip from the brilliantsite or whatever and atsrted up boinc 6.10.13 and ZOOOOM! On Vista Home Premium x64 here. |
Send message Joined: 26 Jan 09 Posts: 589 Credit: 497,834,261 RAC: 0 |
>weird But perhaps understandable as I did the same as you, except with boinc 6.4.5. So I went to the d-l page, got 6.10.16 [development]. Didn't work [all computation errors again] so I found the all versions page but couldn't find 6.6.13. .12 yes. .14 yes. But no .13. Obviously someone's superstitious. Better include your 'out of the box' driver versions too, as computation errors often indicate wrong ones. Also any installation instructions that aren't done by the install program. Cheers, PeterV . |
Send message Joined: 1 Mar 09 Posts: 56 Credit: 1,984,937,499 RAC: 0 |
... but couldn't find 6.6.13. .12 yes. .14 yes. But no .13... Maybe you could try 6.10.13 just after you consume cup #6. Obviously just 5 cups is insufficient stimulation :-). Better include your 'out of the box' driver versions too ... As these cards are so new, are there likely to be different packaged driver versions already? Cheers, Gary. |
Send message Joined: 26 Jan 09 Posts: 589 Credit: 497,834,261 RAC: 0 |
Yes, need more coffee. Which is why I asked for urls - if all i have to do is click on a link to get the correct file then I don't have to rely on my fading memory. Currently d/l-ing 6.10.13. The installed driver came as part of 9-10_vista64_win7_64_dd_ccc_wdm_enu-[Guru3D.com].exe, hopefully a recent version. Cheers, PeterV . |
Send message Joined: 26 Jan 09 Posts: 589 Credit: 497,834,261 RAC: 0 |
OK, next question. I installed 6.10.13. Had to reattach to projects, but miracle diablu they have put the available projects in alphabetical order, making them so much easier to find. Attached, attached, downloading... running. shut down boinc, it didn't ask if I wanted to shut down the science apps too, but I had answered yes with previous boinc installs today and hopefully it had remembered, copied the mw v2.0 [64] files over, restarted boinc. Unfortunately, in spite of the messages tab saying "ati gpu0:ati radeon hd5800 series(cypress)(cal version 1.4.467, 1024mb, 2720GFLOPS)" it then also said "requesting new tasks for cpu". So I'm now running 8 mw WUs on my cpu while my 2.7TFLOP gpu lies idle. Any ideas? Cheers, PeterV . |
Send message Joined: 26 Jan 09 Posts: 589 Credit: 497,834,261 RAC: 0 |
Anyway I worked out how to stop getting cpu tasks, which shouldn't have been a problem as I [thought I was] running Cluster's v2.0 - turn off the 'run cpu WUs' option on my home page', its so intuitively obvious when something I do way over there changes things over here. So now, instead of getting 'cpu WUs' I get none at all. Does anyone yet have an answer to my message 32661? Cheers, PeterV . |
Send message Joined: 30 Dec 07 Posts: 311 Credit: 149,490,184 RAC: 0 |
I don't know what application you are using but with a HD 5870 and Win 64 then http://www.brilliantsite.com/milkyway/win-ati-20b/ati_0.20b_win64.zip would be the easiest to use because it would not require the CAL .dll files to be copied and renamed. This zip file contains contains astronomy_0.20b_ATI_x64_ati.exe and the matching brook64.dll file. Hopefully if you try this version you will soon be able to enjoy the incredible.... Perhaps if you were previously using 8.12 drivers successfully you are not fully familiar with the extra steps that used to be necessary to get CAL 1.4 driver versions to work. It was simple enough once you had grokked the readme file but if you or Windows Update updated your driver version, then the copied and renamed files were sometimes automatically deleted. The recent v0.20b application does away with the need to copy and rename the CAL .dll files, you just choose the correct variant of v0.20b to use to suit your Catalyst driver version. A little extra information. The ATI aware BOINC versions can take a few tries before they actually download ATI work. You may have to let BOINC go through its request cycle for 5-10 minutes before it downloads anything. I allowed new tasks for MilkyWay and downloaded 48 tasks to show you an example: 24/10/2009 4:28:06 PM Milkyway@home Requesting new tasks for CPU 24/10/2009 4:28:11 PM Milkyway@home Scheduler request completed: got 0 new tasks 24/10/2009 4:29:16 PM Milkyway@home Requesting new tasks for CPU 24/10/2009 4:29:26 PM Milkyway@home Scheduler request completed: got 0 new tasks 24/10/2009 4:30:31 PM Milkyway@home Requesting new tasks for CPU 24/10/2009 4:30:56 PM Milkyway@home Scheduler request failed: Couldn't connect to server 24/10/2009 4:31:57 PM Milkyway@home Requesting new tasks for CPU and GPU 24/10/2009 4:32:07 PM Milkyway@home Scheduler request completed: got 0 new tasks 24/10/2009 4:33:12 PM Milkyway@home Requesting new tasks for GPU 24/10/2009 4:33:27 PM Milkyway@home Scheduler request completed: got 48 new tasks Also make sure that "Suspend GPU work while computer is in use?" is set to no in Computing preferences>Processor Usage or ATI tasks will go into waiting to run state if you move the mouse. Ticking "Use GPU while computer is in use" then OK in BOINC Manager > Advanced>Preferences>processor usage tab does the same thing if you prefer to do it locally. I now set my preferences locally after they were reset a number of times recently causing Collatz and MilkyWay ATI tasks to stay in waiting to run state. |
Send message Joined: 26 Jan 09 Posts: 589 Credit: 497,834,261 RAC: 0 |
I followed your instructions and after a bunch of 'couldn't connect to server's it finally did and said 'requesting cpu tasks'. Why!!! I don't want to run &*%$%**^*cpu tasks, I've got a bunch of CPDN WUs to keep my cpu happy. I want my gpu utilisation to finally get above 0% for the first time in the 25hrs I've had it. Thanks anyway, Tombei. Perhaps they'll get it sorted by boinc v10.25.0. Cheers, PeterV . |
Send message Joined: 30 Dec 07 Posts: 311 Credit: 149,490,184 RAC: 0 |
Well I don't know the reason why it still requests CPU work when you have set your preferences for GPU only, but that's the way the ATI BOINC versions currently work when requesting tasks. Very similar at Collatz ATI. Once you have the correct ATI application and your card and app_info.xml are recognised by BOINC only ATI work should be downloaded and no CPU work even though it still requests CPU work on some of the requests. I understand that when the server is overloaded here it is frustrating when you get through and it is on the CPU only request part of the cycle. Depending on how the MilkyWay server is responding at the time, then once you manage to fully download 48 ATI tasks on an i7, it gives you a chance to be assigned more work before you have completed those 48 tasks. If the server is particularly sluggish and/or only giving out the shortest tasks then you may still run out of work, but that applies to everyone to a greater or lesser degree depending on the number of CPU cores and the number and speed of the ATI card(s). Some warmer weather and the recent MilkyWay server sluggishness due to short tasks being issued influenced me to switch to Collatz for a while because I can download a larger cache of work there and leave it to run by itself without needing to check often to see if it has run out of work. It reduces the server load here and besides I like to support the other ATI project, it would be better if there were a few more of them. |
Send message Joined: 6 Apr 08 Posts: 2018 Credit: 100,142,856 RAC: 0 |
... the recent MilkyWay server sluggishness due to short tasks being issued influenced me to switch to Collatz for a while because I can download a larger cache of work there and leave it to run by itself without needing to check often to see if it has run out of work. It reduces the server load here and besides I like to support the other ATI project, it would be better if there were a few more of them. I've been trying that also. The higher cache at Collatz and the 12 MW WUs taking far longer on CPU has brought some respite to constantly checking whether ATI and CPUs are gainfully employed. |
Send message Joined: 30 Dec 07 Posts: 311 Credit: 149,490,184 RAC: 0 |
.....Perhaps they'll get it sorted by boinc v10.25.0. I wouldn't wait. Once ATI applications are fully integrated into BOINC then it is possible that the horror of a reduce towards zero credit scheme for GPUs will be unleashed. Have you tried running an older non ATI aware BOINC version with the <coproc></coproc> section removed from the app_info.xml file? You would probably need to adjust the <avg_ncpus></avg_ncpus> value as mentioned in the readme file. You could use the older BOINC version that previously worked for you and then the ATI tasks would be seen by BOINC as CPU tasks, so you would adjust your MilkyWay preferences accordingly. You may lose some benefits of using the newer 6.10.x BOINC versions but during these periods of MilkyWay server overload using an older BOINC version may have some advantage when requesting work. |
©2024 Astroinformatics Group