1. Forum
  2. Usenet
  3. LINUX.DEBIAN.USER

  • secure boot key enrolling questions

    From Anil F Duggirala@21:1/5 to All on Sun Jan 5 05:40:01 2025
    hello everyone,

    I am looking to install the Nvidia proprietary driver in my Debian 12 machine. This is a clean install on a Dell XPS 9550 laptop.

    I have Secure boot enabled. The instructions say that I need to enroll an mok key (have no idea what that means).

    Running the command: sudo mokutil --import /var/lib/dkms/mok.pub
    Outputs: Failed to get file status, /var/lib/dkms/mok.pub

    There is in fact no folder named dkms in my /var/lib directory.

    I appreciate your help,

    thank you,

    Anil F

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Anil F Duggirala@21:1/5 to All on Sun Jan 5 14:30:01 2025
    Thank you both for your instructions. I have followed the exact
    instructions as proposed by Oli and have managed to successfully
    install and load the nvidia driver.

    However, apparently I am now stuck in an X session instead of the
    Wayland session I had before.

    I have followed the additional instruction here https://wiki.debian.org/NvidiaGraphicsDrivers#Debian_12_.22Bookworm.22
    and have run the command:
    echo "options nvidia-drm modeset=1" >> /etc/modprobe.d/nvidia-
    options.conf

    and now, cat /sys/module/nvidia_drm/parameters/modeset, outputs: Y

    My laptop has both and integrated card and the Nvidia card. I have read
    the instructions here:
    https://wiki.debian.org/NVIDIA%20Optimus#PRIMEOffload

    I don't really understand the second paragraph there, where it says
    that it should just work out of the box but also recommends some
    additional steps. Should I uninstall the xserver-xorg-video-intel
    package as suggested there?

    Should I be getting an option to select Wayland instead of Xorg at
    login? I'm not sure I had that option before.

    I am only using my laptop's screen right now,

    thank you very much,

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From George at Clug@21:1/5 to All on Sun Jan 5 15:00:01 2025
    Are you using Gnome or KDE? (or something else). I ask this as my KDE with the packaged Nvidia 535 drivers is unable to run Wayland. So for now I use X11 with KDE.

    It is my understanding that KDE will work with Wayland when using the Nvidia stable version 560.35.03 however this version has yet to be packaged for/by Debian. I look forward to when this version (or later) has been packaged.

    https://www.nvidia.com/en-us/drivers/details/230918/
    Linux x64 (AMD64/EM64T) Display Driver 560.35.03 | Linux 64-bit
    Drivers Home > Linux x64 (AMD64/EM64T) Display Driver


    George.



    On Monday, 06-01-2025 at 00:03 Anil F Duggirala wrote:
    Thank you both for your instructions. I have followed the exact
    instructions as proposed by Oli and have managed to successfully
    install and load the nvidia driver.

    However, apparently I am now stuck in an X session instead of the
    Wayland session I had before.

    I have followed the additional instruction here https://wiki.debian.org/NvidiaGraphicsDrivers#Debian_12_.22Bookworm.22
    and have run the command:
    echo "options nvidia-drm modeset=1" >> /etc/modprobe.d/nvidia-
    options.conf

    and now, cat /sys/module/nvidia_drm/parameters/modeset, outputs: Y

    My laptop has both and integrated card and the Nvidia card. I have read
    the instructions here:
    https://wiki.debian.org/NVIDIA%20Optimus#PRIMEOffload

    I don't really understand the second paragraph there, where it says
    that it should just work out of the box but also recommends some
    additional steps. Should I uninstall the xserver-xorg-video-intel
    package as suggested there?

    Should I be getting an option to select Wayland instead of Xorg at
    login? I'm not sure I had that option before.

    I am only using my laptop's screen right now,

    thank you very much,



    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Nicolas George@21:1/5 to All on Sun Jan 5 17:20:01 2025
    Anil F Duggirala (12025-01-05):
    sudo mv /usr/lib/udev/rules.d/61-gdm.rules /usr/lib/udev/rules.d/61- gdm.rules.bak

    Unrelated to the actual issue: IIRC you can achieve the same result of disabling a system udev rule by creating an empty rule file in /etc with
    the exact same name. It has the benefit of not being overwritten on the
    next upgrade.

    Regards,

    --
    Nicolas George

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Anil F Duggirala@21:1/5 to All on Sun Jan 5 17:20:01 2025
    Thank you Olafur and George for your answers.

    I am using Gnome, so that is not the issue here.

    Doing: 
    sudo mv /usr/lib/udev/rules.d/61-gdm.rules /usr/lib/udev/rules.d/61- gdm.rules.bak

    Worked for me. I get gdm with options and Wayland by default. I'm back
    in business thanks to you.

    I however did follow a bunch of other instructions and now I don't if I
    should undo any of them. These are the things I did, in case you can
    provide some input:

    1. echo "options nvidia-drm modeset=1" >> /etc/modprobe.d/nvidia-
    options.conf

    2. echo 'GRUB_CMDLINE_LINUX="$GRUB_CMDLINE_LINUX nvidia-drm.modeset=1"'
    /etc/default/grub.d/nvidia-modeset.cfg

    3. # systemctl enable nvidia-suspend.service
    # systemctl enable nvidia-hibernate.service
    # systemctl enable nvidia-resume.service

    4. echo 'options nvidia NVreg_PreserveVideoMemoryAllocations=1' > /etc/modprobe.d/nvidia-power-management.conf

    5. apt remove xserver-xorg-video-intel. (gave me an error on one boot
    (wifi?) but the error didn't come up in subsequent boots).

    And finally I did:
    6. sudo mv /usr/lib/udev/rules.d/61-gdm.rules /usr/lib/udev/rules.d/61- gdm.rules.bak

    I can try renaming back the gdm.rules and only commenting out the gdm- runtime-config, if that is what you recommend?

    Should I undo any of the steps listed above for some reason?

    thank you,

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From David Wright@21:1/5 to Nicolas George on Sun Jan 5 18:30:01 2025
    On Sun 05 Jan 2025 at 17:17:32 (+0100), Nicolas George wrote:
    Anil F Duggirala (12025-01-05):
    sudo mv /usr/lib/udev/rules.d/61-gdm.rules /usr/lib/udev/rules.d/61- gdm.rules.bak

    Unrelated to the actual issue: IIRC you can achieve the same result of disabling a system udev rule by creating an empty rule file in /etc with
    the exact same name. It has the benefit of not being overwritten on the
    next upgrade.

    In the light of:
    https://lists.debian.org/debian-user/2024/12/msg01031.html
    it might be worth noting that "in /etc" would here mean:
    /etc/udev/rules.d/61-gdm.rules

    Cheers,
    David.

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