Arch Linux

n8henrie

Member

From: Shiprock, NM

Registered: 2014-03-30

Posts: 45

Website

Black screen when ending X session or changing TTY

Hi all,

For a few months now my screen turns off after displaying "no signal input" whenever I end an X session or change to a different tty (e.g. ctrl-alt-F2).

I'm using i3 and start it with `startx`. If I exit i3 with mod-shift-E, after the screen goes blank, I can type `startx` and it turns back on. If I switch to a different TTY, the screen goes blank, but if I go back with ctrl-alt-F1, it turns back on.

I use the nvidia drivers with a dedicated nvidia gpu; I've tried both the linux and linux-lts kernels with no differences. I've tried changing my kernel parameters to use nvidia-drm.modeset=1 as well as nomodeset with no difference in this behavior between the two. I need to stay on `nvidia` because I use CUDA quite a bit, so unfortunately I think nouveau and i3 alternatives like sway are out of the question.

I see several posts with relevant problems dating back several years, but I haven't found a solution. So far, I've tried looking through xorg.0.log, journalctl -xf (from an ssh session) while I trigger the undesired behavior, dmesg --follow, and removing my xorg.conf.

I don't see any notable errors here:

$ grep '(EE)' /var/log/Xorg.0.log
        (WW) warning, (EE) error, (NI) not implemented, (??) unknown.
[    18.505] (EE) libinput: MOSART Semi. 2.4G Keyboard Mouse: Failed to create a device for /dev/input/event10
[    18.505] (EE) PreInit returned 2 for "MOSART Semi. 2.4G Keyboard Mouse"
[    18.700] (EE) libinput: MOSART Semi. 2.4G Keyboard Mouse: Failed to create a device for /dev/input/mouse0
[    18.700] (EE) PreInit returned 2 for "MOSART Semi. 2.4G Keyboard Mouse"
[   386.499] (EE) event2  - SINO WEALTH USB KEYBOARD: client bug: event processing lagging behind by 29ms, your system is too slow

I think the most interesting thing I've found so far is a note that `systemd-logind` is "pausing" whenever I trigger the behavior by trying to change TTYs -- lots of messages like what I see below.

[   325.751] (II) systemd-logind: got pause for 13:71
[   325.751] (II) systemd-logind: got pause for 13:70
[   325.751] (II) systemd-logind: got pause for 13:67
[   325.751] (II) systemd-logind: got pause for 13:72
[   328.636] (II) systemd-logind: got resume for 13:64
[   328.652] (--) NVIDIA(GPU-0): Westinghouse Digital Electronics LCM-22w3 (DFP-0): connected
[   328.652] (--) NVIDIA(GPU-0): Westinghouse Digital Electronics LCM-22w3 (DFP-0): Internal TMDS
[   328.652] (--) NVIDIA(GPU-0): Westinghouse Digital Electronics LCM-22w3 (DFP-0): 330.0 MHz maximum pixel clock
[   328.652] (--) NVIDIA(GPU-0):
[   328.652] (--) NVIDIA(GPU-0): DFP-1: disconnected
[   328.653] (--) NVIDIA(GPU-0): DFP-1: Internal TMDS
[   328.653] (--) NVIDIA(GPU-0): DFP-1: 165.0 MHz maximum pixel clock
[   328.653] (--) NVIDIA(GPU-0):
[   328.653] (--) NVIDIA(GPU-0): DFP-2: disconnected
[   328.653] (--) NVIDIA(GPU-0): DFP-2: Internal DisplayPort
[   328.653] (--) NVIDIA(GPU-0): DFP-2: 1440.0 MHz maximum pixel clock
[   328.653] (--) NVIDIA(GPU-0):
[   328.653] (--) NVIDIA(GPU-0): DFP-3: disconnected
[   328.653] (--) NVIDIA(GPU-0): DFP-3: Internal TMDS
[   328.653] (--) NVIDIA(GPU-0): DFP-3: 165.0 MHz maximum pixel clock
[   328.653] (--) NVIDIA(GPU-0):
[   328.653] (--) NVIDIA(GPU-0): DFP-4: disconnected
[   328.653] (--) NVIDIA(GPU-0): DFP-4: Internal DisplayPort
[   328.653] (--) NVIDIA(GPU-0): DFP-4: 1440.0 MHz maximum pixel clock
[   328.653] (--) NVIDIA(GPU-0):
[   328.653] (--) NVIDIA(GPU-0): DFP-5: disconnected
[   328.653] (--) NVIDIA(GPU-0): DFP-5: Internal TMDS
[   328.653] (--) NVIDIA(GPU-0): DFP-5: 165.0 MHz maximum pixel clock
[   328.653] (--) NVIDIA(GPU-0):
[   328.653] (--) NVIDIA(GPU-0): DFP-6: disconnected
[   328.653] (--) NVIDIA(GPU-0): DFP-6: Internal DisplayPort
[   328.653] (--) NVIDIA(GPU-0): DFP-6: 1440.0 MHz maximum pixel clock
[   328.653] (--) NVIDIA(GPU-0):
[   328.653] (--) NVIDIA(GPU-0): DFP-7: disconnected
[   328.653] (--) NVIDIA(GPU-0): DFP-7: Internal TMDS
[   328.653] (--) NVIDIA(GPU-0): DFP-7: 165.0 MHz maximum pixel clock
[   328.653] (--) NVIDIA(GPU-0):
[   328.674] (II) NVIDIA(0): Setting mode "DFP-0:nvidia-auto-select"
[   328.714] (II) event0  - Power Button: is tagged by udev as: Keyboard
[   328.715] (II) event0  - Power Button: device is a keyboard
[   328.734] (II) systemd-logind: got resume for 13:65
[   328.735] (II) event1  - Power Button: is tagged by udev as: Keyboard
[   328.735] (II) event1  - Power Button: device is a keyboard
[   328.735] (II) systemd-logind: got resume for 13:68
[   328.736] (II) event4  - SINO WEALTH USB KEYBOARD Consumer Control: is tagged by udev as: Keyboard
[   328.736] (II) event4  - SINO WEALTH USB KEYBOARD Consumer Control: device is a keyboard
[   328.756] (II) systemd-logind: got resume for 13:69
[   328.756] (II) event5  - SINO WEALTH USB KEYBOARD Keyboard: is tagged by udev as: Keyboard
[   328.757] (II) event5  - SINO WEALTH USB KEYBOARD Keyboard: device is a keyboard
[   328.783] (II) systemd-logind: got resume for 13:73
[   328.784] (II) event9  - MOSART Semi. 2.4G Keyboard Mouse System Control: is tagged by udev as: Keyboard
[   328.784] (II) event9  - MOSART Semi. 2.4G Keyboard Mouse System Control: device is a keyboard
[   328.825] (II) systemd-logind: got resume for 13:66
[   328.826] (II) event2  - SINO WEALTH USB KEYBOARD: is tagged by udev as: Keyboard
[   328.826] (II) event2  - SINO WEALTH USB KEYBOARD: device is a keyboard
[   328.876] (II) systemd-logind: got resume for 13:71
[   328.878] (II) event7  - MOSART Semi. 2.4G Keyboard Mouse: is tagged by udev as: Mouse
[   328.878] (II) event7  - MOSART Semi. 2.4G Keyboard Mouse: device is a pointer
[   328.916] (II) systemd-logind: got resume for 13:70
[   328.918] (II) event6  - MOSART Semi. 2.4G Keyboard Mouse: is tagged by udev as: Keyboard
[   328.918] (II) event6  - MOSART Semi. 2.4G Keyboard Mouse: device is a keyboard
[   328.956] (II) systemd-logind: got resume for 13:67
[   328.958] (II) event3  - SINO WEALTH USB KEYBOARD System Control: is tagged by udev as: Keyboard
[   328.958] (II) event3  - SINO WEALTH USB KEYBOARD System Control: device is a keyboard
[   328.996] (II) systemd-logind: got resume for 13:72
[   328.998] (II) event8  - MOSART Semi. 2.4G Keyboard Mouse Consumer Control: is tagged by udev as: Keyboard
[   328.998] (II) event8  - MOSART Semi. 2.4G Keyboard Mouse Consumer Control: device is a keyboard

Interestingly, I don't see these entries when I run `less +F ~/.local/share/xorg/Xorg.0.log` in alacritty, then ctrl-alt-F2 (screen goes blank, wait a little while), then ctrl-alt-F1 to get back to my i3 session -- there are no new entries in the log. I only see them show up (in real time) when I am using a separate SSH session.

Thanks in advance if anyone has any ideas; I'd love to get back to being able to use the console primarily but have the option to `startx` into an i3 session and exit back to the console easily.

Sharopo

Member

From: Phoenix

Registered: 2013-05-01

Posts: 11

Re: Black screen when ending X session or changing TTY

Probably a long shot, but did you ever get this resolved and do you remember said resolution? I have the exact same thing happening.

V1del

Forum Moderator

Registered: 2012-10-16

Posts: 21,657

Re: Black screen when ending X session or changing TTY

In general please don't necrobump 2 year old threads. This issue can usually be fixed by explicitly enabling modeset support in the nvidia driver: https://wiki.archlinux.org/title/NVIDIA … de_setting

Should this not suffice please open a new thread.

Sharopo

Member

From: Phoenix

Registered: 2013-05-01

Posts: 11

Re: Black screen when ending X session or changing TTY

Thanks for the forum lesson, I will do better moving forward. Additionally, that fix appears to have worked for me.