Is <gpu value="true"/> in your config.xml file? If Windows, the path is C:\ProgramData\FAHClient\config.xml.
Search found 60 matches
- Thu Oct 20, 2022 8:34 pm
- Forum: Problems with AMD/ATI drivers
- Topic: AMD RX6000+ family GPU owners, please update to 22.7.1 drivers for optimal F@H performance
- Replies: 21
- Views: 208629
- Thu Oct 20, 2022 8:24 pm
- Forum: Problems with AMD/ATI drivers
- Topic: AMD RX6000+ family GPU owners, please update to 22.7.1 drivers for optimal F@H performance
- Replies: 21
- Views: 208629
Re: AMD RX6000+ family GPU owners, please update to 22.7.1 drivers for optimal F@H performance
A Windows system restart causes an unwanted GPU client to restart and be assigned a work unit despite continual removal of the Slot 1 GPU client using FAHControl. I have as tenable a solution as any I've seen if you don't want another client (in my case, a Slot 1 GPU client) to start. I set C:\Progr...
- Fri Oct 07, 2022 8:54 pm
- Forum: V7.6.x Public Release Windows/Linux/MacOS X
- Topic: Problem after an unwanted shoutdown
- Replies: 14
- Views: 6109
Re: Problem after an unwanted shoutdown
<config> <!-- Folding Core --> <checkpoint v='10'/> <core-priority v='low'/> <!-- Folding Slot Configuration --> <cause v='HIGH_PRIORITY'/> <!-- Network --> <proxy v=':8080'/> <!-- Slot Control --> <pause-on-battery v='false'/> <power v='FULL'/> <!-- User Information --> <passkey v='8663b3b16d850b5...
- Fri Oct 07, 2022 7:31 pm
- Forum: V7.6.x Public Release Windows/Linux/MacOS X
- Topic: Problem after an unwanted shoutdown
- Replies: 14
- Views: 6109
Re: Problem after an unwanted shoutdown
This happens with every restart since I started running a native Windows client. It does not happen in a virtual machine running Linux. I have not run Linux on the AMD Ryzen 7 5700G other than as a VM or container. The GPU hardware interfaced via X. therefore the MS hypervisor can only see the CPU. ...
- Tue May 10, 2011 5:07 pm
- Forum: Issues with a specific server
- Topic: 171.64.65.54 - Reject [Emergency downtime]
- Replies: 41
- Views: 9405
Re: 171.64.65.54 - Reject [Emergency downtime]
After over 9 hours of trying to upload to this server, I'm still getting rejected. The CS status is in standby and not accepting connections. :e( When this WU finished here, there was still 95% of time to deadline remaining. What happens if the deadline passes before the WS is fixed? I've been using...
- Fri Mar 11, 2011 2:05 am
- Forum: Issues with a specific server
- Topic: 171.64.65.55 sending bad packets
- Replies: 21
- Views: 4516
Re: 171.64.65.55 sending bad packets
Still happening as I type this @ 02:03 GMT.
- Wed Mar 09, 2011 11:16 am
- Forum: Issues with a specific server
- Topic: 171.64.65.55 sending bad packets
- Replies: 21
- Views: 4516
Re: 171.64.65.55 sending bad packets
It was working! But bad packets are getting sent again. The good news is that it didn't make my machine sit for hours with nothing to do this time. [22:40:36] + Attempting to send results [March 8 22:40:36 UTC] [22:40:36] - Reading file work/wuresults_09.dat from core [22:40:36] (Read 3526051 bytes ...
- Mon Mar 07, 2011 9:55 am
- Forum: Issues with a specific server
- Topic: 171.64.65.55 sending bad packets
- Replies: 21
- Views: 4516
Re: 171.64.65.55 sending bad packets
Getting good data from 171.64.65.55 now, no communication errors. Thank you. [22:33:17] Initial: 40AB; - Successful: assigned to (171.64.65.55). [22:33:17] + News From Folding@Home: Welcome to Folding@Home [22:33:17] Loaded queue successfully. [22:33:17] Sent data [22:33:17] Connecting to http://171...
- Fri Mar 04, 2011 5:21 pm
- Forum: Issues with a specific server
- Topic: 171.64.65.55 sending bad packets
- Replies: 21
- Views: 4516
Re: 171.64.65.55 sending bad packets
I have more than one box doing this. My first machine referenced here is running an AMD Phenom II X6 1090T. But I just checked my wife's computer F@H logs that runs F@H 24/7. It has been getting the same assignment problems. The following occurred March 2. [18:30:12] + Attempting to get work packet ...
- Fri Mar 04, 2011 3:54 pm
- Forum: Issues with a specific server
- Topic: 171.64.65.55 sending bad packets
- Replies: 21
- Views: 4516
Re: 171.64.65.55 sending bad packets
This happened again today. It took almost 5 hours (14 failed attempts) to get assigned to a server with valid work units. Is there any way on the client side to force changing servers or shut down the client after x number of failed attempts? I'm trying to limit F@H use of this particular machine to...
- Fri Mar 04, 2011 1:36 am
- Forum: Issues with a specific server
- Topic: 171.64.65.55 sending bad packets
- Replies: 21
- Views: 4516
171.64.65.55 sending bad packets
The last time this occurred communicating with me was at 10:00 GMT on 3/3/11. [10:06:07] + Attempting to get work packet [10:06:07] Passkey found [10:06:07] - Will indicate memory of 2560 MB [10:06:07] - Connecting to assignment server [10:06:07] Connecting to http://assign.stanford.edu:8080/ [10:06...
- Tue Jun 15, 2010 7:14 pm
- Forum: Issues with a specific server
- Topic: Is it just me or......
- Replies: 16
- Views: 4125
Re: Is it just me or......
Thanks Bruce. After our city power comes back up (high winds brought a tree down on a power line and am using a generator right now) I will connect to work and verify the returned WU's. Thanks, BrokenWolf Now that's dedication! :egeek: Hope things are getting better for you folks; we had stormy stu...
- Sat Feb 20, 2010 8:37 pm
- Forum: Issues with a specific WU
- Topic: Project 2653 Run 1, Clone 129, Gen 143 - EUE
- Replies: 2
- Views: 801
Re: Project 2653 Run 1, Clone 129, Gen 143 - EUE
Will check hardware OC, stress test and adjust. In the other thread I started, viewtopic.php?f=58&t=13533, Wrish pointed out this could be a RAM problem. Will take your recommendation and proceed accordingly. EDIT :oops: Found an error in my OC utility (Gigabyte EasyTune) settings. I had BIOS se...
- Fri Feb 19, 2010 11:07 pm
- Forum: Issues with a specific WU
- Topic: Project 2653 Run 1, Clone 129, Gen 143 - EUE
- Replies: 2
- Views: 801
Project 2653 Run 1, Clone 129, Gen 143 - EUE
On Windows 7 x64 Ultimate-RTM, 6.29 beta client. When running Core_A1 consistently get "Working with standard loops on this execution. - Previous termination of core was improper." If get A3 core WU following, either hangs or get ridiculously long TPF until re-boot. Hardware: Phenom II x4 ...
- Wed Feb 17, 2010 7:15 am
- Forum: Issues with a specific server
- Topic: Last two WUs from 171.64.65.56 not credited
- Replies: 14
- Views: 4204
Re: Last two WUs from 171.64.65.56 not credited
I'll talk to Dr. Kasson about the recredit he has in mind. It may have been that a recredit is not possible for some reason or that it required additional information or help from others on the staff. I'll ask him to post. In general, we try to handle recrediing very carefully and it will take us a...