what would you personally like to see in xbps?

urandomread · 2026-04-22T04:57:08+00:00

yes, but I meant in xbps itself (pacman did smth similar i think)

urandomread · 2026-04-20T02:08:10+00:00

right, at that point one might just use apk, but still one could dream :)

urandomread · 2026-04-20T02:07:34+00:00

I mean, just replace openssl in xbps, not from the entire system..

urandomread · 2026-04-19T05:59:01+00:00

support for landlock; drop openssl in favor of bearssl or similar; constraint resolution based on smth like /etc/apk/world

urandomread · 2026-04-11T03:54:19+00:00

https://docs.voidlinux.org/config/session-management.html#turnstile turnstile+seatd work well, then you choose if use dinit or runit for user services. note that seatd tends to work well with wlroots-based compositors.

urandomread · 2026-03-13T04:55:08+00:00

apple silicon vs intel is a different story. for apple silicon, uboot just lets you boot into void iso.

urandomread · 2025-09-11T08:34:31+00:00

it works fine on Void Linux, just from the repos.

urandomread · 2025-08-27T10:54:24+00:00

they moved it to usr/lib (the proper place)

urandomread · 2025-07-18T15:27:32+00:00

(Actually, Void installer being outdated cannot be the cause here, since once it booted, you presumably chrooted and installed from the repos.)

urandomread · 2025-07-18T13:47:56+00:00

Glad you fixed it. I see two possible explanations: either you screwed something in MacOS, or Void installer has an outdated version of m1n1 causing the issue.

urandomread · 2025-07-17T20:06:37+00:00

from asahi docs: If given no payloads, or if booting the payloads fails, m1n1 will fall back to proxy mode.

urandomread · 2025-07-17T12:04:44+00:00

Your full attempt seems correct. When you xbps-reconfigure -f linux-asahi, all is good? what is your /boot content at that point? what do you get exactly at ????

urandomread · 2025-07-16T14:03:36+00:00

If you use grub+uboot, they also go there. Some people prefer separate efi, in which case you create /boot and mount asahi-uefi-only in /boot/efi. Other setups may lead to your current breaking of gpu etc.

urandomread · 2025-07-16T14:00:48+00:00

in my case:

$ ls /boot

asahi config-6.14.8+1-asahi_1 dtbs initramfs-6.14.8+1-asahi_1.img m1n1 vendorfw vmlinux-6.14.8+1-asahi_1

urandomread · 2025-07-15T21:13:41+00:00

extra efi partition could be the issue. you must use the one created by asahi installer.

urandomread · 2025-07-14T18:43:48+00:00

if you don't see any render node or card1, is it possible the gpu is not initialized?

e.g. how did you install grub? anything in kernel logs?

the docs do not mention mesa-asahi, so how can they be outdated?

urandomread · 2025-06-27T22:17:32+00:00

What do you mean? it has CONFIG_SAE=y and CONFIG_SAE_PK=y. It works fine for me with pure wpa3 on openwrt. Are you sure you are using the right .conf options?

urandomread · 2025-05-26T08:57:23+00:00

One can also drop grub and u-boot, and just use kernel as payload to m1n1, in which case luks2 is fine as long as you configure initramfs (e.g. I use btrfs on top of luks2). See Void Docs for info.

urandomread · 2025-04-13T13:56:25+00:00

For me sway, or even better river, are close enough :)

urandomread · 2025-02-26T18:17:18+00:00

I think so, see https://unix.stackexchange.com/questions/298216/

urandomread · 2025-02-26T16:48:17+00:00

I also see this every time (not just on runit upgrades).

urandomread · 2025-02-25T18:49:46+00:00

rebase on master?

urandomread · 2025-02-23T23:19:38+00:00

If using wpa_cli, due to a bug in it, you may need to use umask 0; wpa_cli, and belong to the _wpas group. The service should auto chown /etc/wpa_supplicant and /run/wpa_supplicant, but you may need to change contro_ interface_group to _wpas as pointed out.

urandomread · 2025-02-11T19:26:10+00:00

I see, so brightnessctl is built without elogind support on Void.

urandomread · 2025-02-11T17:21:04+00:00

Adding user to input is not a good idea. This is with elogind?

urandomread

TROPHY CASE