r/voidlinux • • 4d ago

I have some problems

I have a couple of issues I’d like to look into in more detail.
First, there’s a very strange issue with the boot path: my motherboard reads the boot file only from the path /boot/efi/EFI/BOOT/bootx64.efi; it doesn’t read the file from the standard path /boor/efi/Void/BOOT (to be honest, I don’t remember the exact path).
The second problem is that I live in the Village, and I’m sharing the internet with my computer via a USB cable, and for some reason this causes problems on Void. At some point, the internet goes out and only comes back after a reboot!
And thirdly, help me with the sound settings! I didn’t understand anything there at all!

There’s also a problem with the greeter settings, but I think I’ve figured it out.
Thank you very much if you can help me figure out at least something!

7 Upvotes

9 comments sorted by

5

u/pantokratorthegreat 4d ago

First: it is not issue. If it works, it works. Doesn't matter what dir names

Second: try different network manager.

Third: just follow docs instruction for pipewire. Are well written. Then run command $ pipewire and it should works. Them add it to autostart for your DE or whatever you use.

1

u/Sea_Rope9275 4d ago

Ive tried both dhcpcd and Network Manager, the situation is the same…

1

u/Ok_Bus6714 4d ago

I reinstalled void linux yesterday and had basically the same network issue. After installing NetworkManager and activating it on runit I disabled dhcpcd, but forgot to disable wpa_supplicant. So if you're trying to use NetworkManager make sure you enable it correctly on runit and disable wpa_supplicant and dhcpcd.

1

u/Sea_Rope9275 2d ago

Well... how can I put it, I’ve used both dhcpcd and network manager, well, I’ll keep in mind that wpa needs to be disabled.

1

u/furryfixer 3d ago

Directory names MAY matter, and name of the .efi file definitely may matter. This used to be a big problem with whatever BIOS ASUS was using for their motherboards. The file had to be named "bootx64.efi", and I suspect with only the default naming of the path to it.

1

u/pantokratorthegreat 3d ago

I mean in his case. He should not be bothered that he has bootloader inside BOOT directory instead Void.

2

u/furryfixer 3d ago

I see how you interpreted this. The question is whether the "Void" subdirectory is on the host, or actually on the efi partition itself, and mounted to /boot/efi. I don't see how it could easily happen,but the directory structure on the efi partition could be "/Void/BOOT/bootx64.efi" instead of "/EFI/BOOT/bootx64.efi". This would be a problem, I think.

3

u/ruw0lv3 4d ago

The sound issues, enable systemwide for ease as documented here

Then if you are using a desktop environment such as KDE or Xfce4 you can setup pipewore to autostart when you login, check the settings panel for autostart

Locate the pipewire binary i think its under /usr/bin/pipewire but please check this

Then reboot or logout and login again and it should start working

I am unsure about the usb internet issues but gl

1

u/Sea_Rope9275 4d ago

Thanks, Ill try it!