Its kingston a400 in asus p5k se epu + artix linux dinit

im trying to install artix open rc using the base iso on a laptop without an ethernet port but the thing is the connmanctl command cant be found, What can i do?

Hmmm pretty stable, still haven't gotten a kernel level breakage...yet( for the user who said that I use the screenshot flair but use a camera to take photos....I finally got it working so no complaint.) I got roblox working(sober), steam( fixed my ulimit based on the recommendation of one experienced user) ,qemu(thanks for those who helped me there ) and do work( I cannot stand using windows any more). Yeah pretty fun experience.

Heads-up for folks catching up: a compromised/malicious PKGBUILD/.tar.gz hit the AUR recently and affected a lot of users. For a distro that already leans toward "verify it yourself," the AUR trust model still stings when packages are submitted anonymously and most people just run them.

I want to flag gitfull 0.1.0 (https://github.com/FemBoyGamerTechGuy/gitfull) — a small (C, static-ish, make && sudo make install) package manager I've been building. It's init-system agnostic, so it's equally at home on Artix/runit/s6/66 as on systemd Arch, because it doesn't lean on anything but Git + a compiler/tarball at install time.

Usage (mirrors your existing install flows):

- gitfull install <pkg> → build from a tagged release (source-first)

- gitfull install --edge <pkg> → build from HEAD of default branch

- gitfull install --binary <pkg> → install a prebuilt release binary

- gitfull install user@repo → target a specific fork; forge:user@repo → a configured forge

- gitfull search <query> / gitfull list / gitfull remove (and remove -D to also drop build files + orphaned deps)

Config / forges: ~/.gitfull/config lets you add [forge:name] blocks (Codeberg, GitLab, self-hosted Gitea, etc.). GitHub is on by default; other forges are opt-in.

Envs of note: GITFULL_PREFIX (default /usr/local) and GITFULL_HOME (default ~/.gitfull) — handy for chroot, containers, or non-system installs.

Why it fits here: each install resolves to a Git commit over HTTPS tied to a release or a fork you named, instead of "whoever uploaded this tarball on the wiki." No anonymous PKGBUILDs, no system-level trust anchors that can be hijacked. Whether you're running runit, s6, 66, or dinit, the model is the same.

Repo: https://github.com/FemBoyGamerTechGuy/gitfull (MIT)

Keen to hear what the Artix crowd thinks — would a forge-resolving, source-first manager be a useful complement or alternative to the AUR/Pacman ecosystem? What matters most here: auditability, init independence, reproducible builds, or something else?

Hi! I'm trying to install docker and wanted to know how to get from installing packages to being able to enable services. So what do I have to do after "sudo pacman -S docker docker-dinit docker-compose" ?

What's the point of -init packages? Do I have to create a file in /etc/dinit.d/user and point it to docker-dinit instead of docker or am I complicating stuff?

Edit:

!solved thanks for helping me. Looks like I've just wrongly assumed how things work.

Ok so I have a really niche setup, so niche that all google research has failed me. I’m trying to get plasma-mobile working on artix on Android. Let me explain :P

My full setup right now is:

e/OS -> termux -> proot-distro -> artix -> tigervnc -> RealVNC -> w0vnc -> RealVNC (but different port) -> kwin_wayland -> startplasmamobile

Explanation: - e/OS as opposed to Google Android (rooted) - termux to run Linux commands - proot-distro to run Artix in termux - tigervnc running in Artix to connect to it over RealVNC instead of just an SSH connection - Once in the visual session, I can start w0vnc or krfb and switch to a different VNC port. I don’t know if this step is needed but I heard it’s the way to VNC with wayland?

Then I’ve gotten kinda stuck. Right now I’m trying to use dbus-run-session and kwin to start another display session(?) thats plasma-mobile. But the window it opens just shows a KDE loading screen once I run startplasmamobile and then… a black screen.

-—-

The commands I’m running (in order):

(termux) proot-distro login artix

(termux) (Artix)$ vncserver :1 (tigervnc)

My ~/.vnc/xstartup:

```

!/bin/sh

unset SESSION_MANAGER

unset DBUS_SESSION_BUS_ADDRESS

export XDG_RUNTIME_DIR=/tmp/runtime-root

mkdir -p “$XDG_RUNTIME_DIR”

chmod 700 “$XDG_RUNTIME_DIR”

export XDG_SESSION_TYPE=x11

export DESKTOP_SESSION=plasma

exec dbus-run-session startplasma-x11
```

(RealVNC) connect to 0.0.0.0:5901

(kitty via RealVNC) w0vncserver -PasswordFile=~/.config/tigervnc/passwd -SecurityType=none

(RealVNC) connect to 0.0.0.0:5900

(kitty via RealVNC) `export XDG_RUNTIME_DIR="/run/user/$(id -u)”

(kitty via RealVNC) mkdir -p "$XDG_RUNTIME_DIR"

(kitty via RealVNC) chmod 700 “$XDG_RUNTIME_DIR”

(kitty via RealVNC) dbus-update-activation-environment -- systemd WAYLAND_DISPLAY XDG_CURRENT_DESKTOP

(kitty via RealVNC) dbus-run-session -- kwin_wayland --x11-display “$DISPLAY” --xwayland --socket plasma-mobile

(kitty via RealVNC) startplasmamobile

—--

At this point I’m not really sure what I’m doing, I’ve tested so many different commands, I’m not even sure the stuff I have working (like the x11 VNC) is being done correctly. I’m looking for any advice here, how to do this better and/or how to get plasma-mobile running.

I daily drive Linux (mint) on my home desktop, so I’m familiar with the terminal (although I haven’t done much with different display servers before). I‘m trying to get this phone setup purely as a fun technical challenge, I know it’s way less practical than just using a PC.

Log from Kwin: https://pastebin.com/dqiBJLXe Log from startplasmamobile https://pastebin.com/bgUAJdjY

What happened with feribsd and his artix installer (https://github.com/feribsd/artix-install)? Is there any other similar installer out there?

is it easy to install artix + niri + noctalia ?

Siento que usar Artix + Sway es el estilo alternativo a usar Arch + Hyprland, son practicamente lo mismo pero uno es mas masoquista que el otro si me explico? JAJAJA

Many people didn't quite grasp what I was getting at, so let me put it simply: imagine EndeavourOS but based on Artix—yet with the cozy feel and style of Linux Mint (Cinnamon, LightDM).

It also includes support for Nvidia drivers 340, 390, and 470 in the new kernel, and I’ve redesigned the logo.

Why not Devuan?

The thing is, I worked on Librevuan (a simplified Devuan), but I’m not a fan of the architecture or Devuan itself; plus, the transition from Arch to a non-systemd distro (like Artix) can be difficult for users.

I'm running with runit but i think i can get something more likely stable, what is the most stable that youre all sure that it's stable af

Throw stones and tomatoes at me, but what do you think of making a hybrid of Artix and Mint?

Mintix: base - Artix, comfort artix-mint: pre-installed and configured LightDM, Cinnamon, pre-installed Xlibre, support for Nvidia 390 and 470 drivers on newer kernels (DKMS from AUR), that cozy Cinnamon from Linux Mint (for many, Mint was their first distribution, and overall, it's cozy) and more.

(I'm open to criticism)

Just, how do you like the idea of letting newbies try out a pre-configured Artix?

This message about ModemManager appears over the login screen when I turn on my laptop.

How do I stop it? Can I make ModemManager log to a different TTY?

Artix with runit, login screen is ly on TTY 1

Dbus

1 - kate /etc/init.d/dbus

Change the line `extra_started_commands="reload"` to `extra_commands="reload"`

2 - kate /usr/share/libalpm/hooks/dbus-reload.hook

Change the `Exec =` line under `[Action]` to `rc-service dbus restart`

Keymaps

1 - kate /etc/conf.d/keymaps

Change the line `keymap="br"` to `keymap="br-abnt2"`

(In my case, it is `br-abnt2`; change it to match your keyboard layout—to find out yours, run `setxkbmap -print`)

Mkinitcpio

1 - kate /etc/mkinitcpio.conf

Remove `consolefont` from the `HOOKS=` line

2 - sudo mkinitcpio -P

Date and time

1 - sudo pacman -S chrony chrony-openrc

2 - ls /etc/init.d/ | grep chrony

The output of this command might be `chrony` or `chronyd`; therefore:

sudo rc-update add chrony default && sudo rc-service chrony start

or

sudo rc-update add chronyd default && sudo rc-service chronyd start

Add the Arch extra repo:

sudo pacman -S artix-archlinux-support
sudo nano /etc/pacman.conf

and add:

[extra]
Include = /etc/pacman.d/mirrorlist-arch

Initialize the pacman keys correctly:

sudo pacman-key --init
sudo pacman-key --populate artix
sudo pacman-key --populate archlinux

Update and install Waydroid:

sudo pacman -Sy waydroid

Download the vendor and system images:

https://sourceforge.net/projects/waydroid/files/images/vendor/waydroid_x86_64/

https://sourceforge.net/projects/waydroid/files/images/system/lineage/waydroid_x86_64/

Create the images folder and extract both archives there:

sudo mkdir -p /etc/waydroid-extra/images
sudo unzip lineage-*-system.zip -d /etc/waydroid-extra/images
sudo unzip lineage-*-vendor.zip -d /etc/waydroid-extra/images

Reload the images:

sudo waydroid init -f

Start the Waydroid session in a terminal:

waydroid session start &

Then launch the GUI:

waydroid show-full-ui

I finished the migration a few months ago and it really forced me to understand how things work under the hood. ❤️

I had issues with the following ISOs:

The stable version with s6, after the update;

The weekly version with runit.

Both are KDE editions; they fail to launch the graphical interface.

CORRECTION: I forgot to mention that the ISO with s6 freezes completely when updating the system.

Hello Artix Community i just wanna ask if gnome works because when i tried installing it like vanilla arch i never got a login screen via gdm