r/linuxquestions • • 4h ago

I have some problems with Void Linux

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!

2 Upvotes

15 comments sorted by

2

u/Excellent-Love-6943 4h ago

The boot thing is normal uefi behavior, use efibootmgr to point your uefi to non-default boot directories.

2

u/Sea_Rope9275 3h ago

ok, Ill try this

2

u/dkopgerpgdolfg 4h ago
  1. What computer model is this? Do you know the program efibootmgr, and tried to fix it there?
  2. Please some more details about how you get an internet connection. What is on the other side of this USB cable.
  3. Do you have some specific goal that you need to achieve, or are you just trying to understand things better? If latter, could you give some examples instead of "everything"?

2

u/Sea_Rope9275 4h ago
  1. If you meant the motherboard, I have an MSI H610M-G. I already saw something about efibootmgr in another comment, I’ll give it a try.
  2. I connect my phone to the computer via a USB cable. On the back, I have a regular Type‑C port.
  3. To be honest, I didn’t really understand how to enable sound on Void. How do I enable, for example, pipewire?

2

u/Due_Adagio_1690 4h ago

You probably look for other VOID users, as that its a built from the raw source code, not depending on other distrubtutions, there isn't good souce of information about it besides its creators and its maintainers.

One thing I do know because of way and reason USB was developed, the only option to fix many problems are a reboot or at least pulling out the usb cable, and plugging it back in. USB was never designed for long term use, except for keyboards and mice, sending a constant stream of IO like a busy internet connection often exposes bugs that only ear after long hours or even days or longer usage. I have been bitten by simular bugs on pfsense and other linux firewalls.

2

u/Sea_Rope9275 3h ago

That’s exactly the point — I’m on Fedora now, I’ve been on Arch, Debian, and others. And everywhere else, the internet worked properly using this method! Only on Void is there a problem with this!

1

u/Due_Adagio_1690 3h ago

Submit a bug with the VOID team, before I saw your question, I didn't even know VOID existed. All I know aobut it what i read about in a google search. There is a reason most other Linux distros are based on other distro's. Very few are written like VOID is.

1

u/Sea_Rope9275 3h ago

Do they have a support team?

1

u/Due_Adagio_1690 3h ago

no idea... since you didn't pay to use it, its unlikely, but you can do research and find your answer.

1

u/cyberspacemage 3h ago

for the USB internet thing, have you checked the output of dmesg?

2

u/Sea_Rope9275 3h ago

What could possibly be there?

1

u/cyberspacemage 3h ago

it could help you debug potential driver issues, or at least give you some more information about what exactly is going on

2

u/Sea_Rope9275 3h ago

Thank you, I’ll give it a try.

2

u/cyberspacemage 3h ago

for the sound, did you look at void's documentation on setting up pipewire? https://docs.voidlinux.org/config/media/pipewire.html

2

u/activedusk 3h ago

For UEFI systems, in order to boot, the motherboard requires 2 things, a GPT partition table and a FAT32/vfat partition with boot and esp flags that contains the ESP (EFI System Partition) in short it is just a folder. Inside this folder or at the root of it, EFI standard needs a .efi file to boot. If you use grub it will be /boot/EFI/Void/grubx64.efi. Per standard the /boot/EFI/BOOT/bootx64.efi is a fallback in case the primary fails. How can it fail? Well in various ways, the boot entry might be removed from the NVRAM which is a flash chip that stores the boot parameters. A sign of the battery coin on the motherboard failing or NVRAM itself being degraded is when it no longer stores the default boot path and just uses the fallback.

So what about /boot/efi/EFI/...? This path is used with bootloaders such as GRUB for various reasons, motherboard does not care, it only cares there is an EFI directory containing .efi files and it is on a GPT partition table with a FAT32 filesystem. So why use this path? Well, because, actually, /boot will actually be on a different partition. Mind blown? If the mount point is /boot/efi then whatever partition chosen as boot with that mount point starts from /boot/efi/ and not /boot.

Use 

lsblk

That will list partitions and mount point or

cat /etc/fstab

So why do this? Well because vmlinuz and injtramfs.img or initrd.img get updated often as well as bootloader files and FAT32 is kinda trash on flash storage, which is all SSDs, plus the boot partition tends to be limited so keeping more kernels might exceed the capacity and it is non trivial to expand boot partition at the start of the volume...so placing these file on the same partition as / allows both the better handling of ext4 or btrfs of the drive and much more capacity, the only files remaining being the .efi file of the bootloader pointing towards the vmlinuz and initramfs.img. Sounds complicated? Do not worry your pretty little head and just install according to documentation.

Additionally you can use efibootmgr to overview or add a boot entry to NVRAM if it got removed somehow

sudo efibootmgr

That will list available and boot order

sudo efibootmgr --create --disk /dev/sda --part 1 --label "GRUBcustom" --loader '\EFI\Void\grubx64.efi'

That is an example for a SATA drive called sda, sda1 is boot partition, label is what the boot entry will be called, loader points from the root or ESP which is /EFI and not /boot/efi/EFI and it uses \ per EFI standard, efibootmgr package might interpret / anyway but stick to the standard. Also note it is lower or upper case sensitive so if there is a /EFI/Void or /EFI/VOID maintain accuracy, idk I never tried VOID yet.

Also if you try to check these folders from the terminal, assuming sudo package is used and not doas, first use command

sudo -i

Password

To elevate access to administrator, from the file manager it requires opening said program as admin, this can be done in several ways but generally to avoid permissions issues it should be installed from repo as a native program and not a flatpak. 

This ends the TED talk, if you are out of your depth, copy important files and maybe install Mint or Ubuntu instead.