[SOLVED] Unable to run session on Wayland.

Xalares · 2022-05-24 09:26:20

Hi everybody, I'm facing an issue with Wayland. My setup works fine with Xorg, but is unable to run Wayland.
Here is a little extract of my journalctl for the last boot.

mai 23 11:21:54 archlinux systemd[1420]: Starting GNOME Shell on Wayland...
mai 23 11:21:54 archlinux systemd[1420]: org.gnome.Shell@wayland.service: Skipped due to 'exec-condition'.
mai 23 11:21:54 archlinux systemd[1420]: Condition check resulted in GNOME Shell on Wayland being skipped.

Full log here https://gist.github.com/Xalares/d2f2941 … bdd0e19225
If you need more information, let me know.
Loaded all the modules following this https://wiki.archlinux.org/title/NVIDIA#mkinitcpio
In mkinitcpio.conf

MODULES=(nvidia nvidia_modeset nvidia_uvm nvidia_drm)

In grub

# Enable kernel parameter to be able to use wayland with NVIDIA but seems to make things buggy
GRUB_CMDLINE_LINUX_DEFAULT="nvidia-drm.modeset=1"

I've looked there https://wiki.archlinux.org/title/GDM#Wa … DIA_driver
But as I have

local/nvidia 515.43.04-5
    NVIDIA drivers for linux
local/nvidia-settings 515.43.04-1
    Tool for configuring the NVIDIA graphics driver
local/nvidia-utils 515.43.04-1

and a RTX 2060 this issue should not apply to me.

# GDM configuration storage

[daemon]
# Uncomment the line below to force the login screen to use Xorg
WaylandEnable=true

[security]

[xdmcp]

[chooser]

[debug]
# Uncomment the line below to turn on debugging
#Enable=true

Commenting "WaylandEnable=true doesn't change anything (which seems logic, but as the line before says "Uncomment the line below to force the login screen to use Xorg" I still tried .
I've found some posts here and there, but nothing that solved my issue.

Last edited by Xalares (2022-05-26 12:55:32)

V1del · 2022-05-24 09:40:35

Override the udev rule anyway, afaik the general logistics of it are bugged.

Other than that, just adjusting the GRUB cmdline doesn't change anything on it's own, did you rerun grub-mkconfig? Your full log shows that your kernel command line is not yet adjusted and thus the modeset parameter not passed to the kernel

Last edited by V1del (2022-05-24 09:41:10)

Xalares · 2022-05-24 12:06:16

V1del wrote:

Override the udev rule anyway, afaik the general logistics of it are bugged.
Other than that, just adjusting the GRUB cmdline doesn't change anything on it's own, did you rerun grub-mkconfig? Your full log shows that your kernel command line is not yet adjusted and thus the modeset parameter not passed to the kernel

Yeah I heard about overriding the udev. I think I'll do that.
I've set et un-set GRUB_CMDLINE_LINUX_DEFAULT="nvidia-drm.modeset=1" multiple times and ran grub-mkconfig multiple times too. It's possible that I've forgot to run that the last time.
But I've never been able to run Wayland anyway.
I'll try disabling the Udev rule.

Xalares · 2022-05-24 12:27:37

Here this is the log of the last boot, I overrode the udev rule and re-ran grub-mkconfig. Unfortunately nothing changed.
Could it grub issue ? Not passing the modeset parameter to the kernel ?
https://gist.github.com/Xalares/01ba09a … 695aa8ec2a

mai 24 14:16:43 archlinux kernel: nvidia-modeset: Loading NVIDIA Kernel Mode Setting Driver for UNIX platforms  515.43.04  Tue Apr 26 15:44:44 UTC 2022
mai 24 14:16:43 archlinux kernel: nvidia_uvm: module uses symbols from proprietary module nvidia, inheriting taint.
mai 24 14:16:43 archlinux kernel: nvidia-uvm: Loaded the UVM driver, major device number 235.
mai 24 14:16:43 archlinux kernel: [drm] [nvidia-drm] [GPU ID 0x00001000] Loading driver
mai 24 14:16:43 archlinux kernel: [drm] Initialized nvidia-drm 0.0.0 20160202 for 0000:10:00.0 on minor 0

Everything seems ok here no ?

Last edited by Xalares (2022-05-24 12:35:29)

V1del · 2022-05-24 13:00:30

not necessarily, the "nvidia-modeset" is usually loaded regardless, the important part is whether

systool -vm nvidia_drm

shows that the parameter has a Y. And according to that log the "Command line" still doesn't include the parameter. Where are you generating the grub-mkconfig to and is this the correct place your GRUB is actually reading it's config from? (Confusion in that regard usually arises if you mounted e.g. your ESP to /boot during initial GRUB installation but don't do that anymore or vice versa what's your situation here? Check post "mount", "/boot/grub/grub.cfg")

What you can also do is set the parameter in modprobe instead with e.g. /etc/modprobe.d/nvidia-modeset.conf

options nvidia-drm modeset=1

and regenerate your initramfs so that it's logically applied the same way.

Last edited by V1del (2022-05-24 13:20:16)

Xalares · 2022-05-25 17:45:51

Sorry to have taken so much time to reply. I had to reinstall arch because I had an issue when I was trying to resize the boot partition.
But unfortunately, it didn't resolved my issue with wayland.

Where are you generating the grub-mkconfig to and is this the correct place your GRUB is actually reading it's config from? (Confusion in that regard usually arises if you mounted e.g. your ESP to /boot during initial GRUB installation but don't do that anymore or vice versa what's your situation here?

Grub is using his configuration verywell. As I use a full encrypted system it better works, also I've changed grub display resolution to hd.

What you can also do is set the parameter in modprobe instead with e.g. /etc/modprobe.d/nvidia-modeset.conf

I'll try that.
Also I found that error

mai 25 19:31:12 archlinux kernel: nvidia-gpu 0000:10:00.3: i2c timeout error e0000000
mai 25 19:31:12 archlinux kernel: ucsi_ccg 0-0008: i2c_transfer failed -110
mai 25 19:31:12 archlinux kernel: ucsi_ccg 0-0008: ucsi_ccg_init failed - -110

In the journal. Don't know if it's relevant here, I'm putting that here in case it can helps.

Last edited by Xalares (2022-05-25 17:48:59)

V1del · 2022-05-25 18:32:26

It's not relevant, it's normal because relevant open source power sensors try to access a bus that is exposed on nouveau and not on nvidia, generally nothing to worry about (nvidia has their own tooling in nvidia-smi to do this), your main issue currently is still that you are simply not setting nvidia-drm.modeset=1 in a way that the system would apply it.

The second line in that journal output

mai 24 14:16:43 archlinux kernel: Command line: BOOT_IMAGE=/vmlinuz-linux root=UUID=404ca061-aa81-4ee2-8c94-9e1f96d125d8 rw cryptdevice=UUID=d6572102-9fdb-450c-a3cd-5cda2f9c3577:root root=/dev/dm-0 loglevel=3 quiet

should read "nvidia-drm.modeset=1" at the end instead/additionally to the "loglevel=3 quiet" which it doesn't, which suggests to me that you either didn't rerun grub-mkconfig or aren't generating the file at a position that your actual GRUB is reading it.

As for the GRUB adjustments, then for whatever reason at least that line is not being applied as it should (FWIW adjusting that directive where you added the parameter works fine here) maybe post your actual currently generated /boot/grub/grub.cfg

Last edited by V1del (2022-05-25 18:36:44)

Xalares · 2022-05-25 20:17:23

Ok I think I'm strating to see the issue, my new /etc/default/grub has loglevel=3 quiet nvidia-drm.modeset=1 on the same line, (as you can see here https://gist.github.com/Xalares/7f7b6d4 … c596de98ee,
but it doesn't appear in grub.cfg https://gist.github.com/Xalares/19c77aa … 11c195b93f.
And not in my journalctl

mai 25 21:05:03 archlinux kernel: Kernel command line: BOOT_IMAGE=/vmlinuz-linux root=UUID=05d9c49f-bc3e-4de6-85de-ce42fdd3d702 rw rd.luks.uuid=ba212361-37ca-402d-b3a2-40f315cc6493
mai 25 21:05:03 archlinux kernel: Unknown kernel command line parameters "BOOT_IMAGE=/vmlinuz-linux", will be passed to user space.

So in response to

Which suggests to me that you either didn't rerun grub-mkconfig or aren't generating the file at a position that your actual GRUB is reading it.

I've ran grub-mkconfig more times than I can count and every changes I do in /etc/default/grub are taken into account excepts the one that are in the same line as nvidia-drm.modeset=1.

seth · 2022-05-25 20:46:55

I've ran grub-mkconfig more times than I can count and every changes I do in /etc/default/grub are taken into account excepts the one that are in the same line as nvidia-drm.modeset=1.

No.

Please post:
- /etc/mkinitcpio.conf
- the *exact* grub-mkconfig command you ran
- lsblk -f
- /boot/grub/grub.cfg
- cat /proc/cmdline

Xalares · 2022-05-25 21:05:53

the *exact* grub-mkconfig command you ran

grub-mkconfig -o /boot/grub/grub.cfg

lsblk -h

NAME                                          FSTYPE      FSVER LABEL    UUID                                 FSAVAIL FSUSE% MOUNTPOINTS
sda                                                                                                                          
└─sda1                                        ntfs                       E252F2FE52F2D5EF                                    
sdb                                                                                                                          
└─sdb1                                        ntfs                       AC5A5DED5A5DB534                                    
sdc                                                                                                                          
sr0                                                                                                                          
nvme1n1                                                                                                                      
├─nvme1n1p1                                   vfat        FAT32          2FFA-2F12                             417,2M    30% /boot
└─nvme1n1p2                                   crypto_LUKS 2              ba212361-37ca-402d-b3a2-40f315cc6493                
  └─luks-ba212361-37ca-402d-b3a2-40f315cc6493 ext4        1.0            05d9c49f-bc3e-4de6-85de-ce42fdd3d702  853,9G     2% /
nvme0n1                                                                                                                      
├─nvme0n1p1                                                                                                                  
├─nvme0n1p2                                   ntfs                       C08411F08411E9A4                                    
├─nvme0n1p3                                   vfat        FAT32          B65D-9DFC                                           
└─nvme0n1p4                                   ext4        1.0   VM Disks ad6903bf-6fa7-4b68-9713-48c827dc70c0

cat /proc/cmdline 
BOOT_IMAGE=/vmlinuz-linux root=UUID=05d9c49f-bc3e-4de6-85de-ce42fdd3d702 rw rd.luks.uuid=ba212361-37ca-402d-b3a2-40f315cc6493

/boot/grub/grub.cfg

It's in the post you just quoted
Here mkinitcpio.conf https://gist.github.com/Xalares/1c19db6 … e18f7bc7c5

seth · 2022-05-25 21:09:32

Sorry missed that.
https://gist.github.com/Xalares/7f7b6d4 … c596de98ee

GRUB_CMDLINE_LINUX_DEFAULT="loglevel=3 quiet nvidia-drm.modeset=1"
GRUB_CMDLINE_LINUX_DEFAULT="rd.luks.uuid=ba212361-37ca-402d-b3a2-40f315cc6493"

GRUB_CMDLINE_LINUX_DEFAULT="rd.luks.uuid=ba212361-37ca-402d-b3a2-40f315cc6493 loglevel=3 quiet nvidia-drm.modeset=1"

Xalares · 2022-05-25 21:26:13

Unfortunately, still on X11 even doing that , that was worth trying though.

Last edited by Xalares (2022-05-25 21:27:03)

Xalares · 2022-05-25 21:36:22

What you can also do is set the parameter in modprobe instead with e.g. /etc/modprobe.d/nvidia-modeset.conf
options nvidia-drm modeset=1
and regenerate your initramfs so that it's logically applied the same way.

I tried that way, without forgetting about modconf in hooks, and it changed nothing unfortunately.

seth · 2022-05-25 21:41:59

mai 24 14:16:45 archlinux optimus.desktop[1132]: Can't open display
mai 24 14:16:45 archlinux optimus.desktop[1131]: Can't open display
mai 24 14:16:45 archlinux gnome-session[1090]: gnome-session-binary[1090]: WARNING: App 'optimus.desktop' exited with code 1
mai 24 14:16:45 archlinux gnome-session-binary[1090]: WARNING: App 'optimus.desktop' exited with code 1
mai 24 14:16:46 archlinux optimus.desktop[1199]: Could not find provider with name modesetting
mai 24 14:16:56 archlinux optimus.desktop[1566]: Could not find provider with name modesetting

Get rid of (I assume that's) optimus-manager

Xalares · 2022-05-25 22:11:42

I'd be glad to do that, but unfortunately I don't know how... I've never installed optimus-manager and I can't find it with pacman. There is no trace of it in my system I've done a quick search with : sudo find / -name "optimus.*"

seth · 2022-05-26 05:28:55

From google results you probably followed https://wiki.archlinux.org/title/NVIDIA_Optimus#GDM ?
Get rid of that file.

Xalares · 2022-05-26 07:49:55

Sorry, I think this is from my old installation, let me refresh the journalctl, I don't have optimus-manager anymore. Now journalctl is up to date.

Last edited by Xalares (2022-05-26 07:51:55)

Xalares · 2022-05-26 10:08:59

I added manually nvidia-drm.modeset=1 to the /boot/grub/grub.cfg file to see if thatt was working, but it didn't work too.
Here you can find my journalctl with nvidia-drm.modeset=1 manually edited https://gist.github.com/Xalares/c7c488c … ac04aedead.

Xalares · 2022-05-26 12:54:34

My solution was here https://forum.manjaro.org/t/howto-use-w … vers/36130
Although I've already followed most of these steps, step 3

gsettings set org.gnome.mutter experimental-features '["kms-modifiers"]'

Was new to me, I guess that's what made it work !

Xalares · 2022-05-26 13:17:15

Now my issue is that quadrapassel doesn't show

Xalares · 2022-05-26 13:17:57

Thanks for your help everybody !

Arch Linux

#1 2022-05-24 09:26:20

[SOLVED] Unable to run session on Wayland.

#2 2022-05-24 09:40:35

Re: [SOLVED] Unable to run session on Wayland.

#3 2022-05-24 12:06:16

Re: [SOLVED] Unable to run session on Wayland.

#4 2022-05-24 12:27:37

Re: [SOLVED] Unable to run session on Wayland.

#5 2022-05-24 13:00:30

Re: [SOLVED] Unable to run session on Wayland.

#6 2022-05-25 17:45:51

Re: [SOLVED] Unable to run session on Wayland.

#7 2022-05-25 18:32:26

Re: [SOLVED] Unable to run session on Wayland.

#8 2022-05-25 20:17:23

Re: [SOLVED] Unable to run session on Wayland.

#9 2022-05-25 20:46:55

Re: [SOLVED] Unable to run session on Wayland.

#10 2022-05-25 21:05:53

Re: [SOLVED] Unable to run session on Wayland.

#11 2022-05-25 21:09:32

Re: [SOLVED] Unable to run session on Wayland.

#12 2022-05-25 21:26:13

Re: [SOLVED] Unable to run session on Wayland.

#13 2022-05-25 21:36:22

Re: [SOLVED] Unable to run session on Wayland.

#14 2022-05-25 21:41:59

Re: [SOLVED] Unable to run session on Wayland.

#15 2022-05-25 22:11:42

Re: [SOLVED] Unable to run session on Wayland.

#16 2022-05-26 05:28:55

Re: [SOLVED] Unable to run session on Wayland.

#17 2022-05-26 07:49:55

Re: [SOLVED] Unable to run session on Wayland.

#18 2022-05-26 10:08:59

Re: [SOLVED] Unable to run session on Wayland.

#19 2022-05-26 12:54:34

Re: [SOLVED] Unable to run session on Wayland.

#20 2022-05-26 13:17:15

Re: [SOLVED] Unable to run session on Wayland.

#21 2022-05-26 13:17:57

Re: [SOLVED] Unable to run session on Wayland.

Board footer