[Bug 287453] x11/nvidia-driver: Vulkan and OpenGL are broken on RTX 5000 series

[email protected]
Newsgroups gmane.os.freebsd.devel.x11
Message-ID <[email protected]/bugzilla/>
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=287453

Sean Farley <[email protected]> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |[email protected]

--- Comment #5 from Sean Farley <[email protected]> ---
I have a 4070, so the following may not help any.

First, I would like to note that Firefox is not fully hardware accelerated on
FreeBSD by default.  It requires the multimedia/libva-nvidia-driver port, but I
have not been successful at getting it to work with Firefox.  Check "Decision
Log" under about:support in Firefox to see what it has decided to allow.

Are you running with a compositor?  When picom is running, it causes a stutter
when I move the mouse across the window border of vkcube.  Killing picom fixes
it for me.

If you test with mpv, it should run smoothly once started but have a noticeable
delay at start or finish:
- https://github.com/mpv-player/mpv/issues/13019
- https://github.com/mpv-player/mpv/issues/16218
I have resorted to forcing it to use OpenGL to overcome that.

How do you configure X11?  Do you have the iGPU enabled in the BIOS?  Here are
a few things I added to the Device and Screen sections for both monitors:

Section "Device"
...
        # The BusID is required when the iGPU is enabled in the BIOS.
        BusID       "PCI:1@0:0:0"
...
EndSection

Section "Screen"
...
        # NOTE:  supposedly this helps on Linux but cannot find documentation.
        Option      "UseNvKmsCompositionPipeline" "False"
...
        # Put displays to sleep using VESA DPMS rather than modesets to allow
        # xscreensaver to be more responsive after the monitors wake from
sleep.
        #
        # This may be due to the age of the monitors; newer models may not have
        # the lag where keyboard input is not received by xscreensaver until
the
        # monitor is fully awake.
        Option      "HardDPMS" "False"
...
EndSection

Are you enabling or disabling ForceCompositionPipeline and
ForceFullCompositionPipeline options?  They may not matter for your problem,
but they can cause issues with some apps while helping others.

-- 
You are receiving this mail because:
You are the assignee for the bug.
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.