[SOLVED] Failed gnome session after nvidia upgrade to 550.54.14

odror · 2024-02-28 01:22:46

Hi

After the upgrade I get the normal gdm sign screen, but when logging to my user session I get a blank screen.

I get the following error in journalctl. Any ideas how to fix or workaround

Feb 27 17:19:44 i9-13900k-arch /usr/lib/gdm-x-session[4717]: /etc/gdm/Xsession: Beginning session setup...
Feb 27 17:19:44 i9-13900k-arch /usr/lib/gdm-x-session[4732]: localuser:dror being added to access control list
Feb 27 17:19:44 i9-13900k-arch /usr/lib/gdm-x-session[4717]: /etc/gdm/Xsession: Setup done, will execute: /usr/bin/gnome-session
Feb 27 17:19:44 i9-13900k-arch systemd[4548]: Starting Accessibility services bus...
Feb 27 17:19:44 i9-13900k-arch systemd[4548]: Started Accessibility services bus.
Feb 27 17:19:44 i9-13900k-arch at-spi-bus-launcher[4747]: Policy to allow eavesdropping in /usr/share/defaults/at-spi2/accessibility.conf +15: Eavesdropping is deprecated and ignored
Feb 27 17:19:44 i9-13900k-arch at-spi-bus-launcher[4747]: Policy to allow eavesdropping in /usr/share/defaults/at-spi2/accessibility.conf +17: Eavesdropping is deprecated and ignored
Feb 27 17:19:44 i9-13900k-arch dbus-broker-launch[4747]: Ready
Feb 27 17:19:44 i9-13900k-arch systemd[4548]: Created slice Slice /app/gnome-session-manager.
Feb 27 17:19:44 i9-13900k-arch systemd[4548]: Reached target GNOME X11 Session.
Feb 27 17:19:44 i9-13900k-arch systemd[4548]: Reached target Session services which should run early before the graphical session is brought up.
Feb 27 17:19:44 i9-13900k-arch systemd[4548]: Reached target GNOME Shell.
Feb 27 17:19:44 i9-13900k-arch systemd[4548]: Starting Monitor Session leader for GNOME Session...
Feb 27 17:19:44 i9-13900k-arch systemd[4548]: Started Monitor Session leader for GNOME Session.
Feb 27 17:19:44 i9-13900k-arch systemd[4548]: Reached target Tasks to be run before GNOME Session starts.
Feb 27 17:19:44 i9-13900k-arch systemd[4548]: Starting GNOME Session Manager (session: gnome)...
Feb 27 17:19:44 i9-13900k-arch gnome-session[4758]: gnome-session-binary[4758]: WARNING: Desktop file /home/dror/.config/autostart/nvidia-prime.desktop for application nvidia-prime.desktop could not be parsed or references a missing TryExec binary
Feb 27 17:19:44 i9-13900k-arch gnome-session-binary[4758]: WARNING: Desktop file /home/dror/.config/autostart/nvidia-prime.desktop for application nvidia-prime.desktop could not be parsed or references a missing TryExec binary
Feb 27 17:19:44 i9-13900k-arch gnome-keyring-d[4627]: The PKCS#11 component was already initialized
Feb 27 17:19:44 i9-13900k-arch gnome-keyring-daemon[4627]: The PKCS#11 component was already initialized
Feb 27 17:19:44 i9-13900k-arch gnome-keyring-pkcs11.desktop[4775]: discover_other_daemon: 1GNOME_KEYRING_CONTROL=/run/user/1000/keyring
Feb 27 17:19:44 i9-13900k-arch gnome-keyring-daemon[4775]: discover_other_daemon: 1
Feb 27 17:19:44 i9-13900k-arch gnome-keyring-daemon[4627]: The Secret Service was already initialized
Feb 27 17:19:44 i9-13900k-arch gnome-keyring-d[4627]: The Secret Service was already initialized
Feb 27 17:19:44 i9-13900k-arch gnome-session[4758]: gnome-session-binary[4758]: GnomeDesktop-WARNING: Could not create transient scope for PID 4767: GDBus.Error:org.freedesktop.DBus.Error.UnixProcessIdUnknown: Failed to set unit properties: No such process
Feb 27 17:19:44 i9-13900k-arch gnome-session-binary[4758]: GnomeDesktop-WARNING: Could not create transient scope for PID 4767: GDBus.Error:org.freedesktop.DBus.Error.UnixProcessIdUnknown: Failed to set unit properties: No such process
Feb 27 17:19:44 i9-13900k-arch gnome-keyring-daemon[4778]: discover_other_daemon: 1
Feb 27 17:19:44 i9-13900k-arch gnome-keyring-secrets.desktop[4778]: discover_other_daemon: 1GNOME_KEYRING_CONTROL=/run/user/1000/keyring
Feb 27 17:19:44 i9-13900k-arch systemd[4548]: app-gnome-gnome\x2dkeyring\x2dsecrets-4771.scope: PID 4771 vanished before we could move it to target cgroup '/user.slice/user-1000.slice/user@1000.service/app.slice/app-gnome-gnome\x2dkeyring\x2dsecrets-4771.scope', skipping: No such process
Feb 27 17:19:44 i9-13900k-arch systemd[4548]: app-gnome-gnome\x2dkeyring\x2dsecrets-4771.scope: No PIDs left to attach to the scope's control group, refusing.
Feb 27 17:19:44 i9-13900k-arch systemd[4548]: app-gnome-gnome\x2dkeyring\x2dsecrets-4771.scope: Failed with result 'resources'.
Feb 27 17:19:44 i9-13900k-arch gnome-keyring-daemon[4781]: discover_other_daemon: 1
Feb 27 17:19:44 i9-13900k-arch gnome-keyring-ssh.desktop[4781]: discover_other_daemon: 1GNOME_KEYRING_CONTROL=/run/user/1000/keyring
Feb 27 17:19:44 i9-13900k-arch systemd[4548]: Failed to start Application launched by gnome-session-binary.
Feb 27 17:19:44 i9-13900k-arch systemd[4548]: app-gnome-gnome\x2dkeyring\x2dssh-4774.scope: PID 4774 vanished before we could move it to target cgroup '/user.slice/user-1000.slice/user@1000.service/app.slice/app-gnome-gnome\x2dkeyring\x2dssh-4774.scope', skipping: No such process
Feb 27 17:19:44 i9-13900k-arch systemd[4548]: app-gnome-gnome\x2dkeyring\x2dssh-4774.scope: No PIDs left to attach to the scope's control group, refusing.
Feb 27 17:19:44 i9-13900k-arch systemd[4548]: app-gnome-gnome\x2dkeyring\x2dssh-4774.scope: Failed with result 'resources'.
Feb 27 17:19:44 i9-13900k-arch systemd[4548]: Failed to start Application launched by gnome-session-binary.
Feb 27 17:19:44 i9-13900k-arch systemd[4548]: Started GNOME Session Manager (session: gnome).
Feb 27 17:19:44 i9-13900k-arch systemd[4548]: Reached target GNOME Session Manager is ready.
Feb 27 17:19:44 i9-13900k-arch systemd[4548]: GNOME Shell on Wayland was skipped because of an unmet condition check (ConditionEnvironment=XDG_SESSION_TYPE=wayland).
Feb 27 17:19:44 i9-13900k-arch systemd[4548]: Starting GNOME Shell on X11...
Feb 27 17:19:44 i9-13900k-arch gnome-session[4758]: gnome-session-binary[4758]: GnomeDesktop-WARNING: Could not create transient scope for PID 4783: GDBus.Error:org.freedesktop.DBus.Error.UnixProcessIdUnknown: Failed to set unit properties: No such process
Feb 27 17:19:44 i9-13900k-arch gnome-session-binary[4758]: GnomeDesktop-WARNING: Could not create transient scope for PID 4783: GDBus.Error:org.freedesktop.DBus.Error.UnixProcessIdUnknown: Failed to set unit properties: No such process
Feb 27 17:19:44 i9-13900k-arch systemd[4548]: Starting Virtual filesystem service...
Feb 27 17:19:44 i9-13900k-arch systemd[4548]: Started Virtual filesystem service.
Feb 27 17:19:44 i9-13900k-arch gnome-shell[4784]: Running GNOME Shell (using mutter 45.4) as a X11 window and compositing manager
Feb 27 17:19:50 i9-13900k-arch geoclue[4469]: Service not used for 60 seconds. Shutting down..
Feb 27 17:19:50 i9-13900k-arch systemd[1]: geoclue.service: Deactivated successfully.
Feb 27 17:19:50 i9-13900k-arch audit[1]: SERVICE_STOP pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=geoclue comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
Feb 27 17:19:50 i9-13900k-arch kernel: audit: type=1131 audit(1709083190.041:144): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=geoclue comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=

Last edited by odror (2024-03-02 22:54:35)

V1del · 2024-02-28 01:27:50

/home/dror/.config/autostart/nvidia-prime.desktop -- what is this?

odror · 2024-02-28 02:09:50

V1del wrote:

/home/dror/.config/autostart/nvidia-prime.desktop -- what is this?

This is leftover from a test. The executable was actually removed from my system long time ago. This did not prevent the gnome session to start with the prior version of the nvidia driver

seth · 2024-02-28 08:14:56

I get the following error in journalctl.

Please post your complete system journal for the boot:

sudo journalctl -b | curl -F 'file=@-' 0x0.st

Any kind of problem will rather not show up in parts of your session journal.

odror · 2024-02-29 05:09:32

seth wrote:

I get the following error in journalctl.
Please post your complete system journal for the boot:
sudo journalctl -b | curl -F 'file=@-' 0x0.st
Any kind of problem will rather not show up in parts of your session journal.

I have uploaded the file. Now after the second update gdm does not start any display. Any help will be appreciated. Also the process Xorg has 100% CPU usage.

http://0x0.st/HRyI.bin

Last edited by odror (2024-02-29 05:14:07)

seth · 2024-02-29 08:58:17

There're 3 GPUs, the intel IGP, a Quadro M4000 and an RTX 4070 Ti
The xorg config tries puts the server on the RTX 4070 Ti, which has 3 outputs connected
1. Microstep MSI G321CU
2. GBT M32UC
3. DELL U3219Q

There're also two outputs attached to the IGP a GSM via HDMI and a VIZ via DP.

At least the microstep output disappears after the login?
In general, get rid of ~/.config/monitors.xml first and elaborate on what outputs you expect to see anything (because they're really attached and powered on)

Aftre the login you get

odror · 2024-02-29 15:18:36

seth wrote:

There're 3 GPUs, the intel IGP, a Quadro M4000 and an RTX 4070 Ti
The xorg config tries puts the server on the RTX 4070 Ti, which has 3 outputs connected
1. Microstep MSI G321CU
2. GBT M32UC
3. DELL U3219Q

I will try it later this evening. I have the following comment. Maybe you can help me narrow my testing.
1. The quadro m4000 does not count because it is used the vfio driver. Nvidia should not be accessing it.
2. After the test night I do not get the GDM login screen. I get black screens
3. If I plug the monitors to one GPU can that help for testing

seth · 2024-02-29 15:42:23

1. does not, I just wanted to make sure you're not trying to look at an output attached to that.
3. I'd simplify the system as much as possible to get a functional baseline and extend from there.

The xorg log says

Feb 28 20:55:51 i9-13900k-arch /usr/lib/gdm-x-session[3454]:         Using the first device section listed.
Feb 28 20:55:51 i9-13900k-arch /usr/lib/gdm-x-session[3454]: (**) |   |-->Device "onboard"

what seems to suggest an intention to run on the IGP, but you don't.
=> Remove all local X11 configs (or "move them away") and attach one output to the IGP and one output to the RTX 4070 Ti
=> Remove all monitors.xml to allow the default/detected setup, https://wiki.archlinux.org/title/GDM#Se … r_settings

Feb 28 20:57:17 i9-13900k-arch /usr/lib/gdm-x-session[4310]: dbus-daemon[4310]: [session uid=120 pid=4310] Activated service 'org.freedesktop.systemd1' failed: Process org.freedesktop.systemd1 exited with status 1

Might be a red herring, but you could try to replace dbus-broker-units w/ dbus-daemon-units again.

odror · 2024-03-01 06:18:11

I finally narrowed the issue to the file /etc/X11/xorg.conf below.

On the prior versions of the nvidia driver 545.29.06
this file enabled me to be able to render with the intel iGPU monitors that are attached to ports in the MB and it enabled the nvidia dGpu render monitors that are attached to the nvidia card.
without this file all the ports including ones that are attached to the nvidia card are rendered with the intel iGPU.

This file does not work with the new version of nvidia 550.54.14. I am not getting any display (all monitors are blank, except for one that shows flashing "-"). If I remove the file. I am able to get the display, but all the
monitors are rendered with the iGPU. Including ones that are attached to the nvidia card.

Any ideas how to resolve the issue. I have tried to change the file or use a different file, but I was unsuccessful.

Section "OutputClass"
    Identifier "intel"
    MatchDriver "i915"
    Driver "modesetting"
EndSection

Section "OutputClass"
    Identifier "nvidia"
    Driver "nvidia"
    Option "AllowEmptyInitialConfiguration"
    Option "PrimaryGPU" "yes"
EndSection

Section "Screen"
    Identifier     "Screen0"
    DefaultDepth    24
    Option         "Stereo" "0"
    Option         "nvidiaXineramaInfoOrder" "DFP-1"
    Option         "metamodes" "HDMI-0: nvidia-auto-select +0+0 {ForceCompositionPipeline=On, ForceFullCompositionPipeline=On}, DP-0: nvidia-auto-select +3840+0 {ForceCompositionPipeline=On, ForceFullCompositionPipeline=On, AllowGSYNCCompatible=On}, DP-4: nvidia-auto-select +7680+0 {ForceCompositionPipeline=On, ForceFullCompositionPipeline=On}"
    Option         "SLI" "Off"
    Option         "MultiGPU" "Off"
    Option         "BaseMosaic" "off"
    SubSection     "Display"
        Depth       24
    EndSubSection
EndSection

less

seth · 2024-03-01 08:32:21

There're only three relevant lines in that:

Option "PrimaryGPU" "yes"

    Option         "nvidiaXineramaInfoOrder" "DFP-1"
    Option         "metamodes" "HDMI-0: nvidia-auto-select +0+0 {ForceCompositionPipeline=On, ForceFullCompositionPipeline=On}, DP-0: nvidia-auto-select +3840+0 {ForceCompositionPipeline=On, ForceFullCompositionPipeline=On, AllowGSYNCCompatible=On}, DP-4: nvidia-auto-select +7680+0 {ForceCompositionPipeline=On, ForceFullCompositionPipeline=On}"

Comment away the metamodes, see what nvidia-settings currently generates.
How does that configlet relate to the "Device "onboard"" comfig, does the latter still exist?

odror · 2024-03-02 06:33:48

I have tried many combination of setups. I even tried just using the NVIDIA driver and forcing it to use the NVIDIA specific BusId. I am not getting error, but I get blank screen.
I think that there is a bug in the new nvidia driver. The driver should at least work with the NVIDIA card only ignoring the Intel iGPU ports, but it does not.

seth · 2024-03-02 09:06:03

Can you start notgnome (eg. openbox) and, if, test the opengl behavior there (eg. picom w/ glx backend or just glxgears)?
For a wild guess, try explicit "nvidia-drm.fbdev=0" and ""nvidia-drm.fbdev=1"
And, as a cross check, does the system still behave as expected when running on the intel chip and reverse priming nvidia instead?

odror · 2024-03-02 22:48:34

seth wrote:

Can you start notgnome (eg. openbox) and, if, test the opengl behavior there (eg. picom w/ glx backend or just glxgears)?
For a wild guess, try explicit "nvidia-drm.fbdev=0" and ""nvidia-drm.fbdev=1"
And, as a cross check, does the system still behave as expected when running on the intel chip and reverse priming nvidia instead?

Thank you. Problem Solved. setting "nvidia-drm.fbdev=1" fixed the issue. What does that do?

The system prior to change was working fine as long as intel (modesetting) did the rendering on the nvidia ports and using 4 or less 4k monitors (mesa cannot handle more than 4 4k monitors, which is another issue).

After the change, nvidia did the rendering on all the monitors including the ones that are attached to the motherboard. Nvidia call these monitors prime monitors now.

There is a general issue here with all the drivers. I have a desktop with iGPU and dGPU. This is not a laptop and I do not need to be to switching GPUs. I just need to work with the best GPU all the times. In fact I really want to passthrough the intel iGPU to a vm (for which I was unsuccessful). So now I have and additional ones slot GPU f (quadro m4000) for the vm.

seth · 2024-03-02 23:00:09

https://wiki.archlinux.org/title/NVIDIA … de_setting
It's previously been otr to break things badly, https://wiki.archlinux.org/title/Talk:N … al_support
But as you can also read there, thouse might have been fixed… apparently at the cost of introducing issues w/o it

MyChaOS · 2024-03-03 11:16:16

had the same problem, wayland start failed.

for me setting "nvidia-drm.fbdev=0" fixed the issue. So the opposite then for @odror

seth · 2024-03-03 11:59:01

nvidia-drm.fbdev=0 should™ still be the default?
Did you previously explicitly enable it?

Arch Linux

#1 2024-02-28 01:22:46

[SOLVED] Failed gnome session after nvidia upgrade to 550.54.14

#2 2024-02-28 01:27:50

Re: [SOLVED] Failed gnome session after nvidia upgrade to 550.54.14

#3 2024-02-28 02:09:50

Re: [SOLVED] Failed gnome session after nvidia upgrade to 550.54.14

#4 2024-02-28 08:14:56

Re: [SOLVED] Failed gnome session after nvidia upgrade to 550.54.14

#5 2024-02-29 05:09:32

Re: [SOLVED] Failed gnome session after nvidia upgrade to 550.54.14

#6 2024-02-29 08:58:17

Re: [SOLVED] Failed gnome session after nvidia upgrade to 550.54.14

#7 2024-02-29 15:18:36

Re: [SOLVED] Failed gnome session after nvidia upgrade to 550.54.14

#8 2024-02-29 15:42:23

Re: [SOLVED] Failed gnome session after nvidia upgrade to 550.54.14

#9 2024-03-01 06:18:11

Re: [SOLVED] Failed gnome session after nvidia upgrade to 550.54.14

#10 2024-03-01 08:32:21

Re: [SOLVED] Failed gnome session after nvidia upgrade to 550.54.14

#11 2024-03-02 06:33:48

Re: [SOLVED] Failed gnome session after nvidia upgrade to 550.54.14

#12 2024-03-02 09:06:03

Re: [SOLVED] Failed gnome session after nvidia upgrade to 550.54.14

#13 2024-03-02 22:48:34

Re: [SOLVED] Failed gnome session after nvidia upgrade to 550.54.14

#14 2024-03-02 23:00:09

Re: [SOLVED] Failed gnome session after nvidia upgrade to 550.54.14

#15 2024-03-03 11:16:16

Re: [SOLVED] Failed gnome session after nvidia upgrade to 550.54.14

#16 2024-03-03 11:59:01

Re: [SOLVED] Failed gnome session after nvidia upgrade to 550.54.14

Board footer