“Well… still nothing with the 455.50.02 driver…”???
What are you talking about?
Why are you still using 455.xx?
What about the 455.xx.xx Driver? nVidia Driver 460 has been out for a month?
Did you not read the nVidia-460-Driver release? See anything different??
Are you using kernel 5.10.6+ ?
Plently of people are playing CyberPunk as well as it can be played.
Its a rubbish unicorn evaluation scam junk thing anyway.
Or is it you just love Keanu?
See ProtonDB, Proton_Github, Reddit, YouTube…People that have rtfm are good to go.
Your on a nVidia Linux Dev. Forum and your contribution is:
- “Well… still nothing with the 455.50.02 driver…”
- Guess its time to jump ship and go AMD. Atleast you are not 100% in the hands of whimsy companies that cba to implement stuff ppl want"
Is your System even close to being configured properly?
You could have provided your full-system logs and output and got some feed back as what needs to be fixed.
Where your going wrong because you havent read the manual.
Have you benched the graphics acceleration and system performance?
Is it on OpenBenchmarch?
So this awesome gaming rig of yours:…
Is the hardware matched? and the nVidia Card is in the correct PCI-e slot? for the read and addressing?
Is it some AMD boards that address PCI backwards on Linux?
Was your Mboard state setting confirmed as Pure UEFI-BIOS ? before you installed your Linux Distro?
Did you update UEFI-BIOS before you installed your Distro. and nVidia-Driver?
And SecureBoot was [DISABLED] ? and CSM [DISABLED] ? and these remained [DISABLED]? ,
and CPU PAT [ ENABLED ] in the BIOS aswell if applicable?
On Board or UEFI-BIOS IGP or DGP graphics turbo boost [ Disabled] if needed
SecureBoot can cause instability, instalation and poor performance on DKMS built modules?
ie: usually wireless.
And PCI-e 64-bit BAR Support is [ ENABLED ] in theUEFI-BIOS ?
And you’ve confirmed your GPU / System Addressing is in sync and then increased the size of the DMA-Buffer so its not defaulting to a legacy 32-bits expansion ROM protocol with a max allowed access to 4G of RAM?
And because the nVidia Driver doesnt support “SWIOTLB” . A Hardware specific solution to the “SWIOTLB” issue has been Applied? Like the generic ‘iommu=memaper’ kernel parameter.
When the nVidia Driver was installed did you kill X11 and all running GL Applications. Then once the driver was installed you checked that the “GLX” and “NV-GLX” extensions are present, symlinking is correct and the correct libraries and pointers are being used? and confirmed no theres no Cache Aliasing?
And also checked that theres no incorrect and simulateous conflicting usage of FXAA, UUD, Full-composition Pipline and other antialiasing methods? or conflicts.
And after install was PCI.ID update run from a recent repository source? And FirmwareUpdate and Lm-sensors --recommends? and extended ACPI functionality set up?
And no 3rd Party powermanagerment Apps or consertive CPU scheduler have been installed ?.
Should UBB enabled? Color depth right for the App? Are the Monitor(s) being over driven by the GPU?
Is Buffer allocation and submission to DRM KMS and Gnome GDM Display manager being used? Thats a problem.
Are the nVidia recommended number of allocated video surfaces being used by NVIDIA VDPAU?
Are the official recommended boleans being used?
Is the change in default OpenGL/Vulkan Shader Disk Caches location and size being utilized? 128MB to 1024MB
This is a slice odf the options for the driver.
AMD Open Source Graphics ???
maybe ColecoVision is more your style. :}
Learn more: Do more: Get More…
Its all in the readme.