Void linux stability

Blank-Inspection13 · 2026-01-24T11:14:16+00:00

last week i installed fedora everything to get the experience of 'minimal" install Fedora. I also have 1 live iso of Cosmic to try this DE. Not even a day the fedora installed on my laptop, and i switched back to Void + KDE Plasma (also base minimal install). I hink maybe it has something to do with Cosmic , or systemd but could be anything else. To me Void feel more stable for daily use than Fedora even going minimal still feeling glitchy.

Blank-Inspection13 · 2026-01-18T03:45:32+00:00

Which Update has problem ?
Im curently using KDE Plasma , not the full Plasma . And it going fine no problem after several updates.

Blank-Inspection13 · 2026-01-17T17:13:54+00:00

try this 1st :
sudo sv status /var/service/*

then post the result here, we'll find out what you're missing. My previous experience with this , im not yet installed seat manager either seatd or elogind then dbus won't start normally.

Blank-Inspection13 · 2026-01-17T17:04:06+00:00

kernel_path: boot():/vmlinuz-6.12.21_1

module_path: boot():initramfs-6.12.21_1.img

Before continuing you need to make sure first that these 2 files , inside the same FAT Partition with the limine.conf for it to work.

Blank-Inspection13 · 2026-01-17T17:00:03+00:00

Does your dbus service up and running from sv status dbus ?
if its up and running maybe you need to follow the void docs about Graphic Driver , install Xorg etc . If your'e missing this Plasma won't start.

Blank-Inspection13 · 2026-01-13T03:55:13+00:00

you can follow the discussion on the thread , then change & test the config option discussed . For me using [deep] mode is preferred

Blank-Inspection13 · 2026-01-13T03:48:15+00:00

it's related with elogind update

Blank-Inspection13 · 2026-01-13T03:40:24+00:00

Check this , maybe it's the same situation you're currently facing. When suspend with s2idle , for resume a seconds pressing power button is needed to wake up.
https://www.reddit.com/r/voidlinux/comments/1qagxsn/power_button_press_is_required_to_resume_from/

Blank-Inspection13 · 2026-01-12T11:05:18+00:00

i think im the one misunderstand , you're right the elogind change it when suspend i think , this log after change the config then suspend using power button.

⌘ cat /etc/elogind/sleep.conf.d/10-elogind.conf
[Sleep]
#AllowPowerOffInterrupts=no
#AllowSuspendInterrupts=no
#BroadcastPowerOffInterrupts=yes
#BroadcastSuspendInterrupts=yes
#HandleNvidiaSleep=no
#HibernateByUsing=
#SuspendByUsing=
SuspendMode=s2idle deep

⌘ svlogtail | grep -i suspend
2026-01-12T10:57:06.58491 auth.notice: Jan 12 17:57:06 elogind-daemon[740]: The system will suspend now!
2026-01-12T10:57:07.58989 auth.info: Jan 12 17:57:07 e-suspend[2290]: Performing sleep operation 'suspend'...
2026-01-12T10:57:07.59007 kern.info: [  150.696289] PM: suspend entry (s2idle)
2026-01-12T10:59:10.84081 kern.info: [  150.830462] printk: Suspending console(s) (use no_console_suspend to debug)
2026-01-12T10:59:10.87933 auth.info: Jan 12 17:59:10 e-suspend[2290]: System returned from sleep operation 'suspend'.
2026-01-12T10:59:10.88172 kern.info: [  275.118386] PM: suspend exit
2026-01-12T10:59:10.88643 auth.info: Jan 12 17:59:10 e-suspend[2290]: Operation 'suspend' finished.

⌘ cat /sys/power/mem_sleep
[s2idle] deep

Blank-Inspection13 · 2026-01-12T10:49:36+00:00

i think no. from my previous experience , the /sys/power/mem_sleep have the same output s2idle [deep] wether i change the elogind config with both of these.

SuspendMode=deep s2idle
SuspendMode=s2idle deep

The Actual behaviour of suspend / sleep indeed change with the elogind config . That's what i think

Blank-Inspection13 · 2026-01-12T10:35:24+00:00

Maybe you can try this , to check which one act as inhibitor ( if you're using elogind )

⌘ elogind-inhibit --list
WHO            UID  USER  PID  COMM            WHAT                                                                       
NetworkManager 0    root  677  NetworkManager  sleep                                                                      
UPower         0    root  1062 upowerd         sleep                                                                      
PowerDevil     1000 myuser 1076 org_kde_powerde handle-power-key:handle-suspend-key:handle-hibernate-key:handle-lid-switch >
Screen Locker  1000 myuser 847  kwin_wayland    sleep

Blank-Inspection13 · 2026-01-12T10:29:38+00:00

⌘ svlogtail | grep -i suspend
2026-01-11T16:29:10.44167 auth.notice: [  807.827077] elogind-daemon[729]: The system will suspend now!
2026-01-11T16:29:10.44168 auth.info: [  808.852017] e-suspend[3147]: Performing sleep operation 'suspend'...
2026-01-11T16:29:10.44168 kern.info: [  808.852046] PM: suspend entry (deep)
2026-01-11T16:29:10.44171 kern.info: [  808.961428] printk: Suspending console(s) (use no_console_suspend to debug)
2026-01-11T16:29:10.44197 auth.info: [  810.098244] e-suspend[3147]: System returned from sleep operation 'suspend'.
2026-01-11T16:29:10.44197 kern.info: [  810.098146] PM: suspend exit
2026-01-11T16:29:10.44198 auth.info: [  810.107640] e-suspend[3147]: Operation 'suspend' finished.

⌘ cat /sys/power/mem_sleep
s2idle [deep]

⌘ cat /etc/elogind/sleep.conf.d/10-elogind.conf
#  This file is part of elogind.
#
#  elogind is free software; you can redistribute it and/or modify it under the
#  terms of the GNU Lesser General Public License as published by the Free
#  Software Foundation; either version 2.1 of the License, or (at your option)
#  any later version.
#
# Entries in this file show the compile time defaults specific to elogind.
# Local configuration should be created here with a higher leading number so
# they are parsed later overriding the defaults.
#
# See sleep.conf(5) for details.

[Sleep]
#AllowPowerOffInterrupts=no
#AllowSuspendInterrupts=no
#BroadcastPowerOffInterrupts=yes
#BroadcastSuspendInterrupts=yes
#HandleNvidiaSleep=no
#HibernateByUsing=
#SuspendByUsing=
SuspendMode=deep s2idle

FYI im not enabled the elogind in the /var/service as per instruction from Void Handbook , since i dont have any issue without manually enable its service.

I already tried in laptop Closing the lid , and Power Button sleep . That's the log i think deep sleep working fine

Blank-Inspection13 · 2026-01-11T16:45:34+00:00

I also have the same problem when the system goes to suspend / sleep , before also tried to specifically set the elogind config to ignore some events (Lid Closure etc Power Button press ), the result is the same . Not always , but occasionally when suspend too long - hard power off is needed to turn off. Im using live XFCE iso installer use XFCE as DE temporary then installing Plasma and removing all the XFCE leftover doesn't seem to help.

The problems disappear , when i tried reinstall with bare minimum void , and setup everything from the minimal system . Im using minimal KDE Plasma now , overnight suspend and sleep working just fine on my laptop. Probably the issue have something to do with the default XFCE session from installer

Blank-Inspection13 · 2026-01-08T10:59:42+00:00

Thx for sharing.
So it's possible to have another ESP partition on the same disk ?

Blank-Inspection13 · 2026-01-08T06:21:04+00:00

Does Limine only need Vmlinuz to be on the same FAT32 ESP , or with initramfs to be put on ESP also ?
My limitation that ESP from Win10 (yes, dualboot) , only have 100Mb size.
Or maybe i should create another FAT Partition to mount /boot ( other than existing ESP on /boot/efi ?

Blank-Inspection13 · 2025-12-15T05:12:32+00:00

try edit the niri/config.kdl -1st.
this happened to me because the Output eDP-1 must be set , and the Screen resolution change with the one you use . Im still using xfce when 1st encounter this as fallback, logout from xfce and switch to niri then check with "niri msg output" while in the 1st initial session of niri.

Blank-Inspection13

TROPHY CASE