Radeon RX 6800 / 6800 XT / 6900 XT support enabled !

[toTOW]

The new Navi 21 GPUs are now officially enabled in GPUs.txt !

0x73bf = Navi 21 [Radeon RX 6800/6800 XT / 6900 XT]

If you are one of the happy few that have been able to get one, let us know how it works !

[Dampfkanes]

Hello,

do i have to use some special parameters or do i have to load an update?

I'm using a Radeon RX 6800 XT and the slot still gets disabled.



Best Regards,
Tom

[JimboPalmer]

If you delete GPUs.txt on your PC, it should download a new copy from the server.

Let us know if that helps.

[Dampfkanes]

Tanks a lot. That was the solution.
It works pretty well:

[dkinkler]

I unfortunately have a problem with my 6900XT Toxic Extreme, probably because it has some sort of wacky high bin special designation going on. I'd post some details, but it's my first post so I can't link anything. Uh, google "6900xt XTXH" I suppose?

I reinstalled to make sure it wasn't the client and even manually reinstalled GPUs.txt after I reinstalled the FAH client, just to make sure.

Sorry my first post is a complaint!

[muziqaz]

@dkinkler, restart the PC after you create the slot. If that doesn't clear out, we will need PCI-ID of your GPU, which can be found in GPU Z dump file I believe.
@totow can give you exact location where that ID is visible, and he can enable the GPU.
But first try restarting the PC.

[muziqaz]

While I'm here, AMD decided to throttle FAH performance in their 21.4.1 and later drivers by a massive amount. Last best performing driver is 21.3.1

[Joe_H]

The GPU-Z screenshot shows the same PCI device ID as was recently requested to be added in this topic - viewtopic.php?f=83&t=37201. Delete your copy of GPUs.txt and let the client download a new one after restarting your system. The client should be able to properly detect your variant of the 6900 XT.

You may still run into issues with getting the AMD Radeon and your nVidia GTX 1070 to run together. That has been an ongoing problem with F@h configurations with mixed GPU vendors in a single system. It works for some, but others run into issues.

[bruce]

I have confirmed that 1002:73af is in the latest version of GPUs.txt. Have you rebooted after deleting GPUs.txt from the FAH Data directory?

[muziqaz]

I wonder why client does not fetch the latest GPU.txt with new GPU automatically?

[Joe_H]

I wonder why client does not fetch the latest GPU.txt with new GPU automatically?

They are in the initial phase of trying to automate adding new GPUs. That is the whole detect a GPU not listed or enabled and use the beta GPU option bit that shows up in logs. It only partly works so far, and they may not have thought of adding a branch to do that since a new install of the client would get the latest GPUs.txt anyways.

[muziqaz]

I wonder why client does not fetch the latest GPU.txt with new GPU automatically?

They are in the initial phase of trying to automate adding new GPUs. That is the whole detect a GPU not listed or enabled and use the beta GPU option bit that shows up in logs. It only partly works so far, and they may not have thought of adding a branch to do that since a new install of the client would get the latest GPUs.txt anyways.

No no, the new system is still far away, I'm not talking about that. I'm talking about client seeing new GPU slot and then downloading new GPU.txt copy, if that GPU wasn't run before. I thought that was in already alongside autodownload of GPU.txt when client is installed and GPU is detected

[Joe_H]

No, the initial install always downloads a copy of GPUs.txt. It even does it on the Mac client that does not do any configuration of a GPU anyways, and has been doing it since before the 7.5.1 release.

The auto detect is there in the 7.6.21 client. Look at the log in the other topic on this variant of the 6900 XT with this device ID of 1002:73af:

Code: Select all

 06:29:48:           GPUs: 1
06:29:48:          GPU 0: Bus:3 Slot:0 Func:0 AMD:1
06:29:48:           CUDA: Not detected: Failed to open dynamic library 'nvcuda.dll': The
06:29:48:                 specified module could not be found.
06:29:48:
06:29:48:OpenCL Device 0: Platform:0 Device:0 Bus:3 Slot:0 Compute:1.2 Driver:3240.6
06:29:48:***********************************************************************
06:29:48:<config>
06:29:48:  <!-- Network -->
06:29:48:  <proxy v=':8080'/>
06:29:48:
06:29:48:  <!-- Slot Control -->
06:29:48:  <pause-on-battery v='false'/>
06:29:48:  <power v='FULL'/>
06:29:48:
06:29:48:  <!-- User Information -->
06:29:48:  <passkey v='*****'/>
06:29:48:  <team v='226715'/>
06:29:48:  <user v='DJfCZPFxVokzAzHXEGvmjNBRDmis3xBjyr'/>
06:29:48:
06:29:48:  <!-- Folding Slots -->
06:29:48:  <slot id='0' type='CPU'/>
06:29:48:  <slot id='2' type='GPU'/>
06:29:48:</config>
06:29:48:Trying to access database...
06:29:48:Successfully acquired database lock
06:29:48:FS00:Initialized folding slot 00: cpu:15
06:29:48:WARNING:FS02:Disabling beta GPU slot 02: gpu:3:0.  Beta GPUs can be tested for no points by setting ``gpu-beta=true`` in the configuration.

This is an initial install or shortly afterwards, downloading another copy of the same GPUs.txt file is not going to change anything until either the file is updated manually or the slot is enabled with the gpu-beta option set and a WU from that is processed and uploaded. There have been a few GPUs added through this option, but it is not consistently working. And there often are no WUs available for this GPU beta test setting.

[muziqaz]

Well, current new GPU detection behavior is seriously messed up. These simplest things, like pushing GPU.txt update to newly added slots if fahclient was restarted should be default behavior. Oh well, we were pi**ing into the wind before regarding this anyways

[dkinkler]

Thanks for all your help - I don't restart this system often enough since I like to run Metashape at night, then have FAH use the remaining cycles.

To be clear to anyone who googles this in a decade, the full system restart worked after I replaced GPUs.txt , the 5/23/21 GPUs.txt didn't recognize it.