Page 4 of 7 FirstFirst ... 23456 ... LastLast
Results 31 to 40 of 62

Thread: Sudden troubles with nvidia proprietary driver

  1. #31
    Join Date
    Jun 2007
    Beans
    17,215

    Re: Sudden troubles with nvidia proprietary driver

    The patch works but, at least here, there are some issues.
    If I version, i.e
    options nvidia_390_drm modeset=1
    Then nothing happens, kms is not enabled for nvidia

    If I don't version,
    options nvidia_drm modeset=1
    Then modeset for nvidia_drm is enabled but no boot in gdm

    If however I switch to lightdm then it boots & prime sync is realized..

    Edit: regarding gdm, forget that, based on this page, doesn't work
    http://us.download.nvidia.com/XFree8...EADME/kms.html
    Last edited by mc4man; March 15th, 2018 at 05:35 PM.

  2. #32
    Join Date
    Jul 2015
    Beans
    206

    Re: Sudden troubles with nvidia proprietary driver

    I tried to add a module option in nvidia file in /etc/modprobe.d, no sync.
    I added nvidia-drm.modeset=1 in grub boot options and I get sync on both X and (appearing) Wayland sessions. No problems with GDM here.

    Note that the sync is very easy to see in GNOME : overview and desktops dock discovering animation shows what's running...

    Me : Quadro M1000M

  3. #33
    Join Date
    Jun 2007
    Beans
    17,215

    Re: Sudden troubles with nvidia proprietary driver

    Quote Originally Posted by fthx View Post
    I tried to add a module option in nvidia file in /etc/modprobe.d, no sync.
    I added nvidia-drm.modeset=1 in grub boot options and I get sync on both X and (appearing) Wayland sessions. No problems with GDM here.

    Note that the sync is very easy to see in GNOME : overview and desktops dock discovering animation shows what's running...

    Me : Quadro M1000M
    Edit: nothing to do with how kms is enabled, gdm3 won't work on some hardware
    Last edited by mc4man; March 15th, 2018 at 09:52 PM.

  4. #34
    Join Date
    Jul 2015
    Beans
    206

    Re: Sudden troubles with nvidia proprietary driver

    Uh oh, as previously, the Wayland session runs Intel, not Nvidia...

  5. #35
    Join Date
    Jun 2007
    Beans
    17,215

    Re: Sudden troubles with nvidia proprietary driver

    Quote Originally Posted by fthx View Post
    Uh oh, as previously, the Wayland session runs Intel, not Nvidia...
    That's what I saw a couple of weeks ago, then after a few days the wayland session option disappeared.
    Will have to try again on fresh install.
    Sorta gives a means to switch drivers, obviously not ideal.
    Wayland, nvidia & Optimus hardware seems to be a bit of a pipe dream

  6. #36
    Join Date
    Jul 2015
    Beans
    206

    Re: Sudden troubles with nvidia proprietary driver

    I checked powertop and I get roughly 10 W (idle) with Wayland session. When the Nvidia GPU is really disabled, I get less than 4 W (idle).

  7. #37
    Join Date
    Jun 2007
    Beans
    17,215

    Re: Sudden troubles with nvidia proprietary driver

    Did a fresh install, updated, installed nvidia-driver-390
    1. as soon as nvidia driver is detected the option for wayland is removed
    2. gdm3 does not work with nvidia_drm/kms, doesn't matter how it's enabled
    3. lightdm works fine, kms is enabled for nvidia_drm, prime sync works

    So clearly different hardware is going to be treated differently, on this machine NVIDIA GK107M [GeForce GT 755M]

    For me easiest way is to just create a file in /etc/modprobe.d, never needs any attention, is ignored if nvidia drivers are removed.

    For info sake -
    Code:
    sudo nano /etc/modprobe.d/zz-nvidia-modeset.conf
    insert
    Code:
    options nvidia_drm modeset=1
    save, exit nano , run
    Code:
    sudo update-initramfs -u
    reboot with lightdm (- at least for my nvidia chipset
    Last edited by mc4man; March 15th, 2018 at 10:31 PM. Reason: (-

  8. #38
    Join Date
    Jun 2007
    Beans
    17,215

    Re: Sudden troubles with nvidia proprietary driver

    na
    Last edited by mc4man; March 16th, 2018 at 12:21 PM.

  9. #39
    Join Date
    Jul 2015
    Beans
    206

  10. #40
    Join Date
    Jun 2007
    Beans
    17,215

    Re: Sudden troubles with nvidia proprietary driver

    Yeah, it now works thru prime-select, not yet in nvidia-settings
    The end result will be a longer time to switch, the method takes a bit longer & will require a reboot.
    gdm3 previously required a reboot so nothing new to those users, lightdm did thru a log out/in, likely no more..

Page 4 of 7 FirstFirst ... 23456 ... LastLast

Bookmarks

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •