You are not logged in.

#1 2025-02-09 11:11:05

StopkaPeter
Member
From: Slovakia
Registered: 2019-05-20
Posts: 31

Question on the wiki regarding KMS and Nvidia

On the wiki, it says:
Remove kms from the HOOKS array in /etc/mkinitcpio.conf and regenerate the initramfs. This will prevent the initramfs from containing the nouveau module making sure the kernel cannot load it during early boot.

Do I understand it correctly that if I remove kms from the hooks in /etc/mkinitcpio.conf, it will prevent the newly generated initramfs from containing the nouveau driver?

However, later it says this:
Since NVIDIA does not support automatic KMS late loading, enabling DRM (Direct Rendering Manager) kernel mode setting is required to make Wayland compositors function properly
Do I understand it correctly that Nvidia does not support late KMS, but KMS is required for Wayland to function properly.
However, later it says this:
The proprietary NVIDIA driver supports KMS (since 364.12), which has to be manually enabled.

To summarize everything, I understand it like this:
Nvidia drivers support KMS (since version 364.12), but they do not support LATE KMS. For proper Wayland functionality, KMS must be activated, so the only option is EARLY KMS by setting nvidia_drm.modeset=1, which is set by default since version nvidia-utils 560.35.03-5, so there's no need to set it manually. My question is:
Should I remove kms from the HOOKS in mkinitcpio.conf or not? Because KMS is needed, or is the specific kms hook only for Intel, AMD, and Mesa drivers?

Last edited by StopkaPeter (2025-02-09 22:05:27)

Offline

#2 2025-02-09 11:28:15

Lone_Wolf
Administrator
From: Netherlands, Europe
Registered: 2005-10-04
Posts: 13,408

Re: Question on the wiki regarding KMS and Nvidia

Is there a question ?

Also please use a descriptive title.


Disliking systemd intensely, but not satisfied with alternatives so focusing on taming systemd.

clean chroot building not flexible enough ?
Try clean chroot manager by graysky

Offline

Board footer

Powered by FluxBB