Advertising

Welcome to SparkyLinux forums
Zapraszamy również na polsko-języczne Forum Linuxiarze.pl

Author Topic: [SOLVED] Suspend is not working  (Read 1580 times)

Offline rektal

  • Newbie
  • *
  • Posts: 38
  • Karma: 0
[SOLVED] Suspend is not working
« on: March 16, 2021, 10:11:20 am »
Hi,
Sparky Linux is awesome and runs very smooth. I am going to switch to it from Tumbleweed.

But I have got a problem with suspend.
Suspend is not working and I hear my fans is still running.
This is my BIOS setup: BIOS into "Power Management Setup" is set to "ACPI Suspend Type" to "S3 (STR)".


On my desktop computer I have got another linux distro openSUSE Tumbleweed and suspend is working on it.
I was using a Debian based MX Linux distro and suspend was working on it.Sparky Linus is Debian based distro too but suspend is not working on it. Why?
« Last Edit: March 21, 2021, 06:24:09 am by rektal »

Offline paxmark1

  • Hero Member
  • *****
  • Posts: 840
  • Karma: 4
  • https://forum.sparkylinux.org/index.php/topic,4614
Re: Suspend is not working
« Reply #1 on: March 16, 2021, 10:57:16 pm »
Not a real fan of your username. 

Clean install?

Posting inxi -br would let us see if you are in Stable or Semi-Rolling (5 vs 6)   and your DE
Search forum for "More info easier via inxi"    If requested -  no inxi, no help for you by  me.

Offline rektal

  • Newbie
  • *
  • Posts: 38
  • Karma: 0
Re: Suspend is not working
« Reply #2 on: March 17, 2021, 08:01:42 am »
I have got a Semi-Rlling realise Sparky 6 Po-Tolo with KDE.

This is a clean install.

inxi -br is not working in terminal. There is an info:
Code: [Select]
bash: inxi: command not found
Hibernate is not working too.


Offline rektal

  • Newbie
  • *
  • Posts: 38
  • Karma: 0
Re: Suspend is not working
« Reply #3 on: March 17, 2021, 08:50:52 am »
My username is an anagram of my surname in Polish.

This is rektal  and this is not a rectum. I know that in English it is not a good association.

Offline MoroS

  • Sr. Member
  • ****
  • Posts: 290
  • Karma: 0
  • Problem solver ;)
Re: Suspend is not working
« Reply #4 on: March 18, 2021, 02:55:01 pm »
Depending on your install inxi might need to be installed first:
Code: [Select]
apt install inxi
What you can also check is what happens when you try to trigger suspend from the terminal:
Code: [Select]
systemctl suspend (might need root privileges).

You might also check the output of the dmesg command for any errors, warnings, etc.
There's no such thing as "impossible". :)

Offline rektal

  • Newbie
  • *
  • Posts: 38
  • Karma: 0
Re: Suspend is not working
« Reply #5 on: March 18, 2021, 05:55:20 pm »
Thank you.
inxi -br gives me this
Code: [Select]
System:
  Host: Sparky Kernel: 5.10.0-4-amd64 x86_64 bits: 64
  Desktop: KDE Plasma 5.20.5 Distro: SparkyLinux 6 (Po-Tolo)
Machine:
  Type: Desktop Mobo: Gigabyte model: EP45-DS3 serial: <superuser required>
  BIOS: Award v: F10b date: 09/03/2009
CPU:
  Info: Dual Core Intel Core2 Duo E8400 [MCP] speed: 2680 MHz
  min/max: 2000/2667 MHz
Graphics:
  Device-1: NVIDIA G94 [GeForce 9600 GT] driver: nouveau v: kernel
  Display: x11 server: X.Org 1.20.10 driver: loaded: modesetting
  unloaded: fbdev,vesa resolution: 1920x1080~60Hz
  OpenGL: renderer: NV94 v: 3.3 Mesa 20.3.4
Network:
  Device-1: Realtek RTL8111/8168/8411 PCI Express Gigabit Ethernet
  driver: r8169
  Device-2: Realtek RTL8111/8168/8411 PCI Express Gigabit Ethernet
  driver: r8169
Drives:
  Local Storage: total: 2.27 TiB used: 823.68 GiB (35.4%)
Repos:
  Active apt repos in: /etc/apt/sources.list
  1: deb http://deb.debian.org/debian/ bullseye main contrib non-free
  2: deb-src http://deb.debian.org/debian/ bullseye main contrib non-free
  3: deb http://security.debian.org/ bullseye-security/updates main contrib non-free
  4: deb-src http://security.debian.org/ bullseye-security/updates main contrib non-free
  5: deb http://deb-multimedia.org/ bullseye main non-free
  No active apt repos in: /etc/apt/sources.list.d/dropbox.list
  No active apt repos in: /etc/apt/sources.list.d/google.list
  No active apt repos in: /etc/apt/sources.list.d/liquorix.list
  No active apt repos in: /etc/apt/sources.list.d/pipelight.list
  No active apt repos in: /etc/apt/sources.list.d/playonlinux.list
  Active apt repos in: /etc/apt/sources.list.d/sid.list
  1: deb http://ftp.debian.org/debian/ sid non-free contrib main
  2: deb-src http://ftp.debian.org/debian/ sid non-free contrib main
  3: deb http://www.deb-multimedia.org/ sid non-free main
  Active apt repos in: /etc/apt/sources.list.d/sparky-unstable.list
  1: deb https://repo.sparkylinux.org/ unstable main
  2: deb-src https://repo.sparkylinux.org/ unstable main
  Active apt repos in: /etc/apt/sources.list.d/sparky.list
  1: deb https://repo.sparkylinux.org/ core main
  2: deb-src https://repo.sparkylinux.org/ core main
  3: deb https://repo.sparkylinux.org/ potolo main
  4: deb-src https://repo.sparkylinux.org/ potolo main
  No active apt repos in: /etc/apt/sources.list.d/virtualbox.list
  No active apt repos in: /etc/apt/sources.list.d/wine-staging.list
Info:
  Processes: 166 Uptime: 23m Memory: 7.77 GiB used: 1.58 GiB (20.4%)
  Shell: Bash inxi: 3.3.01

I think there are errors in the output of the dmesg
Code: [Select]
[  100.911605] systemd-journald[238]: File /var/log/journal/1f7cf200ca1a401799212e6e336f67a5/user-1000.journal corrupted or uncleanly shut down, renaming and replacing.
[  133.432056] nouveau 0000:01:00.0: firmware: failed to load nouveau/nv84_xuc00f (-2)
[  133.432062] firmware_class: See https://wiki.debian.org/Firmware for information about missing firmware
[  133.432066] nouveau 0000:01:00.0: Direct firmware load for nouveau/nv84_xuc00f failed with error -2
[  133.432071] nouveau 0000:01:00.0: vp: unable to load firmware nouveau/nv84_xuc00f
[  133.432073] nouveau 0000:01:00.0: vp: init failed, -2
[  133.432115] nouveau 0000:01:00.0: firmware: failed to load nouveau/nv84_xuc103 (-2)
[  133.432118] nouveau 0000:01:00.0: Direct firmware load for nouveau/nv84_xuc103 failed with error -2
[  133.432121] nouveau 0000:01:00.0: bsp: unable to load firmware nouveau/nv84_xuc103
[  133.432123] nouveau 0000:01:00.0: bsp: init failed, -2
[ 1530.018319] perf: interrupt took too long (2507 > 2500), lowering kernel.perf_event_max_sample_rate to 79750

Offline rektal

  • Newbie
  • *
  • Posts: 38
  • Karma: 0
Re: Suspend is not working
« Reply #6 on: March 18, 2021, 06:07:19 pm »
 I did systemctl suspend in terminal but nothing has changed.
I hear my fans are still running.


Offline MoroS

  • Sr. Member
  • ****
  • Posts: 290
  • Karma: 0
  • Problem solver ;)
Re: Suspend is not working
« Reply #7 on: March 18, 2021, 06:10:33 pm »
I did systemctl suspend in terminal but nothing has changed.
I hear my fans are still running.

Did they stop for at least a moment? Or did it just ignore the command and keep running? Or maybe screen went off, but only the fans keep running?
There's no such thing as "impossible". :)

Offline rektal

  • Newbie
  • *
  • Posts: 38
  • Karma: 0
Re: Suspend is not working
« Reply #8 on: March 18, 2021, 06:41:04 pm »
Screen went off, but only the fans keep running.

About dmesg output. There is a bolded font and red font. What does it mean? Warning? Errors?

Offline rektal

  • Newbie
  • *
  • Posts: 38
  • Karma: 0
Re: Suspend is not working
« Reply #9 on: March 19, 2021, 07:36:25 am »
These are all errors or warnings in dmesg. Fonts are white bolded or red.
Code: [Select]
[    0.282903] pmd_set_huge: Cannot satisfy [mem 0xf4000000-0xf4200000] with a huge-page mapping due to MTRR override.
[    1.621498] i8042: Failed to disable AUX port, but continuing anyway... Is this a SiS?
[    1.621499] i8042: If AUX port is really absent please use the 'i8042.noaux' option
[    1.930474] Unstable clock detected, switching default tracing clock to "global"
               If you want to keep using the local clock, then add:
                 "trace_clock=local"
               on the kernel command line
[    2.167506] r8169 0000:04:00.0: can't disable ASPM; OS doesn't have ASPM control
[    2.202203] ACPI Warning: SystemIO range 0x0000000000000428-0x000000000000042F conflicts with OpRegion 0x000000000000042C-0x000000000000042D (\GP2C) (20200925/utaddress-204)
[    2.202235] lpc_ich: Resource conflict(s) found affecting gpio_ich
[    2.236857] r8169 0000:05:00.0: can't disable ASPM; OS doesn't have ASPM control
[    2.594365] nouveau 0000:01:00.0: DRM: failed to create encoder 0/1/0: -19
[    2.594367] nouveau 0000:01:00.0: DRM: TV-1 has no encoders, removing
[   12.582645] systemd[1]: /lib/systemd/system/plymouth-start.service:16: Unit configured to use KillMode=none. This is unsafe, as it disables systemd's process lifecycle management for the service. Please update your service to use a safer KillMode=, such as 'mixed' or 'control-group'. Support for KillMode=none is deprecated and will eventually be removed.
[  139.063903] nouveau 0000:01:00.0: firmware: failed to load nouveau/nv84_xuc00f (-2)
[  139.063908] firmware_class: See https://wiki.debian.org/Firmware for information about missing firmware
[  139.063911] nouveau 0000:01:00.0: Direct firmware load for nouveau/nv84_xuc00f failed with error -2
[  139.063914] nouveau 0000:01:00.0: vp: unable to load firmware nouveau/nv84_xuc00f
[  139.063916] nouveau 0000:01:00.0: vp: init failed, -2
[  139.063937] nouveau 0000:01:00.0: firmware: failed to load nouveau/nv84_xuc103 (-2)
[  139.063940] nouveau 0000:01:00.0: Direct firmware load for nouveau/nv84_xuc103 failed with error -2
[  139.063941] nouveau 0000:01:00.0: bsp: unable to load firmware nouveau/nv84_xuc103
[  139.063943] nouveau 0000:01:00.0: bsp: init failed, -2


Offline MoroS

  • Sr. Member
  • ****
  • Posts: 290
  • Karma: 0
  • Problem solver ;)
Re: Suspend is not working
« Reply #10 on: March 19, 2021, 10:52:18 am »
The logs won't probably be too helpful here... Unless it's a nVidia-based issue. Did you at any point of this installation have the nVidia proprietary drivers installled? Nouveau tries to load firmware for the wrong card for some reason (nv84 does not support GF 9600 GT - that's nv94). You might want to check the following directories and files for anything regarding blacklisting, nouveau or nv94:
  • /etc/modules
  • /etc/modprobe.d/*
  • /etc/modules-load.d/*
  • /etc/nvidia/* - if it exists

Could you also post the output of:

Code: [Select]
dmesg | grep nouveau
so we can confirm, that indeed there is no firmware loaded properly.

Faulty firmware might be the issue here, so maybe let's try to fix that first.

You might also check if the /etc/X11/xorg.conf file exists or if you have anything in the /etc/X11/xorg.conf.d/ directory. Don't do anything with it yet, though.
There's no such thing as "impossible". :)

Offline rektal

  • Newbie
  • *
  • Posts: 38
  • Karma: 0
Re: Suspend is not working
« Reply #11 on: March 19, 2021, 11:46:02 am »
There is an output:
Code: [Select]
root@Sparky:/home/rektal# dmesg | grep nouveau
[    2.388847] nouveau 0000:01:00.0: vgaarb: deactivate vga console
[    2.389658] nouveau 0000:01:00.0: NVIDIA G94 (094100a1)
[    2.502986] nouveau 0000:01:00.0: bios: version 62.94.11.00.03
[    2.523624] nouveau 0000:01:00.0: fb: 512 MiB GDDR3
[    2.592187] nouveau 0000:01:00.0: DRM: VRAM: 512 MiB
[    2.592188] nouveau 0000:01:00.0: DRM: GART: 1048576 MiB
[    2.592191] nouveau 0000:01:00.0: DRM: TMDS table version 2.0
[    2.592192] nouveau 0000:01:00.0: DRM: DCB version 4.0
[    2.592194] nouveau 0000:01:00.0: DRM: DCB outp 00: 02000300 00000028
[    2.592196] nouveau 0000:01:00.0: DRM: DCB outp 01: 01000302 00020030
[    2.592197] nouveau 0000:01:00.0: DRM: DCB outp 02: 04011310 00000028
[    2.592199] nouveau 0000:01:00.0: DRM: DCB outp 03: 02011312 00020030
[    2.592200] nouveau 0000:01:00.0: DRM: DCB outp 04: 010223f1 00c0c080
[    2.592202] nouveau 0000:01:00.0: DRM: DCB conn 00: 00001030
[    2.592203] nouveau 0000:01:00.0: DRM: DCB conn 01: 00002130
[    2.592205] nouveau 0000:01:00.0: DRM: DCB conn 02: 00000210
[    2.592206] nouveau 0000:01:00.0: DRM: DCB conn 03: 00000211
[    2.592207] nouveau 0000:01:00.0: DRM: DCB conn 04: 00000213
[    2.593794] nouveau 0000:01:00.0: DRM: MM: using CRYPT for buffer copies
[    2.594365] nouveau 0000:01:00.0: DRM: failed to create encoder 0/1/0: -19
[    2.594367] nouveau 0000:01:00.0: DRM: TV-1 has no encoders, removing
[    2.885312] nouveau 0000:01:00.0: DRM: allocated 1920x1080 fb: 0x70000, bo (____ptrval____)
[    2.885998] fbcon: nouveaudrmfb (fb0) is primary device
[    3.013160] nouveau 0000:01:00.0: [drm] fb0: nouveaudrmfb frame buffer device
[    3.026888] [drm] Initialized nouveau 1.3.1 20120801 for 0000:01:00.0 on minor 0
[  139.063903] nouveau 0000:01:00.0: firmware: failed to load nouveau/nv84_xuc00f (-2)
[  139.063911] nouveau 0000:01:00.0: Direct firmware load for nouveau/nv84_xuc00f failed with error -2
[  139.063914] nouveau 0000:01:00.0: vp: unable to load firmware nouveau/nv84_xuc00f
[  139.063916] nouveau 0000:01:00.0: vp: init failed, -2
[  139.063937] nouveau 0000:01:00.0: firmware: failed to load nouveau/nv84_xuc103 (-2)
[  139.063940] nouveau 0000:01:00.0: Direct firmware load for nouveau/nv84_xuc103 failed with error -2
[  139.063941] nouveau 0000:01:00.0: bsp: unable to load firmware nouveau/nv84_xuc103
[  139.063943] nouveau 0000:01:00.0: bsp: init failed, -2
[ 5515.565573] nouveau 0000:01:00.0: firmware: failed to load nouveau/nv84_xuc00f (-2)
[ 5515.565581] nouveau 0000:01:00.0: Direct firmware load for nouveau/nv84_xuc00f failed with error -2
[ 5515.565586] nouveau 0000:01:00.0: vp: unable to load firmware nouveau/nv84_xuc00f
[ 5515.565588] nouveau 0000:01:00.0: vp: init failed, -2
[ 5515.565611] nouveau 0000:01:00.0: firmware: failed to load nouveau/nv84_xuc103 (-2)
[ 5515.565613] nouveau 0000:01:00.0: Direct firmware load for nouveau/nv84_xuc103 failed with error -2
[ 5515.565615] nouveau 0000:01:00.0: bsp: unable to load firmware nouveau/nv84_xuc103
[ 5515.565616] nouveau 0000:01:00.0: bsp: init failed, -2
[10704.185700] nouveau 0000:01:00.0: firmware: failed to load nouveau/nv84_xuc00f (-2)
[10704.185706] nouveau 0000:01:00.0: Direct firmware load for nouveau/nv84_xuc00f failed with error -2
[10704.185710] nouveau 0000:01:00.0: vp: unable to load firmware nouveau/nv84_xuc00f
[10704.185711] nouveau 0000:01:00.0: vp: init failed, -2
[10704.185738] nouveau 0000:01:00.0: firmware: failed to load nouveau/nv84_xuc103 (-2)
[10704.185740] nouveau 0000:01:00.0: Direct firmware load for nouveau/nv84_xuc103 failed with error -2
[10704.185742] nouveau 0000:01:00.0: bsp: unable to load firmware nouveau/nv84_xuc103
[10704.185743] nouveau 0000:01:00.0: bsp: init failed, -2
[10704.778476] nouveau 0000:01:00.0: firmware: failed to load nouveau/nv84_xuc00f (-2)
[10704.778483] nouveau 0000:01:00.0: Direct firmware load for nouveau/nv84_xuc00f failed with error -2
[10704.778486] nouveau 0000:01:00.0: vp: unable to load firmware nouveau/nv84_xuc00f
[10704.778488] nouveau 0000:01:00.0: vp: init failed, -2
[10704.778514] nouveau 0000:01:00.0: firmware: failed to load nouveau/nv84_xuc103 (-2)
[10704.778526] nouveau 0000:01:00.0: Direct firmware load for nouveau/nv84_xuc103 failed with error -2
[10704.778528] nouveau 0000:01:00.0: bsp: unable to load firmware nouveau/nv84_xuc103
[10704.778529] nouveau 0000:01:00.0: bsp: init failed, -2
[12269.291672] nouveau 0000:01:00.0: firmware: failed to load nouveau/nv84_xuc00f (-2)
[12269.291679] nouveau 0000:01:00.0: Direct firmware load for nouveau/nv84_xuc00f failed with error -2
[12269.291683] nouveau 0000:01:00.0: vp: unable to load firmware nouveau/nv84_xuc00f
[12269.291690] nouveau 0000:01:00.0: vp: init failed, -2
[12269.291732] nouveau 0000:01:00.0: firmware: failed to load nouveau/nv84_xuc103 (-2)
[12269.291735] nouveau 0000:01:00.0: Direct firmware load for nouveau/nv84_xuc103 failed with error -2
[12269.291736] nouveau 0000:01:00.0: bsp: unable to load firmware nouveau/nv84_xuc103
[12269.291738] nouveau 0000:01:00.0: bsp: init failed, -2

It was clean install. I did not install nVidia proprietary drivers.

  • /etc/X11/xorg.conf file. I do not have this file.
  • In the /etc/X11/xorg.conf.d/ directory I have 00-keyboard.conf file.

  • etc/modules - I do not have this directory
  • /etc/modprobe.d/*  - There are files: amd64-microcode-blacklist.conf, dkms.conf, droidcam.conf, etc-modules-parameter.conf and intel-microcode-blacklist.conf.
  • /etc/modules-load.d/*- There are files: cups-filter.conf, droidcam.conf and modules.conf
  • /etc/nvidia/* -  I do not have this directory
« Last Edit: March 19, 2021, 11:50:48 am by rektal »

Offline MoroS

  • Sr. Member
  • ****
  • Posts: 290
  • Karma: 0
  • Problem solver ;)
Re: Suspend is not working
« Reply #12 on: March 19, 2021, 08:13:18 pm »
I've managed to locate the firmware needed for Nouveau to function: https://al1.seblu.net/seblu/x86_64/nouveau-fw-325.15-1-any.pkg.tar.xz

You'll need to extract the contents to the main dir ("/"):
Code: [Select]
sudo tar --wildcards -C / -xv ./nouveau-fw-325.15-1-any.pkg.tar.xz usr/lib/firmware/nouveau/*
This command will:
- extract the contents of the archive (-xv)
- extract only the firmware files ("--wildcards" and "usr/lib/firmware/nouveau/*"), bypassing Arch's package info (it's an Arch-based package)
- extract them to the main directory while preserving the directory structure ("-C /"; putting them in the /usr/lib/firmware/nouveau directory, where they should be).

Then try restarting the system. This should load the firmware files. Check the "sudo dmesg | grep nouveau" command for the output. There shouldn't be any errors. If that's the case try suspending the system and see if this helped.
There's no such thing as "impossible". :)

Offline rektal

  • Newbie
  • *
  • Posts: 38
  • Karma: 0
Re: Suspend is not working
« Reply #13 on: March 19, 2021, 10:21:30 pm »
I have got an error. I cannot do it.
Code: [Select]
tar: Denied reading archive contents from terminal (missing -f option?)
tar: Error is not recoverable: exiting now

Offline MoroS

  • Sr. Member
  • ****
  • Posts: 290
  • Karma: 0
  • Problem solver ;)
Re: Suspend is not working
« Reply #14 on: March 19, 2021, 11:29:38 pm »
Oh boy... Sorry, I was cleaning up the command and removed the "f" (file) instead of "v" (verbose). Here's the command as it should be:
Code: [Select]
sudo tar --wildcards -C / -xf ./nouveau-fw-325.15-1-any.pkg.tar.xz usr/lib/firmware/nouveau/*
There's no such thing as "impossible". :)