Thank you for your guys hard work, this is very much appreciated.
3 Likes
Excited to see this and will update and report back.
One question to @Kieran_Levin - if we have already installed more recent drivers than included in the driver bundle, will the installer skip that particular driver?
Update went smoothly via LVFS, can confirm the UCSI errors are no longer present.
And what is “Z state support”?
What is the real impact of this issue?
3 Likes
Thank you for the 3.05, just updated, everything went well.
Any idea when/if a fix of this issue will come? I tried and unfortunately 3.05 did not address this bug, and this is a valid concern some users had for quite some time now.
(my offer to provide FW my drive/enclosure/cable for testing still stands)
Edit
Further tested, behaviors I described in the original post can all still be replicated.
3 Likes
Might be the display controller sleep state as mentioned in this article
2 Likes
Ok - couldn’t wait 
Driver bundle does overwrite older driver versions. For me, this meant reinstalling AMD Adrenaline and chipset drivers again after the bundle installed. No other way to get the updated Fingerprint Reader, Wifi drivers etc.
Otherwise, so far so good. Bios updated and all running fine. Will keep an eye out for the daily Windows crashes and sleep issues to see if they are resolved/reduced.
1 Like
- Change the BIOS password to remove password expiry after one month.
- Modify the BIOS password complexity requirements to only require a minimum length.
I was losing hope but y’all are awesome, thank you for this!
7 Likes
Are the checksums posted anywhere other then this forum? I would like to cross reference them to make sure it is the real checksum. Maybe on GitHub, FW socials? Posting in one place doesn’t isn’t the most secure method, especially with bios updates. Would be even better if they were signed.
2 Likes
Cross posting in case it’s helpful: Hibernation used to work but stopped working some weeks ago (AMD13). Suspend works fine. The hibernation problem persists after updating to the new BIOS (3.05). The screen goes black, then is restored, but neither mouse nor keyboard respond, and only shutting down by long power button press and restarting works.
3 Likes
Indeed. I have the same problem (affects Modern Standby when Windows decides to hibernate after a period of battery drain).
@Kieran_Levin I just updated (LVFS). All seems good so far (just minutes into the new BIOS) but it also brought back a wake-back-up-on-lid-close issue that’s almost (not 100%) identical to the original report in this old thread:
- All done while plugged in to dock (also provides power).
- Suspend using power button.
- Close lid.
- Machine immediately wakes up.
The only change here was the BIOS+EC update, everything else stayed the same: Fedora 39 on 6.7.11-200.fc39.x86_64.
That original issue above had been worked around at the time with a udev rule:
$ cat /etc/udev/rules.d/20-framework-suspend-fixes.rules
# Disable wakeup from spurious keyboard event caused by power (un)attach (working around FW EC bug).
ACTION=="add", SUBSYSTEM=="serio", DRIVERS=="atkbd", ATTR{power/wakeup}="disabled"
but that hadn’t been necessary for some time now as a kernel workaround rolled out (for Fedora IIRC it was backported during the 6.6 series) so I had disabled it then.
Re-enabling the udev rule mitigates this for me with BIOS 3.05. The only “loss” (if you can call it that) is that the power button no longer pulses while sleeping after the lid is closed. No biggie, just a little side loss (or benefit for some I guess).
There’s FW/AMD things brewing upstream:
https://bugzilla.kernel.org/show_bug.cgi?id=218641
has anything that sorta-reverted that earlier kernel workaround been backported to stable kernels?
ccing @Mario_Limonciello and @Matt_Hartley here I suppose.
3 Likes
I did the update. Boot up and the system operates seemingly ok. One improvement tested: Can close the lid and open again and the system stays on instead of turning completely off.
CLI tool displays correct new version info (3.05).
However, when I went back to turn off booting from USB in the bios options, password I used before now no longer works. Used to show when typing up to 10 characters, now there is 64 character p/w indicator. I can’t edit bios anymore. I’m pretty sure I’m not mistyping or leaving all caps on, or something like that. Even walked and took a few hours break before trying again.
How screwed am I?
4 Likes
It only applied to BIOS 3.03 as we were anticipating it fixed in next BIOS. I guess we need to extend the quirk to this BIOS too if this goes to stable.
Kieran mentioned it in known issues above; it’s still being investigated.
I’ve noticed since upgrading sometimes my caps lock is wrong.
5 Likes
Excellent work. Thank you very much for the very informative post and detailed recap. I appreciate you all keeping your word to include the hashes, and really make this release very smooth and professional; with bonus transparency on what’s next.
Excellent testing and feature deployment, very impressive turnaround. This was much needed, and framework delivered on all counts.
You can extract the exe using 7-zip and just update the stuff you want in device manager.
1 Like
Perhaps you can try rolling back to 3.03 BIOS with the 3.03/3.03B package?
I should have thought about that - thanks!
why is it called BETA? is it not a final release?