I’ll throw my experience here. On powersaver, performance is what you would expect. Hits about 74C before the fans kick in and bring it down to 68ish, starting at 3.2 GHz but dropping to 2.8 GHz. On performance, I get to about 90 before the fans start kicking in hard (but not max). They’re able to keep the temp from going over 90 (one one test they did make it to 92). CPU was at 3.6 the entire time.
Installation worked fine with Fedora 39 LVFS for me. Can recommend.
1 Like
I read your post before I updated to 3.05, so I was paying attention to the fan behavior while running Cinebench R23 (multi core). The benchmark with BIOS 3.03 and 3.05 runs the same, with the same score (about 13800 pts), and with both BIOS versions, the fan takes quite a while to start spinning (maybe 30 seconds?), when the CPU Tctl/Tdie temperature is around 85-90°C. It seems quite late, but it does not impact the benchmark. By the way, if you look at the notebookcheck.net review, you will see that they scored 13981 pts in Cinebench R23 (multi core) back in October 2023, so I’d say nothing negatively changed since then?
Thanks for the insight as well!
Yes, performance is as expected, this never changed for me. It’s exactly what I would expect from this form factor so no issues here. And once the fan kicks in in full, temperatures do settle 92-95C, as was always the case (which is fine).
I’m just surprised at how sluggish the fan is to ramp up. Maybe it was the same in 3.03, as with your experience. I’m not sure. But without downgrading to 3.03 I can’t really confirm. I always thought the fan was a bit slow to respond but seemed ‘okay’. Maybe I’m actively looking into it too much as a result of it being mentioned earlier?
In any case, I still don’t think that 30-40 seconds at roasting 100C is “healthy”, even if the CPU itself will throttle down. If this is has been the ‘expected behaviour’ up until now, perhaps something for the FW to look into in the future.
I’m having the same issue on debian sid.
What i find worrying is that the fans won’t ramp up at single core loads at all.
1 Like
Here’s a graph of temp and fanrpm on my 3.05 bios 7840u for discussion.
I started cpu stressing at around 20 seconds. (where temp starts rising)
1 Like
Installation happened mostly automatically with Fedora Silverblue 40 Beta using Gnome Software (LVFS) for me, just was kinda slow (a black screen for about 10-20 seconds, which were slightly concerning and then a very slow progress bar).
This Happened to me too, laptop shut down, stayed on black screen for ~3h. first time till i force restarted and said decompress failed. second time it shutdown because it ran out of battery, upgrade started on 100%.
My FW 13 Ryzen came with 3.03, so I’ve never done a bios update before. I see the simplest approach is this:
fwupdmgr --force refresh
I’m on Ubuntu 22.04.3; do I need to follow the instructions here:
to switch to the snap of fwupd first?
The longer description of how to do the update using a USB key seems more complicated; when would you need to do that? Is that for distros that don’t have the latest fwupd available?
All help appreciated,
Martin
@Martin_David_Holmes Yes, please follow the instructions in the article you’ve linked. I have scripted those instructions as follows (to make it a one-shot update):
#!/usr/bin/env bash
set -xe
fwupdmgr refresh --force
fwupdmgr get-updates
fwupdmgr update
Since you’re on Ubuntu 22.04, you’d also need to update fwupd before updating firmware:
sudo apt remove fwupd
snap install fwupd
Thank you!
1 Like
That worked perfectly, although the update took a long time to complete. The fingerprint reader is working now too.
1 Like
After upgrading to 3.05, experienced serious issues with Fedora KDE. I tried reinstalling and also tried installing OpenSUSE. Both experienced the same problems. Periodically all apps would force close and the whole Plasma shell would crash - the screen would be completely black except for my cursor. Only option would be a hard reset.
After downgrading back to 3.03, I haven’t experienced the problem. Just wanted to warn others, maybe it only affects KDE.
2 Likes
Works fine here. Where those clean installs or did you retain some configuration (e.g home partition)? Sometimes configuration in ~/.config or ~/.cache can mess with KDE.
Could also be a memory incompatibility issue due to the many changes in the bios.
1 Like
These were fresh installs so there was nothing in config or cache to mess with things. My only bios change was disabling secure boot. My memory came from Framework.
framewwork laptop 13 ryzen bios 3.05 successfully updated yesterday via linux and fwupdmgr. the actual boot/POST with the update flashing process took quite a while but finished without errors. back into linux with 3.05 uefi firmware showing and present. thanks.
1 Like
I updated my Ryzen 7040 FW 13 to 3.05 (running Ubuntu 22.04) this weekend and it went well, but my system no longer stays asleep. Today I tried restarting the laptop, and without starting any programs I put it to sleep. It woke up by itself within 15 minutes. It is connected to a Dell monitor that provides power and USB connections to my mouse and keyboard, but this that’s how it was before 3.05 too. This issue seems to have been introduced by the upgrade to the 3.05 BIOS.
Is anyone else experiencing this?
Hey,
thanks for the update and support. I have updated the BIOS using fwupdmgr on Fedora 39 and there was no issue during the process. However, on Windows 11 I noticed that the Device Encryption option has vanished. I have so far checked the following things:
System Information
Device Encryption Support: Reasons for failed automatic device encryption: PCR7 binding is not supported, Un-allowed DMA-capable bus/device(s) detected, WinRE is not configured
PCR7 Configuration: Binding Not Possible
Secure Boot State: On
BIOS Mode: UEFI
powercfg /a
As far as I understand, PCR7 requires S0 to be supported, which is the case, confirmed by powercfg /a.
tpm.msc
Reports the TPM to be available.
BIOS settings
Secure Boot is enforced
TPM 1.1 is enabled and set to available
I have read that e.g. Lenove firmware updates disable Secure Boot during updating and sometimes do not re-enable it, but both the BIOS and Windows report Secure Boot to be enabled.
Has anyone else ran into this issue?
This sounds like the IRQ1 issue very likely. You can use a udev rule to turn off keyboard wakeup for now.
Thanks to you both for posting these. Worked well for me.
Btw: I’m on Ubuntu 22.04.4 and didn’t need to replace apt’s fwupd with a snap.
Apt shows its version as:
fwupd/jammy-updates,now 1.7.9-1~22.04.3 amd64 [installed]
Snap does show a newer version available:
$ snap find fwupd
Name Version Publisher Notes Summary
fwupd 1.9.16 richard-hughes - Firmware updates for Linux
Thought this may help other’s not sold on snap packages.
1 Like