NOTHING except Gnome works with nvidia on my machine

navknight · 2024-07-03 03:07:55

I have an Intel Core i5, Nvidia 3050 setup, and I have tried Fedora and Linux mint opensuse before finally settling on Arch Linux recently.
I have nvidia-dkms drivers installed with the "nvidia nvidia_modeset nvidia_uvm nvidia_drm" modules in mkinitcpio and the "nvidia_drm.modeset=1 nvidia_drm.fbdev=1 nvidia.NVreg_PreserveVideoMemoryAllocations=1" in the grub_cmd_line parameters with nvidia-suspend and nvidia-resume enabled.

The problem I am facing is with sleep. Only Gnome behaves well with suspend on my machine, and everything else fails to resume properly. This has been the case with all the distros I have tried. What happens is that the laptop goes to sleep, and then when I try to wake it up, the screen comes on for 5-10 seconds and then goes black again for 10-15 seconds, and I can make key presses during the 5 seconds the screen is on.

I am clueless as to what I should do to fix this issue because I want to move away from Gnome due to the lack of proper fractional scaling. I want to switch to i3 or hyprland but the lack of suspend-resume support is not allowing me to do so.

seth · 2024-07-03 07:02:50

the screen comes on for 5-10 seconds and then goes black again for 10-15 seconds

And what happens then?

I can make key presses during the 5 seconds the screen is on

Input while the key is off isn't registered? (Try to type into a text editor or so)

What is the exact context where you experienced that? i3? hyprland? something else (console)?
Is there a screenlocker involved? Sounds like it could just be DPMS…

navknight · 2024-07-03 16:27:57

seth wrote:

the screen comes on for 5-10 seconds and then goes black again for 10-15 seconds
And what happens then?
I can make key presses during the 5 seconds the screen is on
Input while the key is off isn't registered? (Try to type into a text editor or so)
What is the exact context where you experienced that? i3? hyprland? something else (console)?
Is there a screenlocker involved? Sounds like it could just be DPMS…

The key presses get registered even when the screen is black. I got past sddm by inputting my password and hitting enter.
Till now only the GDM + Gnome combo is able to resume properly without this issue, everything else has this issue. For KDE, even after getting past sddm by luckily entering the password, the issue persisted even in the KDE desktop session. This issue is there for i3+GDM, Hyprland+GDM, cinnamon + lightdm. Everything except gnome is broken for me.

The journalctl shows that nvidia-resume was successful for all these cases

Last edited by navknight (2024-07-03 16:29:35)

seth · 2024-07-03 21:45:52

even after getting past sddm

hold on, your OP says this is about resuming from sleep only? Not on boot or general login?

Fwwi, there're multiple reports reg. the 555xx drivers causing output problems - if you've updated to that version, you might want to test https://aur.archlinux.org/packages/nvidia-535xx-dkms
Add "nvidia.NVreg_EnableGpuFirmware=0" to the kernel parameters and check "cat /proc/cmdline" to make sure it applied - or wait for the next nvidia driver release…

If that's not it please post your complete system journal for a boot covering this, eg.

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

for the previous ("-1") one.

navknight · 2024-07-04 03:42:40

hold on, your OP says this is about resuming from sleep only? Not on boot or general login?

Yes, this issue is with sleep-resume only and nothing else.

If that's not it please post your complete system journal for a boot covering this, eg.

I am not sure if that will help, because if I start the system and log into gnome, sleep works. Now without rebooting if I log into KDE, sleep-resume is broken.

I am unsure if it's a boot time issue. I will post the journalctl in a bit

seth · 2024-07-04 06:54:36

The journal covers way more than the boot - what you're seeing after resuming from an S3 isn't the DM but some screenlocker
I'd not be surprised if your general DM is GDM and that ends up being related to the problem, but we first need to establish the actual context of the behavior.

Edit: because the resume is "broken", the suggestion was to pick the journal of the previous boot after a reboot.

Last edited by seth (2024-07-04 06:55:19)

navknight · 2024-07-04 14:19:36

seth wrote:

The journal covers way more than the boot - what you're seeing after resuming from an S3 isn't the DM but some screenlocker
I'd not be surprised if your general DM is GDM and that ends up being related to the problem, but we first need to establish the actual context of the behavior.
Edit: because the resume is "broken", the suggestion was to pick the journal of the previous boot after a reboot.

http://0x0.st/XaDq.bin is the journalctrl from previous boot

seth · 2024-07-04 15:00:31

There's neither an S3 nor a non-gnome session in that journal

navknight · 2024-07-04 17:54:54

seth wrote:

There's neither an S3 nor a non-gnome session in that journal

I apologize for that, http://0x0.st/XanX.bin heres another journalctl. Installed i3 and then gave "systemctl suspend" to suspend the laptop. Waited some time and then pressed a key to resume it. After that the screen came on for a few seconds and went black for a frew seconds. I was able to move the mouse when the screen was on but couldn't click anything or register any key strokes in the terminal.

seth · 2024-07-04 20:30:15

Jul 04 23:17:46 navknight-arch kernel: PM: suspend entry (s2idle)
Jul 04 23:17:46 navknight-arch kernel: Filesystems sync: 0.028 seconds
Jul 04 23:18:02 navknight-arch kernel: Freezing user space processes
Jul 04 23:18:02 navknight-arch kernel: Freezing user space processes completed (elapsed 0.001 seconds)
Jul 04 23:18:02 navknight-arch kernel: OOM killer disabled.
Jul 04 23:18:02 navknight-arch kernel: Freezing remaining freezable tasks
Jul 04 23:18:02 navknight-arch kernel: Freezing remaining freezable tasks completed (elapsed 0.001 seconds)
Jul 04 23:18:02 navknight-arch kernel: printk: Suspending console(s) (use no_console_suspend to debug)
Jul 04 23:18:02 navknight-arch kernel: ------------[ cut here ]------------
Jul 04 23:18:02 navknight-arch kernel: i915 0000:00:02.0: i915 raw-wakerefs=1 wakelocks=1 on cleanup
Jul 04 23:18:02 navknight-arch kernel: WARNING: CPU: 0 PID: 549 at drivers/gpu/drm/i915/intel_runtime_pm.c:447 intel_runtime_pm_driver_release+0x61/0x70 [i915]
Jul 04 23:18:02 navknight-arch kernel: Modules linked in: ccm snd_seq_dummy snd_hrtimer rfcomm snd_seq snd_seq_device snd_ctl_led ledtrig_audio snd_soc_skl_hda_dsp snd_soc_hdac_hdmi snd_sof_probes snd_soc_intel_hda_dsp_common xe drm_gpuvm drm_exec gpu_sched snd_hda_codec_realtek drm_suballoc_helper drm_ttm_helper snd_hda_codec_generic snd_hda_scodec_component snd_soc_dmic cmac algif_hash algif_skcipher af_alg bnep vfat fat intel_uncore_frequency intel_uncore_frequency_common snd_sof_pci_intel_tgl snd_sof_intel_hda_common soundwire_intel snd_sof_intel_hda_mlink soundwire_cadence snd_sof_intel_hda snd_sof_pci snd_sof_xtensa_dsp snd_sof snd_sof_utils snd_soc_hdac_hda snd_soc_acpi_intel_match soundwire_generic_allocation snd_soc_acpi x86_pkg_temp_thermal soundwire_bus intel_powerclamp snd_soc_avs snd_soc_hda_codec coretemp snd_hda_ext_core kvm_intel joydev mousedev iwlmvm i915 kvm snd_soc_core crct10dif_pclmul mac80211 snd_compress snd_hda_codec_hdmi crc32_pclmul ac97_bus polyval_clmulni polyval_generic snd_pcm_dmaengine btusb gf128mul btrtl
Jul 04 23:18:02 navknight-arch kernel:  snd_hda_intel ghash_clmulni_intel snd_intel_dspcfg sha512_ssse3 btintel hid_multitouch snd_intel_sdw_acpi btbcm sha1_ssse3 iTCO_wdt libarc4 hid_generic snd_hda_codec aesni_intel btmtk drm_buddy processor_thermal_device_pci intel_pmc_bxt ptp intel_rapl_msr mei_pxp mei_hdcp pps_core ee1004 iTCO_vendor_support snd_hda_core processor_thermal_device i2c_algo_bit crypto_simd snd_hwdep cryptd bluetooth processor_thermal_wt_hint ttm iwlwifi processor_thermal_rfim snd_pcm r8169 rapl processor_thermal_rapl drm_display_helper snd_timer hp_wmi ucsi_acpi intel_rapl_common intel_cstate intel_lpss_pci cfg80211 intel_uncore platform_profile snd processor_thermal_wt_req realtek typec_ucsi spi_nor pcspkr intel_lpss ecdh_generic processor_thermal_power_floor cec wmi_bmof mei_me mdio_devres processor_thermal_mbox libphy mtd crc16 rfkill typec soundcore i2c_i801 idma64 intel_gtt i2c_hid_acpi mei i2c_smbus roles int340x_thermal_zone i2c_hid intel_pmc_core intel_vsec intel_hid pmt_telemetry acpi_pad soc_button_array
Jul 04 23:18:02 navknight-arch kernel:  sparse_keymap pinctrl_tigerlake pmt_class acpi_tad mac_hid pkcs8_key_parser crypto_user dm_mod loop nfnetlink zram ip_tables x_tables rtsx_pci_sdmmc serio_raw mmc_core atkbd libps2 nvme vivaldi_fmap nvme_core sha256_ssse3 xhci_pci spi_intel_pci rtsx_pci spi_intel nvme_auth xhci_pci_renesas i8042 serio nvidia_drm(POE) nvidia_uvm(POE) nvidia_modeset(POE) video wmi nvidia(POE) btrfs blake2b_generic libcrc32c crc32c_generic crc32c_intel xor raid6_pq
Jul 04 23:18:02 navknight-arch kernel: CPU: 0 PID: 549 Comm: kworker/u48:8 Tainted: P        W  OE      6.9.7-arch1-1 #1 44783200744f92500e6484c6d93590bc19db4a83
Jul 04 23:18:02 navknight-arch kernel: Hardware name: HP Victus by HP Gaming Laptop 15-fa0xxx/8A4F, BIOS F.24 10/26/2023
Jul 04 23:18:02 navknight-arch kernel: Workqueue: async async_run_entry_fn
Jul 04 23:18:02 navknight-arch kernel: RIP: 0010:intel_runtime_pm_driver_release+0x61/0x70 [i915]
Jul 04 23:18:02 navknight-arch kernel: Code: fc 10 48 8b 5f 50 48 85 db 75 03 48 8b 1f e8 c6 2b 36 ce 45 89 e0 89 e9 48 89 da 48 89 c6 48 c7 c7 10 b1 cf c5 e8 2f e3 ac cd <0f> 0b 5b 5d 41 5c c3 cc cc cc cc 0f 1f 40 00 90 90 90 90 90 90 90
Jul 04 23:18:02 navknight-arch kernel: RSP: 0018:ffffba2e0604bd88 EFLAGS: 00010282
Jul 04 23:18:02 navknight-arch kernel: RAX: 0000000000000000 RBX: ffff9721422501e0 RCX: 0000000000000027
Jul 04 23:18:02 navknight-arch kernel: RDX: ffff9724af6219c8 RSI: 0000000000000001 RDI: ffff9724af6219c0
Jul 04 23:18:02 navknight-arch kernel: RBP: 0000000000000001 R08: 0000000000000000 R09: ffffba2e0604bb50
Jul 04 23:18:02 navknight-arch kernel: R10: ffffffff954b21a8 R11: 0000000000000003 R12: 0000000000000001
Jul 04 23:18:02 navknight-arch kernel: R13: ffff9721413f0000 R14: ffff97214c222268 R15: 0000000000000000
Jul 04 23:18:02 navknight-arch kernel: FS:  0000000000000000(0000) GS:ffff9724af600000(0000) knlGS:0000000000000000
Jul 04 23:18:02 navknight-arch kernel: CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
Jul 04 23:18:02 navknight-arch kernel: CR2: 00005f61ea9d3018 CR3: 00000002f1c20002 CR4: 0000000000f70ef0
Jul 04 23:18:02 navknight-arch kernel: PKRU: 55555554
Jul 04 23:18:02 navknight-arch kernel: Call Trace:
Jul 04 23:18:02 navknight-arch kernel:  <TASK>
Jul 04 23:18:02 navknight-arch kernel:  ? intel_runtime_pm_driver_release+0x61/0x70 [i915 c784aa4361bedfbc19f8528dc1a10bbbcf2d8fbc]
Jul 04 23:18:02 navknight-arch kernel:  ? __warn.cold+0x8e/0xe8
Jul 04 23:18:02 navknight-arch kernel:  ? intel_runtime_pm_driver_release+0x61/0x70 [i915 c784aa4361bedfbc19f8528dc1a10bbbcf2d8fbc]
Jul 04 23:18:02 navknight-arch kernel:  ? report_bug+0xff/0x140
Jul 04 23:18:02 navknight-arch kernel:  ? console_unlock+0xd7/0x130
Jul 04 23:18:02 navknight-arch kernel:  ? handle_bug+0x3c/0x80
Jul 04 23:18:02 navknight-arch kernel:  ? exc_invalid_op+0x17/0x70
Jul 04 23:18:02 navknight-arch kernel:  ? asm_exc_invalid_op+0x1a/0x20
Jul 04 23:18:02 navknight-arch kernel:  ? intel_runtime_pm_driver_release+0x61/0x70 [i915 c784aa4361bedfbc19f8528dc1a10bbbcf2d8fbc]
Jul 04 23:18:02 navknight-arch kernel:  ? intel_runtime_pm_driver_release+0x61/0x70 [i915 c784aa4361bedfbc19f8528dc1a10bbbcf2d8fbc]
Jul 04 23:18:02 navknight-arch kernel:  i915_drm_suspend_late+0x101/0x110 [i915 c784aa4361bedfbc19f8528dc1a10bbbcf2d8fbc]
Jul 04 23:18:02 navknight-arch kernel:  ? __pfx_pci_pm_suspend_late+0x10/0x10
Jul 04 23:18:02 navknight-arch kernel:  dpm_run_callback+0x47/0x150
Jul 04 23:18:02 navknight-arch kernel:  device_suspend_late+0xc1/0x260
Jul 04 23:18:02 navknight-arch kernel:  async_suspend_late+0x1d/0x30
Jul 04 23:18:02 navknight-arch kernel:  async_run_entry_fn+0x31/0x140
Jul 04 23:18:02 navknight-arch kernel:  process_one_work+0x18b/0x350
Jul 04 23:18:02 navknight-arch kernel:  worker_thread+0x2eb/0x410
Jul 04 23:18:02 navknight-arch kernel:  ? __pfx_worker_thread+0x10/0x10
Jul 04 23:18:02 navknight-arch kernel:  kthread+0xcf/0x100
Jul 04 23:18:02 navknight-arch kernel:  ? __pfx_kthread+0x10/0x10
Jul 04 23:18:02 navknight-arch kernel:  ret_from_fork+0x31/0x50
Jul 04 23:18:02 navknight-arch kernel:  ? __pfx_kthread+0x10/0x10
Jul 04 23:18:02 navknight-arch kernel:  ret_from_fork_asm+0x1a/0x30
Jul 04 23:18:02 navknight-arch kernel:  </TASK>
Jul 04 23:18:02 navknight-arch kernel: ---[ end trace 0000000000000000 ]---
…
Jul 04 23:18:02 navknight-arch kernel: i915 0000:00:02.0: [drm] *ERROR* Failed to write source OUI
Jul 04 23:18:02 navknight-arch kernel: i915 0000:00:02.0: [drm] *ERROR* [CONNECTOR:236:eDP-1][ENCODER:235:DDI A/PHY A][DPRX] Failed to enable link training
…
Jul 04 23:18:23 navknight-arch kernel: i915 0000:00:02.0: [drm] *ERROR* Failed to write source OUI
Jul 04 23:18:29 navknight-arch kernel: i915 0000:00:02.0: [drm] *ERROR* [CONNECTOR:236:eDP-1][ENCODER:235:DDI A/PHY A][DPRX] Failed to enable link training
Jul 04 23:18:32 navknight-arch kernel: i915 0000:00:02.0: [drm] *ERROR* Failed to read DPCD register 0x92
Jul 04 23:18:36 navknight-arch kernel: i915 0000:00:02.0: [drm] *ERROR* Failed to read DPCD register 0x92
Jul 04 23:18:40 navknight-arch kernel: i915 0000:00:02.0: [drm] *ERROR* Failed to read DPCD register 0x92
Jul 04 23:18:44 navknight-arch kernel: i915 0000:00:02.0: [drm] *ERROR* Failed to read DPCD register 0x92
Jul 04 23:18:50 navknight-arch kernel: i915 0000:00:02.0: [drm] *ERROR* Failed to write source OUI
…
Jul 04 23:19:30 navknight-arch /usr/lib/gdm-x-session[1343]: (WW) modeset(0): hotplug event: connector 236's link-state is BAD, tried resetting the current mode. You may be leftwith a black screen if this fails...

https://gitlab.freedesktop.org/drm/i915 … ssues/8477
You're not getting those errors when suspending a gnome session?

"i915.enable_dpcd_backlight=0 intel_idle.max_cstate=1 i915.enable_dc=0 ahci.mobile_lpm_policy=1", https://wiki.archlinux.org/title/Kernel_parameters
Does the problem remain when setting those?
(This isn't a good fix as it will render suspending s2idle almost pointless, we just need to figure where this is coming from and try to get a functional baseline for this)

navknight · 2024-07-04 21:38:19

seth wrote:

Jul 04 23:17:46 navknight-arch kernel: PM: suspend entry (s2idle)
Jul 04 23:17:46 navknight-arch kernel: Filesystems sync: 0.028 seconds
Jul 04 23:18:02 navknight-arch kernel: Freezing user space processes
Jul 04 23:18:02 navknight-arch kernel: Freezing user space processes completed (elapsed 0.001 seconds)
Jul 04 23:18:02 navknight-arch kernel: OOM killer disabled.
Jul 04 23:18:02 navknight-arch kernel: Freezing remaining freezable tasks
Jul 04 23:18:02 navknight-arch kernel: Freezing remaining freezable tasks completed (elapsed 0.001 seconds)
Jul 04 23:18:02 navknight-arch kernel: printk: Suspending console(s) (use no_console_suspend to debug)
Jul 04 23:18:02 navknight-arch kernel: ------------[ cut here ]------------
Jul 04 23:18:02 navknight-arch kernel: i915 0000:00:02.0: i915 raw-wakerefs=1 wakelocks=1 on cleanup
Jul 04 23:18:02 navknight-arch kernel: WARNING: CPU: 0 PID: 549 at drivers/gpu/drm/i915/intel_runtime_pm.c:447 intel_runtime_pm_driver_release+0x61/0x70 [i915]
Jul 04 23:18:02 navknight-arch kernel: Modules linked in: ccm snd_seq_dummy snd_hrtimer rfcomm snd_seq snd_seq_device snd_ctl_led ledtrig_audio snd_soc_skl_hda_dsp snd_soc_hdac_hdmi snd_sof_probes snd_soc_intel_hda_dsp_common xe drm_gpuvm drm_exec gpu_sched snd_hda_codec_realtek drm_suballoc_helper drm_ttm_helper snd_hda_codec_generic snd_hda_scodec_component snd_soc_dmic cmac algif_hash algif_skcipher af_alg bnep vfat fat intel_uncore_frequency intel_uncore_frequency_common snd_sof_pci_intel_tgl snd_sof_intel_hda_common soundwire_intel snd_sof_intel_hda_mlink soundwire_cadence snd_sof_intel_hda snd_sof_pci snd_sof_xtensa_dsp snd_sof snd_sof_utils snd_soc_hdac_hda snd_soc_acpi_intel_match soundwire_generic_allocation snd_soc_acpi x86_pkg_temp_thermal soundwire_bus intel_powerclamp snd_soc_avs snd_soc_hda_codec coretemp snd_hda_ext_core kvm_intel joydev mousedev iwlmvm i915 kvm snd_soc_core crct10dif_pclmul mac80211 snd_compress snd_hda_codec_hdmi crc32_pclmul ac97_bus polyval_clmulni polyval_generic snd_pcm_dmaengine btusb gf128mul btrtl
Jul 04 23:18:02 navknight-arch kernel:  snd_hda_intel ghash_clmulni_intel snd_intel_dspcfg sha512_ssse3 btintel hid_multitouch snd_intel_sdw_acpi btbcm sha1_ssse3 iTCO_wdt libarc4 hid_generic snd_hda_codec aesni_intel btmtk drm_buddy processor_thermal_device_pci intel_pmc_bxt ptp intel_rapl_msr mei_pxp mei_hdcp pps_core ee1004 iTCO_vendor_support snd_hda_core processor_thermal_device i2c_algo_bit crypto_simd snd_hwdep cryptd bluetooth processor_thermal_wt_hint ttm iwlwifi processor_thermal_rfim snd_pcm r8169 rapl processor_thermal_rapl drm_display_helper snd_timer hp_wmi ucsi_acpi intel_rapl_common intel_cstate intel_lpss_pci cfg80211 intel_uncore platform_profile snd processor_thermal_wt_req realtek typec_ucsi spi_nor pcspkr intel_lpss ecdh_generic processor_thermal_power_floor cec wmi_bmof mei_me mdio_devres processor_thermal_mbox libphy mtd crc16 rfkill typec soundcore i2c_i801 idma64 intel_gtt i2c_hid_acpi mei i2c_smbus roles int340x_thermal_zone i2c_hid intel_pmc_core intel_vsec intel_hid pmt_telemetry acpi_pad soc_button_array
Jul 04 23:18:02 navknight-arch kernel:  sparse_keymap pinctrl_tigerlake pmt_class acpi_tad mac_hid pkcs8_key_parser crypto_user dm_mod loop nfnetlink zram ip_tables x_tables rtsx_pci_sdmmc serio_raw mmc_core atkbd libps2 nvme vivaldi_fmap nvme_core sha256_ssse3 xhci_pci spi_intel_pci rtsx_pci spi_intel nvme_auth xhci_pci_renesas i8042 serio nvidia_drm(POE) nvidia_uvm(POE) nvidia_modeset(POE) video wmi nvidia(POE) btrfs blake2b_generic libcrc32c crc32c_generic crc32c_intel xor raid6_pq
Jul 04 23:18:02 navknight-arch kernel: CPU: 0 PID: 549 Comm: kworker/u48:8 Tainted: P        W  OE      6.9.7-arch1-1 #1 44783200744f92500e6484c6d93590bc19db4a83
Jul 04 23:18:02 navknight-arch kernel: Hardware name: HP Victus by HP Gaming Laptop 15-fa0xxx/8A4F, BIOS F.24 10/26/2023
Jul 04 23:18:02 navknight-arch kernel: Workqueue: async async_run_entry_fn
Jul 04 23:18:02 navknight-arch kernel: RIP: 0010:intel_runtime_pm_driver_release+0x61/0x70 [i915]
Jul 04 23:18:02 navknight-arch kernel: Code: fc 10 48 8b 5f 50 48 85 db 75 03 48 8b 1f e8 c6 2b 36 ce 45 89 e0 89 e9 48 89 da 48 89 c6 48 c7 c7 10 b1 cf c5 e8 2f e3 ac cd <0f> 0b 5b 5d 41 5c c3 cc cc cc cc 0f 1f 40 00 90 90 90 90 90 90 90
Jul 04 23:18:02 navknight-arch kernel: RSP: 0018:ffffba2e0604bd88 EFLAGS: 00010282
Jul 04 23:18:02 navknight-arch kernel: RAX: 0000000000000000 RBX: ffff9721422501e0 RCX: 0000000000000027
Jul 04 23:18:02 navknight-arch kernel: RDX: ffff9724af6219c8 RSI: 0000000000000001 RDI: ffff9724af6219c0
Jul 04 23:18:02 navknight-arch kernel: RBP: 0000000000000001 R08: 0000000000000000 R09: ffffba2e0604bb50
Jul 04 23:18:02 navknight-arch kernel: R10: ffffffff954b21a8 R11: 0000000000000003 R12: 0000000000000001
Jul 04 23:18:02 navknight-arch kernel: R13: ffff9721413f0000 R14: ffff97214c222268 R15: 0000000000000000
Jul 04 23:18:02 navknight-arch kernel: FS:  0000000000000000(0000) GS:ffff9724af600000(0000) knlGS:0000000000000000
Jul 04 23:18:02 navknight-arch kernel: CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
Jul 04 23:18:02 navknight-arch kernel: CR2: 00005f61ea9d3018 CR3: 00000002f1c20002 CR4: 0000000000f70ef0
Jul 04 23:18:02 navknight-arch kernel: PKRU: 55555554
Jul 04 23:18:02 navknight-arch kernel: Call Trace:
Jul 04 23:18:02 navknight-arch kernel:  <TASK>
Jul 04 23:18:02 navknight-arch kernel:  ? intel_runtime_pm_driver_release+0x61/0x70 [i915 c784aa4361bedfbc19f8528dc1a10bbbcf2d8fbc]
Jul 04 23:18:02 navknight-arch kernel:  ? __warn.cold+0x8e/0xe8
Jul 04 23:18:02 navknight-arch kernel:  ? intel_runtime_pm_driver_release+0x61/0x70 [i915 c784aa4361bedfbc19f8528dc1a10bbbcf2d8fbc]
Jul 04 23:18:02 navknight-arch kernel:  ? report_bug+0xff/0x140
Jul 04 23:18:02 navknight-arch kernel:  ? console_unlock+0xd7/0x130
Jul 04 23:18:02 navknight-arch kernel:  ? handle_bug+0x3c/0x80
Jul 04 23:18:02 navknight-arch kernel:  ? exc_invalid_op+0x17/0x70
Jul 04 23:18:02 navknight-arch kernel:  ? asm_exc_invalid_op+0x1a/0x20
Jul 04 23:18:02 navknight-arch kernel:  ? intel_runtime_pm_driver_release+0x61/0x70 [i915 c784aa4361bedfbc19f8528dc1a10bbbcf2d8fbc]
Jul 04 23:18:02 navknight-arch kernel:  ? intel_runtime_pm_driver_release+0x61/0x70 [i915 c784aa4361bedfbc19f8528dc1a10bbbcf2d8fbc]
Jul 04 23:18:02 navknight-arch kernel:  i915_drm_suspend_late+0x101/0x110 [i915 c784aa4361bedfbc19f8528dc1a10bbbcf2d8fbc]
Jul 04 23:18:02 navknight-arch kernel:  ? __pfx_pci_pm_suspend_late+0x10/0x10
Jul 04 23:18:02 navknight-arch kernel:  dpm_run_callback+0x47/0x150
Jul 04 23:18:02 navknight-arch kernel:  device_suspend_late+0xc1/0x260
Jul 04 23:18:02 navknight-arch kernel:  async_suspend_late+0x1d/0x30
Jul 04 23:18:02 navknight-arch kernel:  async_run_entry_fn+0x31/0x140
Jul 04 23:18:02 navknight-arch kernel:  process_one_work+0x18b/0x350
Jul 04 23:18:02 navknight-arch kernel:  worker_thread+0x2eb/0x410
Jul 04 23:18:02 navknight-arch kernel:  ? __pfx_worker_thread+0x10/0x10
Jul 04 23:18:02 navknight-arch kernel:  kthread+0xcf/0x100
Jul 04 23:18:02 navknight-arch kernel:  ? __pfx_kthread+0x10/0x10
Jul 04 23:18:02 navknight-arch kernel:  ret_from_fork+0x31/0x50
Jul 04 23:18:02 navknight-arch kernel:  ? __pfx_kthread+0x10/0x10
Jul 04 23:18:02 navknight-arch kernel:  ret_from_fork_asm+0x1a/0x30
Jul 04 23:18:02 navknight-arch kernel:  </TASK>
Jul 04 23:18:02 navknight-arch kernel: ---[ end trace 0000000000000000 ]---
…
Jul 04 23:18:02 navknight-arch kernel: i915 0000:00:02.0: [drm] *ERROR* Failed to write source OUI
Jul 04 23:18:02 navknight-arch kernel: i915 0000:00:02.0: [drm] *ERROR* [CONNECTOR:236:eDP-1][ENCODER:235:DDI A/PHY A][DPRX] Failed to enable link training
…
Jul 04 23:18:23 navknight-arch kernel: i915 0000:00:02.0: [drm] *ERROR* Failed to write source OUI
Jul 04 23:18:29 navknight-arch kernel: i915 0000:00:02.0: [drm] *ERROR* [CONNECTOR:236:eDP-1][ENCODER:235:DDI A/PHY A][DPRX] Failed to enable link training
Jul 04 23:18:32 navknight-arch kernel: i915 0000:00:02.0: [drm] *ERROR* Failed to read DPCD register 0x92
Jul 04 23:18:36 navknight-arch kernel: i915 0000:00:02.0: [drm] *ERROR* Failed to read DPCD register 0x92
Jul 04 23:18:40 navknight-arch kernel: i915 0000:00:02.0: [drm] *ERROR* Failed to read DPCD register 0x92
Jul 04 23:18:44 navknight-arch kernel: i915 0000:00:02.0: [drm] *ERROR* Failed to read DPCD register 0x92
Jul 04 23:18:50 navknight-arch kernel: i915 0000:00:02.0: [drm] *ERROR* Failed to write source OUI
…
Jul 04 23:19:30 navknight-arch /usr/lib/gdm-x-session[1343]: (WW) modeset(0): hotplug event: connector 236's link-state is BAD, tried resetting the current mode. You may be leftwith a black screen if this fails...

https://gitlab.freedesktop.org/drm/i915 … ssues/8477
You're not getting those errors when suspending a gnome session?

"i915.enable_dpcd_backlight=0 intel_idle.max_cstate=1 i915.enable_dc=0 ahci.mobile_lpm_policy=1", https://wiki.archlinux.org/title/Kernel_parameters
Does the problem remain when setting those?
(This isn't a good fix as it will render suspending s2idle almost pointless, we just need to figure where this is coming from and try to get a functional baseline for this)

This is the journalctl for the gnome session, I think it has the same "Failed to read DPCD register 0x92" errors as above but not the "hotplug event: ..." warning.
http://0x0.st/XaR1.bin

This is the journalctl after setting the kernel params you mentioned and suspending it. Surprisingly, it worked. The resume was succesful and I was able to write the uneditted version of this post on the i3 session. It resumed faster than it does on gnome!
http://0x0.st/XaRp.bin

Last edited by navknight (2024-07-04 21:41:16)

seth · 2024-07-04 21:45:22

The second journal still has the intel_runtime_pm_driver_release warnings, but the DPCD errors are gone (since you disabled dpcd)
See whether you get away w/ only "i915.enable_dpcd_backlight=0"
The "worst" parameter in the previous list is "intel_idle.max_cstate=1", you don't want to use that at all.

navknight · 2024-07-04 21:53:32

seth wrote:

The second journal still has the intel_runtime_pm_driver_release warnings, but the DPCD errors are gone (since you disabled dpcd)
See whether you get away w/ only "i915.enable_dpcd_backlight=0"
The "worst" parameter in the previous list is "intel_idle.max_cstate=1", you don't want to use that at all.

No unfortunately, with only the "i915.enable_dpcd_backlight=0" kernel param, we are back to square one.
Heres the journalctl = http://0x0.st/XaRv.bin

Didn't work with i915.enable_dc=0 set http://0x0.st/XaRY.bin

Didnt work with ahci.mobile_lpm_policy=1 set http://0x0.st/XaR6.bin as well

Last edited by navknight (2024-07-04 22:00:58)

seth · 2024-07-05 06:50:57

Basically, does it work if you set all but "intel_idle.max_cstate=1" ?
If not, what if you're not using GDM as your DM resp. use https://wiki.archlinux.org/title/GDM#Use_Xorg_backend (and what is the impact of those changes on gnome as well)?

Are there BIOS updates available for your system?
Does the behavior differ w/ the LTS kernel?

navknight · 2024-07-05 08:13:10

seth wrote:

Basically, does it work if you set all but "intel_idle.max_cstate=1" ?
If not, what if you're not using GDM as your DM resp. use https://wiki.archlinux.org/title/GDM#Use_Xorg_backend (and what is the impact of those changes on gnome as well)?
Are there BIOS updates available for your system?
Does the behavior differ w/ the LTS kernel?

No it doesnt work if I set all but "intel_idle.max_cstate=1"

LightDM failed to launch (http://0x0.st/XBz8.bin) , SDDM + Gnome was able to work even with wayland enabled http://0x0.st/XBzc.bin (without screen locking because GDM is required for that in gnome)

Installed LTS kernel, worked fine with Gnome but failed similary on i3 http://0x0.st/XBzg.txt

Last edited by navknight (2024-07-05 08:37:03)

seth · 2024-07-05 15:05:17

Please post your lightdm log (somewhere in /var/log)

navknight · 2024-07-05 15:32:25

seth wrote:

Please post your lightdm log (somewhere in /var/log)

Logs from lightdm.log in /var/log

[+0.00s] DEBUG: Logging to /var/log/lightdm/lightdm.log
[+0.00s] DEBUG: Starting Light Display Manager 1.32.0, UID=0 PID=714
[+0.00s] DEBUG: Loading configuration dirs from /usr/share/lightdm/lightdm.conf.d
[+0.00s] DEBUG: Loading configuration dirs from /usr/local/share/lightdm/lightdm.conf.d
[+0.00s] DEBUG: Loading configuration dirs from /var/lib/flatpak/exports/share/lightdm/lightdm.conf.d
[+0.00s] DEBUG: Loading configuration dirs from /etc/xdg/lightdm/lightdm.conf.d
[+0.00s] DEBUG: Loading configuration from /etc/lightdm/lightdm.conf
[+0.00s] DEBUG: Registered seat module local
[+0.00s] DEBUG: Registered seat module xremote
[+0.00s] DEBUG: Using D-Bus name org.freedesktop.DisplayManager
[+0.00s] DEBUG: Using cross-namespace EXTERNAL authentication (this will deadlock if server is GDBus < 2.73.3)
[+0.00s] DEBUG: _g_io_module_get_default: Found default implementation local (GLocalVfs) for ‘gio-vfs’
[+0.01s] DEBUG: Monitoring logind for seats
[+0.01s] DEBUG: New seat added from logind: seat0
[+0.01s] DEBUG: Seat seat0: Loading properties from config section Seat:*
[+0.01s] DEBUG: Seat seat0 has property CanMultiSession=no
[+0.01s] DEBUG: Seat seat0: Starting
[+0.01s] DEBUG: Seat seat0: Creating greeter session
[+0.01s] DEBUG: Seat seat0: Failed to find session configuration lightdm-gtk-greeter
[+0.01s] DEBUG: Seat seat0: Failed to create greeter session
[+0.01s] DEBUG: Failed to start seat: seat0

Last edited by navknight (2024-07-05 15:32:55)

seth · 2024-07-05 15:53:17

Looks like you simply didn't install any greeter?
https://archlinux.org/packages/extra/x8 … k-greeter/

(Unfortunately that's a simple explanation that will likely not get us ahead w/ the overall issue if it remains w/ lightdm+i3)

navknight · 2024-07-05 18:56:42

seth wrote:

Looks like you simply didn't install any greeter?
https://archlinux.org/packages/extra/x8 … k-greeter/
(Unfortunately that's a simple explanation that will likely not get us ahead w/ the overall issue if it remains w/ lightdm+i3)

LightDM worked, but resume with i3 is in the same condition. I have no clue what the issue is.

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

navknight · 2024-07-08 18:03:57

seth wrote:

Looks like you simply didn't install any greeter?
https://archlinux.org/packages/extra/x8 … k-greeter/
(Unfortunately that's a simple explanation that will likely not get us ahead w/ the overall issue if it remains w/ lightdm+i3)

Something new happened, till now I had never used Gnome on Xorg. Today I did and surprisingly resume is broken on gnome+xorg
So the only thing that works on my machine is Gnome+GDM+Wayland and nothing else so far.
http://0x0.st/XBda.bin

seth · 2024-07-08 21:27:30

The the wakeup principally works, can you
1. simply switch to another VT and get visual output?
2. ssh into the system?
=> 3. try to adjust the backlight from there?
(ideally using https://wiki.archlinux.org/title/Backlight#ACPI )

navknight · 2024-07-12 04:08:40

seth wrote:

The the wakeup principally works, can you
1. simply switch to another VT and get visual output?
2. ssh into the system?
=> 3. try to adjust the backlight from there?
(ideally using https://wiki.archlinux.org/title/Backlight#ACPI )

I ssh'ed into the system after suspending and resuming it on gnome+xorg. The screen was still black but I was able to run

systemctl restart gdm

which recovered gdm and I was able to use gdm normally and logged in. But after logging in again the same thing happened, the screen was black like it usually is after a resume. I did try to restart gnome as well

systemctl restart gnome

but it did not have any effect.

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

seth · 2024-07-12 13:02:50

systemctl restart gnome

That's not how this works, but your previous gnome session terminated w/ the GDM restart.

Status quo as before: i915 DPCD problems after the wakeup, foreshadowed by the warning during the boot

Jul 12 08:47:09 navknight-arch kernel: i915 0000:00:02.0: drm_WARN_ON(intel_dp->pps.vdd_wakeref)

It's frankly more surprising that gnome/wayland somehow™ works than that everything else doesn't (the situation/error shows up quite some on google, but seems to likewise affect gnome+wayland there)

Can you disable either the nvidia GPU or the intel IGP in your UEFI/BIOS settings?

navknight · 2024-07-12 16:23:57

seth wrote:

systemctl restart gnome
That's not how this works, but your previous gnome session terminated w/ the GDM restart.

Status quo as before: i915 DPCD problems after the wakeup, foreshadowed by the warning during the boot
Jul 12 08:47:09 navknight-arch kernel: i915 0000:00:02.0: drm_WARN_ON(intel_dp->pps.vdd_wakeref)
It's frankly more surprising that gnome/wayland somehow™ works than that everything else doesn't (the situation/error shows up quite some on google, but seems to likewise affect gnome+wayland there)
Can you disable either the nvidia GPU or the intel IGP in your UEFI/BIOS settings?

I can't unfortunately, I can do that only through software. But setting envycontrol to integrated or nvidia seem to have no effect at all.
HP has the worst UEFI/BIOS

Arch Linux

#1 2024-07-03 03:07:55

NOTHING except Gnome works with nvidia on my machine

#2 2024-07-03 07:02:50

Re: NOTHING except Gnome works with nvidia on my machine

#3 2024-07-03 16:27:57

Re: NOTHING except Gnome works with nvidia on my machine

#4 2024-07-03 21:45:52

Re: NOTHING except Gnome works with nvidia on my machine

#5 2024-07-04 03:42:40

Re: NOTHING except Gnome works with nvidia on my machine

#6 2024-07-04 06:54:36

Re: NOTHING except Gnome works with nvidia on my machine

#7 2024-07-04 14:19:36

Re: NOTHING except Gnome works with nvidia on my machine

#8 2024-07-04 15:00:31

Re: NOTHING except Gnome works with nvidia on my machine

#9 2024-07-04 17:54:54

Re: NOTHING except Gnome works with nvidia on my machine

#10 2024-07-04 20:30:15

Re: NOTHING except Gnome works with nvidia on my machine

#11 2024-07-04 21:38:19

Re: NOTHING except Gnome works with nvidia on my machine

#12 2024-07-04 21:45:22

Re: NOTHING except Gnome works with nvidia on my machine

#13 2024-07-04 21:53:32

Re: NOTHING except Gnome works with nvidia on my machine

#14 2024-07-05 06:50:57

Re: NOTHING except Gnome works with nvidia on my machine

#15 2024-07-05 08:13:10

Re: NOTHING except Gnome works with nvidia on my machine

#16 2024-07-05 15:05:17

Re: NOTHING except Gnome works with nvidia on my machine

#17 2024-07-05 15:32:25

Re: NOTHING except Gnome works with nvidia on my machine

#18 2024-07-05 15:53:17

Re: NOTHING except Gnome works with nvidia on my machine

#19 2024-07-05 18:56:42

Re: NOTHING except Gnome works with nvidia on my machine

#20 2024-07-08 18:03:57

Re: NOTHING except Gnome works with nvidia on my machine

#21 2024-07-08 21:27:30

Re: NOTHING except Gnome works with nvidia on my machine

#22 2024-07-12 04:08:40

Re: NOTHING except Gnome works with nvidia on my machine

#23 2024-07-12 13:02:50

Re: NOTHING except Gnome works with nvidia on my machine

#24 2024-07-12 16:23:57

Re: NOTHING except Gnome works with nvidia on my machine

Board footer