Arch Linux

I want install Arch on a new laptop(that cureently runs Windows 10) I just bought. Since I don't want to run through the installation manually(again) I want to use the installation script. Unfortunately I have a small problem. I can configure everything as I want, except the drives. When I click enter on the tab for the drives it opens a black screen with nothing in it. I can write in it anything I want, but commands don't work. It is also impossible to exit this window except if I use ctrl+c. Does anyone knows how to fix this?

Aloha! I used to run krunner inside a hyprland session by invoking krunner via hotkeys or console.

Yesterday I removed plasma-desktop as hyprland does all I need except krunner. I kept the krunner package, but the executable "krunner" is no longer found. Anything I can do except installing the whole plasma-desktop again?

I don't know why but every now and then my display completely freezes, completely except my mouse which is still able to navigate the screen, but can't interact with anything. No hotkey works, seems that the keyboard freezes too when this happens, except for the one that lets me enable the leds of the pc. I use a msi laptop with hybrid graphics card if that can help

Hello. Please critique how I'm updating / maintaining my new Arch installation so I can fix anything I'm doing wrong. This is mostly what I could gather from the Arch wiki tailored to my system. I think I know what I'm doing - but as I've often learned, it's easy to misunderstand or overlook some things.

Step 1: perform an incremental full system backup so I have something to restore if the update borks anything. I've chosen to use the rsync command as laid out on the wiki:

sudo rsync -aAXHv --delete --exclude={"/dev/*","/proc/*","/sys/*","/tmp/*","/run/*","/mnt/*","/media/*","/lost+found"} / /media/linuxhdd/archrsyncbackup

I have a large hdd mounted as a secondary drive under /media/linuxhdd. It is configured to automatically mount from fstab using uuid. Both my root drive and that hdd are formatted ext4. I'm not using the -S option because I don't think I'll be using virtual machines (I have other hard drives I can make bootable). --delete is used so I maintain one current set of files for restore purposes. This keeps the copying and transfer time to a minimum. (I maintain disk images offline with a different tool - this is simply one local copy for easy restoration purposes)

Step 2: Check the Arch wiki - follow instructions for any manual steps

Step 3: once every 1-2 months, update the mirror list using reflector

sudo reflector --protocol https --verbose --latest 25 --sort rate --save /etc/pacman.d/mirrorlist

This should sort the fastest 25 mirrors into mirrorlist. Remember to use the -Syyu option in step 6 if this step was done

Step 4: Clean the journal

sudo journalctl --vacuum-time=4weeks

This should keep 4 weeks of files.

Step 5: Clean the cache

sudo paccache -r

This should keep no more than 3 versions laying around. Once and a while, I can clean out all uninstalled packages with -ruk0 options instead.

Step 6: Upgrade Arch packages with pacman

sudo pacman -Syu

I need to watch for pacnew and pacsave files and deal with them (although I haven't seen any yet)

Step 7: Review the pacman log

nano /var/log/pacman.log

This should tell me about any warnings, errors, instructions, or other things I need to deal with.

Step 8: Remove Orphans

pacman -Qtdq | sudo pacman -Rns -

This could be recursive and needs to be run more than once. Instead, I'll just run it once every time I update. This should keep things cleaned out.

Step 9: Update AUR packages

Check the build scripts to make sure the package hasn't been taken over and that it won't run anything funny.

yay -Sua

This should update just the AUR packages

Step 10: Remove AUR orphans

yay -Yc

The wiki says this "removes unnecessary dependencies" which I believe means AUR-only orphan packages.

Step 11: Reboot

reboot

Step 12: Update flatpaks from the GUI (Gnome-->Software-->Updates)

Any mistakes? Suggestions?

Thanks!

Hello all,

System spec: Arch with KDE (not using Wayland) PSU - 1000w CPU - 3900x RAM - x4 32G = 128G GPU0 - 2080TI GPU1 - 4060 x3 monitors 1440p x1 monitor 4k

I'm running a multi-gpu setup (4060 and 2080TI). Both cards work in isolation - I've tried all monitors with them from cold boot. System recognises them, and I see both in nvidia-settings and nvtop.

Normally I'm running x3 1440p monitors off of the 2080TI, this works fine. I'm not stretching the display across the three. They share a virtual screen, but are treated as individual desktops.

There is a 4k monitor that I have, but when I plug it into my secondary 4060 GPU all four monitors go black. Unplugging returns back to my 3 1440p monitors plugged into my 2080TI.

I'm running nvidia-dkms and nvidia-settings for drivers. There's a bunch of RGB vomit in my rig, fans and the like... 9 of them with dual commander pros. I have two KVM switches on my monitors (both tested in isolation, behaviour from monitors is identical with or without them) - monitors get used for work. Macbook Pro is happy using a 1440p and the 4k via a KVM switch. Cables all tested and sound.

I've got a power draw plug meter on order, so I'll be checking to make sure I'm not exceeding my PSU's output, but aside from that I'm clueless now. Any ideas what is going wrong?

UPDATE: I managed to resolve my issue, came down to nvidia-settings doing janky stuff.

RESOLUTION:

• sudo rm /etc/X11/xorg.conf
• sudo nano /etc/default/grub -> add nvidia-drm.modeset=1 to GRUB_CMDLINE_LINUX_DEFAULT
• sudo grub-mkconfig -o /boot/grub/grub.cfg
• sudo reboot now
• Log back in...
• xrandr --setprovideroutputsource NVIDIA-G0 NVIDIA-0 && xrandr --auto

That did the trick! For persistence of monitor layouts, I then opened KDE's display config (right-click desktop) and moved the monitors about to desired positions. Saved. Rebooted. Sorted.

However, if I log in and immediately log out, Wayland is available on the login screen and you log in to a Wayland session.

This is identical on both my laptops, they are very different in hardware and performance. This started happening after updates about 3 weeks ago.

I have looked at logs and I can see the subsystems trying Wayland and falling back to X but I can't see an obvious reason (probably my lack of experience at this).

Anyone else experienced similar?

Hello guys,

I am losing my mind over this issue:

I am running Endeavour OS on my laptop and I need to connect to my OPNSense through wireguard, but the performance has been terrible, DNS resolution to be precise. I think this is related to a specific configuration to either NetworkManager or openresolv, because the same configuration file works fine on Android or Windows devices.

My suspicions are that because I am using two piholes that are on the same network of the OPNSense router (and I have a few firewall rules redirecting every DNS traffic to them), there is a conflict somewhere. I have also tried to mess around with the MTU size, but to no avail.

Here is my config file:

[Interface]
PrivateKey = ****************************************
Address = 10.10.10.5/32
DNS = 192.168.0.11, 192.168.0.12
MTU = 1420

[Peer]
PublicKey = ****************************************
AllowedIPs = 0.0.0.0/0, ::/0, 192.168.0.0/24
Endpoint = ******************:51825

Any ideas? Thank you.

hy im trying to install arch as the third os on my windows / ubuntu machine and i cant figure it out how to set the grub bootloader i have already read the friendly manual but probably also due to my non native English origins i coudnt find an answer to my question witch is during the arch install should i reinstall grub with grub-install ? i would prefer to keep the old (ubuntu) one also because its already customized but unfortunately i cant...if i dont install it i dont have the directory /boot/grub in witch i should place the grub.conf file so should i just create this directory ? i have tried with os-prober correctly activated to generate a new grub.conf but it doesnt pick up the arch install .., what are the files i must have to make grub recognize those partitions as a new os to witch assign a new boot entry ..

so closing the lid actually stops the wifi the bluetooth but since I am using swayidle for some reson suspending by closing the lid doesn't tell swayidle to actually show up even though pressing the shutdown button which I made it suspend for tests it actually works in the shutdown button so I am guessing this is an nvidia issue I am using nvidia-dkms not even the open ones so to mitigate this issue I though about making systemd ignore it when the lid closed and just right my own script when runs when the system suspends which is basically just systemctl suspend so any ideas

UPDATE_1: yes I wanted to add that I thoroughly checked "journalctl --system" and it was not helpful at all it seems my laptop sends an unknown key that correspends to other laptops tablet mode and that is funny since my laptop has none

well and systemd basically rfkill soft block wifi and doesn't actually enable it again when the lid is open so yeah I guess the solution I gave is fair enough I guess

I use dwm on Arch and in my autostart.sh I start KMonad. This requires me to be member in the uinput group (what I am). Since a few days starting KMonad fails with:

kmonad: /dev/uinput: openFd: permission denied (Permission denied)

(Same when I try to start it manually.)

The workaround is to run sudo modprobe uinput and then to start kmonad (again).

I just don't understand why this is necessary now. I have this udev rule defined:

/etc/udev/rules.d/90-kmonad.rules:

KERNEL=="uinput", MODE="0660", GROUP="uinput", OPTIONS+="static_node=uinput"

I guess this broke because of a sudo pacman -Syu. Has anything changed in the last few days? I can't find anything that looks related on Arch Linux.

Looks like there's a breaking change in the syntax of the hyprland.conf file that came from yesterday's update, as now things like blur_passes = ... don't work anymore and need to be just passes = ... inside a blur namespace (not even sure this is the appropriate term?), ie something like:

    blur {
        enabled = false
        size = 3
        passes = 3
        new_optimizations = true
    }

Hey everyone. As the title suggests, I use bspwm, with xfce4-power-manager and sddm installed. I have the power manager setup that I can hibernate/suspend (still a bit confused as to the differences between the two but its besides the point) everytime I hit a button on my keyboard to "sleep" I get the popup below:

I'm not aware what application is stopping the sleep, nor if it is something I should worry about, but if I click Yes then my system goes to sleep. Hitting any key after that wakes it up, without me having to enter any password. I know there is software I can install and setup to do that function, but I was wondering if there is any way I can configure xfce4-power-manager to use sddm as the "locker" program, so that it takes me to the sddm login page when waking.

Thanks in advance!

Edit: I just tried to sleep and this time this is the popup that appeared:

Quote from the Archwiki (Installation guide):

Arch Linux should run on any x86_64-compatible machine with a minimum of 512 MiB RAM, though more memory is needed to boot the live system for installation. A basic installation should take less than 2 GiB of disk space.

Does that mean it is technically possible to get a Windows XP-era device with 512 Mb RAM and install Arch on it by pulling out the hard drive, connecting it to a modern machine via a SATA to usb connector, for example, with the modern machine running the live environment, and then just partitioning and installing on the old computer HDD, then putting the hdd back on the old computer? Is something like that feasible? I don't have a machine to test it on, but it certainly sounds like a fun experiment. It sort of reminds me of the stories of Gentoo cross-compiling.

Edit: It is a HYPOTHETICAL question. Please focus on the METHOD and IMPLEMENTATION instead of 32-bit compatibility or driver issues.

I am having issues with putting my PC to sleep. I have a 5800X3D, an ASUS Maximus ROG motherboard and a RTX 3090. Every time I put it to sleep, instant wakeup. Journalctl shows nothing obvious to me that woke it up. I've disabled all ACPI wake devices. My CPU is set to s2idle deep. I am at a loss as to what is causing this, other than possibly it being an Nvidia issue. Anyone else having similar issues? Any assistance is appreciated.

I have a few devices running Arch... Rasperrys, laptops, a NAS, etc

After an update I'll run pacdiff to check for any updated configurations to look out for.

On the laptops I'll use meld to compare and it's nice to visually pick and choose what to update.

But for the headless units, I'm using vimdiff and it's sometimes difficult to see what to change - esp. when a few lines in a block of changes needs picking and choosing.

What other approaches are you using for this?

I have activated passkeys on my Google account and now I cannot use them to login on my laptop running Arch Linux, assuming that both my phone and laptop are connected to the same ESSID. It just says place your phone close to your computer but nothing happens.

Do you think we'll reach a point where it will be the "default" (using quotes since Arch is DIY so no default but we can argue that stuff like systemd is default) way of using Arch? Or at least have all the required packages in an official repository?

cross-posted from: https://feddit.de/post/2456701

This is a bug I just experienced on one of my manjaro computers. I was puzzled as fuck because cpu/io usage wasn't high but it was pretty slow.

Maybe this will help someone.

KDE is now running at 1fps after the most recent update, it was really stable before I updated a few days ago. I don't really know how I should troubleshoot this.

I have a Scarlett Solo and I have found that with the linux-rt kernel, I get no noticeable latency recording audio, whereas there's a few ms delay on the main linux kernel.

I am able to run other applications and play games just fine on linux-rt. Is there any reason not to just make this my default?

For three weeks (since systemd-253.7-1) my system has been full of odd shutdown behaviors...

Failed to move /run/initramfs to /

Failed to switch root to /run/

and then hangs before full shutdown. Last evening's update to systemd-254.1-1 appears to fix it all (and even seems a bit snappier)

Thank you very much to the maintainers! likely: Christian Hesse

I read that AMD microcode from the AGESA always has a higher patch version number than the microcode supplied by the kernel. The lastest microcode version from the linux-firmware repo the latest version for family 0x19 are:

Microcode patches in microcode_amd_fam19h.bin:
Family=0x19 Model=0x01 Stepping=0x01: Patch=0x0a0011d1 Length=5568 bytes
Family=0x19 Model=0x01 Stepping=0x00: Patch=0x0a001079 Length=5568 bytes
Family=0x19 Model=0x01 Stepping=0x02: Patch=0x0a001234 Length=5568 bytes

My CPU (Ryzen 5900x) reports [ 0.579161] microcode: CPU0: patch_level=0x0a20120a, though? My BIOS is from January, the amd-ucode was update in July.

Others have come to the same observation and speculate that the linux-firmware microcode is only for Epyc. AMD in their statement about inception only talks about updating microcode via AGESA.

https://www.phoronix.com/forums/forum/phoronix/latest-phoronix-articles/1402527-amd-inception-cpu-vulnerability-disclosed?p=1402567#post1402567
https://www.phoronix.com/forums/forum/hardware/processors-memory/1349645-amd-publishes-new-family-19h-cpu-microcode?p=1349760#post1349760
https://www.reddit.com/r/archlinux/comments/hdrron/amd_microcode_not_loading/

Anyone having more information on this?

Solved, see below.

I recently reinstalled my home server and was unable to open my LUKS-encrypted hard drive. Neither my usual passphrase nor a newly created keyfile were working. I tested on different distros, initially on my new Proxmox installation, later on a the Arch ISO. I eventually tried the disk on my main system, on which it used to be and I still had an old keyfile on - et voilá. So I created keyfiles as suggested in the wiki and occasionally md5sum returned a different hash for the keyfile! Why is this happening? I find' this extremely concerning because this could potentially result in massive data loss due to a keyfile apparently randomly not working as I was experiencing it. What am I missing?

For reference because I don't know how to share what I exactly did.

Scenario #1:
A directory on a mounted hard drive on my desktop.

$ echo -n '$mypassphrase' > ./dir/keyfile
$ md5sum ./dir/keyfile
 c6dd9329dbe030127ce5e19d85de4df9 ./dir/keyfile
# chown root:root ./dir/keyfile; chmod 400 ./dir/keyfile
# md5sum ./dir/keyfile
c6dd9329dbe030127ce5e19d85de4df9 ./dir/keyfile

Scenario #2:
My old keyfile in /etc on my desktop containing $mypassphrase.

# md5sum /etc/keyfile
a1c10c2d023c982259f6c945ebee664e /etc/keyfile

Scenario #3:
Booted from the Arch ISO on my server.

# echo -n '$mypassphrase' > keyfile
# chown root:root keyfile; chmod 400 keyfile
# md5sum keyfile
c6dd9329dbe030127ce5e19d85de4df9 keyfile

Scenario #4:
A directory in /home on my desktop.

$ echo -n '$mypassphrase' > ./keyfile
$ md5sum keyfile
a1c10c2d023c982259f6c945ebee664e keyfile

EDIT: I just moved the disk back into my server and tried echo'ing my passphrase into a keyfile which returned the hash starting with c6, whereas opening a file using nano and pasting the passphrase into the file returned the hash starting with a1.

EDIT: I moved the disk back into my server, reinstalled Proxmox and tried again. I was able to unlock the disk after I pasted the passphrase into a file and deleted all trailing spaces/newline. I also tried echo'ing the passphrase into a keyfile and that also did not work, no clue why but it seems to work on some systems on not on others.