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?
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
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:bash: inxi: command not found
Hibernate is not working too.
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.
Depending on your install inxi might need to be installed first:
apt install inxi
What you can also check is what happens when you try to trigger suspend from the terminal:
systemctl suspend (might need root privileges).
You might also check the output of the dmesg command for any errors, warnings, etc.
Thank you.
inxi -br gives me this
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
[ 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
I did systemctl suspend in terminal but nothing has changed.
I hear my fans are still running.
Quote from: rektal 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.
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?
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?
These are all errors or warnings in dmesg. Fonts are white bolded or red.
[ 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
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:
dmesg | grep nouveauso 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 is an output:
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
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 ("/"):
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.
I have got an error. I cannot do it.
tar: Denied reading archive contents from terminal (missing -f option?)
tar: Error is not recoverable: exiting now
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:
sudo tar --wildcards -C / -xf ./nouveau-fw-325.15-1-any.pkg.tar.xz usr/lib/firmware/nouveau/*
OK. I will try.
This is the output of this command in Tumbleweed:
[ 3.901483] fb0: switching to nouveaufb from VESA VGA
[ 3.902082] nouveau 0000:01:00.0: vgaarb: deactivate vga console
[ 3.902175] nouveau 0000:01:00.0: NVIDIA G94 (094100a1)
[ 4.045166] nouveau 0000:01:00.0: bios: version 62.94.11.00.03
[ 4.065511] nouveau 0000:01:00.0: fb: 512 MiB GDDR3
[ 4.134439] nouveau 0000:01:00.0: DRM: VRAM: 512 MiB
[ 4.134441] nouveau 0000:01:00.0: DRM: GART: 1048576 MiB
[ 4.134444] nouveau 0000:01:00.0: DRM: TMDS table version 2.0
[ 4.134447] nouveau 0000:01:00.0: DRM: DCB version 4.0
[ 4.134449] nouveau 0000:01:00.0: DRM: DCB outp 00: 02000300 00000028
[ 4.134451] nouveau 0000:01:00.0: DRM: DCB outp 01: 01000302 00020030
[ 4.134453] nouveau 0000:01:00.0: DRM: DCB outp 02: 04011310 00000028
[ 4.134455] nouveau 0000:01:00.0: DRM: DCB outp 03: 02011312 00020030
[ 4.134457] nouveau 0000:01:00.0: DRM: DCB outp 04: 010223f1 00c0c080
[ 4.134460] nouveau 0000:01:00.0: DRM: DCB conn 00: 00001030
[ 4.134462] nouveau 0000:01:00.0: DRM: DCB conn 01: 00002130
[ 4.134463] nouveau 0000:01:00.0: DRM: DCB conn 02: 00000210
[ 4.134465] nouveau 0000:01:00.0: DRM: DCB conn 03: 00000211
[ 4.134467] nouveau 0000:01:00.0: DRM: DCB conn 04: 00000213
[ 4.136029] nouveau 0000:01:00.0: DRM: MM: using CRYPT for buffer copies
[ 4.136600] nouveau 0000:01:00.0: DRM: failed to create encoder 0/1/0: -19
[ 4.136603] nouveau 0000:01:00.0: DRM: TV-1 has no encoders, removing
[ 4.427268] nouveau 0000:01:00.0: DRM: allocated 1920x1080 fb: 0x70000, bo 00000000c884864e
[ 4.428227] fbcon: nouveaudrmfb (fb0) is primary device
[ 4.519972] nouveau 0000:01:00.0: [drm] fb0: nouveaudrmfb frame buffer device
[ 4.554720] [drm] Initialized nouveau 1.3.1 20120801 for 0000:01:00.0 on minor 0
This is the output in Sparky
[ 2.350783] nouveau 0000:01:00.0: vgaarb: deactivate vga console
[ 2.351595] nouveau 0000:01:00.0: NVIDIA G94 (094100a1)
[ 2.464813] nouveau 0000:01:00.0: bios: version 62.94.11.00.03
[ 2.485105] nouveau 0000:01:00.0: fb: 512 MiB GDDR3
[ 2.553568] nouveau 0000:01:00.0: DRM: VRAM: 512 MiB
[ 2.553570] nouveau 0000:01:00.0: DRM: GART: 1048576 MiB
[ 2.553572] nouveau 0000:01:00.0: DRM: TMDS table version 2.0
[ 2.553573] nouveau 0000:01:00.0: DRM: DCB version 4.0
[ 2.553575] nouveau 0000:01:00.0: DRM: DCB outp 00: 02000300 00000028
[ 2.553577] nouveau 0000:01:00.0: DRM: DCB outp 01: 01000302 00020030
[ 2.553579] nouveau 0000:01:00.0: DRM: DCB outp 02: 04011310 00000028
[ 2.553580] nouveau 0000:01:00.0: DRM: DCB outp 03: 02011312 00020030
[ 2.553581] nouveau 0000:01:00.0: DRM: DCB outp 04: 010223f1 00c0c080
[ 2.553583] nouveau 0000:01:00.0: DRM: DCB conn 00: 00001030
[ 2.553584] nouveau 0000:01:00.0: DRM: DCB conn 01: 00002130
[ 2.553586] nouveau 0000:01:00.0: DRM: DCB conn 02: 00000210
[ 2.553587] nouveau 0000:01:00.0: DRM: DCB conn 03: 00000211
[ 2.553588] nouveau 0000:01:00.0: DRM: DCB conn 04: 00000213
[ 2.555184] nouveau 0000:01:00.0: DRM: MM: using CRYPT for buffer copies
[ 2.555770] nouveau 0000:01:00.0: DRM: failed to create encoder 0/1/0: -19
[ 2.555772] nouveau 0000:01:00.0: DRM: TV-1 has no encoders, removing
[ 2.846347] nouveau 0000:01:00.0: DRM: allocated 1920x1080 fb: 0x70000, bo (____ptrval____)
[ 2.847209] fbcon: nouveaudrmfb (fb0) is primary device
[ 2.940198] nouveau 0000:01:00.0: [drm] fb0: nouveaudrmfb frame buffer device
[ 2.974789] [drm] Initialized nouveau 1.3.1 20120801 for 0000:01:00.0 on minor 0
[ 109.950686] nouveau 0000:01:00.0: firmware: direct-loading firmware nouveau/nv84_xuc00f
[ 109.997952] nouveau 0000:01:00.0: firmware: direct-loading firmware nouveau/nv84_xuc103
There are no errors.
But unfortunately it didn't help with suspending. Screen went off, but only the fans keep running.[/code]
Ok, so it wasn't the lack of firmware (although the card should behave a bit better now).
One other thing we might try is adding the ACPI daemon to handle events:
sudo apt install acpid acpi-support
sudo systemctl status acpid
The last command should show acpid enabled and running. If not, then you need to do it manually:
sudo systemctl enable acpid
sudo systemctl start acpid
After that try suspending again.
systemctl status acpid gives me this
● acpid.service - ACPI event daemon
Loaded: loaded (/lib/systemd/system/acpid.service; disabled; vendor pr>
Active: active (running) since Sat 2021-03-20 11:34:40 CET; 2min 37s a>
TriggeredBy: ● acpid.path
● acpid.socket
Docs: man:acpid(8)
Main PID: 491 (acpid)
Tasks: 1 (limit: 9459)
Memory: 528.0K
CPU: 6ms
CGroup: /system.slice/acpid.service
└─491 /usr/sbin/acpid
Warning: some journal files were not opened due to insufficient permissions.
ACPI deamon is enabled and running.
I tried to suspend but with no result. Screen went off, but only the fans keep running.
When I was searching in the internet I have found this:
https://www.linuxquestions.org/questions/suse-opensuse-60/suspend-not-working-4175614923/https://forums.opensuse.org/showthread.php/534882-Hibernate-and-suspend-not-workinghttps://bugzilla.redhat.com/show_bug.cgi?id=832679Maybe it is kernel related.
On Tumbleweed I have 5.11.6 kernel and suspend is working.
MX LInux 19.3 has 5.8 kernel and suspend is working. This kernel is older than Sparky's kernel. They are Debian based distros.
It might me something in Debian Testing, which Sparky is based on. The default kernel in Sparky is that of Debian Testing (unless you're using stable). It's a bit hard to say, but I'm running out of ideas over here.
You might try using another kernel like Liquorix:
https://wiki.sparkylinux.org/doku.php/how_to_install_longterm_liquorix_kernelsIt's nicely optimized, for certain cases better than the stock Debian kernel.
You can install other kernels with APTus (as described in the link above at the bottom of the page).
Thank you for your help.
I installed newer kernel from default repo and it is 5.11.8-1 but it is no active.
Active kernel is still 5.10.0-4. How to change it?
This is inxi -br output:
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: 2000 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: 826.26 GiB (35.5%)
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: 179 Uptime: 3m Memory: 7.77 GiB used: 1.52 GiB (19.6%)
Shell: Bash inxi: 3.3.01
When I want to remove old kernel by APTus it shows me to remove 5.11.8-sparky-amd64. Active kernel is 5.10.0-4-amd64.
And I do not see the newest kernel in bootloader.
You can verify if the kernel is installed by running:
ls /boot/vmlinuz* -l
This should show you all installed kernels.
If the one you want is there, try updating your GRUB config and rebooting:
sudo update-grub2
It'll output all the kernels that are added. If the one you want is not first in the list, then it won't boot as default (the first one is the default, but you'll find others in the advanced options in the GRUB menu while booting).
ls /boot/vmlinuz* -l output:
-rw-r--r-- 1 root root 6809024 03-02 17:49 /boot/vmlinuz-5.10.0-4-amd64
-rw-r--r-- 1 root root 5389376 03-20 13:02 /boot/vmlinuz-5.11.8-sparky-amd64
I could not update grub
[sudo: update-grub2: command not found
Should I install grub2?
No, for the time being don't. Let's test is this works first.
When rebooting, when in GRUB you'll have the option of choosing "Advanced options for Sparky GNU/Linux". This will display a menu with other available kernels to boot. Try selecting the new kernel from there first and see if your system will suspend while running it.
I am very pleased with Sparky and I think it will be my default distro in the future. It is stable for me and updates go smooth.
A lack of suspend feature is only a little inconvenience.
I chose Advanced options for Sparky GNU/Linux but it is only one kernel 5.10.0-4-amd64.
In APTus there are options: Install Debian kernel or Install Sparky kernel. Maybe this are another sort of kernels?
In Synaptic i have installed packages like:Sparky GRUB Theme, GRUB Legacy , grub-common.
I think that default is installed older version of grub not grub2 on Sparky.
I did sudo update-grub instead
root@Sparky:/home/rektal# sudo update-grub
Searching for GRUB installation directory ... found: /boot/grub
WARNING: tempfile is deprecated; consider using mktemp instead.
Searching for default file ... found: /boot/grub/default
Testing for an existing GRUB menu.lst file ... found: /boot/grub/menu.lst
WARNING: tempfile is deprecated; consider using mktemp instead.
Searching for splash image ... none found, skipping ...
Found kernel: /boot/vmlinuz-5.11.8-sparky-amd64
Found kernel: /boot/vmlinuz-5.10.0-4-amd64
Updating /boot/grub/menu.lst ... done
But after reboot I do not see 5.11.8 kernel in advanced settings of bootloader.
That's because the advanced options only show kernels that don't boot by default. From the "update-grub" command I saw that 5.11.8 was first on the list, so now it's the default - no need to use the advanced options to boot. :)
So, now that you're booting 5.11, did you try suspending?
But uname -r output is:
uname -r
5.10.0-4-amd64
@rektal. Boot into Tumbleweed. Update bootlader from command line or yast and reboot. This time sparky kernel will be there.
Success!
I have updated grub in Tumbleweed.
Then reboot to Sparky. Now it is kernel 5.11.8. Thank you @lami07
After this and a new Sparky kernel 5.11.8, suspend is working again. Thank you @MoroS.
There is one problem. When I boot to Sparky there is no plymouth boot theme and I see console.
When I press F2 while booting I see grey screen with 3 white dots
Before that I had.Sparky Blue plymouth theme.
How to fix it?
So, it was a stock Debian kernel issue then. I wasn't rooting for that one, actually. ;)
I also kind of missed the fact, that you have multiple distros on a single machine and thought that you're booting M$ or Tumbleweed from live media (yeah, didn't occur to me, that practically no one suspends the machine while on a live distro ;) )., hence my confusion. Luckily @lami07 swooped in and saved the day (thanks!! :) ), as I was getting really confused. ;D
As for the GRUB theme, then this one will be a bit tricky to do. It was probably set up with Sparky's configuration (installer updated the GRUB config). Now, that you did an update from Tumbleweed, it might have used it's own configuration and theming in that place. It's only a hypothesis, as I never actually tried installing two different distros aside one another. What you would probably need to do is to update the GRUB config from Sparky's side again with the same tool that was used in Tumbleweed (I'm assuming it's GRUB2, which, as you mentioned, you don't have installed on Sparky - the initial configuration was made from the installer, which had that).
I strongly advice not to mess with grub configuration.
You are in a delicate situation where if you make small mistake and replace tumbleweed bootloader with sparkys you wont be able to boot tumbleweed any more. Why? Because opensuse strongly pushes btrfs file system. Their btrfs utils and grub config contains additional patches not found in debian/sparky. Debian grub can't property boot opensuse tumbleweed.
OK. I will not to mess with grub.
I will take advice from @lami07.
I will use Sparky as my default distro. Then I will replace Tumbleweed permanently.
Thank you @lami07 and @MoroS for help.
I really appreciate it.
Quote from: lami07 on March 21, 2021, 11:19:45 AM
I strongly advice not to mess with grub configuration.
You are in a delicate situation where if you make small mistake and replace tumbleweed bootloader with sparkys you wont be able to boot tumbleweed any more.
Then how did @rektal get a Sparky-themed GRUB menu in the first place (he lost it after running configuration updates from Tumbleweed)? It seems that at the very least the configuration from Sparky was applied (installer perhaps?) and he could still boot into Tumbleweed.
@rektal: Did the GRUB theme change (to Sparky's) when you installed Sparky?
It is a little complicated. I try to explain it.
I have got 3 disks.
sda - this is my first disk where I have got Tumbleweed and Windows10.
sdb - the second one is my disk to backup Windows files. It is parted to ntfs partiton and ext4 partition. This ext4 partition I am using to test linux distros f.e. Sparky. My previous distro was MX Linux 19.3.
sdc - it is external drive for backup.
My default disk to boot is sda disk. Grub2 shows me Tumbleweed, Sparky and Windows 10.
When I want to try another distro I disconnect my sda and sdc hard drives. Then I install distro on sdb drive.
Then I reconnect my sda and sdc drives and set sda drive as my first boot drive (Tumbleweed). In Tumbleweed I update grub2.
I can choose from boot menu Sparky linux. First time, before changing kernel from 5.10.04 to 5.11.8, my plymouth theme Sparky-Blue was working fine. After kernel upgrade it didn't work.
Why grub2 is not a default grub in Sparky?
Quote from: rektal on March 21, 2021, 05:13:17 PM
Why grub2 is not a default grub in Sparky?
It is. That should be the case for you also. You can try running, let's say this:
sudo grub-mkconfig --versionGRUB1 is out of usage for quite a few years now and I don't know if there's any distro out there that still uses it. Maybe some packages are not available on Sparky out-of-the-box, when you choose not to install GRUB during installation, but I didn't look at the installer's code or configuration too much (only when bugfixing it a while back) to confirm or deny it.
There is no GRUB1 in Sparky for years, all edytions use GRUB2.
I use on Tumbleweed btrfs file system. Is it possible to use it on Sparky?
Is it safe to use it on Debian system or should I stay on ext4 file system?
It's probably possible to use it in any modern Linux distro. Sparky doesn't have any customizations related to this, so you can follow the general Debian guidelines:
https://wiki.debian.org/Btrfs
Thank you. I will end this thread.
Thank you @pavroo and @MoroS.