I just posted another update to the GitHub issue regarding 240W chargers and dGPU performance degradation: DGPU isnt using full power limit on 240W charger while in performance mode · Issue #27 · FrameworkComputer/SoftwareFirmwareIssueTracker · GitHub
More data points and a few different settings to show that performance mode has unstable framerate in all configurations with a 240W charger.
Feel free to add more data to it as you see fit!
What kernel version are you on?
I am having the same issue as @Obasav - I can set the wattage to any value from 100 to 120 - and I can try and set the lock on the power state for the GPU and memory to the highest clocks - but it still, once the laptop hits 95% or lower battery, goes haywire and I get major stuttering.
Also, what version of LACT are you using?
Is anyone aware of a way to micromanage power targets like this in Windows? Were I not stuck in Adobeland I’d likely be on Linux by now but alas. If not for being forcibly throttled down to an downright unplayable 30W at 95% battery, then this whole issue would be a much lesser inconvenience than the complete exasperation it currently is. If I could just lock it in at 60W or something I could much more easily live with the results for the time being. I can’t even get it to stop throttling on the 180W charger anymore
Given that this issue has not yet been resolved and is so highly disruptive, could you guys not release an “alternate” 3.05b that’s simply a previous BIOS version modified to be able to “upgrade” to from 3.05 as a temporary way to get around the anti-rollback “feature?”
Everyone, please keep this thread on-topic. This thread is primarily for individuals to report issues around the update and/or receive assistance. If you want to discuss other aspects of software support, you’re welcome to open another thread. Further off-topic replies will be deleted/split into different threads.
@TheTRUEAsian
I am not sure which messages you think are off-topic.
I do think making the BIOS upgrade such that it is impossible to rollback was an unwise choice.
That message is fine. There was another off-topic message that has been removed. This is just a general reminder as we’ve seen these threads easily get derailed.
Framework 16 Randomly Shuts Off also appears to be due to the 3.05 BIOS.
Framework employees…
Any update to the progress of the new firmware, or a beta version?
Still waiting…
I’ve been going back and forth with support for a week and a half to diagnose the issue, and currently they’re wanting to replace my mainboard though I’m not currently in a situation where I can receive one. I would encourage anyone who has the time to run through a bunch of diagnostics with them to submit a ticket so they can gather more data points regarding the issue and see it’s clearly not a unit-specific phenomenon.
In my case, stable performance is only possible through the FW-supplied drivers using the FW 180w charger, but MH Wilds crashes on startup with those drivers so that’s not an acceptable option for me anyway.
And for the record, as a result of the diagnostic process it seems that power draw is not the problem but a symptom of an underlying problem. I was hanging around ~30w draw while being throttled at 95% battery, but when just running the game to trigger the issue rather than actually playing it, I noticed that it would actually draw at a range between 50w-95w in a volatile manner, and regardless of draw the stuttering issue was exactly as bad as when I was actually playing and it would hang around ~30w.
Meanwhile, on the Framework-supplied drivers, power draw was rock solid. But on other drivers, performance was still stable until the 95% trigger even though power draw was significantly more variable.
Any updates? The known issues list is only getting longer and there hasn’t been anything as much as a word on when we can actually see fixes happening. No new firmware releases for months. Not looking good Framework, not good at all.
Since AMD seems to be poised to announce RDNA 4 laptop GPUs next week, I’m expecting Framework to announce an upgrade for the 16 in the not too distant future. Seems like an ideal time to fix the EC bugs.
That sounds terrible! If they announce new upgrades for the 16 but not bothering to fix the issues with the current hardware, that is very bad.
I’m certainly ain’t buying nothing from framework until it’s fixed. And maybe not even when it is.
Well, I would think that since there has recently been an FL13 BIOS update that that will flow through into the FL16 soon.
The lack of communication around this has been a driver for community moral dropping around the FW16.
“21 days later”
It is community forum and not official support channel. Framework does not announce anything unless it is almost ready. I do not like it but it is how it works.
Regarding new bios for FW 16 I assume that they are working on it based on that comment from github Bug: "\\.\GLOBALROOT\Device\CrosEC" not found · Issue #80 · FrameworkComputer/framework-system · GitHub
it is related to backporting signed driver for EC and bios changes. it looks like there will be some update for FW16