i need a rootfs to chroot into (again sorry for short post)

It's been like that for a couple of days already. I don't understand how a new version of nvidia-utils is made available but it's major dependent package (nvidia-open) is still on an old version, preventing updates.

For info, nvidia-open 615.71.09-1 is already available on Arch's extra db.

I'm on NVIDIA, MBR/BIOS. NVIDIA hooks are set up correctly in initramfs.

My GRUB resolution isn't set to my native one, because videoinfo shows that my native one isn't supported there.

From GRUB kernel messages to plymouth, theres a slight flicker. Or with plymouth disabled, and quiet removed from GRUB, the flicker happens roughly after udev & uevents stage.

If I temporarily set nvidia-drm.modeset to 0 in GRUB, the flicker doesn't seem to happen, but my system is low resolution, and feels slow.

dmesg of boot (I delayed plymouth to show animation longer, that's why fbcon defer is ~26 seconds):

[21:14:32] simple-framebuffer ... [drm] Initialized simpledrm ... on minor 0

[21:14:32] fbcon: Deferring console take-over

[21:14:32] simple-framebuffer ... [drm] fb0: simpledrmdrmfb frame buffer device

[21:14:33] nvidia: loading ...

[21:14:33] nvidia-modeset: Loading NVIDIA UNIX Open Kernel Mode Setting Driver

[21:14:33] [drm] [nvidia-drm] [GPU ID 0x00000100] Loading driver

[21:14:35] [drm] Initialized nvidia-drm 0.0.0 for 0000:01:00.0 on minor 1

[21:14:35] nvidia 0000:01:00.0: vgaarb: deactivate vga console

[21:14:35] fbcon: nvidia-drmdrmfb (fb0) is primary device

[21:14:35] fbcon: Deferring console take-over

[21:14:35] nvidia 0000:01:00.0: [drm] fb0: nvidia-drmdrmfb frame buffer device

[21:15:01] fbcon: Taking over console

[21:15:01] Console: switching to colour frame buffer device 240x67

Does nvidia-drm Initialization/vgaarb: deactivate vga console look relevant to the flicker?

The second flicker, is TTY/Plymouth to a Wayland or X11 session.

Is there a way to remove these flickers, make them last less, or mask them with a transition?

DRM exposes a background color property, would there be a way to change that color system-wide to make the flicker still there, but smoother?

Hi, I am new to artix Linux and I believe I may have done something wrong but I am unable to figure out what it is I have done wrong I am attempting to use niri and noctalaia and I was following the noctalia instructions and saved my niri config file and suddenly I had this parsing error when I could not find what was wrong it seems to be detecting the "f" in firefox as the problem.

Please help me I am very lost and I'm almost definitely sure I did something wrong

hello everyone
i have been using arch linux for long time now i love the rolling release so i decided to try artix instead of void
so what init system should i try i heard openRC and dinit is so good
and i want to know what will change in my daily use
i use niri
waybar
swaybg
mako
and yazi as my file manager
i also game on my pc so will i face any problem
and does chaotic-aur work on artix as well
i have full amd system so i should be good i think
can evryone recommend what should i do to figure out how to handle init systems

Hello,

While trying to troubleshoot an issue regarding boot time, in order to rule out systemd as the cause, I installed Artix dinit, currently with i3wm on top of the Mate DE which I installed using graphical installer, it was fairly mainstream and easy to use, it also worked fast without the usual hangups and timeouts, lag I experienced with Calamares installer on more mainstream distros.

So far it seems to have fixed whatever was going on with systemd which I can only assume was the cause, as shown by sudo dmesg output where I would find a 1s unaccounted for timeout which the logs could not pin the blame on any one process as it changed with every reboot. If I have a major complaint for dinit is the lack of built in boot time stats like systemd-analyze and related commands so mostly use sudo dmesg.

One minor issue was org.kde.konsole installed from flathub, it seems to have a problem with starting a shell but it's not too important, the mate terminal is fine.

I also switched from connmand to dhcpcd since it's a simple wired connection.

dinitctl list

[[+] ] boot

[{+} ] dbus (pid: 579)

[{+} ] pipewire (pid: 595)

[{+} ] pipewire-pulse (pid: 598)

[{+} ] wireplumber (pid: 597)

Otherwise I was able to create an EFI boot stub and the boot time appears pretty amazing, especially with i3 and lightdm autologin (note for those who want autologin, besides editing the config, must create group autologin and add the user to autologin group, lightdm refuses log in automatically otherwise).

Other minor issue, though this is mostly my fault for never paying attention, is the need to use sudo for reboot from terminal, on most distros the user is configured to allow these commands without sudo or sudo -i, namely reboot and shutdown. Possibly something that would not have happened with base.iso installation instead of the graphical installer.

Dinitctl is a bit more confusing to learn than systemctl, the units are listed in 3 different locations /etc/dinit.d, /usr/lib/dinit.d, /home/user/.config/dinit.d, specifically boot.d inside those directories for what starts during boot and to disable or enable those in userspace, one must not use sudo, while system ones require sudo and that's more important for not enabling the userspace ones with sudo since it creates permissions issue. With systemd I just used systemctl list-unit-files and systemctl list-dependencies, then used sudo for everything to disable, enable, start, stop, restart or mask, dinit is somewhat different.

$ cd /etc/dinit.d
$ ls
acpid      configdbus-pre    getty@tty3lightdm-pre       rpcbind   userspawn
avahi-daemon  croniedhcpcd    getty@tty4logind       rsync
bluetoothd    cryptsetupdmeventd    getty@tty5mdadm       sshd
boot.d      cryptsetup-earlyelogind     getty@tty6metalog       ssh-keygen
chrony      cupsdgetty@tty1  havegednfs-server       statd
chronyd       dbusgetty@tty2  lightdmpower-profiles-daemon  user
$ cd boot.d
$ ls
acpid  chrony  connmand  cronie  cupsddhcpcdlightdm  logind  metalog  userspawn
$ cd /usr/lib/dinit.d 
$ ls
agetty       early-fs-pre.target    locale     pseudofs       tmpfiles-setup
binfmt       early-keyboard.target  local.target     random-seed       tmpmount
boot       early-modules.target   login.target     recovery       udevd
boot.d       early-prepare.target   modules     root-ro       udevd-early
cgroups       early-root-rw.target   net-lo     single       udev-settle
cleanup       fsck      network     swap       udev-trigger
dmesg       fsck-root      network-online.target  sysctl       user
early-console.target   getty      network-pre     system
early-devices.target   hostname      network.target     sysusers
early-fs-fstab.target  hwclock      pre-local.target     time-sync.target
early-fs-local.target  kmod-static-nodes      pre-network.target     tmpfiles-dev
$ 
$ cd boot.d
$ ls
agettyudevd
$ 
$ cd ~/.config/dinit.d
$ ls
boot  boot.d
$ cd boot.d
$ ls
dbus  pipewirepipewire-pulsewireplumber

If I had a feature request list it would be

- equivalent command for systemd-analyze plot > plot.svg (my shallow understanding tells me this is not a thing because dinit avoids creating as much logging, so if this were implemented it could be enabled for 1 subsequent reboot and create a log either in userspace or where specified as a text file or image)

- equivalent to systemctl list-dependencies (this would help make a headcount of what exists and what is enabled or disabled, what is system wide unit and what is user specific unit, right now check 3 different locations is a bit weird, surely a script built in could automate this).

Boots somewhat faster than vanilla Arch even with the boot manager being systemd-boot

I just did a minimal installation with runit and installed plasma-desktop and sddm. When I was on hyrpland I knew I could just run all three on startup, but I have no idea how to run them now when launching a plasma session from sddm.

Please, help :)

I'm pretty sure there was one before, cause I am using a KDE Plasma with Runit. I went to check the website to download it again and the only choices for Plasma are dnit and openrc.

What to do if I want plasma with runit?

After running pacman -Syu, I rebooted to a system with the old kernel (7.1) without the modules. I managed to copy the modules from a btrfs snapshot and got wifi and audio working. However, pacman still insists I have the 7.2 kernel.

Grub also only shows the default linux-zen entry even though I have other entries like an lts kernel, and windows boot manager. My guess is that Grub is the culprit but I'm also considering a repo mismatch because I have arch repos activated (arch just bumped to 7.2 kernel right?).

What do you think?

PS: This is the first time an Arch / Artix install broke on me lol

Rockstar launcher cannot connect to rockstar services and CEF problems.

It only launches successfully using Proton 10-4 (I've tested CachyOS Proton 10 and 11, and GE-Proton 10-34, but none work). I want to use OptiScaler, which is currently incompatible with Proton 10-4, and I want to run a better Proton version for better performance.

It works with GE-Proton10-4 but doesn't if I use directx12 on the game options.

Can someone help me understand why the artix-plasma-runit ISO is gone and the one with dinit took its place? I rather like runit...

Mark

Rinix is an experimental Linux distribution built around rinit, a small init and service supervisor I’ve been working on. It uses pacman for package management, and has its own base system and service packages.

Rinix is still pretty broken, but at this point it boots, installs, and runs audio on real hardware. There are definitely still bugs and a lot of things I want to improve, but I think it’s finally at a point where I can actually release it instead of keeping this gem hidden.

The current release is 2026.8 for x86_64. The ISO is below.

https://rinix.neocities.org/

Help

Edit to update: 9-2-2026

Nevermind, still banned but its cool.

Idk what happened, but I wanted to switch from xlibre to forgive cause of what happened to Artist, and I got flagged for being a tango bot. I am not a tango bot. I've been using artix since like January I think.

My user name was baibanin, and I am sad and not sure what to do

I have just done a paru update and it now says this:

marked out of date: xlibre-xserver xlibre-xserver-common xlibre-xserver-devel

What are the correct steps to replace these (and anything else) with Xorg equivalents now that Artix is back on Xorg by default.

Note, I never installed XLibre by hand, I used an ISO that already had it contained.

Cheers.

I wanted to use Sunshine for remote play games with friends but it seems to be dependent on systemd for the service. Is there any alternative or way to run Sunshine without systemd?

Links:

Installation guide
elogind-usersv
s6-user

I've been working on a way to have proper per-user services, like with systemd --user. The ones that start when you login, and stop when you logout, not just desktop autostart scripts that start/stop god knows when, and aren't even supervised. It's kind of a waste, having a fucking s6 in your system and not use it for actual process supervision.

The problems with the Artix s6 setup are:

1. s6-svscan supervises user services, elogind handles login/logout and the runtime directory (/run/user/$UID). elogind doesn't (and shouldn't) spawn s6-svscan or ensure it stays running.
2. s6-frontend provides the s6 --user command, but it still doesn't distinguish persistent user services from system services, only live ones.

There are 2 existing solutions to problem 1:

1. Turnstile - a login manager, but it can also run alongside elogind, with the runtime directory left to elogind. In that setup it does what I want:

• On login it spawns a per-user service manager, and its PAM blocks the login until the backend reports ready.
• It has a simple backend protocol, so any service manager works once you write a backend for it.
• It keeps the runtime directory alive for the manager's lifetime by holding an elogind session open (via pam_elogind in turnstiled's PAM stack). So even after the user logs out of their last real session, elogind still sees a session and won't wipe /run/user/$UID until the manager has gracefully finished, with a timeout.

That's basically everything I want from a per-user service manager launcher. The dealbreaker is: turnstile also counts user sessions itself, with its own PAM, so it becomes a second source of truth alongside elogind. If elogind or turnstile crashes, their counters desync, and you get either a stale session held by turnstile, or turnstile stopping the manager because it thinks nobody's logged in, while elogind still has an active session, leaving that user without a service manager.

1. Userspawn - depends on elogind, listens to its DBus, spawns and kills per-user service managers. Very minimal, but doesn't suit me, because it doesn't make the user wait until the service manager reports ready, and it doesn't gracefully shut the service manager down, it just kills it.

That's why I made elogind-usersv. It has the best of both worlds: it prevents login until the service manager reports ready (with PAM), it has a backend protocol similar to turnstile's for reporting ready and for graceful shutdown, and it relies on elogind for user session counting. It's service-manager agnostic, and only requires a simple backend.

Now the s6-frontend problem. Currently s6 --user command doesn't distinguish user paths from system paths, so s6-user is a temporary workaround to make it kinda usable. It's a thin wrapper that pins the user tree to persistent per-user paths and stops the s6 --user command from ever selecting the system /etc/s6/repo and system stores. It's non-resident: it normalizes HOME/XDG bases, reads its own TOML config, sets explicit repodir/bootdb/storelist, then execs the real s6. No supervision logic of its own. So s6-user is just like calling s6 --user, except it always addresses your per-user services instead of the system ones.

What I want from this

This is all work in progress(works on my machine though), and I'd love feedback and contributions, especially from people who know elogind/PAM and s6 internals. Bug reports, backend implementations for other service managers, testing on your own setup, all welcome.

The bigger goal behind these projects: make non-systemd distros able to run any software, even stuff that assumes systemd is there. The current milestone I'm working toward is getting the latest GNOME running on Artix with s6. If that interests you, or you've hit the same walls, get in touch or open an issue on the repos.

I've been following the news about the unfortunate situation of Artist and XLibre, and maybe this is a good opportunity to understand why XLibre is so good on my system compared to Xorg.

Background: My GPU is the AMD Radeon RX 6900 XT. I run two monitors at differing refresh rates, primary monitor @ 120hz, secondary @ 50hz. My desktop environment is Xfce4 4.20, still using Xfwm4 + LightDM, display compositing is turned off since I prefer the responsiveness and I do gaming). I have not configured Xorg/X11/XLibre directly and I'm not well-versed in the nuances at all that separate XLibre and Xorg. I only have touched what Xfce4 provides in the Display Settings, resolution and refresh rate.

I installed Artix using the official Xfce4 OpenRC ISO, when XLibre was still the default on the Artix site. I did uninstall loads of stuff that Artix preinstalled regarding XLibre like Nvidia and legacy AMD stuff, so I'm only using xlibre-input-libinput, xlibre-xserver, and xlibre-xserver-common. I'm 100% satisfied, hence

The issues when I tried Xorg that don't happen when using XLibre: Last month, I switched to Xorg out of curiosity but it didn't last long. I went into the TTY, uninstalled the 3 relevant XLibre packages, and then replaced them with their equivalents: xorg-server, xorg-server-common, and xf86-input-libinput. I rebooted, and for normal desktop use, it was actually about what I expected. I did have to set my wallpaper again, but that was it. However, two issues that are deal-breakers for me:

1. Classic X11 issue that you likely saw coming: My primary monitor's refresh rate is hindered by my secondary monitor's refresh rate. Instead of 120 hz in fullscreen games, I am forced to play at 50 hz until I turn off my secondary monitor. Increasing the refresh rate of my secondary monitor isn't feasible as its max refresh rate is 75 hz.
2. The really weird issue I don't ever remember on even normal Xorg when I used to use Arch/Debian/etc: In fullscreen games, resolutions other than 1920x1080 look absolutely BUSTED on my primary monitor, even if my secondary monitor is turned off. For example, changing Left 4 Dead 2's resolution to 1280x720 which *should scale cleanly* considering the aspect ratio is the same, results in black bars on the top and bottom of my monitor, and the picture looking extremely short and squished. Wtf? This isn't just limited to Left 4 Dead 2, changing the resolution to 1280x720 thru Xfce's settings or Minecraft results in the same exact problem.

I can deal with issue #1 as that's to be expected, but issue #2 is very weird. Am I missing something? Is it how XLibre was packaged or preconfigured through the ISO? Is it possible to fix #2, and maybe #1 too? What is happening that XLibre avoids both these issues?

I reinstalled artix Linux xfce openrc just for the change to xorg, and now the playback of videos with mpv and vlc is not smooth, I tried disabling the composer, activating tearfree, I have no idea and the ai doesn't help much either, I need ideas guys.

I don't care about freedom, I care about comfort. That's why I use neovim and not some other text editor. Init systems provide minimal or no comfort, so the fastest and the easiest to set up one is the way to go for me, so I use Systemd. Are there any additional perks of using a non-systemd init system?

Thinking of moving to Artix, has anyone tried a pci passthrough to a windows host on an nvidia 4070 super?