When I Google "OpenMM" it refers to a molecular toolkit. Sounds like it is specific to folding@home.
I don't think folding is recognizing the discrete gpus? What does the folding startup log say?
Tom M
A Proud member of the O.F.A. (Old Farts Association). Be well, do good work, and keep in touch.® (Garrison Keillor) I want some more patience. RIGHT NOW!
It sounds like you should also post your question in the problems section of folding@home.
Already done that, the github page and their forum.
Tom M wrote:
If this is boinc I would do a project reset. That would clear out the project folder and redownload everything. When I get errors I don't understand at all that sometimes clears the problem.
It was a fresh install. Folding hadn't been on that machine ever.
If this page takes an hour to load, reduce posts per page to 20 in your settings, then the tinpot 486 Einstein uses can handle it.
It looks like FAH ships its own environment for its tasks. OpenMM is the common package used for molecular modeling which is of course what FAH does primarily.
The work unit package did not get installed correctly it seems. Usually a problem with directory locations and permissions.
Aha! Now.... I've been having problems with a secondary Boinc on another machine, which I fixed by running it as Admin and resetting all the permissions in the Boinc folder to have no restrictions. I shall try the same with Folding. Probably some recent Windows update is making everything screw up. It's become as overly secure as Linux.
Edit: mission failure, still the same.
If this page takes an hour to load, reduce posts per page to 20 in your settings, then the tinpot 486 Einstein uses can handle it.
Reading your log output, I would say that the FAH client dropped from running once it started crunching your work unit. Something about your setup FAH client doesn't like.
You should post this log to the FAH Help forums for assistance.
Searching for similar messages points to the FAH client and OpenMM not being compatible with some AMD drivers.
Quote:
There is at least one pending bug that can best be described as an incompatibility between the AMD drivers and the OpenMM version in the active FAHCore.
I've fitted Tom's card (PCI-Express 4 lane, to 8 USB riser connections). I connected 6 GPUs to it, but the computer objected (device manager showed one as "cannot start this device") - I blame this on the card, I've often had one card refuse to be on the same machine as another.
So I moved that card back to the miner machine, and am running 5 on the card.
However something is weird - MSI Afterburner is not reading the cards correctly, 4 of them show no usage, one shows 30% usage, and none show any temperature or clock speeds. GPU-Z shows everything but the clock speed ok, so I'm using that instead. I tried a couple of other programs but they failed to work too.
However, folding@home is very happy! It sees all 5 cards, and they are all running at very high (97-99%) usage, even when I run 23 of the 24 CPU cores on Rosetta. Clearly it's sharing more than just the one PCI-E v2 lane the normal risers do.
Tom - thankyou very much indeed! I shall attempt more GPUs on it as I get others repaired, I have 5 on a shelf to take apart.
If this page takes an hour to load, reduce posts per page to 20 in your settings, then the tinpot 486 Einstein uses can handle it.
... I shall attempt more GPUs on it as I get others repaired, I have 5 on a shelf to take apart.
What components do you 'repair'? Is it just fans or do you actually replace components like caps, etc?
I've successfully repaired the electrolytic caps on older style motherboards and PSUs where the failed component is rather obvious. I have some older GPUs with polys that look OK but the GPU is starting to freeze from time to time and, whilst the machine itself hasn't crashed, it needs a cold reboot to get the GPU working again. Have you experienced anything like this?
Replacing the TIM doesn't seem to improve things and the fans are fine so I don't think it's thermal. Swapping identical GPUs between machines shows that the problem goes with the GPU so I guess it's probably some component that has drifted out of spec. It's happened on about 4 cards of the same make and model (MSI HD7850) so it's probably the same component. I bought 34 of these back in 2013 so they certainly don't owe me anything :-). The fans have been rock solid - never had to replace one.
FAH does not use BOINC. They
)
FAH does not use BOINC. They use their own client and installation.
Peter, When I Google
)
Peter,
When I Google "OpenMM" it refers to a molecular toolkit. Sounds like it is specific to folding@home.
I don't think folding is recognizing the discrete gpus? What does the folding startup log say?
Tom M
A Proud member of the O.F.A. (Old Farts Association). Be well, do good work, and keep in touch.® (Garrison Keillor) I want some more patience. RIGHT NOW!
Tom M wrote:It sounds like
)
Already done that, the github page and their forum.
It was a fresh install. Folding hadn't been on that machine ever.
If this page takes an hour to load, reduce posts per page to 20 in your settings, then the tinpot 486 Einstein uses can handle it.
Keith Myers wrote:It looks
)
Aha! Now.... I've been having problems with a secondary Boinc on another machine, which I fixed by running it as Admin and resetting all the permissions in the Boinc folder to have no restrictions. I shall try the same with Folding. Probably some recent Windows update is making everything screw up. It's become as overly secure as Linux.
Edit: mission failure, still the same.
If this page takes an hour to load, reduce posts per page to 20 in your settings, then the tinpot 486 Einstein uses can handle it.
Tom M wrote: Peter, When I
)
*********************** Log Started 2023-03-01T19:37:48Z ***********************
19:37:48:I1:*********************** Folding@home Client ***********************
19:37:48:I1: Version: 8.1.13
19:37:48:I1: Author: Joseph Coffland <joseph@cauldrondevelopment.com>
19:37:48:I1: Org: foldingathome.org
19:37:48:I1: Copyright: 2023 foldingathome.org
19:37:48:I1: Homepage: https://foldingathome.org/
19:37:48:I1: License: https://www.gnu.org/licenses/gpl-3.0.txt
19:37:48:I1: Date: Feb 7 2023
19:37:48:I1: Time: 23:15:53
19:37:48:I1: Compiler: Visual C++
19:37:48:I1: Options: /TP /std:c++14 /nologo /EHa /wd4297 /wd4103 /O2 /Zc:throwingNew /MT
19:37:48:I1: Platform: win32 10
19:37:48:I1: Bits: 64
19:37:48:I1: Mode: Release
19:37:48:I1: Args: --open-web-control
19:37:48:I1: Config: C:\ProgramData\FAHClient\config.xml
19:37:48:I1:****************************** CBang ******************************
19:37:48:I1: Version: 1.7.2
19:37:48:I1: Author: Joseph Coffland <joseph@cauldrondevelopment.com>
19:37:48:I1: Org: Cauldron Development LLC
19:37:48:I1: Copyright: Cauldron Development LLC, 2003-2023
19:37:48:I1: Homepage: https://cauldrondevelopment.com/
19:37:48:I1: License: GPL 2+
19:37:48:I1: Date: Feb 7 2023
19:37:48:I1: Time: 20:33:41
19:37:48:I1: Compiler: Visual C++
19:37:48:I1: Options: /TP /std:c++14 /nologo /EHa /wd4297 /wd4103 /O2 /Zc:throwingNew /MT
19:37:48:I1: Platform: win32 10
19:37:48:I1: Bits: 64
19:37:48:I1: Mode: Release
19:37:48:I1:***************************** System ******************************
19:37:48:I1: CPU: Intel(R) Core(TM) i3-6100 CPU @ 3.70GHz
19:37:48:I1: CPU ID: GenuineIntel Family 6 Model 94 Stepping 3
19:37:48:I1: CPUs: 4
19:37:48:I1: Memory: 31.45GiB
19:37:48:I1:Free Memory: 28.13GiB
19:37:48:I1: Threads: WINDOWS_THREADS
19:37:48:I1: OS Version: 6.2
19:37:48:I1:Has Battery: false
19:37:48:I1: On Battery: false
19:37:48:I1: UTC Offset: 0
19:37:48:I1: PID: 10360
19:37:48:I1: CWD: C:\ProgramData\FAHClient
19:37:48:I1: Exec: C:\Program Files\FAHClient\FAHClient.exe
19:37:48:I1:*******************************************************************
19:37:48:I2:<config>
19:37:48:I2: <!-- HTTP Server -->
19:37:48:I2: <allow v='127.0.0.1 10.0.0.0/8 192.168.0.0/16 172.16.0.0/12 169.254.0.0/16'/>
19:37:48:I2: <deny>
19:37:48:I2: 0/0
19:37:48:I2: </deny>
19:37:48:I2: <http-addresses v='0.0.0.0:7396'/>
19:37:48:I2:</config>
19:37:48:I1:Opening Database
19:37:48:I1:Listening for HTTP on 0.0.0.0:7396
19:37:48:I3:id = 5HkFVsQIZ+XEHOAPwE+AuAhI1tnUdi1cqSxjphCKdpc=
19:37:48:I3:Loading work unit 39 to group '' with ID jkDDmgg09rZ0e-Z9MD0yUfQFSrEUItvS7Rgl5eB-T_Q
19:37:48:I3:Loaded 1 wus.
19:37:48:I1:Started Windows systray control
19:37:48:I3:Adding GPU gpu:00:02:00
19:37:48:I3:Adding GPU gpu:05:00:00
19:37:48:I3:Adding GPU gpu:06:00:00
19:37:48:I3:Adding GPU gpu:02:00:00
19:37:48:I3:Adding GPU gpu:04:00:00
19:37:48:E :Exception: Failed to open dynamic library 'nvcuda.dll': The specified module could not be found.
19:38:09:I3:gpus = {
19:38:09:I3: "gpu:00:02:00": {"type": "intel", "description": "SKL GT2 [HD Graphics 530]"},
19:38:09:I3: "gpu:05:00:00": {"type": "amd", "description": "Tahiti XT [R9 280X/HD 7900/8970 OEM]"},
19:38:09:I3: "gpu:06:00:00": {"type": "amd", "description": "Tahiti PRO [R9 280/HD 7950/8950 OEM]"},
19:38:09:I3: "gpu:02:00:00": {"type": "amd", "description": "Tahiti XT [R9 280X/HD 7900/8970 OEM]"},
19:38:09:I3: "gpu:04:00:00": {"type": "amd", "description": "Tahiti XT [R9 280X/HD 7900/8970 OEM]"}
19:38:09:I3:}
19:38:15:I1::WU39:Downloading WU
19:38:15:I1:OUT10:> POST https://ds03.scs.illinois.edu/api/assign HTTP/1.1
19:38:15:I3:Connecting to ds03.scs.illinois.edu:443
19:38:16:I1:OUT10:< ds03.scs.illinois.edu:443 HTTP/1.1 500 HTTP_INTERNAL_SERVER_ERROR
19:38:16:E ::WU39:HTTP_INTERNAL_SERVER_ERROR: {"error":{"message":"Can't dereference NULL pointer!"}}
19:38:18:I1::Added new work unit: cpus:4 gpus:gpu:02:00:00,gpu:04:00:00,gpu:05:00:00,gpu:06:00:00
19:38:18:I1::WU43:Requesting WU assignment
19:38:18:I1:OUT11:> POST https://assign1.foldingathome.org/api/assign HTTP/1.1
19:38:18:I3:Connecting to assign1.foldingathome.org:443
19:38:19:I1:OUT11:< assign1.foldingathome.org:443 HTTP/1.1 200 HTTP_OK
19:38:19:I1::WU43:Received WU assignment NWAt8YSJTROdhR80olH18g0iP6flLCTYa2KXcBxpnq4
19:38:19:I1::WU43:Downloading WU
19:38:19:I1:OUT12:> POST https://ds03.scs.illinois.edu/api/assign HTTP/1.1
19:38:19:I3:Connecting to ds03.scs.illinois.edu:443
19:38:51:I1:OUT12:< ds03.scs.illinois.edu:443 HTTP/1.1 200 HTTP_OK
19:38:51:I1::WU43:Received WU
19:38:51:I1:Loaded cores/openmm-core-22/fahcore-22-windows-64bit-release-0.0.20/FahCore_22.exe
19:38:51:I1::WU43:CORE 100%
19:38:51:I1::Added new work unit: cpus:3 gpus:gpu:04:00:00,gpu:05:00:00,gpu:06:00:00
19:38:51:I3::WU43:Running FahCore: C:\ProgramData\FAHClient\cores/openmm-core-22/fahcore-22-windows-64bit-release-0.0.20/FahCore_22.exe -dir NWAt8YSJTROdhR80olH18g0iP6flLCTYa2KXcBxpnq4 -suffix 01 -version 8.1.13 -lifeline 10360 -gpu-vendor amd -opencl-platform 1 -opencl-device 2 -gpu 2
19:38:51:I3::WU43:Started FahCore on PID 4172
19:38:51:I1::WU44:Requesting WU assignment
19:38:51:I1:OUT13:> POST https://assign2.foldingathome.org/api/assign HTTP/1.1
19:38:51:I3:Connecting to assign2.foldingathome.org:443
19:38:52:I1::WU43:*********************** Log Started 2023-03-01T19:38:51Z ***********************
19:38:52:I1::WU43:*************************** Core22 Folding@home Core ***************************
19:38:52:I1::WU43: Core: Core22
19:38:52:I1::WU43: Type: 0x22
19:38:52:I1::WU43: Version: 0.0.20
19:38:52:I1::WU43: Author: Joseph Coffland <joseph@cauldrondevelopment.com>
19:38:52:I1::WU43: Copyright: 2020 foldingathome.org
19:38:52:I1::WU43: Homepage: https://foldingathome.org/
19:38:52:I1::WU43: Date: Jan 20 2022
19:38:52:I1::WU43: Time: 01:15:36
19:38:52:I1::WU43: Revision: 3f211b8a4346514edbff34e3cb1c0e0ec951373c
19:38:52:I1::WU43: Branch: HEAD
19:38:52:I1::WU43: Compiler: Visual C++
19:38:52:I1::WU43: Options: /TP /nologo /EHa /wd4297 /wd4103 /O2 /Zc:throwingNew /MT
19:38:52:I1::WU43: -DOPENMM_VERSION="\"7.7.0\""
19:38:52:I1::WU43: Platform: win32 10
19:38:52:I1::WU43: Bits: 64
19:38:52:I1::WU43: Mode: Release
19:38:52:I1::WU43:Maintainers: John Chodera <john.chodera@choderalab.org> and Peter Eastman
19:38:52:I1::WU43: <peastman@stanford.edu>
19:38:52:I1::WU43: Args: -dir NWAt8YSJTROdhR80olH18g0iP6flLCTYa2KXcBxpnq4 -suffix 01
19:38:52:I1::WU43: -version 8.1.13 -lifeline 10360 -gpu-vendor amd -opencl-platform 1
19:38:52:I1::WU43: -opencl-device 2 -gpu 2
19:38:52:I1::WU43:************************************ libFAH ************************************
19:38:52:I1::WU43: Date: Jan 20 2022
19:38:52:I1::WU43: Time: 01:14:17
19:38:52:I1::WU43: Revision: 9f4ad694e75c2350d4bb6b8b5b769ba27e483a2f
19:38:52:I1::WU43: Branch: HEAD
19:38:52:I1::WU43: Compiler: Visual C++
19:38:52:I1::WU43: Options: /TP /nologo /EHa /wd4297 /wd4103 /O2 /Zc:throwingNew /MT
19:38:52:I1::WU43: Platform: win32 10
19:38:52:I1::WU43: Bits: 64
19:38:52:I1::WU43: Mode: Release
19:38:52:I1::WU43:************************************ CBang *************************************
19:38:52:I1::WU43: Date: Jan 20 2022
19:38:52:I1::WU43: Time: 01:13:20
19:38:52:I1::WU43: Revision: ab023d155b446906d55b0f6c9a1eedeea04f7a1a
19:38:52:I1::WU43: Branch: HEAD
19:38:52:I1::WU43: Compiler: Visual C++
19:38:52:I1::WU43: Options: /TP /nologo /EHa /wd4297 /wd4103 /O2 /Zc:throwingNew /MT
19:38:52:I1::WU43: Platform: win32 10
19:38:52:I1::WU43: Bits: 64
19:38:52:I1::WU43: Mode: Release
19:38:52:I1::WU43:************************************ System ************************************
19:38:52:I1::WU43: CPU: Intel(R) Core(TM) i3-6100 CPU @ 3.70GHz
19:38:52:I1::WU43: CPU ID: GenuineIntel Family 6 Model 94 Stepping 3
19:38:52:I1::WU43: CPUs: 4
19:38:52:I1::WU43: Memory: 31.45GiB
19:38:52:I1::WU43:Free Memory: 27.65GiB
19:38:52:I1::WU43: Threads: WINDOWS_THREADS
19:38:52:I1::WU43: OS Version: 6.2
19:38:52:I1::WU43:Has Battery: false
19:38:52:I1::WU43: On Battery: false
19:38:52:I1::WU43: UTC Offset: 0
19:38:52:I1::WU43: PID: 4172
19:38:52:I1::WU43: CWD: C:\ProgramData\FAHClient\work
19:38:52:I1::WU43:************************************ OpenMM ************************************
19:38:52:I1::WU43: Version: 7.7.0
19:38:52:I1::WU43:********************************************************************************
19:38:52:I1::WU43:Project: 19329 (Run 0, Clone 21, Gen 59)
19:38:52:I1::WU43:Reading tar file core.xml
19:38:52:I1::WU43:Reading tar file integrator.xml
19:38:52:I1::WU43:Reading tar file state.xml
19:38:52:I1:OUT13:< assign2.foldingathome.org:443 HTTP/1.1 200 HTTP_OK
19:38:52:I1::WU44:Received WU assignment XPQ10vJRdVeasZ5zyat00wi5YoLeYgG6zfHXtNEl_nI
19:38:52:I1::WU44:Downloading WU
19:38:52:I1:OUT14:> POST https://vav19.fah.temple.edu/api/assign HTTP/1.1
19:38:52:I3:Connecting to vav19.fah.temple.edu:443
19:38:52:I1::WU43:Reading tar file system.xml
19:38:53:I1::WU43:Digital signatures verified
19:38:53:I1::WU43:Folding@home GPU Core22 Folding@home Core
19:38:53:I1::WU43:Version 0.0.20
19:39:08:I1::WU43: Checkpoint write interval: 50000 steps (5%) [20 total]
19:39:08:I1::WU43: JSON viewer frame write interval: 10000 steps (1%) [100 total]
19:39:08:I1::WU43: XTC frame write interval: 25000 steps (2.5%) [40 total]
19:39:08:I1::WU43: Global context and integrator variables write interval: disabled
19:39:08:I1::WU43:There are 3 platforms available.
19:39:08:I1::WU43:Platform 0: Reference
19:39:08:I1::WU43:Platform 1: CPU
19:39:08:I1::WU43:Platform 2: OpenCL
19:39:08:I1::WU43: opencl-device 2 specified
19:39:20:I1::WU43:WARNING:Console control signal 1 on PID 4172
19:39:20:I1::WU43:Exiting, please wait. . .
19:39:23:I1:OUT14:< vav19.fah.temple.edu:443 HTTP/1.1 200 HTTP_OK
19:39:24:I1::WU44:Received WU
19:39:25:I3::WU43:Dumping NWAt8YSJTROdhR80olH18g0iP6flLCTYa2KXcBxpnq4
19:39:26:I1::WU43:ERROR:102: Core startup was interrupted by client.
19:39:26:I1::WU43:Folding@home Core Shutdown: INTERRUPTED
19:39:26:I3::WU44:Dumping XPQ10vJRdVeasZ5zyat00wi5YoLeYgG6zfHXtNEl_nI
19:39:26:I1::WU44:Sending dump report
19:39:26:I1:OUT15:> POST https://vav19.fah.temple.edu/api/results HTTP/1.1
19:39:26:I3:Connecting to vav19.fah.temple.edu:443
19:39:27:I1:OUT15:< vav19.fah.temple.edu:443 HTTP/1.1 200 HTTP_OK
19:39:27:I1::WU44:Dumped
19:39:27:I1::WU43:Core returned INTERRUPTED (102)
19:39:27:I1::WU43:Sending dump report
19:39:27:I1:OUT16:> POST https://ds03.scs.illinois.edu/api/results HTTP/1.1
19:39:27:I3:Connecting to ds03.scs.illinois.edu:443
19:39:28:I1:OUT16:< ds03.scs.illinois.edu:443 HTTP/1.1 200 HTTP_OK
19:39:28:I1::WU43:Dumped
19:39:34:I1:Clean exit
If this page takes an hour to load, reduce posts per page to 20 in your settings, then the tinpot 486 Einstein uses can handle it.
Reading your log output, I
)
Reading your log output, I would say that the FAH client dropped from running once it started crunching your work unit. Something about your setup FAH client doesn't like.
You should post this log to the FAH Help forums for assistance.
Searching for similar messages points to the FAH client and OpenMM not being compatible with some AMD drivers.
Same driver, same cards,
)
Same driver, same cards, moved from another (older inferior) machine.
Which part of the log is relevant and I'll copy it over?
If this page takes an hour to load, reduce posts per page to 20 in your settings, then the tinpot 486 Einstein uses can handle it.
19:39:08:I1::WU43:
)
19:39:08:I1::WU43: opencl-device 2 specified
19:39:20:I1::WU43:WARNING:Console control signal 1 on PID 4172
19:39:20:I1::WU43:Exiting, please wait. . .
19:39:23:I1:OUT14:< vav19.fah.temple.edu:443 HTTP/1.1 200 HTTP_OK
19:39:24:I1::WU44:Received WU
19:39:25:I3::WU43:Dumping NWAt8YSJTROdhR80olH18g0iP6flLCTYa2KXcBxpnq4
19:39:26:I1::WU43:ERROR:102: Core startup was interrupted by client.
19:39:26:I1::WU43:Folding@home Core Shutdown: INTERRUPTED
19:39:26:I3::WU44:Dumping XPQ10vJRdVeasZ5zyat00wi5YoLeYgG6zfHXtNEl_nI
19:39:26:I1::WU44:Sending dump report
19:39:26:I1:OUT15:> POST https://vav19.fah.temple.edu/api/results HTTP/1.1
19:39:26:I3:Connecting to vav19.fah.temple.edu:443
19:39:27:I1:OUT15:< vav19.fah.temple.edu:443 HTTP/1.1 200 HTTP_OK
19:39:27:I1::WU44:Dumped
19:39:27:I1::WU43:Core returned INTERRUPTED (102)
19:39:27:I1::WU43:Sending dump report
I've fitted Tom's card
)
I've fitted Tom's card (PCI-Express 4 lane, to 8 USB riser connections). I connected 6 GPUs to it, but the computer objected (device manager showed one as "cannot start this device") - I blame this on the card, I've often had one card refuse to be on the same machine as another.
So I moved that card back to the miner machine, and am running 5 on the card.
However something is weird - MSI Afterburner is not reading the cards correctly, 4 of them show no usage, one shows 30% usage, and none show any temperature or clock speeds. GPU-Z shows everything but the clock speed ok, so I'm using that instead. I tried a couple of other programs but they failed to work too.
However, folding@home is very happy! It sees all 5 cards, and they are all running at very high (97-99%) usage, even when I run 23 of the 24 CPU cores on Rosetta. Clearly it's sharing more than just the one PCI-E v2 lane the normal risers do.
Tom - thankyou very much indeed! I shall attempt more GPUs on it as I get others repaired, I have 5 on a shelf to take apart.
If this page takes an hour to load, reduce posts per page to 20 in your settings, then the tinpot 486 Einstein uses can handle it.
Peter Hucker wrote:... I
)
What components do you 'repair'? Is it just fans or do you actually replace components like caps, etc?
I've successfully repaired the electrolytic caps on older style motherboards and PSUs where the failed component is rather obvious. I have some older GPUs with polys that look OK but the GPU is starting to freeze from time to time and, whilst the machine itself hasn't crashed, it needs a cold reboot to get the GPU working again. Have you experienced anything like this?
Replacing the TIM doesn't seem to improve things and the fans are fine so I don't think it's thermal. Swapping identical GPUs between machines shows that the problem goes with the GPU so I guess it's probably some component that has drifted out of spec. It's happened on about 4 cards of the same make and model (MSI HD7850) so it's probably the same component. I bought 34 of these back in 2013 so they certainly don't owe me anything :-). The fans have been rock solid - never had to replace one.
Thanks in advance for any thoughts you may have.
Cheers,
Gary.