luc@fedora:~$ ps aux | grep kmod
luc 60180 0.0 0.0 227788 2176 pts/1 S+ 23:57 0:00 grep --color=auto kmod
That single line is exactly what I suggested above.
hello and thanks for your advises, so it seems that i should finally be fine, with those nvidia drivers ?
Only you can tell us the results of following the suggested actions.
Have you completed the suggested steps and then rebooted to see if everything worked as expected?
yes i did every steps provided here , did a reboot and send you the result of : ps aux | grep kmod. I also check systemctl list-jobs it returns : No jobs running.
and systemctl status give
luc@fedora40:~$ systemctlstatus
bash: systemctlstatus: command not found...
luc@fedora40:~$ systemctl status
● fedora40
State: running
Units: 513 loaded (incl. loaded aliases)
Jobs: 0 queued
Failed: 0 units
Since: Sun 2024-07-07 19:49:20 CEST; 1min 15s ago
systemd: 255.8-1.fc40
CGroup: /
├─init.scope
│ └─1 /usr/lib/systemd/systemd --switched-root --system --deserializ>
├─system.slice
│ ├─ModemManager.service
│ │ └─1212 /usr/sbin/ModemManager
│ ├─NetworkManager.service
│ │ └─1246 /usr/sbin/NetworkManager --no-daemon
│ ├─abrt-journal-core.service
│ │ └─1234 /usr/bin/abrt-dump-journal-core -D -T -f -e
│ ├─abrt-oops.service
│ │ └─1241 /usr/bin/abrt-dump-journal-oops -fxtD
│ ├─abrt-xorg.service
│ │ └─1242 /usr/bin/abrt-dump-journal-xorg -fxtD
│ ├─abrtd.service
│ │ └─1207 /usr/sbin/abrtd -d -s
│ ├─accounts-daemon.service
│ │ └─939 /usr/libexec/accounts-daemon
│ ├─alsa-state.service
│ │ └─1216 /usr/sbin/alsactl -s -n 19 -c -E ALSA_CONFIG_PATH=/etc/al>
│ ├─auditd.service
│ │ └─898 /usr/sbin/auditd
│ ├─avahi-daemon.service
│ │ ├─918 "avahi-daemon: running [fedora40.local]"
│ │ └─978 "avahi-daemon: chroot helper"
│ ├─chronyd.service
│ │ └─1091 /usr/sbin/chronyd -F 2
│ ├─colord.service
│ │ └─3577 /usr/libexec/colord
│ ├─crond.service
│ │ └─3040 /usr/sbin/crond -n
│ ├─cups.service
│ │ └─1316 /usr/sbin/cupsd -l
│ ├─dbus-broker.service
│ │ ├─910 /usr/bin/dbus-broker-launch --scope system --audit
│ │ └─915 dbus-broker --log 4 --controller 9 --machine-id 8ca966e5e3>
│ ├─firewalld.service
│ │ └─1217 /usr/bin/python3 -sP /usr/sbin/firewalld --nofork --nopid
│ ├─flatpak-system-helper.service
│ │ └─5766 /usr/libexec/flatpak-system-helper
│ ├─fwupd.service
│ │ └─5411 /usr/libexec/fwupd/fwupd
│ ├─gdm.service
│ │ └─3057 /usr/sbin/gdm
│ ├─geoclue.service
│ │ └─3935 /usr/libexec/geoclue
│ ├─gssproxy.service
│ │ └─1391 /usr/sbin/gssproxy -D
│ ├─low-memory-monitor.service
│ │ └─921 /usr/libexec/low-memory-monitor
│ ├─mcelog.service
│ │ └─924 /usr/sbin/mcelog --daemon --foreground
│ ├─ollama.service
│ │ └─3005 /usr/local/bin/ollama serve
│ ├─packagekit.service
│ │ └─3627 /usr/libexec/packagekitd
│ ├─passim.service
│ │ └─5459 /usr/libexec/passimd
│ ├─pcscd.service
│ │ └─3739 /usr/sbin/pcscd --foreground --auto-exit
│ ├─piavpn.service
│ │ └─1320 /opt/piavpn/bin/pia-daemon
│ ├─polkit.service
│ │ └─932 /usr/lib/polkit-1/polkitd --no-debug
│ ├─power-profiles-daemon.service
│ │ └─934 /usr/libexec/power-profiles-daemon
│ ├─realmd.service
│ │ └─3988 /usr/libexec/realmd
│ ├─rtkit-daemon.service
│ │ └─937 /usr/libexec/rtkit-daemon
│ ├─sshd.service
│ │ └─1322 "sshd: /usr/sbin/sshd -D [listener] 0 of 10-100 startups"
│ ├─sssd-kcm.service
│ │ └─5067 /usr/libexec/sssd/sssd_kcm --uid 0 --gid 0 --logger=files
│ ├─switcheroo-control.service
│ │ └─940 /usr/libexec/switcheroo-control
│ ├─system-dbus\x2d:1.3\x2dorg.freedesktop.problems.slice
│ │ └─dbus-:1.3-org.freedesktop.problems@0.service
│ │ └─5155 /usr/sbin/abrt-dbus -t133
│ ├─systemd-homed.service
│ │ └─947 /usr/lib/systemd/systemd-homed
│ ├─systemd-hostnamed.service
│ │ └─1260 /usr/lib/systemd/systemd-hostnamed
│ ├─systemd-journald.service
│ │ └─647 /usr/lib/systemd/systemd-journald
│ ├─systemd-localed.service
│ │ └─4905 /usr/lib/systemd/systemd-localed
│ ├─systemd-logind.service
│ │ └─952 /usr/lib/systemd/systemd-logind
│ ├─systemd-machined.service
│ │ └─953 /usr/lib/systemd/systemd-machined
│ ├─systemd-oomd.service
│ │ └─863 /usr/lib/systemd/systemd-oomd
│ ├─systemd-resolved.service
│ │ └─866 /usr/lib/systemd/systemd-resolved
│ ├─systemd-udevd.service
│ │ └─udev
│ │ └─698 /usr/lib/systemd/systemd-udevd
│ ├─systemd-userdbd.service
│ │ ├─ 679 /usr/lib/systemd/systemd-userdbd
│ │ ├─5597 "systemd-userwork: waiting..."
│ │ ├─5776 "systemd-userwork: waiting..."
│ │ └─5806 "systemd-userwork: waiting..."
│ ├─udisks2.service
│ │ └─961 /usr/libexec/udisks2/udisksd
│ ├─upower.service
│ │ └─966 /usr/libexec/upowerd
│ ├─uresourced.service
│ │ └─3253 /usr/libexec/uresourced
│ ├─virtqemud.service
│ │ └─3025 /usr/sbin/virtqemud --timeout 120
│ └─wpa_supplicant.service
│ └─3958 /usr/sbin/wpa_supplicant -c /etc/wpa_supplicant/wpa_suppl>
└─user.slice
└─user-1000.slice
├─session-2.scope
│ ├─4060 "gdm-session-worker [pam/gdm-password]"
│ ├─4112 /usr/bin/gnome-keyring-daemon --daemonize --login
│ ├─4145 /usr/libexec/gdm-x-session --run-script /usr/bin/gnome->
│ ├─4147 /usr/libexec/Xorg vt2 -displayfd 3 -auth /run/user/1000>
│ ├─4237 /usr/libexec/gnome-session-binary
│ └─4351 /usr/bin/ssh-agent /bin/sh -c "exec -l /bin/bash -c \"/>
└─user@1000.service
├─app.slice
│ ├─app-gnome-org.gnome.Evolution\x2dalarm\x2dnotify-4775.scope
│ │ └─4775 /usr/libexec/evolution-data-server/evolution-alarm->
│ ├─app-gnome-org.gnome.SettingsDaemon.DiskUtilityNotify-4786.>
│ │ └─4786 /usr/libexec/gsd-disk-utility-notify
│ ├─app-gnome-org.gnome.Software-4860.scope
│ │ └─4860 /usr/bin/gnome-software --gapplication-service
│ ├─app-gnome\x2dsession\x2dmanager.slice
│ │ └─gnome-session-manager@gnome.service
│ │ └─4562 /usr/libexec/gnome-session-binary --systemd-servi>
│ ├─app-org.gnome.Terminal.slice
│ │ ├─gnome-terminal-server.service
│ │ │ └─5612 /usr/libexec/gnome-terminal-server
│ │ └─vte-spawn-baf46268-1797-4fa4-af6e-c8c8a049423b.scope
│ │ ├─5623 bash
│ │ ├─5844 systemctl status
│ │ └─5845 less
│ ├─dbus-:1.2-org.freedesktop.portal.IBus@0.service
│ │ └─4947 /usr/libexec/ibus-portal
│ ├─dbus-:1.2-org.freedesktop.problems.applet@0.service
│ │ └─4949 /usr/bin/abrt-applet --gapplication-service
│ ├─dbus-:1.2-org.gnome.Epiphany.WebAppProvider@0.service
│ │ └─5408 /usr/libexec/epiphany-webapp-provider
│ ├─dbus-:1.2-org.gnome.Identity@0.service
│ │ └─5023 /usr/libexec/goa-identity-service
│ ├─dbus-:1.2-org.gnome.OnlineAccounts@0.service
│ │ └─4966 /usr/libexec/goa-daemon
│ ├─dbus-:1.2-org.gnome.ScreenSaver@0.service
│ │ └─4954 /usr/bin/gjs -m /usr/share/gnome-shell/org.gnome.Sc>
│ ├─dbus-:1.2-org.gnome.Shell.CalendarServer@0.service
│ │ └─4693 /usr/libexec/gnome-shell-calendar-server
│ ├─dbus-:1.2-org.gnome.Shell.Notifications@0.service
│ │ └─4724 /usr/bin/gjs -m /usr/share/gnome-shell/org.gnome.Sh>
│ ├─dbus-:1.6-org.a11y.atspi.Registry@0.service
│ │ └─4664 /usr/libexec/at-spi2-registryd --use-gnome-session
│ ├─dconf.service
│ │ └─4709 /usr/libexec/dconf-service
│ ├─evolution-addressbook-factory.service
│ │ └─5080 /usr/libexec/evolution-addressbook-factory
│ ├─evolution-calendar-factory.service
│ │ └─5022 /usr/libexec/evolution-calendar-factory
│ ├─evolution-source-registry.service
│ │ └─4707 /usr/libexec/evolution-source-registry
│ ├─gnome-session-monitor.service
│ │ └─4557 /usr/libexec/gnome-session-ctl --monitor
│ ├─synergy.service
│ │ ├─4558 /opt/Synergy/synergy-service -d
│ │ ├─4653 /opt/Synergy/resources/synergy-tray
│ │ └─4657 /opt/Synergy/synergy-core server -f --no-tray --ipc>
│ ├─tracker-miner-fs-3.service
│ │ └─5380 /usr/libexec/tracker-miner-fs-3
│ ├─xdg-desktop-portal-gnome.service
│ │ └─5206 /usr/libexec/xdg-desktop-portal-gnome
│ └─xdg-desktop-portal-gtk.service
│ └─5364 /usr/libexec/xdg-desktop-portal-gtk
├─init.scope
│ ├─4074 /usr/lib/systemd/systemd --user
│ └─4083 "(sd-pam)"
├─session.slice
│ ├─at-spi-dbus-bus.service
│ │ ├─4543 /usr/libexec/at-spi-bus-launcher
│ │ ├─4549 /usr/bin/dbus-broker-launch --config-file=/usr/shar>
│ │ └─4550 dbus-broker --log 4 --controller 9 --machine-id 8ca>
│ ├─dbus-broker.service
│ │ ├─4226 /usr/bin/dbus-broker-launch --scope user
│ │ └─4233 dbus-broker --log 4 --controller 9 --machine-id 8ca>
│ ├─gvfs-afc-volume-monitor.service
│ │ └─5183 /usr/libexec/gvfs-afc-volume-monitor
│ ├─gvfs-daemon.service
│ │ ├─4565 /usr/libexec/gvfsd
│ │ ├─4575 /usr/libexec/gvfsd-fuse /run/user/1000/gvfs -f
│ │ └─5268 /usr/libexec/gvfsd-trash --spawner :1.12 /org/gtk/g>
│ ├─gvfs-goa-volume-monitor.service
│ │ └─5177 /usr/libexec/gvfs-goa-volume-monitor
│ ├─gvfs-gphoto2-volume-monitor.service
│ │ └─5158 /usr/libexec/gvfs-gphoto2-volume-monitor
│ ├─gvfs-metadata.service
│ │ └─4982 /usr/libexec/gvfsd-metadata
│ ├─gvfs-mtp-volume-monitor.service
│ │ └─5007 /usr/libexec/gvfs-mtp-volume-monitor
│ ├─gvfs-udisks2-volume-monitor.service
│ │ └─4955 /usr/libexec/gvfs-udisks2-volume-monitor
│ ├─org.freedesktop.IBus.session.GNOME.service
│ │ ├─4730 /usr/bin/ibus-daemon --panel disable --xim
│ │ ├─4886 /usr/libexec/ibus-dconf
│ │ ├─4887 /usr/libexec/ibus-extension-gtk3
│ │ ├─4901 /usr/libexec/ibus-x11 --kill-daemon
│ │ └─5228 /usr/libexec/ibus-engine-simple
│ ├─org.gnome.SettingsDaemon.A11ySettings.service
│ │ └─4732 /usr/libexec/gsd-a11y-settings
│ ├─org.gnome.SettingsDaemon.Color.service
│ │ └─4737 /usr/libexec/gsd-color
│ ├─org.gnome.SettingsDaemon.Datetime.service
│ │ └─4749 /usr/libexec/gsd-datetime
│ ├─org.gnome.SettingsDaemon.Housekeeping.service
│ │ └─4751 /usr/libexec/gsd-housekeeping
│ ├─org.gnome.SettingsDaemon.Keyboard.service
│ │ └─4759 /usr/libexec/gsd-keyboard
│ ├─org.gnome.SettingsDaemon.MediaKeys.service
│ │ └─4761 /usr/libexec/gsd-media-keys
│ ├─org.gnome.SettingsDaemon.Power.service
│ │ └─4764 /usr/libexec/gsd-power
│ ├─org.gnome.SettingsDaemon.PrintNotifications.service
│ │ ├─4768 /usr/libexec/gsd-print-notifications
│ │ └─5297 /usr/libexec/gsd-printer
│ ├─org.gnome.SettingsDaemon.Rfkill.service
│ │ └─4772 /usr/libexec/gsd-rfkill
│ ├─org.gnome.SettingsDaemon.ScreensaverProxy.service
│ │ └─4783 /usr/libexec/gsd-screensaver-proxy
│ ├─org.gnome.SettingsDaemon.Sharing.service
│ │ └─4787 /usr/libexec/gsd-sharing
│ ├─org.gnome.SettingsDaemon.Smartcard.service
│ │ └─4799 /usr/libexec/gsd-smartcard
│ ├─org.gnome.SettingsDaemon.Sound.service
│ │ └─4806 /usr/libexec/gsd-sound
│ ├─org.gnome.SettingsDaemon.UsbProtection.service
│ │ └─4815 /usr/libexec/gsd-usb-protection
│ ├─org.gnome.SettingsDaemon.Wacom.service
│ │ └─4834 /usr/libexec/gsd-wacom
│ ├─org.gnome.SettingsDaemon.XSettings.service
│ │ └─4839 /usr/libexec/gsd-xsettings
│ ├─org.gnome.Shell@x11.service
│ │ ├─4635 /usr/bin/gnome-shell
│ │ └─4673 /usr/libexec/mutter-x11-frames
│ ├─pipewire-pulse.service
│ │ └─4985 /usr/bin/pipewire-pulse
│ ├─pipewire.service
│ │ └─4579 /usr/bin/pipewire
│ ├─wireplumber.service
│ │ └─4580 /usr/bin/wireplumber
│ ├─xdg-desktop-portal.service
│ │ └─5034 /usr/libexec/xdg-desktop-portal
│ ├─xdg-document-portal.service
│ │ ├─5049 /usr/libexec/xdg-document-portal
│ │ └─5060 fusermount3 -o rw,nosuid,nodev,fsname=portal,auto_u>
│ └─xdg-permission-store.service
│ └─4694 /usr/libexec/xdg-permission-store
└─uresourced.service
└─4559 /usr/libexec/uresourced --user
Great! “No jobs running.” means it is safe to reboot.
1 Like
ok nice, is it normal at the log in window that my password will only be recognize on the gnome x11 option and not on the 3 other ones which are gnome classic and 2 other wayland options ?
Did you check that you are writing each time the same password (by toggling the “make password visible” icon)?
Might be that X11 and Wayland are using different keyboard layouts.
oh ok, like wayland will be in AZERTY while X11 in QWERTY strange ? , yes i checked making the password visible. But another thing wich is strange is that sometimes i have 4 choices and some other time only 2
1 Like
Are you still only able to access X11 sessions from the GDM?
Ca you name what are the 2 options (when there are only 2 available), and what are the 4?
If his is like mine then with a cold boot or a restart it shows
gnome
gnome classic
and both log into x11.
When I log out and log back in (without a restart) it shows
gnome
gnome classic
gnome classic on xorg
gnome on xorg
and I can then select either wayland (the first two) or xorg.
1 Like
Interesting. This brings me again to the thought of GDM process starting earlier than KMS, that I have mentioned to another user here, without being convinced about it though. 
Could this explain why after a cold boot Wayland is not available (KMS not yet loaded), but after a logoff it is?
According to RPM Fusion’s team, the KMS feature is enabled by default in the nvidia drivers packaged by them.
This may be the cause. I had not thought of that issue though I had seen it mentioned.
What I don’t know is how to delay the gdm start to ensure kms is active first. My boot usually only takes about 17 seconds. Gdm starts in the last couple seconds of that.
I do have the option in the command line for nvidia-drm.modeset=1 that is mentioned in the link you provided.
I have seen advice for the following setup, with the caveat that I have not tested how it works. It is supposed to delay starting GDM with 3 seconds, which would give enough time for the Wayland KMS to start:
- Edit the GDM service:
sudo systemctl edit gdm
- Then add these lines as a drop-in file:
[Service]
ExecStartPre=/usr/bin/sleep 3
I don’t think the gdm tests work, my test setup uses gdm-x-session even if nvidia modeset is set.
leigh@leigh-pc:~$ sudo cat /sys/module/nvidia_drm/parameters/modeset
Y
I even tried loading the nvidia modules into initramfs so nvidia loaded early (3 seconds quicker) .
I have made a reference to KMS and nvidia, but actually the issue seems to be with KMS and Wayland.
For what it’s worth, I have tested the GDM delay setup, and it is working, meaning it booted to login screen some 3 seconds later. I don’t have the issue in question, so can’t confirm the fix.
Exactly same behaviour with my computer
Added rpmfusion
Kernel Mode Setting happends very early in the boot.
I would have thought a long time before userspace starts up and GDM.