Fedora 42 on the Framework Laptop 16

Fedora Workstation 42 is released! You can download Fedora Workstation 42 here .

Official Fedora 42 release announcement [can be found here ](The answer is 42! Fedora Linux 42, that is. - Fedora Magazine.


Installation Guide: Fedora 42 Installation on the Framework Laptop 16 - Framework Guides

3 Likes

Sweet, I’ve been waiting for this! Anyone here brave enough to test whether it resolves the dGPU detection issue for the rest of us?

Graphics card not available - Framework Laptop 16 / Linux - Framework Community

1 Like

Migration done. It went well. So far I haven’t noticed any problems.
:+1:

(in my case did it that way: Upgrading Fedora Linux Using DNF System Plugin :: Fedora Docs , did not re-install all…)

Kernel 6.14 so

$ sudo dmesg | grep xdna
Placez votre index droit sur le lecteur d’empreintes
[    1.232230] amdxdna 0000:c4:00.1: enabling device (0000 -> 0002)
[    1.334529] [drm] Initialized amdxdna_accel_driver 0.0.0 for 0000:c4:00.1 on minor 0

NPU driver started… now I need to know how to use it :wink:

1 Like

Been running for a few hours. No issues yet on the dGPU - tested “suspend” 3 times so far and its come back each time.

1 Like

Updated this morning and I’ve experienced zero issues so far. Huge props to Framework for their first-party Linux support, I can’t imagine daily driving Linux on any other hardware.

One thing I noticed is that the new update to GNOME (version 48) supports limiting the battery’s max charge. I know this is already possible in the BIOS but it would be nice to see a firmware update to support it through GNOME settings too.

2 Likes

I cannot get my 7700s to be used when playing games. It’s recognized and can be seen, but the moment it is used, the driver crashes.

WARNING: [../src/amd/vulkan/radv_physical_device.c:1987] Code 0: Could not open device /dev/dri/renderD128: Invalid argument (VK_ERROR_INCOMPATIBLE_DRIVER)

TU: error: ../src/freedreno/vulkan/tu_knl.cc:385: failed to open device /dev/dri/renderD128 (VK_ERROR_INCOMPATIBLE_DRIVER)

deviceName (RADV PHOENIX) = AMD Radeon 780M

deviceName 19.1.7, 256 bits) = 1lvmpipe (LLVM

It works with Bazzite. Any ideas? Would really like to use vanilla Fedora.

This sounds like the issue I was referencing in this thread, perhaps you may find it useful and see if the error messages line up:

It’s nice to see Fedora getting updated, I use it as my main OS on my PC. I just hope nothing breaks when I update.

I am actually having quite a few issues since upgrading to Fedora 42.

Gnome shell crashed twice on me in as many days. Resulting in a hard reboot (as even GDM didn’t come up again).
I also have had some screen corruption in gnome shell (I think, but I am not sure, always seconds before those crashes)…
The backtrace shows “amdgpu_ctx_create” as one of the last functions before it crashes (last one being abort).

In crash reporting I also see “Unexpected system error” for the linux kernel, but it can not be reported becasue

A kernel problem occurred, but your kernel has been tainted (flags:GW). Explanation:
W - Kernel issued warning.
Kernel maintainers are unable to diagnose tainted reports.

(Note this might be just noice, I don’t remember this resulting in a crash).

I don’t have a dedicated GPU so problems are also happening with internal AMD GPU

1 Like

Can you send logs from your system?

Edit: other people seem to be having issues

Seems like Linux 6.14 is not running well in general for Fedora on the framework.

Hey,

Someone in the second post mentioned they also had hard freezes on Ubuntu using 6.14.

I tried some other kernel versions on Fedora 42:
6.15.0 rc2: same issue
6.14.xx: same issue
6.13.12: same issue
6.12.15: It panics for some reason (?), but I’m not sure if it’s because I’m using 42 or something went wrong while installing it.

I’ll keep searching through 6.13.xx till I find something stable

Edit: 6.13.6 is promising so far

Nice, compiling a kenral is not too hard (if you have a guide) if you are on Ubuntu 25.04 or Fedora 42, I will find a guide that works well for each and edit it into this reply.

Maintaining one though, and keeping it up to date, can be a pain. But if it works it works, and it can be nice just having a solid kernel in your back pocket.

for my case I have this bug:

but no crache (for now…)
But many artifacts…

I hope a kenral patch is released soon.

I’ve yet to see an acknowledgment that the (various?) issues with the dGPU are being worked on. But saying you’re doing something is not a prerequisite to doing something, so I’m hopeful as well.

Not sure if this is caused by the Fedora 42 update, but I seem to be having issues with secure boot.


Has anyone else experienced this issue?

1 Like

It actually seems to be a mesa problem

A bugfix should be in Fedora soon: FEDORA-2025-47e9ecf4a6 — unspecified update for mesa — Fedora Updates System but you can install the testing version already

Also I’ve had no problems for the past couple of days;
I installed the mesa update yesterday morning, without reboot or restarting most application; Which in a way makes me suspicious because I should have at least needed to relogin for wayland/gnome & firefox to use the new drivers…