Thanks for the feedback. As noted by folks elsewhere in the comments here, the lived experience with Linux on the Framework Laptop is highly dependent on which distribution you use, and specifically, the distros policy on taking on and delivering kernel updates. Our policy at Framework has been to publish setup guides for the most popular distros. Where we've been able to build bridges and get contacts in place with distro maintainers, we also deliver them hardware and reach out to them when folks in the community run into issues.

The obvious issue with this is that when issues occur upstream, we end up reactive to them alongside Framework Laptop customers. There are several possible solutions to this (which are not mutually exclusive):

1. Building our own Linux distribution for the Framework Laptop. We don't believe this is a good business to get into, and we've seen strong distro preferences in the community that mean that even if we did this, we may not address a plurality of customers' needs.

2. Partner more deeply with specific Linux distributions to attempt to validate kernel updates on Framework hardware before they are accepted for release. We see this as much more viable than option 1, and it's something we are discussing with distros (and we would love to work with additional ones on this).

3. Provide more clarity in our recommended Linux distributions and setup guides around which ones have more conservative kernel policies that are unlikely to run into issues (Ubuntu LTS with an OEM kernel for example) vs ones that more aggressively update and have more risk of driver breakage as a result (basically all of the other distros we currently list). Also as noted in this thread, the risks here will be higher for newer platforms (Intel 12th Gen) than older platforms (Intel 11th Gen). This is something we are now going to prioritize based on feedback we've gotten in the community.

We're always open to any and all additional feedback.