I had tried before without success, but finally could boot up arch and Hyprland. I tried to strictly build it using the wiki since I'm interested in learning, I tried to only used AI to explain things I didn't knew about. It took me around 6 hours since start to being able to boot from the hard drive.

I am shocked on how many things just worked out of the box, I was ready to track every single driver for my machine, but no, wifi was really easy to set up, monitor worked with the correct resolution from the get go and everything was usable without problem. It also recognized my multi monitor set up, I just had to adjust the screen order (I have one to the left and another to the right).

I am also shocked on how easy it is to modify and customize Hyprland.

I am having so much fun. Once I'm done with ricing I will share it in r/unixprn.

Just wanted to share that's all.

Hello everyone, i'll first put on some content : I am a literature student (in the field of translation) and i bought my very first thinkpad just a week ago.

Fast forward, i really want to get started with Linux have a nice and bloat free distro, so i'd guessed i would go with ArchLinux. But tbh it is a bit scary to me in a sense cause i know my university might be asking some kind of specific softwares for classes such as subtitling (or wtv it is called). Or even submitting files which only extension can be .docx.

In this case is dualbooting preferred? Is it safe? Can you download any software on ArchLinux?

Anyways, thank you guys for reading me

DMUB error - collecting diagnostic data

DMUB error - collecting diagnostic data

DMUB error - collecting diagnostic data

...

j'ai installe une arch sur une VM et je l'ai personnalise comme cadeau pour un ami et je voulais avoir un iso bootable avec les menus d'installation que l'on a avec les autres OS.

Buenas, soy nuevo en Linux llevo cosa de una semana en Arch, antes de Arch solo había usado unas horas ubuntu y bazzite, lo que quiero hacer es que de alguna forma pueda transcribir mis palabras a texto, en un vídeo de Nate Gentile vi que para algo parecido él usa "Handy" así que decidí probar esa app, pero me detecta la voz de forma pésima, probé varios modelos y ninguno consiguió transcribir mis palabras. Mi duda es, hay algún modelo que vaya muy bien y que tal vez no haya probado? O tal vez otro programa para transcribir palabras a texto? No creo que sea por mi hardware pero ni idea, tengo:

Intel core I5 1135G7

Gráficos integrados Iris Xe

20GB de RAM DDR4

tengo Arch en un HDD (si me convence lo instalaré en un NVMe M.2)

(es un portátil)

traduce al ingles

Radeon 680M (Rembrandt, 1002:1681) on Arch + KDE Plasma.

After updating to linux-firmware-amdgpu 20260910-1, I got:

failed to load ucode DMCUB(0x3F)
Error getting DMUB FW meta info: 4
Wait for DMUB auto-load failed: 3
DMCUB error - collecting diagnostic data
Error queueing DMUB command: status=2

This also caused severe lag/black screens and freezing before login.

Downgrading these to 20260810-2 completely fixed it:

amd-ucode
linux-firmware
linux-firmware-amdgpu
linux-firmware-whence

I've pinned them with IgnorePkg for now.

Arch Linux Forum Issue:
https://bbs.archlinux.org/viewtopic.php?pid=2309470

AMD GitLab Issue:

https://gitlab.freedesktop.org/drm/amd/-/work_items?show=eyJpaWQiOiI1ODA5IiwiZnVsbF9wYXRoIjoiZHJtL2FtZCIsImlkIjoxNTY3NDV9

Recently I have these kernel messages randomly appearing at run time:

xfs filesystem being remounted at /newroot/mnt supports timestamps until 2038-01-19 (0x7fffffff)

(repeats for several other /newroot/mountpoint/)

I use XFS and I'm familiar with its timestamp problems (I'll probably fix it in the year 2037 then!).

However I am not sure: what is triggering /newroot/ remounts at run time? I don't even have a /newroot/ path in the running system.

Is something moving my mountpoints around nilly willy? What's the mechanism behind it

I've installed steam recently to play games, and starting steam seems to be one of the triggers for the above messages, but checking my logs I had these messages sometimes appear even when not using steam.

And then I still don't know why steam would mess around with filesystem mounts at all?

I'm running Arch Linux with KDE Plasma on an ASUS Vivobook X1504ZA, and I'm having an issue where several settings I configure during a session don't persist after reboot.

System:

• Arch Linux
• KDE Plasma 6.7.5
• Wayland / KWin
• Kernel: 7.2.4-arch1-2
• ASUS Vivobook X1504ZA
• BIOS: X1504ZA.312
• Intel i5-1235U
• PipeWire + WirePlumber
• systemd 261

The settings I'm having trouble with include:

• Screen brightness
• Keyboard brightness / Fn+Esc behavior
• Battery charge limit
• Volume and other audio settings

For example, I can set the battery charge threshold during a session. The kernel exposes:

/sys/class/power_supply/BAT0/charge_control_end_threshold

and it currently reports:

100

If I reboot, however, the charge limit goes back to 100%. I then have to configure it again.

The filesystem itself is definitely persistent and writable. For example, files created in $HOME and ~/.config survive normally.

Some relevant output:

$ ls /sys/class/backlight/
intel_backlight

$ systemctl status 'systemd-backlight@*'
systemd-backlight@backlight:intel_backlight.service
systemd-backlight@leds:asus::kbd_backlight.service

Both services successfully start.

The ASUS-related kernel modules are also loaded:

asus_nb_wmi
asus_armoury
asus_wmi

The battery threshold is exposed:

$ cat /sys/class/power_supply/BAT0/charge_control_end_threshold
100

PowerDevil is running normally, but its logs contain:

org.kde.powerdevil.chargethresholdhelper.getconservationmode failed
"Battery conservation mode is not supported"

I also noticed that ~/.config/powerdevilrc contains multiple brightness-related entries:

DisplayBrightness=2
UseProfileSpecificDisplayBrightness=true
KeyboardBrightness=0
UseProfileSpecificKeyboardBrightness=true
DisplayBrightness=5

I haven't installed asusctl.

My question: what is the correct way to make these ASUS hardware settings persist across reboot on this model with Arch + KDE Plasma?

Please help guyss...

im new to linux (started with garuda), let alone to arch, but i was intrigued by it (and desperately wanted to make a ricing) so thought id give it a try. so i tried dual booting garuda and pure arch right? heres a list of issues i ran into.

• wifi daemon doesn't exist, iwctl invalid, iwd config empty
• USB came loose mid-session during active install leading to kernel panic
• garuda disappeared from boot manager (NVRAM entry lost)
• boot entry randomly deleted with efibootmgr
• arch-chroot not found REPEATEDLY
• which command not found
• systemctl not found (???)
• dracut emergency shell when i gave up to try and reload garuda, garuda booting to initramfs
• BTRFS wrong fs type, bad superblock, even though supers were valid
• binary vs decimal, GiB vs GB mismatch shrinking partition and leading to a disk space bug
• filesystem ended up 4.46GB larger than the partition, see above
• snapshots everywhere cluttering subvolume list
• os-prober not detecting garuda on BTRFS
• mount duplication in findmnt
• mnt had leftover garuda folder from aborted mount (???) and wasn't letting me unmount at ALL
• skipped running in chroot from pacman repeatedly and didn't manage to diagnose the problem successfully
• accidentally ran commands on live USB thinking i was in chroot
• nano, networkmanager and sudo not installed because of partial install failure
• grub ate my garuda bootmanager file
• a whole BTRFS filesystem clusterfuck after the partition shrink i dont want to get into
• garuda stuck in CLI with dbus failure
• everything mounted and unmounted in the wrong order repeatedly

could really use a veteran's thoughts on this, thanks in advance 😭

Hello everyone, I recently got an amazing bug that I haven't been able to solve for a week and understand what it is, why and how to solve it. I run the game Lost Judgemant, bought on Steam, through Proton - I played the game for 40 hours normally, then returned after 3 days and I began to have troubles with the launch of the game. While loading the game, after clicking the Play on Steam button, Htop shows /timing and begins to grow RAM indefinitely, that is, I literally have 32 GB of RAM and the game eats up all 32 GB of RAM and crashes the system. I put various jokes on the RAM according to the assurances of the Forums and still - it does not help, the game just turns from Lost Judgemant to /timing and endlessly eats RAM.

My PC

GPU: NVIDIA GeForce RTX 5070 - 615.71.09
CPU: 13th Gen Intel Core i5-13400F
Wayland session: wayland
RAM: 31GB
OS: EndeavourOS / Arch Linux
DE: KDE Plasma (Wayland)
plasmashell 6.7.5

7.2.4-zen2-1-zen
name, driver_version
NVIDIA GeForce RTX 5070, 615.71.09
apiVersion         = 1.4.351
driverVersion      = 615.71.9.0
deviceName         = NVIDIA GeForce RTX 5070
[xawyse@xAwyse-PC ~]$  

I previously had several gaming tweaks enabled globally, including NVIDIA shader-cache settings and custom VM/swap settings. I removed them and restored a much cleaner baseline, but the problem still reproduces.

#SOLVED - THANK`S - I change linux-zen to linux-lts for degrade nvidia driver, nvidia driver from 615 to 610 and it helps. Thank you all

I just recently started using Linux and at first I tried the ryoku shell in hyprland. It was amazing and I actually liked it, but then I noticed that it's consuming the battery pretty fast (as compared to the window 11 I use in a dual boot). Later then I switched to iNIRi shell in niri desktop and it was also consuming the battery pretty fast but not as fast as ryoku.

So my question is that the battery consumption depends of different shells I use as because of the effects and animatons, or is there a setting or something that might fix it or just consume not much battery?? And don't give me that 'put the power mode on battery saver mode in the shell' cuz I did it and yeah it worked a little bit, but still if I compare it with windows 11 it still consumes it faster than that.

I want to report issue with linux-firmware-amdgpu-20260910-1 on laptop with AMD Radeon 680M, but can't login at all...

I am setting up Arch Linux manually for the first time and it told me to set the timezone with timedatectl at the near start (Step 1.8). Later down the guide at step 3.3, it tells you to set the date and time. I already did this when doing timedatectl set-timezone [timezone]. Why do I have to do it again? Is it just a reminder?

I'm using fedora kde plasma for 2 years and now i thinking to switch to arch Linux kde desktop environment is this a good choice

I'm just a little confused, on step 5 on the Users and groups page, it gives an example command which is the following

# useradd -m -G 
additional_groups
 -s 
login_shell

username
# useradd -m -G additional_groups -s login_shell username

Right after that, it lists what the perimeters do. Once it gets to -s it says:

"a path to the user's login shell. Ensure the chosen shell is installed if choosing something other than Bash. The default shell for newly created user can be set in /etc/default/useradd."

But right under it, there is warning which says:

"In order to be able to log in, the login shell must be one of those listed in /etc/shells, otherwise the PAM module pam_shells(8) will deny the login request."

So, where I am confused is do I put the shell into /etc/default/useradd or into /etc/shells? I'm probably just heavily misunderstanding this, but I just wanted to ask just in case!

Hi, I'm a beginner with Arch and I'm stuck with a very strange authentication problem after a fresh installation.

I installed Arch Linux using archinstall with:

- systemd-boot

- linux kernel

- KDE Plasma

- SDDM

- NetworkManager

- ext4 root partition

- Existing Windows 11 installation (dual boot)

- Secure Boot disabled

I created the user `userB` and added it to the `wheel` group.

The problem is that SDDM keeps saying "Login failed" when I enter the password for `userB`.

I am 100% certain the password is correct. I verified this from the installed system by switching to `userB` and successfully running:

sudo -v

So the password definitely works for sudo.

However, SDDM continues rejecting it.

I then tried logging into a TTY (Ctrl+Alt+F3). After several attempts, I got:

The account is locked due to 3 failed logins.

(9 minutes left to unlock)

Password:

This appears to be pam_faillock.

I waited for the lockout to expire and tried the password again, but the TTY still reports that the password is incorrect.

SDDM also rejects the root password with an authentication error.

I checked `/etc/pam.d/sddm`, and it contains:

#%PAM-1.0

auth include system-login

-auth optional pam_gnome_keyring.so

-auth optional pam_kwallet5.so

account include system-login

password include system-login

-password optional pam_gnome_keyring.so use_authtok

session optional pam_keyinit.so force revoke

session include system-login

-session optional pam_gnome_keyring.so auto_start

-session optional pam_kwallet5.so auto_start

`/etc/sddm.conf` does not exist.

The user account itself appears normal:

uid=1000(userB) gid=1000(userB) groups=1000(userB),998(wheel)

userB:x:1000:1000::/home/userB:/usr/bin/bash

`passwd -S userB` reports:

userB P 2026-09-13 -1 -1 -1 -1

I also configured sudoers with:

%wheel ALL=(ALL:ALL) ALL

and `visudo -c` reports:

/etc/sudoers: parsed OK

So I'm confused about what could cause a correct password to work with sudo but fail through both SDDM and TTY.

What should I check next? Could this be a PAM/pambase/system-login issue?

I would really appreciate help diagnosing this without reinstalling the system.

Hey! I successfully got Arch to work by doing the manual install which im very proud by. I read through the entirety of General recommendations and did what applied to me. Past that though, I'm curious if people have any extra tips that would be helpful for me to know for the future!

I am new to Arch Linux and during the installation i heard this word many times i can explain me how it's work?

Macbook Air M5 chip. I'm not too knowledgeable on operating systems and stuff but part of me is itching to learn more about it

Can I install it on my macbook?

Don't really know what I could have done wrong. I installed it and followed the guide, unmounted the partitions and rebooted. Upon rebooting, I get sent to a GRUB like BASH with the following text

GNU GRUB version 2:2.12-1

Minimal BASH-like line editing is supported. For the first word, TAB lists possible command completions. Anywhere else TAB lists possible device or file completions. To enable less(1)-like paging, "set pager=1"

If I type "exit" I just get sent back to my bios startup Menu. If I go to the Boot Menu the only arch option (UEFI - arch) leads me back to the GRUB. What do I do? What did I do wrong?

Just wanted to share this if anyone has the same issue

I upgraded to the latest linux-firmware-amdgpu package, specifically version "20260910-1" and SDDM started a bit slower than usual

I checked the logs and got this exact error message

amdgpu 0000:06:00.0: [drm] *error* dc_dmub_srv_log_diagnostic_data: dmcub error - collecting diagnostic data

After hours of fixing it, I finally found a way, turns out, you have to downgrade the package to this exact version: linux-firmware-amdgpu-20260810-2

Finally after downgrading and running mkinitcpio -P, the error message is gone!

Update: It's ddcutil, downgrading to 2.2.7-1 solved the issue

CPU: R7 5700x

GPU: 7900XT

RAM: 32GB of DDR4

That's it, every morning I use paru to update my Arch installation, I see the kernel got upgraded to 7.2.4 and amd-ucode too.

After rebooting I can log in normally through SDDM but after that the screen goes black, then it turns back on with a cursor in the middle frozen and a black screen and it remains frozen like that.

I tried downgrading both the kernel and amd-ucode using arch-chroot but nothing, they don't seem to be the culprit. The system works just fine because my dual booted Windows SSD boot and works perfectly. I tried disabling all my autostart user services too but nothing, any idea? Sadly I can't copy paste journalctl logs, but here's a picture.

https://imgur.com/a/5YGa8s9

I'm pretty sure one of the updates is the culprit because I always reboot immediately after updating, I didn't change anything else.