ROS, Ubuntu, and the Framework Laptop

Hello all! I have a bit of a catch-22. All the documentation for the Framework Laptop suggests kernel versions of 5.12 for maximal component compatibility. For Ubuntu this currently means 21.04 (Hirsute) is the only workable version. At the same time, I do a lot of work with ROS and the latest version (Noetic) only supports Ubuntu Focal (20.04 LTS).

Before I start installing and reinstalling OS versions I’m wondering if there are any known incompatibilities beyond the AX210 wireless card I should be aware of with running 20.04 on Framework?

My current planned workaround is to pick up a known-compatible wireless NIC to use with the laptop running 20.04 until either a version of 20.04.x with compatible kernel or a version of ROS supporting a compatible OS is released. That assumes of course that there aren’t any other showstopping incompatibilities between Focal and Framework. Advice appreciated!

The kernel in 20.04 most likely doesn’t support Tiger Lake fully. It may or may not boot or install, and there will likely be issues with graphics and standby if it does boot. 20.04.3 is getting released in a couple of weeks which likely has a recent enough kernel.

1 Like

I can’t answer your question directly, but I can say that I have had no issues whatever with 21.04 on my Framework. It runs better than any previous version did on my older Lenovo.

1 Like

Thanks @nrp, I’ll use 21.04 for now and when the new release of 20 comes out I’ll switch down to that to support my workflow. Loving the laptop so far, great job!

1 Like

@carpenma You can also run ubuntu 20.04 with the latest development builds of the mainline kernels. There are several wrapper scripts to install them from the ubuntu kernel PPA such as

@carpenma my solution for this is to just run ROS 2 in a docker container or to build from source. It is honestly much better to develop for ROS in a containerized environment than just having it natively installed. X-forwarding also allows you to use graphical tools too.

Does running a custom kernel in this way mess up future point releases?

I have 21.04 running, and will just keep upgrading until we hit 22.04, but I would have preferred to stay on LTS from the beginning, and this could have been a solution.

1 Like

The problem though is that the OSF might not have binaries until the first point release of 22.04, so building from source, containers, or a custom kernel on 20.04 for a binary install are the only options.

1 Like

Sure but does it break the update mechanism was the question?

1 Like

Oh, no I don’t think it does if the LTS has a newer kernel than the custom one.

1 Like