Fedora 42 on the Framework Laptop 13

Okay, you see I thought your stuff was working as far as this goes on a direct connect to the laptop. It should work out of the box, and if that is not the case outside of month one post cpu release it would be very surprising (i.e. correct kernel on a non beta release).

However if you are talking about whether it is working through the caldigit dock…that is a different story. I have been using thunderbolt docks (including caldigit docks) for years and can definitely say that no dock works with every laptop. They may claim universal support but this is rarely even close to true. In fact the caldigit tb4 dock you are using had uncountable issues with a number of Dell Latitude and Precision models at my job. Caldigits while usually very good about compatibility only support MacOS and WIndows, and as long as that is the case you will experience issues until someone on the linux side essentially reverse engineers its quirks to get everything working. If it does not work out of the box on a dock this is neither on Framework or on Linux. You can blame that squarely on Caldigit, and your own expectations for that.

My point is don’t go blaming the wrong things if you don’t know what the real cause is. Just went through this in a reddit thread, and when we got to the bottom of it…a third party peripheral with an Intel nvme was the cause. Different nvme drives in the peripheral did not cause the problem, only when the intel drive was in, did the problem show itself. No one can engineer for that. Your most likely culprit in your instance is your dock, or the dock with the chain of peripheral attached to it. It will likely get better but with docks especially there is no guarantee. They are finicky, I have even run into situations where Dell TB series docks were having major issues with Dell laptops, same with Lenovo and Lenovo Docks.

I have no problem driving the bus over Framework or Linux, but it better be because they are the ones actually at fault. If you are having issues with the dock specifically my recommendation is try some other docks. Took me four until I landed on my OWC that works extremely well with the Intel Frameworks. AMD Frameworks may be different because quite frankly USB4 is not TB4 and despite the standard…there is no guarantee there.

Lastly if you go through this thread USB-C/Thunderbolt Dock Megathread - #508 by Daniel_Power you will see the general consensus is Caldigit AMD USB4 is a no go..and these go back over a year…Caldigit is not going to suddenly start supporting Linux, so either it works out of the box, you wait and hope it starts working, or you try a different dock. I have a ton of thunderbolt peripherals, which is why I have AMD on most of my workstation setups currently, but I have stuck to Intel for laptops to increase the likelihood of compatibility.

My Caldigit TS4 works very well, although I have the 7040 fw13 model.

But I get the frustration on getting a new laptop and putting linux on it and then getting issues. Its just how Linux is with brand new hardware, it will take some time until the major kinks are resolved and even then there is always a possibility regressions happen. So lets say in a month they work out the kinks and after another month something can again “break” because of something that got updated in the kernel.

Fedora in a way is safe as they do test the kernels, and also provide the user community to test them and provide feedback which in turn tells the fedora developers if a kernel update is safe to push. Although this is far from perfect, it atleast mostly stops totally broken kernels to be pushed to users.

2 Likes

Exactly this. I connected my monitor directly to the HDMI to verify if it was the TS4 causing the issue and still got the black screen. It’s very random. Can take 30min or 4hours. So its very hard to reproduce on demand.

Waoo that is a big thread, thanks for sharing, had not seen it. Have to read later when i got time :slight_smile:
I have been really busy with work so i have not tested my laptop much but it was pretty stable even using the TS4. Will start using it more tonight. Hopefully all the updates has done the trick. And i can agree that Intel laptops specially are more compatible (for now anyway). But hopefully with the AMD’s being more and more popular we can see a shift in the future :wink:

1 Like

Just to update. I have now used my 13’ AI 370 using the TS4 dock for atleast a week and it has been very solid and working without any issue.
Whatever updates that has been pushed out from Fedora and the kernel updates has made my setup very stable now.
So for anyone considering the similar setup i can say its working great now.

3 Likes

good to know that. I have been running Linux Mint on my 7040 13 but I have been considering switching to Fedora if the battery is more optimized on it. I barely get 3 or 4 hours of battery on mine, how many hours are you getting?

I use my dock and external monito so i’m pretty much only using it stationary. The few times i used it i can’t say it was great. Although i also find that using the key combination Win+B can toggle power state so not sure if i was on performace or what. I now use on power save mode mostly for more quiet experience. When i play youtube and have many tabs it gets very noise otherwise. Use the other mode when i need.
But to be honest from my experience Fedora plasma KDE is miles nicer then mint. Menus and everything is just so much more modern. I really love it. So just for that i would recommend it :slight_smile:

I never ever had a linux distro this stable and functioning. It just works. Almost using win11 without the bloat and crap.

Yes I understand that. I have used fedora before. the main reason why I didn’t like fedora at that time even though it was fast and stable was lack of packages and lack of LTS which meant I had to keep on upgrading the whole distro very often whereas Mint i could have it for years.

I’m a noob myself so for me i’m used to keep updating :slight_smile:
All i need is stability and things to just work. I have pretty much everything i need and the “only” problem i had software wise, was the onedrive but i bought InSync which works really great. Well worth the price.
Beside that all my apps like telegram, discord, protonmail, passw manager works very well. I will try on my main pc with 4090 gpu once i get it back and try gaming also with steam :slight_smile:

But i wonder, what is the issue with upgrading the whole distro? (i assume you mean from say fedore plasma kde 42 to 43 or what they call it)

I see, yes it’s not a problem but in my case I like to keep my distro installation for some years that’s all. after more than 20 years using Linux I’m not into changing it every 6 months or a year. Gaming works great nowadays usually on any distro.

1 Like

I just installed Fedora 42 with KDE plasma on AMD Ryzen AI 5 340 w/ Radeon 840M.

Everything is find except can’t get the microphone working. When I goto settings→audio

I see Family 17h/19h/1ah HD Audio Controller Digital Microphone selected. The recording of audio doesn’t work.

The kill switch is good not on red.

Can someone help me here?

1 Like

Hi Framework Linux Community,

I just installed Fedora 42 on AMD Ryzen AI and cannot get the microphone or Bluetooth to work. Can someone please help me? Thanks

For the microphone, the mechanical switch is turned on (no red) and I reinstalled pipewire. I am trying to use Google Meet and have opened a meeting in Chrome and Firefox. I have selected the Digital Microphone, Internal Stereo Microphone, and an External Headset to test. The audio does not work.

For Bluetooth, I get the following:

$ systemctl status bluetooth○ bluetooth.service - Bluetooth serviceLoaded: loaded (/usr/lib/systemd/system/bluetooth.service; enabled; preset: enabled)Drop-In: /usr/lib/systemd/system/service.d└─10-timeout-abort.confActive: inactive (dead)Docs: man:bluetoothd(8)
Sep 09 20:09:36 fedora systemd[1]: bluetooth.service - Bluetooth service was skipped because of an unmet condition check (>

I reinstalled core Bluetooth packages:

sudo dnf reinstall bluez gnome-bluetooth linux-firmware

I still get the same Bluetooth Status.

Hi Framework Linux Community,

I just installed Fedora 42 on AMD Ryzen AI and cannot get the microphone or Bluetooth to work. Can someone please help me? Thanks

For the microphone, the mechanical switch is turned on (no red) and I reinstalled pipewire. I am trying to use Google Meet and have opened a meeting in Chrome and Firefox. I have selected the Digital Microphone, Internal Stereo Microphone, and an External Headset to test. The audio does not work.

For Bluetooth, I get the following:

$ systemctl status bluetooth○ bluetooth.service - Bluetooth serviceLoaded: loaded (/usr/lib/systemd/system/bluetooth.service; enabled; preset: enabled)Drop-In: /usr/lib/systemd/system/service.d└─10-timeout-abort.confActive: inactive (dead)Docs: man:bluetoothd(8)
Sep 09 20:09:36 fedora systemd[1]: bluetooth.service - Bluetooth service was skipped because of an unmet condition check (>

I reinstalled core Bluetooth packages:

sudo dnf reinstall bluez gnome-bluetooth linux-firmware

I still get the same Bluetooth Status.

EDIT:

Bluetooth now works. I just had to iterate through the errors with chatgpt.

I think my microphone is working after a full power down and some updates. I have tested it in an online mic tester and opened a Google Meeting. Both appear to show that it is working. I will just need to confirm in a chat tomorrow :slight_smile:

I occasionally experience an issue where if I connect my LG monitors over USB-C which have their own power supply, I simply do not get video output. I do not notice this issue under Windows 11.

I have a feeling this is a driver issue, anyone has the same experience maybe we can get the Fedora x FW team to look into this.

FW 13 AMD 7040 series.

I’ve encountered the random freeze bug on an FW 13 w/ AI 300 series running F42+Wayland.

Disabling PSR (and Panel Replay too) seems to have fixed it for me, atleast so far. As of the time of me writing this, it’s running stable for ~21.5hrs, vs freezes within ~6-8hrs.

Reported this on the firmware repo and added a PR on the linux docs repo:

For anyone facing a similar issue looking for a tldr fix:

run,

sudo grubby --update-kernel=ALL --args="amdgpu.dcdebugmask=0x610"

then reboot

I just installed Fedora 42 on my FW 13 w/ AI 7 350. So far so good.

I started experimenting w/ Linux on my FW before Fedora was listed as an officially supported OS, so I started w/ Kubuntu 25.10 b/c I’m still a beginner and thought an Ubuntu-based distro would be easier. It worked okay, but I didn’t love how KDE handled multi monitor panels, and it didn’t seem to respect the 80% charge limit I set in the BIOS.

When Fedora was listed as a supported OS, I switched, and to my surprise, the software center had the option to update FW’s AMD drivers. On top of that, it also respected the 80% limit.

Still a couple things I need to work out:

  1. Bluetooth is stuttery on my true wireless headset (Soundcore C40i). Works okay on my Sony 1000XM4. It requires a restart to get working. But at least it stutters less than Kubuntu 25.10.
  2. Occasional freeze on restart. About half of the time I restart, it freezes at the Framework/Fedora splash screen. This seems to happen more if restart after either docking or undocking.

I think I still have some testing to do (ex: microphone, etc), but I’m otherwise enjoying this Linux journey.

This topic was automatically closed 180 days after the last reply. New replies are no longer allowed.