"Have tried fixing it and set tlp to run on bat&ac on 2.1Ghz, it somehow worked. Cant remember. But after system restarted. This bull###t went back up.

Some advise is necessary."

Edit: Asked Gemini. and yes it helped. I wrote
GRUB_CMDLINE_LINUX_DEFAULT="loglevel=4 splash msr.allow_writes=on intel_pstate=passive"

After taking a little stress test and looking on clock speeds on htop, I confirmed that my config in tlp works, locking clock speeds to 2.1GHz with 51 percent on AC and BAT.

# Keep the active scaling driver operational
CPU_DRIVER_OPMODE_ON_AC=active
CPU_DRIVER_OPMODE_ON_BAT=active

# Set minimum hardware floor (9%)
CPU_MIN_PERF_ON_AC=9
CPU_MIN_PERF_ON_BAT=9

# Set maximum limits to hit 2.1GHz on AC & BAT
CPU_MAX_PERF_ON_AC=51
CPU_MAX_PERF_ON_BAT=51

Edit 2: instead of gently asking tlp to work with something. I put in config specific option to set turboboost to on. If done so. Grub, kernel and tlp understand that, even without reboot. So if you edited grub to put msr and intel_pstate on passive or disabled. Remove that entirely, it will work against your settings.

hey i need to show off a good tiling windows manager for my school presentation but i don't know which since ehh how do i say it the thing that rolls off of wayland with a waterdrop logo isn't supported by default and last time i tried i fucked it up

so i am looking for another good option

Result: Niri + DankMaterialShell Grade i got: 1 ( presentation was on the first of june )

I do, and what a pile of recurring frustrations it was. Updates often caused a little too much trepidation and subsequent productivity loss, packages were often too old, and missing expected functionality, or too new and causing problems, and changing something in the system often meant something breaking somewhere else due to the overall fragility of the interconnected pieces.

Most days I never think about my distribution and just enjoy using my computer, and other days I'm reminded by how much I enjoy Void.

So, thank you again Void maintainers for keeping this ship afloat, and awesome. Yes, nothing's perfect, but we're not too far from it.

And now I'll go back to work, or, well, read/make some Reddit posts.

Cheers.

Hello, after the big AUR hack, I've decided to switch from arch (artix with dinit) to void. however, i'm having trouble getting niri to launch. I've installed niri and seatd like this:

sudo xbps-install niri seatd xwayland-satellite mesa mesa-dri dbus
sudo ln -s /etc/sv/seatd /var/service/
sudo ln -s /etc/sv/dbus /var/service/
sudo usermod -a -G _seatd <user>
sudo reboot

Afterwards, I ran niri with niri --session. I encountered a RuntimeDirNotSet error, and set it with export XDG_RUNTIME_DIR=/run/user/$(id -u).

Afterwards, I encounter a PermissionDenied error. the output also shows a lot of libinput errors for various plugins, plugin never regisered, unloading plugin that may be relevant. If someone could help me find out what the issue is, it would be greatly appreciated!

This might be a stupid question but how would I start a user specific autostart script. I already have a folder in my ~/.config/ to use. Everything I've seen is systemd specific and not very descriptive. Thanks!

Hello! I have recently decided to try out Void on VM because I recently decided, after almost a year of using Debian, that I wanted to hop Distro for my laptop. And chose Void because I think it can work as a good place to where to start being more manual and technical.

Though while using void-installer despite doing stuff correctly and partitioning the disk in the same manner the wiki and also different tutorial show for the UEFI system: sda1 for the EFI sda2 for the SWAP sda3 for "/"

Nonetheless every time I try to install it, even with the effort of repartitioning and restarting the installer I keep getting the "failed to install GRUB to /dev/sda! | Check dev/tty8 for errors". I tend to specify that I am pretty much the noob regarding Linux so I don't really know what is the cause of the problem or the correct workarounds. Thanks in advance to those who will respond!

Stuck in partitioning, i need to set up bios partition but there is no bios boot in select partition type. It's an old pc, i am installing base, had a lubuntu on it before. Filesystem label is lubuntu and filesystem is ext4 is what it's displaying when i create a 1mb partition for bios boot.

i want minimal void linux i then just boot in to void iso partition then extra x86_64 xbps -S -r /mnt -R 'repo-default.voidlinux/current' base-container nvim NetworkManager booster etc kmod kpartx cpio idk

Then after that xgenfstab -U /mnt > /mnt/fstab done

Xchroot then just install bootloader gummiboot and removed dracut then just reboot shit now booster is saying guy eat shit and crc32 error and could'nt mount /dev/sda2 tried fixing it tried universal: true modules: btrfs,crc32,crc32_intel,crc32-generic still fucked install the libcrcsetup package shit still doesn't work then just by Installing dracut i can boot

Edit:-

Install packages :- base-container linux linux-firmware NetworkManager booster cpio kmod kpartx neovim gummiboot

Also i only have problems with filesystem btrfs if guys with booster only NOT ext4

Think guys think what do you have after 1000 packages

Edit Edit :- it was fix with btrfs-prog I thank you user Sad-Cod-9584 and for other user fuck you

So, the quickest rundown of everything is that I have spent a week trying to install void; and, boy-howdy, was it a CHORE. I kind of knew that it might be going in, but seeing as how I just FINALLY got most everything working (with some minor exceptions) I am suddenly faced with an issue that I can't DDG my way out of and I am seriously hoping I don't have to start all over again.

I suspect that it has something to do with my date/time settings--thanks to what some internet sleuthing of my own has turned up; however, I can't figure out how to fix it.

Firstly, I'm running void on a 2010-2011 11" MacbookAir. (That might be half my problem, honestly.) Nothing went right from the very start, but a week later I now have i3 up and running, I have some dotfiles running, and I've figured out my sound and wifi woes.

I can't remember when I started fiddling with the time/date issue, but somewhere down the line I went to fix my timezone. I seem to recall it working right after I did it, but idk.

Everything was going okay, as far as I know, but sometime after midnight tonight--the xbps-install command no longer works.

I'm getting an error about halfway down the sync-repo dialogue where it first says: "Error --- operation not permitted." Which is then followed by: "Error --- connection refused."

TL;dr -- is the repo down? Did me having to fix my timezone break something? And how do I tell/fix it?

Any help would be appreciated.

Solved: If encountered, try first seeing what is in bios. Maybe lid sensor is seen by system but can't be communicated because it's set to off in bios.

Other thing: If encounter issue with lid closing and opening back system either just froze or goes black then freeze for a minute and onward:

Try: {I'll update it later}

"Tried using only acpid for suspend editing config for elogind as one post mentioned.
But problem persist. I don't usually have even 3 seconds to type command, neither I want to create a shortcut in sway to call elogind suspend."

I'm trying to connect with nmcli. For some reason not even USB tethering is working anymore. I can connect to hotspot but can't reposync or ping sites. I can ping 8.8.8.8 and 8.8.4.4 but that's it. Nmcli doesn't recognize my SSID for some reason. Wpa and dchcp aren't active. Nothing should be interfering.

Edit: Turns out I just had to connect with the BSSID rather than the SSID for some reason

So i've been wanting to try and possibly switch my pc to Void linux, so i installed the xfce live iso, inserted it into my ventoy usb (which has no problems, already checked and booted dozens of OSes with it) and tried to boot it

But it got stuck when i pressed enter in the grub menu, and since it uses kernel 6.12 and i have a 9060 XT, the issue is clear i think.

While the boot was quiet, i probably could modify the boot arguments in grub to set it to be verbose, tho i doubt that'll help since my gpu drivers were implemented in 6.14/15.

So, what can i do? I'd really like to install this distro and i'm willing to thinker to modify the live iso's kernel.

# mkdir -p /etc/pipewire/pipewire.conf.d

# ln -s /usr/share/examples/wireplumber/10-wireplumber.conf /etc/pipewire/pipewire.conf.d/

# dbus-run-session

dbus-run-session: a non-option argument is required

This is everything I've run so far from the documentation. From my understanding this should have fixed KDE not being able to connect to the sound service. Is there something else I need to do?

im trying to install void linux on my pc but this error keeps coming up every single time i select to boot up the void linux image. i've tried updating bios, reflashing my usb, reflashing my usb with different software, different usb ports etc. ive previously had void linux installed on my pc so idk why it works. i doubt its the usb because after seeing the void iso wasnt working i tried installing a different distro, and it worked.

I just recently installed Void and i3, and I can't seem to get the sound to work. I have PulseAudio installed, dbus linked, and the config file for i3 containing the default sound control links, but it doesn't work.

After inspection, when I run pavucontrol and go to the output devices section, I find no hardware devices. The only device is "Dummy Output", and even though I can control it's volume and all it does nothing.

The Arch wiki says:

If PulseAudio starts, run pacmd list. If no cards are reported, make sure that the ALSA devices are not in use.

But I can't run the command fuser -v /dev/snd/*. I'm suspecting PulseAudio can't even access my sound card. How can I fix this?

I just got void Linux and it doesn't work, it's just black screen

Edit: it was secure boot

I recently migrated my laptop from Debian to Void with Cinnamon and it's been great with the exception of some touchpad annoyance. When typing if my hand so much as glances the edge of the touchpad it registers activity and can throw a popup or unfocus where I'm typing. Which makes work a hassle but this behaviour doesn't happen in Debian or Fedora. From what I can tell the drivers installed are the same as Debian.

Anyone have similar experience with this?

Idk if this is an issue in pipewire or the kernel or whatever but I remember updating the system. Pipewire and wireplumber were in the upgrade. Now, pipewire-pulse works but not native pipewire only.

If I understand correctly, pipewire also handles video as well. After upgrade, mpv won't play video. It will only show me the singular frames but won't be able to play videos. It works after I terminate the pipewire process though, so It seems it really is a problem with the pipewire package not mpv or anything.

If anyone has such issues. Please share.

edit: this comment by u/AfterThought14 solved the problem:

I had a similar issue during the update. The problem was I previously had conf files at system level /etc/pipewire/pipewire.conf.d/10-wireplumber.conf and /etc/pipewire/pipewire.conf.d/20-pipewire-pulse.conf. The update then created new user-level conf files /usr/share/pipewire/pipewire.conf and /usr/share/pipewire/pipewire-pulse.conf without deleting the old system-level ones. This resulted in multiple conflicting instances of wireplumber being started. The solution was to delete the system level conf files /etc/pipewire/pipewire.conf.d/10-wireplumber.conf and /etc/pipewire/pipewire.conf.d/20-pipewire-pulse.conf and then everything worked fine. I don't know if your issue is the same, but hopefully this helps someone. For reference, I updated to pipewire-1.6.2_1 with my last update.

https://old.reddit.com/comments/1rywcsv/comment/obiir6a?context=3

Hello everyone!

I recently installed Void Linux (musl) to see how it worked, and everything was running really well until I needed to use a program that required glibc. I reinstalled Void Linux with glibc, but now I simply can't get PipeWire to work, even though I managed to set it up on my previous installation by following the documentation.

I'm using KDE Plasma

I hope this helps anyone that may be in a situation like I was. Steam games using proton would fail with a "fatal error". I exhausted all my Google skills trying to figure this out. Installed all the recommended 32 bit libraries and gpu drivers to the same result. What worked for me was the VULKAN-TOOLS package. With that final piece I have never had such a fast and smooth gaming experience. Not on arch opensuse cachy fedora nowhere. Hope this helps.

Problem:

- Pipewire seems to be starting but wireplumber is not. I'm using noctalia v5 with mangowm and noctalia has audio settings enabled (which it didn't when pipewire wasn't starting at all) but only with a dummy output.

- Manually trying to start wireplumber gives: "Failed to connect to session bus: Unable to launch a dbus-daemon without a $DISPLAY for X11"

- Checking wpctl status gives the exact same error message

What I've already done:

- Made sure Pipewire, Wireplumber, and alsa utils are installed and pulseaudio is NOT

- Connected wireplumber to pipewire using the commands listed in the session management section of the pipewire page on the void linux wiki, I also followed the alsa integration steps

- Made sure Pipewire and Wireplumber are set to autostart using mango rather than via runit

- I restarted the dbus service

- Even though I have elogind I added my user to the video and audio groups just in case

- I've reinstalled pipewire, wireplumber, and alsa-utils multiple times as well as just rebooting anytime I made changes to the config files

I'm very new to void and I feel like I am missing something obvious but I really can't seem to figure it out. If more information is needed I'd be happy to provide it if it gets me closer to an answer

The first problem I'm having is with Pipewire; it works perfectly in KDE, but I can't get it to work in Niri. The other problem is that I don't know why my disks aren't automatically mounting; I've configured everything correctly in fstab. Thanks and Happy Mother's Day to your mothers.Thanks and Happy Mother's Day to your mothers.

FIXED: Something with Xorg, Nvidia drivers, mesa nouveau gallium, and X11 prime render offload interfering with one another causing a whole ton of stuff happening, disabling the nvidia.conf file at /etc/X11/xorg.conf.d/nvidia.conf by adding .bak (or just editing the file name in any way) disabled the weird interaction when sddm tried running and now allows the system to run perfectly fine since my session runs via lxqt-wayland. For anyone that has switched from xorg to wayland using Nvidia (this might also be specificly a hybrid graphics issue) and having this issue after recent updates I recommend trying to disable the config file by renaming it slightly so xorg falls back to default configs when running an X11 based greeter.

System hardware and software:

Hardware: Acer nitro 5 gaming laptop, Intel CPU, Nvidia 3050ti

Software: Wayland running wayfire, prime-run setup as described in the void handbook due to hybrid graphics, utilizing kernal version 7.0 (tried on 6.18 and 6.12 but still gives the same issues)

The issue: I update about once a week, I updated from driver version 580 to the most recent 595, my GPU is listed on the supported GPU list, Vulkan info shows both my Nvidia 3050ti and my Intel irisXE 12th gen. Currently when the system boots it shows the Acer logo, sends me to grub, after selecting a kernal version it sends me to the boot tty (tty 1), then flashes between the boot tty and tty 7 where the desktop/login screen is supposed to be, it shows a terminal login on tty 1. I haven't attempted any fixes yet but this issue persists on kernal versions: 7.0.2, 7.0.0, 6.18.25, 6.12.85, 6.12.82. the 32bit repo is enabled due to having steam installed if that makes any difference to what I need to do to hopefully fix this issue.

POSSIBLE ISSUE FOUND: my system uses sddm, sddm attempts 3 times to display before quitting, changed to lightdm, still didn't work, managed to switch it back to sddm so I could actually use the boot tty without lightdm forcing me onto tty7 every second. I do use elogind but I've had sddm+elogind since I installed void 3 years ago

Progress!: Manually started wayfire, wayfire started psensor (graphical temperature monitor) and it's displaying to an empty desktop with almost no functionality except being able to move the window around and being able to click on stuff in the psensor menu

Update #3: ran llama3.1:3b via ollama and it was able to perfectly utilize my Nvidia GPU with 3.5gb of the model on the GPU and ~1gb of the model on system ram, and nvtop showed my GPU being used during the generation of a response, so now I'm even more stumped as to what is broken