Secure boot and mokutil --disable-validation

English Install/Boot/Login
1

Lately I have been unable to update my system because the nvidia driver will not register and thus no blue MOK screen appears on boot to enroll the kernel driver.
I have been searching around the net a lot, and have a theory about why this is. None of the proposed solutions I have found works for me. I will start a new conversation concerning this, but for now I will simply ask if

mokutil --disable-validation

will solve the problem for now.

  • The system is tumbleweed with dual boot windows 11
  • Will windows be affected?
  • Will I need to do some changes in the grub booting, and if so why and how? Some threads hints to this, but I am unable to understand exactly.
2

It is difficult to say because your problem is rather unclear.

No.

3

I am aware that it will not solve the underlying problem, but my question is more like:
Will the nvidia kernel module be loaded at boot, and might I expect any problems.

4

Nobody can tell if you do not describe the real problem.
Show installed driver packages:
zypper se -si nvidia
Show inxi:
inxi -GSaz

If we can solve the base issue, there is no need to disable secure boot.

5

I have started a separate conversation on the bas problem
https://forums.opensuse.org/t/problems-enrolling-nvidia-driver-when-sys-firmware-efi-efivars-is-full/188547

tmp:bash$ zypper se -si nvidia
Laster pakkebrønndata...
Leser installerte pakker...

S  | Name                          | Type  | Version                  | Arch   | Repository
---+-------------------------------+-------+--------------------------+--------+------------------------
i+ | kernel-firmware-nvidia        | pakke | 20250516-4.1             | noarch | repo-oss
i+ | libnvidia-egl-gbm1            | pakke | 1.1.2-7.14               | x86_64 | nVidia Graphics Drivers
i+ | libnvidia-egl-gbm1-32bit      | pakke | 1.1.2-7.9                | x86_64 | nVidia Graphics Drivers
i+ | libnvidia-egl-wayland1        | pakke | 1.1.20-1.1               | x86_64 | repo-oss
i+ | libnvidia-egl-wayland1-32bit  | pakke | 1.1.20-51.1              | x86_64 | nVidia Graphics Drivers
i+ | libnvidia-egl-x111            | pakke | 1.0.3-21.1               | x86_64 | nVidia Graphics Drivers
i+ | libnvidia-egl-x111-32bit      | pakke | 1.0.3-21.1               | x86_64 | nVidia Graphics Drivers
i+ | libnvidia-gpucomp             | pakke | 580.76.05-39.1           | x86_64 | nVidia Graphics Drivers
i+ | libnvidia-gpucomp-32bit       | pakke | 580.76.05-39.1           | x86_64 | nVidia Graphics Drivers
i+ | nvidia-common-G06             | pakke | 580.76.05-39.1           | x86_64 | nVidia Graphics Drivers
i+ | nvidia-compute-G06            | pakke | 580.76.05-39.1           | x86_64 | nVidia Graphics Drivers
i+ | nvidia-compute-G06-32bit      | pakke | 580.76.05-39.1           | x86_64 | nVidia Graphics Drivers
i+ | nvidia-compute-utils-G06      | pakke | 580.76.05-39.1           | x86_64 | nVidia Graphics Drivers
i+ | nvidia-driver-G06-kmp-default | pakke | 580.76.05_k6.15.8_1-39.1 | x86_64 | nVidia Graphics Drivers
i+ | nvidia-gl-G06                 | pakke | 580.76.05-39.1           | x86_64 | nVidia Graphics Drivers
i+ | nvidia-gl-G06-32bit           | pakke | 580.76.05-39.1           | x86_64 | nVidia Graphics Drivers
i+ | nvidia-modprobe               | pakke | 580.76.05-17.1           | x86_64 | nVidia Graphics Drivers
i+ | nvidia-persistenced           | pakke | 580.76.05-2.1            | x86_64 | nVidia Graphics Drivers
i+ | nvidia-userspace-meta-G06     | pakke | 580.76.05-11.1           | noarch | nVidia Graphics Drivers
i+ | nvidia-userspace-meta-G06     | pakke | 580.76.05-11.1           | noarch | nVidia Graphics Drivers
i+ | nvidia-video-G06              | pakke | 580.76.05-39.1           | x86_64 | nVidia Graphics Drivers
i+ | nvidia-video-G06-32bit        | pakke | 580.76.05-39.1           | x86_64 | nVidia Graphics Drivers
tmp:bash$ inxi -GSaz
System:
  Kernel: 6.16.1-1-default arch: x86_64 bits: 64 compiler: gcc v: 15.1.1
    clocksource: tsc avail: acpi_pm
    parameters: BOOT_IMAGE=/boot/vmlinuz-6.16.1-1-default
    root=UUID=47285fc1-4710-45c9-ae2d-babb552c716c splash=silent
    resume=/dev/disk/by-uuid/d41f0843-8282-4dcf-acbe-45d894ff6e19
    mitigations=auto quiet security=apparmor rd.driver.blacklist=nouveau
  Desktop: KDE Plasma v: 6.4.4 tk: Qt v: N/A info: frameworks v: 6.17.0
    wm: kwin_x11 tools: avail: xscreensaver vt: 2 dm: SDDM Distro: openSUSE
    Tumbleweed 20250820
Graphics:
  Device-1: NVIDIA AD103 [GeForce RTX 4070 Ti SUPER] vendor: ASUSTeK
    driver: nvidia v: 580.76.05 alternate: nouveau,nvidia_drm
    non-free: 550/565.xx+ status: current (as of 2025-01) arch: Lovelace
    code: AD1xx process: TSMC n4 (5nm) built: 2022+ pcie: gen: 4
    speed: 16 GT/s lanes: 16 ports: active: none off: DP-3
    empty: DP-1,DP-2,HDMI-A-1 bus-ID: 01:00.0 chip-ID: 10de:2705
    class-ID: 0300
  Display: x11 server: X.Org v: 21.1.15 with: Xwayland v: 24.1.8
    compositor: kwin_x11 driver: X: loaded: nvidia unloaded: modesetting,vesa
    alternate: fbdev,nouveau,nv gpu: nvidia,nvidia-nvswitch display-ID: :0
    screens: 1
  Screen-1: 0 s-res: 3440x1440 s-dpi: 110 s-size: 794x333mm (31.26x13.11")
    s-diag: 861mm (33.9")
  Monitor-1: DP-3 mapped: DP-4 note: disabled model: MSI MAG342CQR
    serial: <filter> built: 2024 res: N/A dpi: 111 gamma: 1.2
    size: 790x330mm (31.1x12.99") diag: 864mm (34") modes: max: 3440x1440
    min: 640x480
  API: EGL v: 1.5 hw: drv: nvidia platforms: device: 0 drv: nvidia device: 2
    drv: swrast gbm: drv: nvidia surfaceless: drv: nvidia x11: drv: nvidia
    inactive: wayland,device-1
  API: OpenGL v: 4.6.0 compat-v: 4.5 vendor: nvidia mesa v: 580.76.05
    glx-v: 1.4 direct-render: yes renderer: NVIDIA GeForce RTX 4070 Ti
    SUPER/PCIe/SSE2 memory: 15.62 GiB
  API: Vulkan v: 1.4.321 layers: 7 device: 0 type: discrete-gpu name: NVIDIA
    GeForce RTX 4070 Ti SUPER driver: N/A device-ID: 10de:2705 surfaces: N/A
    device: 1 type: cpu name: llvmpipe (LLVM 20.1.8 256 bits) driver: N/A
    device-ID: 10005:0000 surfaces: N/A
  Info: Tools: api: clinfo, eglinfo, glxinfo, vulkaninfo
    de: kscreen-console,kscreen-doctor gpu: nvidia-smi wl: wayland-info
    x11: xdpyinfo, xprop, xrandr
6

Hi, your way behind the eight ball here kernel wise? Tumbleweed is on 6.17.0-1-default now?

7

Thats becsause I havent been able to update for some time due to the problem mentioned in this conversation…

8

@paslotte you probably need to resolve the other issue first, but until you get up to date on the latest snapshot it will be hard to provide any help… You might wish to disable validation and run zypper -vvv dup.

9

My problem is not that the update does not work. It runs OK, but afterwords I have no graphics so I must do a “snapper rollback”
Do you recomend a " mokutil --disable-validation" followed by an update?

10

@paslotte so press ctl+alt+F1 to get to a terminal login or I would suggest booting to multi-user target (terminal login [called tty or vt]) and run a zypper -vvv dup and reboot.

11

Which will give me a system without the nvidia kernel module, and hence no workable graphics. As long as I have no clue related to what to do next that is not an option for me.

12

@paslotte then your in a rock and a hard place if your not willing to try and see what happens… Many of the modules have moved on to the new kernels and a built for that newer kernel, not your running one?

You can see the current via running zypper se -s nvidia likewise not sure why you don’t run the open version as this has better support for you GPU, as in it gets more fixes for newer GPU’s than the proprietary as this is really only supporting older cards these days ?

Your so far behind it’s going to take some effort on your part to get it working, else you might be better of switching to Leap or Slowroll?

13

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.