Framework Laptop 16 Ryzen 7040 BIOS 3.03 Release and Driver Bundle

Framework Laptop 16
22

had the same issue - wouldn’t have noticed if you haven’t told me, so thanks.

When do we get 5V charging?

1 Like
23

Applied and so far so good. No change in the dGPU crashing when connecting an external monitor to the rear usb port after booting up. But completely expected as it’s not in the change notes.

Any plans to fix that? Or is it an amdgpu module bug?

1 Like
24

I applied the beta bios v3.03 on Friday and have had no issues except today Sunday after gaming on rpcs3 for ~ 1Hr I got a random reboot. No warning or Bsod. I went into event viewer and got an error anout windows boot environment failed to load the HSP firmware (the file %hs does not exist). Then after thay error there is an error reporting that the previous shutdown (which I was gaming and everything was working fine then) was unexpected. Weird thing is the shutdown says thay it happened 4 mines befoe the actual reboot did. Then after that there js a Critical error sayibf the system has rebooted without cleanly shutting down. I hope this helps, and if any more information is needed feel free to reach out.

25

This is a Microsoft invite program. We currently do not have this enabled due to lack of support from Microsoft.

2 Likes
26

What is the failure mode?
Can you describe the device you are attaching, OS, failure steps to reproduce.

27

Sure, I posted the issue here:

I have three different usb to hdmi adapters I can connect to the rear port (also the hdmi and dp expansion cards). They all act the same.

I have discovered recently that if I launch nvtop (need more testing, but probably anything that wakes it up will work), before connecting to the external port after booting up, it also works fine.

However, I noticed that it will never go back into D3cold mode again, even after rear usb is all disconnected and the dGPU is no longer in use.

28

Running Fedora 40 beta, and fwupdmgr doesn’t seem to see the update as available:
Determined that the current version is Version: 03.02, and verified that the metadata on disk even has the FW16 firmware in there.

I have disabled secure boot (or I at least think I have, it was weirdly complicated finding the secure boot menu)

Fwupd version:

$ fwupdmgr --version
compile   com.hughsie.libxmlb           0.3.17
compile   org.freedesktop.Passim        0.1.5
compile   com.hughsie.libjcat           0.2.1
compile   org.freedesktop.fwupd         1.9.16
runtime   org.freedesktop.fwupd-efi     1.4
compile   org.freedesktop.gusb          0.4.8
runtime   org.freedesktop.Passim        0.1.5
runtime   org.freedesktop.gusb          0.4.8
runtime   com.hughsie.libjcat           0.2.1
runtime   org.kernel                    6.8.4-300.fc40.x86_64
runtime   org.freedesktop.fwupd         1.9.16
1 Like
29

I have the same issue on my Framework 13, see:

I filed a bug report for it:

1 Like
30

Thanks

I managed to get it working by deleting everything in the var folder, disabling all remotes (including one called vendor-directory), then enabled lvfs & lvfs-testing, did a refresh, and then suddenly it worked!

I suspect something got into a weird state, and fwupd just went stupid.

EDIT: the fwupd’s var folder. /var/lib/fwupd/ not the whole /var folder :sweat_smile:

1 Like
31

I also had a similar question regarding the Graphics Driver as another posted in the AMD FW13 BIOS/Driver thread.

Does the version included in the Framework bundle include the fix for the “Display frozen after smart MUX switching” issue reported in the 6th and 8th FW16 updates? Is that fix going to be only available in the FW version of the driver and will we have to continually look to FW for the updated versions to include the fix or is that fix going to be rolled into all new drivers available directly from AMD, and does the 24.x version available directly from them include it?

1 Like
32

Are all new machines shipped with latest stable BIOS? I ask, because assuming this BIOS goes to stable in the next couple of weeks, I’m in Batch 12, so curious if it’s likely I’ll be getting this or not.

5 Likes
33

mine (Batch 8 wave 2??) was 3.02 i immediately updated to 3.03 as i plan on installing the 2280 ssd today or tomorrow.
(running OS on the 2230)

Now batch 12 i would assume 3.03 would be final & no longer beta by then but it only took like 10 mins if that to update.

1 Like
34

Folks, it is immensely helpful for Linux users to include their distro and fwupdmgr --version
Editing existing posts with these details works.

Thanks

5 Likes
35

Appreciate the details. Did you do the following:

fwupdmgr enable-remote lvfs-testing

fwupdmgr refresh --force

fwupdmgr get-updates

fwupdmgr update

2 Likes
36

Hi @jared_kidd,

I’d like you to get this into a ticket as I feel like there may be additional factors. A bit warning, we do not actively test against Arch, however, I’d like to get logs from you and see if we can spot the issue, repro again with you testing a few different things.

When creating the ticket, please link to this thread and mention this is for Matt Hartley and to be sent directly to me please.

4 Likes
37

Hi @Kelton_Page, I’d like you to get this into a ticket as I feel like there may be additional factors.

While I am exclusively Linux support, I would like to get this ticket in front of our engineering team and will be the one connecting everyone in the ticket.

When creating the ticket, please link to this thread and mention this is for Matt Hartley and to be sent directly to me please.

2 Likes
38

Has anyone encountered issues connecting with the USB-C enabled iPhone 15 Pro Max (or similar) after updating to 3.03? I am encountering an issue where the USB connection goes through an infinite connection/disconnection cycle after plugging it in via a standard USB-C to USB-C cable. This behavior occurs regardless of laptop power state (the behavior continues when the laptop is powered off). I have tried different cables and different ports but nothing resolves the issue. I sent a request in to support to have them look into the issue but it’s been a slow process of gathering data so far.

1 Like
39

As mentioned I managed to get it working by (as root):

  • Deleting everything in /var/lib/fwupd/.
  • dnf update --refresh
  • dnf reinstall fwupd
  • fwupdmgr disable-remote lvfs-testing
  • fwupdmgr disable-remote lvfs
  • fwupdmgr disable-remote vendor-directory
  • fwupdmgr enable-remote lvfs
  • fwupdmgr enable-remote lvfs-testing
  • fwupdmgr refresh --force
  • fwupdmgr update

I suspect fwupd might have gotten confused as I just upgraded from F39 to F40, and I have no idea what vendor-directory is about, but I suspect disabling that resolved things for me…

40

There seem to have been one or more bugs in fwupd or rather, the libxmlb depedency for it. See: No testing BIOS update available for Framework 13 · Issue #7060 · fwupd/fwupd · GitHub. The updated libxmlb (3.18) is already in Fedora to fix this. There might be more issues in fwupd though, there’s still discussion going on in a similar ticket.

41

Who can the userbase engage with at Microsoft to change this?

1 Like