• Bug#1107887: nvidia-driver: Kernel warnings when opening programs after

    From Andreas Beckmann@21:1/5 to mysha on Thu Jul 31 12:50:02 2025
    Control: tag -1 moreinfo

    On 6/19/25 14:07, mysha wrote:
    After a bit of further debugging it seems that the problem occurs when
    using the nvidia-drm.modeset=1 kernel parameter. Without it the kernel warnings don't appear.

    Does it by chance work again with 550.163.01-2 ?

    Your card (PCI ID 10de:1e84) should also be supported by the nvidia-tesla-535-driver (535.261.03-1). Perhaps you yould try that as well.

    Note that both drivers are co-installable, but the newer one takes
    precedence, so you manually need to switch between them using
    update-glx --config nvidia (and reboot afterwards)
    to activate the Tesla 535 driver.


    Andreas

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From mysha@21:1/5 to Andreas Beckmann on Sat Aug 2 13:30:01 2025
    Unfortunately 550.163.01-2 didn't change anything, still the same
    warining in nv_drm_revoke_modeset_permission+0x327/0x340.
    I'll stay on version 550 for now without modeset enabled, given the other improvements in 550 vs 535.

    Will test any newer driver versions as they come out.


    On Thu, Jul 31, 2025 at 12:45:05PM +0200, Andreas Beckmann wrote:
    Control: tag -1 moreinfo

    On 6/19/25 14:07, mysha wrote:
    After a bit of further debugging it seems that the problem occurs when using the nvidia-drm.modeset=1 kernel parameter. Without it the kernel warnings don't appear.

    Does it by chance work again with 550.163.01-2 ?

    Your card (PCI ID 10de:1e84) should also be supported by the nvidia-tesla-535-driver (535.261.03-1). Perhaps you yould try that as well.

    Note that both drivers are co-installable, but the newer one takes precedence, so you manually need to switch between them using
    update-glx --config nvidia (and reboot afterwards)
    to activate the Tesla 535 driver.


    Andreas

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)