Fedora 36 on the Framework Laptop

Fedora 36 is locked in for a May 10th release, but the current Release Candidate 5 (which will become the final release) is available now.

Installation Guide: Fedora 36 Installation on the Framework Laptop - Framework Guides

See also


s2idle still appears to be broken. I used the command from the F35 thread to change my sleep mode to deep.

This was tracked down a little further and a workaround was found that should make s2idle work no worse than it did before:

1 Like

Good to know. I’ll try that out. Thanks!
EDIT: Seems to have done the trick

Fedora 36 is available on the official website.

Here is the summary.

I just tried to request the backport of the patch to make microphone work without configuration on Fedora 36 by Fedora Bugzilla with component: kernel. However I gave it up for now because I needed to show the reproducing steps on F36 and rawhide. See the description template on the component: kernel. I am not sure if people in Fedora kernel is positive for this kind of backporting, as I saw this comment. However I think it’s still worth to request the backporting.

What is the current state of suspend and hibernate on F36? If I add the “mem_sleep_default=deep” kernel parameter then they keyboard and mouse are unusable upon wake. What does “nvme.noacpi=1” do?

1 Like

I followed a guide to conditionally swap between disk and zram on sleep/suspend but didn’t get suspend + hibernate working yet but general battery drain is terrible. A fully charged laptop will be dead within 24h even if untouched within that period.

Basically this: https://gist.github.com/eloylp/b0d64d3c947dbfb23d13864e0c051c67?permalink_comment_id=3936683#gistcomment-3936683 - maybe with some other tweaks, can’t remember, tried a few things.

I love Fedora and Framework (especially together) but the battery situation is such a bummer. Looking into more options for battery tuning today …

I have a Dell XPS 13" runing ubuntu 22.04 and I tweaked the swap settings on it and the battery life is the polar opposite. Lasts forever while the lid is closed. It HAS to be possible.

For what it’s worth, battery life while using it seems great!

Thanks for sharing the GIST document about the hibernation. I would recommend checking the Fedora 35 main thread written on the 1st comment, and try the sleep: deep for now.

Have you tried this in the guide above on the 1st comment?

There is also one optional workaround needed to get the best suspend battery life, which is setting “nvme.noacpi=1” in your kernel parameters. In Fedora, you can do this by running the following command: sudo grubby --update-kernel=ALL --args=“nvme.noacpi=1”


^the above has worked wonders for me so far. Thanks for reposting this. I can verify this is much better than stock Fedora 36 config.

Ok, after further use with the nvme.noacpi hack and after 24 hours of not plugged in lid shut standby and I am at 19% … usually it would be dead. Not that much better, but during the day when closing and re-opening regularly it’s more of a noticeable improvement. Still not what I would consider good.

1 Like

Thanks for testing the kernel option!

1 Like

I’m not sure if this is a Framework thing or a Fedora 36 / Gnome 42 thing, but I normally see a UI indicator when adjusting the keyboard backlight brightness. This works for most of the Fn keys like display brightness, but not when pressing Fn + Space for keyboard backlight brightness. Is there a way to get this to register in Gnome on Fedora 36 with the Framework?


Does anyone have the Wi-Fi 6E intel AX210 “seeing” 6 GHz channels (In Europe/NL)?

My (11th Gen) Framework laptop with i5 running Windows 10, Windows 11 with Intel driver version.
2.4 GHz and 5 GHz channels are seen. But 6 GHz is not.

Fedora 36 “live” version running from USB or hardware install, not seeing the 6 GHz Wi-Fi network/ESSID.

(I have an Alienware 15R3 with AX210 that is working with 6 GHz. (It is seeing the 6 GHz radio/ESSID of my Wi-Fi 6E access point. But only on Windows 11. Someone “fixed” this remotely for me. But I was not told yet what they did. It was not working before it was fixed either.)

It might have something to do with regulatory domain. However the chart at Countries Enabling Wi-Fi 6E | Wi-Fi Alliance already shows adopted for most of Europe. I know that it passed all regulatory hurdles (for the low part of the 6 GHz band). And link shows it should be adopted into law in the individual EU countries by last December.

But if it needs to be forced, how? Anyone knows? (Or for any Linux distribution and/or Windows 10/11 on the Frameworks laptop? )

There is little to find about it working on 6 GHz specifically. However not many people have access to Wi-Fi6E equipment yet.

Best regards,

1 Like