Problems with GPU Client! Help???

StevenG · 24 Nov 2006 at 20:13

i installed the gpu client updated to the lastest drivers and the latest DX and "GPU initialization failed" that is what i get..

my core voltage is 1.45 standard 3d clocks and i still get it..

any ideas?

StevenG

VeNT · 24 Nov 2006 at 20:19

StevenG said:
i installed the gpu client updated to the lastest drivers and the latest DX and "GPU initialization failed" that is what i get..

my core voltage is 1.45 standard 3d clocks and i still get it..

any ideas?

StevenG

you running it as a service (it doesn't work as a service) check the folder isn't read only (I had that issue) also check the mem voltages aswell. does it work at stock 2D clocks?

StevenG · 24 Nov 2006 at 20:38

how do i run it normally then?
and no it didnt run at 2d clocks

VeNT · 24 Nov 2006 at 21:08

check the graphics forum for details.

there is THE BEST sticcy (nearly typed stiffy, Freudian slip anyone?) on overclocking the X19xx range.

StevenG · 24 Nov 2006 at 21:22

i sorted it out BUT. i have to pause on of my CPU clients to get it to do anything.. the cpu clients take over the GPU one and give it 0 cpu time. anyway to get all 3 clients to run together? or am i better off running 1 Cpu and one GPU or just 2 CPU?

rich99million · 24 Nov 2006 at 21:47

1CPU and 1GPU is best for the points and the science, though if you set the GPU client as "low" priority and the CPU clients as "idle" you should be able to run all three side by side

StevenG · 24 Nov 2006 at 21:48

thanks.. i'll do that then.. 1cpu and 1 gpu.. im sure this will draw more power and its certainly making more noise..

also why cant i run the gpu as a service?

joeyjojo · 24 Nov 2006 at 23:44

StevenG said:
also why cant i run the gpu as a service?

Just a bug afaik.

rich99million · 25 Nov 2006 at 00:36

joeyjojo said:
Just a bug afaik.

actually you can - I've not tried it myself but apparently if you go into the service properties and allow the service to interract with the desktop then it actually works

# The service install option of previous console clients will not work as usual. The main issue is that the client must be run under the user account which owns the display in order for us to access the GPU for calculations. This is not a bug, but a fundmental limitation of Windows when used for GPU computation.

Novec has suggested this work around: Running the GPU client as a service is not a problem, you just have to give it desktop privileges. After installing the client as a service, open the service in computer manager, go to the Log On tab, keep it at "Local System account" and check "Allow service to interact with desktop". Then it crunches along just as usual. You probably shouldn't set it to start up automatically, though, since whichever program you use to increase clock speeds will load after the client service. Athough I haven't had any client crashes or EUEs when changing clock speeds on the fly, it's generally not recommended.

http://folding.stanford.edu/FAQ-ATI.html

edit: just tried it myself and seems to work fine - ahhhh a nice clean taskbar once more :cool:

SiriusB · 25 Nov 2006 at 02:38

I like having the GPU console window open. The client can be a bit temperamental at times and I wanna know about it on the double! Besides, it makes my desktop look 1337 :cool:

SiriusB

StevenG · 25 Nov 2006 at 03:50

well its done 60% on the GPU when typing this in a 23'C room the gpu was at 65'C, is this a normal temp? is it safe to be running this 24/7

ive allowed the client to interact with the desktop and its working fine, i dont like having ugly cmd windows on my task bar lol.

everything working fine.. i just with that FahMon could read the GPU WU's

Thanks for the help.

StevenG

rich99million · 25 Nov 2006 at 09:07

mine's currently running in the low 70's, bit higher than I'd like but the fan is already plenty loud enough

FreeStream · 25 Nov 2006 at 09:32

19C room, 709/845 @ 1.45V, Fan at 62% and temp is 58C.

:cool:

Anything under 70c is fine, under 80c should be ok aswell but as most X1900s fall over at anything more than 80c you should keep it under that, my Sappy X1900 falls over at 72C :eek:

StevenG · 25 Nov 2006 at 12:15

Hi, my GPU has finished a WU but has had 13 attempts to send the data, and still hasnt worked is something wrong?

rich99million · 25 Nov 2006 at 13:19

StevenG said:
Hi, my GPU has finished a WU but has had 13 attempts to send the data, and still hasnt worked is something wrong?

Make sure you have configured it NOT to use IE settings.

Are you still able to get work? If so then the server that WU has to get back to may just be busy or down temporarily. Post the section of your log where it starts going wrong so we can try and work out what's up

StevenG · 25 Nov 2006 at 15:08

[08:38:16] Finished Work Unit:
[08:38:16] - Reading up to 45408 from "work/wudata_02.trr": Read 45408
[08:38:16] - Reading up to 976572 from "work/wudata_02.xtc": Read 976572
[08:38:16] logfile size: 34897
[08:38:16] Leaving Run
[08:38:18] - Writing 1057949 bytes of core data to disk...
[08:38:18] Done: 1057437 -> 1022674 (compressed to 96.7 percent)
[08:38:19] ... Done.
[08:38:19] - Shutting down core
[08:38:19]
[08:38:19] Folding@home Core Shutdown: FINISHED_UNIT
[08:38:21] CoreStatus = 64 (100)
[08:38:21] Sending work to server

[08:38:21] + Attempting to send results
[08:38:44] + Results successfully sent
[08:38:44] Thank you for your contribution to Folding@Home.
[08:38:44] + Starting local stats count at 1
[08:38:48] - Preparing to get new work unit...
[08:38:48] + Attempting to get work packet
[08:38:48] - Connecting to assignment server
[08:38:48] - Successful: assigned to (171.64.65.20).
[08:38:48] + News From Folding@Home: GPU folding beta
[08:38:49] Loaded queue successfully.
[08:38:50] + Could not get Work unit data from Work Server
[08:38:50] - Error: Attempt #1 to get work failed, and no other work to do.
Waiting before retry.

And its gone to 17 re-tries so far

VeNT · 25 Nov 2006 at 17:48

StevenG said:
[08:38:16] Finished Work Unit:
[08:38:16] - Reading up to 45408 from "work/wudata_02.trr": Read 45408
[08:38:16] - Reading up to 976572 from "work/wudata_02.xtc": Read 976572
[08:38:16] logfile size: 34897
[08:38:16] Leaving Run
[08:38:18] - Writing 1057949 bytes of core data to disk...
[08:38:18] Done: 1057437 -> 1022674 (compressed to 96.7 percent)
[08:38:19] ... Done.
[08:38:19] - Shutting down core
[08:38:19]
[08:38:19] Folding@home Core Shutdown: FINISHED_UNIT
[08:38:21] CoreStatus = 64 (100)
[08:38:21] Sending work to server

[08:38:21] + Attempting to send results
[08:38:44] + Results successfully sent
[08:38:44] Thank you for your contribution to Folding@Home.
[08:38:44] + Starting local stats count at 1
[08:38:48] - Preparing to get new work unit...
[08:38:48] + Attempting to get work packet
[08:38:48] - Connecting to assignment server
[08:38:48] - Successful: assigned to (171.64.65.20).
[08:38:48] + News From Folding@Home: GPU folding beta
[08:38:49] Loaded queue successfully.
[08:38:50] + Could not get Work unit data from Work Server
[08:38:50] - Error: Attempt #1 to get work failed, and no other work to do.
Waiting before retry.

And its gone to 17 re-tries so far

looks like it uploaded fine, jus not able to download.

StevenG · 25 Nov 2006 at 18:27

oh well its started another one now i think. i'll see if the points appear.. if they dont i'll have to look into it again.

StevenG · 26 Nov 2006 at 10:00

im back.. and its doing it again.. wont get any work.. but sent the work fine..

i have it setup to use IE settings how do i re-configure? will this fix the problem

rich99million · 26 Nov 2006 at 11:27

StevenG said:
im back.. and its doing it again.. wont get any work.. but sent the work fine..

i have it setup to use IE settings how do i re-configure? will this fix the problem

Yes it's most likely the problem, something that microsoft has changed has stopped the IE settings working for F@H.

Stop the client, then run it with the -configonly switch just like you do when reconfiguring the CPU client (instructions in the sticky will work the same for either client)