• Some users have recently had their accounts hijacked. It seems that the now defunct EVGA forums might have compromised your password there and seems many are using the same PW here. We would suggest you UPDATE YOUR PASSWORD and TURN ON 2FA for your account here to further secure it. None of the compromised accounts had 2FA turned on.
    Once you have enabled 2FA, your account will be updated soon to show a badge, letting other members know that you use 2FA to protect your account. This should be beneficial for everyone that uses FSFT.

It's out

Status
Not open for further replies.
440pt/day!!

I think I just <not suitable for children> my pants. Where's my CC, must buy a ATi card now.
 
uggghhh... i am feeling sick... or something like that *cough cough* ;)

Well, i had better leave work early!
 
stonedwaldo420 said:
uggghhh... i am feeling sick... or something like that *cough cough* ;)

Well, i had better leave work early!
yeah, you really don't look well either. You are all pale and stuff. And it's not the geeky "I never see the sun" kind of pale either. I am sure that if you go home and sleep a little more tonight, you'll get better ;)
 
drizzt81 said:
440pt/day!!

I think I just <not suitable for children> my pants. Where's my CC, must buy a ATi card now.

So a whole 33ppd more than 1 core of my Xeon 5140. Meh.
 
Seems to crash.

Folding@home Core Shutdown: EARLY_UNIT_END
[20:44:47] CoreStatus = 72 (114)
[20:44:47] Sending work to server
[20:44:47] - Error: Could not get length of results file work/wuresults_01.dat
[20:44:47] - Error: Could not read unit 01 file. Removing from queue.
[20:44:47] - Preparing to get new work unit...
[20:44:47] + Attempting to get work packet
[20:44:47] - Connecting to assignment server
[20:44:47] - Successful: assigned to (171.65.103.159).
[20:44:47] + News From Folding@Home: Welcome to our GPU beta.
[20:44:47] Loaded queue successfully.
[20:44:49] + Closed connections

Using 1900xtx on Core2. Have regular folding on CPU off
 
Sweet. Let us know how it goes. If you can see if running CPU client(s) makes a difference that would be great also.
 
I wont bother to delete my post. But you need to use either cat 6.5 or 6.10 beta

was using latest 6.9 and that doesnt work
 
MaDSpartus said:
I wont bother to delete my post. But you need to use either cat 6.5 or 6.10 beta

was using latest 6.9 and that doesnt work

I was about to ask which drivers you were using. Good.

They are also expecting a lot of Early Unit Ends, because they are trying to figure out which WU types will work.
 
It seems to be running ok on my x1900xt with omega drivers. Only thing is it seems to be loading both my gpu and cpu for some reason.
 
So from what I've gathered you need the following:

Latest DirectX drivers
6.5 or 6.10 ATI Catalyst drivers
X1900 or X1950 video card
CPU client(s) must have at least one CPU client set to Idle and 100% or below (can run 2 CPU clients concurrently).
Add: make sure 3 different machine IDs (one for each instance) <-- may not be necessary

Anyone see anything wrong with the list above?
 
yeah in the other thread someone said they tried cpu client at 80% and their GPU temps dropped, so it was robbing cycles from GPU. ALso there is no 6.10 it seems for XP 64 so i had to roll back to 6.5. If I'm getting the same or more PPD out of my 3.4ghz conroe than the GPU and running on conroe will draw less watts, let me use latest 6.9 Cats, and not use up my video ram so I can game without having to close down folding. I think I'll just stick to CPU folding unless some drastic PPD increase from using GPU is given.
 
My guess is that the CPU load will go down and they will be able to suspend GPU folding when gaming when later versions come out, but it might not make sense for a primary gaming rig. I'm going to be testing this on a secondary folding system (X2 3800+ with X1900XT). Just waiting for the card to come tomorrow.
 
Can someone with the proper sort of GPU check if EM3 monitors the GPU client properly? I would imagine it does, but there may be an update required.

 
People are saying that EMIII is not updated yet (different cores and all).
 
I can confirm that, I had to go look up the WU point value. EM3 tells you nothing, not even % finished

i think its cause the look of the log is quite different compared to CPU clients.
 
MaDSpartus said:
I can confirm that, I had to go look up the WU point value. EM3 tells you nothing, not even % finished

i think its cause the look of the log is quite different compared to CPU clients.

If Larry was not on the Alpha team, he's riding the tale end of this as everyone else it.
 
Random copy/paste add to FAQ if useful

http://forum.folding-community.org/viewtopic.php?t=16328&postdays=0&postorder=asc&start=15

Concorde Rules said:
TBH, I dont think you are going to get far, esp with x64 Windows, 64 bit drivers.
This is how I fixed other peoples:
Everyone thats haveing problems do this:
Delete all the current work files and the client config.
Start the client itself to set all the settings again - DO NOT RUN IT AS A SERVICE!!! (this might be the problem)
YOu want workunits above 5mb as a yes.
Adv settings you want CPU usage to low and the next option to 100.
Machine ID ive got as three because I have three clients.
Job done.
Try that.

Cat 6.5 seems to be the way to go

Might have to set from idle to low

Might have to back off one client % wise if running CPU client too.

porn- http://www.thunder-keep.co.uk/site/gpouclient.jpg
http://www.thunder-keep.co.uk/site/gpouclient2.jpg

working porn >> http://www.thunder-keep.co.uk/site/gpouclient3.jpg

http://www.thunder-keep.co.uk/site/gpouclient4.jpg

vj said:
As many of you have seen, we released our beta version of our GPU client today. You can find out all the details in our FAQ (http://folding.stanford.edu/FAQ-ATI.html).

Beta testing has already turned up an important problem with the Catalyst 6.10 drivers (thanks to everyone for their help here); 6.10 is causing EUE's (possibly amongst other causes too) and ATI is looking into this.

For now, we recommend 6.5 *only* (not 6.10, until it can be fixed). This is very much a beta test, so we expect to find problems like this. But we are working to quickly fix them as we find them.
 
I was having trouble reading that post from Concorde Rules.

I got the impression you wanted to lower the priority of the CPU Core(s) (I believe idle is below low).

The config he was suggesting was low and 100% but I got the impression from a few post and our guys that this was still slowing the GPU quite a bit.

Tomorrow is going to be a long day waiting for that GPU.
 
nikhsub1 said:
I have bad news... it wont run on the 1950 cards... look at this:

* Catalyst driver version 6.5 [download from ATI or from a Stanford mirror ] or version 6.10 [download from ATI ], but not any other versions: 6.6 and 6.7 will work, but at a major performance hit; 6.8 and 6.9 will not work at all. Due to all the complexities of support, we will support only versions 6.5 and 6.10.
* DirectX: 9.0c (4.09.0000.0904) or later, [download here] , which yields d3dx9_30.dll (the critical part for FAH)

The 1950's have to use 6.9 AFAIK... i just get errors up the wazoo.

...

edit: 1950 works, just needs cat 6.10 which cause EUE so you screwed either way

just what I'm reading
 
Hito Bahadur said:
You have production machines with X1900's or better?

no, god no.

but somone might just grab the "latest" client and throw into an image. I assume down the road the clients (console) will just be all one. I have not tried .05 but I'd guess would run non GPU

FYI hit I'll just keep dumping in here as to not mess up the FAQ
 
Hito Bahadur said:
I was having trouble reading that post from Concorde Rules.

I got the impression you wanted to lower the priority of the CPU Core(s) (I believe idle is below low).

The config he was suggesting was low and 100% but I got the impression from a few post and our guys that this was still slowing the GPU quite a bit.

Tomorrow is going to be a long day waiting for that GPU.


hell if I know. idle is > (below) low

seems to be a mix of playing with % (leave some open) and setting some to low
 
lol...okay. Didn't remember it that way, but I'm waiting for a computer to spit out a frame so I can look at it myself. Either here or in the FAQ. Doesn't matter.
 
Second I post in the FAQ

Zim will say I suck

Pagien will offer money for sexual favors to SmokeRngs

mage will shave his facial hair

and K* will offer up his nipple luzin

sorry, too much on topic posting of late
 
marty9876 said:
Second I post in the FAQ

Zim will say I suck

Pagien will offer money for sexual favors to SmokeRngs

mage will shave his facial hair

and K* will offer up his nipple luzin

sorry, too much on topic posting of late

OMG he said nothing about me... Thank the lord!!! :D
 
marty9876 said:
hell if I know. idle is > (below) low

seems to be a mix of playing with % (leave some open) and setting some to low
I must disagree with you...

idle !> low

low > idle
 
Jon855 said:
idle !> low
Wow, never seen that notation before. Usually I use <= :p

and the facial hair is staying attached, thankyouverymuch ;)

 
marty9876 said:
Second I post in the FAQ

Zim will say I suck

Pagien will offer money for sexual favors to SmokeRngs

mage will shave his facial hair

and K* will offer up his nipple luzin

sorry, too much on topic posting of late

Mage don't have no facial hair. :eek:
 
marty9876 said:
Second I post in the FAQ

Zim will say I suck

you suck anyways :p
more probation for mary03

these gpu's work units scream along
 
Status
Not open for further replies.
Back
Top