Framework Desktop not booting after Fedora System Updates

Hey there

First time writing here since I am experiencing some issues with my brand new Framework Desktop Batch 17.

After receiving it I mounted it and installed Fedora 43 KDE Plasma, flawlessy. I used the computer for about a week, putting some AI workloads and VMs, just to test how good my new “toy” was. During that time, I got a pop up from Fedora saying that some updates were available. I do not recall all the ones that were available, but Framework Firmware was one of those for sure. I decided to install them as Fedora is supposed to be officialy supported. After some hours of having done that (or maybe even a day) I powered off my computer through the “Power off” button in Fedora’s UI. No “Updates are pending” or “Process is not terminated” or anything like that was shown, so I assume everything finished successfully.

The next day, when powering on the computer, nothing at all came up. The computer LEDs turn on, the fan spins, but no HDMI/DisplayPort/USB-C output on the monitor is present, as well as no power at all on the USB-A ports (Mouse Light does not turn on; on USB-C with a hub it turns on). Note that i left it connected and so on for a while, with nothing at all being displayed (not even “framework” logo). Also note that Caps Lock does not light any light on my Keyboard. I tried everything I could think of:

  • Motherboard reset by clicking “cmos reset” with everything disconnected and draining residual current
  • Disconnecting for some minutes the RTC battery with nothing connected (everything including Power Supply cables disconnected from motherboard")
  • Tried all output ports (HDMI, DisplayPort, USB-C)
  • Tried to boot with no disk to see if at least I can see something (no success)
  • Inspected mother board, no visual defects I could see
  • Left it connected for an entire day, no changes

I don’t know if you might see something I’m missing. I also don’t really understand why this is happening. Since I installed a firmware update, I think I am not entirely off track to think that it might have bricked, but I can not find out why.

I already opened a ticket with support, with nothing clear yet, just sending some photos and the famous “LED video” I’ve seen on other posts, which can be seen here: https://drive.google.com/file/d/1Uw_xi3QtsBAiyncGjtqAXEg_xK7kcvVU/view?usp=drive_link. I did not manage to understand what it means, and Framework Support did not provide further clarification on the meaning of it, I would appreciate if someone in the community could provide me with that (I do not understand exactly what it says when using the Framework documentation on blink codes to decode it)

I’ve also found that support might be confusing my Framework Desktop with a Framework Laptop, as they told me to “Connect the USB-C charger to the raw USB-C input, not the expansion card” which feels odd since this is a Desktop and has no charger, but maybe I am missing out something.

At this point I feel I tried everything I could, and since I am already seeing that the Support request is going to be longer than expected, I wanted to get the support of the community and also leave some traces in case someone finds this behavior too.

Best

Alex

1 Like

Did you get a reply from support? I am in a similar situation (except in my case, fans stop spinning immediately)

I have similar issues. I had Bazzite but kernel 6.18 is not there and AMD seem to love 6.18. So I decided I reinstall with Fedora. At first it went fine. It loaded Fedora I created user, installed Steam, mounted by second disk. Rebooted. Framework Firmware got a lengthy update and Fedora is now stuck on “Booting ‘Fedora Linux 43.1.6 (Silverblue) (ostree:0)’. That is actually after I reinstalled again. I wiped out Secure Boot. I also tried disabling Secure Boot (May be I did not do it right?) . Nothing seems to help.

I wonder if I ought to try some other distro? I really wanted immutable Linux but hey it seems it was not meant to be….

Any hints or ideas?

I have similar issues. I had Bazzite but kernel 6.18 is not there and AMD seem to love 6.18. So I decided I reinstall with Fedora. At first it went fine. It loaded Fedora I created user, installed Steam, mounted by second disk. Rebooted. Framework Firmware got a lengthy update and Fedora is now stuck on “Booting ‘Fedora Linux 43.1.6 (Silverblue) (ostree:0)’. That is actually after I reinstalled again. I wiped out Secure Boot. I also tried disabling Secure Boot (May be I did not do it right?) . Nothing seems to help.

I wonder if I ought to try some other distro? I really wanted immutable Linux but hey it seems it was not meant to be….

Any hints or ideas?

PS It seems my system is booting ok after very long wait like 2-3 minutes. This is a known issue [TRACKING] Fedora 43 slow to boot (update: because of System Firmware 3.04) - #4 by sun . I am trying the downgrade hack to see if this will hold water for me.

Indeed. The newest firmeware version might show this long boot time bug. I downgraded to the previous version and that completely resolved the issue.

That does not explain however why for example a FW Desktop would not boot up in half an hour or so at all.

1 Like

This morning my FD did a wouldn’t boot thing. Let it sit for 30 minutes and no video out over USBC. Not even a UEFI splash screen. When I get home I get to trouble shoot. At least OP has a list of things to try.

system shut down fine last night. Only updates I installed yesterday were for Proton on Bazzite. Sucks especially because other than the known v0.34 long boot bug it had been putting like a kitten. I had previously rolled back that update an was on v0.33

I can’t think how some regular program update should brick the boot process. A Firmware update on the other hand could possibly do that.

This is bizarre. Tried to boot several times this morning, let it sit for half an hour twice–never got any video keyboard and mouse didn’t recognize being attached to a computer (had power though), just fans and the the system LEDs. Unplugged everything, went to work. Came back, and on a whim, plugged in–booted right back and up and purring like a kitten. I seriously don’t understand.

I was brooding all day at work about trying different cables and booting without drives.:zany_face: