Hey, can anyone guide me on this acp-pdm-mach error.

I'm on my third day on Void Linux, and I was testing video streaming on YouTube. This laptop has a low-power dual core AMD CPU, so it does struggle a bit with streaming video (I use a browser extension named enhanced-h264ify to block 60fps).

I noticed two things: First, there is a bit of audio "jitter," when starting a video, or skipping around in it. Second, the CPU is running 20 to even 30 degrees cooler than on Debian LXQt (under similar conditions). It briefly touched 106° just now. And I know the sensor/display isn't wrong, even by touch I can tell the difference. The CPU "percentage" and RAM usage are basically the same while streaming.

Partly I'm just surprised, partly I'm wondering if I just had left something undone over on Debian. Could I have achieved the same seemingly better CPU performance over there? I'm not sure what has made the difference.

Vague question, I know..

First time posting since I made a second reddit account. Anyway, I am trying to record my screen under niri & I get only black in the preview panel & output recordings. Am I missing something?

hi, i was reinstalling void on my system, and while i was verifying the image integrity it failed. on the official site they ask to not download it and notify them, but it doesn't say where, so i figured here would be ok enough. i'll paste here the extract of the session

 ## per instructions on https://docs.voidlinux.org/installation/index.html#verifying-images
## files are all downloaded from https://repo-default.voidlinux.org/live/current/

> minisign -V -p void-release-20250202.pub -x sha256sum.sig -m sha256sum.txt
Signature and comment signature verified
Trusted comment: This key is only valid for images with date 20250202.

## now i verify image integrity
> sha256 sha256sum.txt -c void-live-x86_64-musl-20250202-xfce.iso
SHA256 (sha256sum.txt) = c7f17b27b0045029154bd4e3b4b2d39cb8d8b6fc1546a899dc9cb6bf35a76683 [ Failed ] ## this failed

## checking manually
> sha256 void-live-x86_64-musl-20250202-xfce.iso
SHA256 (void-live-x86_64-musl-20250202-xfce.iso) = eaf73fabc4256af9f048dd440ae3b707776aebf601d282d2d66a26c50f2bc802

Hi y'all,

Im coming from arch and want to try out void and i would like to ask somethings

What exactly is the difference between musl amd gnu libc? Is it just systemd?

What are some quirks of void you encountered?

Why did you choose void, what makes it special?

Hola, espero estén bien, tengo Void con i3WM, pero desde hace dos días cuando lanzó Firefox desde todo tarda entre 10 a 30 segundos en aparecer. ¿Alguien sabe qué debo hacer?

I am wanting to switch over from Arch to Void but every time I try to boot, my computer gets stuck and doesn’t budge unless I turn it off. I had this same problem initially when booting from my install usb, but once I selected the version with the graphics disabled everything worked perfectly fine. Now that I’m actually trying to boot into the system I just installed, it completely freezes. Even when I try and boot into recovery mode, the same thing happens. Based on the fact that everything worked okay when I booted without graphics, I have a feeling that this is something related to incompatible graphics. I have scoured the documentation and cannot find any sort of solution. My GPU and CPU are both AMD btw.

Newbie here. When attempting to load into gnome, it fails because it tries to load something from systemd. Is there a way to make it not do that?

I looked through some posts, somebody mentioned that something needs to be configured (I don't even know what and it's never mentioned anywhere), but most people confirm that this should not happen.

This is what it says after $ exec gnome-session: gnome-session-binary[985]: WARNING: Failed to upload environment to systemd: GDBus.Error:org.freedesktop.DBus.ErrorNameHasNoOnwer: Name "org.freedesktop.systemd1" does not exist gnome-session-binary[985]: WARNING: Could not check if unit gnome-session-tty@gnome.target is active: GDBus.Error:org.freedesktop.DBus.ErrorNameHasNoOnwer: Name "org.freedesktop.systemd1" does not exist gnome-session-binary[985]: WARNING: Falling back to non-systemd startup procedure due to this error: GDBus.Error:org.freedesktop.DBus.ErrorNameHasNoOnwer: Name "org.freedesktop.systemd1" does not exist gnome-session-binary[985]: WARNING: Could not get session id for session. Check that logind is properly installed and pam_systemd is getting used at login. ** Message: couldn't access control socket: /run/user/1000/keyring/control: No such file or directory discover_other_daemon: 0** Message: couldn't access control socket: /run/user/1000/keyring/control: No such file or directory discover_other_daemon: 0discover_other_daemon: 1SSH_AUTO_SOCK=/run/user/1000/keyring/ssh /usr/bin/gnome-shell: /usr/lib/libstdc++.so.6: version `CXAABI_1.3.15` not found (required by /usr/lib/libicui18n.so.77) gnome-session-binary[985]: WARNING: App `org.gnome.Shell.desktop` exited with code 1 /usr/bin/gnome-shell: /usr/lib/libstdc++.so.6: version `CXAABI_1.3.15` not found (required by /usr/lib/libicui18n.so.77) gnome-session-binary[985]: WARNING: App `org.gnome.Shell.desktop` exited with code 1 gnome-session-binary[985]: WARNING: App `org.gnome.Shell.desktop` respawning too quickly gnome-session-binary[985]: CODE_FILE=../gnome-session/gsm-manager.c:CODE_LINE=283:on_required_app_failure: Unrecoverable failure in required component in required component org.gnome.Shell.des ** (gnome-session-failed:994): WARNING **: Cannot open display: (gsd-datemine: 1001): datemine-plugin-WARNING **: Unable to register client: GDBus.Error:org.freedesktop.DBus.Error.UnknownMethod: Object does not exist at path /org/gnome/SessionManager

After the above it returns to the login menu

Unfortunately it will take some time to provide the full log as I have to type it by hand on my phone, but I'll keep updating the post

Update: I got something to work when stopped dbus, elogind and gdm, and then started in this exact order: elogind, dbus, gdm. Though it immediately froze and deathscreened, and now it always does that on boot.

Hi everyone! I've been using Void for about a week now. I'm not a complete newb to Linux, but I'm also not advanced by any means. I basically wanted to use Void so that I could get a deeper understanding of the fundamentals, and it hasn't disappointed.

I'm using Niri and DMS. DMS usually wants elogind, but I'm trying to use turnstile with seatd. I have everything working normally here: pipewire works as a user service, but DMS only starts when I start it through the niri config. My issue is that I use a central repo for my dotfiles, and I symlink them to the appropriate locations in my filesystem because I have more than one computer and when I change one I want them to change everywhere (it's a git repo).

I use Fedora on my M1 MBA, and I also have NixOS on another computer, both of which use systemd. systemd can start DMS no problem. But with Void and turnstile I'm having some problems getting it to start dms for me.

I've tried RTFM, but I'm kind of at the point where it's like, I don't even know what I don't know, you know?

Am I spinning my wheels? Is this even possible with runit? Or have I reached a limitation?

Thanks!

Basically the title. I work with Zoom/Meet a lot. I recently installed Void. Zoom works fine. It seems only to be Chromium browsers that are crashing, and only with backgrounds. Meet/backgrounds works fine with Firefox. I could just use Firefox, but my laptop is a bit of a potato and the video calls seem to use fewer resources on chromium.

I've installed mesa-vaapi and enabled the env variable in the niri config.

Any thoughts on the matter? Thanks!

FYI: AMD 3250U CPU (VEGA 3)

EDIT: Actually, I'd forgotten to put the env variable in Niri's config. It seems to be working now.

Hey guys

I have installed void on a portable ssd with btrfs. I have bspwm running on it and it feels fien but then suddenly ut starts freling unresponsive and sluggish.

Is there something i am missing?

Hello everyone,

I'll be installing Void Linux in the next few days (I'm migrating from Arch).

On Arch, we have the AUR, which gives us access to almost any package imaginable. With Void, there are only about 2 to 5 specific packages I need that aren't in the official repositories, so I'm trying to figure out the best workaround.

I've seen people suggest xbps-src, but I really don't want to build from source. Compiling large applications like a web browser takes way too much time and system resources.

I also considered Flatpak since it's easy to use, but I'm not a fan of how it downloads a ton of bundled dependencies and runs the app in an isolated sandbox.

The last option I thought of was using the Nix package manager. Since it works outside of NixOS, I could use it to install the specific apps I need, such as:

• Brave (brave-origin)
• Waterfox
• Faugus Launcher (this is the most important one for me!)

The Nix repository is massive. My plan is to use the official Void repositories for all my core system packages and strictly use Nixpkgs for these few extra, unrelated applications.

What do you think? Is using Nix alongside Void a good approach for this, or is there a better option I should consider?

Thanks in advance!

The idea of trying out musl over glibc has intrigued me as of late. My only concern is that I play a lot of games. I play games mostly through Steam, but sometimes through Prism Launcher for Minecraft, and through emulators like Dolphin. So my question is, would switching to musl pose any issues when it comes to gaming?

Today I installed Void Linux via chroot and everything went well, but after a boot, my internet chip is having problems, it's not working even with Ethernet cable

My notebook is an Asus F16 core 5 + rtx4050

Installed Void (several months ago) on a 500GB drive without a separate home directory (3 partitions, boot, swap, root) and everything has been fine.

Recently cloned the drive to a 2TB drive and use the extra space as another partition (4 partitions now). Is there a way to use the new, 1.4TB partition as my home directory ? I currently just have it mounted as /mnt/data

I ran an xbps-install -Su recently and my desktop started launching to a black screen.
I tried a few things but haven't had any luck. Notably niri works when launching from tty so I think it has something to do with elogind or the system bus.

For context, I was using lightdm and elogind to start the sessions.
Since I've switched to using sddm, and noticed elogind-daemon is always running if installed. I don't think this was always the case cause the service in /var/service was failing to start cause of this.

What I've tried:

• Switching to sddm
• Switching to turnstile and seatd
• Switching to i3 (this was my desktop before, and it still works).
• Launching niri from tty works, although missing session bus and some other stuff.

EDIT:
I did get this error in .xsession-errors

xrdb: Can't open display ''
2026-09-29T02:10:43.673554Z  INFO niri: starting version 26.04 (unknown commit)
2026-09-29T02:10:43.694769Z DEBUG niri_config: loaded config from "/home/john/.config/niri/config.kdl"
2026-09-29T02:10:44.034984Z DEBUG niri::backend::tty: session is not active, starting libinput in paused state
2026-09-29T02:10:44.047289Z  INFO niri::backend::tty: using as the render node: "/dev/dri/renderD128"
2026-09-29T02:10:44.070189Z  INFO niri: listening on Wayland socket: wayland-1
2026-09-29T02:10:44.070199Z  INFO niri: IPC listening on: /run/user/1000/niri.wayland-1.3597.sock
2026-09-29T02:10:44.071372Z  INFO niri: listening on X11 socket: :2

lightdm contained this log:

[+209.25s] DEBUG: Continue authentication
[+209.26s] DEBUG: Session pid=3041: Authentication complete with return value 0: Success
[+209.26s] DEBUG: Authenticate result for user john: Success
[+209.26s] DEBUG: User john authorized
[+209.28s] DEBUG: Greeter requests session niri
[+209.28s] DEBUG: Seat seat0: Creating display server of type wayland
[+209.28s] DEBUG: Using VT 8
[+209.28s] DEBUG: Seat seat0: Display server ready, running session
[+209.28s] DEBUG: Registering session with bus path /org/freedesktop/DisplayManager/Session0
[+209.28s] DEBUG: Session pid=3041: Running command /etc/lightdm/Xsession /usr/bin/niri --session
[+209.28s] DEBUG: Creating shared data directory /var/lib/lightdm-data/john
[+209.28s] DEBUG: Session pid=3041: Logging to .xsession-errors
[+209.29s] DEBUG: Activating VT 8
[+209.59s] DEBUG: Seat seat0: Stopping greeter
[+209.59s] DEBUG: Terminating login1 session c3
[+209.59s] DEBUG: Session pid=3005: Sending SIGTERM
[+209.59s] DEBUG: Activating login1 session c4
[+209.59s] DEBUG: Seat seat0 changes active session to c4
[+209.59s] DEBUG: Session c4 is already active
[+209.60s] DEBUG: Greeter closed communication channel
[+209.60s] DEBUG: Session pid=3005: Exited with return value 0
[+209.60s] DEBUG: Seat seat0: Session stopped
[+209.60s] DEBUG: Seat seat0: Stopping display server, no sessions require it
[+209.60s] DEBUG: Sending signal 15 to process 2991
[+209.76s] DEBUG: Process 2991 exited with return value 0
[+209.76s] DEBUG: XServer 0: X server stopped
[+209.76s] DEBUG: Releasing VT 7
[+209.76s] DEBUG: XServer 0: Removing X server authority /var/run/lightdm/root/:0
[+209.76s] DEBUG: Seat seat0: Display server stopped

Ok, so first off: I am a total newb to Void Linux, and only through much finagling, some previous Arch experience, and the help of AI (I know... don't crucify me please) was I able to get it running. That said, I kinda knew that's what I was signing up for, and I like the end result. But I didn't go through all of that trouble just to make a cool rice (which I may still do at some point):

I have a couple of Voron 2.4 3D printers, these run on CB1 chips (https://global.bttwiki.com/CB1.html) with a customized version of Debian (https://github.com/bigtreetech/CB1/releases).

Now the question is: how feasible is it to run Void linux on this setup?

To clarify a few things, for my particular Voron build anyway, the CB1 slots directly into a Manta M8P V2 controller board, which has a slot for an SD card which to my understanding functions as the hard drive, and from my previous experience you flash the OS onto this SD card and simply... slot it in.

From my limited experience I can kind of identify at least some of the issues here:

1. What changes did they make to the custom debian? Do they matter? I don't know where to look on their github for that kind of information, and even if I did, I probably wouldn't understand it anyway.
2. The whole point of this is to install Klipper (https://www.klipper3d.org), which is the 3D printer firmware, plus some other utilities; this is often done using a utility called KIUAH (https://github.com/dw-0/kiauh) which is installed via git. I did check, and git is in the Void package repo, but I think that KIUAH assumes that you have Debian infrastructure (like systemd for instance). But in theory, I should be able to use git to directly get the programs without KIUAH?
3. Linking. The guide I used to install Void briefly mentioned this, but didn't really explain it much other than that its how you run things at boot up (like KDE Plasma and other utilities). Can some one explain this or link me where in the documentation this is explained? I figure I will need this to run Klipper + utilities at boot up.
4. I think I should use the aarch64 version of Void in this situation? I don't know much about these different versions...

Any help or insight on this would be greatly appreciated!

Also.. I'm not sure if this breaks rule 2 or not, if so sorry? I only mention 3rd party stuff due to how they may interact with Void, not because I need help with them independently.

I'm completely new to zram. I want to use zram on void. But only a few resources on how to do that. Only found posts recommend Zramen. So how is it going with Zramen? Is it still great for setting up zram? Anything I should care about?

I'm an avid user of REAPER and I would like for the application to be a part of the official Void Linux repository, just like it was in Arch Linux. I asked the creator of REAPER and they agreed. What's the process? I've got the package built and working locally.

EDIT: Here's the template file. Too lazy to raise a PR. xbps-src template

hello everyone
i'm an arch user and i love the last stuff to be on my system but i also want to try void linux
it lake a lot of software and not all of them are up to date i will use flatpak for the missing stuff and what about the last kernel the last drivers will it be good use for me or just stick with arch

I quite like Wayland's innovations and enjoy my Niri very much; clipboard persistence is a known problem: if you do Ctrl+C, close the source window, Ctrl+V -- it will paste nothing, because the clipboard is bound to the window. That's a known limitation of the protocol, and I expected that I would need to do some tweaking to make it work, but I actually can not do it at all.

The solutions I encountered are:

1. wl-clip-persist -- very buggy, at least with Niri. It breaks gedit selection (which is the best GUI text editor I know), firefox is able to copy only 50% of the time
2. Doing a custom solution on top of a complex clipboard manager like CopyQ. That looks like a terrible overkill that would bring a lot of painful debugging
3. A lot of suggestions like "do something else" -- install a thing that would have its own separate keyboard, keep history and paste through a picker; switch to KDE/gnome; my favorite is "persistent clipboard is against wayland philosophy => you should not want it", which is just disgusting

The problem seems quite simple: make clipboard act normally. There are a lot of people using wayland, everybody uses clipboard, somebody should know a normal solution, right?

O que vocês adaptaram do handbook para seu gosto pessoal?

Usam pacotes Nix?

I noticed WineD3D is failing to open OpenGL contexts in my Void Linux install when using the EGL backend:

0128:trace:wgl:display_funcs_init Initialized EGL library 0128:trace:wgl:X11DRV_OpenGLInit Using EGL OpenGL backend 0128:warn:wgl:init_egl_platform Failed to open EGL display for type 0x31d5, native display 0x555578a00be0 0128:warn:wgl:init_egl_devices Failed to query EGL display device (error 0x3008). 0128:err:wgl:egldrv_init_pixel_formats Failed to get any configs from eglChooseConfig 0128:err:wgl:internal_context_create Failed to create internal global context 0128:err:d3d:wined3d_caps_gl_ctx_create Failed to find a suitable pixel format. 0128:err:d3d:wined3d_adapter_gl_init Failed to get a GL context for adapter 0126AA18. wine: Unhandled page fault on read access to 00000000 at address 00401B99 (thread 0128), starting debugger...

If I use winetricks to switch to the GLX backend instead of EGL (useegl=n) it works.

I'm running kernel 6.18.53_1, NVIDIA proprietary drivers 595.99.02. Tried both Wine 11.18 and 11.1, same issue.

Could I be missing some 32-bit package? I have nvidia-libs and nvidia-libs-32bit.

Note: I need to run old DirectX 7 games so DXVK isn't an option.

Kernel: 6.18.53_1

Installer version: 580.178.04

Log:

make[4]: Target './' not remade because of errors.

make[3]: *** [/usr/src/kernel-headers-6.18.52_1/Makefile:2050: .] Error 2

make[3]: Target 'modules' not remade because of errors.

make[2]: *** [/usr/src/kernel-headers-6.18.52_1/Makefile:248: __sub-make] Error 2

make[2]: Target 'modules' not remade because of errors.

make[2]: Leaving directory '/tmp/makeself.ZPaW80Rf/NVIDIA-Linux-x86_64-580.178.04/kernel'

make[1]: *** [Makefile:248: __sub-make] Error 2

make[1]: Target 'modules' not remade because of errors.

make[1]: Leaving directory '/usr/src/kernel-headers-6.18.52_1'

make: *** [Makefile:115: modules] Error 2

-> Checking to see whether the nvidia kernel module was successfully built

executing: 'cd kernel; /usr/bin/make -k -j8 NV_EXCLUDE_KERNEL_MODULES="" SYSSRC="/lib/modules/6.18.52_1/build" SYSOUT="/lib/modules/6.18.52_1/build" NV_KERNEL_MODULES="nvidia"'...

make[1]: Entering directory '/usr/src/kernel-headers-6.18.52_1'

make[2]: Entering directory '/tmp/makeself.ZPaW80Rf/NVIDIA-Linux-x86_64-580.178.04/kernel'

CC [M] nvidia/nv-clk.o

nvidia/nv-clk.c:30:10: fatal error: soc/tegra/bpmp-abi.h: No such file or directory

30 | #include <soc/tegra/bpmp-abi.h>

| ^~~~~~~~~~~~~~~~~~~~~~

compilation terminated.

make[4]: *** [/usr/src/kernel-headers-6.18.52_1/scripts/Makefile.build:287: nvidia/nv-clk.o] Error 1

make[4]: Target './' not remade because of errors.

make[3]: *** [/usr/src/kernel-headers-6.18.52_1/Makefile:2050: .] Error 2

make[3]: Target 'modules' not remade because of errors.

make[2]: *** [/usr/src/kernel-headers-6.18.52_1/Makefile:248: __sub-make] Error 2

make[2]: Target 'modules' not remade because of errors.

make[2]: Leaving directory '/tmp/makeself.ZPaW80Rf/NVIDIA-Linux-x86_64-580.178.04/kernel'

make[1]: *** [Makefile:248: __sub-make] Error 2

make[1]: Target 'modules' not remade because of errors.

make[1]: Leaving directory '/usr/src/kernel-headers-6.18.52_1'

make: *** [Makefile:115: modules] Error 2

-> Error.

ERROR: An error occurred while performing the step: "Checking to see whether the nvidia kernel module was successfully built". See /var/log/nvidia-installer.log for details.

-> The command `cd kernel; /usr/bin/make -k -j8 NV_EXCLUDE_KERNEL_MODULES="" SYSSRC="/lib/modules/6.18.52_1/build" SYSOUT="/lib/modules/6.18.52_1/build" NV_KERNEL_MODULES="nvidia"` failed with the following output:

make[1]: Entering directory '/usr/src/kernel-headers-6.18.52_1'

make[2]: Entering directory '/tmp/makeself.ZPaW80Rf/NVIDIA-Linux-x86_64-580.178.04/kernel'

CC [M] nvidia/nv-clk.o

nvidia/nv-clk.c:30:10: fatal error: soc/tegra/bpmp-abi.h: No such file or directory

30 | #include <soc/tegra/bpmp-abi.h>

| ^~~~~~~~~~~~~~~~~~~~~~

compilation terminated.

make[4]: *** [/usr/src/kernel-headers-6.18.52_1/scripts/Makefile.build:287: nvidia/nv-clk.o] Error 1

make[4]: Target './' not remade because of errors.

make[3]: *** [/usr/src/kernel-headers-6.18.52_1/Makefile:2050: .] Error 2

make[3]: Target 'modules' not remade because of errors.

make[2]: *** [/usr/src/kernel-headers-6.18.52_1/Makefile:248: __sub-make] Error 2

make[2]: Target 'modules' not remade because of errors.

make[2]: Leaving directory '/tmp/makeself.ZPaW80Rf/NVIDIA-Linux-x86_64-580.178.04/kernel'

make[1]: *** [Makefile:248: __sub-make] Error 2

make[1]: Target 'modules' not remade because of errors.

make[1]: Leaving directory '/usr/src/kernel-headers-6.18.52_1'

make: *** [Makefile:115: modules] Error 2

ERROR: The nvidia kernel module was not created.

ERROR: Installation has failed. Please see the file '/var/log/nvidia-installer.log' for details. You may find suggestions on fixing installation problems in the README available on the Linux driver download page at www.nvidia.com.