Arch Linux on the Framework Laptop 13

That’s weird. I have Artix and 12th gen FW13, I do modesetting, xf86-video-intel is not installed, and it has been working fine for two years already.

What’s exactly your error?

Have you tried adding an Xorg config file with the contents:

Section "Device"
    Identifier "Device0"
    Driver "modesetting"
Endsection

I have not tried Identifier "Device0". It does sound like it should work - though it is working now via Wayland. I’ll test this anyway for completeness.

1 Like

Well, I’m this kind of guy who wants to avoid Wayland for the same reasons I want to avoid Systemd.

Have you had any success with X11 now?

Whenever I am on my laptop, regardless of the activity, eventually it becomes laggy (video, mouse movements, keyboard) to a state of almost being unusable. Using AMD GPU and processor, with Hyprland on Arch. Quitting Hyprland does not solve it, neither restarting swap or anything else, only full reboot. Packages updated, RAM is nowhere near full, few processes running. I have changed the GPU to “Gaming” on BIOS to be more effective but not a fix. Could not see anything on dmesg or ps -aux that might be causing this. Has anyone experienced this issue or know of any fix?

If you are using Arch on an AMD CPU, this topic may apply to you:

I’m late to this party, but I had lots of weird little issues with my AMD FW13 on 6.12.X. 6.13 has been much better behaved.

Oops, sorry for the late reply. I can confirm that XWayland works at least, so I think it’s a config issue on my end. I seem to remember that Ubuntu + X11 did work out of the box, but my memory is fuzzy.

I have replied on Artix + KDE + Wayland for some significantly important and time-critical situations and it’s been very reliable, this is Framework 13 13th gen Intel, currently Linux DEVICE_NAME 6.12.20-1-lts #1 SMP PREEMPT_DYNAMIC Sun, 23 Mar 2025 19:17:49 +0000 x86_64 GNU/Linux.

Just a heads up: updated my framework today and I’m seeing the return of random kwin_wayland_drm: Pageflip timed out! This is a bug in the amdgpu kernel driver GPU freezes. Reported it in a similar issue here, reverting to my last snapshot for now.