Framework Laptop 16 Ryzen 7040 BIOS 3.05 Release

Framework Laptop 16
92

Is this update available in fwupdmgr yet? It seems to believe I’m up to date.

Edit: After running system updates and then trying to use fwupdmgr got me to install the update. Not sure why that’s needed and what the purpose of refresh and get-updates is, but oh well I suppose.

93

Yes, I installed it yesterday using the stable LVFS channel.

94

Did the bios update change the default vram values?

Setting the option to “Gaming” in the bios, and now my iGPU is reporting 8gb of vram. Not really an issue for me since I have 64gb. But I did prefer having 4gb as an option.

image

95

You can still set it to 4GB with Smokeless_UMAF

1 Like
96

On 3.05 I am unable to boot into windows with Auto iGPU VRAM settings. On gaming mode I am booting just fine. I have tried loading optimized defaults, booting in safe mode, and reinstalling graphics drivers. When booting on auto I get to a white screen and freeze.

Windows 11 24H2, 7840HS, 7700S, and 64GB 5600MTs CL40 RAM.

97

You have the exact System Config thats problemstic with current AMD Drivers. There is a note on the 3.05 Bios, that Systems with 64+GB of Ram can have Problems with later than 24.8.1 Adrenaline Drivers when not beeing set to Gaming in Bios.

98

I have the exact same system, except Windows 10. I’ve been using latest drivers since day 1, and nary an issue. Eat it, 11.

1 Like
99

I am unfortunately experiencing major GPU flakyness on Fedora 41 after the upgrade. I filed an issue here. I hope it gets resolved soon, as this gets in my way a ton, as it isn’t only affecting gaming but also video playback in Firefox and MPV and requires frequent hard resets.

1 Like
100

wait, smokeless_UMAF work on framework?

101

Yup, disable safe boot and its good to go.

102

I’m 3.05 since Beta and noticed that periodically and suddenly at random times my computer slows down dramatically, i.e. imagine normal function of everything but at 200MHz instead of >2GHz - mouse movements are laggy, video starts chopping.
I’m on Fedora 41 KDE. I thought it was GPU originally but there are no errors in the logs at all related to the GPU. The only error I could find in the last slowdown that happened was:

kwin_libinput: Libinput: event4  - PIXA3854:00 093A:0274 Touchpad: client bug: event processing lagging behind by 247ms, your system is too slow

Anybody experienced anything like this?

1 Like
103

I’ve had that happen once. CPU wouldn’t go above 500MHz on any core (noticed it being laggy then confirmed via /proc/cpuinfo). For me what fixed it was unplugging and then replugging the charging cable.
Hasn’t happened since, even on the same charger (I was/am using the 70W(?) or so Apple MacBook brick I got laying around)

2 Likes
104

I have seen it also on my FW16, but not often.
I have not tracked down the source but I have not discounted the following yet:

  1. IRQ storm. Maybe some GPE interrupt being kicked off unnecessarily.
  2. USB storm. I.e. one device on the USB bus that is preventing others from working. This might be one of the chips on the mainboard misbehaving, so not necessarily an external device. I don’t know which.
  3. All CPUs kept at 500Mhz.
  4. Some bug on the EC somehow affecting performance.
2 Likes
105

That exact problem, at least when caused by disconnecting TB docks, is one of the fixes in this BIOS release.

106

For me this problem appeared only after installing this BIOS patch and never before. My problem also started at random, not associated with TB dock disconnect.

107

I had that happen once pre 3.05. Unplugging and then plugging in the charger seemed to fix it. I’m using Windows 11 Pro though. And it’s never been a reproducible behavior.

108

Cross-posting here.

Can’t roll back to 3.04 to test… but it seems that the dGPU is having some issues when the 240w power supply is being used.

2 Likes
109

I updated the GitHub issue this morning, the issue is present while running the system in performance mode while connected to the 240W charger.

I switched my system to balanced and it seems to give a more normal power usage.

110

Another thing I started noticing that’s definitely new as of 3.0.5: Often after a wake from hibernate, the USB-C PD sensors (via Linux sensors / lm-sensors) all report 0 V / 0 A, even if a power adapter is plugged in and the laptop reports being charged (and the LED next to the port is on).
Unplugging and plugging it back in makes the Voltage / Current show up correctly.
Not sure if this is connected in any way to the other power issues people have been seeing, and just a minor symptom of it?

1 Like
111

Flaky usb issue continue (ports 3,6 with usb A modules)

Charging through dock with the pd 3.1 chargers remains fixed.