Framework Laptop 13 Intel Core Ultra Series 1 BIOS 3.04 Release

Framework Laptop 13
,
7

The link to the linux download in Kieran’s post is this:

https://framework_laptop_13_intel_core_ultra_series1_capsule_signed_allsku_3.03_3.04_efi.zip/

So it is missing the domain that appears to be in the link to the windows version.

2 Likes
9

Thanks for catching the link, i updated the top post with the correct link.

4 Likes
10

Installed fine via EFI, fwupdmgr didn’t show any available updates even with lvfs-testing enabled.

So far, so good.

11

Same for me; lvfs command ran successfully and i enabled the repository in Discovery of Fedora 41, but no update was offered so i proceeded to run the update from USB and that went trough fine.

12

When will this BIOS version hit stable? I use my Framework as a professional machine so I dont really wanna use beta versions :slight_smile: But the battery charge limit changes look really nice.

13

I’m using this since day1, and manually set the Battery Extender days from 5 to 1, it works great and no other issues found.

14

This BIOS release is promoted to stable as of today!

4 Likes
15

After update 3.03 → 3.04 mine does not recognise the trackpad anymore…
Some idea what to do on windows?

16

Try rerunning the driver bundle.

17

Did this - no change.
Solved: Had to re-activate camera in bios and restart once.
After this i could deactivate it again; everything fine now!

18

Just installed the efi shell update (I’m on fedora 41) and my external monitor isn’t recognized anymore. Any idea what might cause that?

Edit: nevermind, the issue seems to have resolved itself by unplugging the HDMI expansion card and plugging it back in, as suggested here.

19

Dual Booters Beware.

I’m running a Windows 11/Fedora dual boot config. My first attempt at BIOS updating failed. There was not enough room in the EFI disc partition to unpack/complete the process. Turns out my EFI partition was only 100Mb in size. A result of the Win11 install.

So I booted a live USB Fedora environment, and used gparted to resize/move various partitions to be able to grow the EFI partition. Well I could enlarge the EFI partition just fine, but gparted could not expand the file system contained in it. I spent about 45min. trying to find a solution, no joy. I finally copied the EFI partition contents to a temporary location, and with gparted deleted the EFI partition, recreated it (careful here, there a flags to be set) and copied the contents back into the new (larger) EFI partition.

Afterwards the system booted W11 just fine. But Fedora would not boot. :frowning: . I spent another 30-45 minutes trying to figure out how to fix the Fedora booting issue. No luck, finally I just reinstalled Fedora.

Everything is now back up and running just fine, and my EFI partition is 1G in size (future proofed). An interesting, informative experience. :wink:

–
Rod

1 Like
20

After updating first to 3.03 and then subsequently to 3.04 automatically via the firmware updater tool in Ubuntu 24.04, my system would not successfully boot, and the init LED codes suggested that DDR OK failed. I have 2x16GB ram installed, which was working without issue before this update. I pulled one of my Crucial (CT32G56C46S5) 16 GB RAM sticks and it successfully booted again. It does not appear to be an issue with the the individual stick or the channel. I booted successfully using each stick alone, but could not get it to boot using both sticks, regardless of which channel they were placed in.

My thought was to lower the speed of the ram in the BIOS and try both sticks, but afaik, that is not possible? Any other thoughts? I do find it odd that this memory worked previously, but failed after the bios update.

I’ll open up an issue in the github issue tracker.

2 Likes
21

I had a similar issue. After upgrading to v.3.03 with the firmware updater on Ubuntu 24.04, the laptop wouldn’t post with Crucial 2x16G CT2K16G56C46S5 (32GB).

Here is what fixed it for me:

  • Removed SODIMM 2. It still couldn’t boot. Physically disconnected the battery and reconnected it. The laptop booted with only 16GB memory on SODIMM 1.
  • Upgraded to v.3.04 with Ubuntu firmware updater, and the laptop booted again with 16GB memory.
  • Turned off the machine and installed the second memory. Disconnected and reconnected the battery, but the laptop couldn’t post again.
  • I took out memory#2 again, and this time, when the laptop was posted, I went into the BIOS and disabled “Quick Boot” and “Quiet Boot”. Then, I chose the “Disconnect Battery” option in the BIOS and pressed F10 to save without an AC connection.
  • With the laptop powered down, I installed the second memory again and connected the AC. I turned ON the laptop and waited for the post. Laptop posted this time showing it testing the memory, when it finished it booted to Ubuntu with 32GB memory installed.
  • Rebooted again and enabled “Quick Boot” and “Quiet Boot”.
22

Thanks for the guide @Omid_Khalili . This worked for me. I only had 1 DIMM in channel 0, so I rebooted to disabled quick and quiet boot, enabled the “disconnect battery” option while only on battery power and saved. I then plugged in my AC power to reboot the system. It posted and did a quick memory test (15 sec or so) and showed all 32 GB reporting as passing. It then booted normally. I restarted to re-enable quick and quiet boot and disable “disconnect battery” option. Things appear to be working fine.

1 Like
23

The update didn’t work for me when using fwupdmgr on Ubuntu. Running the mainboard outside a laptop (no battery or display) and when booting I get to a screen saying “Please keep AC attached while updating.” After a few minutes, the board’s diagnostic lights come on with red lights for expected components not found and the update seemingly just hangs :pensive:.

Diagnostic lights are Blue Green Green Green Green Green Blue Green.

24

The left expansion slot nearest the audio port no longer works after performing this update.

Edit: seems to be working now after disconnecting the battery for a few minutes and reconnecting. weird.

25

Windows warns me about running this update (3.03) and says it is potentially harmful to my computer. In the box that pops up with the warning it says that the distributor is unknown. Can this be fixed?

26

is your PC battery at 100%?
i read somewhere that 100% battery causes an issue with bios updates on ubuntu and unbuntu based systems

27

It’s running in standalone mode so no battery but I was able to get a replacement from support.