Not waking up from sleep after installing Manjaro 20.1.1 liveCD

I use a keyboard shortcut to put the computer to sleep. The problem is that after installing the Manjaro 20.1.1 iso, the computer doesn’t wake up in response to keyboard inputs, mouse clicks or movement, or pressing the power button. So I have to reboot it with the reboot button.

The same thing happens when I put it to sleep via the GUI.

I think it is because I don’t have swap allocated for this partition? I have swap allocated for the previous Manjaro Linux partition. I guess I need to allocate separate swap for this one as well? Here’s an answer; probably better to use separate partitions, and in my case it would be even better to delete the older Manjaro partition, or fix the issue that I have with it and delete the new one.

Sleep should work without swap. After suspending and then rebooting through reset, please post the output of the following command:

journalctl -p3 -b-1

Also try to suspend from the terminal:

systemctl suspend

2 Likes
[jr@fm ~]$ journalctl -p3 -b-1
-- Logs begin at Tue 2020-10-06 13:22:53 AEDT, end at Thu 2020-10-08 12:23:59 AEDT. --
Oct 08 12:20:12 fm kernel: sp5100-tco sp5100-tco: Watchdog hardware is disabled
Oct 08 12:20:12 fm kernel: kvm: disabled by bios
Oct 08 12:20:12 fm kernel: kvm: disabled by bios
Oct 08 12:20:13 fm kernel: kvm: disabled by bios
Oct 08 12:20:13 fm kernel: kvm: disabled by bios
Oct 08 12:20:13 fm kernel: kvm: disabled by bios
Oct 08 12:20:13 fm sddm[637]: Failed to read display number from pipe
Oct 08 12:20:13 fm sddm[637]: Display server failed to start. Exiting
Oct 08 12:20:13 fm kernel: kvm: disabled by bios
Oct 08 12:20:13 fm kernel: kvm: disabled by bios
Oct 08 12:20:13 fm systemd-coredump[805]: Process 637 (sddm) of user 0 dumped core.
                                          
                                          Stack trace of thread 637:
                                          #0  0x00007f654877d615 raise (libc.so.6 + 0x3d615)
                                          #1  0x00007f6548766862 abort (libc.so.6 + 0x26862)
                                          #2  0x00007f6548b929ac _ZNK14QMessageLogger5fatalEPKcz (libQt5Core.so.5 + 0x909ac)
                                          #3  0x000055745448d0c8 n/a (sddm + 0x290c8)
                                          #4  0x00005574544cf4b1 _ZN4SDDM4SeatC2ERK7QStringP7QObject (sddm + 0x6b4b1)
                                          #5  0x00005574544d1081 _ZN4SDDM11SeatManager10createSeatERK7QString (sddm + 0x6d081)
                                          #6  0x00005574544d1ec3 n/a (sddm + 0x6dec3)
                                          #7  0x00007f6548ded036 n/a (libQt5Core.so.5 + 0x2eb036)
                                          #8  0x00005574544d0080 _ZN4SDDM10LogindSeat19canGraphicalChangedEb (sddm + 0x6c080)
                                          #9  0x00005574544d2d7b _ZN4SDDM10LogindSeat11qt_metacallEN11QMetaObject4CallEiPPv (sddm + 0x6ed7b)
                                          #10 0x00007f6549709066 n/a (libQt5DBus.so.5 + 0x21066)
                                          #11 0x00007f6548de27e2 _ZN7QObject5eventEP6QEvent (libQt5Core.so.5 + 0x2e07e2)
                                          #12 0x00007f6548db5cb0 _ZN16QCoreApplication15notifyInternal2EP7QObjectP6QEvent (libQt5Core.so.5 + 0x2b3cb0)
                                          #13 0x00007f6548db87d3 _ZN23QCoreApplicationPrivate16sendPostedEventsEP7QObjectiP11QThreadData (libQt5Core.so.5 + 0x2b67d3)
                                          #14 0x00007f6548e0f304 n/a (libQt5Core.so.5 + 0x30d304)
                                          #15 0x00007f65478ebbfc g_main_context_dispatch (libglib-2.0.so.0 + 0x52bfc)
                                          #16 0x00007f654793d1f9 n/a (libglib-2.0.so.0 + 0xa41f9)
                                          #17 0x00007f65478ea421 g_main_context_iteration (libglib-2.0.so.0 + 0x51421)
                                          #18 0x00007f6548e0e941 _ZN20QEventDispatcherGlib13processEventsE6QFlagsIN10QEventLoop17ProcessEventsFlagEE (libQt5Core.so.5 + 0x30c941)
                                          #19 0x00007f6548db465c _ZN10QEventLoop4execE6QFlagsINS_17ProcessEventsFlagEE (libQt5Core.so.5 + 0x2b265c)
                                          #20 0x00007f6548dbcaf4 _ZN16QCoreApplication4execEv (libQt5Core.so.5 + 0x2baaf4)
                                          #21 0x000055745448ff31 main (sddm + 0x2bf31)
                                          #22 0x00007f6548768152 __libc_start_main (libc.so.6 + 0x28152)
                                          #23 0x000055745449023e _start (sddm + 0x2c23e)
                                          
                                          Stack trace of thread 639:
                                          #0  0x00007f654883546f __poll (libc.so.6 + 0xf546f)
                                          #1  0x00007f654793d188 n/a (libglib-2.0.so.0 + 0xa4188)
                                          #2  0x00007f65478ea421 g_main_context_iteration (libglib-2.0.so.0 + 0x51421)
                                          #3  0x00007f6548e0e941 _ZN20QEventDispatcherGlib13processEventsE6QFlagsIN10QEventLoop17ProcessEventsFlagEE (libQt5Core.so.5 + 0x30c941)
                                          #4  0x00007f6548db465c _ZN10QEventLoop4execE6QFlagsINS_17ProcessEventsFlagEE (libQt5Core.so.5 + 0x2b265c)
                                          #5  0x00007f6548bceca2 _ZN7QThread4execEv (libQt5Core.so.5 + 0xccca2)
                                          #6  0x00007f65496ff098 n/a (libQt5DBus.so.5 + 0x17098)
                                          #7  0x00007f6548bcfe8f n/a (libQt5Core.so.5 + 0xcde8f)
                                          #8  0x00007f65487273e9 start_thread (libpthread.so.0 + 0x93e9)
                                          #9  0x00007f6548840293 __clone (libc.so.6 + 0x100293)
Oct 08 12:20:13 fm kernel: kvm: disabled by bios
Oct 08 12:20:13 fm kernel: kvm: disabled by bios
Oct 08 12:20:14 fm kernel: kvm: disabled by bios
[jr@fm ~]$ 

Same result—non-responsive after sleeping.

For suspend you don’t need swap. You have to make sure how your BIOS is set up for suspend, then on your newer install you have to check
https://wiki.archlinux.org/index.php/Power_management

Ok, sddm crashes. Please post the output of inxi -Fazy and, after a suspend/reboot cycle, the output of cat /var/log/xorg.0.log.old

I enabled virtualisation in BIOS, although I don’t need it.

I also followed these instructions:

post installation - the trick to get sp5100_tco working properly is to have it initialised first. you can do that by adding it into mkinitcpio.conf as follows.

  1. open terminal.
  2. issue the command sudo nano /etc/mkinitcpio.conf
  3. find the line that starts MODULES=
  4. alter it so it reads MODULES=(sp5100_tco)

if you want any additional modules loaded earlier put a space between them, they can all be enclosed in the single quote marks already entered, do not add more. e.g. (sp5100_tco amdpgu)

  1. write out the change using CTRL+O
  2. exit using CTRL+X

6 b. edit /etc/default/grub.conf and remove any blacklist reference to sp5100_tco.

  1. regenerate the linux image with sudo mkinitcpio -P
  2. if you altered grub you also need to sudo update-grub

Now I can boot into kernel 5.8. Awake after suspending doesn’t work, however.

But it is working in 5.4, although now only one monitor wakes up.

Oops, forgot to do step 7 above.

Done, and in 5.4 it suspends and awakes as expected. Will try 5.8.

In 5.8 it suspends but does not awake—i.e. same issue.

[jr@fm ~]$ inxi -Fazy
System:
  Kernel: 5.8.11-1-MANJARO x86_64 bits: 64 compiler: N/A 
  parameters: BOOT_IMAGE=/boot/vmlinuz-5.8-x86_64 
  root=UUID=1e8aecd0-e0c4-4dd2-8320-8a8dd8df66c6 rw quiet apparmor=1 
  security=apparmor udev.log_priority=3 
  Desktop: KDE Plasma 5.19.5 tk: Qt 5.15.1 wm: kwin_x11 dm: SDDM 
  Distro: Manjaro Linux 
Machine:
  Type: Desktop Mobo: ASUSTeK model: TUF B450M-PLUS GAMING v: Rev X.0x 
  serial: <filter> UEFI: American Megatrends v: 1002 date: 03/07/2019 
CPU:
  Topology: 8-Core model: AMD Ryzen 7 2700X bits: 64 type: MT MCP arch: Zen+ 
  family: 17 (23) model-id: 8 stepping: 2 microcode: 800820D 
  L2 cache: 4096 KiB 
  flags: avx avx2 lm nx pae sse sse2 sse3 sse4_1 sse4_2 sse4a ssse3 svm 
  bogomips: 118220 
  Speed: 1991 MHz min/max: 2200/3700 MHz boost: enabled Core speeds (MHz): 
  1: 2032 2: 1848 3: 1979 4: 2075 5: 2167 6: 2192 7: 2194 8: 2194 9: 2037 
  10: 2066 11: 1891 12: 1883 13: 1929 14: 2199 15: 2209 16: 2074 
  Vulnerabilities: Type: itlb_multihit status: Not affected 
  Type: l1tf status: Not affected 
  Type: mds status: Not affected 
  Type: meltdown status: Not affected 
  Type: spec_store_bypass 
  mitigation: Speculative Store Bypass disabled via prctl and seccomp 
  Type: spectre_v1 
  mitigation: usercopy/swapgs barriers and __user pointer sanitization 
  Type: spectre_v2 mitigation: Full AMD retpoline, IBPB: conditional, STIBP: 
  disabled, RSB filling 
  Type: srbds status: Not affected 
  Type: tsx_async_abort status: Not affected 
Graphics:
  Device-1: NVIDIA TU104 [GeForce RTX 2080] vendor: ASUSTeK driver: nouveau 
  v: kernel bus ID: 07:00.0 chip ID: 10de:1e82 
  Display: x11 server: X.Org 1.20.9 compositor: kwin_x11 
  driver: modesetting,nouveau alternate: fbdev,nv,vesa display ID: :0 
  screens: 1 
  Screen-1: 0 s-res: 3840x1080 s-dpi: 96 s-size: 1016x285mm (40.0x11.2") 
  s-diag: 1055mm (41.5") 
  Monitor-1: DP-1 res: 1920x1080 hz: 60 dpi: 94 size: 521x293mm (20.5x11.5") 
  diag: 598mm (23.5") 
  Monitor-2: HDMI-1 res: 1920x1080 hz: 60 dpi: 94 size: 521x293mm (20.5x11.5") 
  diag: 598mm (23.5") 
  OpenGL: renderer: llvmpipe (LLVM 10.0.1 256 bits) v: 3.3 Mesa 20.1.8 
  compat-v: 3.1 direct render: Yes 
Audio:
  Device-1: NVIDIA TU104 HD Audio vendor: ASUSTeK driver: snd_hda_intel 
  v: kernel bus ID: 07:00.1 chip ID: 10de:10f8 
  Device-2: AMD Family 17h HD Audio vendor: ASUSTeK driver: snd_hda_intel 
  v: kernel bus ID: 09:00.3 chip ID: 1022:1457 
  Sound Server: ALSA v: k5.8.11-1-MANJARO 
Network:
  Device-1: Realtek RTL8111/8168/8411 PCI Express Gigabit Ethernet 
  vendor: ASUSTeK driver: r8169 v: kernel port: f000 bus ID: 05:00.0 
  chip ID: 10ec:8168 
  IF: enp5s0 state: up speed: 1000 Mbps duplex: full mac: <filter> 
Drives:
  Local Storage: total: 1.38 TiB used: 13.53 GiB (1.0%) 
  SMART Message: Unable to run smartctl. Root privileges required. 
  ID-1: /dev/nvme0n1 vendor: Samsung model: SSD 970 EVO Plus 500GB 
  size: 465.76 GiB block size: physical: 512 B logical: 512 B speed: 31.6 Gb/s 
  lanes: 4 serial: <filter> rev: 1B2QEXM7 scheme: GPT 
  ID-2: /dev/sda type: USB vendor: Seagate model: Expansion size: 931.51 GiB 
  block size: physical: 4096 B logical: 512 B serial: <filter> rev: 0707 
  scheme: MBR 
  ID-3: /dev/sdb type: USB vendor: SanDisk model: Cruzer Blade size: 14.59 GiB 
  block size: physical: 512 B logical: 512 B serial: <filter> rev: 1.00 
  scheme: MBR 
  SMART Message: Unknown USB bridge. Flash drive/Unsupported enclosure? 
Partition:
  ID-1: / raw size: 111.62 GiB size: 109.37 GiB (97.98%) 
  used: 13.53 GiB (12.4%) fs: ext4 dev: /dev/nvme0n1p4 
Swap:
  Kernel: swappiness: 60 (default) cache pressure: 100 (default) 
  ID-1: swap-1 type: partition size: 69.20 GiB used: 0 KiB (0.0%) priority: -2 
  dev: /dev/nvme0n1p3 
Sensors:
  System Temperatures: cpu: 52.4 C mobo: N/A gpu: nouveau temp: 34 C 
  Fan Speeds (RPM): N/A gpu: nouveau fan: 1119 
Info:
  Processes: 350 Uptime: 1m Memory: 62.81 GiB used: 2.56 GiB (4.1%) 
  Init: systemd v: 246 Compilers: gcc: N/A Packages: pacman: 1194 lib: 319 
  flatpak: 0 Shell: Bash v: 5.0.18 running in: konsole inxi: 3.1.05 
[jr@fm ~]$ 
[jr@fm ~]$ cat /var/log/xorg.0.log.old
cat: /var/log/xorg.0.log.old: No such file or directory
[jr@fm ~]$ 

That was after sleeping via the GUI.

After systemctl suspend in the terminal and rebooting into 5.8, I didn’t get to the login screen. Currently there is a black screen with a cursor. CTRL+ALT+F2 does not show a tty.

Rebooting again into 5.8, I got in. :man_shrugging:

[jr@fm ~]$ cat /var/log/xorg.0.log.old
cat: /var/log/xorg.0.log.old: No such file or directory
[jr@fm ~]$ 

I then slept via the GUI again and rebooted into 5.8 again. However, now Firefox is non-responsive (process ID: 1830), and when I try to close it, after a couple of seconds I get a warning pop up window, saying it’s not responding, do you want to terminate it, but if I click the terminate button nothing happens. kill 1830 also doesn’t close it.

Additionally, systemctl suspend suspended and then it woke up. In the login screen, there was a considerable lag with showing the password after typing it, and doing this process again after logging in, the delay was about 20 s between the login screen appeared and the password prompt showed along with keyboard input. Once more and there was no delay.

I’ll use kernel 5.4 for now.

Use this kernel then. After all, it is the current LTS version. If you still want to post the missing output, the “x” in “xorg” is uppercase (Xorg.0.log.old). Sorry for the typo.

cat /var/log/Xorg.0.log.old

The output was cut off in the terminal so I sent the output to a file and put it here:

Yeah LTS is going to be more stable, which is more important for productivity—avoiding time spent fixing issues or bugs—than having the latest features.

[ 3.941] (EE) Unknown chipset: NV164

I think you’d be better using the proprietary NVIDIA driver instead of noveau. First check available and installed drivers:

mhwd --pci -li
mhwd --pci -l

EDIT: you can also check it in Manjaro Settings Manager > Hardware Config

[jr@fm ~]$ mhwd --pci -li
> Installed PCI configs:
--------------------------------------------------------------------------------
                  NAME               VERSION          FREEDRIVER           TYPE
--------------------------------------------------------------------------------
           video-linux            2018.05.04                true            PCI


[jr@fm ~]$ mhwd --pci -l
> 0000:07:00.0 (0300:10de:1e82) Display controller nVidia Corporation:
--------------------------------------------------------------------------------
                  NAME               VERSION          FREEDRIVER           TYPE
--------------------------------------------------------------------------------
    video-nvidia-450xx            2019.10.25               false            PCI
    video-nvidia-440xx            2019.10.25               false            PCI
    video-nvidia-435xx            2019.10.25               false            PCI
    video-nvidia-430xx            2019.10.25               false            PCI
    video-nvidia-418xx            2019.10.25               false            PCI
           video-linux            2018.05.04                true            PCI
     video-modesetting            2020.01.13                true            PCI
            video-vesa            2017.03.12                true            PCI


> 0000:05:00.0 (0200:10ec:8168) Network controller Realtek Semiconductor Co., Ltd.:
--------------------------------------------------------------------------------
                  NAME               VERSION          FREEDRIVER           TYPE
--------------------------------------------------------------------------------
         network-r8168            2016.04.20                true            PCI


[jr@fm ~]$ 

Installed video-nvidia-450xx.

Awake from suspend now works in kernel 5.8! Thanks!

1 Like

I just woke up my computer just now this morning after sleeping overnight, and I had black screens with the cursor, so I rebooted via the tty. Generally speaking, I put the computer to sleep when I’m not using it.

My energy saving settings:

I’ll try removing video-nvidia-450xx and installing 440x instead.

If the issue persists I’ll revert to kernel 5.4.

I’d try that. Is there any feature you really need specific from kernel 5.8?

You can also wait a bit, to see if the back screen disappears. My desktop, for example, takes a bit to come back - though I know that’s not normal in a laptop waking from suspend. You can also try changing tty and back. On some occasions it brings the login screen back.

Yeah kernel 5.4 seems best. I’m not aware of any 5.8 feature that I really need.

I didn’t wait for long, only 10 s max, but did try to switch between tty and back. I have 64 GB of RAM, so it’s not like it should take long to restore.

The delay isn’t related to RAM. But my desktop is old anyway. It most certainly doesn’t apply to you.

1 Like