You are not logged in.
I guess when I only have the nvidia device section uncommented, it is not finding my laptop's screen?
$ DISPLAY=:0 xrandr
Screen 0: minimum 8 x 8, current 640 x 480, maximum 32767 x 32767
DP-0 disconnected primary (normal left inverted right x axis y axis)
DP-1 disconnected (normal left inverted right x axis y axis)
DP-2 disconnected (normal left inverted right x axis y axis)
HDMI-0 disconnected (normal left inverted right x axis y axis)
DP-3 disconnected (normal left inverted right x axis y axis)Normally when in an X session the screen is eDP-1.
Offline
-rw-r--r-- 1 root root 1279 Oct 31 19:06 /etc/X11/xorg.conf
-rw-r--r-- 1 root root 1279 Oct 31 19:06 /etc/X11/xorg.conf.nvidia-xconfig-original
-rw-r--r-- 1 root root 1431 Nov 4 01:34 20-nvidia.confxorg.conf is not empty.
Move all of those away from /etc/X11
cat /etc/X11/xorg.conf.d/40-dpi.confOffline
xorg.conf is not empty but it is all commented out. it contained an older version of nvidia-xconfig.
40-dpi.conf is also commented out (for testing)
#Section "Monitor"
# Identifier "<default monitor>"
# DisplaySize 344 194
#EndSectionMoving the files changes nothing.
Offline
Please post and updated Xorg log and journal
Offline
0x0.st is down so using a different pastebin
journal: https://p.defau.lt/?ae2rT3uaSvk5uKzneB81Tg
xorg: https://p.defau.lt/?70YZbQm0IrwvzV9594QzZQ
xorg configs: https://p.defau.lt/?fo8OcIG63fS7fDExD2d5OA
Offline
key, X11 log now looks standard optimus: you're running modestting on the IGP and there's no output attached to the nvidia GPU.
If should™ be completely irrelevant to anything else unless you're exporting DRI_PRIME etc. to the session.
glxinfo -Bsays you're running on the intel chip?
There's nothing nvidia related around the suspend (and the GPU is also not supposed to be relevant to get pixels from X11 to your monitor)
Nov 05 11:07:56 incertia-t15g kernel: i915 0000:00:02.0: [drm] *ERROR* Failed to probe lspcon
Nov 05 11:07:56 incertia-t15g kernel: i915 0000:00:02.0: [drm] Registered 3 planes with drm panic
Nov 05 11:07:56 incertia-t15g kernel: [drm] Initialized i915 1.6.0 for 0000:00:02.0 on minor 2
Nov 05 11:07:57 incertia-t15g kernel: i915 0000:00:02.0: [drm] *ERROR* Failed to probe lspcon
Nov 05 11:07:57 incertia-t15g kernel: i915 0000:00:02.0: [drm] *ERROR* LSPCON init failed on port D
Nov 05 11:07:59 incertia-t15g kernel: i915 0000:00:02.0: [drm] *ERROR* Failed to probe lspcon
Nov 05 11:07:59 incertia-t15g kernel: i915 0000:00:02.0: [drm] *ERROR* LSPCON init failed on port D
Nov 05 11:07:59 incertia-t15g kernel: snd_hda_intel 0000:00:1f.3: bound 0000:00:02.0 (ops intel_audio_component_bind_ops [i915])
Nov 05 11:07:59 incertia-t15g kernel: fbcon: i915drmfb (fb0) is primary device
Nov 05 11:08:01 incertia-t15g kernel: i915 0000:00:02.0: [drm] fb0: i915drmfb frame buffer device
Nov 05 11:08:02 incertia-t15g kernel: i915 0000:00:02.0: [drm] *ERROR* Failed to probe lspcon
Nov 05 11:08:02 incertia-t15g kernel: i915 0000:00:02.0: [drm] *ERROR* LSPCON init failed on port D
Nov 05 11:08:03 incertia-t15g kernel: i915 0000:00:02.0: [drm] *ERROR* Failed to probe lspcon
Nov 05 11:08:03 incertia-t15g kernel: i915 0000:00:02.0: [drm] *ERROR* LSPCON init failed on port D
Nov 05 11:08:10 incertia-t15g kernel: i915 0000:00:02.0: [drm] *ERROR* Failed to probe lspcon
Nov 05 11:08:10 incertia-t15g kernel: i915 0000:00:02.0: [drm] *ERROR* LSPCON init failed on port D
Nov 05 11:08:12 incertia-t15g kernel: i915 0000:00:02.0: [drm] *ERROR* Failed to probe lspcon
Nov 05 11:08:12 incertia-t15g kernel: i915 0000:00:02.0: [drm] *ERROR* LSPCON init failed on port D
Nov 05 11:08:56 incertia-t15g kernel: mei_hdcp 0000:00:16.0-b638ab7e-94e2-4ea2-a552-d1c54b627f04: bound 0000:00:02.0 (ops i915_hdcp_ops [i915])
Nov 05 11:08:56 incertia-t15g kernel: i915 0000:00:02.0: [drm] *ERROR* Failed to probe lspcon
Nov 05 11:08:56 incertia-t15g kernel: i915 0000:00:02.0: [drm] *ERROR* LSPCON init failed on port DIf you're checking your older journals for one where you've been using nouveau, did i915 issue those errors as well?
Edit: on a fringe theory:
Nov 05 11:07:54 incertia-t15g kernel: hid-generic 0003:CA04:2377.0001: input,hidraw0: USB HID v1.11 Keyboard [CannonKeys Rekt1800] on usb-0000:00:14.0-1/input0
Nov 05 11:07:54 incertia-t15g kernel: input: CannonKeys Rekt1800 Mouse as /devices/pci0000:00/0000:00:14.0/usb1/1-1/1-1:1.1/0003:CA04:2377.0002/input/input6
Nov 05 11:07:54 incertia-t15g kernel: input: CannonKeys Rekt1800 System Control as /devices/pci0000:00/0000:00:14.0/usb1/1-1/1-1:1.1/0003:CA04:2377.0002/input/input7
Nov 05 11:07:54 incertia-t15g kernel: input: CannonKeys Rekt1800 Consumer Control as /devices/pci0000:00/0000:00:14.0/usb1/1-1/1-1:1.1/0003:CA04:2377.0002/input/input8
Nov 05 11:07:54 incertia-t15g kernel: input: CannonKeys Rekt1800 Keyboard as /devices/pci0000:00/0000:00:14.0/usb1/1-1/1-1:1.1/0003:CA04:2377.0002/input/input9Can you try the behavior w/o those?
Last edited by seth (2025-11-05 21:24:58)
Offline
Edit: on a fringe theory:
Nov 05 11:07:54 incertia-t15g kernel: hid-generic 0003:CA04:2377.0001: input,hidraw0: USB HID v1.11 Keyboard [CannonKeys Rekt1800] on usb-0000:00:14.0-1/input0 Nov 05 11:07:54 incertia-t15g kernel: input: CannonKeys Rekt1800 Mouse as /devices/pci0000:00/0000:00:14.0/usb1/1-1/1-1:1.1/0003:CA04:2377.0002/input/input6 Nov 05 11:07:54 incertia-t15g kernel: input: CannonKeys Rekt1800 System Control as /devices/pci0000:00/0000:00:14.0/usb1/1-1/1-1:1.1/0003:CA04:2377.0002/input/input7 Nov 05 11:07:54 incertia-t15g kernel: input: CannonKeys Rekt1800 Consumer Control as /devices/pci0000:00/0000:00:14.0/usb1/1-1/1-1:1.1/0003:CA04:2377.0002/input/input8 Nov 05 11:07:54 incertia-t15g kernel: input: CannonKeys Rekt1800 Keyboard as /devices/pci0000:00/0000:00:14.0/usb1/1-1/1-1:1.1/0003:CA04:2377.0002/input/input9Can you try the behavior w/o those?
Are you serious. I unplugged the keyboard and it works (albeit after a small delay). Now the real question is why is this only an issue with nvidia installed?
Last edited by incertia (2025-11-06 01:23:10)
Offline
Are you serious.
Sometimes
You could try whether the devices work when touching one to your head and the other one to your butt.
I'm not sure whether it's related but
Nov 05 11:07:56 incertia-t15g kernel: nvidia-gpu 0000:01:00.3: i2c timeout error e0000000
Nov 05 11:07:56 incertia-t15g kernel: ucsi_ccg 0-0008: i2c_transfer failed -110
Nov 05 11:07:56 incertia-t15g kernel: ucsi_ccg 0-0008: ucsi_ccg_init failed - -110
Nov 05 11:07:56 incertia-t15g kernel: ucsi_ccg 0-0008: probe with driver ucsi_ccg failed with error -110 that's the usb controller on your GPU (for VR goggles) - you could try to blacklist ucsi_ccg
https://bbs.archlinux.org/viewtopic.php?id=308155
Still
If you're checking your older journals for one where you've been using nouveau, did i915 issue those errors as well?
Offline
If you're checking your older journals for one where you've been using nouveau, did i915 issue those errors as well?
I don't remember ever installing nouveau, but I've been getting that same i915 error on Lenovo laptops for the past 7 years, although my memory might not quite be the best. It wasn't causing any issues so I just let it be.
For now I just remove the keyboard before doing anything related to VTs, but I'll try changing some settings regarding it later.
Offline