Scheduled Maintenance: We are aware of an issue with Google, AOL, and Yahoo services as email providers which are blocking new registrations. We are trying to fix the issue and we have several internal and external support tickets in process to resolve the issue. Please see: viewtopic.php?t=158230

 

 

 

nVidia Basemosaic black screen on session restart

Linux Kernel, Network, and Services configuration.
Post Reply
Message
Author
dmatta22201
Posts: 3
Joined: 2018-12-03 00:46

nVidia Basemosaic black screen on session restart

#1 Post by dmatta22201 »

Hi! I am trying to learn Debian and have converted my desktop from Windows to Debian 9 (stretch). The computer is an evga X99 motherboard with 2 evga geForce GTX 980 TI classified cards. There are three identical monitors (Ancor VS248), two on GPU-0 (DFP-1 and DFP-3) and one on GPU-1 (DFP-1). I have managed to get the system set up to the point that it consistently boots with both the lock screen and the desktop spanning all three monitors in correct orientation and placement at 1920x1080 per monitor for a single X Screen of 5760x1080. I am using gdm3 for my desktop-manager. I only have one error remaining. Whenever X shuts down or restarts (be it a shutdown/restart, logout, change of runlevel, etc.), the monitors shut down and do not come boack on under any circumstance. When shut downs and restarts, the system will eventually shutdown/restart after about 4 minutes. With logouts, changing runlevel, etc., the monitors are off and I have to hard cycle the power to get them to come back on.

The shutdown messages from journal are:

Code: Select all

Dec 02 20:14:33 Windsor gnome-session[1201]: gnome-session-binary[1201]: GLib-GObject-CRITICAL: g_object_unref: assertion 'G_IS_OBJECT (object)' failed
Dec 02 20:14:33 Windsor gnome-session-binary[1201]: GLib-GObject-CRITICAL: g_object_unref: assertion 'G_IS_OBJECT (object)' failed
Dec 02 20:14:33 Windsor gnome-session[1201]: gnome-session-binary[1201]: GLib-GObject-CRITICAL: g_object_unref: assertion 'G_IS_OBJECT (object)' failed
Dec 02 20:14:33 Windsor gnome-session-binary[1201]: GLib-GObject-CRITICAL: g_object_unref: assertion 'G_IS_OBJECT (object)' failed
Dec 02 20:14:33 Windsor gnome-session-binary[1201]: GLib-GObject-CRITICAL: g_object_unref: assertion 'G_IS_OBJECT (object)' failed
Dec 02 20:14:33 Windsor gnome-session-binary[1201]: GLib-GObject-CRITICAL: g_object_unref: assertion 'G_IS_OBJECT (object)' failed
Dec 02 20:14:33 Windsor gnome-session-binary[1201]: GLib-GObject-CRITICAL: g_object_unref: assertion 'G_IS_OBJECT (object)' failed
Dec 02 20:14:33 Windsor gnome-session-binary[1201]: GLib-GObject-CRITICAL: g_object_unref: assertion 'G_IS_OBJECT (object)' failed
Dec 02 20:14:35 Windsor gnome-session[1201]: gnome-session-binary[1201]: GLib-GObject-CRITICAL: g_object_unref: assertion 'G_IS_OBJECT (object)' failed
Dec 02 20:14:35 Windsor gnome-session[1201]: gnome-session-binary[1201]: GLib-GObject-CRITICAL: g_object_unref: assertion 'G_IS_OBJECT (object)' failed
Dec 02 20:14:35 Windsor gnome-session-binary[1201]: GLib-GObject-CRITICAL: g_object_unref: assertion 'G_IS_OBJECT (object)' failed
Dec 02 20:14:35 Windsor gnome-session[1201]: gnome-session-binary[1201]: GLib-GObject-CRITICAL: g_object_unref: assertion 'G_IS_OBJECT (object)' failed
Dec 02 20:14:35 Windsor gnome-session-binary[1201]: GLib-GObject-CRITICAL: g_object_unref: assertion 'G_IS_OBJECT (object)' failed
Dec 02 20:14:35 Windsor systemd-logind[788]: System is rebooting.
Dec 02 20:14:35 Windsor gnome-session-binary[1201]: GLib-GObject-CRITICAL: g_object_unref: assertion 'G_IS_OBJECT (object)' failed
Dec 02 20:14:35 Windsor gnome-session-binary[1201]: GLib-GObject-CRITICAL: g_object_unref: assertion 'G_IS_OBJECT (object)' failed
Dec 02 20:14:35 Windsor gnome-session-binary[1201]: GLib-GObject-CRITICAL: g_object_unref: assertion 'G_IS_OBJECT (object)' failed
Dec 02 20:14:35 Windsor gnome-session-binary[1201]: GLib-GObject-CRITICAL: g_object_unref: assertion 'G_IS_OBJECT (object)' failed
Dec 02 20:14:35 Windsor systemd[1]: Stopped target Timers.
Dec 02 20:14:35 Windsor systemd[1]: Stopped target Graphical Interface.
Dec 02 20:14:35 Windsor systemd[1]: Stopped Trigger anacron every hour.
Dec 02 20:14:35 Windsor systemd[1]: Stopping User Manager for UID 1000...
Dec 02 20:14:35 Windsor systemd[1]: Stopped Daily apt upgrade and clean activities.
Dec 02 20:14:35 Windsor ModemManager[782]: <info>  Caught signal, shutting down...
Dec 02 20:14:35 Windsor systemd[1]: Stopping GNOME Display Manager...
Dec 02 20:14:35 Windsor apcupsd[821]: apcupsd exiting, signal 15
Dec 02 20:14:35 Windsor systemd[1]: Stopped target Multi-User System.
Dec 02 20:14:35 Windsor apcupsd[821]: apcupsd shutdown succeeded
Dec 02 20:14:35 Windsor systemd[1]: Stopping Modem Manager...
Dec 02 20:14:35 Windsor tracker-miner-user-guides.desktop[1416]: Received signal:15->'Terminated'
Dec 02 20:14:35 Windsor tracker-miner-apps.desktop[1424]: Received signal:15->'Terminated'
Dec 02 20:14:35 Windsor systemd[1]: Stopping Leviathan - Daemon for Kraken x61 Watercooler...
Dec 02 20:14:35 Windsor tracker-store[1415]: Received signal:15->'Terminated'
Dec 02 20:14:35 Windsor tracker-store[1415]: OK
Dec 02 20:14:35 Windsor org.a11y.atspi.Registry[983]: XIO:  fatal IO error 11 (Resource temporarily unavailable) on X server ":0"
Dec 02 20:14:35 Windsor org.a11y.atspi.Registry[983]:       after 33 requests (33 known processed) with 0 events remaining.
Dec 02 20:14:35 Windsor systemd[1]: Stopping Regular background program processing daemon...
Dec 02 20:14:35 Windsor kraken-start.sh[836]: I1202 20:14:35.110711   836 main.cpp:31] ... driver gracefully shutting down
Dec 02 20:14:35 Windsor /usr/lib/gdm3/gdm-x-session[870]: (II) UnloadModule: "libinput"
Dec 02 20:14:35 Windsor /usr/lib/gdm3/gdm-x-session[870]: (II) systemd-logind: releasing fd for 13:69
Dec 02 20:14:35 Windsor systemd[1]: Stopped target Login Prompts.
Dec 02 20:14:35 Windsor liblogging-stdlog[783]:  [origin software="rsyslogd" swVersion="8.24.0" x-pid="783" x-info="http://www.rsyslog.com"] exiting on signal 15.
Dec 02 20:14:35 Windsor systemd[1]: Stopping UPS power management daemon...
Dec 02 20:14:35 Windsor openrazer-daemon[1554]: 2018-12-02 20:14:35 | razer                          | INFO     | Stopping daemon on signal 15
Dec 02 20:14:35 Windsor openrazer-daemon[1554]: 2018-12-02 20:14:35 | razer.device1.keymanager       | DEBUG    | Stopping key manager
Dec 02 20:14:35 Windsor ModemManager[782]: <info>  ModemManager is shut down
Dec 02 20:14:35 Windsor systemd[1182]: Stopped target Default.
Dec 02 20:14:35 Windsor udisksd[1356]: udisks daemon version 2.1.8 exiting
Dec 02 20:14:35 Windsor systemd[1]: Stopping Make remote CUPS printers available locally...
Dec 02 20:14:35 Windsor dbus[803]: [system] Activating via systemd: service name='org.freedesktop.PolicyKit1' unit='polkit.service'
Dec 02 20:14:35 Windsor systemd[1182]: Stopping Evolution address book service...
Dec 02 20:14:35 Windsor systemd[1182]: Stopping D-Bus User Message Bus...
Dec 02 20:14:35 Windsor systemd[1]: Stopping keep memory of all UPnP devices that announced themselves...
Dec 02 20:14:35 Windsor systemd[1]: Stopped Daily apt download activities.
Dec 02 20:14:35 Windsor systemd[1]: Stopped target System Time Synchronized.
Dec 02 20:14:35 Windsor systemd[1182]: Stopping Tracker metadata database store and lookup manager...
Dec 02 20:14:35 Windsor systemd[1182]: Stopping Virtual filesystem service - digital camera monitor...
Dec 02 20:14:35 Windsor systemd[1]: Stopping Disk Manager...
Dec 02 20:14:35 Windsor systemd[1182]: Stopping Evolution source registry...
Dec 02 20:14:35 Windsor systemd[1182]: Stopping Virtual filesystem service - Apple File Conduit monitor...
Dec 02 20:14:35 Windsor systemd[1182]: Stopping Virtual filesystem service...
Dec 02 20:14:35 Windsor systemd[1182]: Stopping Virtual filesystem service - GNOME Online Accounts monitor...
Dec 02 20:14:35 Windsor systemd[1182]: Stopping Virtual filesystem service - Media Transfer Protocol monitor...
Dec 02 20:14:35 Windsor systemd[1182]: Stopping Virtual filesystem metadata service...
Dec 02 20:14:35 Windsor NetworkManager[814]: <info>  [1543799675.1054] ModemManager disappeared from bus
Dec 02 20:14:35 Windsor systemd[1]: Stopping Session c1 of user Debian-gdm.
Dec 02 20:14:35 Windsor systemd[1]: Stopped Daily Cleanup of Temporary Directories.
Dec 02 20:14:35 Windsor systemd[1]: Stopping PackageKit Daemon...
Dec 02 20:14:35 Windsor systemd[1]: Stopping Accounts Service...
Dec 02 20:14:35 Windsor systemd[1]: Stopping Session 2 of user dave.
Dec 02 20:14:35 Windsor unknown[991]: Failed to send session response GDBus.Error:org.freedesktop.DBus.Error.NoReply: Message recipient disconnected from message bus without replying
Dec 02 20:14:35 Windsor systemd[1]: Stopping Save/Restore Sound Card State...
Dec 02 20:14:35 Windsor systemd[1]: Stopping Authorization Manager...
Dec 02 20:14:35 Windsor dbus[803]: [system] Activation via systemd failed for unit 'polkit.service': Refusing activation, D-Bus is shutting down.
Dec 02 20:14:35 Windsor systemd[1]: Stopping User Manager for UID 116...
Dec 02 20:14:35 Windsor speech-dispatcher[1632]: speech-dispatcher disabled; edit /etc/default/speech-dispatcher.
Dec 02 20:14:35 Windsor avahi-daemon[1102]: Got SIGTERM, quitting.
Dec 02 20:14:35 Windsor systemd[865]: Stopped target Default.
Dec 02 20:14:35 Windsor avahi-daemon[1102]: Leaving mDNS multicast group on interface enp5s0.IPv6 with address 2600:1700:840:5610:21f:bcff:fe11:b383.
Dec 02 20:14:35 Windsor systemd[865]: Stopping Accessibility services bus...
Dec 02 20:14:35 Windsor avahi-daemon[1102]: Leaving mDNS multicast group on interface enp5s0.IPv4 with address 192.168.1.66.
Dec 02 20:14:35 Windsor systemd[865]: Stopping Sound Service...
Dec 02 20:14:35 Windsor avahi-daemon[1102]: avahi-daemon 0.6.32 exiting.
Dec 02 20:14:35 Windsor systemd[865]: Stopping D-Bus User Message Bus...
Dec 02 20:14:35 Windsor systemd[1]: Stopping Daemon for power management...
Dec 02 20:14:35 Windsor systemd[1]: Stopped target Sound Card.
Dec 02 20:14:35 Windsor systemd[1]: Stopping System Logging Service...
Dec 02 20:14:35 Windsor systemd[1]: Stopping Manage, Install and Generate Color Profiles...
Dec 02 20:14:35 Windsor systemd[1]: Stopping Unattended Upgrades Shutdown...
Dec 02 20:14:35 Windsor systemd[1]: Removed slice system-getty.slice.
Dec 02 20:14:35 Windsor systemd[1]: Stopping RealtimeKit Scheduling Policy Service...
Dec 02 20:14:35 Windsor systemd[1]: Stopping irqbalance daemon...
Dec 02 20:14:35 Windsor systemd[1]: Stopping LSB: Speech Dispatcher...
Dec 02 20:14:35 Windsor systemd[865]: Stopped D-Bus User Message Bus.
Dec 02 20:14:35 Windsor systemd[865]: Stopped Sound Service.
Dec 02 20:14:35 Windsor systemd[1182]: Stopping Evolution calendar service...
Dec 02 20:14:35 Windsor systemd[1182]: Stopping Daemon to manage razer devices in userspace...
Dec 02 20:14:35 Windsor systemd[1182]: Stopping Telepathy Mission Control service...
Dec 02 20:14:35 Windsor systemd[1182]: Stopping Virtual filesystem service - disk device monitor...
Dec 02 20:14:35 Windsor systemd[1182]: Stopped Evolution source registry.
Dec 02 20:14:35 Windsor systemd[1182]: Stopped Telepathy Mission Control service.
Dec 02 20:14:35 Windsor systemd[1182]: Stopped Virtual filesystem service - GNOME Online Accounts monitor.
Dec 02 20:14:35 Windsor systemd[1182]: Stopped Virtual filesystem service - digital camera monitor.
Dec 02 20:14:35 Windsor systemd[1182]: Stopped Virtual filesystem service - Apple File Conduit monitor.
Dec 02 20:14:35 Windsor systemd[1182]: Stopped Virtual filesystem service - Media Transfer Protocol monitor.
Dec 02 20:14:35 Windsor systemd[1182]: Stopped Evolution calendar service.
Dec 02 20:14:35 Windsor systemd[1182]: Stopped Tracker metadata database store and lookup manager.
Dec 02 20:14:35 Windsor systemd[1182]: Stopped Evolution address book service.
Dec 02 20:14:35 Windsor systemd[1182]: Stopped Virtual filesystem metadata service.
Dec 02 20:14:35 Windsor systemd[1]: Unmounted /run/user/1000/gvfs.
Dec 02 20:14:35 Windsor systemd[1]: Stopped Regular background program processing daemon.
Dec 02 20:14:35 Windsor systemd[1]: Stopped Modem Manager.
Dec 02 20:14:35 Windsor systemd[1]: Stopped System Logging Service.
Dec 02 20:14:35 Windsor systemd[1]: Stopped irqbalance daemon.
Dec 02 20:14:35 Windsor NetworkManager[814]: <warn>  [1543799675.1346] error requesting auth for org.freedesktop.NetworkManager.wifi.share.protected: Authorization check failed: The name :1.8 was not provided by
Dec 02 20:14:35 Windsor NetworkManager[814]: <warn>  [1543799675.1347] error requesting auth for org.freedesktop.NetworkManager.wifi.share.open: Authorization check failed: The name :1.8 was not provided by any 
Dec 02 20:14:35 Windsor systemd[1]: Stopped Accounts Service.
Dec 02 20:14:35 Windsor systemd[1]: Stopped UPS power management daemon.
Dec 02 20:14:35 Windsor systemd[1]: Stopped Authorization Manager.
Dec 02 20:14:35 Windsor systemd[1]: Stopped Leviathan - Daemon for Kraken x61 Watercooler.
Dec 02 20:14:35 Windsor systemd[1]: Stopped Daemon for power management.
Dec 02 20:14:35 Windsor systemd[1]: Stopped keep memory of all UPnP devices that announced themselves.
Dec 02 20:14:35 Windsor systemd[1]: Stopped PackageKit Daemon.
Dec 02 20:14:35 Windsor systemd[1]: Stopped Disk Manager.
Dec 02 20:14:35 Windsor systemd[1182]: Stopped Virtual filesystem service.
Dec 02 20:14:35 Windsor systemd[1182]: Stopped Virtual filesystem service - disk device monitor.
Dec 02 20:14:35 Windsor systemd[1]: Stopped Save/Restore Sound Card State.
Dec 02 20:14:35 Windsor /usr/lib/gdm3/gdm-x-session[1192]: (**) Option "fd" "44"
Dec 02 20:14:35 Windsor /usr/lib/gdm3/gdm-x-session[1192]: (**) Option "fd" "47"
Dec 02 20:14:35 Windsor /usr/lib/gdm3/gdm-x-session[1192]: (**) Option "fd" "48"
Dec 02 20:14:35 Windsor /usr/lib/gdm3/gdm-x-session[1192]: (**) Option "fd" "49"
Dec 02 20:14:35 Windsor /usr/lib/gdm3/gdm-x-session[1192]: (**) Option "fd" "50"
Dec 02 20:14:35 Windsor /usr/lib/gdm3/gdm-x-session[1192]: (**) Option "fd" "51"
Dec 02 20:14:35 Windsor systemd[1182]: Stopped D-Bus User Message Bus.
Dec 02 20:14:35 Windsor /usr/lib/gdm3/gdm-x-session[1192]: (**) Option "fd" "52"
Dec 02 20:14:35 Windsor /usr/lib/gdm3/gdm-x-session[1192]: (**) Option "fd" "53"
Dec 02 20:14:35 Windsor /usr/lib/gdm3/gdm-x-session[1192]: (**) Option "fd" "54"
Dec 02 20:14:35 Windsor /usr/lib/gdm3/gdm-x-session[1192]: (**) Option "fd" "55"
Dec 02 20:14:35 Windsor /usr/lib/gdm3/gdm-x-session[1192]: (**) Option "fd" "56"
Dec 02 20:14:35 Windsor /usr/lib/gdm3/gdm-x-session[1192]: (**) Option "fd" "57"
Dec 02 20:14:35 Windsor /usr/lib/gdm3/gdm-x-session[1192]: (**) Option "fd" "49"
Dec 02 20:14:35 Windsor /usr/lib/gdm3/gdm-x-session[1192]: (**) Option "fd" "53"
Dec 02 20:14:35 Windsor /usr/lib/gdm3/gdm-x-session[1192]: (**) Option "fd" "56"
Dec 02 20:14:35 Windsor systemd[1]: Stopped Make remote CUPS printers available locally.
Dec 02 20:14:35 Windsor NetworkManager[814]: <warn>  [1543799675.1606] error requesting auth for org.freedesktop.NetworkManager.wifi.share.protected: Authorization check failed: Refusing activation, D-Bus is shu
Dec 02 20:14:35 Windsor NetworkManager[814]: <warn>  [1543799675.1608] error requesting auth for org.freedesktop.NetworkManager.wifi.share.open: Authorization check failed: Refusing activation, D-Bus is shutting
Dec 02 20:14:35 Windsor systemd[1]: Stopping CUPS Scheduler...
Dec 02 20:14:35 Windsor systemd[1]: Stopping Avahi mDNS/DNS-SD Stack...
Dec 02 20:14:35 Windsor /usr/lib/gdm3/gdm-x-session[1192]: (II) UnloadModule: "libinput"
Dec 02 20:14:35 Windsor /usr/lib/gdm3/gdm-x-session[1192]: (II) systemd-logind: not releasing fd for 13:80, still in use
Dec 02 20:14:35 Windsor /usr/lib/gdm3/gdm-x-session[1192]: (II) UnloadModule: "libinput"
Dec 02 20:14:35 Windsor /usr/lib/gdm3/gdm-x-session[1192]: (II) systemd-logind: not releasing fd for 13:81, still in use
Dec 02 20:14:35 Windsor /usr/lib/gdm3/gdm-x-session[1192]: (II) UnloadModule: "libinput"
Dec 02 20:14:35 Windsor /usr/lib/gdm3/gdm-x-session[1192]: (II) systemd-logind: not releasing fd for 13:68, still in use
Dec 02 20:14:35 Windsor /usr/lib/gdm3/gdm-x-session[1192]: (II) UnloadModule: "libinput"
Dec 02 20:14:35 Windsor /usr/lib/gdm3/gdm-x-session[1192]: (II) systemd-logind: releasing fd for 13:78
Dec 02 20:14:35 Windsor systemd[1]: Stopped LSB: Speech Dispatcher.
Dec 02 20:14:35 Windsor systemd[1]: Stopped Avahi mDNS/DNS-SD Stack.
Dec 02 20:14:35 Windsor systemd[1]: Stopped target Network is Online.
Dec 02 20:14:35 Windsor systemd[1]: Stopped Network Manager Wait Online.
Dec 02 20:14:35 Windsor /usr/lib/gdm3/gdm-x-session[870]: (II) UnloadModule: "libinput"
Dec 02 20:14:35 Windsor /usr/lib/gdm3/gdm-x-session[870]: (II) systemd-logind: releasing fd for 13:67
Dec 02 20:14:35 Windsor systemd[1]: Stopped Manage, Install and Generate Color Profiles.
Dec 02 20:14:35 Windsor systemd[1]: Stopped RealtimeKit Scheduling Policy Service.
Dec 02 20:14:35 Windsor systemd[1]: Stopped CUPS Scheduler.
Dec 02 20:14:35 Windsor openrazer-daemon[1554]: 2018-12-02 20:14:35 | razer.device1.ripplemanager    | DEBUG    | Closing Ripple Manager
Dec 02 20:14:35 Windsor systemd[1]: Stopped Unattended Upgrades Shutdown.
Dec 02 20:14:35 Windsor /usr/lib/gdm3/gdm-x-session[1192]: (II) UnloadModule: "libinput"
Dec 02 20:14:35 Windsor /usr/lib/gdm3/gdm-x-session[1192]: (II) systemd-logind: releasing fd for 13:80
Dec 02 20:14:35 Windsor /usr/lib/gdm3/gdm-x-session[870]: (II) UnloadModule: "libinput"
Dec 02 20:14:35 Windsor /usr/lib/gdm3/gdm-x-session[870]: (II) systemd-logind: releasing fd for 13:66
Dec 02 20:14:35 Windsor gdm3[855]: GLib: g_hash_table_find: assertion 'version == hash_table->version' failed
Dec 02 20:14:35 Windsor systemd[1]: Stopped GNOME Display Manager.
Dec 02 20:14:35 Windsor /usr/lib/gdm3/gdm-x-session[1192]: (II) UnloadModule: "libinput"
Dec 02 20:14:35 Windsor /usr/lib/gdm3/gdm-x-session[1192]: (II) systemd-logind: releasing fd for 13:79
Dec 02 20:14:35 Windsor /usr/lib/gdm3/gdm-x-session[870]: (II) UnloadModule: "libinput"
Dec 02 20:14:35 Windsor /usr/lib/gdm3/gdm-x-session[870]: (II) systemd-logind: not releasing fd for 13:68, still in use
Dec 02 20:14:35 Windsor /usr/lib/gdm3/gdm-x-session[870]: (II) UnloadModule: "libinput"
Dec 02 20:14:35 Windsor /usr/lib/gdm3/gdm-x-session[870]: (II) systemd-logind: releasing fd for 13:68
Dec 02 20:14:35 Windsor openrazer-daemon[1554]: Stopping daemon.
Dec 02 20:14:35 Windsor openrazer-daemon[1554]: Error in atexit._run_exitfuncs:
Dec 02 20:14:35 Windsor openrazer-daemon[1554]: Traceback (most recent call last):
Dec 02 20:14:35 Windsor openrazer-daemon[1554]:   File "/usr/lib/python3/dist-packages/daemonize.py", line 72, in exit
Dec 02 20:14:35 Windsor openrazer-daemon[1554]:     sys.exit(0)
Dec 02 20:14:35 Windsor openrazer-daemon[1554]: SystemExit: 0
Dec 02 20:14:35 Windsor /usr/lib/gdm3/gdm-x-session[1192]: (II) UnloadModule: "libinput"
Dec 02 20:14:35 Windsor /usr/lib/gdm3/gdm-x-session[1192]: (II) systemd-logind: releasing fd for 13:69
Dec 02 20:14:35 Windsor /usr/lib/gdm3/gdm-x-session[870]: (II) UnloadModule: "libinput"
Dec 02 20:14:35 Windsor /usr/lib/gdm3/gdm-x-session[870]: (II) systemd-logind: releasing fd for 13:65
Dec 02 20:14:35 Windsor systemd[1182]: Stopped Daemon to manage razer devices in userspace.
Dec 02 20:14:35 Windsor systemd[1182]: Stopped target Basic System.
Dec 02 20:14:35 Windsor systemd[1182]: Stopped target Timers.
Dec 02 20:14:35 Windsor systemd[1182]: Stopped target Paths.
Dec 02 20:14:35 Windsor systemd[1182]: Stopped target Sockets.
Dec 02 20:14:35 Windsor systemd[1182]: Closed D-Bus User Message Bus Socket.
Dec 02 20:14:35 Windsor systemd[1182]: Closed GnuPG network certificate management daemon.
Dec 02 20:14:35 Windsor systemd[1182]: Closed GnuPG cryptographic agent (access for web browsers).
Dec 02 20:14:35 Windsor systemd[1182]: Closed GnuPG cryptographic agent and passphrase cache.
Dec 02 20:14:35 Windsor systemd[1182]: Closed GnuPG cryptographic agent and passphrase cache (restricted).
Dec 02 20:14:35 Windsor systemd[1182]: Closed GnuPG cryptographic agent (ssh-agent emulation).
Dec 02 20:14:35 Windsor systemd[1182]: Reached target Shutdown.
Dec 02 20:14:35 Windsor systemd[1182]: Starting Exit the Session...
Dec 02 20:14:35 Windsor systemd[1182]: Received SIGRTMIN+24 from PID 1672 (kill).
Dec 02 20:14:35 Windsor systemd[1183]: pam_unix(systemd-user:session): session closed for user dave
Dec 02 20:14:35 Windsor systemd[1]: Stopped User Manager for UID 1000.
Dec 02 20:14:35 Windsor /usr/lib/gdm3/gdm-x-session[870]: (II) UnloadModule: "libinput"
Dec 02 20:14:35 Windsor /usr/lib/gdm3/gdm-x-session[870]: (II) systemd-logind: releasing fd for 13:78
Dec 02 20:14:35 Windsor /usr/lib/gdm3/gdm-x-session[1192]: (II) UnloadModule: "libinput"
Dec 02 20:14:35 Windsor /usr/lib/gdm3/gdm-x-session[1192]: (II) systemd-logind: releasing fd for 13:81
Dec 02 20:14:35 Windsor /usr/lib/gdm3/gdm-x-session[870]: (II) UnloadModule: "libinput"
Dec 02 20:14:35 Windsor /usr/lib/gdm3/gdm-x-session[870]: (II) systemd-logind: not releasing fd for 13:81, still in use
Dec 02 20:14:35 Windsor /usr/lib/gdm3/gdm-x-session[870]: (II) UnloadModule: "libinput"
Dec 02 20:14:35 Windsor /usr/lib/gdm3/gdm-x-session[870]: (II) systemd-logind: releasing fd for 13:81
Dec 02 20:14:35 Windsor /usr/lib/gdm3/gdm-x-session[870]: (II) UnloadModule: "libinput"
Dec 02 20:14:35 Windsor /usr/lib/gdm3/gdm-x-session[870]: (II) systemd-logind: not releasing fd for 13:80, still in use
Dec 02 20:14:35 Windsor /usr/lib/gdm3/gdm-x-session[870]: (II) UnloadModule: "libinput"
Dec 02 20:14:35 Windsor /usr/lib/gdm3/gdm-x-session[870]: (II) systemd-logind: releasing fd for 13:80
Dec 02 20:14:35 Windsor /usr/lib/gdm3/gdm-x-session[1192]: (II) UnloadModule: "libinput"
Dec 02 20:14:35 Windsor /usr/lib/gdm3/gdm-x-session[1192]: (II) systemd-logind: releasing fd for 13:65
Dec 02 20:14:35 Windsor /usr/lib/gdm3/gdm-x-session[870]: (II) UnloadModule: "libinput"
Dec 02 20:14:35 Windsor /usr/lib/gdm3/gdm-x-session[870]: (II) systemd-logind: releasing fd for 13:79
Dec 02 20:14:35 Windsor /usr/lib/gdm3/gdm-x-session[1192]: (II) UnloadModule: "libinput"
Dec 02 20:14:35 Windsor /usr/lib/gdm3/gdm-x-session[1192]: (II) systemd-logind: releasing fd for 13:64
Dec 02 20:14:35 Windsor /usr/lib/gdm3/gdm-x-session[870]: (II) UnloadModule: "libinput"
Dec 02 20:14:35 Windsor /usr/lib/gdm3/gdm-x-session[870]: (II) systemd-logind: releasing fd for 13:64
Dec 02 20:14:35 Windsor /usr/lib/gdm3/gdm-x-session[1192]: (II) UnloadModule: "libinput"
Dec 02 20:14:35 Windsor /usr/lib/gdm3/gdm-x-session[1192]: (II) systemd-logind: releasing fd for 13:66
Dec 02 20:14:35 Windsor /usr/lib/gdm3/gdm-x-session[870]: (II) UnloadModule: "libinput"
Dec 02 20:14:35 Windsor /usr/lib/gdm3/gdm-x-session[870]: (II) systemd-logind: releasing fd for 13:71
Dec 02 20:14:35 Windsor /usr/lib/gdm3/gdm-x-session[870]: (II) UnloadModule: "libinput"
Dec 02 20:14:35 Windsor /usr/lib/gdm3/gdm-x-session[870]: (II) systemd-logind: releasing fd for 13:72
Dec 02 20:14:35 Windsor /usr/lib/gdm3/gdm-x-session[1192]: (II) UnloadModule: "libinput"
Dec 02 20:14:35 Windsor /usr/lib/gdm3/gdm-x-session[1192]: (II) systemd-logind: releasing fd for 13:68
Dec 02 20:14:35 Windsor /usr/lib/gdm3/gdm-x-session[1192]: (II) UnloadModule: "libinput"
Dec 02 20:14:35 Windsor /usr/lib/gdm3/gdm-x-session[1192]: (II) systemd-logind: releasing fd for 13:67
Dec 02 20:14:36 Windsor /usr/lib/gdm3/gdm-x-session[1192]: (II) UnloadModule: "libinput"
Dec 02 20:14:36 Windsor /usr/lib/gdm3/gdm-x-session[1192]: (II) systemd-logind: releasing fd for 13:71
Dec 02 20:14:36 Windsor /usr/lib/gdm3/gdm-x-session[1192]: (II) UnloadModule: "libinput"
Dec 02 20:14:36 Windsor /usr/lib/gdm3/gdm-x-session[1192]: (II) systemd-logind: releasing fd for 13:72
Dec 02 20:14:36 Windsor /usr/lib/gdm3/gdm-x-session[870]: (II) NVIDIA(GPU-0): Deleting GPU-0
Dec 02 20:14:36 Windsor /usr/lib/gdm3/gdm-x-session[870]: (II) NVIDIA(GPU-1): Renaming GPU-1 to GPU-0
Dec 02 20:14:36 Windsor /usr/lib/gdm3/gdm-x-session[870]: (II) NVIDIA(GPU-0): Deleting GPU-0
Dec 02 20:14:36 Windsor /usr/lib/gdm3/gdm-x-session[870]: (WW) xf86CloseConsole: KDSETMODE failed: Input/output error
Dec 02 20:14:36 Windsor /usr/lib/gdm3/gdm-x-session[870]: (WW) xf86CloseConsole: VT_GETMODE failed: Input/output error
Dec 02 20:14:36 Windsor /usr/lib/gdm3/gdm-x-session[870]: (WW) xf86CloseConsole: VT_ACTIVATE failed: Input/output error
Dec 02 20:14:36 Windsor /usr/lib/gdm3/gdm-x-session[870]: (II) Server terminated successfully (0). Closing log file.
Dec 02 20:14:36 Windsor kernel: nvidia-modeset: ERROR: GPU:0: Failed to query display engine channel state: 0x0000957d:0:0:0x00000033
Dec 02 20:14:36 Windsor kernel: nvidia-modeset: ERROR: GPU:0: Failed to query display engine channel state: 0x0000957d:0:1:0x00000033
Dec 02 20:14:36 Windsor kernel: nvidia-modeset: ERROR: GPU:0: Failed to query display engine channel state: 0x0000917e:0:0:0x00000033
Dec 02 20:14:36 Windsor kernel: nvidia-modeset: ERROR: GPU:0: Failed to query display engine channel state: 0x0000917e:0:1:0x00000033
Dec 02 20:14:36 Windsor kernel: nvidia-modeset: ERROR: GPU:0: Failed to query display engine channel state: 0x0000927c:0:0:0x00000033
Dec 02 20:14:36 Windsor kernel: nvidia-modeset: ERROR: GPU:0: Failed to query display engine channel state: 0x0000927c:0:1:0x00000033
Dec 02 20:14:36 Windsor kernel: nvidia-modeset: ERROR: GPU:0: Failed to query display engine channel state: 0x0000917e:1:0:0x00000033
Dec 02 20:14:36 Windsor kernel: nvidia-modeset: ERROR: GPU:0: Failed to query display engine channel state: 0x0000917e:1:1:0x00000033
Dec 02 20:14:36 Windsor kernel: nvidia-modeset: ERROR: GPU:0: Failed to query display engine channel state: 0x0000927c:1:0:0x00000033
Dec 02 20:14:36 Windsor kernel: nvidia-modeset: ERROR: GPU:0: Failed to query display engine channel state: 0x0000927c:1:1:0x00000033
Dec 02 20:14:36 Windsor kernel: nvidia-modeset: ERROR: GPU:0: Failed to query display engine channel state: 0x0000917e:2:0:0x00000033
Dec 02 20:14:36 Windsor kernel: nvidia-modeset: ERROR: GPU:0: Failed to query display engine channel state: 0x0000917e:2:1:0x00000033
Dec 02 20:14:36 Windsor kernel: nvidia-modeset: ERROR: GPU:0: Failed to query display engine channel state: 0x0000927c:2:0:0x00000033
Dec 02 20:14:36 Windsor kernel: nvidia-modeset: ERROR: GPU:0: Failed to query display engine channel state: 0x0000927c:2:1:0x00000033
Dec 02 20:14:36 Windsor kernel: nvidia-modeset: ERROR: GPU:0: Failed to query display engine channel state: 0x0000917e:3:0:0x00000033
Dec 02 20:14:36 Windsor kernel: nvidia-modeset: ERROR: GPU:0: Failed to query display engine channel state: 0x0000917e:3:1:0x00000033
Dec 02 20:14:36 Windsor kernel: nvidia-modeset: ERROR: GPU:0: Failed to query display engine channel state: 0x0000927c:3:0:0x00000033
Dec 02 20:14:36 Windsor kernel: nvidia-modeset: ERROR: GPU:0: Failed to query display engine channel state: 0x0000927c:3:1:0x00000033
Dec 02 20:14:36 Windsor kernel: nvidia-modeset: ERROR: GPU:0: Failed to query display engine channel state: 0x0000957d:0:0:0x00000033
Dec 02 20:14:36 Windsor kernel: nvidia-modeset: ERROR: GPU:0: Failed to query display engine channel state: 0x0000957d:0:1:0x00000033
Dec 02 20:14:36 Windsor kernel: nvidia-modeset: ERROR: GPU:0: Failed to query display engine channel state: 0x0000917e:0:0:0x00000033
Dec 02 20:14:36 Windsor kernel: nvidia-modeset: ERROR: GPU:0: Failed to query display engine channel state: 0x0000917e:0:1:0x00000033
Dec 02 20:14:36 Windsor kernel: nvidia-modeset: ERROR: GPU:0: Failed to query display engine channel state: 0x0000927c:0:0:0x00000033
Dec 02 20:14:36 Windsor kernel: nvidia-modeset: ERROR: GPU:0: Failed to query display engine channel state: 0x0000927c:0:1:0x00000033
Dec 02 20:14:36 Windsor kernel: nvidia-modeset: ERROR: GPU:0: Failed to query display engine channel state: 0x0000917e:1:0:0x00000033
Dec 02 20:14:36 Windsor kernel: nvidia-modeset: ERROR: GPU:0: Failed to query display engine channel state: 0x0000917e:1:1:0x00000033
Dec 02 20:14:36 Windsor kernel: nvidia-modeset: ERROR: GPU:0: Failed to query display engine channel state: 0x0000927c:1:0:0x00000033
Dec 02 20:14:36 Windsor kernel: nvidia-modeset: ERROR: GPU:0: Failed to query display engine channel state: 0x0000927c:1:1:0x00000033
Dec 02 20:14:36 Windsor kernel: nvidia-modeset: ERROR: GPU:0: Failed to query display engine channel state: 0x0000917e:2:0:0x00000033
Dec 02 20:14:36 Windsor kernel: nvidia-modeset: ERROR: GPU:0: Failed to query display engine channel state: 0x0000917e:2:1:0x00000033
Dec 02 20:14:36 Windsor kernel: nvidia-modeset: ERROR: GPU:0: Failed to query display engine channel state: 0x0000927c:2:0:0x00000033
Dec 02 20:14:36 Windsor kernel: nvidia-modeset: ERROR: GPU:0: Failed to query display engine channel state: 0x0000927c:2:1:0x00000033
Dec 02 20:14:36 Windsor kernel: nvidia-modeset: ERROR: GPU:0: Failed to query display engine channel state: 0x0000917e:3:0:0x00000033
Dec 02 20:14:36 Windsor kernel: nvidia-modeset: ERROR: GPU:0: Failed to query display engine channel state: 0x0000917e:3:1:0x00000033
Dec 02 20:14:36 Windsor kernel: nvidia-modeset: ERROR: GPU:0: Failed to query display engine channel state: 0x0000927c:3:0:0x00000033
Dec 02 20:14:36 Windsor kernel: nvidia-modeset: ERROR: GPU:0: Failed to query display engine channel state: 0x0000927c:3:1:0x00000033
Dec 02 20:14:36 Windsor kernel: nvidia-modeset: ERROR: GPU:0: Failed to query display engine channel state: 0x0000927c:0:0:0x00000033
Dec 02 20:14:36 Windsor kernel: nvidia-modeset: ERROR: GPU:0: Failed to query display engine channel state: 0x0000927c:1:0:0x00000033
Dec 02 20:14:36 Windsor kernel: nvidia-modeset: ERROR: GPU:0: Failed to query display engine channel state: 0x0000927c:2:0:0x00000033
Dec 02 20:14:36 Windsor kernel: nvidia-modeset: ERROR: GPU:0: Failed to query display engine channel state: 0x0000927c:3:0:0x00000033
Dec 02 20:14:36 Windsor kernel: nvidia-modeset: ERROR: GPU:0: Failed to query display engine channel state: 0x0000927c:0:1:0x00000033
Dec 02 20:14:36 Windsor kernel: nvidia-modeset: ERROR: GPU:0: Failed to query display engine channel state: 0x0000927c:1:1:0x00000033
Dec 02 20:14:36 Windsor kernel: nvidia-modeset: ERROR: GPU:0: Failed to query display engine channel state: 0x0000927c:2:1:0x00000033
Dec 02 20:14:36 Windsor kernel: nvidia-modeset: ERROR: GPU:0: Failed to query display engine channel state: 0x0000927c:3:1:0x00000033
Dec 02 20:14:36 Windsor kernel: nvidia-modeset: ERROR: GPU:0: Failed to query display engine channel state: 0x0000927c:0:0:0x00000033
Dec 02 20:14:36 Windsor kernel: nvidia-modeset: ERROR: GPU:0: Unable to update fliplock
Dec 02 20:14:36 Windsor kernel: nvidia-modeset: ERROR: GPU:0: Failed to query display engine channel state: 0x0000927c:1:0:0x00000033
Dec 02 20:14:36 Windsor kernel: nvidia-modeset: ERROR: GPU:0: Unable to update fliplock
Dec 02 20:14:36 Windsor kernel: nvidia-modeset: ERROR: GPU:0: Failed to query display engine channel state: 0x0000927c:0:1:0x00000033
Dec 02 20:14:36 Windsor kernel: nvidia-modeset: ERROR: GPU:1: Unable to update fliplock
Dec 02 20:14:36 Windsor kernel: nvidia-modeset: ERROR: GPU:0: Failed to query display engine channel state: 0x0000957d:0:0:0x00000033
Dec 02 20:14:36 Windsor kernel: nvidia-modeset: ERROR: GPU:0: Failed to query display engine channel state: 0x0000957d:0:1:0x00000033
Dec 02 20:14:36 Windsor systemd[865]: Stopped Accessibility services bus.
Dec 02 20:14:36 Windsor systemd[865]: Stopped target Basic System.
Dec 02 20:14:36 Windsor systemd[865]: Stopped target Sockets.
Dec 02 20:14:36 Windsor systemd[865]: Closed GnuPG cryptographic agent (access for web browsers).
Dec 02 20:14:36 Windsor systemd[865]: Closed GnuPG cryptographic agent (ssh-agent emulation).
Dec 02 20:14:36 Windsor systemd[866]: pam_unix(systemd-user:session): session closed for user Debian-gdm
Dec 02 20:14:36 Windsor systemd[1]: Stopped Session c1 of user Debian-gdm.
Dec 02 20:14:36 Windsor systemd[865]: Closed GnuPG network certificate management daemon.
Dec 02 20:14:36 Windsor systemd[865]: Closed GnuPG cryptographic agent and passphrase cache.
Dec 02 20:14:36 Windsor systemd[865]: Closed Sound System.
Dec 02 20:14:36 Windsor systemd[865]: Closed GnuPG cryptographic agent and passphrase cache (restricted).
Dec 02 20:14:36 Windsor systemd[865]: Stopped target Timers.
Dec 02 20:14:36 Windsor systemd[865]: Stopped target Paths.
Dec 02 20:14:36 Windsor systemd[865]: Closed D-Bus User Message Bus Socket.
Dec 02 20:14:36 Windsor systemd[865]: Reached target Shutdown.
Dec 02 20:14:36 Windsor systemd[865]: Starting Exit the Session...
Dec 02 20:14:36 Windsor systemd-logind[788]: Removed session c1.
Dec 02 20:14:36 Windsor systemd[865]: Received SIGRTMIN+24 from PID 1681 (kill).
Dec 02 20:14:36 Windsor systemd[1]: Stopped User Manager for UID 116.
Dec 02 20:14:36 Windsor systemd[1]: Removed slice User Slice of Debian-gdm.
Dec 02 20:14:36 Windsor systemd[1]: Unmounted /run/user/116.
Dec 02 20:16:05 Windsor systemd[1]: session-2.scope: Stopping timed out. Killing.
Dec 02 20:16:05 Windsor systemd[1]: session-2.scope: Killing process 1194 (Xorg) with signal SIGKILL.
Dec 02 20:17:35 Windsor systemd[1]: session-2.scope: Still around after SIGKILL. Ignoring.
Dec 02 20:17:35 Windsor systemd[1]: Stopped Session 2 of user dave.
Dec 02 20:17:35 Windsor systemd[1]: session-2.scope: Unit entered failed state.
Dec 02 20:17:35 Windsor systemd[1]: Removed slice User Slice of dave.
Dec 02 20:17:35 Windsor systemd[1]: Stopping Permit User Sessions...
Dec 02 20:17:35 Windsor systemd[1]: Stopping Login Service...
Dec 02 20:17:35 Windsor systemd[1]: Stopped Permit User Sessions.
Dec 02 20:17:35 Windsor systemd[1]: Stopped target Network.
Dec 02 20:17:35 Windsor systemd[1]: Stopping Network Manager...
Dec 02 20:17:35 Windsor NetworkManager[814]: <info>  [1543799855.4844] caught SIGTERM, shutting down normally.
Dec 02 20:17:35 Windsor systemd[1]: Stopping Raise network interfaces...
Dec 02 20:17:35 Windsor systemd[1]: Stopping WPA supplicant...
Dec 02 20:17:35 Windsor systemd[1]: Stopped target Remote File Systems.
Dec 02 20:17:35 Windsor systemd[1]: Stopped WPA supplicant.
Dec 02 20:17:35 Windsor NetworkManager[814]: <info>  [1543799855.4937] exiting (success)
Dec 02 20:17:35 Windsor systemd[1]: Stopped Network Manager.
Dec 02 20:17:35 Windsor systemd[1]: Stopping D-Bus System Message Bus...
Dec 02 20:17:35 Windsor systemd[1]: Stopped D-Bus System Message Bus.
Dec 02 20:17:35 Windsor systemd[1]: Stopped Raise network interfaces.
Dec 02 20:17:35 Windsor systemd[1]: Stopped Login Service.
Dec 02 20:17:35 Windsor systemd[1]: Stopped target User and Group Name Lookups.
Dec 02 20:17:35 Windsor systemd[1]: Stopped target Basic System.
Dec 02 20:17:35 Windsor systemd[1]: Stopped target Sockets.
Dec 02 20:17:35 Windsor systemd[1]: Closed Syslog Socket.
Dec 02 20:17:35 Windsor systemd[1]: Closed CUPS Scheduler.
Dec 02 20:17:35 Windsor systemd[1]: Closed Avahi mDNS/DNS-SD Stack Activation Socket.
Dec 02 20:17:35 Windsor systemd[1]: Closed D-Bus System Message Bus Socket.
Dec 02 20:17:35 Windsor systemd[1]: Stopped target Paths.
Dec 02 20:17:35 Windsor systemd[1]: Stopped CUPS Scheduler.
Dec 02 20:17:35 Windsor systemd[1]: Stopped target Slices.
Dec 02 20:17:35 Windsor systemd[1]: Removed slice User and Session Slice.
Dec 02 20:17:35 Windsor systemd[1]: Stopped target System Initialization.
Dec 02 20:17:35 Windsor systemd[1]: Stopping Network Time Synchronization...
Dec 02 20:17:35 Windsor systemd[1]: Stopping Update UTMP about System Boot/Shutdown...
Dec 02 20:17:35 Windsor systemd[1]: Stopping Load/Save Random Seed...
Dec 02 20:17:35 Windsor systemd[1]: Stopped target Swap.
Dec 02 20:17:35 Windsor systemd[1]: Deactivating swap /dev/disk/by-partuuid/a9f2c143-45c2-4d7d-a664-5abc2ffa13c6...
Dec 02 20:17:35 Windsor systemd[1]: Stopped target Encrypted Volumes.
Dec 02 20:17:35 Windsor systemd[1]: Stopped Forward Password Requests to Wall Directory Watch.
Dec 02 20:17:35 Windsor systemd[1]: Stopped Dispatch Password Requests to Console Directory Watch.
Dec 02 20:17:35 Windsor systemd[1]: Stopped Apply Kernel Variables.
Dec 02 20:17:35 Windsor systemd[1]: Stopped Load Kernel Modules.
Dec 02 20:17:35 Windsor systemd[1]: Stopped Load/Save Random Seed.
Dec 02 20:17:35 Windsor systemd[1]: Stopped Update UTMP about System Boot/Shutdown.
Dec 02 20:17:35 Windsor systemd[1]: Deactivated swap /dev/disk/by-path/pci-0000:00:1f.2-ata-5-part1.
Dec 02 20:17:35 Windsor systemd[1]: Deactivated swap /dev/disk/by-partuuid/a9f2c143-45c2-4d7d-a664-5abc2ffa13c6.
Dec 02 20:17:35 Windsor systemd[1]: Deactivated swap /dev/disk/by-id/wwn-0x50014ee20c6129ba-part1.
Dec 02 20:17:35 Windsor systemd[1]: Deactivated swap /dev/disk/by-id/ata-WDC_WD1003FZEX-00MK2A0_WD-WCC3F1URDZ9F-part1.
Dec 02 20:17:35 Windsor systemd[1]: Deactivated swap /dev/sdb1.
Dec 02 20:17:35 Windsor systemd[1]: Deactivated swap /dev/disk/by-uuid/caeb2c62-9416-4a7d-b508-9da4f2a84bb9.
Dec 02 20:17:35 Windsor systemd[1]: Stopped Network Time Synchronization.
Dec 02 20:17:35 Windsor systemd[1]: Stopped Create Volatile Files and Directories.
Dec 02 20:17:35 Windsor systemd[1]: Stopped target Local File Systems.
Dec 02 20:17:35 Windsor systemd[1]: Unmounting /opt...
Dec 02 20:17:35 Windsor systemd[1]: Unmounting /home...
Dec 02 20:17:35 Windsor systemd[1]: Unmounting /boot/efi...
Dec 02 20:17:35 Windsor systemd[1]: Unmounting /run/user/1000...
Dec 02 20:17:35 Windsor systemd[1]: home.mount: Mount process exited, code=exited status=32
Dec 02 20:17:35 Windsor systemd[1]: Failed unmounting /home.
Dec 02 20:17:35 Windsor systemd[1]: Stopped File System Check on /dev/disk/by-uuid/710c0e2f-1d67-41d1-97fa-e358b18f106a.
Dec 02 20:17:35 Windsor systemd[1]: Unmounted /boot/efi.
Dec 02 20:17:35 Windsor systemd[1]: Stopped File System Check on /dev/disk/by-uuid/4DBB-F3E4.
Dec 02 20:17:35 Windsor systemd[1]: Unmounted /run/user/1000.
Dec 02 20:17:35 Windsor systemd[1]: Unmounted /opt.
Dec 02 20:17:35 Windsor systemd[1]: Reached target Unmount All Filesystems.
Dec 02 20:17:35 Windsor systemd[1]: Stopped File System Check on /dev/disk/by-uuid/02d8966a-b6b0-4deb-981a-77ee9f264e4b.
Dec 02 20:17:35 Windsor systemd[1]: Removed slice system-systemd\x2dfsck.slice.
Dec 02 20:17:35 Windsor systemd[1]: Stopped target Local File Systems (Pre).
Dec 02 20:17:35 Windsor systemd[1]: Stopped Create Static Device Nodes in /dev.
Dec 02 20:17:35 Windsor systemd[1]: Stopped Remount Root and Kernel File Systems.
Dec 02 20:17:35 Windsor systemd[1]: Reached target Shutdown.
Dec 02 20:17:35 Windsor systemd[1]: Reached target Final Step.
Dec 02 20:17:35 Windsor systemd[1]: Starting Reboot...
Dec 02 20:17:35 Windsor systemd[1]: Shutting down.
Dec 02 20:17:35 Windsor kernel: systemd-shutdow: 36 output lines suppressed due to ratelimiting
Dec 02 20:17:35 Windsor systemd-shutdown[1]: Sending SIGTERM to remaining processes...
Dec 02 20:17:35 Windsor systemd-journald[371]: Journal stopped
By carefully switching one setting at a time over the course of several days, I have come to the conclusion that the error only occurs when basemosaic is on. That said, I think I need basemosaic to get the multiscreen support...if there is a better way to do it, please let me know.

My xorg.conf file is as follows:

Code: Select all

Section "ServerLayout"
    Identifier     "Layout0"
    Screen      0  "Screen0" 0 0
    Option         "Xinerama" "0"
EndSection

Section "Files"
EndSection

Section "Monitor"
    Identifier     "Monitor0"
    VendorName     "Unknown"
    ModelName      "Ancor Communications Inc VS248"
    Option         "DPMS"
EndSection

Section "Device"
    Identifier     "Device0"
    Driver         "nvidia"
    VendorName     "NVIDIA Corporation"
    BoardName      "GeForce GTX 980 Ti"
    BusID          "PCI:1:0:0"
EndSection

Section "Screen"
    Identifier     "Screen0"
    Device         "Device0"
    Monitor        "Monitor0"
    DefaultDepth    24
    Option         "Stereo" "0"
    Option         "nvidiaXineramaInfoOrder" "DFP-1"
    Option         "metamodes" "GPU-72cfef8c-e88c-7211-3a4d-65f41325f355.HDMI-0: nvidia-auto-select +1920+0, GPU-72cfef8c-e88c-7211-3a4d-65f41325f355.DP-1: nvidia-auto-select +3840+0, GPU-2b34884b-ddfc-ce7f-181a-292943324b9c.HDMI-0: nvidia-auto-select +0+0"
    Option         "MultiGPU" "Off"
    Option         "SLI" "off"
    Option         "BaseMosaic" "on"
    SubSection     "Display"
        Depth       24
    EndSubSection
EndSection
I am on 4.9.0-8-amd64 and running nvidia drivers version 390.87. This is a new installation from the latest stable build as of three days ago. The only changes that were made are:
* installing sudo and chrome
* setting journal to persist the logs
* adding nomodeset boot parameter in grub

I have gone through multiple sites, including nvidia's driver documentation, nvidia's discussion forums, these forums, and a dozen other sites from google and have not found an answer to this issue.

Am I making a mistake somewhere? What else should I be looking at to help triage?

Thanks!
Top
User avatar
Head_on_a_Stick
Posts: 14114
Joined: 2014-06-01 17:46
Location: London, England
Has thanked: 81 times
Been thanked: 133 times

Re: nVidia Basemosaic black screen on session restart

#2 Post by Head_on_a_Stick »

Try the nouveau drivers.
deadbang
Top
User avatar
llivv
Posts: 5340
Joined: 2007-02-14 18:10
Location: cold storage

Re: nVidia Basemosaic black screen on session restart

#3 Post by llivv »

good initial post
you got a lot further than most nvidia posts I've seen here using stable

Info missing in the OP
  • onboard graphics - yes/no - link to evga x99 mobo page or mobo model #
    nvidia packages installed - list all
    method used to install nvidia module ?
    did you follow the debian nvidia wiki - yes / no
    did you add i386 arch - yes/no
    did you blacklist nouveau - yes/no
    did you try i915-modeset=1 instead of nomodeset - yes/no
    what are you using as a guide for xorg.conf options
scroll 3/4 the way down the posted journal above to see this

Code: Select all

Dec 02 20:14:36 Windsor /usr/lib/gdm3/gdm-x-session[870]: (II) NVIDIA(GPU-0): Deleting GPU-0
Dec 02 20:14:36 Windsor /usr/lib/gdm3/gdm-x-session[870]: (II) NVIDIA(GPU-1): Renaming GPU-1 to GPU-0
Dec 02 20:14:36 Windsor /usr/lib/gdm3/gdm-x-session[870]: (II) NVIDIA(GPU-0): Deleting GPU-0
Dec 02 20:14:36 Windsor /usr/lib/gdm3/gdm-x-session[870]: (WW) xf86CloseConsole: KDSETMODE failed: Input/output error
Dec 02 20:14:36 Windsor /usr/lib/gdm3/gdm-x-session[870]: (WW) xf86CloseConsole: VT_GETMODE failed: Input/output error
Dec 02 20:14:36 Windsor /usr/lib/gdm3/gdm-x-session[870]: (WW) xf86CloseConsole: VT_ACTIVATE failed: Input/output error
Dec 02 20:14:36 Windsor /usr/lib/gdm3/gdm-x-session[870]: (II) Server terminated successfully (0). Closing log file.
Dec 02 20:14:36 Windsor kernel: nvidia-modeset: ERROR: GPU:0: Failed to query display engine channel state: 0x0000957d:0:0:0x00000033
Dec 02 20:14:36 Windsor kernel: nvidia-modeset: ERROR: GPU:0: Failed to query display engine channel state: 0x0000957d:0:1:0x00000033
Dec 02 20:14:36 Windsor kernel: nvidia-modeset: ERROR: GPU:0: Failed to query display engine channel state: 0x0000917e:0:0:0x00000033
Dec 02 20:14:36 Windsor kernel: nvidia-modeset: ERROR: GPU:0: Failed to query display engine channel state: 0x0000917e:0:1:0x00000033
Dec 02 20:14:36 Windsor kernel: nvidia-modeset: ERROR: GPU:0: Failed to query display engine channel state: 0x0000927c:0:0:0x00000033
Dec 02 20:14:36 Windsor kernel: nvidia-modeset: ERROR: GPU:0: Failed to query display engine channel state: 0x0000927c:0:1:0x00000033
Dec 02 20:14:36 Windsor kernel: nvidia-modeset: ERROR: GPU:0: Failed to query display engine channel state: 0x0000917e:1:0:0x00000033
Dec 02 20:14:36 Windsor kernel: nvidia-modeset: ERROR: GPU:0: Failed to query display engine channel state: 0x0000917e:1:1:0x00000033
Dec 02 20:14:36 Windsor kernel: nvidia-modeset: ERROR: GPU:0: Failed to query display engine channel state: 0x0000927c:1:0:0x00000033
Dec 02 20:14:36 Windsor kernel: nvidia-modeset: ERROR: GPU:0: Failed to query display engine channel state: 0x0000927c:1:1:0x00000033
Dec 02 20:14:36 Windsor kernel: nvidia-modeset: ERROR: GPU:0: Failed to query display engine channel state: 0x0000917e:2:0:0x00000033
Dec 02 20:14:36 Windsor kernel: nvidia-modeset: ERROR: GPU:0: Failed to query display engine channel state: 0x0000917e:2:1:0x00000033
Dec 02 20:14:36 Windsor kernel: nvidia-modeset: ERROR: GPU:0: Failed to query display engine channel state: 0x0000927c:2:0:0x00000033
Dec 02 20:14:36 Windsor kernel: nvidia-modeset: ERROR: GPU:0: Failed to query display engine channel state: 0x0000927c:2:1:0x00000033
Dec 02 20:14:36 Windsor kernel: nvidia-modeset: ERROR: GPU:0: Failed to query display engine channel state: 0x0000917e:3:0:0x00000033
Dec 02 20:14:36 Windsor kernel: nvidia-modeset: ERROR: GPU:0: Failed to query display engine channel state: 0x0000917e:3:1:0x00000033
Dec 02 20:14:36 Windsor kernel: nvidia-modeset: ERROR: GPU:0: Failed to query display engine channel state: 0x0000927c:3:0:0x00000033
Dec 02 20:14:36 Windsor kernel: nvidia-modeset: ERROR: GPU:0: Failed to query display engine channel state: 0x0000927c:3:1:0x00000033
Dec 02 20:14:36 Windsor kernel: nvidia-modeset: ERROR: GPU:0: Failed to query display engine channel state: 0x0000957d:0:0:0x00000033
Dec 02 20:14:36 Windsor kernel: nvidia-modeset: ERROR: GPU:0: Failed to query display engine channel state: 0x0000957d:0:1:0x00000033
Dec 02 20:14:36 Windsor kernel: nvidia-modeset: ERROR: GPU:0: Failed to query display engine channel state: 0x0000917e:0:0:0x00000033
Dec 02 20:14:36 Windsor kernel: nvidia-modeset: ERROR: GPU:0: Failed to query display engine channel state: 0x0000917e:0:1:0x00000033
Dec 02 20:14:36 Windsor kernel: nvidia-modeset: ERROR: GPU:0: Failed to query display engine channel state: 0x0000927c:0:0:0x00000033
Dec 02 20:14:36 Windsor kernel: nvidia-modeset: ERROR: GPU:0: Failed to query display engine channel state: 0x0000927c:0:1:0x00000033
Dec 02 20:14:36 Windsor kernel: nvidia-modeset: ERROR: GPU:0: Failed to query display engine channel state: 0x0000917e:1:0:0x00000033
Dec 02 20:14:36 Windsor kernel: nvidia-modeset: ERROR: GPU:0: Failed to query display engine channel state: 0x0000917e:1:1:0x00000033
Dec 02 20:14:36 Windsor kernel: nvidia-modeset: ERROR: GPU:0: Failed to query display engine channel state: 0x0000927c:1:0:0x00000033
Dec 02 20:14:36 Windsor kernel: nvidia-modeset: ERROR: GPU:0: Failed to query display engine channel state: 0x0000927c:1:1:0x00000033
Dec 02 20:14:36 Windsor kernel: nvidia-modeset: ERROR: GPU:0: Failed to query display engine channel state: 0x0000917e:2:0:0x00000033
Dec 02 20:14:36 Windsor kernel: nvidia-modeset: ERROR: GPU:0: Failed to query display engine channel state: 0x0000917e:2:1:0x00000033
Dec 02 20:14:36 Windsor kernel: nvidia-modeset: ERROR: GPU:0: Failed to query display engine channel state: 0x0000927c:2:0:0x00000033
Dec 02 20:14:36 Windsor kernel: nvidia-modeset: ERROR: GPU:0: Failed to query display engine channel state: 0x0000927c:2:1:0x00000033
Dec 02 20:14:36 Windsor kernel: nvidia-modeset: ERROR: GPU:0: Failed to query display engine channel state: 0x0000917e:3:0:0x00000033
Dec 02 20:14:36 Windsor kernel: nvidia-modeset: ERROR: GPU:0: Failed to query display engine channel state: 0x0000917e:3:1:0x00000033
Dec 02 20:14:36 Windsor kernel: nvidia-modeset: ERROR: GPU:0: Failed to query display engine channel state: 0x0000927c:3:0:0x00000033
Dec 02 20:14:36 Windsor kernel: nvidia-modeset: ERROR: GPU:0: Failed to query display engine channel state: 0x0000927c:3:1:0x00000033
Dec 02 20:14:36 Windsor kernel: nvidia-modeset: ERROR: GPU:0: Failed to query display engine channel state: 0x0000927c:0:0:0x00000033
Dec 02 20:14:36 Windsor kernel: nvidia-modeset: ERROR: GPU:0: Failed to query display engine channel state: 0x0000927c:1:0:0x00000033
Dec 02 20:14:36 Windsor kernel: nvidia-modeset: ERROR: GPU:0: Failed to query display engine channel state: 0x0000927c:2:0:0x00000033
Dec 02 20:14:36 Windsor kernel: nvidia-modeset: ERROR: GPU:0: Failed to query display engine channel state: 0x0000927c:3:0:0x00000033
Dec 02 20:14:36 Windsor kernel: nvidia-modeset: ERROR: GPU:0: Failed to query display engine channel state: 0x0000927c:0:1:0x00000033
Dec 02 20:14:36 Windsor kernel: nvidia-modeset: ERROR: GPU:0: Failed to query display engine channel state: 0x0000927c:1:1:0x00000033
Dec 02 20:14:36 Windsor kernel: nvidia-modeset: ERROR: GPU:0: Failed to query display engine channel state: 0x0000927c:2:1:0x00000033
Dec 02 20:14:36 Windsor kernel: nvidia-modeset: ERROR: GPU:0: Failed to query display engine channel state: 0x0000927c:3:1:0x00000033
Dec 02 20:14:36 Windsor kernel: nvidia-modeset: ERROR: GPU:0: Failed to query display engine channel state: 0x0000927c:0:0:0x00000033
Dec 02 20:14:36 Windsor kernel: nvidia-modeset: ERROR: GPU:0: Unable to update fliplock
Dec 02 20:14:36 Windsor kernel: nvidia-modeset: ERROR: GPU:0: Failed to query display engine channel state: 0x0000927c:1:0:0x00000033
Dec 02 20:14:36 Windsor kernel: nvidia-modeset: ERROR: GPU:0: Unable to update fliplock
Dec 02 20:14:36 Windsor kernel: nvidia-modeset: ERROR: GPU:0: Failed to query display engine channel state: 0x0000927c:0:1:0x00000033
Dec 02 20:14:36 Windsor kernel: nvidia-modeset: ERROR: GPU:1: Unable to update fliplock
Dec 02 20:14:36 Windsor kernel: nvidia-modeset: ERROR: GPU:0: Failed to query display engine channel state: 0x0000957d:0:0:0x00000033
Dec 02 20:14:36 Windsor kernel: nvidia-modeset: ERROR: GPU:0: Failed to query display engine channel state: 0x0000957d:0:1:0x00000033
Dec 02 20:14:36 Windsor systemd[865]: Stopped Accessibility services bus.
the xorg.conf looks really fuggly to me. (I know jack sheetuffer what the current state of the blo0obb note is in the repos)

you can read the man pages for
xorg.conf
nvidia-xconfig
to clean up xorg.conf
both manuals have a steep learning curve
but the one option at a time is the correct way to test options
In memory of Ian Ashley Murdock (1973 - 2015) founder of the Debian project.
Top
dmatta22201
Posts: 3
Joined: 2018-12-03 00:46

Re: nVidia Basemosaic black screen on session restart

#4 Post by dmatta22201 »

Hey, thanks for the starting points. Here are some answers to the questions.

Onboard graphics - No, this is an Intel i7-5930K Haswell-E CPU on a evga x99 Classified (131-HE-E995-KR)
nvidia packages installed - hers is output of dpkg -l | grep 'nvidia'

Code: Select all

ii  glx-alternative-nvidia                0.8.8~bpo9+1                                amd64        allows the selection of NVIDIA as GLX provider
ii  libegl-nvidia0:amd64                  390.87-2~bpo9+1                             amd64        NVIDIA binary EGL library
ii  libgl1-nvidia-glvnd-glx:amd64         390.87-2~bpo9+1                             amd64        NVIDIA binary OpenGL/GLX library (GLVND variant)
ii  libgles-nvidia2:amd64                 390.87-2~bpo9+1                             amd64        NVIDIA binary OpenGL|ES 2.x library
ii  libglx-nvidia0:amd64                  390.87-2~bpo9+1                             amd64        NVIDIA binary GLX library
ii  libnvidia-cfg1:amd64                  390.87-2~bpo9+1                             amd64        NVIDIA binary OpenGL/GLX configuration library
ii  libnvidia-egl-wayland1:amd64          390.87-2~bpo9+1                             amd64        NVIDIA binary Wayland EGL external platform library
ii  libnvidia-eglcore:amd64               390.87-2~bpo9+1                             amd64        NVIDIA binary EGL core libraries
ii  libnvidia-glcore:amd64                390.87-2~bpo9+1                             amd64        NVIDIA binary OpenGL/GLX core libraries
ii  libnvidia-ml1:amd64                   390.87-2~bpo9+1                             amd64        NVIDIA Management Library (NVML) runtime library
ii  nvidia-alternative                    390.87-2~bpo9+1                             amd64        allows the selection of NVIDIA as GLX provider
ii  nvidia-driver                         390.87-2~bpo9+1                             amd64        NVIDIA metapackage
ii  nvidia-driver-bin                     390.87-2~bpo9+1                             amd64        NVIDIA driver support binaries
ii  nvidia-driver-libs:amd64              390.87-2~bpo9+1                             amd64        NVIDIA metapackage (OpenGL/GLX/EGL/GLES libraries)
ii  nvidia-egl-common                     390.87-2~bpo9+1                             amd64        NVIDIA binary EGL driver - common files
ii  nvidia-egl-icd:amd64                  390.87-2~bpo9+1                             amd64        NVIDIA EGL installable client driver (ICD)
ii  nvidia-egl-wayland-common             390.87-2~bpo9+1                             amd64        NVIDIA binary Wayland EGL external platform - common files
ii  nvidia-egl-wayland-icd:amd64          390.87-2~bpo9+1                             amd64        NVIDIA Wayland EGL external platform library (ICD)
ii  nvidia-installer-cleanup              20151021+4                                  amd64        cleanup after driver installation with the nvidia-installer
ii  nvidia-kernel-common                  20151021+4                                  amd64        NVIDIA binary kernel module support files
ii  nvidia-kernel-dkms                    390.87-2~bpo9+1                             amd64        NVIDIA binary kernel module DKMS source
ii  nvidia-kernel-support                 390.87-2~bpo9+1                             amd64        NVIDIA binary kernel module support files
ii  nvidia-legacy-check                   390.87-2~bpo9+1                             amd64        check for NVIDIA GPUs requiring a legacy driver
ii  nvidia-modprobe                       384.111-2~deb9u1                            amd64        utility to load NVIDIA kernel modules and create device nodes
ii  nvidia-persistenced                   384.111-1~deb9u1                            amd64        daemon to maintain persistent software state in the NVIDIA driver
ii  nvidia-settings                       390.48-2~bpo9+1                             amd64        tool for configuring the NVIDIA graphics driver
ii  nvidia-support                        20151021+4                                  amd64        NVIDIA binary graphics driver support files
ii  nvidia-vdpau-driver:amd64             390.87-2~bpo9+1                             amd64        Video Decode and Presentation API for Unix - NVIDIA driver
ii  nvidia-vulkan-common                  390.87-2~bpo9+1                             amd64        NVIDIA Vulkan driver - common files
ii  nvidia-vulkan-icd:amd64               390.87-2~bpo9+1                             amd64        NVIDIA Vulkan installable client driver (ICD)
ii  nvidia-xconfig                        384.111-1~deb9u1                            amd64        deprecated X configuration tool for non-free NVIDIA drivers
ii  xserver-xorg-video-nvidia             390.87-2~bpo9+1                             amd64        NVIDIA binary Xorg driver
Method used to install nvidia module - I basically followed the instructions on https://wiki.debian.org/NvidiaGraphicsD ... ckports.29
Did I follow debian nvidia wiki - Yes
Did I add i386 arch - Not at this time...I added it later when I was getting other things running
Did I blacklist nouveau - Not specifically, I was following the wiki step 4 which says restart your system to enable the nouveau blacklist.
Did I try i915-modset=1 - No, will try and see if that works.

Guides for xorg.conf options - well, I started with the debian wiki https://wiki.debian.org/NvidiaGraphicsD ... figuration and nvidia driver documentation https://us.download.nvidia.com/XFree86/ ... index.html. I also looked at different versions of what nvidia-settings produces when I set things up and did a save to Xorg.config (note, I never actually saved things there, I just looked at the previews of what it would be, then pieced together what different settings mean and do based on the driver documentation. Lastly, dozens of forum posts on multiple monitors on debian, ubuntu, and other distros. Things like https://askubuntu.com/questions/421730/ ... ter-reboot and http://forums.debian.net/viewtopic.php?f=5&t=133303 and https://forum.manjaro.org/t/nvidia-sli- ... itor/54049

Will check out the manuals listed. Thanks!
Top
User avatar
llivv
Posts: 5340
Joined: 2007-02-14 18:10
Location: cold storage

Re: nVidia Basemosaic black screen on session restart

#5 Post by llivv »

dmatta22201 wrote:I also looked at different versions of what nvidia-settings produces when I set things up and did a save to Xorg.config (note, I never actually saved things there, I just looked at the previews of what it would be, then pieced together what different settings mean and do based on the driver documentation.
There is nothing wrong with saving an auto generated
xorg.conf file. Especially if you use it as a template to build a working configuration file.
/etc/X11/xorg.conf
/etc/X11/xorg.cond.d/20-any-name-you-choose-here.conf
are the perfered conventions for Debian custom X config files
(not sure if you knew that already)

check on nouveau
lsmod |grep nouveau
blacklist nouveau

It has something to do with KMS and modeswitching iirc from years ago.
wondering if that is why using nomodeset


backup and move xorg.conf out of the way

Code: Select all

mv /etc/X11/xorg.conf /etc/X11/xorg.conf.bak

try this one and see if it works OK
/etc/X11/xorg.conf.d /12-triple.conf

Section "Device"
    Identifier "gForce0"
    Driver     "nvidia"
    Screen     0
EndSection
 
Section "Device"
    Identifier "gForce0"
    Driver     "nvidia"
    Screen     1
EndSection

Section "Device"
    Identifier "gForce1"
    Driver     "nvidia"
    Screen     2
EndSection

Don't quote me on that either - but I think it's worth a try to get you started

It's always good to see how X starts without a conf file as a baseline to work from.
And start browsing the Xorg.0.log
as that is the only way to tell for sure if changes made to the config file are being used or ignored
In memory of Ian Ashley Murdock (1973 - 2015) founder of the Debian project.
Top
dmatta22201
Posts: 3
Joined: 2018-12-03 00:46

Re: nVidia Basemosaic black screen on session restart

#6 Post by dmatta22201 »

Ok, so setting i915-modeset=1 has no difference.

That said, I did discover something else...if I do not log in, the error does not happen. Start the computer, wait until it gets to the gnome lock screen, then just shutdown and no issues. However, if once I log in, the problem occurs.

Is there a good place to read about how gdm3 and/or X11 starts up? Specifically, what happens during the switch from the login screen to the desktop. Are there different settings files that get read? I am seeing two logs (Xorg.0.log and Xorg.1.log) and they look sequential, so I think an X server is started (Server 0) to handle the login, then a second server is started (Server 1) once I log in. Once I log out, I assume that it should close Server 1 and return back to Server 0, but it seems that Server 0 never picks back up.

Looking at the startup messages in Xorg.0.log and Xorg.1.log, the only difference I see of note is that in Xorg.0.log, I see two Nvidia setting mode statements later in the log

Code: Select all

[    17.990] (II) NVIDIA(0): Setting mode "GPU-0.HDMI-0: nvidia-auto-select @1920x1080 +1920+0 {ViewPortIn=1920x1080, ViewPortOut=1920x1080+0+0}, GPU-1.HDMI-0: nvidia-auto-select @1920x1080 +0+0 {ViewPortIn=1920x1080, ViewPortOut=1920x1080+0+0}"
[    18.428] (II) NVIDIA(0): Setting mode "GPU-0.DP-1: nvidia-auto-select @1920x1080 +3840+0 {AllowGSYNC=Off, ViewPortIn=1920x1080, ViewPortOut=1920x1080+0+0}, GPU-0.HDMI-0: nvidia-auto-select @1920x1080 +1920+0 {ViewPortIn=1920x1080, ViewPortOut=1920x1080+0+0}, GPU-1.HDMI-0: nvidia-auto-select @1920x1080 +0+0 {ViewPortIn=1920x1080, ViewPortOut=1920x1080+0+0}"
In Xorg.1.log, I see

Code: Select all

[    68.948] (II) NVIDIA(0): Setting mode "GPU-0.DP-1: nvidia-auto-select @1920x1080 +3840+0 {ViewPortIn=1920x1080, ViewPortOut=1920x1080+0+0}, GPU-1.HDMI-0: nvidia-auto-select @1920x1080 +0+0 {ViewPortIn=1920x1080, ViewPortOut=1920x1080+0+0}"
[    69.388] (II) NVIDIA(0): Setting mode "GPU-0.DP-1: nvidia-auto-select @1920x1080 +3840+0 {ViewPortIn=1920x1080, ViewPortOut=1920x1080+0+0}, GPU-0.HDMI-0: nvidia-auto-select @1920x1080 +1920+0 {ViewPortIn=1920x1080, ViewPortOut=1920x1080+0+0}, GPU-1.HDMI-0: nvidia-auto-select @1920x1080 +0+0 {ViewPortIn=1920x1080, ViewPortOut=1920x1080+0+0}"
These settings, while close to what I have in my /etc/X11/xorg.conf, are not the same. I am wondering where or how nvidia is setting these and if the differences are relevant.

Thoughts?
Top
User avatar
llivv
Posts: 5340
Joined: 2007-02-14 18:10
Location: cold storage

Re: nVidia Basemosaic black screen on session restart

#7 Post by llivv »

I think
Xorg.0.log is the log of the current running xsession
Xorg.1.log is the log of the pervious non-running xsession
but you could be right
I have only 1 Xorg.0.log file in ~/.local/share/xorg
but I have two others in /var/log
Xorg.0.log
Xorg.0.log.old
and they are the first two files in /var/log
instead of the last files - the way they used to be.

I don't run nvidia graphics these days so my suggestions may be way off
but I do remember some stuff.

to find if xorg.conf options are being used or ignored you have to keep reading the log and learn what's in there.
look for things like
Options "BaseMosaic" "on" Loaded
or
Options "BaseMosaic" "on" Not Used

unless you have the options in your /etc/X11/xorg.conf file memoried
have a copy of it to look at while you are reading the Xorg.0.log
so you can check them off the list as you find them.
Options like
Option "nvidiaXineramaInfoOrder" "DFP-1"

one way to see what happens during shutdown and startup is to
startup to GDM and CTRL+ALT+F1 to the console and kill gdm3
than look at the Xorg.0.log
than restart gdm3 from the console and a new xsession will start
from the GDM login screen CTRL+ALT+F1 to the console
leave gdm3 running but look at the new Xorg.0.log

FWIW - it's alot easier to figure out what is going on with the xserver
with a minimal xserver install
and without a session loader XDM GDM KDM lightDM.
All the automagic builtin makes it harder to figure out what the log is showing.

since squeeze or wheezy X hasn't needed a config file in most cases.

sorry i915-modeset=1 would have no effect unless you had onboard video
which you don't my bad.
In memory of Ian Ashley Murdock (1973 - 2015) founder of the Debian project.
Top
User avatar
llivv
Posts: 5340
Joined: 2007-02-14 18:10
Location: cold storage

Re: nVidia Basemosaic black screen on session restart

#8 Post by llivv »

you should run the nvidia-installer-cleanup
which will get rid of the xserver-xorg-video-nvidia packages you still have installed.

I'd also get rid of all the other xserver-xorg-video-*all* packages that are installed.
except xserver-xorg-video-vesa for a backup Very Basic xsession just in case.
nomodeset is most likely complacating things too....

Than read the info page for nvidia-settings
/etc/X11/xorg.conf.d/15-file.conf OR /xtc/X11/xorg.conf

Code: Select all

Section "ServerLayout"
    Identifier     "Layout0"
    Screen      0  "Screen0" 0 0
    Option         "Xinerama" "0"
EndSection

Section "Monitor"
    Identifier     "Monitor0"
    ModelName      "Ancor Communications Inc VS248"
    Option         "DPMS"
EndSection

Section "Device"
    Identifier     "Device0"
    Driver         "nvidia"
   BoardName      "GeForce GTX 980 Ti"
    BusID          "PCI:1:0:0"
EndSection

Section "Screen"
    Identifier     "Screen0"
    Device         "Device0"
     Monitor        "Monitor0"
     DefaultDepth    24
    Option         "Stereo" "0"
    Option         "nvidiaXineramaInfoOrder" "DFP-1"
    Option         "metamodes" "GPU-72cfef8c-e88c-7211-3a4d-65f41325f355.HDMI-0: nvidia-auto-select +1920+0, GPU-72cfef8c-e88c-7211-3a4d-65f41325f355.DP-1: nvidia-auto-select +3840+0, GPU-2b34884b-ddfc-ce7f-181a-292943324b9c.HDMI-0: nvidia-auto-select +0+0"
    Option         "MultiGPU" "Off"
    Option         "SLI" "off"
    Option         "BaseMosaic" "on"
    SubSection     "Display"
        Depth       24
    EndSubSection
EndSection
I removed 4 lines of cruft from what you posted above,
It still looks to me like it's missing the section for the second GPU
run

Code: Select all

lspci -b
to get the busID of the second GPU than try adding

Code: Select all

Section "Device"
        Identifier     "Device1"
    Driver         "nvidia"
   BoardName      "GeForce GTX 980 Ti"
    BusID          "PCI:new bus id here:0:0"  
EndSection
and see if that changes anything

run nvidia-settings again and see if you notice multiple listings for
Sections
Monitor Device Screen

With the second Section Device added it probably also needs corrosponding
Monitor and Screen Sections that point at Section "Device" Identifier "Device1" for Monitor 2 and Screen 2 ie: the second GPU running monitor 3

I'm surprised you get 3 Screens working with only one Device Section.

The xorg.conf file gets more complex as Sections are added
take note typically there would be 2 Section "Device" Identifier "Device1"
entries with corrosponding Monitor1 and Screen1 sections for GPU0
as well as more entries for Screen1 and Screen2 in Section "ServerLayout"
And you already know the base xorg.conf file to start debugging from

Code: Select all

Section "Device"
    Identifier     "Device0"
    Driver         "nvidia"
EndSection
In memory of Ian Ashley Murdock (1973 - 2015) founder of the Debian project.
Top
Post Reply

Return to “System and Network configuration”