[Bug 52342] Outdated Cuda version

[WineHQ Bugzilla]

https://bugs.winehq.org/show_bug.cgi?id=52342

--- Comment #16 from Moté <automates+bugwine at lepouete.fr> ---
(In reply to Sveinar Søpler from comment #15)
> I do not think "cudart" is a driver library like nvcuda is. Now i do not
> understand much, but cudart64.dll is included with DAZStudio - as something
> the vendors include to do cuda functions... Much the same way games include
> stuff like nvngx_dlss.dll when using dlss with games. "WE" dont need to
> implement nvngx_dlss.dll cos this is the api that "talks to" nvngx.dll.
>
> Developers can i think use cudart64.dll to call various cuda functions FROM
> nvcuda.. somewhat in the same manner games uses nvngx_dlss.dll to call
> various dlss functions from the driver (via nvngx.dll)
> 

That makes sense, and would explain why cudart is furnished by the cuda-toolkit
and not the cuda driver. Then maybe we need to know more about the calls
between the 2 libs? I tried the relay channel with winedebug, but it didn’t
seem to work. 

> I will continue to do some tests here, and hack away at some functions to
> see what comes up. This looks a bit weird in the DAZ log:
> 2022-01-05 22:04:45.278 NVIDIA Iray GPUs:
> 2022-01-05 22:04:45.278 	GPU: 1 - 
> 2022-01-05 22:04:45.278 	Memory Size: -1 bytes
> 2022-01-05 22:04:45.278 	Clock Rate: -1 kHz
> 2022-01-05 22:04:45.278 	Multi Processor Count: -1
> 2022-01-05 22:04:45.278 	CUDA Device ID: -1
> 2022-01-05 22:04:45.278 	CUDA Compute Capability: NA
> 2022-01-05 22:04:45.278 	PCI Bus ID: 6488169
> 2022-01-05 22:04:45.278 	PCI Device ID: 2097253
> 2022-01-05 22:04:45.278 	TCC Mode: disabled
> 2022-01-05 22:04:45.278 	Display: attached
> 
> And the GPU name that shows up in DAZ is also weird, as it seems to just be
> a pointer to something rather than the actual name.. But
> NvAPI_GPU_GetFullName is being called, so that SHOULD get the name. Perhaps
> it tries to pick the GPU info for all of this from nvcuda? Seems weird,
> since the logs does not seem to indicate cuDeviceGetName being called. Maybe
> it is a new (cuda 11+) function for name of adapter and various info that
> has been implemented?

I’m in contact with the dxvk-nvapi developer on the other end, and we were able
to fix the nvapi issues. With it, the full name of my GPU appears in Daz,
alongside the strange Cuda number. And this part now looks like:

> NVIDIA Iray GPUs:
> GPU: 1 - NVIDIA GeForce RTX 3060
> Memory Size: 12.2 GB
> Clock Rate: -1 kHz
> Multi Processor Count: -1
> CUDA Device ID: -1
> CUDA Compute Capability: NA
> PCI Bus ID: 1
> PCI Device ID: 0
> TCC Mode: disabled

We don’t get any more NVAPI calls, so I don’t think the issue is there.

-- 
Do not reply to this email, post in Bugzilla using the
above URL to reply.
You are receiving this mail because:
You are watching all bug changes.