# Fedora 40 on the Framework Laptop 13 **URL:** \ **Category:** Linux\ **Tags:** fedora\ **Created:** [March 26, 2024, 5:01pm UTC](https://community.frame.work/t/fedora-40-on-the-framework-laptop-13/47746 "2024-03-26T17:01:11Z")\ **Posts on this page:** 1\ **Showing post:** 86
**Author:** ![FW\_NT](https://avatars.discourse-cdn.com/v4/letter/f/e5b9ba/32.png) [@FW\_NT](https://community.frame.work/u/FW_NT)\ **Post date:** [November 1, 2024, 9:03am UTC](https://community.frame.work/t/fedora-40-on-the-framework-laptop-13/47746/86 "2024-11-01T09:03:41Z")
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. 1. Use the given template [here](http://community.frame.work/t/please-tag-your-posts-and-read-this-before-posting-a-support-question/25410) to redact your message for the support team . 2. Potentials updates: if you do not have the latest version of one element in the list, please update to the latest version available: If the problem is not solved, while contacting the support team: 1. Logging and initial information: 2. Connections & expansions cards: try to see if the issue occurs when: 3. Reset RAM & mainboard, Memtest86 4. Check kernel parameters: 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. 1. 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](https://github.com/ntgmx-git/fw13-support-archive/blob/main/tmux-command) 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. --- _[View the full topic](https://community.frame.work/t/fedora-40-on-the-framework-laptop-13/47746)._