F38 suspend mode/freeze issue

kubatron · July 31, 2023, 6:31am

Hi,

I have a problem with Fedora 38 KDE with suspend mode and freeze laptop.
I install all updates and NVidia drivers, when install F38 I choose a automatic installation (disk).

I have another laptop with F38 and there is no problem with suspend or freeze mode.

00:00.0 Host bridge: Intel Corporation Device a702 (rev 01)
00:01.0 PCI bridge: Intel Corporation Device a70d (rev 01)
00:02.0 VGA compatible controller: Intel Corporation Raptor Lake-S UHD Graphics (rev 04)
00:04.0 Signal processing controller: Intel Corporation Device a71d (rev 01)
00:08.0 System peripheral: Intel Corporation GNA Scoring Accelerator module (rev 01)
00:0a.0 Signal processing controller: Intel Corporation Device a77d (rev 01)
00:14.0 USB controller: Intel Corporation Device 7a60 (rev 11)
00:14.2 RAM memory: Intel Corporation Device 7a27 (rev 11)
00:14.3 Network controller: Intel Corporation Device 7a70 (rev 11)
00:15.0 Serial bus controller: Intel Corporation Device 7a4c (rev 11)
00:15.1 Serial bus controller: Intel Corporation Device 7a4d (rev 11)
00:15.2 Serial bus controller: Intel Corporation Device 7a4e (rev 11)
00:16.0 Communication controller: Intel Corporation Device 7a68 (rev 11)
00:1a.0 PCI bridge: Intel Corporation Device 7a48 (rev 11)
00:1b.0 PCI bridge: Intel Corporation Device 7a44 (rev 11)
00:1c.0 PCI bridge: Intel Corporation Device 7a3a (rev 11)
00:1c.4 PCI bridge: Intel Corporation Device 7a3c (rev 11)
00:1d.0 PCI bridge: Intel Corporation Device 7a34 (rev 11)
00:1f.0 ISA bridge: Intel Corporation Device 7a0c (rev 11)
00:1f.3 Audio device: Intel Corporation Device 7a50 (rev 11)
00:1f.4 SMBus: Intel Corporation Device 7a23 (rev 11)
00:1f.5 Serial bus controller: Intel Corporation Device 7a24 (rev 11)
01:00.0 VGA compatible controller: NVIDIA Corporation AD107M [GeForce RTX 4060 Max-Q / Mobile] (rev a1)
01:00.1 Audio device: NVIDIA Corporation Device 22be (rev a1)
02:00.0 PCI bridge: Intel Corporation Device 1133 (rev 02)
03:00.0 PCI bridge: Intel Corporation Device 1133 (rev 02)
03:01.0 PCI bridge: Intel Corporation Device 1133 (rev 02)
03:02.0 PCI bridge: Intel Corporation Device 1133 (rev 02)
03:03.0 PCI bridge: Intel Corporation Device 1133 (rev 02)
04:00.0 USB controller: Intel Corporation Device 1134
38:00.0 USB controller: Intel Corporation Device 1135
6c:00.0 Non-Volatile memory controller: Micron/Crucial Technology P2 NVMe PCIe SSD (rev 01)
6d:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8125 2.5GbE Controller (rev 05)
6e:00.0 SD Host controller: O2 Micro, Inc. SD/MMC Card Reader Controller (rev 01)
6f:00.0 Non-Volatile memory controller: Samsung Electronics Co Ltd NVMe SSD Controller PM9A1/PM9A3/980PRO```

32 × 13th Gen Intel® Core™ i9-13900HX

gnwiii · July 31, 2023, 2:23pm

Power management is a complicated dance that involves the linux kernel and hardware device firmware. Unless both your systems have identical hardware and drivers, you need to make sure the problem system has current firmware. KVM switches and docking stations may also need updates (which may be slow to arrive). If your problem system is from a vendor that participates in the Linux Vendor Firmware project you should be able to get updates using fwupdmgr. Updates from other may require Windows.

Don’t forget to check for SSD firmware updates on the vendor site.

Make sure Fedora is fully updated so others will be using the same software. Once everything is updated, you may need a vendor-dependent magic incantation to ensure that the new firmware is being used. Modern systems never fully power down (MS Windows has “wake-on-wan” used by large enterprises to push updates across the enterprise), so network devices may not reload. You can try disabling network devices in “BIOS”, booting, shutting down and then booting and enabling the devices.

After all that, it the problem persists, please post the output from inxi -Fzzxx. You may want to compare with the non-problem system to focus on devices that differ.

kubatron · August 10, 2023, 8:37am

Ok, I was trying many things.
I read many topics.

First, I try to check if some of device like external monitor, mouse, keyboard is problem. But no.

Then I check battery setting from eco to perfomance, nothing work.

Then I check other thing, I measure what time is freeze suspend mode when I use:

terminal: systemctl suspend or su (to root) systemctl suspend
use a Fn + Suspend keybaord button
Try to use a suspend with closing a laptop
with or without external monitor
with or without mouse/keyboard external

And so for, the time is between 2-3 minutes, sometimes this was a 10minutes.

And when I try that things, I use then:

journalctl -b --grep=suspend

And I got a interesting information when I check what is happend when I use suspend and my laptop is freeze and back to live:

sie 10 10:08:24 kubatron kernel: nvme 0000:6c:00.0: platform quirk: setting simple suspend
sie 10 10:08:24 kubatron kernel: nvme 0000:6f:00.0: platform quirk: setting simple suspend
sie 10 10:09:03 kubatron kded5[3231]: kscreen.kded: PowerDevil SuspendSession action not available!
sie 10 10:09:23 kubatron systemd-logind[1871]: Suspend key pressed short.
sie 10 10:09:23 kubatron systemd-logind[1871]: The system will suspend now!
sie 10 10:09:23 kubatron ModemManager[2045]: <info>  [sleep-monitor-systemd] system is about to suspend
sie 10 10:09:24 kubatron systemd[1]: Starting nvidia-suspend.service - NVIDIA system suspend actions...
sie 10 10:09:24 kubatron suspend[5587]: nvidia-suspend.service
sie 10 10:09:24 kubatron logger[5587]: <13>Aug 10 10:09:24 suspend: nvidia-suspend.service
sie 10 10:09:25 kubatron systemd[1]: nvidia-suspend.service: Deactivated successfully.
sie 10 10:09:25 kubatron systemd[1]: Finished nvidia-suspend.service - NVIDIA system suspend actions.
sie 10 10:09:25 kubatron audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 subj=system_u:system_r:init_t:s0 msg='unit=nvidia-suspend comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
sie 10 10:09:25 kubatron audit[1]: SERVICE_STOP pid=1 uid=0 auid=4294967295 ses=4294967295 subj=system_u:system_r:init_t:s0 msg='unit=nvidia-suspend comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
sie 10 10:09:25 kubatron systemd[1]: Starting systemd-suspend.service - System Suspend...
sie 10 10:09:25 kubatron systemd-sleep[5831]: Entering sleep state 'suspend'...
sie 10 10:09:25 kubatron kernel: PM: suspend entry (deep)
sie 10 10:11:52 kubatron kernel: printk: Suspending console(s) (use no_console_suspend to debug)
sie 10 10:11:52 kubatron kernel: PM: suspend devices took 1.020 seconds
sie 10 10:11:59 kubatron kernel: PM: suspend devices took 0.930 seconds
sie 10 10:11:59 kubatron kernel: PM: suspend exit
sie 10 10:12:00 kubatron systemd[1]: systemd-suspend.service: Deactivated successfully.
sie 10 10:12:00 kubatron systemd[1]: Finished systemd-suspend.service - System Suspend.
sie 10 10:12:00 kubatron audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 subj=system_u:system_r:init_t:s0 msg='unit=systemd-suspend comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
sie 10 10:12:00 kubatron audit[1]: SERVICE_STOP pid=1 uid=0 auid=4294967295 ses=4294967295 subj=system_u:system_r:init_t:s0 msg='unit=systemd-suspend comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
sie 10 10:12:00 kubatron systemd[1]: systemd-suspend.service: Consumed 1.085s CPU time.
sie 10 10:12:00 kubatron systemd[1]: Reached target suspend.target - Suspend.
sie 10 10:12:00 kubatron logger[6020]: <13>Aug 10 10:12:00 suspend: nvidia-resume.service
sie 10 10:12:00 kubatron systemd[1]: Stopped target suspend.target - Suspend.
sie 10 10:14:46 kubatron systemd-logind[1871]: The system will suspend now!
sie 10 10:14:46 kubatron ModemManager[2045]: <info>  [sleep-monitor-systemd] system is about to suspend
sie 10 10:14:47 kubatron systemd[1]: Starting nvidia-suspend.service - NVIDIA system suspend actions...
sie 10 10:14:47 kubatron suspend[6568]: nvidia-suspend.service
sie 10 10:14:47 kubatron logger[6568]: <13>Aug 10 10:14:47 suspend: nvidia-suspend.service
sie 10 10:14:48 kubatron systemd[1]: nvidia-suspend.service: Deactivated successfully.
sie 10 10:14:48 kubatron systemd[1]: Finished nvidia-suspend.service - NVIDIA system suspend actions.
sie 10 10:14:48 kubatron audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 subj=system_u:system_r:init_t:s0 msg='unit=nvidia-suspend comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
sie 10 10:14:48 kubatron audit[1]: SERVICE_STOP pid=1 uid=0 auid=4294967295 ses=4294967295 subj=system_u:system_r:init_t:s0 msg='unit=nvidia-suspend comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
sie 10 10:14:48 kubatron systemd[1]: Starting systemd-suspend.service - System Suspend...
sie 10 10:14:48 kubatron systemd-sleep[6835]: Entering sleep state 'suspend'...
sie 10 10:14:48 kubatron kernel: PM: suspend entry (deep)
sie 10 10:16:06 kubatron kernel: printk: Suspending console(s) (use no_console_suspend to debug)
sie 10 10:16:06 kubatron kernel: PM: suspend devices took 1.046 seconds
sie 10 10:16:11 kubatron kernel: PM: suspend exit
sie 10 10:16:11 kubatron kernel: PM: suspend entry (s2idle)
sie 10 10:16:11 kubatron kernel: printk: Suspending console(s) (use no_console_suspend to debug)
sie 10 10:16:11 kubatron kernel: PM: suspend devices took 0.934 seconds
sie 10 10:16:11 kubatron kernel: PM: suspend exit
sie 10 10:16:11 kubatron systemd[1]: systemd-suspend.service: Deactivated successfully.
sie 10 10:16:11 kubatron systemd[1]: Finished systemd-suspend.service - System Suspend.
sie 10 10:16:11 kubatron audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 subj=system_u:system_r:init_t:s0 msg='unit=systemd-suspend comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
sie 10 10:16:11 kubatron audit[1]: SERVICE_STOP pid=1 uid=0 auid=4294967295 ses=4294967295 subj=system_u:system_r:init_t:s0 msg='unit=systemd-suspend comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
sie 10 10:16:11 kubatron systemd[1]: Reached target suspend.target - Suspend.
sie 10 10:16:11 kubatron logger[6957]: <13>Aug 10 10:16:11 suspend: nvidia-resume.service
sie 10 10:16:12 kubatron systemd[1]: Stopped target suspend.target - Suspend.

Then I do what you say:

fwupdmgr update

There is no any updates for firmware.

I have disabled Secure Boot.

Also, I have for you a inxi

System:
  Kernel: 6.4.8-200.fc38.x86_64 arch: x86_64 bits: 64 compiler: gcc
    v: 2.39-9.fc38 Desktop: KDE Plasma v: 5.27.6 tk: Qt v: 5.15.10
    wm: kwin_wayland dm: SDDM Distro: Fedora release 38 (Thirty Eight)
Machine:
  Type: Laptop System: Notebook product: PD5x_7xSNC_SND_SNE v: N/A
    serial: <superuser required> Chassis: No Enclosure type: 10
    serial: <superuser required>
  Mobo: Notebook model: PD5x_7xSNC_SND_SNE serial: <superuser required>
    UEFI: INSYDE v: 1.07.11TBT date: 05/26/2023
Battery:
  ID-1: BAT0 charge: 45.3 Wh (56.8%) condition: 79.7/77.3 Wh (103.1%)
    volts: 10.9 min: 11.4 model: Notebook BAT serial: <filter>
    status: discharging
CPU:
  Info: 24-core (8-mt/16-st) model: 13th Gen Intel Core i9-13900HX bits: 64
    type: MST AMCP arch: Raptor Lake rev: 1 cache: L1: 2.1 MiB L2: 32 MiB
    L3: 36 MiB
  Speed (MHz): avg: 2298 high: 2400 min/max: 800/2200:1600 cores: 1: 800
    2: 2400 3: 2400 4: 2400 5: 2400 6: 2400 7: 2200 8: 2400 9: 2400 10: 2400
    11: 2400 12: 2400 13: 2400 14: 2400 15: 2400 16: 2400 17: 962 18: 2400
    19: 2400 20: 2400 21: 2400 22: 2400 23: 2400 24: 2400 25: 2400 26: 2400
    27: 2400 28: 2400 29: 2400 30: 2400 31: 2400 32: 2400 bogomips: 154828
  Flags: avx avx2 ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx
Graphics:
  Device-1: Intel Raptor Lake-S UHD Graphics vendor: CLEVO/KAPOK driver: i915
    v: kernel arch: Gen-13 ports: active: eDP-1 empty: DP-1, DP-2, HDMI-A-1,
    HDMI-A-2 bus-ID: 00:02.0 chip-ID: 8086:a788
  Device-2: NVIDIA AD107M [GeForce RTX 4060 Max-Q / Mobile]
    vendor: CLEVO/KAPOK driver: nvidia v: 535.86.05 arch: Lovelace pcie:
    speed: 8 GT/s lanes: 8 ports: active: none empty: DP-3, DP-4, HDMI-A-3,
    eDP-2 bus-ID: 01:00.0 chip-ID: 10de:28e0
  Device-3: Bison BisonCam NB Pro driver: uvcvideo type: USB rev: 2.0
    speed: 480 Mb/s lanes: 1 bus-ID: 1-8:4 chip-ID: 5986:214c
  Display: wayland server: X.org v: 1.20.14 with: Xwayland v: 22.1.9
    compositor: kwin_wayland driver: X: loaded: modesetting unloaded: fbdev,vesa
    dri: iris gpu: i915,nvidia display-ID: 0
  Monitor-1: eDP-1 res: 1707x960 size: N/A
  API: OpenGL v: 4.6 Mesa 23.1.5 renderer: Mesa Intel Graphics (RPL-S)
    direct-render: Yes
Audio:
  Device-1: Intel vendor: CLEVO/KAPOK driver: snd_hda_intel v: kernel
    bus-ID: 00:1f.3 chip-ID: 8086:7a50
  Device-2: NVIDIA driver: snd_hda_intel v: kernel pcie: speed: 8 GT/s
    lanes: 8 bus-ID: 01:00.1 chip-ID: 10de:22be
  API: ALSA v: k6.4.8-200.fc38.x86_64 status: kernel-api
  Server-1: PipeWire v: 0.3.77 status: active with: 1: pipewire-pulse
    status: active 2: wireplumber status: active 3: pipewire-alsa type: plugin
    4: pw-jack type: plugin
Network:
  Device-1: Intel driver: iwlwifi v: kernel port: N/A bus-ID: 00:14.3
    chip-ID: 8086:7a70
  IF: wlp0s20f3 state: up mac: <filter>
  Device-2: Realtek RTL8125 2.5GbE vendor: CLEVO/KAPOK driver: r8169
    v: kernel pcie: speed: 5 GT/s lanes: 1 port: 3000 bus-ID: 6d:00.0
    chip-ID: 10ec:8125
  IF: enp109s0 state: down mac: <filter>
Bluetooth:
  Device-1: Intel driver: btusb v: 0.8 type: USB rev: 2.0 speed: 12 Mb/s
    lanes: 1 bus-ID: 1-14:5 chip-ID: 8087:0033
  Report: rfkill ID: hci0 rfk-id: 0 state: down bt-service: enabled,running
    rfk-block: hardware: no software: yes address: see --recommends
Drives:
  Local Storage: total: 1.82 TiB used: 136.89 GiB (7.3%)
  ID-1: /dev/nvme0n1 vendor: Crucial model: CT1000P3PSSD8 size: 931.51 GiB
    speed: 63.2 Gb/s lanes: 4 serial: <filter> temp: 35.9 C
  ID-2: /dev/nvme1n1 vendor: Samsung model: SSD 980 PRO 1TB size: 931.51 GiB
    speed: 63.2 Gb/s lanes: 4 serial: <filter> temp: 34.9 C
Partition:
  ID-1: / size: 929.91 GiB used: 136.57 GiB (14.7%) fs: btrfs dev: /dev/dm-0
    mapped: luks-***..
  ID-2: /boot size: 973.4 MiB used: 308.4 MiB (31.7%) fs: ext4
    dev: /dev/nvme1n1p2
  ID-3: /boot/efi size: 598.8 MiB used: 17.4 MiB (2.9%) fs: vfat
    dev: /dev/nvme1n1p1
  ID-4: /home size: 929.91 GiB used: 136.57 GiB (14.7%) fs: btrfs
    dev: /dev/dm-0 mapped: luks-***..
Swap:
  ID-1: swap-1 type: zram size: 8 GiB used: 0 KiB (0.0%) priority: 100
    dev: /dev/zram0
Sensors:
  System Temperatures: cpu: 46.0 C mobo: N/A
  Fan Speeds (RPM): N/A
Info:
  Processes: 557 Uptime: 14m Memory: available: 62.49 GiB
  used: 5.35 GiB (8.6%) Init: systemd v: 253 target: graphical (5)
  default: graphical Compilers: gcc: 13.2.1 Packages: pm: rpm pkgs: N/A
  note: see --rpm pm: flatpak pkgs: 24 Shell: Bash v: 5.2.15
  running-in: konsole inxi: 3.3.27

Yeasterday, I have a very weird situation because when I go eat a dinner and try to use suspend with Fn + keyboard button, my laptop was success go sleep, but this was a ONE TIME!

kubatron · August 14, 2023, 7:36am

And I see that error on

dmesg -T

(Receiver ID)
[pon 14 sie 09:35:05 2023] nvme 0000:6f:00.0:   device [144d:a80a] error status/mask=00000001/0000e000
[pon 14 sie 09:35:05 2023] nvme 0000:6f:00.0:    [ 0] RxErr                  (First)
[pon 14 sie 09:35:05 2023] pcieport 0000:00:1d.0: AER: Corrected error received: 0000:6f:00.0
[pon 14 sie 09:35:05 2023] nvme 0000:6f:00.0: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID)
[pon 14 sie 09:35:05 2023] nvme 0000:6f:00.0:   device [144d:a80a] error status/mask=00000001/0000e000
[pon 14 sie 09:35:05 2023] nvme 0000:6f:00.0:    [ 0] RxErr                  (First)
[pon 14 sie 09:35:05 2023] pcieport 0000:00:1d.0: AER: Corrected error received: 0000:6f:00.0
[pon 14 sie 09:35:05 2023] pcieport 0000:00:1d.0: AER: Multiple Corrected error received: 0000:6f:00.0
[pon 14 sie 09:35:05 2023] nvme 0000:6f:00.0: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID)
[pon 14 sie 09:35:05 2023] nvme 0000:6f:00.0:   device [144d:a80a] error status/mask=00000001/0000e000
[pon 14 sie 09:35:05 2023] nvme 0000:6f:00.0:    [ 0] RxErr                  (First)
[pon 14 sie 09:35:05 2023] pcieport 0000:00:1d.0: AER: Corrected error received: 0000:6f:00.0
[pon 14 sie 09:35:05 2023] nvme 0000:6f:00.0: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID)
[pon 14 sie 09:35:05 2023] nvme 0000:6f:00.0:   device [144d:a80a] error status/mask=00000001/0000e000
[pon 14 sie 09:35:05 2023] nvme 0000:6f:00.0:    [ 0] RxErr                  (First)
[pon 14 sie 09:35:05 2023] pcieport 0000:00:1d.0: AER: Corrected error received: 0000:6f:00.0
[pon 14 sie 09:35:05 2023] nvme 0000:6f:00.0: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID)
[pon 14 sie 09:35:05 2023] nvme 0000:6f:00.0:   device [144d:a80a] error status/mask=00000001/0000e000
[pon 14 sie 09:35:05 2023] nvme 0000:6f:00.0:    [ 0] RxErr                  (First)
[pon 14 sie 09:35:05 2023] pcieport 0000:00:1d.0: AER: Corrected error received: 0000:6f:00.0
[pon 14 sie 09:35:05 2023] nvme 0000:6f:00.0: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID)
[pon 14 sie 09:35:05 2023] nvme 0000:6f:00.0:   device [144d:a80a] error status/mask=00000001/0000e000
[pon 14 sie 09:35:05 2023] nvme 0000:6f:00.0:    [ 0] RxErr                  (First)
[pon 14 sie 09:35:05 2023] pcieport 0000:00:1d.0: AER: Corrected error received: 0000:6f:00.0
[pon 14 sie 09:35:05 2023] nvme 0000:6f:00.0: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID)
[pon 14 sie 09:35:05 2023] nvme 0000:6f:00.0:   device [144d:a80a] error status/mask=00000001/0000e000
[pon 14 sie 09:35:05 2023] nvme 0000:6f:00.0:    [ 0] RxErr                  (First)
[pon 14 sie 09:35:05 2023] pcieport 0000:00:1d.0: AER: Corrected error received: 0000:6f:00.0
[pon 14 sie 09:35:05 2023] nvme 0000:6f:00.0: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID)
[pon 14 sie 09:35:05 2023] nvme 0000:6f:00.0:   device [144d:a80a] error status/mask=00000001/0000e000
[pon 14 sie 09:35:05 2023] nvme 0000:6f:00.0:    [ 0] RxErr                  (First)
[pon 14 sie 09:35:05 2023] pcieport 0000:00:1d.0: AER: Multiple Corrected error received: 0000:6f:00.0
[pon 14 sie 09:35:05 2023] nvme 0000:6f:00.0: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID)
[pon 14 sie 09:35:05 2023] nvme 0000:6f:00.0:   device [144d:a80a] error status/mask=00000001/0000e000
[pon 14 sie 09:35:05 2023] nvme 0000:6f:00.0:    [ 0] RxErr                  (First)

gnwiii · August 14, 2023, 2:19pm

nvme 0000:6f:00.0: device [144d:a80a] error status/mask=00000001/0000e000 is a Samsung NVMe SSD Controller PM9A1/PM9A3/980PRO. Check that your BIOS and Samsung NVME firmware are current.

Outdated: Arch Linux NVME Troubleshooting was written for older kernels.

More recent: Get Read-only Filesystem Sometimes on Wake mentions a number of things you can try if firmware updates don’t help.

kubatron · August 22, 2023, 3:58pm

I was struggling with that many days.
And any solution is working, I cannot update firmware, I try that things that you provide me and other.
Yesterday, I have a very weird situation. I have setup in KDE Plasma in Energy Settings, automaticly goes suspend after 15minutes on battery/power, when I turn off a external monitor and turn off mouse, keyboard was still plug-in to laptop , after 15minutes my laptop goes sleep (suspend) automaticly and that was working few times when I was trying to reproduce that, but ONLY AND IF ONLY THE EXTERNAL MONITOR WAS OFF - BY “OFF” I mean turn off by button physicaly. I am thinking mayby it is a problem with not a disk but with a external monitor ?
But, furthermore when that occurs I forget to see what power mode I was using, because I thing this could be potential another thing that brings suspend mode to some problems, and the last thing is a NVIDIA DRIVERS, mayby that drivers are struggling with that ?
And the last last thing that is weird for me is that line from today:

journalctl -b --grep=suspend
::
sie 22 17:25:57 k kernel: nvme 0000:6c:00.0: platform quirk: setting simple suspend
sie 22 17:25:57 k kernel: nvme 0000:6f:00.0: platform quirk: setting simple suspend
sie 22 17:26:52 k kded5[4120]: kscreen.kded: PowerDevil SuspendSession action not available!

And that was occurs when I try to reproduce that suspend today, but today my suspend mode doesn’t work…and the last thing is I have a second SSD

gnwiii · August 22, 2023, 11:56pm

I missed mention of your laptop vendor. Upgrading Samsung firmware should be manageable. Try: How to Update Samsung Firmware.

Linux modesetting drivers query the monitor for the EDID. This can fail if the monitor is turned off. You can experiment with the suggestions from the EDID document: “nomodeset” or "an individually prepared or corrected EDID data set in the /lib/firmware directory from where it is loaded via the firmware interface. "

kubatron · September 1, 2023, 2:09pm

I tried that how to update samsung firmware and I cannot update any thing via fwup* .

sudo fwupdmgr refresh --force -vvv
(fwupdmgr:26414): GLib-DEBUG: 16:03:15.142: setenv()/putenv() are not thread-safe and should not be used after threads are created
(pkttyagent:26416): GLib-GIO-DEBUG: 16:03:15.144: Using cross-namespace EXTERNAL authentication (this will deadlock if server is GDBus < 2.73.3)
(fwupdmgr:26414): GLib-GIO-DEBUG: 16:03:15.148: _g_io_module_get_default: Found default implementation dconf (DConfSettingsBackend) for ‘gsettings-backend’
(fwupdmgr:26414): dconf-DEBUG: 16:03:15.148: watch_fast: “/system/proxy/” (establishing: 0, active: 0)
(fwupdmgr:26414): dconf-DEBUG: 16:03:15.148: watch_fast: “/system/proxy/http/” (establishing: 0, active: 0)
(fwupdmgr:26414): dconf-DEBUG: 16:03:15.148: watch_fast: “/system/proxy/https/” (establishing: 0, active: 0)
(fwupdmgr:26414): dconf-DEBUG: 16:03:15.148: watch_fast: “/system/proxy/ftp/” (establishing: 0, active: 0)
(fwupdmgr:26414): dconf-DEBUG: 16:03:15.148: watch_fast: “/system/proxy/socks/” (establishing: 0, active: 0)
(fwupdmgr:26414): dconf-DEBUG: 16:03:15.148: unwatch_fast: “/system/proxy/” (active: 0, establishing: 1)
(fwupdmgr:26414): dconf-DEBUG: 16:03:15.148: unwatch_fast: “/system/proxy/http/” (active: 0, establishing: 1)
(fwupdmgr:26414): dconf-DEBUG: 16:03:15.148: unwatch_fast: “/system/proxy/https/” (active: 0, establishing: 1)
(fwupdmgr:26414): dconf-DEBUG: 16:03:15.148: unwatch_fast: “/system/proxy/ftp/” (active: 0, establishing: 1)
(fwupdmgr:26414): dconf-DEBUG: 16:03:15.148: unwatch_fast: “/system/proxy/socks/” (active: 0, establishing: 1)
(fwupdmgr:26414): GLib-GIO-DEBUG: 16:03:15.149: _g_io_module_get_default: Found default implementation libproxy (GLibproxyResolver) for ‘gio-proxy-resolver’
(fwupdmgr:26414): GLib-GIO-DEBUG: 16:03:15.151: Using cross-namespace EXTERNAL authentication (this will deadlock if server is GDBus < 2.73.3)
(fwupdmgr:26414): GLib-GIO-DEBUG: 16:03:15.151: Using cross-namespace EXTERNAL authentication (this will deadlock if server is GDBus < 2.73.3)
(fwupdmgr:26414): Fwupd-DEBUG: 16:03:15.151: Emitting ::status-changed() [idle]
(fwupdmgr:26414): dconf-DEBUG: 16:03:15.152: watch_established: “/system/proxy/” (establishing: 0)
(fwupdmgr:26414): dconf-DEBUG: 16:03:15.152: watch_established: “/system/proxy/http/” (establishing: 0)
(fwupdmgr:26414): dconf-DEBUG: 16:03:15.152: watch_established: “/system/proxy/https/” (establishing: 0)
(fwupdmgr:26414): dconf-DEBUG: 16:03:15.152: watch_established: “/system/proxy/ftp/” (establishing: 0)
(fwupdmgr:26414): dconf-DEBUG: 16:03:15.152: watch_established: “/system/proxy/socks/” (establishing: 0)
Aktualizowanie lvfs
Fwupd-INFO: 16:03:15.154: downloading https://cdn.fwupd.org/downloads/firmware.xml.xz.jcat
(fwupdmgr:26414): Fwupd-DEBUG: 16:03:15.154: Emitting ::status-changed() [downloading]
Pobieranie… [ \ ]Fwupd-INFO: 16:03:15.297: download progress: 100%
(fwupdmgr:26414): Fwupd-DEBUG: 16:03:15.298: Emitting ::status-changed() [idle]
Fwupd-INFO: 16:03:15.298: status-code was 200
Fwupd-INFO: 16:03:15.299: changing metadata URI from https://cdn.fwupd.org/downloads/firmware.xml.xz to https://cdn.fwupd.org/downloads/firmware-06724-stable.xml.xz
Fwupd-INFO: 16:03:15.299: metadata signature of lvfs is unchanged, skipping

And to be clear, I used and follow link that you sent me earlier and this doesn’t work.

About EDID I don’t know how to do that and mayby I sounds like idiot.

And I don’t want to install Windows for only one thing to download a Samsung tools for upgrade a firmware and then go back to Fedora, because this is so anoying and time wasting.
Problem with suspend and freezing is still with me, I don’t have any idea how to fix that…I am thing mayby this is related to LUKS encryption and NVidia, I don’t know. Few times suspend start work that I mentioned in this topic, but I don’t know why works and why is still doens’t work.

If someone has any other idea or sollution, please let me know, I can bring a addition logs or whatever here should be need.

gnwiii · September 1, 2023, 3:40pm

but not as annoying and time wasting as the problems bad firmware can cause.

I think Dell and Lenovo support NVME firmware updates using fwupd for NVME models they use.

Check the available Samsung updates and compare with what you get using nvme-cli and then follow the instructions in Firmware Update Utility UserManual to inbstall UNetbootin.

computersavvy · September 1, 2023, 4:56pm

Some systems seem to only allow a firmware update from windows, and many seem to have found that they could install winPE on a usb device and perform the firmware update by booting from the flash drive. Some have even used ventoy to do this from the winpe iso image.

kubatron · September 11, 2023, 7:10am

@gnwiii I search a update via my disk number/etc. but there is (for now) any update availability, furthermore I try to install a tools that you mention from Samsung official website for Linux update, using UNetbootin and I crash my whole Fedora system to state where I can only read files, so I reinstall system to new.

But, one thing that I remember, when I asked first about that issue on Matrix Fedora room, one of the guy said me I should check a SWAP FILE (partition) because that could be a issue, and then I check many things like:

[kubatron@kubatron ~]$ lsblk
NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINTS
zram0 252:0 0 8G 0 disk [SWAP]
nvme0n1 259:0 0 931,5G 0 disk
├─nvme0n1p1 259:1 0 600M 0 part /boot/efi
├─nvme0n1p2 259:2 0 1G 0 part /boot
└─nvme0n1p3 259:3 0 929,9G 0 part
└─luks-f1a59ab0-40c6-4deb-bdf5-954f8cec2b47 253:0 0 929,9G 0 crypt /home
/

[kubatron@kubatron ~]$ blkid
/dev/nvme0n1p1: UUID=“8CA5-CAE1” BLOCK_SIZE=“512” TYPE=“vfat” PARTLABEL=“EFI System Partition” PARTUUID=“e19
6ec03-5016-484f-8170-d3fb58cfff48”
/dev/nvme0n1p2: UUID=“265c8b1e-0753-4c0a-9591-946dc8a7a6d5” BLOCK_SIZE=“4096” TYPE=“ext4” PARTUUID=“b4ebcd85
-c3bb-45c7-9044-21acf8d2d03b”
/dev/nvme0n1p3: UUID=“f1a59ab0-40c6-4deb-bdf5-954f8cec2b47” TYPE=“crypto_LUKS” PARTUUID=“206da2a4-3e19-4279-
8c1a-682403316610”
/dev/nvme1n1p1: UUID=“5ac62cbe-f08a-41ed-a79f-48a8e5d5ca6f” TYPE=“crypto_LUKS” PARTUUID=“f7af0d5d-fc6e-2c4a-
b3a3-465258dcd989”
/dev/mapper/luks-f1a59ab0-40c6-4deb-bdf5-954f8cec2b47: LABEL=“fedora_localhost-live” UUID=“50cc345d-6938-46d
c-97a4-a92bb3ed876d” UUID_SUB=“27dcbf3b-f5d1-4a5b-b835-01b72d0d6296” BLOCK_SIZE=“4096” TYPE=“btrfs”

[kubatron@kubatron ~]$ swapon --show
NAME TYPE SIZE USED PRIO
/dev/zram0 partition 8G 0B 100

[kubatron@kubatron ~]$ sudo cat /etc/fstab
UUID=50cc345d-6938-46dc-97a4-a92bb3ed876d / btrfs subvol=root,compress=zstd:1,x-systemd.device-timeout=0 0 0
UUID=265c8b1e-0753-4c0a-9591-946dc8a7a6d5 /boot ext4 defaults 1 2
UUID=8CA5-CAE1 /boot/efi vfat umask=0077,shortname=winnt 0 2
UUID=50cc345d-6938-46dc-97a4-a92bb3ed876d /home btrfs subvol=home,compress=zstd:1,x-systemd.device-timeout=0 0 0

[kubatron@kubatron ~]$ zramctl
NAME ALGORITHM DISKSIZE DATA COMPR TOTAL STREAMS MOUNTPOINT
/dev/zram0 lzo-rle 8G 4K 80B 12K 32 [SWAP]

And I remember that I try some command that he provided me to try mount a swap file and the suspend was work and I don’t know if this could be a issue, but in /etc/fstab are not any mountpoint.

Is this possible to be a problem with suspend ?

Furthermore, I have a new interesting logs file related to suspend after last time upgrade to new kernel.

And I write that because I don’t wanna mess with a system to do some stuff that I find on many forums and topics how to mount a swap file etc.

Thanks for your patient to me! This is really great to have a people and community like that!

jakfrost · September 11, 2023, 12:44pm

Using a swap partition for suspend activities is a good idea IMO. I have one and also use my zram swap, the swap in ram is higher priority and the swap partition is used as required and set at lower priority.