This is a wiki post, so feel free to edit it with instructions on installing and using Arch!
(Matt’s note: This is a COMMUNITY SUPPORT Linux distro. All support for this distro will be from the Framework and Arch communities. Ticketed troubleshooting will continue to be done using our officially tested/supported distros, Ubuntu LTS and Fedora.)
This’ll be my daily and I run Arch, so I’m stoked. I’ll be sure to contribute to the archwiki if there’s anything I can add, when I get my Batch 3 device.
I’ve been running Arch (and working on it) for about a day and a half. It has been a very seamless experience so far! Bluetooth, web cam, wifi, microphone and my trackpad config from my FW13 worked as-is. I don’t have a GPU so I haven’t tested that. And I don’t use the fingerprint scanner.
I did run into a hiccup today where I resumed my laptop from suspend and I couldn’t get wifi working. I have suspended-and-resumed with wifi working several times before that. A reboot fixed that. So I’ll be on the look-out for that happening again.
Also, as with the FW13, you’ll want acpilight instead of xbacklight to configure screen brightness. Note that acpilight provides an xbacklight command:
This would be amazing. Yes, we will be depending on this as this happens (once the page is updated and goes live) - it will point to the Arch Wiki for the AMD Ryzen 16 and 13.
I have this issue inconsistently on my install as well. Doesn’t matter if the ssd is installed in my Razer Blade or my Thinkpad T470. I wouldn’t assume it’s a Framework issue at this time. Most of the time it doesn’t happen, but sometimes the machine spirit chooses to express its malcontent with its neighbors.
So far, so good. I was able to install Hyperland (Wayland wm).
The only gotcha is that I did enable “game” mode in the bios setting for embedded GPU. I’m using two 4K monitors, and default 0.5GB VRAM is not enough for that
P.S. I did not encounter any framework-specific issues, only Wayland’s issues
The Firefox did not use hardware acceleration otherwise But it is an issue with Hyperland.
I switched to “sway”, and it works fine. The current version of Hyperland has performance issues. My GPU load is 25% idle, causing Framework to run with 50-55C temps And the steam client doesn’t like it (too many bugs and glitches)
Update: It would appear that 0% backlight translates into a very visible image on the screen. I’m not sure if this is working as intended and is some sort of hardware limitation for how low the display can go, but my other laptops basically turn off at 0% (granted the pixels are still updating). It could also be due to technology differences with IPS panels, or a software glitch on my install, I’m really not sure. Just something to be aware of.
I’m on KDE Plasma and using their built in brightness management.
Oh now that’s interesting. This is the same install/SSD as the one that exhibited that behavior on my Thinkpad, so I wonder why the behavior was different. Oh well, it gets dim enough so I guess it’s a non-issue. Just odd.