Adding ASRock RX 9070 XT Steel Legend

[Malvado]

Currently the Gpu shows as just gfx1201 , trying the tools to get the information was problematic (cmd would not respond) , but here is some information :
https://www.techpowerup.com/gpu-specs/a ... end.b12258
Navi 48 Revision C0
AMD Radeon RX 9070 XT
Asrock RX 9070 XT
Device ID 1002 7550 - 1849 5403
Under the description page (folding at home client) you get the info gfx1201 , gpu:03:00:00

[Joe_H]

That card is already whitelisted, here is its entry in the GPUs.txt file:

Code: Select all

0x1002:0x7550:1:10:Navi 48 [Radeon RX 9070(XT)]

Something else is keeping the GPU from being recognized. You need the latest drivers and OpenCL support installed. Details on that will depend on your OS.

[muziqaz]

GPU being recognised as gfx1201 is fine. I take it this is Windows PC. Install AMD provided drivers, make sure chipset drivers are up to date as well. Log files to show what is going on with fahclient also would help

[Malvado]

Did a clean install, fixed some OpenCL issues in the registry , it works at folding, but shows as gfx1201.
I guess this is the log file you wanted?

Code: Select all

*********************** Log Started 2025-11-10T23:59:58Z ***********************
14:35:38:I1:Account websocket closed: PROTOCOL msg=Failed to read header start
14:35:53:W :CON29:DNS lookup failed for api.foldingathome.org
14:35:53:E :OUT29:Failed response: CONNECT
14:36:09:I1:OUT30:> GET https://api.foldingathome.org/machine/DNzCnGbDNT_pOYPJbpo6phuOq-3-euxkgH9kDAbR_-E HTTP/1.1
14:36:09:I1:OUT30:< HTTP/1.1 200 HTTP_OK
14:36:10:I1:OUT2:> GET wss://node1.foldingathome.org/ws/client HTTP/1.1
14:36:10:I1:OUT2:< HTTP/1.1 101 HTTP_SWITCHING_PROTOCOLS
14:36:10:I1:Logging into node account
14:36:34:I1:Account websocket closed: PROTOCOL msg=Failed to read header start
14:36:34:I1:OUT31:> GET https://api.foldingathome.org/machine/DNzCnGbDNT_pOYPJbpo6phuOq-3-euxkgH9kDAbR_-E HTTP/1.1
14:36:34:E :OUT31:Failed response: EOF
14:36:49:I1:OUT32:> GET https://api.foldingathome.org/machine/DNzCnGbDNT_pOYPJbpo6phuOq-3-euxkgH9kDAbR_-E HTTP/1.1
14:36:50:I1:OUT32:< HTTP/1.1 200 HTTP_OK
14:36:50:I1:OUT2:> GET wss://node1.foldingathome.org/ws/client HTTP/1.1
14:36:51:I1:OUT2:< HTTP/1.1 101 HTTP_SWITCHING_PROTOCOLS
14:36:51:I1:Logging into node account
22:23:26:I1:Account websocket closed: PROTOCOL msg=Failed to read header start
22:23:41:W :CON33:DNS lookup failed for api.foldingathome.org
22:23:41:E :OUT33:Failed response: CONNECT
22:24:11:W :CON34:DNS lookup failed for api.foldingathome.org
22:24:11:E :OUT34:Failed response: CONNECT
22:24:48:W :CON35:DNS lookup failed for api.foldingathome.org
22:24:48:E :OUT35:Failed response: CONNECT
22:25:37:W :CON36:DNS lookup failed for api.foldingathome.org
22:25:37:E :OUT36:Failed response: CONNECT
22:26:42:W :CON37:DNS lookup failed for api.foldingathome.org
22:26:42:E :OUT37:Failed response: CONNECT
22:28:07:W :CON38:DNS lookup failed for api.foldingathome.org
22:28:07:E :OUT38:Failed response: CONNECT
22:30:00:W :CON39:DNS lookup failed for api.foldingathome.org
22:30:00:E :OUT39:Failed response: CONNECT
22:32:50:W :CON40:DNS lookup failed for api.foldingathome.org
22:32:50:E :OUT40:Failed response: CONNECT
22:36:50:W :CON41:DNS lookup failed for api.foldingathome.org
22:36:50:E :OUT41:Failed response: CONNECT
22:40:50:W :CON42:DNS lookup failed for api.foldingathome.org
22:40:50:E :OUT42:Failed response: CONNECT
22:44:50:W :CON43:DNS lookup failed for api.foldingathome.org
22:44:50:E :OUT43:Failed response: CONNECT
22:48:50:W :CON44:DNS lookup failed for api.foldingathome.org
22:48:50:E :OUT44:Failed response: CONNECT
22:52:50:W :CON45:DNS lookup failed for api.foldingathome.org
22:52:50:E :OUT45:Failed response: CONNECT
22:56:50:W :CON46:DNS lookup failed for api.foldingathome.org
22:56:50:E :OUT46:Failed response: CONNECT
23:00:50:W :CON47:DNS lookup failed for api.foldingathome.org
23:00:50:E :OUT47:Failed response: CONNECT
23:04:50:W :CON48:DNS lookup failed for api.foldingathome.org
23:04:50:E :OUT48:Failed response: CONNECT
23:08:50:W :CON49:DNS lookup failed for api.foldingathome.org
23:08:50:E :OUT49:Failed response: CONNECT
23:12:50:W :CON50:DNS lookup failed for api.foldingathome.org
23:12:50:E :OUT50:Failed response: CONNECT
23:16:50:W :CON51:DNS lookup failed for api.foldingathome.org
23:16:50:E :OUT51:Failed response: CONNECT
23:20:50:W :CON52:DNS lookup failed for api.foldingathome.org
23:20:50:E :OUT52:Failed response: CONNECT
23:24:50:W :CON53:DNS lookup failed for api.foldingathome.org
23:24:50:E :OUT53:Failed response: CONNECT
23:28:50:W :CON54:DNS lookup failed for api.foldingathome.org
23:28:50:E :OUT54:Failed response: CONNECT
23:32:50:W :CON55:DNS lookup failed for api.foldingathome.org
23:32:50:E :OUT55:Failed response: CONNECT
23:36:50:W :CON56:DNS lookup failed for api.foldingathome.org
23:36:50:E :OUT56:Failed response: CONNECT
23:40:50:I1:OUT57:> GET https://api.foldingathome.org/machine/DNzCnGbDNT_pOYPJbpo6phuOq-3-euxkgH9kDAbR_-E HTTP/1.1
23:40:50:I1:OUT57:< HTTP/1.1 200 HTTP_OK
23:40:51:I1:OUT2:> GET wss://node1.foldingathome.org/ws/client HTTP/1.1
23:40:51:I1:OUT2:< HTTP/1.1 101 HTTP_SWITCHING_PROTOCOLS
23:40:51:I1:Logging into node account
*********************** Log Rotated 2025-11-13T00:00:00Z ***********************

[Malvado]

Or perhaps this info : "23:17:45:I1: Exec: D:\Folding@home\FAHClient\FAHClient.exe
23:17:45:I1:*******************************************************************
23:17:45:I2:<config/>
23:17:45:I1:Opening Database
23:17:45:I1:F@H ID = dvwuJg7TrPFTC7q2X19842i9pTVFFelrmxb6jMqRarU
23:17:45:I3:Loading default resource group
23:17:45:I2:Listening for HTTP on 127.0.0.1:7396
23:17:45:I3:WU31:Loading work unit 31 with ID ecjuRUX1qDmNDTPBNRWuLG73Ty4-Al_ZJzDJqSpGW1U
23:17:45:I3:WU30:Loading work unit 30 with ID j8EAXu9CZUqUjHdQPRxknQufQDg6b7PROKCL7MDN7L0
23:17:45:I3:Loaded 2 wus.
23:17:45:I1:Started Windows systray control
23:17:45:I3:gpus = {
23:17:45:I3: "gpu:03:00:00": {
23:17:45:I3: "vendor": 4098,
23:17:45:I3: "type": "amd",
23:17:45:I3: "description": "gfx1201",
23:17:45:I3: "opencl": {"platform": 1, "device": 1, "compute": "2.0", "driver": "3652.0"},
23:17:45:I3: "uuid": "30303030-3030-3033-3030-303030303030",
23:17:45:I3: "hip": {"platform": 0, "device": 0, "compute": "12.0", "driver": "4515.38"},
23:17:45:I3: "device": 30032,
23:17:45:I3: "supported": true
23:17:45:I3: },
23:17:45:I3: "gpu:14:00:00": {
23:17:45:I3: "vendor": 4098,
23:17:45:I3: "type": "amd",
23:17:45:I3: "description": "gfx1036",
23:17:45:I3: "opencl": {"platform": 1, "device": 0, "compute": "2.0", "driver": "3652.0"},
23:17:45:I3: "device": 5056,
23:17:45:I3: "supported": true
23:17:45:I3: }
23:17:45:I3:}"

[muziqaz]

Please update to the latest beta: foldingathome.org/beta
And use cloudflare DNS
And in the future, if you are "fixing" your opencl in windows registry, you are doing things wrong

[Malvado]

Latest beta is allready in use. All drivers have been cleanly installed again. It seems OpenCL was not correctly added.
I had to create a path to where the correct .dll file was located in registry since there was no mention about OpenCL at all there, even though the .dll files and more was in a folder belonging to Kratos.
regedit
HKEY_LOCAL_MACHINE\SOFTWARE\Khronos\OpenCL\Vendors (Had to add OpenCL and Vendors here)
Added Windows\System32\DriverStore\FileRepository\amdocl.inf_amd64_cef5b52525662fda\amdocl64.dll and made sure it had a value of 0.

Windows 11 pro rev : 25H2

[muziqaz]

Which driver?
Launch Adrenalin control panel from right clicking your desktop and raise a bug report with them about this issue. Please fully explain what happened and what you had to do to get opencl sorted.

This should not be happening in Windows. I have never had to manually force add opencl to any of my Windows systems, and I have gone through massive amount of drivers

[Malvado]

Latest driver. 25.11.1
I have raised a bug report.

It's folding and at the time the 8.5.4 is doing well, stability seems to be ok.
Its weird that using software like Gpu-z can give me ok information, so I wonder if the fault might lie in the difference in where my folding installations are after upgrading and working a bit with a problematic drive.

Edit : Finished the last work units, then removed everything from the system (uninstall and full delete of folders and more) and a cleanup from the registry by regedit. No change, but at least it's a step forward.