Is this just for 96GB devices? I have a 7840U with 64GB RAM and I seem to be having the same issue. I’ll try the workaround.
what was the problem with this BIOS?
Its mentioned in the first lines of the first message on this thread
## 2024-12-05 Release held at BETA - this release will not be promoted to stable.
We found an issue during the beta release period- where the battery will charge and discharge between the sustaining minimum and maximum thresholds, after the sustaining time has expired when the system is in the on state. For Beta users, you can disable the battery sustaining feature in the bios until we release 3.07. We are targeting to release 3.07 to beta to fix this issue by the end of December. This only impacts this product, and does not impact Intel Core Ultra, or Framework Laptop 16.
2 Likes
Is anyone experiencing the LEDs blinking white and red when plugged in and fully charged (at the charge limit)? I’m not sure if this is because of the 3.06 BIOS, but I’ve only started experiencing this after I upgraded from 3.05.
Video showing issue: https://imgur.com/a/tkdo07J
Did you turn off battery extender?
No, but I’ll try turning it off now to see if that causes the issue.
Assuming the answer is no, but any chance you’re still on target for this?
6 Likes
Any update on this? Having windows updates paused is not a sensible solution.
4 Likes
There’s an option shown above to only disable driver update without affecting windows updates
1 Like
I switch my iGPU mode to Gaming. It also solve this problem. I’m using 32G*2 and I can update to the newest driver.
can refer to this Framework Laptop 13 Ryzen 7040 BIOS 3.06 Release BETA - Held - #104 by Brian_Gregory
Not sure if it’s related to this firmware, but had an issue today where my CPU Skin Temperature (as reported in HWinfo64) was stuck around 30C, while the other temperatures were in the 90s, and the fan never came on.
As soon as I rebooted, the fan was on full blast and when I got into Windows, the CPU Skin temperature was reporting a real value of around 50C. (The fan then properly cooled everything back down).
was the laptop actual hot?
Hot to the point it was uncomfortable to touch the bottom of it.
That’s normal for a laptop with metal chassis. A sustained 15W load(power limit on best battery mode) is enough for the bottom of the computer to get hot.
This is not normal, the STAPM will reduce power further when the skin gets hot, the skin temperature should stop increasing and stabilize at or slightly below 45C.
I’ve seen something like this, for a long while and multiple firmware versions, in linux. It seems to me to depend on if I’ve accessed the sensor data “frequently”. The “cpu@4c” sensor can get stuck in an error state, and the EC auto fan control doesn’t work anymore, until the sensor starts working again (which usually needs a suspend or restart). But if I avoid accessing this sensor “too much” with ectool / lm-sensors, and avoid having a dock/bar widget which does so, then it works fine indefinitely.
Related thread: [RESPONDED] FW 13 7840U ACPI thermal readout problem - #22 by Steve-Tech
1 Like
I get that, but there’s a distinct difference between a general uncomfortable warm feeling like a laptop in general, and the practically burning my skin feeling when the fan was stuck off due to misreporting the temperature, as I stated in the previous post.
They’ve gone a bit quiet, I assume there are further issues.
The lack of timely firmware updates and persistent software issues are the biggest drawback of Framework products. Everyone is better off if you stop trying to cook something on your own with Insyde H2O and instead provide the Coreboot team and willing and skilled community members with hardware and documentation. This will make the Framework laptops much more open and community centered. Two values besides reducing e-waste that you guys seem to be praising. It also has a higher chance of resulting in usable firmware as you guys are lacking the staff needed to pull it off on your own. Might also be cheaper in the long run. And before someone blames AMD for the firmware issues, AMD is only partially to blame. Some issues appear on any OEM’s firmware implementation but Framework has had notoriously bad firmware on the Intel boards, too.
17 Likes