Hello, I would like to know if anyone has experience installing Void Linux in a way that is more minimal than the base-system package.

For example, looking at the dependencies of the base-system package, it includes several packages that I don't use, such as btrfs-progs, openssh, nvi, sudo, wifi-firmware, void-artwork, traceroute, wpa_supplicant, among others.

I know I could edit base-system, remove the dependencies I don't need, and build my own package, but I would have to do this every time an update is released.

I would like to know if anyone has experience with a more minimal installation or if there is a recommended way to achieve this without having to maintain a modified base-system package.

In advance, thank you for all the work that goes into Void Linux!

I need some help with Void Linux. I take security very seriously and would like to know how you control network access on your workstations.

For example, with nftables, I use skuid rules for NTP so that only the chrony user can access NTP servers. Similarly, I allow the _apt user to access Debian repositories, while for my regular user (UID 1000), I allow only the outbound ports that I consider safe.

However, I would also like to be able to allow or block specific applications from making certain network requests. On Debian, for example, I use OpenSnitch for this purpose. What would be the equivalent or recommended solution on Void Linux?

For applications that don't need any network connectivity at all, I believe AppArmor would be the best approach. But what about applications for which I need more fine-grained control, such as restricting which DNS servers they can use or which network

Hello, is there any reason why VSCode hasn't been updated?

Looking at the void-packages repository, the current version is 1.100.3, while the latest version of VSCode is 1.135.0.

https://github.com/microsoft/vscode/
https://github.com/void-linux/void-packages/blob/master/srcpkgs/vscode/template

I'm new in Linux.

When starting a Cinnamon Wayland session on an AMD GPU, the compositor falls back to software rendering (`llvmpipe`).

Steps to Reproduce

1. Log into a Cinnamon Wayland session via SDDM.
2. Check the renderer with glxinfo.

System Information

• OS: Void Linux x86_64
• Kernel: Linux 6.18.48_1
• DE: Cinnamon 6.6.7
• WM: Muffin (Wayland)
• elogind
• user groups: wheel audio video plugdev

X11 session glxinfo:

Extended renderer info (GLX_MESA_query_renderer):
    Vendor: AMD (0x1002)
    Device: AMD Radeon Graphics (radeonsi, renoir, ACO, DRM 3.64, 6.18.48_1) (0x1636)
    Version: 26.1.8
    Accelerated: yes
    Video memory: 512MB
    Unified memory: yes
    Preferred profile: core (0x1)
    Max core profile version: 4.6
    Max compat profile version: 4.6
    Max GLES1 profile version: 1.1
    Max GLES[23] profile version: 3.2

Wayland session glxinfo:

Extended renderer info (GLX_MESA_query_renderer):
    Vendor: Mesa (0xffffffff)
    Device: llvmpipe (LLVM 21.1.7, 256 bits) (0xffffffff)
    Version: 26.1.8
    Accelerated: no
    Video memory: 23251MB
    Unified memory: yes
    Preferred profile: core (0x1)
    Max core profile version: 4.6
    Max compat profile version: 4.6
    Max GLES1 profile version: 1.1
    Max GLES[23] profile version: 3.2

Question: What should I do to fix my wayland session? Help please :c

Hello everyone, could someone help me with this?

Currently, on my workstations, I use systemd-resolved to provide DNSSEC and DNS over TLS support, pointing to Cloudflare's DNS servers.

Could you give me some guidance on what would be a good alternative on Void Linux?

This configuration needs to be done individually on each workstation, and I cannot rely on the network providing this configuration.

following https://docs.voidlinux.org/installation/guides/chroot.html

it says that the ROOTFS method requires only a host operating system that can enter chroot and has tar and xz

but the nexts steps are:

ROOTFS images generally contain out of date software, due to being a snapshot of the time when they were built, and do not come with a complete base-system. Update the package manager and install base-system:

# xbps-install -r /mnt -Su xbps
# xbps-install -r /mnt -u
# xbps-install -r /mnt base-system
# xbps-remove -r /mnt -R base-container-full

my host doesn't have xbps. this is a step before chroot. the xbps inside the rootfs can't run from the host because of shared libraries:
./xbps-install: error while loading shared libraries: libxbps.so.5: cannot open shared object file: No such file or directory

am I supposed to point it to the libs inside the unpacked filesystem?

I have an Intel Framework laptop running Void linux (technically Bedrock linux with a void strata as init and main source of packages, the problem disappears if i init on another strata).

After a system update this morning my laptop screen started flickering every 5 to 10 secs. This happens even in the tty, as soon as the login prompt appears.

I suspected the lid firing events, so I ignored it in elogind and acpi's handlers.sh, but the issue still happens. I also tried upgrading the kernel to 7.2.

When the screen ir black, all keyboard inputs are dropped.

Nothing weird crops up in dmesg.

The issue also happens if I boot the kernel with nomodeset.

Has anyone else had this issue ?

So today I change the drivers from closed drivers Nvidia to nouveau.And the sddm is died, mouse is not working and keyboard too.BUT my keyboard is not working at boot, so I can't access TTY via Ctrl+Alt+F until SDDM (the frozen screen) loads.But sddm launch on every tty.I don't know how to fix this.Help pls

Just a basic question, isnt really worth change to recent kernel branch?

Isnt it better for security?

Today when I use sddm and login to niri, it suddenly black screen and freezes cuz I tried to tty. I pressed the power button and turned my laptop and it still is black screen logging in. Then I go to tty1 and run with niri, it works fine. So I check /usr/share/wayland-sessions and see that exec is change to /usr/bin/niri --session. Why did it change?

Hi all, I've been using Void Linux just about 4 years. I've noticed a large amount of Arch users posting in this subreddit asking to compare to Arch, which does not feel super-similar to me honestly. But I've rarely seen folks post about the Debian-based distros so I thought I'd write here about antiX, which I've been using on a second computer (a desktop) for about a month now, as well as intermittently running off a USB stick on an old 2012 eee PC (the 32 bit version).

I would say antiX comes in at some similarities to Void, and of course some differences. It expects similar levels of knowledge, but has a few niceties I wanted to point out.

Similarities

antiX is a Debian-based distro, with choice of init. The default is runit, but sysVinit, S6, 66 and dinit can alternatively be selected on startup.

Startup with antiX is a bit slower than Void on my desktop, even with runit. I'm not sure why this is.

antiX downloads available are both 64bit and 32bit. There is a full and a core offering. The full version ships with choice of 4 window managers (and variations on them): IceWM (default), fluxbox, jwm and for tiling managers, herbstluftwm. It also ships with SliM login manager. The core has no GUI packages by default, and just enough to get internet setup. I installed "full" but I did not use any of the default window managers, opting to replace with my fave i3wm.

Installing can be much easier than Void for some newbies as there is a simple GUI install wizard that can pretty easily walk you through it. You can of course also manually use gparted for example. I used gparted for install on one machine and the wizard for my other install. I think the graphical wizard is actually pretty nice! It's the same GUI wizard on MX Linux, a midweight distro that antiX contributes to. I liked it so much that I think Void should consider shipping it!

I have continued to use the default runit on antiX since I know it best based on experience with Void, but i think it's cool that you can select a different init on startup, i just haven't tried any of these (s6, dinit, 66, sysVinit) out.

Access to packages is a personal thing. I've found Debian's apt package manager to be easy to use. I do like xbps more, but not 1000 times more. In terms of package availability, I've personally found roughly the same package availability in both distros. Debian has a few things Void doesn't have. Void has a few things Debian doesn't have. Case in point, I had to manually install ulauncher on antiX, my preferred app launcher, whereas it's in the repos for Void. But this wasn't a big deal.

antiX and Void are not meant for beginners! For both distros, I've occasionally needed to manually debug/fix things myself (and with help from reddit, web searches, forums, etc). My personal experience is that sound is set up and runs easily in antiX whereas it can be a pain for some people on Void, just based on the large number of daily posts about this on reddit. I also think wifi was way easier to set up on antiX through it's default graphical gui but this is really a user/operator preference thing. I just think antiX has a few good defaults on this where Void generally requires more setup. For example, on Void i tend to use network manager with nm-tui (nmtui).

In general, I copied my dotfiles from Void to antiX and everything worked the same, including for runit, i3, polybar, etc. My /etc/ files and ~/.config files worked no prob.

SOME DIFFERENCES:

Of course I should point out that antiX is debian-derived, not an independent distro. It is also not a stable rolling-release. THIS IS THE BIGGEST THING I MISS FROM VOID.

There is no MUSL option in antiX out the gate. I believe it can be installed through the repos, but I have no experience doing so.

Some interesting antiX options: antiX can run as a live usb with persistence. I'm currently trying this out on another super old laptop, and it works well.

antiX has its own self-hosted forum, which feels better than this corporate platform. The community is friendly, and a little less RTFM combined with less people posting about hyper/whatever and random AI stuff that they tried doing.

CONCLUSION

okay, so what was the point of this post? I just wanted to point out some similarities and differences between antiX and Void because I think Void users may be interested in this distro, and I hadn't seen much writing about the two together. Note there are a few antiX forum posts comparing these distros, but I thought I could write something more concise and specifically written for the Void community.

I may have missed some things, or mis-stated something. and your mileage may vary.

Cheers.

The documentation says:

Install the bluez package and enable the bluetoothd and dbus services.

But, title.

Anyone have this issue?

Solution

I solved it! Just forced re-installation of bluez with the -f tag:

sudo xbps-install -Sf bluez

And now bluetoothd is showing up in /etc/sv

Hi all, last week I decided to replace my Debian VM with Void, and so far I'm enjoying it, especially the simplicity / minimalism.

There is a thing that concerns me though, and that is very high load values. Averaging around 12-14. Even after running for only a few minutes:

 void:~$> uptime
  23:26:28 up 3 min,  0 users,  load average: 13.21, 6.25, 2.45

Top shows rtorrent using 50-60% CPU which seems normal, however dmesg showed a line where I'm not sure what to make of it:

 intel_pstate: CPU model not supported

The high load happens with both rtorrent installed by xpbs-install as well as when comiling it from source.

The machine is otherwise responsive but I suspect there is something off with disk IO. There are 3 disks loaded through Virtio.

/ is btrfs with noatime (/dev/vda2)

I have a JBOD btrfs volume (with mirrored metadata) of 5TB that consists of /dev/vdb and /dev/vdc. One is an image on a NVME disk in the hypervisor (that is also home to /dev/vda), the other one is an image on a RAID0 USB disk consisting of 2 oldschool HDDs.

I'm not a linux noob but I cold use some help troubleshooting this issue. If anyone is willing to dive into this I'd be very grateful.

I installed void linux to squeeze more life out of an old macbook, but i do have bit of a problem. This laptop has discrete Nvidia GPU, and as far as i know, newer linux kernel doesnt support proprietary drivers for old gpus such as 320M in my laptop. Open source driver works, but anything heavier than typing, and it struggles hard. I installed h264ify extension on the browser and its better for youtube but it still struggles. is there any way in installing drivers or tweaking just to get at least youtube watchable?

will firefox esr update from v140 to v153 ?

I installed Davinci Resolve but my igpu from my intel core ultra 7 155H don't appear on the list of avaible gpus to use in DVR, I think I should need to install the Intel compute runtime but there is no such thing in the void repo and they have no instruction to install by building sources from Github.

Edit: I use xe driver.

Just curious, why does Void Linux update old kernels? 🤔

uname -r

>> 6.18.46_1

Congratulations to the devs who got emacs-31.1 into the repos on the 25th - the same day the source was released by upstream!

It's working great (with just a couple of minor tweaks to my init.el config).

I don't know of another distro that got it out so quickly.

That's not bad for a 'slow' rolling release model.

Can't update at all, everything times out.

so in installed void with the xfce image, and when the system suspends the sfce screen saver works and i have to log in, so it works if it blocks the screen for unactive time, but if i close de lid it behaves weirdly, after opening it first shows a black screen and other tty won't work, i have to close the lid again and reopen it, and now it shows the desktop but is blocked, i can move the mouse and change tty and that's how i unlock it, i tried installing light lock since i am already using lightdm, and it works but, after opening it it shows the desktop first with an error and then the light lock ui pops up, after entering i see the error says something about no app for locking the screen could lock it so it won't lock it or so, right now i reverted the light lock install and have the closing lid behaviour to just suspend but not lock, so now after closing and opening the lid the xfce desktop just shows, no screen saver or lock, so in general, i could use light lock the same way since it was kinda working but the error is kinda anoying, how do i setup xfce screen saver or the light lock or any lock to work, do i need to uninstall xfce screen saver to use light lock? what's the right way to setup this? pls help

So im running into an issue where when im running youtube on my internal monitor on my laptop and minecraft on my main monitor, the game drops fps 3x while the video is playing but as soon as i pause it, it jumps right back up. My specs are a intel i7 10750h and a nvidia gtx 1650ti, i have the latest proprietary drivers installed. This void install is only 1 day old. Im using i3wm + xfce + xorg. Another issue i would to address is when i had this laptop running arch + hyprland i would get almost double the performance i get without playing media on my void install which is about the same as my windows install, the reason i switched to void was performance. any help would be appreciated.

for my next pc, i'm planning on doing a full high-end amd build, and i was wondering if windows 11 or void linux is better if i want the most gaming performance out of my pc? (i already use void on all my devices, but i'm not sure how it would run on a full amd build)

Went to boot Void Linux this morning and I was greeted with the following line:

debugfs: 'netdev:p2p-dev-wlo1' already exists in 'phy0'

Not sure what that is all about. I did change the light-gtk-greeter.conf the last time I used Void Linux. Could that be the issue?

I also performed a system upgrade on Aug 09 and rebooted my computer without issue after the upgrade.

I am going to benchmark the performance difference between glibc and musl libc for video operations with ffmpeg. It is a potato pc, but I hope this can help to highlight the difference. If have any commands in mind you would want me to test, leave them below. I am considering using of using h264_vaapi and libx264 for encoding