I must also add that on recent Fedora Kinoite I experienced dreadful regression that resulted in frequent video freezes, corrupted image decoding and high GPU load
I’m not sure if it was kernel or plasma, but it did go away with ostree rollback, and seems to be fixed in the latest rolling release
Not sure if its your case, just though it worth mentioning
I am currently on Plasma 6.1.4-1.fc40 and Kernel 6.10.4-200.fc40 and can confirm that everything GPU stressing is always scary as I expect a crash. And if it crashes, it crashes badly. But I cannot say that it has gotten worse. Has more or less always been that way.
Just saw that, alongside updates to 6.10.5-200.fc40 and Plasma 6.1.4-2.fc40 there are updates for “amd-gpu-firmware” and “amd-ucode-firmware”. Not expecting much of those kernel & plasma updates, but maybe the firmware ones bring hope? Will test that soonish.
1 Like
This a stable configuration for me, at the moment:
ostree 319076423a90a3de2cd75e9e439359218f3a5bd056dc9bbca6e5d98b8001c679
amd-gpu-firmware-20240811-2.fc40.noarch
amd-ucode-firmware-20240811-2.fc40.noarch
plasma-desktop-6.1.4-1.fc40.x86_64
kernel 6.10.5-200.fc40.x86_64
Did you ever fix that function key issue?
Hi, I am using Fedora40 i3 spin for Framework 13 and I have a problem with my microphone.
When I use the pavucontrol, it seems microphone is recognised by device yet it doesn’t get my voice as an input but rather keep getting a whitenoise as an input.
I reinstalled pipewire and alsa-lib by following audio troubleshooting but it doesn’t help. Can anyone help me please?
Do you have the micro and camera switch at the top of the brezel OFF?
Yup i checked the switch is on when I test it, and camera works fine. Just microphone input doesn’t pick up the voice but white noises
1 Like
I am also facing problems with microphone, a lot of white noise and distortion. I have tested on windows and it seems to work fine
I’m still experiencing freezes in Firefox under Fedora 40. E.g. when browsing https://www.openstreetmap.org/ or hovering over game thumbnails on https://gog.com.
sudo dmesg gives me this output:
[ 2214.465529] amdgpu 0000:c1:00.0: amdgpu: [gfxhub] page fault (src_id:0 ring:24 vmid:2 pasid:32777)
[ 2214.465537] amdgpu 0000:c1:00.0: amdgpu: in process firefox pid 10071 thread firefox:cs0 pid 10173)
[ 2214.465541] amdgpu 0000:c1:00.0: amdgpu: in page starting at address 0x0000000000000000 from client 10
[ 2214.465545] amdgpu 0000:c1:00.0: amdgpu: GCVM_L2_PROTECTION_FAULT_STATUS:0x00201430
[ 2214.465548] amdgpu 0000:c1:00.0: amdgpu: Faulty UTCL2 client ID: SQC (data) (0xa)
[ 2214.465550] amdgpu 0000:c1:00.0: amdgpu: MORE_FAULTS: 0x0
[ 2214.465553] amdgpu 0000:c1:00.0: amdgpu: WALKER_ERROR: 0x0
[ 2214.465555] amdgpu 0000:c1:00.0: amdgpu: PERMISSION_FAULTS: 0x3
[ 2214.465557] amdgpu 0000:c1:00.0: amdgpu: MAPPING_ERROR: 0x0
[ 2214.465559] amdgpu 0000:c1:00.0: amdgpu: RW: 0x0
[ 2224.533286] [drm:amdgpu_job_timedout [amdgpu]] *ERROR* ring gfx_0.0.0 timeout, but soft recovered
To give some context, I have taken the following steps to set up hardware video acceleration in Firefox:
- Run the steps from Howto/Multimedia - RPM Fusion, that is the steps as listed under (a) switch to full ffmpeg, (b) install additional codec and (c) Hardware codecs with AMD (mesa).
- Set
media.ffmpeg.vaapi.enabledtotrueinabout:config.
Some more output:
$ vainfo
Trying display: wayland
libva info: VA-API version 1.21.0
libva info: Trying to open /usr/lib64/dri-nonfree/radeonsi_drv_video.so
libva info: Trying to open /usr/lib64/dri-freeworld/radeonsi_drv_video.so
libva info: Trying to open /usr/lib64/dri/radeonsi_drv_video.so
libva info: Found init function __vaDriverInit_1_21
libva info: va_openDriver() returns 0
vainfo: VA-API version: 1.21 (libva 2.21.0)
vainfo: Driver version: Mesa Gallium driver 24.1.7 for AMD Radeon 760M (radeonsi, gfx1103_r1, LLVM 18.1.6, DRM 3.57, 6.10.11-200.fc40.x86_64)
vainfo: Supported profile and entrypoints
VAProfileH264ConstrainedBaseline: VAEntrypointVLD
VAProfileH264ConstrainedBaseline: VAEntrypointEncSlice
VAProfileH264Main : VAEntrypointVLD
VAProfileH264Main : VAEntrypointEncSlice
VAProfileH264High : VAEntrypointVLD
VAProfileH264High : VAEntrypointEncSlice
VAProfileHEVCMain : VAEntrypointVLD
VAProfileHEVCMain : VAEntrypointEncSlice
VAProfileHEVCMain10 : VAEntrypointVLD
VAProfileHEVCMain10 : VAEntrypointEncSlice
VAProfileJPEGBaseline : VAEntrypointVLD
VAProfileVP9Profile0 : VAEntrypointVLD
VAProfileVP9Profile2 : VAEntrypointVLD
VAProfileAV1Profile0 : VAEntrypointVLD
VAProfileAV1Profile0 : VAEntrypointEncSlice
VAProfileNone : VAEntrypointVideoProc
What am I doing wrong here? How can I troubleshoot this further? Or should I revert to Fedora mesa instead of using the RPMFusion one (I can live without the hardware acceleration) and, if so, what would be the best way to do it?
I am sad to say that I have no real updates so far, I am still under discussion with the support team concerning this issue. During the process, I was able to reproduce the issue on a live USB with both last versions of Fedora & Ubuntu. Performed RAM & SSD checks. Also on a “true” fresh install of Fedora 40 on a 125GB SSD stick.
Once the conclusion comes with the support discussion, I will ask if I should share the whole diagnostic process had to follow (~30 emails so far).
Just a quick hot take in case you haven’t tried this: The mic gain should be set quite low with this hardware to avoid noise/heavy distortion:
THis is my sound settings. I use i3wm with Fedora. The input bar is keep shaking even with or without any voice input. I think that is the white noise. Yet, I am not sure what is wrong…
That seems pretty high, try much closer to the “Base” mark.
This helps to reduce the white noise but microphone doesn’t recognise any input. It doesn’t change with my voice
At this point in your shoes I’d replicate this with a vanilla (i.e. GNOME) live image of F40 Workstation, to rule out the small possibility it’s something in the software audio stack or particular user config. If it persists then I’d call it a hardware issue and contact support.
Im fighting with this bug since I got my AMD Framework 13. Most crashes I got with KDE and Firefox, but I couldn’t reproduce it on a live USB version (yet).
Everything is as is out of the box, and im about to confirm to support that im getting the crash with Firefox only. Somewhat worried that it will be categorized as a Firefox-bug or smt like that.
No idea if @kholdstare found a workaround, but needless to say, im very annoyed that the otherwise great laptop is having this issue. 
1 Like
No workaround found, it’s just One of Those AMD Things that’s been a plague since 680M. It happens far less often now but still happens enough I can’t use Linux at all for things like running presentations. I’ve found that browsing through gifs in Discord is a good way to trigger a crash…
sudo nvme smart-log /dev/nvme0n1 | grep unsafe
unsafe_shutdowns : 205
This is a good way to keep track of how many times you’ve had to hold the power button down 
2 Likes
You mentioned running presentations, do you have any suggestions for the contents of said presentation… or the software used?
I need to reproduce this bug with something other than Firefox and I didn’t have much time to experiment the last week. : (
Edit: 67 unsafe shutdowns 
Hi everyone, sorry for being late with this issue. I went through the whole process with the framework support concerning this issue. At the end of the process, the conclusion was (for my case) a mainboard issue and lead to a replacement.
To arrive to this conclusion, many testing steps were required (because it could be more or less anything about hardware). Therefore, here is a summary of steps given by the support team I had to follow during the process. The aim of this list is to try to shorter the whole process by giving more details directly to the support team. Please note that I did not touch windows for a while so it was not question of it through this process, but some part may stay relevant. Also, I most of diagnostic on Fedora so some filenames could change over different distributions.
Also, do not hesitate correct me / give further details / provide links / give alternative tests or orders. This is a try to summarize > 2 months of exchanges. Maybe a comment from a support member could help re-organize / order the steps for a more coherent report.
For my case as described in this feed above, I went to the random crashing issues. I hopped from distros to distros (only linux ones), configuration to configuration (GNOME, KDE, etc…) and still got these crashes.
-
Use the given template here to redact your message for the support team .
-
Potentials updates: if you do not have the latest version of one element in the list, please update to the latest version available:
- BIOS (see the framework guide for AMD).
- Firmware update (Western digital SSD without WD Dashborad link for example).
- OS version (depending on your OS).
- software packets (depending on your packet manager).
If the problem is not solved, while contacting the support team:
-
Logging and initial information:
- Previous Troubleshooting:
- Document any steps you’ve already taken to fix the issue, such as:
- Updating firmware and drivers.
- Changing kernel parameters.
- Testing different Linux distributions and desktop environments.
- Disabling hardware acceleration in applications (some such crashes were caused by some hardware acceleration in web browsers).
- When you want to get some logs, use the newer log script from Framework GitHub to get logs:
link. Downloading / usage instructions are given there. - Note when the problem first started occurring.
- Note the BIOS version (Press F2 repeatedly during startup to enter the BIOS menu & look for “InsydeH2O Version” on the main BIOS screen).
- List all external devices connected to your laptop:
- Hubs
- Docks
- Monitors
- eGPUs
- Third-party power adapters (provide make and model)
- Take some pictures of the opened laptop to see if there is no defaults without plastic shrouds (the small plastic part glued on top of more than one component with QR codes).
- Run the following block of commands:
github_link (the forum does not allow scripts t seems)
You should get a tar archive to send to the support.
- Previous Troubleshooting:
-
Connections & expansions cards: try to see if the issue occurs when:
- You are using a third party specific device connected (dock, hub, monitor, etc…)
- If the issue occurs when charging / on battery
- Using a specific expansion card
-
Reset RAM & mainboard, Memtest86
- Run Memtest86+ on the RAM sticks, make few rounds on it
- Try to reset RAM (just remove and replace RAM stick(s) inside slot(s) and the mainboard tutorial
-
Check kernel parameters:
- Try to set the nomodeset parameter to 1 and see. To my understanding, this parameters put graphic processing in “default-and-no-error-mode”. The laptop become barely usable (since no “complex” graphics are used) but it can help determine the cause of the issue.
Now the point will be to test the following points on both your own system and another live USB using one of framework-officially-supported distros (Ubuntu 24.04 & Fedora 40 right now I think). In my case, crashes where easy to trigger so it was “fine”. But in the case yours are less frequent, it could become longer. The best is to try with both Ubuntu 24.04 and Fedora 40 (as I had to do) but I am not sure that the support team will ask for two distros.
- RAM swapping, CPU stress test on your installation and Fresh USB live:
- Try to swap RAM slot
- If you have more than one RAM stick, try to reproduce the issue with only one RAM stick. Swap the unique stick slot.
- If you have two sticks, also try swapping slots between sticks
- Run a filesystem check with the tool of your choice (for example use GNOME disk utility). You will may need to boot on an USB stick to test your FS without mount it.
- Try to unplug every connected expension card. Replug one by one and see if you can discriminate either one expension or one mainboard’s internal USB-C connection (one of the fours slots).
- Install s-tui & tmux with your package manager & run this
This command starts s-tui in a detached tmux session, runs a stress test for 2 minutes, logs data to s-tui_data.csv, and then stops.
Think to perform these steps on both your installation and a fresh live USB stick. If it does not matter, you could re-install the distro on your laptop. But in my case I had to not so I used USB sticks for testing fresh installation (plus it helps discriminating a faulty SSD). Here either you can try to do so with Fedora / Ubuntu installer, or install a full OS on a bigger USB (I did it with a 128GB USB that usually run Arch for instance).
In my case I only had to watch a YouTube video for a while on a fresh installation to trigger the crash. So during the process, the support team asked me to install lm-sensors and while running a video, launch a terminal (with the “keep on to” option) and run: ‘watch -n 1 sensors’ until the crash happen (while filming). I then shared videos samples on a drive solution.
Hoping this will help some of you with that issue.
1 Like
This is a very good summary of the same process I’ve been through with support in the past 4 weeks about my crashing/reset issues. I’m fairly confident I’ve exhausted all practical options to isolate the problem or cause; so I believe there’s an issue with mainboard. I’m documenting my adventure here: Framework 13 AMD Hard Crashing Issue - #9 by Joris_Kurst
I was so keen to be switching to AMD, but now I’m wondering if I make the jump back to Intel?